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


MobileFirst Server live update service configuration details

The live update service is packaged as a WAR application for us to deploy to the Liberty collective controller. You 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 live update service WAR file is in mfp_install_dir/MobileFirstServer/mfp-live-update.war.

The context root of the live update service must define in this way: /<adminContextRoot>config. For example, if the context root of the administration service is /mfpadmin, then the context root of the live update service must be /mfpadminconfig.


Data source

The JNDI name of the data source for the live update service must be defined as <contextRoot>/jdbc/ConfigDS. The following example illustrates the case whereby the live update service is installed with the context root /mfpadminconfig, and that the service is using a relational database:

<dataSource jndiName="mfpadminconfig/jdbc/ConfigDS" transactional="false"> [...] </dataSource>


Security roles

Declare the configadmin role in the <application-bnd> element of the application.

At least one user must be mapped to this role. The user and its password must be provided to the following JNDI properties of the administration service:

Parent topic: Manual installation on WebSphere Application Server Liberty collective