In a multiple ATG server configuration, it is recommended that you have at least one global server in addition to the process editor server (see above).

You define the identity of the global server in the scenarioManager.xml file that you created in your localconfig directory and used to configure the process editor server (see above). The following shows an example of the file with the addition of the <global-server> tag. Here, two servers, dyn2:8850 and dyn8:8850, have been defined as global.

<?xml version="1.0" encoding="ISO-8859-1" ?>

<!DOCTYPE process-manager-configuration
        PUBLIC "-//Art Technology Group, Inc.//DTD Process Manager//EN"






Specify the name of the global ATG server in the server-name element within the global-server tag. Use the name returned by the /atg/dynamo/service/ServerName component’s serverName() method (typically, the name is of the form hostname:drp-port). For more information about the atg.service.ServerName class, see Referring to Dynamo Servers in the Using Nucleus section of the ATG Programming Guide.

You can define as many global servers as you require.

Note: Because running global scenario servers places an additional burden on your ATG server, consider configuring global servers to not accept any user sessions. Do this by setting the drpEnabled property to false in the server’s /atg/dynamo/Configuration component. Specifically, this may be a good idea if you anticipate creating a lot of scenarios that will run primarily on global servers – for example, scenarios that send e-mail to a large number of visitors at a predetermined time. For more information on session management, refer to the ATG Installation and Configuration Guide.

loading table of contents...