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

Checking the results of deployment

After you have made a deployment, check that the operation has completed successfully.

You can check the results of a deployment in the following ways: Also, check the system log on the target system where the broker was deployed to make sure that the broker has not reported any errors.

Using the IBM Integration Toolkit

Follow these steps to check a deployment using the IBM® Integration Toolkit:

  1. In the Integration Development perspective, open the Deployment Log view:
    1. Click Window > Show View > Other.
    2. In the Show View window expand Integration Development, and click Deployment Log.
  2. View the messages relating to each deployment in the Deployment Log view.
The Deployment Log is only updated after a deployment has been completely processed by the broker. If a deployment fails, the reasons for the failure are shown here.

Using the IBM Integration Explorer

Follow these steps to check a deployment using the IBM Integration Explorer:

  1. Select the broker with which you want to work in the Navigator view.
  2. View the messages in the Administration Log view.
The Administration Log shows all recent configuration change attempts made to the broker and, where possible, the user that requested it.

Using the mqsideploy command

If you use the mqsideploy command to deploy, the command displays the results of the deployment. It also returns a numeric completion code value to indicate the outcome. If the deployment completes successfully, the command returns 0. For details of other values that you might see returned, see mqsideploy command.

Using the CMP

Code your application to test the results of the deploy actions that it takes. You can use code like the following snippet:
DeployResult dr = eg.deploy("MyBAR.bar", true, 30000);
System.out.println("Overall result = "+dr.getCompletionCode());

// Display log messages
Enumeration logEntries = dr.getLogEntries();
while (logEntries.hasMoreElements()) {
  LogEntry le = (LogEntry)logEntries.nextElement();
  System.out.println("General message: " + le.getDetail());
}

The deploy method blocks other processes until the broker has responded to the deployment request. When the method returns, the DeployResult object represents the outcome of the deployment at the time when the method returned; the object is not updated by the CMP.

If the deployment message could not be sent to the broker, a ConfigManagerProxyLoggedException exception is thrown at the time of the deployment. If the broker receives the deployment message, log messages for the overall deployment are displayed, followed by completion codes specific to each broker that is affected by the deployment. The completion code, shown in the following table, is one of the static instances from the CompletionCodeType class.

Completion code Description
pending The deployment is held in a batch and is not sent until you call BrokerProxy.sendUpdates().
submitted The deploy message was sent to the broker, but no response was received before the timeout period expired.
success The broker has successfully completed the deployment.
failure The broker has generated one or more errors during deployment. You can call the getLogEntries() method of the DeployResult class to get more information about the deployment failure. This method returns an enumeration of available LogEntry objects.

af03970_.htm | Last updated Friday, 21 July 2017