Skip to Content

SAP Fiori launchpad is the strategic single point of entry for SAP business applications and analytics. It offers a role-based, personalized and real-time access for end users.

If you are not familiar with Fiori UX and Fiori Launchpad you can find more information here.

Starting from SAP HANA 2.0 SP01, you can aggregate Fiori applications running on this version with Fiori Launchpad and provide the end user with the Fiori Experience.

The Fiori launchpad capabilities include:

  1. Role based access
  2. Personalization
  3. Theming and Branding
  4. Translation

You can now start with creating your Fiori Launchpad site by using SAP Web IDE and add additional applications to it.

So, how to get started?

After you have the applications ready, you can create a new “Multi Target Application Project”. After the project is created you can select New and “SAP Fiori Launchpad Site Modules”. This will open a wizard that will guide you through the creation of a Fiori Launchpad Site that contains the applications you would like to include. Build the project to create an mtar file containing the out of the box content of the site. You can than deploy the mtar file by using the “xs deploy” command. During the deployment, you will receive the URL for the site. This URL can be send to the end users to access the Fiori Launchpad Site with all the applications.

The end user receiving the Fiori Launchpad Site will benefit from the capabilities of branding, translations and personalization.

 

Here is a movie created by our developers that shows step by step how to create a Fiori Launchpad site on SAP HANA 2.0 SP01.

 

 

More information on how to create the site and how to add more content to your site can be found here:

https://help.sap.com/viewer/4505d0bdaf4948449b7f7379d24d0f0d/2.0.01/en-US/fdb899c213d449158836669840fd2690.html

 

Good luck and let us know what you think,

Rachel.

To report this post you need to login first.

15 Comments

You must be Logged on to comment or reply to a post.

  1. Mike Doyle

    Thanks Rachel, this looks awesome.  I have a question regarding the UI5 versions.  In cloud Platform I can choose the UI5 runtime version in the configuration cockpit.  Am I right in assuming that this isn’t possible with an XSA launchpad?  Is the version tied to the HANA release?

    (0) 
    1. Shrutika Purohit

      Hi Rachel,

      Really it is a very informative blog and I have already shared it. Mike, SAP Fiori 2.0 has introduced an important feature of managing large numbers of applications. Fiori has taken UI/UX to the next level like for example if we remember those initial Launchpad looks, which had a specific and restricted number of tiles/applications to this time when Fiori has become much more capable of handling entire business flows with a larger number of SAP Fiori applications.

      (0) 
  2. Rachel Kahana Samet Post author

    Hi Mike,

    Your assumption is correct. This is just one of the (many) benefits for running your applications in the SAP Cloud Platform.

    Best,

    Rachel.

    (0) 
  3. Alexey Myakinkii

    To whom it may concern: there is a module @sap/site-content-deployer that is responsible for pushing the site-content params to sap-portal-persistency service.

    So, basically deploy-tasks-manager.js tries to send it via HTTP/PUT with npm ‘request’ module which fails to do so with self-signed certificate (and deploy.js doesn’t print that error out).

    One can overcome this issue with a well-known nodejs env var:

    xs se <YOUR_CONTENT_APP_NAME> NODE_TLS_REJECT_UNAUTHORIZED 0

    Also, I suppose defining ‘tasks’ section in mta.yaml to redefine deploy task with that env var should work as well.

    Hope this helps.

     

    UPD: ok, the reason why you would be interested in doing all that stuff above is the case when your launchpad site module successfully deploys, but the Content module does not.

    There’s also a small catch setting the node env var: ‘xs se’ cannot set a var to a non-existent app, so you can’t issue the se command prior to ‘xs deploy’, but after you have tried to deploy your sample (or whatever) launcphad mtar and it failed (you can see it with ‘xs mta-ops’ command ) the content module ( which is actually an app in cf terminology) is created and the ‘xs se’ command will succeed.

    You can then retry the deploy command with

    xs deploy -i <OP_ID_FROM_XS_MTA-OPS> -a retry
    (2) 
  4. Matthias Aumüller

    Thank you @rachel.kahanasamet for the blog post.

     

    I wonder if it is possible to add dynamic tiles to this Launchpad?

    I already tried to add a serviceUrl to a tile configuration, but it seems to be ignored. It would be a pity if its not possible to use dynamic tiles on HANA Platforms since it is one of the bests features of Fiori Launchpad.

    Greetings

    (0) 
    1. Zohar Sheinberg

       

      Hi Matthias,

      It is possible to add dynamic tiles to this Launchpad:

      Below I pasted some configuration sample snippet. The “indicatorDataSource” section makes the tile dynamic.

      The ‘path’ specifies the url of the odata call that the tile will invoke.

      “sap.app”: {
      “_version”: “1.3.0”,
      “id”: “72dc6cc1-bb3f-4c6a-899e-379821100c8e-1481201123960”,
      “title”: “No resource selected”,
      “tags”: {
      “keywords”: []
      },
      “crossNavigation”: {

      “inbounds”: {
      “SalesPerformanceDisplay”: {
      “semanticObject”: “SalesPerformance”,
      “action”: “Display”,
      “deviceTypes”: {
      “desktop”: true,
      “tablet”: true,
      “phone”: true
      },
      “info”: “”,
      “icon”: “sap-icon://Fiori2/F0365”,

      “indicatorDataSource”: {
                                “path”: “/product_sales/resources/sap/demo/dynamictile/dynamic.json”,
                                “refresh”: “6000”,
                                “displayNumberUnit”: “%”
                        },

      Some info about the dynamic data your Odata service need to return : https://help.sap.com/saphelp_uiaddon10/helpdata/en/4d/2b9e3c92e54b2192f031a2941927d6/content.htm

      Regards,

      Zohar

      (1) 
  5. Dirk Raschke

    Hi,

    our deploying of this prototype fails, the app is crashing when starting.

    In the logs I could find this issue:

    ERR  VError: environment-destinations/0/url: String is too short (0 chars), minimum 1 

    Has anyone an idea to solve this problem?

    Thanks!

    (0) 
  6. Neha Neha

    After successfully deploying the Fiori Launchpad on XSA, the sample applications still don’t appear for me. Is some configuration is missing or is this problem known?

    (0) 

Leave a Reply