SOAP Capture ((SOAP:FAULT))

Hello
Since SAP XI am consuming a web service NET. If this service has errors send a SOAP FAULT.
How it catches on SAP XI this message?

Solve problem.
I still can not solve this problem.
I have included the field to WSDL and SOAP FAULT yet so I can not get this information.
<wsdl:fault name="SolicitarOrdenPagoFault"/>
<s:schema elementFormDefault="qualified" targetNamespace="http://LarrainVial.WebServices.SAP2LV/Tesoreria">
<s:complexType name="WSSAP2LVSOAPFaultType">
<s:sequence>
<s:element name="faultcode" type="s:string"/>
<s:element name="faultstring" type="s:string"/>
<s:element name="faultactor" type="s:string"/>
<s:element name="detail">
<s:complexType>
<s:sequence>
<s:element name="message" type="s:string"/>
<s:element name="description" type="s:string"/>
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:schema>
Edited by: Claudio Enrique León Hernández on Jan 30, 2008 11:10 PM
I still can not solve this problem.
I have included the field to WSDL and SOAP FAULT yet so I can not get this information.
Edited by: Claudio Enrique León Hernández on Sep 8, 2008 9:20 PM
Edited by: Claudio Enrique León Hernández on Sep 8, 2008 9:20 PM

Similar Messages

Error capturing SOAP fault for Sync Messages

Hi
We have a Sync interface which makes a Proxy call from ECC to PI and then PI makes Soap Sync call to Web application. We are having issues when handling Exceptions. Sender is getting misleading errors in response, even though they are application errors the proxy sender is getting error like MappingObjectNotFound.
When debug the PI system, PI is truncating error info when it return the reponse.
Below is the scenario of Synchronous interface:
ECC(Proxy) -> PI(Soap Receiver Adapter) -> MasterDataApp-(Webserver)
Below is the actual response from Webserver (Extracted via TCPGW sniffer):
<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>*java.rmi.RemoteException: No Messages Found*</faultstring>
<detail>
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">hostname.com</ns1:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
But PI receives this response payload like this :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">hostname.com</ns1:hostname>
and then Sync Request mesasge fails with below error because of the unexpected response payload as shown above:
<?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>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID B0CC6B27847A368AA04F4171EF6460F4 Software Component 86524CE0304911DEAE48CC6C83461631</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID B0CC6B27847A368AA04F4171EF6460F4 Software Component 86524CE0304911DEAE48CC6C83461631</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also in the response message see this error message:
<?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>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please let me for any clues how to handle this error response.
Thanks,
laxman

Hi Laxman,
SOAP Adapter cannot handle fault responses. I understand your issue. You even want to send the errorneous response from the Webservice as a payload back to the sender. But because of application error from Webservice, you are getting an error in the response message (Mapping Not found). SOAP Adapter cannot handle application error (i.e you will not get the errorneous response in form of payload) . For details please read below:
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.
HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<m:GetLastTradePriceResponse xmlns:m="Some-URI">
<Price>34.5</Price>
</m:GetLastTradePriceResponse>
</SOAP:Body>
</SOAP:Envelope>
will result in an application response message with response payload
<m:GetLastTradePriceResponse xmlns:m="Some-URI">
<Price>34.5</Price>
</m:GetLastTradePriceResponse>
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:MustUnderstand</faultcode>
<faultstring>SOAP Must Understand Error</faultstring>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
will result in a system error message.
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<e:myfaultdetails xmlns:e="Some-URI">
<message>My application didn't work</message>
<errorcode>1001</errorcode>
</e:myfaultdetails>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
will result in an application error message with fault payload
<e:myfaultdetails xmlns:e="Some-URI">
<message>My application didn't work</message>
<errorcode>1001</errorcode>
</e:myfaultdetails>
In order to send the erroneous response as a payload to the sender, you should develop flow in below manner:
ECC(Proxy) -> PI --> ECC(Proxy)
In PI make a SOAP lookup. The response of the SOAP lookup will contain the response given by the WebService (it can be a vaid response or an application error in WebService). Now map this response to the proxy...In this way you can handle the application error msgs from webservice..
I hope this helps you...
Regards,
Rakesh Sharma

EPC Capture SOAP Request error

Hello dear experts,
I'm trying to send a simple SOAP EPC capture request to SAP OER. The request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pta="http://sap.com/xi/PTA" xmlns:stan="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader">
   <soapenv:Body>
      <pta:EPCISDocument schemaVersion="1.0" creationDate="2011-04-01T10:02:59+00:00">
         <EPCISBody>
            <EventList>
               <ObjectEvent>
                  <eventTime>2012-12-12T06:36:17Z</eventTime>
                  <eventTimeZoneOffset>+00:00</eventTimeZoneOffset>
                  <epcList>
                     <epc type="sgtin">urn:epc:id:sgtin:0000.0000.11112</epc>
                  </epcList>
                  <action>ADD</action>
               </ObjectEvent>
            </EventList>
         </EPCISBody>
      </pta:EPCISDocument>
   </soapenv:Body>
</soapenv:Envelope>
But than I'm getting an error, that I not understand:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>System Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context></context>
               <code>ABAP.PARSE_APPLICATION_DATA</code>
               <text>Error during XML => ABAP conversion: Request Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SAS261BFEA7FED17BDDAAA1 Line 19 An error occurred when deserializing in the simple transformation program /1SAI/SAS261BFEA7FED17BDDAAA1 (Der Wert '' liegt nicht im Wertebereich des XML-Schema-Typs 'decimal' oder verletzt eine der angegeben Einschränkungen. Kernel ErrorId: ST_VALIDATION_</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
Can somebody help me please?

Hi Juergen Mueller
I think on receiver side you have Proxy. so the thing is debug your inbound Proxy and you come to know where it is getting failed. You can do it by following way..
take payload which is there after mapping and test your inbound proxy in debug.
to debug use
go to sproxy.. then select your inbound proxy and click execute(F8) and provide the payload in provided window click on execute and debug the proxy..
problem is somewhere the data type is not matching or length is not matching..
Thanks,
Bhupesh

Synchronous File- Soap scenario with fault message

Hi!
I have a File to Soap synchronous scenario.
All is right when no exception is returned by the web service.
I want to use fault messages to catch thoses exceptions, so I have added fault message in message interfaces and in the mapping program in the interface mapping.
Now, when the web service return an exception like :
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
   <soap-env:Body>
      <soap-env:Fault>
         <faultcode>soap-env:Client</faultcode>
         <faultstring xml:lang="en">NOT_CREATED</faultstring>
         <detail>
            <n0:Z_WS_CREATE_WAGON.Exception xmlns:n0="urn:sap-com:document:sap:rfc:functions">
               <Name>NOT_CREATED</Name>
               <Text> does not have packaging material type and is therefore not a pack.mat.</Text>
               <Message>
                  <ID>HUSELECT</ID>
                  <Number>041</Number>
               </Message>
            </n0:Z_WS_CREATE_WAGON.Exception>
         </detail>
      </soap-env:Fault>
   </soap-env:Body>
</soap-env:Envelope>
I get the following error :
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
   <SAP:Category>XIServer</SAP:Category>
   <SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
   <SAP:P1>http://www.arcelormittal.com/radis/rad IM_RAD_to_ZWsCreateWagon</SAP:P1>
   <SAP:P2 />
   <SAP:P3 />
   <SAP:P4 />
   <SAP:AdditionalText />
   <SAP:ApplicationFaultMessage namespace="" />
   <SAP:Stack>Interface mapping http://www.arcelormittal.com/radis/rad IM_RAD_to_ZWsCreateWagon does not exist in runtime cache</SAP:Stack>
   <SAP:Retry>N</SAP:Retry>
</SAP:Error>
My mapping program for fault message is well defined (I tested it with the exception message received from the web service).
I have also refresh caches, but without success...
Can anyone help me ?
Thanks in advance,
Laurence

Hey Laurence,
A File adapter is aysnchronous u cant use for synchrous because it cant acknwlodge the response it gets or itt sends.
regarding two asynchoronus
1. file to SOAP asychn.
2. triggger the second one if SOAP has exception then pass the error from SOAP to New File.
using BPM we have to use Transportion level acknowledgments
please reward points if it helps
Regards
Sreeram.G.Reddy

BPEL PM 10.1.3.3.0 : Exception Framework not capturing Business Faults.

Hi Gurus,
I am facing a problem with exception framework of BPEL PM 10.1.3.3.0 whereby it's not capturing Business Faults thrown using throw activity.
The following is exactly what I am using:
1) Fault Policy File:
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicy version="2.0.1" id="TestPolicy" 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:coeFaults="http://test.myco.com/faults" name="coeFaults:testFault">
               <condition>
                    <action ref="ora-human-intervention"/>
               </condition>
          </faultName>
     </Conditions>
     <Actions>
          <Action id="ora-retry">
               <retry>
                    <retryCount>8</retryCount>
                    <retryInterval>2</retryInterval>
                    <exponentialBackoff/>
                    <retryFailureAction ref="ora-rethrow-fault"/>
               </retry>
          </Action>
          
          <Action id="ora-replay-scope">
               <replayScope/>
          </Action>
          
          <Action id="ora-rethrow-fault">
               <rethrowFault/>
          </Action>
          
          <Action id="ora-human-intervention">
               <humanIntervention/>
          </Action>
          
          <Action id="ora-terminate">
               <abort/>
          </Action>
     </Actions>
</faultPolicy>
2) Faultpolicy Binding which I specify in bpel.xml just after partnerLinkBindings completes :
     <faultPolicyBindings>
          <process faultPolicy="TestPolicy"/>
     </faultPolicyBindings>
3) Throw activity in my bpel process is as follows:
<throw name="TestFault" faultName="ns1:testFault"
faultVariable="FaultVar"/>
Where ns1 refers to http://test.myco.com/faults
And FaultVar is of type FaultMessage which is defined as follows:
     <message name="FaultMessage">
          <part name="payload" element="client:FaultEle"/>
     </message>
And FaultEle is of complexType as follows:
<complexType name="FaultType">
<sequence>
<element name="code" type="string"/>
<element name="summary" type="string"/>
<element name="detail" type="string"/>
</sequence>
</complexType>
Gurus, please let me know what wrong I am doing here.
Or is this a known issue in 10.1.3.3.0 ? If so, please provide me the workaround or fix.
Thanks-
Ashish.

The fault management framework catches all faults (business and runtime) for an invoke activity only.
For all other activities use the BPEL fault handler.

SOAP - XI - SOAP Error

Hi,
I am working on a scenario where a SOAP Client ( XMLSPY) sends a request to XI and XI forwards it to a web service and returns the result back to Soap Client. I am using SOAP Adapter at outbound and inbound.
I have done the following steps:
1. imported the WSDL for the web service.
2. created MI based on the WSDL.
3. Configured the agreements and determinations.
4. Generated WSDL based on the configuration objects in ID.
5. Called my WSDL in XMLSPY client.
6. I am asked to login to the XI system.
7. I get an error message back in XMLSPY:
<?xml version="1.0"?>

<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>DeliveryException</code>
                         <text><![CDATA[
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: QName is 'xmlns', but URI is not 'http://www.w3.org/2000/xmlns/' in the qualified name, 'xmlns'
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:457)
     at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:125)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:512)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:141)
          ]]></text>
                    </s:SystemError>
               </detail>
          </SOAP:Fault>
     </SOAP:Body>
