Log Files

SAP Mobile Platform log files provide a source of troubleshooting information. Log file information is aggregated and displayed in the SAP Control Center administrative console.

Accessing server logs

The server log records all system events as per the log level configuration for individual sub-components. For detailed diagnostics, you can configure individual sub-system's log level to DEBUG or TRACE level, and the messages recorded in the server log can help identify the problem. It is not recommended to leave sub-system log levels to those considering the performance impact and growth of the log file when large number of users may be accessing the system. Server log is separate for each server.

Server log settings are controlled from SAP Control Center. Server log configuration settings changes on the primary server are propagated to other nodes within one minute, and do not require a cluster changing action.

In SAP Control Center, navigate to Servers > ServerName > Log node > General tab.

You can also view the server log from the command line using a text editor or any other third-party log viewing tool. (SAP Control Center helps to view the server log remotely without needing access to the server's file system).
  • The main server log file is SMP_HOME\Servers\UnwiredServer\logs\hostname-server.log.
  • The incoming HTTP requests log (for Data Change Notification, and others) is in the hostname >-http.log file. You may also see some additional folders which contain log files produced by the internal modules of the Messaging Server. The key folders are JMSBridge and SUPBridge. The messages recorded in those files are controlled by the log level setting of the MSG sub-component of the SAP Mobile Server logging system.
These key sub-systems can help troubleshoot issues:
  • Data Services – consider modifying this sub-system log level if you are trying to diagnose issues with backend EIS interaction, caching, and Data Change Notification.
  • MMS – consider modifying this sub-system log level if you are trying to diagnose issues with client interaction, message-based synchronization application activities such as subscription command processing, and data import messages, and replication synchronization application activities such as those during upload and download phases of the synchronization, data change notification processing, and background tasks such as cache refresh.
  • MSG – consider modifying this sub-system if you are need to look at the individual messages being exchanged between one or more messaging synchronization application clients and server.

Accessing domain logs

The domain log shows data only if domain logging is enabled for that domain, and one of the packages in the domain has package-level logging enabled. Domain log data is automatically purged based on the domain log setting for the domain. Domain log is a cluster-wide logical view of the activities and errors.

Navigate to Domains > DomainName > Log node > General tab.

Accessing client logs

If client logging is enabled through the client object API, the client logs provide critical information about the application running on the device and its operational state. The client application information is uploaded from the device to SAP Mobile Server, where it is visible using SAP Control Center.

In the left navigation pane, expand the Packages folder and select the package you want to investigate, then in the right pane, select the Client Log tab.

Parent topic: Collecting Information
Related concepts
Mobile Application Project and Deployment Information
Related tasks
Finding the SAP Mobile Server Version
Reviewing the Pending Items Count for Messaging Applications
Related reference
Viewing Messages in SAP Control Center