The administration service is packaged as a WAR application for you to deploy to the
application server. You need to make some specific configurations for this application.
Before you proceed, review Manual installation on Apache Tomcat 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.
You can define the context root as you want. However, usually it is
/mfpadmin.
Mandatory JNDI properties
The JNDI properties are defined within the
<Environment> element in the
application context. For example:
<Environment name="mfp.admin.push.url" value="http://localhost:8080/imfpush" type="java.lang.String" override="false"/>
To enable the JMX communication with the runtime, define the following JNDI properties:
- mfp.topology.platform
- mfp.topology.clustermode
If the push service is installed, you must also configure the following JNDI properties:
- mfp.admin.push.url
- mfp.admin.authorization.server.url
- mfp.push.authorization.client.id
- mfp.push.authorization.client.secret
- mfp.admin.authorization.client.id
- mfp.admin.authorization.client.secret
The JNDI properties for the communication with the live update service are as follows:
- mfp.config.service.user
- mfp.config.service.password
For more information about the JNDI properties, see List of JNDI properties for MobileFirst Server administration service.
Data source
The data source (
jdbc/mfpAdminDS) is declared as a resource in the
<Context> element. For
example:
<Resource name="jdbc/mfpAdminDS" type="javax.sql.DataSource" .../>
Security roles
The security roles available for the administration service application are:
- mfpadmin
- mfpdeployer
- mfpmonitor
- mfpoperator