Show TOC Start of Content Area

Background documentation Executing Mobile Online Applications  Locate the document in its SAP Library structure

Based on wireless technologies such as WAP, WLAN, or GPRS, it is possible to use mobile devices to access information, services, or Enterprise applications. The SAP Web Application Server allows direct access to Web Dynpro applications using mobile devices. These applications are online applications that are executed on the Web Application Server and displayed in the Web browser of the mobile device.

As part of the Web Application Server, Web Dynpro provides a development and runtime environment with which you can quickly and simply create professional user interfaces for mobile devices.

The mobile components of the Web Dynpro runtime environment consist of:

·         The device and browser recognition (ClientInfo) in the Web Application Server

·         WML or HTML renderers that provide data and event handling.

An application developed with Web Dynpro for Java can usually be executed on a mobile device; however, the UIs may have to be adapted for the smaller screen size.

IT Processes of the Scenario Variant

The IT processes of this scenario variant describe the flow of a mobile online application from setting up a connection between a mobile device and the Web Application Server to displaying the requested data in the Web browser of the relevant mobile device.

This scenario variant comprises the following IT processes:

       1.      Creating a connection

       2.      Entering the URL in the browser

       3.      The system checks the authentication and the device ID.

       4.      The system passes the HTTP request to the Web Application Server.

       5.      The system determines the version of the browser using the header information of the HTTP request.

       6.      The system selects the appropriate page renderer.

       7.      The system sets up a connection to the backend system and accesses the data.

       8.      The system retrieves the data from the backend application.

       9.      The system renders the content into the appropriate markup language.

   10.      The system sends the HTTP response.

   11.      The system adapts certain UI elements.

   12.      The system passes the page to the mobile device.

   13.      The browser window displays the page.

 

End of Content Area