EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment
Download as PPTX, PDF0 likes506 views
The document discusses various architectures and deployment strategies for Adobe Experience Manager (AEM), including single tarmk instances, cold standby, and tarmk farms, each with their advantages and disadvantages. It also outlines the typical AEM environment involving the dispatcher module and presents different implementations of the social resource provider for user-generated content (UGC) using MongoDB and Adobe social resources. Overall, it emphasizes configurations for performance, scalability, and failover capabilities.
EVOLVE'16 | Deploy | Abhishek Dwevedi | Understanding a Typical AEM Deployment
- 1. #evolverocks Understanding a typical AEM deployment ABHISHEK DWEVEDI August 31st, 2016
- 2. #evolverocks 2 Understanding a typical AEM deployment 1. OakArchitectures 2. Typical AEM Environment 3. Dispatcher Module Deployment 4. AEM Communities
- 3. #evolverocks 3 Oak Architectures: Single TarMK instance A single TarMK instance runs on a single server. Default setup for Author instances Advantages: Simplicity Easy maintenance Good performance Disadvantages: Not scalable beyond the limits of the server capacity No failover capacity
- 4. #evolverocks 4 Oak Architectures: TarMK Cold Standby One TarMK instance acts as the primary instance. The repository from the primary is replicated to a standby failover system. The failover server is running in cold-standby mode, which means that the HttpReceiver of the instance is running. Advantages: Simplicity Easy maintenance Good performance Failover is provided Disadvantages: Not scalable beyond limits of the server capacity One server is idle
- 5. #evolverocks 5 Oak Architectures: TarMK Farm Multiple Oak instances run with one TarMK instance each. The TarMK repositories are independent and need to be kept in sync. This is the default deployment for AEM Publish instances. Advantages: Good performance Scalability for read access is provided Failover is provided Disadvantages: Write access kept in sync between instances
- 7. #evolverocks DISPATCHER MODULE DEPLOYMENT web server Dispatcher docroot web server Dispatcher docroot web server Dispatcher docroot web server Dispatcher docroot AEM Publish AEM AEM render the page write it into the docroot home.html
- 8. #evolverocks 8 AEM COMMUNITIES: IMPLEMENTING THE COMMON STORE • Social Resource Provider (SRP) • An API that abstracts the storage • Implemented three different ways • MongoMK JCR SRP (JSRP) • Adobe SRP (ASRP) • Mongo SRP (MSRP)
- 9. #evolverocks 9 J S R P : J C R S O C I A L R E S O U R C E P R O V I D E R 9 9 AEM Author • Publish instances are clustered with MongoMK • Default storage mechanism • Easy to setup UGC • UGC is only available on publish instances • Publish Farm is not utilized MongoMK AEM Publish 3 AEM Publish 2 AEM Publish 1
- 10. #evolverocks ASRP: Adobe Social Resource Provider AEM Publish Farm Adobe Social Cloud AEM Author • Recommended for managed UGC • No setup needed • Integrates with Adobe Social Analytics Pipeline and Moderation • Fast
- 11. #evolverocks M S R P : M O N G O S O C I A L R E S O U R C E P R O V I D E R AEM Author AEM Publish Farm • Recommended for on premise UGC • Required to setup a mongo replica set and solr cloud • Fast and scaleable