Troubleshooting Import Data Connections to On-Premise Data Sources

You will have to work with your SAP system administrator or network administrator when troubleshooting SAP BPT cloud connector for connections to on-premise data sources.

Import data connections from SAP Analytics Cloud to on-premise systems all leverage the SAP BTP cloud connector.

Basic logging is enabled in SAP BTP cloud connector by default, however, if there are problems with connecting to on-premise data sources when importing data, then detailed tracing logs may need to be enabled on the SAP BTP cloud connector. These logs can be sent to SAP Support for analysis.

There are several types of traces available for the SAP BTP cloud connector but the ones that are useful for troubleshooting SAP Analytics Cloud connection issues include:

• CPIC Trace Level: cpic_<xxxx>_trace.log

  Allows you to set the level between 0 and 3 and provides traces for the CPIC-based RFC communication with ABAP systems.

• Payload Trace: traffic_trace_<account id>_on_<landscapehost>.trc

  When activated, all the HTTP and RFC traffic content crossing the tunnel for that subaccount going through this SAP BTP cloud connector is traced. The payload trace is subaccount-specific, not global as other logger settings.

• TLS Trace: Helpful to analyze TLS handshake failures from the SAP BTP cloud connector to cloud or from the SAP BTP cloud connector to back-end. It should be turned off again as soon as the issue has been reproduced and recorded in the traces.
• Localhost Access Log: localhost_http_access<date>.log

  This log traces the HTTP/HTTPS traffic between the browser and server triggered by each action you take within a web application.

For more information on how to enable and analyze SAP BTP cloud connector traces, go to: How to Evaluate SAP Cloud Connector Logs and Traces.

You will have to work with your SAP system administrator or network administrator when troubleshooting the SAP Analytics Cloud agent for connections to on-premise data sources.

They can work with you if you experience issues with data import from your on-premise data sources that use the SAP Analytics Cloud agent. They will make sure that it is properly deployed and configured on an Apache Tomcat instance and trace the SAP Analytics Cloud agent to resolve common connection issues.

To verify the version of the SAP Analytics Cloud agent that has been deployed:

1. Access localhost:8080/C4A_AGENT/deploymentInfo on the machine where the SAP Analytics Cloud agent is deployed.
2. When prompted for credentials, specify the User Name and Password provided in the Setup-Guide.html. This file is located in the C:\Program Files\SAP\SACAgentKit folder.
3. Make note of the version of the agent.

To resolve certain connectivity issues, your SAP system administrator may be required to deploy a newer version of the SAP Analytics Cloud agent. If that's the case, they can download the newer version of the SAP Analytics Cloud Agent Simple Deployment Kit and run the installation again or use the procedure below to update the SAP Analytics Cloud agent.

Tracing of the SAP Analytics Cloud agent is also useful to debug connectivity issues. To enable debug in Tomcat, the ${catalina.base}/conf/logging.properties file located in the tomcat\conf directory needs to be modified and set to $catalina.org.apache.juli.FileHandler.level = FINE.

1. Reverse the deployment of the existing SAP Analytics Cloud agent from Tomcat:
   1. Stop Tomcat.
   2. In the Apache Tomcat installation folder, delete \webapps\C4A_AGENT\ and any subfolders and files.
   3. Restart Tomcat.
2. Download the newest version of the SAP Analytics Cloud agent.
3. Unzip the downloaded file and rename the .war file to C4A_AGENT.war.
4. Extract the package and copy the file C4A_AGENT.war to the Tomcat directory.
5. Restart the Tomcat application server for the settings to take effect. The SAP Analytics Cloud agent will automatically deploy when Tomcat is restarted.

Tracing the SAP Analytics Cloud agent can help troubleshoot various issues, including where data import jobs fail due to issues with Java Heap Memory.

The trace logs are created in the tomcat\logs folder.

The trace level can be set to:

• SEVERE
• WARNING
• INFO
• CONFIG
• FINE
• FINER
• FINEST
• ALL

Two of the common errors that are returned in the trace logs are:

1. SERVER_ERROR_500: An error occurred in Connection Server service: GC overhead limit exceeded (max heap: #### MB)
2. An internal server error occurred in SAP Analytics cloud agent: The result set is too large; data retrieval restricted by configuration.

To resolve these types of errors, increase the -Xmx setting in the Tomcat Java configuration.