Handling Fault Messages for JDBC Receiver (Syn Inbound)

Dear Freinds,
Can we handle fault messages for JDBC Receiver which is synchronous.
OB Proxy Syn <> IB JDBC Syn
1. How to handle the same ? Please give some examples.
2. Should we use Stored Procedures at Oracle side to handle the fault messages and send back as response to the Proxy Response. Will it work.
Thanks & Regards
K.Ramesh

Dear Friend,
I have 2 interfaces where Proxy is OB & JDBC is IB. In the first interface both sender and Receiver are synchronous and in the second one it is Async.
In the first interface i have to send one field from R/3 table along with Native SQL query string to XI and the response of the SELECT query is sent back to the sender.
Assume if no fields are selected based on the field sent then proper error message has to be sent instead of the response message.
In the second interface i will be using UPDATE query at Asyn JDBC receiver.
How to do this if you are having JDBC Receiver.
I saw in many blogs where they had mentioned that we cannot handle fault messages in the Receiver JDBC.
KIindly explain.
Thanks
K.Ramesh

Similar Messages

Handling fault messages in BPM

Hi,
I am using BPM for a RFC to SOAP scenario to handle Fault messages. (Please have a look at my previous post also SOAP Fault message )
I have created an exception block in BPM to catch the fault message from SOAP service. Inside the exception block i need to map the fault message to RFC response. But fault message is not accessible in Exception block.
Let me know if you have any idea to solve this.
Thanks,
Uma

Uma:
Let me make clear the requiremt. You have RFC Import(aka Request message) and Export(aka Response + Exception) and you have Web Service with Request, Response, Fault messages. And you want to send the fault messages back to the RFC in addition to the response. I was wondering, If we do the following mapping without BPM, does that fulfill your requirement.
RFC-Import <----
> SOAP Request
RFC-Export <----
> SOAP Response
RFC-Export <----
> SOAP Fault
Can you let me know if you face any problems with this one. I have seen your other thread and was wondering, whats the problem is. May be I didn't understand the requirement properly. Please clarify me

Axis adapter receiver handle fault message

Hi
We have a Sync interface which makes a Proxy call from ECC to PI 7.3 and then PI makes Soap(Axis) Sync call to Web sevice. We are having issues when handling SOAP 1.2 fault message.
Below is the actual fault response from Webserver:
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
   <env:Header/>
   <env:Body>
      <env:Fault>
         <env:Code>
            <env:Value>env:Receiver</env:Value>
         </env:Code>
         <env:Reason>
            <env:Text xml:lang="en">FaultMsg</env:Text>
         </env:Reason>
         <env:Detail>
            <ns2:servicefault xmlns:ns2="https://hostname.de/webservice/0400-0005">
            </ns2:servicefault>
         </env:Detail>
      </env:Fault>
   </env:Body>
</env:Envelope>
But PI receives this response like system error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: FaultMsg</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I checked this way http://scn.sap.com/thread/1675917 but it doesn't fit for Axis adapter.
Please let me for any clues how to handle this fault response.
Regards, Dzmitry

Hi,
I'm working with Dzmitry on the issue since last week. After analyzing the implementation and checking some SAP notes I came to the following conclusion:
According to note 856597 the fault behavior of axis adapter is as follows:
" A: The receiver adapter expects a SOAP message as response. For
synchrnous calls, a successful response should be returned with
HTTP 200. In this case, the content of the SOAP body will be
returned to the caller as the response payload. When some error
occurs, the SOAP message may contain the SOAP fault element. In
this case, when the fault detail element is not empty, its
content will be returned as the fault payload in an application
error message. For others, a system error message will be
returned to the caller."
The example shows a SOAP 1.1 fault message with a "detail" node being mapped to an application fault.
As we are using SOAP 1.2 the namespace as well as structure of the fault defers. I assume that the module responsible for the transformation from AXIS message to XI message within the module chain does not recognize the detail node on out soap 1.2 fault.
Therefore the solution would be to insert a custom AXIS handler before com.sap.aii.axis.xi.XI30OutboundHandle mapping the soap 1.2 fault to a soap 1.1 fault.
Is there something like a short how to on how to implement Axis handler and how to deploy it. Sap help only says to package it into sda file....
Thanks a lot in advance!!!
BR,
Eugen

