Announcement: You can find the guides for Commerce 7.5 and later on the new Elastic Path Documentation site. This Developer Center contains the guides for Commerce 6.13.0 through 7.4.1.Visit new site

This version of Elastic Path Commerce is no longer supported or maintained. To upgrade to the latest version, contact your Elastic Path representative.

Runtime Configurations

Runtime Configurations

Using AEM Web Console, you can configure your OSGi bundles. For information on using AEM Web Console, see AEM's online help: http://docs.adobe.com/docs/en/aem/6-0/deploy/configuring/web-console.html

OSGi Bundle Configurations

Below is a list of the available bundle configurations for EP Commerce for Adobe Marketing Cloud:
Important: Restart Required Configuration changes to the EP Product Importer bundle requires you to restart the bundle for the changes to take affect.
Configuration Description
Elastic Path ActiveMQ Connection Configuration JMS Broker URL Sets the JMS Broker's URL, following this format: {transport}://{host}:{port}
Elastic Path Cortex Client Factory Cortex URL Sets the URL to Cortex.
Elastic Path Cortex Context Manager Cookie Name The authentication cookie's name.
Cookie Domain The cookie's domain attribute.
Cookie Path The cookie's path attribute.
Secure Cookie Enables the cookie's secure flag. If this flag is set to true, all pages/urls that require Cortex data need to be secure (HTTPS).
Http Only Cookie Enables the cookie's HTTP only flag.
Elastic Path Demo Password Configuration Enable Demo Password Allows you to use Cortex Studio to view a shopper's data directly with the Cortex. If this flag is set to true, AEM will create shopper accounts in Cortex with the specified username and a password set to "password". If this flag is set to false, AEM will create shopper accounts in Cortex with the specified username and a randomly generated password. The password entered in AEM when the account was created should still be used when authenticating in AEM.
Elastic Path JAX-RS Client Logging Configurator Jersey Client Logging Activate traffic logging to debug JAX-RS HTTP requests and responses. The log file is available here: crx-quickstart/logs/error.log.
Jersey Entity Logging Activate entity logging to debug JAX-RS HTTP requests and responses. The log file is available here: crx-quickstart/logs/error.log.
Elastic Path JAX-RS Client Apache Connector Max Connections Maximum number of connections allowed for Apache HttpClient. This number should match the number of concurrent connections allowed in Cortex.
Max Routes per Host Maximum number of routes per host allowed for Apache HttpClient. Since JAX-RS Client only talks to Cortex, this value should match the Max Connections count.
Elastic Path JAX-RS Configured Client Provider Client Configurators list The list of named JAX-RS Client Configurators to use to configure a new JAX-RS Client service.
Client Connect Timeout Connect timeout value in milliseconds. How long to wait for the server to accept an http connection.
Client Read Timeout Read timeout value in milliseconds. How long to wait for the server to return a response.
Elastic Path Importer Configuration Save batch size Sets the number of operations to perform before a batch commits to the JCR.
Throttle batch size Sets the number of operations to perform before a throttle is applied. This helps maintain responsiveness for authors working on a system that the import runs against.
Message Cap

Sets the cap size for log messages. This is useful when logging volume can affect performance and become overwhelming.

Bucket Size

Sets the bucket size, which optimizes the performance of the catalog in production. The JCR has better depth vs breadth performance, where your catalog structure or categories within your catalog are large this setting helps ensure the JCR responds well with this data.

Importer initial timeout Sets the initial timeout in milliseconds for the import listeners. This is the length of time the importer waits for the first import message to arrive on the inbound queues (categories and products).
Importer polling timeout Sets the polling timeout in milliseconds for the import listeners. This is the length of time the importer waits for subsequent messages to arrive on the inbound queues (categories and products).
Cortex Proxy Servlet configuration Enabled Enables the Cortex proxy servlet. By default, its disabled. When disabled, requests to the proxy return a 404 Not Found.