Accessing the SOAP fault received by OSB Service Call Out

I have a proxy service with multiple OSB service call outs, which access a backend server via SOAP.
If the backend server returns a fault, the proxy service' exception handling kicks in and the exception handling flow is triggered.
That flow provides a variable 'fault', which holds the OSB fault information with the BEA fault code.
The variable holding the service call out response (to which I assume the backend servers fault is written) is not available in the exception handling flow.
I have multiple service call outs in my flow, all writing their response to different variables.
Is there any way to access the fault received by the service call out? Is there any variable available in the exception flow, to which that information is written?

Is there any way to access the fault received by the service call out?Please refer -
Re: Error Handling OSB
Regards,
Anuj

Similar Messages

OSB Service Call Out without soap envelope

Can we do a service call out without any soap envelope wrapped.
Example if my message is <Test>test</Test>
it should not wrap it like
<soapEnv:Body xmlns:soapEnv="http://schemas.xmlsoap.org/soap/envelope/"><Test>test</Test></soapEnv:Body>in request part of service call out.
My calling service is WSDL based proxy and called service is ANY XML Proxy Service

indeed, I have done my tests and it proved the same: whatever you post to a AnyXML service, OSB will first wrap it into a SOAP Envelope / Body and then pass it to the Message Flow.
After all it makes sense, the Interface of a Proxy Service has nothing to do with its Implementation....
a SOAP proxy service is implemented exactly like a AnyXML proxy service as far as the $body is concerned (maybe I have said an enormous BS!)
Only $operation would not be populated - I would expect. Correct me if I am wrong.

OSB : Service Call out

Hi,
Can anyone tell me what is the basic difference between configure SOAP body and configure PAYLOAD in service call out option? Any examples / use case?
Thanks,
Bhaskar
[I will mark the question as answered, once got the reply.]

Hi Bhaskar,
With Configure SOAP Body you use $body directly, with Configure Payload you can use different variables... Also, Configure Payload does NOT support SOAP-RPC encoded... I've never came across an use case where I had to use payload...
There is a good table explaining what to use when here...
http://docs.oracle.com/cd/E28280_01/dev.1111/e15866/ui_ref.htm#CACGDEAC
Also, check these...
http://docs.oracle.com/cd/E28280_01/admin.1111/e15867/proxy_actions.htm#OSBAG1124
http://docs.oracle.com/cd/E28280_01/dev.1111/e15866/ui_ref.htm#i1291067
Cheers,
Vlad

How to view the SOAP message in a web service call + Urgent

Hi All,
Iam trying to test a web service call(Iam using CXF). But I need to view SOAP message sent to web service or need to debug the web service call. Please help me on this regard with example.

Yes. to find any tcp monitor, define a listen port number, task host and port number, changing your request to listen post, then you can monitor TCP/IP like
HTTP/1.1 200 OK
Set-Cookie: JSESSIONID=7A00BD65EF7516AD8947359A25C4D98B; Path=/ComponentName
Content-Type: text/xml;charset=utf-8
Date: Wed, 20 Oct 2004 15:45:03 GMT
Server: Apache-Coyote/1.1
Connection: close
<?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>
<ns1:testObjectResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:ComponentName">
<testObjectReturn href="#id0"/>
</ns1:testObjectResponse>
<multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:MyObject" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:ComponentName">
<name xsi:type="xsd:string">Set Name</name>
<value xsi:type="xsd:string">set Value</value>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
Lixin

Catching and rethrowing a SOAP Fault from an OSB 11g Proxy service

Hello,
We have a chain of proxy services (that last one of which calls a business service) in our 11.1.1.6 OSB project. At one of the lower levels, we successfully throw a fault like this:
<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Fault xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
    <soap:faultcode>SOAP-ENV:Client</soap:faultcode>
    <soap:faultstring>Non-Existent User</soap:faultstring>
    <soap:faultActor>Client who consumed this Web Service operation</soap:faultActor>
    <soap:detail>
      <sc:UserNonExistentFault xmlns:sc="http://xmlns.sc.com/Services/V1">
        <sc:CustomerNumber>12345</sc:CustomerNumber>
      </sc:UserNonExistentFault>
    </soap:detail>
</soap:Fault>
</soapenv:Body>
In the proxy service which calls this proxy service, I tried to catch this fault in an Error Handler so that I could confirm that it's available for me to re-throw back up the chain. Curiously, the proxy service which calls that proxy service cannot see that fault. But rather it sees what appears to be an OSB-overridden fault:
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380000</con:errorCode>
<con:reason>com.bea.wli.sb.pipeline.PipelineException</con:reason>
<con:details>
    <err:ErrorResponseDetail xmlns:err="http://www.bea.com/wli/sb/errors">
      <err:response-metadata xsi:type="sb:SBResponseMetaDataXML" xmlns:sb="http://www.bea.com/wli/sb/transports/sb" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <tran:headers xsi:type="sb:SBResponseHeadersXML" xmlns:tran="http://www.bea.com/wli/sb/transports"/>
        <tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">1</tran:response-code>
        <tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">utf-8</tran:encoding>
      </err:response-metadata>
    </err:ErrorResponseDetail>
</con:details>
<con:location>
    <con:node>PipelinePairNode</con:node>
    <con:pipeline>PipelinePairNode_request</con:pipeline>
    <con:stage>GetCustomerByNumber</con:stage>
    <con:path>request-pipeline</con:path>
</con:location>
</con:fault>
I have tried printing out the values of $body, $fault, $outbound and $inbound from the calling proxy service's Error Handler just to see if our <sc:UserNonExistentFault> is nested anywhere therein. Unfortunately, it is nowhere to be found.
How can we force OSB to NOT override our faults with OSB-framework faults and, instead, just throw our custom fault all the way up the chain and back to the consumer?
Thank you,
Michael

I think I figured this out.
In proxyService-2, build the <soap:Fault> and assign it to the body, then Reply with Failure (as you mentioned above).
When proxyService-1 receives this, it will still be in the $body variable. But the $fault variable is now populated with a BEA-38000 error. It seems that as long as the $fault variable has data in it, then the OSB system will throw that instead of my fault (ignoring the <soap:Fault> I put into the body).
So what I did was to Delete the $fault variable in the error handler of proxyService-1, then Reply with Failure (again).
It would seem as if the inner workings of OSB has some logic like:
if $fault is not null, throw the BEA-####### fault. Otherwise, return the contents of the $body.
By removing the fault, I effectively got to that "else/otherwise" condition.
Of course, the Reply with Failure is still needed to ensure that an HTTP 500 error is passed with the fault (per the SOAP specification).
Cheers!
Michael

Dynamic Invocation: Error The SOAP PA receives a SOAP Fault from SOAP serve

Hi All,
I am trying to run the sample code "Dynamic Invocation of Oracle9i Web Services using Oracle UDDI registry"
I was able to run the web services, publish them, and inquiry them using local UDDI registry.
However, while invoking any method provided by the web services using the inovk method I get the following error
oracle.j2ee.ws.client.WebServiceProxyException: Invocation failed 5,100: The SOAP PA receives a SOAP Fault from SOAP server
Can anybody help me please?
Regards,
S.Al Shamsi

It looks like the problem is occuring on the server side. I guess you have included the stacktrace from the client, can you get hold of the server side stacktrace?

How to send the SOAP Fault Message to the Web Service Consumer

Hi,
I have configured SAOP to Proxy Syncronous Scenario in PI 7.1 and using XML Validation in Adapter Engine to Validate the Structure of the Message Payload.The scenario is working fine.When some of the Filed's Length increses the maxLength specified in the Data Type . We are getting the Following 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.MessageFormatException: XML Validation for payload with root element name MT_Out_CustomerMaster_FPMReq , target namespace http://Pegasystems.com/I06_Customers Failed!Errors Encountered During Parsing
1.cvc-maxLength-valid: Value '123456789' with length = '9' is not facet-valid with respect to maxLength '8' for type 'null'.
2.cvc-type.3.1.3: The value '123456789' of element 'CompanyCode' is not valid.
3.cvc-maxLength-valid: Value 'asdf' with length = '4' is not facet-valid with respect to maxLength '1' for type 'null'.
4.cvc-type.3.1.3: The value 'asdf' of element 'OperationType' is not valid.
     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1164)
My question is How does the Web Service Consumer can handle this Soap Server Error in the SOAP Fault.Or How can we provide a specific information like 'The value '123456789' of element 'CompanyCode' is not valid.It exceeds the Maximum Length'.
I read this /people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client blog .Where it is mentioned that the Web Service Consumer can handle while calling the Web Service.Is there any other solution?
Kindly appreciate your help.

