Professional Documents
Culture Documents
ICSKI KnownIssues
ICSKI KnownIssues
October 2016
This guide describes Oracle Integration Cloud Service known
issues and workarounds.
Oracle Cloud Known Issues for Oracle Integration Cloud Service, Release 16.4
E55682-17
Copyright 2015, 2016, Oracle and/or its affiliates. All rights reserved.
Contributing Authors: Oracle Integration Cloud Service Development, Product Management, and Quality
Assurance teams
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-
specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless
otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates
will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services, except as set forth in an applicable agreement between you and Oracle.
Contents
Preface ................................................................................................................................................................. v
Audience ........................................................................................................................................................ v
Related Resources ......................................................................................................................................... v
Conventions................................................................................................................................................... v
1 Adapter Issues
URLs in the JCA File are Not Tokenized............................................................................................... 1-2
Salesforce Adapter Custom WSDL Invalid Session is Not Working ................................................ 1-2
Downgrading the SOAP Adapter from the JCA Transport to the HTTP Transport Causes a
Runtime Failure ................................................................................................................................... 1-2
Invoke SOAP Adapter Used with On-Premises Agent Fails When Using the HTTP Transport.. 1-3
Basic Authentication Fields are Unavailable when Updating a SOAP Adapter Connection
after Importing an Integration .......................................................................................................... 1-3
Unexpected Use of the Suppression Insertion of Timestamp into WS-Security Header Feature
in the SOAP Adapter Causes an Unrelated Error Response ........................................................ 1-3
Table Relationships Not Displaying by Default when Adding a MySQL Adapter Connection
as an Invoke to an Integration ........................................................................................................... 1-3
A Single Call with Multiple Updates is Not Supported with the SQL Server Adapter in Basic
Map Data Integration Patterns.......................................................................................................... 1-3
REST Adapter Endpoint Provides a SOAP WSDL with the Basic Map Data Template ................ 1-4
REST Adapter Data is Only Saved When You Click Next ................................................................. 1-4
JSON Files in the REST Adapter are Restricted to 100 KB.................................................................. 1-4
Invoke Endpoint URI Must Match the Base URI + Resource URI in REST Adapter...................... 1-4
REST Adapter Does Not Support Services Returning Multipart Data ............................................. 1-4
Redirect URL Constructed in an Expanded Domain Fails the Provide Consent Button ............... 1-5
Copying SAP Instance-Dependant JARs After On-Premises Agent Installation............................ 1-5
SuccessFactors Fault Response is Not Mapped at Runtime ............................................................... 1-5
Oracle E-Business Suite Adapter Issues ................................................................................................ 1-5
Siebel Application WSDL Validation Errors During Activation of Siebel Inbound Services ....... 1-5
Oracle ERP Cloud Adapter User Name Requires the SOAOperator Role....................................... 1-6
Durable Subscriber Topic in Oracle Messaging Cloud Service Connection in Active-Active
Cluster Behaves Differently............................................................................................................... 1-6
iii
Incorrect UPDATE Statement Syntax Validation................................................................................. 1-6
2 Integration Issues
Jobs Remaining in Ready State and Not Completing.......................................................................... 2-1
Hold and Release Permissions Added to the Application Roles....................................................... 2-2
Viewing an Active Integration Can Cause Deactivation .................................................................... 2-2
Filter Criteria Not Displaying until Refresh Icon Selected ................................................................. 2-2
Logging Level Modifications Not Applied to Managed Servers....................................................... 2-2
Publisher and Subscriber Integrations Require Reactivation after Upgrade................................... 2-2
Used Icons are Not Displayed for Delayed Schema Loads on the Tracking Page.......................... 2-2
Orchestrated Asynchronous and Fire and Forget Integrations Do Not Complete with Large
Payloads in On-Premises Integration Cloud Service ..................................................................... 2-2
Trial Subscriptions Cannot Activate More Than Ten Integrations ................................................... 2-3
Schema Information is Lost When Re-editing the Oracle Messaging Cloud Service Adapter ..... 2-3
Preferences Are Cleared When Browser Cookies Are Deleted.......................................................... 2-3
Restart of Managed Server May Trigger an Exception ....................................................................... 2-3
Inaccurate Error Message When Specifying a Large Number of Months for the Scheduling
Frequency ............................................................................................................................................. 2-4
4 Runtime Issues
Instance Status Not Changing from Failed to Successful After Resubmit ...................................... 4-1
Permissions Error in Diagnostics Log When Performing Tasks in Oracle Integration Cloud
Service ................................................................................................................................................... 4-1
Audit Trail is Not Displayed................................................................................................................... 4-2
iv
Preface
Known Issues for Oracle Integration Cloud Service describes known issues and
workarounds when using Oracle Integration Cloud Service.
Topics:
Audience
Related Resources
Conventions
Audience
Known Issues for Oracle Integration Cloud Service describes known issues for users who
want to create, activate, and monitor application integrations..
Related Resources
For more information, see these Oracle resources:
Oracle Cloud
http://cloud.oracle.com
Conventions
The following text conventions are used in this document:
Convention Meaning
boldface Boldface type indicates graphical user interface elements associated
with an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for
which you supply particular values.
v
1
Adapter Issues
Topics
Downgrading the SOAP Adapter from the JCA Transport to the HTTP Transport
Causes a Runtime Failure
Invoke SOAP Adapter Used with On-Premises Agent Fails When Using the HTTP
Transport
A Single Call with Multiple Updates is Not Supported with the SQL Server
Adapter in Basic Map Data Integration Patterns
REST Adapter Endpoint Provides a SOAP WSDL with the Basic Map Data
Template
Invoke Endpoint URI Must Match the Base URI + Resource URI in REST Adapter
Oracle ERP Cloud Adapter User Name Requires the SOAOperator Role
Downgrading the SOAP Adapter from the JCA Transport to the HTTP
Transport Causes a Runtime Failure
Starting with Release 16.3.3, you can select to use either SOAP Adapter 16.3.3 runtime
features (which use the JCA transport) or 16.2.5 features (which use the HTTP
transport) on the Basic Info page of the Adapter Endpoint Configuration Wizard. Note
that you can only upgrade the SOAP Adapter from the 16.2.5 HTTP transport to the
16.3.3 JCA transport. You cannot downgrade from the 16.3.3 JCA transport to the
16.2.5 HTTP transport.
For example, assume you perform the following steps:
1. Import an older integration (IAR file) that uses the HTTP transport (release 16.2.5
or earlier) for the SOAP Adapter. After importing and activating an integration, it
continues to use the HTTP (default transport) and run successfully end-to-end.
3. Edit the integration to use the JCA transport for the trigger/invoke SOAP Adapter
endpoints by setting Preview updated SOAP adapter runtime to Yes on the Basic
Info page (default is No). This switches the transport protocol from HTTP to JCA.
Note: Even though the word Preview is displayed in the Preview updated
SOAP adapter runtime field, this is a production feature.
6. Edit the transport for the trigger/invoke SOAP Adapter endpoints by setting
Preview updated SOAP adapter runtime to No on the Basic Info page. This
switches the transport protocol from JCA back to HTTP.
7. Activate and invoke the integration, and note that it fails at runtime.
If you need to downgrade to the 16.2.5 or earlier version of the imported integration
that is currently using the JCA transport, perform the following steps:
4. Clone the newly-imported integration and update the integration version to use a
new value.
Invoke SOAP Adapter Used with On-Premises Agent Fails When Using
the HTTP Transport
If you configure an invoke SOAP Adapter used with the on-premises agent and set
Preview updated SOAP adapter runtime to No (that is, to use the HTTP transport) on
the Basic Info page, when you activate and invoke the integration, runtime fails with
an unauthorized error.
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
REST Adapter Endpoint Provides a SOAP WSDL with the Basic Map Data
Template
If you create a REST Adapter connection using a metadata catalog URL, and then
create and activate a REST Adapter inbound-to-REST Adapter outbound integration
using the Basic Map Data pattern, the endpoint link shows an incorrectly constructed
WSDL:
https://podnamexxx-cimdomainrcxxxxxxx.integration.dc1.c9dev2.oraclecorp.com/
integration/flowsvc/rest/RESTAPI/v01/?wsdl
As a workaround, construct and invoke the REST metadata catalog URL as follows:
https://podnamexxx-cimdomainrcxxxxxxx.integration.dc1.c9dev2.oraclecorp.com/
integration/flowapi/rest/RESTAPI/v01/metadata
If you create the same integration using the Orchestration pattern, the WSDL is
correctly constructed.
Invoke Endpoint URI Must Match the Base URI + Resource URI in REST
Adapter
While designing the REST Adapter in the Adapter Endpoint Configuration Wizard,
carefully review the contents on the Summary page. The endpoint URI must match the
invoke service URI. If you do not see the necessary values, review your invoke
connection and the outbound service. The base URI in the connection and resource
URI in the invoke service must add up to the endpoint URI.
For an example of configuring the redirect URI with the Google Calendar Adapter, see
Creating the Google Calendar Project.
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 Cloud Service password should be a
combination of text and numbers.
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 Cloud Service 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.
Oracle ERP Cloud Adapter User Name Requires the SOAOperator Role
When you create a connection to the Oracle ERP Cloud adapter in Integration Cloud
Service, and click Configure Credentials to specify the security policy, user name, and
password, ensure that the user name you specify includes the SOAOperator role. For
information, contact the Oracle ERP Cloud adapter administrator. If the user name
does not include this role, you receive the following error when you click Test after
completing adapter configuration: Unable to test the connection. Contact
your administrator for assistance.
The other active node does not process the message and you receive the following
exception error in the ics_server-diagnostic logs:
Caused by: javax.jms.InvalidClientIDException: Internal error; log reference:
84B5CF00_9E720BE825118DBB5E3E1F1A0899ACC6275A5C02 at
oracle.cloud.messaging.util.JMSUtils.makeException(JMSUtils.java:2414)
This issue is caused when the SQL Server throws the generic, parent level exception
java.sql.SQLException during syntax validation and not the
typicaljava.sql.SQLSyntaxErrorException.
Topics:
Used Icons are Not Displayed for Delayed Schema Loads on the Tracking Page
Schema Information is Lost When Re-editing the Oracle Messaging Cloud Service
Adapter
Inaccurate Error Message When Specifying a Large Number of Months for the
Scheduling Frequency
1. Create an inbound FTP-to-outbound FTP integration using the Basic Map Data
pattern.
2. Select Submit Now to invoke the integration (assuming the permissions on the
files intended to transfer are incorrectly set to 000, which causes the transfer to
fail).
3. Change the file permissions to 755 and resubmit the job from the Past Runs page.
Note that resubmission does not create any new instance and the job remains in
the ready state.
4. Resubmit the job again for the same integration or any other integration and all
continue to be in the ready state and not the completed state.
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.
increase the value in the Large Document Threshold (Byte) field on the BPEL Service
Engine Properties page in Oracle Enterprise Manager Fusion Middleware Control.
Oracle Enterprise Manager Fusion Middleware Control is automatically installed with
on-premises Oracle Integration Cloud Service.
2. From the SOA folder in the navigator, right-click and select soa-infra.
5. Click Apply.
For more information about increasing this value in Oracle Enterprise Manager Fusion
Middleware Control, see Administering Oracle SOA Suite and Oracle Business Process
Management Suite.
Topics
Agent Upgrade Required After Integration Cloud Service Upgrade for Oracle
Database Adapter 16.2.x Integrations to Work
Agent Restart Required After Restart of Oracle Database Cloud Service Instance
export proxyHost=YOUR_PROXY_HOST_NAME
export proxyPort=YOUR_PROXY_PORT
For example:
export proxyHost=www-proxy.us.oracle.com
export proxyPort=80
Note: If you are installing the 16.3.5 on-premises agent without a proxy server,
these tasks are not required. Download the connectivity agent ZIP file from the
Agents page in Oracle Integration Cloud Service.
The agent KSS store is missing in the default Oracle Integration Cloud Service
certificates. As a workaround, import the certificates.
Agent groups for which agents are not configured are also displayed on the
Connection page.
Topics
DN[cn=em_svc_monitor,cn=SystemIDs,cn=Users,orclMTTenantGuid=13090950252140439,
dc=us,dc=oracle,dc=com], Guid[191B8F9819151958E050F90A88A05384],
assertionTime[Thu Sep 22 18:31:24 UTC 2016]
Principal: em_svc_monitor_role
Principal: Monitors