Create the JNDI properties file
Define JNDI properties in a property file using a text editor. Determine where to set JNDI properties according to a selective priority.
The property file follows the standard Java property file syntax and can be edited with any text editor. It has the file extension .properties. We can include all properties of all web archive (WAR) files in the same property file.
Here is an example of the content of a property file.
publicWorkLightHostname=myworklighthost.net
publicWorkLightPort=9080
publicWorkLightProtocol=https
push.gcm.proxy.enabled=false
push.gcm.proxy.host=myproxyhost.net
push.gcm.proxy.port=-1
push.gcm.proxy.protocol=https
ibm.worklight.admin.environmentid=id123
JNDI properties
We can refer to the details of JNDI properties in the relevant parts of the user documentation:
- Application Center
- List of JNDI properties for the Application Center
- MobileFirst Application Services
- JNDI properties in server.xml
- MobileFirst runtime
- Application server-side configuration parameters
We do not have to specify all the possible JNDI properties in the property file. We can specify some in the property file, and others as JNDI properties explicitly set in the web application server. The following list indicates the priority by which properties are enacted.
- If a JNDI property is explicitly set in the application server, this property value is taken.
- If a JNDI property is set in the property file injected into the war file, or provided as a shared library, and is not set in the application server, the property value is taken from this property file.
- If the JNDI property is set in the property file provided on the file system, and is not set anywhere else, the property value is taken from this property file.
- If that is not the case, the default value of the JNDI property is taken.
Parent topic: JNDI properties file for transfer