afaria preriquisitos

SAP How-to Guide Mobile Device Management

SAP Afaria

Applicable Releases:

Afaria 7 .x

Version 2.1

August 20 12

Afaria Technical Pre -Requisites

Copyright 2012 SAP AG. All rights reserved. No part of this publication may be reproduced or tran smitt ed in any form or for any purpose wi thout the express p ermission of SAP AG. Th e information contained herein may b e changed wi thout prior notice.

Some software products marketed by SAP AG and its d ist ributors contain propri etary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, D B2 Universal Datab ase, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeri es, xSeri es, zSeries , eServer, z/VM, z /OS, i5/OS, S/390 , OS/390, OS/4 00, AS/400, S/390 Parall el Enterp rise Server, Po werVM, Power Archit ecture, POWE R6+, POWER6 , POWER5 +, POWE R5, PO WER, OpenPower, PowerPC, BatchPipes, BladeC enter, System Storage, G PFS, H ACMP, RETAIN, D B2 Connect, RACF, Redbooks, OS/2 , Parall el Sysplex, MVS/E SA, AIX,

Intelligent Miner, WebSph ere, Netfinity, Tivoli and Informix are trademarks or registered trad emarks 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 eith er trademarks or registered t rad emarks of Adobe Systems In corp orated in the United States and /or other countries. Oracle is a registered trad emark of Oracle Corporation.

UNIX, X/Op en, OSF /1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trad emarks or r egistered trad emarks of Citrix Systems, Inc.

HTML, XML, XH TML and W3C are t rad emarks or registered trademarks of W3C, World Wid e Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Micro systems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under licen se for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, Partn erEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and se rvices mentioned herein as well as thei r respective logos are trademarks or registered trad emarks of SAP AG in Germany and other c o untries.

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 Adapti ve Server, iAnywh er e, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as thei r respective logos are tr ademarks or registered t rad emarks of Sybase, Inc. Sybase is an SAP comp any.

All other product and service names mentioned are the trademarks of their resp ective co mpanies. Data contained in this document serves information al purposes only. National produc t specifications may vary.

The information in this document is proprietary to SAP. No part of this document may b e rep roduced, co pied, or transmitted in an y form or for any purpose without the express prior writ ten permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This docume nt contains only inten ded strategies, d evelop ments , and functionalities of the SAP product and is not intended to be binding upon SAP to an y parti cular course of business , product strategy, and /or development. Please note that this docu ment is subject to ch ange and may b e ch anged by SAP at any time without notice.

SAP assu mes 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 warr anties of merchantability, fitness for a particular purpose, or non -infringement.

SAP sh all have no liability for damages of any kind including without limit ation direct , special, indirect , or consequ ential d amages that may result from the use of these m ateri als. Thi s limit ation shall not apply in cases of intent or gross negligence. The statutory liability for p ersonal injury and defective products is not affected. SAP has no control over the information that you may access th rough the use of hot links contained in these materials and does not endorse your use of third -party Web pag es nor provide an y warranty whatso ever rel ating to third -part y Web pages.

-

implementation . 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.

documentation are only examples and are not intended to be used in a

productive system e nvironment. 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

in these components may cause unpredictable and severe malfunctions

and is therefore expressively prohibited, as is any decompilation of these

components.

Document History

Document Version Description

2.1 Updated release for Afaria 7.0 SP1 (with GCM), 08/23/2012

2.0 Updated release for Afaria 7.0 , 05/23/2012

1.0 Initial release of the document, 01/26/2012

Note

Please forward a ny comments on this document to:

[email protected]
mailto:[email protected]

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. Step-by-Step Pre-requisites ................................................................................................ 2

3.1 License and Media Download .......................................................................................... 2

3.2 Devices .............................................................................................................................. 5

3.3 Device Requirements ....................................................................................................... 6

3.3.1 iOS ........................................................................................................................ 6

3.3.2 Android ................................................................................................................. 6

3.3.3 BlackBerry ........................................................................................................... 6

3.3.4 Windows ............................................................................................................... 6

3.3.5 Windows CE ......................................................................................................... 7

3.3.6 Windows Mobile Professional ............................................................................ 7

3.3.7 Windows Mobile Standard ................................................................................. 7

3.4 OS User for Installation .................................................................................................... 8

3.5 Internet Access ................................................................................................................. 8

3.6 Server Operating System ............................................................................................... 11

3.6.1 Afaria Server ....................................................................................................... 11

3.6.2 Relay Server in DMZ ..........................................................................................12

3.7 Afaria Database ...............................................................................................................12

