Process Upgrade Options

Depending on how you're using Process in Oracle Integration Generation 2, you'll use a different option to upgrade or migrate. The following workflow will help you determine how to proceed.

Upgrade option When is this option appropriate? Synopsis of the option
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.

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.