Modifying SOAP faults

We'd like to include a bit of detailed information if a SOAP fault is generated by our Web services. Is there a good way to modify SOAP faults before returning them to the client ? Maybe intercepting them ?
We are using Workshop 9.2 and XMLBeans ... appreciate any advice !!

You can probably do it using a Servlet Filter ....

Similar Messages

Create a web service from java bean and map exceptions to SOAP faults

Hi,
We have to expose our Session stateless EJB3 as web services. I've tried to use annotations and jdev wizard "java bean to web service" and it works fine.
Our problem now is that our methods can throw a business exception that contains a list of error message strings to be presented on the client.
I did not find any way to use annotations to make it build a wsdl with soap fault mapped to our exception class. Neither I could to make the wizard to create wsdl with faults.
As we are exposing already designed and implemented classes as web services, I think the bottom-top (java->wsdl) approach is better that top->botton (wsdl->java). Therefore, I'm looking for a possibility to generate the web services from the java beans and have the exception be mapped to a soap fault message.
We are using jdev 10.1.3.1 and OAS 10.1.3.1., is there a way to map exceptions to soap faults using bottom->top approach?
thank you

A couple of links that may be of help:
http://www.netbeans.org/servlets/ReadMsg?listName=nbj2ee&msgNo=1218
My last question concerning web services:
I have already written a session bean and I'd like to add some methods
as a web service to it, how do I do that?
Or I can only create another bean for a webservice and cannot modify the
original one?You might create web service with existing sources and select you bean. New web services with appropriate lookup method will be generated.
All web service method, that will be exposed in web service, you
should add itself (Pop-up menu Web Service -> Add operation)
http://usersguide.netbeans.org/files/documents/40/73/Chapter9-WebServices.pdf

SOAP Fault Exception [Actor null]

Hi All,
Im trying to call a webservice from portal This web service is in ECC. When I try to call it, it throws the following error:
#1.5 #00E0ED0BA5EF005C000000C500001E350004532D85C22E36#1217354889571#com.sap.portal.SOAPLogger#sap.com/irj#com.sap.portal.SOAPLogger#TESTUSER#9868##n/a##4b8f60d05d9911dda9db00e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_4##0#0#Warning#1#/System/Server#Java###Call failed
[EXCEPTION]
{0}#1#SOAP Fault Exception [Actor null] : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'
<Host>undefined</Host>
<Component>APPL</Component>
<ChainedException>
<Exception_Name>CX_SOAP_CORE</Exception_Name>
<Exception_Text>CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_SXMLP</Exception_Name>
<Exception_Text>XSLT exception</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_ST_MATCH_ELEMENT</Exception_Name>
<Exception_Text>System expected element 'ItItem': Main Program:/1BCDWB/WSSC9FCD3336732797F332| Program:/1BCDWB/WSSC9FCD3336732797F332| Line: 11| Valid:X</Exception_Text>
</ChainedException>
#1.5 #00E0ED0BA5EF005C000000C700001E350004532D85C23109#1217354889572#System.err#sap.com/irj#System.err#BHARDWS#9868##n/a##4b8f60d05d9911dda9db00e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_4##0#0#Error##Plain###SOAP Fault Exception [Actor null] : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'
<Host>undefined</Host>
<Component>APPL</Component>
<ChainedException>
<Exception_Name>CX_SOAP_CORE</Exception_Name>
<Exception_Text>CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_SXMLP</Exception_Name>
<Exception_Text>XSLT exception</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_ST_MATCH_ELEMENT</Exception_Name>
<Exception_Text>System expected element 'ItItem': Main Program:/1BCDWB/WSSC9FCD3336732797F332| Program:/1BCDWB/WSSC9FCD3336732797F332| Line: 11| Valid:X</Exception_Text>
</ChainedException>
#1.5 #00E0ED0BA5EF005C000000C800001E350004532D85C231DF#1217354889572#System.err#sap.com/irj#System.err#BHARDWS#9868##n/a##4b8f60d05d9911dda9db00e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_4##0#0#Error##Plain###We are in Exception and got the message778: SOAP Fault Error (n.a) : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'#
Has anyone come across this? Please help by giving directions on how to fix this.
Thanks
SB

