WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Checking the results of broker management in a CMP application
When you have made a change to the broker, use one of the supplied methods to check if the change has been successful.
Choose one of three methods in the CMP API to determine the outcome of
requests to create, delete, modify, and deploy resources:
- If you have initiated a deployment method, you can use the return code from the deployment API; this technique is shown in Checking the results of deployment in a CMP application.
- You can query an object's most recent completion code; this option is shown in Checking the results of broker management with the most recent completion code in a CMP application.
- You can use the administered object notification mechanism; by using this approach, you can code specific routines to handle the responses and take appropriate action, and improve the efficiency of your program. See Checking the results of broker management with object notification in a CMP application.
- If you prefer to make property changes synchronously, call the
method BrokerProxy.setSynchronous() before making
your changes.
If subsequent property change methods give a successful return, the request has been successfully completed by the broker. If the changes are rejected by the broker, or time out (they cannot be completed successfully by the broker before the timeout period expires), the methods throw either a ConfigManagerProxyRequestFailure or a ConfigManagerProxyRequestTimeout exception.
For more information on synchronous property changes, see the description of the BrokerProxy.setSynchronous() method in the CMP API Javadoc information.