PI soap receiver cannot transform attachments in WSDL response message

Hi,
Need a solution for this, urgently?
In synchronous proxy to webservice scenario, the response message payload has <multiref> tag in it.
After going through sdn, help, etc got to know that PI doesnt support multiref in soap-messages.
Then whats the solution for this.
1. Server-config.wsdd" in section <globalConfiguration>. Adding this line <parameter name="sendMultiRefs" value="false"/> didnt made any difference.
help highly appreciated,
Thanks
Pratibha

As far as I understand you may receive multiref messages as attachments. Have you checked the Keep Attachment check box in receiver communication channel?
Regards,
Prateek

Similar Messages

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

WSRM Adapter replaced with soap in PO7.4. Getting error "Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error"

Hello All,
We have scenario proxy->pi->webservice. In older versions of PI system they used wsrm adapter at receiver side and it's working fine.
Receiver interface is asynchronous. So no response structute is present and receiver service is business component(since receiver is a third party).
During migration, we have replaced the receiver adapter with SOAP adapter and used message protocol as SOAP 1.1 but the message is failing and in communication channel it is showing error "Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error". In this case the receiver interface is stateless xi 3.0 compatible(re using the old), after changing it to just stateless also issue persists.
In target url field if i prefix the url with "http" then above mentioned error is occurring otherwise if i use the hostname:port/path.. then it is giving error
"soap: Call failed: com.sap.aii.af.sdk.xi.srt.BubbleException: Unsupported protocol". So maintaing the url as http://hostname:port/pat.....
As in old channel wsrm channel there is no userid and password, i haven't given any userid/pwd in receiver channel.
used the bean sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean with parameters
Module Key = soap
Parameter Name = noSOAPMakeSysErrFromResponseFault
Parameter Value = false
and
xmbws.No SOAPIgnoreStatus = true
but not successful.
Please help me. I got stcuk here.

Hello Jannus,
The connectivity is working fine. Network team has confirmed it. I doubt that any strucutre(header) difference might be present in message when sending with wsrm adapter compared to sending with soap adapter.
Please let me know the exact difference between soap and wsrm functionality in receiving end.
By considering the structure issue, i have checked the "do not use soap envelope" check box, then i got error "Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type"
Then i used message transform bean, but not successful.
Regards,
Ch.Venkat.

OSB and WSDL response message

