Show TOC

Creating a Destination on Gateway Management CockpitLocate this document in the navigation structure

Create destinations for the services to point to the datasource from which the data is fetched.

Procedure

  1. Log in to Gateway Management Cockpit.
  2. On the DESTINATIONS tab, click New Destination.
  3. Enter the information that is appropriate to the type of datasource you want to connect to:
    JDBC:
    Field Description
    <Destination Name> Enter the name for the destination.
    <Destination Type> Select DATABASE.
    <Destination URL> Enter the destination URL of the JDBC datasource you are connecting to. For example, jdbc:hsqldb:mem:com.sap.sample.
    <Database Driver> Enter the JDBC driver that enables the processor to connect to the database. For example, org.hsqldb.jdbcDriver.
    <Authentication Type> Select one of:
    • No Authentication: if no authentication is required to access the JDBC datasource.
    • Basic Authentication: if user name and password is required for to access the JDBC datasource.
    <User Name> If you selected Basic Authentication type, enter the user name to access the JDBC datasource.
    <Password> Enter the password to access the JDBC datasource.
    HTTP:
    Field Description
    <Destination Name> Enter a name for the destination.
    <Destination Type> Select HTTP.
    <Destination URL> Enter the destination URL of the datasource you are connecting to.
    Note
    • If you are creating a destination for an SAP service, see Registering an SAP Service on Gateway Management Cockpit for information on how to get the destination URL.
    • For REST services, enter the base URL and not the absolute URL (that is, exclude the relative URL). For example, if the absolute URL of the destination is https://aaaaa.wdf.sap.corp:10000/ztest/zrest/product/Products, enter https://aaaaa.wdf.sap.corp:1000 in the <Destination URL> field.
    <Authentication Type> Select one of:
    • No Authentication: if no authentication is required to access the datasource.
    • Basic Authentication: if a user name and password is required to access the datasource.
    • Client Certificate: if client certificate is enabled on the datasource.
    • CSI Authentication: if the outgoing call to the destination will use the same authentication mechanism as the incoming request to SAP Mobile Platform.
      Note Only No Authenication and Basic Authentication types are supported for REST services.
    <User Name> If you selected Basic Authentication type, enter the user name to access the datasource.
    <Password> Enter the password to access the datasource.
    <Certificate Alias> If you selected:
    • Client Certificate: enter the certificate alias of the end user in the back-end system.
    • CSI Authentication and have enabled Enable X.509 option: enter the certificate alias of the technical user in the back-end system.
    If you selected CSI Authentication, depending on the authentication providers configured in the security profile associated with the application, you can enable one or more SSO mechanisms:
    1. <Enable Kerberos> Enable this option to access the datasource using Kerberos. You must also specify the Kerberos realm and service name properties.
    2. <Enable Basic Authentication> Enable this option to use the basic authentication mechanism to access the datasource (username and password provided by the user is forwarded to the back-end in the HTTP Basic Authentication header).
    3. <Enable SSO2> Enable this option to use the SAP SSO2 mechanism to access the datasource. You must also provide the certificate alias of the technical user in the back-end system.
    4. <Enable X.509> Enable this option when the client has authenticated using HTTPS and X.509 certificates for mutual authentication. In case it is used with the Principal Propagation Authentication Provider, SAP Mobile Platform will generate short-living X.509 certificates and sign them with the configured key. You must also provide the certificate alias of the technical user in the back-end system when Enable X.509 option is selected.
    <Kerberos Realm> If you selected Enable Kerberos, enter the realm that contains the datasource resources that are accessed using Kerberos.
    <Kerberos Service Name> If you selected Enable Kerberos, enter the service name used by Kerberos to access the datasource. It usually corresponds to the hostname of the datasource.
    JPA:
    Field Description
    <Destination Name> Enter a name for the destination.
    <Destination Type> Select JPA.
    <Persistence Unit> Enter the name of the JPA persistence unit as defined in the persistence.xml file (created in the META-INF directory).
    Note Authentication details are not required to create destinations for JPA datasources.
  4. Save the settings.