SAP Java Connector

The SAP Java Connector (SAP JCo) is a development library that enables a Java application to communicate with on-premise SAP systems via SAP's RFC protocol. It combines an easy-to-use API with unprecedented flexibility and performance. The SAP JCo supports both communication directions: inbound Remote Function Calls (Java calls ABAP) as well as outbound Remote Function Calls (ABAP calls Java).

The SAP Java Connector is the best choice for building SAP-enabled Java applications because of the following features:

  • High performance JNI-based RFC middleware.
  • Supports R/3 3.1I and higher releases (and other SAP components that have BAPIs or RFMs).
  • Supports inbound (Java client calls BAPI or RFM) and outbound (ABAP calls Java server) RFC communication.
  • Supports synchronous, transactional, queued and background RFC (sRfc, tRfc, qRfc, bgRfc protocols).
  • Provides client connection pooling (good for web servers).
  • Multi-platform support.
  • Complete and correct code page handling (including Unicode and non-Unicode single- and multi-byte code pages).

In case of problems with the SAP Java Connector, report an incident under component BC-MID-CON-JCO.

  • High performance JNI-based RFC middleware.
  • Supports R/3 3.1I and higher releases (and other SAP components that have BAPIs or RFMs).
  • Supports inbound (Java client calls BAPI or RFM) and outbound (ABAP calls Java server) RFC communication.
  • Supports synchronous, transactional, queued and background RFC (sRfc, tRfc, qRfc, bgRfc protocols).
  • Provides client connection pooling (good for web servers).
  • Multi-platform support.
  • Complete and correct code page handling (including Unicode and non-Unicode single- and multi-byte code pages).

In case of problems with the SAP Java Connector, report an incident under component BC-MID-CON-JCO.

  • High performance JNI-based RFC middleware.
  • Supports R/3 3.1I and higher releases (and other SAP components that have BAPIs or RFMs).
  • Supports inbound (Java client calls BAPI or RFM) and outbound (ABAP calls Java server) RFC communication.
  • Supports synchronous, transactional, queued and background RFC (sRfc, tRfc, qRfc, bgRfc protocols).
  • Provides client connection pooling (good for web servers).
  • Multi-platform support.
  • Complete and correct code page handling (including Unicode and non-Unicode single- and multi-byte code pages).

In case of problems with the SAP Java Connector, report an incident under component BC-MID-CON-JCO.

  • High performance JNI-based RFC middleware.
  • Supports R/3 3.1I and higher releases (and other SAP components that have BAPIs or RFMs).
  • Supports inbound (Java client calls BAPI or RFM) and outbound (ABAP calls Java server) RFC communication.
  • Supports synchronous, transactional, queued and background RFC (sRfc, tRfc, qRfc, bgRfc protocols).
  • Provides client connection pooling (good for web servers).
  • Multi-platform support.
  • Complete and correct code page handling (including Unicode and non-Unicode single- and multi-byte code pages).

In case of problems with the SAP Java Connector, report an incident under component BC-MID-CON-JCO.

  • High performance JNI-based RFC middleware.
  • Supports R/3 3.1I and higher releases (and other SAP components that have BAPIs or RFMs).
  • Supports inbound (Java client calls BAPI or RFM) and outbound (ABAP calls Java server) RFC communication.
  • Supports synchronous, transactional, queued and background RFC (sRfc, tRfc, qRfc, bgRfc protocols).
  • Provides client connection pooling (good for web servers).
  • Multi-platform support.
  • Complete and correct code page handling (including Unicode and non-Unicode single- and multi-byte code pages).

In case of problems with the SAP Java Connector, report an incident under component BC-MID-CON-JCO.

Download SAP Java Connector 3.0.18 SDK

Release 3.0.18 of the SAP Java Connector includes fixes and new functionality described in SAP Note 2531996. In addition, it contains the fixes and enhancements of all previous patch releases: 2442840, 2361127, 2301211, 2245017, 2155739, 2015561, 1919773, 1748457, 1671480, 1643299, 1572431, 1467969, 1438294, 1405464, 1385673, 1310832, and 1264236.

SAP Note 1077727 describes which operating systems and versions with which JDKs/JREs are supported by the SAP Java Connector, and when the SAP Java Connector maintenance and support period will end.

