WebSphere Message Brokers
File: an09020_
Writer: Bill Oppenheimer

Reference topic

This build: July 31, 2007 21:33:38

mqsideploy command

Supported platforms

Purpose

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 operation 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.

Select the appropriate link for details of this command on the platform, or platforms, that your enterprise uses:

Authorization

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 Broker Toolkit. See ACL permissions for a list of permissions that can be defined in the Configuration Manager.

Responses

This command returns the following responses:
0
(Success) States that the Configuration Manager issued the deployment request and all relevant brokers responded successfully before the timeout period expired.
2
(Failure) States that the Configuration Manager issued the deployment request and at least one broker responded negatively. See the messages output from the utility (or the Configuration Manager's event log) for more information.
3
(Initiated) States that the Configuration Manager has replied, stating that deployment has started, but that no broker responses were received before the timeout occurred.
5
(Submitted) States that the deploy message was sent to the Configuration Manager , but that no response was received before the timeout occurred.
6
(SuccessSoFar) States that the Configuration Manager issued the deployment request and some, but not all of, the relevant brokers responded successfully before the timeout period expired; no brokers responded negatively.
98
States that the Configuration Manager cannot be reached.
99
States that the supplied arguments to the utility are not valid.
Related concepts
Runtime environment
Related tasks
Deploying
Related reference
ACL permissions
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:33:38

an09020_ This topic's URL is: