Introduction

The goal of migration is to reconstruct your earlier version of WebSphere Application Server in a nearly identical V6.1 environment.

A goal of coexistence is to create a mixed-version environment that is not in conflict and allows the nodes of all versions to start and run at the same time; another goal is to create an environment that facilitates rollback and allows one or the other version to run at one time.

Interoperating is exchanging data between two coexisting product installations or between products on different systems.

WAS V6.1 can coexist with V5.x and V6.0.x. Depending on the previous version of WAS, there might be port conflicts that need to be resolved.

To migrate...

1. Test applications in a non-production WAS V6.1 environment.

2. Use migration tools to migrate applications and configuration information to the new version.

WAS V6.1 migration leverages the existing configuration and applications and changes them to be compatible with the WAS V6.1 environment. Existing application components and configuration settings are applied to the V6.1 environment during the migration process.

If you use an earlier version of WAS, the system administrator might have fine-tuned various application and server settings for your environment. It is important to have a strategy for migrating these settings with maximum efficiency and minimal loss.

You can perform incremental migration of your WAS V5.x or 6.0.x configuration by calling the migration tools multiple times, each time specifying a different set of instances or profiles.

See also:

1. manageprofiles command
2. Migrate servers from multi-broker replication domains to data replication ains
3. Comparison of multi-broker versus data replication domains
4. Migrate to V3 of the UDDI registry
5. Migrate a complete gateway configuration
6. Migrate from V5 embedded messaging
7. Manage WebSphere V5 JMS use of WebSphere version 6 messaging resources

If you neither migrate nor coexist with an earlier version of WAS, you are choosing to ignore the previous installation and you can run only one version at a time because of conflicting default port assignments. It is possible for both versions to run at the same time without conflict if you use non-default ports in the earlier version. To set up coexistence with WAS V5.x or 6.0.x, ensure that unique ports are selected during profile creation for the V6.1 installation. To set up coexistence with an existing installation of Version 6.1, select the radio button that states "Install a new copy of the V61 Application Server product" during installation.

You can resolve conflicting port assignments by specifying port assignments for coexistence during profile creation, by wsadmin scripting or by using the console page...

Servers | Application Servers | server1 | Ports

...administrative console page to ensure that WAS V6.1 can run with an earlier version.

Coexistence processing changes the following configuration files:

• virtualhosts.xml
  • HTTP Transport Port
  • IBM HTTP Server Port
  • HTTPS Transport Port
  • HTTP Administrative Console Port
  • HTTPS Administrative Console Secure Port

• serverindex.xml
  • Bootstrap Address
  • SOAP Connector Address
  • DRS Client Address
  • SAS SSL ServerAuth Listener Address (V6.0.x and previous servers only that are federated in a V6.1 cell)
  • CSIV2 SSL ServerAuth Listener Address
  • CSIV2 SSL MutualAuth Listener Address
  • WC adminhost
  • WC defaulthost
  • DCS Unicast Address
  • WC adminhost secure
  • WC default secure
  • SIB Endpoint Address
  • SIB Endpoint Secure Address
  • SIB MQ Endpoint Address
  • SIB MQ Endpoint Secure Address

Consider these issues in a migration or coexistence scenario:

• Conflicting context roots when attempting to share the same Web server.

  Follow the procedure in Migrating Web server configurations to learn how to configure a Web server for sharing between WAS versions.

• A WAS Version 6.1 deployment cell can contain mixed releases of V5.x or 6.0.x nodes, but there is no mixed-node management support for V6.0.0.x and Version 6.0.1.x. The V6.1 migration tools still migrate these nodes during deployment-manager migration, but they issue a warning message that the nodes cannot be managed by the V6.1 deployment manager. You can then do one of the following based on your needs.

  • Upgrade all V6.0.0.x and V6.0.1.x nodes to at least Version 6.0.2. This will allow them to be administered by a V6.1 deployment manager.

  • Immediately migrate these nodes to V6.1.

Related tasks