IBM® WebSphere® Multichannel Bank
Transformation Toolkit version 8.0 provides
the following functions to help you migrate your applications from WebSphere Multichannel
Bank Transformation Toolkit version 5.2 to WebSphere Multichannel
Bank Transformation Toolkit version 8.0:
- Definition transformation
- This feature transforms the definition files from WebSphere Multichannel
Bank Transformation Toolkit version 5.2 to WebSphere Multichannel
Bank Transformation Toolkit version 8.0. All
the existing definition files are converted or migrated to the corresponding WebSphere Multichannel
Bank Transformation Toolkit version 8.0. For
example, the dse.ini definition file is converted
to the btt.xml file.
- Java and
JSP 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 8.0 code
by renaming packages and some classes and methods. This reduces the
workload for the application program migration.
- Default migration rules provided
- WebSphere Multichannel
Bank Transformation Toolkit version 8.0 provides
default migration rules for migration from WebSphere Multichannel
Bank Transformation Toolkit version 5.2 to WebSphere Multichannel
Bank Transformation Toolkit version 8.0. You
can use the default rules or extend the default rules to meet additional
migration requirements.
- Customer extension support
- The migration tool is rule-based, which means that the migration
tasks that are carried out are defined as rules. You can add new rules
to meet your application migration requirements.
- Exclusions
- UI features here refer to the and Swing-based presentation
logic. In WebSphere Multichannel
Bank Transformation Toolkit version 8.0, Swing-based Java client is
wholly compatible with WebSphere Multichannel
Bank Transformation Toolkit version 5.2;
therefore, no migration is required.
- Constraints
- To reduce the complexity of the migration process, the number
of tasks that are performed by the migration tool are limited by the
rules that are defined in the tool. Migration tasks that are not defined
in the migration tool as rules are not performed.