This document lists issues and workarounds specific to Oracle SOA and BPM Suite 11g Release 1 (188.8.131.52.0) Feature Pack.
For known issues and workarounds that apply to Oracle SOA and BPM Suite 11g Release 1 (184.108.40.206.0) see, Known Issues for Oracle SOA Products and Oracle AIA Foundation Pack for 11g Release 1 (220.127.116.11.0).
For known issues and workarounds for any other Oracle SOA and BPM Suite releases, see Known Issues for Oracle SOA Products and AIA Foundation Pack.
On this page: (Last updated: 14-September-2011)
If issue 12904895 occurs, the Outbound Dispatcher Count and Inbound Dispatcher Count properties might be set to 0 (zero). With these properties set to 0, all sequenced messages go into a waiting state. This occurs because the default value for the two properties was 0 in previous releases, but is now 1 in release 18.104.22.168 Feature Pack.
Workaround: If the dispatch count values are set to 0, you need to update the values to 1. If you perform the steps in issue 12904895, verify that the Outbound Dispatcher Count and Inbound Dispatcher Count properties are set to 1 on the healthcare integration user interface. Otherwise, perform the following steps to update the properties in the Oracle B2B Console.
In a Web browser, launch the Oracle B2B Console using the following URL:
In the upper right, click Administration, and then click the Configuration tab.
In the Miscellaneous (continued) section, change the value of the Outbound Dispatcher Count and Inbound Dispatcher Count properties to 1.
Click Save and then click OK.
When trying to import a big block of healthcare metadata, such as endpoints to an already-existing large metadata, you may encounter the Stackoverflow exception.
For example, if you try to to import 200 new endpoints to an existing set of 600 endpoints, you may encounter the exception.
Workaround: You need to add the following JVM argument in the setSOADomainEnv.sh file located at $DOMAIN_HOME/bin:
PORT_MEM_ARGS="-Xss512k -Xms768m -Xmx1536m"
The runtime settings might not appear on the Administration → Settings → Runtime page of the healthcare integration user interface.
Workaround: If the runtime settings do not appear, follow the steps below to export the repository data, purge design-time data, and reimport the repository data.
Launch the healthcare integration user interface in a web browser. The URL is
Under the Designer tab, click the Administration sub-tab and then double-click Repository Management.
Click Export and then click Continue on the dialog that appears.
Save the file to a temporary directory.
Click Purge Design Metadata.Note: If you have any enabled endpoints, you need to disable them before you can purge the metadata.
In the Import section, browse to and select the file you exported in steps 3 and 4 above, and then click Import.
When you create a mapset using the Oracle B2B Console, those mapsets also appear and can be edited on the healthcare integration user interface. This include mapsets for messaging types that are not valid in the healthcare integration user interface (such as HIPAA). These mapsets can be viewed, but should not be modified, from the healthcare integration user interface.
When you create a map EMS file for mapping between a source and a target HL7 documents by using the Oracle SOA Suite for healthcare integration user interface, the GuidelineInfo section of the map file contains only the message type (such as ADT) information. It does not capture information regarding the trigger event, such as A01. This creates a mismatch in the display of the document type in the healthcare integration user interface, because the DocType is set as ADT and not ADT_A01. So, a correct map file that is uploaded using the user interface will not automatically detect the source and target document definitions used in the map file. If there is no available ADT document, then the definitions will not get preselected in the user interface. Even if an ADT document is available, then the document type ADT will be selected and not the ADT_A01 as expected.
Workaround: You need to apply a hotfix after installing the Oracle Document Editor that is bundled with the Oracle SOA Suite for healthcare integration Feature Pack release. You can download the hotfix from support.oracle.com under the patch number 12797702.
Please note that because Oracle Document Editor is available only for the Windows platform, the hotfix is only applicable on the Windows platform.
When you create an internal delivery channel using the Send to Internal function, you cannot specify that queue as the exception queue in the runtime settings. The queue does not appear in the drop-down list of options for the exception queue.
Workaround: Log out of the healthcare integration user interface and then log back in again. The newly created queue appears in the drop-down list for the exception queue.
The reports on the healthcare integration user interface only display messages that have generated an associated business message. If an error occurs before a business message can be generated, then the message does not appear in the reports.
When the maximum number of dynamic tabs are open in Dashboard or Reports tab, then you cannot open any more new dynamic tabs. The maximum number of dynamic tabs that can be opened at a time is 15.
Workaround: Close tabs to be able to open new ones.
The JDeveloper Online Help is not being updated for the FP release. There are multiple UI components that do not have help topics. Also, some topics may have content that is out-of-date.
All new functionality included in the BPM JDeveloper Extension is documented in the Feature Pack update to the Oracle Fusion Middleware Modeling and Implementation Guide for Business Process Management 11g R1 (22.214.171.124.0).
When you click the Help button on the Decision Function Test dialog box, the help text does not appear. This is a known limitation, and the issue will be addressed in the subsequent patchset release.
Oracle SOA Composer enables you to define test variables that provide a way to shorten lengthy expressions that occur in rule and decision table conditions and actions. The variable and its value can be represented as an inline business term definition. The test variables are also called as inline aliases.
So, instead of writing:
some.very.long.expression > 4 and
some.very.long.expression < 10
You can write:
foo > 4 and foo < 10
In subsequent test conditions, you can use
foo as part of your expressions. The expression can be anything from a simple to a complex expression.
To define a variable, in the IF section of a rule, you need to click the down arrow adjacent to Insert Test, and select variable from the list.
Apart from variables, you can also define other test form types, such as simple test, nested tests (
(...)), and not nested tests (
Oracle Business Process Composer cannot import XPDL processes. Oracle BPM Studio can import XPDL processes.
Workaround: You can import XPDL processes using Oracle BPM Studio. You can save the project containing the imported processes to the BPM repository. These can then be opened using Oracle Business Process Composer.
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.
In Oracle SOA Composer, when using Oracle Business Rules test variables or inline aliases in rule and decision table conditions and actions, after you make changes to the variable names, the updated names do not appear in the decision table.
Workaround: In the decision table, do one of the following to force the decision table to redraw and display the updated variable names:
Adding or deleting a rule, condition or action will also cause the decision table to redraw and hence display the updated variable names.
In BPM Workspace, no matter how many workspace pages are created, all the information 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.
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.
When upgrading to a new version of Business Process Composer, you should clear the browser cach and restart your browser.
Even if the script task does not currently support arguments, the data association dialog shows arguments. Using these arguments does not have any effect, because the scrip task does not use them.
You cannot add a variable definition directly inside a nested block.
Workaround: The following are the workarounds for this issue: