Show TOC

Background documentationSAP JCo Server Programming Locate this document in the navigation structure


The following section explains how you can write your own JCo programs for servers if you use the standalone version of the SAP JCo.

A JCo server program implements functions that are called up by an AS ABAP client. The JCo server program is registered via the SAP Gateway and waits for inbound RFC calls.

  • An RFC server program registers itself under a program ID to an SAP gateway (not for a specific SAP system).

  • If an RFC call is passed on from any SAP system to this SAP gateway with the option Connection with a registered program (with the same program ID), the connection takes place with the corresponding JCo server program.

  • Once an RFC function has been executed, the JCo Server waits for further RFC calls from the same or other SAP systems.

  • If an RFC connection is interrupted or terminated, the JCo server automatically registers itself again on the same SAP gateway under the same program ID.


  • You are using the standalone version of SAP JCo.

  • Using transaction SM59, you have defined a destination with connection type T (TCP/IP connection) in the SAP system.

  • You have chosen the registration mode (Registered Server Program option under the Technical Settings tab page) for this destination.

  • The destination contains the required information about the SAP gateway and the registered RFC server program.

  • In the case of a Unicode target system, the Unicode flag is set for the destination.

More Information

Note Note

Because the old and new JCo API (2x and 3.0) differ greatly in their programming models, both of the API versions are handled separately here.

End of the note.