IBM WebSphere MQ plugin
The Deploy IBM WebSphere MQ (WMQ) plugin can be used to manage resources on a WebSphere MQ environment. The plugin can deploy and undeploy local queues and alias queues on a queue manager, and can be extended to support the management of other resources in a WebSphere MQ environment.
For more information, see IBM WebSphere Application Server Plugin Reference.
- Local queue
- Alias queue
- Control task to start and stop queue managers.
This plugin can only be used in WebSphere MQ environments hosted in Linux machines.
The plugin works with the standard deployment package DAR format. The following is a sample
deployit-manifest.xml file that can be used to create a WMQ specific deployment package. It contain declarations for a local queue(
wmq.LocalQueueSpec) and an alias queue (
<?xml version="1.0" encoding="UTF-8"?> <udm.DeploymentPackage version="1.0" application="WebsphereMQApp"> <orchestrator>default</orchestrator> <parallelByContainer>false</parallelByContainer> <deployables> <wmq.AliasQueueSpec name="testAliasQueue"> <target>testTargetQueue</target> <cluster>QUEUE_CLUSTER</cluster> </wmq.AliasQueueSpec> <wmq.LocalQueueSpec name="testLocalQueue"> <maxDepth>3</maxDepth> <boqname>testBackoutQueue</boqname> <bothresh>10</bothresh> </wmq.LocalQueueSpec> </deployables> </udm.DeploymentPackage>
wmq.QueueManager is a container type which represents an existing queue manager running in the MQ environment, and the MQ resources such as local queue or alias queue can be targeted to it. It has a containment relationship with the host, which means that it can only be created under a host.
Also, because a
wmq.QueueManager represents an existing queue manager, the name of the CI must reflect the existing queue manager name. For example, if the existing queue manager running in the MQ environment is called
wmq.QueueManager CI must be called
wmq.QueueManager also supports control tasks for starting and stopping the queue manager.