The WASPostUpgrade command is a migration tool for adding the configuration and applications of a previous version or release to the current WebSphere Application Server node. The configuration includes migrated applications. The tool adds all migrated applications into the install_root/installedApps directory of the current product. The tool locates the saved configuration that the WASPreUpgrade tool saves through a parameter you use to specify the backup directory.
Location of command file
The command file is located in the install_root/bin directory. The command file is a script named WASPostUpgrade.sh for Linux and UNIX-based platforms or WASPostUpgrade.bat for Windows platforms.
WASPostUpgrade.sh command syntax for Linux and UNIX-based platforms
The command syntax is as follows:
WASPostUpgrade.sh backupDirectory [-import xmi_data_file] [-cellName cell_name] [-nodeName node_name] [-serverName server_name] [-webModuleAdditionalClasspath classpath] [-documentRootLimit number] [-substitute "key1=value1[;key2=value2;[...]]"] [-portBlock port_starting_number] [-backupConfig true | false] [-replacePorts true | false] [[-traceString trace_spec [-traceFile file_name]]The first argument is required.
WASPostUpgrade.bat command syntax for Windows platforms
WASPostUpgrade backupDirectory [-import xmi_data_file] [-cellName cell_name] [-nodeName node_name] [-serverName server_name] [-webModuleAdditionalClasspath classpath] [-documentRootLimit number] [-substitute "key1=value1[;key2=value2;[...]]"] [-portBlock port_starting_number] [-backupConfig true | false] [-replacePorts true | false] [[-traceString trace_spec [-traceFile file_name]]
The first argument is required.
Parameters
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 nodeNameBean.cellName= "nodenameNetwork" parameter in the silent installation options response file.
No equivalent parameter is available in the silent installation options response file.
This parameter is ignored when migrating
from V5.0.x, including WebSphere Application Server- Express, V5.
When migrating a configuration that uses anything other than the default server-cfg.xml file name, you must use the -import option along with the path 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.
This parameter is equivalent to the -W nodeNameBean.nodeName= "nodenameManager" parameter in the silent installation options response file.
No equivalent parameter is available in the silent installation options response file.
In the input XML data file, each key appears as $key$ for substitution. This argument substitutes any occurrence of $NODE_NAME$ with admin_node and $APP_SERVER$ with default_server in the input XML file.
If the substitution string contains semicolons, use $semiColon$ to distinguish the string from the ";" delimiter. On Linux and UNIX-based platforms, add an escape character to each dollar sign ($) within the substitution string (for example, \$semiColon\$).
This parameter is applicable for configurations saved from Advanced Edition, Versions 3.5.x and 4.0.x.
No equivalent parameter is available 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 WASPostUpgrade tool displays status to the screen while running. This tool also saves a more extensive set of logging information in the logs directory. You can view the WASPostUpgrade.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 separate configuration files incrementally 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 the 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"