This documentation is for WSO2 Enterprise Mobility Manager 2.2.0. View documentation for the latest release.
Android Platform Configurations - Enterprise Mobility Manager 2.2.0 - WSO2 Documentation
Skip to end of metadata
Go to start of metadata

Multiple tenants can use WSO2 EMM; while, maintaining tenant-based isolation. The Android configurations enable the tenants to customize the Android settings based on their own requirements.

Android configurations

Follow the steps given below to configure the Android platform:

  1. Sign in to the EMM console and click the menu icon.
  2. Click CONFIGURATION MANAGEMENT > PLATFORM CONFIGURATIONS and select Android Configurations.
  3. Enter the following:
    • Notifier Type - The notifier type determines the way in which the notification will take place. The available options are as follows:
      • Local Polling - The device will contact the EMM server periodically. 
      • Firebase Cloud Messaging (FCM) - FCM will send a notification to the device when there are pending operations available for a specific device. If FCM has been selected as the notifier type, configure WSO2 EMM with Firebase Cloud Messaging (FCM).

        For more information on the notifier type and the notifier frequency, see Android Notification Methods.

    • If Local Polling was selected as the notifier type, provide the Notifier Frequency (in seconds) - This is the interval after which the wake-up command will be automatically triggered by the Android Agent.


      From Android 4.4 (KitKat) onwards, the OS does not allow applications to trigger wake-up commands when the trigger period is set to less than a minute. Therefore, make sure to set the notifier frequency to 60 seconds or more. 

    • If Firebase Cloud Messaging (FCM) was selected as the notifier type, enter the Firebase Cloud Token you generated as the API Key.
    • End User License Agreement (EULA) - Provide the license agreement that a user must adhere to when enrolling an Android device with EMM.
  4. Click SAVE.

If the Administrator changes the notifier type (from FCM to Local Polling or from Local Polling to FCM) the existing devices should re-register with WSO2 EMM for the change on the notifier type to be applied to the devices.

In the situation where the notifier type changes from Local Polling to FCM, even if the existing devices are not re-registered they are able to contact the server via local notifications. But in situations where the notifier type is changed from FCM to Local Polling, you must re-register the existing devices as they will not be able to contact the server after the change.

  • No labels