Consuming WS from ABAP- Quality/production environmentsu0085

Hi,
I am able to consume the WS from ABAP. I followed few links in SDN and I am able to do that.. thanks to SDN
Now my issue is.. how it works in Quality and production
I created my class by saving the WSDL in my local fine when I move my object to quality .. the WS also moved from Quality system then the URL changes
How to handle this situation.. do I need to regenerate the proxy again with new WSDL or is it ok to change only Logical port

Hello,
The service-interface, operations and so on are the same - only the "target" is different. So it's ok to change only the logical port on each system.
Regards
Thomas

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

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.
Thanks

Hi, 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.

Problem using webservice method consumer proxy with rawdata from abap

Hello Gurus,
I am struggling with an error using a proxy consumer service from ABAP. The proxy was generated using the WSDL from the web service provider. For a specific method we need to send a rawstring as seen bellow:
The file to be sent on this call is a ZIP file XAdES-BES signed and on BASE64. I’ve implemented the proper code to get the original file from local PC, and convert it to BASE64 before moving the content to the webservice structure and call the service proxy. At SOAMANAGER I also configured the webservice and the proper port with the WSDL:
The communication is working properly but my problem is with the binary content. When calling the webservice the response is that the structure of the file is wrong. I found it very strange since I used a tiny SOAPUI project with the same WSDL and it worked with no problem.
After debugging I could see that the content moved to the rawdata string before calling the proxy does not match the content that I can see from the call payload on web services util (srt_util)!
So the sample code for my method:
* get the file from the specified folder
call function 'GUI_UPLOAD'
exporting
filename                = ld_zipfilename
filetype                = 'BIN'
importing
filelength              = zip_size
tables
data_tab                = t_zip_data[]
exceptions
file_open_error         = 1
file_read_error         = 2
no_batch                = 3
gui_refuse_filetransfer = 4
invalid_type            = 5
no_authority            = 6
unknown_error           = 7
bad_data_format         = 8
header_not_allowed      = 9
separator_not_allowed   = 10
header_too_long         = 11
unknown_dp_error        = 12
access_denied           = 13
dp_out_of_memory        = 14
disk_full               = 15
dp_timeout              = 16
others                  = 17.
* convert to string
clear buffer_zip.
call function 'SCMS_BINARY_TO_STRING'
exporting
input_length = zip_size
importing
text_buffer = buffer_string
tables
binary_tab   = t_zip_data[]
exceptions
failed       = 1
others       = 2.
* encode base 64
perform encode_base64 using buffer_string
buffer_zip.
form encode_base64 using in_string type string
out_string type xstring.
data: l_sbuff     type string.
* convert the file to BASE64
call method cl_http_utility=>encode_base64
exporting
unencoded = in_string
receiving
encoded   = l_sbuff.
call function 'SCMS_STRING_TO_XSTRING'
exporting
text   = l_sbuff
importing
buffer = out_string
exceptions
failed = 1
others = 2.
endform.                    "encode_base64
calling the webservice:
l_input-xxxx-dokument = buffer_zip.
try.
call method l_proxy_test->webservice
exporting
input = l_input
importing
output = l_output.
catch cx_ai_soap_fault into lr_exc_soap_fault.
    endtry.
From my understanding rawstring should be the same as ABAP xstring. If I debug the program and check the content of the l_input-dokument before calling the proxy I get binary content: “Izw/eG1sIHZlcnNpb249IjEuMCIgZW5jb2Rpbmc9InV0Zi04Ij8…” that is in fact correct
If I check the payload after call I can see that the binary content sent on the XML is not the same, in fact it is totally different: ”SXp3L2VHMXNJSFpsY25OcGIyNDlJakV1TUNJZ1pXNWpiMlJw…” !!
I’ve tried a lot of different conversions, changed configuration on the communication, port, etc and nothing seems to work. I really can’t figure out why the binary content on the call is not the same as I move to the webservice structure.
If I use the project from SOAP UI and send the proper binary content, that is “Izw/eG1sIHZlcnNpb249IjEuMCIgZW5jb2Rpbmc9InV0Zi04Ij8…” it works perfectly and the response is successfully.
Anyone has a clue what could be causing this?
Appreciate any kind of input.
Regards,
João Silva Pinto.

Anyone? Any clue would be appreciated.

Error Consuming a webservice from ABAP

Hi all,
I am consuming an external webservice from abap. I created teh proxy using WSDl file. While testing teh service its giving an exception like this-
"JAXB unmarshalling exception: Unable to create an instance of de.*******v2.MeldungType; nested exception is javax.xml.bind.UnmarshalExcept
ion: Unable to create an instance of de.****.MeldungType# - with linked exception:#[java.lang.InstantiationException]"
With a soapfaultcode: 1..
can any one help out in arriving at teh reason for this..
Regards
Sandeep

