WAS v8.0 > Migration and coexistence > Distributed operating systems > Scenario 4: Flexible Management: Migrating a job manager profile and its registered set of servers > 6. Run the WASPostUpgrade command from the new WAS install root bin directory

WASPostUpgrade command

Overview

The WASPostUpgrade command for WAS v8.0 retrieves the saved configuration created by the WASPreUpgrade command from the backupDirectory specified. The WASPostUpgrade script for WAS v8.0 reads the configuration from this directory to migrate to WAS v8.0 and adds all migrated applications into the WAS_HOME/installedApps directory for the v8.0 installation.

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

WASPostUpgrade.sh backupDirectory
                  [-username userID]
                  [-password password]
                  [-oldProfile profile_name]
                  [-profileName profile_name]
                  [-scriptCompatibility true | false]
                  [-portBlock port_starting_number]
                  [-backupConfig true | false]
                  [-replacePorts true | false]
                  [-includeApps true | false | script]
                  [-keepDmgrEnabled true | false]
                  [[-appInstallDirectory user_specified_directory] | [-keepAppDirectory true | false]]
                  [-traceString trace_spec [-traceFile file_name]]

Parameters

backupDirectory

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

-username

Administrative user name of the current WAS v6.x or 7.x installation.

Required parameter if the following conditions are true:

• You are migrating a dmgr 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

Password for the administrative user name of the current WAS v6.x or 7.x installation.

Required parameter if the following conditions are true:

• You are migrating a dmgr 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 WAS 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 WAS configuration files for your previous configuration, including the soap.client.props, ssl.client.props, and security.xml files.

-oldProfile

Parameter for migrating instances or profiles from previous WAS versions. The instance or profile must already exist in the migration backup directory before running this command.

If the -oldPriofile parameter is not specified, the default profile is used. If no default profile is found, the system reports an error.

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

Migrate to specific profiles in WAS v8.0. The value profile_name specifies the name of the v8.0 profile to which the script migrates the configuration. We 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.

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.

When migrating a stand-alone application server from v8.0, you can choose a stand-alone application server node that has already been registered with an admin agent as the target of the migration.

-scriptCompatibility

Specify whether or not migration should create the following v6.x or 7.x configuration definitions:

• Transport
• ProcessDef
• V6.x SSL

...instead of the following v8.0 configuration definitions...

• Channels
• ProcessDefs
• v8.0 SSL

The default value is true.

Specify true for this parameter in order to minimize impacts to existing administration scripts. If we have existing wsadmin scripts or programs that use third-party configuration APIs to create or modify the v6.x or 7.x configuration definitions, for example, you might want to specify true for this option during migration.

To use a cell that contains v6.x or 7.x nodes, specify true for this variable.

This is meant to provide a temporary transition until all of the nodes in the environment are at the v8.0 level. When they are all at the v8.0 level, you should perform the following actions:

1. Modify your administration scripts to use all of the v8.0 settings.

2. Use the convertScriptCompatability command to convert the configurations to match all of the v8.0 settings.

-backupConfig

Specify whether the existing WAS v8.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

The port_starting_number value specifies the starting value of a block of consecutive port numbers to assign when creating new ports. Optional.

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

Include business level applications, assets, and composition units as part of the migration. We can optionally migrate these items using the -IncludeApps parameter on the WASPostUpgrade command. Optional parameter. 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 WAS v8.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. We can then run these files at any point and in any combination after the WASPostUpgrade command has completed. We 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. To perform error checking and start the required wsadmin commands, the script also calls... WAS_HOME/bin/migration/bin/WASPostUpgradeBLAHelper.jy Business level applications, assets, and composition units are not migrated if their dependencies have not been created.

WAS system applications migrate regardless of the value set by this parameter.

-keepDmgrEnabled

Specify whether to disable the existing WAS Version 6.x or 7.x dmgr. The default is false.

If this parameter is specified as true, you can use the existing v6.x or 7.x dmgr while the migration is completed. It is only valid when you are migrating a dmgr; it is ignored in all other migrations.

Caution: Use this parameter with care.

• The reason that WAS v6.x or 7.x dmgr configurations normally are stopped and disabled is to prevent multiple dmgrs from managing the same nodes. We must stop the v6.x or 7.x dmgr before you start using the v8.0 dmgr. The most likely error conditions that occur if this is not done are port conflicts when the second instance of the dmgr is started.

• True for this parameter means that any configuration changes made in the old configuration during migration might not be migrated.

-keepAppDirectory

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 WAS v6.x or 7.x installation and the v8.0 installation. If you keep the migrated applications in the same locations as those of the previous version, the following restrictions apply:

• The WAS v8.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 v6.x or 7.x installation.

-appInstallDirectory

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

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.

-traceFile

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.

Log

The WASPostUpgrade tool displays status to the screen while running. This tool also saves a more extensive set of logging information in the WASPostUpgrade.time_stamp.log file located in the backupDirectory/logs directory. We can view the WASPostUpgrade.time_stamp.log file with a text editor.

Security considerations

The target system must have security disabled before migration. If you migrate from a source configuration that has security enabled, the WASPostUpgrade command automatically enables security for the v8.0 target configuration during the migration.

java.security file

During WASPostUpgrade, a copy of the java.security file is made in the target WAS installation before migrating the file. The presence of this copy, named java.security.premigration, indicates to future migrations that the file has already been migrated. Also, the copy gives you a chance to reference the default Version 8.0 settings and determine to make changes to the migrated java.security file.

The following properties are migrated in the java.security file, all other properties and comments are not migrated:

?security.provider.* - prepend the source provider list before the target provider list and renumber the target provider list, removing duplicates. Also ensure that the com.ibm.crypto.pkcs11impl.provider.IBMPKCS11Impl security provider is placed before the com.ibm.crypto.provider.IBMJCE security provider in preference order if both are present in the migrated file.
?networkaddress.cache.ttl
?networkaddress.cache.negative.ttl
?ocsp.enable
?ocsp.responderURL
?ocsp.responderCertSubjectName
?ocsp.responderCertIssuerName
?ocsp.responderCertSerialNumber

The following situations might cause the migration of the java.security file to fail. If use any of the following settings, then manually migrate the java.security file.

• If the WASPreUpgrade command is run with the machineChange=true option, the source and target operating systems will be checked before migrating the java.security file. If the source operating system iss HP or Sun, and the target operating system is not the same, the file will not be migrated. If the target operating system is HP or Sun, and the source operating system is not the same, the file will not be migrated. This is because the contents of the java.security file are not compatible between the different operating systems.

• If the copy of the java.security file to java.security.premigration cannot be made, the file will not be migrated.

• If the java.security file is not writeable, the file will not be migrated.

• If the java.security file is not found in the backup directory, the file will not be migrated. If you use an old backup directory, or if something there is a problem with the old installation, then this problem might occur.

Migrate product configurations
Migrate product configurations with migration tools
WASPreUpgrade command

+

Search Tips   |   Advanced Search