</SOAP:Envelope>
The message monitoring shows:
2006-04-03 11:37:37 Success SOAP: request message entering the adapter
2006-04-03 11:37:40 Success The message was successfully received by the messaging system. Profile: XI URL: http://diamond:50500/MessagingSystem/receive/AFW/XI
2006-04-03 11:37:40 Success Using connection AFW. Trying to put the message into the request queue.
2006-04-03 11:37:40 Success Message successfully put into the queue.
2006-04-03 11:37:40 Success The message was successfully retrieved from the request queue.
2006-04-03 11:37:40 Success The message status set to DLNG.
2006-04-03 11:37:40 Success Delivering to channel: SOAP_RECEIVER_ADAPTER
2006-04-03 11:37:40 Success SOAP: request message entering the adapter
2006-04-03 11:37:42 Error SOAP: error occured: org.w3c.dom.DOMException: QName is 'xmlns', but URI is not 'http://www.w3.org/2000/xmlns/' in the qualified name, 'xmlns'
2006-04-03 11:37:42 Error Exception caught by adapter framework: QName is 'xmlns', but URI is not 'http://www.w3.org/2000/xmlns/' in the qualified name, 'xmlns'
and it also shows:
Time Stamp Status Description
2006-04-03 11:37:37 Success SOAP: request message entering the adapter
2006-04-03 11:37:40 Success The message was successfully received by the messaging system. Profile: XI URL: http://diamond:50500/MessagingSystem/receive/AFW/XI
2006-04-03 11:37:40 Success Using connection AFW. Trying to put the message into the request queue.
2006-04-03 11:37:40 Success Message successfully put into the queue.
2006-04-03 11:37:40 Success The message was successfully retrieved from the request queue.
2006-04-03 11:37:40 Success The message status set to DLNG.
2006-04-03 11:37:40 Success Delivering to channel: SOAP_RECEIVER_ADAPTER
2006-04-03 11:37:40 Success SOAP: request message entering the adapter
2006-04-03 11:37:42 Error SOAP: error occured: org.w3c.dom.DOMException: QName is 'xmlns', but URI is not 'http://www.w3.org/2000/xmlns/' in the qualified name, 'xmlns'
2006-04-03 11:37:42 Error Exception caught by adapter framework: QName is 'xmlns', but URI is not 'http://www.w3.org/2000/xmlns/' in the qualified name, 'xmlns'
The message I am sending to the XI is :
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <SOAP-ENV:Body>
          <m:VerifyAddress xmlns:m="http://www.webservicex.net">
               <m:City>Plano</m:City>
               <m:State>TX</m:State>
               <m:Zip>75024</m:Zip>
          </m:VerifyAddress>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
There is some URI conflict in both the adapters. They expect some URI format which it is not getting. I dont understand where the problem is.
Can anyone help?
Thanks,
Shubha.

Hi,
I think namespace in the URL is conflicting somewhere.
Just check with this blog-
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
Hope this helps,
Regards,
Moorthy

SOAP to SOAP scenario - XIServer:UNAUTHORIZED

Hello,
I created a scenario synchronous SOAP<>PI<>SOAP, but when I consume the WS (using soapui) this show me the next error:

<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>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:UNAUTHORIZED:
     at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:663)
     at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:447)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
     at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:428)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
     at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:462)
     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:270)
     at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
