WebSphere Message Brokers
File: af35100_
Writer: John Morris-Smith

Task topic

This build: July 31, 2007 21:29:26

Deploying a message flow application

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, so 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 below for help with these actions.

You deploy message flow applications to execution groups by adding required resources, optionally with their source files, to a broker archive (bar) file. The bar file is then sent to the appropriate Configuration Manager, where it is unpacked and the individual files are deployed to execution groups on individual brokers. For more details, see the Message flow application deployment topic.

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 the section about developing user-defined extensions.

Related concepts
Message flow application deployment
Related tasks
Deploying
Creating a Configuration Manager
Creating a broker
Creating a domain connection
Adding a broker to a broker domain
Related reference
Broker Administration perspective
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:29:26

af35100_ This topic's URL is: