Deployment is the process of transferring data to an execution group on a broker so that it can take effect in the broker domain. For deploying message flows and associated resources, the data is packaged in a broker archive (bar) file before being sent to the Configuration Manager, from where it is unpackaged and distributed appropriately.
This topic describes the three environments from which you can perform a deployment.
After reading this conceptual overview, find detailed instructions for particular tasks in the subsequent topics.
You can read a further discussion about deployment in the IBM Redbook, WebSphere Message Broker Basics.
Depending on the environment in which you are working, you can generally choose one of three different ways to initiate a deployment:
In the Broker Administration perspective of the workbench, 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 broker archive (bar) file from the Resource Navigator view onto an execution group within the Domain Navigator view to deploy the contents of the bar.
You might typically use the workbench if you are working in a development environment or if you are new to WebSphere Business Integration Message Broker.
You can deploy from the command line using the mqsideploy command. On the command line, you must typically specify the connection details as well as parameters specific to the type of deployment you want to perform. Details are given in each topic describing the types of deployment.
You might typically use the mqsideploy command in a script when you are more familiar with WebSphere Business Integration Message Broker.
You can control deployment from any Java program using the Configuration Manager Proxy API. You can also interrogate the responses from the broker and take appropriate action.
The Configuration Manager Proxy API also allows Java applications to control other objects in the domain, such as brokers, execution groups, publish/subscribe topologies, topics, subscriptions and the Configuration Manager and its event log. Because of this, you can use the Configuration Manager Proxy API to create and manipulate an entire domain programmatically.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
af01280_ |