SAP Fiori Launchpad in SAP Solution Manager – Adding Tiles to Your Central Launchpad
The SAP Solution Manager provides two sets of Fiori Launchpad tile catalogs for the deployment options we support. That means, depending on the Fiori Launchpad scenarios you choose, you will have access to differing numbers of launchpad tiles.
- For the “embedded” Solution Manager Launchpad option, we provide catalogs with tiles for all the major Solution Manager applications. This includes Fiori and other UI5 applications as well as Web Dynpro and CRM WebClient UI applications.
- For the central front-end server (Central Hub) Launchpad deployment option, we provide a subset of tiles, namely only those for the Fiori applications. This is because only Fiori applications support a straight-forward deployment on a central launchpad.
You can of course get around this by doing the following:
- Create your own tile catalogs and groups in the central launchpad.
- In your catalogs, create URL tiles which launch the respective Solution Manager applications.
SAP does not ship these tiles because only you have the complete information required for the URLs, such as the fully qualified domain names, port numbers, etc. of your Solution Manager system.
URL tiles do not support the same integration as do the tiles for Web Dynpro applications in the embedded Solution Manager launchpad, nor do they support the same frontend/backend separation which Fiori apps provide. Still, for most use cases URL tiles are sufficient.
In this article I describe how you can find tiles only shipped on the Solution Manager system and how, with a little effort, you can create your own tiles on your central launchpad which link to the same applications as the Solution Manager specific tiles.
The Difference Between Embedded and Central Launchpad Deployments
I described these two deployment scenarios in a previous article, Using the SAP Fiori Launchpad in the SAP Solution Manager. However here is a brief summary:
- The embedded launchpad runs as part of SAP Solution Manager system and only provides content available within the Solution Manager.
- The Central Launchpad (Front-end Server, Central Hub) runs on an independent SAP NetWeaver system and can provide central access to applications running on several backend systems.
We provide the embedded option in the Solution Manager to get you up and running as soon as possible. Setting up a central launchpad takes more effort but allows you to have a central access point to applications interacting with many different systems.
Identifying Central Launchpad Catalogs
You can view all launchpad tile catalogs in the respective system by calling the Fiori Launchpad Designer (Cross Client) application (transaction /UI2/FLPD_CONF).
- All catalogs which are deployable on the central launchpad are included in software component ST-UI and have technical names with the prefix SAP_STUI (example: SAP_STUI_ITSM_MYINC_TC – SAP Solution Manager Incident Management).
- All Solution Manager catalogs which are only available on the embedded launchpad are included in software component ST and have technical names with the prefix SM (example: SMBusinessProcessOperation – Business Process Operations)
You can see in the following screenshot the two catalogs we provide for IT Service Management: SMIncidentManagement is the one only available in the Solution Manager embedded launchpad and contains all related applications. SAP_STUI_ITSM_MYINC_TC is also available in the central launchpad, provided you install software component ST-UI there; it contains only tiles for the related Fiori apps.
Adding Solution Manager Tiles to the Central Launchpad
This is a fairly easy two step process:
- Determine the URL of the Solution Manager application.
- In the central launchpad, create a new tile which launches the URL.
Determine the URL of the Solution Manager Application
In many cases, you can simply launch the tile you want from the Solution Manager launchpad and copy the resulting URL. There are several things you might want to watch out for though:
- “Clean” the URL by removing unnecessary parameters and session information.
- Ensure that you copy the URL of the actual application and not that of a framework application.
For example, CRM WebClient Applications, when launched, may contain session information embedded in the URL. It will look something like “https://<server:port>/sap(bD1lbiZaPTMwMCZkPW1pbg==)/bc/bsp…”. You should delete all the information within and including the parenthesis before using the URL for other users.
In particular, most Web Dynpro applications in the Solution Manager launchpad will run in a launchpad “shell”. The URL you see in your browser will be that of the embedded launchpad and not that of the actual Web Dynpro application.
You’ll notice that the URLs in the browser will start with something like “https://<server:port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html…”. To find the actual URL of the Web Dynpro application, do the following:
- Right click the application and select “Technical Help…”:
- Copy the URL from the resulting dialog box:This is the URL which will start the Web Dynpro application directly, and not the Solution Manager’s launchpad shell.
Create a New Tile to Launch the URL
For a full explanation of how to do this, see my previous blog article, SAP Fiori Launchpad in SAP Solution Manager – Creating Your Own Tile Catalogs, Groups, and Roles.
Here is a quick summary of what to do:
- Call the Fiori Launchpad Designer, transaction /UI2/FLPD_CONF (cross-client) or /UI2/FLPD_CUST (client specific).
- Create a new tile catalog, or select an existing one of your own.
- Add a new tile – select App Launcher – Static
- Fill out the details, such as the title, uncheck semantic object navigation and enter the target URL:
- Save your work.
By following this process, you’ll be able to access any URL-based application (in the Solution Manager or otherwise) from your central launchpad, even if SAP does not ship a tile for the application.
- SAP Help Portal: SAP Fiori for SAP Solution Manager – Select your ST-UI support package level and view the application help. The application help lists the respective Fiori apps, their catalogs and authorization roles. These are the applications which can be directly deployed on the central launchpad.
- Blog article: Using the SAP Fiori Launchpad in the SAP Solution Manager – An introduction to the Launchpad as used with the Solution Manager.
- Blog article: The SAP Fiori Launchpad in the SAP Solution Manager – Correcting Links Using Customization – How to override tile destinations delivered by SAP.
- Blog article: SAP Fiori Launchpad in SAP Solution Manager – Creating Your Own Tile Catalogs, Groups, and Roles – This article goes into the details of tile creation.
Could we actually add Solution Manager Launchpad embedded to S4HANA Launchpad in order to save the hassle of 2 launchpads entry?
Actually could we just use S4HANA FrontEnd Server to also access Solution Manager?
Ultimately - could we install Development Solution manager application on the same Data Base as S4HANA as a separate schema/client?
If yes, what is the minimum RAM and memory requirement for this approach?
Thank you very much,
Hi Adi Mogilevsky ,
We don't support using your S/4HANA system as a front end server for the Solution Manager. That's why we can't give any recommendations about sizing here.
There are still a few things you can do if you want to have just a single launchpad:
Hi Gordon Leslie
Indeed we have succeed to use just one Front end server for both s4HANA, Solman and even BW4HANA, while still ahve issues with Netweaver levels - different on each system, but I am ex-SAP Labs Israel, so we hacked correctly the Gateway