Soap Receiver Adapter - No Response Message

Hi, I've got the following scenario: Idoc - XI - Webservice. I've imported the WSDL from the .NET webservice and used the input and output messages in a syncronous interface.  I've setup a SOAP Receiver adapter with the Webservice details.  Everything is working fine when I call the webservice and the data is received 100% at the target system, but I am not getting ANY response back on XI.
RECEIVER SOAP ADAPTER Audit LOG:
2008-01-24 16:41:57 Success SOAP: request message entering the adapter with user J2EE_GUEST
2008-01-24 16:41:57 Success MP_LEAVE1
2008-01-24 16:41:57 Success The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.
2008-01-24 16:41:57 Success Acknowledgement creation triggered for type: AckNotSupported
2008-01-24 16:41:57 Success SOAP: completed the processing
2008-01-24 16:41:57 Success SOAP: continuing to response message 83638fb0-ca8a-11dc-b36c-00145eed9500
2008-01-24 16:41:57 Success SOAP: sending a delivery ack ...
2008-01-24 16:41:57 Success SOAP: sent a delivery ack
2008-01-24 16:41:57 Success The message status set to DLVD.
2008-01-24 16:41:57 Success Acknowledgement sent successfully for type: AckNotSupported
Has it got anything to do with the "AckNotSupported" type?  Is "AckNotSupported" the default setting for the receiver SOAP adapter?  If so, where do I change this setting?
When I call the webservice with the exact same input using a standalone tool, I get the response message back 100%.  Any help will be appreciated.
Thanks
Rudi

Hey
you are confusing between a response and an acknowledgement.
response and acknowledgement and not one and the same thing.
response is basically used when you send some query to the receiver system and expect a set of value(s) for your query.for e.g sending a query to a Database(JDBC) or SAP system(RFC)
and acknowledgement is just a notification that the message was receiver by the receiver correctly,it does not returns you a set of value(s).
now coming to your question,ALEAUDIT IDOC is generated when an IDOC is posted,since in your case you are not posting and IDOC,instead your are sending it ,i m not sure if ALEAUDIT will be generated or not,one thing that will come to your rescue is that every receiver SOAP adapter expects a HTTP response(irrespective of you explicitly asking it or not).
a HTTP 200 means that messages were posted successfully,and HTTP 500 means application error,get this HTTP response and send it back to the SAP system,most probably you would need to use BPM for this.
Thanx
Aamir
Edited by: Aamir Suhail on Jan 24, 2008 11:26 AM

