The Configuration Manager Proxy
(CMP) is
an application programming interface that your applications can use to control
broker domains through a remote interface to the Configuration
Manager.
Your applications have complete access to the
Configuration
Manager functions
and resources through the set of Java classes that constitute the CMP. For
example, you can use the CMP to interact with the
Configuration
Manager to:
- Deploy BAR files, Publish/Subscribe topology, topic trees, and broker
configuration.
- Modify the Publish/Subscribe topology; add and remove brokers, broker
connections, and collectives.
- Create, modify, and delete execution groups
- Enquire and set status of objects in the domain (for example, run state),
and be informed if status changes.
- Manipulate the topics hierarchy.
- View the broker event log and active subscriptions table.
- Modify domain Access Control Lists, when connected to a Version 6.0 Configuration
Manager only.
The CMP is a set of Java classes that sit logically between the user application
and the
Configuration
Manager, inside the Java Virtual
Machine (JVM) of the user application. It requires the
WebSphere MQ Classes
for Java in order to function, as shown below.
The CMP application can be on the same physical machine as the Configuration
Manager,
connected by a JNI (Java Native Interface) connection to the queue manager
using the WebSphere MQ Java Bindings transport.
Alternatively, it can be distributed over a TCP/IP network, and connected
to the queue manager by a WebSphere MQ SVRCONN
channel using the WebSphere MQ Java Client transport.
You cannot use the CMP to communicate with more than one
Configuration
Manager from
within the same application:
Using the API, you can connect to and manipulate a
Configuration
Manager in
the following products:
- WebSphere Business Integration
Event Broker Version 5.0
- WebSphere Business Integration
Message Broker Version 5.0
- WebSphere Business Integration Message Broker with Rules and
Formatter Extension Version 5.0
- WebSphere Event Broker Version 6.0
- WebSphere Message Broker Version 6.0
A domain controlled by a Version 5.0 Configuration
Manager can
consist of Version 2.1 and Version 5.0 brokers, to which either version can
be deployed by the CMP. Although you can run only one Version 5.0 Configuration
Manager on
each physical machine, a single CMP application can still connect to multiple
Version 5.0 Configuration
Manager components.