WASPostUpgrade command

The WASPostUpgrade command for WebSphere® Application Server retrieves the saved configuration that was created by the WASPreUpgrade command from the backupDirectory that you specified. The WASPostUpgrade script for WebSphere Application Server reads the configuration from this directory to migrate to WebSphere Application Server Version 9.0 and adds all migrated applications into the app_server_root/installedApps directory for the Version 9.0 installation.

Supported configurations:

This topic is about profile configuration migration. To migrate your applications to the latest version, use the WebSphere Application Server Migration Toolkit.

Location

The command file is located in and must be run from the app_server_root/bin directory.

Syntax

WASPostUpgrade.sh backupDirectory
                     [-properties properties_file_name]
                     [-username userID]
                     [-password password]
                     [-oldProfile profile_name]
                     [-profileName profile_name]
                     [-setPorts useOld | generateNew | port_starting_number]
                     [-resolvePortConflicts incrementCurrent | port_starting_number]
                     [-backupConfig true | false]
                     [-includeApps true | false | script]
                     [-newDmgrHostname host_name]
                     [[-newDmgrSoapPort port_number] | [-newDmgrRmiPort port_number]]
                     [-keepDmgrEnabled true | false]
                     [-requestTimeout seconds]
                     [-javaoption -Xms...m -javaoption -Xmx...m]
                     [[-appInstallDirectory user_specified_directory] | 
                     [-keepAppDirectory true | false]]
                     [-traceString trace_spec [-traceFile file_name]]
                     [-clone true | false]
                     [-newDmgrHostname hostName]
                     [-newDmgrSoapPort port]
                     [-newDmgrRmiPort port]

WASPostUpgrade.bat backupDirectory
                     [-properties properties_file_name]
                     [-username userID]
                     [-password password]
                     [-oldProfile profile_name]
                     [-profileName profile_name]
                     [-setPorts useOld | generateNew | port_starting_number]
                     [-resolvePortConflicts incrementCurrent | port_starting_number]
                     [-backupConfig true | false]
                     [-includeApps true | false | script]
                     [-newDmgrHostname host_name]
                     [[-newDmgrSoapPort port_number] | [-newDmgrRmiPort port_number]]
                     [-keepDmgrEnabled true | false]
                     [-requestTimeout seconds]
                     [-javaoption -Xms...m -javaoption -Xmx...m]
                     [[-appInstallDirectory user_specified_directory] | 
                     [-keepAppDirectory true | false]]
                     [-traceString trace_spec [-traceFile file_name]]
                     [-clone true | false]
                     [-newDmgrHostname hostName]
                     [-newDmgrSoapPort port]
                     [-newDmgrRmiPort port]

Use these parameters when migrating a registered application server with security enabled for both the target and source administrative agent: [Linux]

WASPostUpgrade.sh backupDirectory
[-oldAdminAgentProfilePath path to old admin agent]
[-oldAdminAgentSoapPort soap port of old admin agent]
[-oldAdminAgentHostname hostname of old admin agent, defaults to localhost ]
[-oldAdminAgentUsername login username for old admin agent, if admin security is enabled ]
[-oldAdminAgentPassword login password for old admin agent, if admin security is enabled ]
[-newAdminAgentProfilePath path to new admin agent ]
[-newAdminAgentSoapPort soap port of new admin agent ]
[-newAdminAgentHostname hostname of new admin agent, defaults to localhost ]
[-newAdminAgentUsername login username for new admin agent, if admin security is enabled ]
[-newAdminAgentPassword login password for new admin agent, if admin security is enabled ]

WASPostUpgrade.bat backupDirectory
[-oldAdminAgentProfilePath path to old admin agent]
[-oldAdminAgentSoapPort soap port of old admin agent]
[-oldAdminAgentHostname hostname of old admin agent, defaults to localhost ]
[-oldAdminAgentUsername login username for old admin agent, if admin security is enabled ]
[-oldAdminAgentPassword login password for old admin agent, if admin security is enabled ]
[-newAdminAgentProfilePath path to new admin agent ]
[-newAdminAgentSoapPort soap port of new admin agent ]
[-newAdminAgentHostname hostname of new admin agent, defaults to localhost ]
[-newAdminAgentUsername login username for new admin agent, if admin security is enabled ]
[-newAdminAgentPassword login password for new admin agent, if admin security is enabled ]

Parameters

The command has the following parameters:

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.

-properties

This is an optional parameter. The value properties_file_name specifies the path to a properties file containing parameter properties that define how migration tools such as WASPostUpgrade operate.

You can define parameter properties in the migration properties file rather than specifying most optional parameters on the command line. If parameters are both defined in the properties file and specified on the command line, the parameters specified on the command line take precedence.

Note: Certain parameters cannot be specified in the properties file, such as the -properties parameter itself and -username and -password. For a list of parameters that cannot be defined as a property, see the template migration.properties file in the app_server_root/bin directory.

-username

This is an optional parameter. The value userID specifies the administrative user name of the current WebSphere Application Server Version 7.0 or later 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 7.0 or later 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.

Tip: When you need to specify a password in the Migration wizard or when you use the WASPostUpgrade command with the -password parameter on the command line, you can type the password in plain text or use the xor-ciphered value. To use the xor-ciphered value, type the entire cipher including the {xor} prefix as the value for the parameter. This xor-ciphered value can be specified in any one of several WebSphere Application Server configuration files for your previous configuration, including the soap.client.props, ssl.client.props, and security.xml files.

