During this phase, the project team can start to migrate the application
by using the migration tool. To do this, the project team needs to do the
following:
- Create a migration project by using the migration tool and import
the definition files from a specific EAR file, or specify the dse.ini file
in the disk. After the process finished, the migration tool will create the
related projects, like EAR project, Web project, EJB project and Services
Project if WebSphere(R) Studio
Application Developer Integration Edition adopted.
- Migrate dse.ini file.
- Migrate the definition files of the context, the data element,
the type data and the format.
- Migrate the business logic:
- Migrate the server operations to Single Action EJBs or business processes
if WebSphere Studio
Application Developer Integration Edition adopted. After you complete the
process, the migration tool will generate things like invoker (Java(TM) code),
and Single Action EJB or business process.
- Migrate the flow processes to business process if WebSphere Studio Application Developer
Integration Edition adopted. After you complete the process, the migration
tool will generate the things like BPEL file, invoker (Java code).
- Migrate the screen flow to Struts Extensions. After you complete the process,
the migration tool will generate things like struts configure file, web diagram
(.gph file) and migrated JSP.
- Migrate self-definition files if there are any. The output includes the
above 3 output files. Also, the definitions of the context, the data element,
the type data and the format in the self-definition files will be add into
the generic definition files.
Note: Business processes do not automatically chain process contexts
(equivalent to operation contexts and flow processor contexts in version4.3)
to session contexts. You need to chain the process contexts to session contexts
manually.
- Generate version 5.1 tooling artifact. The migration tool can generate
the artifact of Graphical Builder based on the generation of the screen flow.