Fault Messages with file to file

Hi frnds,
I have one doubt can i use Fault messages in file to file Asynchronous scenario if it possible please share the how to do the Scenario with Fault messages.
Regards,
Rajendra

Hi
For file to file async scenario, i don't think we can use fault message.
But it can be used with proxy async scenario as per the below blog
Fault Message Types - A Demo (Part 1)
Regards
Osman

Similar Messages

Fault message type using in File to IDoc Scenario

Hi,
I have successfully configured File to IDoc scenario. Now I am thinking to add some flavour to it by using Fault message type.
Can I use fault message type without using any proxies?
Can some body help in giving an answer to my question and provide some weblogs to achieve the configuration?
Thanks in advance.
Suraj Kumar

Hi Suraj,
With IDOCs, you cannot set up fault messages as it is async mode communication. There is not control which waits for the processing of the message/application errors as you have it in case of synch mode.
But, you can set up acknowledgement using ALEAUD. Check this for more /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
praveen

Fault message with 'Server error'

Hi all,
I have the following problem in PI.
The scenario is a synchronous interface, in which messages are send to PI using SOAP adapter. These are sent by proxy to ECC, and afterwards a reponse message is sent back.
So it's a SOAP-Proxy scenario with a synchronous interface and a request/response message.
I'm testing this interface using SOAPUI.
In PI the request and response messages are processed succesfully, however in SOAPUI I get the following error message (fault message), which is also shown in the communication channel logging.

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
     <SOAP:Fault>
       <faultcode>SOAP:Server</faultcode>
       <faultstring>Server Error</faultstring>
       <detail>
          <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
              <context>XIAdapter</context>
              <code>ADAPTER.JAVA_EXCEPTION</code>
              <text>java.lang.ClassCastException
The fault message contains the error: Server Error.
Does anyone have an idea what causes this?
Thanks in advance any help!
Regards,
Marco

Hi Eng Swee
The audit log doesn't show any errors. The java.lang.ClassCastException erro is shown in the processing details of the communication channel (column explanation)
The last step in the audit log is : "The message status is set to DLVD"
I think steps are missing after this, that sent the response message back to SOAPUI.
I also had a look in a similar interface I've build earlier, in which the additional last steps are:
SOAP: Response message leaving the adapter
SOAP: Processing completed
So for some reason the response message is not sent back from the adapter.
Could this issue be related to the test with SOAPUI and the version used?
The SOAPUI version is 5.0 and the PI version is 7.0
Regards,
Marco

Fault Message with JDev 9.0.3

Hello,
I'm using JDev 9.0.3 and I want to create with wizard a Web Service that response with a customized fault message. Is it possible?
If is possible, someone knows where may I look for some examples?
Thanks all...
Regards,
Mirko

What you can do with Oracle9iAS Web Services is create a method (or one that throws an error like) like the following:
public void customError(String p1) throws Exception
throw new java.io.IOException ("Custom error: " + p1);
Pretty much you can thrown any error the the string part of the error will come back in the SOAP Fault.
If you need to do more customized fault handling, you can use Oracle SOAP (based on Apache SOAP) instead of Oracle9iAS Web Services (see below for doc references). This gives you more flexibility but unfortunately puts you into a deprecated stack of software - Oracle is moving to JAX-RPC going forward as an evolution of Oracle9iAS Web Services.
However, if you need it tactically to get the job done, you can consider it. See the following two bits of doc:
http://download-west.oracle.com/docs/cd/A97688_06/generic.903/b10004/oraclesoap.htm#634093
(see http://download-west.oracle.com/docs/cd/A97688_06/generic.903/b10004/oraclesoap.htm for doc covering the entire Oracle SOAP implementation) and:
http://xml.apache.org/soap/docs/guide/errors.html
Mike.

Fault Messages/Response handling in File-XI-SOAP scenario

Hi
I have a File-XI-Webservice scenario.
Suppose I am sending a call "Request" to the webservice with 4 fields a,b,c and d. If the call is succesful we get an epmty "Response" back. Suppose any of the fields a,b,c or d are missing then the webservice throws an "AccountUtilsException" with a message "Required data 'c' missing". I want to be able to capture this message in a file.
I tried using asynchronous scenario first but that didnt work. I didnt get an empty response back for successful messages, neither did i get an error in sxmb_moni for missing data. Only the SOAP adapter would be red and the error "UNKNOWN ERROR" would appear. So I created a BPM with a receive, send-sync, send steps. With the AccountUtilsException set up as the response. Now, when all the data is good everything is successful and a file is created with the empty "Response" xml. When any of the fields is missing I see errors in sxmb_moni with Message class "Application error". But when I go into the payload I cannot see the xml. Instead it says "Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later." When I click view source I see the xml with the message "Required field c is missing". A file is also not written. Can anyone help me figure out what I am doing wrong?
Thanks,
Jahnavi

Hi Jahnavi,
yes, the asynchronous scenario cant work because there is no answer.
I think you should have exception types in your interfaces and map the fields of the exception. I m not shure if the answer of the webService in case of exception (AccountUtilsException) is a xml msg, you shoud be able to find out that at RTW message monitoring. You should be able to put that into a the exception type of the interface. Another possiblility to pick the exception up would be an alert.
Regards,
Udo

Scenario: SOAP message with attached .zip file to FTP ?

Hi all,
I've searched SDN etc but got no good hints to my problem.
My scenario is tht we are receiving an XML message via SOAP adapter and this is a MIME multipart message so it carries also a attached zip-file.
The XML and the attached zip-file should then be saved over FTP.
It enters IS correctly and I can see that I have the attachment and it goes to AE. I can see payload and attachment in the statusreport on receiver cc.
The FTP adapter saves the payload XML correctly but the attachment is not saved anywhere.
I have not configured any modules, BIC etc in the FTP adapter and I need some input on how to set this up tp put both files on FTP server.
In the future the FILE adapter will be used and then I wounder if I will get the same problem there?

I dont think there is a direct way of doing this. I can suggest you a method. In the directory receiver determination use 2 receivers with no condition. You message will get split in to two now. Create the interface determinations and receiver agreements. Complete one of them normally. It will sav the xml t FTP. For the other one, in the adapter use the payloadswapbean. It will swap the attachement to payload. THis one would save your zip on the ftp server.
Hope its clear..!!
VJ

Text messages with animated .gif files attachment

I recieved a text the other day with an animated gif file attached. I believe it was sent as a zip file. Anyway I tried to open it and all I got was a gray screen with an icon . No animation.. The second one I recieved was from a buddy. I watched and listened to it on his Droid 1. I had him send it to my phone text came through fine when I went to load and play the gif file it .had sound but no animation, just the gray screen again. I know the attachment is a zip file as I sent it to my email and opened it on my computer. Any thoughts maybe there's a setting I'm not finding? I'm using whatver text mesage program thats standard on the DX.
Thanks
MTY55.

Sounds like the issue you are having is that the files are zipped, MMS should be zipped because it has to access the files to display it.. I send and recieve anifated gif files and they play fine but also keep in mind that for some reason the stock email client does not play all files at same time, if there is a audio and photo, it will play audio and then the photo..

Segmentation fault message with EXPDP

Hi everybody,
I have issued the command EXPDP...
expdp user_30jun/user_30jun DIRECTORY=datapump DUMPFILE=expdp_export.dmp EXCLUDE=TABLE:\"IN $\'TABLE_A\', \'TABLE_B\', \'TABLE_C\'$\" NOLOGFILE=Y
The system displays a message "Segmentation fault" and then aborts. I could not find out the cause. Please help me out!
Thanks,
Aswin.

Please find below the snapshot...
[oracle@localhost bin]$ expdp user_30jun/user_30jun DIRECTORY=datapump DUMPFILE=expdp_export.dmp EXCLUDE=TABLE:\"IN $\'TABLE_A\', \'TABLE_B\', \'TABLE_C\'$\" LOGFILE=log.log
Export: Release 10.1.0.2.0 - Production on Monday, 30 June, 2008 17:27
Copyright (c) 2003, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Segmentation fault
[oracle@localhost bin]$
The logfile log.log which has been generated at datapump directory has no contents!
Message was edited by:
Aswin.

Create a message with empty file in Service pack 9

Hello.
I have the Service pack 9, and when PI read an emtpy file delete it inmediately.
Is there any way to create the message with an empty file? How?
Thank you.

Look into empty file handling in the file adapter. Below is from the sap help documentation for the file adapter.
Sender File adapter
Handling of Empty Files
Specify how empty files (length 0 bytes) are to be handled.
u25CB       Do Not Create Message
No XI messages are created from empty files.
The files are processed according to the selected Processing Mode.
For example, if the processing mode is Delete, empty files are deleted in the source directory.
u25CB       Process Empty Files
XI messages are created with an empty main payload.
The files are processed according to the selected Processing Mode.
u25CB       Skip Empty Files
No XI messages are created from empty files.
Empty files are skipped and remain in the source directory.
Receiver File adapter
Select the Handling of Empty Messages:
u25CB       Write Empty File
An empty file (length 0 bytes) is put in the target directory.
u25CB       Ignore
No file is put in the target directory.

Got problems with creating RTF-files after OSX update

Hi
I don't know if this is really a MAC OS problem, but it occurred after I updated to 10.5.2 - so it's a likely suspect.
Since the update I can't create RTF-files any more with Final Draft, my script writing program. A file is created, but when I try to open it I get an error message that it cannot be found. But the file is there: I can see it and click on it. It just won't open.
Only today now I got the same error message with a doc-file I downloaded some months ago.
The only big change I lately made to my Mac was the update to 10.5.2 and I got the new Office 2008 (both are the German versions). Could the problem come from either of them? I contacted Final Draft's support - they didn't know of the problem.
Maybe someone else in this forum has encountered similar problems?

Have you tried to Repair Permissions using Disk Utility?
1. Open Disk Utility in your Applications/Utility folder.
2. Click on the icon for your boot volume.
3. Click on the First Aid tab and select Repair Permissions
4. Click the repair permissions button.
This is the first thing to try whenever any program goes wonky. It's free, but takes awhile for all the files that have to be checked and changed.

Fault message handling in BPM

Hi again xi fighters
I created a business process with a synchronous sending step. I defined all interfaces and implemented also an own fault message type within the synchronous abstract interface. If the used RFC got the correct data the sync. sending step worked proper and also the business process worked fine. If I providing wrong data to the RFC to force him to throw an exception the Business process received the fault message. Then I just want to send the received fault message asynchronously to a file adapter within the defined exception branch. And now the question no-one answered in several discussion threads ;-<
How can I send the message? I am not able to implement a new variable in the container for the fault message type. Any advises here?????
Please help me, before I got inshane of SAP ;->>
Regards Oliver
Message was edited by: Oliver Bluhm
Hi everybody
any ideas, or is the question not clear. Please have a look and let me know you exlperience!
Regards Oliver

Hi Oliver,
how do you know, that is impossible to read the content of the fault message in the exception branch? Did someone from SAP say that? For days I read all the notes, blogs, help,.. and didn't find an answer.
It should work.
1. I have an integration process in XI sending a sync message to R3.
- OK
2. In the generated proxy class I raise an exception of the generated exception proxy class.
- OK
3. The exception message is shown in the message monitoring, containing also all our customer-data.
- OK
4. The integration process in XI activates the correct exception branch.
- OK
Missing: How do I get a grip on the data in the error message?
Kind regards Philipp
Message was edited by:
        Philipp Jakob

Soap fault message handling in XI

Hi,
I am using axis 1.4. SAP XI is my clinet. My wsdl file as below
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://ws.example.com/service"
   xmlns:wns="http://ws.example.com/service"
   xmlns:tns="http://ws.exampleenterprise.com"
   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
         <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
                targetNamespace="http://ws.exampleenterprise.com"
                elementFormDefault="qualified">
                 <xs:complexType name="SecrtySbj">
                         <xs:sequence>
                                 <xs:element name="usrname" type="xs:string"/>
                                 <xs:element name="pswrd" type="xs:string"/>
                         </xs:sequence>
                 </xs:complexType>
                 <xs:complexType name="AuthenticateRequest">
                         <xs:sequence>
                                 <xs:element name="secrtySbj" type="tns:SecrtySbj"/>
                         </xs:sequence>
                 </xs:complexType>
                 <xs:element name="authenticateRequest" type="tns:AuthenticateRequest"/>
                 <xs:complexType name="AuthenticateResponse" >
                         <xs:sequence>
                                 <xs:element name="sessnId" type="xs:string"/>
                         </xs:sequence>
                 </xs:complexType>
                 <xs:element name="authenticateResponse" type="tns:AuthenticateResponse"/>
                 <xs:complexType name="customFault">
                         <xs:sequence>
                                 <xs:element name="customCd" type="xs:int"/>
                                 <xs:element name="customMsg" type="xs:string" minOccurs="0"/>
                                 <xs:element name="customExcp" type="xs:string" minOccurs="0"/>
                         </xs:sequence>
                 </xs:complexType>
                 <xs:element name="customFault" type="tns:customFault"/>
         </xs:schema>
</wsdl:types>
<wsdl:message name="authRequest">
   <wsdl:part name="parameters" element="tns:authenticateRequest"/>
</wsdl:message>
<wsdl:message name="authResponse">
   <wsdl:part name="result" element="tns:authenticateResponse"/>
</wsdl:message>
<wsdl:message name="CustomFault">
   <wsdl:part name="CustomFault" element="tns:customFault"/>
</wsdl:message>
<wsdl:portType name="AuthenticateServiceInterface">
        <wsdl:operation name="authenticate">
    <wsdl:input message="wns:authRequest" />
        <wsdl:output message="wns:authResponse" />
    <wsdl:fault name="CustomFault" message="wns:CustomFault"/>
   </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="AuthenticateServiceSoapBinding" type="wns:AuthenticateServiceInterface">
          <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
   <wsdl:operation name="authenticate">
    <soap:operation soapAction=""/>
    <wsdl:input>
     <soap:body use="literal"/>
    </wsdl:input>
        <wsdl:output>
                <soap:body use="literal"/>
        </wsdl:output>
        <wsdl:fault name="CustomFault" >
                   <soap:fault name="CustomFault" use="literal" />
           </wsdl:fault>
   </wsdl:operation>
</wsdl:binding>
<wsdl:service name="AuthenticateServiceService">
   <wsdl:port name="AuthenticateService" binding="wns:AuthenticateServiceSoapBinding">
    <soap:address location="http://10.236.14.6:8080/axis/services/AuthenticateService"/>
   </wsdl:port>
</wsdl:service>
</wsdl:definitions>
Axis generates the soap fault as below in detail tag as below
<ns1:customFault xmlns:ns1="http://ws.examplenterprise.com">
<ns1:customCd>123</ns1:customCd>
<ns1:customMsg>Password is wrong</ns1:customMsg>
<ns1:customExcp>CustomException</ns1:customExcp>
</ns1:customFault>
They are getting error like below while getting the fault message.
<SAP:ApplicationFaultMessage namespace="http://ws.exampleenterprise.com">customFault<SAP:ApplicationFaultMessage>
Question: Why it is throwing "ApplicationFaultMessage" for fault messages? is there any error in wsdl file in defining the elements? or style has to be different? or is it an namespace issue in the wsdl?
Note: They are able to do it sucessfull for the response message.

Hi,
The answer is in your Question itself.
XI Sequence
1.First step is to identify the wsdl:Message element with the namespace http://ws.example.com/service
2.The next step is to go to the part element in http://ws.exampleenterprise.com and map the fault message.
To be simple in your case http://ws.example.com/service is the namespace of Fault Message and http://ws.exampleenterprise.com is the namespace of the fault message payload (Fault XML Message).
So even though the Fault XML Message has the namespace http://ws.exampleenterprise.com ,but if the fault namespace doesnot come with http://ws.example.com/service then Fault will not be triggered and processed in XI.
I hope you get the difference between the two namespaces used and the implications of them.
Fault is entirely different from respone.
Its like exception in java. If you donot catch the correct exception, will the exception raised be caught? Similarly if your SOAP service doesnot invoke the fault message with correct namespace (http://ws.example.com/service ), you cannot invoke/catch the fault message in XI.
Regards,
Sudharshan N A

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 in sender SOAP scenario

Hi mates,
I've a o/b synch MI which is exposed as a web service. I've specified the fault message with faultcode, faultstring, faultactor and detail. I've a BPM as the receiver for this synch infterface. This BPM implements synch-asynch bridge.
Now the question is...How can I specify that a particular fault message needs to be returned to the SOAP caller. I can send the response for the SOAP caller using the send step with mode 'Closes S/A bridge'.
I appreciate you inputs.
thx in adv
praveen

Moorthy,
I've the FM in my BPM. But...how can I append this to Response message as these have two different MTs?
Do you mean to say my response message should have a node for fault message data?
I'm trying to implement sth like in this blog <a href="/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client">Propagation of meaningful error information to SOAP Client</a>
To achieve FM in SOAP scenario, should I be using <b>only</b> a non-BPM receiver like a R/3 system using FM with exception as the receiver? Can this be not possible if I use BPM as receiver?
thx in adv
praveen

Fault message in synchronous send step in BPM

Hi,
When executing a synchronous send step in BPM it is possible to handle application errors (fault messages) with an exception branch. But how do you get hold of the actual data in the Fault message(faultText, faultURL, faultDetail etc) for further processing (mapping)?
Kind regards Johan

Johan,
u have to define another container element in integration process.
For that container element an Async Abstract interface has to created with falult message as the message.
Do u have the fault message defined already...
Also go through this thread.
Fault message handling in BPM
-Naveen.

Fault Messages with file to file

Similar Messages

Maybe you are looking for