In BPEL, how to create a SOAP fault?

I am using JDeveloper 11.1.1.6. I need to send SOAP fault by setting faultstring, faultcode and faultactor. How can I define asoap fault and send?

Thank you very much for your response. Is there any other module/component I can able to access SOAP fault and set my own faultcode, faultstring and fault actor? Presently, when a custom fault is sent from BPEL, it is setting fault code as name of the fault (with namespace: ex: ns0:ProcessFault). Instead of that I want to set a specific fault code (like 100) and appropriate fault actor and fault string. Or is it possible using java code in BPEL SOAP fault can be created and set appropriate values?
If not is it available in OSB? (I have not looked OSB yet). Thanks for you response.

Similar Messages

How to catch a SOAP fault

Hi All,
I have a ISU to web service, PROXY to SOAP sync interface. I am getting following as response.
How can I get this into Fault message mapping?
I have followed these blogs:
Fault Message Types - A Demo (Part 1)
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI
<?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: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Validation constraint violation: data type mismatch in element 'extraOverhead'</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
Aravind

Hi,
Can you please elaborate exactly what you are trying to achieve.....are you trying to display this error message to the user of client proxy...If so, You can catch the exceptions in client proxy using the two standard exception classes.
CATCH cx_ai_system_fault .
CATCH cx_ai_application_fault .
and in the catch block you can receive the error message and display it. The code will look like this
DATA : sys_fault TYPE REF TO cx_ai_system_fault,
             text      TYPE string.
CREATE OBJECT sys_fault.
CALL METHOD sys_fault->get_text
    RECEIVING
      result = text.
WRITE : /10 'System Fault ', 30 text.
Regards,
Priyanka

How to create Inbound SOAP With Attachments

Hi All,
Does someone know how to create an Inbound SOAP Message (from SAP XI to a Business System) with attachments?
We get an Idoc from a SAP R/3 system and transform this Idoc to an other XML format messages, but we want this message as an attachment and not as the payload in the SOAP Envelope.
We tried the PayloadSwapBean module, but we don't have an attachment to swap with, but maybe we used the wrong paramaters.
Thanks,
Frank

Hi Stefan,
Does this quick response mean I challenged you?
Our scenario is that we send an IDoc (ORDERS05) from our R/3-backend-system to XI (3.0/SP15). In an integration process (A/S-bridge) we transform this IDoc to an UBL-Order XML-message, and we want to send this XML-message as an attachment to a (synchronous) SOAP-call to a vendor. Like I said, despite the SAPHelp-content, we don't get this working. Whatever we try, the UBL-Ordermessage is contained in the SOAP-body.
What makes it even more strange, is that XI itself is based on the SOAP-with-attachments-standard...
So, any help is much appreciated!
Regards, Fred

How to create a SOAP body based on a Serializable Object?

Hello,
I have a serializable object such as this one
        HeaderSection header = new HeaderSection();
        RequestName requestName = new RequestName();
        requestName.setActivityName("this is an activity");
        NNSVMessage nnsvMessage = new NNSVMessage();
        nnsvMessage.setHeaderSection(header);
        nnsvMessage.setRequestSection(request);
        nnsvMessage.setResponseSection(response);I create a SOAP message using SAAJ API
        SOAPMessage message = messageFactory.createMessage();
        SOAPPart soapPart = message.getSOAPPart();
        SOAPEnvelope envelope = soapPart.getEnvelope();
        SOAPBody body = envelope.getBody();
...How can I stuff this object into the SOAP body?
Thanks,
Mustafa

Hi Saleem,
Herewith an example:
        Dim oDoc As SAPbobsCOM.Documents
        oDoc = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oOrders)
        oDoc.CardCode = "530010"
        oDoc.DocDate = Date.Now
        oDoc.DocDueDate = Date.Now
        oDoc.DocType = SAPbobsCOM.BoDocumentTypes.dDocument_Service
        oDoc.Lines.ItemDescription = "Line 1"
        oDoc.Lines.Price = 100
        oDoc.Lines.VatGroup = "O1"
        oDoc.Lines.AccountCode = "0000090000"
        oDoc.Lines.Add()
        oDoc.Lines.ItemDescription = "Line 2"
        oDoc.Lines.Price = 200
        oDoc.Lines.VatGroup = "O1"
        oDoc.Lines.AccountCode = "0000090201"
        If oDoc.Add <> 0 Then
            MessageBox.Show(oCompany.GetLastErrorDescription)
        Else
            MessageBox.Show("Added")
        End If