Similar Messages

  • SOAP Receiver Adapter - Read Header data on Synchronous Response

    I have a scenario - flat file to SOAP. The web service provider sends a response that contains data in the Header that I need to access. I have tried to use the "Do Not Use SOAP envelope" option on my receiver SOAP adapter, and I have configured my request message type to include the soap envelope elements. However I'm getting the following error from the web service
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Cannot process the message because the content type 'application/xml' was not the expected type 'text/xml; charset=utf-8'.
    I've read some inputs on this error that say to use the Transform bean to adjust the content to text/xml. However I'm not sure how to do that. If that is the correct resolution to my problem, can someone provide detailed steps on how to add the Transform bean to the adapter module. I have no experience with adding items to the module tab.
    If there are other ways to tackle this scenario to get access to the SOAP Header from the SOAP receiver adapter, please share those as well.
    Thanks in advance.
    Chris

    Resolved with the following blog
    /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi

  • SOAP receiver adapter message: PI payload in parameter or body

    Hi,
    We tried to send messages via the following way to an external partner: SAP --> IDoc > XI (7.1)> HTTP(s) --> external partner.
    We tried 2 techniques:
    1. using a HTTP receiver communication channel with HTTP destination (using certificate).
      As the path prefix in the destination, including parameters,  exceeds 256 characters, we had to search for another solution
    2. using the SOAP receiver communication channel with a target URL (https string) and indicator 'Do not use SOAP envelope' set   
      When sending the message, the body of the message, the IDoc XML payload doesn't seem to be read by the partner, probably related to the fact that they do not use the right software to do so, as decribed in forum: 
    SOAP receiver adapter error (SOAP receiver adapter error.)
    Is this the right interpretation and is there no other solution than try to append the payload to the parameterlist ?
    Regards,
    Jan Macken

    The partner found a way to read the body correctly

  • Usage of Module processor in SOAP Receiver Adapter

    Hi,
    I have scenario where I am calling an external Web Service via XI. Unfortunately I need Java Mapping to generate the complete SOAP Message (there are some special header elements required by the Web Service)  and flag 'no soap' in the SOAP Receiver Adapter. This works fine, but I have additional Web Service Calls that have the same Header logic and I don't want to use Java Mapping all the time.
    I was wondering if it is possible to use graphical User Mapping for the Business Data that goes to the SAOP Body as a payload and use Java code to generate the SOAP Message (actually the SOAP Wrapper and the Header).
    Can I do this in XI using the Module processor in the SOAP Receiver adapter or do I have to use two mappigs, one based on the Graphical mapping and another using Java Mapping? Is it feasible at all in XI?
    Thanks in advance.

    Hi,
    You can use Module Processor.
    But,
    1. If it is a synch call, in when the message is going from the SOAP adapter to the Webservice, you will need to manually Add the SOAP header as you want . ( you will need to create the entire SOAP mesage as the output of the Module ).
    2. When the response comes back, the same module will need to remove the SOAP header etc and pass a valid , XML message to the Graphical mapping.
    If you have a requirement that some fields of the SOAP header will be needed to be accesed in the Response mapping, then you would need to either add this field to some field in the response payload.
    Better option would be to use, Either a Java or a XSL mapping that does all the required stuff for you.
    Regards
    Bhavesh

  • SOAP Receiver Adapter Proxy Settings

    Hi Guys,
    I am trying to send a SOAP message to an external webservice. I was able to get the message to arrive at the webservice when I used a proxy without user authenication.
    I now need to get the SOAP adapter to use a proxy with user authenication.  I have added the username and password on the communication channel, but I keep getting the following response error:
    com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML
    Has anyone got a suggestion as to how I may go about fixing this problem?  Is there somewhere else that I need to configure the proxy server and user to allow the SOAP Receiver to send a message out?
    Thanks very much,
    Miguel

    Hi Abhy,
    I have checked the settings and they appear to be correct according to the help files.
    I know that it has something to do with the authenication in the proxy server because the only thing that I have changed is the proxy server from a server that required no authenication to one that requires authentication.  I have added the username and password and am getting this error.
    According to the sap help, it is either a wrong target URL or invalid authentication.  But the url worked previously, so it is definitely something to do with the authenication.
    I have added this info on the communication channel.  Is there somewhere else that I should add the proxy settings?
    Thanks,
    Miguel

  • Soap Receiver Adapter Error. Pls advice urgent

    Hi All,
    While using Soap Receiver Adapter for synchronous communication
    *My Soap Request is:*
    <?xml version="1.0" encoding="UTF-8" ?>
    <ns1:SendMessage xmlns:ns1="urn:MMWebSrvService">
    <strFrom>XI</strFrom>
    </ns1:SendMessage>
    *My Soap Response from server is:*
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!-- Inbound Message
    -->
    <tns:SendMessageResponse xmlns:tns="urn:MMWebSrvService" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <return xsi:type="xsd:int">-1</return>
    <strErrorDescription xsi:type="xsd:string">String reference not set to an instance of a String. Parameter name: s</strErrorDescription>
    </tns:SendMessageResponse>
    How to resolve the error.
    Regards

    Henry,
    Your xml message is not xsd compliant...see if you can generate a xml message using your wsdl with random values, compare that to your imcoming msg..and thats your issue..
    Hope that helps
    Regards
    Ravi Raman
    Reward points if helpful !

  • SOAP Receiver Adapter / Scenario calling WebServices

    Hi Experts,
    I am trying to call a web service.  Configured a SOAP Receiver adapter. Message to Web Service goes fine but not shown with Checkered flag, but with icon with description "Log Version".
    In response message for the request Error Category - MAPPING and Error ID "Cannot Read Payload".
    Any ideas to clear this problem. I do have response mapping assigned to Message Interface.  Message Interface is Synchronous.
    Thanks in advance for any solutions.

    can you verify that you are getting a response..try re-routing that to tcpgw and check if content is in line with expected response.
    Regards
    Ravi Raman

  • SOAP Receiver Adapter Always "Running"

    I have a SOAP receiver adapter that is working fine.  I call an MDM web service, which sends a response, but I do not need it.  I have tried a synchronous and asyncronous interface.  Both work fine.
    But...with both, the communication channel monitor in RWB always shows a Short Log of "running". 
    Is this right?  I expected that the Short Log value would reset to inactive or something.
    Processing Details...
    2009-01-28 10:13:29 Success Message successfully received by messaging system. Profile: XI URL: http://snadc80i:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
    2009-01-28 10:13:29 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
    2009-01-28 10:13:29 Success Message successfully put into the queue.
    2009-01-28 10:13:29 Success The message was successfully retrieved from the receive queue.
    2009-01-28 10:13:29 Success The message status set to DLNG.
    2009-01-28 10:13:29 Success Delivering to channel: SOAP_MDMIn_MDMUpdateRecord
    2009-01-28 10:13:29 Success MP: Entering module processor
    2009-01-28 10:13:29 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    2009-01-28 10:13:29 Success SOAP: request message entering the adapter with user J2EE_GUEST
    2009-01-28 10:13:29 Success SOAP: completed the processing
    2009-01-28 10:13:29 Success SOAP: sending a delivery ack ...
    2009-01-28 10:13:29 Success SOAP: sent a delivery ack 2009-01-28 10:13:29 Success MP: Leaving module processor
    2009-01-28 10:13:29 Success The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System. 2009-01-28 10:13:29 Success The message status set to DLVD.
    Thanks,
    Keith

    Short Log only displays the status of communication channel. So if it says running, then it would mean that the channel is in running status. When not in use, it doesn't get deactivated itself. I guess "running" is what people wait to see
    Regards,
    Prateek

  • SOAP Receiver Adapter (Asynchronous Call)

    Hi All,
    Scenario is  Proxy to Webservice asynchronous call.
    Scenario configuration is done as follows.
    1) Imported the WSDL and using as a asynchronous inbound interface.
    2) SOAP receiver channel is configured with the target URL & soapAction as given in the WSDL as (soap address & soap Action).
    3) Configured the proxy server details as required.
    SOAP channel is successfully sending the message to the application as DLVD.
    But the issue is target application  not receiving the data. What could be the reason ? I am wondering , i have tried with the external tool like Altova XML Spy & SOAP UI  sending data to the webservice & it's  working fine.
    Please suggest me if anything which can help to resolve this issue.
    Thanks
    Ashwin

    In this case you can do the following:
    1. start your tcpmon or TCPGateway, add there a listener e.g. on port 9090
    2. configure the target URL in TCPGateway for this listener
    3. configure the target URL in your XI SOAP Receiver Adapter to http://<ip of TCPGateway>:9090
    4. now execute the scenario again in XI
    (make sure XI can reach your TCP Gateway, e.g. check Proxy)
    I have used this method successfully for error tracking. In some cases it is necessary to add 2 listeners in TCPGateway and route e.g. 9090 to 9191 and from there to the end (I did not analyse why).
    Then you will be able to see what XI is really sending and you will see the full response from the partner side. You can then compare the XI request data with those which are sent via soapUI. This should give a clue about the problem.
    CSY

  • No SOAP Envelope error in SOAP Receiver Adapter

    Hello Friends,
    Informaiton:-
    I have configured one Synchronous scenarion for SAP R/3 to PI 7.1 to Java based web applicaiton.
    On the Receiver/Outbound side, i have configured the SOAP Receiver Adapter with the Target URL and SOAP Action.
    Outbound and Inbound service interfaces have Request/Response and Fault messages.
    Issue:-
    While sending the Message, Below error is noticed in ABAP stack SXMB_MONI during the Call Adapter Stage and also in RWB (Channel Monitoring) .
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: No SOAP  Envelope but 1 {}RESPONSES; HTTP 200 OK
    I also found that Request message is not reaching to the Java Web server.
    I am taking the Same message Payload (found at Call Adapter Stage) and ussing it in XML Altova SPY Web client tool. There it is running scuccessfully and getting the Response message.
    please suggest.
    Thanks & Regards
    Jagesh

    Hi,
    Yesterday i consumed the same WSDL file in Altova XML SPY and there it is working, getting the Response.
    Now comparing the SOAP Request message reaching to the Third party Web server (which fall within the same Lane network)
    from SAP PI and Altova XML SPY tool. I used TCP Gateway for the below scenarios.
    (1)First i sent the SOAP message from PI and observed the RESPONSE message without the SOAP Envelope in TCP Gatway Trace and hence i am getting the No SOAP Envelope Error in PI.
    (2)I consumed the same WSDLfile in Altova XML SPY and sent the SOAP message, here i got the Proper SOAP Response message and hence success in this case. (Used the same Data Payload as used in point 1)
    (3)Now to identify the issue in the SOAP Request message being sent from PI, i used the same SOAP message sent in step 1 here, that means copy the entire SOAP ENvelope from the TCP gateway Trace and pasted it in Alota Spy and sent, there it is found running (got the response message from Third Party server).
    One difference i found in HTTP Protocol statements in SOAP Request message in Point no 1 and Point no 2 above.
    HTTP Protocols in Point 1 (Through PI).
    POST  HTTP/1.0
    Accept: /
    Host: 172.24.138.142:4544
    User-Agent: SAP-Messaging-com.sap.aii.af.sdk.xi/1.0505
    CallingType: SA
    content-id: <soap-00306EEAC2051ED1839136CEE8564900 sap.com>
    Content-Type: text/xml; charset=utf-8
    Content-Length: 1195
    SOAPACTION: "Action1"
    HTTP Protocols in Point 2 (Through Altova).
    POST / HTTP/1.1
    Content-Type: text/xml
    User-Agent: XML Spy
    SOAPAction: "Action1"
    Host: 172.24.138.142:4544
    Content-Length: 1195
    Connection: Keep-Alive
    Cache-Control: no-cache
    Thanks to Mr. Stefan Grube for writting such a nice blog.
    Troubleshooting SOAP, HTTP and Mail Adapter Scenarios with TCPGateway
    Experts, please suggest me further.
    Thansk & Regards
    Jagesh

  • URL in SOAP Receiver Adapter

    Hi,
    I was given a WSDL file which contains the following:
    <wsdl:port name="ZISU_INSTLN_CREATE" binding="tns:ZISU_INSTLN_CREATE">
      <soap:address location="http:// hostname:port /sap/bc/srt/rfc/sap/zisu_instln_create/100/zisu_instln_create/zisu_instln_create" />
    </wsdl:port>
    I've configured a SOAP receiver adapter. In the URL i put the SOAP address location from the WSDL.
    Is this correct?
    I am seeing the following error when i try to send a message:
    Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection refused: connect.
    Is the error because of the url I use?
    Thx
    Robert

    Hi,
    I do have details in the message:
    - <detail>
    - <ns:SystemFault xmlns:ns="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/">
      <Host>undefined</Host>
      <Component>COREMSG</Component>
    - <ChainedException>
      <Exception_Name>CX_SOAP_CORE</Exception_Name>
      <Exception_Text>SRT: Wrong Content-Type and empty HTTP-Body received: ("HTTP Code 200 : OK")</Exception_Text>
      </ChainedException>
    and there is  lot more if it helps finding the error, but maybe this is already enough.
    Also i tried testing with SOAPUI now:
    Result is good. I dont get error's. I get a response from my request as expected.
    But if I test with XML from the RWB, with he same data as in SOAPUI, i get the error message again.
    Conclusion:
    SOAPUI can communicate with my SAP ISU system.
    But PI cannot communicate with it.
    Why?
    Thx
    Robert

  • Dynamic URL in SOAP Receiver adapter

    Hi all,
    I have a scenario where I am using a SOAP receiver adapter to send a cXML document to some vendors. I need to change the URL based on the vendor number (passed by sender SRM system). So I have created a user-defined function and used in message mapping to assign the right URL to the variable TServerLocation. But the communication channel still prompts for a static URL which appears to be a mandatory field. Even though the DynamicConfiguration tab in Message Monitoring shows that the TServerLocation was correctly assigned, the scenario does not work when I put some dummy in the static URL field like 'dummy' or '*'. Any ideas on how to make the communication channel go for the dynamic URL field and ignore the static URL field? I have already selected the'Use Adapter Specific Message attributes' and 'Variable Transport Binding' check boxes. Am I referring to the correct variable that references the target URL? Also other than the two checkboxes that I mentioned, I am not displayed anything else under "Adapter Specific Message Attributes" section in the comm. channel.
    Thanks

    James,
    I ve just been digging into SAP help, and have tried it too ... Looks like it doesnt work the way it is supposed to.
    Anotheer point i found was, in the FILE ADAPTER, when we say ADAPTER SPECIFI ATTRIBUTES , we can select the attirbutes.. This is not possible in a SOAP adapter...
    Maybe, we can only access the ADAPTER SPECIIFC ATTIRIBUTES of a SOAP adapter, but cannot set them dynamically.
    Let me know if you find something on this issue.
    Regards,
    Bhavesh

  • SOAP receiver adapter digest authentization

    Hallo,
    I have scenario with SOAP receiver adapter configured as follow:
    Adapter Type: SOAP
    Transport Protocol: HTTP
    Message Protocol: SOAP 1.1
    Adapter Engine: Integration Serer
    Target URL: http://localhost:8099/webservices/test_v1_1_2
    Configure User Authentication
    User: ****
    Pasword:****
    but WS need digest HTTP authentication and SOAP adapter send in header Authentication: Basic.
    Hou can I change authentication method for SOAP protocol?
    Thx

    Hallo,
    I solved this problem by using AXIS framework. I hope that this short instruction help to someone.
    1. In SOAP receiver CC you have to set up Transport Protocol to HTTP(AXIS) and Message protocol to AXIS
    2. Now you can switch Authentication to Digest (NOW adapter will still send Basic!!!  Digest Authorization is Supported only by the following handler: com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender)
    3. On Module tabs in section Module configuration change type HTTPSender to CommonHTTPSender:
         (trp  handler.type  java:com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender)
    4. Save and Activate
    Before you start to use AXIS framefork you have to deploy necessary library.
    This thread help:
    Re: How to install SOAP Axis adapter and where is it available  ??
    Be carefull, for digest authorization you have to linked Optional library "Jakarta-Commons HttpClient" too.
    Good luck.
    JK

  • SOAP Receiver adapter error. SOAP CALL Failed

    Hi ,
        I am implementing scenario R/3->RFC adapter->XI->SOAP REceiver adapter->Web Service (Synchronous). I am getting the error.
    SOAP: call failed
    SOAP: error occured: java.net.ConnectException: Connection timed out
    Message log is as below.
    Any clue ?
    Thanks & Regards,
    Mathew
    2005-10-31 18:59:58
    Success
    output
    1130810398454
    The message was successfully received by the messaging system. Profile: XI URL: http://host:Port/MessagingSystem/receive/AFW/XI
    2005-10-31 18:59:58
    Success
    output
    1130810398458
    Using connection AFW. Trying to put the message into the request queue.
    2005-10-31 18:59:58
    Success
    output
    1130810398458
    Message successfully put into the queue.
    2005-10-31 18:59:58
    Success
    output
    1130810398459
    The message was successfully retrieved from the request queue.
    2005-10-31 18:59:58
    Success
    output
    1130810398459
    The message status set to DLNG.
    2005-10-31 18:59:58
    Success
    output
    1130810398460
    Delivering to channel: CC_CALCULATOR
    2005-10-31 18:59:58
    Success
    output
    1130810398564
    SOAP: request message entering the adapter
    2005-10-31 19:03:07
    Success
    output
    1130810587497
    SOAP: call failed
    2005-10-31 19:03:07
    Error
    output
    1130810587497
    SOAP: error occured: java.net.ConnectException: Connection timed out
    2005-10-31 19:03:07
    Error
    output
    1130810587498
    Exception caught by adapter framework: Connection timed out

    Hi Mathew,
    Check if the webservice is availble??? Based on the error below, it looks like the message is timing out at the Adapter Engine level waiting for the connection to make the webservice call...
    Prasad

  • SOAP receiver adapter for Axis

    Hi,
    I used SOAP receiver adapter for Axis  like below:
    Transport Prorocol : HTTP
    Message Protocol : Axis
    Url: http://<IP>:<Port>/xxx/WebService/services/Head/yyy
    Authentication : Basic
    User: <user>
    Password: <password>
    SOAP Version : 1.1
    SOAP Action: : <method>
    Encapsulation Format : MIME
    Payload Extraction : SOAP Body
    When i drive PI message it generates error below.
    What must i do to solve this problem?
    Thanks.
    Error message
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.EJBException: Exception in getMethodReady() for stateless bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: com.sap.engine.services.ejb3.util.pool.PoolException: javax.ejb.EJBException: Exception raised from invocation of public void com.sap.aii.adapter.axis.modules.AFAdapterBean.ejbCreate() throws javax.ejb.CreateException method on bean instance com.sap.aii.adapter.axis.modules.AFAdapterBean@20715646 for bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: javax.ejb.CreateException: java.lang.NoClassDefFoundError: org/apache/axis/types/URI$MalformedURIException

    *Url:*  http://172.28.6.194:8080/AssetManagerWebService/services/Head/SapTest
    When i use Url with *?wsdl* it generates below (it'is very long. I give part of it)
    wsdl
    <?xml version="1.0" encoding="UTF-8" ?>
    - <wsdl:definitions targetNamespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:intf="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:tns1="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Types" xmlns:tns2="http://schemas.hp.com/AssetManager/R51/ACMetaData" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    - <!--
    WSDL created by Apache Axis version: 1.2.1
    Built on Jun 14, 2005 (09:15:57 EDT)
      -->
    - <wsdl:types>
    - <schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:AdministrationTypes="http://schemas.hp.com/AssetManager/Custom/Head/Administration/Types" xmlns:CableTypes="http://schemas.hp.com/AssetManager/Custom/Head/Cable/Types" xmlns:CatalogTypes="http://schemas.hp.com/AssetManager/Custom/Head/Catalog/Types" xmlns:ChargebackTypes="http://schemas.hp.com/AssetManager/Custom/Head/Chargeback/Types"
      <import namespace="http://schemas.hp.com/AssetManager/R51/ACMetaData" />
      <import namespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Types" />
    - <annotation>
      <documentation>Auto-generated schema for AssetCenter web services for Head/SapTest Implementation</documentation>
      </annotation>
      <import namespace="http://schemas.hp.com/AssetManager/Custom/Head/SAM/Types" schemaLocation="../../schema/Head/SAM/SAMTypes.xsd" />
      <import namespace="http://schemas.hp.com/AssetManager/R51/ACMetaData" ......
    <wsdl:operation name="retrieveAllBusinessAPIListByName">
      <wsdlsoap:operation soapAction="retrieveAllBusinessAPIListByName" />
    <wsdl:input name="retrieveAllBusinessAPIListByNameRequest">
      <wsdlsoap:body use="literal" />
      </wsdl:input>
    <wsdl:output name="retrieveAllBusinessAPIListByNameResponse">
      <wsdlsoap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    <wsdl:service name="SapTestService">
    <wsdl:port binding="impl:SapTestSoapBinding" name="SapTest">
      <wsdlsoap:address location="http://172.28.6.194:8080/AssetManagerWebService/services/Head/SapTest" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>

Maybe you are looking for