106 IBM Branch Transformation Toolkit 5.1 Migration and Usage Guidelines
5.2.3 Migrating server operations
In Branch Transformation Toolkit version 5.1, server operations are replaced by
either Single Action EJBs or business processes called by invokers.
To migrate the nonstep server operations to Single Action EJBs or business
processes, and generate the associated invokers, perform the following tasks:
1. In the 4.3 Definitions folder, right-click dseoper.xml and select BTT
Migration Server Operation Migration. This starts the server operation
file migration wizard.
2. From the Server Operation Migration dialog box, select the server operations,
and decide if you want the nonstep server operations to be migrated to Java
snippets for business processes or Single Action EJBs. An invoker will also be
generated for calling the Single Action EJB or business process. From the
Server Operation Migration dialog box, you can see the name of the invoker,
Chapter 5. Migrating an application 107
the name of the Single Action EJB or business process, and the package
where the Single Action EJB and business process locates.
For this sample, migrate all the non-step operations to the default Single
Action EJB, in the pop-up window in Figure 5-7. For the Invoker Type, select
both.
Note: The selection of Java snippets for business processes or Single
Action EJBs affects all the nonstep server operations that are listed in the
server operation file migration wizard. To have one set of server operations
migrated to Single Action EJB and another set that is not, create two
migration projects for each set.
108 IBM Branch Transformation Toolkit 5.1 Migration and Usage Guidelines
Figure 5-7 Server Operation Migration
3. Click Finish. You can see the generated invoker and its properties files in the
Web project of the application, the Single Action EJBs in the EJB project of
the application, and the business processes in the Process project of the
application. The entry properties file is also upgraded in the application
projects.
Stepped operations in toolkit version 4.3 can only be migrated to business
processes. To migrate the stepped server operations to business processes and
generate the associated invokers, perform the following tasks:
1. From the Server Operation Migration dialog box, select the server operations.
You can see the name of the invoker, the name of the Single Action EJB or
business process, and the package where the Single Action EJB and
business process are located.
2. Click Finish. You can see the generated invoker and its properties files in the
Web project of the application, and the business processes in the process
project of the application. The entry properties file is also upgraded in the
application projects.
The operation steps are migrated to Java snippets for business processes.
Generally, links between the Java snippets are automatically based on the
server operation definition files.
If the operation contains suboperations, the stepped suboperations will be
migrated to business processes with associated invokers generated, and the
nonstep suboperations migrated to Java snippets of the BaseOperSnippet type.
To customize the nonstep operation migration option, select the operation in the
Server Operation list in the left side of the panel, and then select Single Action
EJB or Business Process in the right side of the panel. In the same way, you
can select another operation in the list and choose the migration target option in
the left.
Note: The entry properties file is a kind of index or invoker registry to map
an invoker ID to an invoker properties file.
Note: The migration tool automatically migrates Server Operation, which has
steps to BPEL process. Tools allow users to migrate Nonstep Server
Operation to SAE or BP. In default, it will be migrated to SAE.

Get IBM Branch Transformation Toolkit 5.1 Migration and Usage Guidelines now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.