Oracle SOA and Oracle BPM Products 12c Release 1 (12.1.3.0.0)

For a list of issues and workarounds pertaining to Oracle SOA Installation, Upgrade, High Availability, Enterprise Deployment, Performance Tuning, and Web Services, as well as SOA on IBM Websphere, see the Oracle Fusion Middleware Release Notes.

On this page: (Last updated: 09-May-2017)

Oracle Edge Analytics

Supported Platforms

Oracle Event Processing on Oracle Java Embedded System runs on any platform that can run Java Virtual Machine Server of Java Standard Edition Embedded 1.7.* and 1.8.*. However, Server Java Virtual Machine is supported only for the following processors:

1. ARM v7 Hard Float
2. ARM v7 Soft Float
3. i586.

Note: Use Java Standard Edition Embedded 1.7.* if the processors you use are other than the ones listed here.

The following table is the matrix for supported platform matrix:

Supported Java Versions

The following table summarizes the supported Java Platforms for Oracle Event Processing Embedded and Oracle Event Processing Embedded with Eurotech Bundles.

Eurotech Bundles Support

Eurotech's fast-gateway is a x86 processor and slow-gateway is a ARM processor.

Eurotech Bundles fail to resolve when run on Raspberry Pi Devices

1. Bug: 20066623
2. Added: 17-June-2015
3. Platform: All

The following Eurotech Bundles fail to resolve when run on Raspberry Pi devices:

1. Device IO (1.0.1)
2. Serial Device based on RxTx (2.2.0).

This happens for Eurotech Bundles with Version 3.1.0.

Workaround: For Eurotech Bundles with Version 3.1.0 on Pi, add the following system property in the startwlevs.sh file and restart the Server:

-Desf.os.version=raspbian -Dkura.arch=armv6_hf

Cannot deploy OEP Application Using Embedded Derby JDBC Driver Directly

1. Bug: 20887374
2. Added: 15-June-2015
3. Platform: All

Java DB client driver derbyclient.jar, is not included with JES. You must download it from http://db.apache.org/derby/releases/release-10.8.2.2.html. You need to explicitly modify the jar file while using derbyclient.jar as following:

Add the package org.apache.derby.client.am to the MANIFEST.mf and re-construct the derbyclient.jar file.

JVM Error Message while starting OEP Server Default Domain Using JDK 8 on ARM on Raspberry Pi Devices

1. Bug: 20066619
2. Added: 17-June-2015
3. Platform: All

When you try to start Oracle Event Processing Server default domain using JDK Version 8 Update 6 for ARM on Raspberry Pi devices, the following error appears:

Error occurred during initialization of VM Server. VM is only supported on ARMv7+ VFP.

Workaround: The error is thrown from JVM directly because armv6 on Raspberry PI does not support -server parameter of JVM. Internally, Oracle Event Processing startup script startwlevs.sh changes JVM args from -server to -client to start Oracle Event Processing server.

SOA Suite and BPM Suite Common Functionality

SOA Suite 12c Integration with OAM 11g

1. Bug: 20756882
2. Added: 09-May-2017
3. Platform: All

Oracle Access Management (OAM) 11g is now integrated with Oracle SOA Suite 12c. For additional information, see https://www.oracle.com/docs/tech/middleware/fmw-1213certmatrix.xls.

NTLM is not supported

1. Bug: 20756882
2. Added: 09-May-2017
3. Platform: All

NTLM as stated in the section 8.6 at: http://docs.oracle.com/middleware/1213/soasuite/administer/toc.htm is not supported. This section is not valid anymore.

EDN Support in 12c

1. Bug: 20690977
2. Added: 09-May-2017
3. Platform: All

In 12c EDN durable subscriptions are supported. However, the documentation has a note which reads "The EDN does not support durable subscriptions (whether they are backed by native AQ or Oracle WebLogic Server JMS). The subscribing service component must be running to receive events."

This note in the documentation is outdated and in the documentation and is not valid anymore.

Support for SHA2

1. Bug: 22628159
2. Added: 05-May-2017
3. Platform: All

SOA Suite 12.1.3 version supports SHA2.

Cannot Rename SOA Projects and Composites

1. Bug: 22369312
2. Added: 05-May-2017
3. Platform: All

While renaming a service component or binding component artifact, you cannot rename SOA Projects and Composites as opposed to what is stated in the documentation.

Missing Partition Tables

1. Bug: 20614652
2. Added: 02-May-2017
3. Platform: All

When you use RCU utility and set DATABASE PROFILE value to "LARGE", in total 49 tables are partitioned. The following tables are missing in the documentation which need to be configured manually:

1. MEDIATOR_GROUP_STATUS
2. MEDIATOR_RESEQUENCER_MESSAGE
3. SCA_ASYNC_CPNT_STATE

sca_isSOAPlatformReady Command provides SOA Platform readiness information

1. Bug: 20614652
2. Added: 02-May-2017
3. Platform: All

The sca_isSOAPlatformReady command provides information about SOA Platform readiness to accept requests. The following is the syntax of the command:

1. sca_isSOAPlatformReady(host, port, user, password)
2. host - The host name of the server (for example, abc10)
3. port - The port on which the SOA platform is running (for example, 8001)
4. user/password - The user name and password to access the server
5.  
6. Example:
7. sca_isSOAPlatformReady('abc10', '8001', 'weblogic', 'weblogic')

To execute this command you must run ./wlst.sh from middleware home/soa/common/bin directory and then run above mentioned command on wlst prompt.

Implementing Functions in XSLT Mapper

1. Bug: 20861023
2. Added: 02-May-2017
3. Platform: All

This is a sample XSL Mapper User Defined Extension Functions implementation class.

package oracle.sample;

public class SampleExtensionFunctions
{
public static Double toKilograms(Double lb)
{
return new Double(lb.doubleValue()*0.45359237);
}

public static String replaceChar(String inputString, String oldChar, String
newChar )
{
return inputString.replace(oldChar.charAt(0), newChar.charAt(0));
}
} 

For more information, see Programming with Oracle XSLT Extensions at https://docs.oracle.com/database/121/ADXDK/adx_j_xslt.htm.

EM 12c Certification with BPM 12c

1. Bug: 20861023
2. Added: 02-May-2017
3. Platform: All

In addition to the certification information provided at https://docs.oracle.com/middleware/1213/soasuite/administer/soa-bpm-suite-manage-intro.htm#SOAAG236, BPM 12c is also certified on EM 12c.

Spring Context doesn't work from a SOA Template

1. Bug: 20861023
2. Added: 02-May-2017
3. Platform: All

If you include a spring context in a SOA Template, the EJB class files, interfaces, and dependent jars do not get included. This is a know issue.

Cannot Differentiate Between Local and WS Binding Invocation

1. Bug: 20866537
2. Added: 18-March-2017
3. Platform: All

You cannot differentiate between the local and WS binding invocation just by viewing the EM flow trace table. Go to Actions > Flow Trace.xml in Flow Trace Table and look for subType="binding.local", which indicates that the invocation went over local optimization.

This is a limitation.

BPEL Component Audit Trail throws Error

1. Bug: 20349976
2. Added: 18-March-2017
3. Platform: All

When you click a BPEL Component Instance in the flow trace table, its audit trail opens. If you click the flow tab, the error "Flow diagram for this BPEL process instance is unavailable as the composite has been undeployed. To view the flow diagram for this instance, the composite must be redeployed" is thrown. This is because BPEL Component Instance is not persistent.

This is a known issue.

Retired Subscriber cannot subscribe for Activation

1. Bug: 18265205
2. Added: 18-March-2017
3. Platform: All

When subscribers are shutdown/stopped, events are lost. You need at least one subscriber when publishing.

This is a limitation.

Event Delivery Network (EDN) Performance with Multiple Subscribers

1. Bug:21337626
2. Added: 11-March-2016
3. Platform: All

When there are several subscribers with a substantial difference in performance, the Event Delivery Network (EDN) runs at the speed of the slowest subscriber.

When a message arrives, and a thread is allocated, the thread passes the message from one subscriber to the other. If one of the subscribers is substantially slower than the others, then very soon all threads get busy waiting for the slowest subscriber.

Not Prompted for a Username or Password When Using the oracle/wss_username_token_service_policy Security Policy

1. Bug:18998669
2. Added: 24-June-2014
3. Platform: All

If you attach the oracle/wss_username_token_service_policy security policy to a SOAP web service binding component in the Exposed Services swimlane of a SOA composite application with a BPEL process, you are not prompted for a username and password.

Case Sensitivity Issues When Logging in to Oracle Enterprise Manager Fusion Middleware Control

1. Bug:18965140
2. Added: 24-June-2014
3. Platform: All

Assume you create a user name with an initial capital letter (for example, user name Joe) in Oracle WebLogic Server Administration Console to which you assign the appropriate roles. When you log in to Oracle Enterprise Manager Fusion Middleware Control with user name Joe, you can successfully access the Oracle SOA Suite pages permitted by the assigned roles.

However, if you log in to Oracle Enterprise Manager Fusion Middleware Control as joe (all lower case letters), the login is successful, but you receive a You do not have the permissions to view this region error when you try to access any Oracle SOA Suite pages.

Workaround: Log in to Oracle Enterprise Manager Fusion Middleware Control using the exact case sensitivity with which you created the user in Oracle WebLogic Server Administration Console.

Do Not Change the REST Adapter Fault Schema After Adapter Instance Creation

1. Bug:18961508
2. Added: 24-June-2014
3. Platform: All

When using the REST adapter, do not change the fault schema after the adapter instance has been created.

No Design View Option for a Fault Binding Policy

1. Bug:18956382
2. Added: 24-June-2014
3. Platform: All

There is no Design view option in Oracle JDeveloper for a fault binding policy. For example, if you associate a fault policy with appropriate service components and binding components in the Composite Fault Policies dialog, save your changes, and click fault-bindings.xml in the Applications window, Source view of the fault binding policy is displayed. Note that there is no tab for Design view. If you want to change the service components or binding components associated with the fault policy, you must delete the existing fault binding policy and create a new one.

Testing a Complex Parameter with Default Value in XSLT Transformation

1. Bug:17991993
2. Added: 24-June-2014
3. Platform: All

If you assign default values to a complex parameter in the target/XSLT tree and test the map, using the Test XSLT Map option, the output xml does not show the default assignments for the parameter.

Deleted Named Template Parameter Still Appears In Call Template

1. Bug:17992971
2. Added: 24-June-2014
3. Platform: All

After you delete a parameter from a named template, the parameter still shows in the call-template. You can manually delete the parameter.

Priority and Mode Attributes Not Disabled for Named Templates That Are Not Match Templates in Oracle JDeveloper

1. Bug:17992998 and 17992946
2. Added: 24-June-2014
3. Platform: All

The user is incorrectly allowed to set values for the priority and mode attributes even if the match attribute is not enabled. If you specify the priority or mode attribute for a named template that does not have a match attribute, the value for the priority/mode attribute is ignored.

If a named template does not have a match attribute, you should not use the priority and mode attributes in the Properties window for the named template.

Auto Map Not Available in the XSLT Map Editor When Using the Customization Developer Role

1. Bug:18034696
2. Added: 24-June-2014
3. Platform: All

When working with Oracle JDeveloper using the Customization Developer role, auto mapping is not enabled in the XSLT Map Editor. If you need to use the Auto Map feature, you must switch roles using Tools > Switch Roles, and restart Oracle JDeveloper.

Type Chooser Represents Imported Schemas Under WSDL Schemas Section

1. Bug:18546087
2. Added: 24-June-2014
3. Platform: All

When creating a new XQuery module, you can add source parameters and choose their data types. When you invoke the Type Chooser dialog to select the parameter type, the wsdl node has three folders: Imported Schemas, WSDL Schemas, and Imported WSDL.

If you choose an imported schema from the WSDL Schemas folder, then the generated XQuery import incorrectly refers to the wsdl in place of the schema. However, if you choose the imported schema from the Imported Schemas folder, the schema is correctly imported.

Workaround: When using an imported schema, select the schema from the Imported Schemas folder.

Using a Partitioned Distributed Topic to Achieve Better Performance

1. Bug:17214511
2. Added: 24-June-2014
3. Platform: All

You no longer need to manually change Forwarding Policy from Replicated (the default) to Partitioned to resolve subscription duplication issues, as described in Section "Resolving Duplicate Messages for Subscribers in Clustered Environments" of Administering Oracle SOA Suite and Oracle Business Process Management Suite.

In a multinode cluster, the uniform distributed WebLogic JMS topic (UDD) may default its Forwarding Policy setting to Replicated instead of Partitioned. Replicated allows a member to replicate (forward) information to other members of the distributed topic. Partitioned prevents information from being forwarded to other members of the distributed topic.

Although the Event Delivery Network (EDN) in 12c together with the underlying JMS adapter used by EDN handles either value (that is, Partitioned for Partitioned Distributed Topic (PDT) or Replicated for Replicated Distributed Topic (RDT), you should use Partitioned instead to achieve better performance.

Creating an Oracle BAM 11g Connection in Oracle JDeveloper 12c

1. Bug:18805565
2. Added: 24-June-2014
3. Platform: All

To create an Oracle Business Activity Monitoring (BAM) 11g connection in Oracle JDeveloper 12c, you must perform the following steps:

Note: Create the oracle.bam_11.1.1 directory in Oracle JDeveloper 12c, if needed.

1. 1. Copy the following BAM JAR files from the BAM 11g installation:
   • Oracle_Home/soa/bam/modules/oracle.bam_11.1.1/oracle-bam-adc-ejb.jar
   • Oracle_Home/soa/bam/modules/oracle.bam_11.1.1/oracle-bam-common.jar
   • Oracle_Home/soa/bam/modules/oracle.bam_11.1.1/oracle-bam-reportcache-ejb.jar

   To the following location in Oracle JDeveloper 12c:

   Jdeveloper_Home/soa/plugins/jdeveloper/bam/modules/oracle.bam_11.1.1

2. 2. Restart Oracle JDeveloper.

javaAction Fault Policy Action is Not Supported on Inbound Adapters

1. Bug:18860996
2. Added: 24-June-2014
3. Platform: All

When designing a fault policy, the javaAction fault policy action is not supported on inbound adapters.

Backlog Events are Lost When a New Revision of a Subscribing Composite is Deployed

1. Bug:18860753
2. Added: 24-June-2014
3. Platform: All

If an event delivery network (EDN) subscribing composite is still running and processing in-flight events, and you deploy a new revision of the subscribing composite, the backlog events of the older revision are lost and not processed by any subscriber.

Smart Data Tab Not Supported with the SOA Debugger

1. Bug:18892587
2. Added: 24-June-2014
3. Platform: All

When using the SOA Debugger, the Smart Data tab is visible by default in the Log window at the bottom of the page. This tab is not supported with the SOA Debugger. You can hide the tab after initial starting the SOA Debugger. After that the setting is remembered and the tab is not displayed.

OAuth Security Policy Is Not Supported with the REST Adapter

1. Bug:18916662
2. Added: 24-June-2014
3. Platform: All

You cannot attach an OAuth security policy to a REST service or reference binding component.

Explicitly Setting Local Optimization to the Same Value for ws.binding Endpoints

1. Bug:17975064
2. Added: 24-June-2014
3. Platform: All

If the ws.binding of a reference or service does not explicitly disable web service local optimization, but the callback ws.binding does, instance tracking cannot reassociate the callback with the original request. This is because instance tracking assumes both endpoints are configured similarly and only persists the callback properties when going over SOAP. Otherwise, it expects the properties to be propagated in-memory.

Ensure that local optimization is the same value for all endpoints. For example, set the oracle.webservices.local.optimization property to false for all endpoint ws.bindings in the composite.xml file to disable local optimization.

• For the service binding component:
  Copy

  
   
       
   <service name="attachmentbpelprocess_client_ep"
              ui:wsdlLocation="AttachmentBPELProcess.wsdl">
       <interface.wsdl
   interface="http://xmlns.oracle.com/Application1_jws/ReplyAttachment
  WSBPELProj/AttachmentBPELProcess#wsdl.interface(AttachmentBPELProcess)"                  
   callbackInterface="http://xmlns.oracle.com/Application1_jws/
  ReplyAttachmentWSBPELProj/AttachmentBPELProcess#wsdl.interface
  (AttachmentBPELProcessCallback)"/>
       <binding.ws
   port="http://xmlns.oracle.com/Application1_jws/ReplyAttachmentWSBPELProj
  /AttachmentBPELProcess#wsdl.endpoint(attachmentbpelprocess_client_ep/
  AttachmentBPELProcess_pt)" streamIncomingAttachments="true">
         <property name="oracle.webservices.local.optimization">false
  </property>
       </binding.ws>
       <callback>
         <binding.ws
   port="http://xmlns.oracle.com/Application1_jws/ReplyAttachmentWSBPELProj
  /AttachmentBPELProcess#wsdl.endpoint(attachmentbpelprocess_client_ep/
  AttachmentBPELProcessCallback_pt)"
         streamOutgoingAttachments="true">
         <property name="oracle.webservices.local.optimization">false
  </property>
         </binding.ws>
       </callback>
     </service>
  
     
  

• For the reference binding component:
  Copy

  
   
       
        <reference name="Service1"           
  ui:wsdlLocation="http://slc05mor.us.oracle.com:7003/soa-infra/services/
  default/ReplyAttachmentWSBPELProj/AttachmentBPELProcess.wsdl">
       <interface.wsdl
   interface="http://xmlns.oracle.com/Application1_jws/
  ReplyAttachmentWSBPELProj/AttachmentBPELProcess#wsdl.interface
  (AttachmentBPELProcess)"                    
   callbackInterface="http://xmlns.oracle.com/Application1_jws/
  ReplyAttachmentWSBPELProj/AttachmentBPELProcess#wsdl.interface
  (AttachmentBPELProcessCallback)"/>
       <binding.ws
   port="http://xmlns.oracle.com/Application1_jws/ReplyAttachmentWSBPELProj/
  AttachmentBPELProcess#wsdl.endpoint(attachmentbpelprocess_client_ep/
  AttachmentBPELProcess_pt)"               
   location="http://slc05mor.us.oracle.com:7003/soa-infra/services/default/
  ReplyAttachmentWSBPELProj/attachmentbpelprocess_client_ep?WSDL"
                   soapVersion="1.1" streamOutgoingAttachments="true">
        <property name="oracle.webservices.local.optimization">false</property>
         <property name="weblogic.wsee.wsat.transaction.flowOption"
   type="xs:string" many="false">WSDLDriven</property>
       </binding.ws>
       <callback>
         <binding.ws
   port="http://xmlns.oracle.com/Application1_jws/ReplyAttachmentWSBPELProj/
  AttachmentBPELProcess#wsdl.endpoint(attachmentbpelprocess_client_ep/
  AttachmentBPELProcessCallback_pt)" streamIncomingAttachments="true">
         <property name="oracle.webservices.local.optimization">false</property>
         </binding.ws>
       </callback>
     </reference>
     
  

For more information about local optimization, see Section "Configuring Local Optimization" of Administering Oracle SOA Suite and Oracle BPM Suite.

Validation Issues with Business Rules in Oracle SOA Composer

1. Bug:18750236
2. Added: 24-June-2014
3. Platform: All

When using Oracle SOA Composer, note the following validation issues and workarounds:

• When you validate added business phrases, the Business Phrases Editor shows the following message:

  Click to create a new ruleset, then add Decision Tables, Verbal Rules and General Rules.

  If you click Add Rulesets , the existing rules are deleted.

  Workaround: Select any other tab, then return to the Business Phrases tab to retain the rules.

• If you validate added business phrases and do not receive validation errors, note that none of the options available in the Business Phrases Editor work (for example, Post Validation, Add Phrase, Add Parameter, and Make/Clear Draft).

  Workaround: Select any other tab, then return to the Business Phrases tab to resolve this issue.

Specifying SOAP Version 1.2 in the HTTP Binding is Not Supported

1. Bug:18741129
2. Added: 24-June-2014
3. Platform: All

If you are using HTTP binding and specify the soapVersion as 1.2 in the composite.xml file:

    
    
     <service name="TestHTTPBinding" ui:wsdlLocation="TestHTTPBinding.wsdl">
    <interface.wsdl
interface="http://xmlns.oracle.com/pcbpel/adapter/http/A-OS46TCO_
01/TestHTTP/TestHTTPBinding#wsdl.interface
(Request_Response_ptt)"/>
    <binding.ws
port="http://xmlns.oracle.com/pcbpel/adapter/http/A-OS46TCO_
01/TestHTTP/TestHTTPBinding#wsdl.endpoint
(TestHTTPBinding/Request_Response_pt)"
                location="TestHTTPBinding.wsdl"supports="http"
                soapVersion="1.2">
      <property name="http.verb" type="xs:string" many="false">POST
      <property name="http.payload" type="xs:string"
many="false">url-encoded
    </binding.ws>
  </service>

    
  

The following exception error is thrown when the composite is invoked:

version of incoming SOAP message does not match the one returned from provider

SPENGO Policies Do Not Work with REST Services and References in SOA Composite Applications

1. Bug:18713341
2. Added: 24-June-2014
3. Platform: All

REST services and references with attached Simple and Protected GSSAPI Negotiation Mechanism (SPENGO) Oracle Web Services Manager (OWSM) polices do not work. Avoid using SPENGO policies with REST adapters.

Instance Tracking Issue with Oracle Service Bus to Oracle SOA Suite Fault Propagation

1. Bug:18555339
2. Added: 24-June-2014
3. Platform: All

Assume you have a scenario in which SOA composite 1 invokes Oracle Service Bus, which then invokes SOA composite 2 (which is currently shut down). When SOA composite 1 is invoked, Oracle Service Bus returns a fault to SOA composite 1 because SOA composite 2 is shut down. This fault is a recoverable fault and the flow instance state is displayed as Recovery in the Flow Instances page in Oracle Enterprise Manager Fusion Middleware Control.

When SOA composite 2 is started, you retry the fault and the flow completes. The flow trace is correctly displayed, but the flow instance state is displayed as Failed, which is incorrect. It should be displayed as Completed. Also, the count of faults may be more than you expect.

Workaround: To see the correct flow instance state of Completed and the correct number of faults, configure the error handler with a reply with failure action in the Oracle Service Bus pipeline to properly propagate the fault ID between SOA composite 2 and SOA composite 1. For configuration information, see Administering Oracle Service Bus.

After configuration is complete and this scenario is retried, the flow instance state is correctly displayed as Completed after a successful fault recovery and the correct number of faults is displayed.

Server Exception Error to Ignore

1. Bug:18608971
2. Added: 24-June-2014
3. Platform: All

The following exception error that appears in the server logs is caused by several actions, from terminating the browser to closing the tab browser in which you are running. The exception is also caused by browser reloading or by a network failure. This error is benign, and can be ignored.

 Servlet failed with an IOException. 
 java.io.IOException: Broken pipe
 at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
 at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47) 

Audit Trail Issue for Composites that Include Oracle Mediator When Using a Multibyte Character Set

1. Bug:18617793
2. Added: 24-June-2014
3. Platform: All

When the server encoding is a non-UTF-8 type such as ISO-8859-1, after deploying a SOA composite application to the server that includes an Oracle Mediator service component and initiating a business flow instance, the payload in the View Payload link of the Audit Trail for the Oracle Mediator is corrupted.

This is a user interface issue. The real payload sent through Oracle Mediator is not corrupted.

This issue does not occur when the server encoding is UTF-8.

Oracle SOA Composer Issues and Workarounds

1. Bug:18634925
2. Added: 24-June-2014
3. Platform: All

Note the following Oracle SOA Composer issues and workarounds.

1. The Oracle SOA Composer Links menu may redirect you to incorrect URLs for Oracle BPM Worklist, Oracle Business Process Composer, and others. To access the correct URL, remove the extra /soa in the launched application URL.
2. If Oracle SOA Composer hangs and you cannot log out, restart your browser.

Browsing the 11g UDDI Registry for 12.1.3 WSDL Files

1. Bug:18459066
2. Added: 24-June-2014
3. Platform: All

When configuring a 12.1.3 reference binding component in the Create Web Service dialog, configuration does not successfully complete when the WSDL being browsed for is in the 11g UDDI Registry.

For example, assume you perform the following steps:

Web service creation cannot successfully complete.

1. 1. Create and deploy a SOA composite application.
2. 2. Log in to Oracle Enterprise Manager Fusion Middleware Control.
3. 3. Select the Show WSDL and endpoint URI link on the composite home page.
4. 4. Copy the WSDL location for the composite. For example:
5. http://host:port/soa-infra/services/default/HelloUDDI/hellouddibpel_client_ep?WSDL
6. 5. Publish the WSDL in the 11g UDDI Registry. For example:
   1. 1. Go to the 11g UDDI Registry.
   2. http:host:port/registry/uddi/web
   3. 2. Select the Publish option.
   4. 3. Select Add Business and enter the name HelloUDDI.
   5. 4. Select Add WSDL. The business key is automatically selected.
   6. 5. Enter the WSDL location:
   7. http://host:port/soa-infra/services/default/HelloUDDI/hellouddibpel_client_ep?WSDL
   8. 6. Publish the WSDL file.
7. 6. Create a new SOA composite with a BPEL process.
8. 7. Create a SOAP reference binding component and wire it to the BPEL process.
9. 8. In the Create Web Service dialog of the reference binding component, select the Find Existing WSDLs icon to the right of the WSDL URL field.
10. 9. In the WSDL Chooser dialog, select UDDI.
11. 10. In the UDDI Registry, select Business Entities > HelloUDDI > hellouddibpel_client_ep.
12. 11. Enable the checkboxes for the following UDDI deployment options:
    • Dynamically resolve the SOAP Endpoint location at runtime.
    • Dynamically resolve the concrete wsdl location at runtime.

Workaround:

When the service in the UDDI Registry is invoked, the log entries sent in the attachment are observed in the SOA diagnostic logs.

[2014-04-01T17:05:29.815-07:00] [soa_server1] [NOTIFICATION] [] [oracle.fabric.common.uddiurl.resolver.impl] [tid: [ACTIVE].ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: 3e5a3438-effd-4e6b-abad-f71601d211fb-00006120,0:72] [APP: soa-infra] [J2EE_APP.name: soa-infra] [J2EE_MODULE.name: fabric] [WEBSERVICE.name: consumeuddibpel_client_ep] [WEBSERVICE_PORT.name: ConsumeUDDIBPEL_pt] [oracle.soa.tracking.FlowId: 160007] [oracle.soa. tracking.InstanceId: 160027] [oracle.soa.tracking.SCAEntityId: 180014] [composite_name: ConsumeUDDIService!1.0] [FlowId: 0000KKVkK1B2zGI_Ip1Fif1JEG0S000007] Connecting to http:// example.us.mycompany.com:7201/registry/uddi/inquiry

[2014-04-01T17:05:29.815-07:00] [soa_server1] [NOTIFICATION] [] [oracle.fabric.common.uddiurl.resolver.impl] [tid: [ACTIVE].ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: 3e5a3438-effd-4e6b-abad-f71601d211fb-00006120,0:72] [APP: soa-infra] [J2EE_APP.name: soa-infra] [J2EE_MODULE.name: fabric] [WEBSERVICE.name: consumeuddibpel_client_ep] [WEBSERVICE_PORT.name: ConsumeUDDIBPEL_pt] [oracle.soa.tracking.FlowId: 160007] [oracle.soa. tracking.InstanceId: 160027] [oracle.soa.tracking.SCAEntityId: 180014] [composite_name: ConsumeUDDIService!1.0] [FlowId: 0000KKVkK1B2zGI_Ip1Fif1JEG0S000007] Searching for uddi:a61c1f60-b050-11e3-acc5-aea69df0acc5

1. Create an initial SOAP reference binding component that you wire to the BPEL process and select only the Dynamically resolve the SOAP Endpoint location at runtime option after browsing for and selecting the WSDL file.
2. Create a second SOAP reference that you wire to the BPEL process (below the first reference) and select both options for UDDI deployment after browsing for and selecting the WSDL file:
   • Dynamically resolve the SOAP Endpoint location at runtime.
   • Dynamically resolve the concrete wsdl location at runtime.
3. When the service in the UDDI Registry is invoked, the log entries sent in the attachment are observed in the SOA diagnostic logs.

SOA Debugger Hangs Intermittently While Receiving a Response Back From a Human Workflow Component

1. Bug:18450892
2. Added: 24-June-2014
3. Platform: All

On rare occasions, the SOA debugger may hang while receiving a response back from a human workflow component. This typically occurs only the first time with a freshly deployed composite.

WorkAround: Stop and then restart the current debugging session.

Deploying 11g SOA Composite Applications with the Spring Component on Oracle SOA Suite 12c

1. Bug:18401387
2. Added: 24-June-2014
3. Platform: All

For 11g SOA composite applications with the spring component to be successfully deployed on the Windows version of Oracle SOA Suite 12c, you must make the following update:

1. 1. Open the Middleware_Home\user_projects\domains\domain_name\bin\setDomainEnv.cmd file.
2. 2. Change the forward slash (/) to a back slash (\) in the following line:
3. -Doracle.xml.schema/Ignore_Duplicate_Components=true
4. 3. Save the file and restart the SOA server.

Refreshing the SOA Composite Editor to Make WSDL Files Accessible

1. Bug: 18951855
2. Added: 24-June-2014
3. Platform: All

When WSDLs are not accessible in the SOA Composite Editor during design time, the components using these WSDLs are flagged with an appropriate warning. Oracle SOA Suite does not continue to retry accessing these WSDLs to reduce the hang times and exceptions reported in the log file. If you fix access to a WSDL and want the SOA Composite Editor or SOA tools to retry accessing them, click the Refresh Diagram button on the toolbar.

BPEL Process Invocations of Business Rules Fail When Composite Names Exceed 200 Characters in Length

1. Bug: 17993789
2. Added: 24-June-2014
3. Platform: All

When a composite name is more than 200 characters in length and a BPEL process calls a business rules (decision service) component, a fault is thrown and the business flow instance state is shown as failed.

As a workaround, specify a composite name that does not exceed 200 characters.

User with Monitor Permission on Only One Partition Can View a Multipartition Flow Trace

1. Bug: 17992512
2. Added: 24-June-2014
3. Platform: All

In a flow trace that extends across multiple partitions, a user with the Monitor permission on only one partition can still view the entire flow trace.

For example, assume an environment in which composite1 in partition1 calls composite2 in partition2. This flow trace should be visible to only the user with the Monitor permission on both partitions: partition1_Monitor and partition2_Monitor.

However, the user with the Monitor permission on only one of the partitions can view the entire flow trace.

Oracle JDeveloper and ant Command Deploy SAR File to Different Directories

1. Bug: 17992331
2. Added: 24-June-2014
3. Platform: All

The ant-sca-package command and Oracle JDeveloper deploy the SAR file to different directories.

When a JDeveloper project is deployed as a SAR, the deployable composite JAR (for this example, named sca_composite_rev1.0.jar) is created in the Application_Directory\Project_Directory\deploy directory.

When the project is packaged using the ant -f ant-sca-package.xml command from the mwhome/soa/bin directory, the sca_composite_rev1.0.jar file is created in the Project_Directory\SOA\deploy directory. In this case, an additional directory named SOA is created.

Flow Instance State and Flow Trace Behavior for Composites with WS-AtomicTransaction (WS-AT) Transactions

1. Bug:18068151
2. Added: 24-June-2014
3. Platform: All

Instance tracking fails when WS-AT is used for transaction coordination in composites.

Consider the following case in which composite 1 calls composite 2:

• In composite 1 on the reference side (which calls composite 2), the WS-AT transaction property is set to WSDLDriven:

  <property many="false" name="weblogic.wsee.wsat.transaction.flowOption" type="xs:string">WSDLDriven</property>

• In composite 2 on the service endpoint side, the WS-AT transaction property is set to either SUPPORTS or MANDATORY:

  <property name="weblogic.wsee.wsat.transaction.flowOption" type="xs:string" many="false">SUPPORTS</property>

  or

  <property name="weblogic.wsee.wsat.transaction.flowOption" type="xs:string" many="false">MANDATORY</property>

If composite 1 is invoked (which then calls composite 2), a nonrecoverable fault occurs with the following error message:

In the flow trace, entries for composite 2 are missing. Also, the flow instance state is shown as failed instead of completed. In the SOA server logs, an exception similar to the following is logged:

Internal Exception: java.sql.SQLException: ORA-01591: lock held by in-doubt distributed transaction 5.28.4069

Error Code: 1591 Call: INSERT INTO SCA_FLOW_INSTANCE (FLOW_ID, ACTIVE_COMPONENT_INSTANCES, ADMIN_STATE, COMPOSITE_SCA_ENTITY_ID, CONVERSATION_ID, FLOW_CORRELATION_ID, CREATED_BY, CREATED_TIME, ECID, PROPERTIES, PURGEABLE, RECOVERABLE_FAULTS, RESEQUENCER, SCA_PARTITION_ID, TENANT_ID, TEST_CASE, TEST_RUN_ID, TEST_RUN_NAME, TEST_SUITE, TITLE, UNHANDLED_FAULTS, UPDATED_BY, UPDATED_TIME, VERSION) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) bind => [9, 0, -1, 235, null, 0000KEAuWA59tXHLIuT4if1Iot5_00000f, anonymous, 2014-01-13 01:23:48.485, 0000KEAuW9_9tXHLIuT4if1Iov2^000001, null, null, 0, false, 1, -1, null, null, null, null, null, 0, anonymous, 2014-01-13 01:23:48.649, 1]

Query: InsertObjectQuery(SCAFlowToCompositeInstanceAssociationImpl [compositeId=11, flowId=9, activeComponentInstances=0, adminState=-1, title=null, version=1, containsOriginal=true, cloneMemory=false]) at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransact ionManager.java:1013)

Restrictions on Enabling the Global Discovery Cache

Unable to get 12c BAM Adapter to work with 12c BAM

When we install SOA 12c, the default BAM Adapter that gets installed is the 11g BAM Adapter. The 12c Adapter does not work.

Workaround: Undeploy the "OracleBamAdapter" (which is the BAM11g adapter) deployment and deploy "bamjcaadapter.rar" which is located in the $ORACLE_HOME/soa/bam/lib directory of the 12c install. This will install the BAM 12c Adapter. Next, change the JNDI references in the WebLogic console to point to BAM 12c instance and restart the SOA server so it can pickup the changes. For detailed information on updating JNDI references, see the 12c user guide for Monitoring Business Activity with Oracle BAM.

No support for multiple BPM domains feeding into BAM domain

We do not support multiple separate BPM domains feeding into 1 BAM domain.

Workaround: This is as per design. This feature is only supported for 1 SOA or BPM domain configured to communicate with 1 BAM domain. Multiple SOA or BPM domains sending data to a single separate BAM domain is NOT supported. Also, in order to make this work: Both nodes must have BAM and SOA/BPM managed server configured and when you enable Analytics on both nodes, you need to start ALL managed servers (BAM and SOA/BPM) on both nodes.

CQL query not re-started on inserting into empty slow changing dimension DO

The CQL Query does not restart when you insert it into an (empty) slow changing dimension.

Workaround: If a DO marked 'slow changing dimension' it should not be empty. It should have at least one record in it. Only then, a logical Do based on it can be used in Active Views/Continuous queries.

User may receive script error "Access is Denied" when BAM report is loading/opening from an ADF page.

User may receive script error "Access is Denied" when BAM report is loading/opening from an ADF page. This happens with all report views, and is not browser-specific. This error only shows up when script debugging is ENABLED.

When script debugging IS enabled, these browser advanced settings must be set as follows:

Workaround: You can get past the error by clicking 'No' to script error.

Treemap Shows Wrong Data Values

In a treemap view, numeric data may have decimal values different from those in the underlying query.

Workaround: Obtain and apply a patch from Customer Support after installation.

Allow Updating CQ Logging Levels from EM

Updating continuous query loggers from Oracle Enterprise Manager Fusion Middleware Control is not possible.

Workaround: Update the logging.xml file in the FMW_HOME/user_projects/domains/WLS_SOA/config/fmwconfig/servers/bam_server1/logging directory.

Add the following to the log_handlers section:

  
<log_handler name='beam-cqservice-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory' level='TRACE:32'>
    <property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/beam/cqservicelogging/cq.log'/>
    <property name='maxFileSize' value='10485760'/>
    <property name='maxLogSize' value='104857600'/>
    <property name='encoding' value='UTF-8'/>
    <property name='supplementalAttributes' value='J2EE_APP.name,J2EE_MODULE.name'/>
</log_handler>
  
  
  

Add the following to the loggers section:

<logger name='oracle.beam.cqservice' level='TRACE:32' useParentHandlers='false'>
    <handler name='beam-cqservice-handler'/>
</logger>
<logger name=' oracle.soa.cep' level='TRACE:32' useParentHandlers='false'>
    <handler name='beam-cqservice-handler'/>
</logger>

Entering a Business Query Name Automatically Repeats the Query Name Multiple Times

When you enter a Name in a creation dialog, sometimes the name you type is repeated multiple times.

Workaround: Sometimes clearing the browser cache resolves the issue. You can also type the name outside of BAM, copy it, and paste it into the Name field.

Purging Data (from DO UI) Does Not Reflect in Graph (ADS or Refresh)

Purging data from a data object does not remove the data from a currently active dashboard, even if the dashboard is refreshed.

Workaround: Close and reopen the browser window.

Items in Designer Trees Should Be Ordered

Items in the left navigation pane of the Designer page are not ordered alphabeticaly or by type.

Workaround: None

Shading for Columns and Rows Should Have Higher Contrast

For List, Action List, and Collapsed List views, you can set Row Banding Interval or Column Banding Interval properties. However, the shade used for the banded rows or columns is faint.

Workaround: None

Not Able to Select Calculated Fields in Flat Queries

Flat queries do not support aggregated data, therefore calculated fields that include ag gregations are not supported in flat queries.

Workaround: Use group queries for calculated fields that include aggregations.

If you must use a flat query for a calculated field that includes an aggregation, there is a more complex workaround. Use a continuous query with an "Insert values into a data object" alert action to copy the calculated field data to a write-back data object. Then use a flat query to fetch data from the write-back data object.

Get OP Returning Different Representations of Decimal Values in JDBC12 vs. JDBC11

The Get operation of BAM web services displays JDBC11 and JDBC12 decimal values between 1 and -1 differently. JDBC11 does not include a zero to the left of the decimal point, but JDBC12 does.

Workaround: None

Gauge Tick Label Underline Property Does Not Work in Firefox

The Axis properties of Dial and Statusmeter gauge views allow you to format the text of the tick labels. You can make the labels bold, italic, or underlined. Tick label underlining does not appear in the Firefox browser.

Workaround: None

User Actions (Browser Resize, Navigator Collapsing) Cause Whole Dashboard Refresh

If a user performs actions such as resizing the browser window or hiding the prompts pane, the dashboard refreshes.

Workaround: None

Cannot Add Actions Unless Actions Are Expanded or Refreshed

In a view, when you select Runtime-Interaction and then select Actions, you can't add an action to an action button unless the Actions section is expanded.

Workaround: Expand the Actions section by clicking the arrow to the left of Actions. If the section is already expanded, then collapse it and expand it again.

Changing a Query's Measure Can Break Its Views

If you create a query, create a view based on the query, change a measure that the query retrieves, then edit the view properties, the view sometimes breaks, and further view edits cannot be saved.

Workaround: If you change a query, resave the views based on it immediately, without editing the properties. Then you can edit and save the view properties.

Action List - Error When Trying to Update Date Fields

In an Action List view with an Insert or Update action, problems can occur if the Action List column name and the data object column name don't match. This is especially likely for datetime fields.

Workaround: Obtain and apply a patch from Customer Support after installation.

BamJobSchedDataSource Exception in Console

When BAM Composer and Oracle Enterprise Manager Fusion Middleware Control are both open, a BamJobSchedDataSource exception sometimes appears in the BAM console logs.

Workaround: None

Pivot Tables - Pivot Changes Are Persisted Without Saving

If you open a pivot table, pivot the data, close it without saving, and reopen it, the pivot is persisted as if it had been saved.

Workaround: None

Queries Without Group By Selections Not Allowed for Pie Charts

A pie chart view cannot be based on a query with no dimensions selected.

Workaround: None

Value Formatting with Table Charts Fails with Active Data

Value formatting properties applied to Table views do not work on active data.

Workaround: None

Why Do Chart Views Only Show Column Names to Users (Not Display Names)?

Chart views in dashboards show internal column names instead of display names.

Workaround: None

Out Of Memory Error When Starting a Query on a Logical Data Object

Sometimes a continuous query based on a logical data object with many columns defined uses too much computer memory.

Workaround: Simple or derived data objects that contain only dimensions should have the Slow Changing Dimension option checked.

JNDI Lookup Failure for Remote UMS JMS Server

In a high-availability environment in which one BAM managed server fails, alert actions that send email may not work due to JNDI lookup failure on the Oracle User Messaging Service (UMS) server.

Workaround: Although BAM 12.1.3 supports automatic service migration, UMS 12.1.3 does not. One single BAM managed server hosts the BAM JMS and JTA services for all members of the cluster. Therefore, the solution is to restart the failed BAM server and fail back the migrated UMS services to their original managed server. See Section 18.2.3, "Failing Back Oracle BAM Services After Automatic Service Migration Occurs," in Enterprise Deployment Guide for Oracle SOA Suite.

If a BAM server restart is not compatible with your system's recovery time objective, you can configure UMS with Advanced Queuing (AQ) JMS instead of the default JMS provider. Refer to Appendix B, "Configuring User Messaging Service with AQ JMS," in Administering Oracle User Messaging Service.

"Is In List" in Group Filters Only Supports Lists Consisting of 1 Element

The alert event "When a data field in a data object meets specified conditions" has a Group Filters option. The "is in list" comparison operation does not work in Group Filters if the list contains more than one value.

Workaround: Create a separate filter for each value.

Not Using Update Icon for Dependent View After Query Filter Change Requires It

If you change a query filter to use a different column, the icons for the views using that query fail to change to a red X indicating that they need to be resaved. However, if you do not resave these views, dashboards with these views use the original filter instead of the new filter.

Workaround: Take note of the list of affected entities when you save the changed query, and be sure to resave all of them.

BAMCommand Cannot Export a Project If It Has Been Renamed

Exporting a project using the renamed display name results in a "project not found" error.

Workaround: Use the Rename command to display the internal name, then export the project using the internal name.

Formatting Y1 and Y2 at the Same Time Gives a Pop-up Error to the User

If you format both Y-axes of a Dual-Y chart without clicking Apply, then when you do click Apply, a pop-up appears with identical uninformative error messages.

Workaround: Click Apply after changing properties for each Y-axis.

HA - DO Based Alerts Not Firing Consistently

In a high-availability envinonment, when server migration takes place, continuous queries are restarted. If any alert events occur during this restart period, they are lost.

Workaround: None

Combo Charts Are Blank When the Legend Uses a Centered Stepped Line And No Bar

Graph Type is a Legend property specific to Combo views that allows you to choose how each data field is displayed. If Centered Stepped Line is included but Bar Graph is not, the Combo view displays no data.

Workaround: None

Operand of Like Should Be String

The "is like" filter comparison operator only works on VARCHAR data.

Workaround: None

"Last Pinged" in Viewset Monitoring Shows Current Time Whenever Refreshed

When you refresh Viewset Monitoring, the Last Pinged column values change to the current time instead of the actual last pinged times.

Workaround: None

Day Should Be DayOfYear in Column Name for Preview and Edit Mode

A BAM 11g query imported into BAM 12c that uses units of Day or smaller in a time series, or another entity based on such a query, may display errors when saved.

Workaround: Obtain and apply a patch from Customer Support after installation.

Only Able to Add 5 Dashboards to Tabular Dashboard Instead of 6

Only five dashboards can be added to a tabbed dashboard, but the error message says that the limit is six.

Workaround: None

Dashboard Stops Showing Views After Browser Refresh

If you click the browser refresh button for a dashboard window, sometimes only some of the views display.

Workaround: Close and reopen the dashboard.

Narrow Views Clip Pie Charts Such That the Values/Percentages Are Not Visible

Although everything is visible in the view editor, the dashboard editor and the live dashboard may either not display the pie slice labels or display them overlapping the legend text when the pie chart is narrow.

Workaround: None

Config.xml Not Updated When BAM Managed Server Name Is Changed

JMS JNDI errors may occur if WebLogic managed servers for BAM are renamed after the domain has been created.

Workaround: None

WebLogic Server BAM Server Startup Throws Exceptions

Startup of WebLogic managed servers for BAM sometimes throws exceptions such as, "Error occurred in looking up Queue in JNDI, skipping." This error refers to the JMS queue used by Oracle User Messaging Service (UMS).

Workaround: Although BAM 12.1.3 supports automatic service migration, UMS 12.1.3 does not. One single BAM managed server hosts the BAM JMS and JTA services for all members of the cluster. Therefore, the solution is to fail back the migrated UMS services to their original managed server. See Section 18.2.3, "Failing Back Oracle BAM Services After Automatic Service Migration Occurs," in Enterprise Deployment Guide for Oracle SOA Suite.

If a BAM server restart is not compatible with your system's recovery time objective, you can configure UMS with Advanced Queuing (AQ) JMS instead of the default JMS provider. Refer to Appendix B, "Configuring User Messaging Service with AQ JMS," in Administering Oracle User Messaging Service.

BAM Server Becomes Unresponsive with Large Table Datasets

Views with large data sets or dashboards with multiple large data sets sometimes do not finish loading. Errors are thrown on the BAM server after the view or dashboard times out. This makes the BAM server unresponsive in the process.

Workaround: Increase the memory and heap sizes as described in the "Tuning Oracle Business Activity Monitoring" section in the "Oracle Fusion Middleware Tuning Performance" book.

BAM Data Control in 12c Document Update

In BAM 11g PS6, you can download the SOA extension for BAM data control and configure it in JDev 11g, which allows you to create BAM data control using JDev and integrate it with ADF applications. In BAM 12c, there is no JDev support for data control. If you download the SOA extension for BAM data control and try to configure it in JDev 12c, it may cause unexpected behavior.

Workaround: None

ADS Doesn't Work Consistently for Updates with Multiple GROUP BY Queries

Active Data doesn't work as expected in a view based on a Group SQL Query with more than one dimension (grouping field).

Workaround: None

Doc ODI Action in BAM User Guide

For users of both BAM 12c and ODI 12c, the "Run an ODI Service" alert action is available. To enable this action:

To use this action:

Workaround: None

Scheduled KPI: KPI_TIMESTAMP Cannot Be Mapped to DATETIME Field

When you create a scheduled KPI with an "Insert values into a data object" alert action, you cannot map a DATETIME type column to the KPI_TIMESTAMP event output field. The following message appears:

The selected field's datatype does not match with that of the data object column. Please choose a different field.

Workaround: Change the type of the column in the data object from DATETIME to VARCHAR. If other uses of the column make changing the type undesirable, create a realtime KPI or a continuous query that uses the "Insert values into a data object" action instead.

BPMContentViewer Role Is Not Documented

Three application roles defined in Oracle Enterprise Manager Fusion Middleware Control determine access to Oracle Business Process Management (BPM) data in BAM:

Workaround: None

Data Control ID for Watchlist Business View Is Missing Project Name

This is a high severity bug.

The data control for a KPI watchlist does not have the project name in its ID, unlike data controls corresponding to business queries. Therefore, if you create watchlists with the same name in two different projects, both watchlists will have the same ID, and this will cause problems.

If the second project was created using BAM Composer, its watchlist will not display any data.

If the second project was imported using the BAMCommand tool, its watchlist will display incorrect data.

If you attempt to delete the watchlist in the second project, BAM will show a page that displays the "Error 500--Internal Server Error" message.

This error message is a result of corrupted ADF metadata. Access to all ADF URLs results in the same "Error 500--Internal Server Error" message.

Workaround: Obtain and apply a patch from Customer Support after installation. If the Error 500 message occurs, contact Customer Support for assistance.

Slice and Dice - Search Tip Needed to Clarify Wildcards and Case Sensitivity

Dashboard filtering (slice and dice) is case sensitive and uses % as a wildcard character, but the user interface does not explain this.

Workaround: None

Missing Springboard Images

When a dashboard containing image cells is exported, the ZIP file does not contain the images.

Workaround: Obtain and apply a patch from Customer Support after installation.

Dashboard Thumbnails Are Not Shown When Projects Are Imported

When a project containing dashboards is imported, the dashboard thumbnails are not shown in the BAM Viewer (Home page).

Workaround: Obtain and apply a patch from Customer Support after installation.

Document Steps for Integrating SOA 11g and BAM 12c Using a BAM Adapter

Oracle SOA Suite 11g does not integrate with BAM 12c by default.

Workaround: To integrate SOA 11g with BAM 12c, you must install an adapter.

Note: The OracleBamAdapter that is preinstalled with SOA 12c integrates SOA 12c with BAM 11g. Integration of SOA 12c with BAM 12c does not require an adapter.

Business Process Analysis Suite

No issue has been discovered at the time of this release. As additional issues and workarounds are discovered after the release, they will be listed here.

Business Process Management

Web Forms Global and Custom Themes are no longer supported in BP Composer

With Frevvo 5.2, Web Forms Global and Custom Themes are no longer supported in BP Composer.

Workaround: There is no workaround.

BPM Composer Application displays incorrect error messages when using the button to Edit Libraries

An error [unable to resolve class..] is shown when using external classes just imported.

Workaround: Ignore the error, close the code editor, and apply changes in Implementation tab. Save and close the project. Reopen the project and process, select the script task, and open implementation panel. Click Check Code button: the error message disappears.

Note: Even with the error message, the project is valid and can be deployed and executed without any issue.

File Type not detected when attachment is downloaded

The application is unable to detect the file type. It downloads a regular file without any extension.

Workaround: The user must make a note of the file type before downloading, so that the correct file extension can be used after downloading and saving the file from case UI.

Cancel option on Instance Migration Dialog does not work after Failover

When you are on the Grab and Migrate dialog and hit Cancel, the instance might still showing suspended state while it has actually resumed. This happens only when there has been a cluster failover.

Workaround: Click Refresh in the Table toolbar. This refreshes the table and also shows the proper status of the instance.

UCM Document Integration

When you have the UCM configured with Folders_g option, there are following issues with document integration:

These are known issues.

Workaround: There is no workaround.

UCM Document Integration - Human Task Document Upload

The following configuration steps must be followed in Human Task to upload a document if UCM is configured:

Document Integration Issues with UCM

UCM has the following issues with respect to document integration:

These are all known issues.

Workaround: There is no workaround.

OnScreen Validation Unavailable for Primitive Byte Type

The validation for a primitive data type is done in the back-end, but an OnScreen validation for the same is unavailable. If you provide an incorrect value for the byte datatype in Case Activity Form or Data Form, the UI does not indicate that it is an incorrect value; however, in the logs a java.lang.NumberForamtException is logged.

Workaround: There is no workaround.

iCalendar import function supports only specific formats

While using iCalendar as the resource to import calendar in BPM Workspace, no proper message is shown when the import fails. This is because the calendar import function of BPM supports only .ics format.

Workaround: There is no workaround.

Taskflow deployed to non-SOA Server does not show task details

When Human Task task forms are migrated from 11g to 12c, the task forms deployed on non-SOA server do not display in BPM Workspace inline frame. In this case, examine the following element in web.xml of your task form application:

<context-param>

<description>Security precaution to prevent click jacking:  bust frames if the ancestor 
window domain (protocol, host, and port) and  the frame domain are different. Another 
option for this parameter is  always and never.</description>

<param-name>org.apache.myfaces.trinidad.security.FRAME_BUSTING</param-name>
   <param-value>differentOrigin</param-value>
    </context-param>

Change the value of element to never as below and redeploy the application:

