Error Handling in BPEL & ESB - Rejection Handlers

Hi guys
I have been trying to evaluate various ways for handling errors/exceptions in BPEL and ESB in Oracle SOA Suite 10.1.3.4 (Basic installation).
What i have found is that in ESB, errors can be handled at two levels: ESB routing service errors using ERROR_TOPIC and Adapter errors using RejectionHandlers. AND
in BPEL errors can be handled using in built try/catch (calling error hospital from the catch) and adapter erros using RejectionHandlers.
I tried using Rejection handlers (bpel, wsif, file) in BPEL and ESB. In BPEL they all are working fine when registered in bpel.xml.
But in ESB only the file handler is working. What i did in ESB is:
I set up an ESB which is polling a file adapter and simply putting the data into a table in database.
Then i created a BPEL (or a Webservice) which is based on http://localhost:8888/orabpel/xmllib/jca/RejectionMessage.wsdl file, taking
{http://xmlns.oracle.com/pcbpel/errorHandling}RejectedMessage as input.
Then I registered Rejection Handler in ESB's file adapter's .esbsvc (or Enpoint property- rejectedMessageHandlers):
"wsif://http//localhost8888/Error_Service/RejectionHandlerPort?wsdl|handleRejection|message"OR "bpel://default:welcome1|BPEL_Error_Handler|handleRejection|message"
I generated error in ESB by changing a column name of the table
For bpel rejection handler:
i was getting error: "<ERROR> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Rejection handler failed
Error while trying to hand off bad message to Rejection handler bpel://default|BPELProcess2|handleRejection|message due to: java.lang.Exception: Failed to create "ejb/collaxa/system/DeliveryBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/collaxa/system/DeliveryBean not found
at com.evermind.server.rmi.RMIServerContext.lookup(RMIServerContext.java:207)
at com.evermind.server.ApplicationContext.unprivileged_lookup(ApplicationContext.java:256)
at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:196)
at javax.naming.InitialContext.lookup(InitialContext.java:351)"
It was solved by adding in server.xml - <application-server ... global-jndi-lookup-enabled="true">. But now i am getting
"Error while trying to hand off bad message to Rejection handler bpel://default:welcome1|BPEL_Error_Handler|handleRejection|message due to: java.lang.LinkageError: duplicate class definition: com/oracle/bpel/client/ejb/interfaces/IDeliveryBeanHome. Please address the underlying issue or correct/redeploy the process."
*For wsif rejection handler*:
getting error: "Error while trying to hand off bad message to Rejection handler wsif://http//localhost8888/Error_webservices/RejectionHandlerPort?WSDL|handleRejection|message due to: exception on JaxRpc invoke: serialization error: java.lang.IllegalArgumentException: getSerializer requires a Java type and/or an XML type
Please address the underlying issue or correct/redeploy the process."
I followed: Link:[http://www.oracle.com/technology/products/integration/adapters/pdf/Adapter_TN_004_Adapter_ErrorManagement.pdf]
Same bpel/wsif handlers pointing to same BPEL/J2EE services, if configured for BPEL adapters, works absolutly fine and gives proble in ESB.
Am i missing something in ESB or is there any patch need to be applied? Please help me there.
Thanks in advance.
Inder

Hi
I even installed SOA Suite 10.1.3.4 MLR#5 Advanced installation with Oracle Express dehyderation store.
I was able to use WSIF rejection handler with this upgrade... but bpel rejection handler was still a failure.
So basically i re-visited ESB documentation. it says that ESB will not support bpel rejection handler.
At least not upto now.
So Summary:
For BPEL we can use - file, wsif, bpel & aq rejection and fatal message handler.
For ESB we can use file, WSIF (10.1.3.4 with MLR#5) & aq rejection and fatal message handler.
Thanks
Inder
Keep going...

Similar Messages

ESB Error Hospital and Rejection Handlers

Hi,
I am getting confused with ESB Error Hospital and ESB Rejection Handlers? Can anyone of you explain me what is this?
Thanks,
Gomathi

Rejection Handlers are used for adapters such as file adapter. When these fail during the invokation of the ESB, you can perform some operation, e.g. call a BPEL process. The default is to write to a default directory. But no notifications are made.
The error hospital is an error handlers for when the process fails in flight. This allows use to send notifications and retry if required, etc.
Here is a good doc on the subject.
http://www.oracle.com/technology/products/integration/esb/files/esb-transactions-errorhandling.pdf
cheers
James

How to ignore a DML operation using error handler.

In our streams replication application (using Oracle 10G), we have error handler to handle the errors at destination apply process. It uses straight apply process no DML handlers except error handlers. The error handler should just log the error and LCR info into the error log table and discard the DML LCR. Error logging is not a problem. But the problem is how to ignore the error DML LCR and move to next LCR in the same transaction without rollback of the transaction or any error.
Another question, do I need to use LCR.EXECUTE() procedure to continue the transaction in case of errors?
Appreciated your help.

Thanks for reference, confirmation of use of execute function.
I read those pages and other related pages in "Oracle® Streams Concepts and Administration" too.
I am able to write an error handler to handle errors with regular apply process. It is logging "no data found" errors but failing in case of foreign key violations. Error handler takes any kind of error and logs a record into errorlog table and ignores the error. I think it is not calling error handler. I checked for handlers in dba_apply_dml_handlers table. There is a handler for Inert, update and delete. I am investigating it further now. If you have any leads, please post.
Thanks for your time and help.
Dharma

How does BPEL Fault Management Framework gel with ESB Error Handling ?

I see that BPEL 10.1.3.3 has pretty neat Fault Management Framework (although I have to admit it is not very well advertised).
The next logical question is: what about ESB ? Would that help in ESB error handling ? I understand that ESB has its own Error Hospital etc.; however, we have to constantly grapple with two distinct paths for any piece of integration functionality (1. ESB 2. BPEL). I guess, all of this will be moot in the 11g timeframe. Still wondering if anyone out there has somehow unified error handling for these two distinct offerings ?

It's not available in ESB, you have to implement/extend that by your self. Off course in the next release everthing will be better :-)
But, if you are able to use Oracle AIA (http://edelivery.oracle.com) You could use Oracle AIA Foundation, that has a fault 'hospital' implemented both for BPEL and ESB.
Marc
http://orasoa.blogspot.com

ESB error handling and notification features

Hello everyone,
I am newbie to oracle SOA ESB. I am an oracle apps guy.
This being my first post to this forum, I have a lot of questions. :-)
For a small intergration requirement, we are looking for a good integration tool
Some requirements are:
1) Flat files will be generated by concurrent programs on oracle apps which need to be transferred to legacy systems.
2) Pick the data from apps tables and insert them into another database. Not much translation required.
After some research, found ESB to be a good fit.
Before actually start using it, we wanted to do a couple of POCs.
So far we are using shell scripts for ftp process. We opted for an integration tool to have DB to DB transmission. Apart from this we need better error handling and error notification mechanism.
Some error conditions:
1) Unavailability of ftp server or Database server.
2) Permission issues. Say some files may not have read, write, deletion permissions. They need to be caught and notified.
3) Mandatory field missing while inserting data which is read from a flat file into a DB table etc..
My initial thoughts on error handling are:
Connection error: To retry for connection errors. If the retry fails send notification via email and also write the failed connection details into an error log file(apart from the server log file).
Data mismatch: NOtification to be sent with the error details.
I would like to know What happens to the file if the destination ftp server is unavailable while ESB is trying to FTP the file. Will ESB retain the file with itself and FTP the file once the ftp server is up?
In BPEL I could see try catch blocks which can be used to handle the errors and thus send notifications.
ESB documents introduced terms like error hospital related to error handling but I was not able to figure out a way of implementing them. As I am not well versed with XML and WSDL I am probably unable to use the fault tab which is in the routing service. I feel Oracle could have given some samples that explain about ESB error handling.
Also to my dismay, adapter docs say that there is a limitation of 7MB size for ftping. Although our file sizes often fall below this size, I would want to know if there is any workaround to over come this size constraint.
I think I put a lot of stuff in a single post and may be in the most haphazard way. Please bear with me.
Please suggest me of some documents if any related to my questions.
Would be really great if you can give me a straight forward solution to all the above problems
Hope this forum would be a great help to me.
Cheers,
Robert.

