The default Scenario Manager configuration does not specify a process editor server. The first server that is started is assumed to be the process editor server. This behavior works well in a single-server environment, where one ATG server is responsible for handling all scenario events and actions, both individual and global.

Once you move to a multiple ATG server configuration, however, it is highly recommended that you designate one of your servers as the process editor server. Again, if none is specified, the first server that is started is assumed to be the process editor server. However, designating a server in advance is preferable because it gives you greater control over your ATG environment.

The identity of the process editor server is specified in the Scenario Manager’s XML configuration file, which is located in the /atg/scenario/scenarioManager.xml file in <ATG10dir>/DSS/config/config.jar. (Note that this file uses the Process Manager DTD located in <ATG10dir>\DSS\lib\classes.jar.) To override the default server configuration, create a file with the same name and the same path in top-level localconfig directory for your cluster of servers. The following shows an example of the file:

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



Specify the name of the ATG process editor server in the server-name 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 Nucleus: Using Nucleus section of the ATG Platform Programming Guide.

Note the following important points about specifying the DRP port number:

To verify that your process editor server has been configured correctly, start both the process editor server and all other global and individual scenario servers (see below). As each server starts up, an appropriate message appears in the ATG console window; for example, “Initializing process editor server dyn1:8850,” “Initializing global scenario server dyn2:8850,” or “Initializing individual scenario server dyn3:8850.” Make sure that there is exactly one process editor server running and that all other scenario servers are designated as global or individual.

See The Scenario Registry and Scenario Definition Files for information on changing the process editor server from one server to another.