Establishing a Connection Between AS ABAP and AS Java 

Use

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.

Normally the AS Java used is the one installed on the same instance as the AS ABAP. However, it is possible to use any other AS Java with a proper release version. To check whether the AS Java has a suitable release version:

●        Configure the connection between the AS ABAP and the AS JAva

●        Activate SAML for a resource on the AS ABAP as described in Activating SAML for Resources in the AS ABAP

●        In the SAML configuration dialog box in transaction SICF, choose Test Connection.

If the AS Java does not have a suitable release version, you get a corresponding error message.

Prerequisites

The SAML service of the AS Java is running.

Procedure

Configuration on the AS Java

...

       1.      In the JCo RFC Provider of the AS Java, check whether there is already a configured connection to the AS ABAP that has a corresponding entry in the maintenance of RFC destinations in the AS ABAP.

       2.      If there is no such connection yet, create a new connection with the following values:

Field Name	Value
RFC destination
Program ID	We recommend that you use: SAML_SERVICE_<SID> where <SID> is the system ID of the AS ABAP to which you are connecting.
Gateway host	Enter a host name on which a gateway process of the AS ABAP runs (this can be any application server of the AS ABAP).
Gateway service	Enter the port of the gateway or the alias (usually sapgw<nn> where <nn> is the instance number of the AS ABAP).
Number of processes	This number determines how many SAML authentications can be executed in parallel and thus depends on the expected rate of SAML authentications per second. For getting started, use 1.
Repository
Application server host	Application server of the AS ABAP
System number	System number of the AS ABAP
Client	Client of the AS ABAP
Language
User	The user must have appropriate authorizations to access the repository.
Password

In the RFC destination section and the Repository section, configure a connection to the same AS ABAP.

       3.      Choose Set.

The connection should appear in the list on the left side with a running symbol. If not, check the log files to find the cause of the error.

Configuration in the AS ABAP

...

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

       2.      Check whether the RFC destination SAPJ2EE is already pre-configured and points to the local AS Java using connection data that matches the data you have found or entered in the JCo RFC Provider of the AS Java.

       3.      If this is not the case:

                            a.      Create a new RFC destination of type T.

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

                            c.      Enter the same Program ID, Gateway Host, and Gateway Service as you entered in the connection on the AS Java.

                            d.      Save your data.

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

Result

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