Fault handling in osb using publish

Hi all,
i am new to OSB, every thing is working fine. i will explain how we design the basically we have inbound and outbound. call inbound as 'aaaa' and outbound as "bbbb". we have created the proxy and BS which will communicate with EBS, BAM and B2B. i have created BS for all the three. from PS i used 2 assign and 1 publish activity. we are publishing directly to BS correspondingly. since i am not using any route activity i could not get the error back or any invocation error messages. can any one tell how to capture the error and place it into BAM report. we can transform data to BAM we just need to get the details about the fault handling in OSB.
thanks ----

Hi prabu,
thanks for your response.
As we have the discussion on this issue for quit a long time. i have configure the error handler in the proxy services when my EBS throws the error. error handler come active and some data is published to bam. here i got the problem is that, the PO which we are sending is one way or fire and forget when using Publish action. when the PO hit the EBS, i.e. when error message is passed through the test XML, error is occuring and and reporting to bam with some null values. i need to capture the data processed at that transaction. is it possible to capture the data in error handler which is errored out in message flow of PS.
can you please help me
thanks--
anil

Similar Messages

Best practice of OSB logging Report handling or java code using publish

Hi all,
I want to do common error handling of OSB I did two implementations as below just want to know which one is the best practice.
1. By using the custom report handler --> When ever we want to log we will use the report action of OSB which will call the Custom java class which
Will log the data in to DB.
2. By using plain java class --> creating a java class publish to the proxy which will call this java class and do the logging.
Which is the best practice and pros and cons.
Thanks
Phani

Hi Anuj,
Thanks for the links, they have been helpful.
I understand now that OSR is only meant to contain only Proxy services. The synch facility is between OSR and OSB so that in case when you are not using OER, you can publish Proxy services to OSR from OSB. What I didn't understand was why there was a option to publish a Proxy service back to OSB and why it ended up as a Business service. From the link you provided, it mentioned that this case is for multi-domain OSBs, where one OSB wants to use the other OSB's service. It is clear now.
Some more questions:
1) In the design-time, in OER no Endpoints are generated for Proxy services. Then how do we publish our design-time services to OSR for testing purposes? What is the correct way of doing this?
Thanks,
Umar

Fault Handling Issue in OSB

Hi,
This is regarding SOAP fault handling in OSB11g.
i am expecting that whenever OSB proxy service recieves a fault response the flow should move to service error handler if any. But its not happening.
We tested our service with SOA Test stubs and SOAP UI mock services. When SOA test stub send fault response OSB considering it as normal response. But when the same fault is sent by SOAP UI mock service OSB is considering it as fault and going to service error handler.
Now the same is happening when we replaced the service provider with one of the .NET service. The fault response is in SOAP 1.1 structure.
Please let me whats the difference or any setting or HTTP response code we need to look at.
Thanks & Regards
Siva

Hi Anuj,
I am using the same fault structure which is working in Soap UI mock service. Still its not working in Soa test stub. And now facing the same issue when fault comes from .NET based service provider.
Will verify once to see whats the response code thats being sent.
Thanks
Siva

Using Fault handling framework for executing Database procedure

We have a requirement wereby we have API to be executed on Oracle DB which would return a code saying 0 or 1.
I meaning error.
Now with regards to exception handling we require that we receive remote fault we retry for 3 times & if not successful have a email sent out & a human intervention.
This can be easily taken care by having define this in Fault polciy.xml
Another requirement is when the API fails for some reason & we get returncode as 1.Now we would like ot invoke the same policy for this type of error.Although BPEL instance is not failed.But we can throw custom fault.
Now the APi's that we have can be called in 3 ways.
1.In each instance we call API exactly once
2.In each instance we call API in a loop for each record in message.Hence if 10 records are there in message & while executin 7th time it failed then how to handle reminaing records?
3.In each instance we call API only once but submit all 10 reocrds at once.And at same time 7th record fails then whats best way to handle this?
We realy want to use fault handling mechanism because it gives a lot of options of replay rethroew continue...but given the requirement can somebody point out a right way of using fault policy?
Thanks