Hope it helps,
Adele

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 get the SOAP Fault XML?

Can anyone describe how we can get the full XML that is send
when the server returns a SOAP fault?
Thanks
Andrew

I think the problem is that faults return a 500, and that
makes flex quit looking. If you can make the server return say a
200, then you can get the actual exception. Search the archives on
flexcoders, this was discussed extensively there.
Tracy

Question: How to create a SOAP service?

I am working on a POC for evaluation of Aqualogic Service Bus 2.5. I am facing a difficulty in the following aspects.
1. I have a client on my system which reads a data service from DSP and gives a custom object in return.
2. There is a client on another system which has to use the returned custom object through a remote procedure call to my function.
3. I dont want to create a web service just for this purpose.
4. So I want that the object will be communicated to the other client in the form of a SOAP message and generate a response SOAP message which my first client will receive
I believe that Aqualogic Service Bus configuration of SOAP service will help me out in this case but i am not finding a way of doing this. I have been able to successfully communicate with web services configured in ALSB.
I went throught the document
http://e-docs.bea.com/alsb/docs20/consolehelp/businessServices.html
But it doesnt have the information of how to go about creating a soap service and configuring it in ALSB and then consuming it in a step by step manner. Please give me some techniques to achieve this.

First, try using the documentation here instead.
http://e-docs.bea.com/alsb/docs25/consolehelp/index.html
I did something similar with SOAP xml.
1) I had to create a wsdl file based on the incoming xml and
2) import it into ALSB (admin console). Creating the wsdl was the most difficult part for me.
3) Then you can create a proxy service (admin console) that uses the wsdl, and it'll allow accessing the proxy service as a web service.

How to create one soap interface with two soap action?

Hi,
I need to create one SOAP Interface with two or more webmethods (soap action), for example:
Interface: MI_Outb_User
Webmethods: createUser, searchUser, deleteUser.
Can anybody helpe me?

Hi Santos,
I assume you will use one action at a time and depending upon certain condition you want to invoke the webservice and the corresponding action. If this is yes, then please check michaels reply in this thread:
How can I handle serveral soap actions
or see stefans reply:
Re: Is SOAP Adapter Action field can contain 2 or more "SOAP Actions"
If this is not, then please ignore it.
Regards,
---Satish

How to return a Soap Fault from a business process

I'm trying to re-implement an existing web service in WLI that can return soap
faults to clients when business errors occur while processing a request. Is this
possible to do with WLI, and if so can someone please point me in the right direction?
thanks...

If your JWS can throw a SOAPFaultException, that should return a SOAP fault to
the client.
"Michael Hanes" <[email protected]> wrote:
>
I'm trying to re-implement an existing web service in WLI that can return
soap
faults to clients when business errors occur while processing a request.
Is this
possible to do with WLI, and if so can someone please point me in the
right direction?
thanks...

How to raise a soap fault for "business errors"

Hi folks,
I have a scenario.
sync
SOAP<->PI<->RFC
If the update to ECC failed then the RFC response will give back an Error Code in one of the fields, another field will indicate the error description,
I will need to raise a soap fault with this error code and description in the soap fault.
Note , there is only Req and response in the RFC, no fault in the RFC,
Please advice me on this.
Thanks,
Hank

Hi,
I think this could be resolved using multi-mapping.
(RFC)Response - (SOAP) Response
-(SOAP) Fault
In the response mapping, we have RFC response as the source structure , SOAP Response and SOAP Fault as the target structures.DO the validation for ErrorCode and Error Validation in the mapping. Soap Response structure would be generated for succesful RFC response. Soap Fault structure would be generated in case of RFC response containing error code and error message.
Hope it works.
Regards,
Swetha.

How to create WSSE soap header?

I need to connect to a web service and it requires WSSE security namespace in the soap header. Does anyone know to create it using Java in the soap header using WSSE security namespace?
Thanks
I'm using Jdeveloper 11g

Doesn't jdeveloper has a wizard in creating a template code for the subject task.

Handling SOAP faults

