Skip to Content
0

SAP Web Dispatcher fowarding instead of proxying behind Apache reverse proxy

Feb 15, 2017 at 10:05 AM

120

avatar image

In this scenario traffic needs to go through server A (apache reverse proxy) and then through server B (the SAP WebDispatcher).

Server A = sap.company.com

Server B = webdisphostname.internal.systems.com

The problem is that https://sap.company.com/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html is being redirected to http://webdisphostname.internal.systems.com:8020/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html (AS ABAP and WDP running on same host).

Server A has no knowledge about the hostname of the application and the port (8020), so I think it must be a misconfig in the WDP.

Note that we want the end user only to see sap.company.com.

  • Is it required to set both the icm/host_name_full and 'HOST' of the icm/server_port_0 to sap.company.com?
  • Or only icm/host_name_full?
  • Or something else that can be required to change?

PS. There is no primary tag for SAP WebDispatcher?

10 |10000 characters needed characters left characters exceeded

Hi Pieter,

With respect to your tag question, no, there doesn't appear to be one for Web Dispatcher (I've looked previously for this), so I believe mostly these are currently falling under "SAP NetWeaver."

I notice that you used user tags to tag some individuals. Just so you know, that doesn't do anything; those people are not notified in any way that you did so.

Cheers,
Matt

0
* Please Login or Register to Answer, Follow or Comment.

0 Answers