U can archive the records in archive tables once the database adapter polls the data.
-Ramana.

Fault handling using BPEL

Good, I'm working on a research project and I have been assigned the task of processing errors in SOAP BPEL.
I've been searching on Internet and the most commonly methodology used is soap-fault with throwing and catching exceptions in BPEL process.
I wonder if I can do it in a more proactive and comprehensive way, catching those exceptions through a web service, and if possible, how can the BPEL process send the information encapsulated in the soap-fault to the web service?
If there is another way of treating errors or someone can suggest me another way, I would be very grateful.

I am not clear on your objective, but in so far as BPEL SE Component of Open-ESB Project, running on JBI is concerned you can read more about Fault handling and other features of BPELSE here at http://wiki.open-esb.java.net/Wiki.jsp?page=BPELSE. Also, you can find some working examples on this page http://wiki.open-esb.java.net/Wiki.jsp?page=HowToDo
- Malkit

[svn:fx-trunk] 15021: merge 15020: update ASDoc for execute() to use FaultEvent instead of ErrorMessage in the fault handler

Revision: 15021
Revision: 15021
Author:   [email protected]
Date:     2010-03-25 07:35:43 -0700 (Thu, 25 Mar 2010)
Log Message:
merge 15020: update ASDoc for execute() to use FaultEvent instead of ErrorMessage in the fault handler
QE notes:
Doc notes:
Bugs:
Reviewer:
Tests run: checkintests
Is noteworthy for integration:
Modified Paths:
    flex/sdk/trunk/frameworks/projects/datavisualization/src/mx/olap/IOLAPCube.as

*bump* I desperately need to get this fixed for work - I hope someone can please find a solution or point me in the right direction!!

How to handle Asynchronous calls using OSB?

Hi There,
How to handle Asynchronous calls using OSB?
Please help me out??
-Venkat

Hello friend, here is what you need.
Oracle Service Bus, invoke asynchronous webservices | Oracle .. Java .. OpenSource .. SOA

Fault Handling in BPEL process

hi
We have to develop an application which involves several BPEL processes and proxy service(OSB) and JMS queue etc.
What is the difference between Fault Management Framework in SOA11g and normal fault handling(using catch and throw activities)?
which one we should prefer for fault handling in our application n why?
Plz help thanks in advance.

Hi-
In Normal Fault handling process, you will be able to catch the faluts only but in Fault Management Framework if a fault occurs the framework catches the fault and performs a user-specified action defined in a fault policy file associated with the activity. You can also have a human intervention prescribed in it, where you perform recovery actions from Enterprise Manager.
Pls go throgh the below post for detailed description
http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10224/bp_faults.htm
Fault Management Framework and non BPEL soap faults
Edited by: 333333 on Mar 23, 2011 5:01 PM

Fault handling from MDS is not working for messagerejection

