SOAP Response change from http 200 to http 204

Hello
I must change for a application, that call a webservice on the pi, change the
SOAP Response from HTTP 200 OK to HTTP 204. I think that must chnage on the SOAP Adapter and wei can't change in the messages or mapping. Also wit a Fault Messages is this not runnig.
What is with BPM, have any body do somthing with that.
Regards Tom

Hello Stefan
This thrid Application need this response. We cann't change this. We spaek with this product manager, but he want change this. He want this when the interface is async, that application now no conntent come back.
Regards Tom

Similar Messages

SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPT

Hi there,
I am trying to publish a file from SAP as web service using XI and SOAP Adapter.
I am using ABAP proxy to get the data into XI.
Designing and Configuration in XI has no problems because when i use File adapter the data is trasmitted to FTP server.
But when I used SOAP Reciever adapter I am getting following error in RWB
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: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Error during parsing of SOAP header.
<b>Scenario</b>: SAP ABAP Proxy -> XI -> WebService. Asynchronous.
<b>SOAP</b> Receiver adaptor.
<b>Target URL</b> http://<host>:<port number >/sap/xi/engine?type=entry&version=3.0&Sender.Service=SAPDC2653&Interface=urn:bzttest:00:hsa:test%5EOB_MI_BZT_TEST&QualityOfService=ExactlyOnce
Do not use SOAP Envelop is checked.
<b>SOAP Action</b> http://sap.com/xi/WebService/soap1.1
What i am missing here? How should I solve this problem?
Any help is appreciated,
Thx,
Yogi

Say there's a bapi/rfc that you want to call on an R/3 backend (e.g. 4.6c). On it's own, the R/3 system cannot expose the rfc/bapi as a web service, but XI can. So in this case, the scenario would be:
WS client -> XI -> R/3
When XI "exposes" a web service, it is exposing a service for a receiving system (in the above example, the R/3 system). XI itself does not provide or contain the service implementation. When XI exposes a web service, it is always done via the <b>sender</b> soap adapter (i.e. if soap adapter is used). Receiver soap adapter is used to call or consume an actual web service from an external application.
Regards,
Jin

Error Reading Soap Response

