opensap mobile1 week 02 enterprise mobility

Week 2 Unit 1:The Benefits of a Platform

© 2013 SAP AG. All rights reserved. 2Public

Developing an application for an enterprise demands a lot.

These demands affect solution development as seen by different “personas”:

The developer

The admin

The end user

The Benefits of a PlatformMaking Our App ‘”Enterprise Ready”


The Benefits of a PlatformWhy Consider a Platform at All?

Analyst firm Gartner developed a “Rule of Three”.

1. Need to support three or more mobile apps

2. Need to support three or more mobile operating systems

3. Need to integrate with three or more back-end data sources

12

3


The Benefits of a PlatformWhat a Platform Provides

Support for multiple devices andmobile operating systems

Central administration/management

Support for integrating with back-endsystems

Developer support throughtools/SDKs/APIs/reusable services

Integration into enterprise securitysystems

Cloud support is sometimes possible


The Benefits of a PlatformMaking Our App “Enterprise Ready”: The Developer Viewpoint

Focused on TCD

Developer


The Benefits of a PlatformMaking Our App “Enterprise Ready”: The Admin Viewpoint

Focused on TCO

Admin


The Benefits of a PlatformMaking Our App “Enterprise Ready”: The End User Viewpoint

Focused on ease ofaccess and ease of use

User


FunctionalityDeveloper

OperationsAdmin

Ease of AccessUser

The Benefits of a PlatformMaking Our App “Enterprise Ready”: What a Platform Can Provide


Cloud-based mobile platform

Easy to sign up and get going

Built on highly scalablearchitecture

Intuitive, easy-to-use UI

Back-end connectivitythrough SAP HANA CloudConnector

Open, HTTP REST APIinterface

The Benefits of a PlatformSAP’s Cloud-Based Mobile Platform

Thank you

Contact information:

[email protected]


© 2013 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.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation orwarranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothingherein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and other countries.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.







Week 2 Unit 2:Enterprise Mobility EnablementServices


Enterprise Mobility Enablement ServicesEasing the Development and Administration of Our Mobile Application

E2E traceOn-boardingSecurityUsage reportingPerformance metricsData access

Value Add to Administrator

Core Services

SDKsOpen REST HTTP APIsE2E Logging/tracing

App Services

Value Add to Developer


Enterprise Mobility Enablement ServicesEasing the Administration of Our Application: Abstraction

Exposed services and reusablecomponents provide:

Decoupling of client and server

Abstraction of back-end services for appdevelopers

Platform can handle new applicationswithout complex refactoring

Developers can confidently build for theplatform regardless of enterprise

Administrators have ability to configurepackage applications


Enterprise Mobility Enablement ServicesEasing the Development of Our Application: SDKs and APIs

OData parserAPIs to parse and generate ODatamessages

Cache managementAPIs to store and access in-memoryOData objects

PersistenceAllows developer to store and retrievecontent securely on the device

SupportabilityLogging, tracing, and so on

ConnectivityHTTP(S) connectivity APIs


Enterprise Mobility Enablement ServicesEasing the Development of Our Application: REST APIs

REST HTTP APIs

GET

POST

PUT

DELETE

OData

Industry standard

XML/JSON


Enterprise Mobility Enablement ServicesSAP Mobile Platform and Applications

SMP and applications

Abstractions

What is an application?

Why is this useful?

Reporting

Security

Back-end definition


Enterprise Mobility Enablement ServicesSAP Mobile Platform and Applications

Creating a new application

Setting up connectivity

Defining security

Additional properties


Enterprise Mobility Enablement ServicesSAP Mobile Platform Administration

Thank you


[email protected]

Week 2 Unit 3:Security


SecuritySecuring the Application End to End: Authentication and Authorization

AuthenticationAm I who I say I am?

Both parties must trust each other.

Passwords, certificates, two-factor…

AuthorizationDo I have the right to do what I want to do?

Roles, access rights, profiles…


SecuritySecuring the Application End to End: Data on the Move

Securing the network connectionsSSL

HTTPS

Certificates

Network Edge, CA SiteMinder, SSO

WebReverse

Proxy

SMAgent

SMP Server

HTTPAuthLoginModule

SiteminderPolicyServer

SAPBackend

NW Java SAPSSO2

Generator

SM SessionCookie

BasicAuth

Valid()

SAP SSO2


SecuritySecuring the Application End to End: Data at Rest

Securing data at rest on deviceEncrypted stores

Data vaults

PINs

Usability!DataVault

PIN:


SecuritySecuring the Application End to End: SAP Mobile Platform, Cloud Version

HTTPS-only connectivity

Creating a security profileReusable definition

Defines authentication type– Basic– SAP SSO– SiteMinder SSO– Certificates

Secure on-premise back-endconnectivity


