SUP101 - Sybase Unwired Platforms Architectures and Technical Overview

Strictly internal - for the use of SAP employees only

Sybase Unwired Platform Architectures and Technical Overview

Student Guide (Lecture Only)

Version 1.0



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 XP Server, XTNDConnect, XTNDACCESS, 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

�2011 Sybase, Inc. Sybase Unwired Platform Architectures and Technical Overview – Version 1.0 i


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

Student Guide



ii Sybase Unwired Platform Architectures and Technical Overview – Version 1.0 �2011 Sybase, Inc.

Course 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

Objectives



�2011 Sybase, Inc. Sybase Unwired Platform Architectures and Technical Overview – Version 1.0 iii

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



iv Sybase Unwired Platform Architectures and Technical Overview – Version 1.0 �2011 Sybase, Inc.

Course Description

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

This Student Guide includes 1 appendix.

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

Topics

Appendixes



�2011 Sybase, Inc. Sybase Unwired Platform Architectures and Technical Overview – Version 1.0 v

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



vi Sybase Unwired Platform Architectures and Technical Overview – Version 1.0 �2011 Sybase, Inc.

� 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



�2011 Sybase, Inc. Sybase Unwired Platform Architectures and Technical Overview – Version 1.0 vii

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 [email protected].

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 [email protected]. The Professional Services Quality Manager will contact you and will take responsibility for resolving the matter.



viii Sybase Unwired Platform Architectures and Technical Overview – Version 1.0 �2011 Sybase, Inc.


�2011 Sybase, Inc. Sybase Unwired Platform Architectures and Technical Overview – Version 1.0 TOC - 1


Student Guide

Module 0: Course Introduction

Module 1: Introduction to Mobility and Sybase Unwired Platform

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

Module 2: Sybase Unwired Platform Mobility Architectures

Introduction to Sybase Unwired Platform ....................................................................................2-4 Sybase Unwired Platform Landscapes .........................................................................................2-15 Production Environment Considerations .....................................................................................2-32 Architecture Case Study ...............................................................................................................2-47 Sybase Co-Innovation Architecture .............................................................................................2-59

Module 3: Sybase Unwired Platform Native Applications

Introduction to the Unwired Workspace (Eclipse) .......................................................................3-4 Setting Up Connections ...............................................................................................................3-19 Native Mobile Application Development ....................................................................................3-26

Module 4: Sybase Unwired Platform Mobile Workflow Applications

Workflow Introduction ................................................................................................................4-4 Workflow Screen Components ....................................................................................................4-11 Workflow Application Development ...........................................................................................4-20 Workflow Deployment ................................................................................................................4-29

Module 5: SAP Mobile Sales CRM Technical Overview

Overview of SAP CRM 7 ............................................................................................................5-4 Sybase Unwired Platform Integration - DOE Connector .............................................................5-18 SAP Mobile Sales Application Architecture ................................................................................5-27 Configuring SAP CRM Components ...........................................................................................5-35


Student Guide

TOC - 2 Sybase Unwired Platform Architectures and Technical Overview – Version 1.0 �2011 Sybase, Inc.

Customization ..............................................................................................................................5-47 Deploying Mobile Sales CRM to Devices ...................................................................................5-86

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

Sybase Mobile Workflow for SAP Business Suite Overview .....................................................6-4 Sybase Mobile Workflow for SAP Customization ......................................................................6-13

Module 7: Administering Sybase Unwired Platform Environments

Architecture ..................................................................................................................................7-4 Introduction to the Sybase Control Center ...................................................................................7-15 Workflow Administration ............................................................................................................7-32 Device Management .....................................................................................................................7-38 Monitoring ...................................................................................................................................7-47

Module 8: Afaria Device Management Architecture and Overview

Introduction ..................................................................................................................................8-4 Afaria Architectural Components ................................................................................................8-8 Afaria Managers ...........................................................................................................................8-21 Device Lifecycle ..........................................................................................................................8-34


Sybase Unwired Platform Architectures and Technical OverviewModule 0: Course Introduction

Version 1.0

0 - 1©2011 Sybase, Inc.

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.


Module 0: Course Introduction



Version 1.0

0 - 2©2011 Sybase, Inc.

0 - 2

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



Version 1.0

0 - 3©2011 Sybase, Inc.

0 - 3

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



Version 1.0

0 - 4©2011 Sybase, Inc.

0 - 4

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



Version 1.0

0 - 5©2011 Sybase, Inc.

0 - 5

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

OverviewContinued …



Version 1.0

0 - 6©2011 Sybase, Inc.

0 - 6

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



Version 1.0

0 - 7©2011 Sybase, Inc.

0 - 7

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



Version 1.0

0 - 8©2011 Sybase, Inc.

0 - 8

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)


Sybase Unwired Platform Architectures and Technical OverviewModule 1: Introduction to Mobility and Sybase Unwired Platform

Version 1.0

1 - 1©2011 Sybase, Inc.







Version 1.0

1 - 2©2011 Sybase, Inc.

1 - 2

Module Pre-Assessment� There are no pre-assessment questions in this module



Version 1.0

1 - 3©2011 Sybase, Inc.

1 - 3

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

� This course is based on Sybase Unwired Platform 1.5.5 release.



Version 1.0

1 - 4©2011 Sybase, Inc.

1 - 4

MODU

LE T

OPIC

SMO

DULE

TOP

ICS Sybase Unwired Platform Licensing

Installation Requirements

Introduction to Mobility



Version 1.0

1 - 5©2011 Sybase, Inc.

1 - 5

Mobility Use Pyramid� Mobility enterprise used by task and business users to

executives and line of business managers:

Execs

Line of BusinessManagers

Task & Business Users

Scheduling& Dispatch

Time &Expense

CalendarsApproval Requests

Dashboards

CRM

Approvals

Email

Contacts

Field Service



Version 1.0

1 - 6©2011 Sybase, Inc.

1 - 6

Mobile Enterprise Challenges� Enterprises encounter a variety of challenges when

mobilizing applications� Partitioning mobile data� Synchronizing data and

transaction management� Access issues such as

being outside the firewall,bandwidth and connectivity

� Support for numerous typesof devices

� Securing data � Managing devices� Application change management

SybaseNext-Generation

MobilityArchitecture

Differentkinds of

devices/OSDiverse

networksData source

heterogeneity

Managingand securing

devices

Greater ease of

development

Provisioningand securingapplications

Dataavailability

on the device



Version 1.0

1 - 7©2011 Sybase, Inc.

1 - 7

Key to a Mobility Solution

Should enable rapid deployment of mobile

applications across multiple device types

Must offer seamless integration to a variety

of back-end data sources

Enterprise-grade development environment must leverage

existing skills and technologies

Enterprise Data

Changes

Device Technology

Changes

Consistent Development

Platform

� 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 mobileapplications.

� Should follow the Design Once Deploy Anywhere ( DODA ) paradigm. Can design the application one time and deploy it to multiple devices.



Version 1.0

1 - 8©2011 Sybase, Inc.

1 - 8

Enterprise Information System (EIS) Data� Data residing in enterprise backend systems such as:

� Enterprise databases� Web Services� REST Services� SAP ERP and CRM Systems



Version 1.0

1 - 9©2011 Sybase, Inc.

1 - 9

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

Continued …



Version 1.0

1 - 10©2011 Sybase, Inc.

1 - 10

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

Continued …



Version 1.0

1 - 11©2011 Sybase, Inc.

1 - 11

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



Version 1.0

1 - 12©2011 Sybase, Inc.

1 - 12

MODU

LE T

OPIC

SMO

DULE

TOP






Version 1.0

1 - 13©2011 Sybase, Inc.

1 - 13

License Categories and Mapping

� Personal Developer (PD)

� Enterprise Developer (ED)

� Enterprise Server (EE)

Development

Production

Testing/Qualification

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



Version 1.0

1 - 14©2011 Sybase, Inc.

1 - 14

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



Version 1.0

1 - 15©2011 Sybase, Inc.

1 - 15

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



Version 1.0

1 - 16©2011 Sybase, Inc.

1 - 16

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



Version 1.0

1 - 17©2011 Sybase, Inc.

1 - 17

SAP Mobile Solutions Licensing� License Requirements include:

� Sybase Unwired Platform� Pre-built applications

� Sybase Mobile Sales for SAP CRM� Sybase Mobile Workflow for SAP

Business SuiteUnwired ServerSAP

(SAP licensing) (License applies)

Mobile App(Mobile Sales or

Workflow)(License applies)

SUP Client(License applies)

Mobile Device



Version 1.0

1 - 18©2011 Sybase, Inc.

1 - 18

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 astand alone product

(SAP licensing)

Partner Solution

SUP ServerSAP

(License applies)

Custom PartnerApplication

(License applies)

SUP Client(License applies)

Mobile Device



Version 1.0

1 - 19©2011 Sybase, Inc.

1 - 19

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



Version 1.0

1 - 20©2011 Sybase, Inc.

1 - 20

Licensing Scenario� A production server license is needed for each node of a

