IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from previous versions > Migrating your IBM BPM Advanced V7.5.x or WebSphere Process Server V7.x or V6.2.x runtime > Plan the runtime migration
Advanced: Known compatibility issues
The following items are known compatibility issues when migrating to IBM BPM Advanced V8.0.1.
SCA transaction behavior
If you are using a CICS adapter and have a setup of SCA component (transaction = 'global') -> import (join transaction = 'false') -> CICS adapter, the CICS adapter might produce a transaction abort error, because the default transaction behavior of the SCA container is to start a new transaction at the import. To change the default behavior of the SCA container, create a new WebSphere variable SCA_TRANSACTION_ON_IMPORT and set its value to CICS. With this setting, SCA will not start a new transaction at the import. If the variable is missing, or if its value is other than CICS (for example, default), the SCA container will default to guaranteeing a transaction flow into the adapter.
Important:
- Once you have created or changed the value of the WebSphere variable, you must restart the BPM server so that the runtime engine will pick up the new value.
- It is easiest to create the WebSphere variable at cell scope, so that it will be applied to all the servers of the cell, but you could also create it with a different scope, so that different servers in the cell could have different behavior.
- You can check the SCA transaction setting in IBM Integration Designer. Select SCA module project > Assembly diagram and then click component or import. Click properties and check All qualifiers.