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.
  • If you have Process applications calling integrations that use a trigger with no security policy, these integrations will fail after the upgrade with an error. To resolve this issue, ensure that any integrations called by Oracle Integration Generation 2 Process use a REST trigger connection of trigger type that supports the OAuth and Basic Auth security policy.

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 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 or only with Basic Auth security policy, you will need to update it to use OAuth and Basic Auth security policy to avoid failures after upgrade.
  • After the upgrade, when discovering integrations in a Process application, only integrations that use connections of trigger type are listed, and integrations that use connections of trigger and invoke type are not visible. To resolve this issue, use one of the following approaches:
    Workaround 1:
    1. Log in to Oracle Integration Generation 2 Process instance.
    2. In the navigation pane, click Processes, and then click Process Applications.

      The Process Applications page appears.

    3. On the Process Applications page, open the relevant Process application.
    4. In the drop-down list (that appears in the upper right corner of the page), select Integrations.
    5. Click the Integrations tab.
    6. In the upper right corner, click Create, click External, and then click SOAP or REST.

      If you clicked SOAP, in the Add Service Connector dialog, complete the following steps:

      1. Specify the WSDL URL.

        Note:

        You can also select an existing definition from the drop-down list or upload a WSDL from your local machine.
      2. Click Next. This step validates WSDL.
      3. If validation of WSDL is successful, you need to specify details about the connector:
        • In the Basic Properties section, specify a name for the connector, select a port type, select a callback port type, and click Next.
        • In the Advanced Properties section, complete the settings (including security credentials for the connector).
      4. Click Create.
      If you clicked REST, complete the following steps:
      1. In the Create REST Connector dialog, enter a name for the connector, specify the base URL of the integration, and then click Create.
      2. On the page that appears, in the Configuration section, click the Security tab.
      3. On the Security tab, specify the security credentials.
      4. At the top of the Resources section, click Add.
        1. Click the new resource that was added to the Resources list to expand it.
        2. Enter a name for the resource.
        3. In the Path field, specify the integration URL path. For example: /ic/api/integration/v1/flows/rest/PCS_example/1.0/items.
    7. Click Save.

      This new integration will be available in the Integrations section of this application.

    Workaround 2: Configure the connections in the integration to be of trigger type only.

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

  • Visual Builder will no longer be available.

Insight

  • Insight will no longer be available.