The WASPreUpgrade command is a migration tool that saves
the configuration and applications of a previous version or release to a Version
6.0 node.
Location of command file
The command file is located
and should be run in the WAS60_install_root/bin directory. The command
file is a script named WASPreUpgrade.sh for Linux-based platforms
or WASPreUpgrade.bat for Windows platforms.
WASPreUpgrade.sh command syntax for Linux-based platforms
The
command syntax is as follows:
WASPreUpgrade.sh backupDirectory
currentWebSphereDirectory
[adminNodeName]
[-nameServiceHost host_name [-nameServicePort port_number ]]
[-import xmiDataFile ]
[-traceString trace_spec [-traceFile file_name ]]
WASPreUpgrade.bat command syntax for Windows platforms
WASPreUpgrade backupDirectory
currentWebSphereDirectory
[adminNodeName]
[-nameServiceHost host_name [-nameServicePort port_number ]]
[-import xmiDataFile ]
[-traceString trace_spec [-traceFile file_name ]]
Parameters
The first two arguments are required.
The third argument is required and positional only when upgrading from WebSphere
Application Server Advanced Edition, Version 4.0.x.
Supported arguments
include:
- backupDirectory
- Required parameter of the directory in which the WASPreUpgrade tool stores
the saved configuration and files, and from which the WASPostUpgrade tool
later reads the configuration and files. The WASPreUpgrade tool creates the
directory if the directory does not already exist.
- currentWebSphereDirectory
- Required positional name of the installation/instance root for the current
V4.x, V5.0.x, or V5.1.x installation. This version can be any form of WebSphere
Application Server, V4.0.x, and any form of V5.0.x or V5.1.x, including WebSphere
Application Server Express.
- adminNodeName
- Optional, positional name of the node containing the administrative server
for the currently installed product. The value of this argument must match
the node name given in the topology tree on the Topology tab of the
administrative console for the currently installed product. The WASPreUpgrade
tool calls the XMLConfig tool using this parameter. This parameter is only
required when upgrading from WebSphere Application Server Advanced Edition,
Version 4.0.x.
- -nameServiceHost host_name -nameServicePort port_number
- When specified, the WASPreUpgrade tool passes these optional parameters
to the XMLConfig tool. Use these parameters to override the default host name
and port number used by the XMLConfig tool. This parameter is only applicable
when upgrading from WebSphere Application Server Advanced Edition, Version
4.0.x.
- -import xmiDataFile
- The name of the WebSphere Application Server Advanced Single Server Edition
or Advanced Edition, Version 4.0 XML Metadata Interchange (XMI) configuration
file to process. This parameter is optional because the program uses the config\server-cfg.xml file
by default.
When migrating a configuration that uses anything other than
the default server-cfg.xml file name, you must use the -import option
along with a path to point to the non-default XMI configuration file. You
also must use the -import and path option when running the WASPostUpgrade
tool later, to point to the non-default XMI configuration file in the directory
created by the WASPreUpgrade tool.
- -traceString trace_spec -traceFile file_name
- Optional parameters to gather trace information for IBM Service personnel.
Specify a trace specification of "*=all=enabled" (with quotation
marks) to gather all trace information.
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 backup directory. You can view the WASPreUpgrade.log file
with a text editor.
Migrated resources
WASPreUpgrade migrates all of
your resources and applications, but does not migrate entities in your classes directory.
Migration
saves the following files in the backup directory.
- For Version 5.x:
- classes (not saved for iSeries)
- config
- installableApps
- installedApps
- properties
WASPreUpgrade also saves all instances created in the V5.x environment.
(For iSeries, WASPreUpgrade must be invoked for each instance.)
- For Version 4.0.x:
- bin/setupCmdLine.sh (or bin/setupCmdLine.bat for Windows
platforms)
- classes (not saved for iSeries)
- config
- installableApps
- installedApps (by default unless overriden within a specified
developer configuration file)
- installedConnectors (Version 4.x Advanced Edition only)
- properties (including iSeries as of V5.1 migration tooling)
Migrating from V4.0.x Advanced Edition
The following
example specifies a backup directory named backupDirectory, and identifies
the root of the existing installation as d:\WebSphere\AppServer.
WASPreUpgrade backupDirectory d:\WebSphere\AppServer yourNodeName
Migrating from V4.0.x Advanced Single Server Edition with
multiple backup directories
This example shows how to migrate incrementally,
to migrate separate configuration files from a single node with a single installation
of WebSphere Application Server Advanced Single Server Edition. To migrate
more than one configuration file, you must run the WASPreUpgrade tool multiple
times to multiple backup directories because not all of the applications are
in the same
installedApps directory. For this reason, using a single
backup directory for all runs of the WASPreUpgrade tool is not recommended.
Use a separate backup directory for each run. The intent of this example is
to show how to migrate a single node with multiple configuration files.
- Run the following WASPreUpgrade commands to migrate applications A, B,
C, D, and E, which reside in three separate application directories. Server
assumptions include:
- The Application Server uses the default configuration file, server-cfg.xml,
as well as myServer1-cfg.xml and OldServer-cfg.xml.
> WASPreUpgrade C:\WAS4ABBACKUP G:\WebSphere\AppServer
> WASPreUpgrade C:\WAS4CDBACKUP G:\WebSphere\AppServer
-import G:\WebSphere\AppServer\config\myServer1-cfg.xml
> WASPreUpgrade C:\WAS4EBACKUP G:\WebSphere\AppServer
-import G:\WebSphere\AppServer\config\OldServer-cfg.xml
- Run the following WASPostUpgrade commands to restore the applications
and configurations to the Version 6 Application Server:
> WASPostUpgrade C:\WAS4ABBACKUP
> WASPostUpgrade C:\WAS4CDBACKUP -import C:\WAS4CDBACKUP\myServer1-cfg.xml
> WASPostUpgrade C:\WAS4EBACKUP -import C:\WAS4EBACKUP\OldServer-cfg.xml
Migrating from V5.x
This example shows how to migrate
a single instance of the base WebSphere Application Server, V5.x. Verify that
you have stopped all Java processes related to the WebSphere Application Server
product that you are migrating.
- Run the following WASPreUpgrade.bat command to migrate all applications
in the installedApps directory of the V5.x Application Server, which
has an installation root of C:\Program Files\WebSphere\AppServer.
WASPreUpgrade "C:\WAS5xxBACKUP" C:\Program Files\WebSphere\AppServer
- Run the following WASPostUpgrade commands to restore the applications
and configurations to the Version 6 Application Server:
WASPostUpgrade "C:\WAS5xxBACKUP"