For my third post in the WebSphere Process Server Install space, I thought I'd tackle Fix
Pack 3 (v184.108.40.206) install since I've seen quite a few common questions
in this area. Especially in the NON-GUI, no-internet connectivity area.
Please note that this post will talk about only about installing the fix pack
. You'll still need to review the official instructions
for upgrading your profiles and such.
As a very quick refresher, Installation Manager (IM) is what is used to
install WebSphere Process Server (WPS) from v7+ onwards. WebSphere
Application Server (WAS), generally speaking, is still installed via
Update Installer. So you had to install WAS first and then IM and then
Starting with the WPS FP3, WAS Fix Pack 11 (v220.127.116.11) is installable
via IM (v1.4.1+). In a nutshell, what this means is that you can
download all the repositories needed for installing WPS FP3 and just run
IM over a response file to install FP3. Note that WAS as a stand-alone
is still installable via Update Installer only. Only if you're
installing WAS for WPS would you need IM. Any WAS fixes that are in the
IM repository format (.zip file) will be installed via IM.
WPS FP3 has the following requirements:
- Minimum Installation Manager level of 1.4.1
- Minimum WAS level of 18.104.22.168
- Minimum XML Feature Pack level of 22.214.171.124
- Minimum SCA Feature Pack level of 126.96.36.199
+ Mandatory WPS FP3 and WAS FP11 fixes
Before you can actually install WPS FP3 (and associated components), you will need to do a bit of housekeeping:
0. Download the required repositories.
1. Update your IM to 1.4.1 if you haven't already in the past.
2. If you haven't done anything to the underlying WAS, install Update Installer since you need it to remove a couple of fixes.
Note: If you have previously updated or modified the underlying WAS
v188.8.131.52 (that came with the base WPS v184.108.40.206) e.g., updating to
anything above v220.127.116.11 or installing any WAS specific fixes - you may
have the v7.0.0+ Update Installer already.
0. Downloading the required repositories:
- Download WPS FP3
- Download WPS FP3 Mandatory Fixes
- Download WAS FP11 - This is a pretty big file, try to use a download manager that can do multiple streams, paused/resume downloads etc
- Download WAS FP11 Mandatory Fixes
- Download WAS 7.0 Import repository
- Download XML Feature Pack 18.104.22.168
- Download XML 1.0 Import repository
- Download SCA Feature Pack 22.214.171.124
- Download SCA 1.0 Import repository
Note: These downloads will take a while so you can continue with the following steps:
Important Note: Please note that FP3 installation takes a while to finish so it is highly recommended to NOT use a direct putty session to the machine/environment where you're doing the installation. Please consider either using a remote session into another machine on the same network and then ssh into your target environment to run the installation commands. This will ensure that the installation process doesn't die even if you lose your connection to the remote machine.
1. Updating IM to 1.4.1:
- Download the IM 1.4.1 repository from this link.
- Unzip to any temporary location and from that directory run this command:
install --launcher.ini silent-install.ini -dataLocation PATH_TO_IM_DATALOCATION -showVerboseProgress -log /tmp/IM1.4.1_Upgrade.log
Note: Make sure to add the -dataLocation parameter if it's in a
different location from the default /var/ibm/InstallationManager
location otherwise this will corrupt your IM installation.
- Once installation finishes, you can verify the IM version by running the
following from under the 'eclipse' folder in IM installation:
$./IBMIM --launcher.ini silent-install.ini -version
Internal Version 1.4.1000.20100810_1125
2. Install Update Installer:
During the WPS v7 installation process, when WAS v126.96.36.199 is installed, a
couple of WAS fixes [SDKPM00452.pak and
188.8.131.52-WS-WAS-<platform><arch>-IFPK98944.pak] are silently
installed. These fixes need to be removed using Update Installer since
they cannot be removed by IM.
- Download and install the latest Update Installer .
- Run the Update Installer to remove the two maintenance packages above that were installed silently.
Once the downloads are complete from Step 0 above, unzip them into
individual directories. Next grab the template response file for IM from
this link and make the following modifications:
1. Once you read the Terms and Conditions and agree to them, change the acceptLicense to 'true'.
2. In the <server> section, comment out the http:// public.dhe live repository since you've already downloaded all the required stuff.
3. Following sample cues in the XML, add the individual directories of the repositories in the <repository> tags.
4. Point the installLocation and eclipseLocation to your currrent WPS installation and change the id to the id that IM identifies this WPS installation by. You can get more information about finding these values from my earlier technote.
5. If you have updated or modified your underlying WAS in ANY way - uncomment the <import> section so IM will synchronize its registry with whatever WAS is currently at.
6. For the next block of <offering> inside the <install> section, update only the 'profile' with the 'id' of the WPS installation (see 4 above) and leave the version and id as they are.
7. Point the 'eclipseCache' property to the eclipseCache (Shared Resources) directory for your WPS/IM installation.
8. Leave the 'com.ibm.cic.common.core.preferences.searchForUpdates' and 'offering.service.repositories.areUsed' to false since we do not want IM attempting to connect to the internet.
Once done with updating the response file, make sure to cross check
everything. Cross check the repository locations with the directories on
your machine/mount/drive. Make sure the 'id' is picked up correctly from the installed.xml from within IM's dataLocation folder.
After confirming and validating everything, go ahead and run the following command (note: use user-silent-install.ini for a non-root user)
./IBMIM --launcher.ini silent-install.ini -input response-file.xml -showVerboseProgress -log /tmp/FP3-install.log
A successful install should not throw any errors and you can also verify
your WPS installation by running the versionInfo command from the
Well.. that's about it. Hopefully I was able to explain and lay out the
steps required in installing WPS Fix Pack 3. If you have any comments or
questions, please do leave them in the comments below and I'll be sure
to respond as soon as possible.