Fault Message for inbound asynch ABAP proxy

Hi All,
I've got scenario File -> XI -> ABAP proxy all asynchronous.
Inside a proxy I'm throwing an exception using fault message.
I don't see application error in SXMB_MONI on XI, I can see that only in SXMB_MONI on receiving system.
Is it possible to have flag Application Error on XI monitor as well ?
Best Regards,
Tomasz

Jai,
I've checked that many times.
I'll describe my scenario in more details.
1. From the file I'm receiving a lot of items and trying to process as much as possible in one proxy call.
2. Those ones which are causing errors are sent out to XI (outbound proxy) one by one. XI sends them to the same interface which is used in 1. step where I have condition which checks for single item and when it's wrong then exception is thrown.
One SCM box is sender and receiver which my cause that problem.
Tomasz

How to use fault message for error handling.

HI
Anybody has an idea about how we use fault messages to handle errors in XI
Thanks
Debraj

Hi,
Refer this link. This pdf file has descriptions about fault message types and how to use it.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4cdfc390-0201-0010-2197-da4ada09f281
Regards,
Uma

Handling Fault Messages

Hi,
I have this synchronous scenario : RFC > (XI without Integration Process) > SOAP.
Imagine that there is a problem with SOAP System and i get (don't worry about the error itself):
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException:
invalid content type for SOAP:
TEXT/PLAIN; HTTP 400 Bad Request</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I tried to add ExchangeFaultData into SOAP Interface, and mapping it but it didn't work.
Can i get this exception mapped into RFC exception?

The usage of your fault message is not correct, since it is designed to handle application error, in your case, it is technical error, it should be handled by alert framework.
Liang
===========SAP Definition================
Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.
u2022 In the synchronous case, when an application-specific error occurs on the inbound side, instead of sending a response message back to the sender, the application can send a fault message to handle the error.
u2022 The fault message of the application for an asynchronous ABAP server proxy is persisted for monitoring. In the case asynchronous of Java server proxies, the fault message is part of a negative application acknowledgement (see Acknowledgments).
Application-specific means that the application on the inbound side triggers the error itself because, for example, the request message did not contain sufficient information.
========= End of SAP Definition================

To Be Delivered on Adapter Message for JDBC

I'm stuck on a process that was working (file->Map->JDBC) until I made a change to the JDBC message which casued blocking on the SQL Server (don't know why). I ran the test a few times and now am getting status "To Be Delivered" in Adapater Monitoring. I've restored the data type structure to the original design, and still it is stuck per below.
Audit Log:
2005-11-10 10:40:09 Success The message was successfully received by the messaging system. Profile: XI URL: http://hqdvsapxi01:50000/MessagingSystem/receive/AFW/XI
2005-11-10 10:40:09 Success Using connection AFW. Trying to put the message into the receive queue.
2005-11-10 10:40:10 Success Message successfully put into the queue.
That is all there is. Anyone know where this message queue is? No error in adapter monitoring or in message monitoring, or in SXMB_MONI. I'm lost on this one.
Thanks.

Hi Tadd,
What this typically means is that the queues for the Adapter Framework weren't started. This can be for a variety of reasons, but usually happens on startup. If it's possible, restart the Adapter Framework (or search the log files if you have them) to see if you can spot why these queues weren't started.
I think one typical reason for this would be that the application that was supposed to receive messages from a given queue wasn't present (deployed or started) and so the queue wouldn't start. I think that additional logica may have been added to handle this more gracefully in a later service pack.
Cheers,
Steve
If you find a post useful, please help keep the community going by setting a good example and rewarding the poster with points.

Handling fault messages in an Integration Process (bpm)

I have a bpm in PI 7.11 which performs a synch call to an external webservice. In addition to the request/response, that webservice can also generate two faults: ObjectNotFoundFault and generalfault. I am having trouble handling these faults - when a fault occurs my handler is not being invoked and thus the bpm process stops/errors. When I look at the underlying process (via txn swi1), I see the exact error text:
"No exception defined for fault message ObjectNotFoundFault http://www.companyb.com/services/olsa_v1_0/"
From what I understand within the bpm synch call step to the webservice I need to do the following to handle the exception/fault:
- put the synch call (to the webservice) into a block
- add an exception branch to that block named let's say A & set the exception handler of that block to be A
- in the exception setting of that synch step, select A
In my case, I don't care about the fault details other than to ensure it does not stop the whole Integration Process, so in my exception branch I don't do anything. I did try adding a control step within it too (as per SAP Press text book).
Is there anything else I need to do here? I am not mapping the returned fault - does the fault need to be mapped (not sure how I would do this given that the synch step uses an abstract interface and therefore to my knowledge no fault mapping can be done)?
There are 2 Notes that describe my issue exactly:
https://service.sap.com/sap/support/notes/1484903
https://service.sap.com/sap/support/notes/1158699 <-- this one refers more to me, but we already have in 7.11
Can anyone let me know exactly the steps I would perform to handle these faults - does the exception name / handler A above need to be named the actual exception / fault ObjectNotFoundFault?
Any help appreciated.
Thanks,
Keith)?
Any help appreciated.
Thanks,
Keith

Thanks - my scenario I guess is #2 of that blog. But is your take that even if I don't care what is in the fault message, i.e. I don't care about the contents of it but rather I just want to continue on from it, that I still need to perform this java coding? It's not clear to me from what he says - it seems to me he does the java coding to actually capture the contents of the message. I am in fact using the soap axis adapter too, as he is. The screen shot showing the exception branch is basically what I have.
Regards,
Keith

How to modify oracle stored procedure for JDBC Receiver Adapter?

Hi all.
This is Urgent.
Scenario is
SELECT a TABLE with procedure and update column with it,
then send data to SAP System with RFC Adapter.
When I executed a sync bpm, scenario was finished internal error.
Pls, let me know how to correct procedure using JDBC Receiver Adapter?
Regrds all.
Procedure Code -
SET SERVEROUTPUT ON
CREATE OR REPLACE PROCEDURE zwtn2
IS
   v_seller_company      wtnivhd.seller_company%TYPE;
   v_invoice_no      wtnivhd.invoice_no%TYPE;
   v_report_date     wtnivhd.report_date%TYPE;
   v_customs_date     wtnivhd.customs_date%TYPE;
   v_ap_post_date     wtnivhd.ap_post_date%TYPE;
   v_gr_date          wtnivhd.gr_date%TYPE;
CURSOR l_cursor IS
   SELECT seller_company,
          invoice_no,
          report_date,
          customs_date,
          ap_post_date,
          gr_date
     FROM wtnivhd
    WHERE wtn_send_flag = 'N'
      AND rownum < 31
FOR UPDATE;
BEGIN
   OPEN l_cursor;
   LOOP
     FETCH l_cursor
      INTO v_seller_company,
           v_invoice_no,
           v_report_date,
           v_customs_date,
           v_ap_post_date,
           v_gr_date;
     EXIT WHEN l_cursor%NOTFOUND;
     UPDATE wtnivhd
        SET wtn_send_flag = 'Y'
       WHERE CURRENT OF l_cursor;
   END LOOP;
CLOSE l_cursor;
END zwtn2;

Hi Alex,
plz have a look to Runtime Workbench / Adapter Monitoring to find an error message.
Regards,
Udo

Handling fault message in orchestration

Hi,
I have consumed the WCF service here I want to handle the fault message,so when I right click on the service port it is not showing the fault message option.I am using BizTalk 2009 version.
Thanks.

