Oracle® Cloud

Known Issues for Oracle Integration Cloud Service

Release 16.4.5
E55682-22

February 2017
This guide describes Oracle Integration Cloud Service known
issues and workarounds.
Oracle Cloud Known Issues for Oracle Integration Cloud Service, Release 16.4.5

E55682-22

Copyright © 2015, 2017, Oracle and/or its affiliates. All rights reserved.

Primary Authors: Mark Kennedy, Larry Hoffman

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 ............................................................................................................................................................... vii

Audience ...................................................................................................................................................... vii
Related Resources ....................................................................................................................................... vii
Conventions................................................................................................................................................. vii

1 Adapter Issues
Processing a Large Number of Files with the FTP Adapter in a Clustered Environment May
Result in Lost Output Files ................................................................................................................ 1-2
Netsuite Adapter Does Not Support Netsuite WSDL Endpoints Beyond Version 2015_1_0 ....... 1-2
Deployment and Registration of Custom On-Premises Cloud Adapter Is Not Supported .......... 1-2
Oracle RightNow Adapter QueryCSV returns only the first one hundred records ....................... 1-3
Mapping of Custom Field Fails During Runtime in Oracle RightNow Cloud To Oracle Sales
Cloud Integrations ............................................................................................................................. 1-3
Salesforce Adapter Custom WSDL Invalid Session is Not Working ................................................ 1-3
Extra Information is Included in the Response Headers Returned as Part of the Response
Message ................................................................................................................................................ 1-3
Comments Are Not Allowed as Part of the SOAP Header in Request Messages........................... 1-4
Downgrading the SOAP Adapter from the JCA Transport to the HTTP Transport Causes a
Runtime Failure ................................................................................................................................... 1-4
Basic Authentication Fields are Unavailable when Updating a SOAP Adapter Connection
after Importing an Integration .......................................................................................................... 1-5
Unexpected Use of the Suppression Insertion of Timestamp into WS-Security Header Feature
in the SOAP Adapter Causes an Unrelated Error Response ........................................................ 1-5
Table Relationships Not Displaying by Default when Adding a MySQL Adapter Connection
as an Invoke to an Integration ........................................................................................................... 1-6
A Single Call with Multiple Updates is Not Supported with the SQL Server Adapter in Basic
Map Data Integration Patterns.......................................................................................................... 1-6
REST Adapter Endpoint Provides a SOAP WSDL with the Basic Map Data Template ................ 1-6
REST Adapter Data is Only Saved When You Click Next ................................................................. 1-6
JSON Files in the REST Adapter are Restricted to 100 KB.................................................................. 1-6
Invoke Endpoint URI Must Match the Base URI + Resource URI in REST Adapter...................... 1-6
REST Adapter Does Not Support Services Returning Multipart Data ............................................. 1-7

iii
 Redirect URL Constructed in an Expanded Domain Fails the Provide Consent Button ............... 1-7
Copying SAP Instance-Dependant JARs After On-Premises Agent Installation............................ 1-7
SuccessFactors Fault Response is Not Mapped at Runtime ............................................................... 1-7
Application Versions Supported by the ServiceNow Adapter.......................................................... 1-7
Oracle E-Business Suite Adapter Issues ................................................................................................ 1-7
Siebel Application WSDL Validation Errors During Activation of Siebel Inbound Services ....... 1-8
ERP System Does Not Add a Document ID in the JSON String When a Load Interface Job Fails
................................................................................................................................................................ 1-8
Oracle ERP Cloud Adapter User Name Requires the SOAOperator Role....................................... 1-8
Durable Subscriber Topic in Oracle Messaging Cloud Service Connection in Active-Active
Cluster Behaves Differently............................................................................................................... 1-8
Incorrect UPDATE Statement Syntax Validation................................................................................. 1-9
Oracle Logistics Adapter Requires Logistics Cloud Version 6.4.2 or Later ..................................... 1-9

2 Integration Issues
Updating the Schema of an Existing WSDL Causes an Orchestrated Integration Using the
SOAP Adapter to Not Get Activated ............................................................................................... 2-1
Do Not Delete Runtime Artifacts in Minor Version Scenarios .......................................................... 2-1
Expressions with Filters in the Expression Builder Can Fail.............................................................. 2-2
Hold and Release Permissions Added to the Application Roles....................................................... 2-2
Filter Criteria Not Displaying until Refresh Icon Selected ................................................................. 2-2
Logging Level Modifications Not Applied to Managed Servers....................................................... 2-2
Used Icons are Not Displayed for Delayed Schema Loads on the Tracking Page.......................... 2-2
Trial Subscriptions Cannot Activate More Than Ten Integrations ................................................... 2-2
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-3