3.8 Hardware Requirements ................................................................................................13

3.8.1 Processor ........................................................................................................... 14

3.8.2 Disk Space ......................................................................................................... 14

3.8.3 RAM .................................................................................................................... 14

3.9 SMTP ................................................................................................................................15

3.10 SSL HTTPS ...................................................................................................................15

3.11 Apple ID ........................................................................................................................... 16

3.12 Android GCM .................................................................................................................. 16

3.13 Network Ports ................................................................................................................. 16

3.13.1 iOS ....................................................................................................................... 17

3.13.2 GCM by Android ................................................................................................. 17

3.14 APNS by Apple ................................................................................................................ 18

3.15 Apple Certificates ........................................................................................................... 19

3.15.1 Procedure of Generating an APNS certificate ............................................... 19

3.16 Installing the Apple Certificates on the Afaria Server Farm Master ......................... 22

3.16.1 Certificates needed: .......................................................................................... 23

3.16.2 Instructions for installing the certificates on the Afaria Server: .................. 23

3.16.3 Alternate Instructions for installing the certificates on the Afaria Server: . 23

4. Appendix ............................................................................................................................. 24

4.1 Certificate Authority (CA) ............................................................................................. 24

4.1.1 Certificate Authority (CA) ................................................................................ 24

4.2 Component and Feature Requirements Relay Server ............................................ 26

4.3 Client Requirement s iOS ............................................................................................ 27

4.4 Client Requirements BlackBerry ............................................................................... 28

4.5 Client Requirements Android .................................................................................... 28

4.6 Device Requirements Windows ................................................................................. 30

4.7 Device Requirements Windows CE ........................................................................... 32

4.8 Device Requirements Windows Mobile Professional .............................................. 33

4.9 Device Requirements Windows Mobile Standard ................................................... 34

4.10 Antivirus, known Applications, and OS features ......................................................... 35

4.11 Important to Remember for Installations and Upgrades ........................................... 36

5. Afaria 7 New Features......................................................................................................... 36

6. References .......................................................................................................................... 38

Afaria Technical Pre -requisities for iOS, Android, and BlackBerry

August 2012 1

1. Business Scenario This document offers an overview on the technical pre -requisites for Afaria implementations for

Mobile Device Management landscapes . These pre-requisites are advised to be checked prior to

the installation.

2. Background Information This document focuses on a single server environment only with Relay Server included in DMZ. In a

single server environment all Afaria components are installed on a same server. Relay Server is an

optional component but is highly recommended because of the security aspects. Relay Server

typically gets installed in a DMZ environment.

Following is a sample diagram of Afaria architecture:

For iOS

up to two weeks. There is an alternative procedure for a POC like setups. APNS certificate can be

issued by submitting a request to Sybase. This procedure is also cover ed in this document.

For Android landscapes, GCM (Google Cloud Messaging) registration is mandatory. The procedure

is included in this document.


August 2012 2

3. Step -by-Step Pre-requisites This document assumes that the reader has a technical know -how and understanding f or basic

Computer Networking and security centric architectural layers.

3.1 License and Media Download ...

Afaria license should already be available to initialize the installation. The software media link is

usually included in the license key email and shoul d be readily available. Customer may obtain a

trial license from Sybase .

Additionally, Afaria software media should be downloaded by Customer , to be placed locally on the

Afaria server and accessible from the Relay Server.

A typical email with License key would look like following (sent by Sybase Software Fulfillment

[mailto:[email protected]] ):

The software can also be downloaded from either of t he following methods:

1. http://www.sybasefiles.com/afaria7

2. By signing-up and logging on to http://frontline.sybase.com web-site or

3. By logging on to SAP Service Marketplace from the software download area,

https://service.sap.com/swdc

The screenshots to download Afaria from SAP Service Marketplace are as following:
mailto:[mailto:[email protected]]http://www.sybasefiles.com/afaria7http://frontline.sybase.com/https://service.sap.com/swdc


August 2012 3


August 2012 4


August 2012 5

Tip

Checks:

Has Afaria License been issued and available to use?

Has Software Media been downloaded with any latest updates released?

CAUTION

The download link may change and/or the procedure of obtaining the license key. Please check with your SAP contact for latest procedure in obtaining software as well as the license key.

3.2 Devices ...

Mobile devices, accordingly to the chosen device type(s) for the implementation, are to be made

available and handy for the provisioning part. Depending on the device type, Afaria client

application may need to be downloaded before provisioning from an applicable App Store or

Marketplace.

Tip

Checks:

Are mobile devices available?

List Operating Systems of these devices (device types):

