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

Deploying resources

Deploy message flow applications to integration servers by sending a broker archive (BAR ) file to a broker, which unpacks and stores the contents ready for when your message flows are started.

Before you start:

Complete the following steps:

Create and start a broker. You must also start a WebSphere® MQ listener for the associated queue manager.
In the IBM® Integration Toolkit, you must connect to a broker, and create an integration server.
Create a BAR file that contains the resources that you want to deploy; see Packaging resources.

The mode in which your broker is working can affect the number of integration servers and message flows that you can deploy, and the types of node that you can use. See Restrictions that apply in each operation mode.

If you are working with one of the following resources and want to deploy and test it quickly, you can deploy just that resource:

A single application or library
A single message flow
A single subflow that is defined in a .subflow file

Drag the resource onto the integration server to which you want to deploy it. A BAR file is generated automatically, and deployed to the broker. If private libraries are referenced, they are added automatically to the BAR file and deployed. If you drag a message flow that contains a subflow that is defined in a .subflow file, the subflow is automatically included in the BAR file, and deployed with the message flow. If you drag a flow that is contained in an application or library, a message is shown that says that the whole application or library is deployed, because you cannot deploy a message flow on its own if it belongs to an application or library.

Deploying an application or library to an integration server results in a complete deployment of the application or library. If the application or library was deployed before, redeploying it removes the currently deployed application or library and its contents, and replaces it with the deployed application or library.

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. The mixing of cases in this way might cause errors with ESQL and subflow deployment. When the main .msgflow is complied into the CMF, it also in-lines all the related ESQL and subflows that are implemented in the .msgflow files. A potential risk is that the same ESQL code to be inlined into the CMF file is also deployed as source. So the two recommended deployment options are:

Deploy all the resources (for example .msgflow, .subflow, and .esql) as source. This deployment method would be used with applications and libraries because each deployed application and library would contain the same resources that you have on your workspace.
Deploy all the resources in the compiled form. This deployment method requires that all the subflows would be implemented in .msgflow files. As a result, all the flow, subflow, and ESQL code is in-lined into the parent CMF file. This method does not allow the same flexibility as the source deployment, but it does provide an unambiguous runtime behavior.

In most cases, you are working with one or more applications, libraries, message flows, and other objects that you want to deploy with the message flows. In these cases, you can deploy these resources together by packaging them in a BAR file yourself, and deploying just that file. For instructions about how to deploy a BAR file, see Deploying a broker archive file.

If you are deploying a message flow that uses WebSphere Adapters, see Deploying a message flow that uses WebSphere Adapters. To deploy by using the IBM Integration Explorer, see Importing a broker archive file to the IBM Integration Explorer.

If your message flows include user-defined nodes, you must also distribute the compiled C or Java™ code for each node to every broker that uses those message flows. For more information, see Developing user-defined extensions.

Windows platform If your message flows call .NET code from a .NETCompute node or from ESQL, you must distribute the assemblies to every broker that uses these message flows. For more information, see Deploying .NET assemblies.

af35100_.htm |

Last updated Friday, 21 July 2017