Show TOC

 Maintaining RFC DestinationsLocate this document in the navigation structure

Use

Use the following procedures to create or maintain RFC destinations.

When maintaining the destination information, 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.

  • Secure Network Communications (SNC)

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

  • 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.

    Note

    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.

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.
  • If you use SNC, then the following properties are set in the AS Java's profile:
    • snc/gssapi_lib : Location of the SNC library
    • snc/identity/as : SNC name of the AS Java
Procedure

Creating a 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: <Name>
    • Destination Type: RFC
  4. Choose Next.

    The Connection and Transport Security Settings screen appears.

  5. 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.
  6. If you use SNC to secure the connection, then enter the SNC parameters in the SNC section (active/inactive, quality of protection, and the target server's SNC name).
  7. Choose Next.

    The Logon Data screen appears.

  8. Enter the authentication information to use. You can use either a predefined technical user or the current user for the connection. If you use a technical user, enter the user's data in the corresponding fields. If you use the current user, then specify whether a logon ticket or an assertion ticket should be used for authentication.
  9. If you need to access the ABAP repository, then enter a destination that contains the corresponding connection information in the Repository Connection section.
  10. Choose Next.

    The Specific Settings screen appears.

  11. If the destination uses a pooled connection, select Pooled Connection Mode in the Pool Settings and enter the pool connection parameters accordingly.
    Note

    If a destination in the destination service is configured as current user (logon or assertion ticket), the pool settings refer to a single user. Consequently, we recommended setting the values for the number of connections as low as possible.

    Tip

    For example, if the maximum is set to 5 and there are 100 users active on a portal, a maximum of 500 connections can be created.

  12. If a SAProuter is used for the connection, then enter the SAProuter connection information in the Advanced Settings.
  13. Save the data.
    Note

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

Maintaining Destinations

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