Mediator Exception Handling without fault policies

Hi,
Could somebody help me on defining exception handling to MEDIATOR component?
Is there is a way where we can do this without using the fault policies?
Thanks,
SV.

Business faults are application-specific and are explicitly defined in the service WSDL file. You can handle business faults by defining the fault handlers in Oracle JDeveloper at design time. System faults occur because of some problem in the underlying system such as a network not being available. Oracle Mediator provides fault policy-based error handling for system faults.http://docs.oracle.com/cd/E21764_01/integration.1111/e10224/med_faulthandling.htm
Regards,
Anuj

Similar Messages

EDN Mediator exception handling

Hi All,
I am subscrbing to business events through mediator.and then i am using the database adaptor to insert the data into a table.
I want to implement exception handling for the events.The delivery policies for event in mediator is guaranteed.Howver i still see the oracle text as The event is guaranteed to be handed to the subscriber, but because there is no global transaction, there is a possibility that a system failure can cause an event to be delivered more than once. If the subscriber throws an exception (or fails in any way), the exception is logged, but the event is not resent.
Does the above statement menas that i will lose my business event data.I cannot afford to miss any business events in any case.So i would like to know if in guaranteed delivery of events if the subscriber gives an error , i want my events to be still stored in database and not give excpetion to the publisher.
Pls help its urgent
Regards.....

I think it is clearly defined here -
http://docs.oracle.com/cd/E28280_01/dev.1111/e10224/obe_intro.htm#CHDIBHBE
guaranteed
Events are delivered to the subscriber asynchronously without a global transaction. The subscriber can choose to create its own local transaction for processing, but it is committed independently of the rest of event processing. This option incurs a lower cost than the one and only one option because there is only the trip to one queue (the main event queue). In addition, EDN does not attempt to resend an event (regardless of the backing store being AQ or JMS). If one or more subscribers fail to consume the event (while others succeed), those subscribers lose the message. In this respect, guaranteed delivery actually means best effort delivery; that is, it is not guaranteed that each subscriber definitely consumes the message.
So "Guranteed" is just a bad choice of word. It actually means "Best-Effort" so if you cannot afford to miss a single message then avoid using EDN in your solution.
Regards,
Anuj

Exception handling without BPM

Hello,
I have done exception handling with BPM.
i.e. when there exception comes in mapping I have use Block Exception Handler.
Can this be done without BPM.
Please snd me blog for it.
Regards

Hi,
As explained by Michal it is correct, but in message mapping , we can raise an alert .
See the below links
Alerts with variables from the messages payload (XI) - UPDATED - /people/michal.krawczyk2/blog/2005/03/13/alerts-with-variables-from-the-messages-payload-xi--updated
Triggering XI Alerts from a User Defined Function - /people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
Regards
Chilla

Exception handling with fault message type not working

Hi,
I have a sync proxy to proxy scenario and I have created a fault MT and specified in the outbound and Inbound service interface...
*In Inbound proxy I have the following code--*......
RAISE EXCEPTION TYPE z_cx_test_fault
EXPORTING
standard = l_standard_data.
In the sender side abap code which calls the outbound proxy I have the follwing code -
CATCH cx_ai_system_fault INTO lo_cx_ai_system_fault.
txt = lo_cx_ai_system_fault->get_text( ).
WRITE txt.
CATCH z_cx_test_fault INTO lo_cx_test_fault.
txt = lo_cx_standard_message_fault->get_text( ).
WRITE txt.
CATCH cx_ai_application_fault INTO lo_cx_ai_application_fault.
txt = lo_cx_ai_application_fault->get_text( ).
WRITE txt.
when i test the inbound proxy separately I get the custom fault message properly...
however when i run the proxy to proxy sync scenario and the custom exceptionz_cx_test_fault is raised inside the receiver proxy .......control goes to CATCH cx_ai_application_fault and not CATCH z_cx_test_fault .
I understand that cx_ai_application_fault is the super class of all the exception class but why does control go to its exception handling when a custom exception is raised...
Edited by: hema T on Feb 26, 2012 1:16 PM
Edited by: hema T on Feb 26, 2012 1:17 PM

