on 04-04-2008 7:01 AM
Hello Experts,
We a have a scenario with a sync call to a WebService, but sometimes WebService is unavailable, which throuths Connection Timeout error on XI. I want to inform the responsible person about it. I have created a Fault MEssage Type, define it in sync interface in WebService. But what next? How do I define the way to map this Fault Type and the destination where it should be sended?
Thanks for you answers!
From the beginning, ur problem was not at all related to Fault message. Bcoz ur problem is that webservice is not reached at all. Fault will only get generated when webservice is reached and in its execution it is getting some improper value. This is not ur case.
U can notify the person by some alert. Configure alert for the errors and ur problem is solved.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
Are you using WSDL in your application provided by Web Service or Something else .
If you are using WSDL and it doesn't have Fault message type then you will not be able to see the tab.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
is it possible at all to handle System Errors?
and where I can get XSD for this type of Error message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!-- Call Adapter-->*
<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: com.sap.aii.af.ra.ms.api.RecoverableException: java.net.ConnectException: Connection refused (errno:239)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Experts,
we have finaly defined an Exeption type for the RFC, I have created the mapping for Fault messages and added it to the Interface Mapping.
The problem right now is that this mapping is not executed for some reasons, when error is happening.
This error is returned (System error):
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!-- Call Adapter-->
<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: com.sap.aii.af.ra.ms.api.RecoverableException: java.net.ConnectException: Connection refused (errno:239)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
And nothing happens, no mapping is executed, no Exeption message is sended back to the RFC.
Could you please help me with this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Fault message is a error meesage. Its like an exception in simple terms. The fault message is used to
store a log for application error. Fault messages is defined in IR.
To give a overview on Fault messages it is mostly used in synchronous communication. When an error
occurs at the inbound side instead of sending the response message back it sends a fault message back
to the sender system to handle error.
Fault Message are Msg type that provided whenever u create a namespace..they are usually used to get
the exception or error mapped which has occured while execution of Application at the sender/receiver
end....
Fault messages are used to propogate / send back the error message to the calling application. This is
used when there is a failure and the sending system needs to know what the error was. This is more of
catching Application Errors
Check these Fault messages Blogs
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
fault message scenario through blog;
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI -
/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
check this nice blog also
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
http://help.sap.com/saphelp_nw2004s/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-
a258cf083bca
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
Regards
Seshagir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.