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


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 mqsideploy command, or functions that are described by the IBM Integration API.

Deploying with the IBM Integration Toolkit
The Integration Nodes view of the IBM Integration Toolkit displays all the integration nodes on the local machine that you have defined, and any remote integration nodes to which you have defined connections. If you expand an integration node, all the integration servers in that integration node are displayed, as well as deployed resources. You can drag the following resources from the Application Development view onto an integration server to deploy them.
  • If a message flow is contained in an application, drag the application onto an integration server.
  • If a message flow is contained in a static library, drag that library onto an integration server. (You cannot store a message flow in a shared library.)
  • If a message flow is contained in an integration project, drag the message flow onto an integration server.
  • If your resources are packaged in a BAR file, drag the BAR file onto an integration server.
Alternatively, you can right-click an integration server and click Deploy to select an application, library, message flow, or BAR file to deploy to that 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.

Deploying with 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.

Deploying with the IBM Integration API
You can control deployment from a Java™ program by using functions that are described by the IBM Integration API. You can also interrogate the responses from the integration node and take appropriate action.

Java applications can also use the IBM Integration API to control other objects, such as integration nodes and integration servers. Therefore, you can use the IBM Integration API to create and manipulate all your integration nodes 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 use the mqsideploy command, the command completes when the integration node 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 IBM Integration API, 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 2015-05-28 20:51:07