WASPreUpgrade command

 

The WASPreUpgrade command for WebSphere Application Server V6.1 saves the configuration of a previously installed version of WAS into a migration-specific backup directory.

 

Location

The command file is located and should be run in the V6.1 app_server_root/bin directory.

 

Syntax

The syntax is as follows:

WASPreUpgrade.sh backupDirectory 
                currentWebSphereDirectory
                [-traceString trace_spec [-traceFile file_name ]]

WASPreUpgrade.bat backupDirectory 
                currentWebSphereDirectory
                [-traceString trace_spec [-traceFile file_name ]]

 

Parameters

The parameters are as follows:

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 command script stores the saved configuration.

This is also the directory from which the WASPostUpgrade command reads the configuration.

If the directory does not exist, the WASPreUpgrade command script creates it.

currentWebSphereDirectory

This is a required parameter and must be the second parameter that you specify. This can be any edition of WAS V5.x or 6.0.x for which migration is supported.

The value currentWebSphereDirectory specifies the name of the installation root directory for the current WebSphere Application Server V5.x or 6.0.x installation.

-traceString

This is an optional parameter. The value trace_spec specifies the trace information to collect.

To gather all trace information, specify "*=all=enabled" (with quotation marks).

If you do not specify the -traceString or -traceFile parameter, the command creates a trace file by default and places it in the backupDirectory/logs directory.

If you specify this parameter, also specify the -traceFile parameter.

-traceFile

This is an optional parameter. The value file_name specifies the name of the output file for trace information.

If you do not specify the -traceString or -traceFile parameter, the command creates a trace file by default and places it in the backupDirectory/logs directory.

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 runs. The tool also saves a more extensive set of logging information in the WASPreUpgrade.time_stamp.log file written to the backupDirectory directory, where backupDirectory is the value specified for the backupDirectory parameter. You can view the WASPreUpgrade.time_stamp.log file with a text editor.

 

Migrated resources

WASPreUpgrade saves all of your resources, but it does not migrate entities in your classes directory. Migration saves the following files in the backupDirectory directory.

• classes

• config

• properties

The WASPreUpgrade command also saves all instances created in the V5.x environment.

---

 

Related tasks

Migrating product configurations
Use the migration tools to migrate product configurations

 

Related Reference

clientUpgrade command
WASPostUpgrade command

 

Reference topic