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

MobileFirst Operations Console configuration details

The console is packaged as a WAR application for us to deploy to the Liberty collective controller. We need to make some specific configurations for this application in the server.xml file of the Liberty collective controller.

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

The console WAR file is in mfp_install_dir/MobileFirstServer/mfp-admin-ui.war.

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

Mandatory JNDI properties

When we define the JNDI properties, the JNDI names must be prefixed with the context root of the console. The following example illustrates the case to declare mfp.admin.endpoint whereby the console is installed with /mfpconsole as the context root:

<jndiEntry jndiName="mfpconsole/mfp.admin.endpoint" value="*://*:*/mfpadmin"/>

The typical value for the mfp.admin.endpoint property is *://*:*/<adminContextRoot>.

For more information about the JNDI properties, see JNDI properties for MobileFirst Operations Console.

Security roles

Declare the following roles in the <application-bnd> element of the application:

• mfpadmin
• mfpdeployer
• mfpmonitor
• mfpoperator

Any user that is mapped to a security role of the console must also be mapped to the same security role of the administration service.

Parent topic: Manual installation on WebSphere Application Server Liberty collective