Connecting to a BPM Process Model Server
A BPM process model server is an Integration Server that hosts the webMethods Process Engine and executes business processes.
To connect to target BPM (ProcessModel) servers
1. Make sure the Process Audit Log database component is installed and Integration Server is configured to write to it. For instructions, see Installing Software AG Products.
2. In Deployer, go to the Servers > BPM(ProcessModel) page.
3. For every target ProcessModel server, click Configure BPM(ProcessModel) Server and complete these fields:
Field | Entry |
Name | Name to assign to the server. The name can be up to 32 characters long and cannot contain spaces or the following special characters: $ ~ / \ # & @ ^ ! % * : ; , + = > < ‘ ’ " |
Host | Host name or IP address of the server. |
Port | Port for the server. |
User | User name for a user account with Administrator authority that Deployer can use to access the server. |
Password | Password that is associated with the user name. |
Version | |
Use SSL | Whether Deployer should use SSL to connect to the server. |
4. Click Configure. To test the connection, click 
. 5. In Designer, duplicate the logical-to-physical server mapping (defined for each ProcessModel server) on the source and target ProcessModel servers for each model you want to deploy. In the Integration Server Administrator for each of the servers, do the following:
a. Define the physical servers in the mapping as remote servers. For instructions, see webMethods Integration Server Administrator’s Guide.
Note:
Each
Integration Server hosting a process model in a cluster must be configured to use the same alias name and port number as the remote alias defined for the cluster. For more information about deploying to clustered
Integration Servers, see
Deploying to Clustered Integration
Servers.
b. Go to the Packages > Management page and click 
for the WmDesigner package. c. Click Add Logical Server and complete these fields:
Field | Entry |
Name | Name of a logical server in the mapping for the ProcessModel server. The name can be up to 32 characters long and cannot contain spaces or the following special characters: $ ~ / \ # & @ ^ ! % * : ; , + = > < ‘ ’ " Note:
In clusters, both the source and target ProcessModel servers must use the same logical server name. |
Physical Server | Physical server to which the logical server is mapped. This should be the same value as the remote server alias name you defined in step 5a. |
d. Click Add Logical Server.
e. Repeat these steps to duplicate the rest of the mapping.
f. Repeat these steps for every process model you want to deploy.
6. Install the WmDeployerResource package on each ProcessModel server that will run process steps. In Deployer, go to the Servers > IS & TN page; the page lists all ProcessModel servers you defined as remote servers. In the Install column, select the check box next to each ProcessModel server and click Install.
7. If a process model to deploy includes a task, go to the Packages > Management page on the model's source and target ProcessModel servers, click for the WmTaskClient package, and identify the My webMethods Server that hosts the task.