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:
- Sign in to the EMM console and click the menu icon.
- Click Platform configurations and select Android Configurations.
- 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 - The device will contact the EMM server periodically.
GCM - GCM will send a notification to the device when there are pending operations available for a specific device. If GCM has been selected as the notifier type, register with Google Cloud Messaging (GCM).
For more information on the notifier type and the notifier frequency, see Android Notification Methods.
If Local was selected as the notifier type, provide the Notifier Frequency (in milliseconds) - This is the interval after which the wake-up command will be automatically triggered by the Android Agent.
Note
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 60000ms or more.
- If GCM was selected as the notifier type, the following configurations need to be added:
- API keys - The API key that you received after registering with Google Cloud Messaging (GCM). For more information, see Create a server key.
- Sender IDs - This refers to the project IDs. For more information, see Retrieve the Sender ID.
- End User License Agreement (EULA) - Provide the license agreement that a user must adhere to when enrolling an Android device with EMM.
- Notifier Type - The notifier type determines the way in which the notification will take place. The available options are as follows:
- Click SAVE.
If the Administrator changes the notifier type (from GCM to LOCAL or from LOCAL to GCM) 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 to GCM, 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 GCM to LOCAL you must re-register the existing devices as they will not be able to contact the server after the change.