JNDI properties file for transfer

We can configure a JNDI properties file for transfer between one web application server and another; for example, to transfer from test to production environments. JNDI properties are generally specified in the configuration of the web application server, and are outside the WAR file representing the server component. Components we can transfer include...

• operations console
• MobileFirst administration service
• and Application Center

We can configure a test web server and, once the configuration is stable, we can transfer the configuration to the production web server by copying the property file to the production server.

This property file can be made available to the server components in various ways:

• The property file can be placed on the file system.

  Useful for a stand-alone test server when you are experimenting with JNDI properties. Change the file on the file system with a text editor, then restart the web server to enable the changed configuration.

• The property file can be injected into WAR files.

  Useful for transfering the configuration together with the web archive file to another web server. You only have to handle the web archive file, and no other files. The configuration is, in this case, fused into the web archive file.

• The property file can be installed as a shared library for all server components.

  Useful for exchanging the web archive files often, but want to keep the same configuration all the time.

Parent topic: Install and configure