Skip to Content
0

Replicate Business Partners from C4C to ERP using HCI via Web Dispatcher

Feb 23, 2017 at 07:15 PM

509

avatar image

Dear Experts,

As the question itself would reveal that I am fairly new to HCI, so apologies if the problem is rather basic. But after searching the net for a significant amount of time, I thought I would rather post the question for your inputs.

We are implementing C4C for a certain customer and integrating it with ECC using HCI. Now I have done this before for another customer but the reverse proxy used was cloud connector. This time we are using a Web Dispatcher but struggling to send data out of HCI.

The reasons could be many including those in firewall or in Web Dispatcher itself. But before we go that far I want to ensure I have the settings in HCI IDOC Adapter right.

When we were using Cloud Connector, in IDOC Adapter Specific settings for data directed towards ERP, we used Address: 'http://<proxy_host_name>:<port>/sap/bc/srt/idoc?sap-client=xxx' and Proxy Type as 'On-Premise'. In the Cloud Connector we have set up the libk between proxy host and actual host and added the SICF nodes to be used. It worked just fine.

My question is, when we are using Web Dispatcher, what should ideally be configured in IDOC Adapter Specific settings?

Question 1: Should the Address only contain the Web Dispatcher URL followed by port or should it contain the SICF service details as well that we intend to trigger in ERP? (/sap/bc/srt/idoc0

Question 2: Should we use http:// or https:// when we are sending data to ERP with Web Dispatcher enroute?

Question 3: Should we use Proxy Type 'On-Premise' or 'Internet'?

I have tried a few options but the results haven't been favorable.

With https:// and 'Internet' (as in the screenshot below), we get ""SocketTimeoutException:Read timed out" error messages.

With http:// and 'On-Premise', we get a 'HTTP response '503: Service Unavailable' error message.

Any help or guidance would be massively appreciated.

Best Regards,

Sub

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Viktor Lazar
Feb 24, 2017 at 09:30 AM
0

Hi Sub,

in case you are connecting a backend system to HCI, but this is not publically available over the internet then you will need to use "On-Premise" proxy type in HCI receiver channel. But in this case you will have to use either SAP Cloud Connector or Web dispatcher as a reverse proxy.

I would say that the settings that you have when you receive HTTP 503 error back is ok. So using HTTP and "On-Premise" should work.
Now you should continue the investigation on the web dispatcher host. Look for traces and check if this WDP is trying to route the incoming message correctly. Check if you have on this host the called port number available, etc...
Also check if the call reached the called backend. You might see it in icm traces.

Best Regards,
Viktor

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Thanks Viktor. Really appreciate your help.

Now that I can be certain about the HCI Adapter configuration settings, I would investigate further with help of my colleagues on possible issues on the firewall or WDP.

Could you suggest if I need the "/sap/bc/srt/idoc?sap-client=xxx" suffix in the Address or should this be configured in the Web Dispatcher for all traffic coming in from HCI?

Best Regards,

Sub

0
Viktor Lazar
Feb 24, 2017 at 10:37 AM
0

Hi Sub,
yes, i think you will need to keep the called service endpoint URI "/sap/bc/srt/idoc?sap-client=xxx" in the Address field.
Also check in the called SAP system if this idoc service is activated in SICF transaction:

/sap/bc/srt/idoc

Best Regards,

Viktor

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Thanks Viktor.

The service is indeed active in SICF and I will now add the service endpoint to the Address and continue investigation on the WDP and Firewall. Many thanks again for you help. Once we eventually sort this out, I will keep the post updated with further details.

0