The migration tool provided by Branch Transformation Toolkit version 5.2
helps users of earlier versions move up to the full power and versatility
of the IBM® WebSphere® Application
Server and IBM WebSphere Process
server. It provides the migration path to allow an enterprise to reuse much
of its existing toolkit application code base and still take advantage of
the WebSphere J2EE
environment.
IBM recognizes that an enterprise cannot always upgrade its application
software all at once. Because the enterprise can decide how much or how little
toolkit functionality to retain, version 5.2 allows the enterprise to upgrade
to a full J2EE environment incrementally. If desired, with version 5.2, the
enterprise can bypass toolkit functionality entirely and access J2EE components
directly.
This tool is to migrate BTT 5.1 definition to BTT 5.2 base definition.
It generates the corresponding program codes and the BTT version 5.2 tooling
artifact. There are two ways for the migration:
- Single Migration: You can migrate the BTT 5.1 components one by one manually
by using the migration tool. The migration tool will migrate the entities
to BTT 5.2 such as dse.ini, data model, formatter, server operations, screen
flow, process flow, and generate the artifacts for the tools of BTT 5.2 such
as Graphical Builder, BPEL and Struts.
- Batch Migration: You can migrate a batch of components automatically using
your own migration application. The batch migration application will migrate
the entities and generate the related tooling artifacts. The process can only
run on RAD and WID.
It provides you interfaces to help you migrate the BTT 5.1 application
to BTT 5.2 one by one. It can also provide the capability for you to build
your own batch migration application by using a set of definition files. Furthermore,
the migration tool can delegate the migration process to the plug-in custom
code to perform the customer unique extension.
This migration guide describes the migration considerations when you migration
to version 5.2 and the migration tools that help you roll out the migrations.
Note that the descriptions do not present all of the possible architecture
variations available in each version.