See information about the latest product version
Deploying resources
Deploy message flow applications to execution groups by sending a broker archive (BAR) file to a broker, which unpacks and stores the contents ready for when your message flows are started.
Before you start:
Complete the following steps:- Create and start a broker. You must also start a WebSphere® MQ listener for the associated queue manager.
- In the WebSphere Message Broker Toolkit, you must connect to a broker, and create an execution group.
- Create a BAR file that contains the resources that you want to deploy; see Packaging resources.
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.
- A single application or library
- A single message flow
- A single subflow that is defined in a .subflow file
Deploying an application or library to an execution group 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.
- Deploy all the resources (for example .msgflow, .subflow, and .esql) as source. This deployment method would be used with applications and libraries because each deployed application and library would contain the same resources that you have on your workspace.
- Deploy all the resources in the compiled form. This deployment method requires that all the subflows would be implemented in .msgflow files. As a result, all the flow, subflow, and ESQL code is in-lined into the parent CMF file. This method does not allow the same flexibility as the source deployment, but it does provide an unambiguous runtime behavior.
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 a BAR file yourself, and deploying just that file. For instructions about how to deploy a BAR file, see Deploying a broker archive file.
If you are deploying a message flow that uses WebSphere Adapters, see Deploying a message flow that uses WebSphere Adapters. To deploy by using the WebSphere Message Broker Explorer, see Importing a broker archive file to the WebSphere Message Broker Explorer.
If your message flows include user-defined nodes, you must also distribute the compiled C or Java™ code for each node to every broker that uses those message flows. For more details, 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 broker that uses these
message flows. For more details, see Deploying .NET assemblies.