You are on page 1of 9

Afaria GCM Setup



OBTAINING A GOOGLE GCM ACCOUNT ...................................................................................................... 3
RECONFIGURE ENROLLMENT POLICIES .................................................................................................... 8
Google Cloud Messaging for Android (GCM) is a service that helps developers send data from servers to
their Android applications on Android devices. This could be a lightweight message telling the Android
application that there is new data to be fetched from the server (for instance, a movie uploaded by a friend),
or it could be a message containing up to 4kb of payload data (so apps like instant messaging can consume
the message directly). The GCM service handles all aspects of queuing of messages and is utilized by Afaria
to deliver MDM commands to Android devices.

GCM is completely free no matter how big your messaging needs are, and there are no quotas. The below
instructions outline how to request a Google GCM account which is required for Android Device

1. Navigate to the Google GCM Overview Site:

2. Log onto the Google API Console:

3. From the Console, Click on Register from the Dashboard view and enter your Project ID, then click on
Choose this ID

4. In the Address bar, copy the ProjectID out of the URL and save for later use:
a. Sample ProjectID: 6296221286

5. Before we can create the API keys, we will need to enable the Google Cloud Messaging for Android
Service. To do this click on the Services Link and ensure the Messaging Service is enabled:


Fi gure 1; Cl i ck on Servi ces

Fi gure 2: Googl e Cl oud Messagi ng for Androi d = Enabl ed

6. Now that the service is enabled, we need to generate the server Keys that will bind the bind the
API service to a specific server IP address or IP address range:
7. Click on API Access

8. Click on Create new Serer key

9. You will need to bind the server IP address to the Google API Project, it will accept entire subnets thus
you could utilize something like as a valid range.
For Amazon Afaria instances you can just leave this blank as it is not required to provide a specific IP
address/range. For production customers this would however add an additional level of security:

10. When you click on Create you will see the following Keys created:
Option 1: Key for server apps (with IP locking)
API key: AIzaSyB1uigJaDQQxLSnUYGdjapB-ZmIZZmLzxU
IPs: - Only servers with this IP range will work
Activated on: Jul 27, 2012 12:58 PM
Activated by: you

Option 2: Key for server apps (with IP locking)
API key: AIzaSyDbCaMJEr3LlnBxqdJvIgcFcsdaoXcWCAY
IPs: Any IP allowed - Allows any server to utilize API access.
Activated on: Jul 27, 2012 1:21 PM
Activated by: you

Option 3: Key for browser apps (with referers)
API key: AIzaSyDsmfzMUf9GvRBY6MaIIeRtQCwm1gj5PIs
Referers: Any referer allowed
Activated on: Jul 27, 2012 12:55 PM
Activated by: you

Once the GCM patch is applied, it is necessary to re-create all Android enrollment policies. When the user
enters the enrollment code on the device, the enrollment policy using GCM is applied. Next time an existing
device connects, the configuration policy containing the new GCM information is pushed to the device.
You should only need to deactivate your current Android Enrollment policy and then create a new one. Make
sure you configure it to map to the proper Group, Variables, etc.

2013 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP
products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of SAP AG in Germany
and other countries.
Business Objects and the Business Objects logo, BusinessObjects,
Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL
Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered
trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are
registered trademarks of Crossgate AG in Germany and other
countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of
their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials
are provided by SAP AG and its affiliated companies ("SAP Group")
for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express
warranty statements accompanying such products and services, if
any. Nothing herein should be construed as constituting an additional