The WASPostUpgrade script

The WASPostUpgrade script migrates the configuration and applications of previous WebSphere Application Server versions to a Version 6.0 application server node. The script includes applications from the installedApps directory and other directories from the previous version.

Product

This script is available in WebSphere Application Server (Express and Base) and WebSphere Application Server Network Deployment.

Authority

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

Syntax

The syntax of the WASPostUpgrade script is:

WASPostUpgrade backupDirectory [ -profileName profile ]
 [ -import xmi_data_file ]
 [ -includeApps < true | false > ] [ -scriptCompatibility < true | false > ]
 [ -substitute"key1=value1[;key2=value2;[...]]" ]
 [ -portBlock port_starting_number ] [ -backupConfig < true | false > ] 
 [ -replacePorts < true | false > ] [ [ -traceString trace_spec ] 
 [ -traceFile file_name ] ] [ -connectionTimeout timeoutInMinutes ]

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.

• -profileName
  This is a required parameter. The value profile specifies the name of the WebSphere Application Server Version 6.0 profile to which the script migrates your configuration.

• -import
  This is an optional parameter. The value xmi_data_file specifies the name of the WebSphere Application Server Advanced Single Server Edition, Version 4 XML Metadata Interchange (XMI) configuration file to process. The default value is backupDirectory/config/server-cfg.xml where backupDirectory is the value of backupDirectory parameter that was specified for the WASPreUpgrade script.

  If you are migrating a configuration that does not use the default server-cfg.xml file, include the -import to specify the fully-qualified name of the configuration file the WASPreUpgrade tool creates.

• -includeApps
  An optional parameter used to specify whether to migrate only the previous configuration, or to include user enterprise applications as part of the migration. The default is true. WebSphere Application Server system applications migrate regardless of the value set by this parameter.

• -scriptCompatibility
  An optional parameter used to specify whether migration should create Transport and ProcessDef definitions in the configuration instead of Channels and ProcessDefs. Use this parameter if you have existing wsadmin scripts or programs that create or modify Transport or ProcessDef defintions. The default is true.

• -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 consecutive ports to assign when the script runs.

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

• -replacePorts
  This is an optional parameter. Valid values for this parameter are true and false and the default is false. If true is specified, replace all virtual host alias port settings during migration. If you migrate from Version 5.0.x or 5.1.x, virtual host and transport settings in the Version 6.0 profile are replaced by the settings from Version 5.0.x or 5.1.x instance. This parameter must be specified when you migrate from Version 5.0.x Network Deployment or Version 5.1.x Network Deployment to Version 6.0 Network Deployment.

• -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, 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.

• -connectionTimeout
  This is an optional parameter to be used if a SOAP or RMI timeout occurs when you perform a migration of a managed node. This parameter is specified in minutes. (The default value is 10.) It is possible to run into a SOAP or RMI timeout issue when you migrate a very large or very complex configuration; if this happens, you should increase the amount of time before a SOAP or RMI connection timeout occurs and run migration again.

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 profile_root/logs directory. For example, for the default profile of the Base and Express products, the file would be located in /QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/default/logs.

Examples

Migrate from a WebSphere Application Server Version 5.1.x (Base) node to WebSphere Application Server Version 6.0 (Base)

This example illustrates how to migrate from WebSphere Application Server Version 5.1.x (Base) to Version 6.0 (Base). The WASPreUpgrade script created the backup directory named /home/was60migration/WAS51Base. The WASPostUpgrade script reads the configuration from this directory to migrate to Version 6.0.

WASPostUpgrade -profileName default /home/was60migration/WAS51Base

Migrate from WebSphere Application Server Version 4.0.x, Advanced Edition

This example illustrates how to migrate from WebSphere Application Server Version 4.0.x, Advanced Edition. The WASPreUpgrade script created the backup directory named /home/was60migration/WAS40Adv. The WASPostUpgrade script reads the configuration from this directory to migrate to WebSphere Application Server Version 6.0.

WASPostUpgrade -profileName default /home/was60migration/WAS40Adv