IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from other products > Migrating from WebSphere InterChange Server or WebSphere Business Integration Server Express

Premigration considerations

Consider these guidelines for the development of integration artifacts for WebSphere InterChange Server or WebSphere Business Integration Server Express to ease the migration of WebSphere InterChange Server or WebSphere Business Integration Server Express artifacts to IBM BPM.

These recommendations are meant to be used only as a guide. There may be cases where it is necessary to deviate from these guidelines. In these cases, care should be taken to limit the scope of the deviation to minimize the amount of rework required to migrate the artifacts. If that the guidelines outlined here are not all general recommendations for the development of WebSphere InterChange Server or WebSphere Business Integration Server Express artifacts. They are instead limited in scope to those considerations that may affect the ease in which artifacts can be migrated at a future time.

• Premigration considerations: Access framework clients
  

  Do not develop any new clients using the CORBA IDL interface APIs. This is not supported in IBM BPM.

• Premigration considerations: Business objects
  For the development of business objects, use only the tools provided to configure artifacts, use explicit data types and lengths for data attributes, and use only the documented APIs.
• Premigration considerations: Collaboration templates
  When developing WebSphere InterChange Server or WebSphere Business Integration Server Express collaboration templates, follow these guidelines to ensure the best chance of a smooth migration to IBM BPM.
• Premigration considerations: Common code utilities
  IBM recommends that you avoid the development of common code utility libraries for use across integration artifacts within the WebSphere InterChange Server or WebSphere Business Integration Server Express environment. Consider using EJBs running in WebSphere Application Server to encapsulate the logic, and use web service calls to invoke them from WebSphere InterChange Server or WebSphere Business Integration Server Express.
• Premigration considerations: Database connection pools
  A WebSphere InterChange Server or WebSphere Business Integration Server Express database connection pool within a map or collaboration template will be rendered as a standard JDBC resource in IBM BPM. However, the way connections and transactions are managed might differ between WebSphere InterChange Server or WebSphere Business Integration Server Express and IBM BPM, so you should avoid keeping database transactions active across Java™ snippets.
• Premigration considerations: General development
  Follow these recommended practices when developing WebSphere InterChange Server or WebSphere Business Integration Server Express modules to ease future migration to IBM BPM.
• Premigration considerations: Maps
  When developing WebSphere InterChange Server or WebSphere Business Integration Server Express maps, follow these guidelines to ensure the best chance of a smooth migration to IBM BPM.
• Premigration considerations: Reverse maps on connectors
  Determine whether applications with response flows have reverse maps associated with their outbound connectors. If they do not, then a generic SMO is returned in the response.
• Premigration considerations: Preventing database collisions
  Prevent database collisions from occurring by scheduling events to occur at least two seconds apart.
• Premigration considerations: Relationships
  While relationship definitions can be migrated for use in IBM BPM, the relationship table schema and instance data may be reused by IBM BPM, and shared concurrently between WebSphere InterChange Server or WebSphere Business Integration Server Express and IBM BPM.

: Migrating from WebSphere InterChange Server or WebSphere Business Integration Server Express