The migration tools migrate any Apache Derby instances
to the new configuration, and they copy any Apache Derby instances
that are stored in the previous release's WebSphere® Application Server configuration
tree to the new release's configuration tree. After you use the migration
tools, verify the results of the database migration and manually migrate
any database instances or copy any Derby database instances that the
tools do not automatically migrate or copy.
About this task
WebSphere Application Server Version 9.0 requires Apache
Derby Version 10.3 or later. Apache Derby Version 10.3 is a pure Java™ database server that combines the Derby
runtime with the opportunity to use the full services of IBM® Software Support. For comprehensive information about Apache
Derby Version 10.3, read the Apache Derby Web site.
Important: Derby-to-Derby migration performs a file-system copy
of the data at a given point in time. This snapshot will not remain
in sync with the database in the previous installation. If you roll
back to the previous release, any updates to the database that you
made after migration will not be reflected in the previous installation.
Procedure
- Migrate the configuration to Version 9.0.
- Verify that the Derby database instances have been copied.
When you migrate from WebSphere Application Server Version 7.0 or later to Version 9.0, the
migration tools automatically upgrade Derby database instances that
are accessed through the embedded framework by some internal components
such as the UDDI registry. The tools also attempt to upgrade Derby
instances that your applications access through the embedded framework.
You must verify these migration results after running the migration
tools.
- Manually copy Derby database instances where necessary.
- The Version 9.0 migration
tools do not attempt to migrate database instances that transact with
applications through the Apache Derby Network Server framework. This
exclusion eliminates the risk of corrupting third-party applications
that access the same database instances as those accessed by WebSphere Application Server.
To minimize
the risk of migration errors for databases that were only partially
upgraded during the automatic migration process, delete the new database.
Troubleshoot the original database according to the log diagnostic
data, then perform manual migration of the original database.
- The Version 9.0 migration
tools do not copy any Derby database instances outside the WebSphere Application Server configuration
tree.
If migration does not copy a Derby database instance automatically,
copy the database instance manually.
- Manually migrate your UDDI registry if it uses a database
on the Apache Derby Network Server framework.
Read Migrating
the UDDI registry in the documentation for more information.
What to do next
Read Installing and configuring the SDO repository in
the documentation for more information on upgrading the SDO repository
application to Version 9.0.