Start of Content Area

Process documentation BEx Mobile Intelligence Locate the document in its SAP Library structure

Purpose

With the help of BEx Mobile Intelligence, you can access your Web applications on the move. You need one of the following devices:

·        PDA (Personal Digital Assistant) with Microsoft Windows CE 3.0 Operating System and Pocket Internet Explorer

·        WAP-enabled mobile telephone (for example, BlackBerry)

·        i-Mode-enabled mobile telephone

·        Mobile device with an EPOC32 operating system (for example, Nokia Communicator 9210)

Note

Handheld devices, such as Palm Pilots, are also supported to a certain extent. This is dependent upon the browser installed on the system.

The Wireless Application Protocol (WAP) is used as the basis for data transfer with WAP-enabled devices and the Hypertext Transfer Protocol (HTTP) with PDAs. The Wireless Markup Language (WML) for WAP-enabled devices, the Hypertext Markup Language (HTML) without stylesheets and with restricted Java Script for PDAs, and the Compact Hypertext Markup Language (cHTML) for i-Mode-enabled devices, form the descriptive language base.

You can either access your Web application online (for which you need a connection to the BW 3.0 Web Application Server) or offline (no connection). In the latter case, static, pre-calculated HTML pages are used. The pages are precalculated using the Reporting Agent.

The same URL is used to call up BEx Mobile applications as for BEx Web applications. The BW server automatically recognizes which device made the request (PDA, WAP, i-Mode or normal desktop browser), and generates a device-specific HTML or WML page. For this reason, BEx Mobile applications are normal BEx Web applications and are created in the same way as BEx Web applications in the BEx Web Application Designer. For WAP and i-Mode devices, Web items are automatically displayed over several pages.

An additional mobile intelligence function is the use of the Reporting Agent to send an SMS message to a mobile device when a defined exception arises in the Mobile application. By doing this, you highlight the business situations that require close attention.

The following graphic describes the interactions in mobile intelligence:

This graphic is explained in the accompanying text

Process Flow

Mobile intelligence with WAP

This graphic is explained in the accompanying text

...

       1.      You connect to your mobile terminal with a WAP service provider by using your mobile device (for example, a WAP compatible mobile telephone). This allows you to use a WAP Gateway or WAP server, enabling you to transfer contents from the Internet to the mobile device.

       2.      In addition, the WAP-gateway passes on the requested URL to the BW Web Application Server.

       3.      In the URL HTTP request, the BW server recognizes that WML is requested instead of HTML.

       4.      In the BW server, the data is converted into WML.

       5.      The result is returned to the WAP gateway, which converts the WML text data into a compressed byte code and sends it to the mobile device

Background documentation

Compressing the data reduces transfer time.

Mobile intelligence with HTTP

Mobile Intelligence with HTTP has the same process as with the Web applications. See Creating Web Applications with the BEx Web Application Designer.

For more information, see the following sections:

Creating Mobile Applications

Online Scenario

Alert Scenarios

Offline Scenarios

 

 

 

End of Content Area