Soap Receiver Adapter problem. very urgent..

Hi,
When I am sending data from XI to CRM through soap receiver communication channel I am getting error:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Authority check failed
Pls advice urgent.
Regards

Hi Rick,
At fist did you create SOAP fault message mapping in your scenario?
If not then plz do that.
Some links for ur help:
Troubleshooting - RFC and SOAP scenarios *** Updated on 20/04/2009 *** - have a look into this to troubleshoot your SOAP
Fault Message Types - A Demo (Part 1)
Receiver SOAP adapter scenarios:
RFC -> XI -> WebService - A Complete Walkthrough (Part 1)
RFC -> XI -> WebService - A Complete Walkthrough (Part 2)
Regards,
Vinod.

Similar Messages

SOAP Receiver Adapter problem (client certificate required)

My Scenario is similar to described in https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3721. [original link is broken] [original link is broken] [original link is broken] I have two PI servers running on one machine. I am trying to post message HTTPS with Client authentication via SOAP adapter from one PI system to SOAP adapter of other PI server. I have done the following configuration.
PI Server AXD - (Client) - Receiver SOAP adapter
PI Server AXQ - (Server) - Sender SOAP Adapter.
Steps in AXD
1. I have created a certificate of AXD in the service_ssl view of key storage.
2. I have imported the AXQ public certificate in to AXD in the TrustedCAs of Key storage
Steps in AXQ
1. I have created a certificate of AXQ in the service_ssl view of key storage.
2. I have imported the AXD public certificate in to AXQ in the TrustedCAs of Key storage.
3. I have created a user in AXQ and assigned the certificate of AXD under usermangement in Security provider to this user.
4. I have added the AXD certificate under Client Authentication tab with require client certificate option checked in the SSL Provider.
5. I have assigned the user created in AXQ in the step above to the Sender Agreement.
Now when I post message from AXD with Configure Client Authentication checked (Here I have selected the certificate of AXD and view as service_ssl) I am getting the following error.
Exception caught by adapter framework: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - java.security.AccessControlException: client certificate required at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:884) at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3
Any pointer to solve this problem is highly appreciated.
Thanks
Abinash

Hi Hemant,
I have couple of questions. Why do we need to import certificate for SOAP WS-Security and from where I can get it?
As far as my scenario goes I am not using message level security.
Secondly what do you mean by TRUSTED/WebServiceSecurity? I don't see any such view inside the Key Storage. I can see a view named just WebServiceSecuity though.
Also I don't have a decentralized adapter installation rather I have two separate PI instances having their own central adapter engine.
Abinash

SOAP Receiver Adapter problem

Hi guys,
I have problem with ABAP Proxy->XI->SOAP scenario. I send data from R/3 via Proxy. I see in the monitor, that message has been processed successfully, however, the SOAP adapter does not send this message to the target. I tried to run a listener on on my local machine on port 80 and sent data from SAP. Again, in monitor successful, but no action in the listener - the message did not arrive. (the adapter was set up to send data to ma local PC). The scenario is async.
Any idea, what could be wrong?
In the receiver SOAP adapter - hoe to set up Target URL? http://<machine>:<port> or w/o port and it is automatically sent to port 80?
Thanx for answers!
Olain.

Hi guys, thanx for answers..
All the systems are in the local network, so no proxy is there. However, in the communication channel monitoring I get error: connection timed out , can be due to invalid adress.. However, If i try to reach the WS from the SOAPui tool, this web service works...
Any other idea?
Olian

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 !

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 adapter for Axis

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

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

SOAP receiver adapter digest authentization

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

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

SOAP Receiver Adapter / Scenario calling WebServices

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

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

Soap receiver adapter 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

SOAP Receiver adapter with attachments not working

Hello,
I have a simple synchronous scenario like this; ABAP proxy with attachments to SOAP with attachments.
The SOAP receiver adapter has been configured with the parameters 'Do not Use SOAP envelope' and 'Keep attachments'. We create our own SOAP envelope with custom SOAP headers, so that's the reason for the 'Do not use SOAP envelope' setting.
When we test the scenario with an attachment then we get a timeout from PI. However, when we test the same scenario without any attachment then no errors occur.
The external webservice has also been tested with SOAP UI and it works fine.
Do you have any clues what the problem can be? What are we still missing in the configuration?
We did try with the adapter modules such as PayloadSwapBean and the Message TransformBean, so far without success...
Many thanks.
Roberto

