"NO_RECEIVER_CASE_BE" error with SOAP Sender assigned to a Business Service

Hi all,
we have a strange error with XI3.0
We created a configuration scenario where the initial step is done by a Business System, that uses a SOAP Sender communication channel to send its request. And this works great when testing it with XMLSpy.
But we then needed to shift from a Business System to a Business Service, as the machine sending the SOAP request changed and was not anymore part of the landscape, but elsewhere.
Hence we recreated a SOAP sender which we assigned to this new business service, doing absolutely the same configuration work as for the other soap sender of the former business system.
Yet when testing it through XMLSpy, we everytime get a NO_RECEIVER_CASE_BE error back, stating that "No receiver could be determined". Yet when checking in sxi_cache, receiver determination is clearly there. All the blogs I went into are only refering to Business System for a SOAP sender, so I was wondering if any of you already managed to assign a SOAP sender to a business Service.
Regards,
Cedric

hi,
so you sue SOAP to make a query ? (sync)
or to send the data to XI ? (async)?
if async then make sure
you use <b>Quality of Service</b> other then BE
in your soap adapter channel
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>

Similar Messages

Error with Soap sender channel

I have a scenario SOAP->Proxy ..whenever I send a message through SOAP its giving error as below:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection SOAP_http://sap.com/xi/XI/System is currently not started.
Please help me in rectifying this...

Kiran,
strange thing is that when we remove the standard module from the channel then its workign fine..
Well, you can try couple of things more -
1. Re-start the java engine.
2. If step 1 doesn't work, delete the channel -> activate the change list -> create a new channel and try again.
I feel that after step 1, it should work. Let us know how it goes.
Regards,
Neetesh

HTTP Error 501 with SOAP Sender channel

Hello,
i've am simple Question:
I want to call the following SAP XI SOAP Sender channel "MySoapSenderChannel":
XI-Parameters:
namespace: <myInterfaceNamespace>
Interface: <myAsynchInterface>
QoS: Exactly Once in Order
Queue: MY_QUEUE
We do not care about the Response - so the processing is asynchron.
Thus my interface mapping maps to asynch interfaces. The desitnation
is an ABAP Proxy. The configuration has been done and tested.
Here my question:
according the documentation, the URL has the following syntax:
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel.
In our case:
http://<myHost>:8002/XISOAPAdapter/MessageServlet?channel=:MyService:MySoapSenderChannel.
But when i generate a WSDL for the interface out of the Configuration, the address is:
<soap:address location="http://<myHost>:8002/sap/xi/engine?type=entry&version=3.0&Sender.Service=MyService&Interface=...
and so forth.
But was is the difference between these 2 possibilities?
Why do i get HTTP Error 501 when i use the URL from the documentation (the first one)?
Thanx in advance
Gunnar

Gunnar,
I will suggest you to go through it once to check all your connection.
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Regards,
Sarvesh

Problem with Soap Sender CC

Hi,
SOAP - Proxy.
I have 3 seperate Scenarios in PI 7.0 in different Name space, with different Message interface names, under same SWC.
I imported them to PI 7.1 and used the same format that help says... with Service:cc and gave it to the calling service.
During my import, I noticed that the Message Interface and Name space were knocked off from the SOAP Sender adapter in PI 7.1. The scenarios are configured and working currently.
I have 3 CC in this format. In Soap sender CC, we will specify NS and Interface name. Thus I had to use 3 CC.
As per SAP Note 856597, the sender CC format should be...
http://host:port/XISOAPAdapter/MessageServlet?senderParty=FP&senderService=FS&interface=IF&receiverParty=TP&receiverService=TS&interfaceNamespace=IFNamespace
Now, in 7.10 we dont need to specify NS and Message Interface in soap sender CC. Hence, I created 3 sender URL for each scenario to call to PI 7.10 ( based on the interface / NS names ) and I have created 1 CC only instead of 3. This I thought would work because the sender CC is not tied with NS or MI any more, which are included in URL, and thus I have 3 different calling URLs.
Now, when I do this and activate, it is always calling only one service all the time.
Regards,
Venkat.

I have used the other channels in the same format. only NS and MI name changed. Sender and receiver are same.
We do specify outbound Interface and its NS in sender Soap CC prior to 7.1.
Morever, I am following the format as per the note I specified above.
It is able to call PI 7.1 succesfully but failing to call proper IM and MM.
No error mesage but only one scenario is called all the time.
Its like this...
prior to 7.1, we will have MI and NS info on the sender Soap sender CC. Hence we just mention the name of the CC in the target URL along with service. so it picks up the NS and MI from CC.
in 7.1, since we dont specify NS and MI in sender Soap CC, we have to notify the sender side MI and NS and we do that in sender side URL( to be given to the calling system ).
Now as per my understanding, since no NS or MI dependant info is speicfied in CC, I thought we can use one single CC instead of 3.
See my thought looks reasonable ...
but wondering why it isnt working.
Regards,
Venkat.

