PI54228: OVERRIDING MAPPINGS IN NATIVE ANDROID APPLICATION PREVENTS ANALYTICS DATA FROM SHOWING UP IN ANALYTICS CONSOLE

IBM MobileFirst Platform Foundation Interim Fix README for 7.1

APAR status

• Closed as program error.

Error description

• In a native Android application, if source code overwrites
  mappings used in Elasticsearch for analytics console, then data
  will not show up in the analytics console if data type is not
  the same.
  
  For example:
  This will override the timestamp and cause the analytics data
  not to show on the console.
  
  public class AnalyticsData {
     long timestamp;
  
     public AnalyticsData(Timestamp currentTime) {
         this.timestamp = currentTime.getTime();
     }
  }
  

Local fix

• Do not use mappings used in Elasticsearch for analytics console
  (ex: timestamp).
  
  To find current mappings use this url:
  Set JNDI properties in server.xml to <jndiEntry
  jndiName="analytics/http.enabled" value="true"/>
  (Make sure to set it back to false when done as this exposes
  Elasticsearch and anyone with the url can access the data and
  change it.)
  
  Use the following url to find current mappings:
  http://<ipaddress>:9500/worklight/_mapping
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Impacts developers making use of the WLAnalytics API.        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Some analytic data is collected by the framework.  If one of *
  * these reserved keys is passed as an argument in the          *
  * additional metadata object of the WLAnalytics log method,    *
  * then collisions can occur.                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * -                                                            *
  ****************************************************************
  

Problem conclusion

• The WLAnalytics log method now sanitizes the metadata object to
  prevent collisions with data that is already collected.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WL/MFPF ENTERPR

• Fixed component ID

  5725I4300

Applicable component levels

• R710 PSY

     UP