There are many documents and posts on how to setup up and configurate the communication between ERP and SAP Cloud for Customers using HANA Cloud Integration, but there is a lack of documentation on how to test it.
The incoming connection from SAP Cloud for Customers to ERP is more complex than the outgoing connection from ERP to C4C (E2E connectivity test from ERP to C4C via HCI), as there is the Reverse Proxy (SAP Webdispatcher) as an additional component involved.
A connection test from C4C to ERP can be really helpful to find and identify problems. So the communication can be tested until it finally works.
E2E communication test from C4C to ERP via HCI and Webdispatcher
How does it work?
C4C provides an option to do an end to end connection test. The test tries to connect to HCI and calls ‘Check connectivity to SAP Business Suite’ which tests the connection to the ERP backend.
There are several ways how to open the connection test, this is one way:
Open ‘Report for On-Premise Integration’ from (BETA) Administration tab
Leave everything blank and click on ‘Test’Connection’
If you followed the configuration guide you’ll have defined already a communication system and communication arrangement.
So choose your comunication system (= target ERP) and fill out the other fields relevant for the connection to HCI.
The client number depends on your ERP system.
TCP Port ID is the HCI inbound port.
Host Name should be your HCI host.
Make sure ‘Business ByDesign System Key Pair’ is downloaded and used in HCI configuration.
Start the connection test
It’s important to scroll down to see if the test really was successful.
In this case connection to HCI and from there to ERP works. 🙂
Let’s have a look at the HCI monitor:
This is the message log from ‘Check connectivity to SAP Business Suite’ which was triggered from our connection test in the C4C system.
Here you can see that the connection from HCI to ERP backend was ok. In fact the used destination URL host from HCI to ERP is our SAP Webdispatcher, which is configured to forward messages to our ERP.
No message log entry at HCI monitor:
(= means connection problem from C4C to HCI)
– check connection test errors
– check created communication system
– check communication arragements
– check requirements for SSL connection between C4C and HCI (downloaded Business ByDesign System Key Pair should be used in HCI configuration)
– check ‘Check connectivity to SAP Business Suite’ configuration on HCI system
Failed message log entry at HCI monitor:
(= means connection problem from HCI to Webdispatcher or ERP )
– check webdispatcher availability from internet
– check webdispatcher configuration and logs
– check ERP ICM logs and SRUTIL
– check requirements for SSL connection between HCI and Webdispatcher
– check requirements for (SSL) connection between Webdispatcher and ERP
– check SOAMANAGER for connectivity check webservice
– check if communication user is set up
– check certificate to communication user mapping
Communication system definition
Important: Hostname has do be your HCI host.
Active communication arragement for ‘Connectivity check with SAP Business Suite’
Here you can also test the connection but only to HCI. If you get a 405 error the test was successful. 😉
‘Check connectivity to SAP Business Suite’ configuration
COD: This is the place where you need the previously mentioned ‘Business ByDesign System Key Pair’ from C4C.
ERP: Enter SAP client and your webdispatcher host and port.
Profile entries to terminate incoming HTTPS and forward it to ERP with HTTPS:
wdisp/system_1 = SID=<ERP_SID>, MSHOST=<ERP_MS_HOST>, MSPORT=<xxxx>, SRCSRV=*:37287
icm/server_port_1 = PROT=HTTPS,PORT=32287,TIMEOUT=300,PROCTIMEOUT=180
wdisp/ssl_encrypt = 1
wdisp/ssl_auth = 2
wdisp/ssl_cred = /usr/sap/<SID>/W00/sec/SAPSSLC.pse
icm/HTTPS/verify_client = 2
icm/HTTPS/forward_ccert_as_header = true
In this case port 37287 is the public https port of the webdispatcher for access from the internet.
Your firewall has to allow the access also. 😉
Instance profile parameters for forwarded https traffic from webdispatcher
icm/HTTPS/trust_client_with_issuer = CN=<check webdispatcher certificate for issuer CN>, *
icm/HTTPS/trust_client_with_subject = CN=<check webdispatcher certificate for subject CN>, *
icm/HTTPS/verify_client = 1
icm/accept_forwarded_cert_via_http = TRUE
Webservice for connection test has to be activated
Enter transaction SOAMANAGER
Open ‘Simplified Web Service Configuration’ and search cod_connectivity_provider
Allow authorisation through certificate & save.
Certificate to ERP user mapping
Add your HCI certificate and map it to your dedicated user for HCI/C4C communication
This makes authorisation though certificate possible. In order to work your webdispatcher has to forward the client certificate from HCI to ERP.