I get the url from directory (sender component):
http://server:port/XISOAPAdapter/MessageServlet?senderParty=&senderService=BS_DEMOWS_100&receiverParty=&receiverService=&interface=SI_SendSMS&interfaceNamespace=http://namespace.com/WS/SendSMS
Into de SXI_MONITOR I can see errror:
<?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>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Authorization error while sending by HTTP (error code: 401 , error text: Unauthorized)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
And in the /MessagingSystem/monitor the log is:
2011-11-16 11:42:46.56 Success SOAP: request message entering the adapter processing with user XSICONSULTOR
2011-11-16 11:42:46.561 Success Application attempting to send an XI message synchronously using connection SOAP_http://sap.com/xi/XI/System
2011-11-16 11:42:46.562 Success Trying to put the message into call queue
2011-11-16 11:42:46.563 Success Message successfully put into the queue
2011-11-16 11:42:46.564 Success Message retrieved from call queue
2011-11-16 11:42:46.564 Success Message status set to DLNG
2011-11-16 11:42:47.101 Error Received XI System Error. ErrorCode: UNAUTHORIZED ErrorText: null ErrorStack: Authorization error while sending by HTTP (error code: 401 , error text: Unauthorized)
2011-11-16 11:42:47.101 Error Transmitting the message using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:UNAUTHORIZED:
2011-11-16 11:42:47.102 Error Message status set to FAIL
2011-11-16 11:42:47.102 Error Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:UNAUTHORIZED:
2011-11-16 11:42:47.103 Error SOAP: call failed: com.sap.aii.af.lib.mp.module.ModuleException: senderChannel 2e4c634fdd973c1c9c0323846834136d: Catching exception calling messaging system
2011-11-16 11:42:47.103 Error SOAP: call failed com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:UNAUTHORIZED:
The XSICONSULTOR user has the next roles:
SAP_ALM_ADMINISTRATOR
SAP_ALM_CUSTOMIZER
SAP_SLD_ADMINISTRATOR
SAP_SLD_CONFIGURATOR
SAP_SLD_DEVELOPER
SAP_SLD_GUEST
SAP_SLD_ORGANIZER
SAP_XI_ADMINISTRATOR_ABAP
SAP_XI_ADMINISTRATOR_J2EE
SAP_XI_APPL_SERV_USER
SAP_XI_BPE_ADMINISTRATOR_ABAP
SAP_XI_BPE_CONFIGURATOR_ABAP
SAP_XI_BPE_MONITOR_ABAP
SAP_XI_CONFIGURATOR_ABAP
SAP_XI_CONFIGURATOR_J2EE
SAP_XI_CONTENT_ORGANIZER_ABAP
SAP_XI_CONTENT_ORGANIZER_J2EE
SAP_XI_DEMOAPP
SAP_XI_DEVELOPER_ABAP
SAP_XI_DEVELOPER_J2EE
SAP_XI_DISPLAY_USER_ABAP
SAP_XI_DISPLAY_USER_J2EE
SAP_XI_IS_SERV_USER
SAP_XI_MONITOR_ABAP
SAP_XI_MONITOR_J2EE
Z_PFUSER
And the profiles:
SAP_ALL
SAP_NEW
I don't know what happen, may be is a problem of configuration of PI but I don't understand what.
I hope that somebody have any idea and if you required more information I don't have problem.
Thank you in advance.
Greetings.
P.D.
I'm sorry the editor doesn't respet the tags.
--erva
Edited by: Esteban Vera on Nov 16, 2011 6:56 PM

Hi Esteban,
Increase the parameters in the Config Tool in the com.sap.security.core.ume.service service as below:
ume.ldap.connection_pool.max_size (default: 10) - change to 100
ume.ldap.connection_pool.max_wait_time (default: 60000) - change to 100000
(note 948654)
Also ensure you have maintained the correct password, which MUST be the same, for all the service users
on XI. You may check all the places it should be maintained, such as Exchange Profile, SU01, SLDAPICUST, etc..
Check the note below:
#999962 - PI 7.10: Change passwords of PI service users
And ensure that the user has the correct role as per link below:
http://help.sap.com/saphelp_nwpi71/helpdata/en/9f/d12940cbf2195de10000000a1550b0/frameset.htm
Kind regards,
Caio

SOAP to SOAP call - javax.naming.Reference error - PI 7.1

Hi friends,
In our SOAP to SOAP scenario (synchronous) , we are getting the below error in SXMB_MONI.
Error:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: java.lang.Exception: #Begin#Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object.#End#
We have not used any custom module. In both sender & receiver CC only SAP standard module is there. Also there is no interface mapping in Interface Determination step.
We are not getting this error for all messages. But, some of the messages we are getting this error.
Kindly clarify friends.
Kind regards,
Jegathees P.

Hi,
Thanks for your reply!!
My Scenario is File to SOAP to File.
Configred modules in Sender channal below:
Prcessing sequence:
Number       Module Name                                        Module Key
1..........       AF_Modules/RequestResponseBean.......1
2..........       CallSapAdapter..........................................2
3..........       AF_Modules/ResponseOnewayBean.......3
Module Configuration:
Module Key                                       Parameter Name                                       ParameterValue
1                                                        passThrough                                            true
3                                                        receiverChannel                                       receiverChannel name
3                                                        receiverService                                        receiverService name
please tell any more confiration requered.
Regards,
Ramesh

Receiver SOAP : Parsing SOAP Exception

