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

MobileFirst Server push service configuration details

The push service is packaged as a WAR application for us to deploy to the application server. We need to make some specific configurations for this application.

Before proceeding, review Manual installation on Apache Tomcat for the configuration details that are common to all services.

The push service WAR file is in mfp_install_dir/PushService/mfp-push-service.war.

You must define the context root as /imfpush. Otherwise, the client devices cannot connect to it as the context root is hardcoded in the SDK.

Mandatory JNDI properties

We need to define the following properties:

• mfp.push.authorization.server.url
• mfp.push.authorization.client.id
• mfp.push.authorization.client.secret
• mfp.push.services.ext.security - the value must be com.ibm.mfp.push.server.security.plugin.OAuthSecurityPlugin.
• mfp.push.db.type - for a relational database, the value must be DB.

If MobileFirst Analytics is configured, define the following JNDI properties:

• mfp.push.analytics.endpoint
• mfp.analytics.username
• mfp.analytics.password
• mfp.push.services.ext.analytics - the value must be com.ibm.mfp.push.server.analytics.plugin.AnalyticsPlugin.

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

Data source

The JNDI name of the data source for the push service must be defined as jdbc/imfPushDS.

Parent topic: Manual installation on Apache Tomcat