Set SAP BTP, ABAP Environment as a Content Provider for SAP Launchpad Service

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

2. Create a new communication system.

   • System ID and System name: COMMSYS_CONTENTFEDERATION_DEMO

   • Host Name: Callback URL, which is needed for setting up content change notifications. For example, for region EU10, the URL is portal-service.cfapps.eu10.hana.ondemand.com.

   • Port: 443

   

3. Add a technical user for inbound communication.

   
   • Choose authentication method User Name and Password.
   

   • User Name: COMMUNICATIONSYSTEM_INBOUND_USER

   • Description: Inbound user for communication system

   • Let the system generate a password. Do not forget to note the password for later use in Step 6 (Create Design-Time destination).

   

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

   

5. To save the communication system, select Save.

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

2. In the New Communication Arrangement dialog choose communication scenario SAP_COM_0647.

3. Select Create.

4. In the Common Data section, set the following values

   • Arrangement Name: SAP_COM_0647

   • Communication System: COMMSYS_CONTENTFEDERATION_DEMO

   • Logical Target Identifier: LNCHPD_INTG_TGT

   

5. Enter the job execution details for scheduling the SAP Fiori Launchpad content exposure job every 10 minutes.

6. Select Save.

1. In the Maintain Business Roles app, search for business role ID SAP_BR_ADMINISTRATOR.

2. Select business role SAP_BR_ADMINISTRATOR.

3. Choose Expose to SAP Launchpad Service.

   

The content related to the exposed business role, such as groups, catalogs, pages, or spaces, can be consumed by the SAP Launchpad service as soon as the job, which you have configured in the previous step, has run successfully.

1. In the SAP BTP cockpit, download the trust certificate of the subaccount runtime destinations by navigating to Connectivity > Destinations.

2. Select Download Trust.

   

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

4. Create a new communication system by setting the following values.

   • System ID: SUBACCOUNT_SYSTEM_COMMUNICATION

   • System Name: SUBACCOUNT_SYSTEM_COMMUNICATION

   • Select Inbound only

   • Set SAML Bearer Assertion Provider to ON

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

   • Enter the value of the certificate’s CN attribute as SAML Bearer Issuer.

   

5. To save the communication system, select Save.

1. Open the Maintain Protection Allowlists app from the SAP Fiori launchpad in your SAP BTP, ABAP environment system.

2. On the Clickjacking Protection tab page, choose Create to add a new host. On the Add Trusted Host screen, enter the following data:

   • Trusted Host Name: <subdomain>.launchpad.cfapps.<region>.hana.ondemand.com

   • Schema: HTTPS

   • Port: 443

3. Select Save.

You create a design-time destination to define the location from which the SAP Launchpad service should fetch the exposed content.

1. Navigate to the subaccount in which you have subscribed to the SAP Launchpad Service.

2. In the Connectivity menu, choose Destinations.

3. Create a new destination and fill in the following fields:

   • Name: Tutorial_dt

   • Type: HTTP

   • Description: Design-time destination for tutorial

   • URL: Use the service URL of section Inbound Services in the communication arrangement created in Step 2 (Create the Communication Arrangement). Add suffix entities.

   

   • Proxy Type: Internet

   • Authentication: BasicAuthentication

   • User: COMMUNICATIONSYSTEM_INBOUND_USER (Created in Step 1 (Create a Communication System))

   • Password: Maintain password created in Step 1 (Create the Communication System).

   The destination should look like this:
   

   

4. Select Save.

1. Create a new destination and fill in the following fields:

   • Name: Tutorial_Ressources_rt

   • Type: HTTP

   • Description: Tutorial: Runtime destination for ressources

   • URL: Fiori Launchpad URL of the SAP BTP, ABAP environment system

   • Proxy Type: Internet

   • Authentication: NoAuthentication

   • Additional Properties: (Select New Property to add new items)

     • HTML5.DynamicDestination: true

     • sap-platform: ABAP

2. Select Save.

Finally the destination should look like this:

1. Create a new destination.

   • Name: Tutorial_dynamic_OData_rt

   • Type: HTTP

   • Description: Tutorial: Dynamic runtime destination for OData access

   • URL: SAP Fiori Launchpad URL of the SAP BTP, ABAP environment system. Replace abap-web with abap. Format: https://<tenant>.**abap**.<region>.hana.ondemand.com

   • Proxy Type: Internet

   • Authentication: SAMLAssertion

   • Audience: SAP Fiori Launchpad URL of the SAP BTP, ABAP environment system

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

   • Additional Properties: (Select New Property to add new items)

     • HTML5.DynamicDestination: true

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

2. Select Save.

The destination should look like this:

1. Before you create the content provider, make sure the content is available. The content is synchronized every 10 minutes, as configured in step 2. It can take up to one hour until the first synchronization run is scheduled. To check the availability of the content, open the Display Launchpad Content Exposure Logs app from the SAP Fiori launchpad in your SAP BTP, ABAP environment system. Once everything has been synchronized successfully, the content is available for consumption.

2. From the subaccount, navigate to Services > Instances and Subscriptions and search for the Launchpad Service in the search box

3. Access Launchpad Service.

4. Select Provider Manager.

5. Create a new content provider.

   

6. Add title, description, ID, and the destinations created in Step 6-8 (Create Design-Time / Runtime destination) accordingly:

   • Title: Tutorial

   • Description: Content Provider tutorial

   • ID: Tutorial

   • Design-Time Destinations: Tutorial_dt

   • Runtime Destination: Tutorial_Ressources_rt

   • Runtime Destination for OData: Tutorial_dynamic_OData_rt

   • Content Addition Mode: Manual addition of selected content items

7. Select Save.

   The content provider should look like this:

   

In the Status column of the table the status changes to Created as soon as the creation is finished.

1. Navigate to the Content Manager.

2. Open Content Explorer tab, where all the already created content providers are listed.

3. Select the content provider you have created in the previous step.

4. Select the Administrator content item and choose Add to My Content.

   

1. Navigate to the Site Directory.

2. Select Create Sites.

3. Choose a site name and select Create.

4. Select Edit and move your cursor to the search box to Search for items to assign.

   

5. Choose the Administrator role (select +).

6. Select Save.

7. Copy and store the URL of the launchpad for later use.

   

Now you have assigned the business role, that is exposed to the SAP launchpad service, to your launchpad site. With the business role all apps that are related to this business role will be available on the launchpad site. Also, a role collection is created, which is labeled according to this format: <Content Provider name>_<Business Role name>

To access the launchpad site you have to assign the role collection created in the previous step, to your SAP BTP, ABAP environment user in the SAP BTP cockpit.

1. Open the SAP BTP Cockpit and navigate to the subaccount of the SAP Launchpad service.

2. Navigate to the Users menu.

3. Search for your user and select it.

4. Choose Assign Role Collection in the Role Collection section (depending on your window size, you might have to select ... first).

5. Assign the created role collection ~tutorial_SAP_BR_ADMINISTRATOR to the user.

   

1. With your user, access the launchpad site via the URL stored in Step 11.

2. Log off and log on again. This makes sure the newly assigned role collection is taken into account.

The launchpad site should look like this. The groups might be in different order: