IBM® WebSphere® Multichannel Bank
Transformation Toolkit version 7.1 provides
the following functions to help you to migrate your applications from WebSphere Multichannel
Bank Transformation Toolkit version 4.3 to WebSphere Multichannel
Bank Transformation Toolkit version 7.1:
- XML migration
- This feature transforms the definition files from WebSphere Multichannel
Bank Transformation Toolkit version 4.3 to WebSphere Multichannel
Bank Transformation Toolkit version 7.1. All the
existing definition files are converted or migrated to the corresponding WebSphere Multichannel
Bank Transformation Toolkit version 7.1 definition
files. For example, the dse.ini definition file
is converted to the btt.xml definition file.
- Java code
migration
- The migration tool scans the code of your applications and automatically
replaces the code of WebSphere Multichannel
Bank Transformation Toolkit version 7.0, or
earlier, with WebSphere Multichannel
Bank Transformation Toolkit version 7.1 code by
renaming packages and some classes and methods. This reduces the workload
for the application program migration.
- JSP migration
- The JSP migration tool identifies Java code in JSP pages and replaces
the code of WebSphere Multichannel
Bank Transformation Toolkit version 7.0, or
earlier, with WebSphere Multichannel
Bank Transformation Toolkit version 7.1 code by
renaming packages and some classes and methods.
- Migration report
- After the migration, a migration report is generated that provides
information on the successfully migrated code and the code that must
be migrated manually.
- Customer Extension Support
- The migration tool includes default and common customer rules,
which have been identified in real migration scenarios, to improve
automatic migration. If you have extended or modified WebSphere Multichannel
Bank Transformation Toolkit extensively,
you can customize your own migration rules to meet your migration
requirements.
- Exclusions
- In WebSphere Multichannel
Bank Transformation Toolkit version 7.1, Swing-based
Java client is wholly compatible with WebSphere Multichannel
Bank Transformation Toolkit version 4.3; therefore,
no migration is required.
- Constraints
- A migration procedure can be automated only when the migration
procedure has been written as rules, otherwise migration might need
to be performed manually. This scenario occurs only if you have modified
or extended WebSphere Multichannel
Bank Transformation Toolkit code
bases extensively.