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

Similar Messages

SOAP receiver adapter - SOAP request over HTTPS to ther port than 443?

Hi guys!
Is it possible to send SOAP request from XI to target web service over HTTPS to other target port than 443? Our 3rd party web service is running other port..
Thanx a lot, Olian

Hi Olian,
Check out this,
http://www.grc.com/port_443.htm
http://en.wikipedia.org/wiki/HTTPS
The port 443 is just the default port. One can theoretically run protocols over any port. Port assignments are just suggestions to the world as to what to expect on certain ports
Regards,
Prateek

SOAP Receiver error - HTTP 500 Internal Server Error

Hi,
We have a FILE to SOAP Asynchronous scenario to send data from our PI to customer PI.
We are sending PGP encrypted file as the payload. So, foll settings have been maintained:
Do not use SOAP envelope in Sender and Receiver SOAP
nosoap=true in the URL.
Message transform bean in the SOAP channels.
File is successfully sent and received through SOAP protocol.
But, both the SOAP Receiver and Sender channels are in error:
SOAP Receiver error:
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error.
As, this is a asynch scenario, we are not expecting the response.
SOAP sender at customer PI is in error. Error text is not mentioned. It just displays: error occured.
At both the ends, we do not have Repository objects as there is no mapping.
Kindly help...
Thanks,
Pratibha.

Hi All,
For the same scenario, we need to Sign the data using the WebServices Security.
(We are sending PGP encrypted data as SOAP payload using MTB, i have ticked "Do not use SOAP envelope")
I have selected WebServicesSecurity as the security profile in the SOAP Receiver and selected "Sign" in the Receiver agreement, have provided our private cert.
Tried sending a message. Communication channel audit Log shows the message:
Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Success SOAP: request message entering the adapter with user J2EE_GUEST
Success SOAP: Web Services Security processing...
Success SOAP: Web Services Security processing skiped. Empty body...
Success SOAP: completed the processing
Please suggest how I can apply the WSS..
Thanks,
Pratibha.

Message mapping: SOAP Receiver to IDOC Sender

hi,
i have an idoc sent to SOAP receiver. SOAP Response will have only the "Status code" and the "Reason of failure".
IDOC Sender will have the PO Number and the Vendor Name to which we are sending.
The SOAP Response will not have the PO Number and the Vendor Name.
How can i have the Reason of failure, PO Number and Vendor in one message type?
Thanks in advance,
Tirumal

Praveen -
Thanks for the response and appreciate your observation.
Very tight deadlines with the client and have to finish lot of tasks in short time so putting hands in everything.
There are lot of vendors who run their proprietary web services. So cannot change their stuff.
How would i map the SOAP request to the SOAP Response since some information is in one message type and other half of information available in other message type.
I created a SOAP Response Type with the "Reason Code" information.
I created another message type with all the information that i want.
How would i map the SOAP Request to the SOAP Response msg type and the other message type.
Let me know.
Thanks in advance,
Tirumal

SOAP Receiver Channel error

Dear PI and SOAP experts:
I have been having trouble getting a SOAP Receiver channel working for a webservice. I get the following error in the SOAP receiver channel:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: content-type of the request should be text/xml
I also forced the content-type as text/xml;charset=utf-8 from PI by using the MessageTransformBean as a module in the SOAP Receiver channel, but still getting the same response.
When I called the same w/s using XMLSpy and SOAPUI, it works fine and I get a positive response. So there is no problem with the webservice.
I also tried calling a different webservice from PI and that works fine too. So there is no problem with outbound communication with PI and the SOAP receiver channel either.
But whenever I send the request from PI to the first webservice it gives me the above error.
Thank you.
Param.

Hi Param,
Also, please do have a look at the following link which could be of help to you.
https://wiki.sdn.sap.com/wiki/display/XI/SOAPMessagesin+XI
Best Regards

Critical Issue:-- Convert SOAP Attachment into SOAP Body

hi,
   My requirment is
FTP----> SOAP synchronous.
In this one at SOAP receiver side SOAP request is an attachment file and response also I m getting as an attachment.
My problem is that I need to convert this SOAP response (attachment) in SOAP body so that I can map it with FTP datatype.
I used PayLoadSwapBean module but i m unable to convert this attachment into SOAP Body.
I just followed this blog
The specified item was not found.
May be i m not using this module in a proper mannner.
Can anybody explan it step by step.
Is there anyother solution for my problem..
<It is against the rules of Engagement to post a question with the catch of awarding points. Please refrain from the same.>
Thanks
Jaideep Jain
Edited by: Bhavesh Kantilal on Dec 3, 2008 10:26 AM

