To transfer application data and security credentials within your SAP Fiori system landscape, communication between the client, the front end, and the back end is established by using different communication channels and protocols:
Communication Between Client and SAP Web Dispatcher
According to the type of the app that you use and the type of the task that you perform, the client can issue the following types of requests:
HTML requests
OData requests
InA search requests
For fact sheets and analytical apps, these requests are forwarded to the ABAP front-end server or to the relevant back-end server (ABAP or SAP HANA) by SAP Web Dispatcher. For communication between SAP Web Dispatcher and the client, an HTTPS connection is established.
Communication Between SAP Web Dispatcher and ABAP Servers
For SAP Fiori search, transactional apps and fact sheets, SAP Web Dispatcher forwards the following types of requests to the ABAP front-end server and the ABAP back-end server:
ABAP front-end server:
HTML requests
OData requests
ABAP back-end server:
InA search requests (SAP Fiori search fact sheets only)
For communication between SAP Web Dispatcher and the ABAP servers, HTTPS connections are established.
Communication Between ABAP Front-End and ABAP Back-End Server
For transactional apps and fact sheets, data and services from the ABAP back-end server are provided to the ABAP front-end server by using OData services.
For communication between the ABAP front-end server and the ABAP back-end server, a trusted RFC connection is established.
Communication Between SAP Web Dispatcher and SAP HANA XS
For analytical apps, SAP Web Dispatcher forwards OData requests from the client to SAP HANA Extended Application Services (SAP HANA XS).
For communication between SAP Web Dispatcher and SAP HANA XS, an HTTPS connection is established.
Communication Between ABAP Back End and Map Provider
For fact sheets with integrated geographical maps, geographical coordinates and address data are transferred from the ABAP back-end server to the map provider using HTTP or HTTPS.
To ensure confidentiality and integrity of data, we strongly recommend protecting HTTP connections by using Transport Layer Security (TLS) or Secure Sockets Layer (SSL).
To communicate with the map provider using a proxy server, use one of the following options:
Install a separate SAP Web Dispatcher system.
Configure an additional host on the existing SAP Web Dispatcher system.
You can set up the additional host as a virtual host, or by assigning an extra port.
Note that SAP Web Dispatcher supports load balancing.
To use fact sheets with integrated geographical maps, you must buy a map license from a map provider, and you must configure SAP Visual Business accordingly. For more information, see Configure SAP Visual Business to Enable GeoMaps (Fact Sheets).
For information about communication channels in a side-by-side scenario, see Side-by-Side Scenario.
For information about setting up communication encryption for SAP NetWeaver, see the following documentation:
For SAP NetWeaver 7.31, see SAP Help Portal at http://help.sap.com/nw731
For SAP NetWeaver 7.40, see SAP Help Portal at http://help.sap.com/nw74
For information about setting up communication encryption for SAP HANA, see the SAP Help Portal at http://help.sap.com/hana_platform