Various configurations are mapped during product-configuration migration.
Migration always involves migrating a single profile to another single profile on the same iSeries server.
The migration tools map objects and attributes existing in the version or WebSphere Application Server from which you are migrating to the corresponding objects and attributes in the V6.1 environment.
Many migration scenarios are possible. The migration tools map objects and attributes existing in the version from which you are migrating to the corresponding objects and attributes in the V6.1 environment.
If the -portBlock parameter is specified during the call to WASPostUpgrade, however, a new port value is given to each application server that is migrated to V6.1.
The migration tools convert appropriate command-line parameters to JVM settings in the server process definition. Most settings are mapped directly. Some settings are not migrated because their roles in the WAS V6.1 configuration do not exist, have different meanings, or have different scopes.
It is best that you reinstall the resource into the new WAS directory. Whatever you choose to do, the final step is to reset the reference to the new location of the application.
If the old resource that the generic server was managing is not installed under the old WAS installation, nothing further is required.
Migrate the deployment manager first, before migrating any base nodes in the cell.
Use the same cell name when migrating Network Deployment from V5.x or 6.0.x to V6.1. If you use a different cell name, federated nodes cannot successfully migrate to the Network Deployment V6.1 cell.
Migrating a base WAS node that is within a cell to V6.1 also migrates the node agent to Version 6.1. A cell can have some V6.1 nodes and other nodes that are at Version 5.x or 6.0.x levels. See Coexistence support for information on restrictions on using mixed-release cells.
Migration does not overlay property files.
In this case, the RARs are copied over to the corresponding location in the new WAS installation. Relational Resource Adapter RARs will not be migrated.
WAS v6.0 cluster-level resources are configured in resourcexxx.xml files under the cluster directories.
For example...
<resources.j2c:J2CResourceAdapter
xmi:id="J2CResourceAdapter_1112808424172"
name="ims"
archivePath="${WAS_INSTALL_ROOT}\installedConnectors\x2.rar">
...
</resources.j2c:J2CResourceAdapter>
If you have a cluster-level resource, this resource must be in the same location on each cluster member (node). Using the above example, therefore, each cluster member must have the RAR file installed at location...
${WAS_INSTALL_ROOT}\installedConnectors\x2.rar
${WAS_INSTALL_ROOT} is resolved on each cluster member to get the exact location.
In the migration of a deployment manager, the tools migrate the cluster files on the deployment manager, including the resourcexxx.xml files.
In the migration of a managed node, the tools process each J2C adapter. Files such as RAR files are migrated differently depending on whether you are migrating from V5.x to V6.x or from V6.0.x to V6.1.
Because the profile structure changed in V6.0, migration from V5.x to V6.x copies files such as RAR files from the location set for the WAS_INSTALL_ROOT variable to the location set for the USER_INSTALL_ROOT variable and modifies any paths to reflect these changes.
Migration from V6.0.x to V6.1 copies files such as RAR files from WAS_INSTALL_ROOT to WAS_INSTALL_ROOT and from USER_INSTALL_ROOT to USER_INSTALL_ROOT.
If you have a RAR file in the WAS_INSTALL_ROOT for V6.0.x, for example, the migration tools do not automatically copy the file from WAS_INSTALL_ROOT to USER_INSTALL_ROOT as they would do in a V5.x to 6.x migration. This maintains the integrity of the cluster-level J2C resources.
If you hardcoded a path to a RAR file, for example...
archivePath="C:/WAS/installedConnectors/x2.rar
...in V6.0.x, however, the V6.1 migration tools cannot change the archivePath attribute to reflect this because that would break all of the other cluster members that have not been migrated.
During the migration of the deployment manager, only WAS V5.x samples for federated nodes are migrated. Equivalent Version 6.1 samples are available for all other V5.x samples and all Version 6.0.x samples.
Java 2 security is enabled by default when you enable security in WAS V6.1. Java 2 security requires you to grant security permissions explicitly.
There are several techniques used to to define different levels of Java 2 security in Version 6.1. One is to create a was.policy file as part of the application to enable all security permissions. The migration tools call the wsadmin command to add an existing was.policy file in the V6.1 properties directory to enterprise applications as they are being migrated.
When migrating to WAS V6.1, your choice of whether or not to migrate to support script compatibility results in one of two different outcomes.
This is the default.
For example, existing keyfiles and trustfiles are moved out of the SSLConfig repertoire and new keystore and truststore objects are created.
For more information on migrating your security configurations to V6.1, see Migrating, coexisting, and interoperating Security considerations.
The location for these directories is typically the logs directory under the WAS profile directory. For WAS V6.1, the default location for the stdin, stdout, and stderr files is the logs directory located under the WAS profile directory—for example, the logs directory for the default profile is...
/QIBM/UserData/WebSphere/AppServer/V61/Base/profiles/default/logs
The migration tools attempt to migrate existing passivation and working directories. Otherwise, appropriate V6.1 defaults are used.
For more information on passivation directories, see EJB container settings.
For more information on working directories, see Process definition settings.
In a coexistence scenario, using common directories between versions can create problems.
The migration tools migrate all ports. The tools log a port-conflict warning if a port is already defined in the configuration. You must resolve any port conflicts before you can run servers at the same time.
If the -portBlock parameter is specified in the WASPostUpgrade command, a new value is assigned to each transport that is migrated. Choosing -scriptCompatibility="true" or -scriptCompatibility="false" results in two different outcomes for transport ports if you are migrating from WAS V5.x:
This results in your transport ports being brought over as they are. This is the default.
This results in the transport ports being converted to the implementation of channels and chains. From an external application usage standpoint, they will still act the same; but they have been moved to the TransportChannelService.
For more information on the WASPostUpgrade command, see WASPostUpgrade command.
For further information on transport chains and channels, see Transport chains.
You must manually add virtual host alias entries for each port. For more information, see Configuring virtual hosts.
The specification level of the J2EE implemented in WAS V6.0.x required behavior changes in the Web container for setting the content type. If a default servlet writer does not set the content type, not only does the Web container no longer default to it but the Web container returns the call as "null."
This situation might cause some browsers to display resulting Web container tags incorrectly. To prevent this problem from occurring, migration sets the autoResponseEncoding IBM extension to "true" for Web modules as it migrates enterprise applications.