3 On-Premises Agent Issues

Invalid Connection or OMCS Exception Error Requires a Retrigger ............................................... 3-1
Unable to Unzip the Downloaded On-Premises Agent ZIP File ....................................................... 3-2
On-Premises Agent Fails When Installation Credentials are Changed or Expire........................... 3-2
Oracle Integration Cloud Service to On-Premises Oracle E-Business Suite Connection Error .... 3-2
Agent Restart Required After Restart of Oracle Database Cloud Service Instance ........................ 3-2
Agent Installation Throws a FileNotFoundException Error for keystore.jks ................................. 3-2
SSL-Enabled Proxy Is Not Supported for On-Premises Agent Installation ..................................... 3-2
On-Premises Agent Issues ....................................................................................................................... 3-2
Agent Installation on PODs Prior to October 2015 .............................................................................. 3-3

4 Runtime Issue
Cannot View the Payload for Synchronous Integrations and Nonrecoverable Faults................... 4-1

iv
Permissions Error in Diagnostics Log When Performing Tasks in Oracle Integration Cloud
Service ................................................................................................................................................... 4-1
Audit Trail is Not Displayed................................................................................................................... 4-2

v
vi
 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

• Getting Started with Oracle Cloud

• Using Oracle Integration Cloud Service

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.

monospace Monospace type indicates commands within a paragraph, URLs, code

in examples, text that appears on the screen, or text that you enter.

vii
 1
Adapter Issues

This section describes issues associated with adapters.

Topics

• Processing a Large Number of Files with the FTP Adapter in a Clustered

Environment May Result in Lost Output Files

• Netsuite Adapter Does Not Support Netsuite WSDL Endpoints Beyond Version
2015_1_0

• Deployment and Registration of Custom On-Premises Cloud Adapter Is Not

Supported

• Oracle RightNow Adapter QueryCSV returns only the first one hundred records

• Mapping of Custom Field Fails During Runtime in Oracle RightNow Cloud To

Oracle Sales Cloud Integrations

• Salesforce Adapter Custom WSDL Invalid Session is Not Working

• Extra Information is Included in the Response Headers Returned as Part of the

Response Message

• Comments Are Not Allowed as Part of the SOAP Header in Request Messages

• Downgrading the SOAP Adapter from the JCA Transport to the HTTP Transport
Causes a Runtime Failure

• Basic Authentication Fields are Unavailable when Updating a SOAP Adapter

Connection after Importing an Integration

• Unexpected Use of the Suppression Insertion of Timestamp into WS-Security

Header Feature in the SOAP Adapter Causes an Unrelated Error Response

• Table Relationships Not Displaying by Default when Adding a MySQL Adapter

Connection as an Invoke to an Integration

• 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

• REST Adapter Data is Only Saved When You Click Next

• JSON Files in the REST Adapter are Restricted to 100 KB

• Invoke Endpoint URI Must Match the Base URI + Resource URI in REST Adapter

Adapter Issues 1-1

Processing a Large Number of Files with the FTP Adapter in a Clustered Environment May Result in Lost Output Files

• REST Adapter Does Not Support Services Returning Multipart Data

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

Button

• Copying SAP Instance-Dependant JARs After On-Premises Agent Installation

• SuccessFactors Fault Response is Not Mapped at Runtime

• Application Versions Supported by the ServiceNow Adapter

• Oracle E-Business Suite Adapter Issues

• Siebel Application WSDL Validation Errors During Activation of Siebel Inbound

Services

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

• Oracle ERP Cloud Adapter User Name Requires the SOAOperator Role

• Durable Subscriber Topic in Oracle Messaging Cloud Service Connection in

Active-Active Cluster Behaves Differently

• Incorrect UPDATE Statement Syntax Validation

• Oracle Logistics Adapter Requires Logistics Cloud Version 6.4.2 or Later

Processing a Large Number of Files with the FTP Adapter in a Clustered

