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 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:

  1. Create a directory named ep in the following location:
    • for windows : C:\Users\<username>\ep
    • for Linux: /etc/ep
  2. In ep, create a file named ep.override.properties.
  3. In ep.properties, define the property values you want to set and save your changes.
  4. Restart your server for the changes to take effect.
Note:

Common properties, such as ep.storefront.contextURL and ep.geoip.provider, can only be set once for all the web applications.

Configurable ep.properties

Storefront

Property Description Developer default

ep.storefront.contextURL

The storefront web application context

/storefront

ep.storefront.port.http

The storefront HTTP port

8080

ep.storefront.port.https

The storefront HTTPS port

8443

ep.sf.secure.channel

Sets the storefront to use https or http

https

ep.velocity.library.autoreload

Determines the caching behavior of the Velocity templates. Set it to true if you want to reload Velocity templates after the interval specified in ep.velocity.cache.seconds. In production, this should be set to false.

true

ep.velocity.cache.seconds

Specifies the cache timeout (in seconds) for Velocity messages and templates. In production, the default value is -1, which caches templates until the storefront web application is restarted.

3

ep.product.attribute.filter.enable

Set to true to enable filtered navigation by attribute

true

ep.localeUrlTool.localeControllerUrl

Sets the URL for handling locale changes.

locale.ep

ep.geoip.provider

Specifies the GeoIP provider. Possible values are demo or quova.

demo

Commerce Manager Server

Property Description Developer default

ep.storefront.contextURL

The storefront web application context

/storefront

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

ep.geoip.provider

Specifies the GeoIP provider. Possible values are demo or quova.

demo

JMS Messaging

Property Description Developer default

ep.jms.type

The Java Class type of the JMS Broker Connection Factory.

org.apache.activemq.pool.AmqJNDIPooledConnectionFactory

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

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.

Warning:

Only knowledgeable developers should override bean values.

To create an ep.override.properties file:

  1. Create a directory named ep in the following location:
    • for windows : C:\Users\<username>\ep
    • for Linux: /etc/ep
  2. In ep, create a file named ep.override.properties.
  3. In ep.properties, define the property values you want to set and save your changes.
  4. Restart your server for the changes to take effect.

ep.override.properties Syntax

ep.override.properties uses the following syntax: 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