InfoCenter Home >
3: Migration overview
3: Migration overview
Migration focuses on leveraging the existing environment and applications,
changing them to be compatible with the current product version, instead of
starting from the beginning.
Migration for IBM WebSphere Application Server
Version 3.5
includes the following activities:
Activity |
Where to find instructions |
1. Migrate or upgrade product prerequisites to supported versions
As the product version changes, its prerequisites or corequisites
also change. It is probably necessary to update your database, Web
server, JDK version, and other software.
|
Article 3.1 |
2. Upgrade to IBM WebSphere Application Server
Version 3.5
In most cases, migration programs are available to ease the transition.
However, some manual preparation may be necessary.
For example, Version 3.5 offers options
for backing up product customizations (such as Version 3.0x modifications
to the Web server configuration file) before installing the Version 3.5 code,
allowing preserved changes to be migrated to Version 3.5.
To determine the version and release of your current installation,
click Help > About
from the menu bar of the Java administrative console.
Programmatic support for migration
from Version 2.0x is not provided.
To migrate your installation from Version 2.0x,
follow the documentation, starting at article 3.2.1.
|
Article 3.2.
See also
Installing the product |
3. Update application code to supported specification and API levels
Note:
Article 3.3.2a describes the migration issues
with using the Java Servlet API 2.2 specification.
Section 4 of the InfoCenter focuses
on developing new applications, though it also outlines new APIs whose functions
you might add to existing applications in a piecemeal fashion.
|
Article 3.3 |
4. Redeploy applications on
Version 3.5
|
Article 6.4.2 |
5. Migrate administrative configurations
If your company has been using a previous product version,
the system administrator has probably fine-tuned various application
and server settings for the environment.
It is important to have
a strategy for migrating these settings with
maximum efficiency and minimal loss.
|
Article 3.4
|
|
|