After you deploy a BAR file, you can check that the operation completed successfully.
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.
Follow these steps to check a deployment by using the IBM® Integration Toolkit:
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.
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. |