Elastic Path Commerce for AWS Setup
Core Commerce Architecture
Cortex API Architecture
Tutorials & Code Examples
Elastic Path Production Tools
Core Commerce Release Notes
Cortex API Front-End Documentation
EP for Adobe Marketing Cloud Architecture
EP for AMC Developer Documentation
EP for AMC Release Notes
Cortex Studio
Configuring Environment Specific Settings
Configuring Environment Specific Settings
Elastic Path provides two files to configure your web application settings in your deployed .WAR files:
- ep.properties -> Overwrites the web application settings defined in the Web App's module.properties file.
- ep.override.properties ->Overwrites the values of any bean running in your Web App.
ep.properties
Using the ep.properties file provides a convenient way to customize your deployed web applications. This section describes how to create the ep.properties file and lists the web application settings this file can override.
To create an ep.properties file:
- Create a directory named ep in one of the following location:
- for Windows: C:\Users\<username>\ep\conf or C:\etc\ep
- for Linux: ~/ep/conf or /etc/ep
- In ep, create a file named ep.properties.
- In ep.properties, define the property values you want to set and save your changes.
- Restart your server for the changes to take effect.
Configurable ep.properties
Commerce Manager Server
| Property | Description | Developer default |
|---|---|---|
| ep.cm.port.http | The Commerce Manager HTTP port | 8080 |
| ep.cm.port.https | The Commerce Manager HTTPS port | 8443 |
| ep.cm.secure.channel | Sets the Commerce Manager server to use http or https | http |
| ep.cm.topseller.delay | Specifies the initial delay (in milliseconds) before the server will start to calculate the top sellers | 30000 |
| ep.cm.topseller.interval | Specifies the delay (in milliseconds) between recalculations of the top sellers | 30000 |
| ep.cm.productrecommendation.delay | Specifies the initial delay (in milliseconds) before the server will start to calculate product recommendations | 30000 |
| ep.cm.productrecommendation.interval | Specifies the delay (in milliseconds) between recalculations of product recommendations | 30000 |
| ep.cm.searchterms.aggregator.delay | Specifies the delay (in milliseconds) before the server will start tracking search term activity. | 30000 |
| ep.cm.searchterms.aggregator.interval | Specifies the delay (in milliseconds) between updates of search term activity tracking. | 30000 |
Search
| Property | Description | Developer default |
|---|---|---|
| ep.search.contextURL | The search server web application context | /searchserver |
| ep.search.port.http | The search server HTTP port | 8080 |
| ep.index.build.delay | Specifies the initial delay (in milliseconds) before the server will start to update the customer search index. | 10000 |
| ep.index.build.interval | Specifies the delay (in milliseconds) between updates of the customer search index. | 5000 |
| ep.search.requires.master | When set to true, the Search Server, for which the value is set, becomes the master Search Server. For more information, see Search Server Clustering. | false |
| ep.search.triggers | Disables Search Server indexing when set to disabled. This is setting is used to disable the Search slave's indexing. For more information, see Search Server Clustering. | - |
JMS Messaging
| Property | Description | Developer default |
|---|---|---|
| ep.jms.type | The Java Class type of the JMS Broker Connection Factory. | org.apache.activemq.pool.PooledConnectionFactory |
| ep.jms.factory | The JNDI resource factory used by the applicatoin. | org.apache.activemq.jndi.JNDIReferenceFactory |
| ep.jms.url | The URL of the JMS broker. | tcp://localhost:61616 |
Global Settings
| Property | Description | Developer default |
|---|---|---|
| ep.external.ehcache.xml.path | Specifies the path to the external Ehcache configuration file. This property affects all web applications (Cortex, CM Server, Search Server and Integration Server). See by Configuring Ehcache for more information. The file path in ep.external.ehcache.xml.path must be absolute. For example:
Note: Additional Slash (/) The additional slash in file:/// is necessary for Spring. | - |
ep.override.properties
The ep.override.properties file provides a convenient way to override the values of any bean running in your Web App. This section describes how to create the ep.override.properties file and provides some example of beans you can override.
Only knowledgeable developers should override bean values.
To create an ep.override.properties file:
- Create a directory named ep in the following location:
- for Windows: C:\Users\<username>\ep\conf or C:\etc\ep
- for Linux: ~/ep/conf or /etc/ep
- In ep, create a file named ep.override.properties.
- In ep.override.properties, define the property values you want to set and save your changes.
- Restart your server for the changes to take effect.
ep.override.properties Syntax
ep.override.properties uses the following syntax: beanName.propertyName=value
entityManagerFactory.jpaPropertyMap[openjpa.DataCache]=true entityManagerFactory.jpaPropertyMap[openjpa.RemoteCommitProvider]=sjvm