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 8.5 and adds all migrated applications into the app_server_root/installedApps directory for the Version 8.5 installation.
This article is about configuration migration, such as migrating deployment managers and federated nodes in a network deployment environment. The Application Migration Toolkit for WebSphere Application Server provides support for migrating applications from previous versions of WebSphere Application Server to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.
sptcfgThe command file is located in and must be run from the app_server_root/bin directory.
To run this command script, your user profile must have *ALLOBJ authority.
WASPostUpgrade backupDirectory
[-username userID]
[-password password]
[-profileName profile_name]
[-scriptCompatibility true | false]
[-portBlock port_starting_number]
[-backupConfig true | false]
[-replacePorts true | false]
[-includeApps true | false | script]
[-requestTimeout seconds]
[-javaoption -Xms...m -javaoption -Xmx...m]
[[-appInstallDirectory user_specified_directory] |
[-keepAppDirectory true | false]]
[-traceString trace_spec [-traceFile file_name]]
WASPostUpgrade 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 ]
The command has the following parameters:
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 6.x or 7.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 6.x or 7.x nodes, you must specify true for this variable.
Use the restoreConfig command to restore that configuration as required. For more information, see restoreConfig command .
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.
WebSphere Application Server system applications migrate regardless of the value set by this parameter.
If this parameter is specified as true, each individual application retains its location.
If you specify this parameter, you cannot specify the -appInstallDirectory parameter.
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.
MIGR0341W: Application install directory has been updated to {0}.
For example: MIGR0341W: Application install directory has been updated to ${USER_INSTALL_ROOT}\customAppDirectory.
orMIGR0341W: Application install directory has been updated to ${APP_INSTALL_ROOT}\
cellName\customAppDirectory\.
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 do not specify the -traceString or -traceFile parameter, the command creates a trace file by default and places it in the backupDirectory/logs directory.
This value is also used as the timeout parameter during application migration.
This parameter is only required if the application server being migrated is managed by an administrative agent.
This parameter is required only if the application server being migrated is managed by an administrative agent.
This parameter is required only if the application server being migrated is managed by an administrative agent.
This parameter is required only if the application server being migrated is managed by an administrative agent that has administrative security enabled.
This parameter is required only if the application server being migrated is managed by an administrative agent.
This parameter is required only if the application server being migrated is managed by an administrative agent.
This parameter is required only if the application server being migrated is managed by an administrative agent.
This parameter is required only if the application server being migrated is managed by an administrative agent that has administrative security enabled.
This parameter is required only if the application server being migrated is managed by an administrative agent that has administrative security enabled.
The value "-Xms...m" specifies the starting heap size. Replace the "..." with the size in Megabytes that you need. For example, if the starting heap size is to be 128 MB, specify the parameter as: -javaoption -Xms128m
The value "-Xmx...m" specifies the maximum heap size. Replace the "..." with the size in Megabytes that you need. For example, if the maximum heap size is to be 1024 MB, specify the parameter as: -javaoption -Xmx1024m
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 Version 8.5 target configuration during the migration.
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 if you want to make changes to the migrated java.security file.
?security.provider.* - add a prefix to 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