The following modifications are made for the Data Warehouse Server instance.

Data Warehouse Server Property File Configurations

The following property files are configured for the Data Warehouse Server:

Property File

Modification

/atg/dynamo/Configuration

adminPort=8080
siteHttpServerPort=8080
rmiEnabled=true
rmiPort=8860
fileDeploymentPort=8820
drpPort=8810

/atg/server/
SQLRepositoryEventServer

enabled=true

/atg/server/
SQLRepositoryEventServer_agent

enabled=true

/atg/server/
SQLRepositoryEventServer_production

enabled=true

/atg/dynamo/service/
ClientLockManager

$class=atg.service.lockmanager.ClientLockManager
lockServerPort=9010
useLockServer=true
lockServerAddress=localhost

/atg/dynamo/service/
ClientLockManager_production

$class=atg.service.lockmanager.ClientLockManager
lockServerAddress=localhost
lockServerPort=9010
useLockServer=true

/atg/DWDataCollectionConfig

enabled=true
defaultRoot=D:/ATG/ATG9.3/home/logs

/atg/dynamo/service/
Initial

initialServices+=/atg/dynamo/service/
ServerLockManager

/atg/dynamo/serivce/
ServiceLockManager

port=9010

Data Warehouse Server XML File Configurations

The following configurations are made for the Data Warehouse Server XML files:

XML File

Modification

/atg/scenario/
internalScenarioManager.xml

<?xml version="1.0" encoding="ISO-8859-1" ?>
<process-manager-configuration>
<!-- This ensures that the searchadmin server
doesn't start it's own scenario editor server
but instead points to the agent scenario editor
server -->
  <process-editor-server>
    <server-name>localhost:28810</server-name>
  </process-editor-server>
</process-manager-configuration>

/atg/scenario/
scenarioManager.xml

<?xml version="1.0" encoding="ISO-8859-1" ?>
<process-manager-configuration>
  <process-editor-server>
    <server-name>localhost:18810</server-name>
  </process-editor-server>
</process-manager-configuration>

 
loading table of contents...