Use the moveBPCExplorer command to move the Business Process Choreographer Explorer from one deployment target to another deployment target.
One reason for moving the Business Process Choreographer Explorer might be to more evenly distribute processing load. For example, if you have installed everything on a single cluster and you now want to have a separate cluster for your support applications to reduce the load on your application cluster, you could move the Business Process Choreographer Explorer from an application cluster to a support cluster.
Moving Business Process Choreographer Explorer might result in a change of the URL under which the Business Process Choreographer Explorer can be accessed. Make sure 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. If you are using a web server, make sure that you update and propagate the plug-in configuration for your web server. For information about virtual hosts settings and mapping virtual hosts for web modules, see the WebSphere Application Server information center.
AdminConfig.save()
$AdminConfig save
Do not specify this parameter if the fromNodeName or fromServerName parameters are specified
If you specify this parameter, then you must also specify the fromServerName parameter. Do not specify this parameter if you have specified the fromClusterName parameter.
If you specify this parameter, then you must also specify the fromNodeName parameter. Do not specify this parameter if you have specified the fromClusterName parameter.
Do not specify this parameter if you have specified the toNodeName or toServerName parameters.
If you specify this parameter, then you must also specify the toServerName parameter.
Do not specify this parameter if you have specified the toClusterName parameters.
If you specify this parameter, then you must also specify thetoNodeName parameter. Do not specify this parameter if you have specified the toClusterName parameter.
If you do not specify this parameter, all Business Process Choreographer Explorer applications on the deployment target are moved.
The following examples show how to use moveBPCExplorer.
The examples show how to move Business Process Choreographer Explorer from server to server or from cluster to cluster. However, it is also possible to move Business Process Choreographer Explorer from a server to a cluster, or from a cluster to a server.
The example uses moveBPCExplorer to move the Business Process Choreographer Explorer from Server1, to Server2.
AdminTask.moveBPCExplorer('[-fromServerName Server1 -toServerName Server2 -fromNodeName Node1
-toNodeName Node2 -applicationName BPCExplorer_Node1_Server1]')
The example uses moveBPCExplorer to move the Business Process Choreographer Explorer from an application cluster (Cluster1), to a support cluster (Cluster2) in a multi-clustered environment.
$AdminTask moveBPCExplorer { -fromClusterName Cluster1 -toClusterName Cluster2
-applicationName BPCExplorer_Cluster1}