Complete Pre-Upgrade Tasks
There are several tasks you must complete as your upgrade date approaches to prevent errors during upgrade and to allow you to smoothly transition to the new Oracle Integration 3 instance after upgrade.
Summary of Pre-Upgrade Tasks
This table summarizes the pre-upgrade tasks for each area. The details for each task are linked in the table and shown in the next sections.
| Area | Tasks |
|---|---|
| Connectivity Agent | |
| Instances | |
| B2B for Oracle Integration | |
| Integrations | |
| Adapters | |
| Visual Builder | |
| Allowlists | |
| Communication | |
| Development work |
Connectivity Agent Pre-Upgrade Tasks
| Task | Typical owner | Tasks description |
|---|---|---|
|
Prepare for conversion to OAuth 2.0 |
Development Operations team | In Oracle Integration Generation 2, the connectivity agent uses basic authorization to invoke Oracle Integration endpoints. Oracle Integration 3 instead uses OAuth 2.0 token-based authentication, which is more secure. During the upgrade, your connectivity agents connections are automatically converted from using basic authentication to using OAuth 2.0, so you don't need to manually recreate any connections yourself.
However, before upgrade you must prepare for this conversion by allowing egress from the agent network to Oracle Integration design-time and runtime, and to the Oracle Identity Cloud Service or the identity domain as described in Update Allowlists. And, after upgrade, as a result of the new authentication method, you'll see additional traffic to your firewall. This additional traffic occurs because the connectivity agent must communicate with the server to get new tokens. For more information on OAuth 2.0 support in Oracle Integration 3, see When is Basic Authentication Supported in Oracle Integration 3?. |
|
Update your allowlist settings |
Development Operations team | If your organization uses allowlists, you must update your allowlist settings for your connectivity agents. The Allowlist status column in the Connectivity Agent Status section shows the status of all the connectivity agents in your instance, indicating whether the allowlist has been updated appropriately.
As your upgrade window nears, perform the tasks described in Update Allowlists. Agents that are offline 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. |
|
Set the proxy server's Cache property |
Development Operations team | Set your proxy server's Cache property for the Oracle Integration URLs to refresh as frequently as possible.
For example, if your proxy server uses the |
Instance Pre-Upgrade Tasks
| Task | Typical owner | Tasks description |
|---|---|---|
|
Start capturing the activity stream in Oracle Cloud Infrastructure Console |
Administrator | If you don't already, start capturing the activity stream in Oracle Cloud
Infrastructure Console.
Here's why: The activity stream isn't migrated. But if you capture this data in the Oracle Cloud Infrastructure Console, you'll still have access to historical data. See Capture the Activity Stream in Oracle Cloud Infrastructure Console. |
B2B for Oracle Integration Pre-Upgrade Tasks
| Task | Typical owner | Tasks description |
|---|---|---|
|
Ensure all B2B passwords for keystore match |
Administrator | Ensure that all passwords for the keystore file are identical. Your identity certificate file (JKS) requires two sets of passwords: Key Passwords and Keystore Password. All the passwords must be identical. If they're not identical, edit the passwords to match, and re-upload the keystore file.
If you don't have the keystore file that was last uploaded, recreate the file. When uploading the certificate:
See Upload an SSL Certificate in Using Integrations in Oracle Integration Generation 2. Caution: If you don't complete this step, the upgrade will fail. |
Integrations Pre-Upgrade Tasks
| Task | Typical owner | Tasks description |
|---|---|---|
|
Determine what to do with failed instances |
Development Operations team | Failed integration instances fall into one of the following categories, which determines how you can handle them:
Note: If you capture activity stream data in the Oracle Cloud Infrastructure Console, you can still view historical activity for the integration. See Capture the Activity Stream of Integrations in the Oracle Cloud Infrastructure Console. |
|
Decide what to do with asynchronous messages |
Development Operations team | Decide what to do with asynchronous messages from the client side for the duration of the downtime.
Here's why: During the downtime, Oracle Integration rejects all incoming requests. To prepare, you have the following options:
|
|
Ensure your Visual Builder applications call APIs from Integrations REST endpoints |
Development team | If you created Visual Builder applications by creating a service connection from the catalog and they call REST APIs other than Integrations REST Endpoints, you must rewrite the applications by creating a service connection from the catalog, and the applications must use OAuth to authenticate. |
Adapters Pre-Upgrade Tasks
| Task | Typical owner | Tasks description |
|---|---|---|
|
Stop using decommissioned Microsoft adapters |
Development team | Microsoft decommissioned the Microsoft Outlook REST APIs in November 2022. If you use any of the following adapters, you must use the Microsoft Graph REST APIs instead.
|
Visual Builder Pre-Upgrade Tasks
| Task | Typical owner | Tasks description |
|---|---|---|
|
Prepare VBCS for upgrade |
Development Operations team | If you use Visual Builder with your own Oracle database instance (BYODB), there are several steps you need to take to prepare for upgrade:
|