redundant server setup� Relay Server is royalty free

Clustered CDB Servers

Load Balanced SUP ServersRelay Server

Data TierServer Tier

� Check with your Sales Representative for the license requirements for the Data Tier in this type of scenario.



Version 1.0

1 - 21©2011 Sybase, Inc.

1 - 21

MODU

LE T

OPIC

SMO

DULE

TOP






Version 1.0

1 - 22©2011 Sybase, Inc.

1 - 22

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

� 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



Version 1.0

1 - 23©2011 Sybase, Inc.

1 - 23

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

Continued …

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



Version 1.0

1 - 24©2011 Sybase, Inc.

1 - 24

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



Version 1.0

1 - 25©2011 Sybase, Inc.

1 - 25

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



Version 1.0

1 - 26©2011 Sybase, Inc.

1 - 26

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



Version 1.0

1 - 27©2011 Sybase, Inc.

1 - 27

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)

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



Version 1.0

1 - 28©2011 Sybase, Inc.

1 - 28

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

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



Version 1.0

1 - 29©2011 Sybase, Inc.

1 - 29

Recorded Demonstrations� Introduction to Sybase Unwired Platform

� See “SUP101_Mod1_Demonstration.mp4” on your Student CD



Version 1.0

1 - 30©2011 Sybase, Inc.

1 - 30

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



Version 1.0

1 - 31©2011 Sybase, Inc.

1 - 31

Module Post-Assessment1. 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.

� See Appendix A for Pre- and Post-Assessment answers



Version 1.0

1 - 32©2011 Sybase, Inc.


Sybase Unwired Platform Architectures and Technical OverviewModule 2: Sybase Unwired Platform Mobility Architectures

Version 1.0

2 - 1©2011 Sybase, Inc.







Version 1.0

2 - 2©2011 Sybase, Inc.

2 - 2

Module Pre-Assessment1. 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.

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



Version 1.0

2 - 3©2011 Sybase, Inc.

2 - 3


� 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, JCoConnector and Data Orchestration Engine (DOE) components

� Understand Data Change Notification (DCN)



Version 1.0

2 - 4©2011 Sybase, Inc.

2 - 4

MODU

LE T

OPIC

SMO

DULE

TOP

ICS

Sybase Co-Innovation Architecture

Introduction to Sybase Unwired Platform

Sybase Unwired Platform Landscapes

Production Environment Considerations

Architecture Case Study



Version 1.0

2 - 5©2011 Sybase, Inc.

2 - 5

High-Level Design Overview

� 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 back-end 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.



Version 1.0

2 - 6©2011 Sybase, Inc.

2 - 6

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.



Version 1.0

2 - 7©2011 Sybase, Inc.

2 - 7

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

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



Version 1.0

2 - 8©2011 Sybase, Inc.

2 - 8

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”



Version 1.0

2 - 9©2011 Sybase, Inc.

2 - 9

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



Version 1.0

2 - 10©2011 Sybase, Inc.

2 - 10

Native Application Development Model

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



Version 1.0

2 - 11©2011 Sybase, Inc.

2 - 11

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



Version 1.0

2 - 12©2011 Sybase, Inc.

2 - 12

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

� OpenDS is a Java Open Source Next Generation Directory Server. � Based on LDAP v3.� http://www.opends.org



Version 1.0

2 - 13©2011 Sybase, Inc.

2 - 13

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

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



Version 1.0

2 - 14©2011 Sybase, Inc.

2 - 14

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



Version 1.0

2 - 15©2011 Sybase, Inc.

2 - 15

MODU

LE T

OPIC

SMO

DULE

TOP

ICS


Introduction to Sybase Mobility






Version 1.0

2 - 16©2011 Sybase, Inc.

2 - 16

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)



Version 1.0

2 - 17©2011 Sybase, Inc.

2 - 17

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



Version 1.0

2 - 18©2011 Sybase, Inc.

2 - 18

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 3rd Edition and 5th Edition)

� 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



Version 1.0

2 - 19©2011 Sybase, Inc.

2 - 19

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

� SOAP: Simple Object Access Protocol



Version 1.0

2 - 20©2011 Sybase, Inc.

2 - 20

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

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



Version 1.0

2 - 21©2011 Sybase, Inc.

2 - 21

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



Version 1.0

2 - 22©2011 Sybase, Inc.

2 - 22

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

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



Version 1.0

2 - 23©2011 Sybase, Inc.

2 - 23

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

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



Version 1.0

2 - 24©2011 Sybase, Inc.

2 - 24

Operating Environment Architecture

Data Services

Customer SOA

Infrastructure

Mobile Middleware Services Mobile Application

Enterprise Information

Systems

DatabaseJDBC

Accessible

CDB

Operation Replay

State Replication

Data Synchronization Services

Device and ApplicationManagement

Device Security

Device and Application

Management

Device Data

Relay ServerUnwired Server

Sybase Unwired Server Platform

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



Version 1.0

2 - 25©2011 Sybase, Inc.

2 - 25

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 WorkSpace Mobile Business Object Development Tool

(Eclipse)

BlackBerryJava

WindowsJava SE & C#

Windows MobileC#

iPhoneObjective C

Unwired WorkSpace Device Application Development Tool (Eclipse)

Windows Mobile BlackBerry

Native Device Application Development ToolsBlackBerry – JDE, Eclipse JDE Plugin

Windows – Eclipse, Visual Studio

Windows Mobile - Visual Studio

iPhone - Xcode

Workflow Application Development Tool (Eclipse)iPhone Windows Mobile

Unwired Server

Sybase Unwired Platform Development Tools

Continued …



Version 1.0

2 - 26©2011 Sybase, Inc.

2 - 26

Platform-wide Services� Administration (Sybase Control Center):

Continued …Node 1

Node n

Web Container RMI Service

SCC Plugin for SUP

Sybase Control Center

SUP Flex Web Application MBeanInterface

SNMP ServiceSUP SNMP

Plugin

Browser

SNMP Client

Custom Admin Java Client

Flash Plug-in Unwired Server

IIOPS

HTTPS

SNMP

RMI

IIOP



Version 1.0

2 - 27©2011 Sybase, Inc.

2 - 27

Platform-wide Services� 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

IAS Relay Server or Reverse Proxy

ISA/Apache

Firewall Firewall

Administrative

Console BrowserTCP/IP HTTP SSL

DMZ

Afaria Server

IIS Server



Version 1.0

2 - 28©2011 Sybase, Inc.

2 - 28

Deployment Architecture

2.5G NetworksGSM/GPRS

3G Networks

Wi-Fi

Sybase RelayServer

DMZ

ExternalFirewall

InternalFirewall


JCOConnector for SAP

Reliable PushMessaging

MBO Services

Sybase UnwiredServer

JDBC

Connection to Backend Systems

Deploy MBOs

Personal Developer Tooling

Deploy MBOs

Deploy MBOs

Unwi

red S

erve

r Con

necti

on

DOEConnector for SAP

HTTP(S) / SOAP or REST Web

Services



Version 1.0

2 - 29©2011 Sybase, Inc.

2 - 29

Sample Production Architecture

Firewall

Relay ServerOptional for HA

Relay ServerIIS or Apache

Relay ServerFarm

DMZ InternalInternet

Firewall

SUP Production II

SUP Domains



JDBC/JCOs/WS.

JDBC/JCOs/WS

EIS

HTTP(S) Data Change Notification


Inbound TrafficConnects through

Relay Server

OutboundHTTP(S)

Field devices connect to domains which contain MBO packages

HTTP or HTTPS

Devices

Devices communicate to the Relay Server via HTTP or HTTPS

SUP Servers connect outbound

to the Relay Server to the

Relay Server farm

SUP Production I

MBOs deployed to the Production Server

HA available for Unwired Servers

Prov

ision

Decommission

Production

Afaria (optional)

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



Version 1.0

2 - 30©2011 Sybase, Inc.

2 - 30

Redundant Server Production Architecture� A production server license is needed for each node of a

redundant server setup

Clustered CDB Servers

Load Balanced SUP ServersRelay Server

� Relay Server is royalty free



Version 1.0

2 - 31©2011 Sybase, Inc.

2 - 31

Mobility Management Tools

Architecture Integration with SAPM

obile

App

licat

ions

Mob

ility

IT In

fras

truc

ture

Back

end

Syst

ems BAPI Wrappers

SCMCRM SRM HCM PLM EAM

SAP SystemsLegacy Systems

J2EE

.NET

SAP ECC

Sybase Unwired Platform Client

— API— Data persistency— Device management— Data sync engine

Sybase Unwired PlatformData Staging and Caching Services Tools

SAP Mobile GatewaySAP NetWeaver

Mobile DOE

JCO Connector/DOE connector / Web Services

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



Version 1.0

2 - 32©2011 Sybase, Inc.

2 - 32

MODU

LE T

OPIC

SMO

DULE

TOP

ICS








Version 1.0

2 - 33©2011 Sybase, Inc.

2 - 33

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



Version 1.0

2 - 34©2011 Sybase, Inc.

