Web Application Server: AEM can be deployed in standalone mode (it includes an intergated Jetty web server) or as a web application within a third-party application server (WebLogic, WebSphere, etc).
Web Application Framework: AEM incorporates the Sling Web Application Framework that simplifies the writing of RESTful, content-oriented web applications.
Content Repository: AEM includes a Java Content Repository (JCR), a type of hierarchical database designed specifically for unstructured and semi-structured data. The repository stores not only the user-facing content but also all code, templates and internal data used by the application.
The AEM server is Java-based and runs on most operating systems that support that platform. All client interaction with AEM is done through a web browser.
Typical Deployment Scenarios
In AEM terminology an “instance” is a copy of AEM running on a server. AEM installations usually involve at least two instances, typically running on separate machines:
Author: An AEM instance used to create, upload and edit content and to administer the website. Once content is ready to go live, it is replicated to the publish instance.
Publish: An AEM instance that serves the published content to the public.
These instances are identical in terms of installed software. They are differentiated by configuration only. In addition, most installations use a dispatcher:
Dispatcher: A static web server (Apache httpd, Microsoft IIS, etc.) augmented with the AEM dispatcher module. It caches web pages produced by the publish instance to improve performance.
Typical Deployment Scenarios
In AEM terminology an “instance” is a copy of AEM running on a server. AEM installations usually involve at least two instances, typically running on separate machines:
Author: An AEM instance used to create, upload and edit content and to administer the website. Once content is ready to go live, it is replicated to the publish instance.
Publish: An AEM instance that serves the published content to the public.
These instances are identical in terms of installed software. They are differentiated by configuration only. In addition, most installations use a dispatcher:
Dispatcher: A static web server (Apache httpd, Microsoft IIS, etc.) augmented with the AEM dispatcher module. It caches web pages produced by the publish instance to improve performance.
No comments:
Post a Comment
If you have any doubts or questions, please let us know.