Managing Application Logs and Traces

Set the verbosity for application and component logging, and the purge schedule for log and trace files. View all application logs or the subset of your choosing, and drill down to view detailed log and trace information if available.

Setting Log Levels

You can change the logging level for one or more logging components. For Agentry, you change the logging level at the application level. In a troubleshooting situation, you may want to increase the log level to capture more details.

Enabling Application Traces

Enable application traces for selected SAP Mobile Platform Server logging components.

Viewing Logs and Traces

View log and trace information to troubleshoot application problems. Use search criteria to find the log records and trace statements needed to diagnose a problem. Depending on what information is being captured, log and trace information can include entries from client logs, server logs, and application traces. For applications developed using SAP Mobile Platform SDK 3.0 SP04 or earlier, you cannot view client logs in the Logs & Traces View but can instead download and view a client log file in the Registrations view.

Using End-to-End Tracing to Troubleshoot and Diagnose Device Problems

Analyze end-to-end (E2E) tracing to troubleshoot client issues. E2E tracing sessions are conducted by administrators and device users. E2E trace information is recorded in a Business Transaction XML (BTX) file on the client, which is uploaded to the server, and then uploaded to SAP Solution Manager for analysis.

Purging Logs and Traces

Configure a scheduled purge of logs and traces stored in the SAP Mobile Platform Server database, or purge log and trace files immediately.