Use Moduls with SOAP Sender Adapter

Hi Experts,
I have a question regarding the use of modules in the soap sender adapter / communication channel. Is it correct that the use of modules in the soap sender adapter is not possible?
the background of my question is that we use modules from SEEBURGER in our Communication channels for archiving incoming and outgoing documents. the use of modules in the soap receiver adapter is possible. why not in the soap sender???
according to the sap help it is possible to use the axis framwork in the soap adapter. then it should be possible to use modules. Is that correct? I tested it but it is not working. If I send a soap message (with the soap reveicer adapter) to the axis soap sender adapter there occure internal server errors. it is only working if I write my own modules for the axis soap sender adapter? is it not possible to use external modules like in other channels (File/FTP, soap receiver etc.)???
thanks and best regards!
Christopher

we have moduls from SEEBURGER. so I have to test it. but before I need a scenario with which I can test it.
We have a customer who sends xml-files per soap to us. these files we receive succussfully with the soap sender adapter. now we want to use some modules. so we have to use the axis soap sender adapter. I tried to send an xml file with the soap receiver adapter to the axis soap sender adapter, but this was not working. http 500 internal server errors occurred. is it possible that this scenario (soap-to-axis-soap) is not working? need I a specific configuration for this?
thanks and regards
Christopher

Error with SOAP Request to calendar web service

Hi
I'm sending the following SOAP request to a calendar web service to create an appointment in the calendar. The response returns what seems to be a syntax error ("The Create method did not have a proper element in the request") but I can't see the cause of the fault. Any suggestions on what it may be? It's an 11g DB.
Many thanks
-x-POST-x-
POST /ocws-bin/ocas.fcgi HTTP/1.0
Content-Type: text/xml; charset="utf-8"
Content-Length: 993
SOAPAction: SOAPAction: "http://www.oracle.com/WebServices/Calendaring/1.0/Create"
Connection: close
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header><auth:BasicAuth xmlns:auth="http://soap-authentication.org/2002/01/">
<Name>CalendarName</Name><Password>CalendarPassword</Password>
</auth:BasicAuth> </SOAP-ENV:Header>
<SOAP-ENV:Body><cwsl:Create xmlns:cwsl="http://www.oracle.com/WebServices/Calendaring/1.0/"><CmdId>ITS APPOINTMENT</CmdId><iCalendar>
<vcalendar prodid="-//Oracle//Calendaring//Calendarlet//EN" version="2.0">
<vevent><class>PUBLIC</class>
<description>Calendar Body</description>
<dtstart value="DATE-TIME">20102905T120000</dtstart>
<duration>P00DT0H30M00S</duration>
<location>Location of user</location>
<summary>Incident ID - (name of user])</summary>
<uid>XGjRVnpReQALNsILlBlvcyXGCoUyXF</uid>
<x-oracle-eventtype>APPOINTMENT</x-oracle-eventtype>
<priority>5</priority>
</vevent>
</vcalendar>
</iCalendar></cwsl:Create></SOAP-ENV:Body></SOAP-ENV:Envelope>
-x-RESPONSE-x-
HTTP/1.1 500 Internal Server Error
Date: Thu, 27 May 2010 08:22:16 GMT
Server: Apache/2.2.4 (Unix) mod_ssl/2.2.4 OpenSSL/0.9.7a mod_fastcgi/2.4.6
OCAS-ProcTime: 407
Connection: close
Content-Type: text/xml; charset=utf-8
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server.Error::System::SOAPRequest</faultcode>
<faultstring>The Create method did not have a proper element in the request</faultstring>
<detail>
<cwsl:Error xmlns:cwsl="http://www.oracle.com/WebServices/Calendaring/1.0/">
<Class>Error::System::SOAPRequest</Class>
<Code>0020-00-00-00000034</Code>
<Line>3180</Line>
<FileName>SOAPRequestHandler.cpp,v</FileName>
<Version>1.57</Version>
<LastMod>2007/05/30 21:13:25</LastMod>
<Author>pscattol</Author>
<Date>Thu May 27 09:22:16 2010</Date>
<PID>26152</PID>
<TID>3044838304</TID>
<Level>Error</Level>
</cwsl:Error>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>

