Setting up SAP Enterprise Portal (EP) as an access point to Fiori Launchpad (FLP) allows combining capabilities such as EP roles, content management and integration capabilities with the new FLP UX world, and significantly simplifies the integration efforts on the client side.In this blog we will describe, on high level, the corresponding integration architecture.
FLP on EP simple landscape
FLP on EP can run using only portal resources and providing FLP look and feel with full FLP functionality using Portal Fiori Framework Page (FFP).
FFP components include a bootstrap html document, functional Fiori and UI5 resources and content.
The landscape for this scenario looks like this:
FLP on EP with remote content consumption from ABAP FES
An Enterprise Portal integrated with SAP Fiori scenario will require a more sophisticated landscape, where the client will get the resources from EP, Fiori Front-end Server (FES) and Gateway, with a single web url.
For FES, Gateway and Portal systems the ‘System’ objects should be configured in Web Dispatcher profile.
Distributing requests via SAP Web Dispatcher
To enable this scenario a reverse proxy concept must be implemented in the landscape. It is done with SAP Web Dispatcher.
Additionally, FLP requires SSL configuration throughout the entire landscape.
The content requests are distributed on the Web Dispatcher using redirection rules per ‘System’ object. These rules together define the landscape.
The configuration looks like an “non-portal” FLP landscape with an exception of a Portal added as the last rule.
So, Portal/FES integration configuration will have as minimum:
- FES system
- Portal system.
If other systems are included in the landscape (e.g. HANA system), they should be represented in the configuration as well.
- Configure FLP landscape, following the configuration guidelines Configuring SAP Web Dispatcher for FLP on ABAP.
- In the profile file add a configuration line for the Portal:
wdisp/system_# = SID=<EP SID>, MSHOST=<EP MSHOST>, MSPORT=<EP MSPORT>, SRCSRV=*:<WDISP PORT>, SRCURL=/irj;/
(See also: Configuring SAP Web Dispatcher for FLP on Portal )
- This line should be the last one in the configuration list
- It should contain the redirection ‘/’, meaning that all un-matching requests will be redirected to the Portal.
Things to consider
- SAP Fiori Launchpad and Enterprise Portal integration supports various configurations, such as landscape components sharing (for example, for Dev & QA landscapes). For this you can configure different virtual hosts/ports on the same reverse proxy.
- There should not be any hard-coded network attributes
- The request’s “host” header should not change along the flow in reverse proxy configuration.
- For a more complex redirection, e.g. when accessing more than one HANA system, please refer to Configuring SAP Web Dispatcher to Dispatch Requests to Different Systems.
- When consuming UI5 applications from an intranet under another domain name, click-jacking protection might be required (see note 2057847 - Removing/Relaxing Click-Jacking Protection for the SAP Fiori Launchpad ).
SAP Help library links:
- SAP Fiori Launchpad on Portal
- Setup of SAP Fiori System Landscape with ABAP Environment
- Configuring SAP Web Dispatcher ( for FLP on Portal)
- Configuring SAP Web Dispatcher (for FLP on ABAP)
- SAP Web Dispatcher
- SAP Fiori launchpad in SAP Enterprise Portal: Overview Information
- New SAP Fiori Launchpad on SAP NetWeaver Portal Features (NW7.31 SP16, NW 7.40 SP11)
- SAP Enterprise Portal on SAP NetWeaver 7.4: Features and Highlights