The SDK package of SAP Java Connector 3.0 includes the software as well as documentation and examples. The SAP Java Connector 3.0 requires a JDK/JRE 5, 6, 7 or 8. In addition, the SAP Java Connector 3.0 running on Windows operating systems requires the Visual Studio 2005 C/C++ runtime libraries to be installed on the system. See SAP Note 684106 for details on how to install them.

Notes

  • The SDK archives for Windows and Mac OS X of the SAP Java Connector are shipped as a ZIP file embedded in a ZIP file.
    The SDK archives for the Unix versions of the SAP Java Connector are shipped as a TGZ file embedded in a ZIP file.
  • Extract the nested archive variant from the downloaded archive first. In case you have installation instructions from some other component, they usually refer to the nested archive.
  • After extracting the content from the nested archive, further installation instructions can be found in the file <instDir>/javadoc/installation.html.

Note on 32-bit versus 64-bit versions:
You only need the 64-bit version of the SAP Java Connector if you are using a 64-bit Java VM. If you have to use a 32-bit Java VM on a 64-bit platform, download and use the 32-bit version of JCo. But the 64-bit variant should always be preferred on 64-bit platforms, if feasible.
Some JVMs offer both modes, 32-bit as well as 64-bit. In this case, you need to start the JVM with an additional start-up parameter to specify the mode. Usually these are options -d32 and -d64; please consult the JVM documentation for further details.

Operating system Processor Release date File size (KB)
Microsoft Windows and Windows Server 32-bit
March 28, 2018 5,478
64-bit Itanium March 28, 2018
6,347
64-bit x86* March 28, 2018
5,533
Linux (for Intel compatible processors) 32-bit March 28, 2018
3,627
64-bit Itanium March 28, 2018
4,674
64-bit x86* March 28, 2018
3,804
Linux (for IBM eServer zSeries) 64-bit March 28, 2018
3,985
Linux (for IBM PowerPC processors) 64-bit BE** March 28, 2018
4,456
64-bit LE**
March 28, 2018
3,720
HP-UX 64-bit PA-RISC March 28, 2018
4,451
64-bit Itanium March 28, 2018
5,606
IBM AIX 64-bit March 28, 2018
4,120
IBM z/OS 64-bit March 28, 2018
3,716
IBM i (OS/400 PASE) 64-bit March 28, 2018
11,585
Oracle Solaris (Sun OS) 64-bit SPARC March 28, 2018
4,270
64-bit x86* March 28, 2018
3,826
Apple Mac OS X (for Intel processors) 32-bit March 28, 2018
3,851
64-bit x86* March 28, 2018
3,884

* "64-bit x86" refers to Intel EM64T and AMD64 processors.
** "BE" and "LE" refer to IBM PowerPC 64-bit processors running in big-endian or little-endian mode.

In case of problems with the SAP Java Connector, report an incident under component BC-MID-CON-JCO.

Documentation

Type Description Language Release date File size (KB)
Migration Guide Outlines how to migrate a Java application from using an older JCo version 2.x to use version 3.0. English August 8, 2011 100
Migrationsleitfaden Führt aus, wie man eine Java-Anwendung von der Verwendung einer älteren JCo Version 2.x zur Verwendung der Version 3.0 überführt.
Deutsch August 8, 2011 114
Documentation Describes the programming model of the JCo 3.0 standalone version and the Java IDoc Class Library 3.0 add-on.
English April 15, 2013 329
Dokumentation Beschreibt das Programmiermodell der JCo 3.0 Standalone-Version und der Java IDoc-Klassenbibliothek 3.0-Erweiterung. Deutsch April 15, 2013 335

SAP Java IDoc Class Library

The SAP Java IDoc Class Library (SAP JIDocLib) is an add-on library for the SAP Java Connector (SAP JCo). It provides an easy-to-use API for sending and receiving IDocs and IDoc packages to and from on-premise SAP systems. The API also helps interpreting and navigating through IDocs and modifying them or creating new ones. In addition, it provides a processing feature for parsing and rendering IDoc-XML documents.

Important Notes:

  • The SAP Java IDoc Class Library 3.0.12 requires SAP Java Connector 3.0.12 or higher and a JRE/JDK 5, 6, 7 or 8. For installation instructions read the installation.html page included in the downloadable archive. For details about the included fixes read the release notes that can be reached from there.
  • Version 3.0 of the IDoc Class Library has changed incompatibly compared to the previous versions 1.x. For adjusting existing application code to use the new version please see the Migration Guide (PDF file).