2 - 34

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

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



Version 1.0

2 - 35©2011 Sybase, Inc.

2 - 35

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



Version 1.0

2 - 36©2011 Sybase, Inc.

2 - 36

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

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.



Version 1.0

2 - 37©2011 Sybase, Inc.

2 - 37

Key Tiers in Clusters� Primary server

� Contains the master copy of the configuration repository for allservers 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



Version 1.0

2 - 38©2011 Sybase, Inc.

2 - 38

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

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



Version 1.0

2 - 39©2011 Sybase, Inc.

2 - 39

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



Version 1.0

2 - 40©2011 Sybase, Inc.

2 - 40

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

� Windows 2003 is supported on non-cluster installations only.



Version 1.0

2 - 41©2011 Sybase, Inc.

2 - 41

Architectural Strategies Recap

Full-scale or optimized production environments

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.

N+2-node cluster

Entry-level production environments

A simple redundant architecture with two server tier nodes (which 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.

3-node cluster

Enterprise development or test environments

A simple architecture without load balancing that may optionallyuse 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 UnwiredServer, Sybase Control Center, and optionally Afaria) is on another.

2-node

Personal development or trial installations

A non-redundant architecture consisting of an Unwired Server and data tier installed on a single host. This strategy is typically used by personal developers.

Single-nodeUsed forDescriptionType



Version 1.0

2 - 42©2011 Sybase, Inc.

2 - 42

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

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



Version 1.0

2 - 43©2011 Sybase, Inc.

2 - 43

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)



Version 1.0

2 - 44©2011 Sybase, Inc.

2 - 44

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

Continued …



Version 1.0

2 - 45©2011 Sybase, Inc.

2 - 45

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

Continued …



Version 1.0

2 - 46©2011 Sybase, Inc.

2 - 46

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



Version 1.0

2 - 47©2011 Sybase, Inc.

2 - 47

MODU

LE T

OPIC

SMO

DULE

TOP

ICS








Version 1.0

2 - 48©2011 Sybase, Inc.

2 - 48

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

� Business Requirements� Infrastructure:

� 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

Continued …



Version 1.0

2 - 49©2011 Sybase, Inc.

2 - 49

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



Version 1.0

2 - 50©2011 Sybase, Inc.

2 - 50

Current Timesheet Workflow Process� On desktop or laptop, employee submits and manager

reviews, approves or rejects timesheet requests:

Continued …

Timesheet entries

Timesheet entry rejectedTimesheet entry approved

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

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

Employee

ManagerSAP HR Module


�


Version 1.0

2 - 51©2011 Sybase, Inc.

2 - 51

Proposed Mobile Workflow Process

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

� Data sent to SAP� Email generated

and sent to manager in the field

Data submitted is saved to the database in SAP

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

�



Version 1.0

2 - 52©2011 Sybase, Inc.

2 - 52

Proposed High-level Mobile Workflow� Sybase Unwired Platform enables mobile workflow:

Devices

Employee enters time • Sybase Unwired Platform

• Custom SAP Business Objects


SAP HR Module

Manager views/approves and/or rejects time

• Custom BAPIs and Workflows for Time Management

Request sent to SAP via MBO

2

Manager approval status sent to SAP

43

1



Version 1.0

2 - 53©2011 Sybase, Inc.

2 - 53

Mobile Workflow Implementation ChartCreate Notification of time entered

EMPLOYEE

Decision whether to approveMANAGER

Decision on further course of actionEMPLOYEE

Revise time enteredEMPLOYEE

Delete time entered dataSYSTEM

Update HR CATS DBSYSTEM

APPROVED �

REJECTED �

HR CATS DB



Version 1.0

2 - 54©2011 Sybase, Inc.

2 - 54

Integration with SAP HCM

MobileApplication

Business objectCATimeSheetManager: Time Sheet

(CATSDB)

Business objectCATimeSheetRecord.GetList:

Business objectEmployeeCATimeSheet.GetWorklist

Insert data records

Change data records

Retrieve worklist

Retrieve time sheet data

Sybase Unwired Platform Server



Version 1.0

2 - 55©2011 Sybase, Inc.

2 - 55

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

Sybase Unwired Server

Calls Returns

Data Transfer

Data Access

Mobile Application

GetTimeSheetManager.InsertGetTimeSheetManager.ChangeGetTimeSheetManager.Delete

CATS DB

EmployeeCATimeSheet.GetWorkListCATimeSheetRecord.GetList



Version 1.0

2 - 56©2011 Sybase, Inc.

2 - 56

Network Topology ArchitectureExternal Firewall

BES (MDS) Server

Relay ServerIIS or Apache

RIM Proprietary

DMZ Internal NetworkExternal Network

Internal Firewall

SUP Production II

SUP Domains


Common CDB

JDBC/JCOs/WS

JDBC/JCOs/WS



Inbound TrafficConnects through

Relay Server

HTTP

S -4

43

Devices

BlackBerry Carrier

SUP Servers connect outbound

to the Relay Server

SUP Production I

MBOs deployed to the Production Server

HA available for Unwired Servers

HTTP/SSL

Apple APNS Provider

HTTPS – 2195gateway.push.apple.com

HTTPS – 2196feedback.push.apple.com

HTTP 3200

SAP

LDAPServer

Authentication via User/Passsword

CDB

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



Version 1.0

2 - 57©2011 Sybase, Inc.

2 - 57

User Experience – Before� Employee uses web-based Portal to submit a request� Manager uses web-based Portal to review and approve or

reject request

Employee Self Service SAP Portal

Access

Manager Self Service SAP Portal

Access

Web Server

SAP Backend

Employee submits request

Manager approves 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.



Version 1.0

2 - 58©2011 Sybase, Inc.

2 - 58

User Experience – After� Employee uses mobile device to submit a request� Manager uses mobile device to review and approve or reject

request

Mobilized ESS Timesheet via Sybase

Unwired Platform

Mobilized MSS Timesheet via Sybase

Unwired Platform


Backend Systems



Version 1.0

2 - 59©2011 Sybase, Inc.

2 - 59

MODU

LE T

OPIC

SMO

DULE

TOP

ICS




Sybase Unwired Platform Environment Considerations




Version 1.0

2 - 60©2011 Sybase, Inc.

2 - 60

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



Version 1.0

2 - 61©2011 Sybase, Inc.

2 - 61

Skill Set Required for CIA Mobility



Version 1.0

2 - 62©2011 Sybase, Inc.

2 - 62

Sybase Unwired Platform Role� 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


Mobile Adaptation (Gateway)

SAP Business Suite

SRM ERPCRM

NetWeaver Mobile

MobileContent

SCM PLM

MobileContent

BAPI Wrappers



Version 1.0

2 - 63©2011 Sybase, Inc.

2 - 63

Co-Innovation Architecture Role � 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



SAP Business Suite

SRM ERPCRM

NetWeaver Mobile

MobileContent

SCM PLM

MobileContent

BAPI Wrappers



Version 1.0

2 - 64©2011 Sybase, Inc.

2 - 64

Combined Architecture of CIA

� Joint role:� End-to-end lifecycle

management:� Deployment� Version control � Trouble shooting

� End-to-end integration� Integrated

application development

� Customization programming model



SAP Business Suite

SRM ERPCRM

NetWeaver Mobile

MobileContent

SCM PLM

MobileContent

BAPI Wrappers



Version 1.0

2 - 65©2011 Sybase, Inc.

2 - 65

Sybase SAP Mobile Sales and Workflow� CIA architectural overview for mobile sales and workflow:

CRM 2007

NetWeaver Mobile 7.1

SAP Mobile Gateway

PUSH PUSH


DOE Connector

Sybase Device Stack

SAP

Messaging

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

KEY KEY

JCO Connector

or



Version 1.0

2 - 66©2011 Sybase, Inc.

2 - 66

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


DOE Connector

Messaging

JCO Connector

or



Version 1.0

2 - 67©2011 Sybase, Inc.

2 - 67

SAP Connectivity Methods

SAP


Mobile Gateway

PUSH PUSH

?


DOE Connector

Sybase Device Support

SAP

Messaging

BAPI (JCo)Connector

Synchronisation

SYNC

Web ServiceConnector

SQL DB JCDBC

Web Services

SYNC

SYNC

SYNC



Version 1.0

2 - 68©2011 Sybase, Inc.

2 - 68

Complete CIA Architecture

CRM 2007

Sybase Unwired Platform Infrastructure

PUSH

ESDMA Converter

Sybase DOE

Connector

BAPI Wrapper & Data Object Editor

ESDMA Editor

Sybase Mobile AppDevelopment Tools

Sybase Admin Console

SAP Infrastructure

ERP ECC 6

SRM, SCM

, PLM,..

SAP Business Suite

BASIS 7.0 BASIS 7.1

PUSH

Push Messaging


PUSH

NetWeaver Mobile with

DOE Sybase Device Stack

Sybase Device Stack

http

RSS

Mobile

Gatew

ay

Channel Handlers



Version 1.0

2 - 69©2011 Sybase, Inc.

