SUP101 - Sybase Unwired Platforms Architectures and Technical Overview

Sybase Unwired Platform Architectures and Technical Overview

Student Guide

(Lecture Only)

Version 1.0

Strictly internal - for the use of SAP employees only


Student Guide

(Lecture Only)

Version 1.0 Part # SUP101-90-0153-10


Notice

Copyright © 2011 Sybase, Inc. All rights reserved.

Unpublished rights reserved under U.S. copyright laws. Sybase and the Sybase logo are trademarks of Sybase Inc., or its subsidiaries. ® indicates registration in the United States of America. SAP and the SAP logo are the trademarks or registered trademarks of SAP AG Germany and in several other countries. All other trademarks are the property of their respective owners.

Sybase Trademarks

Sybase, SYBASE (logo), ADA Workbench, Adaptable Windowing Environment, Adaptive Component Architecture, Adaptive Server, Adaptive Server Anywhere, Adaptive Server Enterprise, Adaptive Server Enterprise Monitor, Adaptive Server Enterprise Replication, Adaptive Server Everywhere, Advantage Database Server, Afaria, Answers Anywhere, AppModeler, APT Workbench, APT-Build, APT-Edit, APT-Execute, APT-Translator, APT-Library, ASEP, Avaki, Avaki (Arrow Design), Avaki Data Grid, AvantGo,Backup Server, BayCam, Bit-Wise, BizTracker, Certified PowerBuilder Developer, Certified SYBASE Professional, Certified SYBASE Professional Logo, ClearConnect, Client- Library, Client Services, CodeBank, Column Design, ComponentPack, Connection Manager, Convoy/DM, Copernicus, CSP, Data Pipeline, Data Workbench, DataArchitect, Database Analyzer, DataExpress, DataServer, DataWindow, DataWindow .NET, DB-Library, dbQueue, Dejima, Dejima Direct, Developers Workbench, DirectConnect Anywhere, DirectConnect, Distribution Director, Dynamic Mobility Model, e-ADK, E-

Anywhere, e-Biz Integrator, E-Whatever, EC Gateway, ECMAP, ECRTP, eFulfillment Accelerator, EII Plus, Electronic Case Management, Embedded SQL, EMS, Enterprise Application Studio, Enterprise Client/Server, Enterprise Connect, Enterprise Data Studio, Enterprise Manager, Enterprise Portal (logo), Enterprise Work Architecture, Enterprise Work Designer, Enterprise Work Modeler, eProcurement Accelerator, eremote, Everything Works Better When Everything Works Together, EWA, ExtendedAssist, Extended Systems, ExtendedView, Financial Fusion, Financial Fusion (and design), Financial Fusion Server, Formula One, Fusion Powered e-Finance, Fusion Powered Financial Destinations, Fusion Powered STP, Gateway Manager, GeoPoint, GlobalFIX, iAnywhere, iAnywhere Solutions, ImpactNow, Industry Warehouse Studio, InfoMaker, Information Anywhere, Information Everywhere, InformationConnect, InstaHelp, Intelligent Self-Care, InternetBuilder, iremote, iScript, Jaguar CTS, jConnect for JDBC, KnowledgeBase, Logical Memory Manager, lrLite, M2M Anywhere, Mach Desktop, Mail Anywhere Studio, Mainframe Connect, Maintenance Express, Manage Anywhere Studio, MAP, M-Business Anywhere, M- Business Channel, M-Business Network, M-Business Suite, MDI Access Server, MDI Database Gateway, media.splash, Message Anywhere Server, MetaWorks, MethodSet, mFolio, Mirror Activator, ML Query, MobiCATS, MySupport, Net-Gateway, Net-Library, New Era of


Networks, Next Generation Learning, Next Generation Learning Studio, O DEVICE, OASiS, OASiS logo, ObjectConnect, ObjectCycle,

OmniConnect, OmniQ, OmniSQL Access Module, OmniSQL Toolkit, OneBridge, Open Biz, Open Business Interchange, Open Client, Open

ClientConnect, Open Client/Server, Open Client/Server Interfaces, Open Gateway, Open Server, Open ServerConnect, Open Solutions, Optima++, Partnerships that Work, PB-Gen, PC APT Execute, PC DB-Net, PC Net Library, Pharma Anywhere, PhysicalArchitect, Pocket PowerBuilder, PocketBuilder, Power++, Power Through Knowledge, power.stop, PowerAMC, PowerBuilder, PowerBuilder Foundation Class Library, PowerDesigner, PowerDimensions, PowerDynamo, Powering the New Economy, PowerScript, PowerSite, PowerSocket, Powersoft, PowerStage, PowerStudio, PowerTips, Powersoft Portfolio, Powersoft Professional, PowerWare Desktop, PowerWare Enterprise, ProcessAnalyst, Pylon, Pylon Anywhere, Pylon Application Server, Pylon Conduit, Pylon PIM Server, Pylon Pro, QAnywhere, Rapport, Relational Beans, RepConnector, Report Workbench, Report-Execute, Replication Agent, Replication Driver, Replication Server, Replication Server Manager, Replication Toolkit, Resource Manager, RFID Anywhere, RW-DisplayLib, RW-Library, SAFE, SAFE/PRO, Sales Anywhere, SAP, SAP Business Suite, Sybase Unwired Platform, Sybase Workflow for SAP Business Suite, SAP Mobile Sales CRM, Search Anywhere, SDF, Search Anywhere, Secure SQL Toolset, Security Guardian, ShareSpool, Sharelink SKILS, smart.partners, smart.parts, smart.script, SOA Anywhere Trademark,SQL Advantage, SQL Anywhere, SQL Anywhere Studio, SQL Code Checker, SQL Debug, SQL Edit, SQL Edit/TPU, SQL Modeler, SQL Remote, SQL SMART, SQL Toolset, SQL Station, SQLJ, Stage III Engineering, Startup.Com, STEP, SupportNow, S.W.I.F.T. Message Format Libraries, Sybase Central, Sybase Client/Server Interfaces, Sybase Development Framework, Sybase Financial Server, Sybase Gateways, Sybase IQ, Sybase Learning Connection, Sybase MPP, SyberLearning LIVE, Sybase SQL Desktop, Sybase SQL Lifecycle, Sybase SQL Workgroup, Sybase Synergy Program, Sybase Virtual Server Architecture, Sybase User Workbench, SybaseWare, Syber Financial, SyberAssist, SybFlex, SybMD, SyBooks, System 10, System 11, System XI (logo), SystemTools, Tabular Data Stream, The Enterprise Client/Server Company, The Extensible Software Platform, The Future Is Wide Open, The Learning Connection, The Model For Client/Server Solutions, The Online Information Center, The Power of One, TotalFix, TradeForce, Transact-SQL, Translation Toolkit, Turning Imagination Into Reality, UltraLite, UltraLite.NET, UNIBOM, Unilib, Uninull, Unisep, Unistring, URK Runtime Kit for UniCode, Unwired Accelerator, Unwired Orchestrator,Viafone, Viewer, VisualWriter, VQL, WarehouseArchitect, Warehouse Control Center, Warehouse Studio, Warehouse WORKS, Watcom, Watcom SQL, Web Deployment Kit, Web.PB, Web.SQL, WebSights, WebViewer, XA-Library, XA-Server, XcelleNet, and

_X_P _S_e_r_v_e_r_, _X_T_N_D_C_o_n_n_e_c_t_, _X_T_N_D_A_C_C_E_S_S_, are trademarks of Sybase, Inc. or its subsidiaries.

Restricted Rights Legend

Use, duplication or disclosure by the Government is subject to restrictions set forth in subparagraph (c)(1)(ii) of DFARS 52.227-7013 for the DOD and as set forth in FAR 52.227-19(a)–(d) for civilian agencies.

Sybase, Inc., One Sybase Drive, Dublin, CA 94568

How to Use This Guide

Student Guide


This course material is a companion to the Sybase Unwired Platform Architectures and Technical Overview course. The Sybase Unwired Platform Architectures and Technical Overview is divided into 8 modules. Each module contains:

The objectives for the module

A list of topics for the module

Supporting information that follows the flow of the class

Pre- and Post-Assessment questions


2011 Sybase, Inc.

Sybase Unwired Platform Architectures and Technical Overview – Version 1.0

i


Course Objectives

Objectives

After completing this course, you should be able to:

Familiarize yourself with the Sybase Unwired Platform (SUP)

Understand the mobility terminology, concepts, and architectures

Learn how the Co-Innovation Architecture work to integrate Sybase Unwired Platform (SUP) and SAP Business Suite products

Familiarize yourself with the development models for native and workflow mobile applications

Understand the underlying technology architectures used in the Sybase SAP Mobile Sales and Sybase SAP Mobile Workflow for SAP Business Suite products

Understand the development of custom mobile business applications using:

Device Application Designer

Generated Code

A Combination of the DAD and Generated Code


Define the Administration Features of the Sybase Control Center

Describe Afaria Architecture and Requirements

ii


2011 Sybase, Inc.


Audience

This course is designed for:

Mobility Architects

Project Managers and Executives

Consultants

Mobile Application Developers

Anyone who is currently evaluating a mobility solution for his/her organization

Prerequisites

To benefit from this course, you should already have a:

General understanding of mobility technologies


2011 Sybase, Inc.


iii


Course Description

Topics

In this course, you will cover these topics:

Module 1: Introduction to Mobility and Sybase Unwired Platform

Module 2: Sybase Unwired Platform Mobility Architectures

Module 3: Sybase Unwired Platform Native Applications

Module 4: Sybase Unwired Platform Mobile Workflow Applications

Module 5: SAP Mobile Sales CRM Technical Overview

Module 6: Sybase Mobile Workflow for SAP Business Suite Technical Overview

Module 7: Administering Sybase Unwired Platform Environments

Module 8: Afaria Device Management Architecture and Overview

Appendixes

This Student Guide includes 1 appendix.

Appendix A, “Answers Pre/Post Assessments,” contains the correct responses to the assessment questions in each module.


iv


2011 Sybase, Inc.


Icon Samples

Lab – Perform lab exercise

Debriefing – Lab debriefing questions

Caution – Possible damage to equipment, data, or software

Try It – A hands-on opportunity to try out a task or procedure

Note – Information that expands on or supplements the information in the main text


Critical Note – Very important piece of information that should be read

Windows – Information specific to the Windows platform

UNIX – Information specific to the UNIX platform

Tip – Tips on completing a given task

Version Note - Feature is new to the current product version

Version Note - Feature not available in earlier product version

2011 Sybase, Inc.


v


Version Note - Feature is available and behaves the same across versions

Version Note - Feature is available but behaves differently across versions

Version Note - Feature available in version 15.0 only

Version Note - Miscellaneous information about the version should be noted


vi


2011 Sybase, Inc.


Reporting Bugs, Problems, Quality Issues or Questions about the Courseware

Reporting Bugs, Problems or Questions about the Courseware

The Curriculum Development group at Sybase values your input. Your comments and feedback are vital to our efforts to continuously improve Sybase courses.

Please use the following e-mail alias to report bugs, document problems, offer comments and suggestions, or ask questions related to any Sybase course materials. Using this alias will ensure that your communication is logged and monitored properly.

Send e-mail to courseware_input@sybase.com.

Please be specific when reporting. For example, provide the course code and version for the course you have taken. The course code for this course is SUP101, version 1.0.

Client Satisfaction Policy

Your satisfaction with the quality of our products and services is very


important to us. We understand that satisfied clients are essential to the

future of our business.

If at any time you are not satisfied with the services we provided or if you have a suggestion for improvement, please let us know. Contact us by writing to the Consulting or Education Manager at the Professional Services location providing services to you. We will respond within two business days either with a resolution or with an explanation of how long our follow up is likely to take and who is responsible for it. If the matter is not resolved to your satisfaction, please email the Professional Services Quality Manager at svc_qms@sybase.com. The Professional Services Quality Manager will contact you and will take responsibility for resolving the matter.

2011 Sybase, Inc.


vii



viii


2011 Sybase, Inc.

Sybase Unwired Platform Architectures and Technical Overview Student Guide

Module 0: Course Introduction


Introduction to Mobility

1-4

Sybase Unwired Platform Licensing

1-12

Installation Requirements

1-21



Introduction to Sybase Unwired Platform

Sybase Unwired Platform Landscapes

2-4

2-15

Production Environment Considerations

2-32

Architecture Case Study Sybase Co-Innovation Architecture

2-47

2-59


Introduction to the Unwired Workspace (Eclipse) Setting Up Connections Native Mobile Application Development

3-4

3-19

3-26


Workflow Introduction Workflow Screen Components Workflow Application Development Workflow Deployment

4-4

4-11

4-20

4-29


Overview of SAP CRM 7 Sybase Unwired Platform Integration - DOE Connector SAP Mobile Sales Application Architecture Configuring SAP CRM Components

5-4

5-18

5-27

5-35

2011 Sybase, Inc.


TOC - 1

Student Guide

Customization Deploying Mobile Sales CRM to Devices

5-47

5-86


Sybase Mobile Workflow for SAP Business Suite Overview Sybase Mobile Workflow for SAP Customization

6-4

6-13


Architecture Introduction to the Sybase Control Center Workflow Administration Device Management Monitoring

7-4

7-15

7-32

7-38

7-47


Introduction Afaria Architectural Components

8-4

8-8

Afaria

Managers

8-21

Device Lifecycle

8-34


TOC - 2


2011 Sybase, Inc.

Sybase Unwired Platform Architectures and Technical Overview Module 0: Course Introduction Version 1.0

Sybase Unwired Platform Architectures and

Technical Overview

Module 0:

Course Introduction

Copyright © 2011 Sybase, Inc

All rights reserved.

Unpublished rights reserved under U.S. copyright laws. Sybase, and Sybase logo are trademarks of Sybase Inc., or its subsidiaries. ® indicates registration in the United States of America. SAP and the SAP logo are the trademarks or registered trademarks of SAP AG Germany and in several other countries. All other trademarks are the property of their respective owners.


0 - 1

©2011 Sybase, Inc.


Course Description

Demonstrates the architectures and capabilities of Sybase Unwired Platform Covers the Co-Innovation Architecture used in the solutions “SAP Mobile Sales CRM” and “Sybase Mobile Workflow for SAP Business Suite” Goals:

Gain familiarity with Sybase mobility terminology, concepts, and architectures, as well as implementation scenarios Learn the core Sybase Unwired Platform product and how the Co- Innovation Architecture works to integrate Sybase Unwired Platform with SAP Business Suite products

Sybase Product Release

This course is based on the Sybase Unwired Platform 1.5.5 product release

0 - 2


0 - 2

©2011 Sybase, Inc.


Course Objectives

During the course of this class, you will be able to:

Describe the mobility terminology, concepts, and architectures Understand and describe Sybase’s key mobility architectures and ancillary architecture components Familiarize yourself with the Sybase Unwired Platform (SUP) and Sybase Control Center Describe the underlying architectures for Sybase Unwired Platform Mobile Native and Workflow Applications Understand the architecture and implementation of the SAP Mobile Sales CRM and Sybase Mobile Workflow applications Describe the roles of Afaria device management and Sybase Relay Server

0 - 3


0 - 3

©2011 Sybase, Inc.


Target Audience and Prerequisites

Target Audience:

Mobility Architects Project Managers and Executives Consultants Mobile Application Developers Anyone who is currently evaluating a mobility solution for his/her organization

Pre-requisites:

None

0 - 4


0 - 4

©2011 Sybase, Inc.


Course Outline

Module 1: Introduction to Mobility and Sybase Unwired Platform Module 2: Sybase Unwired Platform Mobility Architectures Module 3: Sybase Unwired Platform Native Applications Module 4: Sybase Unwired Platform Mobile Workflow Applications Module 5: SAP Mobile Sales CRM Technical Overview

0 - 5

Continued …


0 - 5

©2011 Sybase, Inc.


Course Outline

Module 6: Sybase Mobile Workflow for SAP Business Suite Technical Overview Module 7: Administering Sybase Unwired Platform Environments Module 8: Afaria Device Management Architecture and Overview

0 - 6


0 - 6

©2011 Sybase, Inc.


Demonstrations

There are four recorded demonstrations available on the Student CD component of this lecture-only course Instructor Led Delivery:

If this courseware is being used for a live delivery of the content, demonstrations of the module content will be performed by the instructor There is no formal lab workbook with this course

SyberLearning OnDemand:

The SyberLearning OnDemand version of this course contains all instructor demonstrations in recorded format

0 - 7


0 - 7

©2011 Sybase, Inc.


Certification and Curriculum Path

Sybase Unwired Platform Developer and Administration Certifications and Certification Preparation exams will be available in 2012 Sybase Unwired Platform Curriculum Paths include:

A - Sybase Unwired Platform Developer (certification included) B - Sybase Unwired Platform Administrator (certification included) C - Sybase SAP Mobile Sales Developer Customization (no certification included) D - Sybase Mobile Workflow for SAP Business Suite Developer Customization (no certification included)

0 - 8


0 - 8

©2011 Sybase, Inc.

Sybase Unwired Platform Architectures and Technical Overview Module 1: Introduction to Mobility and Sybase Unwired Platform Version 1.0


Technical Overview

Module 1:

Introduction to Mobility and Sybase

Unwired Platform





1 -

1

©2011 Sybase, Inc.


Module Pre-Assessment

1 - 2

There are no pre-assessment questions in this module


1 - 2

©2011 Sybase, Inc.


Module Objectives

Upon completion of this module, you should be able to:

Define general mobility terms and concepts Understand basic concepts around mobility and Sybase Unwired Platform Understand the Sybase Unwired Platform licensing methodology Describe some key prerequisites and post installation tasks for Sybase Unwired Platform

1 - 3

This course is based on Sybase Unwired Platform 1.5.5 release.


1 - 3

©2011 Sybase, Inc.


1 - 4

MODULE _T_O_P_I_C_S TOPICSMODULE





1 - 4

©2011 Sybase, Inc.


Mobility Use Pyramid

Mobility enterprise used by task and business users to executives and line of business managers:

1 - 5

Dashboards

Email

Execs

Contacts

Approvals

Line of Business

Managers

Approval

Requests

Calendars

Field

Service

CRM

Task & Business Users

Time &

Scheduling

Expense

& Dispatch


1 - 5

©2011 Sybase, Inc.


Mobile Enterprise Challenges

Enterprises encounter a variety of challenges when mobilizing applications

Different

kinds of

devices/OS

Diverse

Data source

networks

heterogeneity

Sybase

Next-Generation

Managing

Mobility

Greater

and securing

ease of

Architecture

devices

development

Data

Provisioning

availability

and securing

on the

applications

device

Partitioning mobile data Synchronizing data and transaction management Access issues such as being outside the firewall, bandwidth and connectivity Support for numerous types

of devices Securing data Managing devices Application change management

1 - 6


1 - 6

©2011 Sybase, Inc.


Key to a Mobility Solution

Enterprise

Data

Changes

Must offer seamless

integration to a variety

of back-end data

sources

1 - 7

Consistent

Development

Platform

Enterprise-grade development environment must leverage existing skills and technologies

Device

Technology

Changes

Should enable rapid deployment of mobile applications across multiple device types

Back-end data sources can be databases, Web Services (SOAP or REST), and platforms


such as SAP.

Developers who have knowledge of Eclipse (for MBO development only), Visual Studio

or Objective-C should be able to use that knowledge in the building of mobile applications. Should follow the Design Once Deploy Anywhere ( DODA ) paradigm. Can design the application one time and deploy it to multiple devices.

1 - 7

©2011 Sybase, Inc.


Enterprise Information System (EIS) Data

Data residing in enterprise backend systems such as:

Enterprise databases Web Services REST Services SAP ERP and CRM Systems

1 - 8


1 - 8

©2011 Sybase, Inc.


SAP Products

SAP Business Suite

Enables companies to perform essential, industry-specific, and business-support processes with modular solutions that are designed to work with other SAP and non-SAP software

SAP Customer Relationship Management (SAP CRM)

Multichannel application supporting all business lines across:

Marketing Sales Service and customer interaction channels such as the Internet, mobile clients, and interaction centers

1 - 9

Continued …


1 - 9

©2011 Sybase, Inc.


SAP Products

Netweaver Mobile (DOE)

Technology of the SAP NetWeaver platform group that is currently used to enable Business Suite services for mobile consumption

Mobile CRM Mobile Workflow Custom applications

SAP Mobile Gateway

Add-on to the DOE that allows you to develop client framework services for enabling seamless offline/ online access to back-end components on mobile devices

1 - 10

Continued …


1 - 10

©2011 Sybase, Inc.


SAP Products

ESDMA – Entity Source Definition for Mobile Applications

An XML document, very much like an WSDL (Web Services Description Language) Design time artifact Generated and managed as a software artifact in the Mobile Gateway Downloaded from the Mobile Gateway’s ESDMA browser (SAP)

Sybase DOE-Connector

Provides abstraction and optimization layer between DOE and Sybase Unwired Platform Provides ESDMA import capabilities to generate necessary inbound and outbound interfaces

1 - 11


1 - 11

©2011 Sybase, Inc.






1 - 12


1 - 12

©2011 Sybase, Inc.


License Categories and Mapping

Personal Developer (PD)

Enterprise Developer (ED)

Enterprise Server (EE)

1 - 13

Development

Testing/

Qualification

Production

Can use both the ED and EE editions for the Qualification mapping. Can use the


Enterprise Server (EE) with DT license for testing.

EE is also known as the “Enterprise Deployment Edition”.

Most enterprise customers have required an Enterprise Developer server for development purposes. Enterprise application development teams typically consist of more than 5 developers, requiring connections to the Development instance of the Sybase Unwired Platform server.

1 - 13

©2011 Sybase, Inc.


Personal Developer License