Hi,
We are having a problem reading Soap Response:
Scenario: From XI/PI we are calling a webservice with Synchronous
message with WS-Security including Authentication, Signature, TimeStamp
and Encryption using SOAP Receiver Adapter. We are able to send the
request successfully and also the webServer is able to understand the
request and sending the response back. The problem is the PI is unable
to read the response and giving a below error:
com.sap.aii.af.ra.ms.api.DeliveryException: expecting end tag:
Transform, but found
InclusiveNamespaces at state 1
We tested successfully end-end with NON-Secured sites with out WS-
Security.
Please let me know if you have seen this error or any thoughts.
Thanks,
Laxman
This is the actual Request Message:
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:getUser xmlns:ns0="http://csa -namespace:8090/ddsssaws/IdentityManagementService">
<string>XYZ123</string>
</ns0:getUser>
Also we extracted raw traffic using TCPMon:
Below is the raw-traffic of SOAP adapter (used TCPGateway to capture the traffic)
Request:
POST /edsssaws/IdentityManagement HTTP/1.0
Accept: /
Host: 999.97.19.45:9999
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
Content-ID: <soap-1f3af770018111ddc0d300144f2515b0Atsap.com>
Content-Disposition: attachment;filename="soap-1f3af770018111ddc0d300144f2515b0Atsap.com.xml"
Content-Type: text/xml; charset=utf-8
Content-Description: SOAP
Content-Length: 5530
SOAPACTION:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header><wsse:Security xmlns:wsse='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd' SOAP:mustUnderstand='1'><wsse:BinarySecurityToken xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='sap-9' ValueType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3' EncodingType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary'>MIIFFTCCBH6gAwIBAgIKZptrmQABAAALBTANBgkqhkiG9w0BAQUFADByMRMwEQYKCZImiZPyLGQBGRYDY29tMRMwEQYKCZImiZPyLGQBGRYDZWRzMRQwEgYKCZImiZPyLGQBGRYEY29ycDEUMBIGCgmSJomT8ixkARkWBGFtZXIxGjAYBgNVBAMTEUVEUyBFbnRlcnByaXNlQ0ExMB4XDTA4MDQwMTIxMjMyN1oXDTEwMDQwMTIxMjMyN1owIjELMAkGA1UEBhMCVVMxEzARBgNVBAMTCklUQVBJTlRERVYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALjKvScjIEmp5Q1X3/gfR0WZO22KiEAOAx9kM0q3kpT/0dk2ZVit5YCBT4Zkt6Tttyh21xmnCcVgcRo0YOxXcXrLq25HRsSbxY3Zu37qq4tqExX5gQCtfR1pRjRrhQfDPmPGzFOrTzSjxJ5BH49p3KZcUhj7KpWQEakDBvJAgMBAAGjggMAMIIC/DAdBgNVHQ4EFgQUadHS0gj0CBQymaNnAlGJphSCB/YwHwYDVR0jBBgwFoAULNVTI/CtjM0k4MlzJLuQI4tVUy8wggEaBgNVHR8EggERMIIBDTCCAQmgggEFoIIBAYaBxWxkYXA6Ly8vQ049RURTJTIwRW50ZXJwcmlzZUNBMSgxKSxDTj11c3Bsc3NjYTAwMixDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1jb3JwLERDPWVkcyxEQz1jb20/Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPWNSTERpc3RyaWJ1dGlvblBvaW50hjdodHRwOi8vd3d3LmVkcy5jb20vY3J0cmV2bHN0L0VEUyUyMEVudGVycHJpc2VDQTEoMSkuY3JsMIIBDwYIKwYBBQUHAQEEggEBMIHMIG2BggrBgEFBQcwAoaBqWxkYXA6Ly8vQ049RURTJTIwRW50ZXJwcmlzZUNBMSxDTj1BSUEsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1jb3JwLERDPWVkcyxEQz1jb20/Y0FDZXJ0aWZpY2F0ZT9iYXNlP29iamVjdENsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwQwYIKwYBBQUHMAKGN2h0dHA6Ly93d3cuZWRzLmNvbS9jcnRyZXZsc3QvRURTJTIwRW50ZXJwcmlzZUNBMSgxKS5jcnQwDAYDVR0TAQH/BAIwADALBgNVHQ8EBAMCBLAwPAYJKwYBBAGCNxUHBC8wLQYlKwYBBAGCNxUIh4qV4WN/hPFkRuHwclug63SWS2GpOIihPT8LwIBZAIBBDATBgNVHSUEDDAKBggrBgEFBQcDATAbBgkrBgEEAYI3FQoEDjAMMAoGCCsGAQUFBwMBMA0GCSqGSIb3DQEBBQUAA4GBAGzyuh56APinQtmE9oWsT8NHcQqMASHZnN26RAofnxuIUH1VyBK2CGyiiDnCS0cDIGBl45sqOO8uRClE7CngeZEAV9JL5bhpUF6rywmFKvqe5FyqnrScczeaODV0g9sO4vUrwdGlReA5ncvtSN/u82MWDqtHAHBfpYQxZUrW</wsse:BinarySecurityToken><wsu:Timestamp xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsu-targetID-1f10b320-0181-11dd-aebd-00144f2515b0'><wsu:Created ValueType='xsd:dateTime'>2008-04-03T13:23:17Z</wsu:Created><wsu:Expires ValueType='xsd:dateTime'>2008-04-03T13:25:17Z</wsu:Expires></wsu:Timestamp><xenc:EncryptedKey xmlns:xenc='http://www.w3.org/2001/04/xmlenc#' Id='EK52789332'><xenc:EncryptionMethod Algorithm='http://www.w3.org/2001/04/xmlenc#rsa-1_5'/><ds:KeyInfo xmlns:ds='http://www.w3.org/2000/09/xmldsig#'><wsse:SecurityTokenReference><wsse:KeyIdentifier ValueType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier' EncodingType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary'>ykCivrkfwQdj30aJid9VGnjtY=</wsse:KeyIdentifier></wsse:SecurityTokenReference></ds:KeyInfo><xenc:CipherData><xenc:CipherValue>Fi5B3uBMSp4nAKh3rLAs4DJQ5iCLoupE1oq3VOFueea1Y90xI200OFraV2mRS2ywsejH36nwy
XYPuB5ZQScJampqZDtTR28cq890s4sEKFpycsNyNM9VScWaVoi4nKBKRIdGVoLgLf+NrmzJnXD
6eb4F6tWWyw8g2FJel4=</xenc:CipherValue></xenc:CipherData><xenc:ReferenceList><xenc:DataReference URI='#ED13608949'/></xenc:ReferenceList></xenc:EncryptedKey><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='#wsuid-body-1f108c10-0181-11dd-838e-00144f2515b0'><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>UaW58GCrg/nrA/EfW+OyHP2DCio=</ds:DigestValue></ds:Reference><ds:Reference URI='#wsu-targetID-1f10b320-0181-11dd-aebd-00144f2515b0'><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>LFuszgJ412Fe8PRtK3W69RTXndY=</ds:DigestValue></ds:Reference></ds:SignedInfo><ds:SignatureValue>K4iZoVGhuI41fj9BdXx7wUz/JEi2pqh60gZZta8tOfaVmC1PfNtPg61N0sYescfM4RmkQpDorS1d
VB/DAJKz173HTD5rn/SuwmYgql4aVKPNlIDD90ZXoJ/mfzwT/Kei6yjWtvCYthCxaUtP/LFDB/dA
mr1OUAj9X2DHkzF6g=</ds:SignatureValue><ds:KeyInfo><wsse:SecurityTokenReference><wsse:Reference URI='#sap-9'/></wsse:SecurityTokenReference></ds:KeyInfo></ds:Signature></wsse:Security></SOAP:Header><SOAP:Body xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-body-1f108c10-0181-11dd-838e-00144f2515b0'><xenc:EncryptedData xmlns:xenc='http://www.w3.org/2001/04/xmlenc#' Type='http://www.w3.org/2001/04/xmlenc#Content' Id='ED13608949'><xenc:EncryptionMethod Algorithm='http://www.w3.org/2001/04/xmlenc#tripledes-cbc'/><xenc:CipherData><xenc:CipherValue>lZkC7zZZfqBUg5rnqMZypi5ZvnPBvw36fjeFmCDQ5DMDjKXShO4apBjBE3gUsLGL1TMli18D0NWK
dmVHQTePitGhvQ7YiyaXgjekZckS2P91Qv/9Zut5/hzCYhgVarnUgGmr8Qi4aSYXCY0oBD6SzVXy
/UoQHPASF3mhYPaFBtmTJu2dHmV6v4HTKC+Om0</xenc:CipherValue></xenc:CipherData></xenc:EncryptedData></SOAP:Body></SOAP:Envelope>
Response:
HTTP/1.1 200 OK
Date: Thu, 03 Apr 2008 13:23:54 GMT
Content-Length: 9511
Content-Type: text/xml
Set-Cookie: JSESSIONID=cTPmH0hKYvKqK427JJb573FT1RWZhHY5l7XnLlsjsk6yRkS2g5y6!1973031667; path=/
Connection: close
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><env:Header><wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" env:mustUnderstand="1"><xenc:EncryptedKey xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"><xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"></xenc:EncryptionMethod><dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><wsse:SecurityTokenReference><wsse:KeyIdentifier xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier" wsu:Id="Id-dgdMMmsGkjae8aSYF_59_xwe" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">adHS0gj0CBQymaNnAlGJphSCB/Y=</wsse:KeyIdentifier></wsse:SecurityTokenReference></dsig:KeyInfo><xenc:CipherData><xenc:CipherValue>mbOmTXSiYuEiWHbP3dbrDXFpZaSoQ084wMBt7uRxNo49p1fpQBkDpr/H2wPNbHy4qzSTVzP7EESzWFjFEb/7BH3dt4JuyzBFH1M0X77YBW5YHNGpiUmj934ziydojqcU6jWBsUaFxXsAPmvy0q3vVk8xnZcQHxMNhPS5ebK9o=</xenc:CipherValue></xenc:CipherData><xenc:ReferenceList><xenc:DataReference URI="#Id-yMgwZrtQctSvW1mT1sDWdZ8D"></xenc:DataReference></xenc:ReferenceList></xenc:EncryptedKey><wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="Id-2DXBQHwdRE0oquWQV0mjtw1U" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">MIIFVjCCBLgAwIBAgIKfps5MgABAAADHjANBgkqhkiG9w0BAQUFADByMRMwEQYKCZImiZPyLGQBGRYDY29tMRMwEQYKCZImiZPyLGQBGRYDZWRzMRQwEgYKCZImiZPyLGQBGRYEY29ycDEUMBIGCgmSJomT8ixkARkWBGFtZXIxGjAYBgNVBAMTEUVEUyBFbnRlcnByaXNlQ0ExMB4XDTA2MDUyMzIzMDY0OVoXDTA4MDUyMjIzMDY0OVowYzELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlRYMQ4wDAYDVQQHEwVQbGFubzEMMAoGA1UEChMDRURTMQwwCgYDVQQLEwNTRFMxGzAZBgNVBAMTElNTQVdlYlNlcnZpY2VzLURFVjCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0qRmvQkxnPnEZQNSabPVwM6sEf8vFUOAlgQ9uuiDImVmDw4Afg45zbmTBeDdv4wsIap7kI4VJhv60SdOQg6i1mIEi83Qk7UJYD8XvKuOalSLYhHu92lsp0kIZlAdzipVd1Pp0cI3wSvP6o9zfX0gALpisf8rGJ1CkVWbtHaVp0CAwEAAaOCAwAwggL8MB0GA1UdDgQWBBTKT4KKuR/7BB2PfRomJ31UaeO1jAfBgNVHSMEGDAWgBQs1VMj8K2MzSTgyXMku5Aji1VTLzCCARoGA1UdHwSCAREwggENMIIBCaCCAQWgggEBhoHFbGRhcDovLy9DTj1FRFMlMjBFbnRlcnByaXNlQ0ExKDEpLENOPXVzcGxzc2NhMDAyLENOPUNEUCxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxDTj1TZXJ2aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPWNvcnAsREM9ZWRzLERDPWNvbT9jZXJ0aWZpY2F0ZVJldm9jYXRpb25MaXN0P2Jhc2U/b2JqZWN0Q2xhc3M9Y1JMRGlzdHJpYnV0aW9uUG9pbnSGN2h0dHA6Ly93d3cuZWRzLmNvbS9jcnRyZXZsc3QvRURTJTIwRW50ZXJwcmlzZUNBMSgxKS5jcmwwggEPBggrBgEFBQcBAQSCAQEwgf4wgbYGCCsGAQUFBzAChoGpbGRhcDovLy9DTj1FRFMlMjBFbnRlcnByaXNlQ0ExLENOPUFJQSxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxDTj1TZXJ2aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPWNvcnAsREM9ZWRzLERDPWNvbT9jQUNlcnRpZmljYXRlP2Jhc2U/b2JqZWN0Q2xhc3M9Y2VydGlmaWNhdGlvbkF1dGhvcml0eTBDBggrBgEFBQcwAoY3aHR0cDovL3d3dy5lZHMuY29tL2NydHJldmxzdC9FRFMlMjBFbnRlcnByaXNlQ0ExKDEpLmNydDAMBgNVHRMBAf8EAjAAMAsGA1UdDwQEAwIEsDA8BgkrBgEEAYI3FQcELzAtBiUrBgEEAYI3FQiHir5XhY3E8WRG4fByW6DrdJZLYak4iKE9PwvAgFkAgEEMBMGA1UdJQQMMAoGCCsGAQUFBwMBMBsGCSsGAQQBgjcVCgQOMAwwCgYIKwYBBQUHAwEwDQYJKoZIhvcNAQEFBQADgYEALsVozc1aVcPNBVsRXRbAiStchxG2fKDOt9kRzL6BHtQa/fkp81EjOBhETn8N1IHLUsINn05wGgdDA2UszjLtRIpQmdpCyh2gzFW8Dlx5X7vJyvJsoDOPDBArv55dTjCEfok1oz3ux3mrVotuvr1pKIVTr7ylpRM8p8GBXw=</wsse:BinarySecurityToken><dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:SignedInfo><dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></dsig:CanonicalizationMethod><dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></dsig:SignatureMethod><dsig:Reference URI="#Id-wS1xP_ArcYYXY4qkqYznI7_W"><dsig:Transforms><dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>tr3NrozQWsKrvH38naIEnQXrzgQ=</dsig:DigestValue></dsig:Reference><dsig:Reference URI="#Id-1vPAqVSMhSLH3WiBQkTTfldz"><dsig:Transforms><dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"><c14n:InclusiveNamespaces xmlns:c14n="http://www.w3.org/2001/10/xml-exc-c14n#" PrefixList="xsd n1"></c14n:InclusiveNamespaces></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>AUWlqeyq6w5LQnggK5dT6flLUU=</dsig:DigestValue></dsig:Reference></dsig:SignedInfo><dsig:SignatureValue>Yx5Pre8VChTLOhPVln5xhO21dM93a2FPxQTsZY1BBIWlqeHkAEQqXvhI/EU459QZIGDOubLK0Z9AT0SRmDOgtnWNBT0duqveQ1Ippbd0hXaehW48ObrMIKnYfq5ub1kNYv9mslybPRZw9OaiijNmLfIty8qc8ctRV0lFwAjcQyk=</dsig:SignatureValue><dsig:KeyInfo><wsse:SecurityTokenReference><wsse:Reference URI="#Id-2DXBQHwdRE0oquWQV0mjtw1U"></wsse:Reference></wsse:SecurityTokenReference></dsig:KeyInfo></dsig:Signature><wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Id-wS1xP_ArcYYXY4qkqYznI7_W"><wsu:Created>2008-04-03T13:23:55.459Z</wsu:Created></wsu:Timestamp></wsse:Security></env:Header><env:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" wsu:Id="Id-1vPAqVSMhSLH3WiBQkTTfldz"><xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Content" Id="Id-yMgwZrtQctSvW1mT1sDWdZ8D"><xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"></xenc:EncryptionMethod><xenc:CipherData><xenc:CipherValue>LB6IKwEJgvTPdPGNeIzcpjPjC9GXi3sou5PaCnF3m4x6ToA6gDV5Sw/ODnCEeqFURgWFX8ZgxYF9YJdyj7ERAifs8MNBh/rHCitT02mU8pirwGdqSXlfCX4KYsHtUnyiGKbbMCwvCCs4LgBPnx8tCN39aazA1Ge/5JPfwupYMU/lAbyajdP1qva/gxhMCqGkgAnQgB1TJDfARvDsJnx6p2zqKsnRnNreBFClyBG7GHeMvpnzg4poPCFlj2baIoK2CSQmVbPdcPk4rgg1PAWDQwIIzBCKpZjysHeb/sW9jObekbnn4mCnUdzjRERoklstpZNeWKi/jLEaNsIX1ixhsUyWIyknYGaBjDiiGqmS6BIO1RHu0SydiMv1L/FzIWgyO9VhilGdTWsVDP6CxljxTqg41bobuPazkjQHyBK9rCGQI9J/bjSiA2S6FBDHxhA6SfDjyhvGzDhGNLMd/***2ieUGQWg/atFbqItqW2HZzb7T0cuIiROBYaGLUbWnghcUXAn9dV38GbCMfWk65OhpkD5EQXr/5bPxK41L3sPIrAs2JnMM9nLuj6gLo35VMlsdVQ1c0o3JYQ4JARnSlnUrgW20Cilwf3Fn2m7Yj4QicC6RUhChEudnbgYIjqq0Ypc8BsjJWAPYRuVAUVArINqgUjCNuOxQKV3dyEayS0lZ8UOBfopGBnIlEDS9h62ZIiIKfRhCD6xLsY1PED7K5ZHRvj2TEtQtYoZxeTNDH7/IdukO/cATF9B0DhSvx2YK8EzlG3pygcLGeHZ4DfwmGC5lnO5NZrqFaHXa1LNNgZ9H1rezZyOfizbvT/O5mC8tvINNvP5Ik37OdD6Lmjnc4u0gAKee6QqQ7uk8A6xbrjrnOWp46vnoNmvMZxyAMAD8xFBz9b8MVHu0IJX5etLdRbjsSsMYNpUomqFjfweFe3NeHESUA5IhkYUQVNNwJJ3MCpJDWWHFNLEbzRoUolXVOQhC0PC6j6KmHQH2yib0KWKKJn7kLrUtgGazJMatLDhWDU5oEtZbDJzauxikxto0R6ZirhjKqmVCeVu51yrbW4lgC2upXxJsQ2q5igBaX7Qvz4D1ICkp1m7CRG7cWrU6MfBSXusRsPIp/7wJsdBpXSPb97cZi6y82EP6iQhsyRJ9YODUr22WObb4CvIYo8bDFW1Sw6BImoqkgsoXB/j2oNp0g6vLhYy0OjF5LAdDbhDk23WA00KGj9xAHEPVkqfXdivfc3quxWdpIBri0JnQGA/T1GsxwM4YKvhp5hPl28sgLeo7/I0DstkK6Jispkt5/03N364bRQBAHykAqUAyDvMHz8jiZK0Jo2cnTDTzoDtDi9q2wbSI25lh31FZ68kKJ1t399VRdF4JlSKvaXE8pj1ljE3J6GsII6haD3W17Kns2hmnduL0pEeChUgq0VrXaK8k5e0CR1JdmzVEHNo7WKWwB901cOrtRfxh1yQWvw0dHCSlxzAlISAb7Y2t0MlIoITIKi9XzJSpbxtp5zCQiup3PPDni1wQWotYd9WVZ2Zs2KxDkusDbENOAu68RjtWoOQxGXPrek73CQ9ja2D6doNjdbwX9Exrhqlek9507Sn0J2RO5kJG6huXD3TTXcBcBlD8HYq76JfSNtqgpUwKztPCxaECMmvTm4n1YRT5pkpKfOmlx262TJllv1l2B5cs3f6ODWf/ULarjwMPT2ajviYvCDXl4Kl8HNcmXKhR3W8IzCvWCsPwwDoFbjCk5Xkdd6IVPAX9i0LP5hZqS1bMrJnTreNTVd4glne7T6SdjkFt2MR1UJnsNHlVDoeGhb5VhfphgPg2r1DUyY7k3QlXHGxCBctjlkTUVg9D0NgWf4JrE2KXtdCPR/gX7HjrR6wq24UsibqOH5yi2Zh2hGwP2OWrPRQ6QMqIdW2voAux0GOkL7Ip8GCRml5eilopmRyh8D3PxWw8CwfC81slylodVHvGP8AjGE9cddQhMzQ2s96ZPQVTLEo734UQFkH511HtJGWVCTbxGBmtpEyoJZSJJ9CeG2sXuwEGF7YXR31xJJZbtOKFyskQw3BJGb1SE35iF5lr0hshYB1/gm2YmlTX68nZtux9NWRIKnJ3EHvWUc9UIudzoEMf0LyLZm5pFtkZAUQ16F4BfqEVJekVlUBOs1dCSYN6lUcsVzinhUcY1eBni75vEXaO8zSTy4ZwcOiGYvR9QK2bSuzYen1LKBaFK6UIAVstr29avGAGp5nk3qM63/05rUv2jnDM6XYIoFSx1lpE7SwtvbiRUQjgUA4ZX7Oa7Mp9HJj5W0o7ZVViKbYTtxux5/2AXgXxLo/i3YsHd7BUE/2KTjUrKokTYUzCgTlXkSmYOfRY1wdxeixrLfbSWBD1Y4ZbcMw3l/57XIPmGl42HrRyEFIxGnt7kQHR9A3abfJ93E0Y8AMiQuhG2/WTZho/IzxQ/OfDJm78o97K10pbe7OUIrfpPNTfM3cenEd37ZFWI67yPNwYfiZw8E7uks8GIKSAqrt7q55C10EpmizEcydD5EKtGyElXk6ifr3GO6WbHJNUp6FvgyHQTF6VXRiC91Rv/ZvUQggxRDyF6HibOq5BqDwTbMY0OnbB6nR3KlGYfhkBfEUiqbd10HYzCzWx0uGv54swAwsRUtOQFMpbr5B17yXdE5vGN2uTm02Bgr3EwOUyuw2ttgdUedDH8APmOlDr23wPiFljsTgWbbX/UZQGCyhNxa8avQtDdlymu8e8PS5tMupjMSkJtULUUXQyoKGwcXwwvp25iubNODEt5aZNt45bGKwOW5P3Xzu2ZJ6tAtW/zh7NfN1EHVZIwIlxWgPaag0ComeirsmZfNu3W2wge7Cg9aOYws81iIRaLa0YgYWZwH3C6yTRRQcM8fx1U1TiK2tIkFcc4iAjefZKMHBsodtTzo4EYaYvb9SyjGgZLTMYSlTbpx31Ot0T/t8kFxpML/ObDgoKoxWUVXxfD74HDW/0Uo9JDgdaV/lxJ2CJ7y8gb4ayKsVRNB4BmP5OzA/q9vzZWgtfoM4ODu//vsAed9Dvi4f1pJt5Cf8WWxv1PtWS4gvFe87a03kyhwSzI4obai23oYlCcyrUyL9LBZCwcBgn4tDcno6HPIHT2iEpi00sTuTD2bqXyTkXrxgzGSwlfBzCXr7xczoZDJoU5oj5t59cyq/faUZZkhc0bb8dhOH2/oYcanpfdtNS64VeO42eXaPbkMP00IrHTAUb2KxXQa7h80vB3LMA29cS3EBaJ8pnIJ/sPh0bT5A/FiiiJVJNm8g7EBcvd2nbJWRAkVNp1SxLPoUKF1dRt3OiJwhbdOASOnmJS8IXRjskuIYRsMgXSNdlMGxadedsdB9TKRvgzGkutWu9mQ3+0XJJIp7S23E8b3OLH1CAxhH3wyWu8TmeksImbGc0VY7oSTTtNNWOdeRDQ==</xenc:CipherValue></xenc:CipherData></xenc:EncryptedData></env:Body></env:Envelope>

