WebSphere Application Server - Express, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Migration and coexistence overview

WebSphere Application Server contains migration tools that provide migration functionality. The Migration wizard is new for Version 6; it provides a graphical user interface to the migration tools. The Migration wizard can call the migration tools, or you can execute them directly. The migration tools migrate applications and configuration information to the new version, as described in Migrating product configurations and Configuration mapping during migration.

Table 1. Overview of migrating from release to release
Migration path Description
V5.x to V6 The migration from V5.x to V6 is fairly routine. Important reference topics for this migration include:
V4.0.x to V6 The migration tools perform a fairly routine migration from V4 to V6. For example, Java 2 Platform, Enterprise Edition (J2EE) 1.2 enterprise archive (EAR) files in V4 work in V6 of WebSphere Application Server, which supports the J2EE 1.4 specification. Similarly, it is not necessary to redeploy enterprise Java bean (EJB) 1.1 Java archive (JAR) files when moving them from V4 to V6, which also supports EJB 2.0 JAR files. Also be aware that in V6, the statement cache size setting described in WebSphere Application Server data source properties collection is different from WebSphere Application Server V4.0.x. In V4.0.x, the maximum number of possible prepared statements is cached for the data source within an application server. In V5.0 and higher, statement cache size is defined on a given physical connection.

If you neither migrate nor coexist with an earlier version of WebSphere Application Server, 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 setup coexistence with V4.0.x or V5.x, ensure that unique ports are selected during profile creation for the V6 installation. To setup coexistence with V6, select the radio button that states, "Install a new copy of the V6 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 Servers > Application Servers > server1 > End Points administrative console page to ensure that Version 6 can run with an earlier version.

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, and 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:

See Port number settings in WebSphere Application Server versions for more information.

Consider these issues in a migration or coexistence scenario:



Related tasks
Migrating and coexisting

Related information
Migrating product configurations

Concept topic    

Terms of Use | Feedback

Last updated: Jun 8, 2005 12:45:23 PM EDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/cins_prev.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)