Sybase Unwired Platform single install for developers

Individual license generated per developer, based on Host ID of developer machine Each developer machine MUST have a separate license key, so be sure to order enough developer licenses 5 clients (devices) embedded in license key for testing

Features

Includes complete product: Sybase Unwired Platform server, Administration tool and developer tooling

1 - 14


1 - 14

©2011 Sybase, Inc.


Enterprise Developer License Details

Single Unwired Server for development teams

For use as central development server that is needed for project development License generated for server is based on Host ID of machine on which server is installed 20 clients (devices) embedded in license for testing No limit to number of developers who can deploy code to the server

Each developer must have one Personal Developer license to install tooling on their personal machine

Features

Includes complete product: Sybase Unwired Platform server, Administration tool and developer tooling

1 - 15


1 - 15

©2011 Sybase, Inc.


Enterprise Server License Details

Sybase Unwired Platform Deployment / Production License

License is based on host ID of machine(s) on which server is installed Both cores and seats can be divided amongst multiple machines

Features

Includes Sybase Unwired Platform Server and Administration tool

1 - 16


1 - 16

©2011 Sybase, Inc.


SAP Mobile Solutions Licensing

License Requirements include:

Sybase Unwired Platform Pre-built applications

1 - 17

Sybase Mobile Sales for SAP CRM Sybase Mobile Workflow for SAP Business Suite

Mobile Device

Mobile App

(Mobile Sales or

Workflow)

(License applies)

SUP Client

(License applies)

Unwired

SAP

Server

(SAP licensing)

(License applies)


1 - 17

©2011 Sybase, Inc.


OEM Licensing for Partners

If a partner develops a pre-built application based on Sybase Unwired Platform , a Sybase Unwired Platform OEM license is necessary

Enables the partner to sell the solution for a single price as a stand alone product

Partner

Solution

SUP Server

(License applies)

Mobile Device

Custom Partner

Application

(License applies)

SUP Client

(License applies)

SAP

(SAP licensing)

1 - 18


1 - 18

©2011 Sybase, Inc.


Client Licensing Options

Client Application License Types:

Single application instance client license Multiple application instance client license

Perpetual Client License

Pay once for the license, then you can use it “indefinite” in context of the license contract Support contracts need to be purchased separately

Subscription Client License

Annual up front fee Support is included in the subscription price

Check with your Sales Representative for license fee details License server is required to run licensing across a cluster

1 - 19


1 - 19

©2011 Sybase, Inc.


Licensing Scenario

A production server license is needed for each node of a redundant server setup

1 - 20

Relay Server is royalty free

Server Tier

Data Tier

Clustered

Load Balanced

Relay Server

CDB Servers

SUP Servers

Check with your Sales Representative for the license requirements for the Data Tier in this


type of scenario.

1 - 20

©2011 Sybase, Inc.






1 - 21


1 - 21

©2011 Sybase, Inc.


Deployment Edition Requirements

Microsoft Windows 2003 Server, Standard or Enterprise Edition, with Service Pack 2 (64-bit) Microsoft Windows 2008 and 2008 R2, Server Standard or Enterprise Edition (64-bit) Microsoft Windows Server 2008, temporarily turn off User Account Control (UAC) for the installation Sybase Control Center (SCC) requirements:

Adobe Flash Player 9.0.124.0 or greater Internet Explorer 6.0 or later

Minimum of 4GB RAM Installation of Adaptive Server Enterprise and Unwired Platform on the same server is not supported

1 - 22

64-bit Windows 2008 Server support only – Must install the Afaria product on a 32-bit OS


machine.

Other prerequisites:

.NET Framework 2.0 with SP2 Microsoft Windows Installer 3.1 or later Visual C++ Runtime (both 2005 and 2008 with SP1)

The installer checks for these and installs them if they are not on the machine

1 - 22

©2011 Sybase, Inc.


ED and PD Edition Prerequisites

Windows Operating Systems

XP with SP2 Microsoft Windows 7 (32- or 64-bit) Vista Business and Enterprise 2003 with SP2 2008 Server

Approximately 3GB hard drive space

Required for Unwired Server and Unwired Workspace components

Minimum of 4GB RAM Can have Eclipse 3.5.1 and JDK 1.6 already installed, or choose to install them as part of the Sybase Unwired Platform installation

1 - 23

Continued …

Windows 2008 Server (both 32/64-bit supported except for Afaria portion which is 32-bit


only).

1 - 23

©2011 Sybase, Inc.


ED and PD Edition Prerequisites

If necessary, remove the JAVA_TOOL_OPTIONS environment variable before Sybase Unwired Platform installation For Windows Vista and Server 2008, temporarily turn off User Account Control (UAC) for the installation of Sybase Unwired Platform Sybase Control Center (SCC) requirements:

Adobe Flash Player 9.0.124.0 or greater Internet Explorer 6.0 or later

Other prerequisites:

.NET Framework 2.0 with SP2 Microsoft Windows Installer 3.1 or later Visual C++ Runtime (both 2005 and 2008 with SP1)

The installer checks for these and installs them if they are not on the machine

1 - 24


1 - 24

©2011 Sybase, Inc.


Apple and RIM Support

Apple:

iPad iOS 3.2 iPhone iOS 3.1.3 - 4.1 iPod touch iOS 3.1.3 - 4.1

RIM BlackBerry:

For replication-based synchronization [RBS] only—Mobile Workflow Application and message-based synchronization [MBS] not available for the BlackBerry device platform OS 4.2.1 on Blackberry 8800 (Object API only) OS 4.2.2 on Blackberry Curve 8300 (Object API only) OS 4.6.0 on Blackberry Pearl Flip 8220 and Blackberry Bold 9000 (Object API only) OS 4.6.1 on Blackberry Curve 8900 OS 4.7.0 on Blackberry Storm 9530 OS 5.0 on BlackBerry Storm 2 (9550), BlackBerry Bold 2 (9700), BlackBerry Tour 9630, and BlackBerry Curve 8530

1 - 25


1 - 25

©2011 Sybase, Inc.


Supported Application Dev. Environments

BlackBerry

Java Plug-in for Eclipse version 1.1 Java Development Environment (JDE) 4.6.1, 4.7, or 5.0

iPhone

MacOS 10.6 (Snow Leopard), Xcode 3.2.4 (MacBook or iMac). iOS SDK 4.1

Windows Mobile

Visual Studio 2008, Microsoft .NET Compact Framework 3.5

Windows

Visual Studio 2008, Microsoft .NET Framework 3.5 Java Standard Edition (SE) 6.0

1 - 26


1 - 26

©2011 Sybase, Inc.


Sybase Unwired Platform Services

Several Windows services are created during the installation:

Advantage Database Server Afaria Database (even if you did not install Afaria) OpenDS (Open Source LDAP Server) Sybase Messaging Service Sybase Unified Agent 3.0 – Required by the SCC Sybase Unwired Platform (Consolidated Database) Sybase Unwired Platform (Sample Database) Sybase Unwired Platform (Unwired Server)

1 - 27

Remember, the choice to auto-start these services was made during the installation.


1 - 27

©2011 Sybase, Inc.


Key Production Tasks

In a production environment, you need to configure the following where applicable:

Authentication methods Encrypting synchronization via SSL Configuring connection pools Creating / managing clusters Relay Server Afaria

1 - 28

Assuming that a Relay Server will be used in production, then a Relay Server is often


included in a development environment. It is always included in an Enterprise quality Test

environment.

Note that if not using HA, then a Relay Server is optional. If using MBS, then even for HA, a Relay Server is optional if an existing load balancer (i.e.: F5) is already in place.

1 - 28

©2011 Sybase, Inc.


Recorded Demonstrations


See “SUP101_Mod1_Demonstration.mp4” on your Student

1 - 29

CD


1 - 29

©2011 Sybase, Inc.


Module Summary

During the course of this module, you have learned:

General mobility and SAP terms and concepts Basic concepts around mobility and Sybase Unwired Platform Sybase Unwired Platform licensing methodology Key prerequisites and installation requirements for Sybase Unwired Platform

1 - 30


1 - 30

©2011 Sybase, Inc.


Module Post-Assessment

1. Name at least three challenges that most enterprises face with their mobility strategies.

2. What is the SAP Mobile Gateway?

3. Name the three license types for Sybase Unwired Platform.

1 - 31

See Appendix A for Pre- and Post-Assessment answers


1 - 31

©2011 Sybase, Inc.



1 - 32

©2011 Sybase, Inc.

Sybase Unwired Platform Architectures and Technical Overview Module 2: Sybase Unwired Platform Mobility Architectures Version 1.0


Technical Overview

Module 2:

Sybase Unwired Platform Mobility

Architectures





2 - 1

©2011 Sybase, Inc.



1. Sybase Mobile Sales is delivered with the core Sybase Unwired Platform product.

2. Describe a native mobile application.

3. True/False: The Sybase Unwired Server requires a third- party administration module.

2 - 2

See Appendix A for answers to Pre- and Post-Assessments.


2 - 2

©2011 Sybase, Inc.


Module Objectives


Define the general architectures of Sybase Unwired Platform and its components Understand environment components and support provided with the platform Describe different implementations of Sybase Unwired Platform Understand the Sybase Co-Innovation Architecture, JCo Connector and Data Orchestration Engine (DOE) components Understand Data Change Notification (DCN)

2 - 3


2 - 3

©2011 Sybase, Inc.






Architecture Case Study

Sybase Co-Innovation Architecture

2 - 4


2 - 4

©2011 Sybase, Inc.


High-Level Design Overview

2 - 5

Two types of applications can be created with Sybase Unwired Platform – native


applications and mobile workflows.

Native applications allow the developer to write custom code using C#, Java, Objective-C

(depending on the target device). Mobile workflows are a fast and simple way to build applications that support simple business workflows such as expense approvals or vacation requests.

Supported on iPhone, iPad, Windows, Windows Mobile.

Regardless of which type of application you create, Mobile Business Objects (MBOs) are the heart of the Unwired Server package.

An MBO is the data access layer and provides CRUD operations. The business logic is then implemented at the application level. MBOs contain Attributes and Operations

Attributes are mapped to the underlying data fields from a database or a web service ( output ). Operations contain parameters ( or inputs ) that a client application can pass to the backend EIS system.

Sybase Unwired Platform is the Mobile Enterprise Application Platform that enables enterprise developers to simply and quickly develop applications that connect business data to mobile workers on any device. The Unwired Platform addresses the difficult mobile challenge of creating and managing multiple mobile applications that securely connect a variety of heterogeneous back-end data sources to major device types.

2 - 5

©2011 Sybase, Inc.


Application Development Concepts

Complex custom applications

Native Applications High degree of task specialization such as data intensive offline usage

Lightweight applications

Mobile Workflow Forms Scenarios such as Notifications, Alerts, Workflow extensions and simple data entry.

Provides integration to device specific features and peripherals such as barcode scanners, cameras, etc.

2 - 6


2 - 6

©2011 Sybase, Inc.


The Mobile Business Object (MBO)

Sybase Unwired Platform integrates and abstracts enterprise services by representing them as Mobile Business Objects Mobile Business Objects (MBOs):

Represent the data available in the backend exposed via standard services Enterprise applications can provide data to mobile applications by being invoked on demand or via events

Example:

Enterprise application exposes an interface to retrieve and/or create a list of Sales Orders together with its line items Would be represented as a Sales Order MBO with an operation to create new sales orders

2 - 7

An MBO contains Attributes and Operations. The MBO API gives programmatic access


to the members of an MBO as well as means to access, update and delete data.

2 - 7

©2011 Sybase, Inc.


Synchronization Models

Replication-based Synchronization (RBS)

Best suited for application scenarios with occasionally connected devices with a defined upload/download (sync- button) user experience

Messaging-based Synchronization (MBS)

Best suited for application scenarios with occasionally disconnected devices and an always-on user experience De-facto standard application example is “mobile email”

2 - 8


2 - 8

©2011 Sybase, Inc.


Native vs. Workflow

Native applications:

Designed specifically for a target platform and coded in the native language of that platform More complex and robust

Used for business critical scenarios

Workflow applications:

A simple XML form that is sent to the supported target device or can be initiated from the device, if it already resides on the device There is no logic in a workflow app - it's just a form that is filled out and sent back No coding is necessary to build a workflow application

2 - 9


2 - 9

©2011 Sybase, Inc.


Native Application Development Model

2 - 10

Sybase Unwired Platform enables developers to create mobile applications for specific devices either through code generation and language IDE or by using the native device SDK


2 - 10

©2011 Sybase, Inc.


Mobile Workflow Development Model

Enables developers to quickly create simple mobile workflows without writing any code in the application frontend

When utilizing all starting points, code is required in the backend integration such as triggers and stored procedures

2 - 11


2 - 11

©2011 Sybase, Inc.


More on Personal Developer Edition

Personal Developer Edition includes:

Unwired Server Sybase Control Center Afaria Eclipse development tools OpenDS LDAP server

Default is NOT to auto-start services Requirements:

All Sybase Unwired Platform components must be installed on the same machine Allows for a maximum of five synchronization clients for Unwired Server and Afaria Server

2 - 12

OpenDS is a Java Open Source Next Generation Directory Server.


Based on LDAP v3.

http://www.opends.org

2 - 12

©2011 Sybase, Inc.


Enterprise Developer Edition

Enterprise Developer Edition includes:

Unwired Server Afaria Eclipse and Visual Studio development tools OpenDS LDAP server

Default is NOT to auto-start services Enables installation and configuration of components on different machines Allows a maximum of 20 synchronization clients for Unwired Server and Afaria Server

2 - 13

To install components on different machines requires that you run the installation


separately, choosing the appropriate options for each machine. Licensing for each machine

applies.

2 - 13

©2011 Sybase, Inc.


Sybase Unwired Platform Deployment Edition

Deployment Edition includes only:

Unwired Server Afaria components

Does not include any development tooling environments Sybase Control Center is installed with the Unwired Server Enables installation and configuration of components on a separate machine Intended for use in a production environment By default, security on servers is not configured Default is to auto-start services

2 - 14


2 - 14

©2011 Sybase, Inc.


Introduction to Sybase Mobility






2 - 15


2 - 15

©2011 Sybase, Inc.


Supported Operating Systems

The Sybase Unwired Platform can be installed onto the following platforms:

Microsoft Windows XP, Professional Edition, with Service Pack 2 (32-bit) Microsoft Windows Vista, Business and Enterprise, and Ultimate Editions (32- or 64-bit) Microsoft Windows 2003 Server, Standard or Enterprise Edition, with Service Pack 2 (32- or 64-bit) Microsoft Windows 2008 and 2008 R2, Server Standard or Enterprise Edition Microsoft Windows 7 (32- or 64-bit)

2 - 16


2 - 16

©2011 Sybase, Inc.


Supported Back-End Databases

Sybase Unwired Platform supports:

SQL Anywhere 11.x Adaptive Server® Enterprise 12.5.x, 15.x Microsoft SQL Server 2005, 2008 Oracle 10g, 11g IBM DB2 UDB 9.1

2 - 17


2 - 17

©2011 Sybase, Inc.


Supported Client Platforms

Windows (for tablets, laptops)

Windows XP, Professional Edition, with Service Pack 2 (32-bit) Windows Vista, Business, Enterprise, and Ultimate Editions, Windows 7 (Professional, Enterprise and Ultimate Edition) (32- and 64-bit)

Windows Mobile 5.0, 6.0, 6.1, and 6.5 (Standard or Professional) Apple iPhone 3.1.3 - 4.1, iPad iOS 3.2 and iTouch iOS 3.1.3 - 4.1 RIM BlackBerry

OS 4.6.1 on Blackberry Curve 8900 OS 4.7.0 on Blackberry Storm 9530 OS 5.0 on BlackBerry Storm 2 (9550), BlackBerry Bold 2 (9700), BlackBerry Tour 9630, and BlackBerry Curve 8530

Symbian (Nokia Series 60 3 ^r^d Edition and 5 ^t^h Edition)

2 - 18

Other RIM support:


RIM BlackBerry 4.2, 4.6 and 4.7

OS 4.2.1 on Blackberry 8800 OS 4.2.2 on Blackberry Curve 8300 OS 4.6.0 on Blackberry Pearl Flip 8220 and Bold 9000

Android will be supported in version 2.0 of Sybase Unwired Platform

2 - 18

©2011 Sybase, Inc.


Supported Web Services

SOAP Web Services Representational State Transfer (REST) Web Services

A lightweight, easy to build a web service Identifies each unique URL as a representation of some object so that you can get the contents of that object using an HTTP GET Uses POST, PUT, or DELETE to modify the object

In practice, most of the services use POST

2 - 19

SOAP: Simple Object Access Protocol


2 - 19

©2011 Sybase, Inc.


Role of the Unwired Server

Unwired Server is the enterprise server included with Sybase Unwired Platform Unwired Server manages:

Mobile application logic (MBOs) Connections to back-end data resources Replication based synchronization (RBS) uses an occasionally connected synchronization channel Messaging based synchronization (MBS) uses asynchronous messaging to upload and download data Data Change Notification (DCN) pushes updates from the backend system to the Sybase Unwired Platform cache database, whereby mobile users are alerted of changes made to the backend data

2 - 20

Configuration tasks for Unwired Server vary depending on many factors, including


whether you are deploying Unwired Server to a development or production environment.

When DCN pushes updates from the backend system to the Sybase Unwired Platform cache database, those changes are then synchronized to the mobile clients as appropriate. The synchronization between the Sybase Unwired Platform cache database and the Sybase Unwired Platform clients may or may not be a push synchronization.

2 - 20

©2011 Sybase, Inc.


Role of the Relay Server

Necessary for clustered architecture

Supports load balancing HA for MBS is not dependent on the Relay Server HA for RBS is dependent on the Relay Server

Supports across the firewall deployment without requiring the opening of any internal firewall ports Is a set of Web extensions that run on a Web server

IIS on Windows Apache on Linux

HTTP or HTTPS both supported

2 - 21


2 - 21

©2011 Sybase, Inc.


Sybase Unwired Platform Components

Sybase Unwired Platform consists of three distinct architectural components:

Operating Environment

Data Services Mobile Middleware Services Consolidated Database

Platform-wide

Tooling Environment Administration Device Management & Security

2 - 22

The following pages will explain each of these in greater detail.


2 - 22

©2011 Sybase, Inc.


Operating Environment

Consolidated Database (CDB)

Synchronization cache for MBO data and other server artifacts, in addition to device client and user data

Data Services

Manage the Consolidated Database Fill CDB from EIS and invoke exposed EIS operations Update CDB on receipt of Data Change Notifications

Mobile Middleware Services

Runtime container for transaction processing, data synchronization, security, notification, etc. Synchronization can be replication-based (based on Mobilink) or message-based

2 - 23

The cache database does not exist in a DOE configuration. DOE based applications do not


use a cache database.

Mobile applications communicate with a Consolidated Database (CDB) instead of directly communicating with a back-end database.

2 - 23

©2011 Sybase, Inc.


Operating Environment Architecture

Sybase Unwired Server Platform

Mobile

Mobile Middleware Services

Customer

Application

SOA

Device and Application

Management

Device and

Infrastructure

Application

Management

Data Synchronization

Device

Services

Security

Data

Operation Replay

Device

Services

Data

State Replication

CDB

Unwired Server

Relay Server

Enterprise

Information

Systems

Database

JDBC

Accessible

2 - 24

You would want to host your CDB ideally on a separate server in a clustered environment.


2 - 24

©2011 Sybase, Inc.


Platform-wide Services

Sybase Unwired Platform allows developers to build

applications on a preferred IDE using just the generated code

and client APIs, or simply the APIs:

Unwired

Server

Sybase Unwired Platform Development Tools

Unwired WorkSpace Device Application Development Tool (Eclipse)

Unwired WorkSpace Mobile

Business Object Development Tool

(Eclipse)

Windows Mobile

BlackBerry

Native Device Application Development Tools

BlackBerry – JDE, Eclipse JDE Plugin

Windows Mobile - Visual Studio

BlackBerry

iPhone

Java

Objective C

Windows – Eclipse, Visual Studio

iPhone - Xcode

Windows

Java SE & C#

Windows Mobile

Workflow Application Development Tool (Eclipse)

C#

iPhone

Windows Mobile

Continued …

2 - 25


2 - 25

©2011 Sybase, Inc.



Administration (Sybase Control Center):

Node n

Sybase Control Center

Browser

Web Container

RMI

Flash

SUP Flex

Service

Plug-in

HTTPS

SCC Plugin

Unwired Server

Web Application

for SUP

SNMP

IIOPS

SNMP Service

Client

SUP SNMP

SNMP

IIOP

Plugin

Custom

Admin

RMI

Java

Client

Node 1

Continued …

2 - 26

MBean Interface


2 - 26

©2011 Sybase, Inc.



Device Management and Security:

Afaria Device Management is delegated to the Afaria web console and not part of the Sybase Control Center In a production environment, Afaria nodes are typically hosted on a separate server

2 - 27

DMZ

Firewall

Firewall

Afaria Server

IIS Server

Administrative

TCP/IP

IAS Relay Server or

Reverse Proxy

Console Browser

HTTP

ISA/Apache

SSL


2 - 27

©2011 Sybase, Inc.


Deployment Architecture

Connection to

Backend Systems

Sybase Unwired Platform

2.5G

Networks

Sybase

Sybase

Relay

GSM/GPRS

Unwired

Reliable Push

JDBC

Server

Messaging

Server

HTTP(S) / SOAP

or REST Web

Services

3G

Networks

MBO Services

DMZ

JCO

Connector for SAP

Internal

External

Deploy

Deploy

Deploy

MBOs

MBOs

MBOs

Firewall

Firewall

Wi-Fi

DOE

Connector for SAP

