Creating the ATG Service Servers: ATG Self Service

Creating the ATG Service Servers

Use the makeDynamoServer script to create the servers for ATG Knowledge, ATG Self Service and ATG Search. You will need to know the RMI and DRP port numbers for each server.

·                     The RMI port allows various components of ATG Service to communicate. The default value of the RMI port is 8860.

·                     The DRP port number identifies each server as a unique ATG server instance. The DRP port number must be unique on a given host. The default value of the DRP port is 8850.

The makeDynamoServer script will create a directory for each server in the <ATG9dir>/home/
servers directory. These directories will contain the properties files for each server.

 

Creating the Servers

To create the servers:

1.             From the <ATG9dir>/home/bin directory on each server, run the makeDynamoServer command. The command should include the server name, and the RMI and DRP ports of the server. The default command is:

makeDynamoServer Servername RMIport DRPport

The following example uses the server name KnowledgeServer and uses the default RMI and DRP ports:

makeDynamoServer KnowledgeServer 8860 8850

2.             Repeat the command to create the number of servers you have in your environment on each server with different ports.

For example, if you are using ATG Self Service with ATG Search, create three servers for:

·                     svcagent or the agent-facing server directory

·                     svcadmin or the customer-facing server directory

·                     svcsearch or the management server directory

Configuring the Agent-Facing Server

1.             Create a JTDataSource.properties file in <ATG9dir>/home/servers/
svcagent/localconfig/atg/dynamo/service/jdbc. Edit the file to contain:

$class=atg.nucleus.JNDIReference
JNDIName=java:/ATGAgentDS

2.             Create a JTDataSource_production.properties file in <ATG9dir>/
home/servers/svcagent/localconfig/atg/dynamo/service/jdbc. Edit the file to contain:

$class=atg.nucleus.JNDIReference
JNDIName=java:/ATGProductionDS

3.             If you are using ATG Reporting, create a JTDataSource.properties file in the <ATG9dir>/home/servers/svcagent/localconfig/atg/reporting/
datawarehouse directory. Edit the file to contain:

$class=atg.nucleus.JNDIReference
JNDIName=java:/ATGDataWarehouseDS

4.             If you are using ATG Reporting, create a JTDataSource.properties file in the <ATG9dir>/home/servers/svcagent/localconfig/atg/
reporting/datawarehouse/loaders directory. Edit the file to contain:

$class=atg.nucleus.JNDIReference
JNDIName=java:/ATGDatawarehouseDS

5.             Edit the Configuration.properties file in <ATG9dir>/home/
servers/svcagent/localconfig/atg/dynamo directory. Edit the file to contain:

adminPort=admin_port_number
siteHttpServerPort=http_server_port_number

Configuring the Customer-Facing Server

1.             Create a JTDataSource.properties file in <ATG9dir>/home/servers/
svcadmin/localconfig/atg/dynamo/service/jdbc. Edit the file to contain:

$class=atg.nucleus.JNDIReference
JNDIName=java:/ATGProductionDS

2.             Create a SearchJTDataSource.properties file in /atg/search/service/that points ATG Search to the correct location of your other data sources. Refer to the ATG Search Installation and Configuration Guide for additional information.

3.             If you are using ATG Reporting, create a JTDataSource.properties file in<ATG9dir>/home/servers/svcadmin/localconfig/atg/reporting/datawarehouse. Edit the file to contain:

$class=atg.nucleus.JNDIReference
JNDIName=java:/ATGDataWarehouseDS

4.             If you are using ATG Reporting, create a JTDataSource.properties file in the <ATG9dir>/home/servers/svcadmin/localconfig/atg/reporting/
datawarehouse/loaders directory. Edit the file to contain:

$class=atg.nucleus.JNDIReference
JNDIName=java:/ATGDatawarehouseDS

5.             Edit the Configuration.properties file in the <ATG9dir>/home/
servers/svcadmin/localconfig/atg/dynamo directory. Edit the file to contain:

adminPort=admin_port_number
siteHttpServerPort=http_server_port_number

Configuring the Management Server

1.             Create a JTDataSource.properties file in <ATG9dir>/home/servers/
svcsearch/localconfig/atg/dynamo/service/jdbc. Edit the file to contain:

