Use the mqsideploy command to make a deployment request to the Configuration Manager. This allows you to make the various flavors of deployment requests from a batch command script, without the need for manual interaction.
The default situation is a delta or incremental deployment. Select -m to override the default operation.
mqsideploy does not require a Configuration Manager name parameter because all of the required connection details can be obtained from the -n, -q, -i, and -p parameters.
<?xml version="1.0" encoding="UTF-8"?> <configmgr host="localhost" listenerPort="1414" queueManager="QNAME" securityExit="test.myExit"/>
<?xml version="1.0"?>and remove the value for the host attribute, to leave the statement as:
<configmgr host="" listenerPort="1414" queueManager="QNAME" securityExit="test.myExit"/>
If you are using this file on z/OS and want to connect to the local host you must set the value to "".
If you do not supply the -i, -p, and -q parameters, you must specify the -n parameter.
With the -c option deployment is cancelled to the specific broker.
On z/OS the BAR file must be in the file system. The BAR file can be anywhere as long as the user ID of the person or Configuration Manager running the command can access the file and read it.
The -c option must be specified with caution. Only use it if there is no possibility that the affected brokers will respond to the deployment request; if a broker subsequently processes a deployment request that had been cancelled, the Configuration Manager ignores the response, and therefore become out of synchronization with the broker.
Objects of all types can be specified, with the following limitation that, if an ambiguous object name is specified (for example "top", when both "top.dictionary" and "top.cmf" are deployed to the same execution group) the entire command fails with the message BIP1089. In these circumstances, the fully qualified name of the objects to remove must be specified, for example "top.dictionary:top.cmf".
In order to successfully deploy, the user ID issuing the command needs to have sufficient authority defined in the Configuration Manager. The permissions required are the same as the permission required to do the equivalent function in the Message Brokers Toolkit. See ACL permissions for a list of permissions that can be defined in the Configuration Manager.
mqsideploy -n cm1.configmgr -m -w 600
mqsideploy -i localhost -p 1414 -q QMNAME -m -w 600
Note that you can use the i, p, and q parameters in the following examples instead of the -n parameter.
mqsideploy -n cm1.configmgr -t -m -w 600
mqsideploy -n cm1.configmgr -b broker1 -e default -a mybar.bar -m -w 600
mqsideploy -n cm1.configmgr -b broker1 -w 900
Attempt to remove the message flow top and the dictionary bar from the execution group default on broker b1, using a connection file whose parameters are described in the file cm1.configmgr.
mqsideploy –n cm1.configmgr –b B1 –e default –d top.cmf:bar.dictionary
mqsideploy -n cm1.configmgr -c -w 900
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
an09020_ |