Lesson: Business Example

Unit 2: Detailed Architecture and Runtime Lesson: Business Example Lesson: Data Staging Lesson: Data Retrieval and Extraction Lesson: Client Interaction Lesson: Device Rollout

Lesson: Data Distribution

Lesson: Compatibility Layer

SAP AG 2006

Architecture Intro
Mobile Device App1 App2 Mobile Client JVM DB
HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

SAP NetWeaver AS

Device queue Device queue

Device queue

Consolidated Data Store Data Orchestration Engine

Device Inventory

Mobile Administrator Integration Engine

RFC

RFC

HTTPS

Backend A
SAP AG 2006

Backend B

Backend C

Business Example Service Order Management

Two business objects need to be mobilized

Customers Service Orders

Customers are distributed via their region assignment If customer goes to device, assigned order should follow Certain attributes of Service Orders are changed by end user
CUSTOMERS

SERVICEORDERS

SAP AG 2006

Lesson: Data Staging

Unit 2: Detailed Architecture and Runtime Lesson: Business Example Lesson: Data Staging Lesson: Data Retrieval and Extraction Lesson: Client Interaction Lesson: Device Rollout

Lesson: Data Distribution

Lesson: Compatibility Layer

SAP AG 2006

Consolidated Data Store (CDS) and Data Objects

Mobile Device App1 App2 Mobile Client JVM DB
HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Central cache of mobile-relevant information CDS reduces load on back-end systems during

SAP NetWeaver AS

Device rollout

Device queue Device queue

Device queue

Data re-alignment
Device Inventory

Consolidated Data Store Data Orchestration Engine

Mobile Administrator Integration Engine

CDS structure is defined by data objects

RFC

RFC

HTTPS

Backend A
SAP AG 2006

Backend B

Backend C

Data Objects Terminology

A data object represents a business object that is relevant for a mobile scenario A data object has a hierarchical structure, each level in the hierarchy is called as node

Each node will be mapped to a schema, each field is called node attribute Links between nodes are called node associations A data object is assignedMobile to Business a software component version (SWCV) Object
Root Node

Every Node will have a schema linked to it

Child Node 1

Child Node 3

Child Node 2

SAP AG 2006

Data Object Categories

We distinguish between data objects exchanged with mobile devices and the DOE standard data objects - and data which is relevant for complex distribution patterns A standard data object can be

Upload only Download only or Bi-directional

SAP AG 2006

Consolidated Data Store (CDS)

Definition: Collection of tables which stores data object instances On activation of data object metadata, CDS tables are created and runtime code to update data object instances is generated

One table per data object node

Instance Instance

SAP AG 2006

Lesson: Data Retrieval and Extraction

Unit 2: Detailed Architecture and Runtime Lesson: Business Example Lesson: Data Staging Lesson: Data Retrieval and Extraction Lesson: Client Interaction Lesson: Device Rollout

Lesson: Data Distribution

Lesson: Compatibility Layer

SAP AG 2006

Backend Adapters
Backend Adapters retrieves and updates back-end data Currently only BAPI Wrappers are supported (more will follow) Backend Adapters connect data object node attributes with interface fields

SAP AG 2006

How/When are data object instances in CDS updated?

Mobile Device App1 App2 Mobile Client JVM DB
HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Three options:

Triggered by DOE: periodic pull of data Triggered by backend system: back-end system provides keys of changed object instances to DOE Back-end pushes instance or update to DOE

SAP NetWeaver AS

Device queue Device queue

Device queue

Consolidated Data Store

Data Orchestration Engine

Device Inventory

Mobile Administrator Integration Engine

RFC

RFC

HTTPS

Backend A
SAP AG 2006

Backend B

Backend C

At What Time are Device Queues Filled with Updates?

Mobile Device App1 App2 Mobile Client JVM DB
HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

CDS changes are tracked Extract service fills outbound queues with updates Three options for triggering extract service:

SAP NetWeaver AS

Device queue Device queue

Device queue

Consolidated Data Store Data Orchestration Engine

Device Inventory

CDS update trigger extract Job (periodical) Next device sync

Mobile Administrator Integration Engine

RFC

RFC

HTTPS

Backend A
SAP AG 2006

Backend B

Backend C

Demonstration - Outbound
Mobile Device App1 App2 Mobile Client JVM DB
HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Mobile Device App1 App2 Mobile Client JVM 4 DB

HTTPS File

Object instance is updated in back-end system

SAP NetWeaver AS

U
Device queue Device queue

Device queue

2 Consolidated Data Store Data Orchestration Engine

U
Mobile Administrator Integration Engine