Personal Developer Tooling

Unwired Server Connection

2 - 28


2 - 28

©2011 Sybase, Inc.


Sample Production Architecture

Relay Server

Optional for HA

Relay Server

Farm

Firewall

Relay Server

IIS or Apache

DMZ

Inbound Traffic

Connects through

Relay Server

Internet

HA available for

Unwired Servers

Productio

SUP Domains

n


HTTP(S) Data Change Notification

Outbound

HTTP(S)

JDBC/JCOs/WS

EIS

SUP Production I

MBOs deployed to

the Production

Server

Firewall

JDBC/JCOs/WS.



SUP Production II

Afaria

(optional)

Internal

Decommission

Provision

Field devices connect to domains which contain MBO packages

Devices communicate to the Relay Server via HTTP or HTTPS

HTTP or

HTTPS

Devices

SUP Servers connect outbound to the Relay Server to the Relay Server farm

2 - 29

If you are concerned about opening ports in your firewalls to support mobile applications,


Sybase Unwired Platform resolves this through the use of a Relay Server. Mobile devices

connect to Relay Server only in the DMZ using only standard HTTP ports (these ports are

typically open in enterprise firewalls). RSOE (Relay Server Outbound enablers) are used to open outbound connections from the Sybase Unwired Platform and Afaria server farms to the Relay servers. HTTP load balancers in the DMZ distribute mobile device connections between the Relay servers. Multiple Sybase Unwired Platform and Afaria servers are run in a farm to provide high- availability. Primary and Secondary Unwired servers share a common consolidated database.

2 - 29

©2011 Sybase, Inc.


Redundant Server Production Architecture

A production server license is needed for each node of a redundant server setup

Clustered

Load Balanced

Relay Server

CDB Servers

SUP Servers

2 - 30

Relay Server is royalty free


2 - 30

©2011 Sybase, Inc.


Architecture Integration with SAP


Client

— API

— Data persistency

— Device management

— Data sync engine


Data Staging and Caching Services

Tools

JCO Connector/DOE connector / Web

Services

SAP Mobile Gateway

SAP NetWeaver

Mobile DOE

BAPI Wrappers

J2EE

CRM SRM

SCM

HCM

PLM EAM

.NET

Mobility Management Tools

SAP ECC

Legacy Systems

SAP Systems

Backend Systems

Mobility IT Infrastructure

Mobile Applications

2 - 31

There is more information about the SAP integration architecture later in this course.


2 - 31

©2011 Sybase, Inc.








2 - 32


2 - 32

©2011 Sybase, Inc.


Clustered Environment Concepts

Nodes

Host or server computer upon which one or more components have been installed

Unwired Platform Cluster

Groups of similar components that work together to service client requests

Shared Development Environments

Organizations typically opt for a single-node environment, but may also choose to use domains to partition the environment

Fault-Tolerant Production Environments

Design for fault-tolerance introduces component redundancy

Implementing an N+2-node Cluster for Optimal Redundancy

Recommended cluster type for achieving an optimal level of redundancy

2 - 33


2 - 33

©2011 Sybase, Inc.


Sybase Unwired Platform Environment Options

Single-node Environment

Installs all cluster components on one machine Does not support multi-node clusters

Multi-node Environment

One or more Unwired Server nodes Data-tier on the same node as the first Unwired Server Node, OR installed on a separate node

Supports multi-node clusters and multiple tenants

Fault-tolerant production or pre-production (test) systems

One or More Unwired Server (N) nodes for Load Balancing Consolidated, Cluster, and Messaging Databases using Microsoft Cluster on 2 Nodes for High Availability Supports multi-node clusters and multiple tenants

2 - 34

Production environment recommendation: Monitor Database on a separate node with or


without Microsoft Cluster if monitoring and/or domain logging is always ON in high load

environment.

2 - 34

©2011 Sybase, Inc.


Why Clustered Environments?

Purpose:

Redundant Unwired Platform components on network to provide a highly scalable and available system architecture

In a production environment, the Unwired Platform deployment typically uses at least one relay server

Typically not required for shared development environments, or for single-node personal development or trial environments Required if testing across a firewall or using a wireless connection from a service provider

2 - 35


2 - 35

©2011 Sybase, Inc.


Key Tiers in Clusters

Two key tiers in a cluster

Load-balancing server tier clusters

Improve the system performance by sharing workloads and requests Requests initiated from the user are managed by a load balancer, and distributed by relay servers Every node in the Unwired Server cluster scales automatically when another node joins or leaves the cluster

Failover data tier clusters

Improve the availability of runtime database services to Unwired Servers Failover clusters have at least one redundant node, which provides data tier services when the primary node hosting the databases fail The most common size for a failover consolidated database cluster is two nodes - the minimum requirement to provide redundancy and thereby eliminate single points of failure

2 - 36

Continued …

Load balancing is a high-availability strategy that prevents any one server from getting


overloaded with work, thereby adversely affecting system-wide performance, or even

causing the server to fail entirely.

Failover is another high-availability strategy that allows a secondary server to take over in the event of a fault or failure in the first server, thus allowing normal use to continue. Automatic failover is a default behavior of the cluster; it does not require manual intervention or configuration.

2 - 36

©2011 Sybase, Inc.


Key Tiers in Clusters

Primary server

Contains the master copy of the configuration repository for all servers in the cluster Distributes its configuration to the other servers in the cluster When a primary server fails, a new primary is elected from the remaining secondary servers

Secondary server

Gets its configuration from the primary server Servers must have unique names but are identified as members of the same server farm as the primary server

2 - 37


2 - 37

©2011 Sybase, Inc.


Best Practices for Collaboration in Shared Development Environments

Share an Unwired Server, so packages can be deployed to a common server

Place the Unwired Server and data tier on the same node Use a common system data tier for development and testing so that data is centrally managed Divide developers or groups of developers into "tenants" and use domains to partition the server environment Ensure that the development environment is similar to, but separate from, the production environment May want to use the default Open LDAP with its basic application security

2 - 38

Make each developer (or a representative developer from development groups) a domain


administrator so he or she can deploy packages to the shared Unwired Server.

2 - 38

©2011 Sybase, Inc.


Fault-tolerant System

Sybase recommends a redundant node and cluster strategy for most production environments to support:

Load balancing Failover

In an Unwired Platform production environment, system design tends to favor load balancing over failover

Provides better efficiency rather than just ensuring that the system is more reliable

2 - 39


2 - 39

©2011 Sybase, Inc.


Implementing N+2-node Clusters

Recommend Windows 2008 on ALL participating nodes in the cluster Tasks Overview:

Set Up the Microsoft Cluster before installing the Unwired Platform data tier Set Up Data Tier Nodes using the Unwired Platform installer

The data tier node includes the consolidated database (CDB), the cluster database, the monitoring database, and the messaging database. An Afaria database is also installed if you install the Afaria server

Add a Generic Service to the Data Cluster before you can install your runtime server nodes Set Up Runtime Server Tier Nodes once the generic service is available Install Third-party software on each server in a cluster. Validate the Cluster

Once the runtime and data tiers are installed, ensure that these components have been set up correctly

2 - 40

Windows 2003 is supported on non-cluster installations only.


2 - 40

©2011 Sybase, Inc.


Architectural Strategies Recap

Type

Description

Used for

Single-node

A

non-redundant architecture consisting of an Unwired Server and

Personal development or trial installations

data tier installed on a single host. This strategy is typically used by personal developers.

2-node

A

simple architecture without load balancing that may optionally

Enterprise development or test environments

use a relay server. The data tier (which includes the CDB, the messaging database, and the monitoring database) is on one node and the application and server tier (which includes Unwired

Server, Sybase Control Center, and optionally Afaria) is on another.

3-node cluster

A

simple redundant architecture with two server tier nodes (which

Entry-level production

includes Unwired Server, Sybase Control Center, and optionally Afaria) and one data tier node. For an example of this cluster, see Systems Design > Fault-Tolerant Production Environments > Redundant Architecture Options.

environments

N+2-node

An optimally redundant architecture with any number of server tier nodes (which includes Unwired Server, Sybase Control Center, and optionally Afaria) supported by a relay server and two data tier nodes. For an example of this cluster, see Systems Design > Fault-Tolerant Production Environments > Redundant Architecture Options.

cluster

Full-scale or optimized production environments

2 - 41


2 - 41

©2011 Sybase, Inc.


Multitenant Environments

Allows platform administrators to deploy a single production environment to service multiple client organizations known as tenants Multitenancy uses domains, which allow a tenant's administrators to manage Unwired Platform entities within the cluster partition As opposed to platform administrators, domain administrators see only the domains to which they have been assigned

2 - 42

Do not confuse domains in Unwired Platform with the traditional concept of network


domains. In Unwired Platform, a domain is only a namespace used in production

environments.

2 - 42

©2011 Sybase, Inc.


Implementing Relay Servers

Use one or more Relay Server Nodes:

Access Unwired Servers from Outside the firewall Load Balance between Unwired Servers Suspend/Resume Unwired Server for disabling client access

Install on a DMZ host and as a Plug-in to Microsoft IIS/Apache Web Server Choice of Using Sybase Hosted Relay Server

Use one or More Relay Server Outbound Enabler

On each Unwired Server Node Required when using Relay Server

Use an HTTP Load Balancer (or some Hardware-based solution) to:

Load balance Relay Servers Load balance Unwired Servers in a cluster (absent Relay Server)

2 - 43


2 - 43

©2011 Sybase, Inc.


Relay Server Setup

Binaries included in deployment Edition (only) Requires you to copy binaries to IIS or Apache and ‘some’ manual configuration Each Unwired Cluster can have up to 3 Farms:

Replication-based Synchronization Farm (RBS Farm) Messaging-based Synchronization Farm (MBS Farm) Data Change Notification Farm (DCN Farm)

Needed when DCN messages are delivered from outside the intranet such as in a hosted environment

2 - 44

Continued …


2 - 44

©2011 Sybase, Inc.


Relay Server Setup

Security considerations

Replication-based Synchronization and DCN could be via HTTP or HTTPS port Messaging-based Sync is always via HTTP port (encrypted internally) To configure secure communication (HTTPS for RBS or DCN)

Generate self-signed certificates or obtain certificates from trusted certificate authority (manual) Configure IIS or Apache with the security certificates when using secure port (use IIS Manager or whatever) Distribute the public key of the certificate if using self-signed certificate with the client application

2 - 45

Continued …


2 - 45

©2011 Sybase, Inc.


Relay Server Setup

Configuring Relay Server to direct traffic to Unwired Cluster farms

Run regRelayServer.bat to generate rs.config file and registers RSOEs to run as services Run rshost .exe utility which configures Relay Server per the rs.config file

2 - 46


2 - 46

©2011 Sybase, Inc.








2 - 47


2 - 47

©2011 Sybase, Inc.


Time Card Use Case

Use Case:

Provide CompanyX employees and management anytime / anywhere access to SAP time card submission and approval workflow to reduce or even eliminate delays in decision- making

Integration of mobility into existing infrastructure Integrated mobile device management and application provisioning Must support both BlackBerry and iPhone devices

Development

Provide business workflow mobility without the need for proprietary development language expertise and re-training

Business Requirements

Infrastructure:

Continued …

2 - 48


2 - 48

©2011 Sybase, Inc.


Time Card Use Case

Total Cost of Ownership

No need for complete change of current infrastructure to support mobility Enable current developers to leverage existing tools and expertise to create mobility solutions

High Availability

Automatic scaling and adjusting to changing workloads, ensuring high availability of mission-critical business applications

Flexibility

Must be a flexible, open platform to allow business to strategically respond to new device types and data sources A device agnostic approach to managing mobility

2 - 49


2 - 49

©2011 Sybase, Inc.


Current Timesheet Workflow Process

On desktop or laptop, employee submits and manager reviews, approves or rejects timesheet requests:

2 - 50

Employee

Timesheet entries

Timesheet entry approved

Timesheet entry rejected

Manager

SAP HR Module

Approved timesheet entries are updated in the database with status “Approved “

Rejected timesheet entries are changed in the database and resubmitted for approval

Continued …


2 - 50

©2011 Sybase, Inc.


Proposed Mobile Workflow Process

Data submitted

is saved to the

database in SAP

A workflow task executes and sends the timesheet details to the approving manager

Using a mobile device, timesheet is filled out by the employee

Data sent to SAP

Email generated and sent to manager in the field

2 - 51


2 - 51

©2011 Sybase, Inc.


Proposed High-level Mobile Workflow

Sybase Unwired Platform enables mobile workflow:

Sybase Unwired

3

Employee

enters

time

1

Devices

Manager views/approves and/or rejects time

Platform

• Sybase Unwired Platform

• Custom SAP Business Objects

2

Request sent to SAP

via MBO

• Custom BAPIs and

Workflows for Time

4

Management

Manager approval

status sent to SAP

SAP HR Module

2 - 52


2 - 52

©2011 Sybase, Inc.


Mobile Workflow Implementation Chart

Create Notification of time entered

EMPLOYEE

Decision whether to approve

MANAGER

REJECTED

APPROVED

Decision on further course of action

EMPLOYEE

Update HR CATS DB

SYSTEM

Delete time entered data

SYSTEM

Revise time entered

EMPLOYEE

HR CATS DB

2 - 53


2 - 53

©2011 Sybase, Inc.


Integration with SAP HCM

Sybase

Unwired

Platform

Server

Business object

CATimeSheetManager:

Insert data records

Change data records

Time Sheet

(CATSDB)

Mobile

Application

Business object CATimeSheetRecord.GetList:

Business object EmployeeCATimeSheet.GetWorklist

Retrieve worklist

Retrieve time sheet data

2 - 54


2 - 54

©2011 Sybase, Inc.


Integration with the SAP ERP

Sybase Unwired Platform connects to an SAP Human Resource Capital Management module to:

Provide complete support for Time Management BAPIs Support INSERT, CHANGE GETLIST and DELETE for CATIMESHEETMGR

GetTimeSheetManager.Insert

GetTimeSheetManager.Change

GetTimeSheetManager.Delete

Data Transfer

Sybase

Unwired

CATS DB

Server

Data Access

EmployeeCATimeSheet.GetWorkList

CATimeSheetRecord.GetList

Calls

Returns

Mobile Application

2 - 55


2 - 55

©2011 Sybase, Inc.


Network Topology Architecture

External Firewall

Internal Firewall

HA available for

Unwired Servers

SUP Domains

RIM Proprietary

BES (MDS)

Common CDB

Server

Authentica

BlackBerry

tion via

Carrier

User/Pass

HTTP 3200

sword


CDB

JDBC/JCOs/WS

SAP

SUP Production I

HTTP/SSL

MBOs deployed to

the Production

Server

JDBC/JCOs/WS


Devices

Apple APNS

Relay Server

IIS or Apache

Provider


Inbound Traffic

HTTPS – 2195

gateway.push.apple.com

Connects through

Relay Server

SUP Production II

HTTPS – 2196

feedback.push.apple.com

LDAP

Server

External Network

DMZ

SUP Servers

connect outbound

to the Relay

Server

Internal Network

2 - 56

HTTPS - 443

Mobile devices connect to Relay Server only in the DMZ using only standard HTTP ports


(these ports are typically open in enterprise firewalls).

RSOE (Relay Server Outbound enablers) can be used to open outbound connections from the Sybase Unwired Platform and Afaria server farms to the Relay servers. HTTP load balancers in the DMZ distribute mobile device connections between the Relay Server(s). Multiple Sybase Unwired Platform and Afaria servers can be run in a farm to provide high-availability. Primary and Secondary Unwired servers share a common consolidated database.

2 - 56

©2011 Sybase, Inc.


User Experience – Before

Employee uses web-based Portal to submit a request Manager uses web-based Portal to review and approve or reject request

SAP Backend

Employee Self

Service SAP Portal

Access

Manager Self

Service SAP Portal

Access

Web Server

Employee

Manager

submits

approves

2 - 57

request

request

Employee Self Service (ESS) via SAP Portal (through Internet) Explorer. Time claimed


everyday. System is slow and not accessible without PC. Portal integrates with backend

SAP system.

The backend CATS (Cross-Application Time Sheet) integrates with Finance. Contains data validation and data pre-population routines.

2 - 57

©2011 Sybase, Inc.


User Experience – After

Employee uses mobile device to submit a request

Manager uses mobile device to review and approve or reject

request

Backend

Systems

Sybase

Unwired

Platform

Mobilized ESS

Timesheet

Mobilized MSS

via Sybase

Timesheet

Unwired Platform

via Sybase

Unwired Platform

2 - 58


2 - 58

©2011 Sybase, Inc.





Sybase Unwired Platform Environment Considerations



2 - 59


2 - 59

©2011 Sybase, Inc.


Sybase Unwired Platform and SAP Integration

Mobile applications can be pre-built by Sybase or custom built on the integration component called Co-Innovation Architecture (CIA) Current pre-built applications are:

SAP Mobile Sales CRM Sybase Mobile Workflow for SAP Business Suite

Can be delivered to a wide array of mobile devices and platforms

iPhone Windows Mobile Android And others

2 - 60


2 - 60

©2011 Sybase, Inc.


Skill Set Required for CIA Mobility

2 - 61


2 - 61

©2011 Sybase, Inc.


Sybase Unwired Platform Role


Mobile

Mobile

Content

Content

NetWeaver Mobile

Mobile Adaptation (Gateway)

SAP Business Suite

BAPI Wrappers

CRM

SCM

SRM

ERP

PLM

2 - 62

Development and hosting environment for:

Native applications Workflows SAP Mobile Sales and Workflow pre-built applications Other pre-built native applications

Messaging and guaranteed delivery Device management PIM Integration and synchronization


2 - 62

©2011 Sybase, Inc.


Co-Innovation Architecture Role


Mobile

Mobile

Content

Content

NetWeaver Mobile


SAP Business Suite

BAPI Wrappers

CRM

SCM

SRM

ERP

PLM

2 - 63

Business processes

CRM as an example

Business data

Responsibility determination (DOE) Integrity (DOE) Synchronization and multiple version handling (DOE)

Server-side

Programming model Development/customizatio n environment


2 - 63

©2011 Sybase, Inc.


Combined Architecture of CIA


Mobile

Mobile

Content

Content

NetWeaver Mobile


SAP Business Suite

BAPI Wrappers

CRM

SCM

SRM

ERP

PLM

2 - 64

Joint role:

End-to-end lifecycle management:

Deployment Version control Trouble shooting

End-to-end integration

Integrated

application

development

Customization

programming model


2 - 64

©2011 Sybase, Inc.


Sybase SAP Mobile Sales and Workflow

CIA architectural overview for mobile sales and workflow:

Sybase

SAP

Unwired Platform

DOE

PUSH

PUSH

Connector

CRM

or

2007

JCO

Sybase Device Stack

Connector

KEY

KEY

SAP architected components

Engineered by Sybase with know-how share

from SAP as the complementary connector

technology to deliver SAP business data

and process to mobile devices

Messaging

SAP Mobile Gateway

NetWeaver Mobile 7.1

2 - 65


2 - 65

©2011 Sybase, Inc.


Data Orchestration Engine (DOE) Connector

Provides data transformation for DOE interaction

Listener based on WS-Eventing Serves incoming synchronous and asynchronous requests from devices via Sybase Unwired Platform runtime infrastructure Implements the guaranteed delivery concept of ACK and NACK messages (maintains message counters per logical device within Sybase infrastructure, no double guaranteed delivery) Automates Subscribe, Unsubscribe based on client software activation Incoming message routing based on ESDMA and target application

2 - 66

Sybase

Unwired Platform

DOE Connector

or

JCO Connector

Messaging


2 - 66

©2011 Sybase, Inc.


SAP Connectivity Methods

SAP

Sybase

Unwired Platform

DOE

PUSH

PUSH

Connector

SAP

BAPI (JCo)

Connector

SYNC

?

Sybase Device Support

SYNC

SQL DB

SYNC

JCDBC

Web Services

Web Service

SYNC

Connector

Messaging

Synchronisation

Mobile Gateway


2 - 67


2 - 67

©2011 Sybase, Inc.


Complete CIA Architecture

SAP Infrastructure

Sybase Unwired Platform Infrastructure

BAPI Wrapper &

Data Object Editor

ESDMA

Sybase Mobile App

Sybase Admin Console

Editor

Development

Tools

SAP

PUSH

Sybase

Business Suite

DOE

Connector

Channel Handlers

NetWeaver

ESDMA

Mobile with

Converter

Sybase

Sybase

DOE

PUSH

Device

Device

Stack

Stack

Sybase Unwired

BASIS 7.0

BASIS 7.1

Platform

PUSH

Push Messaging

Mobile

Gateway

RSS

http

CRM 2007

ERP ECC 6

SRM, SCM, PLM,

2 - 68


2 - 68

©2011 Sybase, Inc.


Deployment Architecture

Co-Innovation deployment:


Sybase

Sybase

Unwired

Relay

2.5G Networks

Server

Server

GSM/GPRS

SAP CRM

SAP NetWeaver

Reliable Push

DOE

Messaging

Connector

RFC

HTTP(S) /

SOAP Web

Services

SAP NetWeaver

Mobile 7.1 SP09+

with

Gateway 1.1 SP01

MBO Services

3G Networks

DMZ

CRM 2007

Device Management

SP06+

Application Provisioning

Internal

External

OR CRM 7.0

SP05+

Firewall

Firewall

Wi-Fi

2 - 69


2 - 69

©2011 Sybase, Inc.



There are no recorded demonstrations in this module

2 - 70


2 - 70

©2011 Sybase, Inc.


Module Summary


Benefits of Sybase Unwired Platform for mobile application development and deployment How to define the Sybase Unwired Platform development, administration and deployment architectures and its components Sybase Unwired Platform editions available with current release How to describe the various architectures for Sybase Unwired Platform How to define the Sybase Co-Innovation Architecture, Data Orchestration Engine (DOE), and JCO Connector

