Configure Upgrade Settings or Reschedule Upgrade

You should have received notification of your scheduled upgrade window, checked your upgrade readiness, and corrected any precheck issues. Before your upgrade, configure the upgrade settings. If you need to reschedule your upgrade, you can do so if the upgrade is more than three business days away.

Prerequisites:

If any upgrade readiness checks fail, address the issues that apply to your instance. For instructions on how to fix failed upgrade checks, see Check Upgrade Readiness and Correct Precheck Issues.
Only people who are part of the ServiceAdministrator group can perform these tasks. See Create an IAM Policy in an Identity Domain for tenancies that use identity domains or Create an IAM Policy for tenancies that do not use identity domains.

View Your Upgrade Window

You can see your scheduled upgrade window in the following places:

Oracle sends an email, informing you of your upgrade window.
By default, upgrade notifications are automatically sent to the listed 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 Add the distribution list, group email, or any other stakeholders who should receive upgrade notifications, by entering their email addresses, separated with commas (,) in the box Upgrade Notifications. Oracle will include these email addresses in all future upgrade notifications.
An announcement appears in the user interface. You can see the announcement if you're part of an administrator group.
Click Announcements . Next to the upgrade announcement, under Event Time, you'll see the start time of your upgrade window. Click the notification to view the start and end times of your upgrade window.
Click Settings, then click Upgrade to see your upgrade window.

Reschedule Your Upgrade

If you need to reschedule your upgrade, you can do so if the upgrade is more than three business days away.

In Oracle Integration, click Settings, then Upgrade.
Under Time window you see your upgrade window for your current instance.

You can change your upgrade window if it's three or more business days away. All upgrade dates that are available to you appear in the list.

Note:
If you change your upgrade window after new IP addresses have been allocated for you environment (shown in the Allowlist IP Addresses section), Oracle can't guarantee the IP address allocations will remain the same. The IP addresses originally allocated will continue showing in the user interface until new ones are assigned.

If you have multiple instances, choose your upgrade windows carefully. See Recommendations for Upgrading Multiple Instances.

Note:
Does your organization restrict access to the Oracle Integration Generation 2 instance based on the OCID value that uniquely identifies your instance? If so, consult the IAM policy administrator before scheduling the upgrade. The Oracle Integration 3 instance has a different OCID than the Oracle Integration Generation 2 instance. After the upgrade, the IAM policy administrator must update the IAM policy so that it refers to the Oracle Integration 3 OCID. People can sign in only after this work is complete. Make sure the upgrade window is during a time when the IAM policy administrator is available to update the policy.
For information about updating the IAM policy, see About IAM Policies for Oracle Integration and Creating an IAM Policy.
Click Save changes.
Oracle emails you confirming the availability of your requested window.

By default, upgrade notifications are automatically sent to the listed 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 Add the distribution list, group email, or any other stakeholders who should receive upgrade notifications, by entering their email addresses, separated with commas (,) in the box Upgrade Notifications. Oracle will include these email addresses in all future upgrade notifications.

You can continue with configuring your upgrade settings while waiting for the confirmation email.

Configure Your Upgrade Settings

Select the options appropriate for your instance.

Option	Description
Ignore identity certificates during upgrade eligibility check	When selected, the readiness check ignores whether there are connections that use identity certificates. Ignoring this check doesn't affect your upgrade; your upgrade will proceed as scheduled. Additionally, after upgrade, you must upload new identity certificates, test the associated connections, and activate the associated integrations as described in Complete Post-Upgrade Tasks.
Time window	If your upgrade has been scheduled, you see your upgrade window. You can change your upgrade window if it's three or more business days away, as described above. Note: If you change your upgrade window after new IP addresses have been allocated for you environment (shown in the Allowlist IP Addresses section), Oracle can't guarantee the IP address allocations will remain the same. The IP addresses originally allocated will continue showing in the user interface until new ones are assigned.
Shape of Oracle Integration 3	The shape determines when the instance receives updates. The shape you select determines the upgrade time windows that are available. Development: Instances with this shape are updated two weeks before instances with a Production shape. Production: Instances with this shape receive updates two weeks after instances with a Development shape. If you select Production, when you save your changes, you'll be prompted to confirm that you are satisfied with the testing you've done on your Development instances. You can't change the shape after the instance has been assigned an ingress or egress IP address. If the shape is not correct and you're unable to change it, submit a service request (SR) on My Oracle Support. Note: You can't change the shape after the upgrade is complete. However, you can move data to another instance using the export and import features.
Ignore activation failures, I will activate integrations as needed	Determine whether to roll back your upgrade if Oracle isn't able to activate all of your integrations in Oracle Integration 3. When selected, if Oracle can't activate one or more integrations, the upgrade proceeds. If you select this option, plan to check the status of all your integrations after the upgrade finishes and activate integrations as needed. When deselected, if Oracle can't activate one or more integrations, Oracle rolls back the upgrade. After the rollback, you continue working in the Oracle Integration Generation 2 instance. Oracle will schedule another upgrade in the future.
Ignore start schedule failures, I will manually start them if needed	Determine whether to roll back your upgrade if Oracle isn't able to start the schedule for an integration. When selected, if Oracle can't start the schedule on one or more scheduled integrations, the upgrade proceeds. If you select this option, plan to check the schedules of your integrations after the upgrade, and manually start them if needed. When deselected, if Oracle can't start the schedule on one or more scheduled integrations, Oracle rolls back the upgrade. After the rollback, you continue working in the Oracle Integration Generation 2 instance and can schedule another upgrade in the future.
Ignore test connection failures	Select this option to continue with the upgrade, even if connections don't pass testing in Oracle Integration 3 after the upgrade. If you deselect this option, the upgrade is rolled back after a connection doesn't pass testing in Oracle Integration 3. Oracle recommends selecting this checkbox and addressing any connection failures after the upgrade.
For the purpose of troubleshooting, I authorize Oracle Integration to access the IAR file of any integration flow that causes the upgrade to fail	If you select this option, should the upgrade fail, Oracle Integration Generation 2 saves the integration IAR file that caused the failure. This reduces the time required for troubleshooting when you contact Technical Support.
Connectivity Agent Status	The Connectivity Agent Status section shows the status of all the connectivity agents in your instance. The connectivity agent status table shows the following information: Agent Name: Shows the name of the agent. Agent Group: Shows the agent group that the agent is associated with. Agent Status: Your connectivity agents must be up and running before the upgrade of your connectivity agent begins or the upgrade will fail. For any agents that are failing this precheck, make sure that they're available before upgrade begins. Java Version: The servers that host your connectivity agents must use JDK 17 or the upgrade of those connectivity agents will fail. For any agents that are failing this precheck, install JDK 17. PKCS12 KeyStore: The servers that host your connectivity agents must use PKCS12 KeyStore. If your agents use JDK 17, your JKS KeyStores will automatically be converted to the PKCS12 KeyStore during upgrade. In use: If an agent is marked as not in use it means it either isn't used in any connections or there hasn't been any recent traffic from the agent (agent-level messages). If an agent isn't in use it won't cause your upgrade to fail. However, you might want to consider removing unused agents. Allowlist status: Shows whether the connectivity agent's allowlist has been updated to configure connectivity from the connectivity agent to Oracle Identity Cloud Service (IDCS) and Oracle Integration. See Complete Pre-Upgrade Tasks. Caution: You must update your allowlists before upgrade or you'll lose connectivity until it's done. If any of your agents are offline during upgrade or don't meet upgrade requirements, they won't be upgraded. You'll need to perform post-upgrade steps to regain connectivity.
Allowlist IP Addresses	Two weeks before the upgrade, your new ingress and egress IP addresses are available: OIC Design-time IPs: IP addresses for traffic entering into Oracle Integration 3 design time (the Oracle Integration 3 application). Note: The design-time URL supports the built-in Oracle Integration APIs. OIC Runtime IP: IP address for traffic entering into your Oracle Integration 3 runtime applications. OIC Outbound IP: IP address for traffic exiting Oracle Integration 3. VB Inbound IP: IP address for traffic entering into Visual Builder. VB Outbound IPs: IP addresses for traffic exiting Visual Builder. VB VCN OCID: Oracle Cloud ID (OCID) of the Visual Builder service Virtual Cloud Network (VCN) for traffic exiting Visual Builder. Process Outbound IP: IP address for traffic exiting Process Automation. You'll need these values to update your allowlists for your firewall and the server that hosts your connectivity agent.
Upgrade Notifications	By default, upgrade notifications are automatically sent to the listed 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 Add the distribution list, group email, or any other stakeholders who should receive upgrade notifications, by entering their email addresses, separated with commas (,) in the box Upgrade Notifications. Oracle will include these email addresses in all future upgrade notifications.

Click Save changes.

As your upgrade date approaches, complete the pre-upgrade tasks.