Show TOC Start of Content Area

Procedure documentation Maintaining HTTP Destinations  Locate the document in its SAP Library structure


Use the following procedures to create or maintain HTTP destinations.

When maintaining the destination information, you need to consider the following options:

        Authentication methods

The following authentication methods are supported for HTTP destinations:

        No authentication

       Basic (User ID and password)

With this option, specify the user ID and password to use for the connection. The user information is then sent with the request in an HTTP Basic Authentication header.

       X.509 client certificates with SSL

In this case, SSL with mutual authentication is used to authenticate the client. The AS Java uses a certificate stored in the Key Storage service. Select the keystore view and entry to use.

       Logon tickets

In this case, the current user’s logon ticket is sent with the request. No additional parameters are necessary.

       Authentication assertion tickets

For system connections between the AS Java and an AS ABAP service using jRFC or HTTP, there is an additional ticket type called the authentication assertion ticket. This ticket is structured the same as the standard logon ticket and is used in a similar manner with the following restrictions:

         It is to be used for connections between systems where no user interaction is necessary.

         It is limited to one-time use. Once the ticket has been verified, it is deleted. A new ticket is issued for a new connection.

         It has a limited validity period (a few seconds).

       User mapping

User mapping maps user IDs between the AS Java (or portal) system and backend systems, if the user ID is different.


For more information about the authentication methods available, see the User Authentication and Single Sign-On documentation.

      Transport Layer Security

To specify that SSL should be used for the connection, use the protocol HTTPS in the URL.


If you do not use HTTPS but still select SSL options, the SSL options are ignored.


Creating a Destination

To create an HTTP destination:


       1.      Start the Destination service. In the SAP NetWeaver Administrator, choose Configuration Management  Security Management. Choose Destinations from the list of security services.

The available destinations appear in the Destinations List. If you select a destination, its details are shown in the lower pane.

       2.      To create a new destination, choose Create….

The General Data screen appears.

       3.      Enter the following information in the corresponding fields:

        Hosting System: <system where the destination is located>

        Destination Name:Enter a name for the destination.

        Destination Type: HTTP

       4.      Choose Next.

The Connection and Transport Security Settings screen appears.

       5.      Enter the following information in the corresponding fields:

       URL: Enter the target system’s URL.

       Additional Settings for SAP Systems:If the target system is an SAP system, then enter the system ID, client, and language to use for the connection.

       SSL Server Certificates: To use SSL for the connection, select Accept Certificates in Keystore View and select the keystore view that contains the trusted certificates. If you select Ignore Server Certificates, then no SSL is used for the connection.

       6.      Choose Next.

The Logon Data screen appears.

       7.      Select the authentication method to use for the connection and if applicable, enter the authentication parameters in the corresponding fields.

       8.      Choose Finish.


You can use the Ping Destination function to test the connection.

Maintaining Destinations

To maintain a destination, select the entry in the destination list. Modify the parameters as necessary and save the data.




End of Content Area