2 - 71


2 - 71

©2011 Sybase, Inc.



There are no post-assessment questions in this module

2 - 72


2 - 72

©2011 Sybase, Inc.

Sybase Unwired Platform Architectures and Technical Overview Module 3: Sybase Unwired Platform Native Applications Version 1.0


Technical Overview

Module 3:

Sybase Unwired Platform Native

Applications





3 - 1

©2011 Sybase, Inc.



1. What is Eclipse?

2. Before any kind of development can be performed, what must you launch in Eclipse?

3. What must be created before you can begin development in an Eclipse-based environment?

3 - 2



3 - 2

©2011 Sybase, Inc.


Module Objectives


Describe the Unwired Workspace Identify each of the views provided by Unwired Workspace Connect Unwired Workspace to a back-end database as well as to an Unwired Server Describe Native Mobile Applications

3 - 3


3 - 3

©2011 Sybase, Inc.


3 - 4


Introduction to the Unwired Workspace (Eclipse)

Setting Up Connections

Native Mobile Application Development


3 - 4

©2011 Sybase, Inc.


Unwired Workspace User Interface

WorkSpace

Navigator

contains all

project files

Diagram Window

contain all project

diagrams

Enterprise

Explorer contains

all connection

profiles

Problems Tab

displays any

warnings or

errors generated

Properties View

displays the

object in focus

properties

3 - 5

When you start the Unwired Workspace, you are starting Eclipse.


Unwired Workspace is an Eclipse plug-in.

Plug-ins are activated by Opening Perspectives within Eclipse.

Sybase Unwired Platform provides the Mobile Development Perspective.

3 - 5

©2011 Sybase, Inc.


Eclipse Perspectives

Provide a set of capabilities enabling you to work with resources to perform a task

An arrangement of views and editors in the Workbench

Views provide ways to navigate and work with resources Each view has:

Associated menus May have its own toolbar

Editors provide tools to create and modify resources Menu bars and context menus provide the items you need to create and manipulate resources Creation wizards guide you through the process of creating resources

3 - 6

Creation wizards are associated with the resources in a view.


3 - 6

©2011 Sybase, Inc.


Perspective Views

A Perspective can contain multiple views The Mobile Development Perspective contains the following views:

Workspace Navigator Enterprise Explorer Mobile Application Diagram Palette Properties Problems Outline

3 - 7

These views are explained on the following pages.


3 - 7

©2011 Sybase, Inc.


Workspace Navigator View

The WorkSpace Navigator View is the developers focal point When you start Eclipse, you specify the Workspace folder The WorkSpace is a container of projects Projects can contain MBOs as well as other entities, such BOB projects

3 - 8

Project

Closed

If you need to add an existing project to your workspace use the File Import menu.


Specify the destination directory (your workspace directory), then you can import an

archive file (ZIP) or a directory on the file system.

BOB – Blackberry Orchestration Builder.

3 - 8

©2011 Sybase, Inc.


Context Menus

Many views have context menus that provide quick access to common functionality Select File New Other or Press CTRL+N to launch the wizard selection dialog

3 - 9

Right-click to

enable context

menu


3 - 9

©2011 Sybase, Inc.


Wizards

The Mobile Development Perspective contains wizards that simplify the creation of objects For example, wizards help with:

The creation of MBOs The creation of the client application

3 - 10


3 - 10

©2011 Sybase, Inc.


Enterprise Explorer View

Enterprise Explorer View provides functionality to connect to enterprise backend systems such as:

Database Servers REST Services SAP Servers Unwired Servers Web Services

3 - 11


3 - 11

©2011 Sybase, Inc.


Mobile Application Diagram

Mobile Application Diagram is an editor where you graphically design MBOs and define their relationships Items can be dragged onto the diagram from the Palette or the Enterprise Explorer

3 - 12


3 - 12

©2011 Sybase, Inc.


Diagram Context Menus

The following shows the context menu of the Mobile Application Diagram:

3 - 13


3 - 13

©2011 Sybase, Inc.


Items in the Palette are context-sensitive When a Mobile Application Diagram is active, the palette contains controls specific to that diagram

You can select and click controls onto the diagram such MBOs and Relationships

3 - 14

Palette


3 - 14

©2011 Sybase, Inc.


Properties View

Entities such as MBOs contain many properties Property values can be set on this view (where most of your work will be performed)

Watch for tabs

Watch for tabs

3 - 15


3 - 15

©2011 Sybase, Inc.


Problems View

Problems View displays errors and/or warnings Line items in the Properties View can be double-clicked

This action takes you to the specific location (screen, MBO, etc.) where the warning or error occurred

3 - 16


3 - 16

©2011 Sybase, Inc.


Outline View

Outline View shows a thumbnail sketch of either a Mobile Application Diagram (MAD) or a BOB:

3 - 17

Click these icons to

configure the Outline

view for graphical or

list orientation


3 - 17

©2011 Sybase, Inc.


Cheat Sheets

Open the Cheat Sheet Selection dialog by going to Help Cheat Sheets… A cheat sheet opens as a view in a perspective Guide you through complex tasks by either:

Showing you how to perform the task Performing some of the task for you

3 - 18


3 - 18

©2011 Sybase, Inc.






3 - 19


3 - 19

©2011 Sybase, Inc.



Connectivity is performed via the Enterprise Explorer Before development:

Set up EIS database connectivity Set up connectivity to your Unwired Server Set up connections to services Set up connection to SAP

3 - 20


3 - 20

©2011 Sybase, Inc.


Creating a New Database Profile – Step 1

Right-click over the Database Connections node:

Select New and a

wizard will lead

you through the

creation of a

connection profile

3 - 21


3 - 21

©2011 Sybase, Inc.


Completed Database Connection Profile

Right-click

and select

Connect to

connect and

view the

contents of

that database

3 - 22


3 - 22

©2011 Sybase, Inc.


Connecting to Unwired Server

A default connection profile (My Unwired Server) is provided Additional connection profiles to other Unwired Servers in a clustered environment can be created

3 - 23


3 - 23

©2011 Sybase, Inc.


Unwired Server Connection Profile

Default password is:

s3pAdmin

Port 2000 is the default

port during the installation

3 - 24

The user name and password are case-sensitive.


3 - 24

©2011 Sybase, Inc.


View of a Connected Unwired Server

A server can be partitioned by adding domains

“Default” is created on installation

Packages are MBO containers deployed to Unwired Server “admin” is the default security configuration

Must configure a security methodology that meets your organization’s needs

3 - 25

The default admin security configuration provides no real security required by a server.


You must manually configure your own security that meet your organization’s security

needs.

3 - 25

©2011 Sybase, Inc.






3 - 26


3 - 26

©2011 Sybase, Inc.


Development Process / Device Platform Options

Sybase Unwired Platform Development Task Flow

Deploy Mobile

Generate and

Develop

Generate

Test on

Business

Develop

Customize

Mobile

Device

Emulator

Objects

Device

Device

Business

Object

and/or

to Unwired

Application

Application

Objects

Code

Device

Server

Native Code

Sybase Unwired Platform Development Tools

Unwired WorkSpace Device Application Development Tool (Eclipse)

Unwired WorkSpace Mobile

Business Object Development Tool

(Eclipse)

Windows Mobile

BlackBerry

Native Device Application Development Tools

BlackBerry – JDE, Eclipse JDE Plugin

Windows Mobile - Visual Studio

BlackBerry

iPhone

Java

Objective C

Windows – Eclipse, Visual Studio

iPhone - Xcode

Windows

Java SE & C#

Windows Mobile

Workflow Application Development Tool (Eclipse)

C#

iPhone

Windows Mobile

Symbian

3 - 27

MBO development followed by Device Application Development and optionally Native


IDE for custom development.

3 - 27

©2011 Sybase, Inc.


Steps for Native Mobile Development

Create a new mobile application project Create Mobile Business Objects (MBOs) using the Mobile Application Design editor

Attach MBOs to backend data sources

Associate MBOs by creating relationships Deploy MBOs to Unwired Server Create device application user interface screens:

Can use the Flow and Screen Design Editor OR Generate the code and import it into your tooling IDE of choice

3 - 28


3 - 28

©2011 Sybase, Inc.


New Project

Container folders such as Cache Groups and Roles are

created with the new project:

A new Mobile Application

Diagram is created and

opened in the editor

3 - 29

Projects contain the following folders:


Mobile Business Objects

Cornerstone of Sybase Unwired Platform Business logic of the application

Data Source References

Shows all data sources referenced by the MBOs in the project

Cache Groups

Defines the cache refresh schedule for MBOs

Personalization Keys

Allow the user to request certain data from the MBOs

Roles

Used to define access-based security

Synchronization Groups

Describe publish/subscribe parameters for MBOs

Deployment

Contains project-level deployment profiles

Filters

Java classes used to filter results

Generated Code

Client-side code used for custom development of the mobile application

3 - 29

©2011 Sybase, Inc.


Importing Existing Projects

Use the Import feature to import project files, entire folder and subfolders and/or archive files containing projects:

3 - 30


3 - 30

©2011 Sybase, Inc.


Exporting Projects

Useful for sharing a project with other developers To export:

Right-click in a null area of the WorkSpace Navigator Select Export

Can export to a File System or an archive file

3 - 31


3 - 31

©2011 Sybase, Inc.


Mobile Business Object (MBO)

Foundation of Sybase Unwired Platform and forms the business logic Is a metadata definition representing a “slice” of enterprise data Provides a data model to define how information is represented

Provides a transactional model that delivers up-to- date data to and from mobile devices Is made up of attributes, parameters, operations and relationships

Enterprise

Device

System

Representation

3 - 32

Subset

Personalize

Mobilize

An MBO could be the result of a SQL SELECT statement, if the data source is a database


server. Or, it could be the result of a Web Service method call, or the data returned from

an SAP BAPI.

3 - 32

©2011 Sybase, Inc.


Makeup of an MBO

MBOs are made up of:

Attributes:

Formed from data returned from a source – i.e columns in a result set or values returned from a Web Service/BAPI method

Operations:

Mechanism for data modification

Relationships:

Means by which to link multiple MBOs

Roles:

Means of controlling access to data

3 - 33


3 - 33

©2011 Sybase, Inc.


MBO Attributes

Attributes are the data makeup of the MBO

For example, if the MBO is created from a database server, the output columns of the SQL SELECT statement become the MBO’s attributes

Attributes are class-level properties in the client side mobile object

3 - 34


3 - 34

©2011 Sybase, Inc.


MBO Parameters

Parameters allow runtime input

Parameters are mapped to arguments used in a WHERE clause Allows the client to pass input to the query

Parameters can:

Be assigned default values that are used if nothing is sent from the application Be bound to personalization keys where input is provided by the application user

3 - 35


3 - 35

©2011 Sybase, Inc.


Parameter Sample

Stored procedure below contains two parameters which would require runtime input:

customer_id

product_id

Can map these parameters to Personalization Keys

3 - 36


3 - 36

©2011 Sybase, Inc.


MBO Operations

Used to modify the data in the EIS Parameters can be passed to operations Standard operations include update, delete, create which alter the state of the data Can create user-defined operations of type “Other” that do not cause a change in state

3 - 37

Operations, methods and functions are terms which mean the same thing; they are entities


that do the work within the object.

Operations can be defined by personalization keys for a user or group.

3 - 37

©2011 Sybase, Inc.


MBO Relationships

MBOs can be related in the same way that tables can be related in a relational database using Primary/Foreign key relationships Sybase Unwired Platform does not automatically identify relationships Relationships must be manually created

3 - 38

This symbol shows a one-to-

many relationship


3 - 38

©2011 Sybase, Inc.


MBO Roles

Are “logical” entities that secure access to an MBO

Or more granularly define an MBO’s operations

Work in conjunction with physical roles, which reside in the underlying security provider (i.e. LDAP) Provide user authorization before the request goes to the back-end system (Database, SAP, etc.)

3 - 39

Here, a logical role named UserRole was created and then assigned to the Customer and


Sales_order MBOs.

Further configuration of this role would occur using the SCC which will be discussed in the Administrators course.

3 - 39

©2011 Sybase, Inc.


Local Business Object (LBO)

Data exists only in the device’s database

Does not use a remote data source Once a new instance is created, it will be persisted only to the device’s database Does not have pending status Does not require sync

Can only define create, update and delete operations LBO to LBO relationships can be created but NOT between LBO and MBO

3 - 40


3 - 40

©2011 Sybase, Inc.


Initial Synchronization Process

1. User initiates synchronization and includes a parameter

2. If Personalization Keys are used, they are passed to the EIS

3. The EIS refreshes the Unwired Server

4. A partition in the CDB is created for that user’s data

5. The device is synchronized with the partition

Mobile Device

3 - 41

2

1

Unwired Server

EIS

4

CDB

5

3

The partition is created if this is the first synchronization for the user. Otherwise, the


partition is updated.

3 - 41

©2011 Sybase, Inc.


Synchronization Parameters

A synchronization parameter:

Maps to an attribute Limits the data that is returned to the device Can be tied to a Personalization Key

3 - 42

Unwired Server

Mobile Device

CDB

Local Database

Simply stated: Synchronization parameters control the amount of data to be sent to the


mobile device.

3 - 42

©2011 Sybase, Inc.


Personalization Keys

Metadata that enable users to store their search preferences

When mapped to a synchronization parameter, filter the data retrieved into the mobile device Can be stored on the client, server, or by session

Can be created by the developer or may use built-in personalization keys Built-in Personalization Keys (Username and Password) can be used to propagate application credentials to the backend EIS

3 - 43


3 - 43

©2011 Sybase, Inc.


WHERE Clause with Parameters

An MBO’s SELECT statement can contains a WHERE clause A parameter (i.e. state_code) provides the input to the WHERE clause condition Parameters are given a value at runtime

3 - 44

:state_code is considered the load parameter.


state is considered the Propagate To attribute.

3 - 44

©2011 Sybase, Inc.


Parameter Mapping

If the data source of the MBO contains a parameter, it…

Needs to be mapped to the backend system Maps to a data item (Remote Operation) in the backend database

3 - 45

:state_code will be passed as a

parameter to the Select statement

WHERE clause when the remote

operation executes

Refer to the previous slide for the declaration of :state_code.


Once the parameter mapping is done, the basic MBO definition is complete.

3 - 45

©2011 Sybase, Inc.


Load Parameter Properties

Parameters must be given a value at runtime! Load parameters are defined in the properties of an MBO Load parameters values can come from either a Personalization Key or a Synchronization Parameter

A default value will be sent to the server in absence of these ^p^rô^pê^r^t^y ^vâ^lûê^s

state_code automatically

becomes a Load

Parameter

3 - 46


3 - 46

©2011 Sybase, Inc.


Associating Synch and Load Parameters

Load Parameters can get its value from:

Personalization Keys or default values Synchronization Parameters

3 - 47

If not paired (or mapped) to a synchronization parameter, no such synchronization


filtering occurs for the device and the parameter is simply used to update the consolidated

database (CDB) by retrieving a subset of data from the enterprise information system (EIS).

In some cases, a load parameter is desired to refine the data requested from the EIS. Mapping the load parameter to a synchronization parameter partitions data in the CDB according to values sent from each device client.

3 - 47

©2011 Sybase, Inc.


Synch and Load Parameters Scenario

Objective:

Show that the CDB can have one set of data that is not identical to the local device database

Approach:

Create a Load Parameter that limits customers in the CDB to a particular state – i.e. customers from the state of MA Then create a Synchronization Parameter that further limits the data in the local device database to a particular customer or subset of customers in MA. For example:

A certain customer id Customers in MA where number of orders in 2010 exceed 10

3 - 48


3 - 48

©2011 Sybase, Inc.


Deployment

MBOs are deployed into a package in the Unwired Server The package is named after the Mobile Application Project

3 - 49


3 - 49

©2011 Sybase, Inc.


Custom Filter JARs

A custom result set filter is a Java class that allows you to process the result set that is returned so that it can be better consumed by the client application

Unique processing of the data before it is downloaded to the client

During deployment, you can select a JAR file to deploy with your application:

3 - 50

This wizard screen is enabled only when the developer uses the Advanced Developer


profile option.

3 - 50

©2011 Sybase, Inc.


Deploy to a Server/Domain

Select the server and domain to which to deploy:

3 - 51


3 - 51

©2011 Sybase, Inc.


Deployment Profiles

Can create a deployment profile / package on the last screen of the Deployment Wizard

3 - 52


3 - 52

©2011 Sybase, Inc.




3 - 53


3 - 53

©2011 Sybase, Inc.


Module Summary


Development requirements for mobile business applications

Database connections Server connections Workspaces and projects Mobile application diagrams

How to build MBOs from tables and stored procedures How to create a Personalization Key for user input Differences between load and synchronization parameters How to deploy a project to Unwired Server

3 - 54


3 - 54

©2011 Sybase, Inc.



1. True/False: A WorkSpace is a physical file.

2. What is the name of the Sybase Unwired Platform Eclipse Perspective?

3. True/False: A WorkSpace can contain multiple projects.

4. In which view will most entity details be configured?

3 - 55



3 - 55

©2011 Sybase, Inc.



3 - 56

©2011 Sybase, Inc.



Version 1.0


4 - 1

©2011 Sybase, Inc.



Version 1.0



4 - 2

©2011 Sybase, Inc.



Version 1.0


4 - 3

©2011 Sybase, Inc.



Version 1.0


4 - 4

©2011 Sybase, Inc.



Version 1.0

Business processes, such as alerts, time recording, and travel requests require


immediate action, but today are generally only accessible via desktop or laptop

computers.

The Sybase Unwired Platform workflow capability removes the need to physically interact with backend systems or use traditional client applications and allows for this decision-making application to be hosted on multiple mobile devices.

While some business processes require a thick application with business logic and access to reference data, some others do not. Sometimes a business process can be made mobile simply by providing the ability to capture a single YES/NO from a user or by providing the ability to send data in structured form into the existing backend

systems.

4 - 5

©2011 Sybase, Inc.



Version 1.0


4 - 6

©2011 Sybase, Inc.



Version 1.0


4 - 7

©2011 Sybase, Inc.



Version 1.0


4 - 8

©2011 Sybase, Inc.



Version 1.0


4 - 9

©2011 Sybase, Inc.



Version 1.0


4 - 10

©2011 Sybase, Inc.



Version 1.0


4 - 11

©2011 Sybase, Inc.



Version 1.0


4 - 12

©2011 Sybase, Inc.



Version 1.0

Starting Points are places from which a screen flow can be initiated.


4 - 13

©2011 Sybase, Inc.



Version 1.0


4 - 14

©2011 Sybase, Inc.



Version 1.0


4 - 15

©2011 Sybase, Inc.



Version 1.0


4 - 16

©2011 Sybase, Inc.



Version 1.0


4 - 17

©2011 Sybase, Inc.



Version 1.0


4 - 18

©2011 Sybase, Inc.



Version 1.0

Save: Closes the current screen, validates the current input and, if validation


succeeds, saves it.

Cancel: Discards any changes on the current screen and closes it. No validation occurs.

Close: Discards any changes on any open screens and closes all open screens. No validation occurs.

Open: Opens a different screen.

Add: Opens a different screen from where you can add a new row to a listview

Submit: Validates the entered data on open screens and sends it to the server. There, the server invokes the specified MBO operation or object query. If the

Submit is asynchronous, the client application closes once the request is sent. If the

Submit is synchronous, the client application stays open.

Add/Update/Delete Listview Row: Specifies the MBO operation that is associated with the appropriate action on the listview. Note that these operations will not be invoked immediately, but will instead be invoked when a Submit is made on the parent MBO that this MBO is related to. Can only be added to screens that are navigated to as the result of a Listview Details navigation (i.e. clicking on a row in a listview).

4 - 19

©2011 Sybase, Inc.



Version 1.0


4 - 20

©2011 Sybase, Inc.



Version 1.0


4 - 21

©2011 Sybase, Inc.



Version 1.0


4 - 22

©2011 Sybase, Inc.



Version 1.0


4 - 23

©2011 Sybase, Inc.



Version 1.0


4 - 24

©2011 Sybase, Inc.



Version 1.0


4 - 25

©2011 Sybase, Inc.



Version 1.0


4 - 26

©2011 Sybase, Inc.



Version 1.0

Special case: for relationships, you can choose to only affect the children and not to


affect the parent.

4 - 27

©2011 Sybase, Inc.



Version 1.0

As noted earlier, these are the types of menuitems: Save, Open, Close, Cancel, Add,


Submit and Add/Update/Delete Listview Row.

Save, Close and Cancel are entirely self-evident, and have no interesting properties to discuss.

The Screen property is used to specify which screen is to be opened.

4 - 28

©2011 Sybase, Inc.



Version 1.0


4 - 29

©2011 Sybase, Inc.



Version 1.0


4 - 30

©2011 Sybase, Inc.



Version 1.0

Must create a device user for each device that will run a Mobile Workflow


application.

Server-initiated workflow deployment assumes that you have an email server available with all appropriate user accounts, etc. for the workflow application.

4 - 31

©2011 Sybase, Inc.



Version 1.0


4 - 32

©2011 Sybase, Inc.



Version 1.0


4 - 33

©2011 Sybase, Inc.



Version 1.0


4 - 34

©2011 Sybase, Inc.



Version 1.0


4 - 35

©2011 Sybase, Inc.



Version 1.0


4 - 36

©2011 Sybase, Inc.



Version 1.0


4 - 37

©2011 Sybase, Inc.



Version 1.0



4 - 38

©2011 Sybase, Inc.

Sybase Unwired Platform Architectures and Technical Overview Module 5: SAP Mobile Sales CRM Technical Overview Version 1.0


