Show TOC Anfang des Inhaltsbereichs

Vorgehensweisen Maintaining RFC Destinations  Dokument im Navigationsbaum lokalisieren

Use

Use the following procedures to create or maintain RFC destinations.

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

·        Connection settings

In this section, enter the connection information to the ABAP server. If you use load balancing, then enter the system ID, message server and the logon group to use for the connection. Otherwise, enter the hostname and the system number.

Enter the gateway hostname and service to use if the destination is a registered RFC program.

      Logon data

Either enter a predefined service user or select to use the current user. For the current user, you can specify that either the user’s logon ticket or an assertion ticket should be used for the authentication.

Empfehlung

If you use a service user, then make sure that this user only has those authorizations in the ABAP system that are necessary to perform the desired task.

      Repository

If the user used for the connection does not have the authorizations to access the ABAP repository, then you need to set up a destination to use for this purpose. The repository destination should then access the ABAP system with a service user that has the appropriate authorizations.

You can then select the repository destination as the access method to use to access the repository instead of the user specified for the current RFC destination.

      Secure Network Communications (SNC)

To secure the RFC connection, you can use SNC. In this section, maintain the SNC parameters.

Prerequisites

If you need to access the ABAP repository, then a destination exists with the connection data to the repository. This destination should use a service user that has the appropriate authorizations on the ABAP server.

Procedure

...

       1.      Select the destination type RFC.

       2.      In the dialog that follows, enter a name for the destination.

       3.      Enter the parameters for the connection to the ABAP server (hostname and system number or system ID and logon group if load balancing is used). If the destination is a registered RFC server program, enter the corresponding gateway’s hostname and service.

       4.      Enter the authentication information to use. You can use either a predefined service user or the current user. If you select to use the current user, then also specify whether a logon ticket or an assertion ticket should be used for the authentication.

       5.      If you need to access the ABAP repository, then enter a destination that contains the corresponding connection information.

       6.      If the destination uses a pooled connection, select Pooled in the Pool Settings and enter the pool connection parameters (Pool Size and Max. Wait Time). Otherwise select Single (default).

       7.      If you use SNC to secure the connection, then enter the SNC parameters in the SNC section (active/inactive, quality of protection, the AS Java’s SNC name and the target server’s SNC name).

For more information about SNC, see Configuring SNC (AS Java -> AS ABAP).

       8.      If a SAProuter is used for the connection, then enter the SAProuter connection information in the Advanced Settings.

       9.      Save the data.

Hinweis

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

To activate the RFC trace, set the corresponding indicator in the Advanced Settings.

 

 

 

Ende des Inhaltsbereichs