What are the benefits of upgrading?

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
• What's New for Oracle Integration 3

Are all the features from prior versions of Oracle Integration available in Oracle Integration 3?

Am I required to upgrade my instances to Oracle Integration 3?

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.

Is there a charge to upgrade?

No. The upgrade is available at no additional cost.

What is the upgrade workflow?

See Upgrade Workflow Quick Reference.

What happens during upgrade?

See What to Do During Upgrade.

What if issues occur during 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.

When will my instance be upgraded?

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.

Can I choose or reschedule my upgrade date?

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.

Will there be downtime?

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.

My upgrade was scheduled. What if I don't confirm the date or specify upgrade details?

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

What if something changes after my upgrade is scheduled and my instance can't be upgraded anymore?

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.

What do I have to do before the upgrade?

• 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.

Should I stop my scheduled integrations before the upgrade?

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.

What if a scheduled integration is running when the upgrade begins?

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.

How do I know when the upgrade is finished?

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.

Will my Oracle Integration Generation 2 instance still be available after the upgrade?

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

What do I have to do after the upgrade?

See Complete Post-Upgrade Tasks.

Will my user, group, and policy information be available after upgrade?

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.

What if issues occur after the 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.

Will the IP address of my instance change?

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.

Will my URLs change?

• 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.

Can I have both Oracle Integration Generation 2 and Oracle Integration 3 instances?

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.

Can I switch to a different region or compartment during upgrade?

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

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

How else might upgrade affect my service instance?

• Custom endpoint: If you use a custom endpoints, be aware of the following changes:
  • You'll see no difference in runtime access to your integrations after upgrade. 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.
  • If you used an SSL certificate in Oracle Integration Generation 2, you'll need to set up a load balancer as a front end for your Oracle Integration Generation 2 instance, and remove the SSL certificate.
  • Oracle Integration 3 currently doesn't support Visual Builder with a custom endpoint.
  • Oracle Integration 3 currently doesn't support alternate custom endpoints.

  See Custom Endpoint URL precehck.

• Instance ID value: The system-generated instance ID that is displayed on the Instances page and in the activity stream for an integration instance has changed from a numeric value to an alphanumeric value in Oracle Integration 3. See Instance ID Action precheck.
• Daily email limit: Oracle Integration 3 can send a limit of 10,000 emails in a rolling 24-hour window. See Daily Email Limit precehck.
• Custom scopes in IDCS: Oracle Integration 3 adds a default scope to Oracle Identity Cloud Service (IDCS) when the instance is created; no other custom scopes are supported in IDCS. See Custom scopes in IDCS precheck.
• Activity stream data: The activity stream isn't migrated, but you can capture this data in the Oracle Cloud Infrastructure Console. See Instance Pre-Upgrade Tasks.
• Network rules configuration: If you've enabled network rules in any Oracle Cloud Infrastructure services, you might need to configure them to include Oracle Integration. See Instance Pre-Upgrade Tasks.
• Update window: The update window is now determined by the shape of your instance, rather than tags as it was in Oracle Integration Generation 2. See Updates to Your Instance.
• You might also want to look through the following documentation:
  • Benefits of Upgrading
  • What's New for Oracle Integration 3
  • Common Issues in Known Issues for Oracle Integration 3
  • Troubleshoot Upgrade Issues

Will I need to perform any post-upgrade tasks for my service instance?

• Make sure you have access to the Oracle Integration 3 instance, which might include updating an IAM policy with the new OCID. See Ensure Access to the Instance.
• Complete your organization's post-upgrade verification tasks. See Follow Your Organization's Verification Procedures.

If I use the connectivity agent, do I need to recreate any connections?

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

• Agent Java version and KeyStore: For Oracle Integration 3, your connectivity agents must use JDK 17 and PKCS 12 KeyStore. See Agent Java Version precehck.
• Allowlists: 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. See Update Allowlists.
• Agent group identifiers: Oracle Integration 3 doesn't support spaces in agent group identifiers, they won't be migrated to Oracle Integration 3. See Unsupported AgentGroup Identifier precheck.
• Conversion to OAuth 2.0: During the upgrade, your connectivity agents are automatically converted from using basic authentication to using OAuth 2.0 token-based authentication to communicate with Oracle Integration. As long as your agents are running when upgrade begins, all agents are automatically upgraded to OAuth 2.0, so you don't need to manually recreate any agents yourself. See Connectivity Agent Pre-Upgrade Tasks.
• Proxy server caching: Set your proxy server's Cache property for the Oracle Integration URLs to refresh as frequently as possible. See Set the proxy server's Cache property.
• Additional firewall traffic after upgrade: 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.