I've seen lots of unmarshalling errors whilst trying to consume web services via Web Dynpro Java... Usually, it was due to an inconsistency between the WSDL file being used and the underlying web service definition. It might be worth checking the WSDL you are using is correct and up to date, in case the underlying service interface has changed.
Also worth checking if you have any simple boolean type parameters defined as part of the service interface - they have to have a value assigned when you call the service and cannot be null.
HTH.

Windows authentification while consuming web service from ABAP

Hi All,
We are consuming web service from ABAP, we have created client proxy in SE80 and configured logical port in LPCONFIG.
This one was working fine. Now we have added windows user authentification to access this service.
Now when I'm trying to regenerate this proxy in R/3 it is asking for user and password. When I enter these details this one is not working.
If I access this service direcly from internet explorer and I enter same user and password then I would able to access this service.
Could you please let me know how to handle this.
Regards
Vikram

The dialog that is produced by HTTP Destination object of the logical port is designed only for use within Classic Dynpro applications. There is no prompt produced when running in Web Dynpro. If possible assign a generic user within the logical port definition and this will be used automatically by all users.

Web Service Call From Consumer Proxy in ABAP: Security Settings

Hello All,
Have a couple of questions:
We are working on a scenario where we have to connect to a web service from ABAP. We have extracted the WSDL, and generated the client proxy, and configured a Logical Port. However, at the time of actual call, we receive an error message "Header http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate recipient is required but not present in the message.". We suspect that this is a problem with the SOAP Header, which might be missing some tags, which are required by the Web Service. Problem is, we can not trace the Web Service SOAP Header. We can not see it in SOAMANAGER, or any other transaction as such.
1. Does any body have an idea where to look for the complete SOAP Request, in case of a Consumer Proxy call?
2. After re-configuring the Logical Port in SOAMANAGER, our scenario is now stuck at an error which says: 'SoapFaultCode:1 Security requirements are not satisfied because the security header is not present in the incoming message.'. This is probably happening because the target web service is WSE 3.0 compliant, and hence it is asking for UsernameToken and TimeStamp attributes in SOAP Header. In SOAMANAGER Logical Port configuration, we do not see a placeholder for providing this information. However, in earlier LPCONFIG transaction, there was a field for providing WS Security Profile for Operations. Where does this config lie in SOAMANAGER?
Awaiting Replies.
Thanks and Regards,
Sid

Hi Sid,
The setting username/password in the manual logical port configuration will send the username and password in the http header as basic authentication. That's why you don't see a security header.
To configure usernametoken you have to create the logical port out of a WSDL. This WSDL needs to contain WS-Security Policies . So in the policy section of the WSDL you see an XML element called UsernameToken.
In order to let .Net generate a compatible WSDL you have to configure your WCF Web Service to use a CustomBinding with authentication "UsernameOverTransport". This is a username token in the security header send over SSL. So therefore you need an HTTPSTransport (instead of HTTPTransport) in the binding of your .Net WCF endpoint as well.
For an example of such a WCF service configuration see my comment on http://weblogs.sdn.sap.com/cs/user/view/cs_msg/59671.
Regards,
Mathias

Am I the only one that has had every charging cable (for my iPhones and my iPads) fail? Very frustrating. I got used to quality products from Apple but seems the small stuff is being overlooked nowadays.

Am I the only one that has had every charging cable (for all of my iPhones and all of my iPads) fail? Very frustrating. I got used to quality products from Apple but seems the small stuff is being overlooked nowadays!

I have yet to have a cable for my iPad 3, iPad 4 or iPhone 5 fail. I have multiple cables for each device without any failures.

Create an SAP Web Service Consumer (calling External Sharepoint Web Service from ABAP)

hi all,
i am trying to
Create an SAP Web Service Consumer (calling sharepoint Web Service from ABAP) using blog given on following link
Create an SAP Web Service Consumer (calling External Web Service from ABAP)
but when i am using my url at the end of step 3, i am getting error as follows:
i dont want to use local file option. Can anyone help me in this??
thanks in advance
regards,
SDS

Hi SDS,
you recieved a http 404 error when trying to access the Sharepoint Web service. Http 404 indicates that the resource is not reachable (cf. HTTP 404 - Wikipedia, the free encyclopedia). There could be different reasons for that. I'd suggest rubble checking the URL of the Web service first. Try to access it from a browser on you desktop. If the URL is correc. Most likely the SAP system is not able to connect to the URL. This could, for example, be due to some firewall restrictions. You should ask a SAP Basis colleague if they are able to access the URL of the Web service from the server on which the SAP system is running.
Christian

How to consume WEB SERVICES from ABAP ??