RFC

RFC

HTTPS

Backend A
SAP AG 2006

Backend B

Backend C

Lesson: Client Interaction

Unit 2: Detailed Architecture and Runtime Lesson: Business Example Lesson: Data Staging Lesson: Data Retrieval and Extraction Lesson: Client Interaction Lesson: Device Rollout

Lesson: Data Distribution

Lesson: Compatibility Layer

SAP AG 2006

Mobile Client

Tasks of the mobile client:

Runtime environment for mobile components Manages mobile component registry Manages data access to local data base Tracks local data object instance changes Exchanges data with the DOE

SAP AG 2006

Demonstration - Inbound
Mobile Device App1 App2 Mobile Client JVM DB
HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Mobile Device U App1 App2 Mobile Client JVM 2 DB

HTTPS File

Object instance is updated on mobile device

SAP NetWeaver AS

U
Device queue Device queue

C
Device queue

4 Consolidated Data Store Data Orchestration Engine

U
Mobile Administrator Integration Engine

RFC

RFC

HTTPS

Backend A
SAP AG 2006

Backend B

Backend C

Lesson: Device Rollout

Unit 2: Detailed Architecture and Runtime Lesson: Business Example Lesson: Data Staging Lesson: Data Retrieval and Extraction Lesson: Client Interaction Lesson: Device Rollout

Lesson: Data Distribution

Lesson: Compatibility Layer

SAP AG 2006

What is Device Rollout?

Process of creating user IDs, devices and getting software and application data on physical devices It primarily deals with

Users (Our future end users on devices) Devices (Logical and physical ones) Mobile components (software on devices) Application data

Goal:

Highest possible automation to rollout a high number of devices in a given time frame Only few steps required by end user to have software and application data ready

SAP AG 2006

Device Inventory and Receiver Meta Model

Device inventory contains all information about devices Every device has certain attributes:

UserID Queue Platform Mobile Components Distribution Models

These attributes are modeled in the receiver meta model (RMM), each attribute can have one or multiple values Standard RMM can be enhanced

Attributes for administrative tasks Data distribution-relevant attributes

SAP AG 2006

How are Devices Created and Registered?

Mobile Device App1 App2 Mobile Client JVM DB
HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Settings User Server Physical ID Further attributes

SAP NetWeaver AS Device Device ID Mobile Components Physical ID Device Queue Number User(s) Distribution Model(s)

Enabled

Device queue Device queue

Device queue

Consolidated Data Store Data Orchestration Engine

Device Inventory

Mobile Administrator Integration Engine

RFC

RFC

HTTPS

Backend A
SAP AG 2006

Backend B

Backend C

Automatic (Logical) Device Creation

Device Inventory (based on RMM)
Device Name Device ID Physical ID User ID Device Type Queue Work Center ID

Device Inventory can be maintained

Manually Automatically using back-end information via Receiver Generation data object Initial load Updates

Employees (RecGen DO)

Device Name User ID Work Center ID . Employee ID

EMPLOYEES

. .

SAP AG 2006

Further Facts on Device Rollout

Device Profiles can be used to group

Mobile components Agent configurations

Distribution models

Hierarchy groups connect

Device Profiles Users ( Devices)

Setup Packages (with or without device relevant data) speed up device rollout
Mobile component archives, deployment status information and client logs are exchanged using data objects (Meta data is included in NW AS ABAP installation)

SAP AG 2006

Lesson: Data Distribution

Unit 2: Detailed Architecture and Runtime Lesson: Business Example Lesson: Data Staging Lesson: Data Retrieval and Extraction Lesson: Client Interaction Lesson: Device Rollout

Lesson: Data Distribution

Lesson: Compatibility Layer

SAP AG 2006

Data Distribution
Mobile Device App1 App2 Mobile Client JVM DB
HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Goal: Restrict data volume on mobile devices Decides which data object instances are relevant for which mobile device

SAP NetWeaver AS

Device queue Device queue

Device queue

Data Distribution
Device Inventory

Consolidated Data Store Data Orchestration Engine

Further information from backend can be integrated (e.g. territorial assignments of sales force representatives)
Manual assignments are also possible, but not recommended for large deployments

Mobile Administrator Integration Engine

RFC

RFC

HTTPS

Backend A
SAP AG 2006

Backend B

Backend C

Business Example (Data Distribution)

Two other business objects have influence on the data distribution

Employees Work centers

EMPLOYEES

WORKCENTERS

CUSTOMERS

SERVICEORDERS

SAP AG 2006

Data Object Design of Example Application

