As installed, Oracle ATG Web Commerce sets the configuration path to the following directories:

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:

The directories specified by these attributes are included in the configuration path only when the application is assembled with the -liveconfig switch (see the ATG Installation and Configuration Guide).

Named Configuration

Two configuration path attributes let you associate a set of properties files with a user-defined name:

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 MyApp.ear –layer Management –m Service.admin

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