Hi Ram,
Right Click on the PortType and Select New Fault Message as shown below.
A new fault port will then be created as shown below
I found this document very useful for the startup while working with WCF services.
http://download.microsoft.com/download/1/6/9/16968441-c6c8-4bd0-9410-5f4014bc61f0/sampledesignorch.doc
You can also refer
How to Add a Fault Message
Mohamad Halabi's blog is being very useful and descriptive about how to handle different WCF exception scenarios.
BizTalk – WCF Exception Handling Scenarios
Rachit

Multi Mapping for JDBC Receiver JDBC Adapter

Hi All,
I'm trying an IDoc to JDBC (canonical XML) scenario using multi mapping (single IDoc as source and two different JDBC messages in receiver end). But, this is failing in RWB with some parser error. So, am not sure whether multi mapping is allowed for JDBC Canonical XML format. Please clarify.
Thanks,
Hussain.

Hi ,
JDBC Adapter supports multi mapping,so you can implement the same,but what do you mean by Canonical XML format??
Regards,
Raj

Configuring Fault Message For the Send Synchronous step

Hi,
PI receives a file and sends a soap request to Third pary system. If the data sent to third party system is correct, PI receives a empty soap envelopre. If the data is not approriate, PI receives an fault message(Application Error).PI has to trigger an email in either case.
I have configured a send synchronous step to initiate Request/Response with a validation fault, followed with send step for triggering an email.once the interface is executed, The process is not moving further from Send synchronous step.In short the steps after send synchronous are not being executed.
Regards,
Kiran.

Hi,
I have created exception branch if PI receives a validation fault. PI will trigger success email, if the PI receives blank response from third system.PI will trigger failure email, if PI receives a fault message.
Regards,
Kiran.

Alerts for JDBC Receiver Adapter

Hi ,
I am using JDBC receiver adapter. I have configured the alert category and Alert rules. Alerts are getting for Mapping etc.
When ever error occured in the SQL server whether its firewall issue or some other issue. The alerts are not created. Instead I can see the error message in RWB Message monitoring and communicaton channel monitoring.
Please let me know How can raise alerts if the error occured at the JDBC receiver side.
Thanks in advance,
Kevin

Hi Kevin,
Probabaly the alert rule did not capture the error in the adapter engine.
The filter for sender and receiver interface details in the alert rule can cause this issue depending on when and how the error occured. Can you create an alert rule with * for all entries, for adapter engine and check?
Also do NOT check the option "suppress multiple alerts from this rule" because it will prevent subsequent alerts from this rule, if there is already one and not yet confirmed.
Further please check the alerts in SALRT table in se16 if its created properly or via transaction ALRTDISP.
Please use the report SXMSALERT_LOGREADER for troubleshooting and checking the alert logs.
Hope this helps.
Regards,
Francis

Long time waiting , delivery message by jdbc receiver adapter

this is a test case.
There are two large messages for two outbound interfaces, both about 50 000 lines txt files.
Both receiver is database.
There is a queue about 10 minute to wait.
Is it OK? How can I supposed to do?
Does it makes any difference if I use different communication channel?
Edited by: Shen Peng on Jun 9, 2009 10:20 AM

Hi,
In the insert structure of your JDBC the statement name node should be 0... unbounded.
Map your source structure row node ( which occurs 50,000 times for 50,000 records ) to statementname node. Check SAP help link for more details
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
As a result of this your interface will be triggered only once and it will fire 50,000 insert querys at back end.
This will improve your performance considerably instead of firing interface 50,000 times.
Hope this helps.
Regards,
Siddhesh S.Tawate
Edited by: siddhesh tawate on Jun 9, 2009 8:06 AM

"Recordsets per Message" for jdbc adapter

Hi all,
is "Recordsets per Message" kind of option is available for JDBC adapter.
Any help will be appriciated
Thanks
-Kulwant

Hi Kulwant,
its not available.
You can a stored procedure whick picks only certain number of records per each call.
Regards
Inder

Handling Fault Messages for JDBC Receiver (Syn Inbound)

Similar Messages

Maybe you are looking for