| Phased Upgrade for Process |
If you have active process workloads, you can now upgrade to Oracle Integration 3 in a phased manner:
- Phase 1: Upgrade integrations and Visual Builder applications.
- Phase 2: Migrate Process workloads.
This approach is appropriate when:
- You are using Process in production.
- You have long-running Process instances, which can't be completed prior to upgrade.
- You need to continue to serve new Process application requests without any disruption.
- You have integrations or Visual Builder applications that you do not want to disrupt with the Process migration.
|
Phase 1: Upgrade integrations and Visual Builder applications
- As part of the scheduled upgrade process, integrations and Visual Builder applications in Oracle Integration Generation 2 will be upgraded to Oracle Integration 3, however Process will remain on Oracle Integration Generation 2.
- After the upgrade, you will be able to access your existing Oracle Integration Generation 2 environment in addition to your newly created Oracle Integration 3 instance.
- The automated upgrade will ensure that integrated workflows/connectivity between integrations/Visual Builder applications (running on Oracle Integration 3) and Process (on Oracle Integration Generation 2) will continue to work after the upgrade with some exceptions. See Limitations.
- Business users can continue to access Process tasks and create Process instances on Oracle Integration Generation 2 after the upgrade.
Phase 2: Migrate Process workloads
- After Phase 1 is complete, you can continue to use Process in Oracle Integration Generation 2 until December 31, 2026. Process in Oracle Integration Generation 2 will be decommissioned on December 31, 2026.
- To migrate Process workloads to the newly provisioned Oracle Integration 3 instance, you will need to:
- Enable Process in the upgraded Oracle Integration 3 instance.
- Export Process applications from Oracle Integration Generation 2 and import them into Process on Oracle Integration 3.
- Refactor Process applications to resolve validation issues. Activate applications on Oracle Integration 3 Process.
- Update clients that call Process applications.
- Promote Process applications to production.
- Perform switchover to Oracle Integration 3 Process for new process transactions.
- Enter coexistence period.
- Exit coexistence period before December 31, 2026.
|
| Automated In-Place Upgrade for Process |
- You have no process usage (running or completed instances), or
- Your process usage is in a pre-production state, or
- You have short-lived process instances that can be completed in Oracle Integration Generation 2 before upgrade, or
- You are only using decision applications.
|
Before upgrade
You must perform the following steps:
- Replace the Process action in any affected integrations.
- Ensure that all required transactions complete in Oracle Integration Generation 2 prior to upgrade.
During upgrade
Oracle performs the following steps:
- Exports your process applications from Oracle Integration Generation 2.
- Enables Process
Automation in your upgraded Oracle Integration 3 instance.
- Converts your existing process applications and imports them into your Oracle Integration 3 instance.
If any of your process applications use unsupported actions (for example, an Insight activity), Oracle replaces those actions with placeholder actions that you must replace or remove after upgrade. See Complete Post-Upgrade Tasks for Process Automation.
Note: Process instance data is not migrated to Oracle Integration 3. This means you won't see historical transactions created in Oracle Integration Generation 2 after upgrade.
After upgrade
You must perform post-upgrade activities to restore your process applications to working order. See Complete Post-Upgrade Tasks for Process Automation.
|
Note
This option is no longer recommended and should not be used if you are beginning the migration process. Follow the Phased Upgrade for Process approach instead.
Migrate Process Applications to a New OCI Process Automation Instance |
- You are using process in production, and
- You have long-running process instances which can't be completed prior to upgrade, and
- You need to continue to serve new process application requests without any disruption, and
- You have integrations or Visual Builder applications that you do not want to disrupt with the process migration.
|
Migrate process applications to OCI Process Automation
- Provision a new OCI Process Automation instance.
- Migrate process applications to the new instance.
- Perform post-migration activities to restore process applications to working order.
- Update clients that call OCI Process Automation.
Switch to OCI Process Automation for new transactions
- Promote process applications to production.
- Perform switchover to OCI Process Automation.
- Serve new process transactions from OCI Process Automation.
- Run Oracle Integration Generation 2 in parallel with OCI Process Automation until existing transactions complete (coexistence period).
Upgrade to Oracle Integration 3
- Upgrade the Oracle Integration Generation 2 instance once all process instances complete.
- Attach the OCI Process Automation instance to Oracle Integration 3.
|