× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I don't know of anything in the catalina.sh that expects anything regarding a specific location unless someone changes the script. The catalina.sh script I have from my tomcat 7 download on a IBM i 7.1 installation has no references to an sdk that I didn't specifically put there. On my particular installation there are two Java 6 JDK's:

/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit
and
/QOpenSys/QIBM/ProdData/JavaVM/jdk626/32bit

I know of nothing in the vanilla catalina.sh that references these or any other JAVA_HOME values. I set the JAVA_HOME environment variables manually so my *modified* scripts have references to these paths, overriding any other environment settings.

I am not sure why you would say that catalina.sh *expects* that path. I can't find a reference to it....

Pete Helgren
Value Added Software, Inc
www.petesworkshop.com
GIAC Secure Software Programmer-Java


On 12/6/2011 4:08 PM, James Lampert wrote:
I just downloaded and extracted Tomcat 7 on a customer V7 box, and we
seem to have hit a brick wall in the installation:

catalina.sh expects to find Java at "/QIBM/PRODDATA/JAVA400/JDK6," and
there is no "/QIBM/PRODDATA/JAVA400/JDK6" on this box.

Anybody know what to do about this? According to GO LICPGM, Java is
*there* but according to WRKLNK, it's *not* where it is on our V6 box.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.