You can use the migration tools to perform a manual migration between two machines.
Before you begin
Typically you can use the WASPreUpgrade and the WASPostUpgrade migration tools from V5.0.x of WebSphere Application Server to upgrade from either V3.5 or V4.0 to V5.x on the same machine.However, some scenarios require that you migrate the V3.5 or the V4.0 configuration on one machine to V5.0.x on a different machine. One of these scenarios is when you install new machines for your latest V5.0.x environment but need to migrate your existing V3.5.x or V4.0.x configuration from other machines.
Why and when to perform this task
This topic describes using the V5.0.x migration tools to migrate the following products:The WASPreUpgrade tool saves the existing V3.5 or V4.0 configuration into a migration-specific-backup directory. The WASPostUpgrade tool uses this directory to add the old configuration settings to the new V5.0.x environment.
Steps for this task
WASPreUpgrade /opt/tmp/migration-specific-backup /opt/websphere/appserver adminNodeNameFor all scenarios except V4.0.x Advanced Single Server Edition, verify that the administrative server of the existing environment is running.
The WASPreUpgrade tool saves selected files from the V3.5.x or V4.0.x /bin directory. It also exports the existing Application Server configuration from the V3.5.x or V4.0.x repository. The WASPreUpgrade tool calls XMLConfig to export the existing V3.5 or V4.0 repository to the websphere_backup.xml file in the migration-specific-backup directory.
V4.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 install_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 V3.5 or V4.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.
Perform the following steps on the machine with V5.x of WebSphere Application Server.
Each property file contains properties that refer to paths. Update any reference to a file outside of the V3.5 or V4.0 directory structure to the equivalent directory on the new machine, even if you must create an equivalent directory.
You must correct path specifications if they differ from what works on the machine running V5.0.x.
To change an encoded password to a clear-text password, change <password>{xor}LCoxayht</password> to <password>mypassword</password>.
WASPostUpgrade /opt/tmp/migration-specific-backup
Results
This procedure results in migrating WebSphere Application Server from V3.5.x or V4.0.x to a remote V5.0.x machine.What to do next
Return to Migrating configuration data to continue.