Before you begin the process of migrating to WebSphere Application Server Version 6.1, there are some considerations of which you need to be aware.
This ensures that your system has all of the necessary prerequisites and supports the new level of WebSphere Application Server.
Prior levels of WebSphere Application Server will continue to run at the higher prerequisite levels.
In particular, note that the default daemon port definition for both versions is the same when installing to coexist with WebSphere Application Server Version 5.x or 6.0.x.
See Port number settings in WebSphere Application Server versions for default port information.
See Coexisting.
Note that in this mixed-release environment, there might be some restrictions on what you can do with servers at the older release level. There might also be restrictions on creating clusters and cluster members.
To avoid configuration problems, use servlet APIs to control the file location instead of using the default location.
If you create a profile with a new cell name, the migration will fail.
MIGR0378E: The node name of the new configuration must be the same as the old configuration: {0} for this environment.
If you installed an application in your old environment with Use Metadata From Binaries set to true and during that installation or a future update of the application you made a change to the application's metadata (such as JNDI resource references or database entries for example), the change might be lost when you migrate.
When Use Metadata From Binaries is set to true, the administrative code only updates the metadata in the binary EAR file. This option is not supported in a mixed cell; therefore, it is automatically turned to false as part of migration. When this happens, the expanded metadata in the configuration directories take precedence over the values in the binary EAR file. This causes the values from the original EAR file installation to take precedence over any updates that you might have made.
If Version 6.1 does not support a level for which JSP objects are configured, the migration tools recognize the objects in the output and log them.