IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from other products > Migrating from WebSphere Studio Application Developer Integration Edition > Additional migration information > Create SCA Components and SCA Imports for the services in the application for rewiring > Migrating a Java service
Advantages and disadvantages for each of the Java service rewiring options
If the migration wizard did not fully migrate all of your service projects and you have opted to do so manually, note that there are advantages and disadvantages for each of the Java service rewiring options.
The following list describes both options and the advantages and disadvantages of each:
- The first option is likely to give better performance at run time, because invoking a web service is slower than invoking a Java component.
- The first option can propagate context, whereas a web service invocation does not propagate context in the same way.
- The second option does not involve creating any custom code.
- The second option might not be possible for some Java interface definitions, because generating a Java service has limitations. See
the Rational Application Developer documentation here:
Limitations of web services
- The second option might result in an interface change and therefore a change to the SCA consumer.
- The second option requires that an IBM BPM server is installed and has been configured to work with IBM Integration Designer. To see the installed runtime environments that are configured to work with IBM Integration Designer, go to Window > Preferences > Server > Installed Runtimes and select the IBM BPM entry if it exists and ensure that it points to the location where the product is installed. Ensure that this entry is checked if the server does exist and cleared if this server is not actually installed. You can also click Add… to add another server.
- If the Java component was built in WebSphere Studio Application Developer Integration Edition using the top-down approach where the Java skeleton was generated from a WSDL, the parameters in and out of this Java class will probably subclass WSIFFormatPartImpl. If this is the case, choose option 1 to generate a new SCA style Java skeleton from the original WSDL/XSDs or option 2 to generate a new generic Java skeleton (not dependent on the WSIF or DataObject APIs) from the original WSDL interface.
