Defining a Back-End Connection
Define a new back-end connection to a data source or service for a native, hybrid, or Web application.
- In Management Cockpit, select .
- To create a new connection, click the plus sign , and in the Create Connection
Field Value Back-End URL The URL the application uses to access business data on the back-end system or service. This can be a back-end connection, or a service document, usually in the following format:
http://<host>:<port>/gateway/odata/<namespace>/<Connection_or_ServiceName>.../For a service, the service document URL is the document destination you assigned to the service in SAP Gateway. Include a trailing forward slash to avoid triggering a redirection of the URL, and losing important HTTP header details. This is especially important when configuring the application with security such as SSOToken and Certificates, and when Rewrite URL in SMP or Rewrite URL in Backend System is selected as the rewrite mode.
Internal White list a service that you create in SAP Mobile Platform. If you define an endpoint as internal, the host name and port of the back-end URL are ignored, and incoming requests are forwarded to internal services in-process, without another HTTP call to localhost. An example of an internal service is Integration Gateway. Allow Anonymous Access (Optional) If enabled, the user can access the application without entering a user name and password. However, back-end systems still require login credentials for data access, whether it is a read-only user, or a back-end user who is assigned specific roles.
If enabled and the back end requires it, enter the login credentials to access the back-end system:
- User name – the user name for the back-end system.
- Password – (required if you enter a user name) the password for the back-end system.
If disabled (the default) or the back end does not require it, you need not provide these credentials.
Maximum Connections (Optional) The number of back-end connections that are available for connection pooling for this application. The larger the pool, the larger the number of possible parallel connections to this specific connection. For primary endpoints, the default and minimum is 500 connections. Consider the following factors when resetting this property:
- The expected number of concurrent users of the application.
- The load that is acceptable to the back-end system.
- The load that the underlying hardware and network can handle.
To disable connection pooling, set this value to 0. Disable connection pooling only if the back-end system does not support pooled connections, as disabling connection pooling may have a negative impact on processing times.
Timeout in Milliseconds
The number of milliseconds before the back-end connection times out. If set to 0, the JVM timeout value is used.
Online Request Threshold
The threshold value to throttle incoming online requests per second for a connection. Leave blank (default) or set to 0 to remove threshold. Set a threshold value from 1 ‒ 2147483647.
Certificate Alias Optional if the Endpoint URL begins with HTTPS.
If the back-end system has a mutual SSL authentication requirement, select the certificate alias name of the private key and technical-user certificate that can access the back-end system. The certificates are located in the shared keystore smp_keystore.
Rewrite Mode Select one of:
- Rewrite URL on SMP – in request and response messages, the server replaces all back-end URLs with the server URL.
Rewrite URL on Back End – the back end rewrites the URLs. The server forwards its host name and port to the back end in an HTTP header, and the back end creates the URL to retrieve back-end entities.
Select Via HCP App to use the x-forwarded-for header value; or leave it unselected to use the default Host header.
- No Rewriting – request and response messages are not modified; the server passes messages directly between clients and back-end systems.
See URL Rewrite Modes.
Relative Path (Only if Rewrite Mode is Rewrite URL on SMP) If an application requires data from a back end that uses relative URLs, configure those relative URL patterns here.
The server rewrites relative URLs to include the connection ID (connection name), enabling access to the back-end data. For example, a Web service application requests an HTML page named abc.html, which contains the relative URLs /sap/bc and /sap/public/bc in its src or href tags. When a request is made, the server rewrites the relative URLs in the response, so that subsequent requests to these relative URLs are processed correctly.
For example, if "webApp" is the connection name and the response contains the relative URLs /sap/bc and /sap/public/bc, the server rewrites these relative URLS to /webApp/sap/bc and /webApp/sap/public/bc. Without the relative URLs, the request cannot be processed.
To add relative paths, enter a comma-delimited list of relative URLs, for example, /sap/bc,/sap/public/bc.
SSO Mechanisms (Optional) You can add one or more SSO mechanisms, and prioritize them. The runtime calls the first SSO mechanism for which corresponding user credentials are available. Only one SSO mechanism is used per connection attempt. If a connection fails, the server invalidates the client session and requires reauthentication.
Click the Create icon , select an SSO Mechanism, and click Save.
To change the order in which an SSO mechanism is used, select it, and click or .
See Single Sign-On Mechanisms.
- Click Save.