
This document is for demonstrating how to configure SAP Fiori Launchpad on Portal (FLP). This document provides steps on how to enable the Fiori Launchpad which is present in the SAP Portal. It covers how we can convert existing portal roles and convert iViews into tiles in Fiori. It mainly covers how we can Launch Web Dynpro ABAP and SAP GUI transactions from the Portal Fiori Launchpad.
This wiki is the inspiration from the wikis:
http://scn.sap.com/community/enterprise-portal/blog/2014/07/17/sap-fiori-launchpad-on-portal-sample-... written by shani.ozeri
http://scn.sap.com/community/enterprise-portal/blog/2014/11/13/building-your-mobile-portal-using-fio... written by sibylle.brehm
I have tried to elaborate it and have provided more detailed steps.
SAP Fiori launchpad on portal is available for portal customers as of NW 7.31 SP12 and NW 7.4 SP7 and above.
With FLP on EP, portal administrators can control which applications appear in the launchpad for desktop, mobile and tablet devices. SAP Portal iViews appear as tiles in the Launchpad.
It provides the detailed step by step instructions in configuring and building a demo role to access SAP Fiori on SAP Portal.
Portal by default comes with URL alias “portal/fiori”. Check and make sure its present if not then create a new one as per the screen shot.
Navigation: System Administrator->System Configuration->Portal Display->URL Alias Manager
2. | Assigning Fiori Desktop to URL Alias |
We have to assign the Fiori desktop to the url alias “portal/fiori”
Navigation: System Administrator->System Configuration->Portal Display->Desktops and Display Rules->Portal Content->Portal Administrators->Super Administrators->Master Rule Collection
If URL alias = portal/fiori
Portal Desktop = pcd:portal_content/every_user/general/defaultFLPFrameworkContent/FLPDesktop
URL for accessing FLP
After applying this rule, to access Fiori on portal, we have to use the url
http://<host>:<port>/irj/portal/fiori
Device group manager is the place where we can specify what types of devices that are supported. We need not make changes to it unless we have any specific requirement.
Navigation: System Administrator->System Configuration->Portal Display->Device Group Manager
Object IDs: Observe the Object Ids, we need to pass the object ids to the iViews so that the respective iView can be accessed from desktop/smartphone/tablet devices.
If an iView has to be acceded in all the 3 devices i.e. in Desktop, Smartphone and Tablet then the Object ID of iView should have value:
com.sap.portal.dg.desktop;com.sap.portal.dg.smartphone;com.sap.portal.dg.tablet
Using the Categories iView we can manage the tile catalog of Fiori. The iView by default comes with few preconfigured sample categories; we can edit them or can define a new category in the same iView.
Navigation: Content Administrator->Portal Content Management->Portal Content->Portal Users->Standard Portal Users->iViews->Fiori Launchpad->Fiori Launchpad Categories
PCD: portal_content/every_user/general/iViews/FioriLaunchPad/FioriLaunchpadCategories
Here is the screen shot showing the pre-configured. The category has the Category ID, Category Order and Category Title.
For demo let’s add a new category:
Category ID: MY_COMPANY_APPS
Category Order: 8
Category Title: My Company Apps
Create a free style or any other kind of role as needed. For demo let’s create a role “My Organization Fiori Apps” and add couple of iViews, we can add different type of iViews like URL, Wb Dynpro, SAP Transaction, App Integrator, UI5 etc iViews to the role.
We can take the existing SAP Portal roles and can convert the iViews into tiles in Fiori. For this we need to set the following properties for iViews, pages and roles.
a. Category Assignment
b. Object ID of device group
c. Icon URI and Image type
How to set these properties are described below in detail.
We need to set the Category Assignment property for the iView so that the respective iView would be visible in the Category Group in Fiori.
Let’s assign the Category ID which we created in step 4 i.e. MY_COMPANY_APPS
iView can also belong to multiple categories, then in Category Assignment we can have multiple categories with semi colon separated.
If an iView belongs to categories WebDynpro and MY_COMPANY_APPS, then Category Assignment should have value: WebDynpro;MY_COMPANY_APPS
For all the iViews, Pages and Roles used in Fiori we have to set the “Object Id for Device Group” property.
Note: This property is Mandatory; if we don’t set the property then the iView will not be displayed in FLP.
com.sap.portal.dg.desktop – this value will make the iView visible in FLP for desktop users.
com.sap.portal.dg.smartphone – this value will make the iView visible in FLP for smartphone users.
com.sap.portal.dg.tablet – this value will make the iView visible in FLP for tablet users.
For displaying the image on the Fiori tile, for the iView we have to set the “Icon URI” property
Setting the Icon URI and Image type properties, we can see the image on the Fiori tile as shown below.
We can find the SAP delivered images on portal in Web Resource Repository.
Navigation: Content Admin->Web Resource Repository->Web Resources->Pictograms
We can access the SAP Fiori home page by using the url
http://<host>:<port>/irj/portal/fiori
Assign the role which we created for Fiori for a user id and test it. Let’s see how ours apps will be displayed in Fiori.
It will display the POWL based application.
Clicking the Employee Self Service tile will access the backed ECC Launchpad and will display the apps configured in the Launchpad. Here we are displaying the ESS Launchpad in the tile.
It will display the backend Web Gui SAP transaction: S_P99_41000111
It will display Web Dynpro for ABAP application: salv_wd_test_image1
It will display the custom portal application built for searching the documents in KM Repository.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
10 | |
8 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 | |
4 | |
4 |