Before you start:
Before you can deploy a configuration, you must have created a Configuration Manager and started the 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 the related tasks below for help with these.
The Configuration Manager cannot handle simultaneous deploy requests. If you make a change to your configuration within the broker topology that requires a broker topology configuration deploy and a broker configuration deploy, only the broker configuration deploy is sent to the Configuration Manager. A warning message is displayed, explaining that the broker topology configuration could not be sent.
To deploy a message flow application, you have to create a package of deployable resources, optionally with their source files. The LIL file for a plugin node must be deployed to every broker machine that uses that node in a message flow. On deployment, the bar file is sent through the Configuration Manager to a broker.
This section contains the following topics:
Related concepts
Message flow application deployment
Related tasks
Creating a Configuration Manager
Creating a domain connection
Adding a broker to a broker domain
Using rapid application development (RAD)
Setting up broker domain security
Starting the WebSphere MQ channels and listeners
Adding an execution group to a broker
Related reference
Broker Administration perspective
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
af03860_ |