In phase 1, you must analyze the differences between IBM® WebSphere® Multichannel Bank
Transformation Toolkit version 5.2 and WebSphere Multichannel
Bank Transformation Toolkit version 7.1. Particular
attention must be paid to the application logic layer.
About this task
You must identify the parts of
WebSphere Multichannel
Bank Transformation Toolkit version
5.2 that
can be migrated automatically and the parts that cannot be migrated
automatically, and then make necessary preparation for the migration.
Procedure
To prepare for the migration, perform the following tasks:
- Gather the definition files of the existing application
system version 5.2.
Mark your extensions for future verification.
- Prepare your application code and JSP sources. The migration
tool migrates the Java code
of the application to WebSphere Multichannel
Bank Transformation Toolkit version 7.1.
- Prepare to manually migrate the WebSphere Multichannel
Bank Transformation Toolkit version 5.2 invoker.
WebSphere Multichannel
Bank Transformation Toolkit version 5.2 uses
the invoker framework to invoke the business logic. WebSphere Multichannel
Bank Transformation Toolkit version 5.2 leverages
EJB as the business logic implementation. The invoker of WebSphere Multichannel
Bank Transformation Toolkit version 5.2 is
mainly used for EJB calling from the WebSphere Multichannel
Bank Transformation Toolkit runtime
server. In WebSphere Multichannel
Bank Transformation Toolkit version 7.1, the
request from the channel side will directly call the WebSphere Multichannel
Bank Transformation Toolkit processor
or operation in the WebSphere Multichannel
Bank Transformation Toolkit runtime
container.
- WebSphere Multichannel
Bank Transformation Toolkit version 7.1 provides
more powerful context, and the API usage is different from that in WebSphere Multichannel
Bank Transformation Toolkit version 5.2.
The migration tool of WebSphere Multichannel
Bank Transformation Toolkit version 7.1 can
help you migrate the context and APIs.
- Verify version 5.2 services.
The supported services of WebSphere Multichannel
Bank Transformation Toolkit version 7.1 on
the server side support all of the WebSphere Multichannel
Bank Transformation Toolkit version 5.2 services.
The migration tool helps to migrate the package names, class names,
APIs, and so on. If you have customized services, you can customize
the migration rule to meet your migration requirements.
- Verify your event usage. The event mechanism has been changed
to fit the version 7.1 framework
so that it can be distributed, and it spans different servers. The
event mechanism of version 7.1 is
also compatible with the standard usage of version 5.2.
You must perform some manual migration to run the WebSphere Multichannel
Bank Transformation Toolkit version 5.2 events
in WebSphere Multichannel
Bank Transformation Toolkit version 7.1 if
you had special usages.
- Verify your client type. There are two kinds of client
applications in WebSphere Multichannel
Bank Transformation Toolkit version 5.2.
There is no change to the Swing-based Javaclient, so
you do not need to migrate it to WebSphere Multichannel
Bank Transformation Toolkit version 7.1. For
JSP/HTML-based clients, the migration tool migrates JSP Tablib uri, WebSphere Multichannel
Bank Transformation Toolkit customized
tags, page import, and Java code in JSP
files.
- Migrate the WebSphere Multichannel
Bank Transformation Toolkit trace. WebSphere Multichannel
Bank Transformation Toolkit version 7.1 trace
is completely compatible with WebSphere Multichannel
Bank Transformation Toolkit version 5.2 trace.
If you do not want to use the new trace framework, the old trace can
still work in the WebSphere Multichannel
Bank Transformation Toolkit version 7.1 runtime
container.