Configure Your SAP S/4HANA System for Content Federation

1. If you are using your own instance of the SAP S/4HANA, Fully Activated Appliance solution in SAP Cloud Appliance Library, click Connect.

   

2. You can either use the Windows Remote Desktop and login via SAP Logon there or login directly via SAP GUI by clicking Connect in the SAP GUI row in the Connect to the Instance pop-up . Please check the Getting Started with the SAP S/4HANA 2020 (SP00) Fully-Activated Appliance Guide for details.

   

3. An .sap file will be downloaded to your computer to connect to the SAP S/4HANA system.Click the downloaded file. If required, click Allow in the pop-up window.

   

4. Login to client 100 of system S4H with default user BPINST and password Welcome1.

   

Since the SAP S/4HANA apps are integrated into SAP Build Work Zone using iFrames, you need to configure an allowlist to protect your system against clickjacking attacks. The allowlist service is an ABAP-wide service to implement protections. You can manage such allowlist scenarios with the Unified Connectivity Framework (UCON Framework) to optimize the protection of your RFC and HTTP(S) communication against unauthorized access.

To allow SAP Build Work Zone to consume data from your SAP S/4HANA system, you should add your trial account to the allowlist for Clickjacking Framing Protection.

If you do not activate the allowlist, SAP Build Work Zone defaults to a more restrictive clickjacking protection mechanism. It will then only allow framing if the host of the application is part of the same domain as the embedding application, i.e. Work Zone (same origin policy).

Start the transaction uconcockpit.

1. In the drop-down list, select HTTP Allowlist Scenario.

   

   In older SAP S/4HANA releases, scenario names might differ.

2. If the Clickjacking Framing Protection scenario is already available in the list, you do not need to do anything here and can go directly to the next step Open SAP Fiori launchpad client-specific settings. This should be the case the SAP S/4HANA 2023 FPS01 Fully-Activated Appliance.

If not, you need to activate it. To do so, select HTTP Allowlist > Setup in the menu bar.

In the pop-up, check the entry activate Clickjacking Protection (Context Type 02) for all clients (recommended). Then click the Continue icon.

For more details, see Using an Allowlist for Clickjacking Framing Protection

You now see the Clickjacking Framing Protection entry in the table. It is currently set to Logging mode. This means that connections are only logged, but not checked. With this setting, connectivity from your SAP BTP trial account will work. However, this is not a secure setting. In a productive environment, you would need to add the patterns for your SAP Build Work Zone to the allowlist and then set the scenario to Active check mode.

The parameter EXPOSURE_SYSTEM_ALIASES_MODE defines how to handle system aliases during content exposure. In an embedded deployment of the SAP Fiori front-end server, all apps run on the same server. Therefore, system aliases can be cleared during exposure. In a hub deployment in contrast, they might come from different back-end systems and each back-end system may have several aliases. Therefore, you need to map these aliases to the runtime destinations manually after creating the content provider in the last tutorial of this group. See the documentation for details.

This parameter must only be set in an embedded scenario where the SAP Fiori front-end server is deployed into the AS ABAP of the SAP S/4HANA system. This is the case in the SAP S/4HANA trial system.

1. Enter /nspro in the command field to access the customizing.

   

2. Click SAP Reference IMG.

   

3. In the tree, open ABAP Platform > UI Technologies > SAP Fiori > SAP Fiori Launchpad Settings.

   In an older system, e.g. SAP S/4HANA 2020, the path to choose would be SAP NetWeaver > UI Technologies > SAP Fiori > SAP Fiori Launchpad Settings.

4. Then click the IMG Activity icon in front of Change Client-Specific Settings.

   

5. If you see a pop-up window informing you about a refresh of the text index, just confirm it.

   

1. Click New Entries to create one new entry.

   

2. For the new entry, make the following inputs in the first row of the table:

   FLP Property ID: EXPOSURE_SYSTEM_ALIASES_MODE

   Property Value: CLEAR

   The values in other columns, e.g. for Type and Category, will be added automatically when you save the new entry.

3. Click Save.

   

   To save your settings, you need to assign a customizing request.

4. Click the Create icon to create a new customizing request.

   

5. If you want, enter a description. Then click the Save icon.

   

6. Click the OK icon to confirm using the newly created customizing request.

   

7. Your entry was saved. Click the Display button to go back to the main settings table.

   

Now you made all settings required in the SAP S/4HANA trial system.

If you work in your own SAP S/4HANA test system or just want to make sure all prerequisites for content exposure are met, you might check if the service /sap/bc/ui2/cdm3 is activated in the SAP S/4HANA system. This is the case in the preconfigured SAP S/4HANA trial.

1. Enter /nsicf into the command field to launch transaction SICF.

2. Enter cdm3 in Service Name and click the Execute icon.

   

3. Right-click the cdm3 service. Check that the Activate Service entry is grey and inactive. This means that the service is already activated. Otherwise, you can activate it now by clicking Activate Service.

   

You also need to make sure that the user which does the content exposure has the right role and that the page cache is turned on for them. This is also already the case for user bpinst.

1. Enter /nsu01 into the command field to launch User Maintenance.

2. Enter the bpinst as User as this is the user that will do the content exposure. Then click the Display icon.

   

   The permissions to run the content exposure are delivered with the role SAP_FLP_ADMIN. The BPINST user has full administrator permissions and can be used for content exposure.

3. Go to tab Parameters and make sure that the parameter /UI2/PAGE_CACHE_OFF does not show up here. If it does, remove it.

   

This parameter is only used for test purposes to identify caching issues. It should not be available in productive systems anyhow, as it can slow down the loading process significantly.