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 in the server.xml file.
Before you proceed, review Manual installation on WebSphere Application Server Liberty 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
When you define
the JNDI properties, the JNDI names must be prefixed with the context
root of the administration service. The following example illustrates
the case to declare
mfp.admin.push.url whereby
the administration service is installed with
/mfpadmin as
the context root:
<jndiEntry jndiName="mfpadmin/mfp.admin.push.url" value="http://localhost:9080/imfpush"/>
If
the push service is installed, you must 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 configuration
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 JNDI name of the data
source for the administration service must be defined as
jndiName=<contextRoot>/jdbc/mfpAdminDS.
The following example illustrates the case whereby the administration
service is installed with the context root
/mfpadmin,
and that the service is using a relational database:
<dataSource jndiName="mfpadmin/jdbc/mfpAdminDS" transactional="false">
[...]
</dataSource>
Security roles
Declare the following roles
in the
<application-bnd> element of the application:
- mfpadmin
- mfpdeployer
- mfpmonitor
- mfpoperator