The JMS-configuration directory will contain the files that come into the server on a JMS queue that is hosted by a WebSphere MQ queue manager. To create the JMS bindings file, you use the JMSAdmin application. However, before you run this application, you must customize its configuration file to your JMS environment. configure the JMS
To configure the JMS-configuration directory, take the following steps:
WebSphereMQ_Root\java\bin
where WebSphereMQ_Root is the product directory of WebSphere MQ.
INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory PROVIDER_URL=ldap://polaris/o=ibm,c=us
#INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory #PROVIDER_URL=file://C:/JNDI-Directory
Suppose you create your JMS-configuration directory as follows:
C:/filesender/config
For this JMS-configuration directory, Figure 29 shows the modified lines of the JMSAdmin.config file.
Figure 29. Sample lines of the JMSAdmin.config file
#INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory # # The following line specifies the URL of the service provider's initial # context. It currently refers to an LDAP root center. Examples of a # file system URL and WebSphere's JNDI namespace are also shown, commented # out #PROVIDER_URL=ldap://polaris/o=ibm,c=us PROVIDER_URL=file://C:/filesender/config