2 - 69

Deployment Architecture� Co-Innovation deployment:

RFC

CRM 2007 SP06+

OR CRM 7.0 SP05+

2.5G NetworksGSM/GPRS

3G Networks

Wi-Fi

HTTP(S) / SOAP Web

Services

SAP NetWeaver Mobile 7.1 SP09+

with Gateway 1.1 SP01

SAP CRM SAP NetWeaver

Sybase RelayServer

DMZ

ExternalFirewall

InternalFirewall


Device Management Application Provisioning

DOEConnector

Reliable Push Messaging

MBO Services

Sybase Unwired

Server



Version 1.0

2 - 70©2011 Sybase, Inc.

2 - 70

Recorded Demonstrations� There are no recorded demonstrations in this module



Version 1.0

2 - 71©2011 Sybase, Inc.

2 - 71


� 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



Version 1.0

2 - 72©2011 Sybase, Inc.

2 - 72

Module Post-Assessment� There are no post-assessment questions in this module


Sybase Unwired Platform Architectures and Technical OverviewModule 3: Sybase Unwired Platform Native Applications

Version 1.0

3 - 1©2011 Sybase, Inc.







Version 1.0

3 - 2©2011 Sybase, Inc.

3 - 2

Module Pre-Assessment1. 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?




Version 1.0

3 - 3©2011 Sybase, Inc.

3 - 3


� 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



Version 1.0

3 - 4©2011 Sybase, Inc.

3 - 4

MODU

LE T

OPIC

SMO

DULE

TOP

ICS Setting Up Connections

Introduction to the Unwired Workspace (Eclipse)

Native Mobile Application Development



Version 1.0

3 - 5©2011 Sybase, Inc.

3 - 5

Unwired Workspace User InterfaceWorkSpace Navigator

contains all project files

Enterprise Explorer contains

all connection profiles

Diagram Window contain all project

diagrams

Properties View displays the

object in focus properties

Problems Tab displays any warnings or

errors generated

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



Version 1.0

3 - 6©2011 Sybase, Inc.

3 - 6

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

� Creation wizards are associated with the resources in a view.



Version 1.0

3 - 7©2011 Sybase, Inc.

3 - 7

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

� These views are explained on the following pages.



Version 1.0

3 - 8©2011 Sybase, Inc.

3 - 8

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

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.



Version 1.0

3 - 9©2011 Sybase, Inc.

3 - 9

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 Right-click to

enable context menu



Version 1.0

3 - 10©2011 Sybase, Inc.

3 - 10

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



Version 1.0

3 - 11©2011 Sybase, Inc.

3 - 11

Enterprise Explorer View� Enterprise Explorer View

provides functionality to connect to enterprise back-end systems such as:

� Database Servers� REST Services� SAP Servers� Unwired Servers� Web Services



Version 1.0

3 - 12©2011 Sybase, Inc.

3 - 12

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



Version 1.0

3 - 13©2011 Sybase, Inc.

3 - 13

Diagram Context Menus� The following shows the context menu of the Mobile

Application Diagram:



Version 1.0

3 - 14©2011 Sybase, Inc.

3 - 14

Palette� 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 MBOsand Relationships



Version 1.0

3 - 15©2011 Sybase, Inc.

3 - 15

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



Version 1.0

3 - 16©2011 Sybase, Inc.

3 - 16

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



Version 1.0

3 - 17©2011 Sybase, Inc.

3 - 17

Outline View� Outline View shows a thumbnail sketch of either a Mobile

Application Diagram (MAD) or a BOB:

Click these icons to configure the Outline view for graphical or

list orientation



Version 1.0

3 - 18©2011 Sybase, Inc.

3 - 18

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



Version 1.0

3 - 19©2011 Sybase, Inc.

3 - 19

MODU

LE T

OPIC

SMO

DULE

TOP






Version 1.0

3 - 20©2011 Sybase, Inc.

3 - 20

Setting Up Connections� Connectivity is performed

via the Enterprise Explorer � Before development:

� Set up EIS database connectivity

� Set up connectivity to your Unwired Server

� Set up connectionsto services

� Set up connection to SAP



Version 1.0

3 - 21©2011 Sybase, Inc.

3 - 21

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



Version 1.0

3 - 22©2011 Sybase, Inc.

3 - 22

Completed Database Connection Profile� Right-click

and select Connect to connect and view the contents of that database



Version 1.0

3 - 23©2011 Sybase, Inc.

3 - 23

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



Version 1.0

3 - 24©2011 Sybase, Inc.

3 - 24

Unwired Server Connection Profile

Default password is: s3pAdminPort 2000 is the default

port during the installation

� The user name and password are case-sensitive.



Version 1.0

3 - 25©2011 Sybase, Inc.

3 - 25

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

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



Version 1.0

3 - 26©2011 Sybase, Inc.

3 - 26

MODU

LE T

OPIC

SMO

DULE

TOP






Version 1.0

3 - 27©2011 Sybase, Inc.

3 - 27

Development Process / Device Platform Options

DevelopMobile

BusinessObjects

Deploy MobileBusinessObjects

to UnwiredServer

GenerateDeviceObjectCode

DevelopDevice

Application

Generate and Customize

DeviceApplicationNative Code

Test onEmulator

and/orDevice

Sybase Unwired Platform Development Task Flow

Sybase Unwired Platform Development Tools

Unwired WorkSpace Mobile Business Object Development Tool

(Eclipse)

BlackBerryJava

WindowsJava SE & C#

Windows MobileC#

iPhoneObjective C

Unwired WorkSpace Device Application Development Tool (Eclipse)

Windows Mobile BlackBerry

Native Device Application Development ToolsBlackBerry – JDE, Eclipse JDE Plugin

Windows – Eclipse, Visual Studio

Windows Mobile - Visual Studio

iPhone - Xcode

Workflow Application Development Tool (Eclipse)iPhone Windows Mobile Symbian

� MBO development followed by Device Application Development and optionally Native IDE for custom development.



Version 1.0

3 - 28©2011 Sybase, Inc.

3 - 28

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



Version 1.0

3 - 29©2011 Sybase, Inc.

3 - 29

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

� 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



Version 1.0

3 - 30©2011 Sybase, Inc.

3 - 30

Importing Existing Projects� Use the Import feature to import project files, entire folder and

subfolders and/or archive files containing projects:



Version 1.0

3 - 31©2011 Sybase, Inc.

3 - 31

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



Version 1.0

3 - 32©2011 Sybase, Inc.

3 - 32

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 ofattributes, parameters,operations and relationships

EnterpriseSystem

Subset MobilizePersonalize

DeviceRepresentation

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



Version 1.0

3 - 33©2011 Sybase, Inc.

3 - 33

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



Version 1.0

3 - 34©2011 Sybase, Inc.

3 - 34

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



Version 1.0

3 - 35©2011 Sybase, Inc.

3 - 35

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



Version 1.0

3 - 36©2011 Sybase, Inc.

3 - 36

Parameter Sample� Stored procedure below contains two parameters which

would require runtime input:� customer_id� product_id

� Can map these parameters to Personalization Keys



Version 1.0

3 - 37©2011 Sybase, Inc.

3 - 37

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

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



Version 1.0

3 - 38©2011 Sybase, Inc.

3 - 38

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

This symbol shows a one-to-many relationship



Version 1.0

3 - 39©2011 Sybase, Inc.

3 - 39

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

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



Version 1.0

3 - 40©2011 Sybase, Inc.

3 - 40

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



Version 1.0

3 - 41©2011 Sybase, Inc.

3 - 41

Initial Synchronization Process1. User initiates synchronization and includes a parameter2. If Personalization Keys are used, they are passed to the EIS3. The EIS refreshes the Unwired Server4. A partition in the CDB is created for that user’s data5. The device is synchronized with the partition

EISUnwired Server

CDB

Mobile Device

12

3

4

5

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



Version 1.0

3 - 42©2011 Sybase, Inc.

3 - 42

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

Mobile Device

Unwired Server

CDB

Local Database

� Simply stated: Synchronization parameters control the amount of data to be sent to the mobile device.



Version 1.0

3 - 43©2011 Sybase, Inc.

3 - 43

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



Version 1.0

3 - 44©2011 Sybase, Inc.

3 - 44

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

� :state_code is considered the load parameter.� state is considered the Propagate To attribute.



Version 1.0

3 - 45©2011 Sybase, Inc.

3 - 45

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

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



Version 1.0

3 - 46©2011 Sybase, Inc.

3 - 46

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

property valuesstate_code automatically

becomes a Load Parameter



Version 1.0

3 - 47©2011 Sybase, Inc.

3 - 47

Associating Synch and Load Parameters� Load Parameters can get its value from:

� Personalization Keys or default values� Synchronization Parameters

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



Version 1.0

3 - 48©2011 Sybase, Inc.

3 - 48

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



Version 1.0

3 - 49©2011 Sybase, Inc.

3 - 49

Deployment� MBOs are deployed into

a package in the Unwired Server

� The package is named after the Mobile Application Project



Version 1.0

