- 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.
- -username
- This is an optional parameter. The value userID specifies the administrative user name of the current WebSphere Application Server Version 5.1.x or Version 6.x installation.
This is a required parameter if the following
conditions are true:
- You are migrating a deployment manager or a federated node.
- Administrative or global security is enabled in the source installation.
- The administrative or global security user ID is not defined in
the security.xml file.
- -password
- This is an optional parameter. The value password specifies the password for the administrative user name of the current WebSphere Application Server Version 5.1.x
or Version 6.x installation.
This is
a required parameter if the following conditions are true:
- You are migrating a deployment manager or a federated node.
- Administrative or global security is enabled in the source installation.
- The administrative or global security password is not defined
in the security.xml file.
- -profileName
- This is an optional parameter for migrating to specific profiles
in WebSphere Application Server Version 7.0. The value profile_name specifies the name of the Version 7.0 profile to which
the script migrates your configuration. You must have already created
this profile before calling the WASPostUpgrade command.
If the -profileName parameter is not specified, the default profile
is used. If no default profile is found, the system reports an error.
Avoid trouble: If you do not specify
the specific profile name on -profileName, then whatever is the designated
"default" profile will be migrated. You might have to migrate each
profile in the backup taken on pre-migration, using the WASPostUpgrade
post-migration command specifying the -oldProfile and -profileName
parameters for each and every profile that the client wants in the
new environment. If the old profile contains installed applications
(installedApps) in addition to the sample application and system applications,
then the migration process automatically migrates those applications.
gotcha
Note: When migrating a standalone application server
from Version 6.x to Version 7.0, you can choose a standalone application server node that has
already been registered with an administrative agent as the target
of the migration.
- -scriptCompatibility
- This is an optional parameter used to specify whether or not migration
should create the following Version 5.1.x or Version 6.x configuration
definitions:
- Transport
- ProcessDef
- Version 5.1.x or Version 6.x SSL
instead of the following
Version 7.0 configuration definitions:
- Channels
- ProcessDefs
- Version 7.0 SSL
The default value is true.
Specify true for this
parameter in order to minimize impacts to existing administration
scripts. If you have existing wsadmin scripts or programs that use
third-party configuration APIs to create or modify the Version 5.1.x
or Version 6.x configuration definitions, for example, you might want
to specify true for this option during migration.
If you want
to use a cell that contains Version 5.1.x or Version 6.x nodes, you
must specify true for this variable.
Note: This is
meant to provide a temporary transition until all of the nodes in
the environment are at the
Version 7.0 level. When they are all at the
Version 7.0 level, you should
perform the following actions:
- Modify your administration scripts to use all of the Version 7.0 settings.
- Use the convertScriptCompatability command
to convert your configurations to match all of the Version 7.0 settings.
Read convertScriptCompatibility command for more information.
- -backupConfig
- This is an optional parameter used to specify whether the existing WebSphere Application Server Version 7.0 configuration is
saved before any changes are made by the WASPostUpgrade tool. The default is true—that is, to use the backupConfig command to save a copy of the current configuration into the profile_name/temp directory.
Use
the restoreConfig command to restore that configuration
as required. Read the "restoreConfig command" article in the information
center for more information.
- -portBlock
- This is an optional parameter. The port_starting_number value specifies the starting value of a block of consecutive port
numbers to assign when creating new ports.
By default, this parameter
is not set.
If a value is specified for this parameter, any
new ports that are assigned are set based on this value. Every time
a new port value is required, the port is created based on this value
and the seed value is incremented for the next usage. No duplicate
ports are assigned.
- -replacePorts
- This optional parameter is used to specify how to map port values.
- True
Use all port values from the old configuration in the new
configuration. All ports from the old configuration supersede the
settings for the same ports in the new configuration.
- If the -portBlock parameter is not set, a conflicting port is
renumbered incrementally from its original value until a nonconflicting
port is identified.
- If the -portBlock parameter is set, a conflicting port is renumbered
incrementally from the port block number until a nonconflicting port
is identified.
This value is the default.
- False
Do not replace the default port definitions in the new
profile with the values from the old configuration during migration.
All ports values from the new configuration supersede the settings
for the same ports in the old configuration
- If the -portBlock parameter is not set, a conflicting port is
renumbered incrementally from its original value until a nonconflicting
port is identified.
- If the -portBlock parameter is set, a conflicting port is renumbered
incrementally from the port block number until a nonconflicting port
is identified.
- -includeApps
- This is an optional parameter that can be specified in the following
ways:
- True
Include user enterprise applications as part of the migration.
This value is the default.
- False
Do nothing with user enterprise applications during WASPostUpgrade processing.
- Script
Prepare user enterprise applications for installation
in the WebSphere Application Server Version 7.0 installableApps directory without actually installing them during WASPostUpgrade processing.
Scripts that can be used to install these applications
are generated and saved in the backupDirectory directory.
You can then run these files at any point and in any combination after
the WASPostUpgrade command has completed. You can
also reorganize and combine these files for better applications installation
efficiency if you want.
WebSphere Application Server system
applications migrate regardless of the value set by this parameter.
- -keepDmgrEnabled
- This is an optional parameter used to specify whether to disable
the existing WebSphere Application Server Version 5.1.x or Version 6.x deployment manager. The default is
false.
If this parameter is specified as true, you can use the
existing Version 5.1.x or Version 6.x deployment manager while the
migration is completed. It is only valid when you are migrating a
deployment manager; it is ignored in all other migrations.
Caution: Use this parameter with care.
- The reason that WebSphere Application Server Version 5.1.x or Version 6.x deployment manager configurations
normally are stopped and disabled is to prevent multiple deployment
managers from managing the same nodes. You must stop the Version 5.1.x
or Version 6.x deployment manager before you start using the Version 7.0 deployment manager.
The most likely error conditions that occur if this is not done are
port conflicts when the second instance of the deployment manager
is started.
- Specifying true for this parameter means that any configuration
changes made in the old configuration during migration might not be
migrated.
- -keepAppDirectory
- This is an optional parameter used to specify whether to install
all applications to the same directories in which they are currently
located. The default is false.
If this parameter is specified as
true, each individual application retains its location.
If
you specify this parameter, you cannot specify the -appInstallDirectory
parameter.
Restrictions: If this
parameter is specified as true, the location is shared by the existing
WebSphere Application Server Version 5.1.x
or Version 6.x installation and the
Version 7.0 installation. If
you keep the migrated applications in the same locations as those
of the previous version, the following restrictions apply:
- The WebSphere Application Server Version 7.0 mixed-node support
limitations must be followed. This means that the following support
cannot be used when evoking the wsadmin command:
- Precompile JSP
- Use Binary Configuration
- Deploy EJB
- You risk losing the migrated applications unintentionally if you
later delete applications from these locations when administering
(uninstalling for example) your Version 5.1.x or Version 6.x installation.
- -javaoption
- This is an optional parameter. Use this parameter to specify memory
sizes for the Java heap used
by the WASPreUpgrade command.
The value -Xms...m is the parameter specified to indicate the starting
heap size. Replace the "..." with the size in megabytes that you intend
to use. For example, if the starting heap size is to be 128 MB, specify
the parameter as: -javaoption -Xms128m
The
value -Xmx...m is the parameter specified to indicate
the maximum heap size. Replace the "..." with the size in megabytes
that you intend to use. For example, if the maximum heap size is to
be 1024 MB, specify the parameter as: -javaoption -Xmx1024m
- -appInstallDirectory
- This is an optional parameter that is used to pass the directory
name to use when installing all applications during migration. The
default of profile_name\installedApps is used if this parameter is not specified.
If you specify this
parameter, you cannot specify the -keepAppDirectory parameter.
Quotes must be used around the directory name if one or more spaces
are in the name.
If you use this parameter, the migration tools
investigate the node-level variables for the node being migrated both
in the backup directory (variables for the old release) and in the
destination profile (variables from the new release). If the path
is part of any of the following variables in either of these releases,
the tools contract the path information to use the related variable:
- APP_INSTALL_ROOT
- USER_INSTALL_ROOT
- WAS_INSTALL_ROOT
When the contraction takes place, you receive the following warning
message that tells you that the tools changed your specified value
and what that contracted value is:
MIGR0341W: Application install directory has been updated to {0}.
For example:
MIGR0341W: Application install directory has been updated to ${USER_INSTALL_ROOT}\customAppDirectory.
or
MIGR0341W: Application install directory has been updated to ${APP_INSTALL_ROOT}\
cellName\customAppDirectory\.
- -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.