IBM BPM, V8.0.1, All platforms > Tuning > Advanced tuning > Changing the configuration topology > Changing the configuration topology using the command line
Moving the Business Process Choreographer Explorer to a different deployment target
You can move the Business Process Choreographer Explorer from one deployment target to another using the wsadmin command.
Understand the business rationale for moving the Business Process Choreographer Explorer.
One reason for changing your configuration might be to more evenly distribute processing load.
This task describes how to use the wsadmin command to move Business Process Choreographer Explorer from one deployment target (either a server or a cluster) to another deployment target.
You might need to move Business Process Choreographer Explorer if you previously configured a single cluster topology in which the Business Process Choreographer Explorer was configured in the application cluster, and because of new processing requirements, you need to move it to the support cluster of a multi-clustered topology.
In scenarios where multiple instances of Business Process Choreographer Explorer are configured on a particular deployment target, the default behavior of the moveBPCExplorer command is to move all explorer instances to the new deployment target. However, the moveBPCExplorer command does provide an optional parameter named -applicationName which you use to move just one of the explorer instances to a new deployment target.
The human task manager configuration includes settings for an explorerURLPrefix and an administratorURLPrefix that may (depending on the web server configuration) point to the explorer instance . These two settings are not updated automatically when you move Business Process Choreographer Explorer. To make sure the human task manager remains synchronized with the moved Business Process Choreographer Explorer, you may have to update these settings manually. For information on how to change human task manager parameters, see Using the administrative console's Business Process Choreographer configuration page.
Procedure
- Open a command window.
The wsadmin command can be found at <INSTALL_ROOT>/bin. Use wsadmin's -profileName parameter to specify the profile to work with.
- At the command prompt, enter the wsadmin command to enter the wsadmin environment.
- Use the moveBPCExplorer command to move
the Business Process Choreographer Explorer from the deployment target to which is currently configured, to a new deployment target.
The default behavior of the moveBPCExplorer command is to move all explorer instances to the new deployment target.
Example
The example moves Business Process Choreographer Explorer from one cluster to another cluster. The example is shown for both Jacl and Jython.
The -applicationName parameter is optional. If you do not specify this parameter, all Business Process Choreographer Explorer applications on the deployment target are moved.
If you are running the admin client from the dmgr bin folder, you do not need to include the -host and -port parameters in the command.
The following example uses Jacl:
wsadmin -connType SOAP -host myDmgr -port 8879 -user dmgradmin -password dmgrpass
> $AdminTask moveBPCExplorer { -fromClusterName Cluster1 -toClusterName Cluster2
-applicationName BPCExplorer_Cluster1}
$AdminConfig save
The following example uses Jython:
AdminTask.moveBPCExplorer('[-fromClusterName cluster1 -toClusterName cluster2
-applicationName BPCExplorer_Cluster1]')
AdminConfig.save()
This example moves Business Process Choreographer Explorer from one single server configuration, to another single server configuration. The example is shown for both Jacl and Jython
The following example uses Jacl:
wsadmin -connType SOAP -host myDmgr -port 8879 -user dmgradmin -password dmgrpass
> $AdminTask moveBPCExplorer { -fromServerName Server1 -fromNodeName Node1
-toServerName Server2 -toNodeName Node2 -applicationName BPCExplorer_Node1_Server1}
$AdminConfig save
The following example uses Jython:
AdminTask.moveBPCExplorer('[-fromServerName Server1 -fromNodeName Node1 -toServerName Server2
-toNodeName Node2 -applicationName BPCExplorer_Node1_Server1]')
AdminConfig.save()
What to do next
You can use the administrative console to verify that the Business Process Choreographer Explorer has been moved. The application should now be mapped to the new deployment target.
The previous deployment target is not changed other than the fact that the Business Process Choreographer Explorer has been removed.
Attention: After you have moved the Business Process Choreographer Explorer to the new deployment target, you need to complete the node synchronization operation and ensure that changes are saved to the configuration. If you start the server or the application that you have moved before node synchronization, you receive an error indicating that Business Process Choreographer Explorer cannot be started. Moving Business Process Choreographer Explorer might result in a change of the URL under which the Business Process Choreographer Explorer can be accessed. Verify that you adjust your web browser to use the correct Business Process Choreographer Explorer URL. The value of the URL depends on how the virtual host and context root are configured for your installation. In case you are using a web server make sure that you update and propagate the plug-in configuration for your web server. For information virtual hosts settings and mapping virtual hosts for web modules, see the WebSphere Application Server information center.
Changing the configuration topology using the command line
Related tasks:
Using the administrative console's Business Process Choreographer configuration page: 
Postmigration tasks for IBM BPM:
Related reference:
moveBPCExplorer command
Related information:
