The WASPreUpgrade command is a migration tool that saves the configuration and applications of a previous version or release to a Version WebSphere Application Server node or Network Deployment node.
Location of command file
The command file is located in the install_root/bin directory. The command file is a script named WASPreUpgrade.sh for Linux and UNIX-based platforms or WASPreUpgrade.bat for Windows platforms.
WASPreUpgrade.sh command syntax for Linux and UNIX-based platforms
The command syntax is as follows:
WASPreUpgrade.sh backupDirectory currentWASDirectory [adminNodeName] [-nameServiceHost host_name [-nameServicePort port_number ]] [-import xmiDataFile ] [-traceString trace_spec [-traceFile file_name ]]
WASPreUpgrade.bat command syntax for Windows platforms
WASPreUpgrade backupDirectory currentWASDirectory [adminNodeName] [-nameServiceHost host_name [-nameServicePort port_number ]] [-import xmiDataFile ] [-traceString trace_spec [-traceFile file_name ]]
Parameters
The first two arguments are required and positional. The third argument is required and positional only when upgrading from WebSphere Application Server, Version 3.5.x or Advanced Edition, Version 4.0.x.
Supported arguments include:
No equivalent parameter is available in the silent installation options response file.
This parameter is equivalent to the -W migrationInformationPanelBean.migrationBackupDir= "/tmp/migrationbackup" parameter in the silent installation options response file.
This parameter is equivalent to the -W previousVersionPanelBean.selectedVersionInstallLocation= "/opt/WebSphere/AppServer" parameter in the silent installation options response file.
When migrating a configuration that uses anything other than the default server-cfg.xml file name, you must use the -import option along with a path to point to the non-default XMI configuration file. You also must use the -import and path option when running the WASPostUpgrade tool later, to point to the non-default XMI configuration file in the directory created by the WASPreUpgrade tool.
This parameter is equivalent to the -W previousVersionPanelBean.selectedVersionConfigFile= "/opt/WebSphere/AppServer/config/server-cfg.xml" parameter in the silent installation options response file.
No equivalent parameter is available in the silent installation options response file.
No equivalent parameter is available in the silent installation options response file.
Logging
The WASPreUpgrade tool displays status to the screen while it runs. The tool also saves a more extensive set of logging information in the backup directory. You can view the WASPreUpgrade.log file with a text editor.
Migrating from V3.5.x Standard Edition or Advanced Edition, or from V4.0.x Advanced Edition
The following example specifies a backup directory named backupDirectory, and identifies the root of the existing installation as d:\WebSphere\AppServer.
WASPreUpgrade backupDirectory d:\WebSphere\AppServer yourNodeName
Migrating from V4.0.x Advanced Single Server Edition with multiple backup directories
This example shows how to migrate incrementally, to migrate separate configuration files from a single node with a single installation of WebSphere Application Server Advanced Single Server Edition. To migrate more than one configuration file, you must run the WASPreUpgrade tool multiple times to multiple backup directories because not all of the applications are in the same installedApps directory. For this reason, using a single backup directory for all runs of the WASPreUpgrade tool is not recommended. Use a separate backup directory for each run. The intent of this example is to show how to migrate a single node with multiple configuration files.
> WASPreUpgrade C:\WAS4ABBACKUP G:\WebSphere\AppServer > WASPreUpgrade C:\WAS4CDBACKUP G:\WebSphere\AppServer -import G:\WebSphere\AppServer\config\myServer1-cfg.xml > WASPreUpgrade C:\WAS4EBACKUP G:\WebSphere\AppServer -import G:\WebSphere\AppServer\config\OldServer-cfg.xml
> WASPostUpgrade C:\WAS4ABBACKUP > WASPostUpgrade C:\WAS4CDBACKUP -import C:\WAS4CDBACKUP\myServer1-cfg.xml > WASPostUpgrade C:\WAS4EBACKUP -import C:\WAS4EBACKUP\OldServer-cfg.xml