In AEM terminology an “instance” is a copy of AEM running on a server. All client interaction with AEM is done through a web browser. The AEM server is Java-based and runs on most operating systems that support that platform. The repository stores not only the user-facing content but also all code, templates and internal data used by the application.īuilding on this base, AEM also offers a number of application-level features for the management of:įinally, customers can use these infrastructrue and application-level building blocks to create customized solutions by building applications of their own. Content Repository: AEM includes a Java Content Repository (JCR), a type of hierarchical database designed specifically for unstructured and semi-structured data.Web Application Framework: AEM incorporates the Sling Web Application Framework that simplifies the writing of RESTful, content-oriented web applications.Web Application Server: AEM can be deployed in standalone mode (it includes an integrated Jetty web server) or as a web application within a third-party application server (WebLogic, WebSphere, etc).It combines a number of infrastructure-level and application-level functions into a single integrated package.Īt the infrastructure level AEM provides the following: Once you have familiarized yourself with these basics, you will find in more advanced and detailed information in the following subpages:Īdobe Experience Manager is a web-based client-server system for building, managing and deploying commercial websites and related services. For further details, see our technical support periods. AEM 6.4 has reached the end of extended support and this documentation is no longer updated.
0 kommentar(er)
