1. Known Issues for Oracle Integration Generation 2
  2. Integrations Issues

2 Integrations Issues

Review Integrations issues in Oracle Integration.

Topics:

Adapter Issues

Review known issues associated with adapters.

Topics:

Oracle Autonomous Transaction Processing Adapter Wallet Issue

For existing Oracle Autonomous Transaction Processing Adapter connections that connect through the connectivity agent when using the wallet, do not change the wallet until after February 2023 patching completes. Changing your wallet before then results in a runtime error.

If you need to create a new connection that connects through the connectivity agent when using the wallet, wait until February 2023 patching completes.

Performing Update Table Operation Against Multiple Tables with Relations May Cause Issues

When the Update Table operation is performed against two or more tables with relations in the Oracle Database Adapter, the records in the child table may be inserted or deleted. Therefore, if the input to the update contains only one detail record, the other detail records in the table are deleted.

Oracle Sales Cloud REST APIs Sometimes Do Not Appear in the Oracle Sales Cloud Adapter

Oracle Sales Cloud REST API services sometimes do not appear when using the Oracle Sales Cloud Adapter as an invoke connection in an integration.

As a workaround, perform the following steps:

  1. Create a new sandbox in Oracle Sales Cloud.

  2. Navigate to Common AppComposer Account > Fields > Test_c.

  3. Deselect the Include in Service Payload option.

  4. Navigate to Sales AppComposer.

  5. Edit Order_c > Fields > AccountId_c .

  6. Deselect the Include in Service Payload option.

  7. Repeat the same steps (deselect the Include in Service Payload option) for the following fields in Opportunity > Opportunity object > Fields.

    • Architect_c

    • Builder_c

    • Contractor_c

    • Designer_c

    • Installer_c

    • PriceBookName_c

  8. Publish the sandbox and test if the above calls are working now.

Oracle HCM Cloud Adapter ZIP File Issues

Note the following issues when using the Oracle HCM Cloud Adapter ZIP file feature:

  • A ZIP file that is extracted using the Oracle HCM Cloud Adapter must only contain a single file. If there are multiple files, only the file with the most recent time stamp is extracted.

  • The supported method for using the Oracle HCM Cloud Adapter ZIP file feature is to first zip your files, and then encrypt them.

Table Relationships Not Displaying by Default when Adding a MySQL Adapter Connection as an Invoke to an Integration

When adding a MySQL adapter connection as an invoke to an integration, the relationship between two related tables is not shown by default. This behavior also occurs when a foreign key is declared in one of the imported tables. A workaround is not available.

A Single Call with Multiple Updates is Not Supported with the SQL Server Adapter in Basic Map Data Integration Patterns

A single call with multiple updates is not supported with the SQL Server Adapter in basic map data integration patterns. In the case of multiple updates, use an orchestrated integration pattern or a basic map data integration pattern with enrichments.

REST Adapter Basic Authorization Security Policy Limitation

The REST Adapter Basic Authorization security policy does not have a token management and token refresh. If a token expires, you must test the connection in design time before proceeding. For example, if you have an integration that includes a REST Adapter and Google Calendar Adapter, and the Google Calendar token expires, this causes a failure.

As a workaround, perform one of the following steps:

  • Go to the Credentials dialog of the Connections page and click Provide Consent.

  • Use the OAuth Custom Three Lgged Flow security policy with a refresh token request.

Testing a REST Adapter Connection with the HTTP Basic Authentication Security Policy Does Not Validate the Credentials

Testing a REST Adapter connection configured with the HTTP basic authentication security policy and a role connection of Trigger and Invoke or Invoke does not validate the credentials and simply opens a connection to the provided URL. To validate the endpoint and credentials, the REST Adapter must invoke an API that is idempotent.

REST Adapter Does Not Support Services Returning Multipart Data

If you create a REST Adapter connection that returns multipart/mixed or multipart/form-data, you cannot design an integration with the REST Adapter as both the inbound and outbound connections because the response does not support both the multipart/mixed and multipart/form-data media types.

Redirect URL Constructed in an Expanded Domain Fails the Provide Consent Button

Redirect URI configuration with the REST Adapter is required for the following security policies: OAuth Authorization Code Credentials and OAuth Custom Three Legged Flow.

Use the following format when configuring the redirect URI for the client application:

https://ICS_HOST:ICS_SSL_PORT/icsapis/agent/oauth/callback

