Apply latest fix pack to V4.0 before migrating applications to V4.0
 Technote (FAQ)
 
Problem
Before migrating your WebSphere® Application Server V3.5 environment/applications to WebSphere Application Server V4.0 apply the latest WebSphere Application Server V4.0 fix pack.
 
Solution
If you plan to migrate your applications and configurations to WebSphere Application Server V4.0 from an earlier version of WebSphere Application Server, first apply the latest WebSphere Application Server fix pack before migrating to the V4.0 environment.

Prerequisite steps:
  1. Install WebSphere Application Server V4.0.1,
  2. apply the latest fix pack, listed in Recommended Updates
  3. Migrate application and configuration

This process might not be as obvious if you are using the WebSphere Application Server V4.0 migration tools.

The WebSphere Application Server V4.0 provides 2 migration tools scripts:
  1. WASPreUpgrade.sh (WASPreUpgrade.bat for Windows®)
  2. WASPostUpgrade.sh (WASPostUpgrade.bat for Windows)
Note: These tools are automatically executed when using the graphical interface, install.sh or install.bat for Windows. They may also be executed manually from the command line.

To illustrate a typical use of the tools assume you want to do the following:
  • Upgrade a WebSphere Application Server V3.5.6 environment to WebSphere Application Server V4.0.
  • Migrate the applications and configurations to WebSphere Application Server V4.0.
  • Install WebSphere Application Server V4.0 in the same directory previously used for the V3.5.6. You will need to remove the V3.5.6 installation before installing WebSphere Application Server V4.0 to meet this requirement. **

To accomplish this, perform the following procedure:
  1. Start WebSphere Application Server V3.5.6 administrative server.
  2. Start the WebSphere Application Server V4.0.1 install.sh script (install.bat for Windows).
  3. The install GUI will detect that a version of WebSphere Application Server is installed and provide you the option of migrating the previous version to the WebSphere Application Server V4.0.1 version.
  4. If you check the box to migrate the previously installed WebSphere, install will provide you a panel to choose options needed for the WASPreUpgrade.sh script.
  5. Install will execute the WASPreUpgrade.sh script resulting in a set of directories containing a backup of the V3.5.6 applications and configurations. The install program also stores the migration options you selected in step 4 allowing you to complete the migration at a later time.
  6. The GUI install script will automatically exit, allowing you the opportunity to uninstall WebSphere Application Server V3.5.6 and upgrade the prerequisites needed for WebSphere Application Server V4.0.1. Be careful you do not remove the directories created to back up V3.5.6 applications and configurations data from the previous step.
  7. Finally, execute the install.sh script a second time. The install script will now install WebSphere Application Server V4.0.1.

The install program will also detect that WASPreMigration script was previously executed and automatically migrate the V3.5.6 applications and configurations to the WebSphere Application Server V4.0.1 environment.

Hints and Tips:
It is best to have the latest fix pack installed before migrating the V3.5.6 applications and configurations to the WebSphere Application Server V4.0 environment. To accomplish this do the same steps as above except you will be performing steps 6a, 8 & 9.

Before running step 7; add step 6a.

6a) Remove information stored by the install concerning the WASPreUpgrade options as mentioned in step 5.
The location the install script stores the WASPreUpgrade options information will depend on the operating system as follows:
Windows - registry entry "HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere Application Server\Migration4.0"
UNIX - the file tmp/WAS_Migration_temp.properties.

As always, exercise caution when modifying the Windows registry. After this information is removed perform step 7 above. This will result in an installation of WebSphere Application Server V4.0.1 but will not migrate the 3.5.6 applications and configurations to the 4.0.1 environment. Migration of the 3.5.6 applications & configurations
are done by adding steps 8 & 9.

8) Ensure all WebSphere, Java and webserver components are stopped and install the latest Fix Pack.
9) Manually perform the WASPostUpgrade script to migrate the backed up 3.5.6 applications and configurations to the WebSphere Application Server V4.0 environment with the latest Fix Pack.***


Notes:
** WASPreUpgrade is automatically executed from the install process if you choose to do a migration. It will backup files from the following directories.
  • hosts
  • servlets
  • classes
  • deployableEJBs
  • deployedEJBs
  • properties

If you have application specific class/jar files at other locations you must take care to not delete these since WebSphere Application Server does not back them up. In addition they will need to be restored before running WASPostUpgrade since it expects these to exist if specified in the WebSphere Application Server VWebApp classpaths.

*** For more information concerning running the WASPostUpgrade manually consult the WebSphere Application Server Library.
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Migration
Operating system(s): HP-UX
Software version: 4.0
Software edition:
Reference #: 1111150
IBM Group: Software Group
Modified date: Mar 3, 2005