IBM Integration Bus, Version 10.0.0.0 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


Packaging and deploying

Deployment is the process of transferring the development resources for an integration solution to the runtime environment. The development resources are deployed to an integration server on an integration node. To deploy an integration solution to a production environment, you can package your development resources into a single file for transfer to the production environment.

About this task

To develop an integration solution, you might need to create a number of resources such as message flows, subflows, message models, maps, Java™ code, and ESQL files.

You can store your development resources in applications or libraries. If some of your resources are used by multiple applications, you can store those resources in a static library or a shared library. To understand the difference between static libraries and shared libraries, see Libraries. You can then deploy resources by deploying the applications and libraries.
Note: If you are using shared libraries, you must deploy them before you deploy the applications that rely on them.
When you want to deploy your solution to a production environment, you can package the resources into a BAR file. You can add applications and libraries to the BAR file. If your solution contains message flows or other resources that are in an integration project, you can add these resources individually to the BAR file.
Note: You cannot add an integration project to a BAR file.
For more information, see Packaging resources.

Before you deploy your solution to a production environment, you can customize the BAR file to configure the solution for any differences between the development environment and the production environment. For example, you might specify different data source names or queue names; see Editing configurable properties.

You can also use operational policies to control certain aspects of message flow and message flow node behavior at run time. For more information, see Operational policy.

When your BAR file is configured, and any operational policies are defined, you can deploy your BAR file to a production environment; see Deploying solutions.


af03860_.htm | Last updated 2015-03-27 19:26:42