This chapter includes the following sections:
The BPM migration utility migrates BPM project artifacts using the mapping described in the following table:
Table 4-1 Project Artifact Mapping
| 10gr3 Artifact | 12c Artifact |
|---|---|
|
Project Properties |
Only configured languages migrated. |
|
Languages |
Migrated to the Languages preference in Project Preferences. |
|
Current languages |
Migrated to the Current Language preference in Project Preferences |
|
Project Variables |
Project data objects |
|
Business Indicators |
Business indicators |
|
Process Variables |
Process data objects |
|
Process Properties |
Migrates the Generate Events and Author properties. |
|
Procedures |
BPMN process |
|
Documentation |
Migrates i18n process documentation. Images, font type, font style (bold, italic, underline, etc) and font color are not migrated. |
|
Organization |
Migrates roles used in the BPMN processes. |
|
Lanes |
Lanes |
|
Layout |
Migration not supported. BPM 12c uses an automatic layout. |
|
Simulation Models |
Migration not supported. |
|
Presentations |
Not migrated |
|
Project Dependency |
Project dependencies and base project properties are not migrated. The catalog and roles migration supports project dependency. To use this functionality, you must copy the base project to the same directory in which the dependent project is stored. |
The BPM migration utility migrates the BPM process activities using the mapping described in the following sections:
For more information on the limitations and known issues when migrating BPM activities, see BPM Activities Migration Known Issues.
The BPM migration utility uses the following mappings to migrate events from BPM 10gr3 processes to BPM 12c processes:
Table 4-2 BPM 10gr3 Activity to BPM 12c Events Mapping
| 10gr3 Artifact | 12c Artifact |
|---|---|
|
Begin |
Start message catch event.If the begin event contains multiple argument sets, they are migrated to multiple BPMN message start events, one for each argument set. For more information, see Argument and Argument Mapping Migration. |
|
End |
End event. For information about argument and argument mapping migration, see Argument and Argument Mapping Migration. |
|
Boundary events |
Only activities support boundary events. The boundary events in artifacts that are migrated as BPMN events, are not migrated. |
|
Message wait that allows interruptions |
Event subprocess with a message start event. In some cases, notification wait events that allow interruptions may not have a mapping. If the notification wait has more than one outbound transition it is mapped to multiple event subprocesses. |
|
Message wait that does not allow interruptions |
Catch message event. In some cases, notification wait events that do not allow interruptions may not have a mapping. If the notification wait has multiple argument sets, the utility migration creates a catch event for each of the argument sets. |
|
Send message |
Intermediate message throw event |
|
Timer |
Intermediate timer catch event |
|
Compensate |
Migrated as an abstract activity with no implementation. You must decide how to implement it, or remove it. |
|
Runtime Settings Advanced Settings Custom Images |
Not migrated. |
The BPM migration utility uses the following mappings to migrate activities from BPM 10gr3 processes to BPM 12c processes:
Table 4-3 BPM 10gr3 Activity to BPM 12c Activities Mapping
| 10gr3 Artifact | 12c Artifact |
|---|---|
|
Automatic with no implementation |
Abstract activity |
|
Automatic implemented with a component |
Service task |
|
Automatic implemented with a method |
Script task |
|
Automatic implemented with a procedure |
Service task with a process call implementation. Arguments and arguments mappings are migrated. |
|
Automatic with a loop |
Loop condition, evaluation order and condition are not migrated. |
|
Interactive with no implementation |
User task implemented with an empty human task. You must implement the human task to complete the migration. |
|
Interactive that invokes a screenflow |
Service task implemented with a process call. The service task does not support role definition, the role assignment is in the process, so the original role may change after migration. |
|
Interactive implemented with:
|
User task implemented with an empty human task. You must implement the human task to complete the migration. |
|
Interactive with Optional Tasks |
Not migrated. |
|
Interactive with PUnit Tasks |
Not migrated. |
|
Decision |
User task implemented with an empty human task. You must implement the human task to complete the migration. |
|
Interactive Component Call |
User task implemented with an empty human task. You must implement the human task to complete the migration. |
|
Interactive Component Call implemented with:
|
User task implemented with an empty human task. You must implement the human task to complete the migration. |
|
Group |
Embedded subprocess There is no mapping for BPM 10gr3 transactional property. |
|
Subflow |
Abstract activity with no implementation. The activity names have the suffix “was screenflow" to identification. You must decide how to implement them. For information about argument and argument mapping migration, see Argument and Argument Mapping Migration. |
|
Screenflow |
BPMN process |
|
Subscreenflow |
Service task with process call implementation. Dynamic process invocation is not supported |
|
Process Creation |
Send task with no implementation. Dynamic process invocation is not supported. Runtime settings are not migrated. |
|
Termination Wait |
Receive task with no implementation. Runtime settings are not migrated. |
|
Grab |
Does not require migration. The alter flow feature is available from Process Workspace for any BPM process. Migrated to an abstract activity with no implementation. This activity is not connected to the process flow. |
|
Grab All |
Does not require migration. The alter flow feature is available from Process Workspace for any BPM process. |
|
Global Creation |
Start event with no implementation, followed by a default sequence flow to an initiator user task with no implementation defined, followed by a default sequence flow. If the global creation activity contains a script, a script task with the script is added after the last default sequence flow. If the global creation activity invokes a screenflow, a service task that calls the migrated screenflow is added after the last default sequence flow. The autocomplete and runtime settings are not migrated. |
|
Global automatic |
Start event followed by a script task and an end event of type none. Runtime settings are not migrated. |
|
Global Automatic | Polling by Interval |
Timer start event. |
|
Global Automatic - Triggered by Events |
Message start event. |
|
Global Automatic - Automatic Schedule |
Message start event. |
|
Global automatic - JMS Listener |
Message start event. |
|
Global automatic - JMS/JMX |
Message start event. |
|
Global Interactive |
Not migrated. |
|
Runtime Settings Advanced Settings Custom Images |
Not migrated. |
The BPM migration utility uses the following mappings to migrate gateways from BPM 10gr3 processes to BPM 12c processes:
Table 4-4 BPM 10gr3 Activity to BPM 12c Gateway Mapping
| 10gr3 Artifact | 12c Artifact |
|---|---|
|
Conditional Gateway |
Exclusive Gateway |
|
Split |
Parallel Gateway. The Generate Copies property is not migrated. |
|
Or Split |
Inclusive Gateway. |
|
Multiple Gateway |
Multi-instance subprocess. You must complete the migration manually. For more information, see Understanding Multiple Gateway Migration. |
The BPM migration utility migrates multiple gateways to a multi-instance subprocess with the following characteristics:
The type of the multi-instance subprocess is parallel.
The loop characteristics tab has Loop cardinality selected implemented with a simple expression. When you check the migrated process a warning appears asking you to complete the multi-instance implementation expression.
With multiple gateways, you must perform additional manual steps in order to complete the migration. For more information, see Completing Multiple Gateway Migration.
After running the BPM migration utility, you must manually complete the migration of multiple gateways by implementing or adapting the following:
Loop Characteristics
Creation Type
Expressions and Scripts
To replicate BPM 10gr3 functionality using a multi-instance subprocess:
The migration utility uses the following mappings to migrate process artifacts from BPM 10gr3 processes to BPM 12c processes:
Table 4-5 BPM 10gr3 Activity to BPM 12c Process Artifacts Mapping
| 10gr3 Artifact | 12c Artifact |
|---|---|
|
Lane |
BPMN Lanes |
|
Note |
Text annotation. The location of the note changes because of the different process structure. You must relocate the note to complete the migration. |
|
Measurement mark |
Not migrated. |
|
Documentation |
Process notes documentation and process notes use case documentation are migrated to the same artifacts 12c. Images and font type, font style and font color are not supported. |
|
Folders |
Folders containing processes or screenflows are migrated to folders in the 12c BPM project. |
|
Business Rule |
Not migrated. |
|
Process Interface |
Not migrated. |
The BPM migration utility migrates BPM 10gr3 transitions to BPM 12c sequence flows using the following mapping:
Table 4-6 BPM 10gr3 Transition to BPM 12c Sequence Flow Mapping
| 10gr3 Artifact | 12c Artifact |
|---|---|
|
Unconditional transition |
Default sequence flow. |
|
Conditional transition |
Migrated as a BPMN Gateway and a Conditional Sequence Flow. The condition is migrated if the expression is supported in 12c simple expressions. Otherwise the condition appears as a comment in the simple expression. |
|
Due transition |
Sequence flow with an interrupting boundary timer event. For more information, see Understanding Due Transition Migration. |
|
Message transition |
Default sequence flow. |
|
Exception transition |
Catch error boundary event with a default sequence flow. |
|
Business rule transition |
Conditional sequence flow with an empty condition. For more information, see Understanding Business Rule Transition Migration. |
|
Compensate transition |
Not migrated. |
The BPM migration utility migrates due transitions to a catch timer boundary event followed by a default sequence flow.
If the due transition contains an interval expression or a constant expression, this expression must be compatible with the supported expressions in BPM 12c. If the expression is not compatible, a message error appears and you must manually correct it to complete the migration.
Only interval expressions and constant expression are migrated.
The BPM migration utility migrates each business rule transition to a conditional sequence flow with an empty condition.
The BPM 10gr3 business rule code appears as a comment in the empty condition to be used to manually code the new business rule. For more information, see Completing Business Rule Transition Migration.
Business rule transitions are migrated as a conditional sequence flow with an empty condition. The empty condition contains the commented code from BPM 10gr3 to be used as a guide for the new implementation.
After migrating a business transition with the migration utility you must manually code the business rule and configure the condition in the conditional sequence flow to use it.
The BPM migration utility migrates exception handling using the following mapping:
Table 4-7 BPM 10gr3 Transition to BPM 12c Sequence Flow Mapping
| 10gr3 Artifact | 12c Artifact |
|---|---|
|
Exception Transition |
Error catch boundary event with a default sequence flow |
|
Process Exception |
BPMN Event Subprocess. Each exception transition is migrated to a different event subprocess. |
|
Compensate |
Sequence flow with an interrupting boundary timer event. |
|
Skip and back action |
Skip and back actions are supported using the predefined variable action. For more information, see “Configuring Catch Events to Recover from an Exception" in Developing Business Processes with Oracle Business Process Management Studio. |
The BPM migration utility migrates arguments and argument mappings for the following artifacts:
Begin
End
Message Wait
Interactive with Screenflow Call Implementation
Subflow
BPM 10gr3 arguments are migrated to BPM 12c arguments. BPM 10gr3 argument mappings are migrated to BPM 12c data associations.
The migration utility migrates arguments only when the variables, expressions and data types used for those arguments are supported or have an equivalence in BPM 12c.
For interactive activities implemented with a screenflow call, the migration utility uses the input/output arguments of the main task.
Multiple argument sets are not supported in BPMN. For some particular cases multiple argument sets are mapped to a different structure that models the same situation. For more information, see begin activities and notification wait activities that allow interruption in BPM Activities Migration.