How To... Deploy Apps to ios Devices with Afaria

SAP How-to Guide SAP Mobility SAP Afaria How To... Deploy Apps to ios Devices with Afaria provided by SAP Mobile - Rapid Innovation Group Applicable Releases: SAP Afaria 7 (SP1-SP4) Version 1.0 March 2013

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 implementtation. 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 SAP s Support Services and may not be modified or altered in any way.

Document History Document Version Description 1.10 << Enter your summary of changes in this version >> 1.00 First official release of this guide

Typographic Conventions Type Style Example Text Description 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 Icons Icon Description Caution Note or Important Example Recommendation or Tip Example text Example text Example text <Example text> EXAMPLE TEXT Emphasized words or phrases in body text, graphic titles, and table titles File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. 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. Keys on the keyboard, for example, F2 or ENTER.

Table of Contents 1. Business Scenario... 1 2. Background Information... 1 3. Prerequisites... 1 4. Step-by-Step Procedure... 2 4.1 Create an Enterprise Application Policy... 2 4.2 Test the Enterprise Application Policy... 7 4.3 Create an AppStore Application Policy without MDM... 9 4.4 Test the AppStore Application Policy... 11 4.5 Create an AppStore Application Policy with MDM... 13 5. Summary... 14

1. Business Scenario This document provides an overview of steps that one would need to follow to create application policies for ios devices on SAP Afaria. Application policies are used for populating the Afaria App portal with Enterprise and AppStore applications for installation by end users in a self-service manner. In this guide we shall use the SAP Mobile Docs to illustrate application configuration in addition to the basic app policy. 2. Background Information This H2G describes the steps one would need to follow in order to create an Application Policy for ios devices. 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 free AppStore App of your choice. A test ios device with the SAP Afaria client installed and enrolled on Afaria. March 2014 1

4. Step-by-Step Procedure This H2G provides a basic procedure to follow for creating Application Policies for ios. Application Policies are the policies created for supplying a consistent list of enterprise approved AppStore apps and Enterprise Apps to the end user based on their group membership. We will be creating an example of an Enterprise Application Policy and an AppStore Application Policy. 4.1 Create an Enterprise Application Policy ios enterprise application policies define which enterprise-signed applications are available for devices to install. 1. In Policy, select New, Application, ios Enterprise. 2. In the Summary enter: a. Policy: Agentry for ios b. Note: ios Enterprise App Agentry c. State: Published d. Featured App: selected March 2014 2

3. Select General on the left-hand menu. 4. Select Required. 5. For IPA, click the Browse button and locate the install file, in this example, we are using the AgentryA-iOS-OTA-7.0.2.144. 6. Leave Artwork blank, if desired, you can add a custom application icon for the application s display in the Afaria App Portal. 7. The Information field and app icon will be populated automatically from the ipa file you selected. The information and necessary artwork must be associated with the ipa prior to packaging. 8. Next, select Categories March 2014 3

9. Click the + Add button under Available Categories to add a new category. 10. For the new app category, enter the following: a. Category: SAP b. Featured: Yes c. Image File: Browse to the image file you wish to use for the new category d. Note: SAP Apps March 2014 4

11. Click the green tick to confirm your new app category but do not save yet. 12. Select the category you just created using the tick box in Available Categories and use the arrow button to move this category to the Selected Categories. 13. Click the Description Detail menu item in the left-hand menu bar. 14. Enter the following values: a. Display name: Leave Default b. Version: Leave Default March 2014 5

c. Afaria Description: Agentry for ios 15. For screenshots click the browse button to browse to the location of your app screenshot file. Click the green tick button to confirm your screenshot. You can add as many screenshots for an app as you wish. Next, we will configure the Agentry app. This will save the end user from having to locate and manually enter the app configuration needed to run the app. 16. Click Configuration in the left menu bar. 17. Select Text and click Edit. 18. Your completed configuration should look like this: March 2014 6

19. Click Save to complete your edit of the configuration. 20. Next, click Save to save the Application Policy. 21. Now, select the newly created application policy and click the link button in the left toolbar to display the available groups window. 22. In the right hand Groups window, select the All Devices group and click the link button in the toolbar. 4.2 Test the Enterprise Application Policy 1. Open your Afaria client on your device and click the Refresh button. 2. You should be prompted with the following message. March 2014 7

3. The new SAP category should be displayed, with the Agentry A app listed; additionally it should be listed under Featured Apps. 23. Once the app is finished installing, open the Hybrid Web Container app. Notice the status message displayed as the app checks to see if there is configuration data for the app on the Afaria Package Server. This is achieved due to the fact that the HWC app has the Afaria Static Link Libraries included in it, when you open the application, it uses these libraries to check if there is an Afaria client on the device, if so, it asks the Afaria client if there is configuration for this app. If so, the Afaria client passes back a configuration URL for this app to the HWC app. The HWC app then fetches the configuration settings from the package server and populates the fields accordingly. March 2014 8

4.3 Create an AppStore Application Policy without MDM This application policy will not use Deploy using MDM Protocol or B2B App. 1. In Policy, select New, Application, ios App Store. 2. In the Summary enter: a. Policy: Business Objects Mobile b. Note: SAP MOBI Client c. State: Published d. Featured App: selected 3. Select General on the left-hand menu. 4. We will need to get the package id to add this app to our Application Policy. In your favorite web browser search for the app you are planning to configure, in this case, we searched for SAP Business Objects Mobile itunes 5. Locate the link to the AppStore in your search results, the URL should look something like this: March 2014 9

6. Copy the AppStore id from the URL, in this example, 441208302 7. Paste the Id into the AppStore Number field in the General section. 8. Click the update link on the right, and the app logo and description should be displayed. 9. Next, select Categories 10. Select the category you created earlier using the tick box in Available Categories and use the arrow button to move this category to the Selected Categories. 11. Click the Description Detail menu item in the left-hand menu bar. 12. Enter the following values: a. Display name: SAP BusinessObjects Mobile (pre-populated) b. Afaria Description: SAP BusinessObjects Mobile (MOBI) 13. Next, click Save to save the Application Policy. 14. Now, select the newly created application policy and click the link button in the left toolbar to display the available groups window. 15. In the right hand Groups window, select the ios Static group and click the link button in the toolbar. March 2014 10

4.4 Test the AppStore Application Policy 1. Open your Afaria client on your device and click the Refresh button. 2. The SAP category should be displayed, with the Business Objects Mobile app listed; additionally it should be listed under Featured Apps. 3. Click Business Objects App to see the details. Click DETAILS. March 2014 11

4. You will be directed to the AppStore. Click FREE to install the Business Objects App. March 2014 12

Try unpublishing the app (from Afaria Administrator) to see what happens on the device. 4.5 Create an AppStore Application Policy with MDM This application policy will use Deploy using MDM Protocol. 1. In Policy, select New, Application, ios App Store. 2. In the Summary enter: a. Policy: Business Objects Mobile b. Note: SAP MOBI Client c. State: Published d. Featured App: selected March 2014 13

5. Summary By the end of this guide you should now be equipped to create and explore Application Policies for ios devices on Afaria. March 2014 14

March 2014 1

www.sap.com/contactsap http://scn.sap.com/community/mobile http://developers.sap.com/mobile SAP Mobile Platform How-To Guides