hi stefan,
I m getting this error after using PayloadSwapBean.
com.sap.aii.af.ra.ms.api.DeliveryException: Object not found in lookup of payloadSwapBean
I m mentioning here the value of parameter name and value for this module:--
parameter name                                    parameter value
swap.keyName                                        payload-name
swap.keyValue                                        MainAttachment
Can u suggest where i went wrong.....
Thanks
Jaideep
Edited by: Jaideep Baid on Dec 5, 2008 9:27 AM

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

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

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

Receive complete SOAP Envelope as message

Dear all
I have a web service that I have to consume which has a signature value in the SOAP header. In order that I can validate the signature with the message I would like to receive the complete SOAP envelope as (XML) message (<envelope>...<soap-env:header>...</soap-env:header>...<soap-env:body></soap-env:body></envelope>).
I couldn't find a solution for this.
Currently I use the WCF-Custom adapter to receive the multi part message (xml schemas created with svcutil) and receive the body as XML file. I also know how to access the SOAP header in the message but I would like to know if its possible to receive the
complete envelope as message.
Best regards
Jerome

Orchestration subscription includes value for BTS.MessageType context property, this mean you can't start orchestration with the soap envelope message type because the XmlDisassembler Component will discard the soap:Envelope content and the messaging engine
will only get the soap:Body content – so at the end of the process, BTS.MessageType context property will be set to the actual message type of content under soap:Body section and the orchestration will never start with the type soap:Envelope.
In case you need to process the entire soap:Envelope inside orchestration:
Use PassThruReceive pipeline.
Define message of type BTS.soap_envelope_1__1 message inside the orchestration (Message Type > schemas > from referenced assembly > Microsoft.BizTalk.GlobalPropertySchemas).
Use Xml Document as the incoming message.
Assign the incoming Xml Document message to the BTS.soap_envelope_1__1 message.
Reference :
http://pinhask.blogspot.in/2008/06/processing-soap-envelope-within-biztalk.html
Thanks
Abhishek

Problem with soap receiver adapter

Hi All
I have Idoc sender and soap receiver in my scenario.
I am calling web service deployed on WAS.
The web service is getting called but the acknowledgement message in xi contains following system error acknowledgement because of which xi changes the status of message to WAIT and starts retrying.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.MessagingException: java.net.SocketTimeoutException: Read timed out: com.sap.aii.af.ra.ms.api.RecoverableException: java.net.SocketTimeoutException: Read timed out</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please anybody can help to resolve this problem. This scenario has worked without any error previously.
Thanks in advance
Beena

Hi Bhavesh,
It is an Async call where method does not return anything.
I added entries in IDX_NOALE but still it is setting the message status to WAIT and does retry.
Following is the Audit Log in Runtime workbench :
Audit Log for Message: 22b3052d-c519-034e-85db-e65d541d6414
Time Stamp Status Description
2006-12-13 10:25:23 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
2006-12-13 10:25:23 Error Exception caught by adapter framework: Read timed out
2006-12-13 10:25:24 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
2006-12-13 10:25:24 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:30:24 GMT+05:30 2006.
2006-12-13 10:25:24 Success The message status set to WAIT.
2006-12-13 10:30:25 Success Retrying to deliver message to the application. Retry: 1
2006-12-13 10:30:25 Success The message was successfully retrieved from the receive queue.
2006-12-13 10:30:25 Success The message status set to DLNG.
2006-12-13 10:30:25 Success Delivering to channel: INSPWCCT_PVtoSAP_Ack
2006-12-13 10:30:25 Success SOAP: request message entering the adapter
2006-12-13 10:35:28 Success SOAP: call failed
2006-12-13 10:35:28 Success SOAP: sending a delivery error ack ...
2006-12-13 10:35:28 Success SOAP: sent a delivery error ack
2006-12-13 10:35:28 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
2006-12-13 10:35:28 Error Exception caught by adapter framework: Read timed out
2006-12-13 10:35:28 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
2006-12-13 10:35:28 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:40:28 GMT+05:30 2006.
2006-12-13 10:35:28 Success The message status set to WAIT.
I have tried this scenario earlier. I am sending the same Idoc from R3 which was processed successfully earlier.
Thanks
Beena.

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 payload with certficate signature