1. Bug:18047330
2. Added: 24-June-2014
3. Platform: All

   By default, the global discovery cache is not enabled. If you do enable the global discovery cache, access to partitions in not correctly handled.

   For example, when an Oracle SOA Suite administrator logs in to Oracle Enterprise Manaer Fusion Middleware Control, they should only see those partitions to which they have access. If the first user to log in to Oracle Enterprise Manaer Fusion Middleware Control is an administrator with access to all partitions,then the second administrator that logs in can also see all partitions, even if their privileges should restrict them to seeing only a subset of partitions.

   Retry Success Action in Fault Policy does not work

   1. Bug: 17873449
   2. Added: 24-June-2014
   3. Platform: All

   The retrySuccessAction will be executed only after successfulexecution. So, the only allowed action for retrySuccessAction is JavaAction.

   Oracle Mediator Component State Can Be Unclear During BPEL Callback Recovery

   1. Bug: 18275584
   2. Added: 24-June-2014
   3. Platform: All

   Assume you have the following business scenario:

   An Oracle Mediator calls an asynchronous BPEL process, receives a callback, and then calls a file adapter in the callback handler. The file adapter attempts to write messages to a directory, However, because the directory does not have write permissions, a fault occurs.

   Because this occurred during the callback to Oracle Mediator, the transaction rolls back to the asynchronous BPEL process and goes into callback recovery. For this case, the flow trace XML file that is accessible by selecting Actions > Flowtrace XML in the Trace table of the Flow Trace page shows the Oracle Mediator status as RUNNING,FAULTED,NON_RECOVERABLE, which is correct. However, Oracle Enterprise Manager Fusion Middleware Control shows the Oracle Mediator component instance as failed in the Trace table of the Flow Trace page. This is incorrect, because failed is a terminal state and the Oracle Mediator is still running. Do not become confused with the failed state shown in Oracle Enterprise Manager Fusion Middleware Control; the flow trace XMLfile shows it correctly as RUNNING,FAULTED,NON_RECOVERABLE.

   In addition, when the callback recovery successfully occurs, Oracle Mediator is shown as completed in the Trace table of the Flow Trace page in Oracle Enterprise Manager Fusion Middleware Control. Do not become confused with this transition from failed to completed for the Oracle Mediator component instance state in the Trace table of the Flow Trace page; this is the correct behavior.

   GlobalTxMaxRetry Property Setting Does Not Supercede the Composite-level jca.retry.count Property Setting

   1. Bug:18562118
   2. Added: 24-June-2014
   3. Platform: All

   Setting the GlobalTxMaxRetry property to 0 at the SOA Infrastructure level does not supercede the composite-level jca.retry.count property value. This is because the event delivery network (EDN) has dependencies on JCA adapters and the jca.retry.count property cannot be set to 0.

   For example, assume you perform the following steps:

   1. 1. Set the jca.retry.count property to 1 in the composite.xml file:
      Copy

      
      
      
        <service name="Inbound">
         <interface.wsdl
       interface="http://xmlns...#wsdl.interface(Inbound_PortType)"/>
          <binding.jca config="Inbound_db.jca">
             <property name="jca.retry.count">1</property>
             <property name="jca.retry.interval">1</property>
             <property name="jca.retry.backoff">2</property>
             <property name="jca.retry.maxInterval">6</property> 
          </binding.jca>
      </service>
      
      
                  
                      

   2. 2. From the SOA Infrastructure menu, select SOA Administration > Common Properties > More SOA Infra Advanced Configuration Properties.
   3. 3. Set GlobalTxMaxRetry to 0.

   Oracle Edge Analytics

   JVM Error Message while starting OEP Server Default Domain Using JDK 8 on ARM on Raspberry Pi Devices

   1. Bug: 20066619
   2. Added: 17-June-2015
   3. Platform: All

   When you try to start Oracle Event Processing Server default domain using JDK Version 8 Update 6 for ARM on Raspberry Pi devices, the following error appears:

   Error occurred during initialization of VM Server. VM is only supported on ARMv7+ VFP.

   The error is thrown from JVM directly because armv6 on Raspberry PI does not support -server parameter of JVM. Internally, Oracle Event Processing startup script startwlevs.sh changes JVM args from -server to -client to start Oracle Event Processing server.

   Workaround: None.

   Technology Adapters

   Email Subject and Body Garbled in UMS-Outbound when it is Non_UTF-8 Server Encoding

   1. Bug: 20673880
   2. Added: 21-August-2015
   3. Platform: All

   Email subject and body get garbled in UMS-outbound (SendNotification) scenario. This happens when server encoding is Non_UTF-8.

   The mail corruption happens when message is String Type or Opaque or when it is using XSD.

   Workaround: Restart the server, when the server encoding is changed to be UTF-8.

   XSLT Transform Mapper Activity in Oracle BPEL Process Manager

   1. Bug: 19558134
   2. Added: 25-May-2015
   3. Platform: All

   When you attempt to map a node from the source node to the target node in the XSLT Mapper for Oracle RightNow schemas, you receive the following error:

   Could not create element value-of

   In addition, the mapped element comes out of Target Parent Node.

   Workaround:

   Before performing any mapping, the Parent Node on the Target node is gray in color. Select this parent node on the target (for example, Contact), then right-click and select Create Node in XSLT.

   XA class support is deprecated for Oracle JCA Adapter for MQ Series

   1. Bug: 21049656
   2. Added: 07-May-2015
   3. Platform: All

   XA class support is deprecated for Oracle JCA Adapter for MQ series. Do not use XA with Oracle JCA Adapter for MQ Series or Transport.

   Enterprise Manager SHOWING NAME AS CUSTOM ADAPTER INSTEAD OF Oracle Service Adapter

   1. Bug: 19498997
   2. Added: 29-October-2014
   3. Platform: All

   A composite application that has been deployed and which is based on Oracle RightNow adapter shows as "Custom Adapter" in Fusion Middleware Control. This is a known issue.

   Workaround to Fix RuntimeException when RN WSDL, Imports Multiple External WSDLs

   1. Bug: 19685771
   2. Added: 29-October-2014
   3. Platform: All

   When the WSDL obtained from RightNow server instance inturn refers to multiple external WSDLs such as below, you might receive an exception.

   
   
       
   <wsdl:types>
   <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> 
   <xs:import namespace="urn:base.ws.rightnow.com/v1_2" 
   schemaLocation="http://day56-14801-sql-113h.qb.lan/cgi-bin/
   day56_14801_sql_113h.cfg/services/soap?xsd=base"/> 
       <xs:import namespace="urn:generic.ws.rightnow.com/v1_2" schemaLocation=
   "http://day56-14801-sql-113h.qb.lan/cgi-bin/day56_14801_sql_113h.cfg/services/soap?xsd=generic"/> 
     </xs:schema> 
   </wsdl:types>
    
     
   
   

   The exception you might receive is:

   
   javax.resource.ResourceException: Unable to create Cloud Operation: 
           at 
   oracle.tip.adapter.cloud.CloudAdapterInteraction.createCloudOperation(CloudAdapterInteraction.java:278) 
   Caused by: java.lang.RuntimeException: Could not create URL from 
   '../WSDLs/soap.wsdl' ...
   
   

   Workaround: Manually edit the RightNow adapter JCA file for the entry targetWSDLURL to point to the HTTP URL of the WSDL and not to the relative path of the generated WSDL.

   [LDAP] ADAPTER CONNECTION DOESN'T GET RELEASED

   1. Bug: 18356589
   2. Added: 12-June-2014
   3. Platform: All

   Connections established to Directory Server during runtime while using LDAP inbound operations such as EntryChange and ChangeLog do not get released.

   Workaround: The connection pool should be manually Reset or Force Reset for proper closure of stale connections.

   DBADAPTER CERTIFICATION MATRIX BUGS

   1. Bug: 18693782
   2. Added: 19-May-2014
   3. Platform: All

   There are list of bugs related to Database Adapter database-related certifications. Note that:

   • The TABLE Datatype is not supported in STOREDPROCEDURE for MSSQLSSERVER 2012
   • The CHAR FOR BIT Datatype does not work in Release 12.1.3 JDeveloper for the Derby Database.

   The following bugs are deferred to Release12.1.4. The list follows.

   • Bug 18242733 - puresql in sybase db not working with parameters
   • Bug 17978584 - dbadapter storedproc w.r.t. mysql db don't support resultset/introspect option
   • Bug 17862497 - no introspect option for db2 as400 stored proc returning result set.
   • Bug 17854230 - mysql year data type is not supported in dbadapter.
   • Bug 17479170 - insertion failed to "char for bit data" data type in derby.
   • Bug 17021522 - not able to use clob data type in storedprocedure returning resultset(db2/zos)
   • Bug 17021452 - clob datatype gives arrayindexoutofboundsexception for outdata(db2/zos)

   USE OF MDS WSDL IN SALESFORCE ADAPTER WIZARD

   1. Bug:18596082
   2. Added: 28-April-2014
   3. Platform: All

   This encapsulates two engineering bugs related to the SalesForce Adapter: 18559760 and 18593343

   BUG 18559760 - TRANSFER TO MDS FOR CLOUD SERVER WSDL IS NOT UPDATING JCA FILE

   You can transfer to MDS the integration the WSDL generated by a Cloud adapter and it will update the jca file (wsdlLocation attribute).

   However, if you try to transfer to MDS the Cloud Server WSDL, it does not find the reference in the jca file to update. The Cloud Server reference in the jca is just a value attribute in a property element: <property name="targetWSDLURL" value="../WSDLs/soap_wsdl_typed.wsdl"

   Workaround: Manually update any Salesforce adapter jca files after the WSDL is transfered to MDS.

   BUG 18593343 - UPDATING CLOUD ADAPTER THAT USE MDS WSDL IS GETTING WRONG URL

   If you created a Cloud adapter instance using a cloud server WSDL that was moved to MDS, the Connection wizard page displays an incorrect URL which can not be used (because the oramds: url was treated as a relative URL). To get past the Connection page requires that you specify the correct MDS URL.

   Workaround:You must use the browser button to select the MDS WSDL again

   STOREDPROC PROJECT MIGRATED FROM 11G TO 12C CREATE DUPLICATE XSD IF WIZARD RERUN

   1. Bug:18555120
   2. Added: 28-April-2014
   3. Platform: All

   The expected behavior is when a Database Adapter project has a storedProcedure and is migrated from 11g to 12c, followed by your re-running the stored procedure part of the Configuration Wizard, this re-running of the Wizard should not create a new xsd.

   However, when the storedProcedure wizard is rerun, it creates a new xsd under the schema folder in 12C JDeveloper, which is the expected path for a 12.1.3.0 project.

   Rerunning causes two similar xsd files for this project. You only see this occurrence when the Database Adapter uses stored procedures.

   Note also, that if database tables are used, the new schema is correctly written to the old schema location.

   Workaround: Manually delete the old xsd file and update the read.wsdl to reference the new xsd file.

   DIAGNOSTIC DUMPS FOR MSMQ,JDEDWARD,COHERENCE ADAPTERS NOT SUPPORTED

   1. Bug:18534524
   2. Added: 28-April-2014
   3. Platform: All

   DFW Dumps (Diagnostic Dumps) are supported for most Adapters. However, you cannot use these dumps for newer (that is, new for Release 12.1.3.0) Adapters such as the MSMQ, JDEdwards World and Coherence Adapters.

   MSMQ Adapter AUTOMATIONEXCEPTION: 0XC00E0051 OBSERVED WHEN RUNNING STRESS TESTS

   1. Bug:18505696
   2. Added: 28-April-2014
   3. Platform: All

   If you need to use the connection factory eis/msmq/transactional for both inbound and outbound, you can create a jca connection factory, for example, eis/msmq/transactional1 with the same properties. After that, eis/msmq/transactional can be used for the dequeue operation and eis/msmq/transactional1 can be used for the enqueue operation.

   LOOKAHEAD REQUIRED FOR LOOKFROM IN COMPLEXLOOKAHEAD TRANSLATION

   1. Bug:18442306
   2. Added: 28-April-2014
   3. Platform: All

   In the Native Format Builder wizard, when you create the NXSD for translating Native files, you can specify lookAhead in the schema to extract values based on the regular expression specified using lookForPattern. For extracting variable length records, because you do not know the length of record, you can use lookFrom and lookTill attributes in NXSD element, thus using JDeveloper Native Format Builder User Interface window, you can specify values to lookFrom and lookTill with or without skipUntil.

   However, when you select these in the JDeveloper User Interface and move the cursor next to see the NXSD source, the schema misses the lookAhead attribute and prints only lookFrom, lookTill and skipUntil attributes.

   Workaround: Explicitly write nxsd:lookAhead="0" with lookFrom and lookTill attributes.

   LOOKAHEAD ATTRIBUTE DONT COME WITH LOOKTILL IN JDEV UI NFB

   1. Bug:18442186
   2. Added: 28-April-2014
   3. Platform: All

   In the Native Format Builder wizard, when you create the NXSD for translating Native file, you can specify Look Ahead in your schema, to extract values based on regular expressions, specified using lookForPattern. For extracting variable length records, if you do not know length of record, you can use lookAhead with lookTill attribute in NXSD element; using the JDeveloper Native Format Builder User Interface window, you can specify values to lookAhead and lookTill with or without using skipUntil.

   However, when you select them in the JDeveloper User Interface and move the cursor next to see NXSD source, the schema misses the lookTill attribute.

   Workaround: Explicitly write nxsd:lookTill="literal" with the lookAhead attribute.

   JMS Adapter: TIBCO MESSAGES IN SOURCE QUEUE ARE NOT FLUSHED IF TIBCO SERVR IS RESTARTED

   1. Bug:18120859
   2. Added: 28-April-2014
   3. Platform: All

   You can configure the Oracle JMS Adapter to communicate with TIBCO JMS Provider (EMS Server).

   Note that messages in the Source Queue inside TIBCO are not flushed out after they are read if the TIBCO Server is stopped and restarted midway.

   Normally, the messages are flushed from the source Queue as and when read. However, if the TIBCO server is stopped and restarted midway through the processing, the source Queue will not be flushed of read messages.

   JMS Adapter supports connection retry functionality for MQ Provider.

   1. No Bug number.
   2. Added: 14-Jan-2014
   3. Platform: All

   Release 11 Adapter Guide stated that the JMS Adapter "Does not support connection retry functionality for MQ provider"; however, there is now such support in release 11 with the JMS Adapter.

   THERE IS NO TRUNCATE SUPPORT FOR MULTIBYTE STREAMING IN PS6

   1. Bug:14507570
   2. Added: 10-Sept-2013
   3. Platform: All

   Because using truncate in MultiByte Streaming Support can lead to corrupt data, truncate functionality has been removed from the Native Format Builder.

   UMS ADAPTER CLUSTER FAILOVER MAY LOSE MESSAGES

   1. Bug:16439192
   2. Added: 11-June-2013
   3. Platform: All

   Since XA is not supported for UMS Adapter Outbound in this Release, the UMS adapter cluster failover can lose messages.

   OUTBOUND UMS ADAPTER SHOULD USE UTF-8, NOT SERVER ENCODING IF NOT SPECIFIED

   1. Bug:16474430
   2. Added: 13-March-2013
   3. Platform: All

   For the outbound UMS adapter, the property jca.ums.msg.content-type can be used for specifying encoding. But if you do not set the value, the outbound UMS adapter will use server encoding for the email by default. When the SOA server is started in native encoding, for example iso8859-1, it cannot handle ccjk characters--the content will be garbled. Consequently, UTF-8 should be default encoding, not server encoding.

   Workaround: Set the jca property for the outbound UMS adapter as: jca.ums.msg.content-type = 'text/plain; charset=utf-8'

   SUPPORT FOR JMS ADAPTER TO CONNECT WITH IBM WEBSPHERE MQ JMS FOR MULTI INSTANCE

   1. Bug:15919519
   2. Added: 28-January-2013
   3. Platform: All

   You can configure the JMS Adapter to connect to IBM WebSphere MQ Multi-Instance Queue Managers. To do so, use a custom property called connectionNameList. You can use this property to specify the names and ports of the different instances.

   To make sure of the new custom property, you can set the FactoryProperties property in the WebLogic Server console for the used JNDI entry with the following settings:

   QueueManager=<QUEUEMANAGER_NAME>TransportType=1;ConnectionNameList=<HOST1>(<PORT1>),<HOST2>(<PORT2>);Channel=<CHANNEL_NAME>;

   ThirdPartyJMSProvider=true;ClientReconnectOptions=0

   JMS Adapter(11.1.1.7) Never Reconnects to TIBCO EMS 4.2.0 Due to Failing XA Recovery<

   1. Bug:15939498
   2. Added: 7-December-2012
   3. Platform: All

   The JMS Adapter does not reconnect to TIBCO EMS 4.2.0 because of failing XA recovery

   Workaround:All servers where the TIBCO resource is deployed must be shutdown and restarted, if the resource is deployed to a cluster then the entire cluster must be shutdown and restarted. When you are shutting down servers,ensure it is done gracefully to give a chance for prepared transactions to be written to the TLOG and recovered with commit after the server is restarted.

   DBADAPTER Coherence Feature Not Working On WLS 10.3.5

   1. Bug: 14233285
   2. Added: 13-Dec-2012
   3. Platform: All

   The Database Adapter Coherence Feature introduced in 11.1.1.6.0 works out of the box against WebLogic Server 10.3.6, but not WebLogic Server 10.3.5. This is because it must bundle a dependent jar, but no version of the jar is compatible with both 10.3.5 and 10.3.6.

   Workaround: To ensure the Database Adapter Coherence feature works against WebLogic Server 10.3.5 you must follow these steps:

   1. Find DbAdapter.rar in your SOA install.

   2. Remove the bundled 10.3.6 version of toplink-grid.jar from DbAdapter.rar

   3. Rebuild DbAdapter.rar with its existing manifest which looks for the shared library toplink-grid.

   4. Deploy toplink-grid.jar as a shared library named 'toplink-grid'.

   5. Restart the WebLogic Server.

   Some Specific Scenario Like Bug13803044 Needs a WLS Patch

   1. Bug: 14335927
   2. Added: 11-Oct-2012
   3. Platform: All

   Sequencing Polling Duplicate Records

   When using sequencing polling strategy, distributed polling, and non-XA datasources, EclipseLink may internally rollback the transaction releasing locks prematurely and allowing duplicate processing of the same row by another thread.

   Workaround:Apply the appropriate WebLogic Server patch.

   NLS:MBCS Named Table Cannot Be Used Due to Progress Database Limitation

   1. Bug: 14259650
   2. Added: 15-Oct-2012
   3. Platform: All

   Due to a Progress DB limitation, you cannot use MBCS as database object name, such as table name and column name because Progress database can't support MBCS named table/fields/indexes/sequences..

   Progress DB Stored Procedures Are Not Supported in the PS6 Release of the Database Adapter

   1. Bug: 14150479
   2. Added: 22-October-2012
   3. Platform: All

   Progress DB Stored Procedures are not supported in the PS6 release of the SOA Database Adapter.

   UMS Adapter Does Not Support XA Transactions On Outbound Side in the PS6 Release of the Database Adapter

   1. Bug: 14586707
   2. Added: 15-Oct-2012
   3. Platform: All

   The UMS Adapter does not support XA Transactions on the Outbound message side of transactions.

   IllegalStateException when WebSphere cleans up JCA connection pool

   1. Bug: 14275766
   2. Added: 11-Oct-2012
   3. Platform: All

   Following error is observed (at times) when running AQ adapter samples.

   The error in question is:.

   Copy

   
   00000136 MCWrapper EJ2CA0079E: Method cleanup has detected an internal
   illegal state and is throwing an IllegalStateException. The exception is:
   java.lang.IllegalStateException: cleanup: illegal state exception. State =
   STATE_INACTIVE MCW = 8210821.
   
   

   WAS Uses Different JCA Connection Factory for JMS Async Request Reply Scenario

   1. Bug: 14754024
   2. Added: 11-Oct-2012
   3. Platform: All

   In the JMS asynch request reply scenario if the same jca connection factory is used for any other JMS receive operation, as well as for jms asych req-reply operation (in jca file), then the below error is encountered in the WebSphere server environment.This is only applicable when tje JMS adapter is deployed on the WebSphere Server. See the following trace.

   Copy

   
   Caused by: com.ibm.websphere.sib.exception.SIIncorrectCallException: 
   CWSIP0777E: The transaction used for receive on the destination: Destination 
   (1712612884) demoQueueCorr2 : E4143EA44C604CC7E255F98C has already been 
   completed.
   at 
   com.ibm.ws.sib.processor.
   impl.JSLocalConsumerPoint.receive(JSLocalConsumerPoint.java:1590)
    
   at 
   com.ibm.ws.sib.processor.impl.ConsumerSessionImpl.receiveWithWait
   (ConsumerSessionImpl.java:448)
   at 
   com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.
   receiveInboundMessage(JmsMsgConsumerImpl.java:1114)
   
      
   

   Workaround: Use different JCA connection factory for JMS operations when using the WebSphere server. Please refer to bug14730484 for more information.

   Retry Interval, Maxinterval, and Backoff Parameters Will Not Take Effect for UMS Adapter

   1. Bug: 14735717
   2. Added: 12-Oct-2012
   3. Platform: All

   Retry Interval,MaxInterval &Backoff parameters don’t take effect for UMSAdapter Inbound

   The inbound retry interval, max interval and back off parameters cannot be controlled by UMS Adapter as it is not a local retry.So they may not take effect even if we specify some values. The UMS Adapter sends exception back to the UMS and UMS will redeliver the message again. As we never know when and how UMS redelivers the message once we do not acknowledge the message in poller mode.

   Application Is Already a Subscriber For Queue

   1. Bug: 12903224
   2. Added: 15-September-2011
   3. Platform: All

   When using the Oracle JMS adapter with an AQJMS provider and when the configuration involves multiple dequeuer threads in a multi-server cluster, the Oracle JMS Adapter logs the following exception.

   Copy

   
   
   Caused by: oracle.jms.AQjmsException: ORA-24034: application <durable-subscriber-name> is already
   a subscriber for queue <queue-name>
   
   ORA-06512: at "SYS.DBMS_AQADM_SYS", line 6270
   ORA-06512: at line 1
   ORA-06512: at "SYS.DBMS_AQJMS", line 129
   ORA-06512: at line 1
   
   at
   oracle.jms.AQjmsSession.addDurableSubscriber(AQjmsSession.java:3993)
   at
   oracle.jms.AQjmsSession.createSubInCompliantMode(AQjmsSession.java:2961)
   at
   oracle.jms.AQjmsSession.createDurableSubscriber(AQjmsSession.java:2624)
   at
   oracle.jms.AQjmsSession.createDurableSubscriber(AQjmsSession.java:2559)
   at
   oracle.jms.AQjmsSession.createDurableSubscriber(AQjmsSession.java:2404)
   at 
   

   Workaround: The exception can be ignored, as on subsequent retry the subscription is created successfully.

   Application <subscriber-name> is Already a Subscriber For Queue

   1. Bug: 12375483
   2. Added: 26-October-2011
   3. Platform: All

   The Oracle AQ adapter has been changed. It now creates a new subscriber as specifiedby the Consumer property when you are modeling an adapter service. Previously, the subscriber was not created by the adapter but it was expected that the subscriber is created before the adapter service was executed. Due to the change, if the subscriber for the Oracle AQ queue already exists, you see the following warning in the log files. Oracle Application Adapter scenarios that rely on Oracle AQ adapter for interaction with EBS queues will be impacted by this as well.

   <Subscriber <subscriber-name> already exists in the database. If the existing subscriber does not represent the correct subscriber, please undeploy the business process, remove the subscriber, and redeploy.>

   ORA-24034: application <subscriber-name> is already a subscriber for queue <queue-name>

   ORA-06512: at "SYS.DBMS_AQADM_SYS", line 5682

   ORA-06512: at "SYS.DBMS_AQADM", line 314

   ORA-06512: at line 1....

   Workaround: As the warning states, if the subscriber is the correct one, no action is required.

   Updating Required JAR List When Accessing IBM MQ SERVER 7.0 via SOA JMS Adapter

   1. Bug: 12349381
   2. Added: 20-April-2011
   3. Platform: All

   You must use the following required jar list when you use JMSadapter with MQ version 7.x (See the "Configuring Oracle JMS Adapter with IBM WebSphere MQ JMS" section in the Oracle Adapters User's Guide for more information.)

   Non-XA Data Sources

   Copy

   
   
   /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mq.jar
   /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mq.jmqi.jar
   /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mqjms.jar
   /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/dhbcore.jar
    
   

   XA Data Sources

   Copy

   
   
   
   /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mq.jar 
   /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mq.jmqi.jar 
   <YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mqjms.jar 
   /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/dhbcore.jar 
   /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mqetclient.jar 
   
   

   Managed Connection Factory Name Has to Be Modified in Case of Migrated AQ Adapter Composites

   1. Bug: 12369977
   2. Added: 20-April-2011
   3. Platform: All

   If you migrated AQ Adapter projects from Release 10.1.3.x to Release 11g, you need to manually update the managed connection factory from

   Copy

   
   <non-managed-connection
   managedConnectionFactoryClassName="
   oracle.tip.adapter.aq.AQManagedConnectionFactory">

   to

   Copy

   
   <non-managed-connection
   managedConnectionFactoryClassName="
   oracle.tip.adapter.aq.v2.jca.AQManagedConnectionFactory">

   so you can use AQadapter in non-managed mode . Note that non-managed mode is not recommended and not supported in a production environment.To run the adapter in managed mode, you need to configure the connection factory JNDI in the WebLogic Server console.

   AQJMS Dequeue Failed Error When Redeployed By Adding Durable Subscription

   1. Bug: 10434614
   2. Added: 28-April-2011
   3. Platform: All

   When an AQJMS Topic inbound process that is without a durable subscription is already deployed to the server, and is redeployed, adding a durable subscription to the Inbound Topic, the following error occurs when the message is dequeued. (Note this is fixed when you use Oracle Database 11.2.0.2.0 or any later version of the Oracle Database.)

   Copy

   
   
   Caused by: oracle.jms.AQjmsException: JMS-120: Dequeue failed 
   at oracle.jms.AQjmsError.throwEx(AQjmsError.java:315) 
   at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1620) 
   at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:1035) 
   at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:960) 
   at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:938) 
   at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:790) 
    

   Date is Always Set To One Month Higher Than What is Set For the Message

   1. Bug: 13450180
   2. Added: 01-December-2011
   3. Platform: All

   Refer to Bug-13435861.

   The date that is set through MQMD header is based on Gregorian Calendar. So, it is always set one month higher than that specified in the header.

   For example: If I set, jca.mq.MQMD.PutDateTime to "12:24:2011" - the actual date that is set for the message is: January 24th, 2012. Similarly, if I set jca.mq.MQMD.PutDateTime to "10:24:2011" - the actual date that is set for the message is: November 24th, 2011.

   Limitations of Dynamic Queue While Using MQ Adapter

   1. Bug: 13464470
   2. Added: 05-December-2011
   3. Platform: All

   MQ Adapter supports Dynamic Queue with these limitations:

   • Dynamic Queue is supported only for Inbound operations and not for Outbound
   • The property InboundThreadCount has to be set to 1 in the Inbound JCA file.

   Specifying Retry Interval, Max Interval and Backoff parameters for Inbound Poller mode with XA case; might not give results as expected.

   1. Bug:14735717
   2. Added: 7-March-2013
   3. Platform: All

   While using Retry Interval, Max Interval and Backoff parameters with UMS Adapter Inbound Poller mode with XA,it is likely that retries might not happen with given exact interval and one might not get results as expected. This is because there are other associated time factors as the the retry does not happen locally but the message is sent back to the UMS server and will be fetched again and processed.

   NLS:JCA UMS ADAPTER MAIL GARBLE ON NON UTF SERVER ENCODING

   1. Bug: 16464175
   2. Added: 15-March 2013
   3. Platform: All

   UMS Adapter composes outbound email using SOA server encoding. If the payload contains some characters not supported by server encoding, it can cause data corruption.

   Workaround: Set jca.ums.msg.content-type = 'text/plain; character=utf8'.This is a normalized message property set on the outbound invoke for the UMS Adapter for BPEL. If in a Mediator, use "Assign values" to specify the value.

   UMS Adapter has issues parsing non-ascii characters in inbound email if the SOA server is running in non-UTF8 encoding.

   Workaround: Start SOA server in UTF-8 encoding.

   Configuring 11g to Access Queues/Topics Present in 10.1.3.X OC4J

   1. Bug: 9544466
   2. Added: 17-April-2012
   3. Platform: All

   The following steps provide guidance in accessing queues/topics present in 10.1.3x Oracle Containers for J2EE (OC4J)

   Workaround:

   1. 1. Copy the jar files under the /domains/<DOMAIN_NAME>/lib folder of the WebLogicServer:
      • $J2EE_HOME/lib/jms.jar
      • $J2EE_HOME/lib/jta.jar
      • $J2EE_HOME/oc4jclient.jar
      • $AS_HOME/opmn/lib/optic.jar
   2.  
   3. 2. Add the Connector factory in the weblogic-ra.xml file.
   Copy

   
   
   <connection-instance>
   <jndi-name>eis/oc4jjms/Queue</jndi-name>
   <connection-properties>
   <properties>
   <property>
   <name>ConnectionFactoryLocation</name>
   <value>jms/XAQueueConnectionFactory</value>
   </property> 
   <property>
   <name>FactoryProperties</name>
   <value>java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory;
   java.naming.provider.url=<PROVIDER_URL>;
   java.naming.security.principal=<USER>java.naming.security.credentials=<PASSWORD></value> 
   </property> 
   <property>
   <name>AcknowledgeMode</name>
   <value>AUTO_ACKNOWLEDGE</value>
   </property>
   <property>
   <name>IsTopic</name>
   <value>false</value>
   </property> 
   <property>
   <name>IsTransacted</name>
   <value>false</value>
   </property>
   <property>
   <name>Username</name>
   <value><USER></value>;
   </property> 
   <property>
   <name>Password</name>
   <value><PASSWORD></value> 
   </property> 
   </properties>
   </connection-properties> 
   </connection-instance>
   
           

   where is opmn://localhost:6003 or ormi://localhost:12401 to use with a specific node, or opmn:ormi://localhost:6003:oc4j_soa to use

   with the oc4j_soa instance

   Oracle E-Business Suite Adapter

   Database Adapter Stored Procedure Project Migrated from 11g to 12c Creates Duplicate XSD If Wizard Rerun

   1. Bug: 18555120
   2. Updated: 28-April-2014
   3. Platform: All

   While creating a new project, if the underlying Database Adapter project contains a stored procedure and is migrated from 11g to 12c release, when you rerun the stored procedure through the Configuration Wizard, a new xsd under the Schema folder is created for 12c release.

   Rerunning causes two similar xsds only when the Database Adapter project contains a stored procedure. You need to manually delete the old xsd file created earlier before the migration and update the read.wsdl to reference the new xsd in the Schema folder.

   Please also note that if database tables are used, the new schema is correctly written to the old schema location.

   Performance Slow While Importing a Flexfield Mapping for a PL/SQL API

   1. Bug: 18956027
   2. Updated: 11-June-2014
   3. Platform: All

   During the partner link creation for a PL/SQL API that has flexfield data configured, if you decide to construct the flexfield mapping by using an existing one through the Import feature, then it would take 3-5 minutes to get the mapping file (*_mapping.xml) imported to the Oracle E-Business Suite Module Browser.

   Should Not Retry for a Binding Fault

   1. Bug: 18955946
   2. Updated: 11-June-2014
   3. Platform: All

   When an Oracle E-Business Suite Adapter application configured with Open Interface Table is invoked with input xml that throws IntegrityConstraint/UniqueConstraint Violation, it results in one kind of Binding Fault. In this situation, we should be able to see the description as Binding Fault under the Fault Name tab in the Flow Trace page of the Oracle Enterprise Manager Fusion Middleware Control Console, and exception message must clearly show if it is due to the JCA Binding (like invalid connection pool) or unique constraint error.

   In the case of binding faults, there should not happen any retry because retry will not resolve the issue.

   Application Adapters for WebLogic Server

   Missing Libraries in setDomainEnv Causes Application Adapters AE to Fail

   1. Bug: 13929048
   2. Added: 08-June-2012
   3. Platform: All

   This problem affects every release the adapters are certified for: 11.1.1.4.0, 11.1.1.5.0, and 11.1.1.6.0.

   The following two libraries are missing when starting the starting the design tool for the Application Adapters WLS (Application Explorer) after installation:

   1. $MWH/Oracle_SOA1/soa/modules/oracle.soa.adapter_11.1.1/jca-binding-api.jar
   2. $MWH/Oracle_SOA1/soa/modules/oracle.soa.adapter_11.1.1/adapter_xbeans.jar

   In the Oracle Fusion Middleware Application Adapters Installation Guide for Oracle WebLogic Server, section 2.3.1 Starting Application Explorer, the guide states that users must run the setDomainEnv.sh to set the environment accordingly. The two libraries need to be added to the setDomainEnv scripts to avoid class loading exceptions.

   The following exceptions may occur when using the Application Explorer to generate EIS adapter artifacts:

   Copy

   
   20120405-11:51:04 INFO com.ibi.bse.gui.BseFrame:read manifest for iwae.jar 
   20120405-12:12:30 ERROR
   com.ibi.bse.ConfigWorker:java.lang.NoClassDefFoundError: 
   oracle/tip/adapter/api/exception/PCResourceException 
   at
   com.ibi.afjca.cci.IWAFConnection.createInteraction(IWAFConnection.java:81)
   at 
   com.iwaysoftware.iwae.common.JCATransport.initJCA(JCATransport.java:100)
   at
   com.iwaysoftware.iwae.common.JCATransport.(JCATransport.java:87)
   at
   com.iwaysoftware.iwae.common.AdapterClient.(AdapterClient.java:85)
   at com.ibi.bse.ConfigWorker.run(ConfigWorker.java:41) 
   at java.lang.Thread.run(Thread.java:662) 
   Caused by: java.lang.ClassNotFoundException: 
   oracle.tip.adapter.api.exception.PCResourceException 
   at java.net.URLClassLoader$1.run(URLClassLoader.java:202) 
   at java.security.AccessController.doPrivileged(Native Method) 
   at java.net.URLClassLoader.findClass(URLClassLoader.java:190) 
   at java.lang.ClassLoader.loadClass(ClassLoader.java:306) 
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:247) 
   ... 6 more 
   
    
   

   Exception occurred during event dispatching:

   Copy

   
   java.lang.NoClassDefFoundError: 
   oracle/integration/platform/blocks/adapter/fw/metadata/AdapterConfigDocument$Factory
   at
   com.iwaysoftware.af.container.tools.wsdl.oracle.InboundWSDLGenerator.get11g_jca
   at
   com.iwaysoftware.af.container.tools.wsdl.oracle.IWayWSILBrowser.writeFiles
   (IWayWSILBrowser.java:137) 
   at
   com.iwaysoftware.af.container.tools.wsdl.oracle.IWayWSILBrowser.generateIWayWSDL
   (IWayWSILBrowser.java:132) 
   at
   com.iwaysoftware.af.container.OracleAEManager.generateWSDL
   (OracleAEManager.java:83)
   at
   com.iwaysoftware.af.container.OracleAEManager.generateWSDL
   (OracleAEManager.java:64)
   at
   com.iwaysoftware.af.container.ae.AEComponentMessage.buildEXPORTWSDL
   (AEComponentMessage.java:185) 
   at
   com.iwaysoftware.af.container.ae.AEComponentMessage.build
   (AEComponentMessage.java:89)
   at
   com.iwaysoftware.af.container.ae.AEComponentMessage.(AEComponentMessage.java:61)
   at
   com.iwaysoftware.af.container.AEManager.dispatch(AEManager.java:134) 
   at
   com.iwaysoftware.af.container.IWAFContainer.dispatchAERequest
   (IWAFContainer.java:876)
   at
   com.ibi.afjca.cci.IWAFInteraction.execIWAE(IWAFInteraction.java:286) 
   at
   com.ibi.afjca.cci.IWAFInteraction.exec(IWAFInteraction.java:182) 
   at
   com.ibi.afjca.cci.IWAFInteraction.execute(IWAFInteraction.java:107) 
   at
   com.iwaysoftware.iwae.common.JCATransport.execute(JCATransport.java:166)
   at
   com.iwaysoftware.iwae.common.AdapterClient.generateWSDL(AdapterClient.java:437)
   at
   com.ibi.bse.gui.ExportWSDLDialog.saveWSDL(ExportWSDLDialog.java:590)
   at
   com.ibi.bse.gui.ExportWSDLDialog.okButtonActionPerformed
   (ExportWSDLDialog.java:476)
   at
   com.ibi.bse.gui.ExportWSDLDialog.access$000(ExportWSDLDialog.java:36)
   at
   com.ibi.bse.gui.ExportWSDLDialog$2.actionPerformed(ExportWSDLDialog.java:417)
   at
   javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
   at
   javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
   at
   javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
   at
   javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
   at
   javax.swing.plaf.basic.BasicButtonListener.mouseReleased
   (BasicButtonListener.java:236)
   at java.awt.Component.processMouseEvent(Component.java:6267) 
   at javax.swing.JComponent.processMouseEvent(JComponent.java:3267) 
   at java.awt.Component.processEvent(Component.java:6032) 
   at java.awt.Container.processEvent(Container.java:2041) 
   at java.awt.Component.dispatchEventImpl(Component.java:4630) 
   at java.awt.Container.dispatchEventImpl(Container.java:2099) 
   at java.awt.Component.dispatchEvent(Component.java:4460) 
   at
   java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
   at
   java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
   at
   java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168) 
   at java.awt.Container.dispatchEventImpl(Container.java:2085) 
   at java.awt.Window.dispatchEventImpl(Window.java:2478) 
   at java.awt.Component.dispatchEvent(Component.java:4460) 
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:599) 
   at
   java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
   at
   java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
   at
   java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:178)
   at java.awt.Dialog$1.run(Dialog.java:1046) 
   at java.awt.Dialog$3.run(Dialog.java:1098) 
   at java.security.AccessController.doPrivileged(Native Method) 
   at java.awt.Dialog.show(Dialog.java:1096) 
   at
   com.ibi.bse.ComponentNodeData.actionPerformed(ComponentNodeData.java:406)
   at
   javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
   at
   javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
   at
   javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
   at
   javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
   at javax.swing.AbstractButton.doClick(AbstractButton.java:357) 
   at
   javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1223)
   at
   javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased
   (BasicMenuItemUI.java:1264)
   at java.awt.Component.processMouseEvent(Component.java:6267) 
   at javax.swing.JComponent.processMouseEvent(JComponent.java:3267) 
   at java.awt.Component.processEvent(Component.java:6032) 
   at java.awt.Container.processEvent(Container.java:2041) 
   at java.awt.Component.dispatchEventImpl(Component.java:4630) 
   at java.awt.Container.dispatchEventImpl(Container.java:2099) 
   at java.awt.Component.dispatchEvent(Component.java:4460)
   at
   java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
   at
   java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
   at
   java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168) 
   at java.awt.Container.dispatchEventImpl(Container.java:2085) 
   at java.awt.Window.dispatchEventImpl(Window.java:2478) 
   at java.awt.Component.dispatchEvent(Component.java:4460) 
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:599) 
   at
   java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
   at
   java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
   at
   java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
   at
   java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
   at
   java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
   at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) 
   Caused by: java.lang.ClassNotFoundException: 
   oracle.integration.platform.blocks.adapter.fw.metadata.
   AdapterConfigDocument$Factory
   at java.net.URLClassLoader$1.run(URLClassLoader.java:202) 
   at java.security.AccessController.doPrivileged(Native Method) 
   at java.net.URLClassLoader.findClass(URLClassLoader.java:190) 
   at java.lang.ClassLoader.loadClass(ClassLoader.java:307) 
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:248) 
   ... 73 more 
        

   The exceptions are related to missing libraries in the classpath when starting the Application Explorer.

   The following libraries must be added to the classpath via the setDomainEnv script prior starting the Application Explorer:

   • jca-binding-api.jar
   • adapter_xbeans.jar

   Workaround: The installation guide will be updated in a future release.

   Application Server Legacy Adapters

   No issue has been discovered at the time of this release. As additional issues and workarounds are discovered after the release, they will be listed here.

   BPEL Process Manager

   There Are Currently No Known Issues for Oracle BPEL Process Manager 12.1.3

   Business Activity Monitoring

   Colors in Pie charts are not consistent

   1. Bug: 22752300
   2. Updated: 16-March-2016
   3. Platform: All

   A pie chart has been configured using ColorThemes to show the following colors according to the chart values: Red as Failed, Green as delivered, Orange as in-flight. But the colors are not consistent and sometimes they are swapped; for example showing green for failed and red for delivered.

   Workaround:This problem occurs because the color assignment is based on group indexing. If a group is missing from the query result, its color from the color theme array gets reassigned to the next group returned by the query. Re-design the business query or data object so that each group is present in the query result even if the returned data set has a count of zero.

   Resource Catalog/Browse dialog in Dash editor doesn't use Business View display names

   1. Bug: 21170770
   2. Updated: 24-February-2016
   3. Platform: All

   The Resource Catalog (Browse) dialog in the Dashboard editor displays the internal Business View names, not their display names.

   Workaround: None.

   1. Bug: 22759104
   2. Updated: 19-February-2016
   3. Platform: All
   1. Bug: 22742881
   2. Updated: 18-February-2016
   3. Platform: All
   1. Bug: 20820366
   2. Updated: 20-April-2015
   3. Platform: All
   1. Bug: 20047535
   2. Updated: 05-January-2015
   3. Platform: All
   • Disable script debugging (Internet Explorer)- UNCHECKED
   • Disable script debugging (Other)- UNCHECKED
   • Display a notification about every script error - CHECKED
   1. Bug: 17181135
   2. Updated: 11-February-2014
   3. Platform: All
   1. Bug: 17369421
   2. Updated: 11-February-2014
   3. Platform: All
   1. Bug: 17433505
   2. Updated: 05-May-2014
   3. Platform: All
   1. Bug: 17622571
   2. Updated: 11-February-2014
   3. Platform: All
   1. Bug: 17750455
   2. Updated: 18-December-2013
   3. Platform: All
   1. Bug: 17758322
   2. Updated: 18-December-2013
   3. Platform: All
   1. Bug: 17774992
   2. Updated: 28-April-2014
   3. Platform: All
   1. Bug: 17837110
   2. Updated: 11-February-2014
   3. Platform: All
   1. Bug: 17856596
   2. Updated: 12-February-2014
   3. Platform: All
   1. Bug: 17880082
   2. Updated: 10-February-2014
   3. Platform: All
   1. Bug: 17929821
   2. Updated: 18-March-2014
   3. Platform: All
   1. Bug: 18088955
   2. Updated: 17 March-2014
   3. Platform: All
   1. Bug: 18177008
   2. Updated: 31-March-2014
   3. Platform: All
   1. Bug: 18192245
   2. Updated: 18-March-2014
   3. Platform: All
   1. Bug: 18297608
   2. Updated: 25-March-2014
   3. Platform: All
   1. Bug: 18315602
   2. Updated: 28-April-2014
   3. Platform: All
   1. Bug: 18324141
   2. Updated: 13-March-2014
   3. Platform: All
   1. Bug: 18353283
   2. Updated: 05-March-2014
   3. Platform: All
   1. Bug: 18374092
   2. Updated: 19-March-2014
   3. Platform: All
   1. Bug: 18379516
   2. Updated: 25-April-2014
   3. Platform: All
   1. Bug: 18396742
   2. Updated: 14-March-2014
   3. Platform: All
   1. Bug: 18397134
   2. Updated: 14-March-2014
   3. Platform: All
   1. Bug: 18401450
   2. Updated: 15-March-2014
   3. Platform: All
   1. Bug: 18403487
   2. Updated: 15-March-2014
   3. Platform: All
   1. Bug: 18403952
   2. Updated: 29-April-2014
   3. Platform: All
   1. Bug: 18404024
   2. Updated: 15-March-2014
   3. Platform: All
   1. Bug: 18416774
   2. Updated: 25-March-2014
   3. Platform: All
   1. Bug: 18425025
   2. Updated: 19-March-2014
   3. Platform: All
   1. Bug: 18431661
   2. Updated: 03-April-2014
   3. Platform: All
   1. Bug: 18440699
   2. Updated: 24-March-2014
   3. Platform: All
   1. Bug: 18483415
   2. Updated: 03-April-2014
   3. Platform: All
   1. Bug: 18483489
   2. Updated: 31-March-2014
   3. Platform: All
   1. Bug: 18532641
   2. Updated: 28-April-2014
   3. Platform: All
   1. Bug: 18552486
   2. Updated: 30-April-2014
   3. Platform: All
   1. Bug: 18631756
   2. Updated: 24-April-2014
   3. Platform: All
   1. Bug: 18726722
   2. Updated: 08-May-2014
   3. Platform: All
   1. Bug: 18744929
   2. Updated: 14-May-2014
   3. Platform: All
   1. Bug: 18770881
   2. Updated: 15-May-2014
   3. Platform: All
   1. 1. Install BAM 12c and ODI 12c.
   2. 2. Create ODI scenarios in the ODI environment.
   3. 3. Log in to Oracle Enterprise Manager Fusion Middleware Control and set the ODI-related BEAMServerConfig MBean properties. The following is a list of the property names and example values.
      • OdiAgentContext - oraclediagent
      • OdiAgentHost - localhost
      • OdiAgentPort - 4321
      • OdiMasterRepoDriver - oracle.jdbc.OracleDriver
      • OdiMasterRepoPassword - P@$sw0rd
      • OdiMasterRepoURL - jdbc:oracle:thin@localhost:1521:ord
      • OdiMasterRepoUser - DEV_ODI_REPO
      • OdiPassword - P@$sw0rd
      • OdiUser - SUPERVISOR
      • OdiWorkRepo - WORKREP
   1. 1. Select the "Run an ODI Service" action when creating the alert.
   2. 2. In the Configure ODI Action dialog, select the ODIAgentContext.
   3. 3. Select the ODI scenario and version.
   4. 4. Optionally enter variable values.
   5. 5. Optionally enter the session name.
   6. 6. Optionally enter a keyword.
   7. 7. Click OK.
   1. Bug: 18748724
   2. Updated: 19-May-2014
   3. Platform: All
   1. Bug: 18866444
   2. Updated: 29-May-2014
   3. Platform: All

   • BAMAdministrator - Members of this role can view all BPM data.

   • BPMContentViewer - Members of this role can view all BPM data.

   • ProcessName.AnalyticsViewer - Members of this role can view data for a specific BPM process.

   1. Bug: 18897246
   2. Updated: 11-June-2014
   3. Platform: All
   1. Bug: 18967581
   2. Updated: 13-June-2014
   3. Platform: All
   1. Bug: 19139280
   2. Updated: 30-July-2014
   3. Platform: All
   1. Bug: 19226602
   2. Updated: 30-July-2014
   3. Platform: All
   1. Bug: 19260645
   2. Updated: 21-July-2014
   3. Platform: All

   1. Copy the BAM 12c adapter file, bamjcaadapter.rar, from the $FMW_HOME/soa/bam/lib directory to the SOA 11g installation directory.

   2. Delete the OracleBamAdapter from the SOA 11g deployments in Oracle WebLogic Server 11g.

   3. Install bamjcaadapter.rar in WebLogic Server 11g.

   4. Change the JNDI references in the WebLogic Server 11g console to point to BAM 12c.

   5. Restart the SOA 11g managed server.

   6. Create a data object in BAM 12c similar to the one that was in BAM 11g.

   1. Bug: 18641123
   2. Added: 21-May-2014
   3. Platform: All
   1. Bug: 18744682
   2. Added: 22-May-2014
   3. Platform: All
   1. Bug: 18704365
   2. Added: 22-May-2014
   3. Platform: All
   1. Bug: 18703647
   2. Added: 22-May-2014
   3. Platform: All
   1. Bug: 18455701
   2. Added: 22-May-2014
   3. Platform: All
   1. 1. Uploaded document is not visible in the Process Tracking UI.
   2. 2. Uploaded document cannot be deleted in the Task UI.
   1. Bug: 18410212
   2. Added: 22-May-2014
   3. Platform: All
   1. 1. Verify that all the users in Case exist in UCM.
   2. 2. Select the Use Document Package checkbox.
   3. 3. Add Document Folder metadata properties.
   4. 4. Verify that the value of Security Group field is the same as the one configured for UCM root folder. Mark the display field as Read-only.
   5. 5. Verify that the value of Document Folder field is the same as the one configured for Case. Mark the display field as Read-only.
   1. Bug: 18410224
   2. Added: 22-May-2014
   3. Platform: All
   1. 1. Duplicate documents cannot be uploaded from the Process Tracking UI.
   2. 2. An exception is thrown in the Task UI and the form gets corrupted if a non-existing user in UCM tries to access task form.
   3. 3. If a human task is added as a part of plain BPMN process (which is not promoted as a case activity), an exception is thrown in Case UI when you delete a document from Task UI.
   4. 4. If you delete a document from Task UI, it doe snot get deleted from UCM.
   5. 5. Delete privilege is not honored in Task UI.
   6. 6. CMISRUNTIMEEXCEPTION in Task UI while deleting an uploaded document from the process.
   7. 7. You cannot checkout or see more information about the document uploaded and saved from the Task UI.
   8. 8. CasemanagementLink is missing when a document is uploaded from the Task UI.
   9. 9. Documents do not get deleted from the Task UI.
   10. 10. When a user with appropriate permissions [Read,Write] uploads a document in the Task UI, it is not visible.
   11. 11. Task UI allows upload of document only when Security Group filed is hard-coded and marked as Read-only.
   12. 12. When a value is entered in the field Upload file to Folder, NullPointerException is logged. This behavior is observed only for users who do not have Admin rights.
   13. 13. Users with only Read permission can upload documents to the Task UI.
   14. 14. Non-existing users can download documents from Task UI.
   15. 15. In Task UI, when folder path is not specified, root/instance path is not overridden.
   16. 16. NullPointerException is thrown when a document is checked-out from Task UI and checked-in from the Case UI.
   17. 17. Comments added in Process UI are not visible in Case UI.
   18. 18. Documents not visible in Task UI for human task created without DOCUMENTS PACKAGE.
   19. 19. In Studio, when you type a character in the Name field, the first character from name gets appended to Display Name.
   1. Bug: 18220634
   2. Added: 22-May-2014
   3. Platform: All
   1. Bug: 18149522
   2. Added: 22-May-2014
   3. Platform: All
   1. Bug: 18141856
   2. Added: 22-May-2014
   3. Platform: All
