Migrating WebSphere MQ Services

 

WebSphere MQ services define one or more commands to be run when a queue manager is started or stopped. Examples of a service include:

• Listener

• Channel initiator

• Trigger monitor

• Command server

• Channel

• Queue manager custom service

When migrating from a previous version of WebSphere MQ, the WebSphere MQ services are automatically migrated into WebSphere MQ Objects. (For more information about WebSphere MQ Objects see the WebSphere MQ System Administration Guide.) These objects can then be administered in the WebSphere MQ Explorer.

Examples of the migration of services to WebSphere MQ Objects are:

• A listener is migrated to a WebSphere MQ listener object, equivalent to one defined by the DEFINE LISTENER ... MQSC command.

• A trigger monitor is migrated to a WebSphere MQ service object with STARTCMD set to runmqtrm.

• A channel is migrated to a WebSphere MQ service object with STARTCMD set to runmqchl.

It is important to note that after migration all services will run after the queue manager with which they are associated starts. This is the case even if the service previously ran before the associated queue manager started.

Only services that are associated with queue managers will be migrated. ROOT custom services, which are services that are not associated with a particular queue manager, are not migrated and they will remain as they were.

 

Parent topic:

Migrating from WebSphere MQ V5.3