About this task
To deploy the message flow successfully, you must deploy
the WebSphere Adapters
component in the same application, static library, or
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)
- Optional: .appzip (an application)
- Optional: .libzip (a static library)
- Optional: .shlibzip (a shared library)
For more information, see WebSphere Adapters resources.
The mode in which
your integration node 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.