Migrate Process Applications to a New OCI Process Automation Instance

If you're actively using Process in a production environment, Oracle can't automatically migrate you to Process Automation during the upgrade to Oracle Integration 3. You'll have to perform the migration manually.

Migrating process applications to a new standalone OCI Process Automation instance is appropriate under the following situations:
  • 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.

The upgrade path proposed below has been designed to limit disruption and maintain business continuity. It offers a well-tested approach for environments that have active (and usually long-running) process instances. It may not be applicable in all situations, so you should assess your own needs and implementation details to determine whether its appropriate for you.

The upgrade path can be broken down into three phases.

Phase Description Where process users work Tasks
Phase 1: Migrate Process Applications to OCI Process Automation The goal of this phase is to migrate your Oracle Integration Generation 2 Process applications to OCI Process Automation and restore them to a working order. This enables you to identify and correct any issues.

This phase won't affect your existing production environment.

During this phase your process users continue to work in Oracle Integration Generation 2.
  1. Provision and Prepare an OCI Process Automation Instance
  2. Migrate Process Applications to the New Instance
  3. Map Users and Groups to New Application Roles
  4. Validate and Activate Imported Process Applications
  5. Update Clients that Call Process Applications
Phase 2: Switch to OCI Process Automation The goal of this phase is to ensure that all new process requests are served by OCI Process Automation. In this phase, you promote your process applications and their dependencies to production and point all end users and clients to use OCI Process Automation going forward. During this time your process users switch to using OCI Process Automation for all new requests. They may also need to complete existing requests in Oracle Integration Generation 2 until all instances started on Oracle Integration Generation 2 are complete.
  1. Promote Process Applications to Production
  2. Perform Switchover to OCI Process Automation
  3. Coexistence Period
Phase 3: Upgrade to Oracle Integration 3 The goal of this phase is to complete the upgrade of your existing Oracle Integration Generation 2 instance to Oracle Integration 3.

At this stage there should be no running process instances in Oracle Integration Generation 2, making your instance eligible for upgrade to Oracle Integration 3.

At the end of this phase you'll have an Oracle Integration 3 instance linked with a standalone OCI Process Automation instance.

During this time your process users work exclusively in OCI Process Automation.
  1. Prepare for Upgrade
  2. Complete Post-Upgrade Tasks for OCI Process Automation