Database adapter - commit transactions

Question

Hello everybody.
Is it possible with the BPEL Process Manager (Databas Adapter) to handle some f.e. INSERTS on a database (also with more then one adapter) only with on database connection and commit all INSERTS only at the end of the process?
So it is important that I use only one db-connection. I don't want to open a db-connection for every db-adapter I want to open (to do an Insert or sth else) .
Thx a lot

Answer 1

Hi Neil,
at the moment it is not possible to have the entire bpel process from db adapter receive to db adapter invoke inside a single jta/global transaction context. We are working on some ideas for next the release.
The best thing for now is to add exception handling to your business process and apply some compensation logic for the individual records which fail. I.e. if using the LogicalDeletePollingStrategy you could set the 'deleted' flag back to 'errored' for rows which are found to be invalid in the transform step and have a separate business process to deal with these.
You could also try a large maxRaiseSize setting. That way if you read 100 rows they will be raised as a single xml document. If the transform fails then no rows will be written to the target database. However the commit will still occur on the source database.
Finally, you could use a non-destructive polling strategy like the SequencingPollingStrategy or LogicalDeletePollingStrategy and a large maxRaiseSize. Your business process could look like this:
receive (non-destructive destroy)
transform
merge all rows - target db
delete all rows -source db
If the 'merge' operation is jta enabled then it will be rolled back if either the transform or the delete fails.
This above idea is like a two stage polling strategy. First the rows are marked as being processed by the receive, but only when they arrive at the target db are they marked a final time as being completed or deleted completely.
Let us know if you need help implementing these ideas. To jta enable the merge see the recent thread 'oc4j-ra and data-sources.xml'.
Thanks
Steve