|
Problem |
Installing WebSphere Application Server (WAS) 4.0.1 into the same
directory as an existing WAS 3.5 installing will not work correctly. Here
is how to recover on a Unix system after installing WAS AE 4.0.1 into WAS
3.5X dir without first uninstalling WAS 3.5X. |
|
Solution |
This scenarios
uses a WAS 3.5.3 Advanced Edition (AE) to 4.0.1 AE migration
scenario.
Introduction
As a first step we would recommend archiving the WAS install
directory before attempting this migration scenario, typically using
the tar command.
On Solaris, removing of package repository entries is covered.
The following are steps provided by the WAS Install team for
continuing migration when a 4.0.1 install was attempted (into the same
directory as the 3.5 install) before uninstalling the 3.5 install, but
after the first stage of migration or removing of the 3.5 JDK directory.
A 4.0 install to the same directory as the 3.5 install should involve
an uninstall of WAS 3.5 as well as removal of all non-migration
directories from the install path before the second stage of the migration
install is begun.
Steps
Steps to work around the migration problem resulting from migrating
from 3.5.3 to 4.0.1:
Note: Steps 2 and 3 are Solaris-specific.
1. Remove everything from the <was root> directory except the
migration directory ( where you have backed up the 3.5.x
configuration and apps during the first stage of the install ).
2. cd /var/sadm/pkg. Remove all directories starting with WS* and
itj*. ( These are WAS packages for 3.5.3 )
3. cd /var/sadm/spool. Remove all directories staring with WS* and
itj*. ( These are WAS packages for 3.5.3 )
4. For an AIX installation:
- cd
/usr/lpp
- Remove IBMWebAS* with the
command rm -rf IBMWebAS* . Make sure that you are
in the /usr/lpp directory before running this command.
- Using AIX smit or smitty
and remove every package which is the WebSphere package. All the WebSphere
packages start with IBMWebAS.base.*
5. You should have the WAS_Migration_Temp.properties file in /tmp
directory. If you don't, then you can copy it from the directory
$WASROOT/migration/backup to the /tmp directory.
6. Now run the install. It will automatically invoke the second
step of migration. It is not necessary to run the first stage of
install, since all files are already backed up in the migration
directory.
7. Choose either Typical or Custom for a successful completion of
second step process of migration.
|
|
|
|
|
|
|