The direct mode of migration is suitable for most customers.
The direct mode of migration involves changing application code, including
definition XML files, JSP files, and reference libraries, to comply
with the IBM® WebSphere® Multichannel Bank
Transformation Toolkit version 7.1 specifications.
You can use the migration
tool to accelerate the migration process.
The direct mode is suitable when you want to do one of the following
tasks:
- Reconsider your architecture design, for example, changing transaction
management control from branch to headquarter.
- Build new solution features provided by WebSphere Multichannel
Bank Transformation Toolkit version 7.1:
- Next generation Internet banking based on Web 2.0
- Integrated desktop solution based on Rich Client technology
- Mobile banking solution
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 WebSphere Multichannel
Bank Transformation Toolkit definition
files, JSP files, reference libraries and application code.
- Implement manual work identified in step
1.
Note: For Swing Desktop to WebSphere Multichannel
Bank Transformation Toolkit Rich
Client migration, refer to the migration guides.
- Perform function verification test and system verification test.
The advantages of the direct mode migration are:
- Alignment with WebSphere Multichannel
Bank Transformation Toolkit product
strategy and IBM front
office strategy.
- Migration tool support.
The disadvantages of the direct mode migration are:
- Client application code must be changes from Swing to SWT.