In the direct mode migration, you can change old application code,
including definition XML files, JSP files, and reference libraries,
to comply with the BTT version 7.0.x specifications. You can use the
migration tool to
accelerate the migration process. The direct mode is most applicable
when you want to do one of the following:
- Reconsider your architecture design, for example, changing transaction
management control from branch to headquarter.
- Build new solution features provided by BTT 7.0:
- Next Generation Internet Banking based on Web 2.0
- Integrated desktop solution based on Rich Client technology
- Mobile Banking solution
The following chart shows the direct mode migration:
The process for direct mode migration is as follows:
- Analyze the architecture, design and extensions of your
application. Define the target architecture and identify the manual
migration work.
- Use the migration
tool to upgrade the BTT definition files, JSP files, reference
libraries and application code.
- Implement manual work identified in step
1.
Note: For Swing Desktop to BTT Rich Client migration, refer
to the migration guides.
- Perform function verification test and system verification test.
The advantages of the direct mode migration are:
- Keep in line with BTT Product Strategy and IBM front office strategy
- New BTT features supported such as Web2.0 and Rich Client
- New BTT Business Components supported such as override, access
control
- Migration Tool supported
The disadvantages of the direct mode migration are:
- Client Application code need change from SWING to SWT