I was wondering why by defualt both the setEnv.sh and startManagedWebLogic.sh scripts set a value for JAVA_HOME when the startManagedWebLogic script sources the setEnv script. I can see having the option to override the value in the startManagedWebLogic script, but why have it there by default? I am working on a migration to SP4, and (due to the new JDK) need to change more files than I would have otherwise. Can't I comment out the JAVA_HOME set in startManaged, and let the declaration in setEnv be my default for all scripts referencing it?
Thanks for any input.
Joined: Jan 21, 2002
Disregard. Don't know what I was thinking, but the startManaged script calls /common/bin/commEnv.sh, not the setEnv script. Still, there is a declaration of JAVA_HOME there too.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: JAVA_HOME in startManagedWebLogic and setEnv scripts