How many devices of each type?

No of Phones (e.g. iPhone) of each type:

No of Tablets (e.g. iPad) of each type:


August 2012 6

Describe network type (e.g. 3G, Wi -Fi only, etc.):

3.3 Device Requirements ...

Following are device specific requirements covering Device type followed by supported Operating

System versions.

CAUTION

These requirements to be checked and verified prior to installation with latest Release Notes and System Requirement Notes from Fro ntline.

Afaria 7 Release Notes can be downloaded from here: http://frontline.sybase.com/support/fileDownload.aspx?ID=2389

Afaria 7 System Requirements Notes can be downloaded f rom here:

http://frontline.sybase.com/support/fileDownload.aspx?ID=2390

Out of the following, for individual OS version specific notes and instructions refer the latest

Release Notes.

3.3.1 iOS

Devices covered are iPhone, iTouch, iPad, and iPad 2.

Operating System versions: iOS 5.1, 5, 4.3, 4.2, 4.1, 4.0, 3.2.2, 3.1.3

3.3.2 Android

Devices covered are Android phones and tablets

Valid for package com.afaria.client (this is created by Afaria Client Create Device Installation

Program or installed from Google Play); Operating System versions: 4.0, x, 3.x, 2.3, 2.2.x

Valid for package com.afaria.client.samsungclient or com.afaria.client.samsung2client (installed

from Samsung App store or Google Play); Operating System versions: 4.0.x, 3.x, 2.3.x, 2.2.x

3.3.3 BlackBerry

Operating System versions: 7, 6, 5

3.3.4 Windows

Following 64 -bit Operating Systems are supported:

Windows 7

Windows Server 2008 R2
http://frontline.sybase.com/support/fileDownload.aspx?ID=2389http://frontline.sybase.com/support/fileDownload.aspx?ID=2390


August 2012 7

Following 32-bit Operating Systems are supported:

Windows 7

Windows Server 2008

Windows Vista Business

Windows Vista Enterprise

Windows Vista Home Ultimate

Windows Vista Business SP1, SP2

Windows Vista Enterprise SP1, SP2

Windows Vista Home Ultimate SP1, SP2

Windows XP SP3

Windows XP SP2

Windows Server 2003 R2 SP2

Windows Server 2003 SP2

Windows Server 2003

3.3.5 Windows CE

Windows CE 5.0

Windows CE 4.2

Windows CE 4.1

3.3.6 Windows Mobile Professional

Windows Mobile 6.5 Professional

Windows Mobile 6.5 Classic





Windows Mobile 5.0

Windows Mobile 5.0 Phone Edition

3.3.7 Windows Mobile Standard

Windows Mobile 6.5 Standard



August 2012 8


Windows Mobile 5.0

3.4 OS User for Installation ...

A domain user will be required to perform the installations. The user has to be added in the local

and UAC (User Access Control) settings to be turned off. This user

requirement applies to both, Afaria and Relay Server in DMZ. The Relay Server may not have a

domain user but a local Administrator user is must. The same user will be used to setup Afaria and

Relay Server services during the installation.

This user needs to be created on both, Afaria and Relay Server, as mentioned above, added to

1. Password no expiration

2. Logon as Service

Tip

Checks:

Is Afaria service user created?

List the user name:

Is Relay Server service user created?

List the user name:

Password(s):

3.5 Internet Access Internet access from Afaria and Relay Server is required for any missing patches; media download

directly from SAP download site. Direct internet access from Afaria server needed for Enrollment

Code procedure. In case of existing proxy layers the Afaria server to be included in the exceptions

list.

In-case if a Direct Internet access or an exception of the Afaria server is not possible, then as a

work -

Test of either of the above mentioned URL shortening services will be performed on -site, in-case of

an unsuccessful test the exceptions can then be made. The tests can be done from Afaria

own in the following screenshots.


August 2012 9


August 2012 10

For TinyURL:


August 2012 11

Tip

Checks:

Is internet access available from Afaria server?

Is it a direct connection or by using proxy?

Is internet access available from Relay server?

Is it a direct connection or by using proxy?

Is internet access available for consultant?

3.6 Server Operating System

3.6.1 Afaria Server Any of the following Windows 64 -bit operating systems:

Windows Server 2008 R2 Set Up Mode Full

Windows Server 2008 Standard Edition R2 with Service Pack 1

Windows Server 2008 Enterprise Edition R2 with Service Pack 1


August 2012 12

Windows Server 2008 Datacenter Edition R2 with Ser vice Pack 1

Recommendation

We recommend that you install your operating system on NTFS rather than FAT32.

