The WASPreUpgrade script

The WASPreUpgrade script migrates the configuration and applications of previous WebSphere Application Server versions to a Version 5 application server node.

Product

This script is available in WebSphere Application Server and WebSphere Application Server Network Deployment.

Authority

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

Syntax

The syntax of the WASPreUpgrade script is:

WASPreUpgrade backupDirectory currentWASDirectory
 [ administrationNodeName ] [ -instance instance ]
 [ -nameServiceHost host_name [ -nameServicePort port_number ] ]
 [ -import xmiDataFile ] [ -traceString trace_spec 
 [ -traceFile file_name ] ]

Parameters

The parameters of the WASPreUpgrade script are:

• backupDirectory
  This is a required parameter and must be the first parameter that you specify. The value backupDirectory specifies the name of the directory where the script stores the saved configuration and files. This is also the directory from which the WASPostUpgrade tool reads the configuration and files. For example, if you are migrating a configuration from WebSphere Application Server Version 3.5, you could specify the /home/was35_instancename/backup directory. If the directory does not exist, the WASPreUpgrade script creates it.

• currentWASDirectory
  This is a required parameter and must be the second parameter that you specify. The value currentWASDirectory specifies the name of the instance root directory for the Version 3.5.x or Version 4.0.x instance that you want to migrate. This can be any edition of WebSphere Application Server Version, 3.5.x or WebSphere Application Server, Version 4.0.x. In these examples, instance is the name of the instance that you want to migrate:

  • For Version 3.5.x: /QIBM/UserData/WebASAdv/instance
  • For Version 4.0.x Advanced Edition: /QIBM/UserData/WebASAdv4/instance
  • For Version 4.0.x Advanced Single Server Edition: /QIBM/UserData/WebASAEs4/instance

• administrationNodeName
  If you are migrating from WebSphere Application Server Standard Edition, Version 3.5.x, WebSphere Application Server Advanced Edition, Version 3.5.x, or WebSphere Application Server Advanced Edition, Version 4.0.x, this parameter is required and must be the third parameter that you specify. The value administrationNodeName specifies the name of the node that contains the administrative server for the previous version of the product. The value of this argument is case-sensitive and must match the node name given in the topology tree on the Topology tab of the administrative console for the previous version. The WASPreUpgrade tool uses this parameter to call the XMLConfig tool.

• -instance
  Optional. The value instance specifies the name of the WebSphere Application Server Version 5 instance to which you are migrating the configuration. If you do not specify this parameter, the script migrates the configuration to the default instance.

• -nameServiceHost
  Optional. The value host_name specifies the TCP/IP host name of the iSeries server. If you do not specify this parameter, the default host name is localhost.

• -nameServicePort
  Optional. The value port_number specifies specifies the bootstrap port for the administrative server for the instance from which you are migrating. If you do not specify this parameter, the default value is 900.

• -import
  Optional. The value xmiDataFile 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 specified for the backupDirectory parameter.

  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.

  This parameter is ignored when migrating from WebSphere Application Server - Express Version 5.0.x.

• -traceString
  Optional. 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, specify the -traceFile parameter.

• -traceFile
  Optional. 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 WASPreUpgrade tool displays status to the screen while it is running. It also saves a more extensive set of logging information in the WASPreUpgrade.log file. This file is located in the backupDirectory directory, where backupDirectory is the value specified for the backupDirectory parameter.

Security

The WASPreUpgrade script uses the XMLConfig script to export configuration data from WebSphere Application Server Version 3.5 (Standard or Advanced Editions) or Version 4 (Advanced Edition). If WebSphere security is enabled, ensure that the properties are configured properly in the sas.client.props property file for the Version 3.5 or Version 4 instance before running the WASPreUpgrade script or the script fails when it attempts to invoke the XMLConfig script. The following sections in the Version 3.5 and Version 4 product information describe how to configure the sas.client.props property file. Follow the instructions that describe how to configure automatic authentication:

• Version 3.5 Standard Edition:Authenticating to the administrative server
• Version 3.5 Advanced Edition: Authenticating to the administrative server
• Version 4.0 Advanced Edition: Authenticate to the administrative server

Examples

Migrate from WebSphere Application Server Version 3.5.x Standard Edition or Advanced Edition, or 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 backup directory is named /home/was50migration/WAS40Adv, and the instance root of the previous version is /QIBM/UserData/WebASAdv4/default. The administrative server is contained in myNode.

> WASPreUpgrade /home/was50migration/WAS40Adv /QIBM/UserData/WebASAdv4/default MYISERIES

Migrate from a WebSphere Application Server Version 4.0.x, Advanced Single Server Edition node with multiple backup directories

This example illustrates how to migrate the default instance of WebSphere Application Server Version 4.0, Advanced Single Server Edition.

Run this commands from Qshell:

> WASPreUpgrade /home/was50migration/WAS4AES QIBM/UserData/WebASAEs4/default

Note: The administrationNodeName value is not required when migrating from WebSphere Application Server 4.0, Advanced Single Server Edition.