Hi All,
I am sorry if i am asking simple things, but after trying i couldn't figure out the problem so i reached here.
In my project i am using file adapter in many places, so rejection handler is very important in finding out the missing files at the time of reading the file.So i created fault policies and bindings and i created simple process and placed the polices and binding files in the project, as expected it is working fine but if i referred the same files from my mds path rejection is not working.
here is my fault polices and binding files.
faultpolices.xml
<?xml version='1.0' encoding='UTF-8'?>
<faultPolicies version="2.0.1" xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<faultPolicy version="2.0.1" id="BpelFaultMechanism" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.oracle.com/bpel/faultpolicy" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:bindingFault">
<condition>
<action ref="retry-action"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:remoteFault">
<condition>
<action ref="retry-action"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:selectionFailure">
<condition>
<action ref="retry-action"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="retry-action">
<retry>
<retryCount>4</retryCount>
<retryInterval>2</retryInterval>
<retryFailureAction ref="rethrow-action"/>
</retry>
</Action>
<Action id="human-intervention-action">
<humanIntervention/>
</Action>
<Action id="abort-action">
<abort/>
</Action>
<Action id="replay-action">
<replayScope/>
</Action>
<Action id="rethrow-action">
<rethrowFault/>
</Action>
<Action id="ora-terminate">
<abort/>
</Action>
</Actions>
</faultPolicy>
<faultPolicy version="2.0.1" id="RejectedMessages">
<Conditions>
<faultName xmlns:rjm="http://schemas.oracle.com/sca/rejectedmessages" name="rjm:Messagerejection">
<condition>
<action ref="writeToFile"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="writeToFile">
<fileAction>
<location>/u01/textdata/SOADEV/rejection</location>
<fileName>Messagerejection_%ID%_%TIMESTAMP%.xml</fileName>
</fileAction>
</Action>
</Actions>
</faultPolicy>
</faultPolicies>
Note:-In the above xml fault policy BpelFaultMechanism is used in all composite for common remote and binding fault errors and this one is working fine from mds location.
Fault-Binding.xml
<?xml version='1.0' encoding='windows-1252'?>
<faultPolicyBindings version="2.0.1" xmlns="http://schemas.oracle.com/bpel/faultpolicy" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<composite faultPolicy="BpelFaultMechanism"/>
<service faultPolicy="RejectedMessages">
<name>Messagerejection</name>
</service>
</faultPolicyBindings>
Composite.xml
<?xml version="1.0" encoding="UTF-8" ?>

<composite name="Messagerejection"
revision="1.0"
label="2012-09-30_17-41-29_597"
mode="active"
state="on"
xmlns="http://xmlns.oracle.com/sca/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
xmlns:ui="http://xmlns.oracle.com/soa/designer/">
<import namespace="http://xmlns.oracle.com/pcbpel/adapter/file/Correlation/Messagerejection/Messagerejection"
location="Messagerejection.wsdl" importType="wsdl"/>
<service name="Messagerejection" ui:wsdlLocation="Messagerejection.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/pcbpel/adapter/file/Correlation/Messagerejection/Messagerejection#wsdl.interface(Read_ptt)"/>
<binding.jca config="Messagerejection_file.jca"/>
<property name="oracle.composite.faultPolicyFile">oramds:/apps/Faultpolicyfiles/fault_policies.xml</property>
<property name="oracle.composite.faultBindingFile">oramds:/apps/Faultpolicyfiles/fault_binding.xml</property>
</service>
<component name="Messagerejectionservice" version="1.1">
<implementation.bpel src="Messagerejectionservice.bpel"/>
<property name="bpel.config.oneWayDeliveryPolicy" type="xs:string"
many="false">async.cache</property>
</component>
<wire>
<source.uri>Messagerejection</source.uri>
<target.uri>Messagerejectionservice/Messagerejection</target.uri>
</wire>
</composite>
Also in some cases i am going with De-batching option,in which my xml file contains multiple record and publishing each record to the target service. In this case if any record has improper content then that particular record from should move to the custom folder.Please let me know how can i do this.
I hope some one will help me here.
Regards,
Tarak

Hi Kalyan,
Thanks for helping me here.
Now i am able to resolve the issue after restarting the server i place the properties of the files as below
<?xml version="1.0" encoding="UTF-8" ?>

