Before you begin
As the WebSphere Application Server installation wizard migrates applications to Version 5, it also migrates any applications that use IBM WebSphere Application Server Enterprise Edition, Version 4.x. If you install and migrate the WebSphere Application Server base product before installing the Enterprise product, the base migration removes the parts of your configuration from the server configuration that are dependent upon the following IBM WebSphere Application Server Enterprise Edition, Version 4.x services:
The migration process of the base product issues warnings that describe the parts of your configuration that are disabled. It records these warnings in a log file. Disabled services are unavailable to Version 5 applications until you install and migrate WebSphere Application Server Enterprise, which restores the disabled classes.
Why and when to perform this task
There are four scenarios for Enterprise migration:
Follow the scenario below to migrate both products.
Steps for this task
If there is no base product or Network Deployment product installed, the WebSphere Application Server Enterprise installation wizard installs the required WebSphere Application Server base product.
The WebSphere Application Server Enterprise installation wizard updates an already installed WebSphere Application Server product, if required base product features are not already installed.
The WebSphere Application Server Enterprise installation wizard looks for and migrates a previous WebSphere Application Server installation (both an earlier base product or the Enterprise Edition, an earlier version of the Enterprise product), if you choose to let it do so.
The WebSphere Application Server Enterprise installation wizard displays a migration panel for the Network Deployment product, if you are installing Enterprise on the Network Deployment product and the Network Deployment product has not been migrated. Select the option to migrate the Network Deployment product.
Note: After federating a base Application Server node into a deployment manager cell, you cannot use the migration tools on the Application Server node. To use these tools again, remove the node from the cell, use the tools, and add the node to the cell again. You can, however, use the migration tools on a Network Deployment node after base Application Server nodes have been added.
An error can occur during migration when installing the Enterprise product on a Network Deployment node after base Application Server nodes have been added. A migation messages panel appears at the end of the installation with messages similkar to these:
MIGR0122E: Unable to read configuration file /opt/WebSphere/DeploymentManager/config/cells/ws-sunfish2Network/nodes/. at com.ibm.websphere.migration.postupgrade.TransformBaseConfiguration. resolveDirectory(TransformBaseConfiguration.java:690) at com.ibm.websphere.migration.postupgrade.TransformBaseConfiguration. initializeDataModel(TransformBaseConfiguration.java:587) at com.ibm.websphere.migration.postupgrade.TransformBaseConfiguration. doIt(TransformBaseConfiguration.java:1145) at com.ibm.websphere.migration.postupgrade.Restore.doIt(Restore.java:153) at com.ibm.websphere.migration.postupgrade.Restore.<init>(Restore.java:93) at com.ibm.websphere.migration.postupgrade.WASPostUpgrade. restore(WASPostUpgrade.java:196) at com.ibm.websphere.migration.postupgrade.WASPostUpgrade. main(WASPostUpgrade.java:665) at java.lang.reflect.Method.invoke(Native Method) at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94) com.ibm.websphere.migration.exceptions.WASUpgradeInvalidConfigurationException: MIGR0122E: Unable to read configuration file /opt/WebSphere/DeploymentManager/config/cells/ ws-sunfish2Network/nodes/.
The workaround is to invoke the WASPostUpgrade migration tool after Installation has completed. Use the -nodeName parameter to specify the Deployment Manager node on the WASPostUpgrade commandcommand.
You might have already installed and migrated the base WebSphere Application Server product before installing the Enterprise product. If so, installing and migrating the Enterprise product synchronizes both versions and completes the migration of any applications that used IBM WebSphere Application Server Enterprise Edition, Version 4.x.
You can also install the WebSphere Application Server Enterprise product silently, and migrate an earlier version configuration silently. You must supply values for silent migration options when you tailor the option response files for installing Enterprise on either the base product or the Network Deployment product:
You can also configure the options response file for coexistence with an earlier version by specifying non-conflicting port assignments in the file.
CORBA C++ SDK servers are registered in the implementation repository of Enterprise, Version 4.x. You must manually register them in the implementation repository of WebSphere Application Server Enterprise to migrate them.
What to do next
Return to Migrating and coexisting to continue.