Use the following procedures to create or maintain HTTP destinations.
When maintaining the destination information, you need to consider the following options:
The following authentication methods are supported for HTTP destinations:
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.
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.
In this case, the current user's logon ticket is sent with the request. No additional parameters are necessary.
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:
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.
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:
The available destinations appear in the Destinations List. If you select a destination, its details are shown in the lower pane.
The General Data screen appears.
The Connection and Transport Security Settings screen appears.
The Logon Data screen appears.
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.