Thank You Stefan for your kind reply.
So you mean to say if we use the XML Validation .we cannot provide proper error information to the calling Web Service Consumer .And While calling a Web Service they cannot Extract the Exact Message in the Text Filed(<text>) present under the Detail Element (<detail>) in the <SOAP:Fault> node. as
<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: XML Validation for payload with root element name MT_Out_CustomerMaster_FPMReq , target namespace http://Pegasystems.com/I06_Customers Failed!Errors Encountered During Parsing
1.cvc-maxLength-valid: Value '123456789' with length = '9' is not facet-valid with respect to maxLength '8' for type 'null'.
2.cvc-type.3.1.3: The value '123456789' of element 'CompanyCode' is not valid.**
3.cvc-maxLength-valid: Value 'asdf' with length = '4' is not facet-valid with respect to maxLength '1' for type 'null'.
4.cvc-type.3.1.3: The value 'asdf' of element 'OperationType' is not valid.
That is why we have to use the Fault messages and Field Lengths has to be Validated in the Server proxy.
Please Correct me If I am wrong.

Apex_web_service.make_request throws ORA-29273: HTTP request failed. How to get the soap fault XML?

I am trying to call a web service using apex_web_service.make_request function.
It works fine when all the parameters are correct. However, when something is wrong in the request XML, it throws an exception instead of returning the soap:fault message:
ORA-29273: HTTP request failed
ORA-06512: at "SYS.UTL_HTTP", line 1369
ORA-29269: HTTP server error 500 - Internal Server Error
ORA-06512: at "APEX_040200.WWV_FLOW_WEBSERVICES_API", line 130
ORA-06512: at line 37
I need to get back the soap:fault and parse it to display a proper error message to the users (e.g. what was wrong with the input), yet the call throws an exception instead of returning it.
I am trying the exact same request from soapUI and it returns me the soap:fault below:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
   <soap:Body>
      <soap:Fault>
         <soap:Code>
            <soap:Value>soap:Receiver</soap:Value>
         </soap:Code>
         <soap:Reason>
            <soap:Text xml:lang="en">Fault occurred while processing.</soap:Text>
         </soap:Reason>
         <soap:Detail>
            <ns1:RegisterFault xmlns:ns1="http://www.exchangenetwork.net/wsdl/register/1">
               <description xmlns:ns2="http://www.exchangenetwork.net/wsdl/register/1">The security token has expired.</description>
               <errorCode xsi:type="ns2:RegisterErrorCode" xmlns:ns2="http://www.exchangenetwork.net/wsdl/register/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">E_TokenExpired</errorCode>
            </ns1:RegisterFault>
         </soap:Detail>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>
How do I get this back from APEX?
Thanks!

Hi,
   I've just run into this.
   If the webservice returns a fault, such as:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>INVALID_REQUESTER_INFO</faultstring></soap:Fault></soap:Body></soap:Envelope>
   then the user gets presented with an unfriendly error message and there's no chance to output a more friendly one.
   The response above is seen when testing the webservice, when run from the Form/Report page, we get something like:
soap:ServerINVALID_REQUESTER_INFO
Contact your application administrator.
OK
   When OK button is clicked everything is rolled back and we don't even get the fault XML.
   It would be good if Apex could be optionally set to not give the unfriendly messages, so that we could code such a message ourselves.
   Unless anybody has a workaround for this, I guess that I'll have to see if I can code this in PLSQL.
Regards,
Chris

How to send back the soap fault message without details tag to the sender

Hello Expert,
Is it possible to send the soap fault message(fault String element value) without details tag as shown below to the sender in synchrounous scenario.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soapenv:Body>
          <soapenv:Fault>
               <faultcode>soapenv:Client</faultcode>
               <faultstring>autorizarComprobanteRequest.comprobanteCAERequest.arrayOtrosTributos.otroTributo(1).codigo - El Código de Tributo es obligatorio.</faultstring>
               <detail></detail>
          </soapenv:Fault>
     </soapenv:Body>
</soapenv:Envelope>
I have to send the faultstring element value in one of the element in response message back to sender? Is it possible using BPM?The above fault response does not have a fault payload (no detail element) and would result in a system error message.So how to handle this?
If yes .Please tell me the BPM design
faultstring value will be dynamic.
Thanks in advance

Thanks Yzanagi,
I have gone through the index.htm file.
In my scenario that is RFC -PI-soap(using http(Axis) protocol).when the webservice provider is sending the soap fault as.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soapenv:Body>
          <soapenv:Fault>
               <faultcode>soapenv:Client</faultcode>
               <faultstring>autorizarComprobanteRequest.comprobanteCAERequest.numeroComprobante - El Número de Comprobante debe ser mayor o igual a 1</faultstring>
               <detail></detail>
          </soapenv:Fault>
     </soapenv:Body>
