Broker 10.15 | webMethods Broker Documentation | Administering webMethods Broker | Using My webMethods with JMS | Managing JNDI Naming Directories
 
Managing JNDI Naming Directories
 
Listing the JNDI Providers
Viewing a JNDI Provider's Properties
Editing a JNDI Provider's Properties
Adding a JNDI Provider
This section describes how to manage and configure JNDI naming directories, which are used to store JMS administered objects.
For My webMethods to store administered objects on a server (for example, WebLogic, LDAP, or JBoss), the server must be active. WebLogic JNDI objects do not persist when you restart the WebLogic Server.
Note:
If you are using WebLogic as the JNDI provider, make sure the wm-jmsclient.jar file is available under samples\domains\wl_server folder in your WebLogic installation directory. You will not be able to create connection factories, topics, and queues without the wm-jmsclient.jar file.
For LDAP servers, the server must either be running with schema validation turned off or it must have the Java object schema installed. The Java object schema is defined in RFC 2173.
If you are using the webMethods Naming Service for JMS (webMethods Naming Service) as the JNDI provider, make sure the Broker acting as the naming server is running. When you use webMethods Broker as a JNDI provider, make sure you do not use that Broker for publishing and subscribing messages.