The <namingConnection> element of the JMS adapter

The <namingConnection> element of the JMS adapter

Use the <namingConnection> element to identify how the MobileFirst Server connects to an external repository.
The JMS Adapter uses administered objects that must be predefined in a JNDI repository. The repository can either be defined in the JEE server context or an external JNDI repository. If we use an external repository, specify the <namingConnection> element to identify how the MobileFirst Server connects to the repository.
The <namingConnection> element has the following attributes:

Attribute Description
url Mandatory. The url of the external JNDI repository. For example: iiop://localhost. The url syntax is dependent on the JNDI provider.
initialContextFactory Mandatory. The initialContextFactory class name of the JNDI provider. For example: com.ibm.Websphere.naming.WsnInitialContextFactory. The driver, and any associated files, must be placed in the /server/lib directory. If we develop in the Eclipse environment, the driver and associated files must be placed in the /lib directory.
If we develop for WAS with WebSphere MQ, do not add the WebSphere MQ Java archive (JAR) files to the /lib directory. If the WebSphere MQ JAR files are added, classloading problems will occur because the files already exist in the WebSphere Application Server environment.
user Optional. User name of a user with authority to connect to the JNDI repository. If user is not specified, the default user name is guest.
password Optional. Password for the user specified in the user attribute. If user is not specified, the default password is guest.

Parent topic: The adapter XML File

Attribute	Description
url	Mandatory. The url of the external JNDI repository. For example: iiop://localhost. The url syntax is dependent on the JNDI provider.
initialContextFactory	Mandatory. The initialContextFactory class name of the JNDI provider. For example: com.ibm.Websphere.naming.WsnInitialContextFactory. The driver, and any associated files, must be placed in the /server/lib directory. If we develop in the Eclipse environment, the driver and associated files must be placed in the /lib directory. If we develop for WAS with WebSphere MQ, do not add the WebSphere MQ Java archive (JAR) files to the /lib directory. If the WebSphere MQ JAR files are added, classloading problems will occur because the files already exist in the WebSphere Application Server environment.
user	Optional. User name of a user with authority to connect to the JNDI repository. If user is not specified, the default user name is guest.
password	Optional. Password for the user specified in the user attribute. If user is not specified, the default password is guest.