Yes, but only after all the features that you use, other than those that have been deprecated, are available for upgrade in Oracle Integration 3.

Oracle selects an upgrade window for you and sends an email notification. Everyone who receives emails about Oracle Integration Generation 2 quarterly updates receives the email.

If needed, you can select a different upgrade window, but you can't opt out of the upgrade.

If you have to go live during your assigned upgrade window, Oracle can change the upgrade window to a month earlier or a month later. Contact your account representative or customer success manager.

Oracle Integration 3 is the next generation of the Oracle Integration platform. The upgrade to Oracle Integration 3 delivers a modern and intuitive user interface and improved performance. Additionally, the latest features will be delivered only to Oracle Integration 3. See Benefits of Upgrading.

No. The upgrade is available at no additional cost.

See Upgrade Workflow Quick Reference.

All instances have been scheduled for upgrade. Oracle sent you an email with your upgrade date. You can also see this on the Upgrade page and in a message in the banner.

Yes. Oracle selects an upgrade window for you, but you can change your upgrade window if it's three or more business days away.

All upgrade dates that are available to you appear on the Upgrade page, in the Upgrade Window list.

If you have to go live during your assigned upgrade window, Oracle can change the upgrade window to a month earlier or a month later. Contact your account representative or customer success manager. .

Yes. Upgrades generally take less than ten minutes, but may take longer if you have a lot of files or a complex setup. During this time, Oracle Integration is unavailable, and all in-flight instances stop running. See How Upgrade Affects Runtime Data.

Everyone must stop working in Oracle Integration. If you try to sign in during the downtime, a Service Unavailable page informs you that Oracle Integration is unavailable.

Your upgrade will proceed as scheduled even if you don't confirm your date.

Yes. For example, if you have multiple Oracle Integration Generation 2 instances, you can upgrade them at different times. However, be aware that work done in Oracle Integration Generation 2 might not be compatible with Oracle Integration 3 and vice versa based on feature differences between the versions. See the new features and differences from prior versions in What's New for Oracle Integration 3.

If you are an administrator who works in the Oracle Cloud Infrastructure Console, your Oracle Integration 3 instances appear in the same list as your Oracle Integration Generation 2 instances. Each instance is clearly labeled so you can identify its version.

No. When you upgrade, you must upgrade the entire instance.

See How Upgrade Affects Runtime Data.

See How Upgrade Affects File Server.

• Process functionality has undergone some important changes that you should be aware of. See How Upgrade Affects Process Features.
• After the upgrade, Process will be accessible via a new URL. See Complete Post-Upgrade Tasks for Process Automation.
• The upgrade will affect any clients calling Process (for example, integrations or Visual Builder apps). See Complete Post-Upgrade Tasks for Process Automation.

Upgrade doesn't affect Visual Builder (VB); you remain on the same version of VB as you were prior to upgrade.

If you use a custom endpoint after upgrade, you'll see no difference in runtime access to your integrations. For all other access points—design-time, Visual Builder, Process Automation—you still access the custom endpoint, but the custom endpoint then redirects to the appropriate URL.

Upgrades generally take less than ten minutes, but may take longer if you have a lot of files or a complex setup. Oracle sends you an email when the upgrade completes.

You can also see if your instance is available by trying to sign in:

• If you sign in and the user interface remains unchanged, the upgrade hasn't begun yet.
• If you sign in and a page informs you that the service is unavailable, the upgrade is still in progress.
• If you sign in and the user interface has changed, the upgrade is finished.

  Confirm the upgrade finished by checking the version number in the About dialog.

See When is Basic Authentication Supported in Oracle Integration 3?.

• Check upgrade readiness and correct precheck issues.
• Configure your upgrade settings.
• As your upgrade date approaches, perform some pre-upgrade tasks, including updating your allowlists.

Yes. After the upgrade, the Oracle Integration 3 instance has a different IP address than the Oracle Integration Generation 2 instance.

If you have allowlists, you need to allowlist the new IP addresses. See Update Allowlists.

After the upgrade finishes, the Oracle Integration Generation 2 IP addresses are no longer assigned to you.

Note that the incoming IP addresses for development and production instances are different, even within the same region. However, the outgoing IP address is the same for all shapes (development or production) in a single region.

