WebSphere MQ objects

The following are now fully integrated WebSphere MQ objects:

Service and listener objects
On Windows systems, all WebSphere MQ services have been migrated to WebSphere MQ service or listener objects, with the exception of ROOT custom services. ROOT custom services are not associated with a particular queue manager, are administered using the control command amqmdain.

Service objects are used to define programs that are to be executed when a queue manager starts or stops, such as trigger monitors, dead letter queue handlers, or short lived programs that perform specific tasks. You can record and recover a media image of a service, and you can set authorities to service objects. For more information, see Services.

Listener objects allow you to manage the starting and stopping of listener processes from within the scope of a queue manager. You can now record and recover a media image of a listener, and you can set authorities to listener objects. For more information, see Listeners.

Channel objects
Channels are now fully integrated WebSphere MQ objects. You can now record, and recover, a media image of a channel, and you can set authorities to channel objects. For more information, see Channels.
Client connection channel objects
Client connection channels are now fully integrated WebSphere MQ objects. You can now record, and recover, a media image of a client connection channel, and you can set authorities to client connection channel objects. For more information, see Client connection channels.