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. The broker added to the domain is actually a reference, so you must also create and start the physical broker on the target system. A WebSphere MQ listener must be running and you must also have created a domain, added a broker to that domain, and created an execution group within the broker. See the links to related tasks below for help with these.

Message flow applications are deployed 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 deployed to execution groups on individual brokers. The Message flow application deployment topic gives more details.

Viewing version and keyword information for deployable objects describes how to view version and keyword information about deployed objects.

Related concepts
Message flow application deployment
Related tasks
Deploying
Creating a Configuration Manager on Windows
Creating a domain connection
Adding a broker to a broker domain
Developing applications that use the Configuration Manager Proxy Java API
Using the Configuration Manager Proxy API to deploy
Changing Broker Administration preferences
Related reference
Broker Administration perspective
Broker Topology editor