Skip to Content
Technical Articles
Iris Sasson
Iris Sasson
October 29, 2018 4 minute read

Develop your first SAP Fiori launchpad site with portal service on SAP Cloud Platform Multi Cloud – part 2

Follow RSS feed
5 Likes 3,143 Views 26 Comments

The first blog post of this series, provides a step by step guide to create all assets that are required  to develop your first Fiori launchpad site. In this blog post, we continue where we left, and create a Fiori launchpad site, based on the assets you should already have.

We will start by creating a Fiori launchpad site from SAP Web IDE Full Stack, configure the site, deploy it to SAP Cloud Platform and access it.

Read the bottom section of this blog for some answers to FAQ.

 

Add SAP Fiori Launchpad Site Module to your development project

A. Enable the SAP Fiori Launcpad Site feature, from the settings.

Navigate to the settings of Web IDE Full Stack settings, select  Features, locate the SAP Fiori Launchpad Site feature, and turn it to On. Click Save to save your settings.

Enabling the SAP Fiori launchpad Site feature, will allow you to create Fiori Launchpad (FLP) modules from Web IDE Full Stack.

 

B. Add SAP Fiori launchpad site module to your development project

Navigate to the development section.

Right click on the project to open the menu, and add a new SAP Fiori Launchpad Site Module to our project. Note: this is available only for projects of type Multi Target Application (MTA)

 

We provide the module a name (in this demo we use flp) and click Finish.

 

Configure the content and settings of your Fiori launchpad site

A. Add apps to your FLP site

Open the CommonDataModel.json file under the flp\portal-site folder

Click on the Add Group to add two groups: Group1 and Group2

 

Click on the + icon to add apps to a group. Add app1 to Group1 and App2 to Group2. After you click the + icon to add an app, check the relevant app and click Select

 

Your CommonDataModel.json launchpad editor should look like this

 

Note that you can also select the Code Editor tab, to edit the json representation of your portal site

 

Edit your site setting

 

Click on the Site Settings tab, view and edit the available settings

 

Click the save all icon, to save your changes or click ctrl+s.

 

Build and Deploy your project

A. Right click on your project and select Build

An mta archive file is generated. The file is located under the mta_archives folder in your workspace.

Right click on your project mtar file and select to Deploy to SAP Cloud Platform

 

If required, select your end point organization and space and click Deploy. (you will be asked to enter your Cloud Foundry environment credentials)

Look on your console pane, to see a log of the successful deployment. After a successful deployment, a URL address of the deployed project is listed in the console pane.
You can access your SAP Fiori luanchpad site by navigating to this link and adding the extension /cp.portal to the URL address

 

 

View your site in the SAP Cloud Platform cockpit

Let’s navigate to our Cloud Foundry subaccount

We can see that under our space, our application is now available. Note that the name of your app can have a prefix and that it has the appRouter name as postfix.

 

Click on the app on the Cloud Foundry environment to see it’s information. You can see the project URL. Click on it. Add to the URL the extension /cp.portal to view the SAP Fiori luanchpad site

 

End users can now access the Fiori launchpad to access their apps. They can also personalize their home page from the me area.

 

 

Answers to frequently asked questions

A. What Cloud Providers are supported?

You can view the supported Cloud Providers from the SAP Cloud Platform Regions and Service Portfolio page

 

B. What features are supported?

Visit SAP Cloud Platform Portal – Cloud Foundry page  to learn more about the supported features

 

C. I have a license for SAP Cloud Platform portal, can I use the license also for SAP Cloud Platform Portal on the Cloud Foundry environment?

Yes. The quota you licensed (portal site visits or portal users) can be used across Neo and Cloud Foundry – it is not limited to any specific cloud. However, using SAP Cloud Platform services on the Cloud Foundry environment, may require additional licenses.

 

 

Assigned tags