Q: How to consume WEB SERVICES from ABAP program??
     the point here is i am using SAP release 620 and the creation of proxy is out of scenario
     and also no XI.    Its only through ABAP program i need to consume one web service (its a HTTPS one ),
    Using cl_http_client... i tried it but i am totally confused of whats happening ???
Req some senior ppl advice on the same/approach.
any hints will suffice my way of approach...!!!
Please do put in your valuable advices..!!
Thanks in advance..!!!!

Hello Srinivas,
Following is the code for calling web service:
data: client type ref to if_http_client,
      host   type string value 'server url',
      service type string value '8080',
      path type string value '/sap/public/ping',
      errortext type string,
      proxy_service type string,
      scheme type i value 1.
call method cl_http_client=>create
exporting host = host
        service = service
     proxy_host = host
   proxy_service = service
   scheme        = scheme
importing client = client
exceptions
    argument_not_found = 1
    internal_error     = 2
    plugin_not_active = 3
    others             = 4.
case sy-subrc.
when 0.
     write 'Server reached successfully'.
when others.
     write: 'sy-subrc =', sy-subrc.
endcase.
Once you got the client object you can call following methods:
"Set the requrie URL for the web service you want to call. This is not WSDL anyway!!
cl_http_utility=>set_request_uri( request = client->request
uri =' url 2 be called ').
*Then you can call send method with proper inputs for sending request to WS
CALL METHOD client->send
Then you can use receive method for getting the response
CALL METHOD client->receive
*You can get last error in case of exceptions
CALL METHOD cl_http_client=>get_last_error
*Close the client object
CALL METHOD client->close
For more information on full code refer my link in previous replay.
Thanks,
Augustin.
Edited by: Augustarian on Aug 18, 2009 1:49 PM

Consume external webservice from ABAP

Hello all,
Can we consume external web service from ABAP??
If yes please gimme a sample code to do that..
Thanks in advance..
Regards,
Maya

Can we consume external web service from ABAP in version 4.7??

Consume Portal created web service from ABAP

I've done an EJB in Developer Studio, generated a WebService in the same tools and deployed then in Application Server. After that, I run the WS Navigator. The webservice receives a string and returns a List (java.util.List) and is working fine.
This WebService needs to be consumed from ABAP (7.0).
I am geeting multiple options to download WSDL. Which on should I sennt to the ABAPER? Earlier on I send the Default->WSDL. But it is giving some garbage in the return type and the return data type is improperly apped as ANYTYPE rather than a sequence with string within.
2 questions:
Should I send the Default->Download SAP WSDL to the ABAPER?
Why is not ABAP recognising the return type properly? Is there any manual activity in changing the WSDL before sending it to the ABAPER?

Closing for other questions.

Can any help me on consuming rest web services from Abap..

Basically I have an rest based url which i have to call from ABAP, The url has to be passed with some input XML PARSE..How do i do it any idea??
i have tried cl_http_client calls in my case i'm having a problem in passing input xml.

Please post to one of the ABAP SCN Spaces. Each SCN Space has an Overview tab and this tells you what products the Space "supports". To find the ABAP Space see:
SCN Site Index
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter

Consuming SAP HANA from ABAP

Dear all!
I am trying to get data FROM HANA into ABAP AS (so an opposite unusual direction ).
What is the best way of connecting them? Can't find any description.
In Simple words: I have an ABAP program. Now i need connect to Hana (RFC, whatever), then from ABAP program send SQL statement into HANA and then get data back.
What is the easiest/best way?
BR, Dmitry

Hello,
please check SAP HANA Database - SQL Script Guide
page 43 - chapter Calling SQLScript from ABAP
https://service.sap.com/~sapidb/011000358700000604932011
There is nice example how to call SQL Script from ABAP (this also includes calling SELECT statements).
Tomas

Data passed from ABAP proxy not reaching PI...

Hi,
My scenario is
ECC ABAP Proxy --> PI --> legacy
In dev box, it is working fine, when data is sent from ECC dev, it reaches PI dev.
But when data is sent from ECC quality, data is not reaching PI quality.
This set up has already been in production and working fine.
I have done some minor mapping changes only in ESR and moved to PI quality. Nothing changed in the Integration builder side.
But a client copy was done from ECC prod to ECC quality (not PI systems). Will this have any impact on proxy ?
What can I check to make sure everything is in place ?
Pl advise.
thnks

Hi,
In SLDAPICUST the SLD server host and port will be maintained. The ECC will use this to connec to SLD at runtime and get the business sytem details. This can be checked via transaction SLDCHECK.
Also what the transaction SPROXY says in the ECC system. Is it connecting your PI system and loading the ESR information?
There are a few more configuration that needs to be checked in ECC system for proxy communication, I think this blog can help you.
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
regards,
francis

Consuming WS from ABAP- Quality/production environmentsu0085

Similar Messages

Maybe you are looking for