WASPreUpgrade command

The WASPreUpgrade command is a migration tool that saves the configuration and applications of a previous version or release to a Version 5.1 WAS node.

 

Location of command file

The command file is located in the $WAS_HOME/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 WAS, Version 3.5.x or Advanced Edition, Version 4.0.x.

Supported arguments include...

adminNodeName Optional, positional name of the node containing the administrative server for the currently installed product. The value of this argument must match the node name given in the topology tree on the Topology tab of the administrative console for the currently installed product. The WASPreUpgrade tool calls the XMLConfig tool using this parameter. This parameter is only required when upgrading from WAS Standard Edition, Version 3.5.x, WAS Advanced Edition, Version 3.5.x, or WAS Advanced Edition, Version 4.0.x.

No equivalent parameter is available in the silent installation options response file.

backupDirectory Required positional name of the directory in which the WASPreUpgrade tool stores the saved configuration and files, and from which the WASPostUpgrade tool later reads the configuration and files. The WASPreUpgrade tool creates the directory if the directory does not already exist.

This parameter is equivalent to the -W migrationInformationPanelBean.migrationBackupDir= "/tmp/migrationbackup" parameter in the silent installation options response file.

currentWASDirectory Required positional name of the installation root for the current V3.5.x, V4.x, or V5.0.x installation. This version can be either WebSphere Application Server Standard Edition, V3.5.x, WAS Advanced Edition, V3.5.x, any form of WAS, V4.0.x, and any form of V5.0.x, including WAS - Express.

This parameter is equivalent to the -W previousVersionPanelBean.selectedVersionInstallLocation= "/opt/WebSphere/AppServer" parameter in the silent installation options response file.

-import xmiDataFile The name of the WAS Advanced Single Server Edition, Version 4.0 XML Metadata Interchange (XMI) configuration file to process. This parameter is optional because the program uses the config\server-cfg.xml file by default.

When migrating a configuration that uses anything other than the default server-cfg.xml file name, 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.

-nameServiceHost -nameServicePort When specified, the WASPreUpgrade tool passes these optional parameters to the XMLConfig tool. Use these parameters to override the default host name and port number used by the XMLConfig tool.

No equivalent parameter is available in the silent installation options response file.

-traceString trace_spec -traceFile file_name Optional parameters to gather trace information for IBM Service personnel. Specify a trace specification of "*=all=enabled" (with quotation marks) to gather all trace information.

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 WAS Advanced Single Server Edition. To migrate more than one configuration file, 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.

  1. Run the following WASPreUpgrade commands to migrate applications A, B, C, D, and E, which reside in three separate application directories. Server assumptions include...

    • The Application Server uses the default configuration file, server-cfg.xml, as well as servername1-cfg.xml and OldServer-cfg.xml.

    > WASPreUpgrade C:\WAS4ABBACKUP  G:\WebSphere\AppServer
    > WASPreUpgrade C:\WAS4CDBACKUP  G:\WebSphere\AppServer
          -import  G:\WebSphere\AppServer\config\servername1-cfg.xml
    > WASPreUpgrade C:\WAS4EBACKUP  G:\WebSphere\AppServer
          -import G:\WebSphere\AppServer\config\OldServer-cfg.xml
    
    

  2. Run the following WASPostUpgrade commands to restore the applications and configurations to the Version 5 Application Server

    > WASPostUpgrade C:\WAS4ABBACKUP
    > WASPostUpgrade C:\WAS4CDBACKUP -import C:\WAS4CDBACKUP\servername1-cfg.xml
    > WASPostUpgrade C:\WAS4EBACKUP  -import C:\WAS4EBACKUP\OldServer-cfg.xml
    
    

 

Migrating from V5.0.0 or V5.0.1 with the embedded messaging feature

This example shows how to migrate a single instance of base WAS, V5.0.0. Verify that you have stopped all Java processes related to the WAS product that you are migrating. Run the WASPreUpgrade tool against the installedApps directory.

  1. Run the following WASPreUpgrade.bat command to migrate all applications in the installedApps directory of the V5.0.0 Application Server, which has an installation root of C:\Program Files\WebSphere\AppServer

    > WASPreUpgrade C:\WAS500BACKUP  C:\Program Files\WebSphere\AppServer
    

  2. Run the following WASPostUpgrade commands to restore the applications and configurations to the Version 5 Application Server

    > WASPostUpgrade  C:\WAS500BACKUP