BTT version 6.1.2 provides the following functions to help you migrate
your applications from BTT version 4.3 to BTT version 6.1.2:
- Definition Transformation
- This feature transforms the definition files from BTT version 4.3 to BTT
version 6.1.2. All the existing definition files are converted or migrated
to the corresponding BTT version 6.1.2 definition files. For example, the
definition file dse.ini is converted to another definition file btt.xml.
- Java™ Code
Migration
- Because many components in BTT version 6.1.2 are different from those
in BTT version 4.3, the migration tool in BTT version 6.1.2 provides a function
to make the previous code migrated from the existing BTT version
4.3 program to the BTT version 6.1.2 base program. This reduces the workload
for the application program migration.
- Customer Extension Support
- This is a key feature of the migration tool. The migration tool is rule-based,
which means that the specific migration action depends entirely on the given
rules. You can customize your own migration rules to meet the program migration
requirements.
- Default Migration Rules Provided
- BTT version 6.1.2 provides default migration rules for migration from
BTT version 4.3 to BTT version 6.1.2. You can leverage the default rules directly
or extend it to meet your additional requirements.
- Exclusions
- UI features here refer to the JSP presentation logic and Swing based presentation
logic. In BTT version 6.1.2, Swing based Java client is totally compatible with BTT
version 4.3, so no migration is needed. As for JSP presentation logic, you
need to migrate it manually.
- Constraints
- To reduce the complexity of the migration process, the migration tool
limits the availability. The migration tool is rule based, so you are not
able to migrate the migration scenarios that rules cannot represent.