IBM Business Process Manager, V8.0.1, All platforms > Reference > Commands and scripts > Commands (wsadmin scripting)
moveBRManager command
Use the moveBRManager command to move the Business Process Rules Manager from one deployment target to another deployment target.
You can use this command to move the Business Rules Manager from one cluster (such as an application cluster) to another cluster (such as a support cluster). Or, you can use this command to move the Business Process Rules Manager from one server to another server.
One reason for moving the Business Process Rules Manager 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 Rules Manager from an application cluster to a support cluster.
The default behavior of the moveBRManager command is to move the Business Process Rules Manager application with the default name to the new deployment target.
Attention: After you have moved the Business Process Rules Manager to the new deployment target, you must 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 Rules Manager cannot be started.
Moving Business Rules Manager might require you to adjust the web browser to the Business Rules Manager URL. The value of the URL depends on how the virtual host is configured for your installation.
After using the command, save your changes to the master configuration using one of the following commands:
Required parameters
- fromClusterName name_of_cluster
- The name of the cluster on which Business Process Rules Manager is installed.
Do not specify this parameter if you have specified the fromNodeName or fromServerName parameter.
- fromNodeName name_of_node
- The name of the node on which Business Process Rules Manager is installed.
If you specify this parameter, you must also specify the fromServerName parameter.
Do not specify this parameter if you specified the fromClusterName parameter
- fromServerName name_of_server
- The name of the server on which Business Process Rules Manager is installed.
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.
- toClusterName name_of_cluster
- The name of the cluster to which Business Process Rules Manager must be moved.
Do not specify this parameter if you have specified the toNodeName or toServerName parameter.
- toNodeName name_of_node
- The name of the node to which Business Process Rules Manager must be moved.
If you specify this parameter, then you must also specify the toServerName parameter.
Do not specify this parameter if you have specified the toClusterName parameter.
- toServerName name_of_server
- The name of the server to which Business Process Rules Manager must be moved.
If you specify this parameter, then you must also specify thetoNodeName parameter. Do not specify this parameter if you have specified the toClusterName parameter.
Optional parameters
- applicationName name_of_application
- The installation name of the Business Process Rules Manager application that must be moved.
If you do not specify this parameter, the Business Process Rules Manager application with the default name on the deployment target is moved.
The default name of Business Process Rules Manager application is as follows:
- BusinessRulesManager_<clusterName>, or
- BusinessRulesManager_<nodeName>_<serverName>
For example, if you install Business Rule Manager on a cluster named "mycluster", the default name is: BusinessRulesManager_mycluster.
Examples
The examples show how to move Business Rules Manager from server to server or from cluster to cluster. However, it is also possible to move Business Process Rules Manager from a server to a cluster, or from a cluster to a server.
- Jython example:
The example uses moveBRManager to move the Business Process Rules Manager from Server1, to Server2.
AdminTask.moveBRManager('[-fromServerName Server1 -toServerName Server2 -fromNodeName Node1 -toNodeName Node2 -applicationName BRManager_Node1_Server1]')- Jacl example:
The example uses moveBRManager to move the Business Rules Manager from an application cluster (Cluster1), to a support cluster (Cluster2) in a multi-clustered environment.
$AdminTask moveBRManager { -fromClusterName Cluster1 -toClusterName Cluster2 -applicationName BRManager_Cluster1}
Parent topic: Commands (wsadmin scripting)
Related information:
Obtaining online help using wsadmin scripting
Administrative command invocation syntax using wsadmin scripting
Use the wsadmin scripting tool
Jython script library