By Greg Mally on Dec 10, 2012
So this blog will focus on BPM Swimlane roles and users from a ADF context.
So we have an ADF Task Details Form and we are in the process of making it richer and dynamic in functionality. A common requirement could be to dynamically show different areas based on the user logged into the workspace. Perhaps even we want to know even what swim-lane role the user belongs to.
It is is a little bit harder to achieve then one thinks unless you know the trick.
A large south-Asian insurance industry customer using Oracle BPM and SOA ran into this. I have survived this ordeal previously myself but didnt think to blog it then. However, it seems like a good idea to share this knowledge with this reader community and so here goes..
Symptom: A human task (in a SOA/BPEL/BPM process) completes automatically while it should have been assigned to a proper user.There are no stack traces, no related exceptions in the logs.
Why: The product is designed to treat human tasks that don't have assignees as one that is eligible for completion. And hence no warning/error messages are recorded in the logs.
Usecase variant: A variant of this usecase, where an assignee doesnt exist in the repository is treated as a recoverable error. One can find this in the 'pending recovery' instances in EM and reactivate the task by changing the assignees in the bpm workspace as a process owner /administrator.
But back to the usecase when tasks get completed automatically...
When: This happens when the users/groups assigned to a task are 'empty' or null. This has been seen only on tasks whose assignees are derived from an assignment expression - ie at runtime an XPath is used to determine who to assign the task to. (This should not happen if task assignees are populated via swim-lane roles.)
How to detect this in EM
For instances that are auto-completed thus, one will notice in the Audit Trail of such instances, that the 'outcome' of the task is empty. The 'acquired by' element will also show as empty/null.
Enabling the oracle.soa.services.workflow.* logger in em should print more verbose messages about this.
How to fix this
The application code needs two fixes:
input to HT: The XSLT/XPath used to set the task 'assignee' and the process itself should be enhanced to handle nulls better. For eg: if no-data-found, set assignees to alternate value, force default assignees etc.
output from HT: Additionally, in the application code, check that the 'outcome' of the HT is not-null. If null, route the task to be performed again after setting the assignee correctly. Beginning PS4FP, one should be able to use 'grab' to route back to the task to fire again.
Hope this helps.
In in earlier posting, I mentioned you can configure multiple threads of inbound (polling) adapters of Oracle SOA. However, the ways to configure multiple threads vary between adapters and product versions, and the information scatter cross multiple documentations. Hence it is worth to consolidate them here.Please read my blog Configure Oracle Adapter Threads in SOA 11G at BlogSpot for more details.[Read More]
Say you have a simple BPEL process that gets messages from JMS queue
through a JMSAdapter, transforms the message, and then calls a down
stream service via SOAP.
For such a simple BPEL process, are there any optimization that can be done for performance?
The answer is yes. And the low hanging fruits can be picked from layer between the inbound JMSAdapter and BPEL process.
Please read my blog Skipping an unnecessary step at BlogSpot to find out how to optimize the performance for this scenario.[Read More]
One of the nice capabilities of Oracle SOA Suite 11g is the ability to integrate with various packaged applications via Java EE Connector Architecture (JCA) adapters. These adapters include OracleAS Adapter for PeopleSoft, OracleAS Adapter for SAP R/3, OracleAS Adapter for Siebel, and OracleAS Adapter for J.D. Edwards OneWorld. Although the installation for the application adapters is well documented on the Oracle Fusion Middleware On-line Library, it is common to miss certain aspects of the installation ranging from missing .jar files to misconfiguration of the deployable adapter. When troubleshooting a misconfiguration, there are a common set of validation steps that must be conducted before venturing into more complex troubleshooting. The following will detail the common set of validation steps plus provide a utility that can be run from the command-line that will validate your installation.[Read More]
This is the blog for the Oracle FMW Architects team fondly known as the A-Team. The A-Team is the central, technical, outbound team as part of the FMW Development organization working with Oracle's largest and most important customers. We support Oracle Sales, Consulting and Support when deep technical and architectural help is needed from Oracle Development.
Primarily this blog is tailored for SOA issues (BPEL, OSB, BPM, Adapters, CEP, B2B, JCAP)that are encountered by our team. Expect real solutions to customer problems, encountered during customer engagements.
We will highlight best practices, workarounds, architectural discussions, and discuss topics that are relevant in the SOA technical space today.