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 System Settings

Configuring System Settings

Elastic Path Commerce has five types of settings you can configure:

  • System settings
  • System settings have a global scope and only one value for each setting. For example, the location of the assets folder is a system setting. In the Commerce Manager, system setting names begin with COMMERCE/SYSTEM.
  • Store-specific settings
  • Store specific settings are settings that are unique for each individual store. For example, the theme setting is a store specific setting. In the Commerce Manager, Store-specific setting names begin with COMMERCE/STORE.
  • Application-specific settings
  • Application-specific settings are unique settings for the web applications (Cortex, Commerce Manager, Search Server, Integration Server, etc). For example, an application-specific setting is vfsUserName, which is the username to use when connecting to the VFS host. In the Commerce Manager, application-specific setting names begin with COMMERCE/APPSPECIFIC/<appName>.
  • Search settings
  • Search settings can be both store-specific and application specific. You can customize the search settings so each store, application, and index have different values. These settings are described in detail further in the System configuration settings reference. In the Commerce Manager, search setting names begin with COMMERCE/SEARCH.
  • Cache settings define the cache timeout values used for the interval-based refresh strategy. In the Commerce Manager, cache setting names begin with COMMERCE/Cache.

Elastic Path 6.17.0 provides you with two tools to modify your system configurations settings:

Most setting changes do not require restarting the web applications. Changes take effect either immediately or based on their refresh strategy.