You must create a third party project before creating a connection with the REST Adapter using an OAuth Custom Three Legged Flow security policy.

  1. Go to the developer console for the third party application.

  2. Create a new application.

  3. Provide the Oracle Integration redirect URI inside the third party application.

    Enter the SSL URL for the OAuth callback for your Oracle Integration instance. The format is as follows: 

    https://ICS_HOST:ICS_SSL_PORT/icsapis/agent/oauth/callback

    For example, assume the URL you use to access your Oracle Integration instance is the following: 

    http://example.com:7001/ics/faces/global

    The SSL URL for the OAuth callback is likely to be the following:

    https://example.com:7002/icsapis/agent/oauth/callback

    Note:

    Application creation is specific to each vendor.

For an example of configuring the redirect URI with the Google Calendar Adapter, see Creating the Google Calendar Project.

Oracle E-Business Suite Adapter Issues

When using the Oracle E-Business Suite Adapter in an integration, you may encounter the following issues:

  • Trading partner setup form does not accept a password with special characters

    The Trading Partner Setup form does not accept a password with special characters. Therefore, the Oracle Integration password should be a combination of text and numbers.

    To resolve this issue, apply the following patches to enable Oracle XML Gateway to accept passwords with special characters:
    • For Oracle E-Business Suite Release 12.2, apply Patch 27752692:R12.ECX.C.
    • For Oracle E-Business Suite Release 12.1.3, apply Patch 28310667:R12.ECX.B.

  • Service invocation fails for certain PL/SQL APIs with table type input parameters

    When invoking certain PL/SQL APIs having table type input parameters, the following exception may occur:

    java.sql.SQLException: ORA-06531: Reference to uninitialized collection ORA-06512

    To resolve the exception, pass an empty element in the request corresponding to the table type in the API. For example, when invoking the PROCESS_BOM API with table type parameters P_BOM_REVISION_TBL, P_BOM_REF_DESIGNATOR_TBL, and P_BOM_SUB_COMPONENT_TBL, pass the empty tags as a workaround:

    1. Export the integration with the mappings for the Oracle E-Business Suite request.

    2. Locate the corresponding .xsl file to change the mapping entries for P_BOM_REVISION_TBL, P_BOM_REF_DESIGNATOR_TBL, and P_BOM_SUB_COMPONENT_TBL as follows: 

      <P_BOM_REVISION_TBL/>
<P_BOM_REF_DESIGNATOR_TBL/> 
<P_BOM_SUB_COMPONENT_TBL/>

    3. Import this modified mapping for the request mapping.

    4. Activate the integration and the API should be invoked successfully.

Siebel Application WSDL Validation Errors During Activation of Siebel Inbound Services

Siebel Application WSDL validation errors are thrown during activation of a few Siebel inbound services.

A Siebel application WSDL has duplicate element definitions with the same namespace. When you configure the Oracle Siebel Adapter, Siebel application WSDL validation errors are thrown during activation of these Siebel inbound services.

Workaround

Implement either of the following workarounds to resolve the validation errors.

  • Correct the WSDL in the Siebel application and reconfigure the integration flow in Oracle Integration so that the Siebel adapter picks the correct WSDL.

  • Deactivate the services in the Siebel Call center so that these services do not appear in the Siebel adapter operations page.

ERP System Does Not Add a Document ID in the JSON String When a Load Interface Job Fails

When a load interface job fails during an integration import, the ERP system adds the document ID in the JSON callback string. However, the document ID is missing from the ERP JSON payload. Therefore, the Oracle ERP Cloud Adapter cannot process the ERP callback payload.

Integration Issues

Review known issues associated with integrations.

Topics:

Import a Microsoft Intermediate Certificate into the Cacerts Store in Oracle Cloud at Customer Environments

If you are using the December 2022 release of Oracle Integration in an Oracle Cloud at Customer environment and have SOAP-related integration flows that reference schemas from schemas.xmlsoap.org, you must import a Microsoft intermediate certificate into the cacerts store.

This task is required because access to http://schemas.xmlsoap.org has been redirected to https://schemas.xmlsoap.org. Calls to https://schemas.xmlsoap.org fail with a PKIX exception if the required certificates are not available in the JDK trust store.
  1. Download and copy the msft.cer file into the Oracle WebLogic Server container.
    1. Download the certificate by visiting https://schemasxmlsoap.azurewebsites.net/soap/envelope/ and clicking the lock in the address bar.
    2. Once inside the Oracle WebLogic Server container, change directories to the following location.
      cd /u01/jdk/jre/lib/security
    3. Delete the certificate.
      sh -c "keytool -storepass changeit -delete -alias msicert -file
/oic_admin/certs/msft.cer -keystore $keystore_loc/cacerts"
    4. Import the certificate.
      sh -c "keytool -storepass changeit -import -alias msicert -file