If I convert the JKS KeyStore to the PKCS12 KeyStore for the connectivity agent, does this affect my Oracle Integration Generation 2 connectivity agent?

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).

How else might upgrade affect my connectivity?

Will I need to perform any post-upgrade tasks for connectivity?

• 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.
• Make sure your connectivity agents were upgraded and connections are working properly. See Ensure Connectivity.

Can I migrate some integrations in my instance to Oracle Integration 3 and keep some integrations in my existing Oracle Integration Generation 2 instance?

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

Are Oracle Integration Generation 2 and Oracle Integration 3 integrations forward and backward compatible?

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.

How does upgrade affect my activity stream and actively running integrations?

• Data retention: Oracle Integration 3 Standard and Enterprise editions support only 32 days of data retention. During upgrade only the most recent 32 days of retained data will be migrated.
• Activity stream data: The activity stream isn't migrated, but you can capture this data in the Oracle Cloud Infrastructure Console. The activity stream has been greatly enhanced and can be viewed and downloaded from the Instances page, Instance Details page, and Errors page.
• Runtime activities are paused during upgrade downtime: Oracle Integration stops accepting incoming integration requests during the brief downtime during upgrade.

See How Upgrade Affects Runtime Data.

How else might upgrade affect my integrations?

• Delayed (asynchronous) response: The delayed (asynchronous) response pattern was previously supported in the some adapters. See Delayed (Asynchronous) Response precheck.
• Identity certificates: If you have identity certificates, you'll need to upload new identity certificates after upgrade. See Ensure Connectivity.
• Basic routing duplicate app name: In Oracle Integration 3, you can't have multiple basic routing integrations that have the same source and target endpoint names. See Basic Routing Duplicate App Name precheck.
• Number of active integrations: An instance can have a maximum of 700 active integrations, as specified in the Service Limits. See Number of Active Integrations precheck.
• Multiple read file: The Read Multiple File operation was deprecated in Oracle Integration Generation 2. See Multiple Read File precheck.
• Publish/subscribe integrations: Publish/subscribe (or pub/sub) integrations have been replaced by event-driven orchestrations in Oracle Integration 3. See Publish/Subscribe Integrations precheck.
• API calls must use OAuth: Design-time (DT) built-in API calls using a REST connection must use OAuth. See DT API Basic Auth to OAuth action precheck.
• Custom XSLT function definition: Oracle Integration 3 doesn't support custom XSLT function definitions that were added manually in the mapper at this time. See XSLT function definition precheck.
• You might also want to look through the following documentation:
  • Benefits of Upgrading
  • What's New for Oracle Integration 3
  • Integration Issues in Known Issues for Oracle Integration 3
  • Troubleshoot Upgrade Issues

Will I need to perform any post-upgrade tasks for integrations?

• Check your integrations for any failed activations or schedules that failed to start.
• If needed, take action on requests that any clients sent to Oracle Integration during the downtime.

See Ensure Integrations Work.

How might upgrade affect my adapters?

• Custom adapters: Custom adapters aren't supported by Oracle Integration 3 yet. See Custom Adapters precheck.
• Oracle utilities adapter: Swagger 2.0 is no longer supported in the Oracle Utilities Adapter. See Oracle Utilities Adapter precheck.
• Unsupported adapters: Some adapters are no longer supported in Oracle Integration 3. See Unsupported Adapters precheck.
• Unsupported REST types: Some connection types are deprecated and not supported in a REST Adapter connection. See Unsupported REST Types precheck.
• Decommissioned Microsoft adapters: Microsoft decommissioned the Microsoft Outlook REST APIs in November 2022. If you use any of the following adapters, you must use the Microsoft Graph REST APIs instead. See Adapters Pre-Upgrade Tasks.
• You might also want to look through the following documentation:
  • Benefits of Upgrading
  • What's New for Oracle Integration 3
  • Integration Issues in Known Issues for Oracle Integration 3
  • Troubleshoot Upgrade Issues

Will I need to perform any post-upgrade tasks for adapters?

No.

How might upgrade affect my B2B features?

• Data retention: Oracle Integration 3 Standard and Enterprise editions support only 32 days of data retention. During upgrade only the most recent 32 days of retained data will be migrated.
• B2B passwords: Your identity certificate file (JKS) requires two sets of passwords: Key Passwords and Keystore Password. All the passwords must be identical. See B2B for Oracle Integration Pre-Upgrade Tasks.
• You might also want to look through the following documentation:
  • Benefits of Upgrading
  • What's New for Oracle Integration 3
  • Common Issues in Known Issues for Oracle Integration 3
  • Troubleshoot Upgrade Issues

