Recognizing middleware exception when porting JCo code

Recognizing middleware exception when porting JCo code

How do I resolve a middleware exception when porting JCo code from Windows to UNIX?

    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

This is a common problem that usually indicates an incomplete installation of the JCo connector on the UNIX platform. You have probably already installed the sapjco.jar file into your Java classpath, but you have likely missed the native RFC library installation.

Depending on the UNIX OS, the file extensions will differ, however you must point the environment variable LD_LIBRARY_PATH to the JCo connector install directory. This directory should include the .o or .so library files used by the JCo middleware. The environment variable name varies by platform, so check the JCo install guide for your specific operatiing system.

This was first published in April 2004