Universal Messaging's Enterprise Manager tool supports JNDI using the same Universal Messaging Channel based context used by the JMSAdmin example.

The example (jmsdmin.Java) source code demonstrates how to store Universal Messaging Provider for JMS components into a JNDI service provider. The default service provider for the example Universal Messaging's own Universal Messaging Context to store JMS objects references, however any JNDI context provider can be used, from LDAP through to NIS. The Universal Messaging context is discussed in more detail here. The Universal Messaging Context stores references in a channel called /naming/defaultContext.

JMSAdmin creates all required resources on a Universal Messaging realm. Example usage is as follows:

where:

RNAME is the realm name of the Universal Messaging server you wish to connect to. If no RNAME is provided the default RNAME of nsp://localhost:9000 is used.

PRINCIPAL is the subject ( if any) you JNDI service provider requires

PASSWORD is the PRINCIPAL's password for the JNDI service provider used

CONTEXT_FACTORY is the fully qualified class name of the providers context factory implementation. The default CONTEXT FACTORY is com.pcbsys.nirvana.nSpace.Universal MessagingContextFactory and is set automatically if no CONTEXT_FACTORY parameter is provided.

PROVIDER_URL is the custom url required by the context factory and provider implementation. If no PROVIDER_URL parameter is passed the default used is nsp://localhost:9000/.

As an example assume we want to create a TOPIC called rates on a Universal Messaging realm running on our local machine. Typing:

Java com.pcbsys.nirvana.nSpace.JMSAdmin bind topic rates

Will create an event in the /naming/defaultContext channel with the following information in the event properties of the event:

The topic rates will automatically be created on the Universal Messaging realm running on the PROVIDER_URL value. Assuming you wish to reference your local realm as a TopicConnectionFactory named TopicConnectionFactory in JMS use the following command:

This will publish an event to the naming/defaultContext channel with the following information in the event dictionary:

Creating a queue can be achieved using the following command:

Likewise a JMS Queue connection factory called QueueConnectionFactory can be bound into a name space using the following command

Having run both queue related commands the naming/defaultContext channel will contain 4 events, each one pertaining to the 4 objects that have been bound, TopicConnectionFactory, QueueConnectionFactory, rates and movie. The Universal MessagingContext used with your JMS application will now be able to lookup these objects and use them within your application.