Hi Stefan,
The attachments are not really big, around 150KB.
According to the other party (Oracle Service Bus) no messages with attachments have been received. In fact it seems like those messages never leave the PI server. SOAP requests without attachments are processed successfully.
Thanks
Roberto

SOAP Receiver Adapter - Read Header data on Synchronous Response

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

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

CDATA element deleted in SOAP receiver adapter

Hello Everybody!
I've got a problem with SOAP receiver adapter. I've made a mapping for synchronous HTTP -> XI -> SOAP interface, in which the request mapping is java mapping, which produce a message like this:
<?xml version="1.0" encoding="UTF-8"?> <ns0:SaveISDocument xmlns:ns0="http://pl.optix.pl/aews">
<ns0:xmlDocument><IMAGES><IMAGE FileName="tmp.xml" ClassName="IVX">
<![CDATA[PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iaXNvLTg4NTktMiI/Pgo8SU5WT0lDMDECiAgPElET0MCiAgICAgPEVESV9EQzQwPgogICAgICA8VEFCTkFNPkVESV9EQzQwPC9UQUJOQU0CiAgICAgIDxNQU5EVD4zMDwvTUFORFQCiAgICAgIDxET0NOVU0OTAzMTAyMzA4MzwvRE9DTlVNPgogICAgICA8RE9DUkVMPjQ1QjwvRE9DUkVMPgogICAgICA8U1RBVFVTPjMwPC9TVEFUVVMCiAgICAgIDxESVJFQ1QMTwvRElSRUNUPgogICAgICA8T1VUTU9EPjI8L09VVE1PRD4KICAgICAgPElET0NUWVASU5WT0lDMDE8L0lET0NUWVACiAgICAgIDxDSU1UWVAWjFJTlYwMTwvQ0lNVFlQPgogICAgICA8TUVTVFlQPklOVk9JQzwvOVk9JQzAxPgo=]]>
</IMAGE></IMAGES>
</ns0:xmlDocument></ns0:SaveISDocument>
In CDATA is a Base64 representation of some file.
I hoped at oubound of SOAP adapter sholud be something like this:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header/><SOAP:Body><ns0:SaveISDocument xmlns:ns0='http://pl.optix.pl/aews'>
<ns0:SaveISDocument xmlns:ns0="http://pl.optix.pl/aews">
<ns0:xmlDocument><IMAGES><IMAGE FileName="tmp.xml" ClassName="IVX">
<![CDATA[PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iaXNvLTg4NTktMiI/Pgo8SU5WT0lDMDECiAgPElET0MCiAgICAgPEVESV9EQzQwPgogICAgICA8VEFCTkFNPkVESV9EQzQwPC9UQUJOQU0CiAgICAgIDxNQU5EVD4zMDwvTUFORFQCiAgICAgIDxET0NOVU0OTAzMTAyMzA4MzwvRE9DTlVNPgogICAgICA8RE9DUkVMPjQ1QjwvRE9DUkVMPgogICAgICA8U1RBVFVTPjMwPC9TVEFUVVMCiAgICAgIDxESVJFQ1QMTwvRElSRUNUPgogICAgICA8T1VUTU9EPjI8L09VVE1PRD4KICAgICAgPElET0NUWVASU5WT0lDMDE8L0lET0NUWVACiAgICAgIDxDSU1UWVAWjFJTlYwMTwvQ0lNVFlQPgogICAgICA8TUVTVFlQPklOVk9JQzwvOVk9JQzAxPgo=]]>
</IMAGE></IMAGES>
</ns0:xmlDocument></ns0:SaveISDocument>
</SOAP:Body></SOAP:Envelope>
Unfortunatelly there is something like:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header/><SOAP:Body><ns0:SaveISDocument xmlns:ns0='http://pl.optix.pl/aews'>
<ns0:SaveISDocument xmlns:ns0="http://pl.optix.pl/aews"><ns0:xmlDocument><IMAGES><IMAGE FileName="tmp.xml" ClassName="IVX">
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iaXNvLTg4NTktMiI/Pgo8SU5WT0lDMDECiAgPElET0MCiAgICAgPEVESV9EQzQwPgogICAgICA8VEFCTkFNPkVESV9EQzQwPC9UQUJOQU0CiAgICAgIDxNQU5EVD4zMDwvTUFORFQCiAgICAgIDxET0NOVU0OTAzMTAyMzA4MzwvRE9DTlVNPgogICAgICA8RE9DUkVMPjQ1QjwvRE9DUkVMPgogICAgICA8U1RBVFVTPjMwPC9TVEFUVVMCiAgICAgIDxESVJFQ1QMTwvRElSRUNUPgogICAgICA8T1VUTU9EPjI8L09VVE1PRD4KICAgICAgPElET0NUWVASU5WT0lDMDE8L0lET0NUWVACiAgICAgIDxDSU1UWVAWjFJTlYwMTwvQ0lNVFlQPgogICAgICA8TUVTVFlQPklOVk9JQzwvOVk9JQzAxPgo=
</IMAGE>
</IMAGES></ns0:xmlDocument></ns0:SaveISDocument>
</SOAP:Body></SOAP:Envelope>
... which is not correct, because CDATA tags are lost!
Anyone has idea, how to enable adapter to process message right?
Best regards,
Mikolaj

