SAP How-to Guide SAP Mobility
SAP Afaria
provided by SAP Mobile - Rapid Innovation Group
Applicable Releases:
SAP Afaria 7 (SP1-SP4)
Version 1.0
March 2013
How To... Enroll iOS Devices in Afaria
Copyright 2014 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form
or for any purpose without the express permission of SAP AG. The
information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors
contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered
trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p,
System p5, System x, System z, System z10, System z9, z10, z9, iSeries,
pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390,
OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power
Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,
OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS,
HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,
MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and
Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other
countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either
trademarks or registered trademarks of Adobe Systems Incorporated in
the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open
Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame,
and MultiWin are trademarks or registered trademarks of Citrix Systems,
Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks
of W3C, World Wide Web Consortium, Massachusetts Institute of
Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used
under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, 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 company.
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.
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.
The information in this document is proprietary to SAP. No part of this
document may be reproduced, copied, or transmitted in any form or for
any purpose without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license
agreement or any other agreement with SAP. This document contains
only intended strategies, developments, and functionalities of the SAP
product and is not intended to be binding upon SAP to any particular
course of business, product strategy, and/or development. Please note
that this document is subject to change and may be changed by SAP at
any time without notice.
SAP assumes no responsibility for errors or omissions in this document.
SAP does not warrant the accuracy or completeness of the information,
text, graphics, links, or other items contained within this material. This
document is provided without a warranty of any kind, either express or
implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without
limitation direct, special, indirect, or consequential damages that may
result from the use of these materials. This limitation shall not apply in
cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not
affected. SAP has no control over the information that you may access
through the use of hot links contained in these materials and does not
endorse your use of third-party Web pages nor provide any warranty
whatsoever relating to third-party Web pages.
SAP How-to Guides are intended to simplify the product implement-
tation. While specific product features and procedures typically are
explained in a practical business context, it is not implied that those
features and procedures are the only approach in solving a specific
business problem using SAP NetWeaver. Should you wish to receive
additional information, clarification or support, please refer to SAP
Consulting.
Any software coding and/or code lines / strings (Code) included in this
documentation are only examples and are not intended to be used in a
productive system environment. The Code is only intended better explain
and visualize the syntax and phrasing rules of certain coding. SAP does
not warrant the correctness and completeness of the Code given herein,
and SAP shall not be liable for errors or damages caused by the usage of
the Code, except if such damages were caused by SAP intentionally or
grossly negligent.
Disclaimer
Some components of this product are based on Java. Any code change
in these components may cause unpredictable and severe malfunctions
and is therefore expressively prohibited, as is any decompilation of these
components.
Any Java Source Code delivered with this product is only to be used by
SAPs Support Services and may not be modified or altered in any way.
Document History
Document Version Description
1.10 >
1.00 First official release of this guide
Typographic Conventions
Type Style Description
Example Text Words or characters quoted
from the screen. These
include field names, screen
titles, pushbuttons labels,
menu names, menu paths,
and menu options.
Cross-references to other
documentation
Example text Emphasized words or
phrases in body text, graphic
titles, and table titles
Example text File and directory names and
their paths, messages,
names of variables and
parameters, source text, and
names of installation,
upgrade and database tools.
Example text User entry texts. These are
words or characters that you
enter in the system exactly
as they appear in the
documentation.
Variable user entry. Angle
brackets indicate that you
replace these words and
characters with appropriate
entries to make entries in the
system.
EXAMPLE TEXT Keys on the keyboard, for
example, F2 or ENTER.
Icons
Icon Description
Caution
Note or Important
Example
Recommendation or Tip
Table of Contents
1. Business Scenario ................................................................................................................. 1
2. Background Information ....................................................................................................... 1
3. Prerequisites .......................................................................................................................... 1
4. Step-by-Step Procedure ...................................................................................................... 2
4.1 Configure Afaria Server for Enrollment Codes ............................................................ 2
4.2 Create a Group for your Device ..................................................................................... 3
4.3 Create an Enrollment Policy .......................................................................................... 4
4.4 Enrolling your Device ..................................................................................................... 8
5. Summary ............................................................................................................................. 14
6. Appendix ............................................................................................................................. 15
6.1.1 Enabling Google URL Service ......................................................................... 15
6.1.2 Troubleshooting .............................................................................................. 21
How To... Enroll iOS devices in Afaria
March 2014 1
1. Business Scenario
This document provides an overview of steps that one would need to follow to create enrollment
policies for iOS devices on SAP Afaria. Enrollment policies are used with either the Self Service
Portal (SSP) or when users enroll their own devices by installing AppStore Afaria client and entering
enrollment code to connect their devices to the Afaria server.
2. Background Information
This H2G describes the steps one would need to follow in order to create an enrollment policy for
iOS devices. The enrollment policy created in this guide relies on the creation of enrollment codes
using third party URL shortening services provided by either TinyURL or Google. The guide is
designed to be a starting point and does not prescribe best practice for designing your groups
within Afaria or which policies linked to those groups, the groups and policies used here are
intended for illustration purposes only.
3. Prerequisites
The following are pre-requisites that must be met in order for you to complete the business
scenario in this H2G:
Installed Afaria 7.0 SP3 or later
Access to the SAP Afaria Administrator
A test iOS device with the SAP Afaria AppStore client installed
TinyURL access (free, requires no registration) or Google API key (free, requires
registration)
How To... Enroll iOS devices in Afaria
March 2014 2
4. Step-by-Step Procedure
This H2G provides a basic procedure to follow for creating basic Enrollment Policies for iOS.
Enrollment policies are the policies created for use in enrolling new devices onto Afaria. In order to
create an enrollment policy, you will need to create an enrollment code. An enrollment code is a
short code generated by a URL shortening service such as Google or TinyURL and is a translation of
a much longer URL. From an end-user perspective, it is far easier to provide them with a short code
to use for enrollment instead of having to input things like a server name/IP address, ports, Farm Id
etc in order to configure their devices to connect to the Afaria server. This means, that for a user
who installs an Apple AppStore Afaria client onto their device they would simply need to enter a
short code or enroll via the self-service portal to which the same shortcode has been linked. The
purpose of an enrollment policy is then to:
Provide the enrollment code
To define the connectivity parameters for the client to connect to the server
To define the device naming convention (how the device is named in Afaria)
Optionally, to define substitution variables (data elements) to be collected during
enrollment by means of prompting the user to enter certain values at enrollment time, for
example a user name, an Exchange password, a domain etc.
Optionally, to define group membership
Note
It is a requirement for iOS enrollment, that the policy is associated with a group (e.g. iOS Enrollment Policy linked with iOS Static group).
4.1 Configure Afaria Server for Enrollment Codes
Before you can create an enrollment policy, you will need to configure your Afaria server to
generate enrolment codes (if you have not done so).
1. In Afaria Administrator, navigate to Server > Configuration > Server > Enrollment Code.
How To... Enroll iOS devices in Afaria
March 2014 3
2. Enable the URL shortening service you wish to use:
a. Select Enable the TinyURL service to enable TinyURL.
i. Click Test TinyURL connection to test connectivity.
b. Select Enable the Google URL service to enable Googles URL shortening service.
i. If prompted, Accept the terms of service.
ii. For Google, you will need to enter your google API key, refer to the appendix for
instructions on obtaining an API key for this service.
Refer to the troubleshooting section at the end of this guide should you experience difficulty in
testing the connection to Google or TinyURL.
4.2 Create a Group for your Device
Now, we are ready to create a group for our new device. For this guide we will use a Static Group,
that is a group which we either add devices to during enrollment (as we are here) or an
administrator could manually add a device to this group later.
1. In Afaria Administrator, click Group, New, Static.
How To... Enroll iOS devices in Afaria
March 2014 4
2. In Group, enter Default Static iOS.
3. In Note, enter Static Group for iOS Devices.
4. Click Save to save your new group.
4.3 Create an Enrollment Policy
1. Now, we are ready to create the Enrollment Policy.
2. In Afaria Administrator, click Policy, New, Enrollment, iOS.
How To... Enroll iOS devices in Afaria
March 2014 5
3. In Policy, enter iOS Enrollment Policy.
4. In Description, enter Enrollment Policy for iOS.
5. Next, click on General section
6. In the Code section, clieck the + button to add a new short code. 7. Select the URL shortener to use using the radio button to selectTinyURL or Google.
How To... Enroll iOS devices in Afaria
March 2014 6
Note
With Google APIs you can specity an expiry date for your enrollment code(optional).
8. Click the green checkmark buttton to generate your new code. 9. The new code entry should be displayed in the Code table. A useful tip ist o type the code into
the description fiel das shown for quick reference later on.
10. Select the code you generated and click the Inspect button in the toolbar.
11. Notice that the enrollment address to which the shortened URL translates is displayed, this
should correspond to your Servers address. Please refer to the appendix at the end of this guide for details on resolving shortcodes outside of Afaria, which is very useful for
troubleshooting. Close the Inspector window.
How To... Enroll iOS devices in Afaria
March 2014 7
12. Review the remaining settings but leave the defaults in place. Note that by default, the
Enrollment Policy is set for the device to connect to the server after installation. Also note that
you can optionally set the naming convention for your devices here.
13. Click Group to review the Group settings.
14. From Groups, select the iOS Static group you created in the previous step and use the arrows
to move the selected group to the Selected Groups box on the right.
15. Click Save to save your enrollment policy.
16. We are now ready to test enrollment on our device, note that we will be enrolling directly, by
opening the newly installed Afaria Client on our device and entering the enrollment code when
prompted.
How To... Enroll iOS devices in Afaria
March 2014 8
4.4 Enrolling your Device
1. Open the Afaria client on your device.
2. You will be prompted to enter an enrollment code, enter the code you generated when creating
your enrollment policy.
3. You will be prompted to enter your credentials, enter
Username: Valid user name for your domain (student##)
Password: Valid password for the user on the domain (Welcome1)
How To... Enroll iOS devices in Afaria
March 2014 9
4. Click OK.
5. Click Install in order for Afaria client to start the enrollment process.
How To... Enroll iOS devices in Afaria
March 2014 10
6. Click Install Now.
How To... Enroll iOS devices in Afaria
March 2014 11
7. Click Install, when prompted to install ROOT CERTIFICATE
8. Once the enrollment process is completed, you should see the following screen on your mobile
device. Click Done.
How To... Enroll iOS devices in Afaria
March 2014 12
9. The session has completed. Now, lets verify on the device. Go to Settings > General and Click
on Profiles, to verify installed profiles.
How To... Enroll iOS devices in Afaria
March 2014 13
Another way to verify device enrollment is via the Afaria Administrator. This is a recommended
approach since you will not always have the physical device being enrolled in your system.
10. Open Afaria Administrator (http://YourAfariaServer/Afaria) to confirm the device has enrolled
in the Devices page.
Another way to test device enrollment is
1. Click on the Device Tab
2. Select your Device
3. Click Lock button
4. Your Device should be locked
How To... Enroll iOS devices in Afaria
March 2014 14
5. Summary
By the end of this guide you should now be ready to conduct iOS device enrollment using Afaria
Enrollment Codes.
How To... Enroll iOS devices in Afaria
March 2014 15
6. Appendix
6.1.1 Enabling Google URL Service
1. Go to: http://developer.android.com/google/gcm/gs.html and click on "Google APIs Console
Page".
2. Log into a valid Google G-mail account.
3. Click Google Cloud Console
4. Click Create Project
How To... Enroll iOS devices in Afaria
March 2014 16
5. Input name: My Afaria Project
6. Click Continue on SMS Verification screen
How To... Enroll iOS devices in Afaria
March 2014 17
7. Verify your account; input your mobile number to receive text message
8. Input Verification code
How To... Enroll iOS devices in Afaria
March 2014 18
9. Once verified, youll be pe presented with your Project Configuration page.
Note the Project Number as you will be required to input in Afaria Server GCM Enrollment.
10. Next click the APIs & auth and scroll to find Google Cloud Messaging for Android and URL
Shortner API and turn them ON
For tinyURL Enable the "URL Shortener API"
For GCM Enable the "Google Cloud Messaging for Android":
How To... Enroll iOS devices in Afaria
March 2014 19
11. Next, go to API & auth > Registered apps to register an App that will provide us with Google
Enrollment API Key; we will use the browser API Key.
12. Provide a name and select platform (Name: My App Platform Web Application)
How To... Enroll iOS devices in Afaria
March 2014 20
13. Click on the My App (under Registered apps) and expand Browser key and note the API KEY
(see screen on next page)
Note the API KEY as you will be required to input in Afaria Server GCM Enrollment.
How To... Enroll iOS devices in Afaria
March 2014 21
14. You will also need Project ID to use with GCM, to obtain the Project ID, you will have to look
through the URL address for that page:
6.1.2 Troubleshooting
1. How do I resolve a Google shortened URL?
For URLs shortened using Google, you can add '.info' to the end of the URL and this will show a
webpage with both the full URL and statistics about it's usage.
E.g. http://goo.gl/XXXXXX.info
Where XXXXXX is the Google shortened URL (Remember, Afaria will add a 'g' to the beginning
of the shortened URL to identify this as Google (as opposed to Tiny which has a 't', so the prefix
letter will need to be removed.)
2. How do I resolve a TinyURL shortened URL?
For TinyURL shortened URLs, you can navigate to http://tinyurl.com/yourenrollmentcode
How To... Enroll iOS devices in Afaria
March 2014 22
Where yourenrollmentcode = your enrollment code as it appears in Afaria minus the
leadingletter t which represents a URL shortened with tinyURL in Afaria. Your browser should take you to the enrollment address for your Afaria server, for example:
http://yourserveraddress /aips/aipService.svc/GetEnrollmentSeedData?ID=%7B9e6a88d1-
d80e-46f2-a34d-4d091dbdd09f%7D&ClientType=-10
3. How to troubleshoot connectivity?
If your connectivity tests to Google or TinyURL fail, check your Afaria server logs for further
information. Your Afaria server will need a direct connection to the internet for this to function,
your server will need to be able to connect to the web on ports 80 and 443.
How To... Enroll iOS devices in Afaria
March 2014 1
www.sap.com/contactsap
http://scn.sap.com/community/mobile
http://developers.sap.com/mobile
SAP Mobile Platform How-To Guides