Adobe Experience Manager (AEM) 6.0 is a major step forward in enabling marketing teams to create, manage, and optimise digital customer experiences across channels.
It offers new pluggable persistence managers for the storage of content & metadata, giving AEM architects and administrators more control over the user experience with the ability to optimize performance, scalability and availability of AEM.
As a supported persistence layer for AEM, MongoDB introduces several new capabilities which we will explore in this webinar, along with details on how to get started:
> The ability to scale beyond the limit of a single server for both author and publish instances
> The ability to cater to distributed marketing teams and authors
> More efficient ways to handle high amounts of user-generated content
> Minimised latency for geographically distributed audiences
> Automatic failover in the event of a server outage
2. Agenda
• Why MongoDB for Adobe Experience Manager?
• Adobe Experience Manager 6.1
• Storage Options. What to use when
– Tar MicroKernel
– MongoDB (Mongo MicroKernel)
• Case Studies
• Resources to Move Forward
3. How does MongoDB support AEM?
Global Scalability
Multi-Data Center
Recovery
User-Generated
Content
4. What are the Benefits of AEM + MongoDB?
Great Customer
Experience
Deeper Customer
Engagement
Fast Content
Authoring Workflow
5. What is Adobe Experience Manager?
Enterprise-grade
content management
system
Leader in Gartner
Web CMS MQ
Gartner Magic Quadrant for Web CMS 2014
6. ● Multi-Site & Channels
● Brand Consistency
● Cross Platform Experiences
● Managing renditions and layouts across devices
● Digital Asset Management
● Content Publishing Workflows
● Search
● Multi-Version Management
● Web Optimization
● Communities
● Social Driven Personalization
● Sentiment Analysis
● Moderation
● Video Playback
● Encoding
● Rendition Generation
7. New in Adobe Experience Manager 6.1
• Responsive layout authoring
– Better control of page elements for display on multiple devices
• Tighter Integration with
Adobe Marketing Cloud
– Target, Analytics &
Campaign services
• AEM Apps Command
Center
– Offerings to manage
lifecycle of Mobile
Applications
8. AEM 6.x: Jackrabbit Oak Repository
AEM6
JACKRABBIT OAK CONTENT REPOSITORY
Repository can be
configured to use
different persistence
mechanisms (storage
layers)
Storage Options:
- TAR
- MongoDB
9. AEM Storage Layer
• Store & manage content metadata & binary files
• Support AEM concurrency control
• Dictate how much data you can store
• Dictate how quickly AEM can read, write and
search content
• Dictate how AEM scales and secures content
MicroKernel (MK) = Storage Layer for AEM
11. Storage Layer Options: Tar MicroKernel
• Default AEM storage option
• File-based storage
• Co-located with each AEM instance, no shared-state.
• Redundancy via a cold standby
12. Scaling AEM with Tar MicroKernel
PUBLISH ENVIRONMENT
TarMK
TarMK FARM
AEM
AEM
AEM
AEM
AEM
TarMK
TarMK
TarMK
TarMK
2. SCALE ON READS
1. SAME
CONTENT
DEPLOYED TO
ALL SERVERS
13. TarMK: Advantages & Disadvantages
Advantages Disadvantages
Fast to get started No author scalability beyond a single
server
Co-located with AEM: low latency
reads
Manual failover + idle hardware
Co-located with AEM: managed with
AEM’s operational tools
17. MongoDB: Scalable Storage Layer
Distribute AEM storage layer across multiple servers
Increase or decrease capacity as you go
Automatic balancing
Automatic Sharding
18. AEM Sharded Cluster with MongoDB
AEM AEM AEM
DATA PARTITIONED ACROSS SERVERS FOR UNBOUNDED HORIZONTAL SCALABILITY
19. MongoDB: Self-Healing Storage Layer
Replica Set – 2 to 50 copies
Self-healing shard
Data Center Aware
Addresses availability considerations:
High Availability
Disaster Recovery
Maintenance
Workload Isolation: operational & analytics
Replica Sets
AEM
25. User Generated Content
PUBLISH ENVIRONMENT
TarMK
TarMK FARM
AEM
AEM
AEM
AEM
AEM
TarMK
TarMK
TarMK
TarMK
Community and Social Features
involves capturing “User
Generated Content” (UGC)
Synchronization challenge. TarMK Farm isn’t
an appropriate solution architecture.
26. Support for UGC with MongoDB
SCALES ON
READ AND
WRITES
SINGLE
STORAGE
LAYER,
REDUCING
REPLICATION
AEM Social Resource Provider uses MongoDB as the storage layer
27. MongoDB: Advantages & Disadvantages
Advantages Disadvantages
Scale beyond a single server Higher operational overhead:
separate layer from AEM (offset by
Ops Manager)
Support for globally distributed
author teams
Higher latency reads (offset by
scaling)
Self-healing, active/active clusters
Low overhead UGC
30. AEM is a Certified
MongoDB Enterprise Solution
Download MongoDB Enterprise Advanced
for evaluation
http://www.mongodb.com/lp/download/mongodb-enterprise
32. Operational Scale: MongoDB Ops Manager
How do I manage 10s to 1000s of nodes?
• Real-time monitoring
and visualization of
cluster health
• Alerting
• Automated cluster
provisioning
• Automation of daily
operational tasks, i.e.
zero-downtime upgrades
• Centralized configuration
management
• Automated PIT
snapshotting of clusters
• PIT Recovery
• Continuous backup
Automation Monitoring Backup
33. Getting Started
• Download and start MongoDB
• Follow the standard instructions to download and unpack
AEM.
• Create an AEM configuration file, specifying the
appropriate options to connect to MongoDB.
• Start the AEM jar to connect to the running MongoDB
instance.
• Instructions
– http://adobe.ly/1BjYbE2
34. Getting on the Right Path
• Consulting Package: MongoDB for AEM
– 3 day, on-site engagement
– Report detailing hardware requirements, HA,
scaling, security, operations, etc.
– Optional follow-on implementation service
Download the Datasheet
35. Getting Support
• Adobe & MongoDB have certified AEM for MongoDB
Enterprise Advanced
• If customer has a subscription to MongoDB Enterprise
Advanced, Adobe support team can raise tickets to
MongoDB
• Collaborative support team resolution
36. Problem Why MongoDB ResultsProblem Solution Results
Create brand
consistency: increase
NPS
Deepen customer
engagement: increase
conversions
Improve operational
efficiency: reduce costs
AEM 6.1 + MongoDB
Enterprise Advanced
1 template, many brands,
different styles, any
device
Shared features: find-a-
dealer, car configurator
Geo-Scale: support 200
web marketers across 9
locations
Fast TTM: delivered in 12
agile sprints
Op Efficiency: runs on
AWS with Cloudformation
templates
Case Study
Create a single best-in-class global digital platform for all
brands in the Renault-Nissan Alliance
37. Problem Why MongoDB ResultsProblem Solution Results
Deliver multi-channel
product catalog
Existing SQL-based
storage layer wasn’t
scaling
Operations team unable
to maintain QoS
AEM 6.1 + MongoDB
Enterprise Advanced
MongoDB Auto-Sharding
MongoDB Ops Manager
Multi-site AEM
deployment improving
customer experience
Fully supported, with
operational automation
Scale on-demand
Case Study
Multi-channel retailer improves customer experience while
enhancing operational efficiency
OnLine & TV Retail
Shopping Channel
39. MONGODB: THE LARGEST ECOSYSTEM
10,000,000+
MongoDB Downloads
300,000+
Online Education Registrants
35,000+
MongoDB User Group Members
35,000+
MongoDB Cloud ManagerUsers
1k+
Technology and Services Partners
2,000+
Customers Across All Industries
40. MongoDB Use Cases
Single View Internet of Things Mobile Real-Time Analytics
Catalog Customer Data Management Content Management
41. RESOURCES
• If you want advise or feedback on a project
– https://www.mongodb.com/lp/contact/mongodb-adobe-experience-manager
• Adobe Enterprise Manager Recommended Deployments
– http://docs.adobe.com/docs/en/aem/6-0/deploy/recommended-deploys.html
• MongoDB On Demand Webinar: Clustering Made Easy
– http://www.mongodb.com/presentations/webinar-adobe-experience-manager-
clustering-made-easy-mongodb
• Don’t forget consulting!
44. New in Adobe Experience Manager 6.0
• “Sightly” server-side template development language
– Accessible to HTML developers
– Eliminates XSS vulnerabilities
– Plug-ins for common IDEs and code editors
• Projects & Workflows
– Single location for a
projects assets, content,
sites and apps for easy
collaboration
• Operations Dashboard
– Cross cluster view of
system health
Editor's Notes
While it is possible to store binaries in MongoDB, Adobe generally recommends storing them separately for better performance. This could be in a separate shared file server or on Amazon S3.
In order to predict whether or not you’ll need more than one instance, you can look at these metrics:
Number of named users connected in a day: in the thousands or more.
Number of concurrent users: in the hundreds or more.
Volume of asset ingestions per day: in hundreds of thousands or more.
Volume of page edits per day: in hundreds of thousands or more (including automated updates).
Volume of searches per day: in tens of thousands or more.
Released in 2014 – valuable upgrade
XSS = cross site scripting