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 exports to access the migrated service

An SCA export must be created to make the migrated service available to external consumers according to the SCA model for all services that deployment code was generated for in the WebSphere Studio Application Developer Integration Edition service project. This includes all services invoked by clients external to the application. If : The migration wizard creates the exports automatically, however, you can refer to the following information to help verify what the tool did.

If from WebSphere Studio Application Developer Integration Edition you right-clicked the BPEL process or other Service WSDL and selected Enterprise Services > Generate Deploy Code , you must perform the manual migration steps below. If that IBM Integration Designer is different from WebSphere Studio Application Developer Integration Edition in that it stores all of the deployment options. When the project is built, the deployment code is automatically updated in the generated EJB and web projects, so there is no longer an option to manually Generate Deploy Code.

Five binding options were given under the Interfaces for Partners section of the Generate BPEL Deploy Code wizard. The following inbound BPEL service migration information provides more details on the Export type and properties to create based on the deployment binding type(s) that were selected in WebSphere Studio Application Developer Integration Edition:

• EJB
• IBM Web Service (SOAP/JMS)
• IBM web service (SOAP/HTTP)

• Apache web service (SOAP/HTTP)
• JMS

• Migrating the EJB and the EJB process bindings
  The EJB and EJB process bindings can be migrated to the recommended SCA construct.
• Migrating the JMS and the JMS process bindings
  The JMS and JMS process bindings can be migrated to the recommended SCA construct.
• Migrating the IBM Web Service binding (SOAP/JMS)
  The IBM Web Service binding (SOAP/JMS) for a BPEL process or other service type can be migrated to the recommended SCA construct.
• Migrating the IBM Web Service binding (SOAP/HTTP)
  The IBM Web Service binding (SOAP/HTTP) for a BPEL process or other service type can be migrated to the recommended SCA construct.
• Migrating the Apache web service binding (SOAP/HTTP)
  The Apache web service binding (SOAP/HTTP) for a BPEL process or other service type can be migrated to the recommended SCA construct.

: Additional migration information