Skip to Content

[UPDATE 20-Nov-2017] : End users can launch Classic UIs from the Fiori Launchpad via Cloud Connector

Until few weeks back, we could only use the Fiori Launchpad on SAP Cloud Platform to launch Fiori apps deployed within the platform and also other contents via URLs and Mobile document. Fiori Launchpad is the entry point to access all SAP applications and we see many customers  using the Fiori Launchpad on SAP Cloud Platform to launch standard and custom Fiori Apps. However, there are still lot of customers who have a requirement to also expose SAP GUI transactions and WebDynpro ABAP applications along with these HTML5 based Fiori Apps. They were looking for ways to provide one single access point to their end users in order to access all types of applications (on-premise/cloud apps). It is now possible to launch even Classical UIs like SAP GUI (HTML) and WebDynpro ABAP applications which are available in the backend SAP system. If you are on release of ABAP Add-on SAP_UI 751, you have an option to create Technical catalogs in backend system and make them available to the Cloud Portal. In this blog, I am going to show the steps required to do this.

Prerequisites

  • SAP Cloud Platform Trial account
  • SAP Cloud Connector
  • Backend ABAP system with component SAP_UI version 751 and above [This is optional]

Configure Backend System

Login to your backend system and ensure that the SICF service is enabled. Also, ensure that you have the required SAP_UI2_ADMIN* roles in the backend system.

Using the Mass Maintenance Tool

SAP GUI (HTML based) and WebDynpro ABAP applications require an application descriptor if they are to be called from the SAP Fiori launchpad. We need to use the Mass Maintenance Tool (MMT) to create all the necessary application descriptors efficiently and in one place.

I can launch the Mass Maintenance Tool by executing the WebDynpro application SUI_TM_MM_APP as shown below.

In this step I am going to create a technical catalog which will represent a collection of SAPGUI & WebDynpro Apps. I can provide any name for my catalog and select from any of the available Semantic objects. In this example, I am going to use the demo EPM Module to display a Products Application which is delivered as SAPGUI Transaction (SEPM_PD) and also as a WebDynpro ABAP application(S_EPM_FPM_PD). Click on Continue.

Click on the “Insert” button and add the entries as shown below. One for a SAPGUI transaction and the other for a WebDynpro ABAP applicaiton. Click on Save.

With this our catalog is ready.

Setup the SAP Cloud Connector

The below configurations would need to be made in the SAP Cloud Connector (SCC). Its important to understand the role of SCC in this scenario. There are two personas when it comes to using this scenario. The first one is an Administrator who would create a portal site and create applications referring to these classical UIs. When the administrator tries to request for apps metadata, all the requests to the backend system will be routed via the SCC. When the Portal site is built and is accessed in an end-user persona, the requests will be again routed through the same Cloud Connector and the connection is kept secure.

Notice that I have provided the virtual host name same as the internal host name. I have also exposed the services under /sap/bc/ to the SAP Cloud Platform trial account.

Create destinations in SAP Cloud Platform

Below is how the destination needs to be configured. Notice that the URL is the actual host name and port number of the ABAP system. The proxy type is set as OnPremise as it would be needed for all the communication requests triggered by the Administrator when they create Apps in the Portal site. Such calls will go via SCC. Also notice that the usage property is Backend.

Create Apps in the Portal site

I am assuming you know how to create a Portal site. There are plenty of How-To-Guides to help you with that. I am creating a new App from the menu options. Click on the Value help provided for “App Resources”

Select “Backend Systems”. This will look for destinations with the usage property = Backend.

Select the backend system which has been configured.

Search for the Catalog which was created earlier and select it.

Notice that the both the Apps under the catalog would be listed. I have selected the SAP GUI transaction.

Notice that the system defaults all the values for the fields, including the semantic object and action

I have just assigned this app to sample catalog and group in the Fiori Launchpad.

Similarly, I am repeating the same steps to add the WebDynpro ABAP application too.

