## 5.1 Configuring an HTTP Destination
You must create an HTTP destination on the CTS system for every Cloud Foundry target space (every system where you would like to execute imports).
For more information on configuring an HTTP destination in an ABAP system, see Establishing a Connection Using a Destination (SM59).


1. Go to transaction SM59 .
2. Mark HTTP Connections to External Server and choose Create.
3. Enter a name in the field RFC Destination , for example, BT3\_DESTINATION (you need a destination for each target system).


The name that you enter in the field RFC Destination will automatically be converted into upper case as soon as you save the destination. Later, you must enter the name of the destination when you define the target system in STMS . Make sure that you use the correct writing in there.
4. On the tab Technical Settings, enter the details of the target system.
- a) Depending on the account in which BTP region and CF instance it relies on, enter the specific hostname of the SAP Cloud Deployment service as Target Host and leave the Service No. field empty: deploy-service.cf.&lt;domain&gt;, where &lt;domain&gt; is the domain of your target subaccount.
The domain is derived from the Cloud Foundry API endpoint that you can find in the SAP BTP Cockpit in the Overview of your subaccount.
For more information, see Deploying Applications in Regions and Regions and API Endpoints Available for the Cloud Foundry Environment.
## Example 1
Cloud Foundry API endpoint:
api.cf.eu10-004.hana.ondemand.com
SAP Cloud Deployment service URL:
deploy-service.cf.eu10-004.hana.ondemand.com
## Example 2
Cloud Foundry API endpoint:
api.cf.eu10.hana.ondemand.com
SAP Cloud Deployment service URL:
deploy-service.cf.eu10.hana.ondemand.com
- b) Then, enter the Path Prefix using the following:
```
/slprot/<target_org_name>/<target_space_name>/slp
```

## NOTE
You need to escape special characters in your org and space name with a proper URL encoding. For example, replace space characters with %20, and commas with %2C.
Example with URL encoding for organization 'Example Company Test Org' and space 'Example Company Test Space':
/slprot/Example%20Company%20Test%20Org/Example%20Company%20Test%20Space/slp
- c) Finally, configure the HTTP Proxy Options according to your network configuration.
5. Go to the Logon &amp; Security tab and configure the logon to the target system according to your needs. Make sure to check the Active checkbox for SSL and note the Cert. List as it is required below.

Currently CTS+ for SAP BTP Cloud Foundry environment supports only 'Basic Authentication'.
The Cloud Foundry user that you enter here must be part of the default identity provider of BTP (See Default Identity Provider). Users from custom identity providers are not supported (See 4. RESTRICTIONS AND RECOMMENDATIONS). The user must have at least the role SpaceDeveloper

## NOTE
If the root certificate is not imported into the CTS system, the connection test for the connection in transaction SM59 will fail with a similar error:



You have to import all required PEM certificates from BTP Trust Store into the CTS system by following these steps:
1. Log on to the CTS system and open transaction STRUST . Open the edit mode by clicking the Display &lt;-&gt; Change button:

in the corresponding Cloud Foundry target space. More information on the roles is available in the SAP Business Technology Platform documentation under Working with Role Collections.

## NOTE
All import processes of Cloud Foundry content for this target system triggered by CTS use this username and password by default.
6. Repeat these steps for each target system.