Symptom
When integrating SAP Analytics Cloud (SAC) as a source connection to SAP Datasphere, the connection type Cloud Data Integration requests a Data Provisioning Agent (DP Agent) for Remote Tables.
Using the ECS based DPAgent causes the connection to be hanging after "Validate".
Environment
SAP Datasphere
SAP Analytics Cloud
Cause
DPAgent in ECS infrastructure cannot reach SAC tenant.
Using a DB Analysis User, under folder "Database Diagnostic Files" -> File "indexserver", there will be details about the communication failure, for instance:
[4006]\{263317\}[1057/-1]<> 20XX-XX-XX XX:XX:XX.XXXXXX e DPAdapterManager AdapterManager.cpp(04579) : ::sendMessage: Invalid odata connection! Getting odata metadata failed because of org.apache.olingo.client.core.http.OAuth2Exception: Failed to fetch OAuth2 token! Connect to SAC_AUTHENTICATION_URL:443 [SAC_AUTHENTICATION_URL/X.X.X.X (SAC IP), SAC_AUTHENTICATION_URL/X.X.X.X, SAC_AUTHENTICATION_URL/X.X.X.X] failed: connect timed out (local port XXXX to address X.X.X.X (hec_ECS_INFO), remote port 443 to address X.X.X.X (ECS_INFO))
[4006]\{263317\}[1057/-1]<> 20XX-XX-XX XX:XX:XX.XXXXXX e FedTrace DPAdapterAccess.cpp(02484) : DPAdapterAccess::BrowseMetadata: failed with error: Invalid odata connection! Getting odata metadata failed because of org.apache.olingo.client.core.http.OAuth2Exception: Failed to fetch OAuth2 token! Connect to SAC_AUTHENTICATION_URL:443 [SAC_AUTHENTICATION_URL/X.X.X.X, SAC_AUTHENTICATION_URL/X.X.X.X, SAC_AUTHENTICATION_URL/X.X.X.X] failed: connect timed out (local port XXXX to address X.X.X.X (hec_ECS_INFO), remote port 443 to address X.X.X.X (ECS_INFO))
Resolution
Raise a Service Request ticket for ECS to fix this communication.
Possible fix to be applied by ECS:
DP agent registration was requested as "Connect to SAP Datasphere via JDBC". Hence the proxy and port details were chosen for the below values.
jdbc.proxyHost=proxy
jdbc.proxyHttp=true
jdbc.proxyPort=<insert here valid port number, e.g. 3128>
But to connect to SAC via DP agent, it does not happen via jdbc.
Hence apply proxy, proxytype and port details as below parameters in DP Agent configuration, then restart the agent.
proxyHost=proxy
proxyPort=<insert here valid port number, e.g. 3128>
proxyType=https
Keywords
KBA , DS-DI-CON , Connections , Known Error