Upgrade to Oracle Integration 3: Phase 1

Learn about the steps in phase 1 of phased upgrade. Complete these steps to upgrade integrations and Visual Builder applications to Oracle Integration 3.

Prerequisites

Make sure you complete the prerequisites before your instance is upgraded to avoid any disruption.

Oracle Integration Generation 2

  • A new host name will be created for your Oracle Integration Generation 2 instance. You will need to use this new host name for all browser-based access to Process on Oracle Integration Generation 2 instance going forward.
  • The new host name will be displayed under More details in the Process Automation prechecks section on the Upgrade page.

Visual Builder

If you have Visual Builder applications calling Process, then complete the following steps to update the Visual Builder applications.
  1. In the Visual Builder console, navigate to Settings, Services, Backends, Process Applications, and then Servers.
  2. For the Oracle Integration Generation 2 Process server, click Edit.
  3. In the Instance URL field, update the host name to the host name provided in the above step.
  4. In the Authentication field, change the value from Oracle Cloud Account to OAuth 2.0 User Assertion. Update the Scope field to use the Oracle Integration REST endpoint scope with primary audience URL. You can obtain the scope from Oracle Integration instance's OAuth confidentiality app from your tenancy. The scope will be defined in that confidentiality app. See Configure OAuth 2.0 Authentication Using Client Credentials for information about creating the OAuth confidentiality app in Oracle Integration Generation 2. For example: https://example.integration.ocp.oraclecloud.com:443/ic/api/.
  5. For each of the Visual Builder applications you created, complete the following steps:

    Note:

    You need to perform steps a to c only if Visual Builder is used to process the tasks using external UI. For information about external UI connection, see Create an External UI Connection.
    1. Open the security settings of the Visual Builder application.
    2. Set the Embedding field to Allow embedding in specified domains.
    3. In the Domain URL field, add the new Oracle Integration Generation 2 Process URL.
  6. If a Visual Builder web application has any reference to the Process components page, for example, VB_SERVER + "/ic/pub/components/pages/applist.html", then optionally you can create a new system variable for PCS as Oracle Integration Generation 2 PCS will now have a new URL.
  7. Redeploy the Visual Builder applications.
To update Process applications calling Visual Builder web applications as external UI:
  1. Open the Process application and go to Forms.
  2. Open the external UI form and use the staged or live Visual Builder application URL, for example, https://oicvb-vb-axkbv4jfb37h.builder.toronto-1.ocp.oraclecloud.com/ic/builder/rt/ExternalUI_1_0/1.0/webApps/webapp/.
  3. Publish and activate the application.
  4. In the workspace, open the task using the external UI form. The Visual Builder page is now available.

Note:

  • After updating the Visual Builder applications using the above steps, verify that the calls from Visual Builder to Process are working correctly.
  • Completing the pre-upgrade steps to update Visual Builder applications will ensure the following:
    • Verification of Visual Builder connectivity to Process before the actual upgrade, preventing downtime after the upgrade.
    • Once you update Visual Builder to use the new host name and authorization policy, you do not need to revert it.
  • If updating Visual Builder is unsuccessful: Revert the configuration changes and submit a service request (SR) on My Oracle Support to avoid a prolonged outage.
  • If you take no action before the upgrade: You will need to perform the steps to update the Visual Builder applications after upgrading, which will result in downtime. It is highly recommended to complete these steps before upgrading.

Other Front-End Applications

If you are using other front-end applications with Process APIs, you must update them to use the new host name. If you do not update the host name, you might encounter HTTP redirect errors.

Oracle Content Management

If you are using Process integrated with Oracle Content Management (OCM), you will need to update the host name for Process Automation in OCM's integration settings. With the below change, the integration between OCM and Process will work until OCM reaches end of life.

  • If Process is only used to support OCM: Contact your account team to reschedule your upgrade until you have moved off OCM (must be done by December 2025).
  • Otherwise: Your instance will be upgraded using the phased upgrade for Process. The integration between OCM and Process will work until OCM reaches end of life.

Process

  • It is recommended to pause or limit new development work until after the upgrade.
  • For service registration to work as expected, ensure that your REST trigger utilizes the OAuth 2.0 or Basic Authentication security policy.
  • If you have integrations called by processes, then:
    • Before upgrade: Enable Basic Authentication and OAuth for these integrations. The REST trigger for these integrations needs to have one of the following security policies enabled: Basic Authentication or Basic Authentication and OAuth. If it is using only OAuth, then update it to use Basic Authentication and OAuth to avoid failures after upgrade.
    • After upgrade: Verify that integrations called by processes use Basic Authentication or Basic Authentication and OAuth as the security policy.
  • If you have any dynamic processes on Oracle Integration Generation 2 that call integrations, then use REST connectors to deploy such processes on Oracle Integration 3. If you use native adapters instead of REST connectors to deploy such processes on Oracle Integration 3, it might cause failures.

Post-Upgrade Tasks

Learn what happens after the phase 1 upgrade is complete and ensure you complete the post-upgrade tasks.

Note:

The following information applies only to customers who were migrated using the phased upgrade for Process.

After the phase 1 upgrade is complete, here's what happens and what you need to do:

Oracle Integration Generation 2

  • You can still access your Oracle Integration Generation 2 environment using the same host name. All existing (in-flight and completed) transactions will be available.
  • On your Oracle Integration Generation 2 instance, only Process functionality will be available; all other components have been upgraded.
  • No new development work should occur in Oracle Integration Generation 2 from this point onwards.
  • The Oracle Integration Generation 2 instance will no longer be available in the Oracle Cloud Infrastructure Console, so management actions (such as start/stop) for your Oracle Integration Generation 2 instance are no longer possible.
  • You can discover integrations in Oracle Integration 3 if you need to apply any fixes in your existing processes.
  • Dynamic Process calls using the integrations activity will not work after the upgrade. As such, you will need to update your dynamic processes to use a service activity connection to call your integration(s). If you do not do this before the upgrade, you might experience service interruption post-upgrade.
  • For Process, you need to update the web service URL manually for design-time artifacts using the following steps:
    1. In the Oracle Integration Generation 2 instance, in the navigation pane, click Processes, and then click Process Applications.

      The Process Applications page appears.

    2. On the Process Applications page, click Activate.

      The Activate page appears listing the applications that you can manage.

    3. Click Actions Actions icon, then select Web Services.

      The Manage Web Services dialog appears.

    4. In the Manage Web Services dialog, the Exposed tab displays the web services URL that the active application is exposing. Update the host name in this web service URL manually to use the new host name.

    If you don't update the web service URL manually for design-time artifacts using the above steps, you might encounter an error.

Oracle Integration 3

  • Process will not be enabled in Oracle Integration 3 after the upgrade.
  • Integrations that call Process have been migrated and activated.
  • You will be able to discover new processes on Oracle Integration Generation 2 if you need to apply any fixes to existing solutions.
  • Schedule integrations with a process action calling Process are not automatically started after phased upgrade. You need to start these schedule integrations after phased upgrade.

Visual Builder and Other Front-End Applications

  • If you have Visual Builder applications calling Process, and did not complete the pre-upgrade steps, you must complete them now.
  • Oracle Integration Generation 2 Processes will no longer be discoverable or available to call in action chains. You need to use Oracle Integration 3 Process for all new Visual Builder development initiatives.

Validation

  • Perform sanity checks to validate connectivity between integrations, front-end applications, and Process.
  • Perform functional testing on your Process environment.

Resume Operations

  • Once validation is complete, business users can resume creating process instances and performing tasks.