Académique Documents
Professionnel Documents
Culture Documents
OVERVIEW
This sample shows the three basic polling strategies or how to translate events
on the database into intiating instances of a BPEL or SOA process.
The simplest is selecting all possible rows inserted into a table, and afterwards
deleting them to guarantee they are only read once (DeletePollingStrategy).
Next simplest is updating a status column to insure they are only read once
(LogicalDeletePollingStrategy).
For the above reasons PollingStrategies are often called After Read Strategies.
However it is not just about what is done after the select. The third core strategy
assumes all new rows/events have an increasing key. So the select is for all
records with a key greater than the highest key previously processed
(LastReadId). This last highest key is stored in a helper table.
PROVIDED FILES
This sample contains the SOA Project that you can deploy along with the sql
scripts.
VERIFYING EXECUTION
• With adapter logging set to trace, you should see the polling SQL being
issued to the log files.
• After running the start script, go SELECT POLLING_STRATEGY FROM
MOVIES. It should correspond to the polling strategy that you started.
LOGICAL DELETE
• Hit next to the end and finish. For these core samples we will not discuss
any advanced options. However on the where clause page add a query
criteria:
Oracle SOA Suite 11g - Sample
• This way two polling strategy processes active at the same time won’t
interfere with each other. The end sql will look like (by going back to the
“Polling Options” page:
Oracle SOA Suite 11g - Sample
DELETE
• The alternate steps to modelling the delete are quite simple. Simply
choose “Delete the Row(s) that were Read” and hit next:
• You can reuse the outbound merge reference, but you will need to create
another Mediator component and transform.
LAST READ ID
Oracle SOA Suite 11g - Sample