Message flow application deployment

You must deploy configuration data before it can take effect in the broker domain and be used. This section describes the following:

The following figure shows the flow of events during a deployment. The details of this process are discussed in the sections in this topic.


This diagram illustrates graphically the flow of events that constitute the deployment process.

Deployment from the Domain Navigator view

The Domain Navigator view displays all the objects associated with a specific domain. For example, if you expand the Topology view, all the brokers in the domain are displayed; if you expand a Broker view, all the execution groups within that broker are displayed. From the Domain Navigator view you can deploy a topology to all the brokers in the domain, or you can deploy all the execution groups to a particular broker. You can also drag a bar file from the Resource Navigator view onto an execution group within the Domain Navigator view to deploy the contents of the bar file.

When deploying in WebSphere Business Integration Event Broker, only topic information, topology information, and message flow, message set, and broker properties information can be deployed. You cannot deploy everything, or force a complete deploy. This is useful for users who want to write scripts to manage broker deployment separately from the workbench domain development using the Message Brokers Toolkit for WebSphere Studio.

Command line facilities

You can deploy a configuration from the command line using the mqsideploy command. You must specify the name of the broker, the execution group to which you want your configuration to be deployed, and the name of the bar file that contains your message flow. For example:

mqsideploy -b mybroker -e myexecutiongroup -bar mybarfile.bar 
WebSphere Business Integration Event Broker also provides two additional files to help you when writing your own scripts for managing broker deployment outside the workbench. These are:
  • Initialization file mqsicfgutil.ini. This is a plain text file that contains any configurable variables needed to connect to the Configuration Manager. The variables must include:
    • hostname
    • queueManager
    • port
    • SecurityExit
  • Batch file mqsideploy.bat. This file calls the underlying Java program for the deploy utility.

Related tasks
Deploying message flow applications
Creating a Configuration Manager
Creating a domain connection
Adding a broker to a broker domain
Using rapid application development (RAD)

Related reference
mqsideploy command