How Standard Business Events Work With WF_BPEL_Q?
Last updated on MARCH 07, 2018
Applies to:Oracle Workflow - Version 18.104.22.168 to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.
Checked for relevance on 03-AUG-2013
How do standard Business events work with WF_BPEL_Q?
Problem Scenario :
When a standard business event is associated with a BPEL subscription is raised, it goes to WF_DEFERRED queue and then to the WF_ERROR queue with either of the following error messages:
1) "ORA-01403: no data found" .
2) "ORA-24033: no recipients for message
Wf_Event_QH.Enqueue(APPS.WF_BPEL_Q, SQL err is ORA-24033: no recipients for message)
Expected behavior is that the Event should be enqueued in the WF_BPEL_Q for further processing.
Expected Flow: The normal flow involved for Standard Business Events with BPEL is as follows :
a) User from Jdeveloper creates/configures an adapter as a partner link and selects the APPS event to listen
b) These are the background items
1. Create tables for queue named wf_bpel_q
2. Start wf_bpel_q
3. Create and start wf_bpel_qagent listener, which listens on wf_bpel_q.
4. Create subscription for the event for which the partner link was created
c) When the BPEL process is deployed in the BPEL PM, the listener keeps polling the WF_BPEL_Q with whatever frequency was defined.
d) Once the event is raised, it is enqueued into the WF_BPEL_Q and the listener (spawned by BPEL PM) which is listening to this event, would dequeue the item and start the BPEL process.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms