cancel
Showing results for 
Search instead for 
Did you mean: 

Fiori Launchpad without Portal

Sharathmg
Active Contributor
0 Kudos

Hi All,

I am looking for inputs from SAP Experts on the scenario where we use Fiori Launchpad without Portal.

Fiori Lanuchpad will host set of Apps and the user management will be handled in the backend Gateway and ECC system.

Portal is not being considered in the solution as it does not exist in the landscape.

Can you help me understand the risks with this approach and advantages, if any.

Thank you.

Regards,

Sharath

Accepted Solutions (1)

Accepted Solutions (1)

Sharathmg
Active Contributor
0 Kudos

Closing this thread as it is clear that Fiori Launchpad is positioned as standalone entry point for SAP Users.

Once again, thank everyone for your inputs.

Regards,

Sharath

Answers (2)

Answers (2)

patrick_weyers
Participant
0 Kudos

Agreed with Michael - why would you consider adding a Portal to the landscape?

In my view, there is really no place for a Portal in a 2015 system landscape if being used as an app launcher platform - other than for legacy reasons.

Sharathmg
Active Contributor
0 Kudos

Does it imply that going forward, it is recommended to avoid Portal and go all alone with Fiori Launchpad?

Will it not clash with Portal and result in mutiple entry points for users?

Regards,

Sharath

former_member182874
Active Contributor
0 Kudos

Hi Sharath

Portal is indeed not dead and cannot be. Fiori is a new user experience, In cases where you have portal as well and you want to reuse it. You can very well integrate with Fiori launchpad. Yes like Michael said, you save lot of efforts by chosing fiori ux if you have choice between portal and fiori.

If there is a confusion on whether to go with portal and fiori both/ Fiori alone. FIORI alone will suffice your requirement.

SAP can't scrap portal, for customers who are already live with portal can use fiori as well. Portal is specific for desktop use whr customer wants to use the usecase with 100 fields and achieve complex scenarios. FIORI on other hand are light weight applications, which requires tasks to be run through mobile/tab/desktop or on the fly.

So based on design thinking approach, you can make ui5 apps which can run on desktops and have highly used or mandt fields

Regards

Tejas

gill367
Active Contributor
0 Kudos

Hi Sharath;

This is an important link.

What is the impact of Fiori on your SAP Portal?

In our organization we have linked portal to SAP NetWeaver Frontend server. Only reason we did that was because users were already using SAP Portal and we dint want them to remember two passwords or two links to access important information. Having one single gateway was the only reason.

Otherwise SAP Fiori alone is Sufficient and there are no risks involved.

Regards,

Sarbjeet Singh 

Sharathmg
Active Contributor
0 Kudos

Thanks to all your replies.

It is pretty clear now that SAP is moving in the direction of SAP Launchpad with the view better UX. I only feel that this could lead to another set of recreating of apps in older SAP technologies(WD Java, WD ABAP etc.) in UI5 to facilitate integration into Launchpad.

Regards,

Sharath

0 Kudos

Hi Sharat,

What do you mean with risks? There are no risks when you implement Fiori well. If you don't use the Portal you even save a lot of portal admin work.

Please check the page. There you will get all the necessary information about installing Fiori.

Best regards,

Michael Albrecht