XREF best practices in ESB cluster installation-OESB10.1.3.3

Question

Hi,
We are using Oracle ESB during last 2 years.
2 months ago I migrated our ESB installation to ESB Cluster in production (1 ESB DT, 1 ESB RT for polling
adapters, 2 ESB RT for further message processing).
We are using SOA Suite 10.1.3.3 with MLR#17 applied.
I faced a issue with XREF (populateXRefRow XPath function) in production system and need assistance.
All our ESB Processes contains next main parts:
1) Polling DB-adapter (or FTP-adapter, this didn't matter) that initiates a ESB process, routing service for that polling adapter
that asyncronously (!) invokes Requestor ABC level services (AIA terms);
2) Requestor ABC level-services perform XREF population and continues message
processing.
XREF population is doing with next steps:
we call lookupXRefRow XPath function, if value is not present in XREF, we doing
populateXRefRow call.
This logic is working fine when we are not using ESB cluster, but now step 2) (ReqABC level) is performed by different ESB servers
and frequently we faced unique constraint violation error on XREF_DATA
population (during populateXrefRow call).
ESB RT nodes using to balance load but transmitted data is intersected. For example, we are poll not documents but document details instead (polling table populated by Oracle Streams, there are no guarantee that document header receives earlier than document details, because our system is high loaded and we are using commit_serialization=none with parallelism at APPLY processes).
Each ESB RT instance can receive different rows of same document and xref population done at document header level.
My question is: what is best practices to work with XREF in ESB cluster installations?
May be other peoples faced with this issue and how this issue was resolved?
I know possible workarounds to accomplish this task: not call populateXRefRow function in XSLT, instead call PL/SQL procedure or function that working same but can ignore any exceptions.
This's solution not liked to me, but I dont know any other solutions.
Also I cannot not populate XREF because XREF actively used in inter-systems communication.

Answer 1

Hi,
We are using Oracle ESB during last 2 years.
2 months ago I migrated our ESB installation to ESB Cluster in production (1 ESB DT, 1 ESB RT for polling
adapters, 2 ESB RT for further message processing).
We are using SOA Suite 10.1.3.3 with MLR#17 applied.
I faced a issue with XREF (populateXRefRow XPath function) in production system and need assistance.
All our ESB Processes contains next main parts:
1) Polling DB-adapter (or FTP-adapter, this didn't matter) that initiates a ESB process, routing service for that polling adapter
that asyncronously (!) invokes Requestor ABC level services (AIA terms);
2) Requestor ABC level-services perform XREF population and continues message
processing.
XREF population is doing with next steps:
we call lookupXRefRow XPath function, if value is not present in XREF, we doing
populateXRefRow call.
This logic is working fine when we are not using ESB cluster, but now step 2) (ReqABC level) is performed by different ESB servers
and frequently we faced unique constraint violation error on XREF_DATA
population (during populateXrefRow call).
ESB RT nodes using to balance load but transmitted data is intersected. For example, we are poll not documents but document details instead (polling table populated by Oracle Streams, there are no guarantee that document header receives earlier than document details, because our system is high loaded and we are using commit_serialization=none with parallelism at APPLY processes).
Each ESB RT instance can receive different rows of same document and xref population done at document header level.
My question is: what is best practices to work with XREF in ESB cluster installations?
May be other peoples faced with this issue and how this issue was resolved?
I know possible workarounds to accomplish this task: not call populateXRefRow function in XSLT, instead call PL/SQL procedure or function that working same but can ignore any exceptions.
This's solution not liked to me, but I dont know any other solutions.
Also I cannot not populate XREF because XREF actively used in inter-systems communication.