Agent Java Version

1. For any connectivity agent that isn't already using JDK 17, install JDK 17 on the server that hosts the agent.
2. For any agent that is still using the JKS KeyStore, convert the KeyStore to PKCS12 KeyStore. You can do the conversion in one of two ways:
   • Automatically, during upgrade: Your JKS KeyStore will automatically be converted to the PKCS12 KeyStore during upgrade.
   • Manually, before upgrade: You can convert the JKS KeyStore to the PKCS12 KeyStore manually, before upgrade, by following the steps below.
   Note
   
   Converting the JKS KeyStore to the PKCS12 KeyStore doesn't impact your Oracle Integration Generation 2 connectivity agent, and only takes effect after you have upgraded to Oracle Integration 3.

   If you want to manually convert your JKS KeyStore to the PKCS12 KeyStore, complete the following steps before upgrade. These tasks require you to briefly stop and then restart the connectivity agent, so choose a time when the connectivity agent isn't being used.

   1. 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

   2. Move the backup file to a different folder.
   3. 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

   4. Stop the connectivity agent.
   5. Delete the keystore.jks file in the following location:

      Agent_Install_Location/agenthome/agent/cert

   6. Start the connectivity agent.

Agent Connectivity for Oracle Integration 3 - Connectivity agent must be running

Agents that aren't reachable during upgrade or don't meet upgrade requirements won't be upgraded, in which case you'll need to perform post-upgrade steps to regain connectivity.

Agent Connectivity for Oracle Integration 3 - Update your allowlist settings

As your upgrade window approaches, perform the following pre-upgrade tasks:

• Add the IP address for Oracle Identity Cloud Service (IDCS) to the allowlist.
• Add the design-time and runtime 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.

Agents that aren't reachable during upgrade or don't meet upgrade requirements won't be upgraded, in which case you'll need to perform post-upgrade steps to regain connectivity.

Unsupported AgentGroup Identifier

Custom Endpoint URL

• If you're using Visual Builder:
  1. To proceed with upgrade, complete the Visual Builder Pre-Upgrade Tasks.
  2. During upgrade, the upgrade process configures your custom endpoint and any alternate custom endpoints in Visual Builder.
  3. After upgrade, if you need a custom endpoint for your Oracle Integration 3 instance, you must configure it. See Configure a Custom Endpoint for an Instance.
• If you're not using Visual Builder and you have alternate custom endpoints, delete them from your Oracle Integration Generation 2 instance. Oracle Integration 3 currently doesn't support alternate custom endpoints.
• If you're not using Visual Builder and your custom endpoint uses SSL:
  1. To proceed with upgrade, set up a load balancer in front of your Oracle Integration Generation 2 instance and remove the SSL certificate.
  2. During upgrade, the upgrade process configures your custom endpoint in Oracle Integration 3.
  3. After upgrade, runtime access to your integrations will continue to work as it did for Oracle Integration Generation 2. For all other access points—such as design-time and Process Automation—you still access the custom endpoint, but the custom endpoint then redirects to the appropriate URL.
• If none of these situations apply and this precheck passed, the upgrade process configures your custom endpoint in Oracle Integration 3, and the custom endpoint will work as described in the previous bullet for the SSL scenario.

Instance ID Action

If you have integrations that use instance IDs, the precheck shows a warning. Expand More details to see the integrations that need review. To copy the details to the clipboard, click .

Update your systems and processes as required. See Adapting to Instance ID Change when upgrading to Oracle Integration 3.

Note: This precheck just checks for the existence of integrations that use instance IDs, not the accuracy of the instance IDs. The warning will remain after you update your integrations, but doesn't impact your upgrade.

Daily Email Limit

Custom scopes in IDCS

Other Failures

B2B Retention Period

After upgrade to Oracle Integration 3, you'll have the ability to increase the data retention period if you want (may incur extra cost); or upgrade to the Healthcare edition, which supports 184 days of data retention.

Delayed (Asynchronous) Response

• Oracle CX Sales and B2B Service Adapter
• Oracle ERP Cloud Adapter
• Oracle HCM Cloud Adapter
• Oracle Field Service Cloud Adapter
• Salesforce Adapter
• ServiceNow Adapter

Expand More details to see which integrations need review. To copy the details to the clipboard, click .

Identity Certificates

