Before you begin the process of migrating to WebSphere® Application Server Version 7.0, there are some considerations of which you need to be aware.
For more information, read the "Deprecated and removed features" article in the information center.
Read Migrating API and specifications for more information.
Prior levels of WebSphere Application Server continue to run at the higher prerequisite levels.
Read Port number settings in WebSphere Application Server versions for default port information.
Read Running multiple application server versions for more information.
If trace is enabled, which is the default, up to 1 GB (depending on the size and complexity of your configuration)
Port type | Value |
---|---|
Application server | 9633 |
Administrative agent | 9630 |
Job manager | 9631 |
Secure proxy server | 9633 |
Administrative subsystem | 9634 |
IPC_CONNECTOR_ADDRESS port conflicts might exist after running the migration jobs. Reconfigure the conflicting ports.
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.
Read the "Lightweight Third Party Authentication" article in the information center for more information.
If Version 7.0 does not support a level for which JSP objects are configured, the migration tools recognize the objects in the output and log them.
Read Migrating IBM Cloudscape or Apache Derby databases for more information.
Read Migrating from the WebSphere Connect JDBC driver for more information.