Moving the Business Rules Manager to a different deployment target

You can move the Business Rules Manager from one deployment target to another using the wsadmin command.

Before you begin

Understand the business rationale for moving the Business Rules Manager.

One reason for changing your configuration might be to more evenly distribute processing load.

About this task

This task describes how to use the wsadmin command to move Business Rules Manager from one deployment target (either a server or a cluster) to another deployment target.

You might need to move Business Rules Manager if you previously configured a single cluster topology in which the Business Rules Manager 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.

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 moveBRManager command to move the Business Rules Manager from the deployment target to which is currently configured, to a new deployment target.
The default behavior of the moveBRManager command is to move the Business Rules Manager application with the default name to the new deployment target.

Example

The example moves Business Rules Manager from one cluster to another cluster. The example is shown for both Jacl and Jython.

Note: The -applicationName parameter is optional. If you do not specify this parameter, the Business Rules Manager application with the default name on the deployment target is moved.

The default name of Business 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.

Note: If you are running the admin client from the deployment manager bin folder, you do not need to include the -host and -port parameters in the command.

Using Jacl

wsadmin -connType SOAP -host myDmgr -port 8879 -user dmgradmin -password dmgrpass
> $AdminTask moveBRManager { -fromClusterName Cluster1 -toClusterName Cluster2 
-applicationName BRManager_Cluster1}

$AdminConfig save

Using Jython

AdminTask.moveBRManager('[-fromClusterName cluster1 -toClusterName cluster2 
-applicationName BRManager_Cluster1]')

AdminConfig.save()

This example moves Business Rules Manager from one single server configuration, to another single server configuration. The example is shown for both Jacl and Jython

Using Jacl

wsadmin -connType SOAP -host myDmgr -port 8879 -user dmgradmin -password dmgrpass
> $AdminTask moveBRManager { -fromServerName Server1 -toServerName Server2 
-fromNodeName Node1 -toNodeName Node2 -applicationName BRManager_Node1_Server1}

$AdminConfig save

Using Jython

AdminTask.moveBRManager('[-fromServerName Server1 -toServerName Server2 -fromNodeName Node1
-toNodeName Node2 -applicationName BRManager_Node1_Server1]') 

AdminConfig.save()

What to do next

You can use the administrative console to verify that the Business Rules Manager has been moved. The application should now be mapped to the new deployment target.

Note: The previous deployment target is not changed other than the fact that the Business Rules Manager has been removed.

Attention: After you have moved the Business Rules Manager 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 prior to node synchronization, you receive an error indicating that Business 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.