3.6.2 Relay Server in DMZ Any of the following Windows 64-bit operating systems(RS v.12.x ):

Any of the following Windows 32 -bit operating systems:

ion with Service Pack 2

Or

Apache on Linux OS [Apache (Linux 32 -bit only ) RS v.12.x]

This server in DMZ typically will have an external and an internal IP address setup so that the

external devices can connect to this server from internet. In -case of having a single IP address, this

server will need to be made reachable from internal serve r(s), e.g. Afaria server

This external IP address, mapped with the Relay Server host in DMZ, should be set functional in

advance. In case of IIS, a typical test consultant may perform once IIS role is added to the relay

server is to execute this external IP address in a web browser and launch standard IIS page.

Tip

Checks:

List the Server Operating System for Afaria Server:

List the Server Operating System for Relay Server:

Important

Determine if you are using a local CA for Afaria server or an existing Enterprise CA. The CA specific requirements can be found in the latest Release Notes as well as the Afaria installation guide.

3.7 Afaria Database Afaria supports these databases in a production environment:

iAnywhere SQL Anywhere 12

iAnywhere SQL Anywhere 11


August 2012 13

Microsoft SQL Server 2008 R2 Enterprise Edition

Microsoft SQL Server 2008 R2 Standard Edition

Microsoft SQL Server 2008 R2 Datacenter Edition

Microsoft SQL Server 2008 R2 Parallel Data Warehouse Edition

Microsoft SQL Server 20 08 SP1 Enterprise Edition

Microsoft SQL Server 2008 SP1 Standard Edition

Microsoft SQL Server 2005 Enterprise Edition (SP1, SP2, SP3)

Microsoft SQL Server 2005 Standard Edition (SP1, SP2, SP3)

Collations for Afaria operations - Afaria requires case in sensitive collations, rather than binary

collations, such as:

(SQL Server 2008 R2) Latin1_General_CP1_CI_AS

(SQL Server 2005) SQL_Latin1_General_CP1_CI_AS

Regional time zone the Afaria database must be configured for the same time zone as the Afaria server components it supports.

Recommendation

We recommend installing Afaria Database on a separate server. While single server architecture can have Afaria server and the Database co-reside on the same server, we recommend it to be added to an existin g SQL clustered environment or be installed separately on a different server.

3.8 Afaria Self -Service Portal Server Self-Service Portal Server is deployed within intranet with a reverse proxy in DMZ such as Microsoft

Forefront Threat Management Gateway instance to accept traffic and pass it through to the Self -

Service Portal Server.

Afaria Self -Service Portal supports IIS 7.5 and must have an external URL (via TMG instance) with

using SSL.

Any of the following OS is supported:

Windows Server 2008 R2 Se t Up Mode Full

Windows Server 2008 Standard Edition R2 with Service Pack 1

Windows Server 2008 Enterprise Edition R2 with Service Pack 1

Windows Server 2008 Datacenter Edition R2 with Service Pack 1

Windows Server 2008 Web Server Edition R2 with Servic e Pack 1

Windows Server 2008 Standard Edition R2

Windows Server 2008 Enterprise Edition R2

Windows Server 2008 Datacenter Edition R2

Windows Server 2008 Web Server Edition R2


August 2012 14

Recommendation

We recommend that you install your operating system on NTFS rather than FAT32.

3.9 Hardware Requirements

3.9.1 Processor Any of the following processor or compatible types:

Intel Pentium 4 Processor processors at 2.0 GHz or higher

Intel Core Duo, Intel Core Quad, Intel Core 2 Duo or Intel Core 2 Quad processors at 1.8 GHz

or higher

The above is valid for Afaria, Relay, and Self-Service Portal Servers.

Tip

Checks

List the provisioned processors for the landscape:

3.9.2 Disk Space

3.9.2.1 Afaria Server

Minimum 40 GB free

3.9.2.2 Relay Server

Minimum 5 GB free

Tip

Checks

List the disk space available on Afaria server:

List the disk space available on Relay server:

3.9.3 RAM

3.9.3.1 Afaria Server

4 GB

Note

While the minimum RAM requirement is 1.5 GB in a distributed e nvironment where all individual components are installed on separate servers, although based on a sample setup recommended for up to 300 concurrent device sessions, we recommend minimum 4 GB RAM for a scenario where at least another Afaria co mponent is installed on Afaria Server, e.g. Afaria Administrative Console.

3.9.3.2 Relay Server

2 GB

afaria preriquisitos

Documents

sap products

registered trademarks

sap netweaver

sap company

system z10

system z9

system x

system i5