Will I need to perform any post-upgrade tasks for B2B?

No.

How does upgrade affect File Server?

A lot will stay the same after upgrade. During the upgrade, Oracle migrates your File Server files, folder structure, and allowlists (permissions) from Oracle Integration Generation 2 to Oracle Integration 3. After the upgrade, access the File Server REST APIs the same way you did in Oracle Integration Generation 2.

However, there are some changes you should be aware of:

• IP and port values: During upgrade, Oracle assigns new IP and port values for the File Server SFTP server. See How Upgrade Affects File Server. After upgrade, you'll need to complete some post-upgrade tasks described below.
• Access to File Server: In Oracle Integration 3, you can access File Server using the File Server URL and credentials.
• Allowlists: In Oracle Integration Generation 2 you had to submit a service request (SR) to request changes to your File Server allowlists. In Oracle Integration 3, you can update the allowlist yourself. For information on managing your allowlists for File Server after migration, see Restrict Access to an Instance Using the Self-Service Allowlist.
• Legacy algorithms: There are several legacy exchange algorithms that FTP no longer supports. During upgrade, FTP connections will be updated with the current algorithms. See How Upgrade Affects File Server.
• API calls must use OAuth: If you use File Server REST API calls, they must use OAuth. See Integrations Pre-Upgrade Tasks.
• You might also want to look through the following documentation:
  • Benefits of Upgrading
  • What's New for Oracle Integration 3
  • File Server Issues in Known Issues for Oracle Integration 3
  • Troubleshoot Upgrade Issues

Will I need to perform any post-upgrade tasks for File Server?

• Update your integrations and SFTP clients to use the new IP and port values.
• Add the new IP address to your internal firewall allowlist.

See Ensure Connectivity

What are the benefits of upgrading Process?

How does upgrade affect Process features?

• 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 affects any clients calling Process via a REST API (for example, integrations or Visual Builder apps). See Complete Post-Upgrade Tasks for Process Automation.
• Process instance data is not migrated to Oracle Integration 3. This means you won't see historical transactions created or completed in Oracle Integration Generation 2 after upgrade.
• You might also want to look through Process Automation Issues in Known Issues for Oracle Integration 3.

What upgrade paths are available for me if I use process?

Depending on how you're using Process in Oracle Integration Generation 2, you'll use a different option to upgrade or migrate. See Process Upgrade Options.

Will I need to perform any post-upgrade tasks for Process?

Your post-upgrade steps are dependent on which upgrade option applies to your implementation. See Process Upgrade Options.

Why does the manual migration process recommend that the OCI Process Automation instance I create should be a standalone instance?

A standalone OCI Process Automation instance is recommended because:

• It ensures that there's no impact to existing integrations or Visual Builder applications.

  If you instead provisioned a new Oracle Integration 3 instance, you would also need to migrate your existing integrations and Visual Builder applications to the new environment and update your clients to the new Oracle Integration 3 URL. Additionally, you wouldn't be able to take advantage of the Oracle Integration 3 upgrade to automatically upgrade the rest of your environment.

• It limits costs during migration.

  OCI Process Automation standalone can leverage the Oracle Cloud Free Tier pricing model. See Process Automation Pricing.

I'm following the manual migration process and need help. Who can I turn to?

You can contact your Oracle Account Representative and discuss available options if you need guidance throughout the migration process. If you've encountered a specific error or issue, create a service request (SR) on My Oracle Support.

Will Oracle Integration Generation 2 process data be retained as part of the upgrade or migration process?

No. To save or export this data prior to upgrade, complete the steps outlined in Archiving and Purging Process Automation Data in Oracle Integration.

If I wait, will there eventually be an automatic upgrade for instances with actively used process applications?

No. You should perform the manual migration to Oracle Integration 3.

How does upgrade affect Visual Builder?

• Visual Builder with BYODB: If you use Visual Builder with your own Oracle database instance (BYODB), Autonomous Transaction Processing (ATP) must be up and running during upgrade. See Visual Builder Pre-Upgrade Tasks.
• PWAs created with Visual Builder: Oracle Integration 3 doesn't yet support Progressive Web Apps (PWAs) created with Visual Builder. See VBCS-PWA precheck.
• You might also want to look through Visual Builder Issues in Known Issues for Oracle Integration 3.

Will I need to perform any post-upgrade tasks for Visual Builder?

Configure an IAM policy forVisual Builder in Oracle Integration 3. See Set the IAM Policy for Managing the Visual Builder Instance.