Deploying a message flow application

Deploy message flow applications to execution groups by adding required resources, optionally with their source files, to a broker archive (BAR) file. Send the BAR file to a Configuration Manager, where it is unpacked and the individual files distributed to execution groups on individual brokers.

Before you start:

Before you can deploy a message flow application, you must have created and started a Configuration Manager. You must also start a WebSphere® MQ listener for the associated queue manager.

Within the workbench, you must create a domain, add a broker to that domain, and create an execution group within the broker. The broker that you add to the domain is a reference, therefore you must also create and start the physical broker on the target system, and start a WebSphere MQ listener on its queue manager. See the links to related tasks at the end of this topic for help with these actions.

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.

Related concepts
Message flow application deployment
Related tasks
Deploying
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:21:52

af35100_