Public webservice for ABAP consumer proxy?

Hello All,
for a soon coming customer project I want to get familar with the implementation of a ABAP webservice consumer. We're on Netweaver 7.0, no XI/PI.
So I simply started at SE80, and tried to create a service consumer, and entered the URL http://soap.amazon.com/schemas2/AmazonWebServices.wsdl as the source for the WSDL.
Unfortunately that gave me an exception CX_SWSDL11_WSIBP11 (A wsdl:binding in a DESCRIPTION MUST use the value of "literal" for the use attribute in all soapbind:body, soapbind:fault, soapbind:header and soapbind:headerfault elements.).
As I'm not focussed on this special webservice - does anybody know a public webservice for which a ABAP webservice consumer could be created easily?
Any help is appreciated.
Thanks & best regards,
Karsten

[Amazon Associates Webservice|http://ecs.amazonaws.com/AWSECommerceService/2008-08-19/DE/AWSECommerceService.wsdl] is literal.
More Details to be found [here|http://docs.amazonwebservices.com/AWSECommerceService/latest/DG/index.html]
Have fun!
anton

Similar Messages

  • ABAP Consumer Proxy error after upgraded from 7.0 SP14 to 7.01 SP3

    The ABAP consumer proxy was created in ECC6 with Netweaver 7.0 SP14.  After the system was upgraded to Netweaver 7.01 SP3 the proxy call started to get error back.
    The first error message from the service provider said "SoapException: Server did not recognize the value of HTTP Header SOAPAction".  This error was resolved by manually putting the correct action in the SOAManager configuration.
    Ran the same test again and then the service provider complained about the To field in the SOAP Header.  The error message said "SoapHeaderException: SOAP header To was not understood".
    Below is the To field in the Requesting XML message from the 7.0 SP14 system that worked fine:
    <n3:To soap-env:mustUnderstand="1" xmlns:n3="http://schemas.xmlsoap.org/ws/2004/08/addressing"
    xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope">
    http://localhost:50081/AddSix.asmx
    </n3:To>
    Below is the To field in the Requesting XML message from the 7.01 SP3 system that did not work:
    <wsa:To soap-env:mustUnderstand="1" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
    xmlns:soap-env="http://www.w3.org/2003/05/soap-envelope">
    http://localhost:50081/AddSix.asmx
    </wsa:To>
    It looks like the issue is with the xmlns:soap-env element that has different values in these two systems.  Searched in SDN but could not find any related information.  Please help if anyone has experienced similar issue or knows how to fix it. 
    Thanks,
    Jiannan

    Got solution from SAP through an OSS message.  Below is SAP's solution:
    Either the Message ID protocol should be switched off on the SAP
    consumer side or turn on this protocol support on the .NET provider.
    To switch off the Message ID protocol:
    1. start the soa manager
    2. find the consumer proxy
    3. find the corresponding logical port
    4. jump to the 'Messaging' tab
    5. choose the 'Suppress ID Transfer' from the dropdown list of the Message ID Protocol field
    Besides this setting I also have to specify the operation in the Operation specific tab of the logical port configuration.

  • How to create  webservice  for  abap  RFC

    how to create  webservice  for  abap  RFC.......................
    plz any could tel me

    I'll answer my own question...
    In SE80 you create the Function Group and something called a Virtual End Point.  These are the only items that transport forward to you QA and eventually your production system.  Everything else has to be created in SOAMANAGER on the target systems. 
    In Development in SE80, when you create the Virtual End Point, this creates a corresponding entry visible in transaction SICF.  When you are done in SOAMANAGER, it creates three more entries in SICF.  The process of transporting the Virtual End Point does NOT create any entries in SICF in QA.  Don't let this be confusing.  In QA, SOAMANAGER will create all four SICF entries.
    Also, if you try to secure the web services using the S_SERVICE object, you must actually test the web service before you can add it to any roles.  This is because the USOBHASH table is not populated for the web service until you actually run the web service for the first time.

  • ABAP consumer proxy generation for xMII WSDL's

    Hi friends,
    I have a question related to generation of consumer proxies in ECC Box. I am trying to create a consumer proxy for xMII WSDL's using URL method. For the first WSDL, I was able to create a service consumer proxy successfullly. It created with the name "XacuteWSSoap". Now, when I am trying to create another consumer proxy, I am always getting the error saying the proxy object already exists. Then, I went to WSDL and compared all of them, they all are having port type as XacuteWSSoap. I believe this is the reason why, it is not allowing me to create a new proxy object for the second WSDL. Does any one know how to overcome this problem?
    Thanks in advance,
    Regards,
    Adithya K

    Hi Gaurav,
         I tried both of the ways. Here are the results.
         If I delete the proxy and create with new prefix its still the same issue I am having.
         And changing the port type seems to work, it allowed me to create a new proxy object. But, again there are few structures which are getting regenerated and overwriting the existing values. Here is the sample WSDL: If you see closely, the complex type "InputParams",  Port type name "XacuteWSSoap",  Input message name "s0:XacuteSoapIn", Output message name "s0:XacuteSoapOut" are the things which are creating problem for me. If I rename all the above things that I mentioned like port type, input message, etc. Its working for me.  But, I dont think this is the correct way of developing these. So, I want to know whether there is any problem with SAP generating the things or I am doing any wrong.
    <?xml version="1.0" encoding="UTF-8" ?>
    - <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.sap.com/xMII" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="http://www.sap.com/xMII">
    - <!--  Types
      -->
    - <types>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://www.sap.com/xMII">
    - <s:complexType name="InputParams">
    - <s:sequence id="InputSequence">
      <s:element maxOccurs="1" minOccurs="0" name="Mode_Read" type="s:string" />
      <s:element maxOccurs="1" minOccurs="0" name="Mode_Write" type="s:string" />
      <s:element maxOccurs="1" minOccurs="0" name="Server" type="s:string" />
      <s:element maxOccurs="1" minOccurs="0" name="TagGUID" type="s:string" />
      <s:element maxOccurs="1" minOccurs="0" name="TagInput" type="s:string" />
      </s:sequence>
      </s:complexType>
    - <s:element name="XacuteRequest">
    - <s:complexType>
    - <s:sequence>
      <s:element maxOccurs="1" minOccurs="0" name="LoginName" type="s:string" />
      <s:element maxOccurs="1" minOccurs="0" name="LoginPassword" type="s:string" />
      <s:element maxOccurs="1" minOccurs="0" name="InputParams" type="s0:InputParams" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:complexType name="Rowset">
    - <s:sequence>
      <s:element maxOccurs="unbounded" minOccurs="0" name="Row" type="s0:Row" />
      </s:sequence>
      <s:attribute name="Message" type="s:string" />
      </s:complexType>
    - <s:complexType name="Row">
    - <s:sequence id="RowSequence">
      <s:any maxOccurs="132" minOccurs="1" type="s:string" />
      </s:sequence>
      </s:complexType>
    - <s:element name="XacuteResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element maxOccurs="1" minOccurs="0" name="Rowset" type="s0:Rowset" />
      </s:sequence>
      </s:complexType>
      </s:element>
      </s:schema>
      </types>
    - <!--  Messages
      -->
    - <message name="XacuteSoapIn">
      <part element="s0:XacuteRequest" name="parameters" />
      </message>
    - <message name="XacuteSoapOut">
      <part element="s0:XacuteResponse" name="parameters" />
      </message>
    - <!--  Ports
      -->
    - <portType name="XacuteWSSoap">
    - <operation name="Xacute">
      <input message="s0:XacuteSoapIn" />
      <output message="s0:XacuteSoapOut" />
      </operation>
      </portType>
    - <!--  Bindings
      -->
    - <binding name="XacuteWSSoap" type="s0:XacuteWSSoap">
      <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    - <operation name="Xacute">
      <soap:operation soapAction="http://www.sap.com/xMII" style="document" />
    - <input>
      <soap:body use="literal" />
      </input>
    - <output>
      <soap:body use="literal" />
      </output>
      </operation>
      </binding>
    - <!--  Service mapping
      -->
    - <service name="XacuteWS">
    - <port binding="s0:XacuteWSSoap" name="XacuteWSSoap">
      <soap:address location="http://abc.dx.com:50000/XMII/SOAPRunner/Test%20-%20DoNotDelete/OPC/Trx-OPCTag_Prototype" />
      </port>
      </service>
      </definitions>
      Appreciate if you can help.
    Thanks,
    Adithya K

  • ABAP consumer proxy generation for xMII WSDL

    Hi friends,
    I have a question related to generation of consumer proxies in ECC Box. I am trying to create a consumer proxy for xMII WSDL's using URL method. For the first WSDL, I was able to create a service consumer proxy successfullly. It created with the name "XacuteWSSoap". Now, when I am trying to create another consumer proxy, I am always getting the error saying the proxy object already exists. Then, I went to WSDL and compared all of them, they all are having port type as XacuteWSSoap. I believe this is the reason why, it is not allowing me to create a new proxy object for the second WSDL. Does any one know how to overcome this problem?
    Thanks in advance,
    Regards,
    Adithya K

    Hi Friends,
        I would appreciate if anyone can help me with this issue.
    Thanks,
    Adithya K

  • Transport Binding in ABAP Consumer Proxy

    Hello Gurus,
    I am trying to call a webservice using ABAP Proxy in Netweaver SPS 15.
    We donot have XI in our landscape.
    This is a siebel web service ( on our intranet ) and the url to call is
    http://abc12345.abc.com:80/eai/wsprj?SWEExtSource=WebService&SWEExtCmd=Execute&Username=TEST_USR&Password=TEST_USR
    I tried to create a logical port ( Transaction LPCONFIG ) and  put this whole URL and it works fine.
    But abc12345 will be different on QA & PRD systems so I have to change in DEV and transport it which is not optimal solution.
    I tried creating an HTTP Destination  and put this into LPCONFIG with a URL suffix of
    "eai/wsprj?SWEExtSource=WebService&SWEExtCmd=Execute" and it fails with Soap Error.
    Is the special character "?" or "&" causing the issue??
    I also tried to create a logical port in Soamanager using manual config and put "eai/wsprj?SWEExtSource=WebService&SWEExtCmd=Execute" in URL access path and it results in Soap error at runtime.
    I tried WSDL based configuration with URL also but cannot even save the port as it gives error is HTTP destination creation. I also tried WSDL based configuration with local file. It creates the port but ignores the "?SWEExtSource=WebService&SWEExtCmd=Execute" part of URL which again gives saop error at runtime.
    Any pointers on where I am going wrong. I want to be able to change these runtime parameters in QA/PRD either using HTTP destination with LPCONFIG or by creating a logical port using soamanager.
    Thank You
    Sanjay

    i can't open your URL link.Can you send WSDL.I think there is some error in URL or in WSDL.When you create  
    logical port in LPCONFIG you can give URL directly just putting ?WSDL at th end of URL and When you click operation tab you will find SOAP Action Name .Provide same in SOAP Action.
    Regards
    Snehasish
    Edited by: Snehasish Das on Nov 23, 2008 12:33 PM

  • Superclass for ABAP server proxy?

    Hi Experts,
    I generated an ABAP server proxy by using a synchronous inbound interface of XI.
    Can someone tell me which superclass does the server proxy use? I am trying to send an attachment back to XI in the proxy response but am not able to write the code of it.
    Please help.
    Thanks,
    Shobhit

    Hi Prateek,
    This blog is for sending attachment in client proxy. (Sending data from ECC to XI using a trigger in ECC)
    But my requirement is to send the attachment in server proxy (XI calling the ECC proxy program which returns the attachment back to XI synchronously)
    For this purpose Im not able to use the code in https://weblogs.sdn.sap.com/pub/wlg/3509. [original link is broken] [original link is broken] [original link is broken]
    The server prxoy does not recognize the statement
    attachment_protocol ?= prxy->get_protocol(
    if_wsprotocol=>attachments ).
    as the superclass of this method is not accessable by this proxy interface.
    HELP!!
    Regards,
    Shobhit

  • ABAP Consumer Proxy. Not working?

    Hello
    I've created consumer proxy in ABAP. Configured logical port in SOAMANAGER. When I test call operation from this proxy I get "Call successful - Empty result" because it is async interface. But it seems that PI (which serves this service) doesn't get anything from ABAP program. How can I monitor or check the log of whar this proxy sends?
    best regards
    Maciej

    Hi guys,
    I'am still facing the same problem. Queues in PI are registered, the async outbound proxy call gives the same message "Call successful - Empty result". But no messages are shown in SXMB_MONI. I've followed the link above. Other messages from sync scenarios are shown. Services (EO, EOIO) are registered and activated.
    In Adapter Monitoring no messages are shown. I am using XI adapter as sender and JMS sender as receiver.
    I've stopped JMS-sendin-Queue and there is no message too.
    My issue was resolved by COMMIT WORK of proxy-call.
    Thanks in Advance,
    Stefan
    Edited by: Stefan Burghardt on Jul 12, 2011 6:32 PM

  • Webservice for ABAP classes

    Hi ,
        This is regarding creating about web service for ABAP classes. On searching SDN forum this is not possible.
        But we should not call methods from a class within the function module used in webservice?
        Please advice.
        Exposing WebService directly from ABAP Class not from BAPI
    Thanks
    Harsh

    [Amazon Associates Webservice|http://ecs.amazonaws.com/AWSECommerceService/2008-08-19/DE/AWSECommerceService.wsdl] is literal.
    More Details to be found [here|http://docs.amazonwebservices.com/AWSECommerceService/latest/DG/index.html]
    Have fun!
    anton

  • How to determine the sender business system for ABAP client proxy

    Hi All,
    I have one doubt: when the client proxy sends the message to XI, how could i know what is the sender business system name for it?
    Is it the logical system which is reflected in Technical System?
    let's say if i have the ABAP system, the technical system is ECC, which has three clients: 001, 066 and 000.
    And the client 001's logical system in ECCCLNT001 (all the client proxy is created in this client). In this case, the sender business system name is ECCCLNT001, am i right?
    If no, please correct me.
    Thanks in advance
    Leo

    Hi lawrence
    When data is distributed between different systems, each system within a network has to be clearly identifiable. The u201Clogical systemu201D deals with this issue.                               
    A logical system is an application system in which the applications work together on a common data basis. In SAP terms, the logical system is a client.
    Since the logical system name is used to identify a system uniquely within the network, two systems cannot have the same name if they are connected to each other as BW systems or as source systems, or if there are plans to connect them in any way.
    Although SAP does not recommend that you connect test systems to production systems, a test system can have the same name as a production system. This makes copying production systems to test systems a lot simpler.
    You are only allowed to change the logical system name of a system if the system is not connected to any other systems, because changing the logical system name would render all the connections to other systems useless.
    Logical system names must contain capital letters and numbers only. SAP recommends the following naming convention for logical system names: <System-ID>CLNT<Client>.
    Regards
    sandeep

  • Error in Calling a Webservice from ABAP: Consumer

    Hi
    We are reaching a webservice within the same network Zone and have have done the configuration in SOAMANAGER - WebService URL, Port, Operations are defined and the service is active. The logical port is define and an automatic SM59 destination is created in the System as well and works fine.
    While trying to call the Class with the appropriate Method it creates an Exception and on logging within SOAMANAGER or ST11 we get the below error. Not sure how to resolve this as webservice is running fine and it seems a problem in reaching to the service. Neither any Payload is visible in SOAMANAGER Log.
    E SOAP_RUNTIME 20081203021828.6099930 : CL_SOAP_RUNTIME_CLIENT
    ->EXECUTE_PROCESSING A SOAP Runtime Core Exception occurred in
    method get_http_headers of class CL_SOAP_HTTP_TPBND_ROOT at
    position id 3 with internal error id 1007 and error text SRT:
    Unsupported xstream found: ("HTTP Code 404 : ") (fault location is
    1 ).
    Anu inputs appreciated.
    //Swetank

    Hi,
    what does the service?
    XString listens to binary data.... With services you exchange xml messages (SOAP)... -> String
    Maybe you have to convert your binary data into string?
    I have created an email service... the attachments must be converted into a base64-String that a service can handle this issue.
    regards

  • Adapter for ABAP server proxy??

    Hi all
    Can anyone tell me why we need receiver agreement (XI adapter) in case of ABAP server proxies???

    Hi Smith,
      The use of XI adapter in abap server proxies is to communicate the IS with its respective R/3 system ( ie application system).Proxies will communicate with the XI server through the native SOAP calls over HTTP . So we need to mention the integration server to connect to the correct application system during runtime.
    Have luk at below links:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/b1/f29e7a56e18a439984a3c6630951d2/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/85/78af1bf407434796aaf8dbd6d4e7b7/content.htm
    Hope this will help.
    Regards,
    Prasanthi.

  • Debug ABAP consumer proxy -- which URL?

    Hi experts,
    I've a question concerning the URL to be used when debugging cunsumer proxies...
    So, I take transaction SICF on my ECC 6.0 backend system.
    In the menu Client --> Recorder --> Activate recording.
    There I just take the user I'm logged on with. Should this user also exist on the SAP PI system?
    Next, I need to fill in the Client URL Path. What should I do there?
    Thanks a lot!
    Dimitri

    Hi guys,
    I'am still facing the same problem. Queues in PI are registered, the async outbound proxy call gives the same message "Call successful - Empty result". But no messages are shown in SXMB_MONI. I've followed the link above. Other messages from sync scenarios are shown. Services (EO, EOIO) are registered and activated.
    In Adapter Monitoring no messages are shown. I am using XI adapter as sender and JMS sender as receiver.
    I've stopped JMS-sendin-Queue and there is no message too.
    My issue was resolved by COMMIT WORK of proxy-call.
    Thanks in Advance,
    Stefan
    Edited by: Stefan Burghardt on Jul 12, 2011 6:32 PM

  • Error while creating logical port for Consumer Proxy in SOAMANGER

    Hi,
    While creating logical port for my consumer proxy in SOAMANGER, I am getting the error shown below
    SRT Framework exception: HTTP: Current user does not have the required authorization to access the HTTP destination
    I have searched in the forums but none of the answers helped me.
    I have specifed my PI user ID and password and the user has the followwing roles assigned to it.
    SAP_BC_WEBSERVICE_SERVICE_USER
    SAP_BC_WEBSERVICE_ADMIN_TEC
    SAP_BC_WEBSERVICE_CONSUMER
    SAP_BC_WEBSERVICE_ADMIN
    Current user in the error message refers to the PI user that i have specified or the user with which i have logged in the backend ABAP system?
    Please help me reslove this issue.
    Thanks and regards
    Sreehari Nambiar

    Hi,
    Please add the following roles as well.
    SAP_BC_WEBSERVICE_ADMIN_BIZ
    SAP_BC_WEBSERVICE_DEBUGGER
    SAP_BC_WEBSERVICE_OBSERVER
    Also make sure that you are doing the role comparison  after adding all SAP* roles in your profile.
    Let me know if this works?
    Thanks,
    Sridhar

  • 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

Maybe you are looking for

  • HP LaserJet 4100N-print queue reverts to pause

    I've been trying relentlessly to get my iMac (early 2008 model) to print on an HP LaserJet 4100N.  I've been able to establish the connection (via ethernet) using the IP address on the printer and configuring as Protocol LPD, HP LaserJet 4100 Series

  • Labview 8.6.1 - builder message vi is password protected

    I am new in Labview 8.6.1 and I am receiving some messages that I can not explain why. While labview is building an executable I have few messages like the one posted in attachment. The messages are related to the vis that are part of Labview library

  • SCRAP DURING CO11N CONFIRMATION

    Dear All, I am facing client sensitive problem regarding scrap confirmation at CO11N. As I am having Production Order of 5 qty & having 3 Operation. Now I have confirmed the first Operation with 5 qty as Yield. for second operation I confirmed 3 qty

  • How to design  databse for binary tree

    kindly help in desiging databse for binary tree and also to retrive data from database.

  • Can BIP excel output calculate result automatically?

    I have generated the output file with XML format. but i had one question: the cell doesn't calculate automatically, it still show excel formula format "=H7 / ( 1 + .17)", not the result of calculation 109.90. BIP version:10.1.3.4.1. Is there any solu