OpenEdge clients can connect directly to a JMS-provider Broker by using the Progress OpenEdge JMS Adapter for a messaging session. By connecting directly to the JMS-provider Broker, the OpenEdge client has better control over connection management, and there is no need to manage and configure a Progress OpenEdge JMS Adapter server process.

Additional benefits include the availability of client persistence and fault tolerance. For more information on client persistence, see Configure fault tolerance and high availability for ActiveMQ Artemis, Configure client persistence for SonicMQ, Configure fault tolerance for SonicMQ, or your JMS-provider's documentation.

CAUTION: This method creates a larger run-time footprint for your OpenEdge client.

Using SMQConnect on a client

In the following example, the application creates a session procedure by calling jmssession.p persistently specifying the -SMQConnect connection parameter.

DEFINE VARIABLE hSession AS HANDLE NO-UNDO.
RUN jms/jmssession.p PERSISTENT SET hSession ("-SMQConnect").
RUN setBrokerURL IN hSession ("MQBrokerHost:2506").
RUN beginSession IN hSession.
Note: Each messaging session creates a connection to the JMS-provider Broker.