Consuming Webservice in ABAP: SoapFaultCode:1
Hi,
I have created a webservice with NetweaverDeveloperStudio and deployed it to a J2EE. I tested it with the "NDS-Webservice-Tester" and it worked fine.
I then created a proxy following the section for WebAS 640 in the weblog of Thomas Jung:
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
When using the "test-interface" function in SE80 (also described in Thomas weblog) I get the following result:
<CX_AI_SYSTEM_FAULT>
<CODECONTEXT>http://www.sap.com/xml_errorcodes</CODECONTEXT>
<CODE>SoapFaultCode:1</CODE>
<ERRORTEXT>
000D6019F1DD004000000036000020D8000405473991B26F:
Found 0 operation definitions using keys:
Key name:'first-body-element-ns'
key value: 'urn:EdilogUserManagementWebserviceWsd/EdilogUserManagementWebserviceVi/document';
Key name:'SoapRequestWrapper'
key value:'getCompany';
</ERRORTEXT>
<LANGUAGE />
</CX_AI_SYSTEM_FAULT>
Any idea what might cause this error? Is there a list with the SoapErrorCodes and their specific meanings?
Thanks and regards
Jan Hempel
I solved the problem "accidentally": The name of the Webservice was to long! Changing the name from "EdilogUserManagementWebservice" to "UserManagement" did the trick.
This is probably due to the restricted fieldlength of ABAP-programnames.
Regards
Jan Hempel
Similar Messages
-
Consume webservice from ABAP : SoapFaultCode:4
Hi ,
I need your valuable ideas in overcoming the problem mentioned below.
This problem relates to consumption of a webservice from ABAP - Client Proxy without XI. The system is WAS 6.40.
I had created a client proxy (along with the corresponding methods) using a WSDL file pasted below. I had also created a logical port for the proxy class generated.
When I test the interface for one of the methods , I get the following error message.
<u>Error Message</u>
<?xml version="1.0" encoding="utf-8" ?>
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<SYSTEMFAULT href="#o103" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_AI_SYSTEM_FAULT id="o103">
- <CX_ROOT>
<TEXTID>F63AFF63DBE4BB4786A7F52CC4167145</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>193</PROGID>
<CONTID>1050</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_STATIC_CHECK />
- <CX_AI_SYSTEM_FAULT>
<CODECONTEXT>http://www.sap.com/xml_errorcodes</CODECONTEXT>
<CODE>SoapFaultCode:4</CODE>
<ERRORTEXT>System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: //10.136.129.245/PinnacleWebServices/DatabaseAvailable. at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)</ERRORTEXT>
<LANGUAGE />
</CX_AI_SYSTEM_FAULT>
</cls:CX_AI_SYSTEM_FAULT>
</asx:heap>
</asx:abap>
<u>WDSL file used for creating the Client Proxy</u>
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="//10.136.129.245/PinnacleWebServices" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="//10.136.129.245/PinnacleWebServices" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<s:schema elementFormDefault="qualified" targetNamespace="//10.136.129.245/PinnacleWebServices">
<s:element name="DatabaseAvailable">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="DatabaseAvailableResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="DatabaseAvailableResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddCustomers">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddCustomersResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="AddCustomersResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddContracts">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddContractsResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="AddContractsResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddInstalledEquipment">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddInstalledEquipmentResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="AddInstalledEquipmentResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddProducts">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddProductsResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="AddProductsResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddCreditAlerts">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
<s:element minOccurs="1" maxOccurs="1" name="bool_updatecustomers" type="s:boolean" />
<s:element minOccurs="1" maxOccurs="1" name="bool_updatecontracts" type="s:boolean" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddCreditAlertsResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="AddCreditAlertsResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddStockFigures">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddStockFiguresResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="AddStockFiguresResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="string" nillable="true" type="s:string" />
</s:schema>
</wsdl:types>
<wsdl:message name="DatabaseAvailableSoapIn">
<wsdl:part name="parameters" element="tns:DatabaseAvailable" />
</wsdl:message>
<wsdl:message name="DatabaseAvailableSoapOut">
<wsdl:part name="parameters" element="tns:DatabaseAvailableResponse" />
</wsdl:message>
<wsdl:message name="AddCustomersSoapIn">
<wsdl:part name="parameters" element="tns:AddCustomers" />
</wsdl:message>
<wsdl:message name="AddCustomersSoapOut">
<wsdl:part name="parameters" element="tns:AddCustomersResponse" />
</wsdl:message>
<wsdl:message name="AddContractsSoapIn">
<wsdl:part name="parameters" element="tns:AddContracts" />
</wsdl:message>
<wsdl:message name="AddContractsSoapOut">
<wsdl:part name="parameters" element="tns:AddContractsResponse" />
</wsdl:message>
<wsdl:message name="AddInstalledEquipmentSoapIn">
<wsdl:part name="parameters" element="tns:AddInstalledEquipment" />
</wsdl:message>
<wsdl:message name="AddInstalledEquipmentSoapOut">
<wsdl:part name="parameters" element="tns:AddInstalledEquipmentResponse" />
</wsdl:message>
<wsdl:message name="AddProductsSoapIn">
<wsdl:part name="parameters" element="tns:AddProducts" />
</wsdl:message>
<wsdl:message name="AddProductsSoapOut">
<wsdl:part name="parameters" element="tns:AddProductsResponse" />
</wsdl:message>
<wsdl:message name="AddCreditAlertsSoapIn">
<wsdl:part name="parameters" element="tns:AddCreditAlerts" />
</wsdl:message>
<wsdl:message name="AddCreditAlertsSoapOut">
<wsdl:part name="parameters" element="tns:AddCreditAlertsResponse" />
</wsdl:message>
<wsdl:message name="AddStockFiguresSoapIn">
<wsdl:part name="parameters" element="tns:AddStockFigures" />
</wsdl:message>
<wsdl:message name="AddStockFiguresSoapOut">
<wsdl:part name="parameters" element="tns:AddStockFiguresResponse" />
</wsdl:message>
<wsdl:message name="DatabaseAvailableHttpGetIn">
<wsdl:part name="s_dbalias" type="s:string" />
</wsdl:message>
<wsdl:message name="DatabaseAvailableHttpGetOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:message name="AddCustomersHttpGetIn">
<wsdl:part name="s_dbalias" type="s:string" />
<wsdl:part name="s_xml" type="s:string" />
</wsdl:message>
<wsdl:message name="AddCustomersHttpGetOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:message name="AddContractsHttpGetIn">
<wsdl:part name="s_dbalias" type="s:string" />
<wsdl:part name="s_xml" type="s:string" />
</wsdl:message>
<wsdl:message name="AddContractsHttpGetOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:message name="AddInstalledEquipmentHttpGetIn">
<wsdl:part name="s_dbalias" type="s:string" />
<wsdl:part name="s_xml" type="s:string" />
</wsdl:message>
<wsdl:message name="AddInstalledEquipmentHttpGetOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:message name="AddProductsHttpGetIn">
<wsdl:part name="s_dbalias" type="s:string" />
<wsdl:part name="s_xml" type="s:string" />
</wsdl:message>
<wsdl:message name="AddProductsHttpGetOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:message name="AddCreditAlertsHttpGetIn">
<wsdl:part name="s_dbalias" type="s:string" />
<wsdl:part name="s_xml" type="s:string" />
<wsdl:part name="bool_updatecustomers" type="s:string" />
<wsdl:part name="bool_updatecontracts" type="s:string" />
</wsdl:message>
<wsdl:message name="AddCreditAlertsHttpGetOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:message name="AddStockFiguresHttpGetIn">
<wsdl:part name="s_dbalias" type="s:string" />
<wsdl:part name="s_xml" type="s:string" />
</wsdl:message>
<wsdl:message name="AddStockFiguresHttpGetOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:message name="DatabaseAvailableHttpPostIn">
<wsdl:part name="s_dbalias" type="s:string" />
</wsdl:message>
<wsdl:message name="DatabaseAvailableHttpPostOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:message name="AddCustomersHttpPostIn">
<wsdl:part name="s_dbalias" type="s:string" />
<wsdl:part name="s_xml" type="s:string" />
</wsdl:message>
<wsdl:message name="AddCustomersHttpPostOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:message name="AddContractsHttpPostIn">
<wsdl:part name="s_dbalias" type="s:string" />
<wsdl:part name="s_xml" type="s:string" />
</wsdl:message>
<wsdl:message name="AddContractsHttpPostOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:message name="AddInstalledEquipmentHttpPostIn">
<wsdl:part name="s_dbalias" type="s:string" />
<wsdl:part name="s_xml" type="s:string" />
</wsdl:message>
<wsdl:message name="AddInstalledEquipmentHttpPostOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:message name="AddProductsHttpPostIn">
<wsdl:part name="s_dbalias" type="s:string" />
<wsdl:part name="s_xml" type="s:string" />
</wsdl:message>
<wsdl:message name="AddProductsHttpPostOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:message name="AddCreditAlertsHttpPostIn">
<wsdl:part name="s_dbalias" type="s:string" />
<wsdl:part name="s_xml" type="s:string" />
<wsdl:part name="bool_updatecustomers" type="s:string" />
<wsdl:part name="bool_updatecontracts" type="s:string" />
</wsdl:message>
<wsdl:message name="AddCreditAlertsHttpPostOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:message name="AddStockFiguresHttpPostIn">
<wsdl:part name="s_dbalias" type="s:string" />
<wsdl:part name="s_xml" type="s:string" />
</wsdl:message>
<wsdl:message name="AddStockFiguresHttpPostOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:portType name="Pinnacle_x0020_Web_x0020_ServicesSoap">
<wsdl:operation name="DatabaseAvailable">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Checks if a connection to the selected database is available.</documentation>
<wsdl:input message="tns:DatabaseAvailableSoapIn" />
<wsdl:output message="tns:DatabaseAvailableSoapOut" />
</wsdl:operation>
<wsdl:operation name="AddCustomers">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Customers within Service Director</documentation>
<wsdl:input message="tns:AddCustomersSoapIn" />
<wsdl:output message="tns:AddCustomersSoapOut" />
</wsdl:operation>
<wsdl:operation name="AddContracts">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Contracts within Service Director</documentation>
<wsdl:input message="tns:AddContractsSoapIn" />
<wsdl:output message="tns:AddContractsSoapOut" />
</wsdl:operation>
<wsdl:operation name="AddInstalledEquipment">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Installed Equipment within Service Director</documentation>
<wsdl:input message="tns:AddInstalledEquipmentSoapIn" />
<wsdl:output message="tns:AddInstalledEquipmentSoapOut" />
</wsdl:operation>
<wsdl:operation name="AddProducts">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Products within Service Director</documentation>
<wsdl:input message="tns:AddProductsSoapIn" />
<wsdl:output message="tns:AddProductsSoapOut" />
</wsdl:operation>
<wsdl:operation name="AddCreditAlerts">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Credit Alerts to Customers and/or Contracts within Service Director. Warning - Will remove all credit alerts first as it assumes a full list is provided every time.</documentation>
<wsdl:input message="tns:AddCreditAlertsSoapIn" />
<wsdl:output message="tns:AddCreditAlertsSoapOut" />
</wsdl:operation>
<wsdl:operation name="AddStockFigures">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Stock Figures to mobile_data_connector within Service Director in order that the PDA get updated.</documentation>
<wsdl:input message="tns:AddStockFiguresSoapIn" />
<wsdl:output message="tns:AddStockFiguresSoapOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="Pinnacle_x0020_Web_x0020_ServicesHttpGet">
<wsdl:operation name="DatabaseAvailable">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Checks if a connection to the selected database is available.</documentation>
<wsdl:input message="tns:DatabaseAvailableHttpGetIn" />
<wsdl:output message="tns:DatabaseAvailableHttpGetOut" />
</wsdl:operation>
<wsdl:operation name="AddCustomers">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Customers within Service Director</documentation>
<wsdl:input message="tns:AddCustomersHttpGetIn" />
<wsdl:output message="tns:AddCustomersHttpGetOut" />
</wsdl:operation>
<wsdl:operation name="AddContracts">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Contracts within Service Director</documentation>
<wsdl:input message="tns:AddContractsHttpGetIn" />
<wsdl:output message="tns:AddContractsHttpGetOut" />
</wsdl:operation>
<wsdl:operation name="AddInstalledEquipment">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Installed Equipment within Service Director</documentation>
<wsdl:input message="tns:AddInstalledEquipmentHttpGetIn" />
<wsdl:output message="tns:AddInstalledEquipmentHttpGetOut" />
</wsdl:operation>
<wsdl:operation name="AddProducts">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Products within Service Director</documentation>
<wsdl:input message="tns:AddProductsHttpGetIn" />
<wsdl:output message="tns:AddProductsHttpGetOut" />
</wsdl:operation>
<wsdl:operation name="AddCreditAlerts">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Credit Alerts to Customers and/or Contracts within Service Director. Warning - Will remove all credit alerts first as it assumes a full list is provided every time.</documentation>
<wsdl:input message="tns:AddCreditAlertsHttpGetIn" />
<wsdl:output message="tns:AddCreditAlertsHttpGetOut" />
</wsdl:operation>
<wsdl:operation name="AddStockFigures">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Stock Figures to mobile_data_connector within Service Director in order that the PDA get updated.</documentation>
<wsdl:input message="tns:AddStockFiguresHttpGetIn" />
<wsdl:output message="tns:AddStockFiguresHttpGetOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="Pinnacle_x0020_Web_x0020_ServicesHttpPost">
<wsdl:operation name="DatabaseAvailable">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Checks if a connection to the selected database is available.</documentation>
<wsdl:input message="tns:DatabaseAvailableHttpPostIn" />
<wsdl:output message="tns:DatabaseAvailableHttpPostOut" />
</wsdl:operation>
<wsdl:operation name="AddCustomers">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Customers within Service Director</documentation>
<wsdl:input message="tns:AddCustomersHttpPostIn" />
<wsdl:output message="tns:AddCustomersHttpPostOut" />
</wsdl:operation>
<wsdl:operation name="AddContracts">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Contracts within Service Director</documentation>
<wsdl:input message="tns:AddContractsHttpPostIn" />
<wsdl:output message="tns:AddContractsHttpPostOut" />
</wsdl:operation>
<wsdl:operation name="AddInstalledEquipment">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Installed Equipment within Service Director</documentation>
<wsdl:input message="tns:AddInstalledEquipmentHttpPostIn" />
<wsdl:output message="tns:AddInstalledEquipmentHttpPostOut" />
</wsdl:operation>
<wsdl:operation name="AddProducts">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Products within Service Director</documentation>
<wsdl:input message="tns:AddProductsHttpPostIn" />
<wsdl:output message="tns:AddProductsHttpPostOut" />
</wsdl:operation>
<wsdl:operation name="AddCreditAlerts">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Credit Alerts to Customers and/or Contracts within Service Director. Warning - Will remove all credit alerts first as it assumes a full list is provided every time.</documentation>
<wsdl:input message="tns:AddCreditAlertsHttpPostIn" />
<wsdl:output message="tns:AddCreditAlertsHttpPostOut" />
</wsdl:operation>
<wsdl:operation name="AddStockFigures">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Stock Figures to mobile_data_connector within Service Director in order that the PDA get updated.</documentation>
<wsdl:input message="tns:AddStockFiguresHttpPostIn" />
<wsdl:output message="tns:AddStockFiguresHttpPostOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="Pinnacle_x0020_Web_x0020_ServicesSoap" type="tns:Pinnacle_x0020_Web_x0020_ServicesSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
<wsdl:operation name="DatabaseAvailable">
<soap:operation soapAction="//10.136.129.245/PinnacleWebServices/DatabaseAvailable" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddCustomers">
<soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddCustomers" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddContracts">
<soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddContracts" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddInstalledEquipment">
<soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddInstalledEquipment" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddProducts">
<soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddProducts" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddCreditAlerts">
<soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddCreditAlerts" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddStockFigures">
<soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddStockFigures" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="Pinnacle_x0020_Web_x0020_ServicesHttpGet" type="tns:Pinnacle_x0020_Web_x0020_ServicesHttpGet">
<http:binding verb="GET" />
<wsdl:operation name="DatabaseAvailable">
<http:operation location="/DatabaseAvailable" />
<wsdl:input>
<http:urlEncoded />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddCustomers">
<http:operation location="/AddCustomers" />
<wsdl:input>
<http:urlEncoded />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddContracts">
<http:operation location="/AddContracts" />
<wsdl:input>
<http:urlEncoded />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddInstalledEquipment">
<http:operation location="/AddInstalledEquipment" />
<wsdl:input>
<http:urlEncoded />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddProducts">
<http:operation location="/AddProducts" />
<wsdl:input>
<http:urlEncoded />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddCreditAlerts">
<http:operation location="/AddCreditAlerts" />
<wsdl:input>
<http:urlEncoded />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddStockFigures">
<http:operation location="/AddStockFigures" />
<wsdl:input>
<http:urlEncoded />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="Pinnacle_x0020_Web_x0020_ServicesHttpPost" type="tns:Pinnacle_x0020_Web_x0020_ServicesHttpPost">
<http:binding verb="POST" />
<wsdl:operation name="DatabaseAvailable">
<http:operation location="/DatabaseAvailable" />
<wsdl:input>
<mime:content type="application/x-www-form-urlencoded" />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddCustomers">
<http:operation location="/AddCustomers" />
<wsdl:input>
<mime:content type="application/x-www-form-urlencoded" />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddContracts">
<http:operation location="/AddContracts" />
<wsdl:input>
<mime:content type="application/x-www-form-urlencoded" />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddInstalledEquipment">
<http:operation location="/AddInstalledEquipment" />
<wsdl:input>
<mime:content type="application/x-www-form-urlencoded" />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddProducts">
<http:operation location="/AddProducts" />
<wsdl:input>
<mime:content type="application/x-www-form-urlencoded" />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddCreditAlerts">
<http:operation location="/AddCreditAlerts" />
<wsdl:input>
<mime:content type="application/x-www-form-urlencoded" />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddStockFigures">
<http:operation location="/AddStockFigures" />
<wsdl:input>
<mime:content type="application/x-www-form-urlencoded" />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="Pinnacle_x0020_Web_x0020_Services">
<wsdl:port name="Pinnacle_x0020_Web_x0020_ServicesSoap" binding="tns:Pinnacle_x0020_Web_x0020_ServicesSoap">
<soap:address location="http://10.136.129.245/pinnaclewebservices/maintenance.asmx" />
</wsdl:port>
<wsdl:port name="Pinnacle_x0020_Web_x0020_ServicesHttpGet" binding="tns:Pinnacle_x0020_Web_x0020_ServicesHttpGet">
<http:address location="http://10.136.129.245/pinnaclewebservices/maintenance.asmx" />
</wsdl:port>
<wsdl:port name="Pinnacle_x0020_Web_x0020_ServicesHttpPost" binding="tns:Pinnacle_x0020_Web_x0020_ServicesHttpPost">
<http:address location="http://10.136.129.245/pinnaclewebservices/maintenance.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Thanks in advance.Hi Raja,
Thanks for your prompt reply. I tried changing in the WSDL file the SOAP action parameters (http) like you said and still I got the same error message while testing the interface.
I have corrected the problem by trying a different approach. Earlier I used file option for Client Proxy creation and I got the error message.
Now I created the Client Proxy by using the option URL/HTTP destination ( which was also showing errors earlier but it is OK now after our Network Specialists opened the concerned port.)
Your reply was usefull as it helped me to check the "Soap Action" in the "OPERATIONS" tab of the "LOGICAL PORT" for the client proxy. I have awarded the points for that.
I have seen your Blogs and the your replies to the questions in this form. I would like to thank you and all the like minded contributors of this forum. Keep up the good work.
Regards.
François -
Error in consuming webservices using ABAP
Dear Gurus,
I am trying to consume webservices using ABAP. We dont have XI installed and no java instance installed.
I created a customer proxy through SE80 and generated a proxy class by giving a WSDL link and also defined logical port. Traditionally followed the steps. But while testing webservices , I get a ICF error.
The error is as follows:
SOAP : 1:023 SRT : Processing error in internet communication framework ("ICF error when recieving the response ICM_HTTP_CONNECTION_FAILED)
Please let me know the cause of this error and solution to be provided.
I also tried to call the method from an abap program, But I get CX_AI_SYSTEM_FAULT exception.
Awaiting your replies.
Thanks in advance for your support and valuable time.
Thanks
GurushanthiHi Gurushanthi,
It could one of several problems, examples:
- A firewall setting
- http communication out disabled by Basis team or
- The logical port wasn't configured correctly.
Try the suggestions in this thread to narrow down the reason (particularly the telnet test from the server):
[Re: Error testing external web service ICM_HTTP_CONNECTION_FAILED;
Regards, Trevor -
Consuming webservice in ABAP Webdynpro
Hi all,
I am using SAP ECC 5.0.Can I consume External webservices using ABAP Dynpro.Sending related links will be highly appreciated.
Regards
Sandeep.Sthe thread is marked as answered? is it resolved or are you still looking for an answer
-
Error in Consuming Webservice in ABAP
Hello Experts,
I am very new to webservices in ABAP. just to test the webservice within ABAP, I created a Service Definition which gave me a WSDL URL using the Provider wizard. then I generated proxy class to consume the WSDL URL generated in previous step . I am calling the proxy class within a program as below. It is raising a exception CX_AI_SYSTEM_FAULT . Does anyone have idea what this could be and how to correct it?
TRY.
CALL METHOD TEST->ZTESSTHJKJH
EXPORTING
INPUT = INPUT
IMPORTING
OUTPUT = output
CATCH CX_AI_SYSTEM_FAULT .
CATCH CX_AI_APPLICATION_FAULT .
ENDTRY.
Thanks,
HarkamalHi Harkamal,
It seems that the webservice provider and consumer are on the same server (loopback). It's probably releated with network access. You can follow SAP Note Number 1009109 (Analyzing Web service problems using the ICF recorder) to track down the sent and received soap messages . Alternatively, you can download and use "Webservice Studio", a small freeware program to test the webservice easily. Official website is: [http://webservicestudio.codeplex.com/]
Good luck,
Ozcan. -
Soapfaultcode:1 Error when consuming webservice through abap proxy class
Hi All,
I am facing a issue executing a proxy class created by consuming web service.
I have consumed a web service which queries data from oracle server to process them in SAP.We have created a Proxy class and did the following configurations:
1) Created a logical port using SOAMANAGER
2) In SICF t-code we have selected No proxy setting for local server.
But when we execute the proxy class it gives an error as "SoapFaultCode:1'.
Regards,
Madhu.Hi Madhu,
Please tel us how u have solved it. I am also facing this problem.
I am trying to understand this problem description 'SOAP ACTION name by definition of the logical port.' via the thread Re: Get error "SoapFaultCode:1"Consume web service in ABAP proxy - But couldn't able to understand how to do this.
Thank You,
Regards,
Naresh. -
Consuming webservice in ABAP - empty complexType table
Hello,
I've the following problem:
I consume a webservice, which has two parameters as response-result. The first parameter is a simple type. The second parameter is a table type described as follows in the WSDL:
- <element name="getVarListResponse">
- <complexType>
- <sequence>
<element name="getVarListReturn" type="impl:ServiceResult" />
</sequence>
</complexType>
</element>
- <complexType name="ArrayOf_xsd_string">
- <sequence>
<element maxOccurs="unbounded" minOccurs="0" name="item" type="xsd:string" />
</sequence>
</complexType>
- <complexType name="ServiceResult">
- <sequence>
<element name="_errorMessage" nillable="true" type="xsd:string" />
<element name="_resultList" nillable="true" type="impl:ArrayOf_xsd_string" />
<element name="_successfull_processed" type="xsd:int" />
</sequence>
</complexType>
- <element name="getVarListFromDWDocument">
- <complexType>
- <sequence>
<element name="dwdocumentID" type="xsd:long" />
</sequence>
</complexType>
</element>
- <element name="getVarListFromDWDocumentResponse">
- <complexType>
- <sequence>
<element name="getVarListFromDWDocumentReturn" type="impl:ServiceResult" />
</sequence>
</complexType>
</element>
I created a proxy to consume this service. When I test the proxy directly I get the correct result displayed as XML (the response). When I try to call the service over ABAP code (use the proxy in a report), I've the problem that the complex-type table is empty. The simple type value is correctly filled.
Does anyone have an idea which could be the problem? I guess the mapping of the XML response in the DDIC-types isn't working correctly, but I've no idea why.
Thanks in advance
Cunanan1980Hi Srikanth,
Check this regarding the web service in WDA.
Ist Step : configure Logical Port
http://help.sap.com/saphelp_nw70/helpdata/EN/16/285d32996b25428dc2eedf2b0eadd8/frameset.htm
2nd Step : Generate Proxy Object
http://help.sap.com/saphelp_nw70/helpdata/EN/16/285d32996b25428dc2eedf2b0eadd8/frameset.htm
3rd Step : Instantiating the proxy object & calling the methods exposed by webservice
data: sys_exception type ref to cx_ai_system_fault,
sys_exception2 type ref to cx_ai_application_fault,
client_proxy type ref to zco_myesa, "MY PROXY CLASS
lv_ret_code type int4,
lv_input type zsend_email_input,
lv_response type zsend_email_response.
data: lv_from type string,
lv_from_address type string,
lv_to type string,
lv_to_address type string,
lv_subject type string,
lv_msg type string.
lv_input-from = 'MYSAPTEST'.
lv_input-from_address = '<someAddress>'.
lv_input-to = 'Prashant'.
lv_input-to_address = '<someAddress>'.
lv_input-subject = ' TEST'.
lv_input-msg_body = ' Hi this is wonderfull to see it work'.
try.
create object client_proxy
exporting
logical_port_name = 'BASIC'. " Basic is a TYPE G RFC Destination
call method client_proxy->send_email
exporting
input = lv_input
importing
output = lv_response .
catch cx_ai_system_fault into sys_exception .
data lv_err type string.
lv_err = sys_exception->if_message~get_text( ).
write: / lv_err.
catch cx_ai_application_fault into sys_exception2 .
lv_err = sys_exception->if_message~get_text( ).
write: / lv_err.
endtry.
if lv_response is initial.
write: /'Not Executed'.
else.
write: /'Did Execute'.
endif.
Regard
Manoj Kumar -
Consuming Webservice in ABAP - ComplexType table is empty
Hello,
I've the following problem:
I consume a webservice, which has two parameters as response-result. The first parameter is a simple type. The second parameter is a table type described as follows in the WSDL:
- <element name="getVarListResponse">
- <complexType>
- <sequence>
<element name="getVarListReturn" type="impl:ServiceResult" />
</sequence>
</complexType>
</element>
- <complexType name="ArrayOf_xsd_string">
- <sequence>
<element maxOccurs="unbounded" minOccurs="0" name="item" type="xsd:string" />
</sequence>
</complexType>
- <complexType name="ServiceResult">
- <sequence>
<element name="_errorMessage" nillable="true" type="xsd:string" />
<element name="_resultList" nillable="true" type="impl:ArrayOf_xsd_string" />
<element name="_successfull_processed" type="xsd:int" />
</sequence>
</complexType>
- <element name="getVarListFromDWDocument">
- <complexType>
- <sequence>
<element name="dwdocumentID" type="xsd:long" />
</sequence>
</complexType>
</element>
- <element name="getVarListFromDWDocumentResponse">
- <complexType>
- <sequence>
<element name="getVarListFromDWDocumentReturn" type="impl:ServiceResult" />
</sequence>
</complexType>
</element>
I created a proxy to consume this service. When I test the proxy directly I get the correct result displayed as XML (the response). When I try to call the service over ABAP code (use the proxy in a report), I've the problem that the complex-type table is empty. The simple type value is correctly filled.
Does anyone have an idea which could be the problem? I guess the mapping of the XML response in the DDIC-types isn't working correctly, but I've no idea why.
Thanks in advance
Cunanan1980I solved the problem "accidentally": The name of the Webservice was to long! Changing the name from "EdilogUserManagementWebservice" to "UserManagement" did the trick.
This is probably due to the restricted fieldlength of ABAP-programnames.
Regards
Jan Hempel -
Consuming WebServices in ABAP WebDynPro via webservice proxy code
Hi,
My requirement is to consume a webservice using WSDL(basic authentication) in WebDynPro ABAP. then based on the SOAP response I need to show a pop up message whether the response valid or not.?
I first tested the webservice by creating LPCONFIG Logical Port and generated WebService Proxy class.
It got response correctly with basic authentication enabled each time I send a request.
Secondly I generated webservice proxy code using service calls on creating webdynpro test application with some UI elements. Service call created Nodes,attributes and method correctly.
it's giving me error when it tries to invoke webservice method through generated code.
Question is that How do we code authentication to the webservice method via WebDynPro ABAP code.
I appreciate anyone who worked on this area and taken basic authentication via coding. or worked successfully through coding.
Thanks
Praveenhi
Refer this:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/6066fbe8-edc4-2910-9584-a9601649747d
It might be usefull for u.
Regards
Vivekananthan.S -
Consume WebService in ABAP Web Dynpro
Hi, Is there any How To or step by step document which shows to consume web service in ABAP Web Dynpro.
I've searched a lot but could not find any.
Please provide me some pointer/examples.
Thanks,
CDHi Thomas,
I am facing a problem in consuming web service in webdynpro.
I created a web service for standard FM BAPI_BUS1240_CREATE (it is available in SAP ECC server).
I want to consume this web service in another system (SAP Portal system, where users will be providing input; this FM is not available here).
I created a Proxy class in SAP Portal system through the WSDL document of the Web service.
I configured logical port for the same in TCode: SOAMANAGER and successfully tested the Client proxy (through TCode: SE80). As a result, the record is created in SAP ECC server.
Now, I am unable to do the same through Webdynpro. Please find the attached Proxy class screen-shot. It has 6 methods of which BUS1240_CREATE contains the relevant parameters of the actual BAPI FM.
I filled up the same parameters that I used in Testing the Client proxy but unable to create record in SAP ECC system. My code (On_submit of a button) looks like below,
TRY.
CREATE OBJECT wd_assist
EXPORTING
logical_port_name = 'ZXXXXXXX'. "Logical port configured through SOAMANGER
CATCH cx_ai_system_fault.
ENDTRY.
CALL METHOD wd_assist->bus1240create "Method filled with input parameters given by user
EXPORTING
input = ls_inp
IMPORTING
output = ls_outp.
After execution of method BUS1240_CREATE, system throws the error as below,
The following error text was processed in the system DEP : Error (id=SoapFaultCode:5 ): Web service processing error; more details in the web service error log on provider side (UTC timestamp 20141011062545; Transaction ID 5B0F51E4AD4EF13EA6B9E41F137BE3CC)
Please tell me where I went wrong. Do I need to call methods of the Proxy class? Also suggest if any configuration change involved in this.
Have a nice day, thanks. -
Consuming Webservice from ABAP Program
Hi, I need to consume a WebService https and with SSL. But to begin I tried to use a free webservice.
1-I cant create a Client Proxy, because the ppl from IT of the client dont want to do it.... so no SE80 -> Client Proxy.
The thing is if I use the method "call method cl_http_client=>create_by_destination" Creating of course a registry in the SM59, the free webservice works I can receive the info.
But If I use "call method cl_http_client=>create_by_url" It doesnt works I dont know why is this... I guess that its a IT or BASIS problem.
2- Anyway the method "create_by_destination" dont have a SSL parameter and the create_by_url it does, I find a place to set up SSL in the SM59 but I dont find where to put the name of the SSL that was created in the tx STRUST.
So my question is I can make it works a webservice https and SSL with the method "create_by_destination" or I have to use the "create_by_url" or "create" method.
ThanksHi, Sandra thx for the info. Im now passing this information to check if al the ICM and SSL seeting are correct.
Question in the SM59 in the "Logon/Security" tab I see the SSL activation option and a combo box to select the certificate. I only see two options:
ANONYM and DFAULT
If the Basis team added a SSL certificate in the STRUST it should appears in that combobox like a new entry ? or that combobox allways have only those 2 options. -
Hi PI Gurus,
Can this be done:-
I have to send SO data from CRM System to any 3rd party system.
I have created one WS in CRM and created the proxy out of that,
Now I will use that method of generated proxy class to send data.
Can the end point be changes to 3rd party?
Can we do this without any middle ware tool by using WS only?
Thanks,
Krishna...2. Create Logical Port
You configure runtime features for Web services client proxies using logical ports.
These runtime features can be configured when the Web-service client is activated. An example of such a feature is the URL-call of the Web service, which, if applicable, must be modified by users.
TCODE: LPCONFIG
Enter the Proxy class and Logical Port name. Make sure that Default Port is selected. Click the Create button
Enter a description for the logical port.
Enter the WSDL URL into the URL field
Now we need to add the reference from the actual WSDL code into each operation.
Open up the WSDL in a browser and look for the following:
<wsdl:operation name="MakeUpper">
Below that line there will be another line that has a SOAPACTION defined in it:
<soap:operation soapAction="http://www.deeptraining.com/MakeUpper" style="document"/>
Copy the URL defined in that line into the SOAP Action line.
Save and then Activate the Logical Port -
Consuming a webservice in ABAP ECC 6.0 without using XI/ PI
Hi Experts,
I wanted to consume an external webservice without using XI / PI.After doing my homework and search on sdn I came to know that we can consume webservices in ABAP using proxies using SE80(Enterprise Services).
I am trying to create a client proxy with the URL of webservice.It asks me the option to choose between URL or HTTP.
I am selecting URL and in the second screen it asks about the package details and after that it finishes.Later I get an error message stating "NO VENDOR SPECIFIED".Its not allowing me to create a proxy.
So, here are my questions.
Does anyone faced the same kind of problem?
Can we really consume a webservice without using XI / PI or any other middleware?
Is it possible to consume the webservice only with URL or WSDL file ?
Please let me know the exact process.
Thanks in Advance.
Shanker Pandey.Hi Martin,
Please check these following links. Though you have reported already, these may help
Proxy Object generation error using Wizard for Web Service Consumption
Also, please have a look @ /people/thomas.jung/blog/2006/03/13/develop-a-web-service-that-sends-an-email--in-abap-netweaver-04s
Hope this helps,
Karthik -
How to call a webservice in ABAP?
Hi,
I want to call an external webservice in ABAP coding. Do you know how to write or configue it? Is there any documentation?
Thanks!check out this weblog
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
Raja
PS: please search before posting a question -
Execute external WebService from abap
Hi Gurus!
Is it possible to execute an external WebService from an abap function/program without using the XI?
Best regards,
Adrianoyou can do this.
if you are on WAS6.4 there is a tool available within ABAP work bench to generate client proxy.
if you are on WAS 6.20 then you have to use class cl_http_client to consume the webservice,
check out the following weblogs for code sample
Send SMS to India from ABAP
BSP a Developer's Journal Part XIV - Consuming WebServices with ABAP
Regards
Raja
Maybe you are looking for
-
Infinity Order - BT Fail - terrible way to do busi...
Bit of backstory first, feel free to scroll down the the ### to read my problem I have been eagerly waiting for Infinty to increase the speeds i currently get through my BT line (all be it through BE broadband). The date for the service in BRIDGEND w
-
Alternative AppsLocalLogin.jsp
I want to restrict all users from logging into the system with some exceptions. To achieve this I want copy the AppsLocalLogin.jsp to XXAppsLocalLogin.jsp and provide this to the list of users who are in the exception list. I will also replace the Ap
-
In productive scope XI the configuration of the alert has been presenting/displaying some problems, I believe that you can be so that in these machines it exists to cluster, because in atmospheres DES and QA this working as it corresponds. The proble
-
How to delete resources that have been reference or used somewhere else ?
Is there a way to delete resources even if they have been referenced in some other resource or used in PPMs or Orders etc ? I'll look forward to replies. Regards, Ranjini.
-
Hi my 32G itouch stuck on connect to itunes screen
hi....i am having issues.....a few weeks back my itouch just acted funny and 'died' i thought it was the battery and put on my dock like anyother time....well, after a time on the dock it went to the 'connect to itunes' screen....i cant get it to do