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
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 execution groups and message flows that you can deploy, and the types of node that you can use. See Restrictions that apply in each operation mode.