<composite name="Messagerejection"
revision="1.0"
label="2012-09-30_17-41-29_597"
mode="active"
state="on"
xmlns="http://xmlns.oracle.com/sca/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
xmlns:ui="http://xmlns.oracle.com/soa/designer/">
<import namespace="http://xmlns.oracle.com/pcbpel/adapter/file/Correlation/Messagerejection/Messagerejection"
location="Messagerejection.wsdl" importType="wsdl"/>
<service name="Messagerejection" ui:wsdlLocation="Messagerejection.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/pcbpel/adapter/file/Correlation/Messagerejection/Messagerejection#wsdl.interface(Read_ptt)"/>
<binding.jca config="Messagerejection_file.jca"/>
</service>
<property name="oracle.composite.faultPolicyFile">oramds:/apps/Faultpolicyfiles/fault_policies.xml</property>
<property name="oracle.composite.faultBindingFile">oramds:/apps/Faultpolicyfiles/fault_binding.xml</property>
<component name="Messagerejectionservice" version="1.1">
<implementation.bpel src="Messagerejectionservice.bpel"/>
<property name="bpel.config.oneWayDeliveryPolicy" type="xs:string"
many="false">async.cache</property>
</component>
<wire>
<source.uri>Messagerejection</source.uri>
<target.uri>Messagerejectionservice/Messagerejection</target.uri>
</wire>
</composite>
Regards,
Tarak

What are the different approaches to do Fault Handling?

What are the different approaches to do Fault Handling?

for uplodig data to non sap we have 2 methodes
i) if u know bapi u will use lasm
2) bdc
but u mentioned so many records isthere
best thing is u will uplode all record sto al11 using XI interface
then u have to write bdc / lsmw program
beter to go for lsmw before that u will find bapi
if u will unable to find bapi
u have to create bapi and use it in lasmw
ofter that u have schedule the lsmw program as a bockground
then u have to create a job for it
and release from sm 37
then u have to moniter through bd87
if u want to go through i will help u.
if it is usefull to u pls give points
Saimedha

Clarification needed in the Fault Handling Framework(Error Hospital)

Hi,
I need some clarification on Fault Handling Framework...
Scenario:
My BPEL Process is Asynchronous.(10.1.3.3.1) and I tryed to invoke the another BPEL Process( which is used to select the Fname from the table using DB Adapter) . In the Main BPEL Process I have the Fault handling Framework and I done necessary changes in the bpel.xml. This is successfully working for Invoke Activity when ever an Remote or Binding Fault occurs in the Sub-BPEL Process and this Fault is send to Fault-Policy.xml in the server(bpel/domains/default/config/fault-Policy) and works accordingly to the action mentioned in the policy xml....( I have also made changes in the fault-bindings.xml ).
How ever this Framework is working fine for every actions.
Need Clarification:
1) Only the Binding and Remote faults will work for the Fault handling Framework.
2) can we use User defined faults (Buissness Faults,,,) for this........because I used the User defined faults to invoke the fault-policy.xml and it won't works....
3)Only Invoke Activity can be handled for this Framework or any Other Activity........
4)How to handle other Activity in the Fault-policy.xml...
5)Any difference for Asynchronous or Synchronous in this Fault Handling Framework.......
I also referred the Oracle SOA Suite New Feauters PDF .......
Can any one send me the related documents and try to help me on this.
Please help me on this.......
Thanks,
Ashok.

Hi Chintan,
You are saying that Custom faults are also supported for fault-Policy.xml.
I can't understand that 2nd answer you said. can you please explain how to use the Custom faults in the FaultHandlingFramework..
My Scenario:
I have 2 BPEL Process, BPEL1 will invoke the BPEL2 and if any remote fault or binding faults occurs in the BPEL 2 its returning the same fault to BPEL1 and here I am using FaulthandlingFramework , this fault send to fault-policy.xml and necessary action is took place succesfuly...(like retry, human intervention.....)
But when I throw some CustomFaults(userdefinedFaults)in the BPEL2 , its returning as a remotefault to BPEL1. I don't know how to use the customFaults in the Fault handling framework.......
Can you explain me in detail how to use custom faults in faulthandling framework...............
Send me some related documents for this.....

Custom fault message from OSB is not throw in BPEL

Hi,
I have created a custom fault error in OSB which is sent to BPEL.
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault>
</env:Fault>
</env:Body>
</env:Envelope>
If my namespace in FAULT tag is "http://schemas.xmlsoap.org/soap/envelope/",
message is understood as fault IN BPEL. But if I change namespace, BPEL understands as reply message.
How can I use my custom fault message with different namespace as http://schemas.xmlsoap.org/soap/envelope/ ?
Regards,

