The WASPreUpgrade command for WebSphere
Application Server Version 6.1 saves the configuration of a previously installed
version of WebSphere Application Server into a migration-specific backup directory.
Location
The command file is located and should
be run in the Version 6.1 app_server_root/bin directory.
Authority
To run this command
script, your user profile must have *ALLOBJ authority.
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 WebSphere Application Server Version 5.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 Version 5.x or 6.0.x installation.
![[iSeries]](../../iseries.gif)
The value
currentWebSphereDirectory specifies
the name of the instance or profile root directory for the current WebSphere
Application Server Version 5.x instance or 6.0.x profile that you want to
migrate.
- For Version 5.0.x Express: /QIBM/UserData/WebASE/ASE5/instance
- For Version 5.0.x base: /QIBM/UserData/WebAS5/Base/instance
- For Version 5.0.x Network Deployment: /QIBM/UserData/WebAS5/ND/instance
- For Version 5.1.x Express: /QIBM/UserData/WebASE51/ASE/instance
- For Version 5.1.x base: /QIBM/UserData/WebAS51/Base/instance
- For Version 5.1.x Network Deployment: /QIBM/UserData/WebAS51/ND/instance
- In Version 6.0.x, the profile root may be a unique value chosen during
profile creation but the following directories are the defaults:
- For Version 6.0.x Express or base: /QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/profile
- For Version 6.0.x Network Deployment: /QIBM/UserData/WebSphere/AppServer/V6/ND/profiles/profile
- -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).
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, you must 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 Version 5.x environment.