Install Fixpacks

Installing WebSphere Fixpacks

You must have enough free space on the filesystem where WebSphere is installed before you install any fixpacks.

For fixpack 3, 4, 5, and 6 you need to have at least 115Mb free.
Before running a fixpack install, shut down the WebSphere server, apache, and any WebSphere-related java processes. From the fixpack_4 README:
"Stop any java process that are running out of the IBM WebSphere Application java installation. For instance, The Application Assembly Tool (AAT) and third-party applications that use WebSphere JRE (e.g. Tivoli Manager for WebSphere)."
When installing fixpacks 3, 4, 5, or 6 make sure you are root, but with the osg user's environment. In other words, when becoming root, enter:
```
su - osg
su
	  
```
So, you first become the osg user with the osg user's environment. Then you "su" to root while still retaining the same environment.

Install the fixpack. Fixpacks are currently located under: /nerdc/src/bff/websphere/v4.0.1/<fixpack_name>.

As of this writing, the latest fixpack is Fixpack 6. I recommend that you only install this one, since there is no advantage to installing earlier fixpacks in addition to Fixpack 6.

Fixpack 6:

	Note
	It is required that any Fixes installed since the previous FixPak installation be uninstalled before this FixPak is installed. The FixPak will detect if there are any Fixes that are installed that need to be uninstalled. The FixPak will also uninstall these Fixes for the user. However, the user must determine whether each Fix must be re-applied following the FixPak installation.

Run the following command:

WAS_UPDATE_HOME=/usr/IBMWebAS4 ./install.sh -Silent

Since fixpack_6 provides an EAPI-compatible apache plugin, make sure to modify apache's httpd.conf to load the new module:

LoadModule app_server_http_module /usr/IBMWebAS4/bin/mod_app_server_http_eapi.so

fixpack_6 makes the WebSphere JDK unreadable to non-root users. To fix this specific problem, do the following (as root):

cd /usr/IBMWebAS4/java
chmod -R a+r .

Fixpack 5:
Run the following command:
```
WAS_UPDATE_HOME=/usr/IBMWebAS4 ./install.sh -Silent
	         
```
Since fixpack_5 provides an EAPI-compatible apache plugin, make sure to modify apache's httpd.conf to load the new module:
```
LoadModule app_server_http_module /usr/IBMWebAS4/bin/mod_app_server_http_eapi.so
		
```

Fixpack 4:

Run the following command:

WAS_UPDATE_HOME=/usr/IBMWebAS4 ./install.sh -Silent

Unfortunately, the JDK installed with fixpack_4 has given us problems on the SP. To remedy this, you should replace the java directory with a newer one that IBM has provided for us:

cd /usr/IBMWebAS4
mv java/ java_bu/
cd /nerdc/src/bff/websphere/v4.0.1/jdk
gunzip ca131-20021107-repkg.tar.gz
tar xf ca131-20021107-repkg.tar
mv java/ /usr/IBMWebAS4
gzip ca131-20021107-repkg.tar

Since fixpack_4 provides an EAPI-compatible apache plugin, make sure to modify apache's httpd.conf to load the new module:

LoadModule app_server_http_module /usr/IBMWebAS4/bin/mod_app_server_http_eapi.so

Fixpack 3:

Run the following command:

WAS_UPDATE_HOME=/usr/IBMWebAS4 INSTALL_IHS=false ./install.sh -Silent

Fixpack 2:
Run the following command:
```
WAS_DIR=/usr/IBMWebAS4 IHS_INSTALL=false ./install.sh -silent
		
```
Fixpacks have an unfortunate tendency to mess up file permissions after they run, since you run them as root.

In particular, fixpack_2 makes the WebSphere JDK unreadable to non-root users. To fix this specific problem, do the following (as root):
```
cd /usr/IBMWebAS4/java
chmod -R a+r .
		
```