Network Deployment (Distributed operating systems), v8.0 > Migration and coexistence > Migrate Data access resources
Migrate data sources
- Migrate applications to use data sources of the current Java EE Connector Architecture (JCA)
Migrate the applications that use v4 data sources, or data sources (WAS V4), to use data sources that support more advanced connection management features, such as connection sharing.
- Verify Cloudscape automatic migration
Version 7.0 of the application server requires Cloudscape or Apache Derby to run at a minimal version of v10.1.x. During the application server upgrade to version 7.0, the migration tool automatically upgrades the database instances that are accessed through the embedded framework by some internal components, such as the UDDI registry. The tool also attempts to upgrade Cloudscape or Derby instances that the applications access through the embedded framework. We must verify the migration results for these backend databases.
- Upgrade Cloudscape manually
During the upgrade of your application server, the migration tool attempts to upgrade instances of Cloudscape that are accessed through the embedded framework only. The automatic upgrade excludes Cloudscape instances that transact with applications through the Network Server framework. This exclusion eliminates the risk of corrupting third party applications that access the same database instances as the application server. We must manually upgrade database instances that are accessed through the Network Server framework. Do the same for databases that fail the automatic migration.
- Directory conventions
References in product information to WAS_HOME, PROFILE_ROOT, and other directories imply specific default directory locations. This topic describes the conventions in use for WAS.