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 Oracle Commerce Platform server is responsible for handling all scenario events and actions, both individual and global.
Once you move to a multiple 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 Oracle Commerce Platform 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 <ATG11dir>/DSS/config/config.jar. (Note that this file uses the Process Manager DTD located in <ATG11dir>\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" ?> <process-manager-configuration> <process-editor-server> <server-name>dyn1:8850</server-name> </process-editor-server> </process-manager-configuration>
Specify the name of the 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 Platform Programming Guide.
Note the following important points about specifying the DRP port number:
The process editor server must the use the DRP port so that it can be accessed by the
ServerNamecomponent. You do not have to enable DRP (Dynamo Request Protocol) itself; in this case, the Scenarios module just uses it to create aServerNamefor the process editor server.For situations where you have more than one Oracle Commerce Platform product instance running on the same server, you must specify a unique DRP port for each instance to guarantee that each
hostname:drp-portcombination will be unique. This step is required even if the servers do not use DRP.Non-DAS application servers, such as Oracle WebLogic, do not use DRP. However, even if you are running the Scenarios module on a non-DAS application server, you must specify a DRP port so that the Scenarios module can create a unique name for the process editor server. For more information, refer to the Platform Installation and Configuration Guide.
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 Oracle Commerce Platform 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.
