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.
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 HTTP system in the Portal
In the Portal system landscape, I created a new HTTP system 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.
Step 3: Create a URL iView
In Portal Content Management, I created a new iView of type URL iView. I entered the relative path at URL: /sap/bc/personas and checked the Use system in URL box to include the system information of my PersonasHTTP in the URL.
The following URL parameters are important:
- sap-personas-flavor: ID of my flavor
- sap-user: Set to Mapped User
- sap-password: Set to Mapped Password
- ~transaction: The transaction for which the flavor was created
- sap-client: Client of the SAP system
- sap-language: My login language
To hand over the user parameters with the URL, the Portal as well as the Personas system have to be configured for SSL.
To make the iView visible in Fiori Launchpad, I had to set some properties in addition (will be described in my next blog) and to assign it to one of my Fiori Launchpad roles.
Step 4: Create user mappings
In Portal User Administration, I mapped the Portal user to the Personas system user.
And here we go:
Hope that was useful.