Oracle BPM 10g to 12c Migration - Quick Note

Migration path for Oracle BPM 10g projects to 12c has been introduced in Oracle BPM Suite 12c (12.1.3) bu Oracle which was not available in 11g and there was little to no support for BPM 10g projects to be migrated to Oracle BPM 11g version.
Below is the high level steps to follow to migrate Oracle BPM 10g project to 12c migration -

1) execute ant based migration script
Once the ANT task execution completes successfully, it creates the Oracle BPM 12c project export in the target folder which contains following -
• The exported version of the 12c project (.exp).
• The migration report (.xml) and its stylesheet (.xsl). Best when viewed via a browser.
• The 10g project artifacts list (.csv).
• The folder with 12c project SOA components.

2) Import the 12c project into JDeveloper
Create a BPM Application and Import BPM Project created by migration script. The table below enlists the 10g artifacts and its corresponding 12c artifacts –

Oracle BPM 10g project artifacts Oracle BPM 12c project artifacts
Organization Organization
Process Process
Screenflow Synchronous Process
Process and Screenflow Begin/End Process Begin/End
Swim Lanes Role Lanes
Argument Mappings Data Associations
Transitions Sequence Flows
Conditional Transitions Exclusive Gateways
Global Creation Interactive Initiator
Process Instance Variable Process Data Object
Automatics Script Activity
FBL code Groovy code

The above list is not exhaustive, but enlists the major components. It should be noted that 10g and 12c is very different and not all 10g project artifacts can be migrated to 12c project artifacts by the script, such as -
• Groups and Participants in Organization
• Web Resources which includes JSP, CSS, JS files what uses Fuego Tag Libs
• Process Global Interactive
• Out-of-the-box Modules (Fuego and Plumtree) and some developer created Modules.
• BPM Object - Group type.
• BPM Object - Presentations.
• Predefined Variables, for example result, action, description etc.

The above mentioned features needs to be built from scratch in the 12c project.

The magnitude of effort depends on the features used in the 10g project implementation. If the 10g project uses none or minimum features that cannot be migrated by script, the overall project migration would require relatedly less time and effort.