Scenario 6: Installing/porting JCo to other operating systems

Scenario 6: Installing/porting JCo to other operating systems

Porting to other platforms
JCo performs wonderfully well on many UNIX-like and UNIX-flavored platforms. This installation is somewhat simpler, but seems to confuse most people not familiar with a UNIX environment. Should you encounter one of the previous installation exceptions there are only two things you need to check:

- Appropriate environment variable points to JCo installation directory: Depending on the platform, the name of the environment variable will be LD_LIBRARY_PATH (Linux, Sun Solaris, HP Tru64), LIBPATH (IBM AIX), SHLIB_PATH (HP-UX,) or DYLD_LIBRARY_PATH (Mac OS X). This variable should be set to the directory in which you installed the JCo connector. If you are running JCo within an application server, ensure that the application server can "see" OS-level environment variables.

- CLASSPATH contains sapjco.jar: The CLASSPATH environment variable must contain an explicit listing that points to both the directory and sapjco.jar filename. Again, ensure that the CLASSPATH variable is also configured appropriately within your Java application server.

    Requires Free Membership to View

    Login

    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.


TROUBLESHOOTING JCO EXCEPTIONS

 Home: Introduction
 Scenario 1: JCo is unable to find the RFCDSK API library in the system path
 Scenario 2: JCo is unable to find the JCORFC library in the system path
 Scenario 3: JCo cannot load its RFC middleware layer (3 exceptions)
 Scenario 4: JCo finds the wrong version of the librfc library
 Scenario 5: JCo exceeds the number of SAP-allocated work processes
 Scenario 6: Installing/porting JCo to other operating systems
 Review: Conclusion and more resources

This was first published in June 2005