The migration tool cannot migrate everything from BTT
version 5.2 to BTT version 7.0 automatically. You must do some manual
migration, including:
- Some new features in BTT version 7.0, 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 7.0 and makes sure that they
can run in BTT version 7.0. You must re-design your applications and
implement them manually.
- The existing services that are out of the scope of BTT version
7.0. These services in BTT version 5.2 application system are not
included in the migration tool, so you need to migrate them manually.
- The server side event mechanism of BTT version 7.0 is changed.
You can define event related migration rules in BTT version 7.0, 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
7.0. You must modify it manually.
- The BTT version 5.2 invoker. Invoker is a hard coded EJB invocation
framework. BTT version 7.0 provides a common invocation framework
for POJO, EJB, Web Service, and JMS. These two frameworks are totally
different. The API usage and configuration are also totally different.
The EJB invocation information that is defined in the resource bundle
file can be mapped to the EJB invoker definition in the file invoker.xml.
BTT version 7.0 invoker is decoupled with BTT context and formatter.
The usage of BTT version 7.0 invoker is simple and flexible comparing
with the usage of BTT version 5.2 invoker. For detailed information
about BTT version 7.0 invoker, see Invoker.