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


MobileFirst Server administration service configuration details

The administration service is packaged as a WAR application for us to deploy to the application server. You 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 administration service WAR file is in mfp_install_dir/MobileFirstServer/mfp-admin-service.war.

We can define the context root as we want. However, usually it is /mfpadmin.


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.

To enable the JMX communication with the runtime, we must configure the following JNDI properties:

On WebSphere Application Server Network Deployment

  • mfp.admin.jmx.dmgr.host
  • mfp.admin.jmx.dmgr.port - the SOAP port on 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 the push service is installed, we must configure the following JNDI properties:

The JNDI properties for the communication with the configuration service are as follows:

For more information about the JNDI properties, see List of JNDI properties for MobileFirst Server administration service.


Data source

Create a data source for the administration service and map it to jdbc/mfpAdminDS.


Start order

The administration service application must start before the runtime 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.


Security roles

The following roles are defined for this application:

Parent topic: Manual installation on WebSphere Application Server and WebSphere Application Server Network Deployment