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 > Migrating your workspace

Preparing source artifacts for migration

Before migrating source artifacts to IBM Integration Designer from WebSphere Studio Application Developer Integration Edition, ensure that you have properly prepared your environment for the migration process.

The following steps describe how to prepare your environment before migrating source artifacts to IBM Integration Designer from WebSphere Studio Application Developer Integration Edition:

1. Ensure that you have a backup copy of the entire 5.1 workspace before attempting to migrate.
2. Review the web service section of the Rational Application Developer Information Center for background information on the web service functionality provided by Rational Application Developer: Developing Web services
3. Ensure that you have all of the appropriate IBM Integration Designer features enabled. If you do not have these features enabled, the menu options that will be discussed in the following section may not be visible. To enable the important features:

   • In IBM Integration Designer, select Window > Preferences.

   • Click General and select the Capabilities category.

   • Select all features under the following categories:

     • Enterprise Java Developer

     • Integration Designer
     • Java Developer

     • Web Developer (typical)

     • Web Service Developer
     • XML Developer

   • Click OK.

4. Use a new workspace as the migration target workspace.
5. By default, IBM Integration Designer generates the deploy code during build time for the supporting WEB, EJB and EAR projects for IBM Integration Designer modules.

   The deploy code for other projects (for example, Java EE) is not generated.

6. In order to fully migrate the BPEL files within a workspace, ensure that all WSDL and XSD files that are referenced by the BPEL files can be resolved in a business integration project in the new workspace:

   • If the WSDL or XSD files are in the current project, a referenced project, or a common library with the BPEL file, no further action is required.

   • If the WSDL or XSD files are in a different project from the one you are migrating, the 5.1 artifacts must be reorganized using WebSphere Studio Application Developer Integration Edition before migration, because Business Integration (BI) module projects cannot share artifacts. There are two options for reorganizing the 5.1 artifacts:

     • In WebSphere Studio Application Developer Integration Edition, create a new Java project that will hold all the common artifacts. Place all WSDL and XSD files that are shared by more than one project into this new Java project. Add a dependency on this new Java project to all projects that use these common artifacts.
     • Keep a local copy of these shared WSDL and XSD artifacts in each project such that there are no dependencies between projects.

   • If the WSDL or XSD files are in any other type of project (often other Java™ Projects), create a Business Integration library project with the same name as the 5.1 project. You should also set up the class path for the new library project, adding the entries from the 5.1 Java project, if any. This type of project is useful for storing shared artifacts. If that two WSDL files cannot define portType, service, or port with the same name and target namespace. This should be fixed manually before migration to avoid errors.

IBM Integration Designer does not support XML-SOAP types as defined in the http://xml.apache.org/xml-soap namespace. Remove references to these types in WebSphere Studio Application Developer Integration Edition before migrating, to avoid a migration process failure.

What to do next

You are now ready to begin the migration process.

: Migrating your workspace