--- title: Connect Your SAP BTP Trial Account to SAP S/4HANA for Content Consumption description: Set up SAP Cloud Connector to give your SAP BTP trial subaccount access to the SAP S/4HANA system that you configured for content exposure in the previous tutorial and create runtime and design-time destinations for the SAP S/4HANA system on SAP BTP. auto_validation: true time: 15 tags: [tutorial>beginner, software-product>sap-connectivity-service, topic>abap-connectivity, software-product>sap-business-technology-platform, software-product>sap-fiori, software-product>sap-launchpad-service, software-product>sap-build-work-zone--standard-edition, software-product>sap-build-work-zone--advanced-edition] primary_tag: software-product>sap-build-work-zone--standard-edition parser: v2 slug: cp-launchpad-federation-connectivity canonical_url: https://developers.sap.com/tutorials/cp-launchpad-federation-connectivity --- ## Prerequisites - You have an SAP BTP trial account. - You have access to both an SAP Cloud Connector and an SAP S/4HANA demo/test system that you want to connect to your SAP BTP trial account. These systems might be provided to you by the instructor in a workshop or you might have set them up from the SAP Cloud Appliance Library yourself. Please make sure that you have the server names, ports and a user and password available. The screenshots in this tutorial were taken from an SAP S/4HANA 2023 FPS01 system, but an older system, e.g. 2020, would work mostly in the same way. ## You will learn - How to setup connectivity on SAP Cloud Connector - How to create runtime and design time destinations for content federation --- ### Open SAP Cloud Connector 1. Open the URL of your SAP Cloud Connector in Chrome. > In your SAP S/4HANA trial CAL system, you can access it by connecting via Remote Desktop Connection. You can find the link to the SAP Cloud Connector and the initial password in the Welcome page that can be accessed via the **Welcome** Chrome icon on the desktop. 2. Enter your `user name` and `password` and click **Login**. ![SAP Cloud Connector Login](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/1-scclogin.png) 3. If required, enter a new password. ### Connect your SAP BTP trial subaccount If this is the first time SAP Cloud Connector is started, you will see the **Define Subaccount** page. Otherwise, the Connector Overview page opens. 1. If you see the Connector Overview Page, click **Add Subaccount** to add your SAP BTP trial account. ![Connector Overview](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/2b-scc-define-subaccount.png) Otherwise, you can directly start entering the details of your SAP BTP trial on the **Define Subaccount** page. ![Define subaccount](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/2a-scc-define-subaccount.png) 2. To find the right information to enter into SAP Cloud Connector, access your SAP BTP trial in a second browser tab at . 3. Click **Go To Your Trial Account**, then click the **trial** tile. ![Trial subaccount](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/22b-btp-go-to-trial.jpg) 4. You can find the required information to enter in the SAP Cloud Connector form on this Overview page. You can identify the region, the provider and the subaccount ID in the **General** section. Copy the region, e.g. US East (VA). ![BTP Cockpit Overview](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/5c-btp-cockpit-overview.png) 5. Go back to the SAP Cloud Connector tab. In the form, click the Select icon in the **Region** field. ![Select icon](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/4a-scc-selectoricon.png) 6. Paste the region of your trial account and select the right entry in the list. Make sure you select the right provider (hyperscaler). ![Select region](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/4b-scc-selectregion.png) 7. Go back to the BTP Cockpit Overview page and copy the ``subaccount ID`` into the **Subaccount** field. 8. Enter an easily identifiable display name, e.g. your SAP BTP trial's subdomain into **Display Name**. 9. Enter the ``email address`` and ``password`` that you use to login to your SAP BTP trial into **Login E-Mail** and **Password**. 10. If you have attached another SAP Cloud Connector to your SAP BTP trial account already, enter any unique **Location ID** here to distinguish this SAP Cloud Connector from the existing one. Otherwise, you can leave this field empty. ![Add Subaccount dialogue](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/6a-scc-add-dialogue.png) 11. Click **Save**. You have connected your trial subaccount and can now see it in the subaccount dashboard. The status is still yellow, as backend access has not been configured yet. ![Show Subaccount dashboard](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/7-scc-subaccount-dashboard.png) ### Configure SAP Cloud Connector to trust the SAP S/4HANA system In this step, you configure the SAP Cloud Connector to trust all backend systems. This configuration ignoring the allowList is considered less secure, since all server certificates are trusted and the issuing CA is not checked. As a result, certain attacks on the hop between Cloud Connector and internal systems can be performed more easily. Therefore, we strongly recommend that **you don't do this in productive installations**. 1. From the left panel, choose **Configuration** in the **Connector** section. ![Click Configuration](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/30-open-configuration.png) 2. Go to the tab **On Premise**. ![Tab On-Premise](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/31-open-tab-on-premise.png) 3. Scroll down to the **Backend Trust Store** section and change the switch next to **Determining Trust Through Allowlist** to **Off**. ![Tab On-Premise](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/32-allowlist-off.png) ### Configure access control Now, you will specify the on-premise backend system that your trial should be able to access. 1. You can see that the newly connected subaccount is already selected in the lower part of the menu on the left side of the screen. Click **Cloud To On-Premise** below the name of your subaccount. ![Cloud-to-On-Premise](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/8b-scc-cloud-to-onpremise.png) 2. Click the **plus** icon on the **Access Control** tab to add your on-premise system. ![Add System](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/9-scc-add-system.png) 3. Keep the default **``ABAP System``** and click **Next**. ![Select backend type](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/10a-scc-backend-type.png) 4. Select **``HTTPS``** as protocol for communication with your on-premise system and click **Next**. ![Select protocol](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/12-scc-protocol.png) 5. Enter the internal host name of your SAP S/4HANA system and the internal port. If you are using a system from the SAP Cloud Appliance Library (CAL), you can find the IP address in the details of your instance. The port is 44300 in this case. Then click **Next**. ![Enter internal host](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/13b-scc-internal-system.png) ![IP End Point](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/13b-ip-end-point.png) 6. Enter **``s4hana``** as **Virtual Host** and **`44300`** as **Virtual Port** and click **Next**. > You can choose any virtual host name and port here, but you need to reuse the ones defined here when creating a destination later. ![Enter virtual host](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/14-scc-virtual-system.png) 7. In the next screen, deselect the checkbox next to *Allow Principal Propagation*, then click **Next**. ![Deselect principal propagation](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/15a-deselect-pp.png) >In a productive environment, we highly recommend that you use Principal Propagation or some other more advanced authentication concepts. In this tutorial, we just use the quickest and simplest approach for the sake of time. 8. Just keep the default and click **Next**. ![Keep default](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/15b-no-system-certificate.png) 9. Click **Next**. ![Keep default](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/16-scc-host-in-header.png) 10. If you want, enter a description. Then click **Next**. 11. In the summary, check the **Check Internal Host** checkbox and click **Finish**. ![Summary screen](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/17a-scc-summary.png) You now see a new entry in the mappings table. The icon in the **Check Result** column should be green, but the status is still grey, as no accessible resources have been defined yet. ![System Mapping Overview](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/18a-scc-system-mapping.png) ### Add resources 1. In the lower table **Resources of s4hana:44300** click the **plus** icon. ![Add icon](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/19a-scc-add-resources.png) 2. Enter **`/`** in **URL Path**. ![Enter URL](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/20-scc-add-resource-path.png) > Usually you would define this in a more fine granular way, but since this is just a demo system, we will keep it simple. Below you can find the default pathes which you should restrict even further according to your usage. | Path to fetch... | Value | :------------- | :------------- | Card manifests and i18n files | `/sap/bc/lrep/` | The UI5 App Index | `/sap/bc/ui2/app_index/` | CDM3 content | `/sap/bc/ui2/cdm3/` | Data from OData services | `/sap/opu/odata/` | Data from OData V4 services | `/sap/opu/odata4/` 3. Select **``Path And All Sub-Paths``** in **Access Policy**. 4. Click **Save**. You now see a new entry in the lower table and the status of the entries in both tables should be green. SAP Cloud Connector configuration is now finished. You can leave the SAP Cloud Connector now. ![summary screen](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/21a-scc-ac-summary.png) ### Create the design-time destination The design-time destination is used to fetch the federated content from the content provider system during design-time. 1. Go back to the browser tab with your SAP BTP trial subaccount Overview page. 2. In the menu, navigate to **Connectivity** > **Destinations**. ![Go to Destinations](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/23b-btp-goto-destinations.png) 3. Click **Create Destination**. ![Destination screen](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/24b-btp-new-destination.png) 4. Fill in the form: | Field Name | Value | :------------- | :------------- | Name | `s4hanadt` | Type | `HTTP` | Description | `SAP S/4HANA system` | URL | `http://s4hana:44300/sap/bc/ui2/cdm3/entities` | Proxy Type | `OnPremise` | Authentication | `BasicAuthentication` | User | `` | Password | `` If you entered a Location ID in SAP Cloud Connector, enter the same value here in **Location ID** as well. 5. Click **New Property** to add an additional property to your destination. ![Design-time Destination](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/25b-btp-designtime-destination.jpg) 6. Enter ``sap-client`` and the client of your SAP S/4HANA system, e.g. 100 for SAP S/4HANA trial (CAL) systems, as property name and value. 7. Click **Save**. ![Additional property](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/25c-btp-designtime-destination.jpg) ### Create the runtime destination The runtime destination is used to launch federated applications at runtime. 1. Below the destination that you just created, click **Clone**. ![Clone Destination](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/26a-btp-clone-destination.png) 2. Change the **Name** of the new destination to **`s4hanart`**. 3. Change the **URL** to **`http://s4hana:44300`** . 4. Enter the password again. 5. Click **New Property** to add the following properties to your destination. You can **type in the property name, if it is not available in the dropdown list**. | Property Name | Value | :------------- | :------------- | HTML5.DynamicDestination | `true` | sap-platform | `ABAP` (type the property name) | sap-service | A string that consists of the first two characters 32 and the instance number of the ABAP application server, **3200** for your CAL system (type the property name) | sap-sysid | `` - **S4H** for your CAL system (type the property name) 6. Click **Save**. ![Runtime Destination](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-launchpad-federation-connectivity/27c-btp-runtime-destination.jpg) ---