Architecutre of Adobe CQ5 by Nouman Naveed

2,900 views

Published on

Architecture of Adobe CQ5 by Mohammed Nouman Naveed
Adobe Certified Expert, Adobe Certified Instructor, Adobe Certified Professional & Adobe User Group Manager

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,900
On SlideShare
0
From Embeds
0
Number of Embeds
26
Actions
Shares
0
Downloads
224
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Architecutre of Adobe CQ5 by Nouman Naveed

  1. 1. © 2014 Adobe Systems Incorporated. All Rights Reserved. Nouman Naveed – Adobe Certified Instructor & Adobe Certified Professional Adobe CQ5 - Product and Platform Architecture http://in.linkedin.com/in/noumannaveed/ http://www.flexatom.com http://hyderabad.groups.adobe.com +91 9160600073
  2. 2. © 2014 Adobe Systems Incorporated. All Rights Reserved. 2 We are going to learn following:  History of CQ5  What is CQ5?  The technology  Adobe Marketing Cloud – CQ5  CQ5 Main Components  Architecture – CQ (AEM)
  3. 3. © 2014 Adobe Systems Incorporated. All Rights Reserved. History of CQ5  David Nuescheler, one of the founders of Day Software of Basel, Switzerland (currently a Vice President at Adobe)  Day Software Founded in 1993.  Day Software was an enterprise content management software company headquartered in Basel, Switzerland and Boston, Massachusetts. 3
  4. 4. © 2014 Adobe Systems Incorporated. All Rights Reserved. History of CQ5 (continued…)  2002 Day CQ 3.5  2005 Day CQ 4.0  2006 Day CQ 4.1  2008 Day CQ 4.2  2008 Day CQ 5.0  2009 Day CQ 5.2  2010 Day CQ 5.3  2011 Adobe CQ 5.4  2012 Adobe CQ 5.5  2013 Adobe Experience Manager (AEM) 5.6 4
  5. 5. © 2014 Adobe Systems Incorporated. All Rights Reserved. What is CQ5?  CQ5 is Adobe’s flagship Content Management System and the leading CMS in the market. Like any CMS you can use it to build and maintain your web presence, but more importantly you can use it to capture your online visitor behaviour and convert customer interest into sales.  It works on multiple platforms (so its totally compatible with browsers, ipads, smart phones etc) and it uses the latest HTML5 technology, so it looks great.  It seems that Day Software, from whom Adobe bought the platform, just got it right.  Developers report that its easy to use, it’s powerful, it’s scalable, it integrates with 3rd party systems well, it deploys nicely, the list seems to go on and on. 5
  6. 6. © 2014 Adobe Systems Incorporated. All Rights Reserved. The technology  CQ5 is a Java-based CMS, and by making it multi-platform it’s taken Java’s “Write Once Run Anywhere” philosophy and applied it in a modern setting. 6
  7. 7. © 2014 Adobe Systems Incorporated. All Rights Reserved. The Many Names of CQ (in chronological order):  Day Communiqué WCM  Communiqué  Day Software’s CQ  Adobe CQ  Adobe WEM  Adobe WCM  Adobe Experience Manager or AEM (now its current manifestation) 7
  8. 8. © 2014 Adobe Systems Incorporated. All Rights Reserved. The Future of CQ5  Adobe is busy adding new functionality to their “AEM” – by integrating it with their already extensive software suite – in an attempt to maximize the commercial return on its current popularity. 8
  9. 9. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Marketing Cloud – CQ5  CQ5 (Adobe Experience Manager) is part of Adobe Marketing Cloud Suite  Adobe Marketing Cloud product line includes following products: 9
  10. 10. © 2014 Adobe Systems Incorporated. All Rights Reserved. CQ5 Main Components  Adobe Web Content Management  Adobe Content Repository Extreme (CRX)  Adobe JCR Connectors  Adobe Digital Asset Management – DAM  Adobe Advanced Collaboration  Integration with commerce system like ATG 10
  11. 11. © 2014 Adobe Systems Incorporated. All Rights Reserved. Architecture – CQ (AEM)  This section details the technology stack on which AEM is built. The stack can be divided as follows, from lowest to highest level:  Java Platform  Java Runtime Environment (JRE 1.6 minimum. JRE 1.7 recommended)  Granite Platform (runs on JRE)  OSGi Framework (encapsulates all subsequent elements)  CQSE Servlet Engine (optional external application server)  CRX Content Repository  Sling Content Delivery  Granite UI  Abobe Experience Manager (runs on Granite platform, within OSGi framework)  Individual AEM modules (WCM, DAM, Workflow, etc.)  Customer Applications (run on AEM)  Customer specific applications (websites, etc. also run within OSGi framework) 11
  12. 12. © 2014 Adobe Systems Incorporated. All Rights Reserved.  Java Platform - Adobe Experience Manager (AEM) is a Java web application and therefore requires a server-side Java Runtime Environment (JRE). At least JRE 1.6 is required, though JRE 1.7 is recommended. AEM will run on any OS for which the required JRE is available, this includes Windows, Mac OS X and a variety of Unix systems. 12
  13. 13. © 2014 Adobe Systems Incorporated. All Rights Reserved. Granite Platform  Granite is Adobe's open web stack. It forms the technical foundation on which AEM is built. The following sections discuss each element in more detail.  OSGi Framework - AEM includes an OSGi component framework based on Apache Felix, which implements OSGi Service Platform Release 4.  OSGi is a dynamic software component system for Java. In an OSGi- based system, an application is composed of an assemblage of components, called bundles in OSGi terminology, which can be dynamically installed, started, stopped and uninstalled at runtime, without shutting down and restarting the entire application.  A bundle is a jar file holding Java classes that adhere to the OSGi specification.  Servlet Engine - In a quickstart installation, the built-in CQSE servlet engine runs as a bundle within the OSGi framework. AEM includes a built-in servlet engine (CQSE) which runs as a bundle within the OSGi framework when AEM is deployed via the standalone quickstart jar file. 13
  14. 14. © 2014 Adobe Systems Incorporated. All Rights Reserved. Digital Asset Management - DAM  CQ DAM (Communiqué Digital Asset Management) is used to centrally manage all digital media files and essential metadata information 14
  15. 15. © 2014 Adobe Systems Incorporated. All Rights Reserved. Widgets  CQ WCM has been developed using the ExtJS library of widgets.  ExtJS is from http://www.sencha.com  Learn ExtJS library to build complex components. 15
  16. 16. © 2014 Adobe Systems Incorporated. All Rights Reserved. Workflow Engine  Your content is often subject to organizational processes, including steps such as approval and sign-off by various participants. These processes can be represented as workflows, defined within CQ, then applied to the appropriate content pages or digital assets as required.  The Workflow Engine is used to manage the implementation of your workflows, and their subsequent application to your content. 16
  17. 17. © 2014 Adobe Systems Incorporated. All Rights Reserved. Localization  Localization is at the core of CQ5. It provides support for adapting applications, created using the CQ5 platform, into different languages and regional configurations .  While processing the request, the Locale is extracted. 17
  18. 18. © 2014 Adobe Systems Incorporated. All Rights Reserved. Summary  CQ5 is web content management software  Apache Sling is a methodology to access content from CRX – Java Content Repository  CQ5 can be installed on Windows, Mac & Linux  CRX is Day's proprietary implementation of the JCR.  In CQ everything is content  Content is accessed using Sling URLs and content is mapped to pages  All custom applications are built inside apps/ directory in CRX  Widgets and Dialogs are built using ExtJS library 18
  19. 19. © 2014 Adobe Systems Incorporated. All Rights Reserved. Contact Me 19 http://in.linkedin.com/in/noumannaveed/ http://www.flexatom.com http://hyderabad.groups.adobe.com +919160600073

×