Try OpenEdge Now
skip to main content
Messaging and ESB
Implementing Messaging : Externally managed connections : Finding administered objects in JNDI or proprietary directories : Using the OpenEdge Adapter for the SonicMQ and the ABL - JMS API with administered objects
 
Using the OpenEdge Adapter for the SonicMQ and the ABL - JMS API with administered objects
JMS does not impose any specific directory for storing administered objects (although it establishes the convention of using JNDI-compliant directories, such as LDAP). Also, the process of connecting to a JNDI server and obtaining an initial context is not standardized.
Therefore, to use directory-stored JMS objects, you must implement a Java class, compile it, and install the class file on the OpenEdge Adapter for the SonicMQ host under the OpenEdge Adapter for the SonicMQ's CLASSPATH. (For more information on CLASSPATH, see Setting the CLASSPATH.) The OpenEdge Adapter for the SonicMQ looks for that class when it starts up. If it finds the class, it creates an instance object of it and uses it to locate administered objects. If it does not find the class, the OpenEdge Adapter for the SonicMQ creates objects as required.