Environment May Result in Lost Output Files
By default, the maximum number of files that can be processed by the FTP Adapter in
a scheduled run is 100. If you are processing a larger number of files (for example,
5000 files) to be received by an FTP Adapter write operation, it is mandatory to map
the FTP read file operation headers and FTP write file name headers in the mapper. If
you do not map the headers, output files may be lost when compared to the number of
processed input files.

Netsuite Adapter Does Not Support Netsuite WSDL Endpoints Beyond

Version 2015_1_0
The Netsuite Adapter does not support Netsuite WSDL endpoints beyond version
2015_1_0. To connect to Netsuite application versions 2015_2_0 and beyond, use the
2015_1_0 version of the Netsuite WSDL endpoint.

Deployment and Registration of Custom On-Premises Cloud Adapter Is

Not Supported
You can deploy and register your own custom cloud adapters under Designer >
Adapters. This feature currently supports only custom cloud adapters. Custom on-
premise adapters are currently not supported.

1-2 Oracle Cloud Known Issues for Oracle Integration Cloud Service
 Oracle RightNow Adapter QueryCSV returns only the first one hundred records

Oracle RightNow Adapter QueryCSV returns only the first one hundred
records
The RightNow Object Query Language (ROQL) supports querying data using
QueryCSV, which enables you to retrieve data in a tabular format. Note that this query
returns only the first one hundred records.

Mapping of Custom Field Fails During Runtime in Oracle RightNow Cloud

To Oracle Sales Cloud Integrations
The RightNow application documentation indicates that given a Contact, the
CustomFields contains a subobject C_Contacto that has a SalesCloudID field.
To fetch the SalesCloudID using a Query or Get operation, note that the
CustomFields subobject is listed in the object model as specify to get. This
means that you must provide a hint to the system that you want that information.
Provide the hint by including an empty CustomFields subobject in the Contact
object you passed in as a template. This action informs the server that the object to be
returned should also include all the ContactCustomFields. You can do this with
any subobject that is listed as specify-to-get.
In Oracle Integration Cloud Service, the behavior is slightly different. In the
GetContact request mapper, set a value to
ContactCustomFields.C_Contacto.SalesCloudID (for example,
SalesCloudID=1). This step ensures a complete CustomFields return as part of the
response.
If you follow this step and retry, it works.

Salesforce Adapter Custom WSDL Invalid Session is Not Working

Assume you create and activate an integration with an invoke (outbound) Salesforce
Adapter configured with the custom WSDL option. You invoke the integration from
the SOAP UI and then invalidate the session by using the enterprise WSDL. If you
then invoke the integration again from the SOAP UI, you receive an Invalid Session
ID.

Extra Information is Included in the Response Headers Returned as Part

of the Response Message
When standard HTTP headers are used in the response headers as part of the response
message, extra information is included as part of the returned output data at runtime.
This issue occurs only when headers are used in the SOAP Adapter. Without headers,
the output is returned without extra information in the response message.
The extra information is not an extra namespace. It is a valid namespace matching the
prefix of the element. Without headers, the namespace comes as an attribute in the
root element. With headers, since elements are converted from a wrapper, the child
elements are copied along with their namespaces.
For example, with a connection that uses the same web service, but one with a header
(custom HTTP Header) and another one without a header, the body elements in the
response message are different as shown below:
Without a header:

Adapter Issues 1-3

Comments Are Not Allowed as Part of the SOAP Header in Request Messages

<nstrgmpr:result>
<nsmpr6:PartyId>10</nsmpr6:PartyId>
<nsmpr6:PartyName>Acme Corp</nsmpr6:PartyName>
</nstrgmpr:result>

With a header:
<nsmpr2:result>
<nsmpr8:PartyId
xmlns:nsmpr8="http://xmlns.oracle.com/apps/cdm/foundation/parties/
organizationService/">10
</nsmpr8:PartyId>
<nsmpr8:PartyName
xmlns:nsmpr8="http://xmlns.oracle.com/apps/cdm/foundation/parties/
organizationService/">Acme Corp
</nsmpr8:PartyName>
</nsmpr2:result>

Comments Are Not Allowed as Part of the SOAP Header in Request

