The WASPostUpgrade script

The WASPostUpgrade command is a migration tool for migrating the configuration and applications of previous versions to a WebSphere Application Server - Express application server node. The script is located in the /QIBM/ProdData/WebASE51/ASE/bin directory.

The WASPostUpgrade tool installs all migrated applications into the /QIBM/UserData/WebASE51/ASE/instance/installedApps directory, where instance is the name of the instance to which you are migrating. The tool includes applications from the installedApps directory and other directories from the previous version.

Authority

To run this script, your user profile must have *ALLOBJ authority.

Syntax

The syntax of the WASPostUpgrade script is:

WASPostUpgrade backupDirectory  -instance instance 
 [ -cellName cell_name ] [ -nodeName node_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 ] ]

Parameters

The parameters of the WASPostUpgrade script are:

• backupDirectory
  This is a required parameter. The value backupDirectory specifies the name of the directory in which the WASPreUpgrade tool stores the saved configuration and files, and from which the WASPostUpgrade tool reads the configuration and files.

• -instance
  This is a required parameter. The value instance specifies the name of the WebSphere Application Server - Express instance to which the script migrates your configuration.

• -cellName
  This is an optional parameter. The value cell_name specifies the cell name that the script updates. If you do not specify this parameter, the script reads the configuration to determine the cell name. If only one cell name is found, the script updates that cell. If no cell name is found, or if more than one cell name is found, the script returns an error.

• -nodeName
  This is an optional parameter. The value node_name specifies the node name that the script updates. If you do not specify this parameter, the script reads the configuration to determine the node name. If only one node name is found, the script updates that cell. If no node name is found, or if more than one node name is found, the script returns an error.

• -webModuleAdditionalClasspath
  This is an optional parameter. The value classpath specifies the path or the path and file names of specific directories or files that you do not want copied into the Web archive (WAR) file that the script processes. Instead, the script adds the paths and files to the Web Module extension (ibm-web-ext.xmi) additionalClassPath attribute. If you want to specify multiple values for this parameter, separate them with a colon (:).

• -documentRootLimit
  This is an optional parameter. The value number specifies the number of files that the script copies from the document-root field of your Web application. The default value is 300.

• -substitute
  This is an optional argument. This parameter specifies values for security variables to substitute. (for example, -substitute "NODE_NAME=admin_node;APP_SERVER=default_server").

  In the input XML data file, each key appears as $key$ for substitution. This argument replaces all occurrences of $NODE_NAME$ and $APP_SERVER$ with admin_node and default_server, respectively, in the input XML file.

  If the substitution string contains semicolons, use $semiColon$ to separate it from the ";" delimiter.

• -portBlock
  This is an optional parameter. The value port_starting_number specifies the first of a block of 10-15 consecutive port numbers that zare not in use on the iSeries server where the migration is being performed. It is recommended that you always specify the -portBlock parameter if you do not want your instance's ports to conflict with the default instance's ports.

• -backupConfig
  This is an optional parameter. Valid values for this parameter are true and false. The default value is true. If true is specified, then the existing Version 5.1 configuration is saved before any changes are made by the WASPortUpgrade tool.

• -replacePorts
  This is an optional parameter. Valid values for this parameter are true and false. The default value is false. If true is specified, all virtual host alias port settings are replaced during migration. If migrating from Version 5.0.x, virtual host and transport settings in the Version 5.1 instance are replaced by the settings from the Version 5.0.x instance.

• -traceString
  This is an optional parameter. The value trace_spec specifies the trace information that you want to collect. To gather all trace information, specify "*=all=enabled" (with quotation marks). The default is to not gather trace information. If you specify this parameter, you must also specify the -traceFile parameter.

• -traceFile
  This is an optional parameter. The value trace_file specifies the name of the output file for trace information. If you specify the -traceString parameter but do not specify the -traceFile parameter, the script does not generate a trace file.

Logging

The WASPostUpgrade tool displays status to the screen while running. It also saves a more extensive set of logging information in the WASPostUpgrade.log file. This file is located in the /QIBM/UserData/WebASE51/ASE/instance/logs directory, where instance is the name of the instance that you are migrating to.

Examples

Migrate from WebSphere Application Server Version 3.5.x Standard Edition

This example illustrates how to migrate from WebSphere Application Server Version 3.5.x, Advanced Edition. The WASPreUpgrade script created the backup directory named /home/was35_instancename/WAS35Std. The WASPostUpgrade script reads the configuration from this directory to migrate to WebSphere Application Server - Express.

WASPostUpgrade /home/was35_instancename/WAS35Std