Next, the runtime destination will be created. This destination is required to access the business data of the connected SAP S/4HANA system. It does point to the base host, so apps that are requesting data can add to the path to request the data from specific endpoints.
For the name, use the SAP S/4HANA system ID and the suffix "rt" for runtime, for example, s4hrt.
Note
The destination name must be lower case and must not contain the underscore character (_).Similar to the Design-Time destination, use the BasicAuthentication for now. Enter the credentials of an SAP S/4HANA user that can be used to perform a first test for the business content. This could either be your own or a dedicated test user that holds authorizations to the business content in the exposed roles.
In the next lesson, the authentication method will be changed from BasicAuthentication to PrincipalPropagation to enable a connection based on the user logged into SAP Build Work Zone, standard edition.
For the other input fields and additional parameters, use the guidance of the following table:
Destination Configuration
Name | For example, s4hrt |
Type | HTTP |
Description | For example, S4H Runtime Destination |
Proxy Type | OnPremise |
URL | https://< hostname>:<port> |
Authentication | Basic Authentication |
Location ID | <Location ID defined in the Cloud Connector> |
User | <SAP S/4HANA user> |
Password | <Password of respective user> |
Additional Properties
HTML5.DynamicDestination | true |
MobileEnabled | true |
sap-client | <client> for example, 100 |
sap-platform | ABAP |
sap-service | 32<service number> for example, 3200 |
sap-sysid | <sysID> for example, S4H |
Save the entered information.
Note
More information on the parameters is available in the help documentation.