5. Complete Post-Upgrade Tasks
Oracle upgrades your Oracle Integration Generation 2 development instances first. Complete all post-upgrade tasks within three days of the upgrade date, so that you can report any issues. Oracle upgrades your production instances about two weeks after your development instances.
Completing post-upgrade tasks is critical to make sure users can access the new instance, data going to and from integrations can be sent through the firewall, and integrations work as expected.
If you experience any issues after the upgrade, enter a service request (SR) on My Oracle Support or troubleshoot the issues. See Troubleshoot Upgrade Issues.
Note:
You'll see your stopped Oracle Integration Generation 2 instance in the Oracle Cloud Infrastructure Console for a period of time after the upgrade. Do not update, start, or delete this instance. Oracle removes it on your behalf when it is no longer needed.Summary of Post-Upgrade Tasks
Impact | When | Tasks to complete |
---|---|---|
Ensure access to the instance |
Immediately after upgrade |
|
Ensure connectivity |
Immediately after upgrade |
|
Ensure integrations work |
Immediately after upgrade |
|
Complete migration to Process Automation |
Immediately after upgrade |
Complete Post-Upgrade Tasks for Process Automation |
Follow your organization's procedures |
Within two weeks of upgrade |
Complete your organization's post-upgrade verification tasks |
Ensure access to the instance
Task | Who | When | Tasks to complete |
---|---|---|---|
Check the new Oracle Integration 3 instance |
Administrator | Immediately after upgrade | Sign in to your Oracle Integration 3 instance using your existing credentials. Your Oracle Integration 3 instance is in the same compartment and region as your Oracle Integration Generation 2 instance.
Use your existing Oracle Integration Generation 2 bookmark(which redirects to the new URL) or use the new URL for the Oracle Integration 3 instance. See Access an Oracle Integration Instance. The upgrade completed if:
The upgrade is still in progress if:
|
Update the IAM policy with the new OCID |
IAM policy administrator |
Immediately after upgrade | If your organization restricts access to the Oracle Integration Generation 2 instance based on the OCID value that uniquely identifies your instance, update the IAM policy so that it points to the new Oracle Cloud ID (OCID) for the Oracle Integration 3 instance.
Caution: If your IAM policy restricts access based on OCID, users will not be able to sign in until after you perform these steps.Find the new OCID in the Oracle Cloud Infrastructure Console after the upgrade is finished. For information about updating the IAM policy, see About IAM Policies for Oracle Integration and Creating an IAM Policy. |
Configure an IAM policy for Visual Builder |
Administrator | Immediately after upgrade | If you used Visual Builder in Oracle Integration Generation 2, you'll need to configure IAM policies for Visual Builder in Oracle Integration 3. See Set the IAM Policy for Managing the Visual Builder Instance for details. |
Configure the Oracle Integration 3 allowlist with the Visual Builder service VCN OCID |
Administrator | Immediately after upgrade | If you used Visual Builder and configured allowlist or network access rules in Oracle Integration Generation 2, you'll need to add the Visual Builder service VCN OCID in Oracle Integration 3. See Allow Your Instance to Access Services in Administering Oracle Visual Builder Generation 2. |
Get the URL for the new instance and share it |
Administrator | Immediately after upgrade | Get the URL for the new Oracle Integration 3 instance and share it with everyone who needs it. Existing bookmarks also redirect to the new URL, but you want to make sure everyone has the new URL.
|
Ensure connectivity
Task | Who | When | Tasks to complete |
---|---|---|---|
Complete network rules configuration |
Network administrator | Immediately after upgrade | If required, complete any network rules configuration, including adding the Oracle Integration Service VCN as part of the network rule.
This step is required if you use an Oracle Cloud Infrastructure service that supports network rules as a target of an integration connection, such as Oracle Cloud Infrastructure Object Storage or Oracle Autonomous Database, and you have enabled the network rules.
|
Upload a new identity certificate for connections |
Developer with connections that use identity certificates | Immediately after upgrade | Upload a new identity certificate, test the connections that use the identity certificate so their status changes from Draft to Configured, and activate any integrations that use the connections.
Only one person from each organization needs to perform these steps, and only if you have connections that use identity certificates.
|
Regain connectivity with agents that weren't upgraded |
Developer with agents that weren't upgraded | Immediately after upgrade | Agents that are offline during upgrade or don't meet upgrade requirements won't be upgraded. After upgrade, if you see a message stating that some agents didn't meet upgrade eligibility and weren't upgraded, perform the following steps.
Prerequisites Ensure connectivity from your connectivity agents to Oracle Identity Cloud Service (IDCS) and Oracle Integration 3:
To regain connectivity with your agents:
|
File Server: update integrations and SFTP clients to use the new IP and port values |
File Server administrator and developer | Within one week of upgrade | If you use File Server, update your integrations and SFTP clients so that they use the new IP and port values.
The Oracle Integration Generation 2 IP and port values continue working for four months after the upgrade, and then Oracle retires them. However, Oracle recommends updating your integrations and SFTP clients to use the new values now. That way, you don't risk forgetting to update these values in the future.
|
Ensure integrations work
Task | Who | When | Details |
---|---|---|---|
Change Oracle Integration built-in API calls from Basic Authentication to OAuth |
Developer | Immediately after upgrade | In Oracle Integration Generation 2, you can use Basic Authentication to use the Oracle Integration REST API and File Server REST API. In Oracle Integration 3, you must use OAuth. You'll need to update any clients, scripts, integrations and commands that use the Oracle Integration REST API or the File Server REST API to connect using OAuth. For more information on authentication method support, see When is Basic Auth Supported in Oracle Integration 3. For more details on using OAuth with the REST API, see Security, Authentication, and Authorization. |
Check integrations if you selected Ignore activation failures or Ignore start schedule failures |
Administrator | Immediately after upgrade | When you specified the upgrade requirements, if you opted to proceed with the upgrade even if Oracle couldn't activate an integration or restart a schedule, take the appropriate steps:
For information about these settings, see 2. Schedule the Upgrade and Configure Settings. |
Follow your organization's verification procedures
Task | Who | When | Details |
---|---|---|---|
Complete your organization's post-upgrade verification tasks |
Designated team members | Within two weeks after upgrade | Complete your organization's post-upgrade verification tasks, such as performing regression testing.
If needed, take action for requests that any clients sent to Oracle Integration during the downtime. Oracle Integration rejected all requests that were sent during the downtime. |