
Within this framework itself, all the requests for generating or publishing content will be managed including approvals and signoffs.ĬQ Components which are actually a set of widgets, supports the required logic in defining the actual content. There is a provision for a Java API and RESTful HTTP interface for the required access by applications outside of the platform. CQ WCM (Web Content Management) is a tool responsible for generating and publishing pages to the website at real-time.ĬQ Workflow Engine is an easy to use and powerful process engine running on a CQ5 platform. It can be used with scripting languages like JSP (Java Script Pages) and Ruby and many more.ĪEM Adobe Experience Manager is built on OSGi technology which is a dynamic module system for Java.
#Workspace manager aem software#
#Workspace manager aem plus#
JCR is a combination of a web application (which follows JSR-170 compliant API plus temporary data storage in the form of a session) and a Persistence Manager (includes persistent data storage like a database or file system). JCR, Java Content Repository is a storehouse of content which is not dependent on the actual implementation.

To cater to this requirement, CQ WCM is equipped with CQSE (CQ Servlet Engine). CQ WCM (Web Content Management) might not need any additional application server but it surely needs a Servlet engine. It can be any Servlet engine that supports Servlet API 2.4 or higher versions. Servlet engine is a server which has each of the AEM instances running as a web application. It can be from its own internal management or a third-party counterpart. The diagram above shows the basic architecture of Adobe Experience Manager with its interdependencies. For developers, it grants the power to create, access, and reuse content elements for seamless customer interfaces across projects. For marketers, it provides management and optimization of content for their core channels without external dependencies. There is something for everyone.įor designers, it gives strong and user-friendly options to build front-end applications. Ever since CQ is upgraded to AEM, there is no looking back.ĪEM (Adobe Experience Manager) serves as a hybrid CMS. The adobe digital asset management and adobe content management features were provided using WCM (production ready core components) / CQ (older version of AEM) on top of Granite / CRX core.

CRX or Granite managed most of the low-level functionalities like data persistence, event management and user management. Now that Apache Sling is a passé, Adobe expanded the features of Sling to produce their own enhanced version of Apache Sling called the Adobe CRX (Content Repository eXtreme).Īt the time of conception, CQ 5 (older version of AEM) functionality was transferred to Granite (UI framework). Apache Sling uses JCR (Java Content Repository, built with Apache jackrabbit) object database to store required information.Īpache Sling comes with its own HTTP server that can be used as a Web Application with an application server called Jetty web server (basic server functionality with a servlet framework). This makes the Adobe AEM CMS one the most powerful component of the Adobe Marketing Cloud. It is a java application built on OSGi (Open Services Gateway Initiative) framework using Apache Felix engine (a community effort to implement OSGi framework under Apache license). e-Commerce Business Analytics and IntelligenceĪEM is based on Apache Sling framework concepts.Artificial Intelligence/Machine Learning.