3 - 50©2011 Sybase, Inc.

3 - 50

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 betterconsumed 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:

� This wizard screen is enabled only when the developer uses the Advanced Developer profile option.



Version 1.0

3 - 51©2011 Sybase, Inc.

3 - 51

Deploy to a Server/Domain� Select the server and domain to which to deploy:



Version 1.0

3 - 52©2011 Sybase, Inc.

3 - 52

Deployment Profiles� Can create a

deployment profile / package on the last screen of the Deployment Wizard



Version 1.0

3 - 53©2011 Sybase, Inc.

3 - 53




Version 1.0

3 - 54©2011 Sybase, Inc.

3 - 54


� 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



Version 1.0

3 - 55©2011 Sybase, Inc.

3 - 55

Module Post-Assessment1. 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?




Version 1.0

3 - 56©2011 Sybase, Inc.


Sybase Unwired Platform Architectures and Technical OverviewModule 4: Sybase Unwired Platform Mobile Workflow Applications

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

4 - 5©2011 Sybase, Inc.

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



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

4 - 13©2011 Sybase, Inc.

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



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

4 - 19©2011 Sybase, Inc.

� 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).



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

4 - 27©2011 Sybase, Inc.

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



Version 1.0

4 - 28©2011 Sybase, Inc.

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



Version 1.0

4 - 29©2011 Sybase, Inc.



Version 1.0

4 - 30©2011 Sybase, Inc.



Version 1.0

4 - 31©2011 Sybase, Inc.

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



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 OverviewModule 5: SAP Mobile Sales CRM Technical Overview

Version 1.0

5 - 1©2011 Sybase, Inc.







Version 1.0

5 - 2©2011 Sybase, Inc.

5 - 2

Module Pre-Assessment� There are no pre-assessment questions in this module



Version 1.0

5 - 3©2011 Sybase, Inc.

5 - 3


� 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



Version 1.0

5 - 4©2011 Sybase, Inc.

5 - 4

MODU

LE T

OPIC

SMO

DULE

TOP

ICS

Deploying Mobile Sales CRM to Devices

Overview of SAP CRM 7

Sybase Unwired Platform Integration – DOE Connector

SAP Mobile Sales Application Architecture

Customization

Configuring SAP CRM Components



Version 1.0

5 - 5©2011 Sybase, Inc.

5 - 5

Mobile Sales Activities� Typical Mobile Sales requirements:

SAP Mobile CRM

View today’s activities

Call customer to reschedule meetings

Prepare for revenue status meeting

Read e-mails and notifications

View map and visit customer

Make personal calls

View opportunities



Version 1.0

5 - 6©2011 Sybase, Inc.

5 - 6

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



Version 1.0

5 - 7©2011 Sybase, Inc.

5 - 7

Benefits� Value to the business

� 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

Continued …



Version 1.0

5 - 8©2011 Sybase, Inc.

5 - 8

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



Version 1.0

5 - 9©2011 Sybase, Inc.

5 - 9

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



Version 1.0

5 - 10©2011 Sybase, Inc.

5 - 10

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

Sybase

Sybase Unwired Platform*

CRM 2007

orCRM 7


Mobile Gateway 1.1

PUSH

SAP

Sybase Mobile Sales Application

* See slide 19 for a more detailed view of components

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



Version 1.0

5 - 11©2011 Sybase, Inc.

5 - 11

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

Continued …



Version 1.0

5 - 12©2011 Sybase, Inc.

5 - 12

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



Version 1.0

5 - 13©2011 Sybase, Inc.

5 - 13

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



Version 1.0

5 - 14©2011 Sybase, Inc.

5 - 14

SAP NetWeaver Mobile Architecture

SAP NetWeaver AS

Device Queue

Device Inventory

Mobile Device

App 1 App 2Mobile Client

JVM DB

Mobile Device


JVM DB

Mobile Device


JVM DB

Backend A Backend CBackend B

SAP Mobile AdministratorData Orchestration Engine

Device Queue Device Queue

Consolidated Data Store

Mobile Applications

RFC RFC HTTPS

HTTPS FileHTTPS FileHTTPS File

Mobile Gateway



Version 1.0

5 - 15©2011 Sybase, Inc.

5 - 15

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



Version 1.0

5 - 16©2011 Sybase, Inc.

5 - 16

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



Version 1.0

5 - 17©2011 Sybase, Inc.

5 - 17

Architecture of Mobile Gateway



Version 1.0

5 - 18©2011 Sybase, Inc.

5 - 18

MODU

LE T

OPIC

SMO

DULE

TOP

ICS





Customization




Version 1.0

5 - 19©2011 Sybase, Inc.

5 - 19

Architectural Patterns

Run Time

Sybase Mobile Device Stack

Mobile ApplicationUser Interface

Messaging Client

Listener

SyncServerLibrary

PersistentData Store

SQL Access

MBO Code

Com

pone

nt L

ibra

ries

Cus

tom

Bus

ines

s

Push Listener

SAP Enterprise Infrastructure

NetWeaverMobile (DOE) 7.1

Monitoring & Support

Data Distribution

Data Consolidation

NetWeaver

App ComponentsERPCRM SCM

App ComponentsERP

SAP R/3 4.6x, 4.7x

CRM

BA

PI/R

FC

BAPI

Wra

pper

Inte

rface

Ente

rpris

eS

OA

Dat

a Ve

rsio

ning

M

obile

Gat

eway

Backend Handlers

ECC 5.0/6.0

BA

PI/

RFC

SAP Dev & Admin ToolNetWeaver Work Bench(model driven develop)Mobile AdministrationESDMA Editor

Sybase Mobile Dev.SAP Connection Wizards

MBO Modeling Editor

Mobile App Screen Dev

Sybase Admin MBO ConfigurationPull/Push ManagementRoles & SecurityApp Provisioning

3rd Party Dev ToolsMobile App Development

EclipseVisual StudioXcode

Sybase Mobile Middleware

StateEngine

Sybase Web Services

Stack

Apache Axis Libraries

Sybase JCo Wrapper

SAP JCo Connector

Reliable Data

Synchronization

DOE-C Connector

ESDMA Converter

MSG Queue

Messaging MBO

Scheduling Services

Replication MBO

• Data Consolidation• Differential Calc

• Simulated Push• Personalization

Cache

PushEvent Queue

MobilinkEngine

Reliable Push Msg

Server(iMO)

Data Change Notification (DCN)

PUSH

PUSH

WSDL

PULL(https)

PUSH

PULL

(native)

PULL(native)

Sybase Unwired Platform Sybase Unwired Platform



Version 1.0

5 - 20©2011 Sybase, Inc.

5 - 20

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

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



Version 1.0

5 - 21©2011 Sybase, Inc.

5 - 21

DOE Connector Interactions



Version 1.0

5 - 22©2011 Sybase, Inc.

5 - 22

DOE Connector Logical Architecture

HTTP(s) ListenerWeb Services Eventing

Route Incoming notifications

based on URL

DOE Connector

DOE Reliable Messaging

Collaboration Module

ESDMA DOE-C Metadata

DOE-C Repository

DOE to JSONMessaging Format

JSON to DOE Messaging Format

DOE-Connector to iMO

Compute JMS queue based on iMO partition information and device ID

MDB for iMBO inbound messages

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

Client to Server message sequence update and JMS message de-queue transaction for reliable asynchronous requests

AckFromClient to DOE

DOE NotificationsDOE Requests/Responses

Client to Server synchronous web services invocation

DOE Connector Logical Architecture

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

Direct Invocation from Client



Version 1.0

5 - 23©2011 Sybase, Inc.

5 - 23

Messaging Architecture from Server to Client



Version 1.0

5 - 24©2011 Sybase, Inc.

5 - 24

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



Version 1.0

5 - 25©2011 Sybase, Inc.

5 - 25

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



Version 1.0

5 - 26©2011 Sybase, Inc.

5 - 26

Sybase Unwired Platform Integration Flow



Version 1.0

5 - 27©2011 Sybase, Inc.

5 - 27

MODU

LE T

OPIC

SMO

DULE

TOP

ICS





Customization




Version 1.0

5 - 28©2011 Sybase, Inc.

5 - 28

CRM Mobile Sales Co-Innovation ArchitectureSybase Mobile

Sales Application

SAP Business Suite

SAP NetWeaver Mobile 7.1 SP09+


Gateway 1.1 SP00+Consolidated Data Store

Co-In

nova

tion

Pla

tfor

m

SRM SCM ERPPLMCRM 2007 SP06+ OR

CRM 7.0 SP05+



Version 1.0

5 - 29©2011 Sybase, Inc.

5 - 29

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

� 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

Application





Version 1.0

5 - 30©2011 Sybase, Inc.

5 - 30

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

Application





Version 1.0

5 - 31©2011 Sybase, Inc.

5 - 31

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

Application





Version 1.0

5 - 32©2011 Sybase, Inc.

5 - 32

Application Architecture

Application Business Objects (ABO) - Hand Written

Consolidates access across multiple MBOsand implements CRM business logic

