sup development wp
Post on 04-Jun-2018
215 Views
Preview:
TRANSCRIPT
8/13/2019 SUP Development WP
http://slidepdf.com/reader/full/sup-development-wp 1/12
WHITE PAPER
www.sybase.com
Sybase® Unwired PlatformDevelopment Paradigm
8/13/2019 SUP Development WP
http://slidepdf.com/reader/full/sup-development-wp 2/12
TABLE OF CONTENTS
Sybase Unwired Platform ..........................................................................................................................................1
Mobile Application Development ..................... ....................... ....................... ....................... ....................... ........ 2
Mobile Business Object (MBO) Development .................... ....................... ...................... ....................... ......... 3
Mobile Business Objects (MBOs) ..........................................................................................................................4
Mobile Business Object Development in Eclipse ..................... ....................... ....................... ....................... . 5
Device Application Development ...................... ....................... ....................... ....................... ...................... ......... 5
Container-based Development (Mobile Workflows) ....................................................................................6
SAP Workflow Mobilized Using Sybase Unwired Platform ..................... ....................... ....................... ..... 7
Native Application Development ..................... ....................... ....................... ...................... ....................... ......... 7
Production Application Development — Custom Development Using the Object API ................ 8
Rapid Prototype Development — Device Application Designer ..............................................................9
Summary .........................................................................................................................................................................9
8/13/2019 SUP Development WP
http://slidepdf.com/reader/full/sup-development-wp 3/12
1
SYBASE UNWIRED PLATFORM
Sybase Unwired Platform is a flexible, open infrastructure that addresses the challenge of creating and managing
multiple mobile applications that securely connect heterogeneous back-end data sources to major mobile device
types (See Figure 1). This mobile enterprise application platform enables you to respond strategically as your
device type and data source needs evolve, whether because of acquisitions, system refreshes or mobile device
technology changes.
Sybase Unwired Platform main components are:
• Sybase Unwired Workspace, which allows modeling of Mobile Business Objects
• Mobile Workflow Forms Designer, which provides quick mobilization of business processes without coding
• Device Application Designer, which enables developers to create prototype mobile applications using code
generation approach
• Sybase Control Center, which allows administrators to administer, manage and monitor Sybase Unwired Platform
• Sybase Unwired Server, which is the middleware component providing the runtime infrastructure
The key technical features of the Sybase Unwired Platform include:
• Heterogeneous native device development: iPhone®/iPad™, Windows Mobile, Windows 32 laptops/tablets, BlackBerry®• Codeless development for workflow applications: iPhone/iPad, Windows Mobile
• 4GL Rapid Application Development (RAD) tooling and data source integration
• Out-of-the-box integration with enterprise applications (SAP®, databases, and so on) and a f ull Web services stack
• Mobilization of multiple applications and business processes
• Integrated device management and security
Figure 1.
Management Console
ControlDevice and server
management and security
BlackBerry
iPhone
iPad
Windows
Windows Mobile
ConsumeHeterogeneousmobile devices
ConnectHeterogeneous
data sources
Create
Eclipse
Databases
WebServices
SoftwareApplications
Mobile
Business
Objects
Workflows
NativeApplications
Sybase Unwired Platform
8/13/2019 SUP Development WP
http://slidepdf.com/reader/full/sup-development-wp 4/12
2
MOBILE APPL ICATION DEVELOPMENT
When developing mobile applications, you must primarily address data and its associated synchronization, the
device-resident presentation and business logic. The Sybase Unwired Platform provides the tools developers need
to focus on each of these requirements. At the root of the Sybase Unwired Platform development paradigm is the
separation between:
• Modeling the data tier and its link with the enterprise information system (EIS).
and
• The user interface and business logic of the application.
Sybase Unwired Platform provides tools that enable mobile application development in both these domains (see
Figure 2). To address the data aspects of the mobile application, Sybase Unwired Platform uses mobile business
objects (MBO). “MBO development” refers to defining object data models with back-end EIS connections, attributes,
operations and relationships that allow filtered data sets to be synchronized to the device. This aspect of Sybase
Unwired Platform development is supported within Eclipse.
The development tasks associated with the user interface and logic are supported in two paradigms.
• The first paradigm involves building native applications using programming languages native to a mobileoperating system in an integrated development environment (IDE) using the generated API.
• The second paradigm involves a codeless container-driven approach, in which metadata drives the application
interface and logic.
Depending on the application requirements and complexity of the use case, developers can use any of these
approaches to build a mobile application. This paper will help you understand how to develop mobile applications
with Sybase Unwired Platform using each of these approaches.
Figure 2.
2
Develop
MobileBusinessObjects
Deploy Mobile
BusinessObjects to
Unwired Server
GenerateDevice
Object Code
Sybase Unwired Platform Development Task Flow
Sybase Unwired Platform Development Tools
DevelopDevice
Application
Generate and
Customize DeviceApplicationNative Code
Test on
Emulatorand/orDevice
Unwired WorkSpace Device Application Development Tool (Eclipse)
Unwired WorkSpace Workflow Development Tool (Eclipse)
Native Device Application Development Tools
Windows Mobile
BlackBerry – IDE, Eclipse IDE Plug-in
Windows – Eclipse, Visual Studio
Windows Mobile – Visual Studio
iPhone – Xcode
iPhone iPadWindows Mobile
BlackBerry
Unwired WorkSpace MobileBusiness Object Development Tool
(Eclipse)
BlackBerryJava
iPhoneObjective C
WindowsJava SE and C#
Windows MobileC#
8/13/2019 SUP Development WP
http://slidepdf.com/reader/full/sup-development-wp 5/12
8/13/2019 SUP Development WP
http://slidepdf.com/reader/full/sup-development-wp 6/12
4
MOBILE BUSINESS OBJECTS (MBOs)
MBOs encapsulate business process logic and data into a reusable unit. Again, to create MBOs, you have two
development options: the top-down approach or the bottom-up approach.
To use a top-down development approach, use the Mobile Application Diagram and palette, as shown in Figure 4,
which will launch a set of wizards that create MBOs with operations and attributes. When you are ready, bind the
MBO to its data source.
If you are using the bottom-up approach, drag and drop a data source to create the MBO directly from the data
source with immediate binding. You can either define MBO attributes and operations without immediately binding
them to a data source, or you can define them from and bind them to a data source.
At some point in the development process, you must bind the attributes and operations that define an MBO to a
data source. If you already have a connection to the data source through a connection profile, you can quickly generate
attribute and operation bindings based on the data source. However, if you do not yet have access to the required data
source, you can define the MBO, and later bind the operations and attributes to the data source.
The difference between the two development approaches is when you create and bind the attributes and operations.
You can either create an MBO and bind to a data source immediately, or you can defer data source binding.
You have two options for creating an MBO and binding to a data source immediately:
1. Drag and drop the data source onto the Mobile Application Diagram, which launches the appropriate wizards
and automatically creates bindings based on the selected data source.
2. Create an MBO and its operations and attributes using the Mobile Application Diagram and palette that
launches a set of wizards and allows you to bind them directly to a data source.
Figure 4.
8/13/2019 SUP Development WP
http://slidepdf.com/reader/full/sup-development-wp 7/12
5
To create an MBO and defer data source binding:
1. Create an MBO and its operations and attributes using the Mobile Application Diagram and palette. After you
define the data source, bind the MBO to it from the Properties view.
2. Create attributes and operations for mobile business objects, create relationships between mobile business
objects, bind them to a back-end data sources, and modify and test them.
The last step in the MBO development process is to create a deployment package that contains the mobile
application, including mobile business objects, role mappings, server connection mappings and other mobile business
object-related artifacts.
Once your development package is complete, deploy it to Sybase Unwired Server. Optionally, you can create a
deployment profile that enables you to manage multiple deployment packages.
MOBILE BUSINESS OBJECT DEVELOPMENT IN ECLIPSE
Sybase Unwired WorkSpace works like a plug-in to your Eclipse development environment. Experienced Eclipse
developers are familiar with the consistent us e of windows, explorers, views, wizards and preferences. Developers
new to Eclipse can use the online help, cheat sheets, samples and tutorials of Sybase Unwired WorkSpace to become
familiar with MBO and device application development.
DEVICE APPLICATION DEVELOPMENT
Sybase Unwired Platform supports two main modes of application development when creating the user interface
and logic. These two modes are container-based development and native application development.
Container-based applications are appropriate for extensions of business processes or workflows such as approvals
or requests.
Native application development makes sense when:
• Business logic is needed• Device services integration is intrinsic to mobile applications
• User interface expectations depend on device-specific capabilities
• No boundaries other than what is provided natively by the mobile operating system are required
• Ability to evolve with mobile operating system is required
The development lifecycle for native device applications, which you can perform in parallel with back-end MBOs,
includes:
1. Develop device applications
2. Generate code and application
3. Deploy application to simulator
4. Debug/test against simulator
5. Configure Afaria® to provision application
8/13/2019 SUP Development WP
http://slidepdf.com/reader/full/sup-development-wp 8/12
6
CONTAINER-BASED DEVELOPMENT (MOBILE WORKFLOWS)
In container-based development, the application is metadata-based and the device has a single container that
interprets this metadata (Figure 5). This container needs to be deployed once and from then on multiple application
metadata can be deployed automatically without having to generate any code.
Figure 5.
Business processes such as alerts, time recording and travel requests require immediate action, but these messages
are generally accessible only with desktop or laptop computers and may not be fulf illed in a timely manner. However,
mobile workflows allow users to complete pre-defined business processes swiftly (Figure 6). Using a metadata-driven
application paradigm, a Sybase Unwired Platform workflow container enables the rapid development of mobile
workflows, in which existing enterprise business processes or workflows can be extended to a mobile device relatively
easily so that decisions can be made at any instant on a mobile device (Figure 7).
Sybase Unwired Platform has primarily two kinds of workflow models — server-initiated and client-initiated.
These models can co-exist within one package.
In the server-initiated workflow model, for example, a
manager receives a request, perhaps an approval for leave. The
request is initiated by a notification from the back-end system,
where Sybase Unwired Platform receives e-mail or data change
notification (DCN) from a master account. Sybase Unwired
Platform, in turn, delivers a message to an individual device
based on configured distribution and MBO extraction rules.
In the client-initiated workflow model, the user sends a
message, such as an expense report. Users can open workflow
forms on their mobile devices and enter data that can be used
either for kicking off an enterprise workflow or continuing astep in an already executing workflow.
All of this development is enabled through a WYSIWYG
design tool that binds the decisions and actions to MBOs.
Connect Data SourceIntegration
SybaseUnwiredPlatformServer
MobileDevice
ContainerDeployMBO
DeployWorkflow
Sybase Unwired WorkSpace
Figure 6.
8/13/2019 SUP Development WP
http://slidepdf.com/reader/full/sup-development-wp 9/12
7
SAP WORKFLOW MOBILIZED USING SYBASE UNWIRED PL ATFORM
Figure 7.
NATIVE APPLICATION DEVELOPMENT
In native application development, the application is based on compiled code that is specific to a particular mobile
operating system. An iPhone application, for example, is developed in Objective C, Windows Mobile in C# and so on.
Native application development provides the most flexibility in terms of leveraging the device services to their fullestpotential, but each application must be provisioned individually after compilation even for minor changes.
Developers use Sybase Unwired Platform for native application development using a standard IDE. Developers
taking the standard IDE approach for native application development (Figure 8) can use the generated code based on
the MBO. You will build the business logic and user interface pieces of the mobile application in your IDE of choice.
iPhone uses XCode, Windows Mobile uses Visual Studio, and BlackBerry uses BlackBerry Eclipse plug-in. When it comes
to building highly performing production applications, the recommended approach for building applications in SUP is
using native IDE’s like XCode, and Visual Studio, to leverage the MBO API.
Figure 8.
EmployeeInitiates
Travel Request
ManagerReceives
Notification
CheckAmount
NotifyEmployee
NotifyManager
Manager Logsinto WEB UI
ApproveSmall
Amounts
ManagerApproves/
Rejects
Employee uses aWidget on Device
to InitiateTravel Request
Manager Receives
a WorkflowNotification on Device
ManagerViews the
Details
ManagerApproves or
Rejects
Connect
SybaseUnwiredPlatform
Server
MBOAPI
DeviceGUI
DeployMBO
GenerateCode
GenerateDefault GUI
SybaseUnwired WorkSpace
Data Source Integration Device-Specific Development
SDK
Customize
8/13/2019 SUP Development WP
http://slidepdf.com/reader/full/sup-development-wp 10/12
8
Optionally, developers can use Sybase Device Application Designer to develop protype applications. Device
Application Designer is a RAD tool with a WYSIWYG editor that provides a graphical approach to building prototype
mobile applications for Windows Mobile and BlackBerry devices. In this approach, assembling the code that enables
screen rendering, control layout, and other functionality is generated by the Device Application Designer in code that
is native to the platform. Developers can take this generated code and integrate their business logic us ing extension
mechanisms native to the platform. For BlackBerry, Sybase Unwired Platform leverages the generation gap pattern for
customizing generated code in a repeatable fashion. Windows Mobile is supported us ing partial classes. The Sybase
Device Application Designer approach fits well as a development option where a prototype needs to be built for an
end-to-end demonstration of mobility value proposition.
Figure 9 shows a Native Mobile Application Functional Architecture where both the designer-generated user
interface and the custom-built user interface consume the Object API modeled in the Eclipse tool. In both cases,
custom coding is required.
Figure 9.
PRODUCTION APPLICATION DEVELOPMENT — CUSTOM DEVELOPMENT USING THE OBJECT API
To develop custom, production mobile device applications, use the Sybase Unwired Platform Client Object API,
which is generated from the MBO and comes in multiple formats: .NET, Java and Objective C. You can use Visual
Studio or any other tool of choice to build the application interface binding to the Client Object API.
After you have deployed MBOs, application development can proceed entirely with the Client Object API, if required
The Client Object API uses the data persistence library to access and store object data in the database on the device.
The Sybase Unwired Platform Code Generation API generates the Client Object API. This code generation takes
place in Unwired WorkSpace in Eclipse. You can generate code manually or by using scripts. Unwired WorkSpace uses
the Code Generation API to provide generation objects as inputs, then the Code Generation API executes using those
inputs. The code generation engine applies the correct templates based on options and the MBO model, and outputs
client objects.
Designer Generated Prototype
MBO Object API Layer
CustomDevice
Application
Generated Object API
Mobile Application
Object API Framework
Mobile OSServices
Messaging
Mobile System Services
Persistence
Development pathfor building a
production mobileapplication
Development pathfor building aprototype mobileapplication
Generated UICode
Customization
UIFamework
GeneratedUI Code
8/13/2019 SUP Development WP
http://slidepdf.com/reader/full/sup-development-wp 11/12
9
RAPID PROTOTYPE DEVELOPMENT — DEVICE APPLICATION DESIGNER
The following steps illustrate how to create a prototype device application using the Device Application Designer in
the Eclipse-based Sybase Unwired Workspace.
1. Using the Flow Design page of the Device Application Designer, create a flow design for custom application screens.
2. Add and connect screens you design, as well as customized stock screens.3. Connect the Start icon to a target screen. The Start icon appears on the Flow Design page, and its connection is
attached to the first screen you add to the Flow Design. You can change the target to any screen in the
Flow Design.
4. Select a device to display an empty canvas in the Screen Design page, formatted for that device.
5. Add controls to your device application screen using the Screen Design palette.
6. Generate the device application code using the Generate Device Application wizard.
7. Test using a mobile device simulator.
Figure 10.
The Device Application Designer (Figure 10) components are:
• A graphic editor that includes introduction, flow design, screen design, and source editor pages.
• A toolbar with icons to verify, generate, undo, redo, zoom, select and specify the orientation of devices and select
screens.
• An outline view in thumbnail and hierarchical modes.
• A multi-tabbed properties view, in which the contents depend on the item selected from the Workbench.
• Problems view to see errors and warnings in your application.
SUMMARY
The flexible, open Sybase Unwired Platform infrastructure offers development teams many options to create
and manage mobile applications that connect heterogeneous back-end data sources to major device types. Sybase
Unwired WorkSpace provides a graphical environment for developing the data aspects of mobile applications. Device
application developers can use native tools to bind to the Object API programmatically, or work in a GUI environment
using the Unwired WorkSpace Device Application Designer to build prototype applications. Compatible with Eclipse,
Visual Studio, and other tools, Sybase Unwired Platform enables development teams to build mobile applications that
use enterprise data sources quickly and effectively.
Toolbar
Outline View
Properties View
MobileDevelopment
Perspective
Problems View
Application Editor
8/13/2019 SUP Development WP
http://slidepdf.com/reader/full/sup-development-wp 12/12
www.sybase.com
Sybase, Inc.
Worldwide Headquarters
One Sybase Drive
Dublin, CA 94568-7902
U.S.A
1 800 8 sybaseCopyright © 2011 Sybase, Inc. All rights reserved. Unpublished rights reserved under U.S. copyright laws. Sybase, theSybase logo, and Afaria are trademarks of Sybase, Inc. or its subsidiaries. ® indicates registration in the United States ofAmerica. SAP and the SAP logo are the trademarks or registered trademarks of SAP AG in Germany and in several othercountries. All other trademarks are the property of their respective owners. 02/11
iPhone is a registered trademark of Apple Inc. iPad is a trademark of Apple Inc.
top related