Migrating from an operating system that is no longer supported

Why and when to perform this task

You can migrate an earlier WebSphere Application Server Version 3.5.x or Version 4.0.x release that is running on an operating system that Version 5.x does not support.

Steps for this task

  1. Start up the WebSphere Application Server Version 3.5.x or Version 4.0.x Administrative Server.
  2. Run the WASPreUpgrade command line migration tool.
    There are two options. You can run the command from the migration\bin (or migration/bin) directory in the platform_root of the Version 5 CD-ROM. Or, you can copy the files in the directory on the CD-ROM to a directory you create on your hard drive.

    Identify the Version 3.5.x or 4.0.x release, and identify a backup directory where the command stores configuration files and migrating applications from the earlier version. See the WASPreUpgrade topic for command syntax.

    1. Run the command from the migration\bin (or migration/bin) directory in the platform_root of the Version 5 CD-ROM.
      Identify the backup directory and the location of the configuration files.
      CD_drive:\WASPreUpgrade backupDirectory filepath\WebSphere\AppServer yourNodeName
      
      If this works, go to Step 4. If this does not work for some reason, perform steps 2B through 2F.
    2. Make a migration directory on your hard drive.
    3. Copy the WASPreUpgrade.bat (or WASPreUpgrade.sh) and the setupCmdLine.bat (or setupCmdLine.sh) files from the migration/bin directory in the platform_root of the Version 5 CD-ROM, to the directory you created on your hard drive.
    4. Edit the setupCmdLine.bat (or setupCmdLine.sh) file in your new directory.
      Change the following variables:
      • WAS_HOME to point to the fully qualified path to the migration directory you created
      • JAVA_HOME to point to the fully qualified path to your IBM Developer Kit or the Java directory
    5. Ensure that the executable bit is on for the setupCmdLine.sh and WASPreUpgrade.sh files in the directory that you created on your hard drive.
    6. Run the command from the migration directory you created.
      Identify the backup directory and the location of the configuration files.
      yourMigrationDirectory\WASPreUpgrade backupDirectory filepath\WebSphere\AppServer yourNodeName
      
  3. Shut down the WebSphere Application Server Version 3.5.x or Version 4.0.x release by stopping all server nodes in the configuration, including the administrative server node.
  4. Tar or zip the backup directory and FTP it to another system.
  5. Install the new operating system, keeping the same host name.
    If possible, keep the system name and passwords the same as the old system. Place any database files related to applications you are migrating in the same path as the previous system. In general, try to keep paths the same. However, do not install Version 5 in the same directory as the previous version. If you do change paths and names, you can edit the XML configuration files to reflect the changes. Make such changes before running the WASPostUpgrade command below.
  6. FTP the backup directory from the other system and unzip it.
  7. Install WebSphere Application Server, Version 5. Do not select the migration option, if it appears.
  8. Run the WASPostUpgrade command line migration tool, from the bin directory of the Version 5 install_root.
    Specify the backup directory (and any non-standard configuration file name in the directory) that the WASPreUpgrade command created. See the WASPostUpgrade topic for proper command syntax.
    install_root\bin\WASPostUpgrade  WAS_HOME\migration
    

What to do next

Return to Migrating administrative configurations to continue.

Related concepts
Migrating
Configuration mapping during migration
Migration tools
Related tasks
Migrating configuration data



Searchable topic ID:   tins_migOS
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/tins_migOS.html

Library | Support | Terms of Use | Feedback