Any thoughts???
Appreciate your input.
Thanks,
Laxman

Broken SOAP response

Hi all,
we develop a mobile application (.NET compact framework/ WinCE) making use of SOAP-Requests on SAP WebAS 6.20 patch level (PL) 37.
As we patched one of our systems to PL 42, the resulting SOAP response changed and can not interpreted correctly, causing in a managed error in Windows CE. Even if the web service on PL42 is consumed via Visual Studio the problem can not be corrected.
It seems that SAP has changed the namespace in the SOAP response. The WSDL, however, is unchanged.
Has anybody encountered similar problems or has some idea how to change the WSDL correctly?
Can a change in namespace be correct if the WSDL is not adjusted?
     Thanks
          Chris
Answer System PL37:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
          xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
   <Z_SZ_SEND_XML.Response
              xmlns="urn:sap-com:document:sap:rfc:functions">
     <XML>Hallo</XML>
   </Z_SZ_SEND_XML.Response>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Answer System PL42:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
       xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
       xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" >
<SOAP-ENV:Body>
<rfc:Z_SZ_SEND_XML.Response
             xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
   <XML>Hallo</XML>
</rfc:Z_SZ_SEND_XML.Response>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
WSDL(both)
<?xml version="1.0" encoding="utf-8"?>
<definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="urn:sap-com:document:sap:rfc:functions" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="urn:sap-com:document:sap:rfc:functions" xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
    <s:schema targetNamespace="urn:sap-com:document:sap:rfc:functions">
      <s:element name="Z_SZ_SEND_XML">
        <s:complexType>
          <s:all />
        </s:complexType>
      </s:element>
      <s:element name="Z_SZ_SEND_XML.Response">
        <s:complexType>
          <s:all>
            <s:element name="XML" type="s:string" />
          </s:all>
        </s:complexType>
      </s:element>
    </s:schema>
