For up-to-date product documentation, see the IBM MobileFirst Foundation Developer Center.

MobileFirst runtime configuration details

The runtime is packaged as a WAR application for us to deploy to the Liberty collective cluster members. We need to make some specific configurations for this application in the server.xml file of every Liberty collective cluster member.

Before proceeding, review Manual installation on WebSphere Application Server Liberty collective for the configuration details that are common to all services.

The runtime WAR file is in mfp_install_dir/MobileFirstServer/mfp-server.war.

We can define the context root as we want. However, it is /mfp by default.

Mandatory JNDI properties

When we define the JNDI properties, the JNDI names must be prefixed with the context root of the runtime. The following example illustrates the case to declare mfp.analytics.url whereby the runtime is installed with /mobilefirst as the context root:

<jndiEntry jndiName="mobilefirst/mfp.analytics.url" value="http://localhost:9080/analytics-service/rest"/>

You must define the mobilefirst/mfp.authorization.server property. For example:

<jndiEntry jndiName="mobilefirst/mfp.authorization.server" value="embedded"/>

If MobileFirst Analytics is installed, you need to define the following JNDI properties:

• mfp.analytics.url
• mfp.analytics.console.url
• mfp.analytics.username
• mfp.analytics.password

For more information about the JNDI properties, see List of JNDI properties for MobileFirst runtime.

Data source

The JNDI name of the data source for the runtime must be defined as jndiName=<contextRoot>/jdbc/mfpDS. The following example illustrates the case whereby the runtime is installed with the context root /mobilefirst, and that the runtime is using a relational database:

<dataSource jndiName="mobilefirst/jdbc/mfpDS" transactional="false">
  [...] 
</dataSource>

Parent topic: Manual installation on WebSphere Application Server Liberty collective