Hi,
I am having problem using dii client, while sending a
request to c# webservice. error follows
QName QNAME_TYPE_STRING = new QName(NS_XSD,
"string");
call.setReturnType(QNAME_TYPE_STRING);
call.setOperationName(new QName(BODY_NAMESPACE_VALUE,
"GetDetails"));
call.addParameter("String_1", QNAME_TYPE_STRING,
ParameterMode.IN);Do you need another call to addParameter here?
String[] params = { "02", "2004" };
String result = (String)call.invoke(params);

Error in SOAP sender CC. Channel stopped by administrative task.

I am getting an error in my SOAP sender communication chanel as follows;
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: Channel stopped by administrative task.
The channel is Active but still gets the same error. Any help would be appriciated.

RWB ---> Component Monitoring ---> Adapter Engine ---> Communication Channel Monitoring ---> Choose your CC and check its properties....check if it shows Channel Stopped...if yes then restart it.
Channel should be Active in ID and Started in RWB to work properly.
Regards,
Abhishek.

Another problem with SOAP sender

I have another problem with SOAP scenario in a different environment (PI 7.0) from my earlier post.
Scenario:
Soap Sender -> PI -> Soap Receiver
Following steps from GoogleSearch SOAP scenario in the SAP How-to Guide for SAP NetWeaver '04 entitled: "How To... Use the XI 3.0 SOAP Adapter" version 1.00 - March 2006.
I have loaded in the api.google.com/GoogleSearch.wsdl file as an External definition and created the SOAP receiver as described in the How-to guide. It takes a doGoogleSearch as input and sends back a doGoogleSearchResponse (Sync Call).
Note that the GoogleSearch.wsdl contains a complex type ResultElementArray that refers to ResultElement\[\], and a DirectoryCategoryArray that refers to DirectoryCategory\[\]. The ResultElement and DirectoryCategory types are defined in the GoogleSearch.wsdl file.
Problem One:
The generated WSDL for the SOAP sender contains the ResultElementArray and DirectoryCategoryArray types but it DOES NOT contain the required ResultElement and DirectoryCategory types. XML Spy complains that this WSDL is not valid because the type ResultElement\[\] is not defined.
Problem Two:
I generate a SOAP message in XML Spy, provide values for the doGoogleSearch fields, and send. In SXMB_MONI, the SOAP sender payload contains only the <key> value from the doGoogleSearch message body, i.e. <part name="key" type="xsd:string" />
The other doGoogleSearch fields seem to be missing, i.e.
<part name="q" type="xsd:string" />
<part name="start" type="xsd:int" />
<part name="maxResults" type="xsd:int" />
<part name="filter" type="xsd:boolean" />
<part name="restrict" type="xsd:string" />
<part name="safeSearch" type="xsd:boolean" />
<part name="lr" type="xsd:string" />
<part name="ie" type="xsd:string" />
<part name="oe" type="xsd:string" />
Does anyone know why:
(1) PI/XI seems to leave out the ResultElement and DirectoryCategory types from the SOAP sender service WSDL file?
(2) The doGoogleSearch message seen in SXMB_MONI contains only the first <key> field, and not the other fields?
Thanks for any help with this.

I have another problem with SOAP scenario in a different environment (PI 7.0) from my earlier post.
Scenario:
Soap Sender -> PI -> Soap Receiver
Following steps from GoogleSearch SOAP scenario in the SAP How-to Guide for SAP NetWeaver '04 entitled: "How To... Use the XI 3.0 SOAP Adapter" version 1.00 - March 2006.
I have loaded in the api.google.com/GoogleSearch.wsdl file as an External definition and created the SOAP receiver as described in the How-to guide. It takes a doGoogleSearch as input and sends back a doGoogleSearchResponse (Sync Call).
Note that the GoogleSearch.wsdl contains a complex type ResultElementArray that refers to ResultElement\[\], and a DirectoryCategoryArray that refers to DirectoryCategory\[\]. The ResultElement and DirectoryCategory types are defined in the GoogleSearch.wsdl file.
Problem One:
The generated WSDL for the SOAP sender contains the ResultElementArray and DirectoryCategoryArray types but it DOES NOT contain the required ResultElement and DirectoryCategory types. XML Spy complains that this WSDL is not valid because the type ResultElement\[\] is not defined.
Problem Two:
I generate a SOAP message in XML Spy, provide values for the doGoogleSearch fields, and send. In SXMB_MONI, the SOAP sender payload contains only the <key> value from the doGoogleSearch message body, i.e. <part name="key" type="xsd:string" />
The other doGoogleSearch fields seem to be missing, i.e.
<part name="q" type="xsd:string" />
<part name="start" type="xsd:int" />
<part name="maxResults" type="xsd:int" />
<part name="filter" type="xsd:boolean" />
<part name="restrict" type="xsd:string" />
<part name="safeSearch" type="xsd:boolean" />
<part name="lr" type="xsd:string" />
<part name="ie" type="xsd:string" />
<part name="oe" type="xsd:string" />
Does anyone know why:
(1) PI/XI seems to leave out the ResultElement and DirectoryCategory types from the SOAP sender service WSDL file?
(2) The doGoogleSearch message seen in SXMB_MONI contains only the first <key> field, and not the other fields?
Thanks for any help with this.

