Skip to Content
Author's profile photo Vikas Kumar Yadav

Enable Logging to troubleshoot Errors on SAP BusinessObjects mobile server

This blog discusses about how to enable tracing for SAP BusinessObjects mobile server for troubleshooting issues with the SAP BusinessObjects Mobile App.

Errors encountered on the SAP BusinessObjects Mobile App may not always be App issues and would require further logging on the mobile server to troubleshoot and share logs for deeper analysis.

To set log levels for the Mobile server component, you need to create three environment variables in the system where Mobile Server is deployed.

  • BO_TRACE_LOGDIR: Specifies the path to the folder where logs are generated.
  • BO_TRACE_CONFIGFILE: Specifies the path to BO_trace.ini.
  • BO_TRACE_CONFIGDIR: Specifies the path to the folder where BO_trace.ini is located.

BO_trace.ini is the configuration file where multiple log levels can be set. This file is available in the location like for example tomcat ..webapps\MobileBIService\WEB-INF\conf. There are different log level types: trace_none, trace_debug, trace_path, trace_information and trace_error.

The following table describes the logging level importance in decreasing order of detail:

Severity Configuration Value
NONE trace_none
DEBUG trace_debug
PATH trace_path
INFO trace_information
ERROR trace_ error

To set the log level, perform the following steps:

  • Open the BO_Trace.ini file for editing.
  • Set the required logging level for each unit as above.

Set dedicated folder for server logs

By default, the path to BO_trace file location is accessed from BO_TRACE_CONFIGFILE.

However, It can also be configured in web.xml by specifying a new context parameter “mobi.trace” and specifying the path value “/WEB-INF/conf/BO_Trace.ini”.

Sample BO_trace.ini

  • sap_trace_level = trace_none; // Developer log information
  • sap_log_level = log_none; // Administrator log information
  • size = 1000; // Size of log file in KB
  • keep = false; // Retain the log file

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo ROBERTO FRACCAPANI

      HI Vikas,

      are you aware of any issue with mobile bi app on ios9?

      because we are facing an issue with a customized version of mobile bi( only few graphical adjustment) .


      THanks in advance

      roberto fraccapani SAP

      Author's profile photo Vikas Kumar Yadav
      Vikas Kumar Yadav
      Blog Post Author

      Hi Roberto,

      Are you using SSL for communication if yes then IOS 9 onward apple is mandating that communication be encrypted using TLS 1.2 and SSL setups should be upgraded to TLS 1.2.

      Please refer this link iOS 9.0.

      I am quoting the section for quick reference.

      App Transport Security

      App Transport Security (ATS) enforces best practices in the secure connections between an app and its back end. ATS prevents accidental disclosure, provides secure default behavior, and is easy to adopt; it is also on by default in iOS 9 and OS X v10.11. You should adopt ATS as soon as possible, regardless of whether you’re creating a new app or updating an existing one.

      If you’re developing a new app, you should use HTTPS exclusively. If you have an existing app, you should use HTTPS as much as you can right now, and create a plan for migrating the rest of your app as soon as possible. In addition, your communication through higher-level APIs needs to be encrypted using TLS version 1.2 with forward secrecy. If you try to make a connection that doesn't follow this requirement, an error is thrown. If your app needs to make a request to an insecure domain, you have to specify this domain in your app's Info.plist file.