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


Checking the results of deployment

After you deploy a BAR file, you can check that the operation completed successfully.

About this task

You can check the results of a deployment by using any of the following methods: Also, check the system log on the target system where the integration node was deployed to make sure that the integration node did not report any errors.

If version or custom keyword information was included in the resources, you can also check the version of the resources that are deployed to your integration server; see Viewing version information and custom keyword values in your deployed solutions.

Checking deployment by using the IBM Integration Toolkit

About this task

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

Procedure

  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 that relate to each deployment in the Deployment Log view.

Results

The Deployment Log is updated only after a deployment is processed completely by the integration node. If a deployment fails, the reasons for the failure are shown here.

Checking deployment by using the mqsideploy command

About this task

If you use the mqsideploy command to deploy, the command displays the results of the deployment. For example, if you type the following command:
mqsideploy IBNODE -e default -a my.bar
the following response indicates that the deployment was successful:
BIP1039I: Deploying BAR file 'my.bar' to integration node 'IBNODE' (integration
server 'default') ...
BIP1092I: The integration node successfully processed the deployment request.

The command 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.

Checking deployment by using the IBM Integration API

About this task

Code your application to test the results of the deployment actions that it takes. For example:
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 integration node responds 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 IBM Integration API.

If the deployment message could not be sent to the integration node, a ConfigManagerProxyLoggedException exception is thrown at the time of the deployment. If the integration node receives the deployment message, log messages for the overall deployment are displayed, followed by completion codes specific to each integration node that is affected by the deployment. The completion code that is 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 deployment message was sent to the integration node, but no response was received before the timeout period expired.
success The integration node successfully completed the deployment.
failure The integration node 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 a list of available LogEntry objects.

What to do next

You can administer your integration node, integration server, and deployed resources; see Administering integration nodes and associated resources.

af03970_.htm | Last updated 2015-11-26 23:59:49