The 64-bit variant should always be preferred on 64-bit platforms. If you have to use a 32-bit Java VM on a 64-bit platform, download and use the 32-bit version of JCo. You only need the 64-bit version of the SAP Java Connector if you are using a 64-bit Java VM.
Extract the nested archive variant from the downloaded archive first.The SDK archives for the Unix versions of the SAP Java Connector are shipped as a TGZ file embedded in a ZIP file.
The SDK archives for Windows and macOS of the SAP Java Connector are shipped as a ZIP file embedded in a ZIP file.SAP Java Connector 3.1 running on Windows operating systems requires the Microsoft Visual Studio 2013 C/C++ runtime libraries to be installed on the system. The SAP Java Connector 3.1 requires a JDK/JRE 8 or 11. The SDK package of SAP Java Connector 3.1 includes the software, documentation, and examples. SAP Note 2786882 describes which operating systems and versions with which JDKs/JREs are supported by the SAP Java Connector 3.1, and when the SAP Java Connector 3.1 maintenance and support period will end. It also contains items from the previous patch release 2947370.
Release 3.1.4 of the SAP Java Connector includes fixes and new functionality as described in SAP Note 3036882. In case of problems with the SAP Java Connector, report an incident under component BC-MID-CON-JCO. Complete and correct code page handling (including Unicode and non-Unicode single- and multi-byte code pages).Supports synchronous, transactional, queued and background RFC (sRfc, tRfc, qRfc, bgRfc protocols).Supports inbound (Java client calls BAPI or RFM) and outbound (ABAP calls Java server) RFC communication.Supports R/3 3.1I and higher releases (and other SAP components that have BAPIs or RFMs).