Adobe AEM CQ5 - Developer Introduction
•
11 likes•12,259 views
This document provides an introduction to Adobe Experience Manager (AEM), formerly known as CQ5. It discusses key aspects such as installation, prerequisites, content authoring, templates, components, workflows and more. The technical underpinnings including OSGi, JCR, Apache Sling, and ExtJS frameworks are also overviewed. Common terms are defined and the overall architecture and technology stack are depicted in detail.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Adobe AEM CQ5 - Developer Introduction
Similar to Adobe AEM CQ5 - Developer Introduction (20)
More from Yash Mody
More from Yash Mody (11)
Recently uploaded
Recently uploaded (20)
Adobe AEM CQ5 - Developer Introduction
- 1. Adobe AEM aka CQ5 Ge/ng Started and More Dr. Yash Mody, PhD Tekno Point ConsulAng www.teknopoint.us | www.teknopoint.in
- 2. IntroducAon to CQ5 The way developers like it • Web Content Management That’s where we create websites and its content • Digital Asset Management All the digital media goes here like images, documents, movies et. Al. • Campaign Management CreaAng campaigns, mailers and teasers using the same content. • Workflow Automate the processes. Add users, scripts and other processes. Yes can be triggered • Social CollaboraAon Calendar, Customer raAngs, Forum, Comments and the other usual stuff (FB, TwiPer) Dr. Yash Mody | Tekno Point 2
- 3. Ge/ng Started • Current Version – 5.6 Now called as the Adobe Experience Manager • Prereqs – Java v1.7, 4 GB RAM(min), CRXDE And that’s apart from a valid jar and license. • InstallaAon is double clicking a JAR No I am not kidding • Set up as Author That’s where all the content is generated. Called the run-‐mode Dr. Yash Mody | Tekno Point 3
- 4. Key Technologies • OSGi The Universal Middleware. Container for Bundles. Uses Apache Felix • JCR Java content Repository. Everything is content. ImplementaAon used -‐ CRX • Apache Sling The REST framework responsible for delivering content form JCR • CQ WCM API Pages, Templates, Components, Workflows and everything else CQ is made up of • EXTJs • Sencha JavaScript framework. Used for UI Dr. Yash Mody | Tekno Point 4
- 5. Key Terms • Template The Blue print to make a page • Pages This is what the Author creates • Components Part of templates and this is where you will spend a lot of your Ame. JSP, JS, CSS, i18n, ExtJs • Dialog User Interface to collect informaAon from an Author. Custom created. ExtJs • Widgets Each line item in a dialog. Sits inside a widgetcollecAon. ExtJs • Workflow The more I tell you the more I scare you. Model a workflow, Run it, See the inbox, Step ahead.. Phew Dr. Yash Mody | Tekno Point 5
- 6. OSGi • Bundles Your Java Code. Basically a Jar with some meta informaAon • Services This is what you will use and write for other bundles • Blah Blah Modules, RunAme and Security. Class Loader example Dr. Yash Mody | Tekno Point 6
- 7. JCR Terms • Node • It’s the structure • ProperAes • And the content. Key/Value(s) format • API Dr. Yash Mody | Tekno Point 7
- 8. JCR Structure ID FN LN 1 A A 2 B b Employee A FN:A LN:B B FN:A LN:B Repository Model with mulAple workspaces Structured Data Node Data Dr. Yash Mody | Tekno Point 8
- 9. Apache Sling • REST • URL – From JCR • Protocol – HTTP • SlingHTTPRequest/Response • POST handler Dr. Yash Mody | Tekno Point 9
- 10. Too many API’s adaptTo() • Apache Sling • JCR • OSGi • WCM • Workflows • CQ WCM • adaptTo() Dr. Yash Mody | Tekno Point 10
- 11. CQ5 Architecture – Technology Stack Dr. Yash Mody | Tekno Point 11
- 12. Other EssenAals • Publish and Author instances • The 4502 secret Default port • Sidekick & Content Finder On the Authoring Page. CF is used to add content (from DAM) and Sidekick to add components and more • The PARAGRAPH SYSTEM The reason CQ is selling :P Provides ability to drag and drop components. Making it easy to customize templates Dr. Yash Mody | Tekno Point 12
- 13. Deployment • Dispatcher CQ is a powerful rendering engine built on powerful standards. CQ runs with a webserver for content delivery. Makes Sense as well • Publish – Author relaAonship ReplicaAon Agent. Reverse ReplicaAon Agent • Load Balancing and Clustering Lives in clusters. Single instance is a cluster of 1 Dr. Yash Mody | Tekno Point 13
- 14. Environments • CQ Sites– hPp://localhost:4502/siteadmin • CRX – hPp://localhost:4502/crx/explorer • Felix – hPp://localhost:4502/system/console • CRXDE – hPp://localhost:4502/crxde Dr. Yash Mody | Tekno Point 14