Messages
When a comment is included as part of the input SOAP header in the request message
generated by the SOAP UI, the expected header values fail to be sent.
For example, the following request message is invalid because of the <!--
Optional:--> line. Remove the <!--Optional:--> line and the request message
can be successfully sent.
<soapenv:Envelope .. .. .. /">
<soapenv:Header>
<wsse:Security
. . .
. . .
</wsse:Security>
<ser:ArmSoapHeader>
<BusinessAreaID>100</BusinessAreaID>
<!--Optional:-->
<ClientVersion>V2.0</ClientVersion>
<InstanceID>300</InstanceID>
</ser:ArmSoapHeader>
</soapenv:Header>
<soapenv:Body>
<proj:foo>
<arg0>500</arg0>
</proj:foo>
</soapenv:Body>
</soapenv:Envelope>

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-4 Oracle Cloud Known Issues for Oracle Integration Cloud Service
 Basic Authentication Fields are Unavailable when Updating a SOAP Adapter Connection after Importing an Integration

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.

2. Deactivate the integration.

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.

4. Activate and invoke the integration, which runs successfully end-to-end.

5. Deactivate the integration.

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:

1. Deactivate the integration that is currently using the JCA transport.

2. Delete the integration and its connections.

3. Re-import the release 16.2.5 or earlier version of the IAR file.

4. Clone the newly-imported integration and update the integration version to use a
new value.

5. Update the connection information and activate the integration.

Basic Authentication Fields are Unavailable when Updating a SOAP

Adapter Connection after Importing an Integration
After importing an IAR file that was exported from a 16.2.5 release, while updating a
SOAP Adapter Connection that uses Basic Authentication, the Username and
Password fields are not available in the Configure Security dialog. For a trigger
connection, these credentials are not required because this is a SOAP endpoint. The
credentials to access the endpoint are always the Integration Cloud Service runtime
user and password. In previous releases, the inbound SOAP Adapter connection
accepted username and password changes.

Unexpected Use of the Suppression Insertion of Timestamp into WS-

Security Header Feature in the SOAP Adapter Causes an Unrelated Error
Response
When creating a SOAP Adapter connection with Suppress insertion of timestamp
into WS-Security header set to Yes on the Connections page and using a WSDL that
requires a timestamp header, the connection fails during runtime with the following
error instead of a message indicating that a valid timestamp is not present:

Adapter Issues 1-5

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

<errorCode>OSB-380001</errorCode>
<reason>InvalidSecurityToken : The security token is not valid.</reason>

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 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.

REST Adapter Data is Only Saved When You Click Next

When configuring the REST Adapter in the Adapter Endpoint Configuration Wizard,
you must click Next to save your changes and move to the next page of the wizard.
For example, if you configure details on the Request page, click the tab of the Basic
Info page in the left pane, then click Next to return to the Request page, none of your
previous configurations were saved, and the page is empty.

JSON Files in the REST Adapter are Restricted to 100 KB

When designing the REST Adapter on the Request and Response pages of the Adapter
Endpoint Configuration Wizard, the maximum size of the JSON file is restricted to 100
KB.

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

1-6 Oracle Cloud Known Issues for Oracle Integration Cloud Service
 REST Adapter Does Not Support Services Returning Multipart Data

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.

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

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

Copying SAP Instance-Dependant JARs After On-Premises Agent

Installation
Each SAP instance has version-specific JAR files. After installing the on-premises
agent, you must copy sapidoc3.jar and sapjco3.jar. to Agent_Home/
thirdparty/lib and restart the on-premises agent.
Download the JARs from http://service.sap.com/connectors.

SuccessFactors Fault Response is Not Mapped at Runtime

The fault response is not getting mapped during runtime.
If you create an integration using the SuccessFactors adapter in which you select an
outbound operation and configure the request, response, and fault mappings, after
integration activation, the fault response is not mapped during runtime.

Application Versions Supported by the ServiceNow Adapter

The ServiceNow Adapter is now compatible with the Helsinki Patch 5 and Geneva
versions of ServiceNow. Fuji is no longer supported.

Oracle E-Business Suite Adapter Issues

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

• 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.

Adapter Issues 1-7

Siebel Application WSDL Validation Errors During Activation of Siebel Inbound Services

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 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.

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.

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.

Durable Subscriber Topic in Oracle Messaging Cloud Service Connection

in Active-Active Cluster Behaves Differently
In an active-active Integration Cloud Service environment with an inbound Oracle
Messaging Cloud Service connection, the behavior of a durable subscription topic is as
follows:

• Only one node performs message processing.

• 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)

1-8 Oracle Cloud Known Issues for Oracle Integration Cloud Service
 Incorrect UPDATE Statement Syntax Validation

Incorrect UPDATE Statement Syntax Validation