Application User Interface Glue + Screen flow code

Generated MBOWith SQL Interface

SQLLiteData Model



Version 1.0

5 - 33©2011 Sybase, Inc.

5 - 33

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



Version 1.0

5 - 34©2011 Sybase, Inc.

5 - 34

MODU

LE T

OPIC

SMO

DULE

TOP

ICS





Customization




Version 1.0

5 - 35©2011 Sybase, Inc.

5 - 35

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

Continued …



Version 1.0

5 - 36©2011 Sybase, Inc.

5 - 36

Post-Installation for SAP NetWeaver Mobile 7.1� Steps continued…

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



Version 1.0

5 - 37©2011 Sybase, Inc.

5 - 37

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



Version 1.0

5 - 38©2011 Sybase, Inc.

5 - 38

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



Version 1.0

5 - 39©2011 Sybase, Inc.

5 - 39

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



Version 1.0

5 - 40©2011 Sybase, Inc.

5 - 40

Enabling Channel Activation



Version 1.0

5 - 41©2011 Sybase, Inc.

5 - 41

ESDMA Generation� Execute transaction SDOE_ESDMA_DESIGN

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



Version 1.0

5 - 42©2011 Sybase, Inc.

5 - 42

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



Version 1.0

5 - 43©2011 Sybase, Inc.

5 - 43

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



Version 1.0

5 - 44©2011 Sybase, Inc.

5 - 44

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:



Version 1.0

5 - 45©2011 Sybase, Inc.

5 - 45

SAP Resources� NetWeaver Mobile 7.1 Architecture & Runtime overview

� www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e048e20c-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



Version 1.0

5 - 46©2011 Sybase, Inc.

5 - 46

MODU

LE T

OPIC

SMO

DULE

TOP

ICS

Customization








Version 1.0

5 - 47©2011 Sybase, Inc.

5 - 47

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

� The Sybase Unwired Platform Server will not, however, know the difference between iPhone and Windows Mobile Sales applications.



Version 1.0

5 - 48©2011 Sybase, Inc.

5 - 48

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

Continued …



Version 1.0

5 - 49©2011 Sybase, Inc.

5 - 49

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



Version 1.0

5 - 50©2011 Sybase, Inc.

5 - 50

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

Application Business Objects (ABO) - Hand Written

Consolidates access across multiple MBOsand implements CRM business logic

Application User Interface Glue + Screen flow code

Generated MBOWith SQL Interface

SQLLiteData Model



Version 1.0

5 - 51©2011 Sybase, Inc.

5 - 51

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



Version 1.0

5 - 52©2011 Sybase, Inc.

5 - 52

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 columndefinitions

� 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



Version 1.0

5 - 53©2011 Sybase, Inc.

5 - 53

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:

� Account� Contacts� Activities� Leads� Opportunity� Sales Order� Analytics

Continued …



Version 1.0

5 - 54©2011 Sybase, Inc.

5 - 54

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



Version 1.0

5 - 55©2011 Sybase, Inc.

5 - 55

Application User Interface� 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� Components� Libraries� Resources Files� Bundles� Graphics and Images� Certificates� Subprojects

Continued …



Version 1.0

5 - 56©2011 Sybase, Inc.

5 - 56

Application User Interface� 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.

Continued …



Version 1.0

5 - 57©2011 Sybase, Inc.

5 - 57

Application User Interface� 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

Continued …



Version 1.0

5 - 58©2011 Sybase, Inc.

5 - 58

Application User Interface� 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

Continued …



Version 1.0

5 - 59©2011 Sybase, Inc.

5 - 59

Application User Interface� 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



Version 1.0

5 - 60©2011 Sybase, Inc.

5 - 60

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



Version 1.0

5 - 61©2011 Sybase, Inc.

5 - 61

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

Continued …



Version 1.0

5 - 62©2011 Sybase, Inc.

5 - 62

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

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



Version 1.0

5 - 63©2011 Sybase, Inc.

5 - 63

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

Continued …



Version 1.0

5 - 64©2011 Sybase, Inc.

5 - 64

Implementing Custom Extensions for iPhone

Continued …

� 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



Version 1.0

5 - 65©2011 Sybase, Inc.

5 - 65

Implementing Custom Extensions for iPhone� 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�Imagesfolder

� 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

Continued …



Version 1.0

5 - 66©2011 Sybase, Inc.

5 - 66

Implementing Custom Extensions for iPhone� 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

Continued …



Version 1.0

5 - 67©2011 Sybase, Inc.

5 - 67

Implementing Custom Extensions for iPhone� The abo project:

� Include: contains interface files “.h” files

� The same interfaces files are in the icrm Classes�Includesfolder

� 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

Continued …



Version 1.0

5 - 68©2011 Sybase, Inc.

5 - 68

Implementing Custom Extensions for iPhone� 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

Continued …



Version 1.0

5 - 69©2011 Sybase, Inc.

5 - 69

Implementing Custom Extensions for iPhone� 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 libraryContinued …



Version 1.0

5 - 70©2011 Sybase, Inc.

5 - 70

Implementing Custom Extensions for iPhone� 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

Continued …



Version 1.0

5 - 71©2011 Sybase, Inc.

5 - 71

Implementing Custom Extensions for iPhone� 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



Version 1.0

5 - 72©2011 Sybase, Inc.

5 - 72

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)

Continued …



Version 1.0

5 - 73©2011 Sybase, Inc.

5 - 73

Implementing CEs for Windows Mobile� 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

Continued …



Version 1.0

5 - 74©2011 Sybase, Inc.

5 - 74

Implementing CEs for Windows Mobile� 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

Continued …



Version 1.0

5 - 75©2011 Sybase, Inc.

5 - 75

Implementing CEs for Windows Mobile� 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

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.



Version 1.0

5 - 76©2011 Sybase, Inc.

5 - 76

Implementing CEs for Windows Mobile� 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



Version 1.0

5 - 77©2011 Sybase, Inc.

5 - 77

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

Continued …



Version 1.0

5 - 78©2011 Sybase, Inc.

5 - 78

Customization Files for Windows Mobile� 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

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.



Version 1.0

5 - 79©2011 Sybase, Inc.

5 - 79

Customization Files for Windows Mobile� 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



Version 1.0

5 - 80©2011 Sybase, Inc.

5 - 80

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



Version 1.0

5 - 81©2011 Sybase, Inc.

5 - 81

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



Version 1.0

5 - 82©2011 Sybase, Inc.

5 - 82

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



Version 1.0

5 - 83©2011 Sybase, Inc.

5 - 83

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



Version 1.0

5 - 84©2011 Sybase, Inc.

5 - 84

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



Version 1.0

5 - 85©2011 Sybase, Inc.

5 - 85

MODU

LE T

OPIC

SMO

DULE

TOP

ICS





Customization




Version 1.0

5 - 86©2011 Sybase, Inc.

5 - 86

Sybase Control Center� Deployment and Administration of mobile apps use Sybase

Control Center:



Version 1.0

5 - 87©2011 Sybase, Inc.

5 - 87

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



Version 1.0

5 - 88©2011 Sybase, Inc.

5 - 88

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



Version 1.0

5 - 89©2011 Sybase, Inc.

5 - 89




Version 1.0

5 - 90©2011 Sybase, Inc.

5 - 90


� 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



Version 1.0

5 - 91©2011 Sybase, Inc.

5 - 91

Module Post-Assessment� There are no post-assessment questions in this module



Version 1.0

5 - 92©2011 Sybase, Inc.


Sybase Unwired Platform Architectures and Technical OverviewModule 6: Sybase Mobile Workflow for SAP Business Suite Technical Overview

Version 1.0

6 - 1©2011 Sybase, Inc.







Version 1.0

6 - 2©2011 Sybase, Inc.

6 - 2

Module Pre-Assessment1. 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.




Version 1.0

6 - 3©2011 Sybase, Inc.

6 - 3


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

� Sybase Mobile Workflow for SAP customization options



Version 1.0

6 - 4©2011 Sybase, Inc.

6 - 4

MODU

LE T

OPIC

SMO

DULE

TOP

ICS

Sybase Mobile Workflow for SAP Business Suite Overview

Sybase Mobile Workflow for SAP Customization



Version 1.0

6 - 5©2011 Sybase, Inc.

6 - 5

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

1 Workflow & Alerts

3

Business Reason

TimeRecording

Mobile workflowinbox

Facilitate time recording

Faster decision execution on incoming workflows

Improve daily operational activities and

accuracy

2Request approval

for absence & travelLeave & Travel

RequestsMaximize user and

manager productivity

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



Version 1.0

6 - 6©2011 Sybase, Inc.

6 - 6

Business Process Acceleration� End-to-end:

• 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

Staff/Employee

Processes

RolesOperational

ManagerStaff/Employee

Submit request via workflow

Receive workflow

item

Review request

Submitapproval

Send answerto requestor

ERP

Request approved

ERP

Proceed to next step in

workflow engine

ERPMobile Inbox

• 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 Benefit



Version 1.0

