Soap url

hi
can any one please tell me the url to be used while testing the request messgae using soap client.
Thanks

Hai Hema,
     >>>can any one please tell me the url to be used while testing the request messgae using soap client.
      You wont require any URL while testing the webservice.
You require the following things when you are defining the webservice:
1) Specify URL of webserver
Sample URL : http://<servername>:<port>/XISOAPAdapter/MessageServlet?channel=<Communication_Channel_name>:<Sender_Interface_name>
2) Specify Sender Interface or reuest message
3) Specify the sender
XI generate wsdl file for your request message once you define the webservice as specified above.
Use any webservice client or XMLSpy to test this webservice.
Regards,
Govada Chand.

Similar Messages

  • SOAP URL in SXMB_MONI

    Hi,
    We are sending MATMAS idocs to external system using SOAP adapter at receiver. The message status in SXMB_MONI is successful , but the message is not delivered. When we check the same in web based message control , we could see error message 'Connection refused'. We corrected the URL in SOAP adapter , but still the message persists in message control.
    Is is possible to see this SOAP URL in SXMB_MONI ? or in some other way ?
    I just want to confirm that the message is being sent to the updated and correct URL.
    Regards,
    Tushar

    The message gets delivered successfully using soapUI , but fails when sent via XI. This error is not displayed in SXMB_MONI, but in Audit Log. I tried changing the URL again , but the error persists. I put a random URL , but still the same error. Success in SXMB_MONI , but Non delivered in audit log.
    Here's the Audit log. Kindly advice.
    Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect
    Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect
    Error Exception caught by adapter framework: Connection refused: connect
    Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect.

  • SOAP URL requires authentication even after enclosing user and pw

    Hi,
    Currently i have generated a SOAP url and had provided it to the source system owners. All they say is that when they enter the URL in the Internet Explorer, it asked for the username and password again even after adding it to the URL. Also when they integrated it to their application, it throwed an error "Transport error: 401 Error: Unauthorized"
    The URL i shared is in the below format,
    https://<HostName>:<Port>/XISOAPAdapter/MessageServlet?channel=:<BusinessSystem>:<CommunicationChannel>&nosoap=true&sap-user=<username>&sap-password=<password>
    Please help me if i am missing something in this.

    Hi,
    In fact, what Mark mentioned is true. Let me throw some more light to it. You can only include the username and password in the SOAP call to PI if you post the SOAP message directly to the Integration Engine, without using sender SOAP adapter. This approach was described by Stefan Grube in his blog here:
    Using the SOAP inbound channel of the Integration Engine
    As a result, you would have to use a different URL to post your calls:
    http://hostname:port/sap/xi/engine?type=entry&version=3.0&Sender.Service=<service>&Interface=<namespace>^<service_interface>&sap-user=<>user&sap-password=<password>
    Alternatively (and this is how I would personally do it), you can include the username and password in the HTTP header attributes, as I described here:
    A closer look at SOAP Sender authentication
    Thanks to that, you do use the sender SOAP adapter, and achieve some more security thanks to not providing the user name and password in the URL.
    Hope this helps,
    Greg

  • Question about soap url

    hi all,
    In SOAP sender communication channel, the default interface and namespace are defined there. But now I need to use one CC for two interfaces. I followed this how to guide
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
    I add some parameter "Interface=xxxx" to the url. But it dosen't work. When I send a message with another interface, the XI still uses the default interface.
    What could be wrong? Any idea?
    Thanks!
    Regards,
    Hui

    Hi,
    First of all refer this thread:
    Re: Setting interface name dynamically from client for SOAP Adapter...
    You need to:
    1) in SOAP sender CC set the following flags:
    - Use Encoded Headers
    -  Use Query String
    2) prepare URL according to the following:
    http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>&version=3.0&Interface=http%3A
    %2F%2Fsap.com%2Ftest%5ETest
    Then you will be able to use one SAOP sender communication channel to call two or more interfaces specified in the URL
    Regards,
    Jakub

  • SOAP URL without username and password

    Hello Everyone,
    its a synchronous SOAP - PI -ECC scenario .
    I have created HTTP URL through sender agreement in integration for testing.
    However, customer now wants HTTPS URL without Username and password in  production URL. How do i create this .
    Regards,
    Ravi

    Hello,
    However, customer now wants HTTPS URL without Username and password in production URL. How do i create this .
    You can disable basic authentication for the sender SOAP Adapter by following William's reply in this thread
    http://forums.sdn.sap.com/thread.jspa?threadID=236507
    However, the authentication will be disabled for all SOAP Sender, so you should weigh-in the impacts of granting that request.
    Hope this helps,
    Mark
    Edited by: Mark Dihiansan on Feb 13, 2012 3:51 AM

  • SOAP  URL - no action specified

    I was given a target https:// url and I have to send a cXML document to it. I have used the SOAP adapter without envelope with header. Can I do this? I have no action to specify since I have not been given a wsdl file. The cXML message format was taken from cxml.org site. The main question is can webservices be invoked without action i.e. are they set up to perform a default action ?

    > The main question is can webservices
    > be invoked without action i.e. are they set up to
    > perform a default action ?
    Yes, certain webservices can be invoked without SOAP action. For example the sender SOAP adapter does not require an action.
    So if your WSDL has no definition for a SOAP action, leave it empty in the receiver SOAP adapter.
    Regards
    Stefan

  • Is client Needs to be Mention in Sender SOAP URL

    HI ,
    I working on one scenario in which I am providing the WSDL (SOAP Sender) to sender system.
    but they are not ok with the WSDL URL
    http://iltlvsap19.sap.s.com:8000/sap/xi/engine?type=entry&version=3.0&Sender.Service=WS2RFC&Interface=sap.com%3ADn%3AEmpData%5EEmpData_OB
    they are asking for to mention client also in above URL on which I am making this WSDL(XI Client)
    http://iltlvsap19.sap.s.com:8000/sap/xi/engine?type=entry&version=3.0&Sender.Service=WS2RFC&Interface=sap.com%3ADn%3AEmpData%5EEmpData_OB/Client=200
    plz suggest
    Regards

    >
    gangadhar kh wrote:
    > they are asking for to mention client also in above URL on which I am making this WSDL(XI Client)
    > Regards
    Gangadhar,
    What they might be looking for is XI box credentials (username and password) to send data to PI. When creating the WSDL check the Sender URL and include the username and password if required.
    Regards,
    Pavan

  • BEA380002 - error accesing a soap url

    Hi,
    I am trying to make a outbound connection to one of our client web service(soap based)
    I created a BS and and added endpoint url of the wsdl of this web service. "http://ix.tpapi.uat.radixx.com/*somethingsomething.asmx*" I have tested this url and it works fine.
    However i am getting the following error message while testing.
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Body>
    <soapenv:Fault>
    <faultcode>soapenv:Server</faultcode>
    <faultstring>BEA-380002:x.tpapi.uat.radixx.com</faultstring>
    <detail>
    <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
    <con:errorCode>BEA-380002</con:errorCode>
    <con:reason>ix.tpapi.uat.radixx.com</con:reason>
    <con:location>
    <con:node>RouteTo_BS_GAS_AI</con:node>
    <con:path>request-pipeline</con:path>
    </con:location>
    </con:fault>
    </detail>
    </soapenv:Fault>
    </soapenv:Body>
    </soapenv:Envelope>
    How do I resolve this issue.

    Here is the response metadata i am getting:
    <con:metadata xmlns:con="http://www.bea.com/wli/sb/test/config">
    <tran:headers xsi:type="http:HttpResponseHeaders" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <tran:user-header name="Mime-Version" value="1.0"/>
    <tran:user-header name="X-Cache" value="MISS from localhost"/>
    <tran:user-header name="X-Squid-Error" value="ERR_CACHE_ACCESS_DENIED 0"/>
    <http:Connection>keep-alive</http:Connection>
    <http:Content-Length>1242</http:Content-Length>
    <http:Content-Type>text/html</http:Content-Type>
    <http:Date>Mon, 08 Apr 2013 11:12:39 GMT</http:Date>
    <http:Proxy-Authenticate>NTLM</http:Proxy-Authenticate>
    <http:Server>squid/3.3.0.2-20121210-r12424</http:Server>
    <http:Via>
    1.1 localhost (squid/3.3.0.2-20121210-r12424)
    </http:Via>
    </tran:headers>
    <tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">1</tran:response-code>
    <tran:response-message xmlns:tran="http://www.bea.com/wli/sb/transports">Proxy Authentication Required</tran:response-message>
    <tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">iso-8859-1</tran:encoding>
    <http:http-response-code xmlns:http="http://www.bea.com/wli/sb/transports/http">407</http:http-response-code>
    </con:metadata>

  • Use of SOAP Receiver Adapter in a recursive way with dynamic Target URLs

    Hi all,
    I have a following scenario.
    1. I have to call a webservice with a URL http://myserver.com/default.aspx?action=index
    This will return a list of xml filenames as below
    <?xml version="1.0" encoding="UTF-8"?>
    <filelist>
      <file uuid="test1" />
      <file uuid="test2" />
      <file uuid="test3" />
      <file uuid="test4" />
    </filelist>
    2. Now I have to call the same webservice with a change in action so that the url looks like
    URL - http://myserver.com/default.aspx?action=fetch&uuid=
    for all the filenames in the list
    So in essence, I have to create a dynamic URLs recursively like
    http://myserver.com/default.aspx?action=fetch&uuid=test1
    http://myserver.com/default.aspx?action=fetch&uuid=test2 and so on
    3. And with each call to the URL in step 2, the incoming xml is to be mapped to an IDoc.
    I will be creating a ABAP proxy to initiate the calls.
    I would like some ideas so as to have a less complex approach to the solution.
    Regards,
    Neeraj

    Hi,
    dynamic SOAP URL - adapter specific properties (http receiver adapter)
    Dynamic configuration payload - https://media.sdn.sap.com/javadocs/NW04/SPS15/pi/com/sap/aii/mapping/api/DynamicConfiguration.html
    DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get
    (StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","THeaderSOAPACTION");
    String a = http://something.abcd/applicationName/xmlMessage //set the value of actual action here
    conf.put(key, a);
    return "";

  • SOAP Receiver Adapter - Dynamic URL

    Has anyone tried modifying SOAP URL dynamically using UDF in the mapping?. I searched Forum and couldn't get right answer. Does it work with Adapter Specific settings and variable transport binding? Please donot post links to other posts unless it got an answer or atleast close to being answered. We are on PI7.0. Thanks

    Hi,
    I have similar situation. My target URL lookslike this
    http://devlsales.test.com:8000/soap/services/AdapterService which is a working right now.
    With Variable transport binding ( TServerLocation ),  Can I change http://devlsales.test.com from above URL to
    http://devlprofits.test.com and remaining text same resulting
    http://devlprofits.test.com:8000/soap/services/AdapterService   by using UDFs.
    Thanks
    ST
    Thanks

  • Soap Receiver adapter , Target URL and Soap Action

    HI all,
              WIll anyone tell me regarding Soap action, casue , they have given a URL which i have put in Target URL, but i am not able to understand what is SOap action what need to be put in this
    Thankign you
    Sridhar

    i Sridhar,
    In XI SOAP adapter we need two things:
    SOAP URL: which is endpoint to the webserver.
    SOAP action: describes particular method name we wanted to excute on that web applicaiton hosted on the webserver.
    WSDL file has normally multiple operations(methods) , so we execute particular method by giving particular action name.
    Action is not mandatory parameter i guess, this is in case , when wsdl is exposing only one method(action).
    :Normally you can find SOAP Action element under element <SOAP:operation name = "XXX">
    Hope this clears.
    Cheers,
    Div

  • No Payload in the soap receiver call adapter ?

    Hi Guys,
    configured Proxy-SOAP Asynchronus process and in the sxmb_moni, i am unable to see the payload under call adapter in sxmb_moni, but i am able to see the payload under RWB in MDT. The message is checked successful in monitor.
    I am not understanding why i am unable to see the payload under call adapter in sxmb_moni.  I am not getting the data into my receiver system.
    Do i need to mention the QOS as EO in the soap url in the soap receiver adapter configuration ?
    any help would be really appreciated
    Thanks,
    srini

    Hi,
    You can only see the Payload(both with and without transformation) in MONI. message that is handling by adapter can only seen in Adapter Framework using RWB-Message Monitoring or using Communication Channel Monitoring.
    Regards,
    Farooq.
    <b>
    Rewards points if you find it usefull.</b>

  • OWSM 10.1.3.4 and Non-SOAP XML-based web service

    Hi all,
    According to the OWSM 10.1.3.4 Administrator's Guide, "all Web services registered with an Oracle WSM Gateway are virtualized as both a SOAP and non-SOAP Web service." To access the non-SOAP (XML-only) web service, the documentation states "The non-SOAP virtualized URL can be determined from the virtualized SOAP URL by replacing the services keyword in the URL with the xml keyword."
    For example, if the SOAP virtualized endpoint is:
    http://host:port/gateway/services/SID0003001
    then, the non-SOAP XML service endpoint is:
    http://host:port/gateway/xml/SID0003001
    I have several web services registered with an OWSM gateway, running on SOA Suite 10.1.3.4, and can access those without any problem. However, when I attempt to access the "/gateway/xml" version of these services, I simply get an HTTP 200 response header with a null body.
    Does anyone have any ideas what could be causing this or what the secret is to get the non-SOAP XML service feature of OWSM to work?
    Thanks!
    --Gary                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    Hi all,
    According to the OWSM 10.1.3.4 Administrator's Guide, "all Web services registered with an Oracle WSM Gateway are virtualized as both a SOAP and non-SOAP Web service." To access the non-SOAP (XML-only) web service, the documentation states "The non-SOAP virtualized URL can be determined from the virtualized SOAP URL by replacing the services keyword in the URL with the xml keyword."
    For example, if the SOAP virtualized endpoint is:
    http://host:port/gateway/services/SID0003001
    then, the non-SOAP XML service endpoint is:
    http://host:port/gateway/xml/SID0003001
    I have several web services registered with an OWSM gateway, running on SOA Suite 10.1.3.4, and can access those without any problem. However, when I attempt to access the "/gateway/xml" version of these services, I simply get an HTTP 200 response header with a null body.
    Does anyone have any ideas what could be causing this or what the secret is to get the non-SOAP XML service feature of OWSM to work?
    Thanks!
    --Gary                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Use of variable header XHeaderName1 in SOAP sender adapter

    Hi all,
    I have a doubt regarding the use of adapter-specific attributes in SOAP sender adapter. In specific:
    the SOAP client should be able to pass a variable with the SOAP request (XHeaderName1 header variable) and this should be available in mapping (Dynamic configuration)
    I've already checked the [help page|http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm] but it seems I'm doing something wrong.
    I tried with those settings in SOAP adapter configuration:
    Keep headers checked
    XHeaderName1 = Test
    I try to call the SOAP adapters in the following 2 ways, but none works (the value is not available in message mapping with Dynamic configuration)
    1. Pass "Test" value xxxx in SOAP Header as a tag
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <SOAP-ENV:Header>
              *<Test>xxxx</Test>*
         </SOAP-ENV:Header>
         <SOAP-ENV:Body>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    2. Pass "Test" value xxxx in SOAP URL
    http://host:50000/XISOAPAdapter/MessageServlet?channel=p:s:c&version=3.0&Sender.Service=...&Interface=...&Test=xxxx
    Could anyone give me a hint about how to pass those values in the SOAP call and eventually the correct config. of SOAP sender ?
    Thanks a lot,
    Manuel

    Hi Manuel,
    Could you give a bit more detail on how you handled the SOAP message yourself.
    I have a similar issue. I am consuming a non SAP Web Service which requires a non-standard token element to be passed back. I have created a an RFC sender to SOAP reciever scenario which works fine for the inital logon and returns the token it expects in the follow up messages.
    At present I'm at a loss so your help would be much appreciated. We have got round the immediate issue by creating and sending the SOAP message directly from SAP WAS.
    Could we use the XI Adapter and ABAP proxy in a similar way?
    Thanks,
    Tim J.

  • SOAP Web Service Authentication configuration

    Hello,
    I've got a little problem with Web Service authentication configuration.
    I'm working on the SAP NetWeaver CE EHP1 7.11. I also have a XMII application deployed on the server and there are some SOAP Web Services(over XMII Transactions) that require basic authentication.
    I use all Web Services in the EJB layer. So, I've generated proxy using SAP NetWeaver as a Web Service Runtime for generation. And Iuse an injection mechanism to get a service implementation:
    @WebServiceRef(name="GetBatchListService")
    private XacuteWS batchListWS;
    In this case I could use Single Service Administration application in the NetWeaver Administrator@SOA Management@Application and Scenario Communication to configure basic authentication for EVERY Web Service. And this configuration disappears after every redeploy.
    The question is how and where could I configure authentication for all web services?
    I've read a lot of documentation, but, unfortunately, I haven't found needed one. I could see 2 direction of searching now, it might help:
    1) Destination: Configure HTTP Destination or Web Service Template Destination and use it in all Web Services proxies somehow.
    2) Find Configuration way: Create a configuration group or anything else to configure all services from one screen.
    Best Regards,
    Dmitry

    Dimtris,
    If your WSDL url is pointing to the URL of the Adapter Engine as shownin the Hot to Use the SOAP adapter there is no option. You cannot add it to the SOAP Url.
    But, if you change the SOAP Url to the Url shown in this blog by Stefan Grube then you can add the user id and pasword to the url by adding sap- user=userid and sap-password = password.
    The optin shown ion the blog by Grube can be used as long as you do not have to use SOAP attachments and in this  case you would not need both sender SOAP adapter and a sender agreement.
    /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
    Regards
    Bhavesh
    Regards
    Bhavesh

Maybe you are looking for