Launch a remote Slipstream Engine from a central Fiori Launchpad

[fxlevy]

Hello, after some work and the help of the SAP support (see my previous question) we were able to run a SAP Screen Personas flavor using the SAP Slipstream Engine from SAP Fiori Launchpad tile.

That was the first objective, to demonstrate the Slipstream Engine integration inside the SAP Fiori Launchpad.

But our main goal is to do the same for a remote system. Meaning to give the ability to launch a Slipstream Engine Flavor defined in a SAP remote system from a central Fiori Launchpad.

At the moment, i didn't see any documentation that explains this feature. There is a documentation to launch a Personas flavor with the "old" approach but not based on the new approach that was used for our first integration test.

Is this feasible and how?

[eric_carlson]

Hi François, did you ever find a resolution to this issue to enable multiple back-end components from single launchpad?

[fxlevy]

Hello, i come back with this question. The integration of one Back-End Slipstream Engine into a central Front-End server Fiori Launchpad works fine. Many thanks for the help and the workaround provided by SAP to solve this problem.

Now, we would like to integrate two different back-end Slipstream Engine, one from an ECC and one from an EWM to manage centrally from the SAP Fiori Launchpad all warehouses with the same design and process with Personas.

You suggested to create an Alias on the Back-End. That's what we did. We've created in the ECC back-end an alias '/sap/bc/ECC/se' that points to the '/sap/bc/se' services. We update the target in the SAP fiori catalog of the FES to use '/sap/bc/ECC/se/m/script/sap/se/ui' in the URL of the SAP Fiori App target definition instead of the '/sap/bc/se/m/script/sap/se/ui'

We defined in the SAP Web Dispatcher a route to redirect all URL starting with /sap/bc/S51/se to the ECC back-end.

When launching the Tile all URls contains /sap/bc/S51/se except the URL that requests the SAP GUI screen structure (/sap/bc/se/rg) which doesn't contain the S51 prefix. As a consequence the URL cannot be routed to the ECC back-end and the tile doesn't work.

Any suggestion to solve this issue?

Many thanks in advance for the help. 🙂

[fxlevy]

I made a mistake when writing this comment, please read ECC instead of S51. S51 is the real SID of our SAP system. ECC is a more generic name i wanted to use in this comment. Sorry for the misunderstanding. 😞

[fxlevy]

Hello Tamas, thanks for the answer, the help and the proposal. 🙂

Do you mean that we should define an spécific alias in the SICF of each back-end that point to the same /sap/bc/se/rg and define a different route for each alias in the SAP Web Dispatcher to sned the request to the corresponding back-end? Never tried this, we will test and advise.

[tamas_hoznek]

Yes, that's what I mean.

[fxlevy]

Hello, just wanted to keep you inform. After a bit of work the native integration of a Sap Screen Personas flavor inside the SAP Fiori Launchpad works using the Slipstream Engine works.

The Front-End server is a SAP NetWeaver 7.50 with a SAP Kernel 749. The back-end system was a ECC 6 EHP4 with a SAP NetWeaver 7.02 and a SAP Kernel 722.

First thing, we have followed the SAP documentation explained here. There is a schema that mentions the SAP note 2485474. We followed all the content of this note including the modification of the ICF services that are executed in the bakc-end (/sap/bc/se/m, /sap/bc/se/rg and /sap/bc/personas3).

For the configuration of the SAP web dispatcher we created a back-end route only for the /sap/bc/se/rg and the /sap/bc/personas3 for all other routes they address the front-end server. This means that we also had to implement the Personas addon on the front-end, that delivers the SAP URL /sap/bc/se/m/script/sap/se/ui as described in the documentation concerning the SAP Fiori target.

We were facing an issue when executing the /sap/bc/se/rg URL with an ITS_P:019 XSRF no sec_sesstoken error. In fact this problem came from the level of the Front-End Kernel which was at level 401 and not the recommended level 500. We implemented the PL level 600 instead and now everything works smoothly. 🙂

But there is a limitation, based on the target mapping definition explained in the documentation, you can only connect one back-end for the Slipstream Engine. We hope that it will evolve in the near future. We need to connect three bakc-ends, 😞

I hope, this could help anyone who wants to integrate a back-end personas Slipstream app in a SAP Fiori Launchpad front-end tile.

[tamas_hoznek]

Perhaps using external aliases may help in setting up more than one backend?

[fxlevy]

Hello, after reading the documentation, what i have understood is that with the SAP Web Dispatcher configuration, the SlipStream Engine will be executed from only one back-end server. We have three back-ends which must be connected, an ECC on an ABAP 702, an EWM on a 750 and a S/4HANA on a 750. We are able to deliver FIORI Apps for those three back-end servers by defining three RFC and apply them to the ODATA services on the Gateway part of the Front-End server. But for the SlipStream engine, i don't see that the same possibility is offered, meaning connect the three Slipstream Engines of the bakc-end servers from the Front-End server. Is it possible to define three rules in the SAP Web Dispatcher to access the different SlipsStream Engine of each back-end server centrally using three different targets in the SAP Fiori Launchpad Designer Cust?

[fxlevy]

Oups, i'm terribly sorry and missed your answer. Based on the documentation entry point you sent we are in the situation where the backend iq in a lower stack than a 753 Kernel version. I need the help of our SAP basis team to proceed with the SAP Web Disptacher. I take the point and keep you inform. Anyway many thanks for the feedback.

[tamas_hoznek]

Does this help?