The migration tool cannot migrate everything from BTT version
4.3 to BTT version 6.1.2 automatically. You must do some manual migration, including:
- Some new features in BTT version 6.1.2, such as Web 2.0, Rich Client, and
so on. The base functionality of the migration tool only migrates the existing
applications to BTT version 6.1.2 and makes sure that they can run in BTT version
6.1.2. The new features in BTT version 6.1.2 are not migrated by the migration
tool, so you must re-design the applications and implement them manually.
- The existing services that are out of the scope of BTT version 6.1.2. These
services in BTT version 4.3 application system are not included in the migration
tool, so you need to migrate them manually.
- The server side event mechanism of BTT version 6.1.2 is changed. You can
define event related migration rules in BTT version 6.1.2, but for some complicated
cases that migration rules cannot handle, you must migrate them manually.
- The communication service access uses JCA connector in BTT version 6.1.2.
You must modify it manually.