Soap receiver wsdl having soap envelop

Hello Experts ,
We are having Proxy to Soap synchronous scenario .In given wsdl , we are having soap header and soap body in soap envelop .In soap header we are having username and password as parameters while in soap body we are having normal fields . Please let me know how we can pass the data to the soap header because while creating service interface for soap side , we can not add header as well as body in single request tab.
Kindly let me know how to proceed.
Regards ,
Nikhil Save

Hi Muniyappan ,
I have followed as per praveen's blog . But now we are getting below error in message monitoring .
So i added MessageTransformationBean in receiver comm channel as below .
But now we are getting Object not found in lookup of MessageTranspormationBean error as below.
Kindly suggest what can be done .
Regards ,
Nikhil Save

Similar Messages

Problem in testing SOAP receiver adapter using SOAP UI

Dear Experts,
I'm trying to test my SOAP receiver adapter as mentioned in the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/21844. [original link is broken] [original link is broken] [original link is broken] But, my request from ECC proxy keeps failing in XI communcation channel monitor. I've configured my receiver adapter http://ip:8080/mockSoapHTTPBinding and kept the authentication as NONE. Can any of you suggest?
ip - is my system ip shown in ipconfig.
mockSoapHTTPBinding - is the path.
Thanks.

What is the error of the messages? Are the messages leaving the SOAP adapter?
Please try both:
1. Go to Runtime Workbench -> Component Monitoring -> Adapter Engine -> Test message. Then, execute the message directly without the intermediate of the Proxy sender. This will allow you to check only the receiver SOAP.
2. Please use the TCPGateway tool attached from the note below. It will be a "man-in-the-middle" between the target WS and the Receiver SOAP channel, tracking the whole HTTP/SOAP message. Check if the message is well-formed.
[Note 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=856597]
under question "Q: How can I trace the whole message?"

SOAP Receiver: Problem with SOAP Multipart Request (wsdl:part)

Dear PI experts,
our partner provided a WSDL with the following definition (I modified it to keep it simple and showing the principles)
   <wsdl:message name="nameOfMessage">
      <wsdl:part element="part1" name="header" />
      <wsdl:part element="part2" name="parameters" />
      <wsdl:part element="part3" name="attachment" />
   </wsdl:message>
After importing this WSDL in ESR, I found the following definition on tab 'WSDL':
         <xsd:complexType name="nameOfMessage">
            <xsd:sequence>
               <xsd:element name="header" type="authentication" />
               <xsd:element name="parameters" type="businessDatal" />
               <xsd:element name="attachment" type="Binary" />
            </xsd:sequence>
         </xsd:complexType>
When creating the request message in PI it looks as follows:
<nameOfMessage>
<header/>
<parameters/>
<attachment/>
</nameOfMessage>
However our WebService provider expects the following:
<soap:env>
<authentication/>
<parameters/>
<attachment/>
</soap:env>
When using SoapUI and importing the WSDL the request message looks as expected by the web service provider and the part names are resolved.
I could try to convert the request using XSLT but this does not seem to be a best practice approach.
Do you have any advice on how to handle this issue?
Thank you very much.

Hi Florian,
I modified some WS to be handled by another systems, and sometimes, when the SOAP adapter is involved, you send a Request to PI (that has NOT the same structure, than the declared in the MM) but it takes the req. anyway.
Did you try sending a request?
Juan.

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

SOAP receiver adapter - payload inside the soap envelop

Hi,
We have to send a SOAP message to 3rd party from PI 7.1. Using SOAP receiver adapter - we are trying to achieve this. 3rd party software is unable to accept payload as an attachment of the main envelop - they want it enside the main envelop.
I tried with "Keep attachment" option - but PI still keping the payload as an attachment. I think this option is for handling "extra" attachment.
Is there any way we can keep the payload inside the envelop?
In run-time WB, at the moment envelop looks like
<SOAP:Envelope xmlns:SOAP="http://schemas....
<SOAP:Body>
<sap:Payload xlink:type="simple" xlink:href="cid:payload-d6518670ca1311debbd9ca347000800b...">
</SOAP:Body>
</SOAP:Envelope>
And the payload d6518670ca1311debbd9ca347000800b... ( again viewed from RWB) - contains the data.
<?xml version="1.0" encoding="UTF-8" ?>
<ns2:Order> ....
</ns2:Order>
Can we insert this payload directly inside the SOAP:Envelope body instead of a link there?
Regards,
Sudhin

Hi!
It seems to me that this 3rd party is expecting only XML not SOAP.
If this is the case, you should use the HTTP Receiver adapter instead of SOAP.
Some systems 'say' they can speak SOAP but they can only speak XML. Not to blame, it's a mistake many make these days.
The only way you use SOAP Receiver adapter with this 3rd party, is that if someone from the 3rd party hands you a WSDL file.
Ricardo Sancio Lóra
Brazil

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

