The Java Message Service (JMS) adapter enables you to connect messaging systems to the Integration Engine or the PCK. The adapter supports the JMS specification 1.02b and 1.1. You can use the JMS adapter to send or receive an asynchronous message to a listed queue or topic on the JMS server.
The JMS adapter belongs to the com.realops.adapter.jms Java package and consists of a JMS actor adapter and a JMS monitor adapter.
The JMS adapter can use the following base adapter features. For details about these features, see Base adapter features.
Before you begin
In the directory service designated for Java Naming and Directory Interface (JNDI) lookup, create administered objects at the JMS provider (JMS interface) for the following entities:
- ConnectionFactory: an object that a client computer uses to create a connection to the JMS provider
- Queues: a staging area that contains messages
- Topics: a mechanism for publishing messages
Review the JMS provider documentation to obtain a list of all the JAR files that are necessary for a Java client. Copy all the specified JAR files to the $AO_HOME\lib\add-ons directory on the CDP server and all the peers that call the JMS adapter.
If you are using IBM WebSphere MQ or TIBCO application, you must copy the JAR files to the BMC Atrium Orchestrator peers on which the JMS monitor and actor adapters are enabled. For more information, seePrerequisites for the JMS adapter.
Verify that the JAR file of the JNDI service provider to be used is located in the $AO_HOME\lib\add-ons directory on the CDP server and all the peers that call the JMS adapter. Java J2SE 1.6 (SDK) and later include the following service providers:
- Lightweight Directory Access Protocol (LDAP)
- Common Object Services (COS) Naming
- Remote Method Invocation (RMI) Registry
- Domain Name System (DNS)
Verify the JNDI properties required to perform a name lookup using the service provider. These properties are defined in the configuration node.