Deployment overview

Deployment is the process of transferring data to an execution group on a broker so that it can take effect in the broker domain. Message flows and associated resources are packaged in broker archive (BAR) files for deployment.

When you create application resources such as message flows in the workbench, you must distribute them to the brokers on which you want them to run. Associated with the resources that you create is the configuration associated with those brokers in your broker domain. Data for message flows and associated resources is packaged in a broker archive (BAR) file before being sent to the Configuration Manager, from where it is unpackaged and distributed appropriately.

You can initiate a deployment in one of three ways: Depending on your work patterns, you might make use of all three methods at different times. These three options are described in Deployment methods.

You can also perform different types of deployment, depending on whether you are working with new resources, or updating existing ones. Most types of deployment can typically be configured in one of two ways:

See Types of deployment for further information about full and delta deployment.

When you have read these overview topics, find detailed instructions for the tasks that you want to complete in the subsequent topics.

Read the IBM® Redbooks® publication WebSphere Message Broker Basics for further information about deployment.

Related tasks
Deploying
Using the Configuration Manager Proxy API to deploy
Related reference
Workbench
Broker Administration perspective
mqsideploy command
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:40:21

af01280_