Phase 3 of the migration process involves the migration
of your applications with the migration tool.
Procedure
To migrate your applications from WebSphere® Multichannel
Bank Transformation Toolkit version 5.2 to WebSphere Multichannel
Bank Transformation Toolkit version 7.1, do
the following steps:
- Replace the WebSphere Multichannel
Bank Transformation Toolkit version 5.2 JAR
files with WebSphere Multichannel
Bank Transformation Toolkit version 7.1 JAR
files, and change the build path of the project to the new JAR files.
- Import the application that you want to migrate to the
workspace as a project, and configure the migration tool. The
migration tool migrates the application directly based on the original
project.
- Migrate the dse.ini configuration
file to the btt.xml configuration file. In WebSphere Multichannel
Bank Transformation Toolkit version 5.2,
the configuration file is dse.ini, but in WebSphere Multichannel
Bank Transformation Toolkit version 7.1, the dse.ini configuration
file has been renamed as btt.xml.
- Migrate the definition files of global definition files
and self-defined operation and processor.
- Migrate the business logic. In WebSphere Multichannel
Bank Transformation Toolkit version 7.1, the
architecture is refined, and some components are re-designed; therefore,
the package names, class names, and some APIs in WebSphere Multichannel
Bank Transformation Toolkit version 7.1 are
different from those in WebSphere Multichannel
Bank Transformation Toolkit version 5.2.
However, the functions are still compatible. The migration tool will
automatically migrate these differences.
- Manually migrate the components that cannot be completely
migrated by the migration tool. Usually, failure to migrate components
with the migration tool are caused by errors. For information how
to fix the errors, refer to the Phase 4: Adding the business logic and fixing errors topic.