SOAP RECEIVER and WSDL-what specifies how my SOAP REQUEST should look like?

Hi
I am sending a request to a webservice (SOAP RECEIVER) but the webservice in question does not have a wsdl. I have created my own wsdl based on another example but when mapping to the REQUEST part of this and routing it through my SOAP RECEIVER channel it appears that it has NO SOAP-ENV only the pure XML in the request sent to the webservice.
I have UNTICKED the "No SOAP envelope.." so all is pretty basic.
What specifies how the REQUEST sent to the webservice through the SOAP RECEIVER comm channel should look like?
I thought that the SOAP RECEIVER ADAPTER did this automatically, but in my scenariao, it looks as if it something else as well? Is it the XSD or WSDL that dictates how the SOAP REQUEST should look like?
Cheers

> I thought that the SOAP RECEIVER ADAPTER did this automatically, but in my scenariao, it looks as if it something else as well? Is it the XSD or WSDL that dictates how the SOAP REQUEST should look like?
No. The SOAP adapter adds the SOAP enveloped, no matter how the WSDL looks like.
I have no idea why this does not work for you. Check whether the channel is active and the cache is refreshed.
Regards
Stefan

"Do Not Use Envelope" feature: WS Receiver vs Soap Receiver

I have a scenario that I need to call web service on receive side.
When I use Soap adapter, need to use mapping program to compose SOAP message mannully:
Envelope
   + Header
     ++MessageID
     ++Action
   +Body
     ++FistName
     ++FistName
In SOAP receiver adapter, I do not use PI envlope, so I have to choose "Do Not Use Soap Envelope" option.
When I use WS receiver adapter to call the same web service, I could not find the way the Soap adapter does.
Anyone tried to use same feature in WS adapter ?
Thanks
Liang
Edited by: Liang Ji on Oct 27, 2011 4:33 PM

>Anyone tried to use same feature in WS adapter ?
IMO, WS adapter does not provide "Do Not USe Envelope option" in 7.1 as well in above versions.   You might want to see other experts opinion.

How to use given WSDL into SOAP Receiver Adapter.

Hi all,
http://www.webservicex.net/ValidateEmail.asmx?WSDL
I want to use this above given WSDL into SOAP Receiver Adapter.
Can I directly use this link into SOAP Receiver adapter.
Or first I need to register or deploy it somewhere in PI ( Services).
If Yesu2026 Kindly show/Provide me the way..
Regards
Prabhu.

Thanks to all,
i will now try to make the complete end to end scenario.
thanks for now.
I hope above given information would be enough to make end to end webservice scenario.
for now, i i am closing this thread.
if i will find any more further problems in this ... i will come up with new thread.
Thanks all,
Prabhu
I have assigned 2 Points to AMIT , abishek
Edited by: Prabhathcl on Jun 9, 2010 8:39 AM
Edited by: Prabhathcl on Jun 9, 2010 8:39 AM
Edited by: Prabhathcl on Jun 9, 2010 8:40 AM

SOAP RECEIVER - no soap envelope sent

Hi
I am new to soap.
When sending the SOAP request via the SOAP RECEIVER commchannel - the partner only reveives a plain xml with no SOAP-ENV.
My comm channel settings are as follow:
URL is set to the url of the receiver
No other settings is marked. The receiver has no SOAP action so this is left out blank as well.
What must the correct settings be?
Hope for some help
Cheers

Hi,
By any chance, have you checked the checkbox "Do not use SOAP Envelope" in Convesion Paramenters in the comm channel.
regards,
Neeraj

Soap Receiver adapter - 401 error

I am getting following error with soap receiver,
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
I am able to consume the webservice with SOAP UI without any difficulty. I have tried with both the endpoint URL and WSDL url without success. I have tried with/without 'Do not use SOAP envelope'. I am not sure what is wrong. When the message is sent via PI, he is not able to look at the payload (while performing the trace) , while he is able to view the actual soap message with SOAP UI.
When i type the ENDPOINT url in my http address, i get a 'page not found' error.
Any ideas as to what i could be missing?

