Maintaining HTTP and Web Service Destinations 

Use

Use the following procedures to create or maintain HTTP or Web service destinations.

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

·        Authentication options

The following authentication methods are supported for HTTP and Web service destinations:

¡        None

No authentication occurs with this connection.

○       Basic

With this option, specify the user name 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

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 an AS Java and an AS ABAP 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).

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

●      Transport Layer Security

To specify that SSL should be used for the connection, use the protocol https in the URL. You can then maintain the SSL options in the Server Certificates section.

Procedure

Creating a Destination

To create an HTTP or Web service destination:

...

       1.      Select the type of destination and choose New.

       2.      In the dialog that follows, specify a name for the destination and choose OK.

       3.      Enter the connection information for the destination.

This includes the target URL and, for an ABAP-based destination, the system ID, client and language.

For Web service destinations, there are different options for specifying the connection information:

·         Default: The default entry uses the connection information as specified in the SAP NetWeaver Developer Studio during the development process .

·         Custom: To modify the connection information, select this option.

·         SLD: If the connection information has been published in the System Landscape Directory (SLD), then select this option.

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

       5.      If the connection is to use SSL, then specify how the connection should handle SSL server authentication.

If the connection uses HTTPS in the URL, then select the corresponding option under Server Certificates. Select the keystore view that contains the CA root certificates that you accept or select to ignore server certificates.

       6.      Save the data.

You can use the Save and Test function to test the connection.

Maintaining Destinations

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