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 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:
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.
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:
If other systems are included in the landscape (e.g. HANA system), they should be represented in the configuration as well.
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 )
Please note:
Please note:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 |