I have worked on a few SOA Apps implementations. Some successful and some not so. It really comes down to the type of integrations.
But I would say the majority of your integration will be batch as this is what eBus is all about. If this is the case then I would recommend Oracle Data Integrator. If you go Oracle Data Integrator Suite it includes Service Bus and BPEL. ODI has an eBusiness Suite adapter as well.
The good thing about ODI is that you can use it for data conversion, that conversion can then be reused once live, so the conversion is not throw away.
In SOA 10.1.3.4 the limit of 7MB has been resolved but you must be using the file / FTP adapter for input and out, from the sounds of it you want to call concurrent programs so this probably wouldn't work.
cheers
James

Error handling and Manual Retry mechanism in BPEL

Hi Gurus,
We have a requirement that If any error occurs during BPEL process , We need to auto retry. if auto retry is not enough We need to manual retry and send the request message to Worklist for retry.
In our BPEL process We have CreateOrganization API provided which can not be rollback using compansation handlers. From Here I need to intiate the process using worklist if any error.
I dont know how to intiate the process from particular node. Please help me.
thanks,

My process has 5 invoke activities
CreateOrganization
createFaxNumebr
CreateAddress
CreatePhone
CreatePhExt
In my process , the first 2 services gets success, 3rd one 'CreateAddress' fails due to DB connection is broken. I can not rollaback first 2. I want to retry 3 rd using worklist when DB connection is fixed. I dont know how to call CreateAddress partner link as Catchall branch is not in scope of 'CreateAddress' and resume the process to execute 4 and 5 services.

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"