• The runtime URL for Oracle Integration 3 won't change; it will be your Oracle Integration Generation 2 URL.
• The design-time URL will change, but your bookmarks will still work. The design-time URL for Oracle Integration 3 is in the following format.

  https://design.integration.region.ocp.oraclecloud.com/?integrationInstance=query_parameter_repersenting_instance

  After the upgrade, the design-time URL for your Oracle Integration Generation 2 instance redirects to the new Oracle Integration 3 instance URL, so you can continue using your existing bookmark or update it. It's up to you.

• The Process URL will change.

No. Moving regions and compartments is not part of the upgrade process.

See What to Do During Upgrade.

Prior to the upgrade, Oracle stops the schedule if it's running. After the upgrade, the schedule starts in Oracle Integration 3 from the point where it stopped in Oracle Integration Generation 2.

Oracle doesn't recommend stopping your scheduled integrations. If you stop your integrations in your Oracle Integration Generation 2 instance, the integrations remain stopped in the Oracle Integration 3 instance after the upgrade is complete, and you'll have to manually restart everything.

No. Your Oracle Integration Generation 2 isn't available after the upgrade.

Somewhat. Work done in Oracle Integration Generation 2 might not be compatible with Oracle Integration 3 and vice versa based on feature differences between the versions. See the new features and differences from prior versions in What's New for Oracle Integration 3.

See Complete Post-Upgrade Tasks.

After scheduling the upgrade, Oracle checks your instance often to make sure it's still ready. If the check identifies any issues, Oracle emails you so you can address the issues and proceed with the scheduled upgrade. See Correct an Instance with Failed Readiness Checks.

Oracle also checks your instance at the beginning of the upgrade window. If the check identifies any issues, Oracle cancels the upgrade and emails you about the change. Everyone who gets emails about Oracle Integration Generation 2 quarterly updates receives the email, which includes information about next steps.

Yes. All security-related information from your Oracle Integration Generation 2 instance is present in your Oracle Integration 3 instance after the upgrade. Additionally, the upgrade doesn't change anything related to identity domains. For example, if your tenancy uses identity domains before the upgrade, it continues using identity domains after the upgrade.

In rare situations, an issue prevents an upgrade from completing. When an upgrade doesn't complete, Oracle rolls back the changes, turns on the schedule in the Oracle Integration Generation 2 instance, and restores your access to the instance during the downtime period. You continue working in the Oracle Integration Generation 2 instance, with the same features you were using before the upgrade.

In such situations, Oracle informs you by email that you can continue working in Oracle Integration Generation 2. Expect the email to arrive either within your upgrade window or soon after. Everyone who gets emails about Oracle Integration Generation 2 quarterly updates receives the email. You can schedule your upgrade for another time, and Oracle works with you to determine the next steps.

When you specify upgrade requirements, you can also choose to ignore specific issues during upgrade. For instance, you determine whether to proceed with the upgrade if Oracle is unable to activate all integrations and start the schedule for all integrations. See Configure Upgrade Settings or Reschedule Upgrade.

After the upgrade completes, sign in and perform your typical verification tasks, and complete the required post-upgrade tasks.

If you experience any issues after the upgrade, either while performing verification tasks or performing day-to-day activities, enter a service request (SR) on My Oracle Support.

No. However, you should be aware of several points:

• Before upgrade, you must update your allowlist settings to configure connectivity from your connectivity agents to Oracle Identity Cloud Service (IDCS) and the Oracle Integration runtime IP addresses.
• During the upgrade, the connectivity agent is automatically converted from using basic authentication to using OAuth 2.0 token-based authentication to communicate with Oracle Integration. All agents are automatically upgraded to OAuth 2.0, so you don't need to manually recreate any agents yourself.
• After the upgrade, you’ll see additional traffic to your firewall because the connectivity agent must get new authentication tokens from the Oracle Identity Cloud Service or the identity domain.
• Agents that are offline during upgrade or don't meet upgrade requirements won't be upgraded. You'll need to perform post-upgrade steps to regain connectivity.

No. Converting the JKS KeyStore to the PKCS12 KeyStore does not impact your Oracle Integration Generation 2 connectivity agent, and only takes effect after you have upgraded to Oracle Integration 3. You can convert your keystore manually or let it happen automatically during upgrade (requires agent to use JDK 17).