After you use the migration tools to migrate to WebSphere Application
Server Version 6.1, you should verify the results of the automatic Cloudscape
database migration and manually migrate any Cloudscape database instances
that are not automatically migrated by the tools.
Before you begin
See Overview of migration, coexistence, and interoperability and Premigration considerations.
Tips:
- Before you migrate a Cloudscape database, ensure that any application
servers hosting applications that are using the Cloudscape database are shut
down. Otherwise, the Cloudscape migration will fail.
- Before you run the migration tools, ensure that the debug migration
trace is active. By default, this trace function is enabled. To reactivate
the debug migration trace if it is disabled, set one of the following trace
options:
- all traces*=all
- com.ibm.ws.migration.WASUpgrade=all
About this task
WebSphere Application Server Version 6.1 requires Cloudscape Version
10.1.
Cloudscape Version 10.1 is a pure Java database server that combines
the Apache Derby runtime with the opportunity to use the full services of
IBM Software Support. For comprehensive information about Cloudscape Version
10.1, see the Cloudscape section of ibm.com at http://www.ibm.com/software/data/cloudscape/.
For help in troubleshooting problems when
migrating, see Troubleshooting migration.
Procedure
- Verify the automatic migration of Cloudscape database instances.
When you migrate from WebSphere Application Server Version 5.x or
6.0.x to Version 6.1, the migration tools automatically upgrade the database
instances that are accessed through the embedded framework by some internal
components such as the UDDI registry. The tools also attempt to upgrade Cloudscape
instances that your applications access through the embedded framework. You
must verify these migration results after running the migration tools.
- Manually migrate Cloudscape database instances where necessary.
The Version 6.1 migration tools do not attempt to automatically migrate
database instances that transact with applications through the Cloudscape
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.
- Manually migrate your UDDI registry if it uses a database on the
Cloudscape Network Server framework.