With the Microsoft SQL Server Adapter, UPDATE statements with incorrect syntax
validate successfully. For example, this statement validates successfully even though
the comma is missing before bit_id:
UPDATE MSSQLALLDB1 SET decimal_dt=#decimal_dt, dtoffset_dt='2006-01-01
01:01:01' bit_id=#bit_id, money_dt=#money_dt WHERE int_id=#int_id and
numeric_dt=#numeric_dt

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.

Oracle Logistics Adapter Requires Logistics Cloud Version 6.4.2 or Later

The Oracle Logistics Adapter is only supported with Logistics Cloud versions 6.4.2
and later.
See http://www.oracle.com/technetwork/documentation/glog-101972.html for
additional setup information and a description of a sample integration.

Adapter Issues 1-9

Oracle Logistics Adapter Requires Logistics Cloud Version 6.4.2 or Later

1-10 Known Issues for Oracle Integration Cloud Service

 2
Integration Issues

This section describes issues associated with integrations.

Topics:

• Updating the Schema of an Existing WSDL Causes an Orchestrated Integration

Using the SOAP Adapter to Not Get Activated

• Do Not Delete Runtime Artifacts in Minor Version Scenarios

• Expressions with Filters in the Expression Builder Can Fail

• Hold and Release Permissions Added to the Application Roles

• Filter Criteria Not Displaying until Refresh Icon Selected

• Logging Level Modifications Not Applied to Managed Servers

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

• Trial Subscriptions Cannot Activate More Than Ten Integrations

• Schema Information is Lost When Re-editing the Oracle Messaging Cloud Service
Adapter

• Preferences Are Cleared When Browser Cookies Are Deleted

• Restart of Managed Server May Trigger an Exception

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

Updating the Schema of an Existing WSDL Causes an Orchestrated

Integration Using the SOAP Adapter to Not Get Activated
If you create and activate an orchestrated integration that uses the SOAP Adapter and
then update the WSDL being used by adding a new schema, you can edit the invoke
connections in the integration to use the new WSDL, but cannot edit the trigger
connection because it does not provide an option to edit. Because of this scenario, you
cannot reactivate the integration.
As a workaround, create a new integration that uses the new WSDLs. You can then
successfully activate the new integration.

Do Not Delete Runtime Artifacts in Minor Version Scenarios

If you have multiple minor versions of the same integration (for example, version
01.00.0000 and 01.10.0000) and one of them is active, do not delete the inactive
integration. Otherwise, runtime behavior for the active integration becomes out of

Integration Issues 2-1

Expressions with Filters in the Expression Builder Can Fail

sync. As a workaround, deactivate and reactivate the integration after deleting the
inactive version.

Expressions with Filters in the Expression Builder Can Fail

Expressions with filters in the Expression Builder can fail. For example, the following
filtered expression:
/nssrcmpr:process/nssrcmpr:Organization/rno_v1_3:FileAttachments/rno_v1_3:File
AttachmentList[1.0][(rno_v1_3:FileName = "test123")]/rno_v1_3:Name = "ORG"

returns the following error:

"Expected one of '.', '..', '@', '*', <QName> at position: 98"

As a workaround, enter "./" in front of the node name in the filter.

For example:
/nssrcmpr:process/nssrcmpr:Organization/rno_v1_3:FileAttachments/rno_v1_3:File
AttachmentList[1.0][(./rno_v1_3:FileName = "test123")]/rno_v1_3:Name = "ORG"

This action causes the expression to process successfully.

Hold and Release Permissions Added to the Application Roles

Users with the integrationservicedeveloper, integrationserviceruntime, and
integrationserviceadmin roles have the permissions to read, update, cancel, and delete
requests. The hold and release actions are not explicitly granted, meaning only the
submitter has the permission to hold or resume a request.

Filter Criteria Not Displaying until Refresh Icon Selected

On the Oracle Integration Cloud Service Past Runs page, the blue filter criteria band at
the top of the results list does not appear unless the Refresh icon is selected.

Logging Level Modifications Not Applied to Managed Servers

When you modify the logging level settings in the Oracle Integration Cloud Service
administration console and select Save, the new settings are applied to the
administration server and not the managed servers.

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.

Trial Subscriptions Cannot Activate More Than Ten Integrations

With trial subscriptions, only ten or fewer asynchronous integrations can be active at
one time.
If you have ten active asynchronous integrations, you must deactivate one or more
before you can activate a new one.

