Broker 10.15 | webMethods Broker Documentation | webMethods Broker Messaging Programmer's Guide | webMethods Messaging Administration | The JMSAdmin Command-Line Tool | JMSAdmin Properties | Sample JNDI Properties File
 
Sample JNDI Properties File
Following is an example of a JNDI properties file used for an SSL-enabled Broker connection on Windows. The JNDI provider is LDAP. The numbers in brackets are used for illustrative purposes; they are not included in the file.
[1] java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
[2] java.naming.provider.url=ldap://adam.south.acme.com/
ou=jmsdev,ou=pd,o=wm
[3] java.naming.security.principal="cn=Manager,ou=jmsdev,ou=pd,o=wm"
[4] java.naming.security.credentials=JMSatAxyz
[5] com.webmethods.jms.naming.keystore=C:/BrokerSSL/MyKeystore.p12
[6] com.webmethods.jms.naming.truststore=C:/BrokerSSL/MyTruststore.jks
[7] com.webmethods.jms.naming.encrypted=True
The sample properties file specifies:
1. The factory class LdapCtxFactory as the initial context for the JNDI provider.
2. The location of the JNDI provider. In this case, LDAP component identifiers are used.
3. The distinguished name that the JNDI client uses to connect to the Broker. This property must be set if the Broker connection is SSL-enabled.
4. The password that the JNDI client uses to connect to the Broker; here, the password is set to "JMSatAxyz".
5. The fully-qualified name of the file containing the SSL certificate that the JNDI client uses to connect to the Broker.
6. Whether message traffic between the JNDI client and the Broker is encrypted. A value of "true," the setting used here, turns on encryption.