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.