The SAP Java IDoc Class Library (SAP JIDocLib) is an add-on library for the SAP Java Connector (SAP JCo). It provides an easy-to-use API for sending and receiving IDocs and IDoc packages to and from on-premise SAP systems. The API also helps interpreting and navigating through IDocs and modifying them or creating new ones. In addition, it provides a processing feature for parsing and rendering IDoc-XML documents.The SAP Java IDoc Class Library (SAP JIDocLib) is an add-on library for the SAP Java Connector (SAP JCo). It provides an easy-to-use API for sending and receiving IDocs and IDoc packages to and from on-premise SAP systems. The API also helps interpreting and navigating through IDocs and modifying them or creating new ones. In addition, it provides a processing feature for parsing and rendering IDoc-XML documents.

(ZIP file, 579 KB) Includes software, documentation, and examples.

Frequently Asked Questions

The SAP Java Connector (SAP JCo) is a development library that enables a Java application to communicate with on-premise SAP systems via SAP's RFC protocol. It combines an easy-to-use API with unprecedented flexibility and performance. The SAP JCo supports both communication directions: inbound Remote Function Calls (Java calls ABAP) as well as outbound Remote Function Calls (ABAP calls Java).

The SAP Java IDoc Class Library (SAP JIDocLib) is an add-on library for the SAP Java Connector (SAP JCo). It provides an easy-to-use API for sending and receiving IDocs and IDoc packages to and from on-premise SAP systems. The API also helps interpreting and navigating through IDocs and modifying them or creating new ones. In addition, it provides a processing feature for parsing and rendering IDoc-XML documents.


The SAP .NET Connector is based on Microsoft .NET. This connector offers developers the possibility to expose BAPIs and remote enabled function modules to any .NET application (inbound communication). It is also possible to access .NET components from an on-premise SAP system (outbound communication).

The SAP Java Connector employs standards-based information exchange between SAP and a Java application. Additionally, the SAP Java Connector together with the SAP Java IDoc Class Library offer high level support for IDocs.

SAP Java Connector appears to an SAP system as an RFC destination. To direct a BAPI or IDoc call to SAP Java Connector, you simply use this destination. To incorporate external data or services into your SAP system, you create a Java application, which defines the interface to the data, and call the implementation.

The communication between SAP Java Connector and an SAP system can be secured via Secure Network Communication (SNC). For this you need the SAP Common Cryptographic Library. More information about security including the required configuration in the SAP System and how to obtain the SAP Cryptographic Library can be found in the SAP Software Download Center. Information about the necessary configuration within SAP Java Connector can be found in the JavaDoc of the SAP Java Connector SDK.

See SAP Note 1077727 that describes which operating systems and versions with which JDKs/JREs are supported by the SAP Java Connector, and when the SAP Java Connector maintenance and support period will end. Furthermore, it is recommended to have at least 256 MB physical memory on your hardware.

Updates happen by installing a new version over an older version. See also the installation instructions included in the JCo SDK download archive. In general, a new SAP Java Connector patch level is downwards compatible to the previous patch levels of the same release.

Installation is painless and done in a matter of minutes. Unzip the installation file into an arbitrary directory and follow the installation instructions about adjusting the PATH/LIBPATH and CLASSPATH environment variables. Besides a JDK or JRE, no additional software is required.

Configuration is rapid and straight forward and usually a matter of days for a trained person. Practical experience with Java Programming plus basic knowledge of SAP technology, e. g. BAPI or IDoc, is essential. For error tracking, RFC and tRfc knowledge is helpful. As for ALE, SAP JCo is a transparent transport layer, so SAP JCo itself does not require ALE knowledge.

The SAP Java Connector (JCo) and the SAP Java IDoc Class Library (JIDocLib) are available free of charge and can be downloaded from the SAP Support Portal. The license terms are pointed out on the download pages and in the documentation of these components.

If you have existing developer licenses, these named persons already have the required license to develop solutions based on the SAP Java Connector. If additional persons want to develop based on the SAP Java Connector, you will have to acquire additional developers licenses for them.

The runtime does not require any immediate license fees. However, please note that each user accessing application functionality through the SAP Java Connector is required to be licensed under a respective solution or component license.

Yes. Redistribution is not allowed. Please see the license terms on the download page.

SAP customers get full support and service from SAP. This support is provided via the SAP Support Portal.