WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Packaging and 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. 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 WebSphere® Message Broker Toolkit, you must distribute them to the brokers on which you want them to run. Data for message flows and associated resources is packaged in a broker archive (BAR) file before being sent to the broker.

You can package and deploy message flows and associated resources in one step by using the WebSphere Message Broker Toolkit. You can use this approach when you are developing your flows to make changes and quickly see the results. When you want to deploy to a production environment, you can separate the packaging and deployment steps by first packaging your resources into a BAR file and then deploying that file at a later time. You can create BAR files in the following ways:
  • By using the WebSphere Message Broker Toolkit
  • By using the mqsipackagebar command
  • By using the mqsicreatebar command
For more information about packaging resources, see Packaging resources.

After you create a BAR file, you can customize the file for deployment to different brokers; for example, to specify queue names or data source names. For more information about customizing your BAR file, see Configurable properties of a broker archive.

After creating a BAR file and customizing it, you can deploy the BAR file in the following ways:
  • From the WebSphere Message Broker Toolkit
  • From the WebSphere Message Broker Explorer
  • By using the mqsideploy command
  • By using functions defined by the Message Broker API (also known as the CMP API)
Depending on your work patterns, you might use all these methods at different times. These options are described in Deployment methods.

Try to avoid a mixed deployment case that has message flows deployed as CMF and subflows (.subflow) deployed as source files, along with the ESQL modules that are referenced by these subflows. For more information about this behavior, and examples of the recommended deployment options, see Deploying resources.

After you read these overview topics, find detailed instructions for the tasks that you want to complete in subsequent topics in this section.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:01


Concept topicConcept topic | Version 8.0.0.7 | af01280_