Hi Alex,
Please ignore the above bapi call, it is too complex since it is a custom BAPI that Im trying to call. For now, I am trying to call a very simple BAPI --> BAPI_CUSTOMER_GETDETAIL just to make sure that communication is happening.
Here is the WSDL:
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions targetNamespace="urn:sap-com:document:sap:rfc:functions" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="urn:sap-com:document:sap:rfc:functions">
- <wsdl:documentation>
<sidl:sidl xmlns:sidl="http://www.sap.com/2007/03/sidl" />
</wsdl:documentation>
- <wsdl:types>
- <xsd:schema attributeFormDefault="qualified" targetNamespace="urn:sap-com:document:sap:rfc:functions">
- <xsd:simpleType name="char1">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char10">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char130">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="130" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char16">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="16" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char2">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="2" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char20">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char220">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="220" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char3">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char30">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="30" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char31">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="31" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char32">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="32" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char35">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="35" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char4">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char5">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char50">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="cuky5">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="date">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
<xsd:pattern value="\d\d\d\d-\d\d-\d\d" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="lang">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="numeric3">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="numeric6">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="6" />
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:complexType name="BAPIRET2">
- <xsd:sequence>
<xsd:element name="TYPE" type="tns:char1" />
<xsd:element name="ID" type="tns:char20" />
<xsd:element name="NUMBER" type="tns:numeric3" />
<xsd:element name="MESSAGE" type="tns:char220" />
<xsd:element name="LOG_NO" type="tns:char20" />
<xsd:element name="LOG_MSG_NO" type="tns:numeric6" />
<xsd:element name="MESSAGE_V1" type="tns:char50" />
<xsd:element name="MESSAGE_V2" type="tns:char50" />
<xsd:element name="MESSAGE_V3" type="tns:char50" />
<xsd:element name="MESSAGE_V4" type="tns:char50" />
<xsd:element name="PARAMETER" type="tns:char32" />
<xsd:element name="ROW" type="xsd:int" />
<xsd:element name="FIELD" type="tns:char30" />
<xsd:element name="SYSTEM" type="tns:char10" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="BAPIKNA101">
- <xsd:sequence>
<xsd:element name="FORM_OF_AD" type="tns:char30" />
<xsd:element name="FIRST_NAME" type="tns:char35" />
<xsd:element name="NAME" type="tns:char35" />
<xsd:element name="NAME_3" type="tns:char35" />
<xsd:element name="NAME_4" type="tns:char35" />
<xsd:element name="DATE_BIRTH" type="tns:date" />
<xsd:element name="STREET" type="tns:char35" />
<xsd:element name="POSTL_CODE" type="tns:char10" />
<xsd:element name="CITY" type="tns:char35" />
<xsd:element name="REGION" type="tns:char3" />
<xsd:element name="COUNTRY" type="tns:char3" />
<xsd:element name="COUNTRNISO" type="tns:char3" />
<xsd:element name="COUNTRAISO" type="tns:char3" />
<xsd:element name="INTERNET" type="tns:char130" />
<xsd:element name="FAX_NUMBER" type="tns:char31" />
<xsd:element name="TELEPHONE" type="tns:char16" />
<xsd:element name="TELEPHONE2" type="tns:char16" />
<xsd:element name="LANGU" type="tns:lang" />
<xsd:element name="LANGU_ISO" type="tns:char2" />
<xsd:element name="CURRENCY" type="tns:cuky5" />
<xsd:element name="CURRENCY_ISO" type="tns:char3" />
<xsd:element name="COUNTRYISO" type="tns:char2" />
<xsd:element name="ONLY_CHANGE_COMADDRESS" type="tns:char1" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="BAPIRETURN">
- <xsd:sequence>
<xsd:element name="TYPE" type="tns:char1" />
<xsd:element name="CODE" type="tns:char5" />
<xsd:element name="MESSAGE" type="tns:char220" />
<xsd:element name="LOG_NO" type="tns:char20" />
<xsd:element name="LOG_MSG_NO" type="tns:numeric6" />
<xsd:element name="MESSAGE_V1" type="tns:char50" />
<xsd:element name="MESSAGE_V2" type="tns:char50" />
<xsd:element name="MESSAGE_V3" type="tns:char50" />
<xsd:element name="MESSAGE_V4" type="tns:char50" />
</xsd:sequence>
</xsd:complexType>
- <xsd:element name="BAPI_TRANSACTION_COMMIT">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="WAIT" type="tns:char1" minOccurs="0" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="BAPI_TRANSACTION_COMMITResponse">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="RETURN" type="tns:BAPIRET2" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="BAPI_CUSTOMER_GETDETAIL">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="CUSTOMERNO" type="tns:char10" />
<xsd:element name="PI_DISTR_CHAN" type="tns:char2" minOccurs="0" />
<xsd:element name="PI_DIVISION" type="tns:char2" minOccurs="0" />
<xsd:element name="PI_PASS_BUFFER" type="tns:char1" minOccurs="0" />
<xsd:element name="PI_SALESORG" type="tns:char4" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="BAPI_CUSTOMER_GETDETAILResponse">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="PE_ADDRESS" type="tns:BAPIKNA101" />
<xsd:element name="RETURN" type="tns:BAPIRETURN" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
- <wsdl:message name="BAPI_TRANSACTION_COMMIT">
<wsdl:part name="parameters" element="tns:BAPI_TRANSACTION_COMMIT" />
</wsdl:message>
- <wsdl:message name="BAPI_TRANSACTION_COMMITResponse">
<wsdl:part name="parameter" element="tns:BAPI_TRANSACTION_COMMITResponse" />
</wsdl:message>
- <wsdl:message name="BAPI_CUSTOMER_GETDETAIL">
<wsdl:part name="parameters" element="tns:BAPI_CUSTOMER_GETDETAIL" />
</wsdl:message>
- <wsdl:message name="BAPI_CUSTOMER_GETDETAILResponse">
<wsdl:part name="parameter" element="tns:BAPI_CUSTOMER_GETDETAILResponse" />
</wsdl:message>
- <wsdl:portType name="YCUST">
- <wsdl:operation name="BAPI_TRANSACTION_COMMIT">
<wsdl:input message="tns:BAPI_TRANSACTION_COMMIT" />
<wsdl:output message="tns:BAPI_TRANSACTION_COMMITResponse" />
</wsdl:operation>
- <wsdl:operation name="BAPI_CUSTOMER_GETDETAIL">
<wsdl:input message="tns:BAPI_CUSTOMER_GETDETAIL" />
<wsdl:output message="tns:BAPI_CUSTOMER_GETDETAILResponse" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="YCUST" type="tns:YCUST">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
- <wsdl:operation name="BAPI_TRANSACTION_COMMIT">
<soap:operation soapAction="" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
- <wsdl:operation name="BAPI_CUSTOMER_GETDETAIL">
<soap:operation soapAction="" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="service">
- <wsdl:port name="YCUST" binding="tns:YCUST">
<soap:address location="http://myportal:8040/sap/bc/srt/rfc/sap/ycust/040/ycust/ycust" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
As you will see below in my portal component, Im populating the four fields that it requires:
public class WS_ECC_Service extends PageProcessorComponent {
public DynPage getPage(){
 return new WS_ECC_ServiceDynPage();
public static class WS_ECC_ServiceDynPage extends JSPDynPage{
 protected IPortalComponentRequest request;
 protected IPortalComponentResponse response;
 protected IPortalComponentSession session;
 protected IPortalComponentContext context;
 protected IPortalComponentProfile profile;
 protected String userId;
 // protected IUser epUser;
 protected String sapSystem;
 protected String fileName;
 private DAO DAO = null;
 // private FileUploadUtility FIU = null;
 // private ReadExcelData RED = null;
 private final static int SUCCESS_STATE = 0;
 private final static int INITIAL_STATE = 1;
 private final static int ERROR_STATE = 2;
 private int state = INITIAL_STATE;
 public void doInitialization(){
 this.communicate();
 // fill your bean with data here...
 public void communicate()throws IllegalArgumentException{
 try{
 IPortalRuntimeResources runtimeResources = PortalRuntime.getRuntimeResources();
 IYBAPI_Service myService = (IYBAPI_Service)runtimeResources.getService(IYBAPI_Service.KEY);
 System.err.println("b4 passing object to service Anurag-"+IYBAPI_Service.KEY);
 com.ybapi.BAPI_CUSTOMER_GETDETAIL param = new com.ybapi.BAPI_CUSTOMER_GETDETAIL();
 com.ybapi.BAPI_CUSTOMER_GETDETAILResponse result1 = new com.ybapi.BAPI_CUSTOMER_GETDETAILResponse();
 com.ybapi.Char10 custno = new com.ybapi.Char10();
 custno.setValue("0000009702");
 param.setCUSTOMERNO(custno);
 com.ybapi.Char2 distr = new com.ybapi.Char2();
 distr.setValue("12");
 param.setPI_DISTR_CHAN(distr);
 param.setPI_DIVISION(distr);
 com.ybapi.Char1 buff = new com.ybapi.Char1();
 buff.setValue("w");
 param.setPI_PASS_BUFFER(buff);
 com.ybapi.Char4 sorg = new com.ybapi.Char4();
 sorg.setValue("0001");
 param.setPI_SALESORG(sorg);
 result1 = myService.BAPI_CUSTOMER_GETDETAIL(param);
 System.err.println("message message dear message : - " + result1.getPE_ADDRESS().getNAME());
 }catch (IllegalArgumentException ex){
 System.err.println("Getting details2 " + ex.getMessage());
 }catch (Exception e) {
 e.printStackTrace();
 System.err.println("We are in Exception and got the message778: " + e.getMessage());
 }//end try catch
 public void doProcessAfterInput() throws PageException {
 public void doProcessBeforeOutput() throws PageException {
 this.setJspName("uploadutility.jsp");
and this is what it is throwing the error, exactly the same that I got in my above post which I asked you to ignore.
#1.5 #00E0ED0BA5EF006E0000015A00001E350004533EB66A08B6#1217428720322#com.sap.portal.SOAPLogger#sap.com/irj#com.sap.portal.SOAPLogger#BHARDWS#17255##n/a##2aaa48605e4511ddbbf300e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_2##0#0#Warning#1#/System/Server#Java###Call failed
[EXCEPTION]
{0}#1#SOAP Fault Exception [Actor null] : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'
<Host>undefined</Host>
<Component>APPL</Component>
<ChainedException>
<Exception_Name>CX_SOAP_CORE</Exception_Name>
<Exception_Text>CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_SXMLP</Exception_Name>
<Exception_Text>XSLT exception</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_ST_MATCH_ELEMENT</Exception_Name>
<Exception_Text>System expected element 'CUSTOMERNO': Main Program:/1BCDWB/WSSB675FB6DBC9770445BC| Program:/1BCDWB/WSSB675FB6DBC9770445BC| Line: 19| Valid:X</Exception_Text>
</ChainedException>
#1.5 #00E0ED0BA5EF006E0000015C00001E350004533EB66A09BD#1217428720322#System.err#sap.com/irj#System.err#BHARDWS#17255##n/a##2aaa48605e4511ddbbf300e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_2##0#0#Error##Plain###$$$$$$$$$$$$$exex-SOAP Fault Error (n.a) : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'#
#1.5 #00E0ED0BA5EF006E0000015D00001E350004533EB66A0B44#1217428720323#System.err#sap.com/irj#System.err#BHARDWS#17255##n/a##2aaa48605e4511ddbbf300e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_2##0#0#Error##Plain###SOAP Fault Exception [Actor null] : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'
<Host>undefined</Host>
<Component>APPL</Component>
<ChainedException>
<Exception_Name>CX_SOAP_CORE</Exception_Name>
<Exception_Text>CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_SXMLP</Exception_Name>
<Exception_Text>XSLT exception</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_ST_MATCH_ELEMENT</Exception_Name>
<Exception_Text>System expected element 'CUSTOMERNO': Main Program:/1BCDWB/WSSB675FB6DBC9770445BC| Program:/1BCDWB/WSSB675FB6DBC9770445BC| Line: 19| Valid:X</Exception_Text>
</ChainedException>
#1.5 #00E0ED0BA5EF006E0000015E00001E350004533EB66A0B93#1217428720323#System.err#sap.com/irj#System.err#TESTUSER#17255##n/a##2aaa48605e4511ddbbf300e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_2##0#0#Error##Plain###We are in Exception and got the message778: SOAP Fault Error (n.a) : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'#

SOAP Fault when returning null from a Native Web Service Stored Procedure

I have a stored procedure which I can successfully invoke via soapUI
However, if one of the Stored Procedure's OUT arguments is set to null the native web service returns the following fault :
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Client</faultcode>
<faultstring>Error processing input</faultstring>
<detail>
<OracleErrors xmlns="http://xmlns.oracle.com/orawsv/faults">
<OracleError>
<ErrorNumber>ORA-19202</ErrorNumber>
<Message>Error occurred in XML processing</Message>
</OracleError>
<OracleError>
<ErrorNumber>ORA-01405</ErrorNumber>
<Message>fetched column value is NULL</Message>
</OracleError>
</OracleErrors>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>I can see how to control the processing of null values when invoking orawsv (using the null_handling element).
Is there an equivalent for Stored Procedures ?
Thanks,
PD
versions as follows :
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
"CORE 11.2.0.1.0 Production"
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production

Without going into any technical discussion about the code, my first question is what JDK version was used to create this which was imported into the form? Understand that Forms 10 runs on JDK 1.4.2, so if you used any newer JDK version, likely there will be problems.

BPM: System_Error" SOAP fault message received

Hi,
We upgraded SAP system from 4.7 to ERP2004 on 09/17/05.
We have XI-3.0 version from last 9 months and this BPM was working good so far. We have not changed anything in it except we upgraded the SAP system.
We are using ABAP proxy from SAP to send "userid"
message to XI-BPM and then it would make a Synchonous call to SAP system to get roles of those "usrid".
In the first step when it is sending data to XI an exception is raised and in the second step when it tries to make synchronous call to SAP we are getting error:
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="3" type="System_Error">SOAP fault message received</Trac
<Trace level="3" type="System_Error">SOAP fault code: Client</Trace>
<Trace level="3" type="System_Error">SOAP fault string: Error during c
I noticed that the XML name tag looks different now
Before upgrade when message was successful.
<?xml version="1.0" encoding="utf-8" ?>
- <ns1:MT_ECA_USRID xmlns:ns1="http://bcm.edu/common"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<USRID>CLARKSON</USRID>
<USRID>2_MA140016</USRID>
</ns1:MT_ECA_USRID>
After upgrade when message is failed
<?xml version="1.0" encoding="utf-8" ?>
- <nr1:MT_ECA_USRID xmlns:nr1="http://bcm.edu/common">
<USRID>AABULIMI</USRID>
<USRID>AB147899</USRID>
<USRID>ACHALL</USRID>
</nr1:MT_ECA_USRID>
You would notice that
" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
missing after upgrade.
I would appreciate if anyone could help me.
Mrudula

Hi,
Can you paste the full error message. Also take a look at the default trace log in Visual Admin. Set the logging for soap to debug.
Naveen

SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: Exception during processi

Hi: We are using weblogic81 sp3. Other developers in my office ran the same porgram and got no errors.
My startWebLogic.cmd are configured exactly same as theirs.
My startWebLogic classpath:
set CLASSPATH=%WL_HOME%\server\lib\ojdbc14.jar;%WL_HOME%\server\lib\CR122067_81sp3.jar;%WEBLOGIC_CLASSPATH%;%POINTBASE_CLASSPATH%;%JAVA_HOME%\jre\lib\rt.jar;%WL_HOME%\server\lib\webservices.jar;%CLASSPATH%
I keep getting this webservice error.
SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: Exception during processing: w
eblogic.xml.schema.binding.DeserializationException: mapping lookup failure. typ
e=['java:language_builtins.util']:ArrayList schema context=TypedSchemaContext{ja
vaType=[Ljava.lang.Object;} (see Fault Detail for stacktrace)
Detail:
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webse
rvice/fault/1.0.0">weblogic.xml.schema.binding.DeserializationException: mapping
lookup failure. type=['java:language_builtins.util']:ArrayList schema context=T
ypedSchemaContext{javaType=[Ljava.lang.Object;}
at weblogic.xml.schema.binding.RuntimeUtils.lookup_deserializer(RuntimeU
tils.java:461)
thank you for your help

we used castor to do xml mapping

Java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException

Hi, I created a webservice using weblogic8.1 sp3 workshop. On my desktop, I tested the webservice with a java client and it worked fine. When I deployed webservice application on UNIX production server, it deployed successfully and it displayed WSDL file too. But, when I run java client from desktop to access this webservice on UNIX server, it is throwing the following exception.
java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: EXCEPTION: java.lang.NoClassDefFoundError [ServiceException]
Detail:
<detail>
null </detail>; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: EXCEPTION: java.lang.NoClassDefFoundError [ServiceException]
at weblogic.jws.proxies.MyServiceSoap_Stub.getInfo(MyServiceSoap_Stub.java:31)
at SoapClient.main(SoapClient.java:17)
Caused by: javax.xml.rpc.soap.SOAPFaultException: EXCEPTION: java.lang.NoClassDefFoundError [ServiceException]
at weblogic.webservice.core.ClientDispather.receive(ClientDispatcher.java:313)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:290)
at weblogic.jws.proxies.MyServiceSoap_Stub.getInfo(MyServiceSoap_Stub.java:26)
can somebody please help me. This is very critical for me.
Thanks in advance.

Hi, I created a webservice using weblogic8.1 sp3 workshop. On my desktop, I tested the webservice with a java client and it worked fine. When I deployed webservice application on UNIX production server, it deployed successfully and it displayed WSDL file too. But, when I run java client from desktop to access this webservice on UNIX server, it is throwing the following exception.
java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: EXCEPTION: java.lang.NoClassDefFoundError [ServiceException]
Detail:
<detail>
null </detail>; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: EXCEPTION: java.lang.NoClassDefFoundError [ServiceException]
at weblogic.jws.proxies.MyServiceSoap_Stub.getInfo(MyServiceSoap_Stub.java:31)
at SoapClient.main(SoapClient.java:17)
Caused by: javax.xml.rpc.soap.SOAPFaultException: EXCEPTION: java.lang.NoClassDefFoundError [ServiceException]
at weblogic.webservice.core.ClientDispather.receive(ClientDispatcher.java:313)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:290)
at weblogic.jws.proxies.MyServiceSoap_Stub.getInfo(MyServiceSoap_Stub.java:26)
can somebody please help me. This is very critical for me.
Thanks in advance.

SOAP Fault while invoking ISG Service through BPEL

Hi,
I am trying to invoke a EBS R12 pl sql API exposed as a web service through integrated SOA gateway. But i am hitting the same error for different API`s that i have tried with. the error is :
<remoteFault>
<part name="summary">
<summary>Error occured while service was processing.</summary>
</part>
<part name="detail">
<detail>oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : Error occured while service was processing.</detail>
</part>
<part name="code">
<code>{http://schemas.xmlsoap.org/soap/envelope/}Server</code>
</part>
</remoteFault>
I have supplied the r12 credentials through the composite WS Policies and the header details for the API as well. I am also able to call the API through PL/SQL code. Any reason why this error is occuring.

My 2 cents here - are you using ?wsdl for accessing the wsdl? Reason I am asking this is because you get a fault message as you have posted, i.e., The action (ABC#) did not identify an operation, looks like you are hitting the service directly instead of querying for the wsdl. Also, while you are using this wsdl in your PS/BS, for example, maybe in a route action, are you sure you are selecting the operation from the list of operations this wsdl has?

Error:SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. --- There is an error in XML document (1, 447). --- Input string was not in a correct format.

Hi All,
We have a scenario of FTP-->PI---> Webservice. While triggering the data in the FTP, it is failing in the PI with the below error
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 447). ---> Input string was not in a correct format.
Can you please help?

Hi Raja- It seems to be a data quality issue.
Check for the value @ 1447 position in the xml message that you are trying to send to web service..
may be a date filed/decimal value which is not in expected format.

Handling of SOAP Faults in SOAP Clients consuming PI Web services

Hi there,
the following is in regards to SOAP fault error handling in a SOAP client that consumes a Web Service published by PI.
I have been reading a number of threads and blogs in regards to this topic and I am still left with some open questions which I hope to get some final answersclarifications through this thread.
In particular the blogs
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI - Handling Web Service SOAP Fault Responses in SAP NetWeaver XI
XI: Propagation of meaningful error information to SOAP Client - XI: Propagation of meaningful error information to SOAP Client
have caused by attention.
Both of these threads are realating to the Fault Message type one can use to return errors back to a SOAP Client (.Net, Java, etc.).
In our scenario we published a number of Web Services through PI that provide functionality to integrate with an R3 back-end system using inbound ABAP Proxies.
The services are standardised and will be consumed by a number of .NetJava applications and systems. The reason for the use of ABAP proxies is the customer specific application logic that is executed in the backend system. The Web services are synchronous and don't use ccBPM in the middle. Transformations are performed in PI combined with various lookups to set default values before the message is passed into the ABAP Framework of the R3 back-end system. The lookups are done against the R3 back-end system using the PI RFC Lookup feature.
The inbound proxies currently return application errors as part of the response message back to the SOAP client. For more critical errors we introduced the use of Fault message types as the method to return the information back to the SOAP Client. This is all working satisfactory.
The questions I have are as follows.
1. When an error occurs at the IE level (e.g. mapping error), ABAP Proxy framework level (e.g. conversion from XML to ABAP format) or Adapter Framework level (Adapter releated error) a different SOAP fault message structure is returned to the SOAP Client than the one used for the application errors. The SOAP fault message structure used in this case is the standard SOAP fault used by PI to return system errors back to the caller. For those SOAP fault messages there is no payload generated that could be mapped to the SOAP fault structure used for the application errors. This would be preferrable as there would be only one Fault message structure used for both inbound ABAP proxy generated fault messages and PI generated fault messages.
Also the error messages generated by PI can be quite cryptic and difficult to interpret at the client end and could be filtered ranslated during message mapping if the payload of the PI generated SOAP fault message could be accessed in a message mapping.
Point 3 of the above thread 2759 indicates that this would be possible but doesn't outline how. Could somebody please clarify this for me as I don't believe that this is really possible ???.
My idea instead was to use the PI SOAP fault message structure to also return application errors. Therefore I would create a Fault message type that matches the PI SOAP fault structure. This would enable the SOAP Client to handle only one SOAP Fault error structure. Would that be something to look into instead ?????.
2. We have been looking at using the integrated WEB AS SOAP adapter instead of using the AF Sender SOAP adapter. While playing with this we encountered differences in the content returned through the SOAP fault generated by PI. A sample is below. Shouldn't the content of these SOAP faults be the same if the error that caused it is the same. Also the SOAP fault returned by the IE SOAP adapter is much more useful in this particular case. Both errors below are the same, a conversion error from XML to ABAP took place in the inbound ABAP proxy framework of the back-end system.
SOAP fault returned when using SOAP Sender adapter of AF
<!see the documentation>
<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.aii.af.ra.ms.api.DeliveryException: XIProxy:PARSE_APPLICATION_DATA:
 at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
 at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
 at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:916)
 at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
SOAP fault using integrated SOAP adapter of PI IE
<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/>
 <code>ABAP.PARSE_APPLICATION_DATA</code>
 <text>Error during XML => ABAP conversion (Request Message; error ID: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXSBE20FF604BAFEF8D990A XML Bytepos.: 564 XML Path: ns1:CreatePORequest(1)POHEADER(2)COMP_CODE(1) Error Text: Data loss occurred when converting ############################## Kernel ErrorId: CONVT_DATA_LOSS))</text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
I have been reading threads for hours without being able to find one that answers questions 1 or provides a blog that outlines the approach one should take for error handling in SOAP clients that consume PI Web Services (and covers both PISystem generated faults and faults raised in Proxies).
There may already be a blog or thread and I just missed it.
Any comments are welcome.
Thanks. Dieter

Hi Dieter,
As Bhavesh already mentioned fault messages are used for application errors. The same is described in SAP XI help:
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
In case of system error (e.g. field length too long in proxy call or error in XI/PI mapping) there seems to be no standard way of handling it and propagating the response to the consumer of webservice.
Each system error is not recognized by SOAP adapter and SOAP adapter exception is raised.
The only bizzare solution that I can see is developing an adapter module and transport wrong message to standard fault message before delivering it to adapter engine:
http://help.sap.com/saphelp_nw04/helpdata/en/a4/f13341771b4c0de10000000a1550b0/frameset.htm
Kind regards,
Wojciech
btw nice thread

ABAP proxy exception to SOAP fault and vice versa not getting mapped

Hi there,
I have these scenario's: ABAP proxy to SOAP (AXIS framework) and the other way around, synchronous, using AAE.
When declaring the Synchronous Service interfaces we also defined error message types in order to pass system and application exceptions back to the service consumers.
The behavior we are observing is as follows;
When an exception is generated on the ABAP proxy, the error message type is correct generated and filled with the corresponding values in the ABAP proxy runtime. However, when the response arrives at the service consumer, it only contains a SOAP fault filled with some kind of generic PI mapping exception information.
1. Why is the original ABAP proxy exception not mapped/passed into the SOAP response?
2. What can we do in order to change that situation?
3. Does it has to do with the use of the AAE - Advanced Adapter Engine or the AXIS framework?
PS: We have performed a test of the Operation Mapping - OM using the ABAP exception as input and it did work correctly, so the error structure seems to be Ok.
Many thanks for your replies.
Edited by: Roberto Viana on Jul 26, 2010 8:30 PM

Problem was caused by some differences in namespaces between source and target.

Java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : Failure in SDOSerializer.deserialize

Hi All,
I am getting this exception while invoking one of our service from EM. Any pointers will be very helpful.
java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : Failure in SDOSerializer.deserialize. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:813) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:385) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:303) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.el.parser.AstValue.invoke(AstValue.java:187) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:297) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1491) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:111) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:384) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:114) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:101) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:111) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:384) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:114) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:95) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:972) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:439) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:219) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:102) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:211) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:131) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:447) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:447) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:181) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:183) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:158) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.security.wls.filter.SSOSessionSynchronizationFilter.doFilter(SSOSessionSynchronizationFilter.java:419) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3739) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3705) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2282) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2181) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1491) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : Failure in SDOSerializer.deserialize. at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:362) at oracle.sysman.emSDK.webservices.wsdlparser.OperationInfoImpl.invokeWithDispatch(OperationInfoImpl.java:1004) at

Hi,
its JDeveloper and ADF on this forum. For EM related questions, you should try the EM forum
Frank

PI 7.1 Adapter Module Development - Identify SOAP Fault Message

Hi Experts,
here's a PI 7.1 Adapter Module Development issue I hope you can help me to resolve. It's about identifying SOAP fault messages.

Scenario at a glance:
Adapter Modules placed in the modules chain at request and response time in a synchronous Scenario:
- Request: SOAP Axis to RFC 
- Response and Fault Response: RFC to SOAP Axis

The issue is how to identify SOAP fault message in SOAP Axis Adapter Module in the response message:
The client gets SOAP fault messages like the follwong one:
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <ns1:exception xmlns:ns1="http://typen.geschaeftsstelle.pab.barmer.de">
 <ns1:errortext>bla bla bla ...</ns1:errortext>
 </ns1:exception>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>


But when trying to access the tags faultcode and/or faultstring in the adapter module via xPath expressions I do not get them. Obviously the SOAP Fault tags are built AFTER the adapter module has been passed. So my question is:
How can I clearly/uniquely detect a SOAP fault response message (and distinguish it from a "normal" response message) in my SOAP Axis Adapter Module?

I tried it the following way:


// Check Message Payload for SOAP Fault Message via xPath expressions
...
// SOAP Fault Code
zv_xPression = zc_constXPattern.replaceFirst("&", "faultcode");
zv_soapFaultCode = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// SOAP Fault String
zv_xPression = zc_constXPattern.replaceFirst("&", "faultstring");
zv_soapFaultString = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// check for SOAP Fault Message
if (zv_soapFaultCode.equals("") && zv_soapFaultString.equals("")) {
 // Create Audit Log entry - NOT a SOAP Fault Message
 zv_msgText = zc_constModuleName + " 0190: xPath - OK! This message is NOT a SOAP Fault Message";
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.SUCCESS, zv_msgText);
 zv_faultCheck = false;
}
else {
 ...
 // Create Audit Log entry - SOAP Fault Message
 zv_msgText = zc_constModuleName 
 + " 0200: xPath - this message is a SOAP Fault Message. " 
 + " - Faultcode is: " + zv_soapFaultCode 
 + " - Faultstring is: " + zv_soapFaultString; 
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
 ...
}
...

But zv_soapFaultCode and zv_soapFaultString are always empty (with other payload tags this coding works fine).

Any ideas? 
Thanx very much in advance!
Regards,
Volker

Hi Alex!
Like already mentioned I solved my problem by identifying the SOAP exception with the messageClass attribute of the PI message header. Acess code:
try {
String zv_msgClass = zv_piMsg.getMessageClass().toString();
} catch (Exception e) {
zv_msgText = zc_constModuleName
+ " E0110: Message processing terminated."
+ " Reason: Error while getting MessageClass "
+ zv_dataSource
+ e;
// create trace and audit log entry (severity ERROR) for exception
zv_location.errorT(ZV_SIGNATURE, zv_msgText);
zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
ModuleException me = new ModuleException(e);
zv_location.throwing(ZV_SIGNATURE, me);
e.printStackTrace();
throw me;
} // end of try-catch-block
But I do not think this will solve your problem. I am almost sure, that something in your Axis configuration is wrong/missing. If a handler cannot be instatiated then it really may be missing. Have a look at defaultTrace.trc. Maybe you will find more suitable information about the root cause of your problem. Also have a look at NWA under software components and/or application modules if you can find/see your modules.
But there is a general issue when trying to catch PI fault messages. If e.g. the requestor tries to login with wrong userid/pasword, then you will have no chance to catch this kind of error - at least as far as I know. Because in this very early stage of PI message processing no module is called.
One last question: Did you develop your own Adapter or just an adapter module? In the first case: Is your adapter started and healthy? Have a look at RWB -> communication channel monitoring.
Regards,
Volker

Soap Fault mapping issue

Hi,
I have a synchronous scenario of (request) Proxy --> XI --> SOAP and (response) SOAP --> XI --> Proxy. I am having an issue returning the application soap faults back to the sender system. When I enter invalid data while testing this webservice call with a soap client directly without XI I get a soap fault response:
<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.generalException</faultcode>
 <faultstring>Login failed</faultstring>
 <detail>
 <LoginFault xmlns="NAMESPACE">
 <exceptionCode>710</exceptionCode>
 <exceptionMessage>Login failed</exceptionMessage>
 </LoginFault>
 <ns1:exceptionName xmlns:ns1="http://xml.apache.org/axis/">NAMESPACE</ns1:exceptionName>
 </detail>
 </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>
When testing this through XI, the response message after the Soap call is returning the following soap fault in XI payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<LoginFault xmlns="NAMESPACE">
<exceptionCode>710</exceptionCode>
<exceptionMessage>Login failed</exceptionMessage>
</LoginFault>
Notice just the detail body exists in the payload instead of the soap evelope and body, which I read is stripped off within XI in the case of application errors. I have setup a fault message mapping to tie the wsdl login fault with the standard fault message type and included this in the service interfaces and operations mapping. When the soap fault happens within XI I am getting the following mapping error:
NO_MAPPINGPROGRAM_FOUND: Mapping program is not available in runtime cache:
I am expecting the fault mapping to be executed in this case but doesn't seem to be found. Any ideas why this mapping error is occuring and not being directed to my fault message mapping? Is the mapping expecting the soap envelope and body to be included in the payload?
Any suggestions would be appreciated.
Thanks,
Nate

Here are the errors I am seeing within the sxmb_moni transaction:
Call adapter exception:
<?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>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID 35F8008AA0A830FC93FC221572A15ABD Software Component DC6FB8300EDE11DC8E05DB6DA3E77028</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID 35F8008AA0A830FC93FC221572A15ABD Software Component DC6FB8300EDE11DC8E05DB6DA3E77028</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Response Message 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>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="NAMESPACE REMOVED">LoginFault</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
and response message payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <LoginFault xmlns="NAMESPACE REMOVED">
<exceptionCode>710</exceptionCode>
<exceptionMessage>Login failed</exceptionMessage>
</LoginFault>

Error "soap fault: No operation available for request" in proxy to soap Scenario

Hi Experts,
Unable to trace the below error when pushing the message from RWB while testing the PROXY to SOAP interface
Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No operation available for request {http://schemas.xmlsoap.org/soap/envelope/}Envelope.
Thank you very much if any one provided the solution
Regards,
Yugandhar

Hi Yugandhar,
Check the below thread,
Connecting from SAP PI To Salesforce
Regards
RK N.

Modifying SOAP faults

Similar Messages

Maybe you are looking for