CIG support team does not provide support integrations which use web dispatcher

[former_member82170]

2023-06-26-11-55-12-search.png

Hello,

We are having issues integrating CIG --> SAP Cloud Connector --> SAP Webdispatcher --> ERP Backend System, so created a ticket with SAP and SAP is saying they do not support this scenario!! is this true? we are using the same scenario for BTP/Success Factors and it works seamlessly and no issues at all!

if web dispatcher is not supported, how do we load balance between the application servers? as we got 7 application servers to balance the load! , please suggest

[AndreMiranda]

I've encountered numerous issues with the Web Dispatcher with Cloud Connector, and all of them were related to Web Dispatcher configurations. In most cases, these problems were resolved by adjusting the 'wdisp/system_0' parameter and removing the 'SRCVHOST'.

[Jowhara]

did you find a solution to this issue ?

[AndreMiranda]

The SAP Managed Gateway (also known as CIG) does support Web Dispatcher, but the issues typically arise on the Web Dispatcher side. Please check the link below where I outlined some potential solutions to resolve your issue.

You can refer to this link: https://community.sap.com/t5/technology-q-a/sap-cig-integration-with-web-dispatcher-not-working/qaq-....

[former_member82170]

Yeah, I tried webdispatcher host, but it is not working as Ariba service does not recognize webdispatcher alias name.

[AndreMiranda]

I think it might be helpful to consider this issue from a different perspective.

With CIG, the cloud connector is utilized solely for sending messages to ERP. In this context, there's no necessity for Ariba/CIG webservices to initiate calls to the webdispatcher; in fact, the situation is reversed, with the webdispatcher making calls to the ERP and its associated webservices.

Given that we don't employ any CIG webservice to initiate calls to the Cloud Connector, the statement that Ariba/CIG webservices cannot recognize the webdispatcher seems to not make sense.

Also check if there is an alias when the webdispatcher is calling the services; these alias needs to be recognized by the ERP.

[former_member82170]

We are not using CPI, instead we are using SAP CIG to SAP Cloud Connector to SAP ERP

[Ryan-Crosby]

Then you would need to update CIG so it has knowledge of the WD host, or somehow make use of the virtual hosts option.

[former_member82170]

Sorry for creating multiple threads.

I did trace end to end and calls are coming to SAP backend system and terminates with error code 403 service not available, if I use same link with any application server it works, ARIBA SOAMANAGER web services does not aware of web dispatcher hostname.

Currently we have BTP/Success factors integration between SAP Cloud Connector and SAP ERP which is working fine and we are using same cloud connector and same ERP system, why it does not work!

[Ryan-Crosby]

You will need to consider an integration flow in CPI to wrap the integration point because another platform cannot know the DNS name housed in an internal network elsewhere. Create an iFlow and then place that endpoint in your CIG configuration.

[AndreMiranda]

Please do not create multiple threads for the same topic/issue; I have already provided guidance to you about this one.

The SAP CIG team won't support issues in Webdispatcher as this is way beyond their scope; When you don't have Webdispatcher it works fine, and when you add it as an additional layer for load balance is not working.

That said, it is clear the issue is with the Webdispatcher configuration, which must be tweaked to work for Cloud Connector to On-Premise ERP, and this must be solved by the customer or consulting team.

Check my suggestion of reviewing the 'wdisp/system_0' parameter and removing the 'SRCVHOST'.