Checking the RequestListener

After the RequestListener to the SAP alias has successfully been initialised, it is shown in the SapConnectionService in the Admin Console. You can display more detailed information using the context menu of an SAP alias or an RFC function.

Note: In general, make sure that the minSize parameter in the configuration of the SAP alias in ./etc/sap.xml is greater than 0 if a RequestServer is configured.

Simple ABAP program for testing "MY_RFC"

To test the successful call of the RFC from SAP, you can use a simple ABAP program. The program can be written and tested as a report in the ABAP editor (transaction SE38). In SAP Easy Access, transaction SE38 is entered in the input field on the top left and started with Enter.

Enter the name of the program in SE38, e.g. Z_MY_RFC_CALL. After clicking (1), a new program will be created.

In the following screen, enter a title for the program (2) and choose an executable program as type with the status of a test program (3). Then save with (4).

Now you can save a local object (5).

The program code is then entered in the subsequent editor screen.

The name of the remote destination (here: LOBSTERTESTSYSTEM) has to match the destination defined in SM59 for the Integration Server.

The program can be saved with (6) or Ctrl+S and started with key F8.

After successfully calling the RFC on the Lobster Integration Server, a text line with the words Start and End appears. If an error occurs, SE38 ends with an error message and must be restarted. Open the already saved program with (1) and restart with F8.

After a successful call, a job of the processing profile has been created, which you can view in the Control Center. The backup file of the job for the example RFC "MY_RFC" has the following form.