</types>
<message name="Z_SZ_SEND_XMLInput">
    <part name="parameters" element="s0:Z_SZ_SEND_XML" />
</message>
<message name="Z_SZ_SEND_XMLOutput">
    <part name="parameters" element="s0:Z_SZ_SEND_XML.Response" />
</message>
<portType name="Z_SZ_SEND_XMLPortType">
    <operation name="Z_SZ_SEND_XML">
      <input message="s0:Z_SZ_SEND_XMLInput" />
      <output message="s0:Z_SZ_SEND_XMLOutput" />
    </operation>
</portType>
<binding name="Z_SZ_SEND_XMLBinding" type="s0:Z_SZ_SEND_XMLPortType">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
    <operation name="Z_SZ_SEND_XML">
      <soap:operation soapAction="http://www.sap.com/Z_SZ_SEND_XML" />
      <input>
        <soap:body use="literal" />
      </input>
      <output>
        <soap:body use="literal" />
      </output>
    </operation>
</binding>
<service name="Z_SZ_SEND_XMLService">
    <documentation>SAP Service Z_SZ_SEND_XML via SOAP</documentation>
    <port name="Z_SZ_SEND_XMLPortType" binding="s0:Z_SZ_SEND_XMLBinding">
      <soap:address location="http://brain05a.dsc-gmbh.de:8080/sap/bc/soap/rfc" />
    </port>