Technical Overview

Module 5:

SAP Mobile Sales CRM Technical

Overview





5 - 1

©2011 Sybase, Inc.



There are no pre-assessment questions in this module

5 - 2


5 - 2

©2011 Sybase, Inc.


Module Objectives


Define in greater detail the SAP portion of the Architecture used in the SAP Mobile Sales application Understand environment components for the SAP Mobile Sales application Gain a broad understanding of customization options for the SAP Mobile Sales application

5 - 3


5 - 3

©2011 Sybase, Inc.


Overview of SAP CRM 7


Sybase Unwired Platform Integration – DOE Connector

SAP Mobile Sales Application Architecture

Configuring SAP CRM Components

Customization

Deploying Mobile Sales CRM to Devices

5 - 4


5 - 4

©2011 Sybase, Inc.


Mobile Sales Activities

Typical Mobile Sales requirements:

Call customer to

reschedule

meetings

Read e-mails

and

notifications

View today’s

activities

View

opportunities

SAP Mobile CRM

View map and

visit customer

Prepare for

revenue status

meeting

Make personal

calls

5 - 5


5 - 5

©2011 Sybase, Inc.


SAP CRM Basics

SAP Customer Relationship Management (SAP CRM) is a multichannel application supporting all business lines across:

Marketing Sales Service and customer interaction channels such as the Internet, mobile clients, and interaction centers

SAP CRM provides the following business benefits:

Industry-specific and cross-industry end-to-end business processes An open, adaptable technology platform powered by SAP NetWeaver® Flexible and process-based deployment options

SAP CRM is part of the SAP Business Suite

5 - 6


5 - 6

©2011 Sybase, Inc.


Value to the business

Benefits

Improves sales effectiveness and responsiveness Provides immediate awareness of relevant customer information Improves overall sales decision-making due to access to timely data Increases ROI on SAP CRM investment through easy and frequent use

Value to IT Organizations

Extends reach of SAP sales applications Supports heterogeneous devices through a single, highly scalable mobile platform Enforces enterprise-class security Enables easy deployment, support and management

5 - 7

Continued …


5 - 7

©2011 Sybase, Inc.


Benefits

Solution application is fully certified and supported by Sybase and SAP Built on proven mobile infrastructure of Sybase Unwired Platform and SAP NetWeaver Provides full access to SAP CRM from iPhone ®, BlackBerry and Windows Mobile

Additional device support coming soon for Android

5 - 8


5 - 8

©2011 Sybase, Inc.


Functions

Account and Contact Management

Allows for sales account management by monitoring, tracking critical information Integration into native functionality to insure instant triggering of emails and phone calls, etc.

Lead and Opportunity Management

New leads appear instantly when assigned in the CRM

Activity Management

Critical for scheduling and planning and logging customer information

Sales Documentation and Analytics

Comprehensive view of all customer information

5 - 9


5 - 9

©2011 Sybase, Inc.


Landscapes

Supports:

Windows Mobile 6.x Standard and Professional Apple iPhone 3.1.x

Sybase Unwired Platform system includes device management service and SAP Mobile Gateway Connector

SAP

Sybase

Sybase Unwired

Sybase Mobile

PUSH

CRM

Platform*

Sales Application

2007

or

CRM 7

* See slide 19 for a more detailed view of components

5 - 10

Mobile Gateway 1.1


*Review slide 19 for a more detailed view of components in Sybase Unwired Platform.


5 - 10

©2011 Sybase, Inc.


SAP NetWeaver Mobile (NWM/DOE)

Technology of the SAP NetWeaver platform group that is currently used to enable Business Suite services for mobile consumption

Mobile CRM Mobile Workflow Custom applications

Requires the business services (content) to be developed with particular patterns

GetList, GetDetails, ….

Primarily provides the following capabilities:

Data consolidation – Load data from backend into staging area (CDS)

Load rules separate from distribution rules

Data distribution – Large, staged roll-out, complex distribution rules

5 - 11

Continued …


5 - 11

©2011 Sybase, Inc.


SAP NetWeaver Mobile (NWM/DOE)

Provides certain key quality attributes:

High scalability Conflict management Correcting errors on transactions in queued/batch mode Security on SAP data (authorization rules) Monitoring Trouble shooting

Introduces another Server in the deployment architecture as it is on a different BASIS stack

5 - 12


5 - 12

©2011 Sybase, Inc.


SAP NetWeaver Mobile Components

Data Orchestration Engine (DOE)

Create software component versions (SWCVs) Define data objects Define distribution models Create back-end adapters

Mobile Client Platform

Transport layer Synchronization dispatcher Client synchronization Error and conflict handling Persistency

Mobile Administrator

Monitoring - Client communication, logs and traces, messages, workload, and performance

5 - 13


5 - 13

©2011 Sybase, Inc.


SAP NetWeaver Mobile Architecture

Mobile Applications

Mobile Device

Mobile Device

Mobile Device

App 1

App 2

App 1

App 2

App 1

App 2

Mobile Client

Mobile Client

Mobile Client

JVM

DB

JVM

DB

JVM

DB

HTTPS File

HTTPS File

HTTPS File

Mobile Gateway

SAP NetWeaver AS

Device Queue

Device Queue

Device Queue

Device

Consolidated Data Store

Inventory

Data Orchestration Engine

SAP Mobile Administrator

RFC

RFC

HTTPS

Backend A

Backend B

Backend C

5 - 14


5 - 14

©2011 Sybase, Inc.


Mobile Gateway

Add-on to the DOE so as to develop client framework services for enabling seamless offline/ online mobile access to back-end components Design time features

Group various data objects

Provides a design time environment to build applications with complete reusability of data models

Tailor the data models based on scenario needs

Runtime features

Mobile friendly search, read and write Web service-compliant interfaces Mobile friendly data push Web service event interfaces

5 - 15


5 - 15

©2011 Sybase, Inc.


Mobile Gateway for NW Mobile

Delivered as an Add-on to NWM 7.1 Sits on top of DOE

It is one of the delivery channels to DOE

Provides the following capabilities

True Push for large scalable mobile scenarios Life-cycle management (Versioning, content upgrade) Queuing and device tracking

5 - 16


5 - 16

©2011 Sybase, Inc.


Architecture of Mobile Gateway

5 - 17


5 - 17

©2011 Sybase, Inc.







Customization


5 - 18


5 - 18

©2011 Sybase, Inc.


Architectural Patterns

SAP Dev & Admin Tool

Sybase Mobile Dev.

Sybase Admin

3rd Party Dev Tools

NetWeaver Work Bench

(model driven develop)

Mobile Administration

ESDMA Editor

SAP Connection Wizards

MBO Modeling Editor

Mobile App Screen Dev

MBO Configuration

Pull/Push Management

Roles & Security

App Provisioning

Mobile App Development

Eclipse

Visual Studio

Xcode


Run Time


NetWeaver

Mobile (DOE) 7.1

PUSH

DOE-C

Reliable

MSG

Mobile Application

Connector

Push Msg

Queue

State

User Interface

Monitoring & Support

Server

Engine

PUSH

Data Distribution

ESDMA

(iMO)

Messagin

Converter

Data Consolidation

WSDL

g MBO

Messaging

Client

Backend Handlers

Listener

ECC 5.0/6.0

Sybase

Scheduling

Reliable

Web Services

Services

App Components

PULL

Data

Stack

Synchronization

(https)

CRM

ERP

SCM

Apache Axis

Replication

Libraries

MBO

NetWeaver

Mobilink

MBO Code

Engine

Sync

Data Change

Server

Notification (DCN)

Cache

SAP R/3 4.6x, 4.7x

Library

SQL

Access

•

Data

Sybase

App Components

Consolidation

JCo Wrapper

ERP

CRM

Push

• Differential Calc

Push

Persistent

Event

PULL

SAP

• Simulated Push

Listener

Data Store

Queue

PULL

JCo Connector

(native)

• Personalization

(native)

SAP Enterprise

Sybase Mobile

Infrastructure

Sybase Mobile Middleware

Device Stack

5 - 19

PUSH

BAPI/RFC

Data Versioning

BAPI/ Enterpris

BAPIWrapper

Mobile

Gateway

RFC

e

Interface

SOA

Custom Business

Component Libraries


5 - 19

©2011 Sybase, Inc.


Sybase DOE-Connector (DOE-C)

Abstraction and optimization layer between SAP DOE and Sybase Unwired Platform Provides ESDMA import capabilities to generate necessary inbound and outbound interfaces Provides data transformation for DOE interaction

Listener based on WS-Eventing Serves incoming application specific synchronous and asynchronous requests from devices Implements the guaranteed delivery concept of ACK and NACK messages

Maintains message counters per logical device within Sybase infrastructure, no double guaranteed delivery

Automates Subscribe, Unsubscribe, Upgrade and Reset based on software deployment callback or client software activation Incoming message routing based on ESDMA and target application

5 - 20

Provides configuration option for automatic log details gathering and upload to DOE.


5 - 20

©2011 Sybase, Inc.


DOE Connector Interactions

5 - 21


5 - 21

©2011 Sybase, Inc.


DOE Connector Logical Architecture

DOE

Connector

Client to Server synchronous web services invocation

Client to Server message sequence update and JMS

message de-queue transaction for reliable asynchronous

requests

MDB for iMBO

inbound messages

Route Incoming

notifications

based on URL

JSON to DOE

Messaging Format

Direct Invocation

from Client

DOE Reliable

Messaging

ESDMA DOE-C

DOE Notifications

HTTP(s) Listener

Web Services Eventing

Collaboration

Metadata

DOE Requests/

Module

Responses

DOE to JSON

Messaging Format

DOE-Connector

to iMO

5 - 22

Compute JMS queue based on iMO partition information and device ID

Server to Client message sequence update and JMS message queue transaction. Acknowledge DOE based on latest sequence if it reliable messaging is used

AckFromClient to DOE

DOE-C Repository

Contains:

Routing information: subscription ID to destination queue Subscription message sequences (client <-> Server) JMS queues and messages

DOE Connector Logical Architecture


5 - 22

©2011 Sybase, Inc.


Messaging Architecture from Server to Client

5 - 23


5 - 23

©2011 Sybase, Inc.


Underlying Technology

ESDMA – Entity Source Definition for Mobile Applications

An XML document, very much like an WSDL Design time artifact DOE Data Model for its Business Objects called Data Objects Generated and managed as a software artifact in Mobile Gateway Downloaded from the Mobile Gateway’s ESDMA browser

5 - 24


5 - 24

©2011 Sybase, Inc.


Sybase ESDMA Converter

Operates on any DOE generated ESDMA bundle Generates necessary meta data for the DOE Connector

Deployment archive for Sybase Unwired Platform Runtime Transformation meta data for data conversion Object API MBO source code generation

Objective C for iPhone OS C# for Windows Mobile and Win32 Java for BlackBerry

5 - 25


5 - 25

©2011 Sybase, Inc.


Sybase Unwired Platform Integration Flow

5 - 26


5 - 26

©2011 Sybase, Inc.







Customization


5 - 27


5 - 27

©2011 Sybase, Inc.


CRM Mobile Sales Co-Innovation Architecture

5 - 28

Sybase Mobile

Sales Application


Gateway 1.1 SP00+

Consolidated

Data Store

SAP NetWeaver Mobile 7.1 SP09+

SAP Business Suite

SRM

SCM

PLM

ERP

CRM 2007 SP06+ OR

CRM 7.0 SP05+

Co-Innovation Platform


5 - 28

©2011 Sybase, Inc.


Technical Attributes - Application

Application layer:

Developed in the native programming environment of the device

C# .NET for Windows Mobile Objective C for iPhone RIM Java

Sybase

Unwired

Platform

Applications need to be first class citizens on the device

Leveraging the Phone and PIM integration capabilities of the device Leveraging the GPS, maps and context information

5 - 29

Application

Sybase Device

Support


5 - 29

©2011 Sybase, Inc.


Seamless Offline/Online Experience

Users can work regardless of the connectivity

All critical activities that can be made available in a disconnected mode will be made

available When connected the users will be able to access the enterprise system synchronously as well

Example of an online search

Sybase

Unwired

Platform

5 - 30

Application

Sybase Device

Support


5 - 30

©2011 Sybase, Inc.


Push Based

User gets relevant business data calculated and pushed directly

Automated synchronization Alerts to the user to grab the attention to critical tasks or business data that was pushed

Sybase

Unwired

Platform

Application

Sybase Device

Support

5 - 31


5 - 31

©2011 Sybase, Inc.


Application Architecture

5 - 32

Application User Interface

Glue + Screen flow code

Application Business Objects (ABO)

- Hand Written

Consolidates access across multiple MBOs

and implements CRM business logic

Generated MBO

With SQL Interface

SQLLite

Data Model


5 - 32

©2011 Sybase, Inc.


Application Implementation Steps

Assumption: Installation, post-installation and configuration of Sybase Unwired Platform , Relay Server, SAP CRM 7.0 and SAP NetWeaver Mobile 7.1 with Mobile Gateway 1.1 add-on has been done Steps:

1. Create BAPI Wrapper definitions for the target business processes

Can be done by SAP functional/basis experts doing SAP implementation

2. Define Data Object definition for use by the DOE

Can be done by resources skilled in SAP NetWeaver technology

3. Define an ESDMA for object definitions to be pushed by the SAP Mobile gateway 4. Execute Sybase ESDMA converter to translate ESDMA object definitions to Sybase Unwired Platform MBO definitions 5. Generate meta-data for Sybase DOE Connector 6. Customize mobile device application using the Sybase client technology stack and development tools

5 - 33


5 - 33

©2011 Sybase, Inc.







Customization


5 - 34


5 - 34

©2011 Sybase, Inc.


Post-Installation for SAP NetWeaver Mobile 7.1

Assumption: Completed the installation of SAP CRM 7.0 and SAP NetWeaver Mobile 7.1 with Mobile Gateway 1.1 Steps:

1. Create an administrator profile 2. Log on to the SAP NetWeaver Mobile Administrator 3. Create an RFC destination to the backend 4. Perform DOE initial setup and configuration 5. Configure Back-End Destination Objects in DOE system 6. Ensure the activation of queues 7. Object generation 8. Configure the ICF Service 9. Configure security parameters in DOE

5 - 35

Continued …


5 - 35

©2011 Sybase, Inc.


Post-Installation for SAP NetWeaver Mobile 7.1

Steps continued…

10. Identify device attributes for registration 11. Obtain the port information

5 - 36


5 - 36

©2011 Sybase, Inc.


General Customization

Define Mobile Languages Allow administrator to maintain languages needed for smartphone scenarios (English is the default language) Define Mobile Currency shown in the following screen:

General Customized data which is downloaded to SAP NetWeaver Mobile 7.1 for master and transaction data is always a subset of the CORE SAP CRM data

5 - 37


5 - 37

©2011 Sybase, Inc.


Defining Date and Organization Filters

Date Filter is used for initial download of transactional data to SAP NetWeaver Mobile

7.1

Maintain separate date filter for each transaction object

Mobile Organization is transaction data that can also be filtered based on organization

Maintain separate combinations in different rows Done on Sales Org., Distribution Channel, Sales Office, Sales Group

5 - 38


5 - 38

©2011 Sybase, Inc.


Mobile Gateway Configuration

Steps for gateway configuration related to SAP CRM Sales:

1. Channel activation 2. Back-end search configuration 3. ESDMA generation 4. Synchronization extract enablement of data objects 5. Configure authorization download 6. Initial data load 7. Rule activation 8. Optional configuration 9. Background jobs and reports

5 - 39


5 - 39

©2011 Sybase, Inc.


Enabling Channel Activation

5 - 40


5 - 40

©2011 Sybase, Inc.


ESDMA Generation

Execute transaction SDOE_ESDMA_DESIGN

Perform on one client only, not in parallel to multiple clients

5 - 41


5 - 41

©2011 Sybase, Inc.


Sync Extract Enablement of Data Objects

Execute transaction code DO_SYNC_EXTRACT

SAP Basis Object and the USER DETAILS and USER_AUTHORIZATION are included in this

5 - 42


5 - 42

©2011 Sybase, Inc.


Initial Data Load

Business Partner initial data download prerequisite:

Mobile Sales for smart phone scenarios needs to be deployed RFC connections need to be maintained Data download will depend on the language specified

Technical steps

Go to report of initial download of Business Partner On selection screen specify your download criteria Run the report, and based on the above criteria, the system will download all data to the SAP NetWeaver Mobile 7.10 system Above steps will be executed by T-Code SMIGH in SAP CRM 2007 and T-Code SPRO in SAP CRM 7.0 systems

5 - 43


5 - 43

©2011 Sybase, Inc.


ESDMA Deployment Process for Sybase Unwired Platform

Log in to DOE system and launch ESDMA browser:

Click MAS_SMARTPHONE _SALES_V00 and click the “Download Bundles” link:

5 - 44


5 - 44

©2011 Sybase, Inc.


SAP Resources

NetWeaver Mobile 7.1 Architecture & Runtime overview

www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e04

8e20c-7246-2a10-e8a5-8b2b78b5b994

Requires member login

NetWeaver Mobile 7.1 Application Development Cycle

www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/204f

c387-6646-2a10-99b7-bba030bc3f68

Requires member login

SAP NetWeaver Mobile Library

http://help.sap.com/saphelp_nwmobile71/helpdata/en/ca/6fbd3

5746dbd2de10000009b38f889/frameset.htm

5 - 45


5 - 45

©2011 Sybase, Inc.







Customization


5 - 46


5 - 46

©2011 Sybase, Inc.


Before Customization…

Be familiar with the application’s:

Design

Architecture

Technologies

Frameworks

Components

Apple iPhone CRM and Windows Mobile Sales customizations are slightly different due to:

Technology stacks available Platform features Restrictions

5 - 47

The Sybase Unwired Platform Server will not, however, know the difference between


iPhone and Windows Mobile Sales applications.

5 - 47

©2011 Sybase, Inc.


Customizations and Enhancements

Customization

Mobile-specific technical configurations done in the CRM system Automatically delivered to the app as a customization object

Custom enhancements (CE)

Add new custom fields to existing objects without change to app Requires writing custom BADI code in the CRM application to inject the custom fields into the solution

5 - 48

Continued …


5 - 48

©2011 Sybase, Inc.


Customizations and Enhancements

Custom Extensions

The capability to extend and change the application with new business processes, rules, and custom processing. This capability requires customers and partners to work with the CRM mobile application APIs, library, and code.

Application Branding

The ability for the customer or partner to change the look and feel of the mobile CRM application Several personalization settings available in the application

5 - 49


5 - 49

©2011 Sybase, Inc.


Architecture Common to iPhone and Win Mobile

Four layers from bottom up:

SQL Lite Data Model Generated MBO Classes Application (CRM) Business Objects Application User Interface

5 - 50


Glue + Screen flow code

Application Business Objects (ABO)

- Hand Written

Consolidates access across multiple MBOs

and implements CRM business logic

Generated MBO

With SQL Interface

SQLLite

Data Model


5 - 50

©2011 Sybase, Inc.


SQL Lite Data Model

As defined and automatically created by generated classes when the application is initialized Tables created for:

Objects Nodes Other management data

All activity occurs on device Any change in the generated classes requires recreation of this data model Incremental updates on data model are not currently supported

5 - 51


5 - 51

©2011 Sybase, Inc.


Generated MBO Classes

MBO Classes are either C# (Windows Mobile) or Objective C (iPhone) Generated on the Unwired Server by:

Taking an AFX document that is generated from a ESDMA Running the TemplateJ engine for code generation

MBO classes represent Object Relationship Mapping (ORM) code between attributes of ESDMA object and nodes to SQL table column definitions Ensures that the attribute type info is maintained and converted when working with database column types

Relationships not maintained but flattened to independent tables

Only one level of parent-child relationship from ESDMA to generated objects is handled

5 - 52


5 - 52

©2011 Sybase, Inc.


Application Business Objects (ABOs)

Reusable layer of abstraction consisting of application business objects Incorporate business and functional knowledge of the CRM application Built on top of the generated MBOs Defined top-level ABOs to be used by the UI frameworks are:

5 - 53

Account Contacts Activities Leads Opportunity Sales Order Analytics

Continued …


5 - 53

©2011 Sybase, Inc.


Application Business Objects (ABOs)

These ABOs provide everything that the UI frameworks require to build the application The ONLY layer of data and operations that the application UI interacts with MBOs define a layer of supportable contract for application customization, extensibility and support

5 - 54


5 - 54

©2011 Sybase, Inc.



Top-most layer of the application that generates the screens and screen flows Built on top of several well-structured and componentized modules of code and functionality 1. Project Build Template

Defines dependency and compilation structure for application

5 - 55

Components Libraries Resources Files Bundles Graphics and Images Certificates Subprojects

Continued …


5 - 55

©2011 Sybase, Inc.



Project Build Template (Cont’d)

Represented by the IDE project template files (VS or Objective C) Capture all internal and external dependencies needed to compile, build and generate the deployable unit Defines the nonfunctional shell of the application

2. Application Template

Defines the common functional application and shell

Core structure Organization of the UI code Various frameworks used

Example – use of login/logout screens, idle timeouts, re-authentication, headers, footers, common function structures, menu structure, etc.

5 - 56

Continued …


5 - 56

©2011 Sybase, Inc.



3. Configuration Files

External human readable and editable files used for application configuration without need for any recompile Represent most of the implementation strategy for customization

4. UI Framework

Set of services for commonly needed capabilities for Windows Mobile Application UIs Uses well-defined stacks, wizards, and more Represents a best practices of Windows Mobile application development application to any mobile application

5 - 57

Continued …


5 - 57

©2011 Sybase, Inc.



5. Resco Control Templates

Third-party supplier of rich graphics components and widgets for Windows Mobile Includes types of list, table and chart controls Based on an external XML template file specifying attributes, location, placement, and size

Different types of presentation such as device resolution, landscape vs. portrait orientations, and UI styles, require different versions of this file

iPhone uses a similar but different approach to the application’s design

5 - 58

Continued …


5 - 58

©2011 Sybase, Inc.



Language and Resource Bundles

Primary units for language, locale, and branding customizations Contains all literal strings, images, icon references and local information used by the application

Images and Icons

All graphics and icons are organized using a well-defined structure in the project bundle Multiple sets are required since graphics and icons are sensitive to disparate resolutions Typically branding is the first level of customization

5 - 59


5 - 59

©2011 Sybase, Inc.


SAP Mobile Sales Customization

All customization in this area is performed by an SAP expert For details, read the “Configuration Guide – Mobile Gateway 1.0” documentation

Available from the SAP Service Marketplace

All SAP backend customizations are automatically handled by the standard Sybase Mobile Sales CRM application

5 - 60


5 - 60

©2011 Sybase, Inc.


CE Table Enhancements

Allows CRM developers to deliver attributes associated with backend CRM entities not exposed in the current ESDMA

Example:

CRM schema might contain a “language” attribute associated with a partner object which isn’t present in the current ESDMA Can use CE Tables to expose the language attribute and make it available to mobile device This does not require a change to the ESDMA or an adjustment to the data entities that are mobilized on the device

5 - 61

Continued …


5 - 61

©2011 Sybase, Inc.


CE Table Enhancements

Enhancements are performed by creating or modifying BADIs

BADIs are specialized add-ins to the BAPI wrappers used to push data from CRM to DOE to Device Requires a detailed understanding of the CRM system

Therefore, the creation or modification of BADIs is performed by the CRM functional experts

For more detailed information about available CE tables and how to populate these tables, read Sybase’s white paper “Sybase Mobile Sales for SAP ® CRM” Implementation of Custom Extensions is different for iPhone and Windows Mobile

5 - 62

Implementation of custom extensions require manipulation and changes to source code.


5 - 62

©2011 Sybase, Inc.


Implementing Custom Extensions for iPhone

Consists of a structure of three projects in Xcode

1. icrm – iPhone main application project containing the UI source code that generates the application executable for deployment 2. abo – Application business object (ABO) project containing the data model and business logics of icrm application

Static library project that generates a libabo.a file

3. mbo – Database model object generated from the ESDMA bundle

Contains source code files generated by the Sybase Unwired Platform code generation process Generates a libmbo.a file Do NOT modify files in this project

5 - 63

Continued …


5 - 63

©2011 Sybase, Inc.



The icrm project

Classes Common: contains utility classes and classes commonly shared by the entire project Classes Controllers: contains UI screen implementation classes Classes Includes – contains interfaces files provided by the abo project Classes Workflow – contains Sybase Mobile Workflow application implementation classes Classes Views – contains UI screen for the graphical report view

Resources: contains resource strings files, UI design (xib) files, and images files

5 - 64

Continued …


5 - 64

©2011 Sybase, Inc.



Rebranding the UI

1. Change application images and icons

To change an image or icon used in the application, for example, the accounts icon, create an icon file called “accounts.png” and copy this file to the Resources Images folder

2. Change UI strings

Locate the CRM.strings file in the Resources Strings files folder and update the value of the string identified by the key

3. Change application name - default application name is “Mobile Sales”

Locate the CRMBranding.strings file in the Resources String files folder and change “Mobile Sales” to the new name

5 - 65

Continued …


5 - 65

©2011 Sybase, Inc.



Rebranding the UI

4. Add a new locale file

Supported languages are English, French, German and Japanese For a new language, translate the CRM.strings content to the new language Use Xcode to add a new localization file to the project Associate this new language file to this new localization support to the project

Any changes to the UI require you to rebuild and re-sign the application

5 - 66

Continued …


5 - 66

©2011 Sybase, Inc.



The abo project:

Include: contains interface files “.h” files

The same interfaces files are in the icrm Classes Includes folder

Common: contains utility classes and common classes Model: contains implementation classes

Any changes to this project requires recompilation and a rebuild to generate a new libabo.a file

5 - 67

Continued …


5 - 67

©2011 Sybase, Inc.



The mbo project

Sybase recommends no changes to this project If changes are required, they should be made in the meta model file and have the code generation engine to generate the files into this project If changes are made to the generated files, the project must be recompiled and rebuilt to generate a new libmbo.a file

5 - 68

Continued …


5 - 68

©2011 Sybase, Inc.



Adding a new entity to the application requires 2 major tasks:

1. Add data model and business logic to the abo layer:

In the abo project, add three interface files into the includes file group: XXXDatasouce.h, XXXEntity.h, XXXEntityDetail.h

See the interfaces and properties in the CRMAccountDatasource.h, CRMAccount.h, and CRMAccountDetail.h files for reference

Add the corresponding implementation to each interface to the “model” folder

See the implementation in the CRMAccountDataSource.m, CRMAccount.m, and CRMAccountDetail.m files for implementation details

Rebuild the project and generate the libabo.a library

5 - 69

Continued …


5 - 69

©2011 Sybase, Inc.



2. Add the UI to the icrm project:

Add UI implementation files to the controllers file group to render a new entity to the UI Add three header files: XXXViewController.h, XXXDetailViewController.h and XXXEditViewController.h

See the CRMAccountViewController.h, CRMAccountDetailViewController.h, and CRMAccountEditViewControler.h files for interface and properties information

5 - 70

Continued …


5 - 70

©2011 Sybase, Inc.



2. Add the UI to the icrm project (continued)…

Add the corresponded implementation files to the “Controllers” file group

See the CRMAccountViewController.m, CRMAccountDetailViewController.m, and CRMAccountEditViewController.m files for implementation reference

Rebuild the project and generate the icrm.app executable

5 - 71


5 - 71

©2011 Sybase, Inc.


Implementing CEs for Windows Mobile

Visual Studio 2008 projects:

CRMDataEntities: contains compiled MBO code autogenerated from ESDMA CRMUtils: contains some support utility classes CRMBusinessObjects: contains the ABO (application business objects) layer SybaseCRMPro: the UI project for Professional SybaseCRMStd: the UI Project for Standard SybaseCRMControls: the project for UI controls

There are some additional projects for CAB generation and menu extensions used to enhance native PIM applications (Contacts/Calendar/Mail)

5 - 72

Continued …


5 - 72

©2011 Sybase, Inc.



CRMDataEntities Project

Encapsulates the generated files produced by converting the ESDMA bundle to C# classes Change this project ONLY if a new code generator is available, producing different code from the same ESDMA, or if the ESDMA itself changes The build result from this project is a single cross-platform DLL: CRMDataEntities.dll

CRMUtils Project

Contains some useful utility classes Likely that no changes here will be necessary, unless additional support classes are required, or if bugs are discovered in these classes

5 - 73

Continued …


5 - 73

©2011 Sybase, Inc.



CRMBusinessObjects Project

Contains the main ABO layer and mediates all access to the CRMDataEntities layer

UI layer has no exposure at all to the classes in CRMDataEntities.dll

Reflect Main SAP objects (Accounts, Contacts, Leads, Opportunities, etc.) Classes that represent these entities are structured using a core class (for example, AccountCore) that contains base functionality and a top level class (for example, Account) that mostly extends the base class The top-level class is presented using partial classes, with the assumption being that end users will modify the code in the top-level partial class, overriding functionality inherited from the core class

5 - 74

Continued …


5 - 74

©2011 Sybase, Inc.



SybaseCRMPro/SybaseCRMStd Projects:

UI layer projects which access the CRMBusinessObjects layer to obtain and work with SAP-related entities The code in these projects uses Resco XML templates to actually render the UI

These templates are included directly in the projects (there is a different set for Standard and Professional devices) Sybase anticipates that most UI related changes can be carried out by changing only the XML templates

Code changes to these projects are required only if logic changes are needed in terms of how the UI is to be rendered

5 - 75

Continued …

Currently, menus are explicitly defined in the code, rather than in XML or configuration


files, so changes to the menu structure will require changes to the project itself.

5 - 75

©2011 Sybase, Inc.



SybaseCRMControls Project:

Certain controls are defined in this project If changes to control behavior (for example, specialized menu bars, and so on) are required, those changes will be made in this project

5 - 76


5 - 76

©2011 Sybase, Inc.


Customization Files for Windows Mobile

Windows Mobile uses a variety of editable XML files to control how screens are rendered Generally, such changes will be carried out by partners who are delivering a solution to an end user, and will be carried out prior to deployment to the end-user devices There are also images and language resource bundles that are shipped with the device Can make significant changes to an application’s look and feel by modifying these XML, image, and resource bundles, along with the templates used to hold initial copies of the settings used by the application

5 - 77

Continued …


5 - 77

©2011 Sybase, Inc.



Customization can be done via:

1. XML Templates 2. Images 3. Language Resource Bundles 4. Configuration File

1. XML Templates

Used to control how fields are positioned on the screen Changes might include:

Rearranging or hiding fields and Changing field size Changing fonts Altering colors

The XML files are located in the …\Templates\UI\Pro (or Std) directories

5 - 78

Continued …

You must understand the structure of the XML files, but this should not be a significant


challenge. The XML files are used by Resco controls and documentation is readily

available that describes how the XML file is structured.

5 - 78

©2011 Sybase, Inc.



2. Images:

Used by the application are located in the …\Resources\Images directory Can replace images with alternative images Image file name must remain the same, but the image content can be changed

3. Language Resource Bundles:

Located in the language directories (for example, …\de) Can develop new resource bundles for new languages

4. Configuration File

Located in the …\Templates directory At application start-up, a copy is made into the …\Data directory May choose to ship a default copy with changes that are suited to your requirements

5 - 79


5 - 79

©2011 Sybase, Inc.


Application Enhancement

“Application enhancement” means that you can make changes to the application source code May include any or all of the types of the following enhancements

ABO Extensions UI-Level Enhancement ABO Class Changes ESDMA Enhancements

5 - 80


5 - 80

©2011 Sybase, Inc.


ABO Extensions

If changes to the ABO layer are required, should first:

Write extension classes that enhance the standard ABO components These classes can then override or extend functionality exposed in the ABO classes

The MBO and ABO layers remain untouched

The extension classes form an additional layer which holds all the required changes The existing UI code (with the XML templates) then utilizes the extended ABO classes

5 - 81


5 - 81

©2011 Sybase, Inc.


UI-Level Enhancement

If changes to the UI are required that are not deliverable using changes to the XML templates:

Must make code changes to the UI layer to enable the required UI behavior Ideally, all UI changes should be encapsulated in changes to the XML templates as described earlier

5 - 82


5 - 82

©2011 Sybase, Inc.


ABO Class Changes

Can modify the ABO layer directly

However, this is required only if it is impossible to implement the required changes using one of the approaches already discussed

5 - 83


5 - 83

©2011 Sybase, Inc.


ESDMA Enhancements

When enhancing the data entities, must decide if changes can be accommodated within CE tables, or whether the changes require an enhanced ESDMA An enhanced ESDMA requires these steps:

1. A new set of generated MBOs 2. Either ABO partial classes are written or existing ones modified to expose or handle the changed data entities as exposed in the MBOs 3. Possible changes made to actual ABO classes 4. XML template changes made as appropriate 5. UI code changes only if absolutely necessary

5 - 84


5 - 84

©2011 Sybase, Inc.







Customization


5 - 85


5 - 85

©2011 Sybase, Inc.



Deployment and Administration of mobile apps use Sybase Control Center:

5 - 86


5 - 86

©2011 Sybase, Inc.


Registering the Mobile Device in Sybase Unwired Platform

Sybase Unwired Platform Admin must register the user device in the Sybase Control Center

Server Name is the name of the Relay Server Default port is 80 but configurable Company ID is the farm ID registered

Example - MyCompID.1080

Configure an activation code

Example - 12345

These details will need to be entered by the user in the “Sybase Settings” application on Windows Mobile or in the Settings screen on the Apple iPhone

5 - 87


5 - 87

©2011 Sybase, Inc.


Installing SAP Mobile Sales CRM Application

Windows Mobile and BlackBerry

In production, Afaria Server should be used to deploy the application ActiveSync for Windows Mobile devices can be used for testing deployments

iPhone

Available for download from the Apple AppStore Users can also deploy the app using the iTunes software with the device connected via cable to laptop/desktop

Once the client is installed, configure the device’s “Settings”

SCC Admin sends user the information needed to activate the client Software will try to connect to the relay server and in turn to Sybase Unwired Platform

User can then start SAP Mobile Sales CRM on the device and enter user ID and password

5 - 88


5 - 88

©2011 Sybase, Inc.




5 - 89


5 - 89

©2011 Sybase, Inc.


Module Summary


Benefits of Sybase SAP Mobile Sales application More details about the application architecture itself and the components required to run the application Customization options for the SAP Mobile Sales application How to install the client application on to a device

5 - 90


5 - 90

©2011 Sybase, Inc.



There are no post-assessment questions in this module

5 - 91


5 - 91

©2011 Sybase, Inc.



5 - 92

©2011 Sybase, Inc.

Sybase Unwired Platform Architectures and Technical Overview Module 6: Sybase Mobile Workflow for SAP Business Suite Technical Overview Version 1.0


Technical Overview

Module 6:

Sybase Mobile Workflow for SAP

Business Suite Technical Overview





6 - 1

©2011 Sybase, Inc.



1. On which device platform is the Sybase Mobile Workflow for SAP application supported?

2. True/False: There are a series of tasks and activities that need to be performed on the SAP side of the solution to implement the Sybase Mobile Workflow for SAP application.

3. True/False: There is absolutely no customization available for Sybase Mobile Workflow for SAP Business Suite.

6 - 2



6 - 2

©2011 Sybase, Inc.


Module Objectives


Understand environment components and support provided with the platform for Sybase Mobile Workflow for SAP Business Suite Sybase Mobile Workflow for SAP customization options

6 - 3


6 - 3

©2011 Sybase, Inc.


6 - 4


Sybase Mobile Workflow for SAP Business Suite Overview

Sybase Mobile Workflow for SAP Customization


6 - 4

©2011 Sybase, Inc.


SAP User Benefits

Take action immediately on the mobile device … No need to return to the desktop Execute within familiar SAP “inbox” … No need for special applications Increase Return on Investment in wireless email and SAP Business Suite

Workflow

Mobile workflow

Faster decision execution on

1

Business Reason

& Alerts

inbox

incoming workflows

2 Leave & Travel

Requests

Request approval

for absence & travel

Maximize user and

manager productivity

Time

Facilitate time

3

Recording

recording

Improve daily

operational activities and

accuracy

6 - 5

Keep in mind that Sybase Mobile Workflow for SAP is NOT the same as Sybase Unwired


Platform Workflows. Customization for Sybase Mobile Workflow for SAP is limited,

whereas your business needs will drive your development for a workflow application

developed in Sybase Unwired WorkSpace.

6 - 5

©2011 Sybase, Inc.


Business Process Acceleration

End-to-end:

Roles

Staff/Employee

Operational

_M_a_n_a_g_e_r

Processes

Mobile Inbox

ERP

ERP

ERP

Receive

Submit request

Review

Submit

Proceed to next

step in

workflow engine

Send answer

Request

workflow

via workflow

request

approval

to requestor

approved

item

• Universal work list supporting workflow and alert items

• Notification support for missed workflow deadlines

• Workflow decision buttons made available for approval

• Enables processing of any decision-based workflow items supported by SAP

6 - 6

• Access to approve workflow items while away from the desktop

• Helps increase operational efficiency by providing up to the minute notifications on required approval decisions

Functionality

6 - 6

©2011 Sybase, Inc.

Benefit



High Level Requirements

Sybase Unwired Platform:

Sybase Unwired Platform 1.5.5 Deployment Edition

SAP requirements:

ERP 6.0 EhP4 SP05

Supported devices:

Windows Mobile Professional 5 - 6.5 Apple iPhone and iPod Touch 3.1.3 - 4.1

Set up an appropriate security configuration for Mobile Workflow on your Unwired Platform installation using the Sybase Control Center Supported by Afaria 6.6 mobile device management and security

6 - 7


6 - 7

©2011 Sybase, Inc.


Application Requirements

Windows Mobile device prerequisites

Microsoft ActiveSync 4.5 or later

Allows synchronization of files between the Sybase Unwired Platform machine and a Windows Mobile device or emulator

.NET Compact Framework 3.5 or later

iPhone device prerequisites

Apple iTunes 9.0 or later

Allows synchronization of files between the Sybase Unwired Platform machine and an iPhone device

Using Sybase Control Center, register each device and assign the SAP Workflow to each device so it can connect to Unwired Server

6 - 8

For each device, note the user name, Unwired Server name, Unwired Server port number,


relay server farm ID (if applicable), and activation code.

6 - 8

©2011 Sybase, Inc.


Posting Client Files for Users

SAP Mobile Workflow application for iPhone

Users may download the iPhone client through iTunes or directly from the App Store to the device

Windows Mobile clients

Must provide a means for users to download the application

Arrange a location on a company Web server where you can post the Windows Mobile clients for users to download

From the device, users should be able to simply execute a link to the appropriate client file in this location to download the client to the device

6 - 9


6 - 9

©2011 Sybase, Inc.


Process Components

Workflow package hosted in the Unwired Platform for all mobile device clients Custom function modules (RFCs) in the SAP back end integrate using JCO Connector with mobile business object (MBO) package that is deployed into the Unwired Platform runtime:

6 - 10

SUP Protocol

Devices

Above is the overall architecture for SAP Mobile Workflow application using the new


JCO connector product. The product is built on top of Sybase Unwired Platform and used

for mobilizing SAP workflow inbox to mobile device of each SAP workflow user.

6 - 10

©2011 Sybase, Inc.


Process Flow

To receive a new work item:

1. In the SAP Workflow system, an exit component program pushes out new work items to Mobile Workflow users

The message push is performed through the WF-DCN channel in the Unwired Platform server

2. When the Unwired Platform server receives the new work item ID, it triggers the Unwired Platform Workflow package and uses the ZSUP_MWF_WI_GETDETAIL function module to retrieve work item details 3. The Unwired Platform server converts the work item to a Mobile Workflow message, based on the Unwired Platform definition 4. The workflow message is pushed out by Unwired Server to the device, which appears in the Mobile Inbox

6 - 11

Continued …


6 - 11

©2011 Sybase, Inc.


Process Flow

To complete a Work Item

Device user opens the work item in the Mobile Inbox and selects a decision

The decision triggers an asynchronous request to the Unwired Platform server

2. Work item message in the Mobile Inbox is marked as processed and the mobile user cannot select a different decision 3. Inside Unwired Platform, the workitem MBO’s completion operation is executed and the ZSUP_MWF_WI_COMPLETE function module is called at the backend 4. Work item is completed and removed from the SAP Inbox

A delete message for the work item is pushed from the back end to Unwired Platform via the WF-DCN channel

5. When the delete message is received by the device, the message in the Mobile Inbox is removed

6 - 12


6 - 12

©2011 Sybase, Inc.



Sybase Mobile Workflow for SAP Business Suite Overview

Sybase Mobile Workflow for SAP Customization

6 - 13


6 - 13

©2011 Sybase, Inc.


Customization Requirements

Custom Repository Objects must be created for customization

Dictionary Objects Class Library/Classes Function Groups/Function Modules Includes SET/GET Parameters

Set the SAP Mobile User in the backend system Set the SAP Mobile Destination Customize the Workflow Template

6 - 14


6 - 14

©2011 Sybase, Inc.


Dictionary Objects

Custom Repository Objects must be created for

customization

Dictionary Objects:

6 - 15

See “Sybase Mobile Workflow for SAP ® Business Suite 1.2” white paper for a complete


task outline on how to create these objects.

6 - 15

©2011 Sybase, Inc.


Class Library/Classes

Class Library/Classes:

Creating the class in SAP:

6 - 16


6 - 16

©2011 Sybase, Inc.


Function Groups/Function Modules

6 - 17


6 - 17

©2011 Sybase, Inc.


Other Objects

Includes:

SET/GET Parameters:

6 - 18


6 - 18

©2011 Sybase, Inc.


SAP Mobile User

In the back-end system, enable the SAP user as a Sybase Mobile Workflow user Use the ZSUP_MWF_ENABLED parameter in the Parameters tab of the SU01 transaction:

It is automatically set when activation is completed from a user’s mobile device for the assigned Sybase Mobile Workflow package

6 - 19

If a user no longer wants to receive e-mail messages from his or her mobile device, the


administrator removes the “X” flag in the Parameter Value column to stop the back-end

system from pushing any new work items to this user. At the same time, the administrator

should also use Sybase Control Center to un-assign the Sybase Mobile Workflow package from the users’ device.

6 - 19

©2011 Sybase, Inc.


SAP Mobile Destination Setting

Use transaction SM59 to set up the destination Steps:

1. Create a destination to your Sybase Unwired Platform installation as “HTTP Connections to External Server” configured with the Unwired Platform server’s DCN port and host name

Configure the connection to use the DCN servlet that supports HTTP BASIC authentication

If you test the connection, ignore the HTTP error code

6 - 20

Continued …


6 - 20

©2011 Sybase, Inc.



6 - 21

Continued …


6 - 21

©2011 Sybase, Inc.



2. Specify the user name and password as defined by your Sybase Unwired Platform administrator:

6 - 22


6 - 22

©2011 Sybase, Inc.


Workflow Template Customization

In the SAP Workflow Builder (transaction SWDD), open the workflow definition for the workflow containing the decision step to be mobilized Identify the user decision task to be pushed to your users’ Mobile Inbox:

6 - 23

