IBM BPM, V8.0.1, All platforms > Tuning > Advanced tuning > Changing the configuration topology > Changing the configuration topology using the command line
Use the command line to move the CEI server to a different deployment target
You can move the Common Event Infrastructure (CEI) server from one deployment target to another using the wsadmin command.
Understand the business rationale for moving the CEI server.
You must be at the dmgr from which you will move the CEI server.
When security and role-based authorization are enabled, use a user ID and password with administrator or operator authority to perform this task.
This task describes how to use the wsadmin command to move the CEI server from one deployment target (either a server or a cluster) to another deployment target.
You might need to move the CEI server if you previously configured a Single Cluster topology in which the CEI server was configured in the application cluster, and because of new processing requirements, you need to move it to the support cluster of a Remote Messaging and Remote Support topology.
In some instances, having the CEI server on the application cluster might adversely affect the processing capabilities of applications deployed on the application cluster. Moving the CEI server off the application cluster and on to a support cluster can reduce the adverse effect that CEI processing has on deployed applications.
The moveCEIServer command invokes moveBPCEventCollector internally, moving the associated CEI Event Group and deployment target-scoped JMS resources such as activation specifications, connection factories and queues (but not the destinations). The destinations are moved only when the messaging engine (ME) is moved.
Procedure
- Open a command window.
The wsadmin command can be found at <INSTALL_ROOT>/bin. Use the wsadmin -profileName parameter to specify the profile to work with.
- At the command prompt, enter the wsadmin command to enter the wsadmin environment.
- Use the moveCEIServer command to move the CEI server from the current deployment target (cluster or server) to a new deployment target (cluster or server).
Example
The example moves the CEI server from one cluster to another cluster. The example is shown for both Jacl and Jython.
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.
Use Jaclwsadmin -connType SOAP -host myDmgr -port 8879 -user dmgradmin -password dmgrpass > $AdminTask moveCEIServer { -fromClusterName Cluster1 -toClusterName Cluster2 > $AdminConfig save
Use Jythonwsadmin -lang jython -connType SOAP -host myDmgr -port 8879 -user dmgradmin -password dmgrpass -lang jython > AdminTask.moveCEIServer('[-fromClusterName cluster1 -toClusterName cluster2]') > AdminConfig.save()This example moves the CEI server from one single server configuration to another single server configuration. The example is shown for both Jacl and Jython
Use Jaclwsadmin -connType SOAP -host myDmgr -port 8879 -user dmgradmin -password dmgrpass > $AdminTask moveCEIServer { -fromServerName Server1 -toServerName Server2 -fromNodeName Node1 -toNodeName Node2} > $AdminConfig save
Use Jythonwsadmin -lang jython -connType SOAP -host myDmgr -port 8879 -user dmgradmin -password dmgrpass -lang jython > AdminTask.moveCEIServer('[-fromServerName Server1 -toServerName Server2 -fromNodeName Node1 -toNodeName Node2]') > AdminConfig.save()
What to do next
You can use the administrative console to verify that the CEI server 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 CEI server has been removed.
Changing the configuration topology using the command line
Related reference:
moveCEIServer command