IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from other products > Migrating from WebSphere MQ Workflow
Limitations of the migration process (from WebSphere MQ Workflow)
There are certain limitations involved with the WebSphere MQ Workflow migration process.
- The migration of FDL will generate invoke activities for UPES activities and the corresponding WSDLs. However, the runtime environment significantly differs between IBM WebSphere MQ Workflow and IBM BPM in terms of the techniques used to correlate invocation messages and their responses.
- The runtime engines of IBM WebSphere MQ Workflow and IBM Process Server handle uninitialized data differently. While in IBM WebSphere MQ Workflow this did not cause errors, IBM BPM handles this situation with an exception and stops executing the process. To run migrated applications correctly in IBM BPM, ensure that all variables and sub-structures are initialized before they are used with Assign, Invoke, Staff, and Reply activities.
:
Migrating to IBM Integration Designer from WebSphere MQ Workflow