SUP Arch Presentation

7/28/2019 SUP Arch Presentation

http://slidepdf.com/reader/full/sup-arch-presentation 1/21

Short Presentation Title

Speaker’s Name/Department (delete if not needed)Month 00, 2011

N O T E : ( D e l e t e t h i s e l e m e n t )

S a m p l e o f t i t l e s l i d e i m a g e .

S e e S AP I m a g e Li b r a r y f o r o t h e r

a v a i l a b l e i m a g e s .

Sybase Unwired Platform



© 2011 SAP AG. All rights reserved. 2

Address Complexity Across the Enterprise

Create

Connectheterogeneous

data sources Consumeheterogeneousmobile devices

Databases

Webservices

Softwareapplications

ControlDevice and server management and security

Management console

RIM (BB)

iOS(iPad / iPhone)

Windows

Mobilebusinessobjects

Workflows

Native

applications

Eclipse

SybaseUnwired Platform

Android Mobile




Sybase mobile SDK: mobile SDKs

Accelerate development of mobile apps

Device integrationGPS, address book, e-mail, tasks, phone,

calendar, browser, camera, barcode scanner, printer, and RFID

Reusable UI componentsUI controls, widgets, forms, and views

Configuration and

packagingPreferences, defaults, and app

constants

SupportabilityError handling, logging, tracing,

about, and versioning

SecurityOn-boarding support, RSA key

generation, and certificate-

handling

Connectivity Authentication (basic

authentication and single sign-on),asynchronous and synchronous

requests, notifications, progress

tracking, and error handling

Cache mangementRuntime data management, metadata, and

app data

PersistanceMetadata, app data, and encryption

Data parser Data protocol parsers

Target platforms:

iOS (iPhone and iPad) Android BlackBerry Windows Mobile (future)




Create various types of backendconnections with ease:

üApplications (SAP, Oracle,Microsoft, etc)

ü Databases (Sybase, DB2,Oracle, MS SQL, etc)

ü JDBC

ü REST Web Services

ü Web Services

Model DataGraphically


Connect to Data





Connect to Data

What is Mobile Business Object (MBO) ?Ÿ Graphical Mobile data model and synchronization behavior

Ÿ Abstraction Layer for mobile developer regarding backend connectivity

Ÿ Reusable item in various mobile application




Connect various device types

using the Sybase Unwired

Platform secure, efficient,

reliable transport


Consume





Application Development Patterns

Business Scenario

n Roles with complex interaction

n Occasionally connected (Offline)

n High degree of task specialization & data intensive

offline usage

Technical Patterns

n Self-contained: No browser/container App etc.

needed

n Large amount of local data possible

n Complex Business Logic can be covered

n Leverage device native capabilities

NATIVE Application CONTAINER ApplicationBusiness Scenario

n Roles with simple interaction

n Mostly connected (Online)

n Data capture, online lookups & workflow driven

processes

Technical Patterns

n Container app (Native / Device Browser - HTML5)

n Designed for Online

n Backend notifications

n Device Inbox Integration

Windows 32 iPhone iPad Android BlackBerry Windows Mobile





Development Paradigm

Definebackend data

model

Define MobileBusiness

Object model

Deploy MobileBusinessObjects to

SUP

GenerateDevice Object

code

DevelopDevice

Application

Test onEmulator and /

or Device

Platform Development Task Flow

Unwired Work Space Mobile

Business Object Development Tool

(Eclipse)

Unwired Work Space Device Application Designer Tool

(Eclipse)

Native Device Application Development Tools

Unwired WorkSpace Workflow Development Tool

BlackBerry Java iOs ObjectiveC

Windows Java

SE and C#

Windows

Mobile C#

BlackBerry-

JDE, Eclipse Plugin

Windows

Eclipse, Visual Studio

Windows Mobile

Eclipse, Visual Studio

iPhone / iPad

Xcode

Android*



SUP native application development




Basic application types

- native apps

With SUP you can create two application types

SUP

HWC

Apps

SUP

Native

Apps




SUP native applications

- overview

Best fit: High degree of task specialization and data intensive offline usage

Device Support

Ÿ BlackBerry (RIM Java ME)

Ÿ Windows and Windows Mobile (C#)

Ÿ iOS (Objective C)

Ÿ Android

Characteristics

Ÿ Self-contained: No browser/container App etc. needed

Ÿ Full Offline capabilities

Ÿ Large amount of local data possible

Ÿ Complex Business Logic can be covered

Ÿ Client coding required





- app development task flow

Data

modeling

Deploy

to SUP

Generate Develop app

using SUP API

Compile





- development tasks

1. Data modeling of backend sources

Ÿ Graphical tooling

Ÿ Multiple backends

2. Application developer uses data model

Ÿ Developer can focus on application development

Ÿ No need to work on data storage, persistance, synchronisation, etc

1

2




Basic application types

- native apps

With SUP you can create two application types

SUP

HWC

Apps

SUP

Native

Apps




SUP Hybrid Web Container applications

- overview

Best fit: Simple applications and workflows

Device Support

Ÿ BlackBerry

Ÿ Windows Mobile

ŸiOS

Ÿ Android

Characteristics

Ÿ Fast to develop and to deploy

Ÿ Offline capabilities

Ÿ No or minor application logic (JS)

Ÿ No native client coding required

Ÿ Base HTML workflow for cross platform compatibility





- creation task flow

Data

modeling

Deploy

to SUPCreate

WF base

design

Custom

HTML5 designSubmit

WF to

SUP





- creation tasks

1. Data modeling of backend data sources

Ÿ Graphical tooling

Ÿ Multiple backends

2. Workflow creation

Ÿ Creation of screenflows and functional base screens

Ÿ Optional HTML5 UI design and Java Scripting enhancements

1

Sybase Unwired

Pla orm

SyncEngine

Data Model

B a c k e

n d

C o n n e c t

WebService

SQL DB

SAP

BAPI (JCO)

DOEWebService

SUP runtime

WF repository

CDB

1 2



Summary

Native and HWC applications




Summary

- Hard facts

Technical differences

SUP native SUP HWC

Native development (Xcode, C#, Java, …) yes no

Mobile DB – offline capable yes no

Temporary offline capable (temp storage) yes yes

Full mobile hardware utilization (RFID, Barcode,

camera etc)

yes no

Eclipse based application builder no (as addon for

prototyping)

yes

Large data quantities yes no

Cross platform capable limited (DataModel + API)

yes




Summary

- Soft facts

Highlighting some soft facts to indicate possible use cases

SUP native SUP HWC

Implementation / development effort higher low

Time to production longer quick

Application usability higher lower Mobile application development skills needed yes no

Is used for pre-built apps (by SAP, Sybase, partners)yes yes



© 2011 SAP AG All rights reserved 21

Contact information:Saket Amraotkar

Documents

SUP Arch Presentation