Hi
I tried changing the sequence also but it did not work...
I can see an appropriate response coming from the receiver in SXMB_MONI of PI...this response has the "fault response "
"fault detail" data that I want.....however when the control goes to the sender why does it go to CATCH CX_AI_APPLICATION_FAULT and not not my CATCH z_cx_test_fault .
My observation - If I change the scenario to SOAP to Proxy sync..then the sender SOAP client gets the appropriate custom fault message back.
Edited by: hema T on Feb 27, 2012 1:17 PM
Edited by: hema T on Feb 27, 2012 1:17 PM

Exception handling without instanceof

Imagine you have 3 Exceptions:
Exception Z
Exception Y extends Z
Exception X extends Y
In a method you do:
throw new X ("...
And that method declares that it throws an Exception:
throws Y
To access this method you have to do through an interface which declares:
throws Z
If you need to handle exceptions X, Y and Z differently, how can you do it without using instanceof which is supposedly bad design? The interface needs to throw the generic 'Z' exception because it doesn't know what exceptions the methods that it invokes will throw.

hi,
just have catch blocks for all exception types; it's
the actual type of the exception thrown that matters,
not the type of the exception that is declared to be
thrown.
try {
} catch (X x) {
} catch (Y y) {
} catch (Z z) {
}You're right! I thought it would catch the top level exception only! Thanks!

Mediator exception handling when no data found in database

hi Guys,
I am using DB adapter in a composite and using a mediator to invoke them, however not getting how to send the response back,
in case there is NO_DATA_FOUND error.
waiting for response
thanks
Yatan

Yatan
As far as i know a DB adapter will not throw no_data_found exception if it is not able to get rows from database it will just initialize the output variable with null. But yes in case of call to procedure or function it may cause that you should handle then and there only.
Let us know what exactly is the issue you are facing.
Thanks
AJ

Can error handling framework use fault policies and BPEL catch blocks

As part of an integrated customer solution that makes substantial use of SOA Suite (including OSB, BPEL, Mediator, etc) we are in the process of designing an “Error Hospital” subsystem to expose a web service API specifically for BPEL services and/or the OSB layer to call whenever they encounter an exception which they cannot handle so that the appropriate user is notified of the error (via email) and the error is recorded (in an appropriate common fault format, with error codes elaborated into more meaningful descriptions, etc) within OEM, immediately prior to returning the exception to the caller.
The problem we have experienced in our design is as follows:
•     We have an error handling service to be called, inside the BPEL catch blocks, when an error occurs to notify the appropriate user, via email, that an error has occurred;
•     We also use the error handling XML fault-policies so that we can recover from an error using OEM (via human intervention);
•     The error service needs to be called before the process is suspended (waiting for human intervention) so the email notification and error message formatting occurs BEFORE the recovery action. Unfortunately the fault policies trigger BEFORE the error handler is able to transform the error into the appropriate format and notify the user so the error recorded is not the reformatted one and the user is never notified.
The key question is how can a BPEL, upon catching an exception, invoke the error handling service and AFTER that send the error to OEM (and have the process suspended).
It seems the two mechanisms "cannot play nicely together"

As part of an integrated customer solution that makes substantial use of SOA Suite (including OSB, BPEL, Mediator, etc) we are in the process of designing an “Error Hospital” subsystem to expose a web service API specifically for BPEL services and/or the OSB layer to call whenever they encounter an exception which they cannot handle so that the appropriate user is notified of the error (via email) and the error is recorded (in an appropriate common fault format, with error codes elaborated into more meaningful descriptions, etc) within OEM, immediately prior to returning the exception to the caller.
The problem we have experienced in our design is as follows:
•     We have an error handling service to be called, inside the BPEL catch blocks, when an error occurs to notify the appropriate user, via email, that an error has occurred;
•     We also use the error handling XML fault-policies so that we can recover from an error using OEM (via human intervention);
•     The error service needs to be called before the process is suspended (waiting for human intervention) so the email notification and error message formatting occurs BEFORE the recovery action. Unfortunately the fault policies trigger BEFORE the error handler is able to transform the error into the appropriate format and notify the user so the error recorded is not the reformatted one and the user is never notified.
The key question is how can a BPEL, upon catching an exception, invoke the error handling service and AFTER that send the error to OEM (and have the process suspended).
It seems the two mechanisms "cannot play nicely together"

Task flow exception handler

Hi all,
I'm trying to specify a method activity as an exception handler in the adfc-config. The problem is if I specify a view activity or a bounded task flow as the exception handler then it works fine, but if the exception handler is a method activity then it is not recognized. What could be the cause?. I need to execute a method when an exception occurs.
Version: 11.1.2.0
Edited by: NewBee on Apr 23, 2013 10:37 AM

Hi,
there should not be a problem with this and I recently did the same with JDeveloper 11g R2 (not sure which version of JDeveloper you use because you did not share this information). I assume you just marked the method activity as an exception handler without any other configuration? If so then set a break point to the managed bean method that you access from the method activity to see if it actually stops there. Also note that not all exceptions are handled by the controller exception handler. E.g an exception during render response phase (typically an exception in a managed bean) is not handled by the controller. Also you need to avoid the managed bean that handles the exception to itself throw one. This however you will see when debugging the bean.
Frank

Mediator 11.1.1.5 faults Java Handler not getting called fault-policies

Hi,
I have a Oracle SOA 11.1.1.5 Mediator and am handling the faults using fault policies but somehow custom java handler is not invoked when an error occurs and this is what I see in the log but somehow my custom java handler class is not getting called.
INFO: FaultPoliciesParser.parsePolicies ------->Begin Parsing of policy file
<Apr 16, 2012 10:30:17 PM EDT> <Error> <oracle.soa.mediator.common.listener> <BE
A-000000> <Enququeing to Error hospital successful...>Here is the fault-policies.xml
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<faultPolicy version="2.0.1" id="medFaultHandling"
               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="java-fault-handler"/>
        </condition>
      </faultName>
      <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
                 name="bpelx:bindingFault">
        <condition>
          <action ref="java-fault-handler"/>
        </condition>
      </faultName>
      <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
                 name="bpelx:runtimeFault">
        <condition>
          <action ref="java-fault-handler"/>
        </condition>
      </faultName>
    </Conditions>
    <Actions>
      <Action id="java-fault-handler">
        <javaAction className="com.mediator.faults.CustomMediatorFaultHandler"
                    defaultAction="ora-human-intervention" propertySet="myMediatorProps">
          <returnValue value="OK" ref="ora-human-intervention"/>
        </javaAction>
      </Action>
      <Action id="ora-human-intervention">
        <humanIntervention/>
      </Action>
      <Action id="ora-rethrow-fault">
        <rethrowFault/>
      </Action>
      <Action id="ora-retry">
        <retry>
          <retryCount>3</retryCount>
          <retryInterval>15</retryInterval>
          <exponentialBackoff/>
          <retryFailureAction ref="java-fault-handler"/>
        </retry>
      </Action>
    </Actions>
    <Properties>
      <propertySet name="myMediatorProps">
        <property name="logFileName">mediator-faults.log</property>
        <property name="logFileDir">C:/software</property>
      </propertySet>
    </Properties>
</faultPolicy>
</faultPolicies>Here is my the fault-bindings.xml:
<?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">
<composite faultPolicy="medFaultHandling"/>
</faultPolicyBindings>And here is the snippet of composite.xml where I put the below properties:
<component name="Router">
    <implementation.mediator src="Router.mplan"/>
    <property name="oracle.composite.faultPolicyFile">fault-policies.xml></property>
    <property name="oracle.composite.faultBindingFile">fault-bindings.xml></property>
</component>But when the exception occurs I don't see my custom Java Handler being invoked. As I created a jar file and placed it in
*<Middleware_Home>\Oracle_SOA1\soa\modules\oracle.soa.mediator_11.1.1*
and updated oracle.soa.mediator.jar manifest by putting the path of the jar file. Restarted the servers but still when an exception occurs in Mediator custom java handler is not invoked. Any ideas what I am missing or are there any special steps
Thanks

There is no point in retry on binding fault, rather you can raise it as exception and catch it in sepcific catch block or catch all will handle it.
Ideally this particular instance will be faulted and if required you can customize to send a mail with fault string to developer or support person or dba
This type of fault need human intervension to fix this code or it could be data issue.
- It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts).
Thanks,
Vijay

