Migrating and coexisting
This topic describes migrating, which is copying the configuration
from a previous release of a WebSphere Application Server product into a new
release. This topic also describes coexisting, which is running a new release
of a WebSphere Application Server product on the same machine at the same
time as you run an earlier release.
Before you begin
IBM Support offers tutorials on various WebSphere Application Server
installation topics. See WebSphere education on demand: Installation best practices
tutorials
for more information. One topic describes migration. Another
topic describes installing a coexisting WebSphere Application Server product.
Determine if an existing version of WebSphere Application
Server is installed on the machine where you plan to install your Version
5.x product.
Why and when to perform this task
If you have a previous version,
you must decide whether to copy the configuration and applications of the
previous version to the new version. Migration does not uninstall the previous
version. The earlier release is still functional but you cannot run both releases
at the same time. To run an earlier release and the new release at the same
time is coexistence. You must provide non-default port assignments to support
coexistence, by selecting the coexistence option during installation.
See Migration and coexistence overview for
more information.
Steps for this task
- Prepare to migrate or update product
prerequisites and corequisites to supported versions.
Refer to the
WebSphere Application Server detailed system
requirements
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27006921
Web site for current requirements.
An example is the embedded messaging feature.
V5.0.0 and V5.0.1 use a level of embedded messaging that is
incompatible with the level supported by V5.0.2. To solve this problem, upgrade V5.0.0 or V5.0.1 to V5.0.2 by applying
Fix Pack 2.
- Prepare to use the migration function
of the Installation wizard, to migrate silently, or to migrate using the migration
tools.
You have the option of letting the Installation wizard issue
the commands to use the migration tools or you can issue the commands after
installation.
The Installation wizard detects a previously installed version,
and displays a coexistence panel. If you choose not to coexist with the existing
product, the Installation wizard displays a migration panel. You can select
either option or no option.
- Start the administrative server of WebSphere Application Server
Standard Edition (V3.5.x) or WebSphere Application Server Advanced Edition
(V3.5.x or V4.0.x).
When you start the administrative server, the
migration tools can use the XMLConfig tool to export the configuration data
repository. It is not necessary that you start the administrative server for
WebSphere Application Server Advanced Single Server Edition, V4. The migration
tools use the XML Metadata Interchange (XMI) configuration files directly.
- Select the migration option and click Next when using
the Installation wizard. When using the silent installation method, select
the appropriate option.
Enter a fully qualified path for the backup
directory, where the migration tools store and read the saved configuration
and other files. During migration, the wizard backs up the old version of
the administrative configuration and the user data files, but does not uninstall
the old version. The wizard automatically configures the new installation
with the previous configuration data and copies some application data to the
newer version.
The Installation wizard uses the WASPreUpgrade migration
tool to export the current administrative configuration. After this phase
completes, the wizard runs the second phase, which uses the WASPostUpgrade
migration tool to convert the backed-up administrative configuration into
the new V5.x configuration. You can stop the administrative server of the
earlier version after the migration is complete. You must stop the administrative
server of the earlier version before starting the V5.x WebSphere Application
Server.
The installation program prompts you for the following information
during migration:
- Backup directory.
- Currently installed WebSphere Application Server directory. You must install
V5.x in a different directory.
- Plan to complete the migration after the installation is complete.
Here is an overview of the tasks that you must perform to complete the
migration:
- Stop all servers from the earlier version.
- Load existing applications into your development environment and fix any
known problems.
- Start the Application Servers in the new installation.
- Deploy the changed applications in a test environment.
- Test all applications thoroughly.
- Follow normal test procedures as you move the test environment into production.
The Installation wizard backs up the earlier version but does not
uninstall it, exports the current configuration, and migrates the configuration
to the new installation. If errors result when using the WASPreUpgrade tool,
the Installation wizard does not run the WASPostUpgrade tool. The wizard displays
the WASPreUpgrade.log and the WASPostUpgrade.log files if
errors occur.
Migrate the configuration
of a previous version to Enterprise using the Installation wizard or using
a silent installation. See Migrating to Enterprise V5.0.x and Installing silently for more information.
Migrate
the configuration using the migration tools if you prefer a more incremental
approach.See
Migrating configuration data for more information. The
Migrating topic describes migrating from
V4.x (little to consider) or V3.5.x (several things to consider). The topic
describes differences between V3.5.x and V5.0.x that result from the full
compliance of V5.0.x with Java 2 Platform, Enterprise Edition (J2EE) specifications.
- Set up multiple versions
of WebSphere Application Server to coexist.
No run-time conflicts
can exist for multiple instances and versions of WebSphere Application Server
to run at the same time on the same machine. Potential conflicts can occur
in these areas:
- Prerequisites and corequisites, including the level of the embedded messaging
feature
- Operating system registration
- Environmental conflicts
- File system
- Port assignments
![[5.0 only]](../../v50.gif)
Run V3.5.x and V5.0.x together, as described in Setting up Version 3.5.x and Version 5 coexistence.
![[5.0 only]](../../v50.gif)
Run V4.0.x and V5.0.x together,
as described in Setting up Version 4.0.x and Version 5.x coexistence.
![[5.0 only]](../../v50.gif)
Install V5.0.x more than once
on the same machine, as described in Setting up Version 5 coexistence.
Results
The
migration function migrates all of your resources and applications, but does
not migrate entities in your classes directory. As the WebSphere
Application Server Installation wizard migrates applications to Version V5.0.x,
it also migrates any applications that use IBM WebSphere Business Integration
Server Foundation Edition, Version 4.0.x.
The
base migration removes (from the server configuration) those parts of your
configuration that are dependent upon the Integration Server services.
Migration
saves the following files in the backup directory.
- For Version 3.5.x:
- bin/setupCmdLine.sh (or bin/setupCmdLine.bat for Windows
platforms)
- classes (not saved for iSeries)
- deployableEJBs (Advanced Edition only)
- deployedEJBs (Advanced Edition only)
- hosts
- properties
- servlets
- For Version 4.0.x:
- bin/setupCmdLine.sh (or bin/setupCmdLine.bat for Windows
platforms)
- classes (not saved for iSeries)
- config
- installableApps
- installedApps (by default unless overriden within a specified
developer configuration file)
- installedConnectors (Version 4.x Advanced Edition only)
- properties
You can coexist with,
or migrate the applications and configuration from a previous version of WebSphere
Application Server.
What to do next
Migration
from V4.x to V5.0.x does not require extensive tuning. Migration from V3.5.x
to V5.0.x does require that you examine the migrating applications. See Migrating configuration data for a
description of fine tuning a migration. Part of the procedure for using the
migration tools includes a description of what to tune after using the tools.
After migrating, return to Installing the product.
For more information on coexistence among releases,
see Migration and coexistence overview.

Migration and coexistence overview
Migrating
Configuration mapping during migration
Migration tools

Installing the product
Creating multiple Version 5 configuration instances

Coexistence support
Port number settings in WebSphere Application Server versions
Default coexistence settings for port numbers
Installation: Resources for learning
Searchable topic ID:
tins_prev
Last updated: Jun 21, 2007 8:07:48 PM CDT
WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/tins_prev.html