IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Deployment methods

Choose the appropriate method of deployment to suit the way in which you are working. You can use the IBM® Integration Toolkit, the IBM Integration Explorer, the mqsideploy command, or functions described by the IBM Integration API (also known as the CMP).

Using the IBM Integration Toolkit

The Integration Nodes view of the IBM Integration Toolkit displays all the brokers on the local machine that you have defined, and any remote brokers to which you have defined connections. If you expand a broker, all the integration servers in that broker are displayed, as well as deployed message flows and their associated resources. You can drag a message flow or a broker archive (BAR) file from the Application Development view onto an integration server to deploy it. Alternatively, you can right-click an integration server to select a message flow or BAR file to deploy to the selected integration server.

You would typically use the IBM Integration Toolkit if your primary role is as an application developer, or if you are new to IBM Integration Bus.

Using the IBM Integration Explorer

The Navigator view of the IBM Integration Explorer displays all the integration nodes (brokers) on the local machine that you have defined, and any remote brokers to which you have defined connections. If you expand a broker, all the integration servers in that broker are displayed, as well as deployed message flows and their associated resources. You can import BAR files into the IBM Integration Explorer. The BAR files are displayed in the Broker Archive Files folder in the IBM Integration Explorer. You can drag a BAR file from the Broker Archive Files folder onto an integration server to deploy the contents of the broker archive. Alternatively, you can right-click an integration server or BAR file and click Deploy File to deploy resources to an integration server. You can also drag BAR files from your file system directly onto an integration server to deploy the contents of the broker archive.

You would typically use the IBM Integration Explorer if your primary role is as an IBM Integration Bus administrator.

Using the mqsideploy command

You can deploy from the command line by using the mqsideploy command. On the command line, specify the connection details and parameters that are specific to the deployment.

You would typically use the mqsideploy command in a script when you are more familiar with IBM Integration Bus.

Using the CMP

You can control deployment from a Java™ program by using functions described by the CMP. You can also interrogate the responses from the broker and take appropriate action.

Java applications can also use the CMP to control other objects, such as brokers and integration servers. Therefore, you can use the CMP to create and manipulate all your brokers and associated resources programmatically.

Deployment results

Whichever deployment method you use, configuration changes are attempted immediately.

If you are using the IBM Integration Toolkit, the Deployment Log view is updated to show the results when your deployment completes. If the deployment fails, the reason for the failure is displayed in this view.
If you are using the IBM Integration Explorer, you can see the deployment status for all users connected to the broker. The Administration Queue shows all deployments that are currently being processed by the broker, and the Administration Log shows all recent configuration requests and changes made to the broker.
If you use the mqsideploy command, the command completes when the broker has processed the deployment request, or when the wait time, defined by the -w parameter, has expired, whichever occurs first. The results of the deployment are displayed as output from the command.
If you are using the CMP, you can view the results of the deployment in the following ways:
- Review the DeployResult object that is returned from the deployment methods.
- Access the LogProxy object that represents the administration log.
- Access the AdminQueueProxy object that represents the administration queue.

af01282_.htm |

Last updated Friday, 21 July 2017