</service>
</definitions>

I agree that you should escalate your support request. However I do not think the problem is the namespace. Both messages seem consistent with the WSDL to me and the namespaces are the same. These two elements are equivelent:
<Z_SZ_SEND_XML.Response xmlns="urn:sap-com:document:sap:rfc:functions">
<rfc:Z_SZ_SEND_XML.Response xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
The difference between them is that one uses a namespace prefix (rfc in this example), the other does not. Both of these are valid for the WSDL you have provided. I would also say that using namespace prefixes as the PL42 system does is a better practice. So your problem is coming from something else I think. This could be an error with the xml parser if it can not handle namespace prefixes, but I'm fairly certain .NET Compact Framework can handle this.

SOAP Response error:

HI Experts,
Here my scenario is RFC PI SOAP synchronous interface. While sending the message from PI receiver system is expeting SAOP envelop I added this envelop with xslt mapping. Even response message is coming with SOAP envelop I removed with Xslt.. now I am getting below error message in response:
*Here i am not using any authoentication. it is not required..*
In SXMB_moni:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In communication channel:
Description
23.11.2011 14:45:11.557     Information     The message was successfully received by the messaging system. Protocol: XI URL: http://r3vidci.got.volvo.net:52000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
23.11.2011 14:45:11.564     Information     Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
23.11.2011 14:45:11.568     Information     Message successfully put into the queue.
23.11.2011 14:45:11.572     Information     The message was successfully retrieved from the request queue.
23.11.2011 14:45:11.573     Information     The message status was set to DLNG.
23.11.2011 14:45:11.577     Information     Delivering to channel: SOAP_Receiver_BOSS_VID
23.11.2011 14:45:11.577     Information     MP: entering1
23.11.2011 14:45:11.579     Information     MP: processing local module localejbs/AF_Modules/MessageTransformBean
23.11.2011 14:45:11.599     Information     Transform: using Transform.Class: $identity
23.11.2011 14:45:11.634     Information     Transform: transforming the payload ...
23.11.2011 14:45:11.637     Information     Transform: successfully transformed
23.11.2011 14:45:11.638     Information     MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
23.11.2011 14:45:11.676     Information     SOAP: request message entering the adapter with user J2EE_GUEST
23.11.2011 14:45:11.695     Information     SOAP: completed the processing
23.11.2011 14:45:11.696     Information     SOAP: continuing to response message bf2ba0ac-15e1-11e1-cc01-00000c601d4e
23.11.2011 14:45:11.696     Error     SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
23.11.2011 14:45:11.698     Error     MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
23.11.2011 14:45:11.699     Error     Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
23.11.2011 14:45:11.700     Error     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: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized. Setting message to status failed.23.11.2011 14:45:11.704     Error     The message status was set to FAIL.