Tip: When you use the WASPostUpgrade command with the -password parameter on the command line, you can type the password in plain text or use the xor-ciphered value. To use the xor-ciphered value, type the entire cipher including the {xor} prefix as the value for the parameter. This xor-ciphered value can be specified in any one of several WebSphere Application Server configuration files for your previous configuration, including the soap.client.props, ssl.client.props, and security.xml files.

-oldProfile

This is an optional parameter for migrating instances or profiles from previous WebSphere Application Server versions. The instance or profile must already exist in the migration backup directory before running this command.

If the -oldProfile 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 -oldProfile, 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 Version 9.0 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.

-profileName

This is an optional parameter for migrating to specific profiles in WebSphere Application Server Version 9.0. The value profile_name specifies the name of the Version 9.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.

Note: When migrating a stand-alone application server from Version 9.0, you can choose a stand-alone application server node that has already been registered with an administrative agent as the target of the migration.

-backupConfig

This is an optional parameter used to specify whether the existing WebSphere Application Server Version 9.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. For more information, see restoreConfig command .

-setPorts

This is an optional parameter that specifies how to set the ports for the new profile. The parameter takes the following values:

useOld (default): Use the same ports that the old profile used. For local migrations, this value cannot be used with the -clone true option.
generateNew: Generate new ports based on the default port assignments.
port_starting_number: Generate new ports, incrementing from the specified value.

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.

-resolvePortConflicts

This optional parameter is used to specify how to map port values. When a port cannot be used, its value is incremented from a starting value until an available port is found.

incrementCurrent (default): Increment from the conflicted port value.
port_starting_number: Increment from the specified common starting port value.

-includeApps

You can include business level applications, assets, and composition units as part of the migration. You can optionally migrate these items using the -IncludeApps parameter on the WASPostUpgrade command. This is an optional parameter that can be specified in the following ways:

True
Include user enterprise applications, business level applications, assets, and composition units as part of the migration.

This value is the default.
False
Do nothing with user enterprise applications, business level applications, assets, and composition units during WASPostUpgrade processing.
Script
- Enterprise applications
  Prepare user enterprise applications for installation in the WebSphere Application Server Version 9.0 installableApps directory without 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 to enhance the efficiency of application installation.
- Business level applications, assets, and composition units
  The install_all_BLAs.jy script is generated and placed in the backup directory. This script can migrate all business level applications, assets, and composition units located in the backup directory to your target profile. The WASPostUpgradeBLAHelper.bat/.sh script, located in the <WAS_PROFILE_ROOT>/bin directory, is used to migrate the business level applications, assets and composition units in the install_all_BLAs.txt file.
  
  Avoid trouble: To migrate business level applications, assets, and composition units, you must first create their dependencies.

WebSphere Application Server system applications migrate regardless of the value set by this parameter.

-clone

This optional parameter indicates whether to perform a clone migration, which means that you can continue to use the source profile after you migrate it to the Version 9.0 environment. The default value is false.

[9.0.5.11 or later] You can migrate a WebSphere Application Server Version 9.0 profile from one WebSphere Application Server Version 9.0 installation to another one, including to an installation on a different machine. To do so, set the -allowSameRelease parameter on the WASPreUpgrade command and the -clone parameter to true.

When the -clone parameter is true, you can specify -setPorts useold only for remote migrations, which are migrations to different machines. For local migrations, you cannot specify -setPorts useold. The new profile configuration must use unique port numbers so that the now coexisting new and old configurations do not have port conflicts.

If you clone a deployment manager, you must also clone its federated nodes, and you cannot clone federated nodes without cloning the deployment manager. Clone migrations of federated nodes require that you set the new host name and either the node SOAP port or the RMI port on the following parameters.

-newDmgrHostname: The host name of the Version 9.0 deployment manager
-newDmgrSoapPort: The Simple Object Access Protocol (SOAP) port of the Version 9.0 deployment manager
-newDmgrRmiPort: The Remote Method Invocation (RMI) port of the Version 9.0 deployment manager

-keepDmgrEnabled

This is an optional parameter used to specify whether to disable the existing WebSphere Application Server Version 7.0 or later deployment manager. The default is false unless the -clone parameter is true, in which case -keepDmgrEnabled is also set to true.

If this parameter is specified as true, you can use the existing Version 7.0 or later 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 7.0 or later deployment manager configurations normally are stopped and disabled is to prevent multiple deployment managers from managing the same nodes. You must stop the Version 7.0 or later deployment manager before you start using the Version 9.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 7.0 or later installation and the Version 9.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 9.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 your Version 7.0 or later installation.

-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.

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.

-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.

-requestTimeout

This is an optional parameter. The value seconds refers to the number of seconds that migration will wait before failing attempted wsadmin connections.

This value is also used as the timeout parameter during application migration.

-oldAdminAgentProfilePath

This is an optional parameter. The value path to old admin agent refers to the file system path of the profile directory for the original administrative agent.

This parameter is only required if the application server being migrated is managed by an administrative agent.

-oldAdminAgentSoapPort

This is an optional parameter. The value soap port of old admin agent refers to the SOAP port used by the original administrative agent for administrative connections.