I have a requirement.. where XI calls external webservice using SOAP.
I have configured SOAP receiver adapter, but the webservice wants the certificate authentication.. From XI we sent the certficate to external webservice and then in the comm channel I did activate the 'certficate' check box. It did not work.
For test purpose now they have deactivated the certficate authentication in their end.. it works if they deactivate. It means there is no issue with request structure.. purely the issue is when I use the certficate.
External webservice sent me the copy of the soap request which works for them.. <b>that has security signature inside the payload.</b> ( I have atteched below).
If anybody has done it have an idea how to do it please let me know.
- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <soapenv:Header>
- <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="CertId-62149565">MIIGOzCCBaSgAwIBAgIQIKVRaj76KNaG5Dl6P5X7wzANBgkqhkiG9w0BAQUFADCBnjEPMA0GA1UEChMGaHAuY29tMRowGAYDVQQLExFJVCBJbmZyYXN0cnVjdHVyZTELMAkGA1UEBhMCVVMxIDAeBgNVBAoTF0hld2xldHQtUGFja2FyZCBDb21wYW55MUAwPgYDVQQDEzdIZXdsZXR0LVBhY2thcmQgUHJpbWFyeSBDbGFzcyAyIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MDMyMzAwMDAwMFoXDTA4MDMyMjIzNTk1OVowUDEgMB4GA1UEChQXSGV3bGV0dC1QYWNrYXJkIENvbXBhbnkxEDAOBgNVBAsUB1NlcnZlcnMxGjAYBgNVBAMTEWl0Zy5lcHJpbWUuaHAuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDVGa1x5j/RJHHkqYzEb9NIQGChffTb1D0LiYAP5arbxz0trCp8ZeG4FCH71jc6x9Ks3gC4YdWgQbOCz64wnpM8NvEVCZBHuxvdnPZpziPWQqDr0yvwSoCXg8mkeJrHql0MSm7TNiyhzCAzlmB9JgmoHrRtArJdXMRpHjdZQK3QIDAQABo4IDxTCCA8EwDAYDVR0TAQH/BAIwADAOBgNVHQ8BAf8EBAMCBaAwHwYDVR0jBBgwFoAUSlYfvIpRj/SDE8naXHlUyAK6q58wHQYDVR0OBBYEFE99o7D6AITUcqWVmeYzu/2k66VEMIIBKAYDVR0fBIIBHzCCARswggEXoIIBE6CCAQGUWh0dHA6Ly9vbnNpdGVjcmwudmVyaXNpZ24uY29tL0hld2xldHRQYWNrYXJkQ29tcGFueUlUSW5mcmFzdHJ1Y3R1cmUvTGF0ZXN0Q1JMLmNybIaBuWxkYXA6Ly9sZGFwLmhwLmNvbS9DTj1IZXdsZXR0LVBhY2thcmQlMjBQcmltYXJ5JTIwQ2xhc3MlMjAyJTIwQ2VydGlmaWNhdGlvbiUyMEF1dGhvcml0eSxPPUhld2xldHQtUGFja2FyZCUyMENvbXBhbnksQz1VUyxPVT1JVCUyMEluZnJhc3RydWN0dXJlLE89aHAuY29tP2NlcnRpZmljYXRlcmV2b2NhdGlvbmxpc3Q7YmluYXJ5MCoGA1UdJQEB/wQgMB4GCCsGAQUFBwMBBggrBgEFBQcDAgYIKwYBBQUHAwQwggEWBgNVHSAEggENMIAwgAYKKwYBBAELBAMCATCAMCkGCCsGAQUFBwIBFh1odHRwOi8vZGlnaXRhbGJhZGdlLmhwLmNvbS9jcDCABggrBgEFBQcCAjCAMB4WF0hld2xldHQtUGFja2FyZCBDb21wYW55MAMCAQIagZVBdXRob3JpdHkgdG8gYmluZCBIZXdsZXR0LVBhY2thcmQgQ29tcGFueSBkb2VzIG5vdCBjb3JyZXNwb25kIHdpdGggdXNlIG9yIHBvc3Nlc3Npb24gb2YgdGhpcyBjZXJ0aWZpY2F0ZS4gSXNzdWVkIHRvIGZhY2lsaXRhdGUgY29tbXVuaWNhdGlvbiB3aXRoIEhQLgAAAAAAAAAAAAAwge4GCCsGAQUFBwEBBIHhMIHeMCsGCCsGAQUFBzABhh9odHRwOi8vb25zaXRlLW9jc3AudmVyaXNpZ24uY29tMIGuBggrBgEFBQcwAqSBoTCBnjEPMA0GA1UEChMGaHAuY29tMRowGAYDVQQLExFJVCBJbmZyYXN0cnVjdHVyZTELMAkGA1UEBhMCVVMxIDAeBgNVBAoTF0hld2xldHQtUGFja2FyZCBDb21wYW55MUAwPgYDVQQDEzdIZXdsZXR0LVBhY2thcmQgUHJpbWFyeSBDbGFzcyAyIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MA0GCSqGSIb3DQEBBQUAA4GBAMB3vOFZYe26MaZ8mpnoZwhWbLBFV/lxtefZT1uT7mKZiaHjVqwu3tN1eAYAUXtJQHVJTnCnbDm9zFunlvuEzGMt9PwXS61MK6GwPmtjEsevRnGIA7arvpjSJ1/EQlD620I7icM9BNXbElYFfsnZjlWKFTZz3VX1OT2qmJtVWpD</wsse:BinarySecurityToken>
- <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
- <ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />
- <ds:Reference URI="#id-24819136">
- <ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<ds:DigestValue>6Mzpm7P8k3f8UuxbBMP4ZTC83Yc=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>HcqMChOzlHFXTRRAf7kyTSQ5Jd53Yiu7oFLjkh5P3vayo2G4sjFv/qFKHX0E6a5xkBMTIRrW+30t7IdB4X0x35FPO1dTulz37KM1/jpLSGVxnjnWWeFZvseVjJsk5NTPiSE6GAjO7rFW/Vled2djATTmZsIgJCIfhLYVp112Uis=</ds:SignatureValue>
- <ds:KeyInfo Id="KeyId-21369792">
- <wsse:SecurityTokenReference xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="STRId-29015968">
<wsse:Reference URI="#CertId-62149565" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" />
</wsse:SecurityTokenReference>
</ds:KeyInfo>
</ds:Signature>
</wsse:Security>