Exception Handling In BPEL By using Catch Blocks or Fault Policies Or Both

I have a confusion regarding
Exception handling :
When Should i go for 1)Catch Block (Remote , or binding ) in bpel for exception handling .
2)Fault Policy , Fault binding.xml
Currently iam using catch blocks , but even fault policy is good , but can i use both...
Currently in My bpel ,when any error occurs i have to send a error notification by Email .
Currently i have exposed the email service which shuts emails and write a file with errored Message.
Hence if any error i will catch i in a parent BPEL, i will just invoke the above email, service .
So anybody can help me by giving the suggestion how to go for the best approach
Edited by: anantwag on Mar 23, 2011 6:31 AM

Currently in My bpel ,when any error occurs i have to send a error notification by Email .
Currently i have exposed the email service which shuts emails and write a file with errored Message.Seeing your use case I will suggest you to use fault handling framework (fault policy). Fault handling framework should be used where you need generic error handling framework which handles all the faults occured in any composite component. Generally BPEL catch block should be used to propagate error info/fault back to the client/to fault handling framework or to consume an error
Regards,
Anuj

Using fault-policies with mediator and db Adapter doesn't work

Please help! I'm stuck on this for 2 days....
Hi Friends.
In my project I am trying to give some treatment to an exception from a db adapter running a pl/sql procedure.
I am forcing a raise_application_error in the procedure in order to treat the exception and I'd like the fault-police to treat it as "human-intervention".
The db-adapter is wired to a mediator:
jms-service ----> Mediator -----> Jca db adapter
When I get the exception the log says:
9d8bff56a1 due to: BINDING.JCA-12563[[
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PersistirODS' failed due to: Stored procedure invocation error.
Error while trying to prepare and execute the FORNECEDOR.UPSERTFORNECEDOR API.
An error occurred while preparing and executing the FORNECEDOR.UPSERTFORNECEDOR API. Cause: java.sql.SQLException: ORA-20101: Deu Merda
ORA-06512: at "FORNECEDOR.UPSERTFORNECEDOR", line 405
ORA-06512: at line 1
Check to ensure that the API is defined in the database and that the parameters match the signature of the API. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-20101" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
and then it looks like it's trying to run some fault-police but it says:
[2014-04-10T20:01:39.667-03:00] [AdminServer] [WARNING] [] [oracle.integration.platform.faulthandling] [tid: Workmanager: , Version: 0, Scheduled=false, Started=false, Wait time: 0 ms\n] [userId: weblogic] [ecid: 11d1def534ea1be0:-1fa77a00:145468d59e7:-8000-000000000002801a,0] [APP: soa-infra] [RejectedMsgHandling]Unable to apply policies on the rejected message with id - 60046[[
oracle.fabric.common.FabricException: Cannot resolve binding to a fault policy [Faulted Activity Details:
Activity Name=null
Activity Id=null
Activity lineNumber=null
Reference Name=null
WsdlLocation=null
ActivityType=null
Here are my fault-policies and fault-bindings files:
<?xml version="1.0" encoding="UTF-8" ?>
<faultPolicyBindings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                     xsi:schemaLocation="http://schemas.oracle.com/bpel/faultpolicy ../xsd/FaultBindings.xsd"
                     xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<composite faultPolicy="fault-policy"/>
</faultPolicyBindings>
<?xml version="1.0" encoding="UTF-8" ?>
<faultPolicies xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
               xsi:schemaLocation="http://schemas.oracle.com/bpel/faultpolicy ../xsd/FaultPolicies.xsd"
               xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<faultPolicy id="fault-policy">
    <Conditions>
      <faultName xmlns:medns="http://schemas.oracle.com/mediator/faults"
name="medns:mediatorFault" >
        <condition>
          <action ref="default-human-intervention"/>
        </condition>
      </faultName>
      <faultName xmlns:rjm="http://schemas.oracle.com/sca/rejectedmessages" name="rjm:PersistirODS">
        <condition>
          <action ref="default-human-intervention"/>
        </condition>
      </faultName>
      <faultName>
        <condition>
          <action ref="default-human-intervention"/>
        </condition>
      </faultName>
    </Conditions>
    <Actions>
      <Action id="default-human-intervention">
        <humanIntervention/>
      </Action>
    </Actions>
</faultPolicy>
</faultPolicies>
Again
Please help! I'm stuck on this for 2 days....

Could you try specifying test element inside condition like the following one
    <faultName xmlns:medns="http://schemas.oracle.com/mediator/faults" name="medns:mediatorFault">
        <condition>
         <test>contains($fault.mediatorErrorCode, "AppropriateErrorCode")</test>
          <action ref="default-human-intervention"/>
        </condition>
      </faultName>

Facing issue while handling faults using fault-policies.xml

Hi All,
Scenario: One Asynchronous Bpel is trying invoke the webservice. When the status of the webservice is "Down", the BPEL will throw "System fault : remoteFault"
This fault will be handled by the fault-policies.xml.
CustomFaultHandler.java : basically it will print data to audit-trail and send data to the JMS Queue.
I am facing some issues , when i am trying to handle faults using fault-policies.xml.
Issue1: Display warning message at time of deployment : Warning: Schema validation failed for fault-policies.xmlXML-24506: (Error) Identity constraint validation error: 'Key sequence not found in key reference'
Issue2: CustomFaultHandler.java is able to print data to audit-trail but unable to send data to the Queue. and why the policy file getting executed at time of "Start of Invocation" and then it's showing "Invocation faulted" ?
Audit-Trail Message:
*===========*
Started invocation of operation "process" on partner "RemoteService".Started invocation of operation "process" on partner "RemoteService".
[Fault Recovery] Invoked handleBPELFault on custom java action class "com.CustomFaultHandler".
Invoke1
190002190002
default/TestjavaAction!5.0*soa_fcb2a5dd-06a7-47f9-bb88-cab14d343856/TestBPEL
190002
Faulted while invoking operation "process" on provider "RemoteService". Faulted while invoking operation "process" on provider "RemoteService".
fault-policies.xml:
*==========*
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<faultPolicy version="2.0.1" id="ErrorHandlingModelr"
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-java"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="ora-java">
<javaAction className="com.CustomFaultHandler"
defaultAction="ora-terminate">
<returnValue value="Manual" ref="ora-abort"/>
</javaAction>
</Action>
<Action id="ora-abort">
<abort/>
</Action>
</Actions>
</faultPolicy>
</faultPolicies>
fault-bindings.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">
<component faultPolicy="ErrorHandlingModelr">
<name>TestBPEL</name>
</component>
</faultPolicyBindings>
Warning Message when trying to deploy the composite to the server :
=============================================
Warning: Schema validation failed for fault-policies.xmlXML-24506: (Error) Identity constraint validation error: 'Key sequence not found in key reference'
Error Message from server:
*==============*
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled.
failure to handle a fault thrown from a scope, by any blocks in the scope chain.
This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.
A top-level fault handler should be added to the flow to handle faults not caught from within the flow.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled.
failure to handle a fault thrown from a scope, by any blocks in the scope chain.
This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.
A top-level fault handler should be added to the flow to handle faults not caught from within the flow.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:205)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:850)
at java.lang.Thread.run(Thread.java:662)
Please help..
Thanks in Advance
Edited by: Sharmistha Ghosh on May 16, 2012 12:37 PM

My SOA suite version is 11.1.1.7 and i was getting the same warning while compiling the Composite in JDeveloper. To fix it update your fault-policy.xml
Change it to
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <faultPolicy version="0.0.1"
                 id="BPELProcessV1_Faults"
                 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">
And it will solve the issue.

How to check was the object bound or not without exception handling?

context.lookup("someName");throws NameNotFoundException in case object was not bound to someName.
How to check was the object bound or not without exception handling?

context.lookup("someName");throws NameNotFoundException in case object was not bound to someName.
How to check was the object bound or not without exception handling?

Fault policies for Mediator and BPEL

Hi
Can i use same fault-policies.xml for both mediator and BPEL or i need to create different fault-policies.xml

Yes you can use the same file, just you need to mention the BPEL/Mediator name with in component tag. Like below in fault policy file.
<component faultPolicy="FusionMidFaults">
<name>MediatorName</name>
<name>BPELName</name>
</component>
You can refer the below URL.
https://blogs.oracle.com/ateamsoab2b/entry/fault_management_framework_by_example
*7) Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question.*
thanks,
Vijay

Sync Send without a Exception Handler ??

hi..
Can a synchronous send step work with out an exception handler..??
im gettin my messages and combinin then n sendin via the sync send to call rfc , followeed by a send back to my server..
at this very stage it expects me to define a handler for the same for the sync send.
regards,
vishal

hi bhavesh..
im doin the same...
Mode : Synch
Request Message
Response Message
Receiver From : Send Context
any reason fr it dmandin fr an exception handler../
it tch details i see the error as "no handler defined for this system exception"..
any inputs..

Mediator Exception Handling without fault policies

Similar Messages

Maybe you are looking for