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 application server. We need to make some specific configurations for this application.
Before proceeding, review Manual installation on WebSphere Application Server and WebSphere Application Server Network Deployment 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
We can set JNDI properties with the WebSphere Application Server administration console. Go to Applications > Application Types > WebSphere enterprise applications > application_name > Environment entries for Web modules and set the entries.
You must define the mfp.authorization.server property with the value as embedded.
Also, define the following JNDI properties to enable the JMX communication with the administration service:
- On WebSphere Application Server Network Deployment
- mfp.admin.jmx.dmgr.host - the host name of the deployment manager.
- mfp.admin.jmx.dmgr.port - the SOAP port of the deployment manager.
- mfp.topology.platform - set the value as WAS.
- mfp.topology.clustermode - set the value as Cluster.
- mfp.admin.jmx.connector - set the value as SOAP.
- On a stand-alone WebSphere Application Server
- mfp.topology.platform - set the value as WAS.
- mfp.topology.clustermode - set the value as Standalone.
- mfp.admin.jmx.connector - set the value as SOAP.
If MobileFirst Analytics is installed, you also 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.
Start order
The runtime application must start after the administration service application. We can set the order at Startup behavior section. For example, set the Startup Order to 1 for the administration service and 2 to the runtime.
Data source
Create a data source for the runtime and map it to jdbc/mfpDS.
Parent topic: Manual installation on WebSphere Application Server and WebSphere Application Server Network Deployment