Broker 10.5 | webMethods Broker Documentation | webMethods Broker Messaging Programmer's Guide | webMethods Naming Service for JMS: Configuration Settings and Properties | Using a JNDI Properties File | Provider Property Descriptions
 
Provider Property Descriptions
The following are the properties for the Naming Service.
Note:
When you use My webMethods and go to Naming Directories, default property values are set when you add a JNDI provider and select Naming Service. You can then configure the provider as appropriate. For more information, see Administering webMethods Broker .
java.naming.factory.initial
Required. The factory class for the Naming Service. This factory class resides in the wm-jmsnaming.jar library. You must include wm-jmsnaming.jar in the CLASSPATH on the machine where the Naming Service client is running. Set this property as follows:
java.naming.factory.initial=com.webmethods.jms.naming.WmJmsNamingCtxFactory
java.naming.provider.url
Optional. The URL that points to the initial context and to the Broker that will act as the naming server and to the initial naming context. The following is the URL syntax:
wmjmsnaming:// [ brokerName ] [ @brokerHost [ : port ] ] [ /context ]
If brokerName is omitted, the default Broker is used. If brokerHost is omitted, localhost is used. If port is omitted, 6849 is assumed. Use context to specify the root namespace; use the following notation:

rootContext::subContext::subContext
Each segment in context must begin with an alphabetic character followed by any combination of alphanumeric characters or the underscore character (_). Each segment of the context name can be up to 255 characters long. (On the Broker, context is represented by a document type name, which means that it must adhere to valid, document-type naming syntax.)
If you do not specify an initial context, Naming Service creates a default initial context with the name WmJmsNamingContext.
*Example 1
The following example points to a Broker called "mars" on Broker host B01East at port 9000. It sets the initial context to JMS::CustMgmt.
java.naming.provider.url=wmjmsnaming://mars@B01East:9000/JMS::CustMgmt
*Example 2
The following URL points to the default Broker on localhost on the default port (6849). It sets the initial context to JMSObjects.
java.naming.provider.url=wmjmsnaming::///JMSObjects
com.webmethods.jms.naming.clientgroup
Required to access webMethods Naming Service for JMS with admin tools. The client group that the Naming Service for uses to connect to the Broker naming server. To access the Naming Service through the administrative tools, set this property to the admin client group as shown below:
com.webmethods.jms.naming.clientgroup=admin
A client that operates as a member of the admin group has permission to write to the Broker's JNDI namespace. For more information, see the "Managing Client Groups" chapter of Administering webMethods Broker .
You do not need to set the clientgroup property for read-only access to the Naming Service (for example, to simply recall an administered object from within a JMS application). By default, Naming Service clients function as members of the "WmJmsNamingReader" client group, which has read-only access to all objects in the Broker JNDI namespace.
If you are using webMethods JNDI event listener, you must add the "Broker::Activity::EventTypeChange" document type to the client group's can-subscribe list. Otherwise, if the Broker Server restarts, the event listener will not get a remote notification, and the JNDI client will throw the following exception:
Cannot subscribe to document type 'Broker::Activity::EventTypeChange'.
Permission is denied. Check the 'can subscribe' permissions in the client's
client group.
com.webmethods.jms.naming.keystore
Required if the Broker that provides naming services is SSL-enabled.The fully qualified name of the file containing the SSL certificate that the Naming Service is to use to connect to the Broker.
The following example points to the file myKeystore.p12.
com.webmethods.jms.naming.keystore=C:\BrokerSSL\myKeystore.p12
com.webmethods.jms.naming.truststore
Required if the Broker that provides naming services is SSL-enabled. The fully qualified name of the file containing the trusted root certificates that the Naming Service is to use to connect to the Broker.
The following example points to the file myTruststore.jks.
com.webmethods.jms.naming.truststore=C:\BrokerSSL\myTruststore.jks
java.naming.security.principal
Required if the Broker that provides naming services is SSL enabled. The distinguished name that the Naming Service will use to connect to the Broker. The following example sets a distinguished name:
java.naming.security.principal=CN=Developer 1,OU=Product Development,
O=webMethods Inc.,L=Fairfax,ST=VA,C=US
java.naming.security.credentials
Required if the Broker that provides naming services is SSL enabled. The passphrase for the keystore that is specified in com.webmethods.jms.naming.keystore. The following example sets the password to mysecurePassword.
java.naming.security.credentials=mySecurePassword
com.webmethods.jms.naming.encrypted
A true/false flag that specifies whether traffic between the Naming Service and the Broker is encrypted.