Step5: Configuring Request-Reply
Output of above message mapping acts as an input to the on premise webservice. Request-Reply step uses receiver soap adapter to post data to on premise synchronous web service and the response will send back to S4Hana cloud by ODATA API call.
Due to sensitive data of customer, this service restricted to the customer intranet with in the customer landscape.
In order to integrate on-cloud and on-premise systems, as per SAP best practise we are using SAP Cloud connector. Please refer the above new architecture screen shot for more details.
Receiver SOAP Adapter Configuration:
SAP Cloud connector Configuration:
SAP Cloud connector acts as a reverse proxy and firewall to backend or on-premise systems not required to open. No additional licensing required. It comes under SAP CPI licensing. In this case, SAP CC installed in customer data centre and firewall open between SAP CPI and SAP CC.
This blog does not cover the details of SAP Cloud connector installation and configuration. Please refer scn blogs and articles
Below is the screen shot of the SAP Cloud connector configurations successfully connected to HCP subaccount. Please provide proxy settings if required, dedicated s-user and Location ID.
As we are integrating on-cloud to on-premise integration, click on + icon and add the system mapping as per the below screen shot. Follow the wizard process.If we are not sure about the resources path and sub-paths use ‘/’ as per below screen which will allow to access all the resources
Connecting SAP Cloud connector to subaccount can monitor from the SAP Cloud Platform cockpit.
Log into cloud platform cockpit and under connectivity—>Cloud connectors you can see the status of cloud connector and its resources configured in cloud connector
Step6: Response Message Mapping from On-premise system to S4Hana Cloud
Response from on premise webservice mapped to the custom ODATA API in order to track the status of the customer data send to on premise system from S4Hana cloud
Step7: Configuring Receiver ODATA adapter
Step8: Exception Sub process
Exception sub process is for the error handling in the Integration Process. This sub process call the local integration process through process call to trigger an alert or email to the support team
Step9 to 11: Local Integration Process
From steps 9 to 11. Please refer below blog to trigger an email
For the comfort of the readers,this blog is split into 3 parts.Monitoring the end-to-end process is published in Part-3.Please refer below link
Happy Learning !!!