2. Schedule the Upgrade and Configure Settings

Your instance is ready for upgrade after you complete all prerequisites and the instance passes the upgrade check. Oracle sends you an email indicating that your instance is ready for upgrade. Oracle selects an upgrade window, but you can change it if the upgrade is more than seven business days away (detailed below).

After you receive the email, you configure upgrade settings and can reschedule the upgrade, if needed. Complete these steps after Oracle sends your scheduled upgrade date over email.

Prerequisites:

• If any upgrade checks fail, address the issues that apply to your instance, or the instance won't be scheduled for upgrade. For instructions on how to fix failed upgrade checks, see Complete Upgrade Prerequisites.
• If you haven't received an email and want to schedule your upgrade, you can enter a service request. For additional information, see How do I submit an upgrade request?.
• 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.

Steps:

1. Once your instance has passed the upgrade check, wait for Oracle to inform you that your upgrade has been scheduled.
   Oracle informs you that your instance is ready for upgrade in the following ways:

   • Click Settings, then click Upgrade to see your upgrade window.
   • An announcement appears in the interface.

     You can see the announcement if you're part of an administrator group.

   • Oracle sends an email, informing you that you're eligible for upgrade.

     Everyone who gets emails about Oracle Integration Generation 2 quarterly updates receives the email.

2. Review your upgrade window, change it if needed, and specify your requirements for the upgrade:
   1. In Oracle Integration, open the Upgrade page using one of the following methods:
      • In the navigation pane, click Settings, then Upgrade.
      • Click Announcements , and then click the link in the notification.
      
   2. On the Upgrade page, fill in the fields.

      Field	Description
      Ignore identity certificates during upgrade eligibility check	When selected, the upgrade proceeds, even if the instance contains connections that use identity certificates. After the upgrade, you'll need to upload new identity certificates into your Oracle Integration 3 instance, test the connections that use the identity certificate so their status changes from Draft to Configured, and activate any integrations that use the connections. If you do not select this field, the upgrade cannot proceed unless you manually delete the identity certificates.
      Upgrade Window	If your upgrade has been scheduled, you see your upgrade window. You can change your upgrade window if it's seven or more business days away. All upgrade dates that are available to you appear in the list. If you have multiple instances, choose your upgrade windows carefully. See Prerequisites When You Have 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.
      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. When you select Production and click Confirm to schedule your upgrade, you'll be prompted to confirm again that you want to upgrade your production instance and that you are satisfied with the testing you have 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 capabilities.
      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: 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. Caution: 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 URL and IP addresses. Perform the following updates: Add the URL for Oracle Identity Cloud Service (IDCS) to the allowlist. Add the runtime URL and IP addresses for Oracle Integration to the allowlist. Set the proxy server's Cache property for the Oracle Integration URLs to refresh as frequently as possible. 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.
      Skip process applications?	If you use the Processes capability but aren't using it in production, you have the option to skip process applications during upgrade. This approach is appropriate if you've tried Processes in non-production Oracle Integration Generation 2 environments but don't need or want to retain it in Oracle Integration 3. If you want to proceed with the upgrade, select Upgrade and lose process applications and runtime data. Note: If you see the option to skip process applications, but it's unavailable, you have process runtime transactions. If you want to proceed with upgrade at this time, export your process applications and remove your runtime transactions, as described in Complete Upgrade Prerequisites. If you have process in production, wait until Processes upgrade is supported. Importing process applications created in Oracle Integration Generation 2 into Oracle Integration 3 isn't currently supported. After upgrade, if you want to leverage process or decision capabilities, you can enable Process Automation with Oracle Integration 3.
      Allowlist IP Addresses	Two weeks before the upgrade, the ingress and egress IP addresses are available: Ingress IP Address(es): IP addresses for traffic entering into Oracle Integration 3. Egress IP Address(es): IP addresses for traffic exiting Oracle Integration 3. You'll need these values to update your allowlists for your firewall and the server that hosts your connectivity agent. To copy an IP address, click next to the address.
      Upgrade Notifications	By default, upgrade notifications are automatically sent to the listed admin email. Enter the email addresses of any additional stakeholders who should receive communications about the upgrade. Separate multiple email addresses using a comma (,). Oracle includes the stakeholders in all future communications for the upgrade.

   3. Click Save changes.
3. If you selected a different upgrade window, wait for the email that confirms that your requested window is available.
   Oracle emails a confirmation of the upgrade window that you selected. Everyone who gets emails about Oracle Integration Generation 2 quarterly updates receives the email.
4. Inform users and stakeholders about the upcoming upgrade.
   For example, consider completing the following tasks:

   • Share the date of the upgrade.
   • Ask everyone to limit their development work starting two days before the upgrade, if possible.

     If teams can't pause their work, the upgrade continues as planned. But, limiting your work can help ensure a successful upgrade.

   • Tell everyone to expect downtime during the upgrade window.
   • Plan and assign the tasks to complete before and after the upgrade.

     See 3. Update Allowlists and Complete Pre-Upgrade Tasks and 5. Complete Post-Upgrade Tasks.

If you rescheduled your upgrade, Oracle sends an email confirmation for the new date and time.

Two weeks before your upgrade date, Oracle shares your new ingress IP address(es). Use the values to update your allowlists. See 3. Update Allowlists and Complete Pre-Upgrade Tasks.

Three days before your upgrade date, Oracle locks your upgrade window.