Setting Up Analytics Support for Push Notifications

improve this page | report issue

Overview

To set up Analytics support for Push Notification, the following JNDI properties must be set in order to initialize and configure the Analytics plug-in. The Analytics plug-in is provided by the Push Notifications service. If it is not set, the Push Notifications service will default to logging the events in the system logger.

<jndiEntryjndiName = "imfpush/mfp.push.services.ext.analytics" value = "com.ibm.mfp.push.server.analytics.plugin.AnalyticsPlugin"/>

The following properties are required to configure and initialize the MobileFirst Analytics plug-in. The username and password will be used to authenticate with the Analytics service at the provided endpoint.

<jndiEntryjndiName = "imfpush/mfp.push.analytics.endpoint" value = "http://<mfpserver:port>/analytics-service/rest"/>
<jndiEntryjndiName = "imfpush/mfp.push.analytics.user" value = "<username>"/>  
<jndiEntryjndiName = "imfpush/mfp.push.analytics.password" value = "<password>"/>

To track the notifications dispatched out of the Push Notifications service, ensure the following property is set to true (which is the default value):

<jndiEntryjndiName = "mfp.push.analytics.events.notificationDispatch" value = "true"/>

To disable the sending of this event, set the property to false.

For information on viewing the Push Notification reports in the Analytics Console, see Push Notification Reports.

For more information on the JNDI properties for push service, see List of JNDI properties for MobileFirst Server push service. Note: The IBM Mobile Foundation installer creates and sets up these properties to defaults.

Inclusive terminology note: The Mobile First Platform team is making changes to support the IBM® initiative to replace racially biased and other discriminatory language in our code and content with more inclusive language. While IBM values the use of inclusive language, terms that are outside of IBM's direct influence are sometimes required for the sake of maintaining user understanding. As other industry leaders join IBM in embracing the use of inclusive language, IBM will continue to update the documentation to reflect those changes.
Last modified on June 01, 2020