/oic_admin/certs/msft.cer -keystore $keystore_loc/cacerts"
    5. Search for the imported file.
      sh -c "keytool -storepass changeit -list -keystore cacerts"

      Search for mscert in the output of this command to ensure that the certificate is imported.

  2. Check your SOAP-related integration flows.

Error Invoking Process Using Message Start with No Input Arguments

When invoking an activated process in an integration where the process uses a Message Start event, the Message Start must have input parameters (arguments) defined. If no parameters are present, a 400 Bad Request response status is returned..

Windows 10 Design-Time Issues

If you attempt to drag a connection into an integration when using the Chrome browser on Windows 10, the connection is not added. If you use Internet Explorer, a forbidden icon is displayed.

If you disable support for the touch screen and restart the browser, this issue goes away.

Notification Action Failure Does Not Impact an Orchestrated Integration Flow

If a notification action fails, the overall integration flow continues running past that action. The Tracking page shows a red icon for the corresponding notification action. A fault is logged, but not reported as a failure for the instance. If you view the error on the Tracking page, the fault is not shown.

Icon and Screen Text are Overlayed When Adblock Plus Extension is Enabled in Safari Browser

If you use the Safari browser with the Adblock Plus extension enabled, the icon and screen text that are displayed in the banner indicating the status of integration creation/editing are overlayed. Disable this extension to eliminate the problem.

Inner For-Each Actions Do Show the Badge and are Not Tracked in the Audit Trail in Successful Integrations

On the Tracking instance details page, activities inside a for-each action are not logged and any inner for-each action does not display the badge for a completed integration. The audit trail only shows a message saying that the outer for-each action started and ended. In case of failure (for example, the inner for-each action failed), the badge is displayed for the inner for-each action. The audit trail shows messages related to activities inside the for-each action up until the point of failure.

In addition, the lines are shown as dotted (...) inside the for-each action for a successful integration. For a failure inside a for-each action, solid lines are shown (in green) before the point of failure and the failed node and line before it are marked in red.

Using the Mapper with Touch Screen Interfaces on Windows 10

The mapper has a known issue with touch screen interferes when dragging and dropping components on Windows 10 hosts (for example, dragging and dropping connections from the Connections palette). Check if your Windows 10 host has touch screen enabled. If so, disable it.

API Library Issue

Note the following API library issue.

  • If you attempt to register and save an uploaded library without any functions on the Libraries page, you receive a null pointer exception error. Ensure that your uploaded library includes functions.

Configure a Global Fault to Prevent the Sending of Messages to the Error Hospital

You can configure a global fault in an orchestrated integration to prevent the sending of messages to the error hospital. You first delete the Error Hospital icon that is automatically added to a global fault, then perform either of the following options:

  • Add a Stop action, then add a Switch action. Note that the Stop action can be deleted. However, deleting the Stop action causes a confirmation dialog to be displayed. After confirming your decision, the Stop action being deleted is replaced with another Stop action automatically.

  • Add a Switch action. Note that a Stop action is added automatically, but it cannot be deleted and replaced with an Error Hospital icon.

If you want to get the Error Hospital icon back, you must recreate the integration (for example, delete and recreate the whole integration or delete every action in the integration until it is empty, and then add the Error Hospital icon back in).

Oracle Integration Message Delivery Does Not Work in XA Mode

Oracle Integration message delivery does not work in XA mode. There is a chance for duplicate messages to be delivered to the destination. This may occur when the managed servers go down or any other scenario in which the managed servers must be brought down when messages are being processed.

Used Icons are Not Displayed for Delayed Schema Loads on the Tracking Page

If you select an element for tracking on the Business Identifiers for Tracking page that is more than three levels deep (which requires clicking the Load more link), these elements are not marked with the green used icon after you save, exit, and then re-enter this page. This is a display issue only. If you attempt to redrag the element, an error is displayed indicating that this element is currently being tracked.

Preferences Are Cleared When Browser Cookies Are Deleted

Assume you select user_name > Preferences in the upper right corner of the page, select Show these options at sign in, save your changes, and log out. The next time you log in, the preferences page is displayed. However, if you log out and then delete all cookies in your web browser, the next time you log in, the preferences page is not displayed. This is because preferences are stored in the cookies of the browser. Clearing the cookies resets the preferences.

Inaccurate Error Message When Specifying a Large Number of Months for the Scheduling Frequency

When creating a schedule, if you manually enter a value of 10000000000 when specifying the number of months in the Frequency section, you receive a The number must be less than or equal to 2147483647 error message. You can only specify a value of 12 or less.

Runtime Issues

Review known issues associated with runtime.

Topics:

Cannot View the Payload for Synchronous Integrations and Nonrecoverable Faults

For synchronous integrations and nonrecoverable faults, you cannot view the payload on the Error Message Details page and Tracking page.