One more interesting behaviour when I was sending from SOAP UI, The request was posted twice, meaning there were two POST actions in my TCPGATEWAY listening port, while there was only one request via PI.
Wnen my partner put a trace, the SOAP envelop was missing in their TRACE for PI file while the SOAP envelop was available for SOAP ui message (in the second request). Could it have something to do with a fact that we are doing HTTP 1.1with soap uI While PI is HTTP 1.0 (HTTP 1.1 being a persistent connection resulting in second request)
Trace on the partner side,
PI Message
POST /Services/Calculator/Version1/Calculator.asmx HTTP/1.0
accept: * / *
host: www.html2xml.nl
user-agent: SAP-Messaging-com.sap.aii.af.sdk.xi/1.0505
callingtype: SJM
content-id: <soap-4EB90CC8537E011DE1008000CDEB6913>
content-type: text/xml; charset=utf-8
content-length: 888
SOAPAction: "http://tempuri.org/Add"
HTTP/1.0 401
WWW-Authenticate: Basic realm="CASM"
Content-Type: text/html;charset=utf-8
Content-Length: 40
Date: Thu, 10 Nov 2011 11:50:13 GMT
Connection: close
SOAP UI log
POST /Services/Calculator/Version1/Calculator.asmx HTTP/1.1
accept-encoding: gzip,deflate
content-type: text/xml;charset=UTF-8
soapaction: "Create"
user-agent: Jakarta Commons-HttpClient/3.1
host: www.html2xml.nl
content-length: 2496
HTTP/1.1 401
WWW-Authenticate: Basic realm="CASM"
Content-Type: text/html;charset=utf-8
Content-Length: 40
Date: Thu, 10 Nov 2011 12:04:40 GMT
POST /Services/Calculator/Version1/Calculator.asmx HTTP/1.1
accept-encoding: gzip,deflate
content-type: text/xml;charset=UTF-8
soapaction: "Create"
user-agent: Jakarta Commons-HttpClient/3.1
content-length: 2496
authorization: Basic U1lTX1dFQl9TQVBQSTo=
host: www.html2xml.nl
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
</soapenv:Envelope>
HTTP/1.1 200
Set-Cookie: JSESSIONID=A48C8808315935EFD7AFBA8B4B96FC62; Path=/xx
Keep-Alive: timeout=1200000, max=1000
Connection: Keep-Alive
Content-Encoding: gzip
Content-Type: text/xml;charset=utf-8
Content-Length: 2882

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" ?>

<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 problem

Hi everyone.
I'm facing a new problem with SOAP Receiver adapter.
We have an WSDL that works perfectly using SOAP Clients such as SOAPUI or StylusStudio. End-point is HTTPS://XXXXX:XXX/XXXXX
WSDL is like this :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<tes:registraEntrada0Request xmlns:tes="http://testing.com" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<asu_id>SIO7</asu_id>
<asu_descripcion>desc</asu_descripcion>
<uo_id>1272</uo_id>
<nombre>nombre</nombre>
<ape1>ape1</ape1>
<ape2>ape2</ape2>
<usu_id>virtualdesa</usu_id>
<usu_pass>virtualdesa</usu_pass>
</tes:registraEntrada0Request>
Problem is when i try to use this webservice from XI using a SOAP Receiver communication channel. I get a strange error :
soap fault: No Deserializer found to deserialize a ':asu_id' using encoding style 'null'. [java.lang.IllegalArgumentException]
I don't know if the problem is because HTTPS. All the process has been defined correctly in XI and my doubt is about the configuration of the RECEIVER SOAP or the WSDL structure.
Hope you can help me
Regards,
Inigo.

hi,
check out response by Ricardo,
Re: Error in Receiver Soap Adapter for Google API
maybe you need to fill some attributes in an adapter module like mentioned there
Regards,
michal

Soap receiver target url

Hi guys,
I'm having some doubts on a soap receiver adapter.
Imagine, you use the ID to define a webservice.
Two simple synchronous interfaces, meaning, you send a string and receive another string via SOAP.
In the ID you define the comm channels, the soap sender and receiver.
My doubt is in the receiver side, you have tou specify the target URL. The problem is, how can I know the target URL, since the service will only be defined later. Meaning, I want XI to answer to a sender client which will use the WSDL generated after by the ID tool.
Where should XI answer to?
I've seen some blogs concerning some similar issues, but none concerning the problem I'm facing.
Can you guys help me or give me any hints on how to work around the problem...

Hi,
If you have a SOAP client sending a request message to XI and expecting a Response message, you need to configure SOAP sender adapter only. You do not need SOAP receiver adapter in this scenario. Sender adapter doesnt require any URL, moreover when you define a webservice in XI, you have to construct a URL where this web service can be reached.
You need the SOAP receiver adapter (where u need to mention the URL of teh service) if the receiver system exposes a webservice to which you are trying to connect from XI.
What are ur sender and receiver systems?
praveen

SOAP Receiver to use operations and methods

