In Branch Transformation Toolkit version 5.2, screen flow processors
are re-based on the Apache Struts Framework. To migrate your version 4.3 screen
flows to the corresponding constructs in version 5.2, do the following:
- From the Package Explorer view of your WebSphere® Integration Developer, right-click
the your dseproc.xml file that contains your version 4.3 screen flow processors
, and select . This
starts the screen flow processor file migration wizard.
- From the Screen Flow Processor Migration dialog
box that opens, select the screen flow processors. From the Screen
Flow Processor Migration dialog box , you can see the common information,
like context, validation class, and Struts file name.
- Enter the JSP Source Directory, and select
the Invoker Type.
- Click Finish.
The migration of screen flow processors does the following for you:
- Convert the <htmlProcessor> tag to a Struts process definition file.
- Convert Actions to Struts Actions.
- Convert operation actions to business processes, defined in a BPEL file.
- Translate the navigation links into the Struts definition file. Transitions
are transformed into the forward definitions of Struts.
- Convert version 4.3 validation classes to version 5.2 validation classes.
- Convert condition definitions to the condition definitions of Struts Extensions.
- Convert processor contexts to the processor CHA contexts of Struts Extensions.
- Convert transition actions to two Struts actions.
- Convert transition contexts to transition CHA contexts and Form Beans
of Struts Extensions.
- For JSP files, change the next event to a URI.
After the screen flow migration process finishes, the result will
be placed in the web project. You can browse and edit the screen flow by the
Struts configuration file in an XML editor or the .gph file in a graphical
screen flow editor.