Fiori Launchpad connect to backend S4 issue "Do you want to allow this website to open an app on your computer"

So basically we have done the Fiori frontend testing. Now here is the issue.

Open Fiori launchpad main url http://s4fiorigw.efglobe.com:8080/fiori

Click any of them, obvious it's not correct since it should point to the backend S4 server A4H, but actually it points to the Fiori Frontend server NPL

We go to LPD_CUST and take a look, all these demo tiles are pointing logical system SAP_ERP_LO

So we created a trusted RFC named SAP_ERP_LO pointing to the backend S4

This time when we go back and click any of the tiles from the Fiori launchpad, it pops up the following:

Then we know these type of Webgui may not be able to called this way.

So we created an HTTP type of RFC named 'SAP_ERP_PRC_HTTP'

Then change the definition in LPD_CUST to a URL type

Then we retest again, this time it's able to connect to the backend S4

Now we know the naming convention for RFC, or system alias it has to follow some standards. Here I copy the comments from SAP scn

For example, if the system name is XYZ, the different destination names should be the following:

    SM59 name-resolving sequence for SAP GUI aliases: XYZ_RFC,XYZ
    SM59 name-resolving sequence for HTTP aliases: XYZ_HTTPS, XYZ_HTTP, XYZ



Using this approach, it is possible to reference multiple connections by passing the base name only. Using the example above, it would be XYZ. The following name extensions (suffixes) can be used:

    _HTTP (XYZ_HTTP) - to define HTTP connection settings. Can be applied for connection types G and H.
    _HTTPS (XYZ_HTTPS) - to define HTTPS connection settings. Can be applied for connection types G and H.
    _RFC (XYZ_RFC) - to define RFC / SAP GUI connections. Can be used for connection type 3.
    _BOE (XYZ_BOE) - to define additional HTTP connection when used ABAP Launchpad Crystal Reports links. Can be define with connection of types G and H.



For connection types RFC (3) and HTTP (H,G), the name extension can be omitted (base name equal to SM59 destination name) and the runtime will still resolve the connection data properly. This fallback allows you to reuse existing definitions without extra configuration.

So besides above very traditional 'WEBGUI' or 'SAPGUI for HTTP' things, where the UI5 goes? where's the ODATA stuff?

So let's choose another Example

In this tile if we simply click it, errors shows up

Obvious this means the ODATA service was not published.

Above was the system alias that we define for backend S4. If you're not doing so then only local services are choosable

Then you can see hundreds of ODATA servers from S/4 show up

Then we publish all these MM related services, pay attention to the 'system alias'

Now we click again the tile, this time it's able to run

Another thing I would like to point out was, from Fiori frontend to S4 backend, even if you have SAP_ALL, that's not sufficient. To be able to call trusted connection, you'll need to have extra RFC authorizations. Otherwise it'll show authorization failures. You'll have to make sure you've tested the trusted RFC connection

A further configuration on the SAPGUI reverse proxy resolved the WEBGUI issue. Now it should not need to define HTTP within the LPD_CUST. The transaction should have worked.

Got some othe errors like

Error

The user menu tree for user "ALI" is empty. Please contact your system administrator.

So Finally we understand this is because the Apache reverse proxy could not pass something from the SAP web dispatcher.

We decided to define the web Dispatcher's port 8888 directly over internet so now it's able to display anything about webGUI, and the items within LPD_CUST don't need to be changed to 'HTML' any more