Limitations

Learn about the limitations post upgrade.

Oracle Integration 3

Process

After upgrade, for design-time artifacts, you need to update the web service URL manually. Otherwise, you might encounter an error. See Post-Upgrade Tasks.
After upgrade, if you try to reactivate any existing processes with an integration that was configured to use Propagate Identity before the upgrade, you will encounter an error indicating that no security is configured. The workaround is to select Basic Security.

Visual Builder

Oracle Integration Generation 2 processes will no longer be discoverable or available to call in action chains. You need to use Oracle Integration 3 Process for all new Visual Builder development initiatives.
Existing applications that reference Oracle Integration Generation 2 Process will continue to work after following the prerequisites.

Integration

Design-time discovery for Process instances with complex schema definitions is not supported. After upgrading, if your processes contain complex schemas, then there might be errors or failures if you try to generate artifacts.
Schedule integrations with a process action calling Process are not automatically started after upgrade. You need to start these schedule integrations after upgrade.

Lifecycle Management

The Oracle Integration 3 instance should not be deleted or shut down when Oracle Integration Generation 2 Process is active. If it is deleted or shut down, it will prevent the network traffic via the original URL from reaching the Oracle Integration Generation 2 instance.

Insight

Insight will not be available in Oracle Integration 3.
Calls from Process to Insight will not be supported after the upgrade. Processes with Insight activities will continue to run (and no failure will occur on Insight activity), but as Insight is not available in Oracle Integration 3, no Insight data will be available.

Oracle Integration Generation 2

Process

No new development work should occur.
Integration connectors will only support the generic credentials security policy.
Process calls to Insight will no longer be supported after the upgrade.
Dynamic Process calls using the integrations activity will not work after the upgrade. Oracle Integration Generation 2 Process does not show any error and erroneously indicates that the integration call is successful although it is not successful. You can reconfigure these calls to use the Service Task (calling the REST trigger on Oracle Integration 3).
If there are any dynamic processes calling integrations using Generic Credentials as security, it will result in failures at runtime.
Process Analytics will no longer be available after the upgrade. However, you can see the number of open instances per application using a new report that is available if you navigate to Process, Administration, and then Migration Report.
REST triggers in integrations called by processes need to be set up with Basic Auth or OAuth and Basic Auth security policy. If you have processes calling an integration with a REST trigger that is configured only with OAuth security policy, you will need to update it to use OAuth and Basic Auth or Basic Auth to avoid failures after upgrade.

Lifecycle Management

You will no longer be able to manage (perform Lifecycle Management operations such as start/stop or update network access control lists) on the Oracle Integration Generation 2 instance after the upgrade.
You will no longer see metric data (such as inbound/outbound requests, consumed messages, processing time metrics, and so on) for your Oracle Integration Generation 2 instance.

Integration

Integration and related features such as File Server and B2B will no longer be available.

Visual Builder

Insight