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 J2C-IMS service

If the Migration wizard did not fully migrate all of your service projects, you can migrate a J2C-IMS service to an SCA Import with EIS Binding or an SCA Import with Web Service Binding.

Do not use any of the WebSphere Studio Application Developer Integration Edition artifacts that were generated for this IMS service.

You will need to create the service using the wizards available in IBM Integration Designer and manually rewire the application.

Turn Auto-Build on or build the module manually.

You have the following options:

For both options, note that if a BPEL service invokes this IMS service, the BPEL will need to change slightly, because the interface exposed by the EIS service will be slightly different from the old 5.1 interface. To do this, open the BPEL editor and adjust the partner link that corresponds to the EIS service. Use the new interface (WSDL file) generated when performing these steps. Make any necessary changes to the BPEL activities for the new WSDL interface of the EIS service.

• Create an SCA Import to invoke the IMS service: option 1
  

  You can create an SCA Import with EIS Binding that will use DataObjects to store the message/data to communicate with the IMS system.

• Create a web service around the J2C service: option 2
  

  You can create a J2C web service and if the consumer of the service is an SCA component, consume the service as an IBM Web Service (SOAP/HTTP or SOAP/JMS).

• Advantages and disadvantages for each of the J2C-IMS service rewiring options
  There are advantages and disadvantages for each of the J2C-IMS service rewiring options.

: Create SCA Components and SCA Imports for the services in the application for rewiring