Did you need any special configuration or was running the install script and setting the LD_LIBRARY_PATH environment variable sufficient?

I'm currently using IBM Websphere 7. The code within WAS just hangs when attempting to connect to Centera. We're also getting UnsatisfiedLinkError exceptions trying to run Verify and JCAS outside of WAS. 

Yes:  RHEL 5.7 & 6.1 x64, Java 1.6, standalone application.

Nothing more than setting LD_LIBRARY_PATH in an application launch script needed for us.

Over the years there have been people who've had trouble using the SDK with J2EE application servers, have you tried a forum search?   I have never directly worked with WebSphere and any JNI libraries such as the SDK.

Good Luck,

Mike Horgan

Hi Noxx -

The answer to that question turns out to be more complicated than I expected:

[root@il-nfs ~]# which java

/usr/bin/java

[root@il-nfs ~]# ls -l /usr/bin/java

lrwxrwxrwx 1 root root 22 Nov 19  2010 /usr/bin/java -> /etc/alternatives/java

[root@il-nfs ~]# ls -l /etc/alternatives/java

lrwxrwxrwx 1 root root 29 Jan 30 14:32 /etc/alternatives/java -> /usr/java/latest/jre/bin/java

[root@il-nfs ~]# ls -l /usr/java/latest

lrwxrwxrwx 1 root root 21 Jan 30 14:17 /usr/java/latest -> /usr/java/jdk1.6.0_30

Hope that helps,

Mike Horgan

I have another question for you Mike.  Do you know where Java was installed on your server that is working? The EMC guy working my support ticket seems to think that might be our problem and wanted me to ask you that.

Thanks!

Just checked:

[root@il-nfs ~]# ls /bin/java

ls: /bin/java: No such file or directory

Good Luck,

Mike Horgan

Thanks, Mike.

Hmm Thanks,  Do you know if you have a symbolic link under /bin pointing to it? the EMC guy seems to believe Java needs to be installed there.

-Tom

I suppose I should follow up here in case anyone else uses this. A few weeks ago we got our app to work in WAS 7.0.0.19 running on RHEL 6.1 64-bit. After a bit of research we discovered IBM requires you to set an environment variable called CENTERA_LIB_PATH as well as LD_LIBRARY_PATH. we also had to chmod 755 /lib/64/*.  Our initial security didn't want to give us read permissions, and just execution.  I followed installation directions as provided in the IBM WAS documentation. I hope this is of some help to someone eventually.

I know this is many many years later, but I need to find out what else you had to do to get this working.  I have done all of the above but still cannot get it to work.