The WASPreUpgrade command is a migration tool that saves the configuration and applications of a previous version or release to a Version 6.0.x application server node.
The command file is located and should be run in the app_server_root/bin directory.
WASPreUpgrade.sh backupDirectory currentWebSphereDirectory [admin_node_name] [-nameServiceHost host_name [-nameServicePort port_number ]] [-import xmiDataFile ] [-traceString trace_spec [-traceFile file_name ]]
WASPreUpgrade.bat backupDirectory currentWebSphereDirectory [admin_node_name] [-nameServiceHost host_name [-nameServicePort port_number ]] [-import xmiDataFile ] [-traceString trace_spec [-traceFile file_name ]]
The parameters are as follows:
If you are migrating a configuration that does not use the default server-cfg.xml file, you must include this parameter to specify the fully-qualified name of the configuration file.
This parameter is only valid when upgrading from WebSphere Application Server Advanced Single Server Edition, Version 4.
The WASPreUpgrade tool displays status to the screen while it runs. The tool also saves a more extensive set of logging information in the WASPreUpgrade.log file written to the backupDirectory directory, where backupDirectory is the value specified for the backupDirectory parameter. You can view the WASPreUpgrade.log file with a text editor.
WASPreUpgrade migrates all of your resources and applications, but it does not migrate entities in your classes directory.
Migration saves the following files in the backup directory.
WASPreUpgrade also saves all instances created in the Version 5.x environment.
This example specifies a backup directory named backupDirectory, and identifies the root of the existing installation as d:\WebSphere\AppServer.
WASPreUpgrade backupDirectory d:\WebSphere\AppServer your_node_name