Missing SAP Java Connector libraries JCo- librfc32.dll, com.sap.utils and com.sap.mw

Please note that all these library files ? librfc32.dll, com.sap.utils and com.sap.mw come under JCo 2.1. With release of JCo 3.0, its classes were also relocated from packages com.sap.mw.jco.* to com.sap.conn.jco.*

For running with SAP JCo 3.0, you need these files at runtime ? sapjco3.jar and sapjco3.dll (on Windows). You can follow below procedure for installation of JCo files:

Installing JCo on Windows Platform

In Windows OS, you have to copy sapjco3.jar file into ITDI_HOME/jars/3rdparty/others.

Copy the sapjco3.dll file into ITDI_HOME/libs. On Windows, JCo 3 requires additional Microsoft Visual C++ 2005 libraries to be installed. Installation details for the package that contains these libraries are specified in Microsoft Knowledge Base article 973544.

Restart the adapter service after copying the files.

Installing JCo on UNIX or Linux

Create a symbolic link to the sapjco3.jar file in ITDI_HOME/jars/3rdparty/others ?

ln -s <sapjco_install_dir>/sapjco3.jar ITDI_HOME/jars/3rdparty/others/sapjco3.jar

Next is to add SAP JCo installation directory to the dynamic library path by following below steps ?

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<sapjco_install_dir>
export LIBPATH=$LIBPATH:<sapjco_install_dir>

Restart the Dispatcher after making these changes.

Important Notes

The ITDI_HOME refers to the IBM Tivoli Directory Integrator installation directory. Replace <sapjco_install_dir> with the actual path where you extracted the SAP JCo files.

Conclusion

Upgrading from JCo 2.1 to JCo 3.0 requires replacing the old library files with new ones and updating package references. Following the platform-specific installation steps ensures proper SAP connectivity functionality.