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.

1. In Management Cockpit, select  Logs  Logs & Traces .
2. Under Search Criteria, enter log search criteria:
   • For Application, select an application to view only logs or traces specific to that application, or select All.
   • For Component, select a server logging component to view only log messages and trace information specific to that component, or select All.
   • For Status, select a logging level to view only log messages and trace information of a specific type, or select All.

     Table 1: System Logging Components

     Component	Description
     Admin	Logs system messages related to SAP Mobile Platform administration.
     Agentry	Logs system message related to Agentry applications.
     Agentry user.*	Logs system messages related to Agentry application users.
     Agentry <app_ID>	Logs system messages related to the Agentry application.
     Agentry <app_ID>.BackEnd.*	Logs system messages related to the back-end data source connections, such as SQL or Java, for the Agentry application.
     Agentry <app_ID>.ThirdPartyPushServices	Logs system messages related to the back-end data source push service for the Agentry application.
     Agentry <app_ID>.WebSockets	Logs system messages related to server/client communication using WebSockets connection type for the Agentry application.
     Agentry <app_ID>.WebSockets.connection.*	Logs system messages related to server/client communication using WebSockets connection type for the Agentry application.
     B2C Application Services	Logs system messages related to the Business-to-Consumer services used for Mobiliser logs. Mobiliser must be enabled to set log levels.
     B2C Framework	Logs system messages related to the Business-to-Consumer framework used for Mobiliser logs. Mobiliser must be enabled to set log levels.
     Backend Request Header Trace	When the logging level is set to Debug, logs the backend request and response headers issued by SAP Mobile Platform. This log can be used to analyze communication issues between SAP Mobile Platform and back end systems, including push services. Note This log contains sensitive information such as passwords and should be used for technical analysis only.
     Backend Request Wire Trace	When the logging level is set to Debug, logs the backend request and response headers issued by SAP Mobile Platform, including the payload information (in binary or compressed format). This log can be used to analyze communication issues between SAP Mobile Platform and back end systems, including push services. Note This log contains sensitive information such as passwords and should be used for technical analysis only.
     Client Request Trace	When the logging level is set to Debug, logs the client request and response headers issued by SAP Mobile Platform. This log can be used to analyze communication issues between SAP Mobile Platform and clients. Note This log contains sensitive information such as passwords and should be used for technical analysis only.
     Cluster	Logs system message related to managing the cluster.
     Connectivity	Logs system messages related to all HTTP connections made by the server.
     Foundation	Logs system messages for core SAP Mobile Platform Server functionality.
     Hybrid Application Management	Logs system messages related to managing hybrid apps through Management Cockpit or the API, and client interactions for requesting and downloading updated hybrid apps.
     Integration Gateway	Logs server-side system messages for plug-ins integrated with SAP Mobile Platform Server, such as data sources (SAP and OData), and third-party systems and protocols (such as SOAP, JDBC, HANA Cloud, and NetWeaver PI).
     Offline	Logs system messages related to the offline OData service.
     Other	Controls all other loggers not covered here. This is implemented by having a single logger named ROOT in this component, setting the level of the root logger affects any logger that does not fall under one of the loggers have been assigned a level explicitly
     Proxy	Logs system messages related to any client-back end interactions using SAP Mobile Platform Server as a proxy (for example, OData requests).
     Push	Logs system messages related to push actions.
     Registration	Logs system messages related to application registration.
     Security	Logs system messages related to SAP Mobile Platform security.
     Serviceability	Logs system messages related to framework components such a security or Web services, plus messages that are related to JDK and the server's runtime environment.
     Statistics	Logs system messages related to usage statistics.

     Table 2: Logging Levels

     Log Level	Description
     Path	For tracing execution flow. Used, for example, in the context of entering and leaving a method, looping, and branching operations. (Not applicable to the offline logging component.)
     Debug	For debugging purposes, includes extensive and low-level information.
     Info	Informational text, used mostly for echoing what has been performed.
     Warn	The application can recover from the anomaly, and fulfill the task, but requires attention from the developer or operator.
     Error	The application can recover from the error, but cannot fulfill the task due to the error.
     Fatal	The application cannot recover from the error, and the severe situation causes fatal termination.

   • For Type, select a request type to view only log messages or trace information for that type of request, or select All.
   • For Time Frame, indicate a start and stop range.
   • For User Name, enter the name of a user to view only log messages and trace information for requests initiated by that user.
   • For No. of Entries, select the maximum number of log entries to be displayed. Limiting the number of entries displayed improves performance.
3. Click Search, to view the logs and traces that meet the search criteria:

   Column	Description
   Status	Log entry status, typically Error or Success.
   Registration ID	The unique connection identifier that makes the request to the server.
   User Name	The name of the user associated with the application ID.
   Created Time	The time and date stamp for the log entry.
   Type	The log type, such as application settings, deregistration, and so forth.
   View Trace	The link to detailed log and trace information associated with the execution request. Optionally, you can download a text file for further analysis.
   Application ID	Unique identifier for the application, in reverse domain notation. This is the application or bundled identifier that the application developer assigns or generates during application development. The administrator uses the application ID to register the application with the server, and the client application uses the application ID to send requests to the server.

4. (Optional) Select one or more rows and click Download to download a text version of the log file to the Downloads directory.
5. (Optional) Click the View Trace icon to view log messages and trace information.

   The Trace Logs Details window appears with log messages and trace information. Click Download to download a text file of the trace information to the Downloads directory.