See information about the latest product version
Deployment methods
Choose the appropriate method of deployment to suit the way in which you are working. You can use the WebSphere® Message Broker Toolkit, the WebSphere Message Broker Explorer, the mqsideploy command, or functions described by the Message Broker API (also known as the CMP API).
- Using the WebSphere Message Broker Toolkit
- The Brokers view of the WebSphere Message Broker Toolkit displays all the brokers on
the local machine that you have defined, and any remote brokers to
which you have defined connections. If you expand a broker, all the
execution groups in that broker are displayed, as well as deployed
message flows and their associated resources. You can drag a message
flow or a broker archive (BAR) file from the Broker
Development view onto an execution group
to deploy it. Alternatively, you can right-click an execution group
to select a message flow or BAR file to deploy to the selected execution
group.
You would typically use the WebSphere Message Broker Toolkit if your primary role is as an application developer, or if you are new to WebSphere Message Broker.
- Using the WebSphere Message Broker Explorer
- The Navigator view of the WebSphere Message Broker Explorer displays
all the brokers on the local
machine that you have defined, and any remote brokers to which you
have defined connections. If you expand a broker, all the execution
groups in that broker are displayed, as well as deployed message flows
and their associated resources. You can import BAR files into the WebSphere Message Broker Explorer. The BAR files are displayed
in the Broker Archive Files folder in the WebSphere Message Broker Explorer. You can drag a BAR file from
the Broker Archive Files folder onto an execution group to deploy
the contents of the broker archive. Alternatively, you can right-click
an execution group or BAR file and click Deploy File to
deploy resources to an execution group. You can also drag BAR files
from your file system directly onto an execution group to deploy the
contents of the broker archive.
You would typically use the WebSphere Message Broker Explorer if your primary role is as a WebSphere Message Broker administrator.
- Using the mqsideploy command
- You can deploy from the command line by using the mqsideploy command. On the
command line, specify the connection details and parameters that are
specific to the deployment.
You would typically use the mqsideploy command in a script when you are more familiar with WebSphere Message Broker.
- Using the CMP API
- You can control deployment from a Java™ program
by using functions described by the CMP API.
You can also interrogate the responses from the broker and take appropriate
action.
Java applications can also use the CMP API to control other objects, such as brokers and execution groups. Therefore, you can use the CMP API to create and manipulate all your brokers and associated resources programmatically.
- Deployment results
- Whichever deployment method you use, configuration changes are
attempted immediately.
- If you are using the WebSphere Message Broker Toolkit, the Deployment Log view is updated to show the results when your deployment completes. If the deployment fails, the reason for the failure is displayed in this view.
- If you are using the WebSphere Message Broker Explorer, you can see the deployment status for all users connected to the broker. The Administration Queue shows all deployments that are currently being processed by the broker, and the Administration Log shows all recent configuration requests and changes made to the broker.
- If you use the mqsideploy command, the command completes when the broker has processed the deployment request, or when the wait time, defined by the -w parameter, has expired, whichever occurs first. The results of the deployment are displayed as output from the command.
- If you are using the CMP API,
you can view the results of the deployment in the following ways:
- Review the DeployResult object that is returned from the deployment methods.
- Access the LogProxy object that represents the administration log.
- Access the AdminQueueProxy object that represents the administration queue.