Various configurations are mapped during product-configuration migration.
Migration always involves migrating a single profile to another single profile on the same machine or a separate machine. Examples include a WebSphere® Application Server Version 6.x deployment manager migrating to a Version 7.0 deployment manager and a Version 6.x application server migrating to a Version 7.0 standalone application server.
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 Version 7.0 environment.
The migration tools carry the old release value into the Version 7.0 environment.
If a value for 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 Version 7.0.
The migration tools convert appropriate command-line parameters to Java™ Virtual Machine (JVM) settings in the server process definition. Most settings are mapped directly. Some settings are not migrated because their roles in the WebSphere Application Server Version 7.0 configuration do not exist, have different meanings, or have different scopes.
For information on how to change the process-definition settings, read the "Process definition settings" article in the information center. For information on how to change the JVM settings, read the "Java virtual machine settings" article in the information center.
It is best that you reinstall the resource into the new WebSphere Application Server 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 WebSphere Application Server installation, nothing further is required.
When migrating all WebSphere Application Server Version 5.1.x or Version 6.x EAR files to Version 7.0 using the wsadmin tool, the WASPostUpgrade tool uses the default maximum Java heap size value of 64 MB to install the EAR files.
java.lang.OutOfMemoryError JVMXE006:OutOfMemoryError
Increase the maximum Java heap size, and follow the example below to install the application.
Example of installing the application on WebSphere Application Server Version 7.0
wsadmin -conntype NONE -c "$AdminApp install C:\\WebSphere\\AppServer\\installableApps\\ EAR_file_name {-nodeployejb -appname app_name -server server_name -node node_name}"
Example of installing the application on WebSphere Application Server, Network Deployment Version 7.0
wsadmin -conntype NONE -c "$AdminApp install C:\\WebSphere\\ Manager\\installableApps\\ EAR_file_name> {-nodeployejb -appname app_name -cluster cluster_name}"
The JMS server was changed in WebSphere Application Server Version 6.x from type MESSAGE_BROKER to type APPLICATION_SERVER. Any queues or topics that it owned have been migrated into the default messaging provider, which is based on service integration technologies. In Version 5.1.x and earlier, jmsserver was its own MESSAGE_BROKER server in a WebSphere Application Server, Network Deployment environment; in the base environment, it was contained within APPLICATION_SERVER types.
All JMS resources were left untouched and should work without modification. Further migration of these resources can be performed by running scripts or bats provided by the Version 7.0 default messaging provider.
You can migrate a WebSphere Application Server Version 5.1.x or Version 6.x node that belongs to a cell without removing the node from the cell.
Migrate the deployment manager first, before migrating any base nodes in the cell.
Migrating a baseWebSphere Application Server node that is within a cell to Version 7.0 also migrates the node agent to Version 7.0. A cell can have some Version 7.0 nodes and other nodes that are at Version 5.1.x or Version 6.x levels. Read Coexistence support for information on restrictions on using mixed-release cells.
Migration copies files from prior version directories into the WebSphere Application Server Version 7.0 configuration.
RARs that are referenced by J2C resources are migrated if those RARs are in the old WebSphere Application Server installation. In this case, the RARs are copied over to the corresponding location in the new WebSphere Application Server installation. Relational Resource Adapter RARs will not be migrated.
<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 federated node, the tools process each J2C adapter. Files such as RAR files are migrated differently depending on whether you are migrating from Version 5.1.x to Version 7.0 or from Version 6.x to Version 7.0.
Because the profile structure changed in Version 6.0, migration from Version 5.1.x to Version 7.0 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 Version 6.x to Version 7.0 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 Version 6.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 Version 5.1.x to 7.0 migration. This maintains the integrity of the cluster-level J2C resources.
During the migration of the deployment manager, only WebSphere Application Server Version 5.1.x samples for federated nodes are migrated. Equivalent Version 7.0 samples are available for all other Version 5.1.x samples and all Version 6.x samples.
Java 2 security is enabled by default when you enable security in WebSphere Application Server Version 7.0. Java 2 security requires you to grant security permissions explicitly.
There are several techniques that you can use to define different levels of Java 2 security in Version 7.0. 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 Version 7.0 properties directory to enterprise applications as they are being migrated.
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 Version 7.0, read the "Migrating, coexisting, and interoperating – Security considerations" article in the information center.
The location for these directories is typically within the installation directory of a previous version. The default location for stdin, stdout, and stderr is the logs directory of the WebSphere Application Server Version 7.0 installation root.
The migration tools attempt to migrate existing passivation and working directories. Otherwise, appropriate Version 7.0 defaults are used.
In a coexistence scenario, using common directories between versions can create problems.
The migration tools migrate all ports. You must resolve any port conflicts before you can run servers at the same time.
If you specify the -portBlock parameter in the WASPostUpgrade command, a new value is assigned to each transport that is migrated.
If you specify true for the -replacePorts parameter in the WASPostUpgrade command, all port values from the old configuration are used in the new configuration. If you specify false for the -replacePorts parameter, the default port definitions in the new profile are not replaced with the values from the old configuration during migration. .
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, read WASPostUpgrade command.
For further information on transport chains and channels, read the 'Transport chains' article in the information center.
You must manually add virtual host alias entries for each port. For more information, read the "Configuring virtual hosts" article in the information center.
The specification level of the Java Platform, Enterprise Edition (Java EE) implemented in WebSphere Application Server Version 6.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.
If you migrate a Version 6.1 configuration that has feature packs installed, the migration tools might add one or two JVM system properties for each Java server in your configuration, including your administrative servers. Web servers are not affected. The properties are set to indicate to the JVM that the configuration should use a Java annotation scan policy other than the Version 7.0 default scan policy.
com.ibm.websphere.ejb.UseEJB61FEPScanPolicy = true
com.ibm.websphere.webservices.UseWSFEP61ScanPolicy = true
com.ibm.websphere.ejb.UseEJB61FEPScanPolicy = true com.ibm.websphere.webservices.UseWSFEP61ScanPolicy = true
A WebSphere Application Server, Network Deployment configuration requires that the deployment manager profile be augmented with all of the feature packs used in the cell. This means that the deployment-manager profile can potentially have both feature packs installed even if none of its federated nodes have both installed.