The main advantage of using Network Deployment (ND) to create and administer process choreographer instances is that it makes clustering scenarios possible, where all the business process containers in a cluster are administered centrally.
Deployment manager must have access to the process choreographer database
The deployment manager must have access to all the process choreographer databases that are used by business process containers in the cell. You must install an appropriate database client on the deployment manager machine, and add the database driver to the deployment manager class path. The following figure shows this configuration.
Customization required after installing and configuring process choreographer on a cluster
If you are creating a clustered setup that uses WebSphere MQ clusters of queue managers, you must perform some manual customization to make each process choreographer instance use its own queue managers. The necessary actions are described in Configuring the business process container.
For more information about using clustering with process choreographer, see process choreographer scenarios for clustering
Before installing a business process application
Make sure that the servers where you want to install the application are running before installing the application. At least one server must be running for JNDI names to be resolved. After installing the application, it is still possible to map it onto additional servers and clusters by editing the business process application..
Restrictions when editing a business process application
When you edit a business process application, you change the mapping of the application modules to the application servers and the WebSphere clusters in the cell. You can use the administrative console or administration scripts to change this mapping.
Only the EJB modules and Web modules appear in the administrative console. If you change the mapping of an EJB module to a deployment target, then the processes associated with the module are written to the databases that belong to the new deployment target. The processes are not automatically deleted from the database that belongs to the previous deployment target. These processes are only deleted if you remove all the modules belonging to the process application from the deployment target.
When you edit a business process: