In this phase, you can start migrating your applications
with the migration tool.
About this task
To migrate your applications from BTT version 5.2 to BTT
version 7.0, take the following steps:
- Replace the BTT version 5.2 jar files with BTT version
7.0 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 will migrate the application directly based on the original project.
- Migrate the configuration file dse.ini to btt.xml. In BTT version 5.2, the entrance of the configuration file is dse.ini,
but in BTT version 7.0, it is renamed as btt.xml. See the following
figure.
Figure 1. Migrating the configuration
file
- Migrate the definition files of global definition files
and self defined operation and processor.
- Migrate the business logic. BTT version 7.0
uses process, operation, and operation step as channel aware business
logic, which is similar with BTT version 5.2. In BTT version 7.0,
the architecture is refined, and some components are re-designed,
so the package names, class names, and some APIs in BTT version 7.0
are different from those in BTT version 5.2. The migration tool will
automatically migrate these differences.
- Manually migrate the components that cannot be completely
migrated by the migration tool.