hello,
I created a java control which calls an external webservice. How do you handle
SOAP fault messages coming back from the webservice?
Weblogic just throws an java.lang.reflect.UndeclaredThrowableException since it
cannot parse the expected XML message.
For example, when I call Logon() via the java control. The WebService should
reply with a LogonResult object(in xml format). However, if there's an error,
the WebService returns a SOAP Fault message. Since this fault message is not
in the format of the expected LogonResult xml schema, weblogic throws an error
(since it cannot create the LogonResult object) and the caller just receives the
UndeclaredThrowableException without knowing any of the contents within the SOAP
Fault.
I'd like to be able to send back the SOAP fault content back to the calling function.
I've tried throwing an exception from the java control handler, but it gets swallowed
up by the SOAP Handler so I still get an exception with no content.
any info is appreciated.
thanks,
Tom

Hi,
Do you get answer for that?
I had similar problem and solved this in this way:
In this java.lang.reflect.UndeclaredThrowableException handler is possible to get also SoapFault back:
catch (java.lang.reflect.UndeclaredThrowableException e){
RemoteException re = (RemoteException).getUndeclaredThrowable();
ServiceControlException sfe = (ServiceControlException)re.getCause();
SoapFault fault = sfe.getSoapFault();
XmlObject[] objs = fault.getDetailContents();
// more procssing here to get Soap detailed error
Maybe this helps.
rgrds,
H

Throw a new soap fault

Hello to Everyone,
I'm a OSB 10.3.1 newbie, and i want to throw a new soap fault.
The problem is that the error code & error message comes in the body of the response message (not in a soap fault). From this response i capture the errors (code & message) and assign them to context variables.
How can i throw a new soap fault with the values of the context variables?.
Thanks

Hi,
The body of the response is in fact where you would create the soap fault (for SOAP services of course). The only trick is that the child element of the body variable must be a <soap-evn:Fault> element.
What I've done in some projects is define an XQuery transformation to create the soap fault. The soap fault has a detail element where you can add your custom exceptions (those defined in your WSDL). As input arguments to the XQuery transformation you can send the error code and message that come in the fault variable plus any other arguments you might want to add.
For example (I'm omitting the namespace declarations, variable declarations that the transformation should have):
declare function xf:createSOAPFault($errorCode as xs:string, $errorMessage as xs:string, $operationId as xs:string)
    as element(env:Fault) {
<env:Fault>
    <faultcode>env:Server</faultcode>
    <faultstring>{ $errorMessage }</faultstring>
    <detail>
        <ns0:MyException>
            <ns0:operationId>{ $operationId }</ns0:operationId>
            <ns0:errorCode>{ $errorCode }</ns0:errorCode>
            <ns0:errorMessage>{ $errorMessage }</ns0:errorMessage>
        </ns0:MyException>
    </detail>
</env:Fault>
};If your client is using JAX-WS for example, you could do something like this:
try {
   // invoke ws
} catch (MyException e) {
    log("Operation ID: " + e.getOperationId() + ", Error Code: " + e.getErrorCode() + ", Message: " + e.getErrorMessage());
}

How to expose a SOAP web service from HCP

Hello All,
Currently I am trying to create a SOAP web service within a HCP Java application to allow backend systems to consume data stored in HCP.
This is the planned scenario:
1. Create data in HCP - therefor I am using JPA and a oData Model.
2. Backend uses web service to consume data from HCP - with this point I do have some problems.. I do want to create a SOAP web service in order to achieve this.
Is there an easy way to create a SOAP web service in HCP? There are many tutorials in the internet of how to create a SOAP web service in 20 sec´s, but non of these helped me. I do was able to consume a SOAP web service in HCP coming from the ByD, but the other way around seems pretty complicated...
Can I make use of the Eclipse functions to create a web service? (New --> Other... --> Web Services --> Web Service and than choose the Button up Java bean Web Service type)
Have any of you some coding snippets that would probably help me out?
I have unsuccessfully tried to use the @WebService, @SOAPBinding, @WebMethod notation in my java classes...
Thank you,
Swen

Hello Nedelcho,
Yes. All the required jar files are in the lib directory.
Currently I am able to create a web service locally.
But when I deploy that to the cloud server my JPA service is not working any more.
Receiving the following error message:
<?xml version='1.0' encoding='UTF-8'?><error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code/><message xml:lang="en">javax.naming.NamingException: Error while attempting to resolve reference [Root exception is javax.naming.NamingException: Cannot create resource object instance due to exception in the object factory [Root exception is javax.naming.NamingException: Data source 'jdbc/DefaultDB' not available.]]</message></error>
The web.xml contains the following:
Any advice?
Best regards,
Swen

In BPEL, how to create a SOAP fault?

Similar Messages

Maybe you are looking for