Show TOC

Procedure documentationConfiguring Communication Channel between Clients and SAP Web Dispatcher

 

To facilitate communication between the browser and the different systems in the SAP Fiori system landscape, you use a reverse proxy to ensure queries from the browser are correctly directed to the appropriate system.

As SAP Fiori apps access multiple back-end systems but JavaScript code is constrained by the Same Origin Policy, all systems are exposed to the browser through the reverse proxy, which brings them into a common origin (combination of protocol, host name, and port).

Recommendation Recommendation

We recommend using SAP Web Dispatcher as the reverse proxy. The following describes the configuration of the SAP Web Dispatcher only. If you use any other reverse proxy, see the manufacturer’s documentation for more information.

If you use a reverse proxy other than SAP Web Dispatcher, you must ensure it is configured to preserve the “Host” header of the reverse proxy that is sent by the browser. If the reverse proxy overwrites or replaces the “Host” header, the back-end systems cannot generate correct absolute URLs. For this reason, SAP Web Dispatcher automatically preserves the host name; however, other reverse proxies may need to be configured to do so.

End of the recommendation.

Note Note

You can configure SAP Web Dispatcher to be able to handle a high load of incoming requests.

For more information, see the following documentation:

  • For SAP NetWeaver 7.31, see SAP Note 2007212Information published on SAP site.

  • For SAP NetWeaver 7.4, see SAP Help Portal at Start of the navigation path http://help.sap.com/nw_platformInformation published on SAP site Next navigation step Application Help Next navigation step Function-Oriented View Next navigation step Application Server Next navigation step Application Server Infrastructure Next navigation step Components of SAP NetWeaver Application Server Next navigation step SAP Web Dispatcher Next navigation step Administration of the SAP Web Dispatcher Next navigation step Configuring SAP Web Dispatcher for High System Load Due to Inbound Requests End of the navigation path.

End of the note.

Prerequisites

You have implemented SAP Web Dispatcher.

For more information, see Installation of SAP Web Dispatcher.

Procedure

Configure SAP Web Dispatcher to Support SSL

All communication to back-end systems should be handled using HTTPS requests and SAP Web Dispatcher itself should be called using only HTTPS.

  1. Open the Web Dispatcher profile sapwebdisp.pfl.

  2. To configure HTTPS settings, you can copy the following source code and adapt it to your business requirements:

    Syntax Syntax

    1. ssl/ssl_lib = <sapcrypto dll>
    2. ssl/server_pse = <pse>
    3. icm/HTTPS/verify_client = 0
    4. ssl/client_pse = <pse>
    5. wdisp/ssl_encrypt = 1
    6. wdisp/ssl_auth = 2
    7. wdisp/ssl_cred = <pse>
    8. icm/HTTPS/forward_ccert_as_header = true
    End of the code.

    For more information about the parameters, see:

    • For SAP NetWeaver 7.31: Start of the navigation path http://help.sap.com/nw731Information published on SAP site Next navigation step Application Help Next navigation step Function-Oriented View Next navigation step Application Server Next navigation step Application Server Infrastructure Next navigation step SAP Web Dispatcher Next navigation step Administration of the SAP Web Dispatcher Next navigation step Configuring SAP Web Dispatcher to Support SSL End of the navigation path

    • For SAP NetWeaver 7.4:Start of the navigation path http://help.sap.com/nw74Information published on SAP site Next navigation step Application Help Next navigation step Function-Oriented View Next navigation step Application Server Next navigation step Application Server Infrastructure Next navigation step Components of SAP NetWeaver Application Server Next navigation step SAP Web Dispatcher Next navigation step Administration of the SAP Web Dispatcher Next navigation step Configuring SAP Web Dispatcher to Support SSL End of the navigation path

Configure SAP Web Dispatcher Server Port

In order to satisfy the requirement of the Same Origin Policy, all systems in an SAP Fiori app landscape have to be served by a single Web server access point. Therefore, you configure a single icm/server_port in SAP Web Dispatcher to serve all back-end systems of an SAP Fiori scenario.

  1. Open the Web Dispatcher profile sapwebdisp.pfl.

  2. To configure the ports, you can copy the following source code and adapt it to your business requirements:

    Syntax Syntax

    1. icm/server_port_0 = PROT=HTTPS,PORT=443,TIMEOUT=120
    End of the code.

    Additional parameters needed by SAP Fiori for correct request routing:

    Syntax Syntax

    1. wdisp/system_conflict_resolution = 1
    2. wdisp/add_clientprotocol_header = 1
    3. wdisp/handle_webdisp_ap_header = 1 
    4. wdisp/add_xforwardedfor_header = true
    End of the code.

  • For SAP NetWeaver 7.31: Start of the navigation path http://help.sap.com/nw731Information published on SAP site Next navigation step Application Help Next navigation step Function-Oriented View Next navigation step Application Server Next navigation step Application Server Infrastructure Next navigation step SAP Web Dispatcher Next navigation step Administration of the SAP Web Dispatcher Next navigation step Parameterization of the SAP Web Dispatcher Next navigation step Overview of Parameters End of the navigation path.

  • For SAP NetWeaver 7.4:

    Start of the navigation path http://help.sap.com/nw74Information published on SAP site Next navigation step Application Help Next navigation step Function-Oriented View Next navigation step Application Server Next navigation step Application Server Infrastructure Next navigation step Components of SAP NetWeaver Application Server Next navigation step SAP Web Dispatcher Next navigation step Administration of the SAP Web Dispatcher Next navigation step Configuration of the Web Dispatcher Server Port End of the navigation path