Before installing IBM JDK 118, you should ensure a clean installation of the
Java environment. This involves removing any existing Java virtual machine
and runtime environments, unless they are necessary for any other
For example, we queried the Linux distributions with the command:
rpm qa | grep jdk
We found that Caldera eDesktop 2.4 installs JDK 1.2.2 1 by default. Our
scenario requires IBM JDK 118. Hence, the default JDK was removed with
rpm e jdk 1.2.2 1
22.214.171.124 Installing IBM JDK 118
Our JDK target installation is in the /opt directory.
The JDK118 distribution is in tar format and gzipped. Logged in as the user
root, we change the working directory to the target installation directory, /opt,
then used the
command to uncompress and untar this file,
ibm jdk l118 linux x86.tgz.
Since we will be installing IBM HTTP Server and WebSphere after installing
the JDK, we also define and export the environment variable JAVA_HOME to
indicate where the JDK has been installed.
Figure 23 shows the results of issuing the
commands on our
front end server.
[root@bdtest2 /opt]# tar zxf /mnt/cdrom/Java/ibm jdk l118 linux x86.tgz
[root@bdtest2 /opt]# export JAVA_HOME=/opt/jdk118/
Figure 23. Installing IBM JDK118 on the front end server
2.4.4 IBM HTTP Server
IBM HTTP Server installation is performed while logged in as the root user.
We encountered some problems using the Apache Web server that comes
bundled with RedHat 6.2 and Caldera eDesktop 2.4. If WebSphere is installed
with the Apache Web server module, and Apache restarted, Apache
complains about the Apache 1.3 API used by the WebSphere module. Figure
24 illustrates this error on RedHat 6.2.
Chapter 2. Setup and configuration