SOAP Fault has a defined structure and defined namespaces. It does provide a placeholder for custom data though. Just like you can not change the namespace of Envelope of Body, similarly you cant change the namespace of Fault(if you want it to be recognized by the client apps). Any custom data you want to send in the SOAP Fault needs to be set as a child of 'detail' element of SOAP Fault. This custom data can have any namespace you wish. This Custom XML will be the element you define as Fault element in your WSDL
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault>
<faultcode>env:Client</faultcode>
<faultstring>some error string</faultstring>
<faultactor>somedata</faultactor>
<detail>
{here you can put your custom XML content in any namespace which you have defined in the WSDL}
</detail>
</env:Fault>
</env:Body>
</env:Envelope>

Fault handling in DIServer Interact

Good Day Mentors,
I'm currently testing out how the DIServer works.
Now, I am testing Fault handling with the DI Server,
and would want to know if there is a way to get multiple Errors from an DI Server Interact call.
My test scenario was adding 2 Sales Orders into SAP via DI Server using the Interact Call(Not BatchInteract).
The actual SOAP call sent , with comments, is as below:
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Header>
<SessionID>5659CCC6-2E15-4664-BFA2-4E6A3BDD3E35</SessionID>
</env:Header>
<env:Body>
<dis:Add xmlns:dis="http://www.sap.com/SBO/DIS">
<Service>OrdersService</Service>
<Document>
<DocType>dDocument_Items</DocType>
<DocDate>2014-05-09</DocDate>
<DocDueDate>2014-05-10</DocDueDate>
<CardCode>C23900</CardCode>
<Comments>DI Server Test - ADD</Comments>
<DocumentLines>
<DocumentLine>
<ItemCode>A00003</ItemCode>
<Quantity>2</Quantity>
</DocumentLine>
<DocumentLine>
<ItemCode>TESTITTEM02</ItemCode> 
<Quantity>2</Quantity>
</DocumentLine>
</DocumentLines>
</Document>
</dis:Add>
<dis:Add xmlns:dis="http://www.sap.com/SBO/DIS">
<Service>OrdersService</Service>
<Document>
<DocType>dDocument_Service</DocType>
<DocDate>2014-05-09</DocDate>
<DocDueDate>2014-05-10</DocDueDate>
<CardCode>C20000</CardCode>
<Comments>DI Server Test - ADD</Comments>
<DocumentLines>
<DocumentLine>
<ItemDescription>Printer Servicing</ItemDescription>
<AccountCode>499999</AccountCode> 
</DocumentLine>
</DocumentLines>
</Document>
</dis:Add>
</env:Body>
</env:Envelope>
I commented the parts that should throw errors, which are the non existent ItemCode and AccountCode in 2 separate Sales Orders.
I was hoping to get a Fault Response from the DIServer which tells me that there are two error from 2 different Documents.
Basically, 2 separate error messages for the 1st Sales order(non existent Item Code) and 2nd Sales Order (Non Existent Account Code).
But the Fault Response I got from the DIServer was this:
<?xml version="1.0" ?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Body>
<env:Fault>
<env:Code>
<env:Value>env:Receiver</env:Value>
<env:Subcode>
<env:Value>-1</env:Value>
</env:Subcode>
</env:Code>
<env:Reason>
<env:Text xml:lang="en">Error in SOAP command 'Add'</env:Text>
</env:Reason>
<env:Detail>
<Command>Add</Command>
<SessionID>5659CCC6-2E15-4664-BFA2-4E6A3BDD3E35</SessionID>
</env:Detail>
</env:Fault>
</env:Body>
</env:Envelope>
The fault response only tells me that there is an error, but nothing specific to the documents. Just something specific to the actual SOAP call.
If I something is not clear, please do clarify with me.
I'm using SAP B1 9.0 PL05.
Thanks in advance!
Sean