</soapenv:Envelope>
In PI sxmb_moni it is converting to the error (system not application error)as shown below when using receiver soap adapter with https(Axis) transport protocol and Message protocol:Axis.
<?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:P1>
<SAP:P2></SAP:P2>
<SAP:P3></SAP:P3>
<SAP:P4></SAP:P4>
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: autorizarComprobanteRequest.comprobanteCAERequest.numeroComprobante - El Número de Comprobante debe ser mayor o igual a 1.</SAP:AdditionalText>
<SAP:Stack></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
As my requirement was (I have mentioned in my first question) that I want to pass
SAP:AdditionalText tag
value back to sender in one of the elements of response message payload or handle using fault message mapping if this error could be converted to application error and map to the RFC exception but unfortunately which is not possible even using AXIS adapter.
so other option to inform the sender RFC is mentioned here http://help.sap.com/saphelp_nw70/helpdata/en/22/0425e0488911d189490000e829fbbd/content.htm
but while handling the SYSTEM_FAILURE exception from PI at sender in report program and displaying the msg variable ,I am not getting complete error message..It is getting truncated.Is there a limit to the no of character the msg variable contains which is set by system.Even if we declare msg variable with more length(for example char length 500) it is just displaying part of the error message from PI.
Any Idea to read complete system error message from PI in report program at RFC sender..
Kind Regards,
Kubra fatima

How to catch SOAP fault from PeopleSoft web service

I am trying to catch the SOAP fault thrown from pplsoft. Currently we get only runtime error if we call pplsoft web service thru ESB. Fault is not being propagated back to route ESB.
thanks for your help

Have you managed to solve this issue? BPEL does allow you to do this.

JWSDP1.4 Access the SOAP Message in an RPC server

hi i am new to web services... i have created RPC using JSWDP 1.4.
I used the wscompile and wsdeploy tool to create the WSDL and server side of the web service.
but because of a requirement change now i have to get the SOAP message Header and verify the client details (log who is using my service). How can i access the SOAP header??

Make a backup then edit this file,
TomcatRoot: ./shared/classes/com/tarantella/tta/webservices/client/apis/Resources.properties
Edit all locations to point to https://localhost:443

Not able to access the links to Planning and Shared Services

Hi,
I am trying to access the links to Planning and Shared Services but I get the following error message.
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
I tried to restart all the services on all the servers and also restarted the servers but it didn't work.
Please let me know how to fix this issue. Also please let me know where else can I find the logs to the errors.
Thanks.

The logs would be a good place to start, if you are not sure where to look post your OS and planning version.
Cheers
John
http://john-goodwin.blogspot.com/

Route node and Service Call out in OSB

In OSB for a composite Proxy service (PS) that has to call 3 external services in sequence- we make service call out for 1st and 2nd external services and for invoking the last external service we can use route node.
Here technically PS is making web service calls to all the three external services. For the first two OSB uses service call outs and for the last one, route node is used.
What is the difference in service callout and route node in invoking an external service?
If route node is better in any ways why can't OSB come with route node type message flow action for all external service calls?
Thanks

HI there,
I have the same scenario as yours, I have to call 3 external services using Service Callouts and i have no idea how to use service callouts, how to and what to configure in SOAP body OR Payload parameters.
I have to call one service and then the response of the 1st service , i have to pass it as a request to the 2nd service, so on.
Can u please share with me how i can do it and what will be the best approach for that.
Thanks and Regards
Piyush Kapoor

Change timeout in Service call out (OSB)

I have a proxy service P1 that invoke a other Proxy Service P2 throught a service call out component.
The proxy service P2 route to a business service (biz). This business service timeout is 10 s.
It's possible change the timeout in service call out in OSB? How do it?
I need change the P1 proxy service to invoke the P2 with timeout of 1s instead of 10s (business service - biz).

i assume you mean how you can change it on runtime from within the proxyservice flow, and not from the default configuration like vladodias mentioned
i checked some settings in the transport headers but couldn't find anything to overrule this on runtime
HttpOutboundPropertiesType has a connection-timeout element, but don't see a transport header option to overrule this when routing to a http transport bs service
maybe you could use the *other option there and add some other http header timeout setting which will be interpreted by the server which hosts the server...but this is all just a bit of guessing

Will Service call out return an exception with an object embedded in it

Hi,
I have a service callout in a request pipeline.Service will throw an exception with a custom object embedded inside the exception.When i see the response $fault in the service error handler, i dont see the object.Is this something which can be done or not?if yes then guide me through it.

Hi,
If you invoke the service call out, and it returns a soap fault (make sure that it returns http 500), so you should be able to access the custom fault element inside $fault/con:details/con1:ReceivedFaultDetail/con1:detail
Are you sure that your webservice is returning the fault properly?
Are you not raising a new error after getting the response in the error handler, right?
Regards,
Fabio Douek.

Accessing the SOAP fault received by OSB Service Call Out

Similar Messages

Maybe you are looking for