Expand More details to see the names of the identity certificates and the connections that use them. To copy the details to the clipboard, click .

If you have identity certificates, after the upgrade, you'll need to upload new identity certificates as described in Ensure Connectivity:

Basic Routing Duplicate App Name

1. Edit your basic routing integration, deleting the target endpoint, and adding it again with a different name.
2. Save your integration.

Expand More details to see the integrations that need review. To copy the details to the clipboard, click .

Multiple Read File

If you have integrations that include an operation to read multiple files, rework the integrations so that they don't use this pattern. For example, use a listFile operation to list the files, and use a for-each action to read each file individually. Expand More details to see the integrations that need review. To copy the details to the clipboard, click .

Publish/Subscribe Integrations

If your instance includes integrations that publish messages or subscribe to messages from Oracle Integration, be aware that publish/subscribe (or pub/sub) integrations need to be converted to event-driven orchestrations. The integrations will be handled differently depending on their configuration:

• Pub/sub integrations that use attachments can't be automatically converted at this time. If you want to proceed with upgrade, you can either remove these integrations or ignore precheck failures. After upgrade, you can recreate them, pushing the attachment into the FTP server or Object Storage in your tenancy and passing the reference to the subscriber flow. See Define Header-Based Subscription Filtering in Using Integrations in Oracle Integration 3.
• All other active pub/sub integrations are automatically converted during upgrade. Pub/sub integrations in a draft state can't be migrated, and will be blank post-upgrade.
• If you've mapped data in the subscriber flow, the mappings are converted as accurately as possible. However, after upgrade, you should review the mappings and correct them if necessary.
• If you see the error Only Subscribers are present, no Publishers, you have orphan subscribers that must be deleted before upgrade.

Expand More details to see the integrations that can't be automatically converted. To copy the details to the clipboard, click .

Note: You might want to take this opportunity to delete any draft Publish flows.

DT API Basic Auth to OAuth action

In Oracle Integration Generation 2, you could use Basic Authentication to use the Oracle Integration REST API and File Server REST API. In Oracle Integration 3, you must use OAuth. You 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 details on using OAuth with the Oracle Integration REST API, see Security, Authentication, and Authorization, or with the File Server REST API, see Security, Authentication, and Authorization.

Custom Adapters

Oracle Utilities Adapter

Unsupported Adapters

• Automation Anywhere Adapter
• Evernote Adapter
• Oracle Messaging Cloud Service Adapter
• Oracle Monetization Cloud Adapter
• Oracle Taleo Business Edition (TBE) Adapter
• UiPath Robotic Process Automation Adapter

  Note: Robotic process automation (RPA) capabilities are available in Oracle Integration 3. See Learn About Robots and Build a Robot in Using Robots in Oracle Integration 3.

Expand More details to see which unsupported adapters you're using. To copy the details to the clipboard, click .

Unsupported REST Types

• Metadata Catalog URL
• Swagger Definition URL
• RAML Definition URL

Expand More details to see which unsupported REST types you're using. To copy the details to the clipboard, click .

Another option is to convert RAML into an OpenAPI specification to use with the REST Adapter connection.

To provide more robust and complete support for the Swagger/OpenAPI specifications, the REST Adapter includes a unified option to specify all OpenAPI specifications in a single field. This option also replaces the option to provide a Swagger definition URL, which is no longer available.

Custom Endpoint URL

If you have a custom endpoint and you're using Visual Builder:

1. To proceed with upgrade, complete the Visual Builder Pre-Upgrade Tasks.
2. During upgrade, the upgrade process configures your custom endpoint and any alternate custom endpoints in Visual Builder.
3. After upgrade, if you need a custom endpoint for your Oracle Integration 3 instance, you must configure it. See Configure a Custom Endpoint for an Instance.

VBCS

Make sure to complete the additional tasks described in Prepare Visual Builder for the Upgrade in Administering Oracle Visual Builder in Oracle Integration 3.

Process Automation

There are several differences between Process in Oracle Integration Generation 2 and Process Automation in Oracle Integration 3. See Process FAQs.

Depending on how you're using Process in Oracle Integration Generation 2, you'll use a different option to upgrade or migrate. See Process Upgrade Options.

Process Action

If you're using the Process action in any integrations, you'll need to replace or remove the Process action prior to upgrade. Use the method described in the Process upgrade option that applies to your situation.