Try OpenEdge Now
skip to main content
Messaging and ESB
Understanding the OpenEdge Adapters : Unified domain for JMS sessions
 

Unified domain for JMS sessions

Prior to OpenEdge Release 10.1, clients were required to create a JMS session for either PTP or Pub/Sub. In order for a client to use both queues and topics, the client needed to create two separate JMS sessions.
The following ABL code starts a JMS session using queues:
RUN jms/ptpsession.p PERSISTENT SET ptpsession (adapterConnection).
The following ABL code starts a JMS session using topics:
RUN jms/pubsubsession.p PERSISTENT SET pubsubsession (adapterConnection).
Currently, clients can use both PTP and Pub/Sub in the same JMS session by using the unified domain model.
The following ABL code starts a JMS session using the unified domain to access both queues and topics in one JMS session object:
RUN jms/jmssession.p PERSISTENT SET jmssession (adapterConnection).
Note: See the Connection options for valid values for adapterConnection.