|
Problem(Abstract) |
Occasionally, it may become necessary to install a product
feature after the IBM® WebSphere® Application Server has been updated with
fix packs and/or cumulative fixes. This document describes a procedure for
how features can be installed. For example, attempting to install
WebSphere APAR PQ78370 (which is required by WebSphere Portal Server) will
fail if the Performance and Analysis Tools feature was not installed
originally. |
|
|
|
Cause |
Some features may not be realized as useful or necessary
until after fix packs and cumulative fixes have been installed. |
|
|
Resolving the
problem |
Simple Answer:
- Stop all WebSphere Application Server processes
- It is preferred that you uninstall all fixes, cumulative fixes, and fix
packs before installing a base (For example, V5.0) feature. It is
possible, however, that you may be able to perform the installation after
having only removed the fixes, and cumulative fixes, while will restore
the Application Server to the most recent fix level (For example, 5.0.2.0)
- Use the original Application Server installation CD's to install the
feature (e.g., the Performance and Analysis Tools (PAT) feature).
- Reinstall (or refresh) the Application Server fix pack, to install all
fixes related to the recently installed feature.
- Reinstall the Application Server cumulative fixes and fixes to restore
the product to the level at which you started (For example, 5.0.2.4)
Detailed Instructions:
Note: Perform these steps on a test system first to verify that
you are familiar with each step, and that you have all of the necessary
and required installation software available.
- Locate/retrieve all of the necessary installable software images
* WebSphere Application Server V5.0 install CD's
* Application Server V5.0 update installer
http://ibm.com/support/docview.wss?uid=swg24001908
* Application Server fix pack 2
http://ibm.com/support/docview.wss?uid=swg24005012
* Application Server cumulative fix 4 for the appropriate platform
- Make a backup your current installation
- Prepare the WebSphere Application Server fix pack 2
- Create a directory to contain the Application Server fixes, and the
updateInstaller (For example, maybe something like /opt/WebSphere/updates)
- Expand the fix pack 2 archive into this directory
- Expand the cumulative fix pack archive to this same directory
- Check the date of the updateInstaller that is present
- If the updateInstaller from the Web site is more recent, expand the
updateInstaller archive to this same directory structure, thus replacing
the version provided with the cumulative fix pack with the most recently
available version.
- Stop all of the WebSphere Application Server processes
- Verify that all Java.™ processes have terminated,
e.g., on UNIX® you can use the following command:
# ps -ef | grep [j]ava
- Initialize the environment variables using the setupCmdLine script
found in the Application Server bin directory:
# cd /opt/WebSphere/AppServer/bin
Note: The following command is very easy to mistype. In English, it is
read as "dot space dot slash setupCmdLine.sh"
# . ./setupCmdLine.sh
Verify that the script has been executed successfully
# echo $WAS_HOME
If the WAS_HOME environment variable has no value, the command was not
executed correctly.
# which Java
If the result does not indicate that the Java executable is from the
WebSphere Application Server directory structure, then the setupCmdLine
script was not executed correctly
- Change to the directory containing the Application Server
updateInstaller and expanded fixes
- If this directory contains a "java_tmp" directory, remove it, and its
contents using the following command:
# rm -rf java_tmp
- Execute the GUI version of the updateInstaller:
# ./updateWizard.sh
- Verify/identify the proper installation/location of the Application
Server to be updated. Make certain that you note the exact version of the
Application Server (For example, 5.0.2.4). This completely identifies the
version of the product (For example, 5.0), the level of the fix pack
(i.e., 2), and the level of the cumulative fix (For example, 4) that is
currently being used.
- Select the "Uninstall fix packs" option
Carefully uninstall all cumulative fix packs, one at a time, from the
most recent (i.e., highest number) to the oldest. For example, you could
have the following cumulative fix packs installed:
* Cumulative fix 1 - Name: was502_cf1...
* Cumulative fix 2 - Name: was502_cf2...
* Cumulative fix 4 - Name: was502_cf4...
You must select the highest numbered fix first (For example,
"was502_cf4...") and uninstall it. After it is successfully uninstalled,
you will have an opportunity to "run the wizard again" by clicking on a
button.
Repeat this step for all cumulative fixes.
- At this point, you should have your Application Server at version
5.0.2.0
- Use the WebSphere Application Server installation CD, and perform a
custom install. Select only the "Performance and Analysis Tools"
feature.
- Execute the updateWizard.sh script again.
- Select/Specify "Install fix packs" this time
- Install/refresh fix pack 2, so that all of the updates related to the
Performance and Analysis Tools can be applied.
- After this step has completed successfully, "run the wizard again", and
Install the proper cumulative fix to return to you the level at which you
started (For example, cumulative 4).
Note that if you had earlier cumulative fix packs installed, it is not
necessary to reinstall them. The name "cumulative fix pack" indicates that
each contains all of the fixes present in the earlier version. So, by
installing cumulative fix pack 4, you have installed all of the fixes
there were available in each of the preceding cumulative fix packs.
- After you have successfully installed this cumulative fix pack, you are
ready to install the original fix that you were trying to install when you
got to this point (For example, PQ78370). You can "run the wizard again",
and select the "Install fixes" in order to perform this installation. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|