Michael R. Head (suppressingfire) wrote,
Michael R. Head
suppressingfire

  • Location:
  • Music:

Installing WAS 6.0 on RHEL 5u4

Recently, I found myself installing Websphere Application Server 6.0 on a current Red Hat Enterprise Linux 5u4 for x64. I was running
$ sudo ./install
from the WAS directory on the installation media, but I kept running into problems during the installation. At the console, the installer suggested to run with the -console switch, but that also failed. I checked /tmp/log.txt and found this:
(Apr 8, 2010 2:47:04 PM), Install, com.installshield.wizard.StandardWizardListener, err, could not initialize interface swing
That didn't provide enough information, but I guessed that the problem had to do with the JRE version (the installation media comes bundled with an embedded Java 1.4). I forced the installer to use my own Java 1.4 version, like so:
$ sudo ./install -is:javahome /usr/local/IBMJava2-amd64-142 -is:log /tmp/debug -is:tempdir /tmp
This also failed, but I was able to inspect the /tmp/debug file and found the command line that was failing:
LAUNCH_COMMAND=/usr/local/IBMJava2-amd64-142/bin/java -cp .:::::"setup.jar":::::: -Dtemp.dir="/tmp" -Dis.jvm.home="/usr/local/IBMJava2-amd64-142" -Dis.jvm.temp="0" -Dis.media.home="" -Dis.launcher.file="/storage/WAS-6.0/WAS/./install" -Dis.jvm.file="/tmp/istemp20434098162355/ibmjdk142.jvm" -Dis.external.home="/storage/WAS-6.0/WAS/." run 1>>/tmp/debug 2>>/tmp/istemp20434098162355/APP_STDERR
My goal was to use a more recent JDK, but it turns out that the installer checks the Java version and uses its embedded JRE if the version reported is anything but 1.4.2, so it wasn't helpful to run sudo ./install -is:javahome /usr/local/ibm-java-x86_64-60. However, with above command line, I could bypass the install script's version check and run the install manually like so:
$ sudo /usr/local/ibm-java-x86_64-60/bin/java -cp .:::::"setup.jar":::::: -Dtemp.dir="/tmp" -Dis.jvm.home="/usr/local/ibm-java-x86_64-60" -Dis.jvm.temp="0" -Dis.media.home="" -Dis.launcher.file="/storage/WAS-6.0/WAS/./install" -Dis.jvm.file="/tmp/istemp20434098162355/ibmjdk142.jvm" -Dis.external.home="/storage/WAS-6.0/WAS/." run
After running that command, the installer kicked off OK and I was able to complete the installation.


Update: In order to run the launchpad.sh program successfully, it appears to be necessary to do this first:
$ sudo ln -s /usr/bin/firefox /usr/bin/mozilla

Update 2: When running the update to 6.0.2.0, the same trick is possible, but the Java 6 JRE directory should be copied over to update directory, and the copied java should be used. If this isn't done, the updater will attempt to copy the JRE itself, and try to restart before completing the update, but that restart will fail.
$ cd /opt/IBM/WebSphere/AppServer/updateinstaller
$ sudo mv java/jre java/jre.bak
$ sudo cp -a /usr/share/java/jre java
$ sudo `pwd`/java/jre/bin/java -cp .:::::"update.jar":::::: -Dtemp.dir="/tmp" -Dis.jvm.home=`pwd`/java/jre -Dis.jvm.temp="1" -Dis.media.home="" -Dis.launcher.file="/opt/IBM/WebSphere/AppServer/updateinstaller/./update" -Dis.jvm.file="/tmp/istemp17189098175324/localibmjdk14X_unix.jvm" -Dis.external.home="/opt/IBM/WebSphere/AppServer/updateinstaller/." "-Xmx"384m "-Xms"48m run
The above command should be pulled out of a debug log file as above (that will create the istemp directory)

Update 3: I've been told that installing libXp and libXmu into RHEL 5u4 would allow Java 1.4 to spin up AWT, so an alternative to the above is to simply do this:
$ sudo yum install libXp libXmu
Tags: java, websphere
  • Post a new comment

    Error

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 0 comments