0
SAP JCO shared libraries
Posted by sanjay
on
12:01 PM
Shared libraries are good to use. They make your code base smaller, but they do create some issues while deploying. Recently while deploying a Java provider for SAP JCO, I came across an issue where the dynamic library path was different for each platform. Why is it so? I do not know.. But here it is
Ok two interesting points here. I was surprised to find that SAP JCO supports Mac OS X. Perhaps Mac OS X is big, but I really did not know that it would be used to run business software. I always thought of Macs as personal computers!.I am learning
The second interesting point I noticed is that on HP-UX the enviornment variable is SHLIB_PATH where as it is LD_LIBRARY_PATH on HP Tru64. Aren't they both sold by the same vendor? How come the names of the shared libraries are so different?
I know not.
| OS | Dynamic Library Environment Variable |
| Windows NT, 2000, 2003 | PATH |
| Linux | LD_LIBRARY_PATH |
| Sun Solaris | LD_LIBRARY_PATH |
| IBM AIX/td> | LIBPATH |
| HP-UX | SHLIB_PATH |
| HP Tru64 | LD_LIBRARY_PATH |
| Apple Mac OS X, Version 10.3.1 | DYLD_LIBRARY_PATH |
| IBM OS/400 | ADDENVVAR ENVVAR(LIBPATH) VALUE ('(sapjco-install-path)') |
| IBM z/OS | LIBPATH |
Ok two interesting points here. I was surprised to find that SAP JCO supports Mac OS X. Perhaps Mac OS X is big, but I really did not know that it would be used to run business software. I always thought of Macs as personal computers!.I am learning
The second interesting point I noticed is that on HP-UX the enviornment variable is SHLIB_PATH where as it is LD_LIBRARY_PATH on HP Tru64. Aren't they both sold by the same vendor? How come the names of the shared libraries are so different?
I know not.