Hi Rajesh,
I tried with XMLSPY.. i am able to send and get the responce witout any authentication.. I gone through vijay's blog... but i din't find any solution in that..
one more thing.. here inteface is sending from SAP portal system > SAP ECC> SAPI--> webservice(Microsoft system). whenever Portal team sending the message to SAP they are getting below error"
call to messaging system failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENER
In PI I am getting below error:
.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized

SOAP response message error

Hi,
We have a scenario where in we perform a synchronous send from a BPM and post the request to a url using a SOAP receiver channel.
When we test the scenario,the message fails in PI with the following error "com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error"But when we try to test the same in SOAPUI by using the same payload,we do not have any issues in getting the response back.
Please could anyone advise on what could be the issue.
Thanks and Regards,
Induja

>
Induja Ramesh wrote:
> Resolved.
How?

XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request

Hi,
We are doing File to WCF Scenario( SOAP ). I am trying to post the Data to WCf usingf SOAP Reciver Adapter.
Getting the Following error.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request
Thanks in advance

>>> Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request
Answer: Use the third party wsdl in SOAP UI or any soap client tool and send the request and see the response. The problem here is the message structure mismatch between your request to the webservice and webservice expecting...
Possible 2 reasons:
1) You are not creating the target message based on the wsdl structure or not configured soap receiver properly.
or
2 ) Your wsdl is not latest or updated one or some changes have happened in the third party webservice hosting side.

XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error

I'm getting this message in RWB when trying to send an order:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Weird thing is, other orders have been successfully to the same partner.
Is this something on my side or the receivers side?
What does HTTP 500 Internal Server Error mean and how to fix?
Thanks,
Jeff

More info on this problem:
Discovered that the HTTP 500 error only occurs when a "change" file is sent:
I send an order create file to a partner using a SOAP adapter. They receive it successfully.
I make a change to the sales order and send that file. It uses the same Config Scenario, receiver determination, receiver agreement and comm. Channel.
But this file shows an HTTP 500 error in the RWB.
I send it right after the first order create file, so no overloading is happening, etc.
Conenctivity to the url is fine because the create file went through.
I don't know what else it could be. Any other info/log in RWB to look at to help decipher the error?

Parsing Soap Responses

Hello,
I am fairly new to CF and am trying to parse and then query a soap response from a third-party api. I have been able to get a response in xml format, but that is where I am stuck. Below the xml response I am getting an error that reads Element.LOGINRESPONSE.LOGINRESULT.XMLTEXT is undefined in LOGINXML.
I realize my code is a mess, but I am just trying out various things. Does anyone have any insight how to get at the Login Response variable in my soap response so that I can query it?
Thanks for any insight!!

<cfset wsdl_url="http://somewebsite/sirewebsvc/sire.asmx?wsdl">
<cftry>
    
    <cfsavecontent variable="soap"><?xml version="1.0" encoding="UTF-8" ?>
         <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:Body>
                 <Login xmlns="http://www.siretechnologies.com/">
      <LicenseKey>LicenseKey</LicenseKey>
      <Username>username</Username>
      <Password>password</Password>
      <LicenseType>2</LicenseType>
      <APIKey>APIKey</APIKey>
      <SiteKey></SiteKey>
      <CryptKey></CryptKey>
      <WebOnly>false</WebOnly>
    </Login>
              </soapenv:Body>
          </soapenv:Envelope>
    </cfsavecontent>
        
        <cfhttp url="#wsdl_url#" method="post" >
            <cfhttpparam type="header" name="content-type" value="text/xml">
            <cfhttpparam type="header" name="SOAPAction" value="http://www.siretechnologies.com/Login">
            <cfhttpparam type="header" name="content-length" value="#len(soap)#">
            <cfhttpparam type="header" name="charset" value="utf-8">
            <cfhttpparam type="xml" name="message" value="#trim(soap)#">
        </cfhttp>
