Configuring the JMS administration tool

You must configure the administration tool with values for the following three parameters:

INITIAL_CONTEXT_FACTORY
This indicates the service provider that the tool uses. There are currently two supported values for this property:
  • com.sun.jndi.ldap.LdapCtxFactory (for LDAP)
  • com.sun.jndi.fscontext.RefFSContextFactory (for file system context)
PROVIDER_URL
This indicates the URL of the session's initial context, the root of all JNDI operations carried out by the tool. Two forms of this property are currently supported:
  • ldap://hostname/contextname (for LDAP)
  • file:[drive:]/pathname (for file system context)
SECURITY_AUTHENTICATION
This indicates whether JNDI passes over security credentials to your service provider. This parameter is used only when an LDAP service provider is used. This property can currently take one of three values:
  • none (anonymous authentication)
  • simple (simple authentication)
  • CRAM-MD5 (CRAM-MD5 authentication mechanism)

If a valid value is not supplied, the property defaults to none. If the parameter is set to either simple or CRAM-MD5, security credentials are passed through JNDI to the underlying service provider. These security credentials are in the form of a user distinguished name (User DN) and password. If security credentials are required, then the user will be prompted for these when the tool initializes.

Note: The text typed is echoed to the screen, and this includes the password. Therefore, take care that passwords are not disclosed to unauthorized users.

These parameters are set in a plaintext configuration file consisting of a set of key-value pairs, separated by an "=". This is shown in the following example:

#Set the service provider
INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory
#Set the initial context
PROVIDER_URL=ldap://polaris/o=ibm_us,c=us
#Set the authentication type
SECURITY_AUTHENTICATION=none

(A "#" in the first column of the line indicates a comment, or a line that is not used.)

An example configuration file is included in examples/jms/MQeJMSAdmin.config.


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.