As installed, the Oracle Commerce Platform sets the configuration path to the following directories:
configis the module base configuration directory, specified by the configuration path attributeATG-Config-Path.config. This directory contains configuration files that are used to start up components required by Oracle Commerce Platform products.Because each new Oracle Commerce Platform distribution overwrites the configuration files in
config, you should not edit their properties.localconfigcontains custom properties settings, and have the highest priority in the configuration path. Settings inlocalconfigare preserved across product upgrades; changes to base configuration properties can be safely set here.
Depending on application requirements, you can set the configuration path so it includes settings for specific configurations:
Application Server Configuration
During application assembly, you can add to the configuration path directories that are specific to your application server. You do so by setting the configuration path attribute ATG-platformConfig-Path, where the string platform denotes the application server—for example, ATG-jbossConfig-Path.
Production Environment Configuration
Two configuration path attributes can be used to configure an application for production:
ATG-LiveConfig-Pathcontains settings appropriate for applications that are deployed for production.ATG-platformLiveConfig-Pathcontains production-ready settings that are specific to your application server. The stringplatformdenotes the application server—for example,ATG-jbossLiveConfig-Path.
The directories specified by these attributes are included in the configuration path only when the application is assembled with the -liveconfig switch (see the Platform Installation and Configuration Guide).
Named Configuration
Two configuration path attributes let you associate a set of properties files with a user-defined name:
ATG-cfgNameConfig-Pathspecifies configuration directories that are associated with the named configurationcfgName—for example,ATG-ManagementConfig-.
PathATG-app-svrCfgNameConfig-Pathspecifies configuration directories that are associated with the named configurationCfgNameand are specific to the application server denoted byapp-svr—for example,ATG-JBossManagementConfig-Path.
In order to set the configuration path with the configuration directories associated with cfgName, the application must be assembled with the –layer cfgName switch.
Named configurations are useful for associating related configuration settings that span multiple modules, which can be simultaneously invoked under specific conditions.
For example, given the following configuration path attributes—
ATG-ManagementConfig-Path: management_config/ ATG-JbossManagementConfig-Path: jboss_management_config/
—the configuration path includes these directories if you assemble the application as follows:
runAssembler -jboss MyApp.ear –layer Management –m Service.adminNote: You can assemble a single EAR file that contains all named configuration layers that are required across various servers, then activate the desired named configuration layers on each server by setting the system property atg.dynamo.layers on server startup. For more information, see Specifying Configuration Layers on Server Startup.
