IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

The IBM Integration API

The IBM® Integration API is a programming interface that your applications can use to control brokers and their resources through a remote interface.

The IBM Integration API is also known as the Configuration Manager Proxy, or CMP

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 have been retained, and are used in this information center to refer to the IBM Integration API, for continuity and consistency with the JAR file ConfigManagerProxy.jar that supplies all the classes.

The IBM Integration API (CMP) consists solely of a Java™ implementation, and is sometimes referred to as the IBM Integration Bus Java API. Your applications have complete access to the broker functions and resources through the set of Java classes that constitute the IBM Integration API. Use the IBM Integration API to interact with the broker to perform the following tasks:

Deploy BAR files
Change the broker configuration properties
Create, modify, and delete integration servers
Inquire and set the status of the broker and its associated resources, and to be informed if status changes
- Integration servers
- 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.

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 diagram is described in the surrounding text.

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 IBM Integration API to communicate with more than one broker from within the same application, as shown in the following diagram.

Migrating from earlier versions of IBM Integration Bus

For information about migrating your CMP applications to Version 9.0, see Migrating CMP applications.

be43410_.htm |

Last updated Friday, 21 July 2017