Henrique:
As I wrote - the webservice was wrote by 3rd party software supplier - so I wasn't sure if I could change a specification at this point - that was a reason why I needed a CDATA element. A CDATA element was at entry of this webservice and I couldn't send to it my data correctly using XI. That was a problem. Hope You got it now.
Finally I've managed the problem because 3rd party software supplier agreed to change their service and use <CDATA> tag instead of CDATA element.
I solved the problem but my question still remain not answered.
At OSS I was asked to upload latest SP (now I've got 12 at Java Stack).
If this will help I'll close this thread.
Best regards
Mikolaj

SOAP Receiver Adapter (Asynchronous Call)

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

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

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

HTTPS config in SOAP receiver adapter ?

Hi Guys,
I have configured the soap receiver adapter with the URL
*https://xxxx.abcd.com/xyzv/bbbb.asmx with the user authentication *
I have tested the url and the user and pw in the browser and they are working fine but the messages are failing the soap receiver adapter with the 401 unautorized error as the message from the Audit log in the 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: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized. Setting message to status failed.
Do i need to configure the Java Stack for HTTPS ? The communicaion is between the XI system and a third part system internally.
any help would be appreciated ?
Thanks,
Srini

Hi Guys,
I have solved the problem and NTLM works with PI 7.0 but we need to configure soap axis adapter
The Windows NTLM authentication is supported by Axis's CommonsHTTPSender handler and consequently it is supported by the Axis adapter's corresponding handler com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender. Read about How Can I use CommonsHTTPSender as the transport handler? if CommonsHTTPSender is not enabled on your system. Once it is enabled, you can use com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender instead of default com.sap.aii.adapter.axis.ra.transport.http.HTTPSender as the transport handler in the module configuration and set the authentication setting to NTLM and enter usename as domain\username in the channel configuration
To use CommonsHTTPHandler, the optional Jakarta-Commons-Net, Jakarta-Commons-HttpClient, Jakarta-Commons-Codec libraries are required. Make sure that these libraries are available for the Axis adapter at the deployment check page If these components are not available, you will need to include the corresponding jar files (commons-codec-1.3.jar, commons-httpclient-3.0.jar, and commons-net-1.0.0-dev.jar from the Axis 1.4 release) in aii_af_axisprovider.sda and deploy this archive (see How to prepare aii_af_axisprovider.sda?).
The provider.xml file must include the jar-name entries for these jar files, as shown in:
    <jars>
       <jar-name>commons-net-1.0.0-dev.jar</jar-name>
       <jar-name>commons-codec-1.3.jar</jar-name>
       <jar-name>commons-httpclient-3.0.jar</jar-name>
    </jars>
Once you do all the above settings, NTLM works fine
Thanks,
Srini

Soap Receiver Adapter problem. very urgent..

Similar Messages

Maybe you are looking for