Choose the appropriate method of deployment according to the way in which you are working. You can use the workbench, the mqsideploy command, or functions described by the Configuration Manager Proxy (CMP) API.
You might typically use the workbench if you are working in a development environment or if you are new to WebSphere® Message Broker.
You might typically use the mqsideploy command in a script when you are more familiar with WebSphere Message Broker.
WebSphere Message Broker provides two files to help you when writing your own scripts that invoke the mqsideploy command:
hostname = localhost queueManager = QMNAME port = 1414 securityExit = test.myExitInformation that you do not explicitly specify as parameters on the mqsideploy command (as shown in the examples in subsequent topics), is taken from the mqsicfgutil.ini file.
Alternatively, use the -n parameter on the command to specify an XML-format .configmgr file that describes the connection parameters to the Configuration Manager.
Java applications can also use the CMP to control other objects in the domain, such as brokers, execution groups, publish/subscribe topologies, topics, subscriptions, and the Configuration Manager and its event log. This means that you can use the CMP to create and manipulate an entire domain programmatically.
A deployment request always completes, either because the broker has sent a response or the timeout has expired. If you have reason to believe that the deployment might not be successful, for example if you become aware that a problem with the network or the broker might prevent its completion, you can cancel the deployment request. Use this only in exceptional circumstances; cancelation might cause the state of the execution groups to become unpredictable.
When the request is received by the broker, it communicates with the execution groups that are affected by the contents of the deployment request. The broker waits for a certain amount of time, during which it expects the execution groups to complete the work. If the execution groups do not indicate that they have finished before the time has expired, the broker sends back a negative response with message BIP2066.