Migrating server operations

To migrate your 4.3 server operations to Single Action EJBs, or Business Processes, or server operations in 5.2, do the following:
  1. From the Package Explorer view of your WebSphere® Integration 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.
    Server operation migration window
  2. From the Server Operation Migration dialog box shown in the figure above, select the server operations.

    An invoker will also be generated for calling the Single Action EJB or business process or operation steps. From the Server Operation Migration dialog box, you can see the common information, and the name and type of the invoker, and the name of the Single Action EJB or Business Process or operation steps, and also the package where they locate

  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, or the business processes in the Process project of your application, or register information for operation steps. 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.

    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.