<p><cfoutput>#xmlFormat(cfhttp.fileContent)#</cfoutput> </p>
        <cfset MyXML = XmlParse(CFHTTP.FileContent)>
        XmlSearch(MyXML, "/LoginResponse/LoginResult/")
<cfcatch type="any">
        <cfdump var="#cfcatch#">
    </cfcatch>
</cftry>
<cfsavecontent variable="XMLFile"><?xml version="1.0"?>
<LoginResponse>
    <LoginResult>
???How do I get this from above, or make it a variable???
    </LoginResult>
</LoginResponse>
</cfsavecontent>

<cfset MyXMLDoc = xmlParse(XMLFile) />

<h2>Dump</h2>
<cfdump var="#MyXMLDoc#">
<cfset MyNodes = xmlSearch(MyXMLDoc,'/LoginResponse/LoginResult')>
<cfoutput>
    <h2>Nodes</h2>
    <cfloop from="1" to="#arraylen(MyNodes)#" index="i">
        
        <cfset LoginXML = xmlparse(MyNodes[i]) />
        <b>SessionKey:</b> #LoginXML.LoginResponse.LoginResult.xmltext#<br>
    </cfloop>
</cfoutput>
--->

I think I figured it out. Thanks to all who helped!! If anyone is interested, this is how I retrieved the session key from my Soap response.

<cfset wsdl_url="http://SOMEURL/sire.asmx?wsdl">
    
    <cfsavecontent variable="soap"><?xml version="1.0" encoding="UTF-8" ?>
         <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:Body>
                 <Login xmlns="http://www.siretechnologies.com/">
      <LicenseKey>LicKey</LicenseKey>
      <Username>user</Username>
      <Password>pass</Password>
      <LicenseType>2</LicenseType>
      <APIKey>API</APIKey>
      <SiteKey></SiteKey>
      <CryptKey></CryptKey>
      <WebOnly>false</WebOnly>
    </Login>
              </soapenv:Body>
          </soapenv:Envelope>
    </cfsavecontent>
        
        <cfhttp url="#wsdl_url#" method="post" >
            <cfhttpparam type="header" name="content-type" value="text/xml">
            <cfhttpparam type="header" name="SOAPAction" value="http://www.siretechnologies.com/Login">
            <cfhttpparam type="header" name="content-length" value="#len(soap)#">
            <cfhttpparam type="header" name="charset" value="utf-8">
            <cfhttpparam type="xml" name="message" value="#trim(soap)#">
        </cfhttp>
        <p><cfoutput>#xmlFormat(cfhttp.fileContent)#</cfoutput> </p>
        <cfset MyXml = XmlParse(cfhttp.fileContent)>
        <cfdump var="#MyXml#">
    <cfset responseNodes = xmlSearch(MyXml,"//*[ local-name() = 'LoginResponse' ]")>
     <cfdump var="#responseNodes#">
    <cfoutput>
<cfloop from="1" to="#arraylen(responseNodes)#" index="i">
    <cfset TheXML = xmlparse(responseNodes[i])>
    <cfset SesKey = "#TheXML.LoginResponse.LoginResult.XmlText#">
    <b>SessionKey:</b> #TheXML.LoginResponse.LoginResult.XmlText#<br>
    <b>Session Key:#SesKey#
</cfloop>
</cfoutput>

Soap response Error when processing XML CF.

Hello,
I have problems with soap response and wondered if you could give some advice.
Every time I send my message via soap I get the following error:
com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Error when processing XML CF.
Is it possible that the communication is aborted and my response message mapping is never started?
(Additional info: I tried to create an integration process and am not able to evaluate the response.)
Thanks a lot for your help.
Regards,
Julia

hi,
do you see any more error details in :
http://xiserver:port/MessagingSystem/monitor
did you check logs in visual admin ?
>>>>Is it possible that the communication is aborted and my response message mapping is never started?
yes - if the response is not ok the mapping may not be started
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 404 Not Found

Hi,
The scenario is ECC-XI-SOAP(Asynchronous). We are getting the below mentioned error in SOAP reciver channel:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 404 Not Found
Channel Configuration:
Target URL:
http://<hostname>:<port>/bpm/com/xyzprocess/SomeIntermediateEvent?wsdl=binding&mode=ws_policy
Tried with
http://<hostname>:<port>/bpm/com/xyzprocess/SomeIntermediateEvent as well
Conversion parameters:
Checked Do Not Use Soap Envelope
Appreciate any help in this regards.
Regards,
Vishal

Can you share with us the HTTP Headers for the Request?
POST http://server/sap/xi/engine?type=entry&version=3.0&Sender.Service=BusService&Interface=http://company.com/abc/CommonAck%5EMI_CommonAck_ia HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://sap.com/xi/WebService/soap1.1"
User-Agent: Jakarta Commons-HttpClient/3.1
Host: server
Content-Length: 560
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xir="http://www.dummy.org/response/">
<soapenv:Header/>
<soapenv:Body>
<xir:responseInput>
<Id>007</Id>
<Flag>10</Flag>
</xir:responseInput>
</soapenv:Body>
</soapenv:Envelope>
You can use the MessageTransformBean to correct the content type.
Thanks for the suggestion Mark.I am using MessageTransformBean but still the same issue.
Parameter Name:Transform.ContentType
Parameter Value:text/xml;charset=utf-8
Edited by: Vishal.P.Kulkarni on Oct 17, 2011 6:27 AM
Edited by: Vishal.P.Kulkarni on Oct 17, 2011 6:29 AM

How to handle soap responses

