Seperate DB Update not working at the end of transaction after polling DB

Question

I am using DB Adapters in OSB(built using JDveloper) to poll a DB. I am doing logical delete on one of the field(PROC_RSLT) on table by updating read column to 0.
The issue is after I have done the polling and send the polled data to external party, external party send me a response which I have to again update to PROC_RSLT field.
1. This update is not working if my JCA adapter proxy service having "transaction" and "Same Transaction For Response " options are disabled.
2. When I enable the "Same Transaction For Response" option my DB update after external system with external system response is possible but logical delete(update to 0) on PROC_RSLT happen only after transaction is completed.
Since PROC_RSLT is not updated to 0 same record is polled by adapter multiple times. I want my PROC_RSLT to be updated as soon as it poll and also my DB update to happen with external system response
Can anyone help?
Thanks

Answer 1

Please refer section "Update a Field in the [Table_Name] Table (Logical Delete)" at below link -
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10231/adptr_db.htm#BABEEBIH
Database Configuration: A status column on the table being polled must exist. If it does not exist already, you can add one to an existing table.
Support for Polling for Updates: Given that rows are not deleted with each read, it is possible to repetitively read a row multiple times. You must add a trigger to reset the mark read field whenever a record is changed, as follows:
create trigger Employee_modified
before update on Employee
for each row
begin
:new.STATUS := 'MODIFIED';
end;
Support for Concurrent Access Polling: Just as a single instance should never process an event more than once, the same applies to a collection of instances. Therefore, before processing a record, an instance must reserve that record with a unique value. Again, the status column can be used:
<operation name="receive">
<jca:operation
ActivationSpec="oracle.tip.adapter.db.DBActivationSpec"
PollingStrategyName="LogicalDeletePollingStrategy"
MarkReadField="STATUS"
MarkUnreadValue="UNPROCESSED"
MarkReservedValue="RESERVED${IP-2}-${weblogic.Name-1}-${instance}"
MarkReadValue="PROCESSED"
The polling query instead appears, as shown in the following example:
Update EMPLOYE set STATUS = 'RESERVED65-1-1' where (CRITERIA) AND (STATUS = 'UNPROCESSED');
Select … from EMPLOYEE where (CRITERIA) AND (STATUS = 'RESERVED65-1-1');
The after-read UPDATE is faster because it can update all:
Update EMPLOYEE set STATUS = 'PROCESSED' where (CRITERIA) AND (STATUS = 'RESERVED65-1-1');Your second aaproach should work -
2. With option ”Same transaction for Response” Enabled : PROC_RSLT is not updated to 0 as soon as record is polled. Instead it is updated to resultcode from CSM at the end of transaction. By that time DB adapter poll for multiple times as PROC_RSLT is still considered unread(not 0).Regards,
Anuj