A separate system (known as the trusted authenticator) performs the authentication and provides Experience Manager with the user credentials. Single Sign On (SSO) allows a user to access multiple systems after providing authentication credentials (such as a user name and password) once. These are then applied as required.Īll configuration settings are stored in the one repository and activated by setting the Run Mode. A basic set of configuration parameters is applied for all run modes, you can then tune additional sets to the purpose of your specific environment. This is done by defining collections of configuration parameters for each run mode. Run modes allow you to tune your AEM instance for a specific purpose for example author or publish, test, development or intranet, etc.
#Store manager for magento too many connections from this ip how to
See Version Purging for full details, in particular Version Manager for details of how to configure AEM to purge older versions when a new version is created. These versions are never purged, so the repository size will grow over time and therefore need to be managed. All these versions are stored in the repository and can be restored if required. In a standard installation AEM creates a new version of a page or node whenever you activate a page (after updating the content).You can also create additional versions on request using the Versioning tab of the sidekick. The default case of localhost will be interpreted for both IPv4 and IPv6 network installations This means that when an IP address needs to be specified you can select (as required) from: Operation is seamless as no special configuration is required, when needed you can simply specify an IP address using the format that is appropriate to your network type. the repository, the Dispatcher, etc) can be installed in both IPv4 and IPv6 networks. You can configure the UI you require using Root Mapping.įurther information about selecting the UI is available under Selecting your UI. There are two UIs available for use in AEM: Configuring the Default UI - Touch-Optimized or Classic Please ensure that you read this and take any action necessary for your installation. Several key configuration issues are listed in the Security Checklist. The list gives a short overview of each configuration aspect, together with links to the pages that provide full details. Not all are needed, but the list must be read and reviewed to see what is applicable to your project. This list details the primary areas that are commonly configured for every new project. Any changes made via the OSGi console are immediately applied to the running system (no restart is required). For this reason, ensure you have the necessary experience and knowledge before you start to configure AEM, and make only the changes which you know are required. Various aspects can be configured within AEM WCM itself, many using the Tools console for example, replication agents.Ĭonfiguring AEM is straightforward, but you must be aware that:Ĭertain changes can have a major impact on the application(s). See OSGi Configuration in the Repository and in particular Adding a New Configuration to the Repository for further details.Ī few configuration files reside within the file system. You can also add your own configurations, dependent on run-mode, to the repository. This ensures that copying, or replicating, repository contents recreates identical configurations. See Configuring OSGi for further details and recommended practices.Ī sub-set of OSGi configurations are available in the repository. This is a standard location for configuring OSGi bundles and services.