Configuration files for a configuration group are stored in one of these directories:

The groupconfig directory contains server and client subdirectories, which are used by the local ConfigurationServer and ConfigurationClient, respectively. The client directory obtains its content from the master ConfigurationServer and should not be edited. You should only update the server directory content on the master ConfigurationServer.

Node-Type Configuration

Configuration for a given node type is stored in the subdirectory of the same name. For example, if a configuration group defines two node types, production and staging, the master ConfigurationServer stores settings for them in two subdirectories as follows:

../groupconfig/server/nodetype/production
../groupconfig/server/nodetype/staging

For example, a production setting for /atg/dynamo/service/jdbc/FakeXADataSource is stored on the master ConfigurationServer in this directory:

$ATG_HOME/groupconfig/server/nodetype/production/atg/dynamo/service/jdbc/
FakeXADataSource.properties

This file is propagated to production clients as follows:

$ATG_HOME/groupconfig/client/nodetype/production/atg/dynamo/service/jdbc/
FakeXADataSource.properties

At startup, a client’s nodetype directory is added to its configuration path and is read before its instance and localconfig directories.

Instance Configuration

Configuration settings that are specific to an Oracle ATG Web Commerce server instance can be stored on this path:

../groupconfig/client/instance/host-name+server-name

The master configuration server stores configuration settings for each Oracle ATG Web Commerce server instance in this subdirectory:

../groupconfig/server/instance/host-name+server-name

For example, a master configuration server maintains instance settings for server production1 on host saturn in this directory:

../groupconfig/server/instance/saturn+production1

At startup, a server’s instance directory is added to its configuration path and is read immediately before any localconfig property settings.

Note: In order to avoid ambiguity among instances on a given host, each instance subdirectory has its own instance.id.properties file. The properties in that file uniquely identify the given instance, so the master configuration server can differentiate among multiple Oracle ATG Web Commerce instances on the same host, if necessary.