Broker 10.5 | webMethods Broker Documentation | Administering webMethods Broker | Using My webMethods with JMS | Binding Administered Objects in JNDI
Binding Administered Objects in JNDI
The administered objects you use for JMS messaging (connection factories and destinations) and their properties are bound to locations in a standardized namespace built from a set of Java classes called JNDI (Java Naming and Directory Interface). The root location is called the initial context. JNDI serves as a template for the JMS administered objects, storing their property settings in specified locations relative to the initial context. These settings are applied when the JMS connection factories and destinations are created and used when the JMS application runs.
There may be cases where you do not want to use JNDI but want to configure the administered objects programmatically rather than administratively (that is, in your JMS application code). My webMethods supports the configuration of JMS applications programmatically, using the WmJMSAdminFactory class. For more information, see the product Javadoc.
Working with JMS administered objects programmatically has the advantage of reducing the amount of administration required; however, you cannot use JMS applications created programmatically with other JMS providers.
It is important to note that JNDI does not contain the JMS objects themselves, only the information necessary to configure them. For example, when working with a destination such as a topic, you must bind the topic in JNDI and, in a separate operation, create the topic on the Broker either programmatically using the JMS Admin API or with My webMethods.