Solution : https://service.sap.com/sap/support/notes/1760422 (SAP Service marketplace login required)
Summary :
This SAP Note discusses the deployment complexities of HTML5 applications in ABAP systems needing connectivity to Web Services via SAP NetWeaver Gateway configured as a Hub. The central challenge is the browser's Same-Origin Policy which demands a Reverse Proxy, like the SAP Web Dispatcher, to manage URL-based routing/rewriting effectively. Ideally, placing the Gateway Server within the same NW AS ABAP system as the application server is recommended, yet a separate Gateway Hub might be chosen. This setup can create issues with system-dependent cookies, same-origin policy, routing conflicts, and multi-destination support, necessitating specific configurations to route HTTP requests correctly and manage cookies and service deployments effectively. Solutions and workarounds for these challenges are currently under development, with updates expected to be documented soon.
Key words :
gateway system wdisp/system_conflict_resolution=1 wdisp/system_0 = sid=gm2, srcurl=/sap/opu/odata/ wdisp/system_1 = sid=lrm, configuration wdisp/system_conflict_resolution=1 wdisp/system_0 = sid=gm2, prerequisites sap web dispatchersap netweaver gateway server deployed, application backend system odata service configuration, application backend / gateway system alternative solution, preferred solution define virtual hosts, /sap/opu/odata/<servicename>, srcurl=/sap/ advantages configuration, odata service implementations reside
Related Notes :
| 1759682 | UI Add-On for SAP NetWeaver: Central Note |