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 > Migrating to the SCA programming model > Migrating WebSphere Business Integration Server Foundation client code

Migrating the Business Process Choreographer web client

This topic shows how to migrate the 5.1 Business Process Choreographer web client settings and custom JSPs.

The Migration wizard preserves the 5.1 web client settings and you may not edit these settings in the Human Task editor. You should create new web client settings and JSPs using IBM Integration Designer.

Migrating web client modifications

In 5.1 you could modify the appearance of the Struts-based web client by modifying its JSP Header.jsp and style sheet dwc.css.

Because the web client (renamed to the Business Process Choreographer Explorer) is based on Java Server Faces (JSF) instead of Struts, automatic migration of web client modifications is not possible. Refer to the "Developing JSP pages for task and process messages" documentation for details on customizing the new version of this application.

User-defined JSPs could be defined for business processes and for staff activities.

The web client uses these JSPs to display input and output messages for the process and activities.

These JSPs are particularly useful when:

  1. Messages have non-primitive parts to enhance the usability of the message's data structure.

  2. You want to extend the web client's capabilities.

In version 6 and later releases, there are more and different options available when specifying web client settings for a process. Use IBM Integration Designer to redesign the web client settings for migrated processes and activities:

  1. Select the process canvas or an activity in the process.

  2. In the Properties view, select the Client tab to redesign the web client settings.
  3. Manually migrate any user-defined JSP:
    1. See the "Migrating to the SCA programming model" section for programming model changes.

    2. The web client uses the Generic APIs to interact with business processes. See the sections that show how to migrate calls to these generic APIs.

  4. Specify the name of the new JSP in the version 6 or later web client settings for the process.

In version 6 and later releases, mapping JSPs are not needed with the Business Process Choreographer Explorer because DataObjects do not need any custom mapping.

: Migrating WebSphere Business Integration Server Foundation client code