See information about the latest product version
The Message Broker API
The Message Broker API is a programming interface that your applications can use to control brokers and their resources through a remote interface.
The Message Broker API is also known as the Configuration Manager Proxy, or CMP API
The Configuration Manager has been removed from Version 7.0, and the full name of the API has changed. However, the terms CMP application and CMP API have been retained, and are used in this information center to refer to the Message Broker API, for continuity and consistency with the JAR file ConfigManagerProxy.jar that supplies all the classes.
The Message Broker API (CMP API) consists solely of a Java™ implementation, and is referred to as the WebSphere® Message Broker Java API. Your applications have complete access to the broker functions and resources through the set of Java classes that constitute the CMP. Use the CMP API to interact with the broker to perform the following tasks:
- Deploy BAR files
- Change the broker configuration properties
- Create, modify, and delete execution groups
- Inquire and set the status of the broker and its associated resources,
and to be informed if status changes
- Execution groups
- Deployed message flows
- Deployed files used by the message flows (for example, JAR files)
- View the Administration log
- View the Activity log
- Create and modify message flow applications. For more information, see Developing message flow applications by using the Message Broker Java API.
Interaction between CMP applications and the broker
For applications that interact with the broker, the Java classes sit logically between the user application and the broker, inside the Java Virtual Machine (JVM) of the user application. The API requires the WebSphere MQ Classes for Java for connectivity, as shown in the following diagram.

The CMP application can be on the same physical computer as the broker, connected by a JNI (Java Native Interface) connection to the queue manager that uses the WebSphere MQ Java Bindings transport. If appropriate, you can distribute your applications over an Internet Protocol (TCP/IP) network, and connected to the broker by using a WebSphere MQ SVRCONN channel through the WebSphere MQ Java Client transport.
You can use the CMP API to communicate with more than one broker from within the same application, as shown in the following diagram.

Migrating from earlier versions of WebSphere Message Broker
For information about migrating your CMP applications to Version 8.0, see Migrating Message Broker API applications.