6 - 7©2011 Sybase, Inc.

6 - 7

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



Version 1.0

6 - 8©2011 Sybase, Inc.

6 - 8

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

� For each device, note the user name, Unwired Server name, Unwired Server port number, relay server farm ID (if applicable), and activation code.



Version 1.0

6 - 9©2011 Sybase, Inc.

6 - 9

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



Version 1.0

6 - 10©2011 Sybase, Inc.

6 - 10

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:

Devices

SUP Protocol

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



Version 1.0

6 - 11©2011 Sybase, Inc.

6 - 11

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

Continued …



Version 1.0

6 - 12©2011 Sybase, Inc.

6 - 12

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



Version 1.0

6 - 13©2011 Sybase, Inc.

6 - 13

MODU

LE T

OPIC

SMO

DULE

TOP

ICS

Sybase Mobile Workflow for SAP Business Suite Overview

Sybase Mobile Workflow for SAP Customization



Version 1.0

6 - 14©2011 Sybase, Inc.

6 - 14

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



Version 1.0

6 - 15©2011 Sybase, Inc.

6 - 15

Dictionary Objects� Custom Repository Objects must be created for

customization� Dictionary Objects:

� See “Sybase Mobile Workflow for SAP ® Business Suite 1.2” white paper for a complete task outline on how to create these objects.



Version 1.0

6 - 16©2011 Sybase, Inc.

6 - 16

Class Library/Classes� Class Library/Classes:

� Creating the class in SAP:



Version 1.0

6 - 17©2011 Sybase, Inc.

6 - 17

Function Groups/Function Modules



Version 1.0

6 - 18©2011 Sybase, Inc.

6 - 18

Other Objects� Includes:

� SET/GET Parameters:



Version 1.0

6 - 19©2011 Sybase, Inc.

6 - 19

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

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



Version 1.0

6 - 20©2011 Sybase, Inc.

6 - 20

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

Continued …



Version 1.0

6 - 21©2011 Sybase, Inc.

6 - 21

SAP Mobile Destination Setting

Continued …



Version 1.0

6 - 22©2011 Sybase, Inc.

6 - 22

SAP Mobile Destination Setting� 2. Specify the user name and password as defined by your

Sybase Unwired Platform administrator:



Version 1.0

6 - 23©2011 Sybase, Inc.

6 - 23

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:

Continued …



Version 1.0

6 - 24©2011 Sybase, Inc.

6 - 24

Workflow Template Customization� 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:

Continued …



Version 1.0

6 - 25©2011 Sybase, Inc.

6 - 25

Workflow Template Customization� On the next tab, Properties, configure the settings for the

Mobile Workflow push:

� See notes for details

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



Version 1.0

6 - 26©2011 Sybase, Inc.

6 - 26

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



Version 1.0

6 - 27©2011 Sybase, Inc.

6 - 27

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

Continued …



Version 1.0

6 - 28©2011 Sybase, Inc.

6 - 28

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



Version 1.0

6 - 29©2011 Sybase, Inc.

6 - 29

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”

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



Version 1.0

6 - 30©2011 Sybase, Inc.

6 - 30

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 definitionContinued …



Version 1.0

6 - 31©2011 Sybase, Inc.

6 - 31

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

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



Version 1.0

6 - 32©2011 Sybase, Inc.

6 - 32

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:

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



Version 1.0

6 - 33©2011 Sybase, Inc.

6 - 33

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



Version 1.0

6 - 34©2011 Sybase, Inc.

6 - 34

Default Screen User Interfaces� Examples:

Activate Screen

Credentials Screen

Client-initiatedWelcome Screen

Continued …



Version 1.0

6 - 35©2011 Sybase, Inc.

6 - 35

Default Screen User Interfaces

Server-initiatedScreen



Version 1.0

6 - 36©2011 Sybase, Inc.

6 - 36




Version 1.0

6 - 37©2011 Sybase, Inc.

6 - 37


� 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



Version 1.0

6 - 38©2011 Sybase, Inc.

6 - 38

Module Post-Assessment1. 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.



Sybase Unwired Platform Architectures and Technical OverviewModule 7: Administering Sybase Unwired Platform Environments

Version 1.0

7 - 1©2011 Sybase, Inc.







Version 1.0

7 - 2©2011 Sybase, Inc.

7 - 2

Module Pre-Assessment1. 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.




Version 1.0

7 - 3©2011 Sybase, Inc.

7 - 3

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

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



Version 1.0

7 - 4©2011 Sybase, Inc.

7 - 4

MODU

LE T

OPIC

SMO

DULE

TOP

ICS Introduction to the Sybase Control Center

Architecture

Device Management

Monitoring

Workflow Administration



Version 1.0

7 - 5©2011 Sybase, Inc.

7 - 5

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



Version 1.0

7 - 6©2011 Sybase, Inc.

7 - 6

Administration ComponentsCore Unwired Server� Server components

� Replication-Sync Server� Messaging-Sync Server

� Database components� Consolidated, Cluster, and

Monitor Database � SQL Anywhere 11.0.1.2045

� Messaging Server Database� Advantage Database

Server 9.1� Management components

� Server (Unified Agent Service)

� Repository Database� SQL Anywhere 11

Optional� Relay Server � Relay Server Outbound Enabler� Afaria 6.5

� Afaria Server � Afaria Management

Console (IIS)� Afaria Database

� SQL Anywhere� Afaria Client Service

� OpenDS LDAP Server� Installed in Developer

Edition

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



Version 1.0

7 - 7©2011 Sybase, Inc.

7 - 7

Component Model

Management Agent

Relay Server Outbound Enabler

Security Server (LDAP, Windows OS,…)Relay Server

Messaging Sync subsystemReplication Sync subsystem

Unwired Server

Unwired Server Node (1..n)

Unwired ClusterConsolidated Database (SA)

Cluster Database (SA)

Messaging Database (ADS)

Monitor Database



Version 1.0

7 - 8©2011 Sybase, Inc.

7 - 8

Sybase Control Center Architecture

Node 1

Node n

Web Container RMI Service

SCC Plugin for SUP


SUP Flex Web Application

MBeanInterface

SNMP ServiceSUP SNMP

Plugin

Browser

SNMP Client

Custom Admin Java Client

Flash Plug-in Unwired Server

IIOPS

HTTPS

SNMP

RMI

IIOP

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



Version 1.0

7 - 9©2011 Sybase, Inc.

7 - 9

Administration Options in Sybase Control Center

Domain

MBO PackageLogging (Package and Client)

Security Configurations

Server Connections

Cache Groups

Synchronization Groups

Subscriptions

Role Mappings

Security Configuration

Mobile Workflow Package

Security Configuration

Users

Monitoring

Devices

Authentication Provider

Authorization Provider

Attribution Provider

Administrators

Audit Provider

Application Users

Messaging Devices

Replication Devices

Replication Sync

Messaging Sync

Messaging Queues

Data Change Notifications

Device Notifications

Cache

Monitoring Configuration

Monitoring Profiles

Matching Rules

Context Variables

Users (Devices)

Errors

Cluster WideServer Communication Ports

CDB Configuration

Replication Synchronization Configuration

Log ConfigurationPerformance Configuration

Server

Messaging Synchronization Configuration

Server Specific



Version 1.0

7 - 10©2011 Sybase, Inc.

7 - 10

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



Version 1.0

7 - 11©2011 Sybase, Inc.

7 - 11

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

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.



Version 1.0

7 - 12©2011 Sybase, Inc.

7 - 12

Runtime Databases to Consider� 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 themessaging 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.

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.



Version 1.0

7 - 13©2011 Sybase, Inc.

7 - 13

Runtime Databases to Consider� 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

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.



Version 1.0

7 - 14©2011 Sybase, Inc.

7 - 14

Runtime Databases to Consider� 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

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



Version 1.0

7 - 15©2011 Sybase, Inc.

7 - 15

MODU

LE T

OPIC

SMO

DULE

TOP


Architecture

Device Management

Monitoring




Version 1.0

7 - 16©2011 Sybase, Inc.

7 - 16

Control Center Home Page

The toolbar is based on tile views which can be

opened or closed via the toolbar icons

Menu bar contains major view and areas

in the SCC

Most views contain tabs – look inside

eachThe Unwired Cluster

Tree View

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



Version 1.0

7 - 17©2011 Sybase, Inc.

7 - 17

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

� 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



Version 1.0

7 - 18©2011 Sybase, Inc.

7 - 18

General Administration Tasks



Version 1.0

7 - 19©2011 Sybase, Inc.

7 - 19

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)



Version 1.0

7 - 20©2011 Sybase, Inc.

7 - 20

Creating Logins� Create logins by clicking the Application menu and selecting

Administration

� Logins are createdvia the Security folder:



Version 1.0

7 - 21©2011 Sybase, Inc.

7 - 21

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



Version 1.0

7 - 22©2011 Sybase, Inc.

7 - 22

SCC Server Configuration� Select the Sybase Unwired Platform server to configure:



Version 1.0

7 - 23©2011 Sybase, Inc.

