Migrating server operations

In Branch Transformation Toolkit version 5.1, server operations are replaced by Single Action EJBs or business processes called by invokers.

To migrate your non-step server operations to Single Action EJBs or business processes and generate the associated invokers, do the following:

  1. From the Package Explorer view of your WebSphere(R) Studio Application Developer, right-click the your version 4.3 dseoper.xml file, and select BTT Migration > Server Operation Migration. This starts the server operation file migration wizard.
  2. From the Server Operation Migration dialog box that opens, select the server operations, and select if you want the non-step server operations to be migrated to Java(TM) 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, the name of the Single Action EJB or business process, and the package where the Single Action EJB and business process locates.
    Note: The selection of Java snippets for business processes or Single Action EJBs will affect all of the non-step server operations that list in the server operation file migration wizard. If you want to have one set of the server operations that are migrated to Single Action EJB and another set that are not , you must create two migration projects for each set.
  3. Click Finish. You can then see the generated invoker and its properties files in the Web project of your application, the Single Action EJBs in the EJB project of your application, and the business processes in the Process project of your application. The entry properties file is also upgraded in the application projects.
    Note: The entry properties file is a kind of index or an invoker registry to map an invoker ID to an invoker properties file.
Stepped operations in toolkit version 4.3 can only be migrated to business processes. To migrate your stepped server operations to business processes and generate the associated invokers, do the following:
  1. From the Package Explorer view of your WebSphere Studio Application Developer, right-click the your version 4.3 dseoper.xml file, and select BTT Migration > Server Operation Migration. This starts the server operation file migration wizard.
  2. From the Server Operation Migration dialog box that opens, 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 locates.
  3. Click Finish. You can then see the generated invoker and its properties files in the Web project of your application, and the business processes in the Process project of your application. The entry properties file is also upgraded in the application projects.

The operation steps are migrated to Java snippets for business processes. Links between the Java snippets are generally automatically based on the server operation definition files.

If the operation contains sub-operations, the stepped sub-operations will be migrated to business processes with associated invokers generated,, and the non-step sub-operations can be migrated to Java snippets of the BaseOperSnippet type.