Migrating from Version 4.0.x to a remote standalone Version 6.0.x machine

Use the migration tools to migrate from Version 4.0.x to a remote standalone Version 6.0.x machine.

Before you begin

Typically, you can use the WASPreUpgrade and the WASPostUpgrade migration tools from WebSphere Application Server Version 6.0.x to upgrade from Version 4.0.x to Version 6.0.x on the same machine.

However, some scenarios require that you migrate the Version 4.0 configuration on one machine to Version 6.0.x on a different machine. One of these scenarios is when you install new machines for your latest Version 6.0.x environment but need to migrate your existing Version 4.0.x configuration from other machines.

About this task

This article describes using the Version 6.0.x migration tools to migrate the following products:

The WASPreUpgrade tool saves the existing Version 4.0 configuration into a migration_specific_backup directory. The WASPostUpgrade tool uses this directory to add the old configuration settings to the new Version 6.0.x environment.

Procedure

  1. Obtain the Version 6.0.x product CD-ROM.

    On this CD is the migration/bin directory. This directory contains a special environment that you can use to run the WASPreUpgrade tool without installing Version 6.0.x.

  2. Save the current configuration using the WASPreUpgrade script from the /migration/bin directory of the Version 6.0.x product CD-ROM, which you must mount to the Version 4.0 machine. Save the configuration in the migration_specific_backup directory on the Version 4.0 machine.
    WASPreUpgrade /opt/tmp/migration_specific_backup /opt/websphere/appserver admin_node_name
    For all scenarios except Version 4.0.x Advanced Single Server Edition, verify that the administrative server of the existing environment is running. The WASPreUpgrade tool provides status to the screen and to log files in the migration_specific_backup directory. ASCII log file names start with the text WASPreUpgrade and include a date and timestamp.

    The WASPreUpgrade tool saves selected files from the Version 4.0.x /bin directory. It also exports the existing application server configuration from the Version 4.0.x repository. The WASPreUpgrade tool calls XMLConfig to export the existing Version 4.0.x repository to the websphere_backup.xml file in the migration_specific_backup directory.

    Version 4.0.x Advanced Single Server Edition does not require the administrative server to run at the time of migration. The WASPreUpgrade tool copies the server-cfg.xml file from the app_server_root/config directory to the migration_specific_backup/config directory.

    If errors occur while running the WASPreUpgrade tool, you might have to apply fixes to the Version 4.0 installation to successfully complete the export step. See the IBM Support page for the latest fixes that might be applicable. When viewing this information from the information center, click Support to link to the IBM Support page.

  3. Copy the migration_specific_backup directory from the Version 4.0 machine to the Version 6.0.x machine. Use the ftp command, shared storage, or some other mechanism to copy the file to the new machine.

    Perform the following steps on the machine with WebSphere Application Server Version 6.0.x.

  4. Copy the migration_specific_backup/websphere_backup.xml or the migration_specific_backup/config/server-cfg.xml file and store it as an archive. You edit the original file in the next step.
  5. Edit the migration_specific_backup/websphere_backup.xml or the /migration_specific_backup/config/server-cfg.xml file to correct machine-dependent settings.
    1. Change the node name in the migration_specific_backup/websphere_backup.xml file. There is no node name in the migration_specific_backup/config/server-cfg.xml file. If you are using the same node name for the Version 6.0.x machine that you use for the original Version 4.0.x configuration, do not change the name. Otherwise, you must change all occurrences of the Version 4.0.x node name to the node name you are using for WebSphere Application Server Version 6.0.x. The node name occurs in many XML stanzas throughout the file. Failing to change all occurrences results in an incomplete migration of data.
    2. Change the path names in the migration_specific_backup/websphere_backup.xml or the migration_specific_backup/config/server-cfg.xml file. The configuration file refers to path names in many XML stanzas throughout the file. Update any reference to a file outside of the Version 4.0.x directory structure to the equivalent directory on the new machine, even if you must create an equivalent directory. The implication of configuring a matching environment means that you might have to copy the original directory to the Version 6.0.x machine. Or you might have to install the appropriate software.
    3. Check files in the properties directories for references that contain path names. In particular, edit the migration_specific_backup/properties/sas.client.props and the migration_specific_backup/properties/TraceSettings.properties files to correct machine-dependent settings. Make the following changes in the file:
      1. Change the path values of any property in the file.

        Each property file contains properties that refer to paths. Update any reference to a file outside of the Version 4.0.x directory structure to the equivalent directory on the new machine, even if you must create an equivalent directory.

      2. Correct specification styles for path values that are dependent on the operating system.

      You must correct path specifications if they differ from what works on the machine running Version 6.0.x.

    4. Correct specification styles for path names that are dependent on the operating system. You must correct path specifications if they differ from what works on the machine running Version 6.0.x. For example, if you are moving from Version 4.0.x on a Windows platform to Version 6.0.x on a Linux platform, change any Windows-specific path in the configuration file to use the Linux path style. Change c:\mystuff\somepath to /opt/mystuff/somepath.
    5. Change user IDs and passwords to match security requirements. You might have to change user IDs and passwords if they are not identical to those in use on the Version 6.0.x machine.

      To change an encoded password to a clear-text password, change <password>{xor}LCoxayht</password> to <password>mypassword</password>.

    6. Change other machine-specific information. The configuration might refer to other software products or configurations that do not exist on the new machine. For example, the old machine might have a database. The Version 6.0.x configuration should still point to the database on the old machine, possibly. Modify the data source to point to the database on the Version 4.0.x machine.
  6. Install the Version 6.0.x product.
  7. Use the Profile creation wizard to create a Version 6.0.x profile.
  8. Add the Version 4.0.x configuration to the Version 6.0.x configuration. Use the WASPostUpgrade tool in the app_server_root/bin directory of Version 6.0.x to add the Version 4.0.x configuration to the Version 6.0.x configuration.
    WASPostUpgrade /opt/tmp/migration_specific_backup
    The WASPostUpgrade tool records detailed information specific to each enterprise bean it deploys, in the migration_specific_backup/WASPostUpgrade.log file.
  9. Configure WebSphere Application Server after migration. This is a way of verifying the results of the migration tools. You can read Configuration mapping during migration to learn more about the results of migration. This article has a detailed description of how the migration tools migrate objects, and what you should verify.
  10. If you migrated from a machine being run as non-root on a Linux or UNIX platform, perform additional steps.
    1. Set up the deployment manager to run as a non-root user.
    2. Set up the application server and the node agent process to run as non-root.

Results

You have migrated WebSphere Application Server from Version 4.0.x to a remote Version 6.0.x machine.

What to do next

Return to Migrating product configurations to continue.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 7:21:45 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=tinsmanualmigdif3
File name: tins_manualmigdif3.html