Hi all,
from the WSDL, that I put at bottom of this post, I've created a new OSB project importing the WSDL itself and creating a proxy service based on it.
I've implemented it using the fn-bea:execute-sql function:
<ctx:route><ctx:service>{
fn-bea:execute-sql (
$myDataSource,
'resultset',
'SELECT id, name, type_id, domi_country_id, open_date, close_date FROM myTable WHERE id=?',
xs:string($body/urn:clientDataLookup/portfolioNumber/text())
}</ctx:service></ctx:route>
For getting the response, in the pipeline reponse I added a REPLACE action:
Replace [ node contents ] of [ . ]
in [ body ] with
[ <urn:clientDataLookupResponse>
<xmlCntent>{ $result/con:service/resultset }</xmlCntent>
</urn:clientDataLookupResponse>
I deduced the above xml response message using the OSB xquery wizard navigating through variable structure section and selecting $body - clientDataLookup (response) variable:
$body/urn:clientDataLookupResponse/xmlCntent
from that xpath expression I deduced the above xml response message.
My question: is that approach correct ? Why should I rewrite the xml response message ?
I'm wondering how to allow OSB to generate the correct xml response message in automatic way and then use it as template and fill only the xmlCntent param.
Thanks in advance
ferp
<definitions name="ClientDataLookup"
targetNamespace="http://wsdl/ClientDataLookup.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://wsdl/ClientDataLookup.wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<message name="ClientDataRequest">
<part name="buId" type="xsd:string"/>
<part name="portfolioNumber" type="xsd:string"/>
</message>
<message name="ClientDataResponse">
<part name="xmlCntent" type="xsd:string"/>
</message>
<portType name="ClientData_PortType">
<operation name="clientDataLookup">
<input message="tns:ClientDataRequest"/>
<output message="tns:ClientDataResponse"/>
</operation>
</portType>
<binding name="ClientData_Binding" type="tns:ClientData_PortType">
<soap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="clientDataLookup">
<soap:operation soapAction="clientDataLookup"/>
<input>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:bsource:dataservice"
use="encoded"/>
</input>
<output>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:bsource:clientdataservice"
use="encoded"/>
</output>
</operation>
</binding>
<service name="ClientDataService">
<documentation>WSDL File for Client Data Lookup</documentation>
<port binding="tns:ClientData_Binding" name="ClientData_Port">
<soap:address
location="http://localhost:8080/soap/servlet/rpcrouter"/>
</port>
</service>
</definitions>

In most common use cases a service bus transforms the messages from one format to other. In your case you are actually doing the same. You are transforming the message from database structure to the structure which is defined by the WSDL. The snippet you are using is not XML, its an XQuery snippet. There is nothing unusual about it. The tree structure in the left side is given for that purpose only, to facilitate writing XPaths and XQuery snippets. If you do not want to type anything and want to get it graphically (or example when its a big XML), use Eclipse IDE of OSB and create a XQuery transformation which you can call from OSB message flow.
Edited by: AbhishekJ on Nov 11, 2011 12:57 AM

Soap Receiver adapter Transform.ContentType

Dear experts,
We are getting error "415 Unsupported Media Type".my knowledge we need transform content type wil be Application/soap+xml. Could we get this format from PI?. need to add any module for this transform.
Thnaks,
ajai

Dear Stefan,
now we getting below error in sxmb_moni
<?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code>
<SAP:P1>-BC_RECEIVER_WS_TO_WS_YGVK</SAP:P1>
<SAP:P2>-SAPISU,http://ygvk_ws_to_ws.SI_RECEIVER_WS_TO_WS_YGVK</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>No standard agreement found for , BC_RECEIVER_WS_TO_WS_YGVK, , SAPISU, http://ygvk_ws_to_ws, SI_RECEIVER_WS_TO_WS_YGVK</SAP:AdditionalText>
<SAP:Stack>Problem occurred in receiver agreement for sender -BC_RECEIVER_WS_TO_WS_YGVK to receiver -SAPISU,http://ygvk_ws_to_ws.SI_RECEIVER_WS_TO_WS_YGVK: No standard agreement found for , BC_RECEIVER_WS_TO_WS_YGVK, , SAPISU, http://ygvk_ws_to_ws, SI_RECEIVER_WS_TO_WS_YGVK</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
ajai

SOAP fault - How to log error in response message map

Hi,
I have a scenario ABAP Proxy <-> XI <-> SOAP.
Occassionally there is an issue with communication to the destination system and an HTTP 500 Error is returned. I assume this is due to a system related error and it is returned as a SOAP Fault as opposed to a SOAP response with payload.
How do I get this "HTTP-500" error into my message map to return to the calling system ?
I have looked at Fault Messages but need to know if these are relevant for the SOAP Adapter and how they can be utilised ?
Thanks for any help.
Kind regards
Colin.

SOAP fault message not in correcto format to allow an application error to be caught.

SOAP receiver configuration and ESR part

Hi,
Could you Please help me out?
I have a scenario like IDOC to SOAP in that they are not giving the WSDL structure I have to prepare and have to use.
Please tell me how to create wsdl and then how to proceed with Data Types, Message Types, Service interfaces and mappings and ID configuration.
Thanks & Regards,
L N Venkata Praveen Gade.

Basically you are using target system using soap adapter as receiver.
Import the WSDL In ESR as external definition.
use external message type in the message type tab to choose mesg from WSDL.
create receiver service interface as usual and specify wsdl message as message type.
Message Mapping again choose source message your sender message type and receiver as reciever mesg type(one you picked from the WSDL)
Operation mappping is pretty same
Configure soap receiver channel.
two things
specify wsdl url (find out soap address location tab in the wsdl)
and action (if required) other leave blank.
http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
check this [link |http://www.riyaz.net/blog/xipi-a-guide-to-using-sap-xi-soap-adapter/technology/sap/113/]too
hope that helps.

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.

How to use given WSDL into SOAP Receiver Adapter.

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

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

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

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

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

SOAP Responce cannot be decoded after during a long web service exection

I have an AIR application.
I am using the spark web service and i have set up a fualt handler and set the requestTimeout to 0.
I call an opertaion that calls a .Net web service.
Inside that .Net web service i run a very heafty SQL using ADO and then i take the results from the SQL statment and I use those results to make an excel spreadseeht and saved on the machine running the webservice.
This web service ran by itself can easily take up to two minutes to run (which is very acceptable given the nature of the query), and I would like the AIR application to just continue to sit there and wait for it to complete (also acceptable).
Even with the request timeout set 0 i receive a "SOAP Responce cannot be decoded" fault from the webservice before the web service is even done running. Why is this happening?
I've run several debuggers to make sure the info to the .Net web service is correct, I've stepped through the entire web service piece by piece and no exceptions are thrown during its execution. It just takes a long time to perform and the fault occurs right in the middle of the execution of web service.
I've also had this happen when i'm debugging some of my other web serivces. If a breakpoint is hit in visual studio in my webservice and i do my thing and step through stuff blah blah blah standard debugging stuff, the same thing will happen a fault will be hit before the webservice is done executing.
Please help.

I'm not sure what the deal is between Flex/AIR and Visusal Studios, but i descided to publish my webservices and point the wsdl there instead of using the visual studio generated one.
AND BEHOLD
I't worked and worked much much faster than i was anticipating.
So i'll just chalk it up to poor communication between FLEX and VS. But if anybody knows a more complete answer I would still love to hear it.

SOAP receiver adapter configuration issue

Hi Everyone,
When I am trying to excute a sync scenario from SAP<>XI<>Webservice from Integration engine , I am getting the below error message.
Error while sending message: com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Cannot process the message because the content type 'text/xml; charset=utf-8' was not the expected type 'application/soap+xml; charset=utf-8'.
In the receiver SOAP adapter, I have configured Transformation module where I kept the MessageTransformationBean in processing sequence as a priority and also provided the module configuration.
ModuleKey: transform
ParameterName: Transform.ContentType
Parameter Value: application/soap+xml;charset=utf-8.
But still get the above error message in the communication channel. I am using certificates in my configuration that were deployed in visual Admin.
In the adapter configuration, I have just provided the Target URL, Configured User Authentication, certificate authentication and SOAP action.
Can anyone help me.. how to rectify the issue.....
Thanks in advance,
Hareen

HI Hareen,
I decided to give SOAP1.2 using the standard SOAP Adapter a try
There are a few noticeable differences between the request message of SOAP1.1 and SOAP1.2
1.) SOAP 1.1 uses a different namespace from SOAP 1.2. For SOAP 1.1 it is "http://schemas.xmlsoap.org/soap/envelope/" while for SOAP 1.2 it is "http://www.w3.org/2003/05/soap-envelope".
2.) SOAP 1.2 does not use SOAPAction in its header.
3.) Content type is also different, for SOAP 1.1 it is "text/xml" while for SOAP 1.2 it is "application/soap+xml"
So a sample request for SOAP 1.1 would be like this:
Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://sampleaction"
While for 1.2 it is:
Content-Type: application/soap+xml;charset=UTF-8;action="http://sampleaction"
The SOAP action is moved to the content type (experts please correct me on this).
Based on the differences, you need:
1.) Construct the correct SOAP Envelope for request message mapping and remove it for the response mapping
2.) Use MessageTransformBean to change content type
3.) Leave SOAPAction as blank
I think dynamic soap action is no longer possible because the action is hardcoded in the module configuration (please correct).
Hope this helps,
Mark

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