Hi Sean,
I don't think there is such a feature available. This is standard behaviour in SBO - same for UI and DI API. The first problem/error found will abort the action and message is shown and in this case it is one action ( interact).
regards,
Maik

Fault handling in 11g - fault-bindings.xml for a partnerLink

I'm using 11g and I'm trying to use the fault handling framework for a specific partner link. In fault-bindings.xml I have:
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicyBindings version="2.0.1" xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<partnerLink faultPolicy="GetDateFaultPolicy">
<name>GetDateService</name>
</partnerLink>
</faultPolicyBindings>
I have a partner link named GetDateService in the bpel that I'd like to defin a policy for, but when I try to compile, I get:
Warning(3,58): Schema validation failed for fault-bindings.xml<Line 3, Column 58>: XML-24534: (Error) Element 'partnerLink' not expected.
Does the framework still allow partnerlinks granularity, it says it does in the docs?
Thanks

Maybe I should have looked at the new schema first.... : }
It's now reference:
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicyBindings version="2.0.1" xmlns="http://schemas.oracle.com/bpel/faultpolicy">
*<reference faultPolicy="GetDateFaultPolicy">*
<name>GetDateService</name>
*</reference>*
</faultPolicyBindings>
Edited by: Brutus35 on Sep 16, 2010 10:42 AM

11g: Help regarding fault handling framework

I am trying to implement a POC demonstrating the fault handling framework using fault policies. I am trying to handle remote and business faults. These faults are being thrown explicitly in the code. But I dont see the framework coming into picture. Here are the fault policies and fault bindings files
The POC does the following
1. If input is R, throws a remote fault.
2. If input is B1, throws a business fault. There is a catch defined for this. But as we also have a policy for this error, we expect the policy overrides the catch
3. If input is B2, throws a business fault. There is no catch defined for this. We expect the policy to handle this.
4. If any other input, we return a string.
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<faultPolicy version="2.0.1" id="ComponentFaults"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
name="bpelx:remoteFault">
<condition>
<action ref="ora-human-intervention"/>
</condition>
</faultName>
<faultName xmlns:ns1="NS_B1"
name="ns1:LP_B1">
<condition>
<action ref="ora-human-intervention"/>
</condition>
</faultName>
<faultName xmlns:ns2="NS_B2"
name="ns2:LP_B2">
<condition>
<action ref="ora-human-intervention"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="ora-human-intervention">
<humanIntervention/>
</Action>
</Actions>
</faultPolicy>
</faultPolicies>
Here is the fault-bindings.xml file
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicyBindings version="2.0.1"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<component faultPolicy="ComponentFaults">
<name>BPEL</name>
</component>
</faultPolicyBindings>

I created another bpel in the same composite that calls the original bpel. So now, those errros are supposed to travel to calling bpel.
Fault policies are coming into effect now. So, one part of the problem is solved, that atleast syntax and all is correct, and the fwk does work (!) but another one has opened - why is the fault not getting handled by the fwk if there is a single bpel that is throwing and not catching those faults.
Also, even in this new avatar, fault b1 is getting handled by the catch in BPEL process, while the fault policies are supposed to override any catches in bpel code.
What I was attempting was, throwing the fault in a bpel process and expecting the fault handling fwk to handle it.
It turns out, the framework is not capable of doing this, its only capable of handling faults coming after an invoke activity.
Consulted Oracle Support on this. Their response
The behavior within the single composite you are seeing is correct and is by design. As the documentation states:
http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10224/bp_faults.htm#BABIGGIB
If a fault occurs during runtime in an invoke activity in a process, the framework catches the fault and performs a user-specified action defined in a fault policy file associated with the activity.
The fault management framework catches all faults (business and runtime) for an invoke activity.
So the above means that unless the fault is thrown in response to an invoke activity the Fault Policy set will not be triggered, which has been confirmed through the test you have uploaded. Please let me know if you have any questions or concerns.

Fault handling in osb using publish

Similar Messages

Maybe you are looking for