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.

Configuring Environment Specific Settings

Configuring Environment Specific Settings

Elastic Path provides two files to configure your deployed Elastic Path applications:

  • ep.properties -> Overwrites property placeholders defined in the application's Spring configuration.
  • ep.override.properties ->Overwrites the values of any Spring bean in the application.

ep.properties

Using the ep.properties file provides a convenient way to customize your deployed 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:

  1. Create a file named ep.properties in one of the following configuration directories:
    • for Windows: C:\ep\conf or C:\Users\<username>\ep\conf
    • for Linux: /ep/conf or ~/ep/conf
  2. In ep.properties, define the property values you want to set and save your changes.
  3. Restart your server for the changes to take effect.

Configurable ep.properties

Batch Server

Property Description Developer default

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

Cortex

Property Description Developer default

bundle.environment

Specifies the Cortex work environment. Possible values are dev-bundles or prod-bundles.

dev-bundles

bundle.location

Specifies where Cortex Resource Extensions are deployed.

${project.build.directory}/extensions

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 Configuring Ehcache for more information.

The file path in ep.external.ehcache.xml.path must be absolute. For example:
  • Windows: file:///C:/path1/path2/path3/test-ehcache-configuration.xml
  • Linux/Mac: file:///path1/path2/path3/production-ehcache-configuration.xml
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 a deployed application. This section describes how to create the ep.override.properties file and provides some example of beans you can override.

Warning:

Only knowledgeable developers should override bean values.

To create an ep.override.properties file:

  1. Create a file named ep.override.properties in one of the following configuration directories:
    • for Windows: C:\ep\conf or C:\Users\<username>\ep\conf
    • for Linux: /ep/conf or ~/ep/conf
  2. In ep.override.properties, define the property values you want to set and save your changes.
  3. Restart your server for the changes to take effect.

ep.override.properties Syntax

ep.override.properties uses the following syntax for setting values like text, numbers etc: beanName.propertyName=value

For example, the following settings override OpenJPA's DataCache and RemoteCommitProvider beans: 
entityManagerFactory.jpaPropertyMap[openjpa.DataCache]=true
entityManagerFactory.jpaPropertyMap[openjpa.RemoteCommitProvider]=sjvm

To override a Spring bean reference use the following syntax:

beanName.propertyName=${newBeanName}

For example, the following setting enables topSellerJob (disabled by default using disabled list, a Spring bean defined in quartz-setup.xml) in the Batch Server:
topSellerSchedulingTriggersMerger.mergeList=#{topSellerSchedulingTriggers}