Skip to Content

SAP provides SAP Java Connector in a number of different versions:

as a standalone software component that can be installed independently of the SAP system. You can access the installation files at service.sap.com/connectors. You can also use download sapjco.jar file and install it in your java application server, it doesn’t have to be NWDS, it can be any sever installed java application. Based on the server you can download different Jco jar.

The following example I finished on Windows32 operating systems. The instructions for the installation of SAP JCo on other operating systems are included in the corresponding download files.

Create a directory, for example C:\\SAPJCo, and extract the JCo .zip file I download from service markedt into this directory.

Copy the file librfc32.dll  from my SAP JCo main directory to my PC C:\WINNT\SYSTEM32, as long as the version that is already there is not a more recent version than the one that is delivered with the SAP JCo. Make sure that the file sapjco.jar (in the SAP JCo main directory) is contained in the class path for all projects for which you want to use the SAP JCo. For productive operation, the following files from the SAP JCo .zip file are necessary:  sapjco.jar,librfc32.dll,sapjcorfc.dll

Here is example I installed the Jco in NetBean and call SAP system.

image

image

image

image

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Ulrich Schmidt
    Hello Wu,
    I see that you are using JCo 2.1 for this example. One suggestion: perhaps you could update the example to use the more recent JCo 3.0? There are a few advantage to this:
    a) JCo 3.0 has now been available for two years, and in most of the recent projects it has replaced JCo 2.1.
    b) librfc32.dll is no longer needed by JCo 3.0, resulting in a huge performance improvement, because nearly no native C/C++ memory is needed now.
    (JCo 2.1 created two copies of the function module data: one on the Java heap and one on the C/C++ heap. The second copy has been eliminated in JCo 3.0, reducing the memory footprint by a factor of 2!)

    Regards, Ulrich

    (0) 

Leave a Reply