SecuritySecuring the Application End to End: SAP Mobile Platform, Cloud Version

Reuse security profiles

Modify existing profiles

Use Cloud Connector

Thank you


[email protected]

Week 2 Unit 4:Managing Access to the Data


Managing Access to the DataWhere is Our Data?

Where is the data?

What systems contain the data?

What form is the data in?

Spread across multiple systems?

What sort of access do we need?

Update? Read-only?

Cached? Live?

Define a suitable “consumption”model

Using OData to define the model


Managing Access to the DataHow do we get at the data?

Define the end points

Reusability

Associate security profiles

Usage and monitoring


Managing Access to the DataSAP Mobile Platform, Cloud Version

Defining a connection

Is it on-premise or over theInternet?

Do we need anonymousaccess?


Managing Access to the DataSAP Mobile Platform, Cloud Version: Cloud Connector

Cloud Connector

Routes data from on-premisesystem to SMP cloud

Connector runs in Linux system

Has its own Admin UI


Managing Access to the DataSAP Mobile Platform, Cloud Version: Cloud Connector (2)

You can create cloud connectionsto various back-end systems.

You can decide what resourcesare accessible on each system


Managing Access to the DataSAP Mobile Platform, Cloud Version: Cloud Connector (3)

You can monitor access to the systems

Check logs

Audit connections

Thank you


[email protected]

Week 2 Unit 5:User Onboarding


User OnboardingGetting End Users Up and Running

Granting access to a userBack end

Mobile infrastructure

Device setup

Deploying/installing the application

Configuring/provisioning theapplication

Authenticating as and when needed


User OnboardingGetting End Users Up and Running (2)

Getting users access to thesystems

Back-end access

Mobile platform


How do users obtain the application?

App stores

Enterprise stores

“Cradled” devices

Web




Configuring the device

VPN/MDM

Setting up connection details

Logging in


User OnboardingRemoving a User from the System

End of lifeUninstall

Remove access rights

De-allocate system resources


User OnboardingSAP Mobile Platform, Cloud Version, and Users: Managing Users

Viewing users

Viewing application connections

Removing connections and users


User OnboardingSAP Mobile Platform, Cloud Version, and Users: Registering

Client application code registers newconnection

HTTP REST APIPOST to Connections collection in SMP

X-SUP-APPCID returned

GET on connection retrieves latestproperties

PUT on connection can update theproperties

View connection in SMP Admin UI

Future business OData requestsshould use X-SUP-APPCID

Ensures requests are reported againstconnection


User OnboardingSAP Mobile Platform, Cloud Version, and Users: Registering (2)

You can try this out for yourself.

There are many REST clients thatwe can use for this purpose.

Chrome and Firefox have onesthat are nice and easy to use.

There are also standalone ones,such as WizTools.

Thank you


[email protected]

Week 2 Unit 6:Scaling Up


Scaling UpMeeting the Demands of a Growing System

Growing demandsMore users

More data

More applications

More back-end systems

More device types


Scaling UpMeeting the Demands of a Growing System (2)

More hardware

More powerful devices

Larger back-end systems

Faster and more capable networks

Better application design



Easy scale architecture

Client limitations

Back-end system impact andimplications



Reporting

Analytics

Thank you


[email protected]

Week 2 Unit 7:When Things Go Wrong


When Things Go WrongRoot Cause Analysis

Root cause analysis (RCA)

Tools to help analyze failures

Logging/tracing

Client-side SDK support

E2E tracing


When Things Go WrongThe Mobile Context

Complex E2E

Multiple components

• User-facing application and device

• Networks

• Middleware

• Backend Systems

• Security systems


When Things Go WrongPrevention is better than cure

Monitoring system health

Checking resource usage

Reporting

House keeping

Upgrading and patching


When Things Go WrongSAP Mobile Platform, Cloud Version: Logs and Traces

Logs give visibility into whathappened.

Logs can be viewed at varyinglevels of severity,

Logs cover different aspects ofthe system.

SAP Mobile Platform allowsadmins to alter log settingsto suit needs.


When Things Go WrongSAP Mobile Platform, Cloud Version: Logs and Traces (2)

Reporting gives visibility intooverall system performance.

Admins can see how systems areresponding under different loadcharacteristics.


When Things Go WrongSAP HANA Cloud Connector: Logs and Traces

Cloud Connector also provides:

• Logs and traces

• Audit trails

• Processor usage


When Things Go WrongClient and Back-end Logging

Clients can log additionaldata to assist debuggingand RCA.

Back-end systems alsoprovide logging ofinteractions.

Network diagnostic tools

O/S and other tools

Thank you


[email protected]

opensap mobile1 week 02 enterprise mobility

Documents

sap products

sap groupproducts

express permission of

publicthe benefits

affiliated companies

app enterprise ready

software products

end user viewpointfocused