Hello
We have a simple scenario SOAP scenario and we are calling backend service in our Receiver SOAP
It seems that issue is with the SOAP Action.
Our backend service has multiple SOAP Actions :
Endpoint is as follows
http://serverID/ABCSoftware/ABCdataexchange.asmx
The SOAP Action is given as follows
http://ABCSoftware.net/SOAPAction
We are getting the following error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: System.Web.Services.Protocols.SoapException: Server was unable to read request. ---> System.InvalidOperationException: There is an error in XML document (1, 266). ---> System.FormatException: Input string was not in a correct format. at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) at System.Xml.XmlConvert.ToInt32(String s) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read40_Item(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read141_AllocatedResourceDetails() at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer172.Deserialize(XmlSerializationReader reader) at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) --- End of inner exception stack trace --- at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle) at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters() --- End of inner exception stack trace --- at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters() at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
We appreciate your assistance with the issue.
Thanks.
Kiran

Hi Kiran
As you have multiple SOAP action. WSDL can have only one and can be used per communication channel.
Looking at your error its a XML serialization issue - exception with parser. Your XML input is not correct. If changes are made in your system / target system for the WSDL used. Reimport corrected one and try again
Thanks
Gaurav

Problem in SOAP Sender - SOAP Receiver Senario.

Hi,
I am working on SAOP Sender- SOAP Receiver Senario, i am using a standard web service.I have successfull created the senario and tested in the Test Configuration in Integration Directory. The problem occurs when i expose my sender interface as a Web Service and use Altova XmlSpy to send the SOAP Request, i am getting an HTTP error. Also it could be great if you could define steps required in Integration Directory -> Tools -> Define a Webservice.. the valued that should be inserted in the URL and other values to complete the Wizard
I am using this URL:- http://host:port/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>
And when i use the default URL :- http://host:port/sap/xi/engine?type=entry i don't get an HTTP error, the message goes till the receiver determination and Says Sender Not found.
Looking forward to ur Guidance.
Harpreet

Hi Peter,
I have verified the name of the server and port, there is no problem in it.
Here is the detailed error:-
<?xml version="1.0"?>

<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>CPAException</code>
                         <text><![CDATA[
com.sap.aii.af.service.cpa.CPAException: invalid channel (party:service:channel) = :
     at com.sap.aii.af.mp.soap.web.MessageServlet.getChannel(MessageServlet.java:464)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:400)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:207)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
          ]]></text>
                    </s:SystemError>
               </detail>
          </SOAP:Fault>
     </SOAP:Body>
</SOAP:Envelope>
Thanks !!
Harpreet

I am trying SOAP to SOAP scenario an i am getting the following error

HTTP operation 'POST' could not be performed on URL
'/XISOAPAdapter/MessageServlet?channel=:BS:CC'due to an error :The connection with the server was terminated abnormally.
Can some one help me out , really urgent

Hi,
You could give more data.
I assume that you have SOAP<>XI<>SOAP and the problem its in the communication SOAP-->XI
Can you give us the exception that you obtain in SXB_MONI?
The error can be the error signed by Matias or another internal error in the service.
Regards.

** SOAP to SOAP call - HTTP 404 not found - invalid content type

Hi friends,
We have one scenario SOAP to SOAP call. It is synchronous interface. We are calling the WSDL.
For some of the messages (not all), we are getting the error in SXMB_MONI
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found
In the sender & receiver SOAP communication channel also, same error : SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found
Friends, this error is not coming for all messages. For some of the messages it is coming. For example,
10:50 - Message Processed Successfully
10:54 - Message Processed Successfully
10:59 - Error
11:05 - Message Processed Successfully
By looking threads and blogs, I implemented MessagesTransformBean in the receiver CC and added the parameter Transform.ContentType as 'text/xml;charset=utf-8'.
After implementing this also, error is coming for some of the messages.
Can you kindly clarify friends, what could be the problem?
Kind regards,
Jegathees P.

I'm in agreement with Stefan...
If the problem is intermittent then the system is overloaded at certain times. You would probably need to do some JVM analysis to see the resource usage & look at increasing the memory.
Regards, Trevor

Response from PI in SOAP to SOAP Scenario

