Including WebSphere Adapters resources in a BAR file

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

Before you begin

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.

Procedure

  1. For details of the steps that you must complete before you can deploy a message flow, see Deployment rules and guidelines.
  2. Add the message flow to the BAR file.
    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
  3. When you have added the message flow, WebSphere Adapters components, and library, deploy the BAR file.