In a cluster, you must take following steps to ensure that Content Administration servers do not conflict when they send and receive workflow messages.
Identify the Process Editor Server
You specify the identity of the process editor server in the Workflow Process Manager’s XML configuration file, workflowProcessManager.xml. By default this file is located in:
<ATG2007.3dir>/Publishing/base/config/atg/epub/workflow/process/
To override the default server configuration, create a file with the same name in the top-level directory <ATG2007.3dir>/home/localconfig/atg/epub/workflow/process/ (that is, in the /home/localconfig directory that applies to the whole cluster). The following example shows the process editor server setting in this file:
<?xml version="1.0" encoding="UTF-8" ?> <process-manager-configuration> <process-editor-server> <server-name>dyn1:88500</server-name> </process-editor-server> </process-manager-configuration>
For detailed information on determining the server name and port number, refer to Configuring the Scenario Manager in the ATG Personalization Programming Guide.
The same server can act as the process editor server for scenarios and workflows. To use the same server for both, specify the same <servername> setting for the process editor server in the scenarioManager.xml and workflowProcessManager.xml files.
Specify Global and Individual Workflow Servers
After you designate one server as process editor server, you can decide whether the remaining ATG Content Administration servers should act as global or individual servers for handling workflows. You define a server as global or individual in the top-level localconfig copy of the workflowProcessManager.xml file (see Identify the Process Editor Server).
For detailed information on this configuration process, refer to Configuring the Scenario Manager in the ATG Personalization Programming Guide.