4. <param-value>never</param-value>

   Workaround: There is no workaround.

   Date format not reflected according to the browser in Activity Case Form UI

   1. Bug: 18107471
   2. Added: 22-May-2014
   3. Platform: All

   In Case Management, the date format does not consider the browser/LDAP locale. It considers the Sever locale.

   This is a known issue.

   Workaround: There is no workaround.

   Case listing shows previously filtered data

   1. Bug: 18085901
   2. Added: 22-May-2014
   3. Platform: All

   When you load the Workspace after upgrading from 11g to 12c, refresh the data to see updated Case List.

   Microsoft® Office Integration: Microsoft® Excel Workbook fails to retrieve tasks with error

   1. Bug: 18037932
   2. Added: 22-May-2014
   3. Platform: All

   After installing Oracle Desktop ADF Integration, when you open a Microsoft® Excel Workbook (with .xlsx extension) in Microsoft® Excel 2007 an error occurs and an exception is thrown.

   This is a known issue.

   Workaround: There is no workaround.

   Task form from previous release fails to compile due to wrong XMNLS

   1. Bug: 17831337
   2. Added: 22-May-2014
   3. Platform: All

   Some older task forms do not compile in 12c JDeveloper. The following error occurs:

   Error: weblogic.appc failed to compile the application. Recompile with the -verbose option for more details about the issue.

   Workaround: Update the weblogic.xml file as follows:

   Replace

   <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app">

   with

   <weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app">

   NullPointerException is thrown when a process name starts with lowercase

   1. Bug: 16518944
   2. Added: 22-May-2014
   3. Platform: All

   If a process name starts with lowercase, a NullPointerException is thrown in Process Tracking page. This happens when the process has an initiator task.

   This is a known issue.

   Workaround: There is no workaround.

   Duplicate pages after migration

   1. Bug: 12879747
   2. Added: 22-May-2014
   3. Platform: All

   After migration, if the workspace has users with duplicate access privileges with the same page associated, that page will be shown as duplicate.

   This is a known issue.

   Workaround: There is no workaround.

   Application crashes publishing process with invalid BR

   1. Bug: 18810627
   2. Added: 23-May-2014
   3. Platform: All

   Application crashes with an Error 500 page during the publishing process when a Business Rule (BR) is created with an input or output argument with an unselected Fact Type.

   Workaround: Clear the browser cache and access the Project page again. Create another BR with a different name and be sure to select the fact type of all arguments in the BR decision functions.

   BPM cannot import Microsoft® Visio 2013 models

   1. Bug: 17670719
   2. Added: 23-May-2014
   3. Platform: All

   Models from Microsoft® Visio 2013 cannot be imported into BMP Studio or Composer.

   Workaround: If you have a Microsoft® Visio 2013 model to be imported, open the model in Microsoft® Visio 2010 and save it with the extension .vdx before importing.

   Replay Scope Support

   1. Bug: 17331576
   2. Added: 23-May-2014
   3. Platform: All

   Replay scope is not applicable to BPM because it does not support the concept of scope.

   Workaround: There is no workaround.

   DIFF MERGE tool honors Composer changes over Studio changes

   1. Bug: 18454088
   2. Added: 23-May-2014
   3. Platform: All

   If the model is locked by Composer, any change from Studio will not be honored.

   Workaround: There is no workaround.

   Users with migrated projects (MDS-PAM) do not belong to BPMPAMDEFAULTGROUP

   1. Bug: 18600656
   2. Added: 23-May-2014
   3. Platform: All

   Users with migrated projects (MDS-PAM) do not belong to BpmPamDefaultGroup.

   Workaround: Follow these steps:

   1. 1. Log in to the WebLogic console.
   2. 2. On Domain Structure, click Security Realm -> MyRealm -> Users and Group -> Groups. The BpmPamDefaultGroup is created.
   3. 3. Search for users with permission on the migrated projects and select them.
   4. 4. Click Groups flap of the users.
   5. 5. Add BpmPamDefaultGroup to the user and click Save.
   6. 6. Repeat this step for each user with permission in MDS projects.

   Either all or none of the Human Tasks in process should have the UCM Repository configured

   1. Bug: 18340674
   2. Added: 23-May-2014
   3. Platform: All

   If Human Tasks of a BPM Process are configured to use UCM Repository to store attachments, then all the Human Tasks of that process must use UCM. Attachments will not work if the process has both UCM and non-UCM based tasks.

   This is a known issue.

   Workaround: There is no workaround.

   Process instance not visible after dynamic OU association

   1. Bug: 18316584
   2. Added: 23-May-2014
   3. Platform: All

   When you dynamically change the process instance organization association to a new Org Unit (OU), the users who are part of new Org Unit (OU) cannot lookup process definitions. Without process definitions, workspace does not show the process instances in the process instance table.

   This is a known issue.

   Workaround: There is no workaround.

   iCal unable to import for BYMONTH and BYMONTHDAY rule

   1. Bug: 18232842
   2. Added: 23-May-2014
   3. Platform: All

   The iCalendar import does not work for BYMONTH and BYMONTHDAY RRULE. The import works fine with RRULE:FREQ=YEARLY, but does not work for RRULE:FREQ=YEARLY;BYMONTHDAY=1;BYMONTH=5.

   This is a known issue.

   Workaround: There is no workaround.

   Manual refresh of Process Instance Table needed after grab or migrate

   1. Bug: 17906633
   2. Added: 23-May-2014
   3. Platform: All

   After Grab or Migrate, the process instance state may not update automatically.

   Workaround: Refresh the process instance table to see the updated instances.

   Role description cannot be updated

   1. Bug: 17906613
   2. Added: 23-May-2014
   3. Platform: All

   Users cannot edit the role descriptions for the existing roles.

   This is a known issue.

   Workaround: There is no workaround.

   Consecutive iCal imports display result summary of previous imports

   1. Bug: 17906590
   2. Added: 23-May-2014
   3. Platform: All

   When you perform consecutive imports of iCalendar for holidays, result summary of the previous import is displayed. The import is successful.

   This is a known issue.

   Workaround: There is no workaround.

   Composer freezes after upgrading from 11g to 12c

   1. Bug: 18828130
   2. Added: 27-May-2014
   3. Platform: All

   Composer freezes after upgrading from 11g to 12c.

   Workaround: Close the Composer, clear the cache, and re-login to the Composer.

   When the next task is assigned to other user, the Milestone section does not refresh

   1. Bug: 18517453
   2. Added: 27-May-2014
   3. Platform: All

   If 2 consecutive tasks are assigned to the same user, the Activity Guide (AG) page refreshes properly. But when 2 consecutive tasks are assigned to 2 different users, the AG page does not refresh.

   This is a known issue.

   Workaround: Click the Refresh button available in the Activity Guide panel to refresh the page explicitly.

   New projects exported from Studio generate a wrong project name

   1. Bug: 18826761
   2. Added: 27-May-2014
   3. Platform: All

   When you export projects created from scratch from Studio, an incorrect name is generated.

   This happens only for projects that have been created from scratch in Studio. It does not happens for projects created from scratch in composer. A project created and exported from Composer and the imported in Studio works fine.

   How to detect it:

   Studio

   When the project is imported in studio the project name proposed by the wizard is 'ProjectInfo' or 'SOA'.

   Composer

   If you import these exported projects in Composer with this problem, the name in Composer home were all the projects are shown will look fine, but if you open the project the name at Project home is shown as: 'SOA' Do not continue working with it.

   Workaround: Follow these steps:

   1. 1. Import the exported project file into Studio.
   2. 2. Select Import BPM Project. Browse and select the project file.
   3. 3. After selecting the file to import, copy its name to Clipboard (without the file extension and its previous path).
   4. 4. Click Next. The wizard proposes the project name as projectInfo. Replace the proposed name with the name copied to the clipboard.
   5. 5. Click Finish. Now, export the project from Studio.

   COHERENECE Exception while shutting down SOA Server in 12c

   1. Bug: 18822651
   2. Added: 27-May-2014
   3. Platform: All

   Coherence exception is thrown while shutting down SOA Server. This exception is thrown only when domain is configured with BPM. This exception is not seen in SOA alone domains.

   This is a known issue.

   Workaround: There is no workaround.

   Failed to create space from BPM composer and dialog popup to prompt "BPM-0:An I/O error occurs trying to execute the operation"

   1. Bug: 18818838
   2. Added: 27-May-2014
   3. Platform: SOLARIS

      Failed to create space from BPM composer and dialog popup to prompt BPM-0:An I/O error occurs trying to execute the operation.

      This is a known issue.

      Workaround: Set the environment variable svnkit.useJNA to false before starting the WebLogic JVM.

      Keyboard navigation fails in Composer

      1. Bug: 18284871
      2. Added: 27-May-2014
      3. Platform: All

      You cannot navigate from on element to other element in BP Composer using the Tab key.

      Workaround: Use the mouse to select the Control or the Input field.

      Issues in Workspace Administration: Task Configuration

      1. Bug: 18284915
      2. Added: 30-May-2014
      3. Platform: All

      Install the OGHAG Helper Toolbar from. Run the OGHAG toolbar on each of the Worklist app page. This tool reports workspace administration issues for Color (Color Contrast), Form (Missing or Empty Label), and Table (No Summary Defined for Data Table).

      This is a known issue.

      Workaround: There is no workaround.

      Issues in Workspace Administration: Public/Protected Flexfield

      1. Bug: 18284903
      2. Added: 30-May-2014
      3. Platform: All

      Install the OGHAG Helper Toolbar from. Run the OGHAG toolbar on each of the Worklist app page. This tool reports workspace administration issues for Color (Color Contrast), Form (Missing or Empty Label and LABEL defined but it either contains no text or is hidden using an incorrect technique), Image (No ALT Text specified WCAG2.1.1.1), and Link (Link with href ...... is not found WCAG2.2.4.4).

      This is a known issue.

      Workaround: There is no workaround.

      Issues in Workspace Administration: Business Parameters Page

      1. Bug: 18284889
      2. Added: 30-May-2014
      3. Platform: All

      Install the OGHAG Helper Toolbar from. Run the OGHAG toolbar on each of the Worklist app page. This tool reports workspace administration issues for Color (Color Contrast) and Table (Table headers are not read; and No row header found WCAG2.1.3.1).

      This is a known issue.

      Workaround: There is no workaround.

      Issues in Workspace Administration: Evidence Search

      1. Bug: 18284883
      2. Added: 30-May-2014
      3. Platform: All

      Install the OGHAG Helper Toolbar from. Run the OGHAG toolbar on each of the Worklist app page. This tool reports workspace administration issues for Color (Color Contrast), Form (Multiple Labels found), Image (No ALT text specified WCAG2.1.1.1), and Link (Link with href ...... is not found WCAG2.2.4.4).

      This is a known issue.

      Workaround: There is no workaround.

      Issues in Workspace Administration: Approval Group

      1. Bug: 18284911
      2. Added: 30-May-2014
      3. Platform: All

      Install the OGHAG Helper Toolbar from. Run the OGHAG toolbar on each of the Worklist app page. This tool reports workspace administration issues for Color (Color Contrast), Image (A Link must have ALT text specified WCAG2.1.1.1), and Link (Link with href ...... is not found WCAG2.2.4.4).

      This is a known issue.

      Workaround: There is no workaround.

      BI bindings are gone when deploying the BPM project

      1. Bug: 18899016
      2. Added: 05-Jun-2014
      3. Platform: All

      In 12c 12.1.3, BI bindings are gone when deploying the BPM project in JDev. This is a known issue.

      Workaround: Do not create the BIs immediately after you create the project. Close and re-open the project and then create the BI bindings.

      OPSS Security principal not found after BPM product upgrade

      1. Bug: 18747172
      2. Added: 06-Jun-2014
      3. Platform: All

      BPM Product security roles granted by the user are not found in OPSS resources after the BPM upgrade. This issue appears in production environments if users use a file based security store, but not if they use a DB based security store.

      Workaround: There is no workaround.

      BPM Composer fails to create space and an error is thrown

      1. Bug: 18815389
      2. Added: 06-Jun-2014
      3. Platform: SOLARIS

         The BPM Composer fails to create space. The following error is thrown:

         BPM-0:An I/O error occurs trying to execute the operation

         This issue is found only on SOLARIS platform.

         Workaround: Insert the value as JAVA_OPTIONS in commENV.sh under oracle_common/common/bin like as

         
         commEnv.sh line 301 of 652
              JAVA_OPTIONS="${JAVA_OPTIONS} ${VERIFY_NONE}
         -Djava.endorsed.dirs=${JRE_HOME}/lib/endorsed${PATHSEP}${MODULES_DIR}/endorsed-Dsvnkit.useJNA=false"

         Restart the Admin Server and Management Server. BPM composer creates the space without any exception.

         Data form generation fails if data based on startCaseInputMessage type

         1. Bug: 18191441
         2. Added: 16-Jun-2014
         3. Platform: All

         In a Case Composite, if the data is based on the startCaseInputMessage type, the form generation fails with NullPointerException. Whenever the data is based on a schema that already has <globalBindings> declared, this exception will occur.

         This is a known issue.

         Workaround: There is no workaround.

         In Impact Analysis report, duplicate Organization Units are shown

         1. Bug: 17049483
         2. Added: 16-Jun-2014
         3. Platform: All

         If 2 projects have an Organization Unit defined with the same name, the Impact Analysis report will display duplicate entries for the Organization Unit.

         This is the expected behavior as Organizations need not be unique across projects in a space.

         Workaround: There is no workaround.

         Repetitions is not available for Start Timers

         1. Bug: 17252599
         2. Added: 16-Jun-2014
         3. Platform: All

         Repetitions, which enable you to define the number of times an event runs, is not available for start timers.

         Workaround: There is no workaround.

         Using the Diff-Merge Feature in Business Process Composer

         1. Bug: 19024276
         2. Added: 20-Jun-2014
         3. Platform: All

         The Diff-Merge feature is only used for Microsoft® Excel spreadsheet import in BP Composer.

         Workaround: There is no workaround.

         Priority search works in inverted manner for '<' and '>' operators

         1. Bug: 18650918
         2. Added: 20-Jun-2014
         3. Platform: All

         In Process Workspace, when you run a query using the advanced search functionality to search/filter on Priority, the returned results are based on numerical sequence, not on priority, and are reversed from what you would expect. For example, when you specify Less than Highest, nothing is returned. When you specify Less than Lowest, items with priorities 2,3,4 and 5 are returned.

         This is a known issue.

         Workaround: There is no workaround. Adjust your queries accordingly.

         Case Management Does Not Support SQL and DB2 Databases

         1. Bug: 15920616
         2. Updated 18-June-2013
         3. Platform: All

         Currently the case management feature does not support the SQL and DB2 databases.

         Workaround There is no workaround.

         Mandatory Patches for Case Management

         1. Bug: 14808494
         2. Updated 18-June-2013
         3. Platform: All

         Install the following mandatory patches for the case management feature:

         • TopLink fix for Bug 14642695 - unable to use and reference alias inside subquery
         • TopLink fix for Bug 14306399 - stress bpm casem:get npe at casedecisionservicehandler.createdecisionpointfactli
         • Sun JDK fix for bug 14698557 stress bpm casem:get classcastexception at oracle.bpm.casemgmt.event. Multithreaded deserialization of Calendar leads to ClassCastException as at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7017458

         Workaround There is no workaround

         Non-ASCII Characters Cannot be Displayed In Web Form Print PDF File

         1. Bug: 16434235
         2. Added: 05-March-2013
         3. Platform: All

         When attempting to map a dropdown web form control to a string value in the human task data association, Business Process Composer generates an error when validating the BPM Project. The error reports that the data assocaition for the human task assigment is invalid.

         Workaround There is no workaround.

         Generate simulation from runtime data not supported in JDeveloper

         1. Bug: 16341922
         2. Updated 11-March-2013
         3. Platform: All

         Generating a simulation from runtime data is not supported in the JDeveloper environment.

         Workaround There is no workaround.

         Non-ASCII Characters Cannot be Displayed In Web Form Print PDF File

         1. Bug: 16287282
         2. Added: 05-February-2013
         3. Platform: All

         Web form controls do not support non-ASCII characters as label names. If a web form control contains non-ASCII character, they do not appear correctly in a generated PDF.

         Task Payload Name Should Contain Only ASCII Characters When Using Web Forms

         1. Bug: 16284318
         2. Added: 05-February-2013
         3. Platform: All

         If the task payload element contains non-ASCII characters, Business Process Composer will attempt to generate a web form which also contains non-ASCII characters. However, these are not supported. You must edit the name part of the fields and change as follows:

         • The field names should only contain letters (a-z, A-Z), numbers (0-9) and the underscore ("_") character.
         • The field names should not begin with a number.

         Must Access Business Process Composer Using SOA Server URL When Using Web Forms

         1. Bug: 16272773
         2. Added: 05-February-2013
         3. Platform: All

         Web Forms are not rendered inside Business Process Composer or Process Workspace unless those applications are accessed using fully qualified domain name. You must use the full URL of the SOA server.

         Web Forms Editor Does Not Support Non-ASCII Characters in Graphic Filenames

         1. Bug: 16220642
         2. Updated: 01-February-2013
         3. Platform: All

         When adding a graphic file to a web form, you must ensure that the filename contains only ASCII characters.

         Web Forms Functionality Not Supported on in Web Center Modeling Space

         1. Bug: 16102020
         2. Updated: 01-February-2013
         3. Platform: All

         Web forms functionality is not supported in Web Center's Modeling Space.

         No Support for Deleting Case Management Stakeholders

         1. Bug: 15951289
         2. Updated 31-December-2012
         3. Platform: All

         The case management API does not support support deleting stakeholders.

         Workaround There is no workaround.

         Setting the Case Management Permission Tag Using the setPermissionTag Function is Not Supported in Alfresco CMIS

         1. Bug: 15951238
         2. Updated 31-December-2012
         3. Platform: All

         Setting the case management permission tag using the function setPermissionTag() is not supported if the selected document content storage system is Alfresco CMIS.

         Workaround Set the permission tag when you upload the document using the uploadDocument() function.

         Transaction Error When Calling a Subprocess with a Receive Task

         1. Bug: 15940185
         2. Updated: 01-February-2013
         3. Platform: All

         When calling a subprocess from a receive task, the following exception may be thrown:

         java.sql.SQLException: ORA-12899: value too large for column "<schema>"."WORK_ITEM"."CUSTOM_ID"

         This error occurs because the size of the transaction is too large. If you encounter this error, increase the size of the custom_id column to 512.

         Web Forms Functionality Not Supported on Some Database Platforms

         1. Bug: 15920624
         2. Updated: 12-December-2012
         3. Platform: All

         Web Forms functionality is not supported on the following databases:

         • Microsoft SQL databases
         • IBM DB2 databases

         Web Forms Functionality Not Supported on Websphere Application Server (WAS)

         1. Bug: 14315026
         2. Updated: 12-December-2012
         3. Platform: Websphere Application Server

            Web Forms functionality is not supported on IBM Websphere Application Server (WAS).

            Case Management Functionality Not Supported on Websphere Application Server (WAS)

            1. Bug: 14315026
            2. Updated: 12-December-2012
            3. Platform: Websphere Application Server

               Case Management Functionality is not supported on Websphere Application Server (WAS).

               Max Limit on Redeployment in BPM Workspace

               1. Bug: 14840457
               2. Added: 2-November-2012
               3. Platform: All

               If the composite being redeployed has more than 100 existing BPM process instances, only 100 of them are migrated during redeployment and the component is left suspended. This limit is used to minimize the deployment time. To migrate the remaining instances, use Process Management APIs.".

               Expiration Date Field In Case Input Payload Is Not Supported

               1. Bug: 14768646
               2. Updated 29-October-2012
               3. Platform: All

               The expiration date field in the case input payload is not supported. The attribute exists for possible use in future versions.

               Workaround There is no workaround.

               Restrictions in Case Management Design and Runtime

               1. Bug: 14767324
               2. Updated 11-March-2013
               3. Platform: All

               The following restrictions apply to case management design and runtime:

               • There is no schema validation for the case data payload. You can assign the payload value any value, even invalid random Strings, regardless of the type defined in the case file.
               • The Human Task case activity does not support task outcome and execData in their output arguments.

               Workaround There is no workaround.

               Auto Update not available in BPM Workspace

               1. Bug: 14671243
               2. Added: 12-October-2012
               3. Platform: All

               If you have an assigned Initiator Task, when you invoke instances by clicking on the Process Link in the BPM Workspace Administration Tab, the Initiated Task count does not update automatically or after refreshing the webpage.

               Workaround: After clicking the Initiated Task link, the count is updated accordingly.

               Repeatable Option Not Support for Non-Conditional Automatic Case Activities

               1. Bug: 14745503
               2. Updated 29-October-2012
               3. Platform: All

               Non-conditional automatic case activities cannot be repeatable. The UI enables you to select this option but the BPM Runtime does not take it into account.

               Workaround There is no workaround.

               Audit Trail not Maintained for Previous Process Version

               1. Bug: 13466122
               2. Updated: 06-December-2011
               3. Platform: All

               Consider this scenario:

               • One version of a process is deployed.
               • An instance of that version is completed.
               • Later, a second version of that process is deployed.

               In this scenario, the first process instance shows the audit trail for the second version of the process rather than the first.

               No Support for Deleting Case Management Comments

               1. Bug: 14570446
               2. Updated 29-October-2012
               3. Platform: All

               The case management API does not support support deleting comments.

               Workaround There is no workaround.

               Logging in to BPM Workspace Gets Out of Memory Error

               1. Bug: 13387403
               2. Updated: 05-December-2011
               3. Platform: All

               At times, when you log into BPM Workspace and select a task for viewing the details, the taskform keeps loading endlessly. If you check the server console, then you note that it throws OutOfMemoryError.

               The workaround is:
               1. 1. Make sure that JRockit R28.2.0 is used for Oracle Weblogic Server.
               2. 2. In the file setSOADomainEn.sh, increase the Perm Gen space to -XX:MaxPermSize=768m.

               Characters in Comments Added to Flow-Altered or Migrated Instances Become "?" When Using Native Server Encoding

               1. Bug: 13369711
               2. Updated: 05-December-2011
               3. Platform: All

               If the server encoding is native encoding, and if you are doing either "Alter Flow" for a process instance or "Migrate" for a pending process instance, then strings added in comments that are not recognized by server encoding become question marks (?).

               Audit Is Available When Turned Off

               1. Bug: 13369711
               2. Updated: 05-December-2011
               3. Platform: All

               Audit records are shown for all activities even when auditing is turned off in EM at both the BPMN engine and common soa-infra levels. Auditing is also shown even when auditing is turned off, and there is no measurement artifact in the process, and measurement is enabled.

               Cannot Add An Attachment Having the Same Name as Another

               1. Bug: 13404430
               2. Updated: 05-December-2011
               3. Platform: All

               Adding an attachment having the same name as another without deleting the previous one can cause unexpected results. If an attachment with the same name that you need to attach exists, then:

               • Delete the attachment.
               • Save the task.
               • Add the new attachment.

               Manual Refresh Needed After Resuming a Pending Component

               1. Bug: 13425069
               2. Updated: 05-December-2011
               3. Platform: All

               After you resume a component from the pending components panel in the Process Tracking tab page, you must manual refresh BPM Workspace manually to show that the resumed component has been removed from the Pending Components panel. The Refresh icon is located on top of the Process Tracking tab page.

               Boundary Event Seen as an X Icon in Audit Trail

               1. Bug: 13263092
               2. Updated: 10-November-2011
               3. Platform: All

               During migration of an instance, an activity removed from the new process displays an X icon in the process instance audit trail. This can be confusing because a boundary event displays the same icon even though it is not removed. Note that this is a user interface issue only and causes no loss of functionality.

               Issues with Input/Output Message in Audit Trail During Alter Flow

               1. Bug: 13361923
               2. Updated: 10-November-2011
               3. Platform: All

               Issue 1: Viewing comments after alterflow

               Comments applied during grab/migrate are not visible unless you select the tree view in the audit trail list. Within that tree view, expand the activity where comment is applied. The comment column in audit trail is then populated with the comment.

               Issue 2: Input output message shows the content of a previously selected record

               If, in the audit trail of an instance, the input/output message is for a previously selected record, then do the following:

               1. 1. Refresh the process tracking table.
               2. 2. Select any other record.
               3. 3. Select once again the record whose message you want to view. This time the input/output content is correct.

               Use Only a Valid Combination When Changing the Variables ownerType and owner

               1. Bug: 13355820
               2. Updated: 10-November-2011
               3. Platform: All

               You can change the values of the process instance variables ownerType and owner during runtime while performing a grab/migrate action in the BPM Workspace Process Tracking page. When you do this, you must use the valid combination of ownerType and owner -- for example:

               • Valid combination: owner=jstein and ownerType=USER
               • Invalid combination: owner=jstein and ownerType=ROLE

               Cannot Simultaneously Move a Token from both a User Task Within a Subprocess and from the Subprocess Itself

               1. Bug: 13336279
               2. Updated: 05-December-2011
               3. Platform: All

               Moving a token simultaneously from both a user task within a subprocess and the subprocess itself may result in an error. You should move the token from either the subprocess, or from the user task, but not from both.

               You Can Neither Alter the Flow of an Errored Instance Nor Resume It

               1. Bug: 13254650
               2. Updated: 05-December-2011
               3. Platform: All

               You cannot alter the flow of an errored instance, nor can you resume it.

               Custom Page Name and Layout Changes While Navigating Between Pages in Edit Mode

               1. Bug: 13253389
               2. Updated: 07-November-2011
               3. Platform: All

               You can edit only one custom page at a time. You can create a custom page, edit it, add panels to it, and then save it. Then, after you have saved the previous page, you can select another page to edit or create a new page. However, if you do not save the previous page that you were editing, then the settings of the older page-- for example, the page name--are copied on to the new page.

               Unable to View Complete Error Message in Grab Panel

               1. Bug: 13098620
               2. Updated: 07-November-2011
               3. Platform: All

               When you attempt to alter the flow of a running instance, a Grab Confirmation dialog box tells you the result. If an exception is thrown, the error message may not be completely visible in the Grab results panel. To view the complete message, hover over the cell and read the tool tip that appears.

               The weblogic.xml file Is Incorrect when Task Form Application Is Migrated from an Older Version in Oracle JDeveloper

               1. Bug: 13051963
               2. Updated: 07-November-2011
               3. Platform: All

               When task-details projects are either moved or deployed on the server based on Releases PS3 to PS5 onwards, then you must change the weblogic-application.xml file in the task details project to include the following:

               Copy

               
               
                 <library-ref>
                     <library-name>oracle.soa.worklist.webapp</library-name>
                     <specification-version>11.1.1</specification-version>
                 </library-ref>
               reference 
               

               No Auto-Migration While Redeploying Incompatible Process with "Force Deploy" Property Set to TRUE

               1. Bug: 12918436
               2. Updated: 05-December-2011
               3. Platform: All

               If a process is incompatible with a new implementation, and if, during design time, the process is implemented with both "keep running instances" and "force deploy" set to true, then, on deployment, instances of that process go into pending migration and the component is suspended. The "force deploy" property is set in the composite.xml file in Oracle JDeveloper. The property is oracle.bpm.bpmn.force.deploy.

               In this scenario, a pending migration instance may not migrate successfully. For example, if the token is running inside a parallel gateway pair and the gateway pair is removed from the modified process, then the token will not have a valid target to move to and migrate will not succeed.

               BPM Workspace Page Takes Only One Entry in BPM_USERAPPLICATIONDATA; Limits Test-to-Production (T2P) page migration

               1. Bug: 12876023
               2. Updated: 07-November-2011
               3. Platform: All

               In BPM Workspace, no matter how many workspace pages are created, all the info is recorded in one row of BPM_USERAPPLICATIONDATA with:

               APPLICATIONDATANAME = WAM

               APPLICATIONDATATYPE = PART_PROPS

               This limits the Test-to-Production (T2P) page migration to either all or nothing.

               It also limits the T2P page migration to replace all the existing pages.

               For example:

               Test env has following defined in page: "Widget1" , "Widget2" , "Widget3"

               Prod env has following defined in page: "WidgetA" , "WidgetB"

               In this example, T2P cannot just export "Widget1" and append to production which results to "WidgetA", "WidgetB", "Widget1". Only option after the export and import is that the production environment will have "Widget1", "Widget2", "Widget" defined, and "WidgetA", "WidgetB" removed.

               Unable to Obtain Task ID to use Update Task Activity

               1. Bug: 12813850
               2. Updated 29-October-2012
               3. Platform: All

               The Update Task Activity enables you to update a task based on the task ID but currently there is no predefined dialog or XPATH function to obtain the taskId. Using the TaskExecutionData is not an option because the value is available after the task is completed.

               Workaround Assign the taskId variable to an output parameter in the Update Task data association. The BPM Engine evaluates and assigns a value to this variable after initiating the task, so the variable is assigned the task ID before completing the task.

               Pending Migration Instance Details Show Activity ID Instead of Activity Name in Open Activities

               1. Bug: 12681352
               2. Updated: 12-September-2011
               3. Platform: All

               After installing the OPatch and performing the BPM-specific post-installation steps, but before starting the soa_server1, delete the WLS tmp directory for Oracle BPM Workspace.

               Business Rules

               Verbal rule is not updated when business phrase is modified

               1. Bug: 18717541
               2. Added: 23-May-2014
               3. Platform: All

               There are 2 issues that arise when a business phrase is modified.

               1. Closing curly brace does not show up on newly added business phrase. This issue comes up while creating a verbal rule test/action by adding a new business phrase that contains a parameter within curly braces at the end of the phrase. The business phrase gets added without a closing brace.

               Workaround: Add a space after the parameter. Another workaround is to edit the business phrase and add the parameters.

               2. Verbal rule is not updated when a business phrase is modified. When a business phrase is modified and if that business phrase is used within a verbal rule that has already been displayed, automatic Refresh does not occur.

               Workaround: Add/delete a test/action to refresh the list.

               Order Rules By Buckets value lost after importing in Microsoft® Excel

               1. Bug: 18383063
               2. Added: 23-May-2014
               3. Platform: All

               The Order Rules By Buckets property is not persistent in Microsoft® Excel during export-import cycle.

               Workaround: Set the appropriate flag after importing.

               IllegalArgumentException is thrown when you move from Decision Table screen to If/Then Rules screen

               1. Bug: 16197234
               2. Added: 23-May-2014
               3. Platform: All

               When you change the name of a ruleset in Decision Table screen and then move to If/Then Rules screen, an IllegalArgumentException is thrown.

               Workaround: Refresh the page.

               Rule Reporter deprecated in 12c

               1. Bug: 18323091
               2. Added: 23-May-2014
               3. Platform: All

               OBR RuleReporter is deprecated in 12c.

               Business-to-Business Integration (B2B)

               DOC: Release Notes for 12.1.3. AS4 Opatch

               1. Bug: 20518563
               2. Added: 10-Feb-2015
               3. Platform: All

               Oracle B2B introduces Applicability Statement4 (AS4) protocol to the existing exchange protocol stack of B2B for secure document-agnostic exchange of payloads using web services. AS4 secures data with authentication, message integrity, non-repudiation of origin, and privacy features. The AS4 release patch is Drummond Group certified.

               PSR:PERF:SOA: Too many open files exception with ebMS 2.0 B2B - BT Use case

               1. Bug: 19319135
               2. Added: 29-July-2014
               3. Platform: All

               When system performance on Linux is affected by using too many file descriptors, you may receive an error message in the log file '(Too many open files)'.

               Workaround: For Linux systems the file responsible for setting limits is /etc/limits. In case of Linux add the following code in this file path - /etc/security/limits.conf:

               weblogic soft nproc 32768

            4. weblogic hard nproc 32768 weblogic soft nofile 32768 weblogic hard nofile 32768

               Weblogic is your user, then re-login with Weblogic user and test open file descriptors limit by $ ulimit -n

               Note: The setting in /etc/security/limits.conf is specific to the Linux platform. Each platform needs a different technique to increase the maximum file descriptor.

               Archive/Restore from PS6 to 12c

               1. Bug: 18610942
               2. Added: 09-May-2014
               3. Platform: All

               Archiving and restoring of RT data from one major release (such as 11.1.1.7.0) to another major release (12c 12.1.3) is not supported.

               Incomplete update of message states in Inbound EDIEL batch cases

               1. Bug: 18442417
               2. Added: 09-May-2014
               3. Platform: All

               In Inbound EDIEL batch cases, only one of the inbound message is marked as MSG_COMPLETE, and other messages remain in MSG_WAIT_FA state. The CONTRL generated is also in MSG_COMPLETE state.

               Single Quote in agreement name is displayed as another character in EM

               1. Bug: 18199273
               2. Added: 09-May-2014
               3. Platform: All

               If the agreement name contains a single quote in the B2B design data, then it is displayed as another character in the EM environment. For example, the single quote, ' (U+0027) is displayed as ` (U+0060).

               This is a known issue.

               Batch Update option is removed from the B2B UI

               1. Bug: 18191795
               2. Added: 09-May-2014
               3. Platform: All

               The Batch Update option in the Manage Batch screen (which was available in earlier releases) under Administration is no longer available.

               Intermittently, B2B does not create proper error for negative GTCP scenarios

               1. Bug: 18178730
               2. Added: 09-May-2014
               3. Platform: All

               Intermittently, B2B does not create proper error for messages revived on generic TCP without start block, end block, data size, and so on.

               Error information missing in required PO if ACK fails on delivery to back-end

               1. Bug: 18177661
               2. Added: 09-May-2014
               3. Platform: All

               When the Inbound Ack (for the Outbound Req) fails to be delivered to the back-end, the OB Req message goes to the MSG_ERROR state. However, in the Report, the OB Request message has no information about the error. The fields like Error Code, Error Description, Error Text do not have any information.

               OB Batch message remains in MSG_WAIT_BATCH state after it is invoked

               1. Bug: 18177625
               2. Added: 09-May-2014
               3. Platform: All

               In B2B, When a new Batch job is created for HIPAA outbound messages (from Administration/Batch), once the scheduled time has expired, while processing the messages, if these messages fail due to no message translation, the batch processing is then aborted with no given error and the messages will remain in MSG_WAIT_BATCH state. Enable the message translation to avoid this problem.

               MLLP: Inbound message with sync FA, Outbound FA remain in MSG_WAIT_ACK

               1. Bug: 18060437
               2. Added: 09-May-2014
               3. Platform: All

               In MLLP 1.0 message with sync FA case, outbound Synch FA remains in MSG_WAIT_ACK state and creates one additional message with processing state in Wire Message Reports. This is a limitation of MLLP.

               EDIEL: CONTRL send from back-end is not co-related to the inbound message

               1. Bug: 18058353
               2. Added: 09-May-2014
               3. Platform: All

               Outbound CONTRL document generated from the backend (not self generated by B2B) is not getting correlated to the inbound EDIEL message (for example an inbound DELFOR message).

               INBOUND270-SYNC999 use case with error shows up as a flow instance in completed state

               1. Bug: 18044150
               2. Added: 09-May-2014
               3. Platform: All

               In Sync response case, if the negative acknowledgement is received and inbound message is marked as an Error in B2B reports, however, still SOA composite instant state will not be updated to error and flow instance state will be completed in EM console.

               Fabric instance are marked completed as message is received in B2B

               1. Bug: 18026990
               2. Added: 09-May-2014
               3. Platform: All

               To avoid any performance issue, if a message is marked for batching, the fabric instance is marked as complete as soon as the message is received in B2B. Though in B2B the message is not delivered to the Trading Partner and B2B message state may not be completed. For error message, user can still use the exception notification which is sent to the back-end as exception notification will be associated with the corresponding flow id. In case of retrying/resubmitting wire of a batched message, only a single notification is sent to the back-end and it will be associated with the flow id of the first message in the batch.

               Failed Inbound/Outbound edifact payload in native Windows environment

               1. Bug: 17885311
               2. Added: 09-May-2014
               3. Platform: Windows Environment

                  The edifact messages for inbound/outbound messages fail due to b2bhealthcare_generic.jar file Windows environment though .NET 4.0/.NET 4.5 is installed. This issue is specific to Windows environment.

                  The following are the errors:

                  • Inbound messages:
                    • Error Code: B2B-51507
                    • Error Description: Machine Info: (slc06fjy), Module could not be loaded
                    • Error Text: Plugin Manager Error
                  • Outbound messages:
                    • Error Code: B2B-51507
                    • Error Description: Machine Info: (slc06fjy), Payload validation error
                    • Error Text: Error Brief: Plugin Manager Error

                  Workaround: Remove all NetEngine related entries in the $ORACLE_HOME\soa\soa\thirdparty\edifecs\XEngine\config\XERegistry.xml file.

                  B2B outbound message and Ack need to have same correlation ID for flow tracking

                  1. Bug: 17550136
                  2. Added: 09-May-2014
                  3. Platform: All

                  The correlation will be strictly at an instance level. If an acknowledgement is received from the back-end for a message, the correlation ID present in the acknowledgement/response message will be honoured for tracking. If nothing is present, the instance tracking correlation ID information will be absent in B2B. The B2B reference to message id mechanism should be used to correlate such messages.

                  RNIF11 - Inbound request encountered B2B-51503 error when only Ack signed enabled

                  1. Bug: 17343994
                  2. Added: 09-May-2014
                  3. Platform: All

                  During the acknowledgement generation, it is required to have the original message digest reference to be mentioned in the acknowledgement message. The UI should not allow the user to enable Ack Signed unless Message Signed is enabled.

                  Ability to provide time-stamp format for file-name format transport parameter

                  1. Bug: 17003370
                  2. Added: 09-May-2014
                  3. Platform: All

                  You now have the ability to provide time-stamp in the desired format for Transport Protocol Parameter: Filename Format. You must provide the desired format within square brackets, i.e., [].

                  Send/Receive the acknowledgement/exception from back-end

                  1. Bug: 16944779
                  2. Added: 09-May-2014
                  3. Platform: All

                  This feature enables you to send/receive the acknowledgement/exception messages from/to the back-end.

                  Inbound messages:

                  To achieve this for inbound messages, you must set the Ack Mode as >code>Deferred in the channel configuration.

                  Outbound messages:

                  If the acknowledgement/exception messages need to be sent from back-end, it is required to have these values:

                  1. 1. Message Type = 3 for acknowledgement
                  2. 2. Message Type = 4 for exception

                  B2B positional flat file ECS/XSD files must have STANDARD: PFF, Version: V2

                  1. Bug: 16857601
                  2. Added: 09-May-2014
                  3. Platform: All

                  When generating the ECS/XSD files using the Oracle Document Editor (Edifecs Spec Builder), the Standard and the Version properties must be set to PFF and V2 respectively.

                  B2B message is in error but B2B composite instance state completed

                  1. Bug: 17712413
                  2. Added: 09-May-2014
                  3. Platform: All

                  When SOA composite sends messages to B2B, the B2B message is in ERROR state, but the B2B composite instance is in COMPLETED state.

                  The state of the composite reflects the state of the application message in B2B. The App Message for these messages is marked as complete as soon as the message is delivered; same is the case with the composite. Within B2B, you have the flexibility to mark the App message state as ERROR from COMPLETE. In case of Composite, this is not possible.

                  This is a known issue.

                  Allow more than one batch criteria per trading partner

                  1. Bug: 17952712
                  2. Added: 09-May-2014
                  3. Platform: All

                  Messages with the following plan information will be batched separately from messages with other plan information:

                  1. 1. D:Plan1A:0:0 - all messages with this plan with D will be held until the message with I:Plan1A:0:0 is received. Later, all the messages with Plan1A will be batched.
                  2. 2. D:Plan1B:0:0 - all messages with this plan with D will be held until the message with I:Plan1B:0:0 is received. Later, all the messages with Plan1B will be batched.

                  However, if B2B receives a message with E (E:Plan1B:0:0), then all the messages with the Plan1B will set to error and will not batch out any more.

                  Corrupted native payload shown in report for email inbound messages

                  1. Bug: 18430555
                  2. Added: 09-May-2014
                  3. Platform: All

                  In B2B Business Message Reports inbound Multi Byte Character Set (MBCS) payload over email transport case, some Multi Byte Characters are shown corrupted.

                  This is a known issue.

                  Corrupted payload in receiver reports for OAG native scenario

                  1. Bug: 18455891
                  2. Added: 09-May-2014
                  3. Platform: All

                  In B2B, when inbounding native payloads by generic protocol HTTP-1.0, some MBCS in payload is shown corrupted in receiver reports.

                  B2B Fabric CompositeDn should not be used as a application message criteria

                  1. Bug: 18596115
                  2. Added: 09-May-2014
                  3. Platform: All

                  While using Application Message search criteria, do not use Fabric CompositeDn.

                  Re-submit functionality issues

                  1. Bug: 18724855
                  2. Added: 09-May-2014
                  3. Platform: All

                  The following are the known issues with re-submit functionality:

                  1. 1. The RESUBMIT-REF_TO of re-submitted application message does not reference to original application message.
                  2. 2. If the message is part of the batch, then RESUBMIT_COUNT of the original message does not increment by 1.

                  AS1 requires email servers that use content type set as application/xml

                  1. Bug: 18622036
                  2. Added: 19-May-2014
                  3. Platform: All

                  Outbound payload messages can be sent successfully using AS1 protocol, but inbound messages will fail if the email server uses content type different from application/xml.

                  B2B UI is not HA Compliant

                  1. Bug: 18763874
                  2. Added: 20-May-2014
                  3. Platform: All

                  Users see the following warning message:

                  [APP: b2bui] Resource META-INF/adf-config.xml not found on the classpath.

                  Hence, the B2B UI is not High Availability (HA) mode compliant.

                  Sent timestamp shows incorrect value on the receiver's side

                  1. Bug: 18805257
                  2. Added: 22-May-2014
                  3. Platform: All

                  When a message is sent using AS2, the timestamp displayed at the receiver's side is incorrect. It is neither the sender's timestamp nor the receiver's timestamp. This issue occure only when the sender and receiver are in different timezones.

                  This is a known issue.

                  Command line Resubmit with -Dappmsgid argument

                  1. Bug: 18866486
                  2. Added: 05-Jun-2014
                  3. Platform: All

                  When running the command line Resubmit using -Dappmsgid argument, user is required to use the value of the ID field (instead of the APP_MESSAGE_ID) in the B2B_APP_MESSAGE table. The Resubmit will fail if the APP_MESSAGE_ID value is used with -Dappmsgid argument.

                  This is a known issue.

                  Issue with command line Purge with the -Dtp argument

                  1. Bug: 18898846
                  2. Added: 05-Jun-2014
                  3. Platform: All

                  When using the -Dtp argument with Command line Purge, it will either fail to run or fail to remove expected runtime message instance(s).

                  This is a known issue.

                  Host/Remote Admin users allowed to purge/resubmit un-provisioned messages

                  1. Bug: 18940870
                  2. Added: 13-Jun-2014
                  3. Platform: All

                  In B2B, Host and Remote Administrators under Report are allowed to Re-submit/Purge a message with a document type that is not currently provisioned to the Administrator.

                  This is a known issue.

                  CRLF used as default segment delimiter when one of "Override Version Param" is NULL

                  1. Bug: 18955341
                  2. Added: 13-Jun-2014
                  3. Platform: All

                  User must specify each delimiter used in the document protocol area (global) or each delimiter used in "Override Version Param" area.

                  Security information not propagated in received RNIF Request Signed message

                  1. Bug: 18960127
                  2. Added: 13-Jun-2014
                  3. Platform: All

                  While sending an Outbound RNIF Signed Request message on receiver side under Report in the Inbound Request message (wire), the Security information (i.e., SMIME) is not propagated from the sender side (empty).

                  This is a known issue.

                  Oracle Event Processing

                  Oracle API Catalog Supports Harvesting Services with Only REST or SOAP Bindings from Oracle Service Bus

                  1. Bug: 20975485
                  2. Updated: 26-June-2015
                  3. Platform: All

                  The Oracle API Catalog harvester supports harvesting services with only REST or SOAP bindings from Oracle Service Bus. Harvesting services from Oracle Service Bus with other bindings is not supported.

                  This is a known issue.

                  Resource Properties Displays Wrong Type

                  1. Bug: 19808038
                  2. Added: 31-October-2014
                  3. Platform: All

                  When viewing the properties for an Oracle API Catalog Connection in the Oracle Enterprise Repository JDeveloper Plugin, Oracle Enterprise Repository is selected as default instead of Oracle Enterprise Repository.

                  This is a known issue for this release.

                  Cannot Extend a SOA Domain for Oracle API Catalog

                  1. No bug number
                  2. Added: 31-October-2014
                  3. Platform: All

                  When running the Domain Configuration Wizard, it is not possible to extend an existing Oracle SOA Suite domain for use with Oracle API Catalog. You must create a new domain for Oracle API Catalog.

                  This is a known issue for this release.

                  Harvesting from Oracle JDeveloper Not Supported

                  1. No bug number
                  2. Added: 03-December-2014
                  3. Platform: All

                  The 12c release of Oracle API Catalog does not support harvesting assets directly from JDeveloper.

                  Harvesting Assets from Oracle Service Bus on Windows

                  1. No bug number
                  2. Added: 03-December-2014
                  3. Platform: Microsoft Windows

                     You may receive an error message when using the Oracle Service Bus harvester to harvest assets from Oracle Servicer Bus on Microsoft Windows operating systems. This is a known issue.

                     Workaround

                     1. Ensure that the harvester is extracted into the /oer/tools/ directory in the same FMW Home directory to which Oracle Service Bus is installed. The full path to the harvester should be /oer/tools/osbharvester.

                     2. Using a text editor, edit the setEnv.bat file. Replace the following line:

                        set HARVESTER_HOME=%OER_HOME%\osbharvester

                        with this line:

                        set HARVESTER_HOME=%OER_HOME%\tools\osbharvester

                     Join a Stream with the Derby Database

                     When you join a stream with the Derby database, where the join condition compares two timestamp values where one value is from the stream attribute and the other value is from the Derby data source attribute, the Derby database performs the predicate evaluation. However, the Derby database supports only the yyyy-MM-dd-HH.mm.ss[.nnnnnn] format. For the Derby database to perform the evaluation correctly, the stream timestamp value must use the Derby database format.

                     1. Bug ID:17855179
                     2. Platforms: All

                     Workaround: Convert the timestamp from the stream to the Derby database format. The to_timestamp expression in the WHERE clause in the following example performs the conversion.

                     Copy

                     
                      
                       SELECT t.testTimestamp
                     FROM S1[NOW] as s, T1 as t
                     WHERE to_timestamp(to_char(s.testTimestamp, 'yyyy-MM-dd HH:mm:ss'),'yyyy-MM-dd HH:mm:ss') = t.testTimestamp
                     
                     

                     If the timestamp value contains a fractional second component, use the appropriate format to parse the fraction component as shown in the following example:

                     Copy

                     
                         
                         SELECT t.testTimestamp
                         FROM S1[NOW] as s, T1 as t
                         WHERE to_timestamp(to_char(s.testTimestamp, 'yyyy-MM-dd HH:mm:ss.SSS'),'yyyy-MM-dd
                         HH:mm:ss.SSS') = t.testTimestamp   
                     
                     

                     Note: For information about the data type mappings between Oracle CQL, Java, and JDBC to form join expressions, see Table 3-4 in Section 3.3 of Oracle Fusion Middleware Developing Applications for Oracle Event Processing.

                     In Oracle CQL, the XML Query String Must Be On One Line

                     When you write an Oracle CQL XML query string, you must keep it all on one line with no line breaks.

                     The following example shows an XML query string on one line followed by an XML query string that is incorrect:

                     Copy

                     
                      
                     
                     xmlquery(
                         'let $i := /*:FraudCheckRequest[1]/*:OrderNumber[1] return data($i)' 
                         PASSING BY VALUE S.xmlContent AS "." 
                         RETURNING CONTENT 
                         ) XMLData 
                     
                     The const string 'let $i := /*:FraudCheckRequest[1]/*:OrderNumber[1] return data($i)' 
                     can only be on one line. The following case is NOT supported:
                         

                     
                     xmlquery( 'let $i := /*:FraudCheckRequest[1]/*:OrderNumber[1] return data($i)' PASSING BY VALUE S.xmlContent AS "." RETURNING CONTENT ) XML 

                     Remote Oracle Event Processing Visualizer: Cannot See Events in Pub-Sub Channel

                     When you use Oracle Event Processing Visualizer, you cannot see the events in a publish-subscribe channel unless you use the workaround explained here.

                     1. Bug ID: 18741048
                     2. Platform: All

                     Workaround:

                     1. Start the record and playback sample domain on the local machine.
                        • The record and playback sample domain is here:
                        • /Oracle/Middleware/my_oep/oep/examples/domains/recplay_domain/defaultserver
                        • Start the server by executing the startwlevs command that is appropriate for your platform, either Windows or UNIX.
                     2. Access Oracle Event Processing Visualizer from a remote machine with a URL that contains the IP address of the local machine. For example, if the IP address is 10.245.27.37, the URL would be http://10.245.27.37:9002/wlevs.
                     3. Log into Oracle Event Processing Visualizer. The default login is oepadmin and welcome1
                     4. Open the EPN for the Record and Playback application.
                     5. Start recording on the simpleEventSource stage and stop recording after about 5 mins.
                     6. Start Playback on eventStream.

                     7. Use the Oracle Event Processing Viewstream module to view the events that are publishing to the publish and subscribe channel called playbackchannel. The output looks similar to the following:

                        {"creationTime":"02:09:07.629","playbackTime":"02:17:02.119"} {"creationTime":"02:09:07.933","playbackTime":"02:17:02.427"} {"creationTime":"02:09:08.237","playbackTime":"02:17:02.727"} {"creationTime":"02:09:08.541","playbackTime":"02:17:03.031"} {"creationTime":"02:09:08.845","playbackTime":"02:17:03.335"} {"creationTime":"02:09:09.149","playbackTime":"02:17:03.639"}

                     A Join with a Property that is Not a Key Does Not Work with Cache Loader and Store

                     A cache that has a custom cache loader and store cannot be joined with the non-key properties of the cache in Oracle CQL. Also, with a cache that has a loader and a store, you must present all of the key properties in the Oracle CQL Join condition statement.

                     1. Bug ID: 18798061
                     2. Platform: All

                     You join the cache in the following unsupported and supported cases. In the following cases, the key properties of the cache are key1 and key2:

                     Not Supported

                     • Less key property:

                       SELECT s.field1, cfield2 FROM S1[NOW] AS s, Cache AS c WHERE s.key1 = c.key1

                     • Non-key property:

                       SELECT s.field1, c.field2 FROM S1[NOW] AS s, Cache as c WHERE s.key 1 = c.key 1 AND s.field 1 = c.field1

                     Supported

                     • Equal operator:

                       SELECT s.field1, c.field2 FROM S1[NOW] AS s, Cache as c WHERE s.key1 = c.key1 AND s.key2 = c.key2

                     • Not-equal operator:

                       SELECT s.field1, c.field2 FROM S1[NOW] AS s, Cache AS c WHERE s.key1 = c.key1 AND s.key 2 != c.key2

                     Custom Cache Loader and Store Does not Work with a Replicated or Distributed Coherence Cache

                     A custom cache loader and store does not work with a replicated or distributed Coherence cache. However, the built-in Java Persistence API (JPA) cache loader and store work well with a distributed or replicated Coherence cache.

                     1. Bug ID: 18797792
                     2. Platform: All

                     Workaround: Use the built-in JPA cache loader with a distributed or replicated Coherence cache.

                     Some Samples Do Not Build the JAR File from Source Code Folder

                     The spatial, cql, and signalgeneration sample programs come with the Oracle Event Processing installation. The build process for these examples fails.

                     Workaround:

                     To build these sample programs, perform the following steps:
                     1. Add the Oracle\Middleware\my_oep\oep\common folder to the classpath.
                     2. Build the source:
                        1. Import the source to Oracle JDeveloper or to Eclipse.

                           The build files for the samples are in the following directory:

                           Oracle\Middleware\my_oep\oep\examples\source\applications\[example]\src

                        2. In your IDE, Build the project.
                        3. In your IDE, Export the JAR file.
                     1. Bug ID: 18795353
                     2. Platform: All

                     Oracle CQL Replace View Fault when in Business or Admin Role

                     When you are in either the BusinessUser or Admin administrator role, you cannot replace the view with Oracle CQL commands that contain the wildcard (*) in the SELECT clause. Instead, you must specify the column names in the SELECT clause.

                     1. Bug ID: 18003465
                     2. Platform: All

                     Workaround: Specify the column names in the SELECT clause.

                     Deploy Same EPN Multiple Times with Different Parameters

                     When you deploy the same EPN multiple times with different parameters, you must follow these steps:

                     1. Create your parameterized application and specify the parameters of your choice according to the MetaType specification.
                     2. Write an Ant task that takes as input the JAR file from Step 1 and generates the same JAR file but with a new value for the MANIFEST header entry of 'Bundle-SumbolicName'(myapp-1, myapp-2, ...).
                     3. Use a shell to deploy the JAR file of step 2 with the right parameter values.

                     In parameterized applications, do not include entities that are global, such as event type definitions and EPN stages that are marked as advertised.

                     1. Bug ID: 18637586
                     2. Platform: All

                     Server Start Failed with Cluster Configuration on AIX

                     When you deploy to AIX, be aware of the following workarounds:

                     • Multicast and IPv6
                     • Unique Multicast Addresses and Ports
                     1. Bug ID: 18243414
                     2. Platform: AIX

                     Multicast and IPv6

                     AIX 5.2 release and above default to running multicast over IPv6 instead of IPv4. If you run in a mixed OPv6/IPv4 environment, configure your JVMs to explicitly use IPv4, as follows:

                     On the command line, set the java.net.preferIPv4Stack system property to true. See the IBM 32-bit SDK for AIX User Guide for details.

                     Unique Multicast Addresses and Ports

                     On AIX, it is suggested that each Coherence cluster use a unique multicast address and port. This is because some versions of AIX do not take both into account when delivering packets. See the element for details about how to configure this address.

                     Cannot Configure Encrypted Password for Oracle Event Processing Components in Oracle JDeveloper

                     The encrypted password mechanism for Oracle Event Processing components does not work in this release.

                     1. Bug ID: 16819424
                     2. Platform: All

                     Workaround: None.

                     Type Conversion Problems Default to Zero for Long to Int Downcast in Event Types

                     Oracle Event Processing does not throw a ClassCastException when an application implicitly converts a long value to an integer value between two event type classes. Your application might display unpredictable behavior when the input long value is out of scope for the integer value.

                     1. Bug ID: 17370920
                     2. Platform: All

                     Workaround: None.

                     Oracle JDeveloper Does not support One Zip file with Multiple Applications or Projects

                     1. Bug: 17342003
                     2. Platform: All

                     Oracle JDeveloper 12c does not support one zip file that contains multiple applications or multiple projects within one application.

                     Java Event Properties with CQL Keywords for Property Names Cause Errors

                     1. Bug: 12426096
                     2. Platform: All

                     The Java event property timestamp is a native data type that clashes with the CQL keyword, timestamp. When you use the timestamp event property and CQL keyword in the same application, Oracle Event Processing generates an error similar to this:

                     The application context could not be started. Could not initialize component "MarketEventprocessor": Event property [cTimeStamp] defined in query [ExampleQuery] must exist in event type [MarketEvent]. Consider using the expression 'cTimeStamp AS ...' in the query.

                     Workaround: None.

                     No Support for Multibyte Character Sets

                     1. Bug:17277407
                     2. Platform: All

                     Oracle Event Processing does not support Chinese and other character sets that need more than a single byte to be represented.

                     Workaround: None.

                     CQL Processor Cannot be Named lifecycleprocessor

                     1. Bug: 13848408
                     2. Platform: All

                     In an Oracle Event Processing application, do not name a processor lifecycleprocessor. If you name a processor lifecycleprocessor, you get the application context "lifecycleapp" could not be started error when you deploy the application.

                     Workaround: None.

                     Failed To Load The Bus Tracking Figure Of The OEP Spatial Sample On Oracle Enterprise Linux 6.1 Running FireFox 3.6.17

                     1. Bug: 16088260
                     2. Platform: All

                     The Flash file used in the spatial application for PS6 is incompatible with Oracle Enterprise Linux 6.1 running FireFox 3.6.17.

                     Workaround: Run earlier or later versions of the software.

                     Browser Hangs When an Application Subscribes to too Many Channels

                     1. Bug: 10416835
                     2. Platform: All

                     When you start an event trace on a channel in Visualizer and then subscribe to the trace channel in the ViewStream panel, the browser becomes unresponsive after about 10 minutes.

                     Web Application Installed with Spatial Sample is Not Removed When Sample is Uninstalled

                     1. Bug: 16052630
                     2. Platform: All

                     Installing the spatial sample also installs a web application that can be accessed at http://localhost:9002/bus/main.html. When you uninstall the sample, the web application remains. As a result, if you reinstall the sample, it may fail to redeploy.

                     Workaround: Separately remove the included web app when you uninstall the sample.

                     Operating System Locale Must Be Set to English for Installation

                     1. Bug: 14627283
                     2. Platform: All

                     Before installing on a non-English platform, the OS locale must be set to English in order for the installer's user interface to display properly. After installation, an English locale is not required for product user interfaces to display properly.

                     Workaround: Set operating system locale to English for installing.

                     A Cache Declared as a Foreign Stage Cannot Be Used as a Channel's Listener

                     1. Bug: 16026765
                     2. Platform: All

                     A cache declared in one OEP application can't be used as the listener for a channel in another OEP application. Declaring the cache as a foreign stage in the second application will generate an error when starting up the second application.

                     Workaround: None.

                     The silent.xml File Cannot be in the Relative Path

                     1. Bug: 13472811
                     2. Platform: All

                     Due to an issue in this release, you cannot create a domain with the configuration wizard in silent mode. On Windows and Linux, the following generates an error:

                     $MIDDLEWARE_HOME/ocep_11.1/common/bin/config.sh -mode=silent silent_xml=silent_domain.xml

                     The error is similar to this:

                     A fatal error has occurred. This application will terminate.

                     Workaround: Specify an absolute path to the domain XML file when running the configuration wizard, as in the following example:

                     $MIDDLEWARE_HOME/ocep_11.1/common/bin/config.sh

                     -mode=silent silent_xml=/home/username/silent_domain.xml.

                     Multiple Processor Views with the Same Name Hinder EPN Display

                     Bug: 13370547

                     In the Oracle CEP IDE for Eclipse, the Event Processing Network (EPN) viewer might be unable to display the EPN view if there are multiple processors with the same view name. For example, the EPN XML code snippet below shows two views whose names are "SomeView".

                     Copy

                     
                      
                            <processor> 
                             <name>OneProcessor</name> 
                             <rules> 
                                 <view id="SomeView"> 
                                     <!-- View code -->
                                 </view> 
                             </rules>
                             <!- More code -->
                         </processor> 
                     
                         <processor> 
                             <name>AnotherProcessor</name> 
                             <rules> 
                                 <view id="SomeView"> 
                                     <!-- View code -->
                                 </view> 
                             </rules>
                             <!- More code -->
                         </processor>
                          
                     

                     Workaround: Ensure that each view has its own name.

                     JDK 7 Must Be Used for Oracle CEP Server When Both IPv4 and IPv6 Support is Needed on Windows

                     1. Bug: 10215099
                     2. Platform: All

                     If your Windows installation of Oracle CEP server must support clients over both IPv4 and IPv6, the server instance must use JDK 7.

                     Workaround: No workaround.

                     Limited Browser Support for Uploading an Application JAR Over HTTPS

                     1. Bug: 12793925
                     2. Platform: All

                     Uploading an application JAR file over HTTPS by using Oracle CEP Visualizer is not supported in the following browsers: Mozilla Firefox, Google Chrome 15, Apple Safari 5.1. For uploading over HTTPS, use Internet Explorer.

                     Workaround: No workaround.

                     Event Processing Language (EPL) is Deprecated

                     1. Bug: 13350828
                     2. Platform: All

                     Oracle Event Processing Language (EPL) is deprecated and may be removed in a future release. Use Oracle Continuous Query Language (CQL) for new development.

                     Workaround: N/A.

                     Creating a Two-Way SSL Connection with WebLogic Server

                     1. Bug: 12771217
                     2. Platform: All

                     While making a two-way SSL connection with WebLogic Server, use the following steps.

                     1. Copy the DemoTrust.jks and DemoIdentity.jks from weblogic server to the CEP domain and run the following command. The command is displayed here on multiple lines for readability, but it should be run on a single line.
                        Copy

                        
                        keytool -importkeystore 
                                -srckeystore \defaultserver\ssl\DefaultIdentity.jks
                                -srcstorepass DemoIdentityKeyStorePassPhrase
                                -srcalias demoidentity
                                -srckeypass DemoIdentityPassPhrase 
                                -destkeystore \defaultserver\ssl\server.jks 
                                -deststorepass welcome 
                                -destalias demoidentity
                                -destkeypass welcome
                        Using the java command, pass the following properties to the startwlevs.sh script:
                        "%JAVA_HOME%\bin\java" %JVM_ARGS% %DGC% %DEBUG% 
                                -Dwlevs.home="%USER_INSTALL_DIR%" 
                                -Dbea.home="%BEA_HOME%" 
                                -Djavax.net.ssl.trustStore=ssl\DemoTrust.jks 
                                -Djavax.net.ssl.trustStoreType=JKS 
                                -Djavax.net.ssl.trustStorePassword=DemoTrustKeyStorePassPhrase 
                                -Djavax.net.ssl.keyStore=ssl\server.jks 
                                -Djavax.net.ssl.keyStoreType=JKS 
                                -Djavax.net.ssl.keyStorePassword=welcome 
                                -Dweblogic.StdoutDebugEnabled=true 
                                -Dssl.debug=true  
                                -jar "%USER_INSTALL_DIR%\bin\wlevs.jar" %ARGS% 

                     2. In the WebLogic Server console, enable two-way SSL by setting Two Way Client Cert Behavior to Client Certs Requested and Enforced.
                     3. In the WebLogic Server console, if your client certificate doesn't specify the hostname, set Hostname Verification to None.
                     4. If you are using your certificate instead of the certificate from demoIdentity.jks, you must import the certificate into the servers trust store using the JDK keytool.

                     Enterprise Repository

                     Correction to Upgrade Assistant Screens: Upgrading Schemas table in Task 2 of Section 1.1.4 in the Oracle Fusion Middleware Upgrade Guide for Oracle Enterprise Repository

                     1. No bug number
                     2. Added: 23-March-2015
                     3. Platform: All

                     In Section 1.1.4 of the Oracle Fusion Middleware Upgrade Guide for Oracle Enterprise Repository, the Available Components entry in Table 1-1 contains the following note.

                     NOTE: By default, the Oracle Platform Security Services (OPSS) and Audit Services schemas are selected. Most component upgrades requires these schemas. Do not deselect these options unless you are certain your upgrade does not require these schemas.

                     The Oracle Enterprise Repository upgrade does not require these schemas. The Oracle Platform Security Services and Audit Services schemas should not be selected.

                     This will be clarified in a future release of the documentation.

                     Harvesting from Oracle JDeveloper Not Supported

                     1. No bug number
                     2. Added: 23-March-2015
                     3. Platform: All

                     Previous versions of the Oracle Enterprise Repository Harvester allowed you to harvest assets directly from Oracle JDeveloper. The 12c release of OER does not support harvesting assets directly from JDeveloper.

                     Harvesting Assets from Oracle Service Bus on Windows

                     1. No bug number
                     2. Added: 23-March-2015
                     3. Platform: Microsoft Windows

                     You may receive an error message when using the Oracle Service Bus harvester to harvest assets from Oracle Servicer Bus on Microsoft Windows operating systems. This is a known issue.

                     Workaround

                     1. Ensure that the harvester is extracted into the <FMW_HOME>/oer/tools/ directory in the same FMW Home directory to which Oracle Service Bus is installed. The full path to the harvester should be <FMW_HOME>/oer/tools/osbharvester.

                     2. Using a text editor, edit the setEnv.bat file. Replace the following line:

                        set HARVESTER_HOME=%OER_HOME%\osbharvester

                        with this line:

                        set HARVESTER_HOME=%OER_HOME%\tools\osbharvester

                     REX API No Longer Being Depreciated

                     1. Bug: 17722159
                     2. Added: 31-October-2014
                     3. Platform: All

                     The Release Notes for Oracle Fusion Middleware, 11g Release 1 (11.1.1.4) states:

                     "The APIs in Repository Extensibility Framework (REX) are deprecated, and will be replaced in a major future release, however, you can still continue to use REX APIs in 11g Release 1 (11.1.1) and in other minor releases of Oracle Enterprise Repository 11g."

                     "The next major release of Oracle Enterprise Repository, which is 12g, is planned to include significant modifications to the current APIs in REX in order to align with standards, and improve ease of use and integration."

                     This note is no longer valid. The REX API is no longer being depreciated for Oracle Enterprise Repository 12c.

                     Composite Harvesting and Version Numbers Fixed

                     1. Bug: 18176300
                     2. Added: 31-October-2014
                     3. Platform: All

                     In previous versions of Oracle Enterprise Repository, when harvesting a composite at runtime, the harvester would take the revision number of the SOA Suite project and use this for the Version field for created assets. This was done for only assets specific to the composite, not all assets. For all other assets, such as services, endpoints, or interfaces, the harvester would set the Version field to “1.0”, making the assets inconsistent in the model.

                     This has been fixed in this release.

                     Incorrect Plug-in Login Module Class Name Corrected

                     1. Bug: 12941584
                     2. Added: 31-October-2014
                     3. Platform: All

                     The “Enable LDAP Integration System Properties Setting” section in the Configuration Guide for Oracle Enterprise Repository for the 11g Release incorrectly lists the Plug-in Login Module Class Name as:

                     com.oer.enterprise.authentication.server.loginmodule.LDAPLogin

                     The correct Plug-in Login Module Class Name is:

                     com.flashline.enterprise.authentication.server.loginmodule.LDAPLogin

                     This has been fixed in the documentation for the current release.

                     Inaccurate Search Results Fixed

                     1. Bug: 17742299
                     2. Added: 31-October-2014
                     3. Platform: All

                     Asset search results can be limited to a specific number. For example, a customer can display only 10 matches at a time for a search when there are 1000 matches. In previous versions of Oracle Enterprise Repository, search results displayed from a limited search were not displayed in alphabetical order. If no limit or “Show All” was selected the results were alphabetized.

                     This has been fixed in this release.

                     Project and Admin Portlets User Interface Behavior Updated

                     1. Bug: 18176285
                     2. Added: 31-October-2014
                     3. Platform: All

                     In previous versions of Oracle Enterprise Repository, the text boxes in the sidebar would not change size when the sidebar was extended when viewing the Project and Admin Portlets.

                     This has been fixed in this release.

                     Incorrect Version of BI Publisher Referenced in Upgrade Guide

                     1. No bug number
                     2. Added: 31-October-2014
                     3. Platform: All

                     Section 2.1 in the Oracle Fusion Middleware Upgrade Guide for Oracle Enterprise Repository states:

                     Note: If you are running BI Publisher 10g, the patch 9021224 is also required and must be applied to the BI Publisher server."

                     BI Publisher 10g is no longer supported for use with Oracle Enterprise Repository. This note should be ignored, as this patch is not required to use BI Publisher 11g with Oracle Enterprise Repository.

                     Enterprise Scheduler

                     Oracle Enterprise Fusion Middleware Control Console Throws an Exception when Attaching a Web Service Policy to an ESS Cluster

                     1. Bug: 18682657
                     2. Updated: 30-April-2014
                     3. Platform: All

                     When you use the scheduling service Job Metadata/Job Definition page to attach a web service policy at the cluster level, Oracle Enterprise Fusion Middleware Control Console throws an exception (EMSystemException).

                     Workaround: Instead of choosing the cluster in the Oracle Enterprise Fusion Middleware Control Console Target Navigation pane, choose one of the constituent servers from the cluster. Use the Job Metadata/Job Definition page to add the web services policy to that server.

                     Human Workflow

                     Workaround for Out Of Memory error while using the BPM Notification Service

                     1. Bug: 18781466
                     2. Added: 20-May-2014
                     3. Platform: All

                     While using the BPM Notification Service, when large number of log messages are rapidly generated, the jobs scheduled to process them are sometimes not started. This leads to such messages being piled up. As a result, the weblogic.diagnostics.watch.WatchEventListener object retains large amount of memory, which may eventually result in OutOfMemoryError.

                     Workaround: The limit on the number of outstanding jobs scheduled by WatchEventListener can be changed with the undocumented system property weblogic.diagnostics.watch.max_pending_jobs. By setting it to a high value, the work-manager eventually starts the scheduled jobs, thus draining the log messages queue in WatchEventListener. Use the following command for this workaround:

                     -Dweblogic.diagnostics.watch.max_pending_jobs=5000

                     If you run into problems while using this workaround, contact Oracle Support.

                     SOA Composer does not show Scroll Bar in Firefox and Chrome browsers

                     1. Bug: 18628955
                     2. Added: 21-May-2014
                     3. Platform: All

                     The horizontal Scroll Bar is not functional in SOA Composer when you use Firefox (24.4.0) and Chrome (34.0.1847.116) browsers. This is a known issue.

                     Workaround: Use Internet Explorer (IE). The Scroll Bar functions as expected with IE 9.0.8112 version.

                     Actionable Emails do not work for pre-upgrade instances

                     1. Bug: 18367575
                     2. Added: 21-May-2014
                     3. Platform: All

                     Actions taken on actionable emails sent in the pre-upgrade environment do not work post-upgrade. This is an expected and known behavior. This is because different encryption keys are used pre-upgrade and post-upgrade. due to which decryption fails.

                     Workaround: Use the worklist UI instead of notification email for approving the task created in pre-upgrade.

                     Portlet Integration/Upgrade not supported in 12c

                     1. Bug: 18315473
                     2. Added: 21-May-2014
                     3. Platform: All

                     Portlet integration/upgrade for services is not supported in 12c 12.1.3. If you have SOA and WebCenter portlet integration configured in 11g, you will be unable to upgrade to 12c 12.1.3 SOA, even just the SOA part. You must wait for the upgrade till WebCenter becomes available in the 12c train.

                     Workaround: There is no workaround.

                     Setting properties for JPS-CONFIG.XML is not required in 12c

                     1. Bug: 18140781
                     2. Added: 21-May-2014
                     3. Platform: All

                     The following properties that were required to be set in jps-config.xml file for 11g are not required to to be set in 12c:

                     user.login.attr=sAMAccountName

                     username.attr=sAMAccountName

                     Stake holder application role creation fails while deploying Case Composite

                     1. Bug: 16169796
                     2. Added: 23-May-2014
                     3. Platform: All

                     When you deploy the uploaded Case Composite, application roles for stake holders are not created during deployment.

                     Workaround: Add the following snippet in the system-jazn-data.xml file after upgrade to deploy composite of Case Management.

                     Copy

                     
                     
                     
                       <grant>
                                <grantee>
                                      <codesource> 
                         <url>file:${soa.oracle.home}/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.
                          <casemgmt.implementation.jar</url>
                         </codesource>
                          </grantee>
                           <permissions>
                           <permission>
                            <class>oracle.security.jps.JpsPermission</class>
                            <name>VerificationService.createInternalWorkflowContext</name>
                            </permission>
                              <permission>
                              <class>oracle.security.jps.service.policystore.
                               <PolicyStoreAccessPermission
                                </class>
                                <name>context=APPLICATION, name=OracleBPMProcessRolesApp</name>
                                 <actions>createAppRole,removeAppRole,addPrincipalToAppRole,
                                 removePrincipalFromAppRole,grant,revoke,getApplicationPolicy</actions>
                                 </permission>
                                   </permissions>
                                    </grant>
                         
                     
                      

                     Error thrown when submitting request from SOA-Infra

                     1. Bug: 18106765
                     2. Added: 28-May-2014
                     3. Platform: All

                     An exception is thrown when a request is submitted from SOA-Infra. This exception is only logged in VerificationService. This exception is thrown when the principal passed from SOA-Infra is not a WLSUSER like WebLogic.

                     Workaround: There is no workaround.

                     Deprecated SAML ports in all HWF Services

                     1. Bug: 18858774
                     2. Added: 29-May-2014
                     3. Platform: All

                     All HWF Services with SAML Ports are deprecated. Any more SAML port in HWF services in the following ports are not supported:

                     • TaskQueryServiceSAML in TaskQueryService
                     • TaskServicePortSAML in TaskService
                     • TaskMetadataServicePortSAML in TaskMetadataService
                     • UserMetadataServiceSAML in UserMetadataService
                     • RuntimeConfigServiceSAML in RuntimeConfigService
                     • TaskEvidenceServicePortSAML in TaskEvidenceService
                     • DiagnosticServiceSAML in DiagnosticsService
                     • AGQueryServicePortSAML in AGQueryService
                     • AGMetadataServicePortSAML in AGMetadataService
                     • OrganizationServiceSAML in OrganizationService

                     The client configuration file wf_client_config.xml does not include the identityPropogation element. To enable identityPoropogation, enable the Web Service Policy Sets and attach the SAML-token policy to them.

                     For more in formation about SAML, see the Introduction to Human Workflow Services chapter in the Developing SOA Applications with Oracle SOA Suite guide.

                     For more information about Client Configuration, see the Introduction to Human Workflow Client Integration with Oracle WebLogic Server Services chapter in the Developing SOA Applications with Oracle SOA Suite guide.

                     Rules based on Milestone Due Date and Deadline not available in Rule Dictionary

                     1. Bug: 18067641
                     2. Added: 29-May-2014
                     3. Platform: All

                     Users are unable to create rules based on Milestone Due Date and Deadline.

                     This is a known issue.

                     Workaround: There is no workaround.

                     Rules based on Case Due Date and Deadline not available in Rule Dictionary

                     1. Bug: 18067625
                     2. Added: 29-May-2014
                     3. Platform: All

                     Users are unable to create rules based on Case Due Date and Deadline.

                     This is a known issue.

                     Workaround: There is no workaround.

                     Unable to add same type of Input and Output data objects to Rules

                     1. Bug: 182751195
                     2. Added: 29-May-2014
                     3. Platform: All

                     Users are unable to add same type of Input and Output data objects to Rules. The following error message appears:

                     Variables of the same name type are not allowed for rules

                     This is a known issue.

                     Workaround: Do not add the output data object while creating the BPMN process. When the business rule is created, go to business rules decision and edit it. Now, in the Outputs tab add the same data type as that of the input.

                     Missing data objects in data association of Business Rule Task

                     1. Bug: 18280982
                     2. Added: 29-May-2014
                     3. Platform: All

                     The data association for the business rule task does not work as expected. If you add 2 input and 2 output data objects while modeling the business rules task, the following behavior is observed:

                     The input business rule task arguments should have had 2 data objects, but the BPMN process has only 1 data object.

                     The output business rule task arguments should have had 2 data objects, but the BPMN process does not have any data objects.

                     This is a known issue.

                     Workaround: There is no workaround.

                     Rules file gets updated only after closing and re-opening the file

                     1. Bug: 18372065
                     2. Added: 29-May-2014
                     3. Platform: All

                     The .Rules file gets updated with the changes made to it only after you close and re-open the file.

                     This is a known issue.

                     Workaround: There is no workaround.

                     Exception thrown when Business Task name is in lowercase

                     1. Bug: 18388804
                     2. Added: 29-May-2014
                     3. Platform: All

                     An exception is thrown when the name of a Business Task is in lowercase in the BPMN process.

                     This is a known issue.

                     Workaround: There is no workaround.

                     NullPointerException thrown in Rules Facts

                     1. Bug: 18388842
                     2. Added: 29-May-2014
                     3. Platform: All

                     When you change the XSD element name in the Rules File -> Facts, a NullPointerException is thrown.

                     This is a known issue.

                     Workaround: There is no workaround.

                     Rules Facts not updated on renaming/deleting the XSD element

                     1. Bug: 18388940
                     2. Added: 29-May-2014
                     3. Platform: All

                     When you modify the XSD element (adding another element inside it, renaming the element, or deleting the element), the changes are not updated to Rules Facts.

                     This is a known issue.

                     Workaround: There is no workaround.

                     Exception thrown while creating a Business Object (BO) based on XSD

                     1. Bug: 18516874
                     2. Added: 29-May-2014
                     3. Platform: All

                     The unable to parse schema exception is thrown when you try to create a BO (with the option Based on external schema) based on an XSD with the complexType element.

                     This is a known issue.

                     Workaround: There is no workaround.

                     Case Rules get corrupted while Modeling Case Project

                     1. Bug: 18541008
                     2. Added: 29-May-2014
                     3. Platform: All

                     When you create a BO based on oramds:/soa/shared/casemgmt/CaseEvent.xsd, perform the data association, and promote the process as CaseActivity, the case rules file gets corrupted.

                     This is a known issue.

                     Workaround: There is no workaround.

                     Rules Value Set is not updated when the project name is long

                     1. Bug: 18629390
                     2. Added: 29-May-2014
                     3. Platform: All

                     The rules value set (Milestone, Outcome, use defined events, and others) is not updated when the project name is long.

                     This is a known issue.

                     Workaround: There is no workaround.

                     NullPointerException is thrown while generating a Case Activity Form based on oramds type

                     1. Bug: 18534515
                     2. Added: 29-May-2014
                     3. Platform: All

                     A NullPointerException is thrown while generating a Case Activity Form based on the oramds:/soa/shared/casemgmt/Caseevent.xsd element type.

                     This is a known issue.

                     Workaround: There is no workaround.

                     Audit trial not updated properly across instances

                     1. Bug: 18053449
                     2. Added: 16-Jun-2014
                     3. Platform: All

                     If multiple instances have the same parent/instance folder, when a document is uploaded/deleted in one instance, the audit trial is not updated in the other instance.

                     This is a known issue.

                     Workaround: There is no workaround.

                     Audit trial is not updated if a document is added directly from UCM

                     1. Bug: 17925154
                     2. Added: 16-Jun-2014
                     3. Platform: All

                     When a document is uploaded into a case folder from the UCM Server, the audit trial is not updated.

                     Sometimes resource files are not copied to Classes directory

                     1. Bug: 18263712
                     2. Added: 20-Jun-2014
                     3. Platform: All

                     When you add locales to a case and re-deploy the project, the resource bundles are not copied to the SCA-INF/classes directory.

                     Workaround: Follow any one of the workarounds given below:

                     1. After adding the new locales, click General tab. Then click Translation icon and click OK.
                     2. Manually copy resource bundle file from the resources directory to the SCA-INF/classes directory.

                     Cannot Select the Tasktype from Tasktype Browser when Creating Vacation Rule

                     1. Bug: 14090553
                     2. Updated: 25-jul-2012
                     3. Platform: All

                     When creating Task Namespace,Task Definition Name,and Task Display URL conditions for a vacation rule in Oracle BPM Worklist, you do not have the option to select the tasktype from tasktype browser.

                     Cannot Use Oracle JDeveloper to Search for Approle in an Environment with only SSL Enabled

                     1. Bug: 13372192
                     2. Updated: 29-April-2011
                     3. Platform: All

                     In an environment in which SSL ports are enabled and non-SSL ports are disabled, you cannot search for approle by using Oracle JDeveloper. Attempting to do so prompts a SOAP exception.

                     Two Parameters not Relevant in Federated Worklist Environment

                     1. Bug: 13111612
                     2. Updated: 06-December-2011
                     3. Platform: All

                     The following parameters are irrelevant in a federated Worklist environment:

                     • showCreateTODOTaskAction
                     • showAssignmentFilter

                     If these are set in a federated environment, they will not be reflected in the Action list in Worklist.

                     FYI Stage Disappears from Task Sequence When It Follows a Parallel Participant

                     1. Bug: 13366984
                     2. Updated: 10-November-2011
                     3. Platform: All

                     The FYI stage disappears from the task sequence when it follows a parallel participant and the parallel participant completes the task. This is apparent in the following scenario:

                     1. Create an application with Human Workflow.
                     2. Add stage1 with parallel users jcooper, jlondon, fkafka.
                     3. After stage1, add stage2, sequential with stage1. Stage2 has only FYI user jstein.
                     4. Deploy the application and invoke an instance.
                     5. Login to BPM Worklist as jcooper, and click history in Task Details. The stage 2 user jstein is visible.
                     6. After all of the parallel users in stage 1 complete the task, log in to BPM Worklist as stage2 FYI user jstein, and click the history.

                     Note that stage2 has disappeared from the task sequence.

                     Completed Task Disappears When There Are Both an FYI USER and a Non-FYI User After the Task

                     1. Bug: 13366978
                     2. Updated: 10-November-2011
                     3. Platform: All

                     Consider the following scenario in which a task disappears from the list of completed tasks:

                     1. Create an application with Oracle Human Workflow.
                     2. Add stage1 with single user jcooper
                     3. After stage1, add parallel stages: stage2, stage3, and stage4. These are sequential with stage1.
                        • In stage2, there is only an FYI user, jstein
                        • In stage3, there is only an FYI user, wfaulk
                        • In stage4, there is a single user, cdickens
                     4. Deploy the app and invoke an instance.
                     5. In BPM Worklist, log in as stage1 user jcooper and approve the task.
                     6. Change the "State" to "Completed" to list the completed task.
                     Note that the task has disappeared.

                     A Parallel Stage with Only an FYI User Shows as Sequential Stages in History

                     1. Bug: 13366516
                     2. Updated: 10-November-2011
                     3. Platform: All

                     When parallel stages have only one or more FYI users in each of stages, the stages show up as sequential in the history graph.

                     Reusable Worklist Task Flow regions Need Entry in web.xmlFile

                     1. Bug: 13354559
                     2. Updated: 08-November-2011
                     3. Platform: All

                     Newer versions of Oracle JDeveloper configure applications to use ojsp.next mode. To override that, include the following servlet and servlet-mapping entries in the web.xml file.

                     Copy

                     
                     
                            <servlet>
                             <servlet-name>jsp</servlet-name>
                             <servlet-class>oracle.jsp.runtimev2.JspServlet</servlet-class>
                              <init-param>
                                  <param-name>static_text_in_chars</param-name>
                                  <param-value>true</param-value>
                             </init-param>
                              <init-param>
                                  <param-name>generic_servlet_mode</param-name>
                                  <param-value>single</param-value>
                              </init-param>
                              <init-param>
                                  <param-name>page_provider</param-name>
                                 
                      <param-value>oracle.adf.library.webapp.ADFJspResourceProvider</param-value>
                              </init-param>
                              <load-on-startup>2</load-on-startup>
                          </servlet>
                          <servlet-mapping>
                              <servlet-name>jspvservlet-namev
                              <url-pattern>*.jspx</url-pattern>
                          </servlet-mapping>
                          <servlet-mapping>
                              <servlet-name>jsp</servlet-name>
                              <url-pattern>*.jsff</url-pattern>
                          </servlet-mapping>
                     
                          
                     

                     Incorrect Error Message When a Non-Existent UCM User Tries to Add UCM Attachments

                     1. Bug: 12917983
                     2. Updated: 12-September-2011
                     3. Platform: All

                     If you create a task with a single assignee that does not exist in UCM server, and you then enable UCM in the task editor without adding any extra properties, then, when you log into Worklist and try to add a UCM attachment, the following incorrect error message appears:

                     Error occurred while inserting a task attachment record.

                     Error occurred while inserting attachment liu10.txt for task a6ad8d42-f588-4e10-aacd-8f4542d2ca6d.

                     Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

                     Exceptions While Loading Configurations From Workflow Identity Configuration

                     1. Bug: 16399934
                     2. Updated 18-June-2013
                     3. Platform: All

                     The exceptions that appear while loading configurations from the workflow identity configuration, do not provoke any problems. They are just warnings.

                     Workaround There is no workaround.

                     Mediator

                     SOA-MDS Based Domain Value Maps (DVMs) Incorrectly Display Edit Options in Oracle JDeveloper

                     1. Bug: 18651132
                     2. Added: 10-June-2014
                     3. Platform: All

                     If you are using a SOA-MDS based DVM, or have moved a file-based DVM to the SOA-MDS design time repository, the DVM file is read-only. However, the Edit Mediator Override DVM dialog shows the Add, Edit, and Remove Domain/Values buttons. If you use these buttons to make changes to your SOA-MDS based DVM, the changes are not saved.

                     Overriding a Static Routing Rule Using a Decision Component Throws Exception if No Matching Rule Can Be Found for a Request

                     1. Bug: 15953009
                     2. Added: 09-June-2014
                     3. Platform: All

                     If you override a Mediator static routing rule using a decision component, then for cases where the request does not match any value in the business rule, exceptions are generated.

                     Workaround: The workaround is to create a rule with an otherwise condition, and provide an empty value in the otherwise condition.

                     SQLINTEGRITYCONSTRAINTVIOLATIONEXCEPTION Exception Observed in Administration/Managed Server Logs after Upgrade or Server Restart

                     1. Bug: 18146388 and 14752082
                     2. Added: 09-June-2014
                     3. Platform: All

                     After server upgrade or restart, you might find the following error in the Administration or managed server log:

                     Copy

                     
                     
                     org.eclipse.persistence.exceptions.DatabaseException
                     
                     Internal Exception: java.sql.SQLIntegrityConstraintViolationException:
                     
                     ORA-00001: unique constraint 
                     
                     ...
                     
                     

                     This can happen after you upgrade or restart a server that has a resequencer component deployed in it, and a message arrives for an existing group after the server restart.

                     Also, when using resequencer on a cluster domain in standard mode, the messages are processed correctly, but the error message may appear in the linux shell on each of the cluster servers.

                     The unique constraint error messages are shown if you have previously changed the default logging level of the resequencer from ERROR to WARNING, NOTIFICATION, or TRACE.

                     This is a benign error and can be ignored. The resequencer takes care of the exception internally.

                     Duplicate Message Processing for Standard Resequencer Does not Complete After Purging

                     1. Bug: 13043897
                     2. Updated: 04-November-2011
                     3. Platform: All

                     When you run the purge scripts and remove Oracle Mediator sequenced messages, group information is retained for standard resequencers. If at a later time, a duplicate message is received with the same group ID and sequence ID as a message that was processed prior to the purge, that message is shown as Running in Oracle Enterprise Manager and the duplicate message is not processed. This only occurs when using the resequencer and does not cause any runtime failure.

                     Oracle Mediator - BPEL Process Manager Callback Processing

                     1. Bug: 8472652
                     2. Updated: 15-April-2011
                     3. Platform: All

                     If Oracle Mediator calls a BPEL process with callback processing and timeout, the best practice is to explicitly handle the callback exceptions returned from Oracle Mediator in the BPEL process. This ensures that the global transaction associated with callback processing gets committed and is not rolled back. This way, the timeout handler configured in Oracle Mediator will not kick in even if the callback handling in Oracle Mediator fails.

                     Oracle Mediator Components May Cause SOA Suite Server to Run Out of Memory

                     1. Bug: 9067255
                     2. Updated: 15-April-2011
                     3. Platform: All

                     Oracle Mediator applications may run out of memory under heavy loads. For example, if the rate of incoming messages to Oracle Mediator is faster than the rate of callback messages, memory accumulation occurs in the Oracle Mediator cache.

                     Workaround: To fix this issue, change the cache size through the Oracle Enterprise Manager Fusion Middleware Control Console by adding the following property in the Parameters attribute of the Oracle Mediator configuration properties:

                     mediator.runtime_cache.limit=value

                     For example, if you set the value of the mediator.runtime_cache.limit property to 100, the number of objects that can be stored in the cache is limited to 100. You can switch off caching completely by setting this property to zero.

                     Mapper Test Functionality Does Not Work for Mediator Advanced Functions in Design Time

                     1. Bug: 9072259
                     2. Updated: 15-April-2011
                     3. Platform: All

                     Oracle Mediator advanced functions, such as mhdr:getCompositeName() and mhdr:getHeader, require a runtime context to execute. If these functions are run using the Mapper Test feature during design time, the target XML file is not generated and the following error is thrown:

                     Copy

                     
                     
                     
                     XML-22044: (Error) Extension function error: Error invoking 'getComponentName':'
                     
                     java.lang.IndexOutOfBoundsException: Index: 0, Size: 0'
                     
                     These functions work correctly in the runtime environment.
                     
                     

                     Service Bus

                     What's New in 12c

                     For information on new features in Oracle Service Bus 12c, see the following:

                     • What's New in This Guide in Developing Services with Oracle Service Bus
                     • What's New in This Guide in Administering Oracle Service Bus

                     IBM WebSphere MQ Version 7.5 Now Certified with This Release of Oracle Service Bus

                     1. Bug: no bug number
                     2. Updated: 16-July-2015
                     3. Platform: All

                     IBM WebSphere MQ Version 7.5 has been certified for use with Oracle Service Bus 12c Release 12.1.3.

                     Oracle Service Bus Dashboard Page is Missing in Fusion Middleware Control

                     1. Bug: 20136341
                     2. Updated: 23-February-2015
                     3. Platform: All

                     In some instances, The Oracle Service Bus Dashboard page may be missing from Fusion Middleware control. If the service-bus node is missing from the SOA folder in the Target Navigation pane, perform the following steps to display it in Fusion Middleware Control:

                     1. In the server staging location, the em.war application's weblogic.xml file should have the following entry:

                        
                             <library-ref>     <library-name>osb.em</library-name>     </library-ref>     

                        If the entry is not present, add it to the weblogic.xml file.

                     2. Restart the servers. After the servers are restarted the Oracle Service Bus dashboard page should now appear in Fusion Middleware Control.

                     Resequencer Only Applies to Messages in the Pipeline

                     1. Bug: 19004690
                     2. Added: 17-June-2014
                     3. Platform: All

                     The behavior of the resequencer is not fully documented with regard to business services. When you configure a resequencer for a pipeline, only the messages coming into the pipeline are sequenced per the resequencing rules. The pipeline then forwards the messages, in order, to its target business service. However, it is possible the business service will process the messages in a different order. The resequencer does not guarantee the order messages are processed by the business service.

                     Debugger Limitations for SOA Apply to Oracle Service Bus

                     1. Bug: 19002913
                     2. Added: 16-June-2014
                     3. Platform: All

                     There are several guidelines and limitations published for the SOA debugger, which also apply to debugging Oracle Service Bus components. For more information, see Introduction to the SOA Debugger in Developing SOA Applications with Oracle SOA Suite.

                     WSDL Errors Can Occur When Oracle Service Bus and Oracle Business Process Manager Are on the Same Domain

                     1. Bug: 18856204
                     2. Added: 10-June-2014
                     3. Platform: All

                     If Oracle Service Bus is installed on the same domain as Oracle Business Process Manager (BPM), the following error can occur when creating a WSDL file:

                     The WSDL is not semantically valid: Failed to read wsdl file from url due to -- java.net.MalformedURLException: Unknown protocol: servicebus.

                     Workaround: Contact Oracle Support for a solution to this issue.

                     Workaround: Contact Oracle Support for a solution to this issue.

                     Changes Do not Show up on Fusion Middleware Control with Discovery Cache Enabled

                     1. Bug: 18774509
                     2. Added: 10-June-2014
                     3. Platform: All

                     When the Discovery Cache is enabled in Fusion Middleware Control, all target information is cached upon first login. Consequent logins retrieve the targets from the cache, which means changes, additions, and deletions to targets are not accurately reflected in the navigation tree.

                     Workaround: Either disable the Discovery Cache, or refresh the WebLogic server domain to update the target information.

                     Using Only Simple Element Types Causes Parsing Errors in REST Binding

                     1. Bug: 18695606
                     2. Added: 10-June-2014
                     3. Platform: All

                     Using only a simple element type (as you might do in testing) causes the parsing of the underlying object in a REST binding proxy service creation to fail.

                     Workaround: Data types must be wrapped in a complex type. For example:

                     Copy

                     
                     
                             
                       <element name="Name">
                              <complextType>
                                   <sequence>
                                       <element name="firstName" type="xsd:string">
                                  </sequence>
                              </complextType>
                           </element>    
                           
                        
                     
                     

                     OWSM Policies Are Not Applied When Activating a JCA Business Service

                     1. Bug: 18562166
                     2. Added: 10-June-2014
                     3. Platform: All

                     When you activate a project or deploy a configuration JAR file that includes a JCA business service with a PII policy attached, the policy is not applied until the server is restarted.

                     Workaround: Restart the server after importing or updating the JCA business service.

                     Updating a JCA Proxy or Business Service's Policy Mode Causes a Runtime Error

                     1. Bug: 18562207
                     2. Added: 10-June-2014
                     3. Platform: All

                     If you change the configuration of a JCA proxy or business service from OWSM Policy Store to No Policies, or vice versa, the JCA service generates an exception at runtime. For JCA business services with an OWSM policy attached, any change to the security or endpoint properties results in a runtime exception.

                     Workaround: For proxy services exhibiting this issue, modify one of the JCA endpoint properties and redeploy. The properties that can be changed depend on the specific JCA adapter used. For business services exhibiting this issue, restart the server after updating the properties.

                     WSDL Generated Missing Elements for Custom Exception

                     1. Bug: 18502287
                     2. Added: 17-June-2014
                     3. Platform: All

                     If an EJB contains custom exceptions and you export the WSDL file from the EJB business service, the generated WSDL file does not include the custom exception properties. The issue is limited only to the WSDL generation part of the file. During runtime, the custom exception thrown from the EJB is mapped to the respective elements in the SOAP fault. The elements in the response payload are populated corresponding to the properties of the custom exception.

                     Workaround: Manually edit the WSDL file to include these custom exception properties.

                     The Policy Violation Count Does Not Include HTTP Token Policy Violations

                     1. Bug: 18477417
                     2. Added: 10-June-2014
                     3. Platform: All

                     The policy violation metrics displayed on a service's Policies page in Fusion Middleware Control do not count http_*_token policy violations. This happens for HTTP token-based authentication policies only.

                     Connection to Application Server is Refused During UMS Adapter Configuration

                     1. Bug: 18424427
                     2. Added: 10-June-2014
                     3. Platform: All

                     When configuring the JCA Adapter for UMS, a server exception occurs and the connection is refused on the Identity Lookup for the application server.

                     Workaround: This issue is only observed from a server created outside of JDeveloper. Use an integrated server created within JDeveloper instead. You can also enter the user account manually.

                     Default Logging Format Does Not Log Authorized User

                     1. Bug: 18417685
                     2. Added: 10-June-2014
                     3. Platform: All

                     The default extended logging format does not include the name of the authorized user in the access log, which is required when using HTTP basic authorization.

                     Workaround: Change the logging format to Common. To access the log properties, launch the WebLogic Server Administration Console and navigate to Environment > Servers > server_name > Logging > HTTP (Advanced section) > Format. A server restart is required after this change.

                     Automatic Policy Configuration for STS May Result in an Incompatible Policy

                     1. Bug: 18384215, 18416081
                     2. Added: 10-June-2014
                     3. Platform: All

                     Using the automatic policy configuration for STS might not result in a compatible policy for a web service client.

                     Workaround: For information about this and other web services policy issues, see Web Services in the Release Notes for Oracle Fusion Middleware.

                     Global Policy Inheritance Rule Does Not Work For Authorization Policies

                     1. Bug: 18295336
                     2. Added: 10-June-2014
                     3. Platform: All

                     Authorization policies in the global policy set cannot be disabled by locally attaching the oracle/no_authorization_service_policy to the proxy service, where global policy is applied.

                     Workaround: To disable globally attached authorization policies, select No Policy in the proxy service security policy configuration in either the Oracle Service Bus Console or JDeveloper.

                     History Changes View Does Not Reflect All Proxy Services

                     1. Bug: 18058244
                     2. Added: 10-June-2014
                     3. Platform: All

                     In the Oracle Service Bus Console, the Changes sub-tab on the Histories tab does not reflect a newly created proxy service that was generated when creating a pipeline by selecting Expose as a Proxy Service.

                     Workaround: Refresh the window to show the new proxy service.

                     Pipeline Info Buttons on the Service Type Page Do Not Work When Launched from the Keyboard

                     1. Bug: 17959710
                     2. Added: 10-June-2014
                     3. Platform: All

                     With screen reader accessibility enabled, the Pipeline Service Type page has Info buttons next to the service type options. When you use the keyboard to navigate to and launch the Info windows, the window appears and then closes immediately. When you click an Info button with the mouse, the Info window remains open until you press Esc .

                     Workaround: Click the Info button with the mouse.

                     Import Config JAR Dialog Has Incorrect Default Focus

                     1. Bug: 17950304
                     2. Added: 10-June-2014
                     3. Platform: All

                     The Import Config JAR dialog defaults the focus to the "Input Source" flow diagram at the top of the dialog, which does not include active objects.

                     Workaround: Press the Tab key to bring the focus to the Browse button for the configuration JAR input.

                     KSS Keystore Might Require Updates After Import

                     1. Bug: 17799824
                     2. Added: 10-June-2014
                     3. Platform: All

                     The default keystore for Oracle Web Services Manager (OWSM) is now KSS. Any imported resources that previously used the JKS keystore might require either updates to the KSS settings or overriding the setting to use KSS. KSS keystore does not use passwords and does not require credential store, so these override properties might not be correct in the imported project.

                     Workaround: If you have overrides configured for keystore.sig.csf.key and keystore.enc.csf.key to csf-key, you need to change their values to give the direct keystore alias instead of csf-key. If you use default values (that is, no overrides), you can skip this step.

                     Updating REST Binding Fault Schema Results in Error

                     1. Bug: 17625172
                     2. Added: 10-June-2014
                     3. Platform: All

                     When you create a REST business service and add the fault binding for the response, you should not be able to change the schema type of the fault. However, the REST Binding wizard allows this. Editing the schema here returns a WADL validation error.

                     Workaround: Do not change the default schema.

                     Admin Server Log Contains an aia-log-debug-handler Error Post-Upgrade

                     1. Bug: 17381835
                     2. Added: 10-June-2014
                     3. Platform: All

                     The following message appears only once during the first re-start of the Admin server after you upgrade to 12c. The error does not indicate any issues with the AIA logging functionality and can be ignored.

                     The handler 'aia-log-debug-handler' is already defined in the target logging @ configuration document.

                     Null Pointer Exceptions Occur When Projects and Resources in JDeveloper Are in the Wrong Location

                     1. Bug: 17299328
                     2. Added: 10-June-2014
                     3. Platform: All

                     When you create projects and resources in a folder location outside of the folder of the containing application, null pointer exceptions occur when you perform certain tasks, such as importing resources. Creating resources outside of the application folder is not currently supported.

                     Workaround: Make sure to create all projects, folders, and resources under the directory of the containing application.

                     Runtime Validation for content-type is More Strict

                     1. Bug: 17187825
                     2. Added: 10-June-2014
                     3. Platform: All

                     In 12c, content-type validation is more strict than in previous versions. Therefore, requests with bad content-type that were previously allowed are no longer allowed in the current version. One example is sending a SOAP message with the content-type set to text/plain. This request would now be rejected.

                     Workaround: Configure the correct content-type for 12c services.

                     Creating a Global Policy Generates a Design-Time Conflict

                     1. Bug: 16894883
                     2. Added: 10-June-2014
                     3. Platform: All

                     If a proxy or business service is configured for OWSM policies and matches the configuration of an existing global policy set but does not support all of the policies in the global policy set, the following error occurs when you update the service in a new session, and a conflict is generated.

                     [OSB-398128]One of the Web service policy attached is not allowed on service path/resource_name because the service binding does not support it.

                     Workaround: When you create a global policy set with policies that are not supported by non-SOAP services, make sure that the policy set is configured specifically enough to exclude any non-SOAP services.

                     Log4j is no Longer Added to the System Classpath

                     1. Bug: 16729226
                     2. Added: 10-June-2014
                     3. Platform: All

                     Oracle Service Bus no longer adds log4j.jar to the system classpath automatically. If any of your applications or Java callouts depend on log4j being in the system classpath, add it to the classpath manually.

                     Moving a Service Causes Duplication in Policy Usage Analysis

                     1. Bug: 16711022
                     2. Added: 10-June-2014
                     3. Platform: All

                     If you move a proxy or business service with locally attached OWSM policies from one folder to another or from one project to another, the service is listed twice on the WebLogic Domain > WSM Policy > Usage Analysis page in Fusion Middleware Control. The expected behavior is that the service no longer appears in its original location on the usage analysis page, but it appears under both the original and the new locations.

                     Renaming a Service Causes Duplication in Policy Usage Analysis

                     1. Bug: 16704604
                     2. Added: 10-June-2014
                     3. Platform: All

                     If you rename a SOAP-based proxy or business service with locally attached OWSM policies, the service is listed twice on the WebLogic Domain > WSM Policy > Usage Analysis page in Fusion Middleware Control, once under its original name and once under its new name. The expected behavior is that the service no longer appears with its original name on the usage analysis page.

                     Deleted Services Still Appear in Policy Usage Analysis

                     1. Bug: 16704586
                     2. Added: 10-June-2014
                     3. Platform: All

                     If you delete a SOAP-based proxy or business service with locally attached OWSM policies, the service continues to appear on the WebLogic Domain > WSM Policy > Usage Analysis page in Fusion Middleware Control. The expected behavior is that the service no longer appears on the usage analysis page.

                     Unable to Create Durable Subscriptions on AQ Topics

                     1. Bug: 14321803
                     2. Added: 10-June-2014
                     3. Platform: All

                     On Oracle AQ, the subscriber name must be between 1 and 30 bytes long. Oracle Service Bus uses an MDB for JMS subscriptions, and generates the MDB name using the format "RequestEJB"+GUID. The GUID alone can be longer than 30 characters. When the MDB name is longer than 30 characters, an error similar to the following is logged:

                     RequestEJB5599235263010875116XX3906baed.137fe8c76cf.X7fc6 is unable to connect to the JMS destination: jms.fromSys1toSys2. The Error was: oracle.jms.AQjmsException: JMS-230: Illegal operation on durable subscription with active TopicSubscriber

                     Assign Activity Produces an Empty Message Body if a New Line Character Exists

                     1. Bug: 16205232
                     2. Added: 07-March-2013
                     3. Platform: All

                     The resulting message body is empty if a proxy service processes an XML string with a newline character after the XML declaration (<?xml version="1.0" encoding="UTF-8"?>), the message flow includes an Assign activity that uses fn-bea:inlinedXML() to assign that XML string to a variable, and the message flow uses the variable to replace the contents of $body. This is related to issue 13902323, caused by the fn-bea:inlinedxml() function trimming whitespace when parsing text to XML.

                     Pass-Through Pipeline Might Marshall and Unmarshall Message Body

                     1. Bug: 15908859
                     2. Added: 29-January-2013
                     3. Platform: All
                     If the message flow in a pipeline is configured to simply pass messages through with no modification, the messages are still parsed by the XML parser if the message content is accessed and read during processing. This means the original text is materialized into XMLBeans and then back into XML. For example, the message might be processed in a pass-through scenario, but be accessed and read by a logger during processing. In this case, the message is materialized into XMLBeans. When the message body includes decimal or hexadecimal representation of characters, the XML parser resolves these representations to the actual characters. Note that only the character representation of the information is changed and not the information itself.

                     Workaround: If there are character representations in the message content and you want to preserve the original character representations instead of converting them to the actual characters, either make sure the message body is unread during processing to ensure it is truly pass-through, or specify the representations inside a CDATA section before the message is received by Service Bus. For example:

                     
                     
                         <typ:NameElement>
                     <typ:name><![CDATA[&#x6C38;&#x697D;&#x4F4F;]]></typ:name>
                     </typ:NameElement> 
                     

                     JCA Polling Proxy Services Generate Stuck Thread Errors

                     1. Bug: 14831608
                     2. Added: 29-January-2013
                     3. Platform: All

                     Proxy services configured for JCA polling adapters (such as the JCA File Adapter, DB Adapter, AQ Adapter, and so on) might generate errors in the server log indicating that the thread is stuck, which causes the server's health status to change to WARNING. The errors are caused by the single listening thread created in the default Work Manager. This thread is non-terminating so the services can continue to poll for new events, but this means the thread necessarily remains busy longer than the configured maximum time. The error message indicates that the thread has been busy for "xx" seconds working on the request, which is more than the configured time (StuckThreadMaxTime) of "xx" seconds. The errors can be ignored, but might also fill up the server log.

                     Workaround: Because these error messages do not indicate a true problem, they can be suppressed. To do this, create a new Work Manager with the following setting:

                     <ignore-stuck-threads>true</ignore-stuck-threads>

                     Then modify the service's Dispatch Policy in the transport settings to use the new Work Manager. Any new stuck thread messages are written to the new Work Manager instead of cluttering up the default Work Manager.

                     Harmless Warning for JEJB 3.0 Proxy Service

                     1. Bug: 14321779
                     2. Added: 29-January-2013
                     3. Platform: All

                     After a JEJB 3.0 proxy service is created and activated, the following warning message appears in the managed server logs:

                     <Warning> <WebLogicDescriptorWL> <BEA-2156000><"config-root"/<path_to_ear_file>/<filename.ear>/plan was not found>

                     This warning is harmless and can be ignored.

                     HTTP Business Service Connection Timeout Not Honored on Windows 2008 64-bit

                     1. Bug: 13097895
                     2. Updated: 13-January-2012
                     3. Platform: Windows 2008 64-bit

                        Connection timeouts set on HTTP business services ("Connection Timeout" property in the HTTP transport configuration) are not honored in Windows 2008 64-bit environments.

                        Starting Managed Server with IPv6 Host and Port Throws BEA-000000 Error

                        1. Bug: 10029204
                        2. Updated: 14-January-2011
                        3. Platform: All

                        In the development environment, when starting a managed server by passing the managed server's IPv6 address and port, Oracle Service Bus throws a BEA-000000 "Cannot contact Admin server" error.

                        Workaround: Create a new key-pair, then reconfigure SSL on the Admin server so that the key-pair in the server-side SSL certificate uses the host name of your IPv6 managed server. Then restart your managed server. For more information on SSL, see Configuring SSL in Administering Security for Oracle WebLogic Server.

                        Password Field Not Editable in Domain Template on Linux

                        1. Bug: 10394900
                        2. Updated: 14-January-2011
                        3. Platform: Linux

                           On Linux, when creating a new domain using a developer template in the Oracle Fusion Middleware Configuration Wizard, the password and confirm password fields are not editable, and you cannot enter a password to create a domain.

                           Workarounds:

                           To work around the issue each time it occurs:
                           1. Click the close window "x" button in the upper right corner of the Configuration Wizard.
                           2. In the confirmation dialog that appears, click "No" to return to the Configuration Wizard.
                           3. Now you can enter the password and confirmation password.
                           To fix the issue permanently:
                           1. Kill a scim processes. For example, kill "pgrep scim"
                           2. Modify (or create) the file ~/.scim/config to include the following line: /FrontEnd/X11/Dynamic = true (follow case sensitivity).
                           3. If you are running VNC, restart the VNC server.
                           4. Run the Configuration Wizard again.

                           MQ Transport in Binding Mode Throws Error on Linux

                           1. Bug: 10020344
                           2. Updated: 14-January-2011
                           3. Platform: Linux

                              When Oracle Service Bus and IBM WebSphere MQ are installed on the same Linux system, configuring the Oracle Service Bus MQ transport to run in binding mode causes an error.

                              Workaround:

                              1. Make sure Oracle Service Bus and IBM WebSphere MQ are installed using the same user credentials.
                              2. Add the MQ Java library path to the Oracle Service Bus DOMAIN_HOME/bin/setDomainEnv.sh file. For example:

                                 -Djava.library.path=/opt/mqm/java/lib

                              3. Oracle JRockit: When using Oracle JRockit on Linux, add the LD_PRELOAD property to setDomainEnv.sh as well. For example:

                                 LD_PRELOAD=${JAVA_HOME}/jre/lib/i386/libjsig.so

                              Resources Disappear When Server Encoding Changes

                              1. Bug: 9488927
                              2. Updated: 14-January-2011
                              3. Platform: All

                              After creating resources in the Oracle Service Bus Console, then changing the server encoding and restarting the server with the different encoding, only English language resources (if any) appear in the Oracle Service Bus Console. Non-English resources do not appear. For example, if you start the server using ja_JP.utf8 encoding and create resources in the Oracle Service Bus Console with Japanese, Korean, and English names, then restart the server using a different encoding such as ko_KR.euckr, only the English-name resources appear in the Oracle Service Bus Console. In this situation, the missing resources still exist but are not displayed because of the encoding change.

                              Workaround: Switch back to the original server encoding and restart the server. Oracle Service Bus does not support server encoding changes.

                              Healthcare Integration

                              b2b.preProcessorDocIdentification causes issue in Inbound Acknowledgement Message Processing

                              1. Bug: 16321831
                              2. Added: 06-May-2014
                              3. Platform: All

                              You must use the healthcare em property b2b.preProcessorDocIdentification in conjunction with b2b.discardACKList=ALL.

                              Healthcare Reports UI Msg Flow Color Annotations

                              1. Bug: 16525641
                              2. Added: 06-May-2014
                              3. Platform: All

                              The following colors annotate a condition between two stages (internal/external endpoint, wire/business/app message) bracketing a flow link:

                              • Red: Error occurred between the stages connected by the link. For example, a wire message could not be translated into a business message.
                              • Yellow: Waiting for some corrective action to occur so that processing can move from one stage to other stage of the link. For example, a business message which is in MSG_WAIT_TRANSMIT/MSG_PROCESS_ACK/MSG_WAIT_ACK/MSG_WAIT_FA state or a wire message which is in PROCESSING state.
                              • Green: Processing succeeded from one stage to other stage of the link.
                              • Gray: Stage at one or both ends of the link is not applicable. For example, an outgoing immediate ack for an incoming wire message will have all the links to the right of the wire message as gray since BM/AM are not generated for this situation.

                              MLLP2.0 is not generating exception messages in the back-end for NAK

                              1. Bug: 18386185
                              2. Added: 06-May-2014
                              3. Platform: All

                              MLLP2.0 is not generating the exception message in the back-end for NAK. This is a limitation of MLLP2.0.

                              MLLP2.0: Error description is not generated for NAK

                              1. Bug: 18386170
                              2. Added: 06-May-2014
                              3. Platform: All

                              In MLLP2.0, when healthcare receives a NAK, the message goes to the MSG_ERROR state, but the error description does not display in the business message reports. This is a limitation of MLLP2.0.

                              MLLP2.0: Re-submission of Outbound App Msg does not increment the RESUBMIT count

                              1. Bug: 18386154
                              2. Added: 06-May-2014
                              3. Platform: All

                              In MLLP2.0, when the outbound application message is re-submitted, the RESUBMIT count does not increment and remains as 0. This is a limitation of MLLP2.0.

                              MLLP2.0: Re-submit Inbound Wire Message does not increment the re-submit count beyond 1

                              1. Bug: 18386139
                              2. Added: 06-May-2014
                              3. Platform: All

                              In MLLP2.0, when the inbound wire message is re-submitted initially, the RESUBMIT count is shown as 1. When the same wire message is further re-submitted, the RESUBMIT count does not increment beyond 1. This is a limitation of MLLP2.0.

                              MLLP2.0: Custom block characters do not work

                              1. Bug: 18143528
                              2. Added: 06-May-2014
                              3. Platform: All

                              In MLLP2.0, the custom block characters for "Start Block", "End Block", and "Carriage Return" do not work.

                              • Start Block: Only the "Control" characters work but not the "Displayable" characters. If you use "Displayable" characters, you get a transport error and the message goes into MSG_WAIT_STACK state.
                              • End Block: Only the "Control" characters work but not the "Displayable" characters. If you use "Displayable" characters, you get a transport error and the message goes into MSG_WAIT_STACK state.
                              • Carriage Return: Healthcare ignores the custom block characters and always considers the default value: CR.

                              This is a known issue with MLPP2.0.

                              MLLP2.0: Transmission with Callout on receiver does not generate NAK

                              1. Bug: 18143515
                              2. Added: 06-May-2014
                              3. Platform: All

                              In MLLP 2.0 inbound with transport callout case, if callout generates any exception and Healthcare fails to commit the message to database, then Healthcare does not generate NAK.

                              NACK Feature is not supported in NIO mode

                              1. Bug: 17986068
                              2. Added: 06-May-2014
                              3. Platform: All

                              The MLLP endpoints can be made to run in NIO mode by setting the EM property b2b.nio=true. After setting this and restarting the server, the MLLP endpoints will start in NIO mode. This mode is helpful in thread handling and keeping the memory levels to optimal usage. However, once the NIO mode is enabled, the NACK feature for MLLP has issues and Healthcare does not support the same. Hence, if NACK feature is required for MLLP customers, then NIO mode should not be enabled.

                              Expand and Collapse for Nodes do not work with Keyboard in Screen Reader Mode

                              1. Bug: 17756279
                              2. Added: 06-May-2014
                              3. Platform: All

                              Expand and Collapse options for nodes do not work while using keyboard in Screen Reader mode.

                              Workaround:

                              Follow these steps to expand/collapse using keyboard:

                              1. Navigate to the required component using Tab key.
                              2. Press Enter to select the component.
                              3. Press Ctrl+Alt+M to launch the context menu.
                              4. Use the Up and Down arrows to navigate through the options in the context menu.

                              Healthcare UI is not HA Compliant

                              1. Bug: 18762886
                              2. Added: 20-May-2014
                              3. Platform: All
                              • Users see the following warning message:
                              • [APP: Healthcare UI] [DSID: 0000KMV6c1r7MAW5HzXBif1JMkLk000006] ADFc: This application is running in a cluster but High Availability (HA) mode is not enabled in the adf-config.xml file.
                              • Hence, the Healthcare UI is not HA compliant.

                              Re-submit count issue

                              1. Bug: 18810351
                              2. Added: 22-May-2014
                              3. Platform: All

                              When resubmitting Healthcare Outbound Application message from Healthcare UI, the Resubmit Count of the original message that was re-submitted does not increment.

                           4. This is a known issue.

                              Additional required properties for Healthcare Alert/Contacts in T2P Migration

                              1. Bug: 18896176
                              2. Added: 05-Jun-2014
                              3. Platform: All

                              For Healthcare Alert and Contacts migration, from Test environment to Production environment (T2P), users need to change Contact details along with other related properties after T2P process. See T2P User Guide for more information.

                              Unable to create SFTP endpoint in the HCFP console

                              1. Bug: 18911165
                              2. Added: 13-Jun-2014
                              3. Platform: All

                              While trying to create an SFTP endpoint in the Healthcare UI, the following error is thrown:

                              MDS-00001: exception in Metadata Services layer MDS-01607: The relationship from /soa/b2b/tp_MyCompany.xml#param0AF079411466105E5F80000024158591 to /soa/b2b/seed/protocol.xml#sftp-param-copy_Contents is invalid because type information is not available for the latter.

                              The issue will be addressed in the next SOA Bundle Patch that will be released on top of 12.1.3. If you need the fix urgently, contact Oracle Customer Support.

                              This is a known issue.

                              Managed File Transfer

                              Multibyte file name is garbled in transfer instance page

                              1. Bug: 24611740
                              2. Updated: 12-September-2016
                              3. Platform: All

                              Multibyte file name is garbled in the transfer instance page.

                              To avoid this, change the server encoding configuration to UTF-8 from the MFT user interface while designing the connection to SFTP Source/Target. Use Linux "locale charmap" to know local characterset and set the same in MFT.

                              MFT 12.1.3 to JDev 12.2.1 forward compatibility is not supported

                              1. Bug: 23306785
                              2. Updated: 19-May-2016
                              3. Platform: All

                              MFT 12.1.3 to JDev 12.2.1 forward compatibility is not supported.

                              Workaround: Enter the source name and endpoint URL in MFT Sevice Binding Discovery page in JDeveloper.

                              Designer Rename not supported after an artifact is deployed

                              1. Bug: 20374018
                              2. Updated: 20-January-2015
                              3. Platform: All

                              In the MFT Design page -> Designer tab, the Rename feature (Rename artifact command icon located in the left navigation pane) can be used to rename a Source, Target or Transfer after it is created, up to the point that it is deployed. However, Rename cannot be used after artifact deployment, and hence is grayed out once an artifact has been deployed one or more times.

                              IDEA and SAFER algorithms are not supported by MFT for PGP

                              1. Bug: 20091307
                              2. Updated: 24-November-2014
                              3. Platform: All

                              The IDEA and SAFER algorithms are not supported by MFT for PGP. The SAFER algorithm is not applicable for PGP symmetric keys.

                              APS Lists Folders in the "CurrentFolderPrivilege" Section That Are Not Present

                              1. Bug: 15919883
                              2. Updated: 19-March-2014
                              3. Platform: All

                              The Embedded Server User Access tab continues to show folders for which permissions were assigned even if the folders no longer exist in the file system.

                              Workaround: Manually remove the deleted folders from the Embedded Server User Access tab.

                              Target Instance Resubmit With Process and Deliver Option Is Not Present in Target Page

                              1. Bug: 16449241
                              2. Updated: 09-May-2014
                              3. Platform: All

                              The Resubmit button in the Target Report does not offer an option to process the file in addition to delivering it.

                              Workaround: Use the Resubmit button in the Transfer Report instead.

                              When Post Processing Executed, Post Processing Action Should Be Displayed

                              1. Bug: 16621042
                              2. Updated: 22-April-2014
                              3. Platform: All

                              When postprocessing is in progress at the target, no postprocessing details are displayed in the target report, and the flow diagram shows an error even though no error has occurred. The target report should show the postprocessing action with a status of "Processing" and no error in the flow diagram.

                              Workaround: None

                              Embedded (s)FTP Services Are Getting Started Even If Stopped Before Server Restart

                              1. Bug: 16685674
                              2. Updated: 09-May-2014
                              3. Platform: All

                              The embedded FTP and sFTP servers are services on the Oracle WebLogic Server managed server dedicated to MFT. If you stop the embedded servers, then restart the managed server, the embedded servers are restarted even though they are supposed to remain stopped until explicitly restarted.

                              Workaround: None

                              JDev Client Proxy Generation Issue: Create Java Web Service from WSDL

                              1. Bug: 16982653
                              2. Updated: 10-May-2014
                              3. Platform: All

                              JDeveloper client proxy generation from the MFT SOAP WSDLs MFTAnyTypeService.wsdl, MFTService.wsdl, and MFTSOAService.wsdl can fail with this JDeveloper error message:

                              [ERROR] Invalid wsdl:operation "submitInline": its a document-literal operation, message part must refer to a schema element declaration

                              Workaround: Make sure the WSDL file has a valid value for MFTServicePort.

                              There Is No Option to View the Scheduled Info In Case of Listening Sources

                              1. Bug: 17009023
                              2. Updated: 09-May-2014
                              3. Platform: All

                              Schedules for non-listening source types, such as FTP Embedded, and listening source types, such as File and FTP Remote, are handled differently. Non-listening types pick files immediately and show a status of Scheduled and schedule details on the Monitoring page. Listening types do not pick files or show schedule details on the Monitoring page until the schedule expires.

                              Workaround: None

                              MFT Accessibility - Click Event Is Not Appropriate on Admin Page

                              1. Bug: 17888359
                              2. Updated: 24-March-2014
                              3. Platform: All

                              When screen reader mode is enabled in Preferences, clicking an item in the left pane navigator is not sufficient to open the corresponding tab.

                              Workaround: Click the Select radio button for the item first, then click the item.

                              MFT Throwing Exception When Submit Inline Has Special Characters in Request

                              1. Bug: 18080753
                              2. Updated: 01-May-2014
                              3. Platform: All

                              If an inline payload has special characters such as angle brackets (< or >), the transfer fails with an error such as, "MFT message processing failed with exception code: MFT_WS_INBOUND_INVALID_SOAP_REQUEST."

                              Workaround: Pass these characters as CDATA or use escape characters.

                              MFT Accessibility - Use for This Session Option Is Missing for Accessibility

                              1. Bug: 18130140
                              2. Updated: 01-May-2014
                              3. Platform: All

                              The "Use for this session" accessibility option is not included in Preferences.

                              Workaround: You can access this option from the Accessibility link on the login page.

                              FTP Remote Source Is Not Picking the File in IPv6 Environment

                              1. Bug: 18226117
                              2. Updated: 21-February-2014
                              3. Platform: All

                              IPv6 is not supported for Remote FTP and Remote FTPS due to a limitation in the JCA FTP Adapter utilized by MFT.

                              Workaround: Remote sFTP supports IPv6.

                              All Cipher Suites in the FTP Configuration Page Should Be Selected by Default

                              1. Bug: 18344879
                              2. Updated: 04-March-2014
                              3. Platform: All

                              When no cipher suites are selected, it means all are available. All of them should be selected by default.

                              Workaround: None

                              Encrypt and Compress Actions Should Be Removed from B2B and HC Targets

                              1. Bug: 18386605
                              2. Updated: 12-March-2014
                              3. Platform: All

                              Encryption and compression actions should be removed from B2B and Healthcare targets, because B2B and Healthcare do not support encrypted or compressed messages.

                              Workaround: None

                              Stop-Start Embedded Server Error When Active Server Is Shut Down

                              1. Bug: 18401837
                              2. Updated: 21-March-2014
                              3. Platform: Windows Internet Explorer

                                 In the Embedded Server Ports tab, when you Stop the active server, clicking Start displays an error page.

                                 Workaround: Refresh the browser.

                                 No Response from SOA Causes Stuck Thread

                                 1. Bug: 18469258
                                 2. Updated: 29-March-2014
                                 3. Platform: All

                                 To prevent the target message delivery thread from getting stuck, the maxTargetHttpTimeout MBean property has been added, with a default value of 600000 milliseconds, equivalent to 10 minutes. If this timeout is exceeded, the MFT transfer fails.

                                 Workaround: You can change this timeout value in Oracle Enterprise Manager Fusion Middleware Control.

                                 1. Log in to the Fusion Middleware Control console.
                                 2. In the Target Navigation pane, expand the MFT node.
                                 3. Click the MFT server name, for example, mft-app (mft_server1).
                                 4. Click the More MFT Configuration Properties link.
                                 5. Click the Operations tab.
                                 6. Click the addProperty link.
                                 7. Type maxTargetHttpTimeout as the key and the desired number of milliseconds as the value.
                                 8. Click Invoke.

                                 MFT WSDLs Are Subject to Change in Future Releases

                                 1. Bug: 18506069
                                 2. Updated: 14-April-2014
                                 3. Platform: All

                                 MFT WSDLs are subject to change in future releases.

                                 Workaround: None

                                 Handling Event If JCA Adapter Deactivates Endpoint on Some Error

                                 1. Bug: 18604832
                                 2. Updated: 29-April-2014
                                 3. Platform: All

                                 If any error occurs during inbound operations and the JCA Adapter deactivates the endpoint, MFT should send a specific notification and update the artifact accordingly. In the current release, this is a generic runtime error.

                                 Workaround: None

                                 Expanded View File Finder Size Filter Is Not Working

                                 1. Bug: 18604861
                                 2. Updated: 16-April-2014
                                 3. Platform: All

                                 When you expand the File Finder view, the expanded view provides search fields for each column. The search field for the Size column does not work.

                                 Workaround: None

                                 FAX and Phone Notification Channels Shouldn't Be Allowed for Notification WLST Commands

                                 1. Bug: 18641735
                                 2. Updated: 23-April-2014
                                 3. Platform: All

                                 There is no server support for the FAX and PHONE notification channels in the current release. They are present for possible future support. Therefore, these options do not work for the contact_type parameter of the addContactToNotification, createContact, deleteContact, listContacts, and removeContactFromNotification commands.

                                 Workaround: None

                                 Restart All Button in Embedded Servers Tab Should Be Visible Only to Admin

                                 1. Bug: 18649086
                                 2. Updated: 23-April-2014
                                 3. Platform: All

                                 The Restart All button in the Embedded Servers tab should be visible only to users with the MFTAdmin role in the Administrators group.

                                 Workaround: None

                                 The Web Service Test Page URL Cannot Be Visited in Production Mode

                                 1. Bug: 18661443
                                 2. Updated: 14-May-2014
                                 3. Platform: All

                                 On a development system, when you create a web-service-based source of type SOAP, SOA, Service Bus, or ODI, an icon to the right of the URL field becomes active after deployment. Clicking this icon opens a web service test page in a new browser tab so you can verify the source URL.

                                 However, on a production system, clicking a source test page icon may result in an error, even if the URL is valid.

                                 Workaround: On a production system, the web service test page is disabled by default. To enable it:

                                 1. Log in to the Oracle WebLogic Server console.
                                 2. In the Domain Structure pane, click the name of the domain in which MFT is installed, for example, soainfra.
                                 3. Verify that the Production Mode setting is checked.
                                 4. Click Advanced at the bottom of the page.
                                 5. Check the Enable Web Service Test Page setting.
                                 6. Click Save.
                                 7. Restart the MFT and SOA managed servers.

                                 Monitoring Expanded Finders: Date Format Search Issue

                                 1. Bug: 18708696
                                 2. Updated: 06-May-2014
                                 3. Platform: All

                                 The From and To fields in the File Finder and Recent Errors expanded views accept dates only, not times. For both these fields, the date format is mm/dd/yyyy and the time defaults to 00:00:00.

                                 Workaround: None

                                 Passing Parameters to MFT WLST Commands

                                 1. Bug: 18723065
                                 2. Updated: 12-May-2014
                                 3. Platform: All

                                 Some MFT WLST commands that appear to have correct syntax fail.

                                 Workaround: Use unnamed parameters in the standard parameter order.

                                 Supported (recommended as best practice): Name all the parameters. In this case, they can be passed in any order.

                                 Example: archiveInstanceData(archiveFileName="mft_runtime_archive.dmp", startDate="01-02-2013 00:00:00:00", endDate="31-03-2013 00:00:00:00", testMode="false")

                                 Supported (recommended as best practice): Pass unnamed parameters in the standard parameter order, as indicated in the help text and documentation.

                                 Example: archiveInstanceData("mft_runtime_archive.dmp", "01-02-2013 00:00:00:00", "31-03-2013 00:00:00:00", "false")

                                 Supported (advanced): Pass some unnamed parameters in order, and the rest named. Once a named parameter is used, all the parameters that follow must be named.

                                 Example: purgeInstanceData("01-02-2013 00:00:00:00", "31-03-2013 00:00:00:00", testMode="false", status="A,F")

                                 Incorrect Instances or Payloads Shown in Instance Archive

                                 1. Bug: 18742734
                                 2. Updated: 12-May-2014
                                 3. Platform: All

                                 If you use the archiveInstanceData MFT WLST command, then use the purgeInstanceData command with the same batch ID, then repeat the archiveInstanceData command with the same batch ID and testMode=true, the archiveInstanceData output should tell you that there is nothing to archive. Instead, the output is as if the purge had never taken place.

                                 Workaround: Do not repeat the same command using the same batch ID. If you repeat the same command with the same parameters but no batch ID, the command works correctly.

                                 MFT Server Cannot Be Started When Changed from Development Mode to Production Mode

                                 1. Bug: 18789100
                                 2. Updated: 19-May-2014
                                 3. Platform: All

                                 The MFT and SOA managed servers fail to start after being changed to production mode. The error message looks like this:

                                 Server mft_server1 is configured with localhost as the Unicast Listen Address which is an error in Coherence Production mode. A generated Coherence WKA list will not operate correctly across multiple machines.

                                 Workaround: The MFT and SOA managed servers cannot start up in production mode without a listen address. To check for a listen address and restart the servers:

                                 1. In the Domain Structure pane, under the name of the domain in which MFT is installed, expand the Environment node.
                                 2. Under the Environment node, click Servers.
                                 3. In the Servers table, click the MFT server, for example, mft_server1.
                                 4. If the Listen Address setting is blank, enter a value. Using "localhost" does not work. You must enter the actual IP address or hostname of the MFT managed server.
                                 5. Click Save.
                                 6. Click the Control tab and the Start/Stop subtab.
                                 7. Above the Server Status table, click Shutdown and choose an option: When Work Completes or Force Shutdown Now.
                                 8. After shutdown completes, click Start.
                                 9. Repeat these steps for the SOA server, for example, soa_server1.

                                 Monitoring Nav Tree May Not Show All Deployed Artifacts

                                 1. Bug: 18894404
                                 2. Updated: 05-June-2014
                                 3. Platform: All

                                 The left pane navigator on the Monitoring page may not show all deployed artifacts.

                                 Workaround: Find the deployed artifact using the navigator filter, or use a filter in the main dashboard or the dashboard for all transfers, sources, or targets.

                                 Missing Step in MFT User's Guide for Adding JMS Error Queues

                                 1. Bug: 19003005
                                 2. Updated: 17-June-2014
                                 3. Platform: All

                                 In Section 6.8, "Configuring Oracle Managed File Transfer Error Queues," in Using Oracle Managed File Transfer, a step is missing from the procedure. Between steps 13 and 14, this step needs to be

                              4. Added:

                                 Select Redirect from the Expiration Policy drop-down list.

                                 Workaround: None

                                 MFT Logging Doesn't Work When MFT and SOA Are Installed in the Same Domain

                                 1. Bug: 19236873
                                 2. Updated: 21-August-2014
                                 3. Platform: All

                                 When MFT and SOA are installed in the same domain, "mft" is missing from the file name of the MFT diagnostic log. The log file is named server-name-diagnostic.log instead of server-name-mft-diagnostic.log.

                                 Workaround: None

                                 Recommendations When Using Append Mode

                                 1. Bug: 19267246
                                 2. Updated: 22-July-2014
                                 3. Platform: All

                                 The Append option, under Advanced properties for targets, appends newly transferred files to previously transferred files of the same name. When using this option:

                                 • Set the Retry Count to zero.
                                 • Don't pause and resume the transfer.
                                 • Don't resubmit the transfer.

                                 Workaround: None

                                 Need Connection URL Example in MFT Managing Domains Section

                                 1. Bug: 19331022
                                 2. Updated: 31-July-2014
                                 3. Platform: All

                                 In Using Oracle Managed File Transfer, Section 4.2, "Managing Domains," an example is needed for the Connection URL, such as:

                                 t3://host:port

                                 Workaround: None

                                 Oracle API Catalog

                                 Users with the Curator role cannot run the Oracle API Catalog Harvester

                                 1. Bug: No bug number
                                 2. Updated: 27-July-2015
                                 3. Platform: All

                                 The documentation states that users with the curator role can run the harvester to create new API assets in Oracle API Catalog. This is not supported. Only users with the Admin role can run the harvester to create new API assets in Oracle API Catalog.

                                 Resource Properties Displays Wrong Type

                                 1. Bug: 19808038
                                 2. Added: 31-October-2014
                                 3. Platform: All

                                 When viewing the properties for an Oracle API Catalog Connection in the Oracle Enterprise Repository JDeveloper Plugin, Oracle Enterprise Repository is selected as default instead of Oracle Enterprise Repository.

                                 This is a known issue for this release.

                                 Cannot Extend a SOA Domain for Oracle API Catalog

                                 1. No bug number
                                 2. Added: 31-October-2014
                                 3. Platform: All

                                 When running the Domain Configuration Wizard, it is not possible to extend an existing Oracle SOA Suite domain for use with Oracle API Catalog. You must create a new domain for Oracle API Catalog.

                                 This is a known issue for this release.

                                 Oracle API Manager

                                 Issues Displaying Online Help Content

                                 1. Bug: 20225372
                                 2. Added: 16-February-2015
                                 3. Platform: All

                                 The frame that displays online help content is small, making it difficult to read online help content included with the 12.1.3 release of Oracle API Manager

                                 This also causes the results from the search pane to be hidden.

                                 These are known issues for this release.

                                 API Description Tool Tip Displays ???apis.list.desc??? on Analytics Page

                                 1. Bug: 20449403
                                 2. Added: 16-February-2015
                                 3. Platform: All

                                 The tool tip displays ???apis.list.desc??? when hovering over an API on the Analytics page in the Oracle API Manager Portal.

                                 This is a known issue for this release.

                                 Pie Chart Displays Different Ratio of Failed to Successful Messages on the Analytics Page than Oracle Enterprise Manager

                                 1. Bug: 20449373
                                 2. Added: 16-February-2015
                                 3. Platform: All

                                 The pie chart on the Analytics page displays the ratio of successful messages to failed messages. This ratio is displayed incorrectly. For instance, if two messages are sent and both return errors, the pie chart displays two failed messages and two successful messages, showing a 50% failure rate instead of a 100% failure rate, as displayed in Oracle Enterprise Manager.

                                 This ratio is calculated correctly in Oracle Enterprise Manager.

                                 This is a known issue for this release.

                                 Analytics and API Detail Pages Display Aggregation Interval Only in Minutes

                                 1. Bug: 20450422
                                 2. Added: 16-February-2015
                                 3. Platform: All

                                 The Analytics page and API Detail pages display the aggregation interval only in minutes. These aggregation intervals are displayed in Oracle Enterprise Manager in Days, Hours, and Minutes, as appropriate. For example, if the aggregation interval is set as one week in Oracle Enterprise Manager, the aggregation interval is displayed in the Oracle API Manager Portal as 10080 minutes.

                                 This is a known issue for this release.

                                 API Consumer and API Admin Users May Not Be Able to View Analytics Data in the Oracle API Manager Portal Deployed in a Clustered Domain Configuration

                                 1. Bug: 20443511
                                 2. Added: 16-February-2015
                                 3. Platform: All

                                 In a clustered domain configuration, users with the API Consumer or API Admin roles may not be able to view analytics on the Analytics or API Detail pages. In this instance users with WebLogic Server Administrative privileges can view analytics data on Analytics and API Detail pages.

                                 This is a known issue for this release.

                                 Key Enforcement Issues if API Status is Changed when Managed Server is Down in a Clustered Environment

                                 1. Bug: 20465234
                                 2. Added: 16-February-2015
                                 3. Platform: All

                                 If an API Curator updates the status of an API (for instance, from Draft to a Published, Unmanaged API) when a managed server in a clustered environment is down, requests sent to this API are processed as if the API still had the previous status. For example, if an API status is changed from Draft to Published and Unmanaged when a managed server is down, users may receive a 403 Forbidden response for requests processed by that API, even though the API should be processing requests normally.

                                 This is a known issue for this release.

                                 Proxy Service Throws Runtime Exception if Not REST or WSDL-SOAP Type

                                 1. Bug: 20449386
                                 2. Added: 16-February-2015
                                 3. Platform: All

                                 Invocation of proxy services not of REST or WSDL-SOAP type exposed as APIs results in a 500 Internal Server error. The server log displays an exception similar to the following:

                                 Copy

                                 
                                 
                                         <Error> <HTTP> <BEA-101020> [ServletContext@705049964[app:Service Bus Kernel module:/default/anysoapproxy 
                                 path:null spec-version:3.0]] Servlet failed with an Exception oracle.apimanager.runtime.APIConfigException: 
                                  API ID [QVBJTWFuYWdlcg.ZGVmYXVsdC9hbnlzb2FwcHJveHk] not found at oracle.apimanager.internal.subscription.
                                  persistence.PersistenceController. getApiIdVisibility (PersistenceController.java:391) 
                                  at oracle.apimanager.internal.runtime.APIConfigManagerServerImpl.
                                 getVisibility(APIConfigManagerServerImpl.java:26) at oracle.apimanager.internal.runtime.InvocationHandlerImpl.
                                 onRequest(InvocationHandlerImpl.java:71) at oracle.apimanager.internal.runtime.InvocationServletFilter.
                                 doFilter(InvocationServletFilter.java:110) at oracle.apimanager.internal.runtime.InvocationServletFilter.
                                 doFilter(InvocationServletFilter.java:88) Truncated. See log file for complete stacktrace.
                                 
                                 

                                 This is a known issue for this release.

                                 Stream Explorer

                                 Can't Get Event Type of Complex Element to Create EDN Stream

                                 1. Bug ID: 20700113
                                 2. Added: 3-March-2015
                                 3. Platforms: All

                                 Creating a stream with EDN as a source has a few limitations. The other EDN types are not visible for selection. In this release:

                                 1. Only the XML element that has a flat structure is supported.
                                 2. The XML schema does not import other schemas.

                                 Column Values will be Invalid Date if Column's Type is Date in DB

                                 1. Bug ID: 20481257
                                 2. Added: 24-February-2015
                                 3. Platforms: All

                                 The values in the columns for which the type is defined as DATE in the database, are displayed as invalid in Stream Explorer.

                                 Can't see some previously created Event Shapes

                                 1. Bug ID: 20477830
                                 2. Added: 24-February-2015
                                 3. Platforms: All

                                 Event shapes created for stream types other than CSV do not persist in Stream Explorer.

                                 Can't register Event Type whose property name is in Uppercase in REST Stream

                                 1. Bug ID: 20467915
                                 2. Added: 24-February-2015
                                 3. Platforms: All

                                 Uppercase is supported only for application/json content type and not for CSV content type. This is a limitation specifically with REST Stream.

                                 Publishing Exploration with CSV Target Failed

                                 1. Bug ID: 20459026
                                 2. Added: 24-February-2015
                                 3. Platforms: UNIX/Linux

                                 When you publish an exploration that has a CSV File as a target, the publishing fails. This is because the corresponding folder is not generated for the target.

                                 Workaround: Create any CSV Source with the uploaded file.

                                 Error pops up after changing the Stream's Shape for an Exploration

                                 1. Bug ID: 20460312
                                 2. Added: 24-February-2015
                                 3. Platforms: All

                                 An error pops up when a stream's shape name is changed. This is a dependency related limitation.

                                 Can't Deploy Application with CSV-Inbound Adapter Exported by Another User/

                                 1. Bug ID: 20460049
                                 2. Added: 24-February-2015
                                 3. Platforms: All

                                 When you try to deploy an exploration exported by another user, it fails. This is a limitation in FileStorage.

                                 AIA Foundation Pack

                                 CCI Fails in Windows

                                 1. Bug ID: 18894575
                                 2. Added: 18-March-2017
                                 3. Platforms: All

                                 CCI MATS and CCI fails in a Windows Environment.

                                 Workaround:

                                 In cci.bat file, search for %args% string and replace it with %*.