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 JavaTools.properties file on the Progress OpenEdge JMS Adapter for [SonicMQ] CLASSPATH (regardless of JMS-provider). The Progress OpenEdge JMS Adapter 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 Progress OpenEdge JMS Adapter creates objects as required.

For more information, see the next topic: Build the AdminObjectFinder for use with JNDI.