8 Differences from Prior Versions of Oracle Integration
Features that are available in prior versions of Oracle Integration may not be available in Oracle Integration 3. These features may be permanently removed, replaced, enhanced, or not currently supported in Oracle Integration 3.
This page is updated when features become available in Oracle Integration 3.
Changes Between Oracle Integration Generation 2 and Oracle Integration 3
Audience | Features in Prior Versions of Oracle Integration | Equivalent or Enhanced Features in Oracle Integration 3 |
---|---|---|
Administrator |
User interface pages for:
|
|
Administrator |
Specifying how long to retain data and whether to purge data when low space is reached (available under Settings, then Data Retention in Oracle Integration Generation 2). |
Oracle now handles this responsibility. See Oracle and Customer Responsibilities in Oracle Integration 3 in Provisioning and Administering Oracle Integration 3. |
Administrator |
Choosing the update window for an instance using tags. |
The shape of an instance now determines its update window. For new instances created in Oracle Integration 3, the person who created the instance chooses the shape during provisioning. For instances that you upgrade from Oracle Integration Generation 2, an administrator chooses the shape while scheduling the upgrade. |
Administrator |
Creating an instance in a region other than your home region. |
To create an Oracle Integration Generation 2 instance in a region other than your home region, you first had to subscribe to the region in the Oracle Cloud Infrastructure Console. For Oracle Integration 3 instances, the ability to create instances outside your home region depends on several factors. See Restrictions in Provisioning and Administering Oracle Integration 3. |
Administrator |
Custom endpoint. |
In Oracle Integration 3, runtime access to your integrations will use the custom endpoint with no redirection. For all other access points—design-time, Visual Builder, Process Automation—you still access the custom endpoint, but the custom endpoint then redirects to the appropriate URL. If you used an SSL certificate with your custom endpoint in Oracle Integration Generation 2, you'll need to set up a load balancer as a front end for your service instance, and remove the SSL certificate. Currently, Oracle Integration 3 doesn't support alternate custom endpoints or using Visual Builder with a custom endpoint. See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration 3. |
Administrator |
The Reports section of the Notifications page includes selections for critical health alert, integration errors, hourly status, and daily status reports. |
The Reports section of the Notifications page only includes selections for hourly and daily reports. |
Developer |
Activity stream download API and download option on the Integration dashboards page under the View menu. |
The activity stream has been greatly enhanced and can be viewed and downloaded from the Instances page, Instance Details page, and Errors page. |
Developer |
In Oracle Integration Generation 2, the on-premises connectivity agent is certified with JDK 8, 11, and JDK 17. Note: To comply with Oracle security standards, JDK 8 and JDK 11 are deprecated. See System Requirements. |
In Oracle Integration 3, the on-premises connectivity agent must use JDK 17. |
Developer |
When making an API call with the REST Adapter, you encode the integration identifier
with
%7C . For example:
|
When making an API call with the REST Adapter, you encode the integration identifier
with a pipe (
| ) symbol. For
example:
|
Developer |
The system-generated instance ID that is displayed on the Instances page and in the activity stream for an integration instance is a numeric value. |
The system-generated instance ID for an integration instance has changed from a numeric value to an alphanumeric value. This may affect any systems that you use that rely on the instance ID being a numeric value. For example, if you parse the instance ID from a REST API and store the instance ID in a database as a number field, you'll need to update the database field. The data type of the value in Oracle Integration remains unchanged and is a string. See Adapting to Instance ID Changes when Upgrading to Oracle Integration 3. |
Developer |
Integrations declared the policy information in the WSDL. |
Integrations no longer declare the policy information in the WSDL. This impacts the Oracle Logistics Adapter and Oracle Transportation Management (OTM). To support this and any external WSDLs that do not declare an
attached policy, but need to be accessed through a WSDL URL,
configure the following properties:
See Oracle Fusion Cloud Transportation and Global Trade Management. |
Not Currently Available in Oracle Integration 3
Audience | Features in Prior Versions of Oracle Integration |
---|---|
Administrator |
The following user interface pages under Settings, then Integrations:
|
Developer |
You cannot invoke a process from an integration. |
Developer |
The following recipes: Note: Select another recipe from the Integration Store. See Recipes and Accelerators. |
Developer |
The Expression Builder is not available on the Configure Operation on Table page of the Adapter Endpoint Configuration Wizard for the following adapters:
Use the SQL Query field on the same page to add any necessary parameters or arguments. |
Not Supported in Oracle Integration 3
Audience | Features in Prior Versions of Oracle Integration | Alternatives in Oracle Integration 3 |
---|---|---|
All |
Insight capability |
Use Oracle Cloud Infrastructure Logging Analytics and Process Automation Analytics. |
Administrator |
Visual Builder instance administrator tasks:
|
No alternative. |
Administrator |
B2B instance administrator tasks:
|
No alternative. |
Administrator |
The following
|
No alternative. |
Administrator |
The REST API, command line interface (CLI) tool, and terraform script for creating an Oracle Integration instance include a parameter for enabling the file server. This parameter is not applicable in Oracle Integration Generation 3. |
Enable the file server from the Oracle Cloud Infrastructure Console after creating the Oracle Integration instance. |
Developer |
Reporting incidents for problematic issues that occur during design time. |
No alternative. |
Developer |
Basic routing integration style. |
Create schedule or application integrations. Before you can upgrade from Oracle Integration Generation 2 to Oracle Integration 3, you must migrate your basic routing integrations to application integrations. If you attempt to manually import an exported Oracle Integration Generation 2 basic routing integration into Oracle Integration 3, it is automatically converted to an application integration. |
Developer |
File transfer integration style. |
Create a schedule integration. |
Developer |
REST Adapter - Metadata Catalog URL, Swagger Definition URL, and RAML Definition URL connection types. |
Developers with a REST API that is described using RAML or the Oracle metadata catalog must take the following action:
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. See Configure Connection Properties for Invoke Connections in Using the REST Adapter with Oracle Integration 3. |
Developer |
The following adapters are not available in Oracle Integration 3:
|
For the Automation Anywhere Adapter and UiPath Robotic Process Automation Adapter, use the REST API-based approach available with the technical adapters. You can also select another adapter to use from our growing portfolio of hundreds of adapters. See Adapters. Additionally, robotic process automation (RPA) capabilities are also available in Oracle Integration 3. See Learn About Robots and Build a Robot in Using Robots in Oracle Integration 3. |
Developer |
Oracle NetSuite Adapter TBA authorization flow security policy support. |
No alternative. |
Developer |
Delayed (asynchronous) response support in the following adapters:
|
No alternative. Note the following behavior in Oracle Integration 3:
|
Developer |
The AS2 Adapter available in the Standard edition can only be used in standalone mode in existing integrations upgraded from Oracle Integration Generation 2 (for example, for file transfer protocol use cases not using B2B features). |
Use the AS2 Adapter with B2B features such as the B2B action, B2B design time, and B2B runtime. These features require use of the Enterprise edition in Oracle Integration 3. |
Developer |
Use of basic authentication with the Oracle-provided REST APIs. |
Use OAuth with the Oracle-provided REST APIs instead. For more information on authentication method support, see When is Basic Auth Supported in Oracle Integration 3. For more information on the Oracle-provided REST APIs, see APIs and CLI. |
Developer |
The Oracle Asserter testing framework for recording tests of integration instances and replaying them to reproduce potential issues. |
No alternative for recording instances for replay. Use the Configure and run page to test REST Adapter trigger connection-based integrations and scheduled integrations. See Test REST Adapter Trigger Connection-Based Integrations and Run a Schedule Integration Immediately in Using Integrations in Oracle Integration 3. |