Hi,
My scenario is Soap to SOAP sending purchase orders. they want acknowledgement from PI whether PI received the message or not in the form of SOAP response.
sender system not expecting the response after the message processing in receiver system, they are expecting the response when PI receives message from them.
As any way they receive HTTP200 OK acknowledgement is it necessary that to send the SOAP response from PI by developing BPM?
Is it a good way of doing it?
Is any other way of doing it?
Your suggestions will be helpful to me.
Thank you.
Santhi.

Hi Santhi,
Please refer to SAP Note 856597 - SOAP Adapter FAQ Question number 2
2. Sender Asynchronous Calls
o Q: What are the correct sender options for asynchronous calls?
When the client sends a SOAP message and checks if the response is
an HTTP 200 response message with an empty soap envelope or an HTTP
202 response message with no content, the quality of service with
AtLeastOnce can be realized. In this case, the client must resend
the message until such a successful response is returned. When the
message successfully accepted by the adapter, an HTTP 200 response
with an empty SOAP envelope or an HTTP 202 response message with no
content is returned.
You don't have to do anything. When an async message is sent, PI will either reply with a 200 with an empty SOAP Envelope or an HTTP 202 with no content . That will serve as your acknowledgement.
Regards,
Mark

SOAP to SOAP BPM scenario

Hi Experts,
Could you please tell me, how to do SOAP to SOAP scenario using BPM?
SOAP -> XI -> BPM ( Inside BPM two more SOAP Adapter call) -> SOAP.
1. Pass the request thro' SOAP to BPM
2. Call first SOAP Adpter.
3. Response of the first SOAP will be the input for the next SOAP adapter
4. Call second SOAP adapter.
5. Return the SOAP response
Regards
Sara
Message was edited by:
        Sara D

Message Interface
1. MI_SEND_SOAP_OUT           - (Out,Asyn : MT_BPM_SOAPRequest)
2. MI_SEND_SOAP_IN          - (In, Asyn : MT_BPM_SOAPResponse)
3. MI_BPM_Req_ABS_OUT          - (Abs,Asyn : MT_BPM_Receiver_SOAPRequest)
4. MI_BPM_Req_ABS_IN          - (Abs,Asyn : MT_BPM_Receiver_SOAPResponse)
5. MI_WS1_Service_ABS          - (Abs, Synch : OutMessage : MT_BPM_WS1_Request InMessage:MT_BPM_WS1_Response)
6. MI_WS2_Service_ABS          - (Abs, Synch : OutMessage : MT_BPM_WS2_Request InMessage:MT_BPM_WS2_Response)
Message Mapping
1. MM_BPM_SOAPRequest_To_BPM_RecSOAPRequest ( Source: MT_BPM_SOAPRequest Target :MT_BPM_Receiver_SOAPRequest)
2. MM_BPM_RecSOAPRequest_To_BPM_WS1Request ( Source: MT_BPM_Receiver_SOAPRequest Target :MT_BPM_WS1_Request)
3. MM_BPM_WS1Response_To_BPM_WS2Request     ( Source: MT_BPM_WS1_Response Target :MT_BPM_WS2_Request)
4. MM_BPM_WS2Response_To_BPM_RecSOAPResponse( Source: MT_BPM_WS2_Response Target :MT_BPM_Receiver_SOAPResponse)
5. MM_BPM_RecSOAPResponse_To_BPM_SOAPResponse( Source: MT_BPM_Receiver_SOAPRespons Target :MT_BPM_SOAPResponse)
Could you please tell me, whether the above objects are correct for this scenario?
Regards
Sara
Regards
Sara
Message was edited by:
        Sara D
Message was edited by:
        Sara D

File to SOAP and SOAP to File (Synchronous)

Hi,
Can anybody advice me how to do the File to SOAP and SOAP to File with Synchronous call.
Thanks,
Naidu.

Hi,
Use this blog
RFC -> XI -> WebService - A Complete Walkthrough (Part 1)
and create an inbound synchronous interface for soap receiver structure. provide request and response structure in it.
Thanks!

SOAP Capture ((SOAP:FAULT))

Similar Messages

Maybe you are looking for