How data is handled during migration from earlier versions
The WebSphere ESB version-to-version
migration tools will handle different sets of data (application data, configuration
data, database information, and long-running processes) in different ways.
Upgrading databases for migration
In conjunction with migration, the database schema of some WebSphere ESB components
must be upgraded. This can occur automatically but in two cases
you must upgrade the schema manually.
Migrating stand-alone servers
Migrate a stand-alone WebSphere ESB server,
choosing from several methods depending on your needs.
Verifying migration
Verify that your migration was successful by checking the
log files and checking operation with the administrative console.
Rolling back your environment
After migrating to a WebSphere ESBversion 6.2 environment,
you can roll back to a version 6.0.x or 6.1.x environment.
This returns the configuration to the state that it was in before
migration. After rolling back the environment, you can restart the
migration process.
Postmigration tasks for WebSphere ESB
After migration, you should check some configuration settings.
You might need to change them, or further configure the version 6.2 server.
Migrating Cloudscape databases
After you use the migration tools to migrate to WebSphere ESBversion 6.2, 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.