migrateServerMEtoCluster command

When a server that is a member of a bus is converted to a cluster, use the migrateServerMEtoCluster command to migrate the messaging engine (ME) in the server to cluster scope. During the conversion, the bus membership is not automatically transferred to cluster scope. If we want the cluster to be a member of the bus, use this command to perform that transfer.

To run the command, use the AdminTask object of the wsadmin scripting client.

(iSeries) (iSeries) The wsadmin scripting client is run from Qshell. (iSeries) See Configure Qshell to run WebSphere scripts .

This command is valid only when used with WebSphere Application Server v7.0 or later application servers. Do not use it with earlier versions.

Command-line help is provided for service integration bus commands:

• For a list of the available service integration bus commands in Jython and a brief description of each command, enter at the wsadmin prompt:

  print AdminTask.help('SIBAdminCommands')

• For overview help on a given command, enter at the wsadmin prompt:

  print AdminTask.help('command_name')

After using the command, save the changes to the master configuration using the following command:

AdminConfig.save()

The migrateServerMEtoCluster command migrates a messaging engine in a server to the scope of a cluster. This is of use when a server that is a member of a service integration bus has been converted to a cluster. The conversion to a cluster does not automatically make the cluster a member of the bus. Use this command to transfer the bus membership to the cluster. This can be used to allow the messaging engine to be highly available or to add further messaging engines to the cluster for scalability. In this situation, we must not delete the messaging engine at server scope and re-create it at cluster scope, because the unique identifier (UUID) of the messaging engine would be lost and the messaging engine would not work with previously configured destinations.

The migrateServerMEtoCluster command makes the new server cluster a member of the bus.

One example of a situation when this command is useful is after a server that is a member of a bus has been federated into a cell, using the option to include the bus, then the server is promoted to a member of a cluster by creating a new cluster with the server as the first member.

Target object

A messaging engine.

The messaging engine is copied to the scope of the cluster and all the destination localization references are copied, ensuring that it continues to function with previously configured destinations. The messaging engine definition at the scope of the server is deleted.

Required parameters

-bus bus_name

The name of the service integration bus that the server is a member of, when that server hosts the messaging engine to migrate. We can use the listSIBuses command to list the names of existing buses.

-node node

The name of the node on which the server runs, when that server hosts the messaging engine to migrate.

-server server

The name of the server that hosts the messaging engine to migrate.

The server must be a member of the bus specified and run on the node specified, and must already be converted to the cluster specified in the command.

-cluster cluster_name

The name of the server cluster that the server has been converted to, and to which we want to migrate the messaging engine.

The cluster must exist and the server must be a member of the cluster. The cluster must not yet be a member of the service integration bus that the server is a member of.

Optional parameters

-rename TRUE | FALSE

Whether to rename the messaging engine and message points and use the naming conventions for these resources in a cluster. For example, the name of a messaging engine on a server that uses the naming convention node.server-bus_name changes to use the naming convention cluster_name.nnn-bus_name.

TRUE

The messaging engine and message points are renamed using the naming conventions for these resources in a cluster.

FALSE

The messaging engine and message points are not renamed using the naming conventions for these resources in a cluster.

The default is FALSE.

Example

Migrate to cluster1 a messaging engine that is currently configured on node1 server1, and rename the messaging engine and all its message points to use cluster terminology. Server1 is a member of bus1 and has already been converted to cluster1. Cluster1 is not yet a member of bus1.

AdminTask.migrateServerMEtoCluster ('-bus bus1 -node node1 -server server1 -cluster cluster1 -rename TRUE')