go through this webinar and follow the steps...It will solve your problem..
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1b657d59-0c01-0010-4fa8-f792fa412823
Regards,
Ravi

XI SOAP receiver adapter. Java and decentral adapter engine.

Hi,
I would like to send the below to a web service... have done a custom mapping to
produce the entire message below, and turned off Use SOAP envelope option in the
receiver adapter.
Can anyone point me in the right direction (in terms of the correct why to go about this)
or to why it is not working? Because I see it in the payload option of the message fine (in RWB).
Can java mapping be used to build the entire message?
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:noNamespaceSchemaLocation=" EnvelopeStructure.xsd">
<SOAP-ENV:Header>
<Q-ENV:Header>
<Q-ENV:Sender-Id>a03430170001</Q-ENV:Sender-Id>
<Q-ENV:Receiver-Id>1aa1150001</Q-ENV:Receiver-Id>
<Q-ENV:Correlation-Id>1231201109096878</Q-ENV:Correlation-Id>
<Q-ENV:Message-Id>M1231201109096878</Q-ENV:Message-Id>
<Q-ENV:Date-Sent>26 Apr 2004 18:01:08 CDT</Q-ENV:Date-Sent>
<Q-ENV:Document-Type>RequestForQuotation</Q-ENV:Document-Type>
<Q-ENV:Message-Format>Q 1.0</Q-ENV:Message-Format>
</Q-ENV:Header>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<Q-ENV:Body>
<Q-ENV:Content-Type>text/xml</Q-ENV:Content-Type>
<Q-ENV:Message-Type>xCBL</Q-ENV:Message-Type>
<Q-ENV:Encoding>UTF-8</Q-ENV:Encoding>
<Q-ENV:Message-Body>
blah blah
</Q-ENV:Message-Body>
</Q-ENV:Body>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
thanks
Dylan.

I am getting various errors, because I am not sure I understand how this adapter works exactly.
I would like to send a custom SOAP message.
I use a java mapping to create the entire soap message...
In the soap adapter I turn on "Do not Use SOAP envelope".
What should the final message sent out of the SOAP adapter look like ? Will a standard SOAP
envelope be added around it anyway?
Do I need to add beans after the XISoapAdapter bean in order to remove the soap envelope?
How do the modules work? Is there a good resource on the subject?

SOAP RECEIVER - no soap envelope sent

Similar Messages

Maybe you are looking for