Content Federation from SAP Business Suite is now available
There is good news for all those who are looking for an easier and more efficient way to integrate larger amounts of SAP Fiori launchpad content from an SAP Business Suite system to a central launchpad running on SAP BTP, Cloud Foundry environment. With SP04, SAP Fiori Front-End server 6.0 now also supports content federation. With this new capability, it is no longer necessary to integrate SAP Business Suite applications manually into a launchpad running on SAP BTP one by one, but administrators can make complete roles with all their apps, catalogs, and groups available in one step.
What is content federation about?
With content federation, SAP solutions such as SAP S/4HANA and the SAP Business Suite can serve as content providers for a central launchpad. An administrator of a content provider system selects and exposes business roles with their assigned catalogs, groups, and applications. This preconfigured content can be consumed by the SAP Launchpad service, the SAP Cloud Portal service and SAP Work Zone in a very easy and efficient way – making the day-to-day operations and maintenance by the content administrator much more effortless.
How does it work?
The content exposure in the SAP Business Suite system works exactly like in SAP S/4HANA. Administrators use transaction /ui2/cdm3_exp_scope to select the roles for exposure, trigger or schedule the exposure process and access exposure logs.
On the SAP Business Technology Platform side, a new content provider needs be to be created in the respective service (SAP Launchpad service, SAP Cloud Platform service or SAP Work Zone) based on SAP BTP destinations. Administrators can then either manually select roles or automatically add all exposed roles to the My Content area to make them available for usage in a site or work zone.
Where can I find additional information?
You can find detailed information on how to expose SAP Fiori launchpad content using SAP Fiori front-end server 6.0 in the documentation. To learn more about the end-to-end process of content consumption, please see Federation of Remote Content Providers.
Please see also the SAP note 3057822 detailing the current restrictions related to exposing SAP Business Suite content to the SAP Launchpad or SAP Cloud Portal service via content federation.
To understand the end-to-end configuration flow for content federation (using the example of an SAP S/4HANA system), please check out the tutorial Enhance Your SAP Launchpad Site with Federated SAP S/4HANA Content.
Good to see content federation capability now available for SAP Business Suite.
Thanks for this introduction. How does this scenario work with customer extensions of Fiori apps? Can they be directly enhanced on the BTP or on the S/4 FES and then consumed by the service?
yes, you can either create side-by-side extensions, deploy them to BTP, and integrate them to the Launchpad on BTP or you do in-app extensions in the ABAP system. With content federation, the app is still located in the provider system, so you can have the extended app running in an iFrame on the Launchpad on BTP.
just for my own clearification: an app is published via content federation on BTP but actually runs on S/4 system. This app need some extensions and enhancement. So the extension project can be direcly deployed to BTP and is smart enough to realize that the extended app actually runs on some S/4 backend system?
Thanks and best regards
the documentation link regarding exposing SAP Fiori launchpad content using SAP Fiori front-end server 6.0 doesn't work. Any idea where to find the current SAP documentation?