BPEL/ESB Errors to Worklist app

Hi All,
I have a requirement in which I have to bring the error message for all the errors that happen in BPEL and ESB to the worklist application. I have used BPEL fault policy and BPEL client API to implement this in BPEL and listened ESB_ERROR topic to implement this in ESB.
Now I want one 'RESUBMIT' outcome to appear in the task details if these errors are retryable. My odubts are:
1) How can I find out which errors are retryable in case of both BPEL/ESB ? I found a Retyable field in ESB_FAULTED_INSTANCE table in ORAESB ; but not sure how to use it . How can I find out the same for BPEL?
2) How do I add the Outcome 'RESUBMIT' dynamicaaly to the task whenevr the error type is retryable?
Please pour in some ideas on how to implement this....
Thanks.

Please deploy the bpel project and then you can locate it in the bpel console.
Then ,initiate the main process and only then log into the worklist app with the correct port number.
Then login with the correct user credentials and will be able to see the tasks allocated to him.
P.S.:Unless you initiate the process in BPEL Console , you cannot see the tasks for the user in worklist app.

File Adapter - Exception / Error handling

We are using File Adapter in BPEL process to read multiple records from the file. Additionally, we have also handled rejectedMessageHandlers & fatalErrorFailoverProcess exception to lunch custom BPEL process. The process is running fine and also successfully launches custom handler processes too.
Need help / direction in addressing following issues.
1. While reading from file, if a records errors out, the custom BPEL process is launched (as specified in rejectedMessageHandlers property). In such instance, the previously read valid records are processed but remaining records are marked as errored out. Our requirement is to make entire record set as invalid and would like to perform rollback of entire process.
2. Whenever an error occurs during reading the records using File adapter, the associated data file is being deleted from the input directory and also NOT available in archive directory also.
Are we missing any set up ? We are on 10.1.3.1
thanks
-Yj
Sample Log file:
<2009-04-20 11:46:14,080> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::init - Initializing the JCA activation agent, processId='bpel://localhost/default/TestFileRead~1.0/
<2009-04-20 11:46:14,080> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::initiateInboundJcaEndpoint - Creating and initializing inbound JCA endpoint for:
process='bpel://localhost/default/TestFileRead~1.0/'
domain='default'
WSDL location='Read.wsdl'
portType='Read_ptt'
operation='Read'
activation properties={portType=Read_ptt, rejectedMessageHandlers=bpel://default|AdapterError2|initiate|payload}
<2009-04-20 11:46:14,096> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - endpointActivation for portType=Read_ptt, operation=Read
<2009-04-20 11:46:14,143> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Endpoint Activation called in File Adapter for endpoint: c:\temp\yj
<2009-04-20 11:46:14,143> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - successfully completed endpointActivation for portType=Read_ptt, operation=Read
<2009-04-20 11:46:30,580> <WARN> <default.collaxa.cube.activation> <File Adapter::Inbound> PollWork::run exiting, Worker thread will die
<2009-04-20 11:47:14,158> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Translated inbound batch index 1 of file {testdata6.txt} with corrupted message count = 1
<2009-04-20 11:47:14,158> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Sending message to Adapter Framework for rejection to user-configured rejection handlers : {
fileName=C:\temp\yj\testdata6.txt, startLine=3, startColumn=1, endLine=-1, endCol=-1, Exception=ORABPEL-11168
Error while reading native data.
[Line=3, Col=5] Expected "|" for the data starting at the specified position, while trying to read the data for "element with name C2", using "style" as "terminated" and "terminatedBy" as "|", but not found.
Ensure that "|", exists for the data starting at the specified position.
<2009-04-20 11:47:14,158> <WARN> <default.collaxa.cube.activation> <AdapterFramework::Inbound> [Read_ptt::Read(Root-Element)]onReject: Sending invalid inbound message to Exception Handler: bpel://default|AdapterError2|initiate|payload
<2009-04-20 11:47:14,315> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Setting last error record to : -1
<2009-04-20 11:47:14,658> <ERROR> <default.collaxa.cube.activation> <AdapterFramework::Inbound> onBatchFailure: Batch 'bpel://localhost/default/TestFileRead~1.0//testdata6.txt_1240205493408' (C:\temp\yj\testdata6.txt) has failed due to: ORABPEL-11168
Error while reading native data.
[Line=3, Col=5] Expected "|" for the data starting at the specified position, while trying to read the data for "element with name C2", using "style" as "terminated" and "terminatedBy" as "|", but not found.
Ensure that "|", exists for the data starting at the specified position.

Any light / idea on the following issue ?
1. While reading from file, if a records errors out, the custom BPEL process is launched (as specified in rejectedMessageHandlers property). In such instance, the previously read valid records are processed but remaining records are marked as errored out. Our requirement is to make entire record set as invalid and would like to perform rollback of entire process. Even, if we do not configure rejectedMessageHandlers, the behavior is that valid rows are processed with the rest of BPEL process and for Invalid rows, the records are rejected. Our requirement, is that, even if there is one invalid record, the entire set of record should NOT move ahead with the BPEL process
2. Whenever an error occurs during reading the records using File adapter, the associated data file is being deleted from the input directory and also NOT available in archive directory also. Note, in case of all valid record the file is available in archive directory

Error Handling in File Adapter

I have been working on a requirement where the file adapter picks up the file and gives to the BPEL for processing the data.
So, in order to do Error Handling for file adapter, i have been reading the Oracle documentation for technology adapters. In that, some of the
points which i felt valuable for my error handling when using file adapter are the uniqueMessageSeparator property, fault-policies for rejected messages,
and one of the action for rejected messages could be writing the payload to a file or invoking any other webservice.
In my composite, i have configured the file adapter as a service for reading files, and i defined the xsd using the native format builder....If i put some data like 'aaaa' in the attribute of type integer , the .csv file is being picked up and its being passed to the BPEL without any error ? I believe there should be a translation error...right...
But i am not getting the error, please tell me if anything is wrong in my xsd....
Here is my xsd...
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
xmlns:tns="http://TargetNamespace.com/InboundService"
targetNamespace="http://TargetNamespace.com/InboundService"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
nxsd:version="NXSD"
nxsd:stream="chars"
nxsd:encoding="US-ASCII"
nxsd:hasHeader="true"
nxsd:headerLines="1"
nxsd:headerLinesTerminatedBy="${eol}"
>
<xsd:element name="names">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" minOccurs="1" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="FirstName" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="LastName" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Number" type="xsd:integer" nxsd:style="terminated" nxsd:terminatedBy="${eol}" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
And for DB Adapter, there is a property called SchemaValidation, i think that is not there for File adapter, by default it will take care of validation i guess....In another composite, my file adapter is picking up the .xml file and if i put any wrong data over there, that is working fine, i am getting the translation error, but only here in the case of csv file, i am not getting the error. Experts, please help me in this regard...I am using SOA 11G
Thanks,
Naresh

Hi Yatan,
Thanks for the reply. I did the same way, where my composite is picking up an XML file and translation error is coming. Even the fault policies are working fine, like writing to a file and even invoking other web service. Its really good that you have achieved the same thing in csv files. But the same thing i am unable to achieve when my file adapter is picking up the csv file. I really cant understand where i am doing wrong.
here is my XSD which i defined through my native builder format...
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
xmlns:tns="http://TargetNamespace.com/FileRecv"
targetNamespace="http://TargetNamespace.com/FileRecv"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
nxsd:version="NXSD"
nxsd:stream="chars"
nxsd:encoding="US-ASCII"
nxsd:hasHeader="true"
nxsd:headerLines="1"
nxsd:headerLinesTerminatedBy="${eol}"
>
<xsd:element name="Roots">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="FirstName" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="LastName" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="Number" type="xsd:integer" nxsd:style="terminated" nxsd:terminatedBy="${eol}" nxsd:quotedBy=""" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
the jca file ..
<adapter-config name="FileRecv" adapter="File Adapter" wsdlLocation="FileRecv.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/FileAdapter" UIincludeWildcard="n*.csv"/>
<endpoint-activation portType="Read_ptt" operation="Read">
<activation-spec className="oracle.tip.adapter.file.inbound.FileActivationSpec">
<property name="DeleteFile" value="true"/>
<property name="MinimumAge" value="0"/>
<property name="PhysicalDirectory" value="C:\files"/>
<property name="Recursive" value="false"/>
<property name="PollingFrequency" value="5"/>
<property name="IncludeFiles" value="n.*\.csv"/>
<property name="UseHeaders" value="false"/>
</activation-spec>
</endpoint-activation>
</adapter-config>
I told that the file will contain only 1 record while defining xsd and i kept a record whose values are John , Peter and akjdkjdskj.
Now if the data is like above, the file is still getting picked up without any translation error and the BPEL is getting completed successfully...
Is it possible for you to send your sample project and the csv file from which you have defined the xsd to me if you dont mind ?
Thanks,
Naresh

Error Handling in Mediation for sequential Invocation in Routing rules

Hi all,
I have a situation File Adapter->Mediator->BPEL Process 1->BPEL Process 2.When an error occurs in BPEL Process 1 a soap fault is returned to the mediator service.
Now since the mediator service invokes BPEL process 1 synchronously hence the fault policy is by-passed and the error is returned to the file adapter(the caller).
I have configured rejection handling in the fault-policy file as below -
_+<faultName xmlns:rjm="http://schemas.oracle.com/sca/rejectedmessages" name="rjm:pollFlatFiles">+_
_+<condition>+_
_+<action ref="ora-ws"/>+_
_+</condition>+_
_+</faultName>+_
_+<service faultPolicy="RejectionMessageHandlerPolicy">+_
_+<name>pollFlatFiles</name>+_
_+</service>+_
The following scenario occurs when trying to test the error handling -
1.First when the error occurs in BPEL processes 'oracle.fabric.common.BusinessFaultException' is thrown at the composite level and no message is rejected by the file adapter.
2.Immediately when the errors occurs for a second time the messages gets rejected and my rejection handler is called since the following exception is thrown from the file adapter -
The adapter has exceeded maximum configured retries. The adapter was unable to process "{0}" after having retried for {1} times, now the adapter will reject the message. This exception usually comes due to errors in downstream systems. Please increase the value for "jca.retry.maxRetries" in composite.xml for the inbound service and redeploy.
I have tried increasing the retry count also in composite.xml but the same sequence occurs i.e-
First time business exception.
Next time message rejection.
Any idea how the error can be properly handled in synchronous invocation to avoid this situation so that the messages always get rejected?
I am using SOA Suite 11.1.1.2.0 version.
Thanks and Regards,
Mandrita.

Hi samay,
In the transfer rules, if returncode is not 0, the upload stop,so..
Actually I delete the "wrong" data in the start routine of the transfer rules

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

AIA or BPEL/ESB for Integration ?

Hi All,
I know that this question has been raised many times on this forum. :)
But still I want to know the main difference between the integration development using AIA or BPEL/ESB ?
Which one is better in which scenario and why.
Please throw some light on this.
Cheers,
KK Chopra

<div class="jive-quote">
What if I am integrating two custom application where I am sure that a pre-build PIP will never be available.
What do you suggest?
What is the value add of AIA except XSD and WSDL?<br>
<br>
</div>
Check out AIA Foundation Pack which can help you to build PIP between any custom applications.
Well such XSDs and WSDLs can be downloaded from OAGIS. But hold on AIA gives you more than that.
Some of the things which I can see in AIA ....
- Just by using SOA tech stack - BPEL/ESB/XSD/WSDL one can't achieve true SOA. AIA teaches how exactly we should build integrations using these technologies to get SOA values.
It has proven reference architecture that consists of documented best practices,design patterns and template to help to accelerate your approach to SOA.
- AIA's EBOs (XSDs) and EBSs (WSDLs) are already practiced for bunch of integrations between different applications. They are much more matured. Also AIA has best practices for extending,versioning these artifacts.
- SOA governance tools like SOA Repository,testing integration scenarios,error-handling
- Conceptual models of End-to-End business processes which are application independent.
Thanks
/Mishit

How to take control back from service error handler in osb

I am using osb to send data to multiple services at the same time.since x query is a procedural language if any single operation fails the flow goes to service error handler which calls a BPEL webservice and logs the error in a database but the control doesnt comes back to my code I have tried everything including RESUME,REPLY operations but all in vain similarly i cannot use service callout call to my business service because its not allowing to select my BPEL wsdl operation

If your statement "the control doesnt comes back to my code" means you expect that your xquery will continue in processing than your expectations are just too high. :-)
Resume action is supposed to resume the next action in the message flow. It means the action that follows the action which caused an error.

How to stop execution after generating error message in an error handler?

I am working on ALSB 3.0.I have a proxy consisting of 2 stages in a pipeline pair. I have error handlers for each of the stages. The first stage contains schema validation action. Whenever the schema validation fails,control should transfer to error handler.
The error handler has a publish action and in request action I am calling an xquery transformation to generate error message.Publish action should publish message to a jms based business service configured. My questions are:
1. After getting into the error handler, the first alert msg configured inside request action (of publish action) is generated.Subsequent actions to generate error xml message and to replace the contents of errorXml in $body are not executed.And so no error message is generated or published.
2. I have also configured a reply with failure. Inspite of that,the control shifts to next stage in request pipeline and execution continues.
Can anyone tell me where I need to do the corrections.
Cheers.
Edited by: arrajago on Jun 15, 2009 11:55 PM

Got the answer.Generate error xml outside publish action.Replace action has to placed inside Publish's request action.To stop execution,use Reply action after Publish.

Error Handling in BPEL & ESB - Rejection Handlers

Similar Messages

Maybe you are looking for