Migration and coexistence overview

 

+

Search Tips   |   Advanced Search

 

WebSphere Application Server contains migration tools that provide migration functionality.

The migration wizard provides a graphical user interface to these migration tools.

The migration tools migrate applications and configuration information to the new version, as described in...

• Migrate product configurations
• Configuration mapping during migration

For V5.x to V6, see also...

• Profile creation, using either the Profile creation wizard or the wasprofile command
• Incremental cell upgrade
• Migrate V6.0 servers from multi-broker replication domains to data replication domains
• Comparison of multi-broker versus data replication domains
• Migrate to V3 of the UDDI Registry
• Migrate a complete gateway configuration
• Migrate from v5 embedded messaging
• Manage WebSphere v5 JMS use of WebSphere v6 messaging resources

If you neither migrate nor coexist with an earlier version of WebSphere Application Server, you are choosing to ignore the previous installation, and we can run only one version at a time because of conflicting default port assignments.

It is possible for two versions of WAS to run at the same time without conflict if you use non-default ports for one of the WAS instances. To setup coexistence, during installation, select the radio button that states...

Install a new copy of the V6 Application Server product

We can resolve conflicting port assignments by specifying port assignments for coexistence during...

• Profile creation

• wsadmin scripting

• Using the console page...

  Servers | Application Servers | server1 | End Points

Migrating and coexisting have roughly opposite goals. The goal of migration is to reconstruct your earlier version in a nearly identical V6 environment, including...

• applications
• configuration settings
• universal resource identifier (URI) descriptors
• Web server context roots

The migration wizard uses the migration tools to migrate the previous configuration and applications.

The goal of coexistence is to create an environment that is not in conflict with an earlier version, so far as port settings are concerned. This allows both nodes to start and run at the same time. 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
  • 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

See Port number settings in WAS versions for more information.

Consider these issues in a migration or coexistence scenario:

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

• If your deployment manager is configured to run as non-root

  Change the ownership and file permissions of the deployment manager directories after running WASPostUpgrade. This must be done before starting the V6 deployment manager.

• If your node agent or application server has been configured to run as non-root.

  Change the ownership and file permissions of the node directories after running WASPostUpgrade. This must be done before starting the V6 node agent or application server.

---

 

Related Information

Migrating product configurations

 

---