Deploy solutions to integration servers by sending a BAR file to an integration node, which unpacks and stores the contents ready for when your message flows are started.
Complete the following steps:
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.
If you drag a flow that is contained in an application or static library, a message is shown that says that the whole application or library will be deployed, because you cannot deploy a message flow on its own if it belongs to an application or static library. You cannot store a message flow in a shared library.
Deploying an application or library to an integration server results in a complete deployment of the application or library. If the application or library has been deployed before, redeploying it removes the currently deployed application or library and its contents, and replaces it with the deployed application or library.
In most cases, you are working with one or more applications, libraries, message flows, and other objects that you want to deploy with the message flows. In these cases, you can deploy these resources together by packaging them in BAR files yourself, and deploying the BAR files. For instructions about how to deploy a BAR file, see Deploying an integration solution.
If you are deploying a message flow that uses one or more Mapping nodes, see Deploying message maps.
If you are deploying a message flow that uses WebSphere® Adapters, see Deploying a message flow that uses WebSphere Adapters.
If your message flows include user-defined nodes, you must also distribute the compiled C or Java™ code for each node to every integration node that uses those message flows. For more information, see Developing user-defined extensions.
If your
message flows call .NET code from a .NETCompute node or from ESQL,
you must distribute the assemblies to every integration node that
uses these message flows. For more information, see Deploying .NET assemblies.