e
Key Components
| Component Front-End to Back | Purpose | Summary | Notes | Key Reading Matrial |
|---|---|---|---|---|
| Akamai | CDN (Content Distribution Network) | |||
| Apache with Adobe Dispatcher Module | Web Server, Caching and Load Balancing | Caches into static content pages generated by CMS to improve performance. | ||
| AEM Instance for Publisher | CMS Publisher | Serves the published content to the public. Appears to be using Apache Sling for Web framework to expose the repository. Bundles CRXDE Lite web interface to manage the repository at http://<host>:<port>/crx/de/index.jsp | ||
| CRX Content Repository | CMS Publisher Database Cache | Data storage for content-centric applications, implementing Content Repository API for Java Technology (JCR 2.0). Appears to use Apache Jackrabbit as manager (searching, versioning, transactions, etc.) of repository. | ||
| AEM Instance for Author | CMS Author | Create, upload and edit content and to administer the website. | ||
| CMS Author Database | ||||
| Microsoft AD | Centralized Authentication Directory | Optional and should failback to local authentication repository if AD fails. |
Adobe Experience Manager Shortlist of Project Documentation
AEM 6.x with Apache Sling uses TarMK with Apache Jackrabbit Oak. Key aspect of speed is the combination deserializes the repository memory. It is not caching the repository in memory. The repository exists in memory and uses the tar files to serialize adn persist the data. It will deserialize the entire repository into memory if enough memory available. So give AEM lots of memory.
Though AEM and Apache Sling runs in a JVM, the memory they use for repository is not the JVM heap, but the "off-heap" memory. You may limit it via Java parameter -XX:MaxDirectMemorySize. One consideration to gain memory is to set the Pool Size parameter of Apache Sling Job Thread Pool to 1. This iwll limit the memory used by jobs at the cost of speed of job completion when jobs are queued.
Setup of Web Server Dispatcher
...
Setup of AEM Application Server
AEM package comes in two flavours,
- cq-quickstart-6.2.0.jar - executable to run as a Java process.
- cq-quickstart-6.2.0.war - install in a container like Tomcat
Enable license by entering at startup or in license.properties file (preferred to automoation).
By default the package starts up running both the author and publish components as one service. Enterprise configurations will want to segregate and this occurs with a file rename,
cq-<instance-type>-p<port-number>.jar
Modify temporary directory,
CQ_JVM_OPTS # may modify in serverctl or start script
Author Server
Rename file,
mv cq-quickstart-6.2.0.jar cq-author-p4502.jar
This will result in an author instance running on port 4502.
Publish Server
Rename file,
mv cq-quickstart-6.2.0.jar cq-publish-p4502.jar
This will result in an publish instance running on port 4502.