$class=atg.nucleus.JNDIReference
JNDIName=java:/ATGProductionDS

2.             Create a JTDataSource_production.properties file in <ATG9dir>/
home/servers/svcsearch/localconfig/atg/dynamo/service/jdbc. Edit the file to contain:

$class=atg.nucleus.JNDIReference
JNDIName=java:/ATGProductionDS

3.             Edit the Configuration.properties file in <ATG9dir>/home/
servers/svcsearch/localconfig/atg/dynamo directory. Edit the file to contain:

adminPort=admin_port_number
siteHttpServerPort=http_server_port_number

4.             Create a RemoteSolutionAuxiliaryDataAdapter.properties file in the <ATG9dir>/servers/svcsearch/localconfig/atg/searchadmin/
adapter/customization directory. Edit the file to contain:

initialRepositories+=/atg/userprofiling/
PersonalizationRepository_production

ServerLockManager on Customer-Facing Servers

The customer-facing servers should define a primary ServerLockManager instance. Additionally, there should be a defined ClientLockManager, which points to the primary ServerLockManager. You can configure backup ServerLockManager instances for redundancy if needed.

ClientLockManagers on Agent-Facing Servers

Agent-facing servers must use the Customer facing cluster lock manager for any shared repositories, and individually scheduled services. The agent-facing servers must define a ClientLockManager_production, which points to the ServerLockManager used by the customer-facing server.

Configuring the LockManager

You must configure the ClientLockManager.properties and the ServerLockManager.properties files to ensure that all servers are using the correct ports.

You can configure the lock managers for any unique and unused ports on your system, however the ports must match. The following example uses the ports 9010, 9011 and 9012:

Server Name	ServerLockManager	ClientLockManager	ClientLockManager_production
Agent-Facing Server	Port 9011	Port 9011	Port 9010
Management Server	Port 9012	Port 9010	NA
Customer-Facing Server	Port 9010	Port 9012	Port 9010

1.             Open the <ATG9dir>/home/servers/svcagent/localconfig/atg/
dynamo/service/directory.

2.             Create a ClientLockManager.properties file. Edit the file to contain the following:

useLockServer=true
lockServerPort=9011

3.             Create a ClientLockManager_production.properties file. Edit the file to contain the following:

lockServerAddress=ProductionLockServerHostname
useLockServer=true
lockServerPort=9010

4.             Create a ServerLockManager.properties file. Edit the file to contain the following:

lockServerPort=9011

5.             Create an <ATG9dir>/home/servers/svcagent/localconfig/atg/
dynamo/server/SQLRepositoryEventServer.properties file. Edit the file to contain the following:

clientAddress=servername
clientPort=18860

6.             If you are using ATG Self Service, open the <ATG9dir>/home/servers/
svcadmin/localconfig/atg/dynamo/service/directory.

7.             Create a ClientLockManager.properties file. Edit the file to contain the following:

useLockServer=true
lockServerPort=9010

8.             Create a ServerLockManager.properties file. Edit the file to contain the following:

lockServerPort=9010

Configuring the ATG Search Requirements

Perform the following steps if you are using ATG Search:

1.             Open the <ATG9dir>/home/servers/svcsearch/localconfig/
atg/dynamo/service/directory.

2.             Create a ClientLockManager.properties file. Edit the file to contain the following:

useLockServer=true
lockServerPort=9012

3.             Create a ClientLockManager_production.properties file. Edit the file to contain the following:

useLockServer=truelockServerPort=9010

4.             Create a ServerLockManager.properties file. Edit the file to contain the following:

lockServerPort=9012

5.             Create an <ATG9dir>/home/servers/svcsearch/localconfig/atg/
dynamo/server/SQLRepositoryEventServer.properties file. Edit the file to contain the following:

clientAddress=servername
clientPort=18860

Adding Additional Components

Note: Making modifications to the existing window scoped and session scoped properties files may cause failover to not work as expected.

Add failover components for any customized code that you have written by modifying theconfig/atg/dynamo/servlet/pipeline/WindowScopeManager.properties file in your custom module. You must add your customized components into thewindowBackupPropertyList+=
/new/custom/component.property list.