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 a message flow that uses WebSphere Adapters

Deploy the resources that are generated when you run the Adapter Connection wizard by adding them to a broker archive (BAR) file.

Before you start:

Read WebSphere Adapters nodes.
Complete the steps in Preparing the environment for WebSphere Adapters nodes
Complete the steps in Connecting to an EIS by using the Adapter Connection wizard.

To deploy the message flow successfully, you must deploy the WebSphere Adapters component, either on its own or in the same BAR file as your message flow. If the WebSphere Adapters component is not available, deployment of the message flow fails. The following list includes the file extensions of the resources that you deploy:

.msgflow (the message flow)
.inadapter (the inbound WebSphere Adapters component)
.outadapter (the outbound WebSphere Adapters component)
.libzip (the library)

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.

For details of the steps that you must complete before you can deploy a message flow, see Deploying resources.
Add the message flow to the BAR file. (For a description of how to add files to a BAR file, see Adding files to a broker archive.) When you add a message flow that contains one or more WebSphere Adapters nodes to a BAR file, a dialog box opens so that you can identify the following resources:
- One or more WebSphere Adapters components to be used by the WebSphere Adapters nodes
- One or more libraries that contain an XSD for the business objects that are used by the WebSphere Adapters nodes
When you have added the message flow, WebSphere Adapters components, and library, deploy the BAR file.

ac37250_.htm |

Last updated Friday, 21 July 2017