Finally, I publish the site and preview it. I get to see both my Apps in my Fiori Launchpad (which has a Belize theme in SAP Cloud Platform )

The SAP GUI version of Display Products renders as below in my Fiori Launchpad. This would open as a new tab.

Similarly, I can also launch the WebDynpro version of Display Products too from the Fiori launchpad.

Its also important to note that there are two ways of creating the Portal apps based on Classic UIs. The one described above assumes that you have a backend ABAP system with SAP_UI 7.51 version or above that enables you to create Technical catalogs. If you do not have a backend system with this version of SAP_UI, you could directly create a SAP GUI App/WebDynpro App on the Cloud Portal and provide the configuration details manually. For example, if you are configuring an App for WebDynpro, you would need to manually provide the application ID, Configuration ID etc.

To report this post you need to login first.

14 Comments

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

  1. Bernd Herold

    Hi Murali, thanks for the great blog. Question: Is there a simple way to render standard Fiori apps from the ABAP backend system with in HANA Cloud Portal, ideally even a mass import / rendering option that let’s me bring a set of standard Fiori apps from the ABAP backend system into the HANA Cloud Portal? Or is the only way to accomplish this through import from the SAPUI5 ABAP repository via Web IDE, basically app by app?

     

    (0) 
  2. Arun Obilisetty

    Hi Murali, For me the catalog is not getting loaded . I have created the connection to S4Hana using HCC. the virtual and the actual hostname are same and the connections are all working.

    I have also assigned the user which I am using for connection to s4hana the role which is required.

    Can you please help.

    (0) 
    1. Murali Shanmugham Post author

      Hi Arun,

      Please check you have exposed the services in the Cloud Connector and that you have used the usage property in the Destination. Please raise a question in the discussion forum if you need more support.

       

      (0) 
      1. Manuel Bellet

        Same problem for me; backend systems are listed but catalog is not getting loaded. Any idea? I checked connections, roles ecc. and everything seems to be ok.

        (0) 
  3. Manu Gupta

    Hi Murali ,

    Thanks for this Great Blog. I have one doubt that if we configure others SAP GUI Transactions like MIGO , VA01 , VL 10 N etc. in the same way you did ,  Would these be rendered with responsiveness and compatible with Mobile Devices ?

     

    Thanks,

    Manu

     

    (0) 
    1. Murali Shanmugham Post author

      Hi Manu,

      SAP transactions would be rendered as GUI for HTML. They wont be responsive. You can view GUI for HTML screens in mobile devices, but there are limitations.

      Regards,

      Murali

      (0) 
  4. Johannes Bacher

    Hello Murali,

    Whe creating the new app, i can select backend systems and I see my backend, but the catalog is not found. In the destination i have set property usage to Backend, what exactly needs to be enterd in property WebIDEUSAGE ? ist it required ?

    Also on our cloud connector, all lights are green.

    Any other hints ?

    thank you, Johannes

    (0) 
  5. Radhika Kuthiala

    Hello Murali,

     

    I am able to integrate a Web Dynpro in cloud portal using Basic authentication but it fails when I use Principal Propagation. Somehow the web Dynpro applications read the cloud cockpit destination URL as the main hostname rather than proxy URL and therefore I don’t see the call going to cloud connector.

    We do have Fiori applications working in cloud portal connected to Gateway through Principal Propagation

     

    Regards

    Radhika

    (0) 
    1. Murali Shanmugham Post author

      Hi Radhika,

      Classic UIs like WebDynpro do not get executed via Cloud Connector. The user needs to be on the corporate network to launch the Classic UIs. In order to achieve SSO, may be you could try something like Kerberos with Active Directory

      (0) 
      1. Radhika Kuthiala

        Hi Murali,

         

        We are planning to launch Supplier Portal which will be exposed   to end users and not Company Employees

        The Supplier Portal will expose Web Dynpro applications from QIM and PPM.Is there any option to establish SSO with backend SAP server from cloud portal to expose the web dynpro’s .The users will login with email id.

         

        Regards

        Radhika

        (0) 

Leave a Reply