2-2 Oracle Cloud Known Issues for Oracle Integration Cloud Service
 Schema Information is Lost When Re-editing the Oracle Messaging Cloud Service Adapter

Schema Information is Lost When Re-editing the Oracle Messaging Cloud

Service Adapter
If you create an integration that includes an Oracle Messaging Cloud Service adapter
for which you specified the XSD schema file, when you invoke the adapter
configuration wizard again to re-edit that adapter, the XSD schema file is lost and
must be specified again.

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.

Restart of Managed Server May Trigger an Exception

Stopping and starting a managed server after activating an integration might trigger
an exception.
If you stop and start a managed server after activating an integration, you might see
an exception message in the log file similar to the following:
<Feb 12, 2016 4:02:58 AM PST> <Error> <Cluster> <BEA-000123> <Conflict start: You
tried to bind an object under the name QueueIn in the JNDI tree.
The object from -6627227834449688464S:den00bhr.us.oracle.com:
[22601,22601,-1,-1,-1,-1,-1]:WLS_ ICS:ics_server2 is non-clusterable, and you have
tried to bind more than once from two or more servers. Such objects can only be
deployed from one server.>

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.

Integration Issues 2-3

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

2-4 Known Issues for Oracle Integration Cloud Service

 3
On-Premises Agent Issues

This section describes issues associated with the on-premises agent.

Topics

• Invalid Connection or OMCS Exception Error Requires a Retrigger

• Unable to Unzip the Downloaded On-Premises Agent ZIP File

• On-Premises Agent Fails When Installation Credentials are Changed or Expire

• Oracle Integration Cloud Service to On-Premises Oracle E-Business Suite

Connection Error

• Agent Restart Required After Restart of Oracle Database Cloud Service Instance

• Agent Installation Throws a FileNotFoundException Error for keystore.jks

• SSL-Enabled Proxy Is Not Supported for On-Premises Agent Installation

• On-Premises Agent Issues

• Agent Installation on PODs Prior to October 2015

Invalid Connection or OMCS Exception Error Requires a Retrigger

If you see an invalid connection or Oracle Messaging Cloud Service (OMCS)
exception, you should also see a Message processing will resume after
recovery message in the agent log file. This means that you must wait for some time
for message recovery to complete and then retrigger the request. A portion of the log
file message is shown below.
Retry after 503 response or possible messaging context expiration succeeded
[2017-01-09T20:59:27.955-08:00] [AdminServer] [ERROR] []
[oracle.cloud.cpi.agent.transport.CpiAgentTransporter] [tid:
pool-14-thread-14] [userId:<anonymous>] [ecid:

93f0ca35-4ee9-4443-8234-f13a5c7d5123-00000004,0] [APP: agent-webapp] Receive

failed with exception Closed object. Starting recovery loop...
[2017-01-09T20:59:27.956-08:00] [AdminServer] [NOTIFICATION] []
[oracle.cloud.cpi.agent.transport.AbstractInboundChannel] [tid:
pool-14-thread-14] [userId:<anonymous>] [ecid:

93f0ca35-4ee9-4443-8234-f13a5c7d5123-00000004,0] [APP: agent-webapp] Stopping

