Adobe Experience Manager is a combined web content management system and digital asset management system. The combined applications of Adobe Experience Manager Sites and Adobe Experience Manager Assets is offered by the vendor as an end-to-end solution for managing and delivering marketing content.
N/A
HCL Digital Experience
Score 9.0 out of 10
N/A
HCL Digital Experience is based on the former IBM Web Content Manager and IBM WebSphere Portal products, acquired by HCL Technologies from IBM in late 2018. The product allows the user to create, manage and deliver engaging omnichannel digital experiences to audiences with responsive content, targeted offers, seamlessly integrated applications and consistent branding across channels (web, mobile, and hybrid mobile/web applications and more).
N/A
Pricing
Adobe Experience Manager
HCL Digital Experience
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Adobe Experience Manager
HCL Digital Experience
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Adobe Experience Manager
HCL Digital Experience
Considered Both Products
Adobe Experience Manager
Verified User
Anonymous
Chose Adobe Experience Manager
End to end capabilities as well as integrations with upstream and downstream systems to make work flows, easier and faster time to market
SSO is one fits all, so we don't have to have a separate SSO for each application of Adobe The integration with Analytics works perfectly and bring directly value really quickly Target remains more complicated to set up, but can also bring a lot of value once integrated with …
Adobe Experience Manager is what I use most frequently. While the other tools I listed above are important, they are ultimately a secondary tool utilized on a need by need basis where as AEM is what we use daily for content creation, content updates, content optimization, etc.
AEM is comparable to Sitecore and less agile than Bynder, but Adobe products were already being used across the org and adding AEM allowed us to link it all together.
Each of the options had good points and bad points. Building a site with tight integration to HCL Commerce and SAP backend systems was just easier with HCL DX. Security is also a concern and HCL DX provided better fine-grained security across the board. HCL DX also allowed us …
IBM Web Content Manager comes with IBM WebSphere Portal. Both [have been] leaders in the portals and content management space for a long time with proven capabilities. Our clients also have other products from the IBM stack and they fit along nicely.
I used Liferay WCM; the open source system is too customizable such that what you get out of the box is not adequate. However, the portal pages in Liferay blend better with WCM than IBM: This is not always an advantage if you want to build a WCM site separated from portal …
I'll answer the second one because I mean, the first one I don't have an issue with. The second scenario is we oftentimes have the need to spin off very small campaign style sites or sites that generate leads but are unbranded and that sort of thing. So that's hard to do in AEM because you have to then create another organization within AEM to do that. And we're talking about sites that are maybe five to 10 pages in size. So we've been investigating Edge, but then that's a different workflow, so we'd have to train people on that. So it would be nice if there was something within the AEM structure that could allow you to do something very similar to Edge, where you make some small micro sites that are not necessarily branded, that you could still host within the platform and not have to retrain everybody on a completely different platform.
IBM Web Content Manager is well suited for intranet employee portals, websites which drive extensive marketing content, and e-commerce sites to provide product images and details. It cannot be used a document management system to store large volumes of data as it's purely a web content management system.
It allows us to scale so that we can make a change on a global footer. And it applies to all of the different property websites. It allows us to set up components and compartmentalize things in a way. The big thing is that it's scalable. And then it also ties into Adobe Analytics and other Adobe products. So we are a complete Adobe shop. Every Adobe product that we can use, we use. I don't think we do it for marketing so much, but for doing target testing and analytics, data scientists are using the same product and so it all speaks.
Well designed web content management system with clearly defined relationships between the various web content objects such as sites, site areas, authoring templates, presentation templates, library resources, components, web content objects, etc.
Can create robust content creation and publishing workflows with workflow stages and workflow actions
Web Content can be rendered on multiple devices and browsers in a responsive and adaptive manner.
easier way to make universal changes for multiple websites at a time (ie pushing out a new experience fragment to all as opposed to having to individually add to each site)
easier way to get site images to look and be sized exactly as I want directly from the site page editor
Search is not working well. We could not get it work even we worked it with IBM support.
Java Applet in Ephox editor is pain. You have to watch that you update your Java version correctly or You cannot edit anything. This might work somehow on enterprise environment with tight workstation configuration. I think that Java Applet editor is the worst part of IBM WCM
IBM WCM needs lot of capacity on database and appserver.
We had and still have a fantastic experience using Adobe CQ. Lots of flexibility, great integration with other Adobe products we already use and a powerful technology make it a great fit for our corporate environment. Also as the community grows, it makes it easier to network with other developers and users to get new ideas on how to continue to get the best out of the software.
IBM products always moves forward to adapt to new requirements and technologies. I have used versions 6, 6.1, 7 and 8 of IBM WCM, and I know IBM is ready to revamp the tool based on emerging needs, and still provide the capabilities to migrate your old system to the newer versions.
Sure there are a few quirks in the interface, but once you learn them, building and editing pages is fast and efficient. Once you have the content and the planned design decided (how the pages will look and which components you will use), page builds and publishing are quick. I was able to build a 10-page specialized site with cards built using the list component in an afternoon
Being part of Adobe Suite means you are already notified when the tool has any outages. However, I have never faced unplanned outages. Whenever you face any issue with the site, it is clearly stated if there were any planned outages and how quickly you will be back to normal. So, I will say that even the outages are planned and managed in a great way like their other services.
With respect to performance, Adobe experience manager is one of the best in the CMS space. We didn't observe frequent slowness on platform, however the systems which are accessing experience manager should be of good specifications without which slowness would be observed. Adobe experience manager works well in integration with other solutions, unless the destination application is designed to trigger frequent calls to AEM.
Adobe Experience Manager, in all its capacity, is a great alternative to any other CMS you are using. It helps in rapid development and makes life easier for maintaining the website for multi-language sites. Technical know-how is eliminated at content authoring. Better documentation in terms of live examples with videos would be appreciated.
Depending on your individual needs, It is really quite simple to create an authoring experience for a website that looks really good. I have been part of many implementations and many teams and have seen many projects that were super successful and others that were not implemented well. AEM has room for a lot of flexibility in the implementation process compared to other CMS like SharePoint
SSO is one fits all, so we don't have to have a separate SSO for each application of Adobe The integration with Analytics works perfectly and bring directly value really quickly Target remains more complicated to set up, but can also bring a lot of value once integrated with the rest of the Adobe platform The fact that the solution is Cloud services is also a big advantage for maintenance
Each of the options had good points and bad points. Building a site with tight integration to HCL Commerce and SAP backend systems was just easier with HCL DX. Security is also a concern and HCL DX provided better fine-grained security across the board. HCL DX also allowed us to use multiple technologies and maintain a cohesive feel across everything.
Unique, easy and user friendly solution that has increased business benefits such as a single repository for all company's products. It provides a better customer service.
A huge network of offices managed centrally increasing SEO, marketing, business and clients.
Employee efficiency reducing time through a single automated solution.
Internal communication within the company has been helped by Web Content Manager as a way of transparency, shared repository and networking with the goal of bringing teams and colleagues together.