Flashes (Alerts)
Abstract
Migration of push notification support from Google Cloud Message (GCM) to Firebase Cloud Messaging (FCM)– IBM Maximo Anywhere version 7.6.2 and version 7.6.2.1.
Content
Starting April 11, 2019, Google will end support of GCM push services. This document includes the step by step process for installing an IBM MobileFirst interim fix and a Maximo Anywhere limited availability fix to implement Google FCM support on both Maximo Anywhere version 7.6.2.0 and version 7.6.2.1. To obtain the limited availability fix for Maximo Anywhere, contact IBM Support.
Ensure that your build machine has access to https://services.gradle.org/distributions/gradle-4.6-all.zip.
Ensure that Android SDK version 26 is installed.
Step 1 Install the MobileFirst interim fix
Install the MobileFirst interim fix from the following link by downloading MFPF-IF201903191506..
(https://www-945.ibm.com/support/fixcentral/swg/selectFixes?product=ibm%2FOther+software%2FIBM+MobileFirst+Platform+Foundation&fixids=7.1.0.0-MFPF-IF201903191506&source=SAR&function=fixId&parent=ibm/Other%20software)
Note: This version is required for FCM support on MobileFirst version 7.1. Also, you must install Android 28.0.3 build tools, Android SDK Platform-Tools 28.0.2, and API level 26, using the Android Package Manager.
Step 2 Get the key from Google Firebase
Go to the Google console Firebase (https://console.firebase.google.com) and generate a new server key and sender id. A part of Google Firebase configuration includes a download of the file google-services.json file. If you are going to use FCM notification for the WorkExecution and Inspection apps, ensure that during the generation of the google-service.json file you provide the package name. For the Inspection app it is com.Inspection, and for the Work Execution app, it is com.WorkExecution. For each app that will use FCM, after setting the package name for the app, download the google-services.json file and make notes about the server key and sender id for each app as you will use this information later in this process.
Step 3 Apply the Maximo Anywhere limited availability fix
Apply the limited availability fix for Maximo Anywhere that has the FCM support for version 7.6.2.0 and 7.6.2.1. Contact IBM Support for this limited availability fix.
You use the platformbuildnumber.zip file to implement the Maximo Anywhere limited availability fix:
a) Open the MaximoAnywhere/build.properties file and find the platformzip.location path.
b) Copy the platformbuildnumber.zip file from the platformzip.location path.
c) Unpackage the MaximoAnywhereApplication.zip inside the MaximoAnywhere folder.
d) Go to the MobileFirst Server installation folder that is commonly found in the /MobileFirst_Platform_Server/WorklightServer folder and copy the following JAR files:
- worklight-ant-builder.jar
- worklight-ant-deployer.jar
- worklight-jee-library.jar
Replace the files in the MaximoAnywhere/libs/build folder with the files that you copied from your MobileFirst Server installation folder.
e) Run a build install-platform all command from the MaximoAnywhere folder.
Step 4 Implement the Google FCM key for Maximo Anywhere
For the Work Execution app:
· Open the MaximoAnywhere/build.properties file and update the android.pushSender.Key and android.senderId properties.
· In the MaximoAnywhere/apps/WorkExecution/android/native folder, replace the default google-services.json file with the new google-services.json file you downloaded from Firebase.
· Open the build.gradle file and uncomment the last line so that //apply plugin: ‘com.google.gms.google-services’ is now apply plugin: ‘com.google.gms.google-services’.
This step ensures that google-services is enabled and checks the google-services.json file during builds.
· Ensure that the MaximoAnywhere/WorkExecution/app-features.properties file has the push notification properties set to true.
For the Inspection app:
· Open the MaximoAnywhere/build.properties file and update the android.pushSender.Key and android.senderId properties.
· In the MaximoAnywhere/apps/Inspection/android/native folder, replace the default google-services.json file with the new google-services.json file you downloaded from Firebase.
· Open the build.gradle file and uncomment the last line so that //apply plugin: ‘com.google.gms.google-services’ is now apply plugin: ‘com.google.gms.google-services’.
This step ensures that google-services is enabled and checks the google-services.json file during builds.
· Ensure that the MaximoAnywhere/Inspection/app-features.properties file has the push notification properties set to true.
Step 5 - Run the build process to build the APK file with FCM support
Go to the MaximoAnywhere folder and run a build all command. Ensure that you test push notifications on your device.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPJLC","label":"Maximo Anywhere"},"Component":"","Platform":[{"code":"PF003","label":"Android"}],"Version":"7.6.2, 7.6.2.1","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
26 September 2022
UID
ibm10879643