Some parts of this blog post are out-of-date and have to be changed. In particular, the recommended iView type for SAP Screen Personas is the Transaction iView. A complete update will come as soon as possible.
when preparing a demo system for TechEd, we set up a Fiori Launchpad running on Enterprise Portal (blog to follow). To complete the demo, we planned to add a transaction edited using SAP Screen Personas to the Portal. I found a nice blog by Peter Spielvogel about the integration, but then noticed that this is on SAP Screen Personas 2.0, while our systemwas on 3.0.
Here is a description about how to integrate a transaction edited with SAP Screen Personas 3.0 into the Portal. I first published this blog describing the integration using a URL iView. This worked fine – however, the recommended way is to use an Application Integration iView for UI5 applications.
Therefore, you will find the adapted description below now:
Step 1: Get the flavor ID in the Personas System
Go to SAP Screen Personas Flavor Maintenance (TA code /PERSONAS/FLAVORS) and search for your flavor. I used the transaction for which I had created the flavor to search.
In the results screen, you find the ID of the flavor.
Step 2: Create an SAP system in the Portal
In the Portal system landscape, I created a new SAP system (using dedicated application server) to connect to the SAP Screen Personas system and gave it an alias. Next, I assigned end user permissions for my new system to the Fiori Launchpad user. Then I established trust between the Personas system and the Portal.
Step 3: Create a UI5 iView
In Portal Content Management, I created a new UI5 iView.
Copy the UI5 template, then select a folder under Portal Content and click Paste as PCD Object.
Give your new iView a name.
In the iView properties, I made the following settings:
Relative Path for UI5 Applications:/sap/bc/personas?~transaction=<transaction_to_be_launched>&sap-personas-flavor=<ID of the flavor I created>
System: Alias of myPersonas system
Application Parameters: sap-ie=Edge (UI5 applications need to run in standard mode)
Launch in New Window: Display in separate headerless portal window (standard mode)
To make the iView visible in Fiori Launchpad, I had to set some properties in addition (see Shani’s blog on Sample content for Fiori launchpad for Portal or mine on Mobile Portal with Fiori Launchpad) and to assign it to one of my Fiori Launchpad roles.
And here we go:
Hope that was useful.