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

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.

User-defined database connection pools are useful within maps and collaboration templates for simple data lookups and for more sophisticated state management across process instances. A database connection pool in WebSphere InterChange Server or WebSphere Business Integration Server Express will be rendered as a standard JDBC resource in IBM BPM, and the basic function will be the same. However, the way in which connections and transactions are managed may differ.

To maximize future portability, avoid keeping database transactions active across Java snippet nodes within a collaboration template or map.

For example, code related to obtaining a connection, beginning and ending a transaction, and releasing the connection should be in one code snippet. Failure to do this could result in a runtime error, because IBM BPM handles the transaction, whereas in WebSphere InterChange Server or WebSphere Business Integration Server Express it was managed explicitly.

: Premigration considerations