Oracle Cloud Infrastructure Documentation

Limit Development Work Before the Upgrade

In the days and hours leading up to the upgrade, limiting your work in Oracle Integration Generation 2 can help ensure a successful upgrade. You'll receive an email reminder to pause your development work two days before the upgrade.

By default, upgrade notifications are automatically sent to the specified administrator email. Oracle recommends you have notifications sent to a distribution list or group email so that you don't miss important emails if someone leaves the company. You set who receives notifications on the Upgrade page. See "Upgrade Notifications" in Configure Your Upgrade Settings.

Make sure you also complete all required tasks before the upgrade. See Complete Pre-Upgrade Tasks.
During the two days leading up to the upgrade, Oracle completes the following tasks:
  • Exports data from your Oracle Integration Generation 2 instance.
  • Creates an Oracle Integration 3 instance in your existing tenancy.
  • Imports Oracle Integration Generation 2 data into your new instance.

Runtime traffic continues to be routed to your Oracle Integration Generation 2 instance.

  1. During the two days leading up to the upgrade: Pause or limit your development work as much as possible.
    Any changes that you make are saved, but they might cause the upgrade check to fail. In such cases, the upgrade would need to be rescheduled. For example:
    • Don't add metadata.
    • Don't create integrations.
    • Don't activate integrations.
    • Resubmit any failed integration instances.

      When you chose your upgrade window, you specified whether to upgrade even if you have one or more failed integration instances. If you chose not to upgrade and an integration instance fails, your upgrade will be postponed.

    • If you use Processes in Oracle Integration Generation 2, don't create any new Process applications or Process transactions.
  2. One to two hours before the upgrade:

    • If you can, avoid starting any long-running asynchronous integrations.

    • Check again for any failed integration instances, and resubmit them.

      If the instance contains any failed integration instances, recover them. If you don't need them anymore, you can also delete them.

    • Limit your work as much as possible.

      For instance, try to limit your activation and deactivation work.

    • Make sure that the connectivity agent is up and running.

      In Oracle Integration Generation 2, the connectivity agent uses basic authorization to invoke Oracle Integration endpoints. During the upgrade, the connectivity agent is automatically converted from using basic authentication to using OAuth 2.0 token-based authentication to invoke Oracle Integration endpoints. All connections are automatically upgraded to OAuth 2.0, so you don't need to manually recreate any connections yourself.

  3. Fifteen minutes before the upgrade: Don't perform any business-critical tasks in Oracle Integration Generation 2.
    Note

    Oracle recommends that you do not stop your scheduled integrations prior to upgrade. If you stop integrations in your instance, the integrations remain stopped in the instance after the upgrade is complete, and you'll have to manually restart everything.
  4. At least one minute before the upgrade: Everyone should stop working in Oracle Integration Generation 2 and sign out.
Next, on upgrade day, you need to wait for the upgrade to finish and then perform the post-upgrade tasks. See What to Do During Upgrade.