5. Complete Post-Upgrade Tasks

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	Check the new Oracle Integration 3 instance Update the IAM policy with the new OCID Configure an IAM policy for Visual Builder Configure the Oracle Integration 3 allowlist with the Visual Builder service VCN OCID Get the URL for the new instance and share it
Ensure connectivity	Immediately after upgrade	Complete network rules configuration Upload a new identity certificate for connections File Server: update integrations and SFTP clients to use the new IP and port values Complete this task within one week of upgrade. Regain connectivity with agents that weren't upgraded
Ensure integrations work	Immediately after upgrade	Change Oracle Integration built-in API calls from Basic Authentication to OAuth Check integrations if you selected Ignore activation failures or Ignore start schedule failures
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: You sign in and the user interface is different from Oracle Integration Generation 2. Check the version number in the About dialog. The upgrade is still in progress if: You sign in and the user interface is the same as in Oracle Integration Generation 2. You sign in and a page indicates that the service is unavailable.
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. Sign in to the Oracle Cloud Infrastructure Console. Open the navigation menu and click Developer Services. Under Application Integration, click Integration. Click the name of the new Oracle Integration 3 instance. To the right of the Service console URL field, click Copy. Share the URL with anyone who needs it.

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. Sign in to Oracle Cloud Infrastructure Console. Get the OCID value for the Oracle Integration 3 instance. See Viewing Instance Details. Follow the rules for your target service, such as Configure Access Control Lists When You Provision or Clone an Instance in Using Oracle Autonomous Database Serverless. If the Oracle Cloud Infrastructure service you are accessing is in a different region than your Oracle Integration instance, allowlist the egress IP address.
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. Upload a new identity certificate. See Upload an SSL Certificate in Using Integrations in Oracle Integration 3. Test the connections that use the identity certificate so that their status changes from Draft to Configured. See Test the Connection in Using Integrations in Oracle Integration 3. Activate any integrations that use the connections. See Activate an Integration in Using Integrations in Oracle Integration 3.
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: You should have added the IDCS URL and the Oracle Integration 3 IP addresses and URLs to the allowlists prior to upgrade, as described in 3. Update Allowlists and Complete Pre-Upgrade Tasks. Add the Oracle Integration 3 design-time IP address to the allowlists. Use the following command to get the design-time IP address, replacing `region` with the region from your Oracle Integration 3 URL: `nslookup design.integration.region.ocp.oraclecloud.com` To regain connectivity with your agents: Stop the connectivity agent. Make sure that the agent prerequisites are complete: Ensure that the connectivity agent is using JDK 17. If it isn't, set the `JAVA_HOME` and `PATH` environment variables to `JDK17`. Ensure that the agent is using the PKCS12 KeyStore. If it isn't, convert it using the following steps. On the server that hosts the connectivity agent, create a backup of the `keystore.jks` file, which is located in the following folder: `Agent_Install_Location/agenthome/agent/cert` Move the backup file to a different folder. Convert the JKS KeyStore to the PKCS12 KeyStore by running the following command from the command line: `keytool -importkeystore -srckeystore keystore.jks -destkeystore keystore.p12 -srcstoretype JKS -deststoretype PKCS12 -deststorepass changeit -srcstorepass changeit` Delete the `keystore.jks` file in the following location: `Agent_Install_Location/agenthome/agent/cert` Download the agent installer ZIP file from Oracle Integration 3. In the navigation pane, click Design, then Agents. Click Download, then Connectivity agent. Extract `oic_conn_agent_installer.zip` to a new directory on your connectivity agent server. Delete your existing connectivity agent `lib` folder under `Agent_Install_Location/agenthome/` and replace it with the `lib` folder from the ZIP file. Delete your existing `version` file under `Agent_Install_Location/agenthome/` and replace it with the `version` file from ZIP file. Delete your existing `connectivityagent.jar` file under `Agent_Install_Location` and replace it with the `connectivityagent.jar` file from ZIP file. Delete your existing `cpi_upgradeutility.jar` file under `Agent_Install_Location` and replace it with the `cpi_upgradeutility.jar` file from ZIP file. In Oracle Integration 3, on the Agents page, hover over the agent group, click Actions , then select Download config. This step downloads a preconfigured `InstallerProfile.cfg` file for the agent group. Delete your existing `InstallerProfile.cfg` file under `Agent_Install_Location` and replace it with the `InstallerProfile.cfg` file you downloaded in the previous step. Restart the connectivity agent by running the following command: `java -jar connectivityagent.jar` Reactivate the integrations that are in the upgraded agent group.
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. In the navigation pane, click Settings, then File Server, then Settings. Under General, obtain the IP and port values for the File Server SFTP server. Update all integrations that call File Server so that they use the new IP and port values. Update all SFTP clients so that they use the new IP and port values.

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: If you selected Ignore activation failures, check the status of all your integrations, and activate integrations as needed. If you selected Ignore start schedule failures, check the schedules of your integrations, and manually start them if needed. 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.

Oracle Cloud Infrastructure Documentation