SAP BTP, ABAP system as Content Provider for SAP Launchpad Service

• Open the Communication Systems app from the SAP Fiori Launchpad in your SAP BTP, ABAP environment system.

• Create a new Communication system.

• Specify System ID and System Name for the new Communication System.

• In the field Host Name enter the callback URL. This is needed for setting up content change notifications. For example portal-service.cfapps.eu10.hana.ondemand.com.

  

• Add a technical user for inbound communication.

  

  

• Authentication method is User Name and Password. Let the System generate a Password. Do not forget to note the password down. It will be used in Step 5 (Create Design-Time destination).

• Similarly add a technical user for outbound communication with Authentication Method None.

  

• Open the Communication Arrangements app from the SAP Fiori Launchpad and select New.

• In the New Communication Arrangement app choose Communication Scenario SAP_COM_0647 for creation.

• Press Create.

• In the “Common Data” section set the Communication System created before using the value help.

• Enter the job execution details for scheduling the FLP Content Exposure job every minute and press Save.

• Open the Maintain Business Roles app.

• Search for Business Role ID SAP_BR_ADMINISTRATOR.

• Mark Business Role SAP_BR_ADMINISTRATOR.

• Click Expose to SAP Launchpad Service.

The content related to the Business Role, such as groups, catalogs, pages or spaces can then be consumed by the SAP Launchpad Service.

• In the SAP BTP Cockpit download the trust certificate of the subaccount runtime destinations, by navigating to Connectivity -> Destinations. Press the Download Trust button.

  • Open the Communication Systems app from the Fiori Launchpad in your SAP BTP, ABAP environment system.

  • Create a new Communication system.

  • Specifiy the System ID and System Name for the new System.

  • Select Inbound only.

  • Set SAML Bearer Assertion Provider to ON.

  • Upload the certificate file that you downloaded from your subaccount as the Signing Certificate.

  • Specify a unique Provider Name in the following format: cfapps.<**region**>.hana.ondemand.com/<unique_name>

  • Save the communication system.

We will create the design-time destination in order to define the location from which the SAP Launchpad service should fetch the exposed content.

• Go to the subaccount in which you want to use the Launchpad Service.

• Choose Destinations in the Connectivity menu item.

• Create a new Destination.

URL:

• Use Service URL of section Inbound Services in the Communication Arrangement created in Step 2 (Create the Communication Arrangement).

• Add suffix /entities.

• Format: https://<guid>.abap.<region>.hana.ondemand.com/sap/bc/http/sap/aps_flp_content_exposure/entities

Authentication: BasicAuthentication.

User: Inbound user with its password created in Step 1 (Create the Communication System).

Click “Save”.

Create a new Destination.

URL: Use the domain of the Service URL in section “Inbound Services” in the Communication Arrangement created in Step 2 (Create the Communication Arrangement). Replace abap with abap-web. (Format: https://<tenant>.abap-web.<region>.hana.ondemand.com)

Additional Properties:

Click on New Property to add new items.

HTML5.DynamicDestination: true

sap-platform: ABAP

Click “Save”.

URL: Use the domain of the Service URL in section “Inbound Services” in the Communication Arrangement created in Step 2 (Create the Communication Arrangement). Format: https://<tenant>.abap.<region>.hana.ondemand.com

AuthnContextClassRef: urn:oasis:names:tc:SAML:2.0:ac:classes:PreviousSession

Additional Properties:

HTML5.DynamicDestination: true

nameIdFormat: urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress

Click “Save”.

• From the subaccount, navigate to Services, Instances and Subscriptions and search for the Launchpad Service in the Search box

• Access Launchpad Service.

• Go to Provider Manager.

• Create a new Content Provider.

  

• Add Title, Description, ID and the Destinations created in Step 5-7 (Create Design-Time / Runtime destination) accordingly.

  

• Click “Save”.

In the Status column of the table the status will be set to Created as soon as the creation is finished.

• Navigate to the Content Manager.

  • Open Tab Content Explorer. Here all the created Content Providers are listed.

  • Click on the Content Provider created in the previous Step.

  • Mark the item with Title Administrator and click Add to My Content.

  

• Navigate to the Site Directory.

  • Click Create Sites.

  • Choose a site name and click Create.

  • Click Edit and click into the box to Search for items to assign.

  

  • Choose the Administrator role (click on +).

  • Click Save.

  • Copy and store the URL of the Launchpad for later use.

  

Now you assigned the Business Role, which you exposed to the Launchpad Service, to your Launchpad Site. With it all apps that are related to this Business Role will be available in the Launchpad Site. Also a Role Collection is created, which is named in this format: <Content Provider name>_<Business Role name>

In order to be able to access the Launchpad Site you have to assign the Role Collection created in the last Step, to the SAP BTP, ABAP environment user in the SAP BTP Cockpit.

• Open the BTP Cockpit.

• Go to the subaccount, of the Launchpad Service.

• Navigate to the Users menu.

• Search for and mark the BTP user of the SAP BTP, ABAP environment.

• Click on Assign Role Collection in the Role Collection section (might be hidden behind the ..., dependent on the window size).

• Assign the created authorization to the user.


Now access the Launchpad Site via the URL stored in Step 10 with the SAP BTP user you assigned the Role Collection to in Step 11.