Continued …


6 - 23

©2011 Sybase, Inc.



Open the user decision step by double-clicking, or right- clicking and selecting Change Click the Program Exits tab to add the class created for this purpose

Set up the ZCL_SUP_MWF class:

6 - 24

Continued …


6 - 24

©2011 Sybase, Inc.



On the next tab, Properties, configure the settings for the Mobile Workflow push:

See notes for details

6 - 25

sup.mwf.destination: The name of the destination to the Unwired Platform server (see SAP Mobile


Destination Setting)

sup.mwf.qname: A name that is unique to the particular workflow. If the property is not declared, outgoing requests do not go through a queue, and the notification might be lost if Unwired Platform is unavailable.

sup.mwf.qcount: The number of queues to which to distribute outgoing notifications. If the property is not declared, a single queue is used to push notifications to Unwired Platform.

sup.mwf.match: Allows a specific Unwired Platform workflow package to be associated with a specific decision task by using the workflow package matching rules in the Unwired Platform design or runtime configuration.

sup.mwf.security: The name of the security configuration in Unwired Platform that is used to authenticate incoming device users against Unwired Platform (for example, “admin”).

sup.mwf.sender: Contains the default sender address that appears in the Mobile Inbox for notifications originating from this decision task.

sup.mwf.sender.l10n: Allows you to specify alternative localized versions of the sender text as a comma-separated list (for example, “en,es,fr”). Based on the agent’s default system language, a localized sender text is chosen during runtime.

sup.mwf.sender.en: The sender text for users with a default language set to English (EN). If more than one alternative is configured, you can add more properties (for example, “sup.mwf.sender.es” and “sup.mwf.sender.fr”).

sup.mwf.priority: Specifies whether the notification on the mobile device is marked as high priority (a red exclamation mark) or with default priority.

sup.mwf.markread: Specifies whether the notification is created on the mobile device as a read or unread notification.

6 - 25

©2011 Sybase, Inc.


Communication Troubleshooting

Use Transaction SMQ1 to monitor a work item notification that is stuck in the system

May be caused by either a configuration error or a physical network problem To resolve such an error, manually restart the queue

6 - 26


6 - 26

©2011 Sybase, Inc.


Importing the Workflow Project

Product installs into the $SUP_ROOT$\SMW for SAP Business Suite directory Two ways to apply the Unwired Platform deployment packages:

Directly into an Unwired Platform installation Import the development project files into Unwired WorkSpace

These files are installed:

SMW-JCO.zip – development and design-time project files SUP_MWF.jar – MBO deployment package MobileWorkflow.zip – Sybase Mobile Workflow deployment package

6 - 27

Continued …


6 - 27

©2011 Sybase, Inc.


Importing the Workflow Project

Steps:

1. Unzip the SMW-JCO.zip file to a folder 2. Select File > Import to add the project to the open workspace 3. Navigate to where you unzipped the project, then click Next and Finish 4. Import the SAP connection template into Enterprise Explorer 5. In the Project folder, select SMW_SAP_Default_Endpoint.conn

6 - 28


6 - 28

©2011 Sybase, Inc.


Mobile Application Diagram

MBOs in the diagram are already mapped to the interfaces of the function modules mentioned earlier:

Services MBO Workitem MBO Alternatives MBO

All the MBOs are located in the Cache Group “default,” which uses the cache policy “Online”

6 - 29

MBO is designed to map to the created ECC Remote function modules.


6 - 29

©2011 Sybase, Inc.


MBO Details

Alternatives MBO:

Definition of this MBO maps to the ALTERNATIVES table, which is returned from the ZSUP_MWF_WI_GETDETAIL function module All the available decisions for the current work item are modeled in this MBO

Services MBO:

Pure service MBO with no attributes itself The operation “UserActivation” activates the Sybase Mobile Workflow user The operation is mapped to the ZSUP_MWF_ACTIVATE BAPI function module interface definition

6 - 30

Continued …


6 - 30

©2011 Sybase, Inc.


MBO Details

Workitem MBO:

Definition of this MBO maps to the ZSUP_MWF_WI_GETDETAIL function module, which retrieves the work item details based on the WI_ID pushed via the WF-DCN channel The “WorkitemCompletion” operation is mapped to the ZSUP_MWF_WI_COMPLETE function module, which records a mobile user’s work item decision

Used to approve/reject a workflow

6 - 31

The load operation of this MBO maps to ZSUP_MWF_WI_GETDETAIL BAPI function


to retrieve the workitem details basing on the WI_ID pushed from ECC via WF_DCN

channel. The object query will be created by Sybase Unwired Platform and load parameters are propagated to Attributes of this MBO in the case the workflow page needs to use these attribute values in the workflow design.

6 - 31

©2011 Sybase, Inc.


Workflow Template

Workflow screens defined in the Mobile Workflow Forms Designer are shown in Sybase Unwired WorkSpace Note that the screen flow contains starting points for device activation, email notification server-initiated, credentials, and client-initiated flows:

6 - 32

Server-initiated flow:


1. Sets the notification start point to extract information from the message pushed over the

WF-DCN channel.

2. Invokes the findByParameter object query generated onto the Workitem MBO.

3. Defines the Work item detail screen on the device side and operation invoked for completion.

6 - 32

©2011 Sybase, Inc.


Application User Interface Customization

Most of the customization that will affect how a users experience the application will be made using the workflow template To customize the user interface of Sybase Mobile Workflow for SAP Business Suite, you would use this template to add or remove fields or screens based on the customizations made on the function modules and MBO package

6 - 33


6 - 33

©2011 Sybase, Inc.


Default Screen User Interfaces

Examples:

Client-initiated

Welcome

Activate

Screen

Screen

6 - 34

Credentials

Screen

Continued …


6 - 34

©2011 Sybase, Inc.


Default Screen User Interfaces

Server-initiated

Screen

6 - 35


6 - 35

©2011 Sybase, Inc.




6 - 36


6 - 36

©2011 Sybase, Inc.


Module Summary


General architecture and benefits of Sybase Unwired Platform Workflow for SAP Business Suite How to import the development project into Unwired WorkSpace How to administer and deploy the workflow application Customization options available for the Sybase Unwired Platform Workflow for SAP Business Suite application

6 - 37


6 - 37

©2011 Sybase, Inc.



1. Which component in the architecture interacts between Sybase Unwired Platform MBOs and the BAPI custom functions in the SAP system?

2. What is the mechanism in Sybase Unwired Platform used to alert the device that there has been a change to the data?

3. Name at least three Custom Repository Objects that must be created in the SAP system for customization.

6 - 38



6 - 38

©2011 Sybase, Inc.

Sybase Unwired Platform Architectures and Technical Overview Module 7: Administering Sybase Unwired Platform Environments Version 1.0


Technical Overview

Module 7:

Administering Sybase Unwired

Platform Environments





7 - 1

©2011 Sybase, Inc.



1. What is the product component used to administer the SAP Mobile Workflow for SAP package?

2. True/False: The administration component of Sybase Unwired Platform can only administer packages for the server on which it is installed.

3. True/False: A clustered Sybase Unwired Platform implementation is not available to customers who have purchased the SAP Mobile Workflow for SAP product.

7 - 2



7 - 2

©2011 Sybase, Inc.


Module Objectives

Upon completion of this module, you should be able to understand:

Administration architecture and components Navigate the Sybase Control Center, Sybase Unwired Platform’s Administration tool Fundamental Unwired Platform administration tasks Monitoring Unwired Servers

7 - 3

This module is a basic introduction to the administration functionality of Sybase Unwired


Platform. If you are required to administer an Sybase Unwired Platform environment, you

must attend the SUP611: Sybase Unwired Platform Administration course.

7 - 3

©2011 Sybase, Inc.


Architecture


Introduction to the Sybase Control Center

Workflow Administration

Device Management

Monitoring

7 - 4


7 - 4

©2011 Sybase, Inc.


High-level Architecture

Sybase Control Center (SCC)

Web browser based monitoring and management utility for Sybase Unwired Platform environments

UAF Agent

Management infrastructure to administer an Unwired Server Runs a Web Server (Jetty Container) that hosts:

Server side of the web application Downloadable Flex plug-in to run in the client side browser

Runs an RMI service (JMX Agent) to talk to an Unwired Server Runs a JINI service to discover available Unwired Servers

7 - 5


7 - 5

©2011 Sybase, Inc.


Administration Components

Core Unwired Server Server components Replication-Sync Server Messaging-Sync Server Database components Consolidated, Cluster, and Monitor Database

Optional Relay Server Relay Server Outbound Enabler Afaria 6.5 Afaria Server Afaria Management Console (IIS) Afaria Database

SQL Anywhere 11.0.1.2045

Messaging Server Database

SQL Anywhere

Advantage Database Server 9.1

Afaria Client Service OpenDS LDAP Server Installed in Developer Edition

Management components Server (Unified Agent Service) Repository Database

SQL Anywhere 11

7 - 6

All Unwired Server components on one node work as one unit. If one of the component


goes down, all other components on the Unwired Server node will shutdown.

If consolidated database goes down, all the nodes in the cluster will shutdown.

Sybase Control Center (Management component) is outside agent and remains up.

7 - 6

©2011 Sybase, Inc.


Component Model

Unwired Cluster

Consolidated

Database (SA)

Unwired Server Node (1 n)

Cluster

Database (SA)

Management Agent

Unwired Server

Messaging

Database (ADS)

Relay Server

Replication Sync subsystem

Messaging Sync subsystem

Monitor Database

Outbound Enabler

Relay Server

Security Server (LDAP, Windows OS,…)

7 - 7


7 - 7

©2011 Sybase, Inc.


Sybase Control Center Architecture

Node n


Browser

Web Container

RMI

Flash

Service

Plug-in

HTTPS

SUP Flex

Unwired Server

Web Application

SCC Plugin

SNMP

for SUP

IIOPS

SNMP Service

Client

SNMP

SUP SNMP

IIOP

Plugin

Custom

Admin

RMI

Java

Client

Node 1

MBean Interface

7 - 8

This is a view of the Integrated Multi-Cluster/Multi-node Administration architecture.


7 - 8

©2011 Sybase, Inc.


Administration Options in Sybase Control Center

Authentication Provider

Replication Sync

Administrators

Security Configuration

Authorization Provider

Messaging Sync

Application Users

Role Mappings

Attribution Provider

Messaging Queues

Users

Audit Provider

Data Change Notifications

Subscriptions

Messaging Devices

Security Configuration

Synchronization Groups

Device Notifications

Replication Devices

Cache

Cache Groups

Matching Rules

Devices

Monitoring Configuration

Context Variables

Logging (Package and Client)

Monitoring Profiles

MBO Package

Users (Devices)

Monitoring

Security

Server

Errors

Configurations

Connections

Cluster Wide

Domain

Mobile Workflow Package

Server Communication Ports

Replication Synchronization Configuration

CDB Configuration

Messaging Synchronization Configuration

Performance Configuration

Log Configuration

Server

Server Specific

7 - 9


7 - 9

©2011 Sybase, Inc.


Administrator Types

Two Administrators Types:

Platform Administrator Domain Administrator

Platform Administrator has Cluster-wide administration rights

Super user of the platform Domain management, Server configuration, Device Registration, Monitoring, and Package Deployment and Management Has all of the domain administrator rights as domain owner

Domain Administrator has rights to perform Domain manager tasks

Package deployment and management, server connections, security configuration and role mapping Access to those domains that platform administrator grants

7 - 10


7 - 10

©2011 Sybase, Inc.


Runtime Databases to Consider

As an administrator, you need to be aware of the following databases:

Consolidated Database

Acts as the synchronization cache for mobile business object (MBO) data Contains Unwired Server properties Tracks Push subscriptions and status Contains synchronization timestamps for each device client Contains user data, such as personalization keys and device tracking information

7 - 11

Continued …

If you install multiple Unwired Servers in a load-balancing cluster, all Unwired Servers in


the same cluster must share a CDB; however, in this scenario, a CDB failure can introduce

a single point of failure for Unwired Platform. To mitigate this risk, you can run the CDB

in failover mode using a shared-disk cluster.

7 - 11

©2011 Sybase, Inc.



Messaging Database

Stores in-flight messages in a messaging cache as part of a queue so they can be delivered By default, an embedded Advantage Database Server is used as the messaging database Permanent store of device connection information:

During the first device connection, a physical device identifier is obtained by the messaging runtime client and is stored together with the connection information - Subsequently, the physical device identifier validates the device on every connection

Transient store for messages:

Holds business data only for a short amount of time. Once the data is delivered to the device, Unwired Server deletes the data from this database.

7 - 12

Continued …

Depending on your network or system topology, install the messaging database either with


the Unwired Server, or separately, on its own physical hardware. If you install multiple

Unwired Servers in a load-balancing cluster, all Unwired Servers in the same cluster must share the messaging database. Sybase recommends that you install the messaging database separately on a failover cluster that uses a shared-disk array. You can install the messaging database and consolidated database together on the same physical hardware.

Depending on you environment, the location of the messaging database file varies:

In cluster environment, the default file location is <UnwiredPlatform_InstallDir>\Data\Messaging\.

For all other environments, the default file location is <UnwiredPlatform_InstallDir>\Servers\MessagingServer\Data.

Unwired Server accept messages from the device, but only when the identity is valid. This validation occurs even before the actual mobile application is authenticated by an Unwired Server security provider.

7 - 12

©2011 Sybase, Inc.



Cluster Database

By default, a SQL Anywhere database used by the Unwired Server and associated command line utilities Contains configuration information about the cluster for which the database is installed, as well as data used to coordinate cluster components Records configuration properties that are set for each component

Populated during installation and then maintained over time as administrators use Sybase Control Center to change the production environment

Includes configuration information for components in a cluster and installation details for components and the corresponding operational state of each

7 - 13

Continued …

Depending on you environment, the location of the cluster database file varies:


In cluster environment, the default file location is

<UnwiredPlatform_InstallDir>\Data\CDB\clusterdb.db.

For all other environments, the default file location is <UnwiredPlatform_InstallDir>\Servers\UnwiredServer\data\clusterdb.db.

The sup.properties file is a copy of information from the cluster database that facilitates scripting. This file is located in <UnwiredPlatform_InstallDir>\Servers\UnwiredServer\Repository\Instance\com\sybase\ sup\server\SUPServer.If you are troubleshooting the cluster, always check the cluster values in this database first.

7 - 13

©2011 Sybase, Inc.



Monitoring Database

Stores data related to replication and messaging synchronization, queues status, users, data change notifications, and device notifications By default, uses the same database server instance as the consolidated database and cluster database Can install a monitoring database on host that is different from the consolidated or cluster database host Can be one of:

New SQL Anywhere database used only by Unwired Platform monitoring (default installation for Unwired Platform) Existing SQL Anywhere database already used in your environment Must set up Unwired Platform to use this database by configuring the database location

7 - 14

A monitoring database is shared by all server instances in a cluster. Consequently,


administrators must allocate and manage the database depending on the monitoring

configuration and system load.

If necessary, you can manually delete data, or you can use Sybase Control Center to allow Unwired Server to automatically purge the data. You can schedule a periodic and automatic flush of monitoring data that is captured in memory and move the data to the underlying monitoring database. This allows for capturing monitoring data without performance degradation of the client applications. If there are high levels of activity, Sybase recommends that you install the monitoring database on high performance hardware, and that you configure optimal flush settings for this environment.

7 - 14

©2011 Sybase, Inc.


Architecture




Device Management

Monitoring

7 - 15


7 - 15

©2011 Sybase, Inc.


Control Center Home Page

Menu bar contains

major view and areas

in the SCC

The toolbar is based on

tile views which can be

opened or closed via the

toolbar icons

The Unwired Cluster

Tree View

Most views contain

tabs – look inside

each

7 - 16

This is a view of the main page after the initial login.


7 - 16

©2011 Sybase, Inc.


Uses of the SCC

Sybase Control Center (SCC) allows you to:

Start and stop servers Create Domains Register replication and/or messaging devices Create security configurations (assigned to packages and domains) Deploy mobile applications and workflows to Unwired Server Monitor the health of the server environment See below

7 - 17

A complete list of what can be done with the SCC:

Unwired Server Administration:


Login/Logout

Start/Stop/Restart

View Server Properties

Log Configuration:

View log details Search entries Config server log lifecycle Sybase Unwired Platform Packages Management:

Create new package Deploy, MBO Package Management:

asdf Personalization Management:

Update pers. key description View pers. key value Subscription Management:

Delete subscription Config subscription properties Create subscription template Role Mapping:

Configure role mapping at server level Configure package role mapping Users Management:

Delete user

View and search users Server Administration:

Listener port Afaria host/port PUSH notification CDB threads Synchronization listener Connection Management:

Connection templates Endpoints (JDBC, SAP) Connection pools Cluster Support:

Multi-node cluster administration Multi-cluster administration Security Configuration:

Authentication

Authorization

Attribution

Audit

7 - 17

©2011 Sybase, Inc.


General Administration Tasks

7 - 18


7 - 18

©2011 Sybase, Inc.


Server Management

Maintenance

Start/Stop/Suspend/Resume server

Review Log

During troubleshooting and diagnostics Change sub-component log level Server log files are separate for each node and client requests could be spread over multiple logs if multiple servers in the cluster Messaging server has a separate configuration file for fine-grained control

JMSBridge: Outbound messages (server to client) SUPBridge: Inbound message (client to server) Set client log level in device settings and then send request to retrieve messaging client log (debugging purpose)

7 - 19


7 - 19

©2011 Sybase, Inc.


Creating Logins

Create logins by clicking the Application menu and selecting Administration

Logins are created

via the Security

folder:

7 - 20


7 - 20

©2011 Sybase, Inc.


Discovering and Registering Servers

Open Resource Explorer to view already discovered and registered resources (servers)

To register new ones and “add” them

Must add a server resource to Perspective Resources view before it can be managed

7 - 21


7 - 21

©2011 Sybase, Inc.


SCC Server Configuration

Select the Sybase Unwired Platform server to configure:

7 - 22


7 - 22

©2011 Sybase, Inc.


Consolidated Database Configuration

Review Consolidated Database configuration:

7 - 23


7 - 23

©2011 Sybase, Inc.


Performance Settings

Java VM Settings Max Heap size Min Heap size Thread Stack size Requires removing and re-installing server services Message Queues Inbound queue count Outbound queue count Replication-Synchronization Server Server thread count

Synchronization Cache size Consolidated Database Server SQL Anywhere thread count

Manual step using bat file

7 - 24


7 - 24

©2011 Sybase, Inc.


Server Log

Each discovered/registered Unwired Server has its own log

Can be displayed in text or grid view

7 - 25


7 - 25

©2011 Sybase, Inc.


Server Log Configuration

Log Settings Max log file size Number of backup files Sub-component log levels

Truncate Log

7 - 26

Note for cluster environments:


Log level changes done on Primary Node are automatically pushed to primary.

Changes done on secondary node will be overwritten when next cluster-sync occurs.

Recommend using Primary node for log-level settings.

Server log file is separate for each node.

7 - 26

©2011 Sybase, Inc.


Creating a Domain

Select Domains Click New and enter the domain name:

7 - 27


7 - 27

©2011 Sybase, Inc.


Operational Management

Logins

Create and remove

Users

Remove users Doesn’t prevent users from accessing application if they authenticate successfully subsequently

Mobile Workflow

Register and Assign new devices

Monitoring

7 - 28


7 - 28

©2011 Sybase, Inc.


Creating/Removing Device Users

Multiple users from single device and multiple devices for a user Deletion of user doesn’t release license Deletion of user cleans-up personalization data

7 - 29


7 - 29

©2011 Sybase, Inc.


Packages

Deploy and administer packages in the SCC:

These are MBOs in a

Package

7 - 30


7 - 30

©2011 Sybase, Inc.


Package Management

Subscriptions

Remove, recover, and so on to resolve application user issues RBS: Change push settings MBS: Change device settings

MBO History

Review and clean data refresh error history

Operation History

Review and clean operation replay errors

Client Log

Review and clean operation replay history log Application log (if used by application developer)

7 - 31

MBO/Operation history and client log data are stored in the consolidated database.


7 - 31

©2011 Sybase, Inc.


Architecture




Device Management

Monitoring

7 - 32


7 - 32

©2011 Sybase, Inc.


Workflow Package Deployment

Workflow Package Deployment Tasks

Choose Icon for the Workflow Configure context variables such as domain name if MBO Package is used by Workflow and any other context variables Configure Matching Rules to match email for the workflow Assign Devices to the workflow

Register Devices if not already registered

Upon successful activation from device, the Mobile Workflow will show in the Device Inbox and ready to use

7 - 33


7 - 33

©2011 Sybase, Inc.


Notification Mailbox

Notification Mailbox

Mail server host and port Mailbox username and password

One-time

Configuration

Task

7 - 34


7 - 34

©2011 Sybase, Inc.


Mobile Workflow Configuration

Displays icon Matching Rules

Email matching condition

Context Variables

Application-defined variables

Domain

name

where

MBO

package

used by

Workflow

is deployed

7 - 35


7 - 35

©2011 Sybase, Inc.


Workflow Devices

Devices

Assignment/Un-assignment

Queue Items

Reviewing device queue status

Error Log used to review device errors

7 - 36


7 - 36

©2011 Sybase, Inc.


Assigning Users to Workflows

Can assign or un-assign users to a workflow device:

7 - 37


7 - 37

©2011 Sybase, Inc.


Architecture




Device Management

Monitoring

7 - 38


7 - 38

©2011 Sybase, Inc.


Device Types

Replication-based Sync (RBS)

Application used from the device is Replication-based Sync

Messaging-based Sync (MBS)

