Migrating a Java service

You can migrate a Java service to an SCA Java Component.

About this task

In WebSphere® Studio Application Developer Integration Edition when generating a new Java™ service from an existing Java class, the following options were given:
  • Create XSD schemas for complex data types:
    • Within the interface WSDL file
    • As a new file for each data type
  • Support error handling capability:
    • Generate fault
    • Do not generate fault
  • Other details about the service to generate such as binding and service names

There are many new components that offer new functionality such as data mapping, interface mediation, business state machines, selectors, business rules, and more. First you should determine whether one of these new component types can replace the custom Java component. If that is not possible, follow the migration path described below.

Using the Migration wizard results in the creation of a business integration module with the WSDL Messages, PortTypes, Bindings, and Services generated in WebSphere Studio Application Developer Integration Edition.

In the Business Integration perspective, expand the module to see its contents. Open the Assembly Editor by double-clicking the first item under the module project (it will have the same name as the project).

Note: If the Migration wizard did not fully migrate all of your service projects, you have the following options: