In mixed mode migration, you can keep the Swing client code without
any changes and integrate it into BTT version 7.0 Rich Client framework
while upgrading the server side code through direct mode.
The following chart shows the mixed mode migration:
The migration process for mixed 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 mixed mode migration are:
- Keep In line with BTT product strategy and IBM® Front
Office strategy.
- New features, such as Web 2.0 and Rich Client are supported.
- New BTT Business Components, such as override, access control
are supported.
- Migration tool is supported.
- Less migration effort and cost.
The disadvantages of the mixed mode migration are:
- Mixed SWING and SWT application usage.