Error in SOAP sender scenario

Hi All,
   I am getting the following error when i execute a sender SOAP scenario from XMP Spy.
Scenario : SOAP --> XI --> RFC
I am getting the following error when i try to send request from XML Spy.
Error in XMl Spy:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>ADAPTER.JAVA_EXCEPTION</code>
               <text>com.sap.aii.af.mp.module.ModuleException: *adapter inactive*
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:703)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3.process(ModuleLocalLocalObjectImpl0_3.java:103)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292)
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
     at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:174)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:436)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
When i go to RWB-- > communication channel monitoring i see the channel status as "Started but Inactive" and when i go to Cluster node tab--> Cluster Node Details for Channel Unifier i see the following two entries every single time i try to send a message
14/10/10 05:35:10   error occured
14/10/10 05:35:10   request received
Please help to figure out what could be wrong.

open the SOAP Sender channel in Integration directory and change the status to active and then activate. Try resending SOAP message from XML spy

Principal Propagation with SOAP sender

Hello
I've already read some blogs and SAP help about configuring the principal propagation (PP), those blogs explains details about the configuration with SAP (ABAP and Java) system.
However in my case I have the third party SOAP sender application. I jsut wonder how to configure or write the soap Java program. Basically 2 things need to be done for hte soap sender:
1) Force the soap sender to send message along with a SAP assertion ticket
2) Sign the assertion ticket with private key (Public key/certification will be installed in PI Java AE)
I have no idea how step 1 works (Take Java soap client program as example)
Once a private key / public key is generated, how to use it to sign the assertion ticket?
Basically our soap sender could be from any platform (.net, java program, oracle, etc.), I need to know how to configure the soap sender for PP generally.
Anybody configured PP for soap sender?
Thank you so much

Hi Jayson,
With the amount of questions asked in one single question , i feel things are not clear at your end.
i suggest you going through:
Prinicipal propogation:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/808d3048-638c-2a10-35a6-faa48e50ad59
Principal Propagation in SAP XI
/people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi
Configuring adapters for principal propogation
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/cf9e199bf23e49e10000000a421937/frameset.htm
Regards
joel

CANNOT_READ_PALOAD error with SOAP to PROXY Synchronous interface

Hi,
Problem with SOAP to PROXY Synchronous interface.
In Production client, some times we are getting the below shown error in SXMB_MONI. There is no Inbound payload also.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Unable to read payload from the message object</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Please suggest me to resolve this.
Thanks in advance,
Hari.

Hi Hari,
In your case, check SAP Notes: 1082111 and 1060723.
Regards,
P.Rajesh

Error in Using the RPC WSDL based Business service

Hi,
I am using OSB 11g. I have created a business service with one of the WSDL which supports rpc/literal style. I am trying to call this business service using the service callout.
For the service callout if i use Configure SOAP Body option, i am getting the following error and unable to deploy to the server.
*'The Configuration does not correspond to a SOAP RPC WSDL.The WSDL of the target service may have changed.'*
But i am able to use the same option in sbconsole with out any problem. Is it an real issue with Eclipse IDE or a bug in the IDE? Please let me know if any insights into this issue.
Thanks
Siva

Siva,
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15867/monitoring_ops.htm#i1108369
Enable message trace for BS and see what the actual payload that is being sent. It would give you clear indication what might be the problem.
Thanks
Manoj

Problem with file adapter (FTP) created under business service

Hi
I am using file adapter in my receiver communication channel. I dont know the physical existance of the system so i have created one business service. Under this business system i have created a file adapter with FTP protocol. I have given all the parameters. But when i am trying to execute my scenarion i am getting the following error in SXMB_MONI.
com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_SQLMediaCodeToCRMCapaign_: RuntimeException in Message-Mapping transformatio~
In RWB i am getting the following error.
Mapping Error
Execption_During_Execution
In Communication Channel monitoring I am not getting any information regarding receiver file adapter. Its not showing any message either error or sucessful. How to find whether my receiver communication channel FTP parameters configured correctly or not.What is the error. Please help me.
Regards
Sowmya

