Connection to SAP
- Connection by URL to a proxy
- Connection using SAP Cloud Connector inside of SAP Business Technology Platform
Note that in both cases, the account credentials used are only for the Connect console to be able to query the API availability on the source system. In most use cases, account credentials (which might also be for a service account) will be passed on each API call, rather than using the credentials configured here.
Using this connection approach, no additional setup is needed beyond configuration of your proxy.
SAP Cloud Connector is a reverse proxy solution provided by SAP to natively connect to applications (like your Connect end points) running in SAP Business Technology Platform. It consists of an on-premise component (sapcc) that connects to your SAP system and a connector inside SAP BTP.
Many customers choose to use separate connectors for their dev and production instances, so just be aware that this must be done in separate subaccounts
Use the SAP Cloud Connector install guide or use a community provided docker image.
- If installing on Windows, it is recommended to use sapjvm - Windows x64 in place of the Oracle JVM/JDK. sapcc needs the JDK, will not run with just the JRE/JVM.
- Extract zip file and copy the whole folder to
- Create new system environment variable
;C:\SAP\sapjvm_8\binto the system
In the Cloud Connector admin portal
- Region: This should match the region of the subaccount in Cloud Foundry (and it needs to be the same subaccount where you will be running your Connect end points), check your subaccount or trial subaccount and ensure the region listed in the subaccount matches the region selected when adding the subaccount.
- Subaccount: the value is the Id of the subaccount and not the SubDomain. The ID can be obtained using the info hover or the details tab in the SAP Cloud Platform Cockpit.
- Display Name: enter the subdomain Subaccount User & Password: Use an authorized user account in the subdomain. If you started a trial use your trial credentials.
Cloud to on-premise
In the subaccount add a new System Mapping.
- Back-end Type: Other SAP System
- Protocol: HTTP
- Internal Host: dns name or ip of the SAP ECC/S4 HANA system
- Internal Port: port, e.g. http port 8000
- Virtual Host: create a unique name for the virtual host. (e.g. sap-dev)
- Virtual Port: 80
- Principal Type: None
- Host In Request Header: Use Virtual Host
- Description: leave blank or provide the system name.
- In the summary check the checkbox (Check Internal Host) [X]
- Click [Finish]
Under Resources add a Resource
- URL Path:
- Active: [X]
- Access Policy: (x) Path And All Sub-Paths
Finally, you need to create a destination to map the cloud connector to a destination service that can be used by Connect.
You will need the virtual host and virtual port from the previous section for the Cloud Connector you'd like to access in Connect (on the "Cloud Connectors" tab).
Select Connectivity | Destinations from the subaccount menu and add a new Destination.
- Name: Give it a name - this will be visible in Connect when selecting an SAP system to attach to an app
- Type: HTTP
- Description: Optional
- URL: The host and port from above, plus
http://sap-dev-ecc:80/enosix/paca?sap-client=900) where the number specified is the client ID to which you wish to connect.
- If you want to use the default client ID, you can just do
- Proxy Type: OnPremise
- Authentication: BasicAuthentication
- Location ID: leave blank
- User/Password: valid credentials for the SAP system and client ID specified (typically a service account) - these will be used by Connect to query available APIs during end point configuration; they will also be used if you configure an end point to not authenticate individual calls