Configuring Multiple JVMs in Self Service

Note: It is strongly suggested that you install data warehousing using CIM. During the installation process, you can configure your environment to use multiple JVMs. The following instructions are provided merely as a reference should you need to reinstall.

It is best to run the production SelfServiceDataWarehouse module in a separate JVM instance than your Self Service server. Depending on the volume of reporting data to be summarized, you may want to dedicate one instance to an application that contains only the SelfServiceDataWarehouse module.

It is also possible to configure the SelfServiceDataWarehouse module to work in the same JVM as your Self Service Server.

The last two steps in this procedure specify modules to include in the Web application you build. For guidance on assembling applications, see the ATG Installation and Configuration Guide for your application server.

To run the Self Service application in one JVM and run a Self Service application or service.common and Self Service DataWarehouse in another JVM:

  1. Configure each server’s properties to use same the same database by modifying the FakeXADataSource.properties file. Refer to the Configuring FakeXADataSource Files section for additional information.

  2. Disable user sessions for the second server. Refer to the ATG Installation and Configuration Guide for further information. (Skip this step if you are configuring a service.common and Self Service Data Warehouse JVM.)

  3. Configure the lock manager by configuring one or more of your servers to start the /atg/dynamo/service/ServerLockManager at application startup. Modify the <ATG10dir>/home/servers/svcadmin/localconfig/atg/dynamo/service/
    Initial.properties     file: Refer to the Configuring the LockManager section for additional information.

    #server/12.3.4.500
    #/localconfig/atg/dynamo/service/Initial.properties:
    initialServices+=ServerLockManager

  4. Configure the ClientLockManager component in the <ATG10dir>/home/servers/svcadmindw/localconfig/atg/dynamo/service/
    ClientLockManager.properties     file for both servers to use the ServerLockManager:

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

    Refer to the ATG Repository Guide for additional information.

  5. Assemble, deploy, and start a Self Service application that includes the Service.SelfService module. Refer to the Assembling ATG Service section for additional information.

  6. Assemble, deploy, and start a Self Service Data Warehouse application that includes the Service.SelfServiceDataWarehouse module.