This blog is for portal administrators who are implementing FLP on EP.
The content:
The Fiori Launchpad on Enterprise Portal is recommended for existing Portal customers. It allows customers to leverage their Portal capabilities and configuration and run all Portal content types with Fiori applications side-by-side for SAP and Non-SAP backend applications.
The Fiori Launchpad on ABAP integrates content from SAP systems only, using several specific UI technologies.
An average user may have up to ~50 applications on his Home Page and hundreds in the App Finder (also known as Tile Catalog). An excellent filtering and search controls enable the user to easily find and launch applications through the App Finder.
In Fiori 2.0 the Fiori Launchpad will be enhanced for high load of content, through Overview Pages, Links, App Finder enhancements and smart navigation.
Is the Cloud Portal able to replace the Enterprise Portal (on-premise)?
The Cloud Portal can replace the Enterprise Portal in some scenarios. It mainly answers simple scenarios in which a customer wants to integrate Fiori content provided by SAP or custom applications.
In the near future, the Cloud Portal will enable a much wider range of UI technologies integration (including legacy content).
When deploying a UI5-based application to the Enterprise Portal (either from Web IDE or uploading it to the Web Resource Repository), the application files are extracted into the Web Resource Repository.
The application is transportable through EP transport package mechanism and CTS+. You should include the whole app from WRR and the iView rendering the app (or parent role) in a regular transport package and export & import it between your systems.
All iViews and pages types are supported in FLP on EP. This means that all UI technologies are supported through FLP on EP, and should be opened in-place or in a new window according to the UI technology standards\quirks mode supportability.
For SAP Enterprise Portal:
The FLP on EP recommended landscape: https://eaexplorer.hana.ondemand.com/_item.html?id=11406#!/overview.
Landscape deployment scenarios and high level product overview: https://eaexplorer.hana.ondemand.com/rest/mimeRepositories/11427/file/Deployment_Recommendations_SAP....
The information can be accessed by customers directly on Service Marketplace by clicking on the Info link for SPS/Patch Level:
Example for NW SAPUI5 in 7.31:
The result then looks like this:
You can implement Fiori integration in FLP on EP in 2 ways:
Fiori iViews in Portal content are used when there is no Fiori Framework page (FFP) and the integration of Fiori apps is done in other Framework pages (e.g. AFP).
Remote Catalogs consumption from FESr is possible only with FFP, and then Fiori iViews are not needed.
The further advantages of remote catalog consumption are:
You can learn how to consume the remote content here.
Locked group is a special group of tiles on the Homepage:
Locked group definition is located in one the role/folder/workset properties. Sometimes it is hard to find where exactly it was defined. To make the locked content transparent and easy to maintain we suggest the following:
2. Provide The ID and the title under the path Portal Users -> Standard Portal Users -> iViews -> Fiori Launchpad Configuration:
3. Create a role to hold locked group content
4. Create a folder with a property Included in Locked Group and mark it as an Entry point.
Note: Only direct child of Folder/Role or workset will be seen in the locked group
5. Assign the relevant iViews to the folder:
This role can be included into relevant users’ roles.
If you have Fiori iViews for BEx reports in FLP on EP, the recommended navigation mode for them is Display in headerless portal window (standards mode), especially in Internet Explorer browser.
The reason is that BEx reports launched from FLP on EP in Internet Explorer browser, change UI mode to Quirks mode, and when coming back to FLP, the UI might be corrupted.
.
2031108 - SAP Fiori Integration with SAP Enterprise Portal - Central note
2261419 - Maintenance Strategy for FLP on Portal
The content:
- When to use the Fiori Launchpad on Enterprise Portal and when the Fiori Launchpad on ABAP?
- Does the concept of Fiori Launchpad on Enterprise Portal fit scenarios where dozens of applications are maintained?
- Is the Cloud Portal able to replace the Enterprise Portal (on-premise)?
- How is the SAPUI5 application lifecycle is done (DEV->QA->PROD) in the SAP Enterprise Portal?
- Which iView types can run through FLP on EP?
- Portal Landscape Deployment Recommendations
- SAPUI5 Release for NetWeaver SPS
- Fiori iViews vs Remote Catalogs
- Locked Group Easy Maintenance
- BEx Reports in FLP on EP in IE
- Maximum Number of Categories
- Useful Notes
When to use the Fiori Launchpad on Enterprise Portal and when the Fiori Launchpad on ABAP?
The Fiori Launchpad on Enterprise Portal is recommended for existing Portal customers. It allows customers to leverage their Portal capabilities and configuration and run all Portal content types with Fiori applications side-by-side for SAP and Non-SAP backend applications.
The Fiori Launchpad on ABAP integrates content from SAP systems only, using several specific UI technologies.
Does the concept of Fiori Launchpad on Enterprise Portal fit scenarios where dozens of applications are maintained?
An average user may have up to ~50 applications on his Home Page and hundreds in the App Finder (also known as Tile Catalog). An excellent filtering and search controls enable the user to easily find and launch applications through the App Finder.
In Fiori 2.0 the Fiori Launchpad will be enhanced for high load of content, through Overview Pages, Links, App Finder enhancements and smart navigation.
Is the Cloud Portal able to replace the Enterprise Portal (on-premise)?
Is the Cloud Portal able to replace the Enterprise Portal (on-premise)?
The Cloud Portal can replace the Enterprise Portal in some scenarios. It mainly answers simple scenarios in which a customer wants to integrate Fiori content provided by SAP or custom applications.
In the near future, the Cloud Portal will enable a much wider range of UI technologies integration (including legacy content).
How is the SAPUI5 application lifecycle is done (DEV->QA->PROD) in the SAP Enterprise Portal?
When deploying a UI5-based application to the Enterprise Portal (either from Web IDE or uploading it to the Web Resource Repository), the application files are extracted into the Web Resource Repository.
The application is transportable through EP transport package mechanism and CTS+. You should include the whole app from WRR and the iView rendering the app (or parent role) in a regular transport package and export & import it between your systems.
Which iView types can run through FLP on EP?
All iViews and pages types are supported in FLP on EP. This means that all UI technologies are supported through FLP on EP, and should be opened in-place or in a new window according to the UI technology standards\quirks mode supportability.
Portal Landscape Deployment Recommendations
For SAP Enterprise Portal:
- Landscape Deployment of SAP Enterprise Portal (EP)
- Landscape Deployment Recommendations for SAP Enterprise Portal
- SAP Enterprise Portal
The FLP on EP recommended landscape: https://eaexplorer.hana.ondemand.com/_item.html?id=11406#!/overview.
Landscape deployment scenarios and high level product overview: https://eaexplorer.hana.ondemand.com/rest/mimeRepositories/11427/file/Deployment_Recommendations_SAP....
SAPUI5 Release for NetWeaver SPS
The information can be accessed by customers directly on Service Marketplace by clicking on the Info link for SPS/Patch Level:
Example for NW SAPUI5 in 7.31:
The result then looks like this:
Fiori iViews vs Remote Catalogs
You can implement Fiori integration in FLP on EP in 2 ways:
- Creating Fiori iViews in Portal content
- Consuming Remote Catalogs from Frontend Server (FES).
Fiori iViews in Portal content are used when there is no Fiori Framework page (FFP) and the integration of Fiori apps is done in other Framework pages (e.g. AFP).
Remote Catalogs consumption from FESr is possible only with FFP, and then Fiori iViews are not needed.
The further advantages of remote catalog consumption are:
- Easy tile maintenance on FES with Fiori Launchpad Designer
- Easy catalog and group maintenance on FLP on EP - the changes in the catalog on FES are visible on FLP on EP automatically
- Big variety of Fiori apps available via the catalogs
- New features available via the catalogs (e.g. dynamic tiles)
- Running better on Mobile access due to no-iFrame integration.
You can learn how to consume the remote content here.
Locked Group Easy Maintenance
Locked group is a special group of tiles on the Homepage:
- Its content is determined by an administrator and cannot be personalized by an end-user.
- Any administrator changes in this group are reflected immediately on the Homepage.
- Only one locked group can be configured. It always appears at the top of the home page.
- The locked group content can be combined from Portal tiles and remote groups.
Locked group definition is located in one the role/folder/workset properties. Sometimes it is hard to find where exactly it was defined. To make the locked content transparent and easy to maintain we suggest the following:
- Enable a locked group in FWP
2. Provide The ID and the title under the path Portal Users -> Standard Portal Users -> iViews -> Fiori Launchpad Configuration:
3. Create a role to hold locked group content
4. Create a folder with a property Included in Locked Group and mark it as an Entry point.
Note: Only direct child of Folder/Role or workset will be seen in the locked group
5. Assign the relevant iViews to the folder:
This role can be included into relevant users’ roles.
BEx Reports in FLP on EP in IE
If you have Fiori iViews for BEx reports in FLP on EP, the recommended navigation mode for them is Display in headerless portal window (standards mode), especially in Internet Explorer browser.
The reason is that BEx reports launched from FLP on EP in Internet Explorer browser, change UI mode to Quirks mode, and when coming back to FLP, the UI might be corrupted.
Maximum Number of Categories
Today there is a limitation for the number of categories you as an EP administrator can define via iView Properties editor: maximum 20 categories.
However, you can increase this number using PCD Inspector tool as describe in SAP note 2214932 - Addition of more than 20 categories in FLP@EP.
.
Useful Notes
2031108 - SAP Fiori Integration with SAP Enterprise Portal - Central note
2261419 - Maintenance Strategy for FLP on Portal
2008931 - Known issues for Fiori Framework Page (FLP on Portal)
- SAP Managed Tags:
9 Comments
