This article discusses a legacy implementation of JMS messaging that should not be used for new implementations. This legacy implementation may be removed in future releases. Instead see Common Messaging APIs.
The Java Messaging Service (JMS) is a Java messaging framework for providing communication between two or more systems. In this framework, a JMS provider manages a queue of messages sent by JMS clients. A typical JMS message has the following path:
A JMS client sends the message to a JMS provider.
The JMS provider sends the message to another JMS client.
With interoperability productions, InterSystems products can be a JMS client that both sends and receives JMS messages. InterSystems JMS clients use the EnsLib.JMS.Operation business host to send messages to JMS providers and the EnsLib.JMS.Service business host to receive messages from JMS providers. Advanced users who are familiar with ObjectScript can create their own custom JMS business hosts rather than using these built-in components.
Internally, JMS business hosts leverage an InterSystems external server to connect to Java.
Within the JMS client’s interoperability production, the JMS messages are EnsLib.JMS.MessageOpens in a new tab objects. The text property of message object contains the message content. The type property of the message object specifies the message type such as TextMessage and BytesMessage. The EnsLib.JMS.Message class also provides methods for setting and retrieving properties of the message.
The jar file for the JMS feature is available at: install-dir\dev\java\lib\JDK18\intersystems-enslib-jms-3.0.0.jar
The following client development jar files are also available: