Symptom
- In SAP Analytics Cloud (SAC), you can create import connections to data source systems to allow data acquisition by SAC, where Data is imported (copied) to SAC, and changes made to the data in the source system do not affect the imported data (in SAC).
- SAP Analytics Cloud requires the SAP Analytics Cloud Agent and the SAP Cloud Connector installed within your network to access resources / servers located in your network.
Note: The SAP Analytics Cloud agent is required for all import data connections except SAP BPC NW, SAP BPC for BW/4HANA, OData Services and SAP S/4HANA. - As of SAP Analytics Cloud version 2019.15, setting up Data Acquisition between SAC and the SAP Cloud Connector is now fully self service, which can be completed by following the steps described in the following resources:
- SAP KBA 2397165 - How do I configure SAP HANA Cloud Connector (HCC) and Agent with SAP Analytics Cloud?
- SAP Blog Enable SAP Analytics Cloud for data acquisition from on-premise systems
- SAP Help Configuring SAP Analytics Cloud Agent
- To troubleshoot any issue in this scenario (setting-up data acquisition & configuring SAC Agent), this article will help you understand:
- Which trace is necessary for investigation and how to collect?
- How to analyze important and useful information from the collected trace files?
- What will be the expected result in trace files for successful case?
- What will be observed in trace file for typical issues?
Images and data taken from SAP internal systems and demo environments. Any similarity to production data is purely coincidental.
Environment
- SAP Analytics Cloud (Enterprise)
- SAP Cloud Connector (SCC)
- SAP Analytics Cloud Agent (SAC Agent)
Resolution
Prerequisites
Please make sure you have followed all the steps to finish the configurations.
- The cloud connector must be installed. For more information, see Installing the SAPCP Cloud Connector.
- The SAP Analytics Cloud agent must be installed. For more information, see Installing SAP Analytics Cloud Agent.
- The cloud connector must be configured. For more information, see Configuring the SAPCP Cloud Connector.
- The SAP Analytics Cloud agent must be configured in SAP Analytics Cloud for more information, see Configuring SAP Analytics Cloud Agent.
Trace Type & collection methods
Trace Type | Description | File extension/name/path | Collection Method | Analysis Tool |
HAR trace | Chrome developer tools network trace | .har | 2280022 - How to collect a HTTP archive (HAR) file (Chrome developer tools network trace) in SAP Analytics Cloud | Chrome developer tool/Http Watch |
Console log | Chrome developer tools console log | .log | Notepad/Notepad++ | |
ljs trace
|
| scc_core.trc | 2452568 - Log and Trace files for SAP Cloud Connector | |
traffic trace
|
| traffic_trace_<account id>_on_<landscapehost>.trc | ||
tomcat log
|
|
<Tomcat_Install_Dir>/logs/tomcat-stderr.<DATE>.log <Tomcat_Install_Dir>/logs/catalina.<DATE>.log |
|
Steps to collect essential traces
- Enable SCC Debug-level trace & Payload trace by following KBA 2452568 - Log and Trace files for SAP Cloud Connector
- Enable Tomcat high level traces following either one of methods above and restart Tomcat after applying the changes.
- Reproduce the issue in SAC (i.e., Go to System > Administration > Data Source Configuration > Check Configuration on the selected Location).
=> At the same time, collect the HAR trace as well as the console log by following KBA 2280022.
Observation in traces of Successful Workflow
HAR file:
Scenario | Request URL | Method | Payload | Response |
Start to Add/Edit location | https://<SAC Tenant URL> /sap/fpa/services/rest/v1/locations/%7BlocationId%7D?&tenant=<...> | Get | All the locations that have been added in the current SAC tenant. | |
Click Create button after adding or editing location | https://<SAC Tenant URL>/sap/fpa/services/rest/v1/locations/<LocationID>?&tenant=<...> Note: If it is the default location, <Location ID> is something like ONPREMDEFAULT-XXXXXXXXXXXX | Put | Detailed information of Cloud Agent | {"message":"","stack":"","errorDetails":[],"status":200,"bUIMsg":false,"bWarning":false} |
Click Create button after adding or editing location OR |
https://<SAC Tenant URL> /sap/fpa/services/rest/v1/locations/<LocationID> /agent/version?&tenant=<...> | Get | {"minSupportedVersion":"1.0.75", "currentVersion":"1.0.257"} |
SCC scc_core.trc:
Observation in trace file | Comment |
| SCC received the requests from SAC and started to build a connection with BTP Connectivity Service. |
| SCC tried to connect to Cloud Agent now. |
| SCC sent HTTP request to http://<CloudAgentInternalHost>:<Port>/C4A_AGENT/deploymentInfo |
| Mapping Virtual host with Internal host. |
| This is a general message, not indicated an issue in this scenario. |
| After test, the connection was closed. |
SCC Traffic trace (traffic_trace_<account id>_on_<landscapehost>.trc) :
- HTTP Request crossing the tunnel for that subaccount going through this Cloud Connecton to access SAC agent
- GET http://<CloudAgentInternalHost>:<Port> /C4A_AGENT/deploymentInfo
- Authorization: Basic <base64encoded-username-password>
- Response returned from SAC agent
- HTTP/1.1 200
- {"minSupportedVersion":"1.0.75", "currentVersion":"1.0.257"}
- Example:
Typical issues/errors
Observation in HAR file:
Issue | Observation in trace | Possible Cause | Resolution |
Error "Please verify the SAP Cloud Platform Cloud Connector connection status under the SAP Cloud Platform account that is linked to your SAP Analytics Cloud system; and check the Cloud Connector logs to see if the network firewall is blocking access to the Cloud Platform. If connected, please contact SAP Support regarding backend connectivity issue. HTTP Status: 503, Action: Check version" when
|
|
Either SCC, Cloud Agent or both are not configured. |
Please make sure all the Prerequisites have been configured. |
Note: You may need to look into other traces as below to help you identify the issue further.
Observation in SCC scc_core.trc
Observation in trace file | Possible Solution |
| 2508215 - "Failed to call SAP Analytics Cloud agent..." error in SAP Analytics Cloud after checking the configuration in datasource configuration |
|
3084008 - SAP Analytics Cloud cannot connect to SAC agent |
Observation in SCC Traffic trace(traffic_trace_<account id>_on_<landscapehost>.trc) :
Observation in trace file | Possible Solution |
|
It indicates the username and password maintained in SAC when adding the location is incorrect comparing with the ones maintained is tomcat-user.xml. |
|
It indicates the role Services is not assigned to the tomcat user correctly. Please check the configurations in the tomcat-user.xml file. |
Observation in Tomcat logs:
Observation in trace file | Possible Solution |
|
In these cases, please check if Tomcat is using the correct JVM. Please refer the KBAs below for further information and solutions.
|
See Also
- Data Connectivity | SAP Analytics Cloud | SAP Community
- SAP Analytics Cloud – Authentication and Data Connectivity | openSAP (Course)
- 2569847 - Where can you find SAC user assistance (help) to use, configure, and operate it more effectively?
- Have a question? Ask it here and let our amazing SAP community help! Or reply and share your knowledge!
- 2487011 - What information do I need to provide when opening a case for SAP Analytics Cloud?
- 2511489 - Troubleshooting performance issues in SAP Analytics Cloud
- Search for SAP Analytics Cloud content using Google or Bing:
- https://www.google.com/search?q=site%3Ahttps%3A%2F%2Fuserapps.support.sap.com+SAP+Analytics+Cloud
- https://www.bing.com/search?q=site%3Ahttps%3A%2F%2Fuserapps.support.sap.com+SAP+Analytics+Cloud
- Note: Add relevant text or warning/error messages to the text search field to filter results.
- SAP Analytics Cloud Connection Guide
- Getting Started with SAP Analytics Cloud Expert Community page
- SAP Analytics Cloud Get More Help and SAP Support
- Need More Help? Contact Support or visit the solution finder today!
Your feedback is important to help us improve our knowledge base.
Keywords
SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Connection, Sac, Connector, Live, Acquisition, Up, Set, setup, Model, BW, Connect, Story, Tenant, Import, Failed, Using, Working, SAML, SSO, sapanalyticscloud, sap analytical cloud, sap analytical cloud, SAC, sap analyst cloud, connected, failure, stopped, sap analyst cloud,