Skip to Content

SAP cloud connector and reverse proxy : Can they both be used in one scenario?

Dec 04, 2017 at 10:35 PM


avatar image

Hi Experts,

I am configuring standard employee and Org replication package and client has introduced web dispatcher to act as median between On-Prem and SCPI. My question is if I can use web dispatcher as reverse/forward proxy to push messages from ERP to HCI and cloud connector for the inbound interface to On-prem? Can they be used together or is it one or the other?

Also, when I try to use SCC for pushing messages from HCI to ERP, I get "

HTTP response '502: Host not found' when communicating with http://cloudconnectorpath:44300/sap/bc/srt/scs/sap/eemasterdataandorgassbndlreq?sap-client=100&MessageId=2B6C1566-4C31-44A6-82B1-4A688B41656F.

I have configured old package to replicate employee from SuccessFactors as well and that works with cloud connector configurations but I am baffled by this whole proxy and SCC situation altogether.

Any pointers on this would be greatly appreciated.



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

1 Answer

Muni M Dec 05, 2017 at 05:07 AM

web dispatcher and cloud connector both are used to expose your on premise systems to outside.I have not tried using both to check it works or not.

request will be sent to your on premise based on the host name mapping.let us say, your ECC is host is

and you defined exposed host as in scc and in webdisptacher. based on what url you are using in channel will determine through which the request will be received.

But you dont need both. either scc or webdispatcher should be enough. SCC is the newly added by sap to expose the on prem systems. better go with scc.

these all come into picture when you are using inbound scenario.

For outbound you dont need reverse/forward proxy. ECC can directly call HCI url without any proxy.

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

Hi Muni,

thank you for your answers. With latest version of standard integration, query is in On-Prem now so first call is outbound and client doesn't want direct call from ECC to HCI hence web dispatcher is being used and I can see messages coming over to HCI using that proxy but fails to identify SCC end point as part of inbound interface.