SOAP receiver problems

Hi Folks,
I am sending data to the webservice using SOAP receiver. In the runtime workbench I can see the message as successfull, but the end user is claiming that , he didn't get the data from XI.
What could be the possible reason for this?
Where might the message lost?
And for one message which is using SOAP receiver as communication channel , In the audit log I can see the steps as below:
SOAP: request message entering the adapter with user J2EE_GUEST
SOAP: completed the processing
SOAP: continuing to response message
SOAP: sending a delivery ack
SOAP: sent a delivery ack
The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.
MP: Leaving module processor
The message status set to DLVD.
For other message I can see the log as :
SOAP: request message entering the adapter with user J2EE_GUEST
SOAP: completed the processing
SOAP: continuing to response message
SOAP: sending a delivery ack ...
SOAP: sent a delivery ack
MP: Leaving module processor
The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.
The message status set to DLVD.
Both are using same communication channel. still u can see the difference in the steps that are exicuted (check leaving module processer line in both).
Is it mandatory that the series of steps should be same for all the messages?
I have 2 queries, please answer both......
Thanks SPMD

HI
As a first test , import the wsdl shared by third party in soap uI/MS infopath/xml spy , fill in the test data (preferably same which you are trying to post now) and do a test :- doing this you will get to know if there is any problem in the WS iteslf. if you get http 200 ok then posting happened and ask the third party to check if they got any request.
If you have sync soap then you will be getting the desired response back to soap ui .
Also check if you need to put soap action also check the content type if its text/xml or app/xml some WS dont accept App/xml u may need to use message transformation bean in modules tab.
if there is any connectivity at ntwrk level then please try if you can trouble shoot using this blog
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
Regards
$rinivas

