Database Adapter configuration for resuability
509675Apr 16 2009 — edited Apr 19 2009Hi All,
I have scenario where I need to insert/update/select from the tables in database from more than one BPEL processes i.e one table can be accessed by several BPEL processes.
For that
1) one solution is to create adapters in all BPEL processes and use them. But it will have duplicacy i.e same adapter code at multiple places. And also in case of change in table structure (which is least expected), I will have to change adapters in all BPEL processes.
2) The other solution is to create adapters in and ESB and deploy them as ESB service and call them from BPEL by just giving wsdl url in partner link.
This works fine but the problem is that it doesn't throw fault if one-way database operations (insert,update) fail. My BPEL process continues even if the operations fails.
However it throws fault when something is wrong in two-way (select) operation. For ex. If I specify the column name which does not exist in database table, it throws fault and I am able to catch in catchAll in BPEL.
In case of 1) above where I have DB Adapters configured wihin process, I get the fault in BPEL and so I can catch and process accordingly.
I need to receive fault from adapters configured in ESB when insert or update fails. Is there any way to achieve this? Or is there any other way I can configure database adapters at one location and use at multiple places?
I use Oracle SOA version 10.1.3.4 MLR#6 and jdev 10.1.3.4.
- Sam