Data distributed to devices is modeled as standard data object Data for automatic creation of devices in the device inventory is modeled as receiver generation (RecGen) data object Data relevant for data distribution is modeled as subscription generation (SubGen) data object

Standard Data Object

Standard Data Object

SubGen Data Object

RecGen Data Object

Service Order
Association

Customer
Customer ID Name City . Region

Work Center
Work Center ID Region

Employees
Device Name User ID Work Center ID . Employee ID

Order ID Customer ID

. . .
SAP AG 2006

. .

. . .

. .

Service Order Management Example

Customers should be distributed according to region assignments Distribution Rule for Customer data object

Criteria field: Region Region = Work Center.Region Device Attribute Mapping: DI.Work Center ID = Work Center.Work Center ID

Service Order
Association

Customer
Customer ID Name City Address Region

Work Center (SubGen)

Work Center ID Region

Device Inventory (based on RMM)

Device Name User ID Work Center ID . Employee ID

Order ID Customer ID Long Text

. . .

. . .

. .

SAP AG 2006

Service Order Management Example

If a customer is distributed, the assigned orders should also go Distribution Dependency for Customer data object

Dependencies re-using associations:

Customer.Customer ID Service Order.Customer ID

Service Order
Association

Customer
+ Dependency

Work Center (SubGen)

Work Center ID Region

Device Inventory (based on RMM)

Device Name User ID Work Center ID . Employee ID

Order ID Customer ID

. . .
Following Data Object

Customer ID Name City . Address Region .

.
Leading Data Object

. . .

. .

SAP AG 2006

Distribution Models

A distribution model is meta data and consists of

Distribution Rules Distribution Dependencies Distribution Dependency Rules

Once a distribution model is assigned to one or many devices, device subscriptions (runtime data for data distribution) are created The process of creating/updating device subscriptions is called rule evaluation

SAP AG 2006

Device Subscriptions and Rule Evaluation Example

Service Order
Association

Customer
Customer ID Name City Address Region

Work Center (SubGen)

Work1242 Center ID Region NTH

Device Inventory (based on RMM)

WOLFG_LAPTOP1 Device Name HEGMANN User ID Work1242 Center ID . D026065 Employee ID

Order ID Customer ID Long Text

. . .

. . .

. .

If Customer.Region EQ NTH, go to device WOLFG_LAPTOP1

SAP AG 2006

Demonstration - Realignment
Mobile Device App1 App2 Mobile Client JVM DB
HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Mobile Device App1 App2 Mobile Client JVM 4 DB

HTTPS File

Distribution-relevant information is updated in back-end system DOE re-aligns business data accordingly

I D

SAP NetWeaver AS

I D
Device queue Device queue

I D
Device queue

2 Consolidated Data Store Data Orchestration Engine

U
Mobile Administrator Integration Engine

RFC

RFC

HTTPS

Backend A
SAP AG 2006

Backend B

Backend C

Data Distribution - Summary

Device subscriptions can be created automatically based on

Distribution Model(s) assigned to device Referenced SubGen data object instances Device Inventory attribute values

Important: Same data object instances can be distributed using different Distribution Models

SAP AG 2006

Lesson: Compatibility Layer

Unit 2: Detailed Architecture and Runtime Lesson: Business Example Lesson: Data Staging Lesson: Data Retrieval and Extraction Lesson: Client Interaction Lesson: Device Rollout

Lesson: Data Distribution

Lesson: Compatibility Layer

SAP AG 2006

How about applications built on existing releases?

Mobile Device App1 App2 Mobile Client JVM DB
HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Mobile Device App1 App2 Mobile Client JVM DB

HTTPS File

Compatibility layer for existing mobile business content

SAP NetWeaver AS
Mobile components still run

Device queue Device queue

Device queue

Data Distribution
SyncBO meta data can be imported + Generic Sync can be configured

Consolidated Data Store Data Orchestration Engine

Mobile Administrator Integration Engine

RFC

RFC

HTTPS

Backend A
SAP AG 2006

Backend B

Backend C

Existing BAPI Wrappers can be re-used

Compatibility Layer on the Mobile Client

Mobile Device App1 App2

Gen/Smart Sync/Pers Generic Sync Persistence Smart Sync

Application still uses old APIs

Converts API calls

Mobile Client
Data base contains data objects

JVM

DB
Data Object

SAP AG 2006

Unit Summary

You should now be able to:

Explain how information is staged in the consolidated data store and forwarded to device queues
Describe how information is retrieved from backend systems Name the role of the mobile client Tell the main tasks of device rollout

Depict how subscriptions are created

Describe the high-level concept of the compatibility layer

SAP AG 2006