Application used from the device is Messaging-based Sync Both (RBS and MBS) Minimum of one application of each type (RBS and MBS) on the same device (Windows Mobile device only) RBS/MBS Status of Registered means an device application user has successfully accessed a package MBS Status Registration Initiated: Administrator has registered a device and waiting for activation from device

7 - 39


7 - 39

©2011 Sybase, Inc.


Device Properties

For viewing additional MBS device properties, switch to MBS mode, and/or click on Properties button Each successfully registered device consumes one license

License count is displayed on cluster’s properties tab Multiple application on the same device still consume one

7 - 40

license


7 - 40

©2011 Sybase, Inc.


Device Management

Devices

Register new devices, change device settings, clone devices, and reregister devices Delete MBS devices

Frees up license Prevents user from accessing application

Delete RBS devices

Frees up license Doesn’t prevent user from accessing application if license is still available Lock device is the correct option for RBS

7 - 41


7 - 41

©2011 Sybase, Inc.


Server Communication Ports

Modify management port (IIOP and IIOPS) in the SCC

Add/modify Data Change Notification ports (HTTP/HTTPS)

7 - 42


7 - 42

©2011 Sybase, Inc.


Replication-Synchronization Configuration

Synchronization Port (HTTP or HTTPS)

Secure protocol configuration

Server’s Identity Certificate

Certificate Password

Replication-sync server thread count

Synchronization Cache size

Continued …

7 - 43


7 - 43

©2011 Sybase, Inc.


Replication-Synchronization Configuration

Device Notification (aka RBS Push) Configuration

Required configuration to enable device notification for RBS applications

Two types:

Push-based

Notifier

(For BlackBerry)

Pull-based

Notifier

(for Windows

Mobile)

7 - 44


7 - 44

©2011 Sybase, Inc.


Messaging-Synchronization Configuration

Fine-grained control (delivery frequency, etc.) via Subscription properties for each RBS package Set Synchronization Port (s) Apple Push Configuration (APNS)

Apple Push Gateway Host and Port Apple provided push certificate Application Name Requires Apple Developer License to get a certificate

7 - 45


7 - 45

©2011 Sybase, Inc.


Securing Data

Transport Security

Generate Self-signed or Use CA-issued Certificate Configure Unwired Server to use those certificates to secure:

Replication-based Synchronization Port Data Change Notification Port Administration Port Configure Sybase Control Center to use the secure port

Data Security

Secure Database Host Access Change Database Password

Manual step

Use Secure port for DCN and Replication-based Sync Use Secure port for administration

7 - 46


7 - 46

©2011 Sybase, Inc.


Architecture




Device Management

Monitoring

7 - 47


7 - 47

©2011 Sybase, Inc.


Monitoring Tasks

7 - 48


7 - 48

©2011 Sybase, Inc.


Server-level Monitoring

7 - 49


7 - 49

©2011 Sybase, Inc.


MBS Request History

7 - 50


7 - 50

©2011 Sybase, Inc.


User Statistics and Security Log

Messaging-

based

synchronization

Package User

KPIs

Different KPIs for

Replication-based

Package User

7 - 51


7 - 51

©2011 Sybase, Inc.


Device Notifications (RBS Push) History & KPIs

Available KPIs

7 - 52


7 - 52

©2011 Sybase, Inc.


Cache Statistics

Package-level

Cache Group:

Snapshot Data

Domain-level:

Usage Data

Package-level:

KPIs

7 - 53


7 - 53

©2011 Sybase, Inc.


Messaging Queues

Historical and Snapshot Data:

7 - 54


7 - 54

©2011 Sybase, Inc.




7 - 55


7 - 55

©2011 Sybase, Inc.


Module Summary

During the course of this module, you have learned how to:

Describe the administration architecture and its components Navigate the Sybase Control Center and perform general administration activities Check for Sybase Unwired Platform server status and deployed packages, MBO’s, etc. Register devices and assign workflows to devices Secure and monitor the Unwired Server

7 - 56


7 - 56

©2011 Sybase, Inc.



1. What is the purpose of a Domain in the Sybase Unwired Platform environment?

2. True/False: If you install the messaging database on its own physical machine, separate from the Unwired Server machine, Sybase Control Center will not be able to administer that database.

3. True/False: If you install multiple Unwired Servers in a load-balancing cluster, all Unwired Servers in the same cluster must share the messaging database.

7 - 57



7 - 57

©2011 Sybase, Inc.



7 - 58

©2011 Sybase, Inc.

Sybase Unwired Platform Architectures and Technical Overview Module 8: Afaria Device Management Architecture and Overview Version 1.0


8 - 1

©2011 Sybase, Inc.




8 - 2

©2011 Sybase, Inc.



8 - 3

©2011 Sybase, Inc.



8 - 4

©2011 Sybase, Inc.



8 - 5

©2011 Sybase, Inc.



8 - 6

©2011 Sybase, Inc.



8 - 7

©2011 Sybase, Inc.



8 - 8

©2011 Sybase, Inc.



8 - 9

©2011 Sybase, Inc.



8 - 10

©2011 Sybase, Inc.



8 - 11

©2011 Sybase, Inc.



8 - 12

©2011 Sybase, Inc.



8 - 13

©2011 Sybase, Inc.



8 - 14

©2011 Sybase, Inc.



8 - 15

©2011 Sybase, Inc.



8 - 16

©2011 Sybase, Inc.



8 - 17

©2011 Sybase, Inc.



8 - 18

©2011 Sybase, Inc.



8 - 19

©2011 Sybase, Inc.



8 - 20

©2011 Sybase, Inc.



8 - 21

©2011 Sybase, Inc.



8 - 22

©2011 Sybase, Inc.



8 - 23

©2011 Sybase, Inc.



8 - 24

©2011 Sybase, Inc.



8 - 25

©2011 Sybase, Inc.



8 - 26

©2011 Sybase, Inc.


Client types supported:


Android

Blackberry Symbian Palm Java Win32 Windows Mobile Professional and Standard

8 - 27

©2011 Sybase, Inc.



8 - 28

©2011 Sybase, Inc.



8 - 29

©2011 Sybase, Inc.



8 - 30

©2011 Sybase, Inc.



8 - 31

©2011 Sybase, Inc.



8 - 32

©2011 Sybase, Inc.



8 - 33

©2011 Sybase, Inc.



8 - 34

©2011 Sybase, Inc.



8 - 35

©2011 Sybase, Inc.



8 - 36

©2011 Sybase, Inc.



8 - 37

©2011 Sybase, Inc.



8 - 38

©2011 Sybase, Inc.



8 - 39

©2011 Sybase, Inc.



8 - 40

©2011 Sybase, Inc.




8 - 41

©2011 Sybase, Inc.



8 - 42

©2011 Sybase, Inc.

Appendix A: Answers to Pre/Post Assessments


Pre-Assessments:

Post-Assessments:

1.

There are no Pre-Assessments in this module.

Name at least three challenges that most enterprises face with their mobility strategies.

Answer: Partitioning mobile data, Synchronizing data and transaction management, and Access issues such as being outside the firewall.


2.

What is the SAP Mobile Gateway?

Answer: SAP Mobile Gateway is an add-on to the DOE that allows you to develop client framework services for enabling seamless offline/ online access to back-end components on mobile devices.

3. Name the three license types for Sybase Unwired Platform.

Answer: Personal Developer (PD), Enterprise Developer (ED), and Enterprise Server (EE).

2011 Sybase, Inc.


A-1

Appendix A: Answers to Pre/Post Assessments Module 2: Sybase Unwired Platform Mobility Architectures


Pre-Assessments:

1. Sybase Mobile Sales is delivered with the core Sybase Unwired Platform product.

Answer: False. Sybase Mobile Sales CRM is a separate mobile application product.

2. Describe a native mobile application.

Answer: A Native mobile application must use the programming language understood by the specific device to which it is deployed.

3. True/False: The Sybase Unwired Server requires a third-party administration module.

Answer: False. Sybase Unwired Platform is packaged with the Sybase Control Center to administer and manage Unwired Servers.

Post-Assessments:

There are no Post-Assessments in this module.


A - 2


2011 Sybase, Inc.

Appendix A: Answers to Pre/Post Assessments Module 3: Sybase Unwired Platform Native Applications


Pre-Assessments:

1.

What is Eclipse?

Answer: Eclipse is an open source community, whose projects are focused on building an open development platform comprised of extensible frameworks, tools and runtimes for building, deploying and managing software across the lifecycle.

2. Before any kind of development can be performed, what must you launch in Eclipse?

Answer: You must launch plug-ins (perspectives). The user community is constantly developing plug-ins (perspectives) that enable vendor specific functionality to the core Eclipse IDE.

3. What must be created before you can begin development in an Eclipse-based environment?

Answer: Eclipse needs a WorkSpace AND a Project in order to begin development.


Post-Assessments:

1.

True/False: A WorkSpace is a physical file.

Answer: False. It is a folder.

2. What is the name of the SUP Eclipse Perspective?

Answer: Mobile Development

3. True/False: A WorkSpace can contain multiple projects.

Answer: True

4. In which view will most entity details be configured?

Answer: Properties view.

2011 Sybase, Inc.


A - 3

Appendix A: Answers to Pre/Post Assessments Module 4: Sybase Unwired Platform Mobile Workflow Applications


Pre-Assessments:

1. What are the four starting point screens available for a Mobile Workflow?

Answer: Start, Credential Request, E-mail Subscription, Activate.

2. What control is available to display HTML?

Answer: HtmlView.

3. How do you associate an attribute of an MBO to a screen control?

Answer: You would use keys.

4. Name at least two devices for which SUP generates workflows.

Answer: Windows Mobile and Apple iPhone.

Post-Assessments:

1. True/False: A Mobile Workflow application can allow you to control the screens generated and the sequence of those screens.

Answer: True


Answer: True, with a few exceptions.

2.

True/False: New controls can not be added to generated screens.

3. True/False: A Workflow application does not require the device to have the Messaging Client installed in order to work properly.

Answer: False.

A - 4


2011 Sybase, Inc.

Appendix A: Answers to Pre/Post Assessments Module 5: SAP Mobile Sales CRM Technical Overview


Pre-Assessments:

Post-Assessments:

There are no Pre-Assessment questions in this module.

There are no Post-Assessment questions in this module.


2011 Sybase, Inc.


A - 5

Appendix A: Answers to Pre/Post Assessments Module 6: Sybase Mobile Workflow for SAP Business Suite Technical Overview


Pre-Assessments:

1. On which device platform is the Sybase Mobile Workflow for SAP application supported?

Answer: Apple iPhone and Windows Mobile

2. True/False: There are a series of tasks and activities that need to be performed on the SAP side of the solution to implement the Sybase Mobile Workflow for SAP application.

Answer: True

3. True/False: There is absolutely no customization available for Sybase Mobile Workflow for SAP Business Suite.

Answer: False

Post-Assessments:

1. Which component in the architecture interacts between Sybase

Unwired Platform MBOs and the BAPI custom functions in the SAP


system?

Answer: JCo Connector.

2. What is the mechanism in Sybase Unwired Platform used to alert the device that there has been a change to the data?

Answer: Data Change Notification (DCN).

3. Name at least three Custom Repository Objects that must be created in the SAP system for customization.

Answer: Dictionary Objects, Class Library/Classes, Function Groups/Function Modules, Includes, SET/GET Parameters.

A - 6


2011 Sybase, Inc.

Appendix A: Answers to Pre/Post Assessments Module 7: Administering Sybase Unwired Platform Environments


Pre-Assessments:

1. What is the product component used to administer the SAP Mobile Workflow for SAP package?

Answer: Sybase Control Center.

2. True/False: The administration component of Sybase Unwired Platform can only administer packages for the server on which it is installed.

Answer: False.

3. True/False: A clustered Sybase Unwired Platform implementation is not available to customers who have purchased the SAP Mobile Workflow for SAP product.

Answer: False.

Post-Assessments:

1. What is the purpose of a Domain in the Sybase Unwired Platform environment?


2.

Answer: Domains are created to allow the deployment of packages

and workflows to reside in their own logical areas.

3. True/False: If you install the messaging database on its own physical machine, separate from the Unwired Server machine, Sybase Control Center will not be able to administer that database.

Answer: False. It is actually highly-recommended that the messaging database be installed on a separate server, especially in a load-balancing cluster scenario.

4. True/False: If you install multiple Unwired Servers in a load- balancing cluster, all Unwired Servers in the same cluster must share the messaging database.

Answer: True.

2011 Sybase, Inc.


A - 7

Appendix A: Answers to Pre/Post Assessments Module 8: Afaria Device Management Architecture and Overview


Pre-Assessments:

1. True/False: Afaria client devices cannot be locked down.

Answer: False. Afaria can be used to remotely to lock down client

devices.

2. Afaria components include functionality to manage devices. Which of these components does not perform device management functions:

a. Backup Manager

b. Software Manager

c. Inventory Manager

Answer: a. Backup Manager performs File Handling functions.

3. True/False: Afaria is a tool to manage and secure remote and mobile computing devices.

Answer: True

Post-Assessments:

1. True/False: Using Afaria, remote devices must be configured in the

office.

Answer: False. Using Afaria, IT personnel can setup and manage a


2.

mobile workers devices remotely.

True/False: Inventory Manager is used to deliver files and

applications to Afaria clients.

Answer: False. Software Manager is used to deliver files and applications to Afaria clients.

3. An Afaria administrator can use the

Manager

component to push documents to an Afaria client.

Answer: Document

A - 8


2011 Sybase, Inc.



*SUP101-90-0153-10-SG-S*

Printed In Canada


SUP101-90-0153-10

Mult mai mult decât documente.

SUP101 - Sybase Unwired Platforms Architectures and Technical Overview

Încărcat de

Informații document

Descriere:

Data încărcării

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Descriere:

Drepturi de autor:

Formate disponibile

SUP101 - Sybase Unwired Platforms Architectures and Technical Overview

Încărcat de

Descriere:

Drepturi de autor:

Formate disponibile

Titluri conexe

Interese conexe

Documente similare cu SUP101 - Sybase Unwired Platforms Architectures and Technical Overview

Mai multe de la አንበሳዉ ዳንኤል

Populare în Technology (General)

	The objectives for the module
	A list of topics for the module
	Supporting information that follows the flow of the class
	Pre- and Post-Assessment questions

	Familiarize yourself with the Sybase Unwired Platform (SUP)
	Understand the mobility terminology, concepts, and architectures
	Learn how the Co-Innovation Architecture work to integrate Sybase Unwired Platform (SUP) and SAP Business Suite products
	Familiarize yourself with the development models for native and workflow mobile applications
	Understand the underlying technology architectures used in the Sybase SAP Mobile Sales and Sybase SAP Mobile Workflow for SAP Business Suite products
	Understand the development of custom mobile business applications using:

	Device Application Designer
	Generated Code
	A Combination of the DAD and Generated Code

Audience
	This course is designed for:
		Mobility Architects
		Project Managers and Executives
		Consultants
		Mobile Application Developers
		Anyone who is currently evaluating a mobility solution for his/her organization
Prerequisites

Topics	In this course, you will cover these topics:
		Module 1: Introduction to Mobility and Sybase Unwired Platform
		Module 2: Sybase Unwired Platform Mobility Architectures
		Module 3: Sybase Unwired Platform Native Applications
		Module 4: Sybase Unwired Platform Mobile Workflow Applications
		Module 5: SAP Mobile Sales CRM Technical Overview
		Module 6: Sybase Mobile Workflow for SAP Business Suite Technical Overview
		Module 7: Administering Sybase Unwired Platform Environments
		Module 8: Afaria Device Management Architecture and Overview
Appendixes	This Student Guide includes 1 appendix.

Introduction to Mobility	1-4
Sybase Unwired Platform Licensing	1-12
Installation Requirements	1-21

Production Environment Considerations	2-32
Architecture Case Study Sybase Co-Innovation Architecture	2-47
	2-59
Module 3: Sybase Unwired Platform Native Applications
Introduction to the Unwired Workspace (Eclipse) Setting Up Connections Native Mobile Application Development	3-4
	3-19
	3-26
Module 4: Sybase Unwired Platform Mobile Workflow Applications
Workflow Introduction Workflow Screen Components Workflow Application Development Workflow Deployment	4-4
	4-11
	4-20
	4-29
Module 5: SAP Mobile Sales CRM Technical Overview
Overview of SAP CRM 7 Sybase Unwired Platform Integration - DOE Connector SAP Mobile Sales Application Architecture Configuring SAP CRM Components	5-4
	5-18
	5-27
	5-35

Customization Deploying Mobile Sales CRM to Devices		5-47
		5-86
Module 6: Sybase Mobile Workflow for SAP Business Suite Technical Overview
Sybase Mobile Workflow for SAP Business Suite Overview Sybase Mobile Workflow for SAP Customization		6-4
		6-13
Module 7: Administering Sybase Unwired Platform Environments
Architecture Introduction to the Sybase Control Center Workflow Administration Device Management Monitoring		7-4
		7-15
		7-32
		7-38
		7-47
Module 8: Afaria Device Management Architecture and Overview
Introduction Afaria Architectural Components		8-4
		8-8
Afaria	Managers	8-21
Device Lifecycle		8-34

		Introduction to Sybase Unwired Platform
MODULE _T_O_P_I_C_S TOPICSMODULE		Sybase Unwired Platform Landscapes
		Production Environment Considerations
		Architecture Case Study
		Sybase Co-Innovation Architecture

		Introduction to Sybase Mobility
MODULE _T_O_P_I_C_S TOPICSMODULE		Sybase Unwired Platform Landscapes
		Production Environment Considerations
		Architecture Case Study
		Sybase Co-Innovation Architecture

Type	Description		Used for
Single-node	A	non-redundant architecture consisting of an Unwired Server and	Personal development or trial installations
	data tier installed on a single host. This strategy is typically used by personal developers.
2-node	A	simple architecture without load balancing that may optionally	Enterprise development or test environments
	use a relay server. The data tier (which includes the CDB, the messaging database, and the monitoring database) is on one node and the application and server tier (which includes Unwired
	Server, Sybase Control Center, and optionally Afaria) is on another.
3-node cluster	A	simple redundant architecture with two server tier nodes (which	Entry-level production
	includes Unwired Server, Sybase Control Center, and optionally Afaria) and one data tier node. For an example of this cluster, see Systems Design > Fault-Tolerant Production Environments > Redundant Architecture Options.		environments
N+2-node	An optimally redundant architecture with any number of server tier nodes (which includes Unwired Server, Sybase Control Center, and optionally Afaria) supported by a relay server and two data tier nodes. For an example of this cluster, see Systems Design > Fault-Tolerant Production Environments > Redundant Architecture Options.
cluster			Full-scale or optimized production environments

		Overview of SAP CRM 7

MODULE _T_O_P_I_C_S TOPICSMODULE
		Sybase Unwired Platform Integration – DOE Connector

		SAP Mobile Sales Application Architecture

		Configuring SAP CRM Components

		Customization

		Deploying Mobile Sales CRM to Devices

		Architecture
MODULE _T_O_P_I_C_S TOPICSMODULE		Introduction to the Sybase Control Center
		Workflow Administration
		Device Management
		Monitoring

Core Unwired Server Server components Replication-Sync Server Messaging-Sync Server Database components Consolidated, Cluster, and Monitor Database	Optional Relay Server Relay Server Outbound Enabler Afaria 6.5 Afaria Server Afaria Management Console (IIS) Afaria Database
SQL Anywhere 11.0.1.2045
Messaging Server Database	SQL Anywhere
Advantage Database Server 9.1	Afaria Client Service OpenDS LDAP Server Installed in Developer Edition
Management components Server (Unified Agent Service) Repository Database
SQL Anywhere 11

	A complete list of what can be done with the SCC:
	Unwired Server Administration:

Pre-Assessments:	1. What are the four starting point screens available for a Mobile Workflow?
	Answer: Start, Credential Request, E-mail Subscription, Activate.
	2. What control is available to display HTML?
	Answer: HtmlView.
	3. How do you associate an attribute of an MBO to a screen control?
	Answer: You would use keys.
	4. Name at least two devices for which SUP generates workflows.
	Answer: Windows Mobile and Apple iPhone.
Post-Assessments:	1. True/False: A Mobile Workflow application can allow you to control the screens generated and the sequence of those screens.

Pre-Assessments:	1. On which device platform is the Sybase Mobile Workflow for SAP application supported?
	Answer: Apple iPhone and Windows Mobile
	2. True/False: There are a series of tasks and activities that need to be performed on the SAP side of the solution to implement the Sybase Mobile Workflow for SAP application.
	Answer: True
	3. True/False: There is absolutely no customization available for Sybase Mobile Workflow for SAP Business Suite.
	Answer: False
Post-Assessments:	1. Which component in the architecture interacts between Sybase

Pre-Assessments:	1. What is the product component used to administer the SAP Mobile Workflow for SAP package?
	Answer: Sybase Control Center.
	2. True/False: The administration component of Sybase Unwired Platform can only administer packages for the server on which it is installed.
	Answer: False.
	3. True/False: A clustered Sybase Unwired Platform implementation is not available to customers who have purchased the SAP Mobile Workflow for SAP product.
	Answer: False.
Post-Assessments:	1. What is the purpose of a Domain in the Sybase Unwired Platform environment?

Pre-Assessments:	1. True/False: Afaria client devices cannot be locked down.
	Answer: False. Afaria can be used to remotely to lock down client
	devices.
	2. Afaria components include functionality to manage devices. Which of these components does not perform device management functions:
	a. Backup Manager
	b. Software Manager
	c. Inventory Manager
	Answer: a. Backup Manager performs File Handling functions.
	3. True/False: Afaria is a tool to manage and secure remote and mobile computing devices.
	Answer: True
Post-Assessments:	1. True/False: Using Afaria, remote devices must be configured in the