7 - 23

Consolidated Database Configuration� Review Consolidated Database configuration:



Version 1.0

7 - 24©2011 Sybase, Inc.

7 - 24

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



Version 1.0

7 - 25©2011 Sybase, Inc.

7 - 25

Server Log� Each discovered/registered Unwired Server has its own

log� Can be displayed in text or grid view



Version 1.0

7 - 26©2011 Sybase, Inc.

7 - 26

Server Log Configuration� Log Settings

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

� Truncate Log

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



Version 1.0

7 - 27©2011 Sybase, Inc.

7 - 27

Creating a Domain� Select Domains � Click New and enter the domain name:



Version 1.0

7 - 28©2011 Sybase, Inc.

7 - 28

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



Version 1.0

7 - 29©2011 Sybase, Inc.

7 - 29

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



Version 1.0

7 - 30©2011 Sybase, Inc.

7 - 30

Packages� Deploy and administer packages in the SCC:

These are MBOs in a Package



Version 1.0

7 - 31©2011 Sybase, Inc.

7 - 31

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)

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



Version 1.0

7 - 32©2011 Sybase, Inc.

7 - 32

MODU

LE T

OPIC

SMO

DULE

TOP


Architecture

Device Management

Monitoring




Version 1.0

7 - 33©2011 Sybase, Inc.

7 - 33

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



Version 1.0

7 - 34©2011 Sybase, Inc.

7 - 34

Notification Mailbox� Notification Mailbox

� Mail server host and port� Mailbox username and password

� One-time Configuration Task



Version 1.0

7 - 35©2011 Sybase, Inc.

7 - 35

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



Version 1.0

7 - 36©2011 Sybase, Inc.

7 - 36

Workflow Devices� Devices

� Assignment/Un-assignment� Queue Items

� Reviewing device queue status� Error Log

used to review device errors



Version 1.0

7 - 37©2011 Sybase, Inc.

7 - 37

Assigning Users to Workflows� Can assign or un-assign users to a workflow device:



Version 1.0

7 - 38©2011 Sybase, Inc.

7 - 38

MODU

LE T

OPIC

SMO

DULE

TOP


Architecture

Device Management

Monitoring




Version 1.0

7 - 39©2011 Sybase, Inc.

7 - 39

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



Version 1.0

7 - 40©2011 Sybase, Inc.

7 - 40

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

license



Version 1.0

7 - 41©2011 Sybase, Inc.

7 - 41

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



Version 1.0

7 - 42©2011 Sybase, Inc.

7 - 42

Server Communication Ports� Modify management port (IIOP and IIOPS) in the SCC

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



Version 1.0

7 - 43©2011 Sybase, Inc.

7 - 43

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 …



Version 1.0

7 - 44©2011 Sybase, Inc.

7 - 44

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)



Version 1.0

7 - 45©2011 Sybase, Inc.

7 - 45

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



Version 1.0

7 - 46©2011 Sybase, Inc.

7 - 46

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



Version 1.0

7 - 47©2011 Sybase, Inc.

7 - 47

MODU

LE T

OPIC

SMO

DULE

TOP

ICS

Monitoring

Introduction to the Sybase Control Center

Architecture

Device Management




Version 1.0

7 - 48©2011 Sybase, Inc.

7 - 48

Monitoring Tasks



Version 1.0

7 - 49©2011 Sybase, Inc.

7 - 49

Server-level Monitoring



Version 1.0

7 - 50©2011 Sybase, Inc.

7 - 50

MBS Request History



Version 1.0

7 - 51©2011 Sybase, Inc.

7 - 51

User Statistics and Security Log

Messaging-based synchronization Package User KPIs

Different KPIs for Replication-based

Package User



Version 1.0

7 - 52©2011 Sybase, Inc.

7 - 52

Device Notifications (RBS Push) History & KPIs

Available KPIs



Version 1.0

7 - 53©2011 Sybase, Inc.

7 - 53

Cache StatisticsPackage-level Cache Group: Snapshot Data

Domain-level: Usage Data

Package-level: KPIs



Version 1.0

7 - 54©2011 Sybase, Inc.

7 - 54

Messaging Queues� Historical and Snapshot Data:



Version 1.0

7 - 55©2011 Sybase, Inc.

7 - 55




Version 1.0

7 - 56©2011 Sybase, Inc.

7 - 56

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



Version 1.0

7 - 57©2011 Sybase, Inc.

7 - 57

Module Post-Assessment1. 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.




Version 1.0

7 - 58©2011 Sybase, Inc.


Sybase Unwired Platform Architectures and Technical OverviewModule 8: Afaria Device Management Architecture and Overview

Version 1.0

8 - 1©2011 Sybase, Inc.



Version 1.0

8 - 2©2011 Sybase, Inc.




Version 1.0

8 - 3©2011 Sybase, Inc.



Version 1.0

8 - 4©2011 Sybase, Inc.



Version 1.0

8 - 5©2011 Sybase, Inc.



Version 1.0

8 - 6©2011 Sybase, Inc.



Version 1.0

8 - 7©2011 Sybase, Inc.



Version 1.0

8 - 8©2011 Sybase, Inc.



Version 1.0

8 - 9©2011 Sybase, Inc.



Version 1.0

8 - 10©2011 Sybase, Inc.



Version 1.0

8 - 11©2011 Sybase, Inc.



Version 1.0

8 - 12©2011 Sybase, Inc.



Version 1.0

8 - 13©2011 Sybase, Inc.



Version 1.0

8 - 14©2011 Sybase, Inc.



Version 1.0

8 - 15©2011 Sybase, Inc.



Version 1.0

8 - 16©2011 Sybase, Inc.



Version 1.0

8 - 17©2011 Sybase, Inc.



Version 1.0

8 - 18©2011 Sybase, Inc.



Version 1.0

8 - 19©2011 Sybase, Inc.



Version 1.0

8 - 20©2011 Sybase, Inc.



Version 1.0

8 - 21©2011 Sybase, Inc.



Version 1.0

8 - 22©2011 Sybase, Inc.



Version 1.0

8 - 23©2011 Sybase, Inc.



Version 1.0

8 - 24©2011 Sybase, Inc.



Version 1.0

8 - 25©2011 Sybase, Inc.



Version 1.0

8 - 26©2011 Sybase, Inc.



Version 1.0

8 - 27©2011 Sybase, Inc.

� Client types supported:� Android� Blackberry� Symbian� Palm� Java� Win32� Windows Mobile Professional and Standard



Version 1.0

8 - 28©2011 Sybase, Inc.



Version 1.0

8 - 29©2011 Sybase, Inc.



Version 1.0

8 - 30©2011 Sybase, Inc.



Version 1.0

8 - 31©2011 Sybase, Inc.



Version 1.0

8 - 32©2011 Sybase, Inc.



Version 1.0

8 - 33©2011 Sybase, Inc.



Version 1.0

8 - 34©2011 Sybase, Inc.



Version 1.0

8 - 35©2011 Sybase, Inc.



Version 1.0

8 - 36©2011 Sybase, Inc.



Version 1.0

8 - 37©2011 Sybase, Inc.



Version 1.0

8 - 38©2011 Sybase, Inc.



Version 1.0

8 - 39©2011 Sybase, Inc.



Version 1.0

8 - 40©2011 Sybase, Inc.



Version 1.0

8 - 41©2011 Sybase, Inc.




Version 1.0

8 - 42©2011 Sybase, Inc.


�2011 Sybase, Inc. Sybase Unwired Platform Architectures and Technical Overview – Version 1.0 A-1

Appendix A: Answers to Pre/Post Assessments


There are no Pre-Assessments in this module.

1. 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).

Pre-Assessments:

Post-Assessments:


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

A - 2 Sybase Unwired Platform Architectures and Technical Overview – Version 1.0 �2011 Sybase, Inc.


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.

There are no Post-Assessments in this module.

Pre-Assessments:

Post-Assessments:


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

�2011 Sybase, Inc. Sybase Unwired Platform Architectures and Technical Overview – Version 1.0 A - 3


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.

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.

Pre-Assessments:

Post-Assessments:


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


Module 4: Sybase Unwired Platform Mobile Workflow Applications

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.

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

2. True/False: New controls can not be added to generated screens. Answer: True, with a few exceptions.

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

Answer: False.

Pre-Assessments:

Post-Assessments:


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



There are no Pre-Assessment questions in this module.

There are no Post-Assessment questions in this module.

Pre-Assessments:

Post-Assessments:


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



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

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.

Pre-Assessments:

Post-Assessments:


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



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.

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.

Pre-Assessments:

Post-Assessments:


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


Module 8: Afaria Device Management Architecture and Overview

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

1. True/False: Using Afaria, remote devices must be configured in the office. Answer: False. Using Afaria, IT personnel can setup and manage a mobile workers devices remotely.

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

Pre-Assessments:

Post-Assessments:



*SUP101-90-0153-10-SG-S*Printed In Canada


SUP101-90-0153-10

Documents

SUP101 - Sybase Unwired Platforms Architectures and Technical Overview