Start of Content Area

Procedure documentation Activating Tracing on the Mobile Device Locate the document in its SAP Library structure

Use

If problems occur on the mobile device you can activate the tracing function. A log file is then created that contains detailed information on the program flow. You can use this file to analyze the errors that have occurred.

A transaction has been provided on the server to activate the function on the mobile device.

Note

As an alternative to the server setting described here, you can also ask the user to activate the tracing function himself or herself on the mobile device (see Setting the Trace for Error Correction).

After you have activated the tracing function, the systems records the errors and events in the trace file. You can determine the level of detail the trace function is to use by setting the trace level.

Note

If system performance problems arise in relation to SAP MI, in exceptional cases you can also briefly measure the system performance (for more information, see Measuring System Performance on the Mobile Device).

Procedure

...

       1.      Start the transaction ME_RTRACE on the server.

       2.      Enter the device ID, determine the required settings, and save your entries.

Field

Description

Trace Status

Switch tracing on here.

You can also determine that the tracing function be switched off for the next synchronization process and that the trace file be sent to the server. If you do not switch this option on, the user has to send the file manually via SAP MI.

Default: Activated

Trace Level

Determine the level of the trace. Choose a high value to receive as much information as possible (for example, 1000)

Possible values:

10 (System-critical errors only)

50 (Errors)

60 (Warnings)

70 (Information)

80 (Execution paths)

90 (Debugging)

1000 (All)

Default value: 50

Maximum Size [KB]

Specify a maximum size in KB.

If the file size exceeds the given value, the system creates a backup file with the past traces and starts a new trace file. The old backup file is overwritten.

Possible values:

     All positive integers corresponding to a 32-bit number.

     -1 (no size restriction)

Default: The value defined in the client (default 200)

Extend Existing Trace File

Only activate this option if you want to extend the existing trace file.

If you only want to analyze the current problems, do not activate this option.

Result

The system records the events on the mobile device and writes them to the file trace.txt. They are then saved under <installation directory>\log on the mobile device.

Note

You can change the path and file name using the file MobileEngine.config (see Parameters for Tracing).

If it is possible to synchronize with the mobile device, the trace file is sent to the server with the next synchronization (either automatically or manually using the corresponding function in SAP MI). You can call it using the CCMS or open it and analyze it with a text editor (see Checking the Trace and Log in CCMS and Analysis of the Trace File).

 

End of Content Area