First, enable data collection on the loader server. This step is only necessary if you intend to pre-load data into the warehouse (see the “Preparing to Use Commerce Reporting” chapter of the ATG Commerce Programming Guide for information). Create a <ATG10dir>/home/servers/server_name/
localconfig/atg/dynamo/service/DWDataCollectionConfig.properties file and set the following content:

enabled=true
defaultRoot=path to log file directory

Next, configure the data sources for the data warehouse repository, production schema, and local loader machine. Create the following properties file in your loader server’s localconfig directory:

/atg/reporting/datawarehouse/DirectJTDataSource.properties
$class=atg.nucleus.JNDIReference
JNDIName=JDNI name for warehouse datasource

/atg/dynamo/service/jdbc/DirectJTDataSource_production.properties
$class=atg.nucleus.JNDIReference
JNDIName=JDNI name for production datasource

/atg/dynamo/service/jdbc/DirectJTDataSource.properties
$class=atg.nucleus.JNDIReference
JNDIName=JDNI name for local datasource

/atg/dynamo/service/jdbc/DirectJTDataSource_management.properties
$class=atg.nucleus.JNDIReference
JNDIName=JDNI name for management datasource

The data loaders use a lock manager to ensure that only a single loader processes a given file. To configure your loader server as a lock management client, create the following files:

<ATG10dir>/home/servers/server_name/localconfig/atg/dynamo/service/
ClientLockManager.properties

<ATG10dir>/home/servers/server_name/localconfig/atg/dynamo/service/
ClientLockManager_production.properties

<ATG10dir>/home/servers/server_name/localconfig/atg/dynamo/service/
ClientLockManager_agent.properties

<ATG10dir>/home/servers/server_name/localconfig/atg/dynamo/service/
ClientLockManager_management.properties

Each of these files should include the following configuration:

lockServerAddress=lock server hostname
lockServerPort=lock server port
useLockServer=true