SOAP receiver adapter error using Google Search web service

Hi all,
I'm trying to connect and old 4.5b system to XI SP16 to make it receive information from external Web Services.
My scenario is made up of a sender RFC adapter and a SOAP receiver which is sending the message to the Google web service (http://api.google.com/GoogleSearch.wsdl) and then awaiting a response from it.
I'm stuck with this error: "No Deserializer found to deserialize a ':key'". The problem is that XI is sending this kind of message:
          <m:doGoogleSearch xmlns:m="urn:GoogleSearch" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
               <key>mykey</key>
               <q>testing</q>
               <start>0</start>
               <maxResults>1</maxResults>
               <filter>true</filter>
               <restrict>String</restrict>
               <safeSearch>true</safeSearch>
               <lr>String</lr>
               <ie>String</ie>
               <oe>String</oe>
          </m:doGoogleSearch>
while Google is expecting this:
          <m:doGoogleSearch xmlns:m="urn:GoogleSearch" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
               <key xsi:type="xsd:string">mykey</key>
               <q xsi:type="xsd:string">testing</q>
               <start xsi:type="xsd:int">0</start>
               <maxResults xsi:type="xsd:int">1</maxResults>
               <filter xsi:type="xsd:boolean">true</filter>
               <restrict xsi:type="xsd:string">String</restrict>
               <safeSearch xsi:type="xsd:boolean">true</safeSearch>
               <lr xsi:type="xsd:string">String</lr>
               <ie xsi:type="xsd:string">String</ie>
               <oe xsi:type="xsd:string">String</oe>
          </m:doGoogleSearch>
with explicitly declared xsi:type.
I've tested both messages with XMLSpy and the first one is always returning the same error.
Is there a way to make XI send an XML message with written xsi:type?
Many thanks in advance!
Max

Hi Ricardo!
I followed your suggestion to create a simple XSLT mapping program (in the ABAP stack) and I added it to the Interface Mapping in the Integration Repository. The result is exactly the soap message that the Google web-service is expecting.
I'm attaching the XSLT code below in case somebody has the same problem... thanks again for your hint!!
Regards!
Max
<xsl:transform version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:sap="http://www.sap.com/sapxsl"
>
<xsl:strip-space elements="*"/>
<xsl:template match="/">
<ns1:doGoogleSearch xmlns:ns1="urn:GoogleSearch" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
      <key xsi:type="xsd:string"> <xsl:value-of select= "//key"/> </key>
      <q xsi:type="xsd:string"> <xsl:value-of select= "//q"/> </q>
      <start xsi:type="xsd:int"> <xsl:value-of select= "//start"/> </start>
      <maxResults xsi:type="xsd:int"> <xsl:value-of select= "//maxResults"/> </maxResults>
      <filter xsi:type="xsd:boolean"> <xsl:value-of select= "//filter"/> </filter>
      <restrict xsi:type="xsd:string"> <xsl:value-of select= "//restrict"/> </restrict>
      <safeSearch xsi:type="xsd:boolean"> <xsl:value-of select= "//safeSearch"/> </safeSearch>
      <lr xsi:type="xsd:string"> <xsl:value-of select= "//lr"/> </lr>
      <ie xsi:type="xsd:string"> <xsl:value-of select= "//ie"/> </ie>
      <oe xsi:type="xsd:string"> <xsl:value-of select= "//oe"/> </oe>
   </ns1:doGoogleSearch>
</xsl:template>
</xsl:transform>

PI soap receiver cannot transform attachments in WSDL response message

Similar Messages

Maybe you are looking for