Hi.
I have got a WSDL with 3 methods and I have to call one of them.
However, the SOAP Receiver adapter only has a Action section which can be maintained.
How can this be attained?
The WSDL I am using is as follows:
<?xml version="1.0" encoding="ISO-8859-1"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:tns="urn:uniface:applic:services:CSYV1000" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="urn:uniface:applic:services:CSYV1000" name="CSYV1000">
     <wsdl:types />
     <wsdl:message name="EXTERNALRequest">
          <wsdl:part name="REQUEST" type="s:string" />
          <wsdl:part name="REQUESTDATA" type="s:string" />
     </wsdl:message>
     <wsdl:message name="LOGOFFRequest">
          <wsdl:part name="REQUEST" type="s:string" />
     </wsdl:message>
     <wsdl:message name="LOGONRequest">
          <wsdl:part name="REQUEST" type="s:string" />
     </wsdl:message>
     <wsdl:message name="EXTERNALResponse">
          <wsdl:part name="return" type="s:int" />
          <wsdl:part name="RESPONSE" type="s:string" />
          <wsdl:part name="RESPONSEDATA" type="s:string" />
          <wsdl:part name="RESPONSEERROR" type="s:string" />
     </wsdl:message>
     <wsdl:message name="LOGOFFResponse">
          <wsdl:part name="return" type="s:int" />
          <wsdl:part name="RESPONSE" type="s:string" />
          <wsdl:part name="RESPONSEERROR" type="s:string" />
     </wsdl:message>
     <wsdl:message name="LOGONResponse">
          <wsdl:part name="return" type="s:int" />
          <wsdl:part name="RESPONSE" type="s:string" />
          <wsdl:part name="RESPONSEERROR" type="s:string" />
     </wsdl:message>
     <wsdl:portType name="CSYV1000PortType">
          <wsdl:operation name="EXTERNAL" parameterOrder="REQUEST REQUESTDATA RESPONSE RESPONSEDATA RESPONSEERROR">
               <wsdl:input message="tns:EXTERNALRequest" />
               <wsdl:output message="tns:EXTERNALResponse" />
          </wsdl:operation>
          <wsdl:operation name="LOGOFF" parameterOrder="REQUEST RESPONSE RESPONSEERROR">
               <wsdl:input message="tns:LOGOFFRequest" />
               <wsdl:output message="tns:LOGOFFResponse" />
          </wsdl:operation>
          <wsdl:operation name="LOGON" parameterOrder="REQUEST RESPONSE RESPONSEERROR">
               <wsdl:input message="tns:LOGONRequest" />
               <wsdl:output message="tns:LOGONResponse" />
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="CSYV1000Binding" type="tns:CSYV1000PortType">
          <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc" />
          <wsdl:operation name="EXTERNAL">
               <soap:operation soapAction="" />
               <wsdl:input>
                    <soap:body use="encoded" namespace="urn:uniface:applic:services:CSYV1000" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
               </wsdl:input>
               <wsdl:output>
                    <soap:body use="encoded" namespace="urn:uniface:applic:services:CSYV1000" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="LOGOFF">
               <soap:operation soapAction="" />
               <wsdl:input>
                    <soap:body use="encoded" namespace="urn:uniface:applic:services:CSYV1000" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
               </wsdl:input>
               <wsdl:output>
                    <soap:body use="encoded" namespace="urn:uniface:applic:services:CSYV1000" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="LOGON">
               <soap:operation soapAction="" />
               <wsdl:input>
                    <soap:body use="encoded" namespace="urn:uniface:applic:services:CSYV1000" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
               </wsdl:input>
               <wsdl:output>
                    <soap:body use="encoded" namespace="urn:uniface:applic:services:CSYV1000" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="CSYV1000Service">
          <wsdl:port name="CSYV1000" binding="tns:CSYV1000Binding">
               <soap:address location="http://localhost/pathway/environment.pathway" />
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>
Your help is appreciated.
Regards,
Reenal

Hi, Amit.
The problem arises when I send a logon messages from XI, it fails.
The request which works is:
<?xml version="1.0" encoding="utf-16"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="urn:uniface:applic:services:CSYV1000" xmlns:types="urn:uniface:applic:services:CSYV1000/encodedTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <tns:LOGON>
      <ns0:REQUEST xmlns:ns0="urn:aucklandcity-govt-nz:filenet:property_search"><service>CSYV1000</service><trace/><groupId/><product>SAP XI</product><processId/><threadId/><nodeId/><ipAddress/><sourceUserId/><sourceOSUserId/><uiForm>CMNQ1030</uiForm><groupIdPrevious/><userId>albadryh</userId><password>husain</password><osUserId></osUserId></ns0:REQUEST>
    </tns:LOGON>
</soap:Body>
</soap:Envelope>
The problem is that XI is not adding the <tns:LOGON> tags.
Regards,
Reenal

Soap receiver wsdl having soap envelop

Similar Messages

Maybe you are looking for