Somya,
Error clearly indicates that issue is with mapping....so there is no point of checking receiver adapter..
BTW for checking whether the FTP site is working properly or not , you can use any ftp client softwares or command prompt of windows also.
---->In Communication Channel monitoring I am not getting any information regarding receiver file adapter. Its not showing any message either error or successful.
Message has not reached up to that level so no point of looking at receiver communication channel.
Regards,

Urgent:Assigning Payload to business service based on WSDL

Hi,
I have a business service, wrapped on a wsdl, whose message tag has multiple part tags of type string, now I am not sure as how to pass values to my business service as payload when I am trying to route to this business service, as there is no XSD to comply with, and since the wsdl is a client wsdl so I cannot change it.
regards,
rahul

Hi Anuj,
This is my wsdl, I have changes namespaces etc for security and compliance issues.
<?xml version="1.0"?>
<wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
     xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
     xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
     xmlns:tns="https://ws.local.co.in/soap/fix/1.3/" targetNamespace="https://ws.local.co.in/soap/fix/1.3/">
     <wsdl:types>
          <xsd:schema targetNamespace="https://ws.local.co.in/soap/fix/1.3/">
               <xsd:complexType name="vAuthHeader">
                    <xsd:all>
                         <xsd:element name="userName" type="xsd:string" />
                         <xsd:element name="password" type="xsd:string" />
                    </xsd:all>
               </xsd:complexType>
          </xsd:schema>
     </wsdl:types>
     <message name="AuthHeaderMessage">
          <part name="AuthHeader" type="tns:vAuthHeader" />
     </message>
     <message name="cancellationRequest">
          <part name="valuationMessage" type="xsd:string" />
          <part name="reason_id" type="xsd:int" />
          <part name="comments" type="xsd:string" />
     </message>
     <message name="cancellationRequestResponse">
          <part name="result" type="xsd:int" />
     </message>
     <wsdl:portType name="CheckThirdpartyPortType">
          <wsdl:operation name="cancellationRequest">
               <wsdl:input message="tns:cancellationRequest" />
               <wsdl:output message="tns:cancellationRequestResponse" />
          </wsdl:operation>
     </wsdl:portType>
     <binding name="CheckThirdpartyBinding" type="tns:CheckThirdpartyPortType">
          <soap:binding style="rpc"
               transport="http://schemas.xmlsoap.org/soap/http" />
          <wsdl:operation name="cancellationRequest">
               <soap:operation
                    soapAction="https://mythirdparty.local.co.in/soap/fix/1.3.1/index.php?n=localHunt&method=cancellationRequest"
                    style="rpc" />
               <wsdl:input>
                    <soap:header use="encoded"
                         namespace="https://ws.local.co.in/soap/fix/1.3/" message="tns:AuthHeaderMessage"
                         part="AuthHeader" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
                    <soap:body use="encoded" namespace="https://ws.local.co.in/soap/fix/1.3/"
                         encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
               </wsdl:input>
               <wsdl:output>
                    <soap:header use="encoded"
                         namespace="https://ws.local.co.in/soap/fix/1.3/" message="tns:AuthHeaderMessage"
                         part="AuthHeader" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
                    <soap:body use="encoded" namespace="https://ws.local.co.in/soap/fix/1.3/"
                         encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
               </wsdl:output>
          </wsdl:operation>
     </binding>
     <wsdl:service name="CheckThirdparty">
          <wsdl:port name="CheckThirdpartyPort" binding="tns:CheckThirdpartyBinding">
               <soap:address
                    location="https://mythirdparty.local.co.in/soap/fix/1.3.1/index.php?n=localHunt&handle" />
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>

Passing attachment from a SOAP Proxy to a REST Business Service

I am trying to create a SOAP proxy for a REST service on OSB 10g. I have to send a binary attachment as part of my SOAP request. I tried to use Service Callout to call my REST business service. Even though I receive the attachment as part of the request (I could log $attachments and see it), it is not being sent to the Business Service. I would appreciate any help. Thanks.
Ardi

OK, here is what I found out. I was using service callout to invoke the REST BS which does not seem to work, which I have not understood why?
If I change to Routing to the invoke the BS I could pass the attachment and get it to work. I would appreciate any thoughts on the Service Callout issue.
Thanks,
Ardi

"NO_RECEIVER_CASE_BE" error with SOAP Sender assigned to a Business Service

Similar Messages

Maybe you are looking for