Related Blog Posts

    Related Questions

      26 Comments
      You must be Logged on to comment or reply to a post.
      • Steffen Schmidt

        Hi,

        thanks a lot for the blog post.

        I tried to follow the steps, but when deploying the build mtar file I get the following error:

        Error creating services: Error creating service “portal_resources_PortalDemo” from offering “portal” and plan “standard”: Controller operation failed: 404 Not Found: Could not create service instance “portal_resources_PortalDemo”. Service plan “standard” from service offering “portal” was not found.

         

        Where my Portal demo is the name of the MulitTarget project in WebIDE Full-Stack.

        Any idea what I am missing?

        Best Regards,

        Steffen

        • Iris Sasson Post author

          Hi Steffen

           

          There is currently an issue with the portal quota for existing portal customers.

          Please open a BCP ticket with the component BC-NEO-CIS-OPS and request the quota for the portal. (type ‘Portal’ with plan ‘Standard’)

           

          Iris

           

          • John Juan

            Hi Iris,

            Thanks for creating this post!

            I received a similar error to Steffen when deploying the mtar file:

            Error creating services: Error creating service “dt_portaldemo_ui_deployer” from offering “html5-apps-repo” and plan “app-host”: Controller operation failed: 404 Not Found: Could not create service instance “dt_portaldemo_ui_deployer”. Service plan “app-host” from service offering “html5-apps-repo” was not found.

            Should I create a similar BCP ticket for this as well? Or is this a different issue?

            Thanks!

            JJ

      • Iris Sasson Post author

        Hi

        I wanted to update that the below mentioned issue is fixed. You can now create portal sites without opening the above mentioned BCP

         

        Cheers

        Iris.

      • Amit Choudhary

        Hi

        I followed all steps but getting following error when i try to build –

        “Invalid mta.yaml. Make sure that the required module or resource dt_CFPOCHANA_appRouter is defined”

         

        Please help me.

      • Andre Fernandes

        Hi Iris Sasson ,

        I followed your steps and everything worked fine with a dummy UI5 app. I did the same for a List Report (Fiori Elements template) and it also worked. However, when I tried to use Overview Pages or Analytical Pages (the other two FE templates), there were errors.

        The FLP could open the ALP, but nothing loaded as somehow the app couldn’t read the odata’s metadata (the exactly same endpoint that worked fine with the List Report).

        The OVP didn’t even open from the FLP, as the Component and manifest couldn’t be reached.

        Those were all created directly with the Web IDE’s wizard, without any additional code. Are you aware if extra steps are required for OVPs or ALPs to work with the FLP module?

        Best regards,
        André

      • Cara Damm

        Hi Iris,

         

        thanks for the blog.

        The portal service seems to be fixed, which is great news.

        However I’m still facing issues with the FLP part. The build part is running fine – however the deployment is failing.

        I have checked my logs and there is an error with the buildpack saying: “ERR None of the buildpacks detected a compatible application”

         

         

        Thanks,

        Cara

        • Cara Damm

          In case someone is having the same problem as me, here is how I was able to solve it:

          1. Download the Directory to your local machine
          2. Check your npm version (It needs to be higher than 6.0)
          3. deploy the FLP app from your cf cl

          Regards,

          Cara

           

           

      • Alejandro Sensejl

        Hi Iris Sasson , great blog. I learned a lot from it.

        I tried the same using a Fiori template fetching metadata from WebIDE/Neo destination.

        Can you explain what to do in order to adopt to a CF destination, please?

        In my case there is a subaccount level CF destination that targets the same on-prem system as the Neo destination that was used to create the app, but it does not have the same name.

        Thank you!!

        Best regards,
        Alej

      • Paige Ola

        Hi Steffen Schmidt,

        how did you fix your issue in the end? I have the same one now and apparently the issue was not fixed..

        I’m using the trial version of cloud foundry. Now I recognized, that in the first blog post it’s mentioned:

         (important: Portal service on the Cloud Foundry environment is currently available only on the production environment, so you cannot use a trial account to create your portal site)

        But the tile is available and I can add a module to my mta and so on, even building works. But not deploying.

        Can I open a BCP Ticket as well then? And how can I do this?

        Best regards,

        Paige

      • Sasi Reddy

        Hi All/ Thomas Jung

         

        We are in the process of developing oData v4 and UI5 apps in Hana (Cloud Foundry) and exposed them via the Fiori Launchpad as defined in this bog. It looks like UAA.USER scope is needed for the users to get to the Fiori Launchpad and we are not able to bind our custom UAA scopes to the UI apps nor to the FLP. It means, anyone with the link to our FLP can access it as long as they have a valid SAP ID, which we dont want. It would be great if you can point me to the right direction.

         

        We even tried the same in the Portal Service using the below link, I was able to create the groups and catalogs, but no was to bind the apps and roles to these groups and catalogs.

        https://help.sap.com/viewer/ad4b9f0b14b0458cad9bd27bf435637d/Cloud/en-US/b824e1a682c044d6a7a0d836a364f13d.html

        Thanks

        Sasi

          • Sasi Reddy

            Hi Trim

             

            Yes, we got this issue resolved. We are able to restrict the users at the app level. We need to add the scope for the app in the manifest.json and use this scope to build the role mapping in the CF. Once you assign this role in the CF at the space level, then the apps will be isolated.

            Did you work for Mindset before?

             

            Thanks

            Sasi

      • SIMMACO FERRIERO

        Hi,

        Does anybody know how to add an external application to the launchpad? For example an existing application in the same CF space, but not included in the same project?

        Regards,

        Simmaco

      • Iris Sasson Post author

        You can try to do that using the Portal service. i.e. deploy two MTAs with apps to the SAP Cloud Platform. Create a Portal site using the Portal service (admin experience). Create a destination to each of the launchpad modules that were deploy and add the apps to your Portal site using the Admin tool. This is well documented and we plan to issue a document further explaining how to do that soon. I must say I did not yet try to connect applications from different projects, so there may be issues but it should work as far as I know. I will try to find the time next week to verify. Let me know how it goes for you