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
All migrated business processes must be wired to their business partners. An SCA Component or Import must be created for all other service types. For WebSphere Studio Application Developer Integration Edition service projects that interact with systems or entities external to the project, an SCA Import can be created in order for the migrated project to access those entities as services according to the SCA model.
The Migration wizard attempts to do this automatically, however, you can refer to the following information to help verify what the tool did.
For WebSphere Studio Application Developer Integration Edition service projects that interact with entities within the project (for example, a business process, transformer service or Java class), an SCA Import can be created in order for the migrated project to access those entities as services according to the SCA model.
The following sections provide details on the SCA Import or SCA Components to create based on the type of service that must be migrated:
Migrating a Java service
You can migrate a Java service to an SCA Java Component.
- Migrating an EJB service
You can migrate an EJB service to an SCA Import with stateless session bean binding.
- Migrating a business process to business process service invocation
This scenario applies to a business process that invokes another business process, where the second business process is invoked using a WSIF Process Binding. This section shows how to migrate a BPEL to BPEL service invocation using a wire or an Import/Export with SCA Binding if the Migration wizard did not fully migrate all of your service projects. - Migrating a web service (SOAP/JMS)
If the Migration wizard did not fully migrate all of your service projects, you can migrate a web service (SOAP/JMS) to an SCA import with web service binding.
- Migrating a web service (SOAP/HTTP)
If the Migration wizard did not fully migrate all of your service projects, you can migrate a web service (SOAP/HTTP) to an SCA import with web service binding.
- Migrating a JMS service
If the Migration wizard did not fully migrate all of your service projects, you can migrate a JMS service to an SCA Import with JMS binding.
- 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.
- Migrating a J2C-CICS ECI service
You can migrate a J2C-CICS ECI service to an SCA Import with EIS Binding or an SCA Import with Web Service Binding.
- Migrating a J2C-CICS EPI service
There is no direct support for the J2C-CICS EPI service in IBM Integration Designer. In order to access this service from an SCA module, you will need to migrate using the consumption scenario. - Migrating a J2C-HOD service
There is no direct support for the J2C-HOD service in IBM Integration Designer. In order to access this service from an SCA module, you will need to migrate using the consumption scenario. - Migrating a transformer service
You can migrate a transformer service to an SCA Data Map and Interface Map where possible. You can also use the consumption scenario to access this service from an SCA module.
- The consumption scenario for service migration
If there is no direct counterpart for a WebSphere Studio Application Developer Integration Edition service type, a consumption scenario is needed to consume the old WebSphere Studio Application Developer Integration Edition service as-is when redesigning the application in IBM Integration Designer.