Mapping error code from Business service to Proxy

Question

I am trying to get hands on with 11g and following the book Getting started with Oralce 11G soa suite. The example I have described is based on chapter 11 and chapter 14. I have a proxy service and business service. The business service calls a "ValidateCC" composite which validates the credit card information passed and is proxied by the proxy service. The validation of CC is done by a stored procedure, which returns an error ora-20001 if the credit card info is not found in the database.
Testing PROXY service from OSB console:
Here is the REQUEST message sent to proxy service:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<soapenv:Body>
<cca:creditcardStatusRequest xmlns:cca="http://www.globalcompany.com/ns/CCAuthorizationService">
<cca:CCNumber>2234-1234-1234-1234</cca:CCNumber>
</cca:creditcardStatusRequest>
</soapenv:Body>
</soapenv:Envelope>
Here is the response message received:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>BEA-380001: Internal Server Error</faultstring>
<detail>
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380001</con:errorCode>
<con:reason>Internal Server Error</con:reason>
<con:location>
<con:node>RouteTo_validationForCC</con:node>
<con:path>response-pipeline</con:path>
</con:location>
</con:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Testing Business service from OSB console
Response received for the same message:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'validateCC' failed due to: Stored procedure invocation error.
Error while trying to prepare and execute the VALIDATECC API.
An error occurred while preparing and executing the VALIDATECC API. Cause: java.sql.SQLException: ORA-20001: UNKNOWN CREDIT CARD
ORA-06512: at "SOADEMO.VALIDATECC", line 12
ORA-06512: at line 1
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</faultstring>
<faultactor/>
<detail>
<exception>
ORA-20001: UNKNOWN CREDIT CARD
ORA-06512: at "SOADEMO.VALIDATECC", line 12
ORA-06512: at line 1
</exception>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
What i need:
I would like to have the exception 20001 populated in faultcode of the response from proxy message. A down stream BPEL process checks the faultcode and processes the message as needed.
My OSB message flow contains :
ValidateCredit +> envelope
PipelinePairNode1
Request Pipeline
Report and Validate
Response Pipeline
RouteTo_validationForCC
Service Error Handler
stage1 with Alert action.
My question is how to map the actual error occured in the cally be business service handler to the Service error handler in stead of throwing a generic BEA error. Please let me know

Answer 1

Thank You Swgt for your reply.
This is what I did:
When I'm in Edit mode, in the OSB Web Console, I go to my proxy service, click on the Edit Message Flow icon, in the Map of Message Flow window I left-click on my Route icon (which as you already mentioned routes to my Business Service), select Add Route Error Handler (this option only appears if you're in Edit Mode already), click on the Error Handler icon, Add Stage, click on the Stage icon, Edit Stage, click on Add an Action, Flow Control -> Reply. Here I select the Radio Button "With Failure" and then Save All and Activate the change for the session.
Is this correct?
I tried this. I no longer get the BEA-380001 error code. However, the fault returned is not a bindingFault as I would have expected, but rather a remoteFault. hence my fault policy never detects it, doesn't rethrow it, and my BPEL error handling never kicks in.
Is there a way to change this to work more or less in the sense of the tutorial?
Does using OSB to connect to the service automatically make it a remote fault, instead of a bindingFault?
Here's the SOAP message handled by my BPEL Component.
<messages>
<input>
<invokeCCStatusService_execute_InputVariable>
<part name="part1">
<creditcardStatusRequest>
<CCNumber>2234-1234-1234-1234</CCNumber>
</creditcardStatusRequest>
</part>
</invokeCCStatusService_execute_InputVariable>
</input>
<fault>
<bpelFault>
<faultType>0</faultType>
<remoteFault>
<part name="summary">
<summary>Beim Aufrufen des Bindings ist eine Exception aufgetreten.
Beim Aufrufen des JCA-Bindings ist eine Exception
aufgetreten: "JCA Binding execute of Reference operation
'validateCC' failed due to: Fehler beim Aufrufen von
gespeicherter Prozedur. Beim Versuch, die VALIDATECC-API
vorzubereiten und auszuführen, ist ein Fehler aufgetreten.
Beim Vorbereiten und Ausführen der VALIDATECC-API ist ein
Fehler aufgetreten. Ursache: java.sql.SQLException:
ORA-20001: UNKNOWN CREDIT CARD ORA-06512: in
"SOADEMO.VALIDATECC", Zeile 12 ORA-06512: in Zeile 1 Prüfen
Sie, ob die API in der Datenbank definiert ist und die
Parameter der API-Signatur entsprechen. Diese Exception wird
als nicht wiederholbar betrachtet. Sie ist wahrscheinlich auf
einen Modellierungsfehler zurückzuführen. Um den Fehler
stattdessen als wiederholbar zu klassifizieren, fügen Sie die
Eigenschaft nonRetriableErrorCodes mit dem Wert "-20001" zum
Deployment-Deskriptor hinzu (d.h. weblogic-ra.xml). Um einen
wiederholbaren Fault automatisch zu wiederholen, legen Sie
folgende Eigenschaften von composite.xml für diesen Aufruf
fest: jca.retry.interval, jca.retry.count und
jca.retry.backoff. Alle Eigenschaften sind Ganzzahlen. ". Der
aufgerufene JCA-Adapter hat eine Ressourcen-Exception
ausgelöst. Prüfen Sie die obige Fehlermeldung sorgfältig, um
eine Lösung zu finden.</summary>
</part>
<part name="detail">
<detail>
<exception>ORA-20001: UNKNOWN CREDIT CARD ORA-06512: in
"SOADEMO.VALIDATECC", Zeile 12 ORA-06512: in Zeile 1</exception>
</detail>
</part>
<part name="code">
<code>{http://schemas.xmlsoap.org/soap/envelope/}Server</code>
</part>
</remoteFault>
</bpelFault>
</fault>
<faultType>
<message>0</message>
</faultType>
</messages>