channel for destination UVAG1PROXY_CPI_RUNTIME_REQ_RES_CHANNEL
[2017-01-09T20:59:28.042-08:00] [AdminServer] [NOTIFICATION] []
[oracle.cloud.cpi.agent.transport.AbstractInboundChannel] [tid:

. . .
. . .

On-Premises Agent Issues 3-1

Unable to Unzip the Downloaded On-Premises Agent ZIP File

Unable to Unzip the Downloaded On-Premises Agent ZIP File

You may be unable to unzip the downloaded on-premises agent ZIP file. If this occurs,
download and unzip the file again.

On-Premises Agent Fails When Installation Credentials are Changed or

Expire
If you installed the on-premises agent, and the Oracle Integration Cloud Service user
name and password credentials you specified during installation are later changed or
expire, all REST calls from the agent fail with the following error:
The Agent Instance metrics could not be retrieved for "oracle.jbo.JboException:
JBO-29000: Unexpected exception caught: java.lang.RuntimeException

As a workaround, contact Oracle Support Services to obtain a script that updates the
credentials for the on-premises agent.

Oracle Integration Cloud Service to On-Premises Oracle E-Business Suite

Connection Error
You can receive the following error when creating a connection to on-premises Oracle
E-Business Suite from Oracle Integration Cloud Service. You can also receive a PKIX
Path building failed exception error. To avoid these errors, you must import
the target endpoint certificate on the instance on which the on-premises agent is
installed.
Unable to test connection "CORELOGI_EBS_CLPNDEV_2". [Cause: CASDK-0007]:
- CASDK-0007: Unable to establish a secure connection to
clpndevlbqn.corelogic.net. SSL protocol related exception occurred.
- PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
- unable to find valid certification path to requested target

Agent Restart Required After Restart of Oracle Database Cloud Service

Instance
When you shut down the Oracle Database Cloud Service instance for maintenance or
other reasons from the My Services Console, the host on which the Oracle Database
Cloud Service and on-premises agent are installed is also shut down. You must restart
the on-premises agent after restarting the Oracle Database Cloud Service instance.

Agent Installation Throws a FileNotFoundException Error for keystore.jks

During agent installation, a keystore.jks not found exception can occur.
This exception does not impact functionality. This exception occurs because a
monitoring REST service is getting called before the agent servlet is initialized.

SSL-Enabled Proxy Is Not Supported for On-Premises Agent Installation

An SSL-enabled proxy is not supported for an on-premises agent installation.

On-Premises Agent Issues

Note the following on-premises agent issues.

3-2 Oracle Cloud Known Issues for Oracle Integration Cloud Service
 Agent Installation on PODs Prior to October 2015

• The agent KSS store is missing in the default Oracle Integration Cloud Service
certificates. As a workaround, import the certificates.

Agent Installation on PODs Prior to October 2015

If you are running Oracle Integration Cloud Service on a pre-October 15, 2015 POD,
you must file a service request for Oracle to manually fix the OMCS URL if you install
a new on-premises agent. Note that this is not an issue if you are upgrading an
existing on-premises agent.

On-Premises Agent Issues 3-3

Agent Installation on PODs Prior to October 2015

3-4 Known Issues for Oracle Integration Cloud Service

 4
Runtime Issue

This section describes issues associated with runtime.

Topics

• Cannot View the Payload for Synchronous Integrations and Nonrecoverable

Faults

• Permissions Error in Diagnostics Log When Performing Tasks in Oracle

Integration Cloud Service

• Audit Trail is Not Displayed

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.

Permissions Error in Diagnostics Log When Performing Tasks in Oracle

Integration Cloud Service
You can receive the following error in the diagnostic logs when performing an action
in Oracle Integration Cloud Service for which you do not have the correct permissions.
<nos-ics-ics2046-ics-as1.ics.cloudqa.myoraclecorp.com> <AdminServer>
<[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default
(self-tuning)'> <<WLS Kernel>> <>
<0538f60b-882f-4911-8694-108349b6d3a1-000004b2> <1474569089159> <BEA-080003>
<A RuntimeException was generated by the RMI server:
javax.management.remote.rmi.RMIConnectionImpl.getAttribute(Ljavax.management.O
bjectName;Ljava.lang.String;Ljavax.security.auth.Subject;)
javax.management.RuntimeMBeanException: javax.ejb.EJBException:
EJB Exception: ; nested exception is:
java.lang.SecurityException: User "Subject:
Principal: oracle.security.opss.principals.CrossTenantUserImpl:
name[em_svc_monitor], tenantId[13090950252140439],
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
Principal: authenticated-role
Principal:
ApplicationRoleicswebapp/integrationserviceemmonitor,uname:cn=integrationservi
ceemmonitor,cn=Roles,cn=icswebapp,cn=opssSecurityStore,cn=JPSContext,cn=opssRo
ot,guid:8422B39080ED11E6BFCD65963D43E860 Private Credential: Subject:
Principal: oracle.security.opss.principals.CrossTenantUserImpl:

Runtime Issue 4-1

Audit Trail is Not Displayed

name[em_svc_monitor], tenantId[13090950252140439],
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

" is not authorized to perform action "SOA access"..

. . .
. . .

Audit Trail is Not Displayed

The audit trail functionality does not work in this release of Oracle Integration Cloud
Service
The audit trail functionality is described in Viewing Past and Present Integration Runs
of Using Oracle Integration Cloud Service.

4-2 Oracle Cloud Known Issues for Oracle Integration Cloud Service