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

Migrating workspaces using the IBM Integration Designer Migration wizard

The IBM Integration Designer Migration wizard enables the migration of workspaces, including all projects.

Before you migrate the source artifacts, review the information in Migrating a process instance, Migrating XML maps, Migrating generated Java EE staging projects, and Migrating server runtime targets.

Specifically for the migration of service projects, the Migration wizard does the following tasks:

  1. Creates a new business integration module (the module name is defined by you)
  2. Migrates the service project's classpath entries to the new module
  3. Copies all WebSphere Business Integration Server Foundation source artifacts from the selected source project to this module
  4. Migrates the BPEL extensions in WSDL files
  5. Migrates the business processes (.bpel files) from BPEL4WS version 1.1 to the new level supported by IBM BPM, which is built on BPEL4WS version 1.1 with major capabilities of the upcoming WS-BPEL version 2.0 specification

  6. Creates an SCA component for each BPEL process
  7. Generates a monitoring .mon file for each BPEL process to preserve the default monitoring behavior from WebSphere Studio Application Developer Integration Edition (if necessary)

  8. Creates imports and exports depending on the deploy options chosen in WebSphere Studio Application Developer Integration Edition
  9. Wires the BPEL component to its partner links (imports, exports, and Java components)

Use a new IBM Integration Designer workspace as the migration target. To migrate workspaces using the IBM Integration Designer Migration wizard, follow these steps:


Procedure

  1. Invoke the wizard by selecting File > Import > Business Integration > WebSphere Studio Application Developer Integration Edition Workspace and click Next.

  2. The Migration wizard opens. Enter the path for the workspace to migrate or click Browse to find it. Click Next.

  3. From the migration options page, you can change the option to preserve the original BPEL Java snippets in the comments.

  4. Click Finish to begin the migration process. You will see a migration status bar at the bottom of the Migration wizard's window.

  5. Once the process has completed, you will see the Rational Desktop Migration message appear. Click Next in the message to begin the migration validation process.

  6. Select the workspace projects to migrate. Click Next.

  7. The project resources which may be impacted by the migration process are listed. Review this list and click Next.

  8. Once you are ready, click Finish to begin migrating the projects that you have selected.

  9. Once the migration validation process has completed, you should see a message.

  10. After the process has completed, the Migration Results window opens. A log file containing these migration messages will automatically get generated to the 6. x workspace's .metadata folder. The log file will have a .log extension.

  11. To keep all messages for future reference, click the Generate ToDo's button to create a list of "ToDo" tasks in the task view or click the Save as... button to save the messages in a text file in the file system. Examine each message to see if any action needs to be taken to immediately fix an artifact that couldn't be fully migrated. To see the generated To Do's, click Window > Show View > Other > General > Tasks and click OK. The Tasks view opens with the list of generated To Do's from the migration process.


What to do next

After the Migration wizard has completed, build the workspace that was created and try to resolve any build errors. Inspect all migrated BPEL files and ensure that they are fully migrated and can be opened in the IBM Integration Designer BPEL Editor. There are some BPEL Java™ snippets that cannot be automatically migrated. If you see any errors in the BPEL Java snippets, see "Migrating to the SCA Programming Model" for steps needed to fix the errors. Also, if you used the Migration wizard to migrate a service project to a workspace, open the dependency editor to ensure that the dependencies are set correctly. To do this, switch to the Business Integration perspective, expand the business integration module project, and double-click Dependencies. From the Dependencies editor you can add dependencies on business integration library projects, Java projects, and Java EE projects.

: Migrating your workspace