Using JMS Business Services and Operations (Legacy Implementation)
This page 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, use the JMSPEX interoperability adapters (inbound and outbound) which InterSystems has implemented using the PEX framework. Alternatively, use the JMS Messaging API.
To enable an InterSystems production to receive JMS messages, add a new business service, specifying the service class of this business service as EnsLib.JMS.ServiceOpens in a new tab. This business service ignores any response.
To enable an InterSystems production to send JMS messages, add a new business operation, specifying the operation class of this business operation as EnsLib.JMS.OperationOpens in a new tab. This business operation returns an instance of EnsLib.JMS.ResponseOpens in a new tab the business host that sent the JMS message to the business operation.
Once you have added these business hosts to the production, configure the following settings on the Settings tab:
-
JMSCredentials—The credential defined for the username and password of the JMS server. See Defining Credentials.
-
JavaGatewayHost and JavaGatewayPort—The IP address and port of the InterSystems external server that your production is using to enable JMS support. An external server is also known as a Java Gateway. If you added the EnsLib.JavaGateway.ServiceOpens in a new tab business host to the production, use the IP address and port under its Basic Settings.
-
JMS Server—URL of the JMS server.
-
JMSFactory—Name of the QueueConnectionFactory.
-
JMSQueue—Name of the JMS Queue.
-
JMSClientID—Name that appears on the JMS Server’s list of active connections.
