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

After a successful migration, you may still want to review the following sections to identify tasks that are required to complete the migration of your workspace. The information in this section can be used to help ensure that the migration was complete.

1. Open IBM Integration Designer and switch to the Business Integration perspective. You should see the module(s) that were created by the Migration wizard (one module for each service project that was migrated). The first artifact listed under the project is the module's assembly file (it has the same name as the module).
2. Double-click the assembly file to open it in the Assembly Editor where SCA components can be created and wired together to obtain similar functionality to the Version 5.1 application. If there were any BPEL processes in the WebSphere Studio Application Developer Integration Edition workspace, the migration wizard should have created default SCA components for each of those processes and they will be in the Assembly Editor.

3. Select a component and go to the Properties view where the Description, Details, and Implementation properties will be displayed and can be edited.

Some projects may require some rewiring after migration in order to reconnect the services the way they were in 5.1. The following information further describes how to manually rewire the application using the tools available in IBM Integration Designer.

• 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.
• 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.
• Migrating to the SCA programming model
  For any free-form Java™ code that interacts with a WebSphere Studio Application Developer Integration Edition service, this section shows how to migrate from the WSIF programming model to the new SCA programming model where the data flowing through the application is stored in Eclipse Service Data Objects (SDOs). This section also shows you how to migrate manually the most common client types to the new programming model.
• Manually deleting 5.1 web Services Invocation Framework (WSIF) definitions
  After you have completed migrating your source artifacts, you should delete all 5.1 WSIF Binding and Service WSDL definitions from your 6. x and 7.x projects that are no longer being used. The consumption scenario for service migration is the only case where a WSIF Binding or Service would still be in use.

: Migrating from WebSphere Studio Application Developer Integration Edition