JMS Bindings

JMS bindings integrate JMS applications with TIBCO ActiveMatrix. The JMS bindings convert JMS messages to TIBCO ActiveMatrix messages and TIBCO ActiveMatrix messages to JMS messages.

Java Message Service (JMS) is a Java specification for messaging between applications. JMS is based on the creation and delivery of messages. The creator of the message is known as the publisher and the receiver of the message is known as the subscriber. A JMS server acts as an intermediary for the message and manages its delivery to the correct destination.

Configuration Overview

JMS bindings enable you to establish request and response message communication with a JMS server. In other words, adding a JMS binding enables a particular application to receive JMS messages or to send messages to the JMS server (JMS destination).

For an application to receive messages, for example, it must subscribe to a JMS server on a destination, which is defined by the JMS Connection Factory, JMS Destination, and JNDI Connection resources.

For the application to send messages, configuration details must be provided for the runtime library through the JMS Connection Factory, JMS Destination, and JNDI Connection configuration resources.

Use Cases

TIBCO ActiveMatrix supports the following JMS use cases and corresponding Message Exchange Pattern (MEPs):

• Service binding - You can create a service referencing port types of a component hosted inside TIBCO ActiveMatrix. The component hosted inside TIBCO ActiveMatrix dictates the WSDL file and provides services.

  • TIBCO ActiveMatrix subscriber communicating with a JMS publisher - In-Only

  • TIBCO ActiveMatrix server communicating with a JMS requestor - In-Out