Use the mqsideploy command to make a deploy request to the Configuration Manager. This allows you to make the various flavors of deploy requests from a batch command script, without the need for manual interaction.
The default situation is a delta or incremental deploy. Select -complete to override the default operation.
The return code from mqsideploy is zero if the command succeeds. If the command fails, the return code is theBIP message number that describes the failure, minus 1000 for messages in the format BIP1xxx; or minus 8000, for messages in the format BIP8xxx. For example, if the command fails with the message BIP1034, the return code is 34.
<?xml version="1.0" encoding="UTF-8"?> <configmgr host="localhost" listenerPort="1414" queueManager="LUCAS" securityExit="test.myExit"/>
hostname = localhost queueManager = QMNAME port = 1414 securityExit = test.myExit
Specifying the -connection option causes the mqsicfgutil.ini file to be ignored.
These files need to be in the directory from which the command is being run. This is not necessarily the same directory as the mqsideploy.bat file.
Perform a deploy to broker <broker_name> and wait five minutes for a reply:
mqsideploy -b <broker_name> -w 300
Read any replies (log messages) received from brokers that have previously been deployed to:
mqsideploy -r
Related concepts
Runtime environment
Related tasks
Deploying message flow applications
Related reference
Syntax preference
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
an09020_ |