Component documentation Developing Mobile Applications for Occasional Connection 

Purpose

This scenario variant allows you to develop applications for client devices like laptops, ultra mobile PCs and PDAs. These applications can run on the devices in offline mode.  

To develop these applications, you use the specialized development tools provided in the back-end system, the SAPNetWeaver Application Server, and the SAPNetWeaver Developer Studio.

Architecture of the Scenario Variant

The following figure provides an overview of the architecture of the scenario variant:

This graphic is explained in the accompanying text

SAPNetWeaver Mobile consists of specialized development tools to define data and create applications:

  In the SAP NetWeaver AS, the Data Orchestration Workbench, which is part of the Data Orchestration Engine (DOE), provides tools to define the data structure (data objects), distribution logic, and back-end adapters.

  In the SAP NetWeaver Developer Studio, the Mobile Web Dynpro Offline perspective allows yo to create mobile applications. These applications are based on the data objects created in the Data Orchestration Workbench.

The back-end system contains all the original data. This is the source for data replication.

Required and Optional Installable Units

To use this variant, you require the following installable units:

  Mobile

  SAP NetWeaver Development Infrastructure (DI)

  Application Server ABAP (AS ABAP)

  Application Server Java (AS JAVA) – optional

For more information about the required system landscape, see the Master Guide on SAP Service Marketplace at service.sap.com/installnwmobile71.

IT Processes of the Scenario Variant

This scenario variant comprises the following IT processes

Process

Description

Defining Back-End Interface

Developers define the data required for the mobile scenario by identifying the existing BAPIs and, if necessary, enhancing them. New BAPI wrappers can also be added.

Defining Data Model and Data Distribution Logic

Developers import the metadata into the Data Orchestration Engine (DOE), which can then be modified and extended as necessary.

Developing Mobile Components

Developers import the data objects from the DOE and create the business logic and user interface of the application. The application is packed into an archive and uploaded to the DOE for deployment to the mobile devices.

Testing Mobile Scenario

Developers test and debug the mobile scenario including the back-end, DOE, and a mobile device.

Related Information

The following role-specific guide contains further information about this scenario variant:

Task Area

Guide

Development

Developing Mobile Applications

 

Was this page helpful to you?