IBM Integration Bus, Version 9.0.0.8 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 integration server 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 IBM® Integration 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 they are sent to the broker.

You can package and deploy message flows and associated resources in one step by using the IBM Integration 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 later. You can create BAR files in the following ways:

By using the IBM Integration 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 you create a BAR file and customize it, you can deploy the BAR file in the following ways:

From the IBM Integration Toolkit
From the IBM Integration Explorer
By using the mqsideploy command
By using functions that are defined by the IBM Integration API (also known as the CMP)

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 the following topics:

af01280_.htm |

Last updated Friday, 21 July 2017