All the properties that you entered with the wizard are still available via the iView property editor under the category ‘Content – Fiori’
Once this is done you can preview the iView. Minimal Header – You will have the FLP header with functions that match embedded mode, personalization will be enabled (supported as of ABAP add-on SP9). No Header – you will not see the FLP header, personalization will be off (disclaimer: supported as of ABAP Add-on SP10). SAP Fiori Application Header: You can choose one of the following:. If you leave this field blank you will simply get the SAP Fiori Launchpad (FLP). Parameters to Pass on the Location String in the URL: Shell-runStandaloneApp?sap-ushell-SAPUI5.Component=&sap-ushell-url=/sap/bc/ui5_ui5/sap/crm_opprtnty. Relative Path for SAP Fiori Application: sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html. System: WEBSIDP (this is the system alias we defined before). In the next screen, fill in the details as follows (according to the example):. Go through the wizard, choose a name for your iView, and then click Next. In Content Administration, create a new iView from template and select SAP Fiori iView. You can set other properties too according to your needs. Set the system HTTP Security Session to be on. Enter the following mandatory settings for this system object:. This system will actually points to on the same URL we are using to access the portal – the web dispatcher. Create a system object and give it an alias, such as ‘WEBSIDP’. Shells/abap/FioriLaunchpad.html?sap-client=123#Shell-runStandaloneApp?sap-ushell- SAPUI5.Component=&sap-ushell-url=/sap/bc/ui5_ui5/sap/crm_opprtnty Steps Since the web dispatcher is already set up it also can be accessed from: The Fiori app can be accessed directly from: ushell/shells/abap/FioriLaunchpad.html?sap-client=123#Shell-runStandaloneApp?sap-ushell- SAPUI5.Component=&sap-ushell-url=/sap/bc/ui5_ui5/sap/crm_opprtnty #SETTING UP UNWRELLA IN MAYA 2014 HOW TO#
So, How to Integrate a Fiori Application into Portal When the URL matches the /sap/bc template, it accesses server A.įor the client, it seems as if, both the portal and the Fiori application are on the same server. When the URL contains /irj/portal it actually accesses server B.
The client always uses server C (the web dispatcher). Server C is our web dispatcher and its URL is:. We need to access both servers via the same URL. 
Server B is our portal server and its URL is:. How to configure a web dispatcher (example) This can be achieved by using a SAP Web Dispatcher. You have made sure that both the portal server and the ABAP server can be reached via the same URL (including the server name). Your back-end server has SAP Fiori Launchpad SP 8 or above. By using this iView, you will be able to call a specific Fiori application running on an ABAP back-end system and run it within the portal framework. We have created a new iView template in the portal: SAP Fiori iView. Standard use of the Application Integrator (UI5 iView) is not possible – precisely because of the problems listed above. Extra parameters need to be forwarded to the application to ensure it runs in standalone mode. Fiori applications are protected against click-jacking attacks this prevents them from being rendered in an iFrame. Therefore, a simple form submission is not sufficient here. Fiori (Wave II and above) applications are called via a URL location fragment. See details in SAP Note # 2103156 What’s the Problem?Īctually there are a few problems we need to address: ℹ This capability is applicable only for a subset of Fiori transactional applications, which are self-contained in nature and do not require contextual services. In only a few steps you can easily add a SAP Fiori application to Portal. This blog post is for portal developers and administrators who would like to learn about the tasks required to integrate SAP Fiori applications in Portal. The purpose of this blog post is to explain and demonstrate how to integrate an SAP Fiori application into SAP Enterprise Portal.
0 kommentar(er)
