End-user documentation @ SAP Help Portal

 

Using SAP Mobile Infrastructure

This chapter gives a quick start on using SAP MI. For more information, please consult the end-user documentation at the SAP Help Portal.

Starting SAP Mobile Infrastructure

To start SAP Mobile Infrastructure, select Start -> Programs -> SAP Mobile Engine. A browser window appears with the MI logon page:

Logon to MI using your Web AS user and password. If you haven't logged in before, your user will be created locally and compared against your Web AS user on first synchronization. If you logged in before, you need to furnish the same password or request a new password by clicking New Password.
MI supports multiple users sharing the same device as explained in detail in the chapter multiple user support.

After successful logon, the MI home page is shown:

In the system tray at the bottom-right hand-side of your screen, you see an MI icon displaying the current state of MI ( if MI is running and and if it is stopped). On right-click, the icon allows to start/stop the MI Client as well as launch the MI homepage. While the MI is running, you can also launch it in a browser with the URL http://localhost:4444.

Note that on first logon, your long user name is not displayed after Hello. On first synchronization, your long user name will be requested from the Web AS and display in the grey line starting with hello.

Installation information

Right after installation, no MI applications are yet installed as as they are always automatically deployed from the MI server at first synchronization.
Choosing the Info link, a page is displayed showing the version of the MI Client Component as well as the versions and names of all other applications that have are registered with the framework. An application that is deployed from the server, is automatically deployed with the framework. Applications that are manually deployed to MI's Tomcat during the development process are not registered with the MI client and will hence not be displayed on the MI homepage. Get back to MI homepage via the HOME link or by clicking on the MI logo on the upper left hand-side.
To see the current MI version, you can also right-click on MI icon in the system tray and select About.

MI administration

Choosing the My Settings link, you can enter the settings necessary to allow synchronization with the MI server. These are basically the server location and the user information needed for authentication at the server. No further administration is necessary on the client-side.
If the MI serveris not yet set up, you should not fill this screen at this stage. When you have reached the Generic Sync tutorial, it will be necessary that you furnish at least dummy logon data though.

The following information needs to be furnished:

Field name

Description  
User The user name on the WebAS. This field cannot be changed because you're already logged on under this name.
Client Client on the ABAP stack of the WebAS.
Language The language that you normally use to logon to the WebAS. It will be used by MI to log onto the WebAS also and may influence language-specific application data.
Country This setting will be drawn to localize dates, time and currency formatting in the way typical for your country.
Time Zone The time zone will be used as reference time zone for localizing time stamps
Daylight Saving Time This setting displays whether your time zone uses daylight saving time during the summer.
Protocol You can select http or https as transmission protocol. For secure communication via https, SSL also needs to be enabled on the Java Stack of WebAS.
Host Host machine for Java Stack of WebAS
Port If your protocol is http, choose the http port of the Java Stack of the WebAS. If your protocol is https, choose the https port of Java Stack of the WebAS.
System System name of the ABAP stack of the WebAS
Proxy, Host and Port If a proxy is needed to reach the gateway, the proxy checkbox must be checked and the proxy's host and port information must be furnished.
Device ID Specifies the id of your local device. The Device ID is generated by the server on first synchronization of the device and communicated to the device. All users of a device see the same device ID. It is used by the server to identify the device and is displayed in the Web Console for device identification.

 

To save and activate the settings, click Save. If you changed your proxy settings, you need to restart MI also (i.e. right-click on the MI icon in the system tray and select first Stop and then Start).

Synchronization

To synchronize data with the MI server, select on MI's homepage. MI will try to establish an http(s) connection with the gateway or proxy defined in the user settings and send its registry (see Installation information) as well as data that applications released for synchronization to the MI server. In return, all data queued on the MI server for this client device is transported back. The synchronization log is automatically displayed after the synchronization. It should be read carefully by the user, as it may contain error information or the request to restart MI.

Tracing application or deployment problems

MI and MI applications use the Logging API to write trace files on the client. You can activate the trace by clicking the Trace link on the My Settings page. Select a trace level via the dropdown box and activate the trace by clicking on Turn On. You can then recreate the problem (e.g. a failed synchronization) and afterwards navigate back to to trace screen. You can now display the trace file in the browser, prepare its sending to the administrator or delete it. If you choose to send it to the administrator, it will be released internally and be sent to the MI Server on next successful synchronization where it will be displayed in the MI Web Console. If no synchronization is possible, the trace file can also be picked from the file directory and be sent to the administrator via email.