Before you start
Before starting this step, you must have completed Configuring an environment for developing and running Configuration Manager Proxy applications.
import com.ibm.broker.config.proxy.*; public class ConfigManagerRunStateChecker { public static void main(String[] args) { displayConfigManagerRunState("localhost", 1414, ""); } public static void displayConfigManagerRunState(String hostname, int port, String qmgr) { ConfigManagerProxy cmp = null; try { ConfigManagerConnectionParameters cmcp = new MQConfigManagerConnectionParameters(hostname, port, qmgr); cmp = ConfigManagerProxy.getInstance(cmcp); String configManagerName = cmp.getName(); System.out.println("Configuration Manager ‘"+configManagerName+ "’ is available!"); cmp.disconnect(); } catch (ConfigManagerProxyException ex) { System.out.println("Configuration Manager is NOT available"+ " because "+ex); } } }
The first line of the program requests Java to import the CMP classes. All CMP classes are in the com.ibm.broker.config.proxy package.
The first line inside the try block of the displayConfigManagerRunState() method instantiates a ConfigManagerConnectionParameters object. This is an interface which states that implementing classes are able to provide the parameters to connect to a Configuration Manager.
This means that if the Configuration Manager is not running, the application hangs for a period. It is possible to control the timeout period by using the ConfigManagerProxy.setRetryCharacteristics() method. Generally, however, blocking only occurs when a given resource is accessed for the first time within an application.