I am following this tutorial to handle SOAP responses but it does not work http://livedocs.adobe.com/flex/3/html/help.html?content=data_access_6.html
using code blew I am trying to parse the following soap response.
    <?xml version="1.0" encoding="utf-8"?>
    <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
                                     xmlns:s="library://ns.adobe.com/flex/spark"
                                     xmlns:mx="library://ns.adobe.com/flex/mx"
                                     xmlns:components="components.*"
                                     xmlns:hellos="services.hellos.*"
                                     height="957" creationComplete="initApp()" >
              <fx:Style source="Styles.css"/>
              <fx:Script>
                        <![CDATA[
                                  import mx.controls.Alert;
                                  private namespace invesbot = "http://Services.com";
                                  use namespace invesbot;
                                  private namespace a = "http://schemas.xmlsoap.org/soap/envelope/";
                                  private namespace b = "http://www.w3.org/2001/XMLSchema";
                                  private namespace c = "http://www.w3.org/2001/XMLSchema-instance";
                                  use namespace a;
                                  use namespace b;
                                  use namespace c;
                                  [Bindable]
                                  var _result:*
                                  private function initApp():void
                                            myService.mycustomers();
                        ]]>
              </fx:Script>
              <fx:Declarations>
                        <mx:WebService id="myService" wsdl="http://localhost:8081/WebServiceTest/services/Hellos?wsdl"
                                                         showBusyCursor="true"
                                                         fault="Alert.show(event.fault.faultString), 'Error'">
                                  <mx:operation name="mycustomers" resultFormat="e4x">
                                            <mx:request>
                                            </mx:request>
                                  </mx:operation>
                        </mx:WebService>
              </fx:Declarations>
    <mx:HBox>
                        <mx:Text
                                  text="{myService.mycustomers.lastResult.mycustomersReturn.name}"
                                  />
              </mx:HBox>
    </s:Application>
The SOAP response is as following
    <?xml version="1.0" encoding="UTF-8"?>
    <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:Body>
        <mycustomersResponse xmlns="http://Services.com">
          <mycustomersReturn>
            <age>28</age>
            <name>John</name>
          </mycustomersReturn>
          <mycustomersReturn>
            <age>29</age>
            <name>Alex</name>
          </mycustomersReturn>
          <mycustomersReturn>
            <age>30</age>
            <name>Jack</name>
          </mycustomersReturn>
        </mycustomersResponse>
      </soapenv:Body>
    </soapenv:Envelope>
Using the above code the output will be
    <name xmlns="http://Services.com" 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">John</name>
    <name xmlns="http://Services.com" 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">Alex</name>
    <name xmlns="http://Services.com" 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">Jack</name>
but when I use the following code to put the result in dropdown box it gives the following error
    <s:FormItem label="Employee:">
                        <s:DropDownList id="dropDownList3"
                                                                labelField="name"
                                                                dataProvider ="{myService.mycustomers.lastResult.mycustomersReturn}"/>
              </s:FormItem>
TypeError: Error #1034: Type Coercion failed: cannot convert XMLList@106e9af1 to mx.collections.IList.

Hi Ashish,
You can use Catch All error handler within scope of InvokeService action. By specifying SOAP Fault variable name there, response soap fault will be populated in variable.
In 11g(As per observation), split joins are strict towards definition of input and output message based on WSDL of target service which causes exception for invalidMessage in InvokeService action.
Hope this helps.

SOAP response to file

Hello,
i am working on scenario as given below.
JDBC to SOAP synchronous.
So once i got the response i need to save as file (XML format).
please let me know the stpes to capture the SOAP response payload from SXMB_MONI and save as XML file.
Thanks in advance...SARAN

Hi Saran,
Follow the below steps:
1. Goto the T-code SXMB_MONI.
2. Select the Interface Namespace and time
3. Press F8 to execute.
4. Select the Message.
5. In the Left Navigation Bar, you would be able to find Response, under that click on SOAP Header.
6. Right on "Main" and select the option to download.
7. Save the file as you would like.
Thanks,

SOAP Adapter XI 3.0 - HTTP 200 response fails

We have a scenario where a request message is sent successfully to a URL by the SOAP Adapter.
However, the response message has an HTTP response of 200 (meaning ok) which is not handled correctly by the
SOAP Adapter.
The error text shown in SXMB_MONI is:
com.sap.aii.af.ra.ms.api.DeliveryException: Failed to call the endpoint HTTP 200 OK
Is there something I am missing in the configuration to allow HTTP responses in the SOAP Adapter ? It is very odd that the SOAP Request works fine, but the SOAP Response does not.
Any ideas anyone ?
Kind regards
Colin.

Hi Bill
1. synchronous out / in
2. yes
3. working fine
following the way out to the elocateserver system is working fine.
The soap is working and the responce from the elocteserver is fine . But when the message is pick put the Timeout show up.
below is the Responce from elocateserver to xi
Hope this will help you
thanks olaf
Help
!http://sapnt09:50200/sap/public/icman/img/theme.jpg|alt=SAP|width=122 height=61 border=0 |src=http://sapnt09:50200/sap/public/icman/img/theme.jpg!
500 Connection timed out
Connection timed out (-5)
Error:
-5
Version:
6040
Component:
ICM
Date/Time:
Sat Oct 16 06:13:25 2004
Module:
icxxthr.c
Line:
2556
Server:
sapnt09_M64_02
Detail:
Connection to partner timed out
© 2001-2003, SAP AG

PO 7.4: NW BPM: HTTP Error response for SOAP request or invalid content-type.HTTP 200 OK

Hi Experts
I am trying to call NW BPM scenario(File to BPM) from PI, and using below adapter config.
I am getting below error.
Failed to call the endpoint: Error in call over HTTP: HTTP 200 OK
SOAP: Call failed: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
Any idea how to fix this issue?
Thanks,
Sandeep Maurya.

Hi Sandeep,
Test the URL from your browser and check the proxy settings as well.
Refer the below links
SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT
SOAP: Call failed: java.io.IOException: Failed to get the input stream from socket: java.net.SocketException: Connection…
Regards
Bhargava Krishna

SOAP Response change from http 200 to http 204

Similar Messages

Maybe you are looking for