Show TOC

Establishing a Connection Between AS ABAP and AS JavaLocate this document in the navigation structure


The AS ABAP uses the SAML service of the AS Java to perform the SAML protocol execution with the source site. Therefore the AS ABAP needs a connection to an AS Java with a running SAML service to perform SAML authentication.


If a connection has already been established between the AS ABAP and the AS Java using the Java Resource Adapter you do not need to set up a dedicated connection for the SAML service.

Note, however, that the resource adapter must not use the BindingKey property.

  • The SAML service of the AS Java is running.


Configuring the AS Java

  1. Create a new destination of type RFC that points to the AS ABAP.

    1. In SAP NetWeaver Administrator, choose Start of the navigation path Configuration Next navigation step Destinations End of the navigation path and on the Destinations tab, choose Create .

    2. Configure the connection to use a technical user and enter the name of a user who has authorizations for the function groups SYST, RFC1, SYSU, and SDIFRUNTIME.

    3. To verify the correctness of the entered data, choose the Ping Destination button.

    For more information about RFC destinations, see Maintaining RFC Destinations .

  2. Create a new resource of type Resource Adapter .

    1. In SAP NetWeaver Administrator, choose Start of the navigation path Configuration Next navigation step Application Resources Next navigation step Create New Resource Next navigation step New Resource Adapter End of the navigation path.

    2. On the Names tab, in the Template field enter SAPJRATemplate and in the Application field enter a name for the application.

    3. Choose Next .

    4. On the Settings tab, enter a JNDI Name (for simplicity, you can use the same name as for the application) and a description.

    5. On the Properties tab, provide the following information:

      Field Name



      We recommend that you use: SAML_SERVICE_<SID> where <SID> is the system ID of the AS ABAP to which you are connecting.




      Enter the name of a host on which a gateway process of the AS ABAP runs (this can be any application server of the AS ABAP).


      Enter the port of the gateway or the alias (usually sapgw<nn> where <nn> is the instance number of the AS ABAP).


      Enter the name of the RFC destination that you created above.

  3. Save your entries.

  4. On the Namespace tab, enter a JNDI Name for the JCA Connection Factory . You can use the same name as for the application.

  5. Save your entries.

    The new resource adapter appears in the resource list with status Fully available .

    For more information about creating resources in the Java Resource Adapter, see SAP Java Resource Adapter .

Configuring the AS ABAP

  1. Start the Configuration of RFC Connections (transaction SM59).

  2. Check under TCP/IP connections whether the RFC destination SAPJ2EE is already preconfigured and points to the local AS Java using connection data that matches the data you have found or entered in the Java Resource Adapter of the AS Java.

    If this is not the case:

    1. Create a new RFC destination of type T.

    2. On the Technical Settings tab, choose Registered Server Program as Activation Type .

    3. Enter the same Program ID , Gateway Host , and Gateway Service as you entered in the Resource Adapter on the AS Java (for the properties Program-ID, GatewayServer and GatewayService respectively).

    4. Save your data.

    5. Choose Connection Test to check whether the connection between the AS ABAP and the AS Java is correctly established.

For more information about creating RFC destinations, see Maintaining Remote Destinations .


You have an RFC destination in the AS ABAP that can be used to communicate with the AS Java.