SOAP Adapter doesn't find channel

Hi all,
I currently have XI 3.0 SP11 running and I'm trying to set up a simple <SOAP> -> <XI> -> <SOAP> scenario with it. Therefore I configured a Business Service called "WSClient" without associating it to a party. This service contains a Communication Channel called "SOAPClient" that is configured to use the SOAP Adapter and to act as a sender.
When i now try to send data to XI using a simple web service client i get the following error:
SystemError:
 <context>XIAdapter</context>
 <code>ModuleUnknownException</code>
 <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/aii/30_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#7 $)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:497)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at ...
</text>
Therefore I tried to use the HelperServlet to see if the channel is available. When invoking the HelperServlet with the parameters action=FindChannel&channel=:WSClient:SOAPClient
I get the following error:
<SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError>
 <context>XIAdapter</context>
 <code>ADAPTER.SOAP_EXCEPTION</code>
 <text>
java.lang.Exception: Channel not found for SOAPClient in http://sap.com/xi/XI/System^SOAP
 at com.sap.aii.af.mp.soap.web.HelperServlet.processFindChannel(HelperServlet.java:408)
 at
Somehow the Adapter Engine seems not to recognize the channel I have configured.
Any ideas how to solve this problem?
Thanks for your help.
Christian

Hi,
I have observed that when the SOAP sender channel is not activated, and a request is posted to XI, u will get "ModuleUnknownException".
When the Sender SOAP Adapter is created in BE mode and "no receiver determination" is created, you will encounter "DeliveryException" while testing using XMLSPY. U will find that the message has failed in XI with an error "NO_RECEIVER_CASE_BE"
When the Sender SOAP Adapter is created in EO/EOIO mode and "no receiver determination" is created, you will not encounter any error while testing using XMLSPY. But you will find that the message has failed in XI with an error "NO_RECEIVER_CASE_ASYNC"
Also make sure you defined the correct
"Default Interface NameSpace" and
"Default Interface Name"
in the Sender SOAP Channel. Else the message will fail b'cos it will not find the correct receiver Determination.
Cheers,
Siva Maranani

Similar Messages

SOAP Adapter sender/receiver commnunication channel?

Hello everybody,
I wonder how to configure the commnunication channel for the SOAP-Adapter. If XI triggers a webService (acts like a WebService client) then XI expects a response from the WebService. The first step seems to me as a receive-step. Then I wonder how XI gets the response?
Thanks a lot
Mario

hi,
>>>The first step seems to me as a receive-step.
why? it's a send step
if you want to do it in a sync way then
XI does not loose connection and it waits
for the response
if you want to understand little bit more
sync calls have a look at this weblog:
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
the rfc call is done in a sync way
the same can be done with SOAP
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

SFTP Seeburger adapter - Could not find channel for report handling between

Hello Friends ,
We have R3 -> PI-> SFTP scenario . The messages are transferred successfully and the file is successfully received at the receiving end . But when we do communication channel monitoring , we see errors in Receiver CC . The Reciever CC contains SFTP adapter (Seeburger) . Recently the Seeburger adapter is upgraded and the below error has started occuring then onwards .
Error Message which we see in CC monitoring for Receiver CC (SFTP) is as below .
Initiation of Transmission Report( job id: da405030-30c6-11df-8b6e-797b8921162c milestone: 290) failed! Exception occured: Error while preparing XI message. Error: Could not find channel for report handling between parties: fromParty, toParty: Itella) - com.seeburger.xi.connector.fw.ConfigurationException: Error while preparing XI message. Error: Could not find channel for report handling between parties: fromParty, toParty: Itella) [3/16/10 8:40 AM]
Could experts help me ...
Thanks for your time .
Regards,
Laxman Nayak .

Hi,
I also have the error you mentioned but we're implementing the Seeburger SFTP adapter for the first time.
I've requested transport acknowledgements in my ABAP proxy and have checked the 'Deliver transmission report' flag in the adapter but I don't know what else I must do.
Any help would be greatly appreciated.
Thanks,
Alan

Sender Soap Adapter communication channel error

Dear Experts,
When i see Sender soap adapter status in Communication channel monitoring.I am getting the status as:
"Processing Errors in the Last 50 Minutes"
Thanx in advance

Aamir,
My other interface is working fine by giving the following url:
http://kpmgvm015:8001/XISOAPAdapter/MessageServlet?channel=:KPMG_AU_ALL:RetrieveOpportunityRecord_SOAP_Sender
I am not using the propsed url.
Moreover when i try to give this url in the browser . It is asking of user id and password.
I am giving user as : PIAPPLUSER.It gives message servelet is ok.
In my communication channel monitoring the corresponsing communication channel:
RetrieveclientRecord_SOAP_Sender is in Red - Processing Errors In the Last 40 Minutes
Error meesage in Webclient:
java.security.AccessControlException: PIAPPLUSER has no permission for accessing binding com.sap.aii.af.service.cpa.Binding@d046043a

Commuication Channel monitoring for SOAP Adapter

Hi friends,
When i see Sender soap adapter status in Communication channel monitoring.I am getting the status as:
Channel started but Inactive
What does that indicate?
Kindly update what i need to do..

Check these links :
SOAP adapter - Channel started but inactive (case inside)
SOAP Adapter status stay "Channel started but inactive"
it ll be solved by given solutions in these thread like send messages,cache refresh..

Error in Receiver Soap Adapter for Google API

Hi,
I am working on HTTP-XI-Soap scenario which on the receiver side calls google API for spell check.
I get the following error : No Deserializer found to deserialize a ':key' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.
However if I try calling the webservice individually using SOAP Client it works fine and do get desired response.The soap message that is sent by the client to the target URL is :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:GoogleSearch" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
 <urn:doSpellingSuggestion soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
 <key xsi:type="xsd:string">qXWD4x1QFHIo/dePqlYOLwT7kMmkv80E</key>
 <phrase xsi:type="xsd:string">Bratney</phrase>
 </urn:doSpellingSuggestion>
 </soapenv:Body>
</soapenv:Envelope>
However if i remove the "xsi:type="xsd:string" part from the element 'phrase' and 'key' it returns the same error as it does while using with XI.
Hence I am assuming that that the outgoing soap message elements need to have the above highlighed attribute.
Now I want to have this attribute(xsi:type="xsd:string) in the soap message that is sent from XI.
My question is , Is there any setting using which I can add the attributes in the above form to the outgoing message from XI.I do not want to use a adapter Module.
Thanks & Regards,
Sidharth

Hi Sidharth,
You post here the soap message that is sent by the client to the target URL, but did you look to the soap message that is sent by XI?
Try the AF monitor http://<host>:<j2ee-port>//MessagingSystem/monitor/monitor.jsp?
Because XI soap adapter doesn't support all tags of wsdl rpc-based, we need to adjust them...
Look to the SOAP FAQ (SAP note number 856597) under question "Can I convert an RPC styled WSDL to a document styled WSDL?"... Look at last but one paragraph ;o)
So, you need to change this attribute to one that it is compatible...
Go to http://service.sap.com/xi > Media Library > Documentation and there you will find this xls document -> SAP XI 3.0 (SP11) - Supported XML Schema and WSDL (EN) in this document you have all the compatible elements of wsdl for XI.
One more thing, you can adjust your soap request and change or add the required tags You can do it with xslt-mapping or create your won data types in XI without import the WSDL generated by google.
Hope it helps,
Ricardo.
Message was edited by: Ricardo Quintino

Sender SOAP adapter: get soap header data

Hi,
I've been going through various posts and blogs here on SDN + looked in the how to guide for SOAP adapter, but still find it quite difficult to actually find out how to do it. I've tried to follow recommendations seen, but it doesn't add up.
So can someone please tell me how to get an element situated in the SOAP header of the request sent to XI via sender soap adapter?
Let's for instance say the request looks like this:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <SOAP-ENV:Header>
 <SSN>1234567890</SSN>
 </SOAP-ENV:Header>
 <SOAP-ENV:Body>
 <event>
 <elem1>data 1</elem1>
 <elem2>data 2</elem2>
 <elem3>data 3</elem3>
 </event>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
How can I get the data in the SSN-header element at mapping time?
I'm sure this can be done by using adapter modules as the first step adapter, but I prefer doing it at mapping time if possible.
Best Regards,
Daniel

I solved it on my own now. My missing link was the fact that I'm using XMLSPY to send request and thus need to replace all '&' with & in Connection Endpoint.
Message was edited by:
 Daniel Engsig-Karup

SOAP adapter and WS with rpc/encoded

Hi All,
Does anyone know if and how the SAP XI 3.0 SOAP Adapter supports WebServices which expects XML messages in rpc/encoded.
Cheers,
FRank

Hi Frank,
I have the same issue and I got a reply from OSS:
This problem is caused by the diversification of the WSDL binding
styles.
A Web service is described by a WSDL document. A WSDL binding
describes how the service is bound to a messaging protocol, particularly
the SOAP messaging protocol. A WSDL SOAP binding can be either an RPC
style binding or a document style binding. A SOAP binding can also have
an encoded use or a literal use. This gives us four style/use models:
- RPC/encoded
- RPC/literal
- document/encoded(It will probably disappear from future versions of
WSDL.)
- document/literal
RPC styled web services have serious interoperability problems. This
is the reason that the rpc style is not in the basic profile
specification of the web interoperability and also it has been
deprecated in the current soap specification. For these reason, the
integration directory does not currently support the RPC style! I would
suggest you to use other document style web service provider if possible
. It's the best way to solve this problem. But if you persist in using
this RPC web service provider, we still have a workaround solution:
you need to convert your RPC wsdl to a document styled wsdl and import
it to the directory and if necessary, you need to add some mapping to
solve some RPC interoperability problems.
In your case,
1. The WSDL file you used is RPC style.
2. The XI SOAP adapter doesn't support the RPC style. It only sends the
document/literal SOAP message which can't be understand by your web
service provider.
One of the significant differences between the SOAP message of RPC
style and that of the document style: the operation name is contained in
the RPC style SOAP message but not in the document's.
However, you can't solve this problem by simply specify a method
name. What you should do is convert your RPC wsdl to a document styled
wsdl. RPC turns out to be a subset of document/literal. This
means for any given RPC WSDL, you can create a completely
equivalent document/literal WSDL that would describe the same wire
messages. Here are the steps for doing this (mostly schema element
declarations).
Solution:
For each RPC operation:
1. For each part in the input and output messages of that operation,
declare a type with the contents described in step 2.
2. Declare an element with the name of the part, the type referenced by
type=". The element form must be unqualified.
3. Declare a global element with the operation name and the namespace
from soap:body/@namespace in the binding. Make the type of this element
the one defined in step 1 for the input message.
4. Declare a global element with the operation name and the word
Response appended to it and the namespace from soap:body/@namespace in
the binding. Make the type of this element the one defined in step 1 for
the output message.
5. Change the input message to contain one part and reference the
element you declared in step 3.
6. Change the output message to contain one part and reference the
element you declared in step 4.
7. Change the style to document in the binding.
After that, import the new WSDL file to the integration directory. You
will find the "method name" appears in the document style SOAP message.
But actually it's the name of the input element which is the same as
the name of the operation. It's just a little trick.
Cheers Stefan

HTTP error in SOAP Adapter

Hello Everybody,
I have a SOAP adapter with several communication channels configured.
When i want to test these scenarios, i obtain this error:
com.sap.aii.messaging.net.TransportException: HTTP 401 Unauthorized
 at com.sap.aii.messaging.net.ClientHttpImpl.call(ClientHttpImpl.java:180)
 at com.sap.aii.messaging.adapter.WSTestClient.doPost(WSTestClient.java:241)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.aii.messaging.adapter.Zone.service(ModuleGUIBrowserEngine.java:1072)
 at com.sap.aii.messaging.adapter.HTTPRequest.run(ModuleGUIBrowserEngine.java:370)
What could be happening? Is something about permissions in SOAP? in this case what are the SOAP commands to specify this parameters?
Thakns a LOT!!
Regards,
Javier Sahagun

Hi agasthuri
I readed https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4061. [original link is broken] [original link is broken] [original link is broken] [original link is broken]
I restarted the service in SICF transaction, etc, etc, etc.....
now I execute and I receive
java.lang.NullPointerException
 at com.sap.aii.messaging.net.EndpointImpl.parseURI(EndpointImpl.java:303)
 at com.sap.aii.messaging.net.EndpointImpl.<init>(EndpointImpl.java:59)
 at com.sap.aii.messaging.net.EndpointHTTPImpl.<init>(EndpointHTTPImpl.java:33)
 at com.sap.aii.messaging.net.FactoryImpl.createEndpoint(FactoryImpl.java:116)
 at com.sap.aii.messaging.adapter.XMBTestClient.doPost(XMBTestClient.java:223)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.aii.messaging.adapter.Zone.service(ModuleGUIBrowserEngine.java:1072)
 at com.sap.aii.messaging.adapter.HTTPRequest.run(ModuleGUIBrowserEngine.java:370)

SOAP Adapter Polling.

Hi,
We have a scenario where I need to poll a website using a SOAP call every 15/30 mins. Since the SOAP adapter doesn't support polling what are my options.
Note:
a. The SOAP request is in a BPM.
b. Its a R/3 <-> XI <-> Website scenario
c. Current plan is to use idocs/rfc from R/3 as triggers to poll the website.
Regards,
Harsh

Hi,
>>>>a. The SOAP request is in a BPM.
this way you need to start the BPM first
so it's the same as c.
>>>>b. Its a R/3 <-> XI <-> Website scenario
yes you can use IDOCs, abap porxies or RFC
it's the same as c.
you mention only one option and it's a good one
as you will have a nice SAP scheduler
(you can schedule a report that will do the RFC call to XI)
Regards,
michal

Unable to find channel ID at inbound SOAP Adapter

Hi experts,
I encountered a very puzzling problem:
I have a scenario:
IDOC -> XI -> SOAP
For 2 interfaces of such nature, 1 works fine, 1 doesn't.
The one that does not work is throwing the following error in RWB - Message Display Tool (MDT):
2007-03-22 10:57:05 Success The message was successfully received by the messaging system. Profile: XI URL: http://ootspdbs02:50100/MessagingSystem/receive/AFW/XI
2007-03-22 10:57:05 Success Using connection AFW. Trying to put the message into the receive queue.
2007-03-22 10:57:06 Success Message successfully put into the queue.
2007-03-22 10:57:06 Success The message was successfully retrieved from the receive queue.
2007-03-22 10:57:06 Success The message status set to DLNG.
2007-03-22 10:57:06 Error Unable to find channel ID
2007-03-22 10:57:06 Error Delivery of the message to the application using connection AFW failed, due to: Couldn't find delivery channel for message: a277e57c-c837-e44f-9ae2-da0d701980c4. 
2007-03-22 10:57:06 Success The asynchronous message was successfully scheduled to be delivered at Thu Mar 22 10:58:06 SGT 2007.
2007-03-22 10:57:06 Success The message status set to WAIT.
In SXMB_MONI, it shows the message has been processed successfully - indicating that the mapping is fine. Status = Awaiting acknowledgement.
I've looked up the forums, and the general solution offered is to refresh the SLD cache.
I've tried that, but it doesn't work.
Please help.
Thanks.
Ron

> hmm.. then things not a problem with the cache.
> Is the error in MONI? Or is it in the Adapter Engine?
>
>
> I know it isrepeatitive, but checking if the Objects
> are all active and correct in the ID is the only
> solution I can suggest.
>
> Regards
> Bhavesh
In the MONI, the status is successful, awaiting acknowledgement.
After sometime, the ack status will be "Acknowledgement contains System Errors"
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_ROUTING_BACK_ERROR</SAP:Code>
<SAP:P1>,BS_DEV1_NAUTICUS_OOTS</SAP:P1>
<SAP:P2>,BS_NHGDDBS01,,</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error occurred during back-routing Error in communication channel</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
But I don't think these are related, because the message wasn't sent out, naturally there's an error in the ack.

SOAP ACTION IN SOAP ADAPTER and PROGRAM IF IN RFC COMMUNICATION CHANNEL

Hi Gurus,
Please Explain me what is SOAP action in soap adapter what is the use of it.
What is the Program ID in the RFC communication channel and what is the use of it.
Please tell me in Detail.
Thanks and Regards,
RAM.

Hi,
Please Explain me what is SOAP action in soap adapter what is the use of it.
As of W3C definition:
The SOAPAction HTTP request header field can be used to indicate the intent of the SOAP HTTP request. The value is a URI identifying the intent. SOAP places no restrictions on the format or specificity of the URI or that it is resolvable. An HTTP client MUST use this header field when issuing a SOAP HTTP Request.
The presence and content of the SOAPAction header field can be used by servers such as firewalls to appropriately filter SOAP request messages in HTTP. The header field value of empty string ("") means that the intent of the SOAP message is provided by the HTTP Request-URI. No value means that there is no indication of the intent of the message.
Putting things simple, this is an identifier of an operation that you want to execute in the web service (as one web service can offer multiple actions).
What is the Program ID in the RFC communication channel and what is the use of it.
Again, this is an identifier for both: RFC sender and receiver systems. It tells the receiver where to listen for connections, and the sender - where to send the data. It works a little bit like a port number in HTTP communication, but with less restrictions.
Hope this helps,
Greg

Need help in troubleshooting communication channel using soap adapter

Hello friends
I have a simple scenario.
I have created 2 communication channels, one for searching a record and another for updating it with a new value
Both uses SOAP as sender and RFC as receiver with a Standard BAPI.
Everything was working ok, but without any changes, all of a suddent I am not being able to update the values and when I checked RWB, I see for Update SOAP Adapter Channel, the messages say
Request received for a channel
but in a second it says 'Call Failed'.
I haven't made any changes.
I even tried restarting XI and ERP servers but still getting the same error.
Any suggestions or feedback will be greatly appreciated.
Thanks
Ram

THE PROBLEM WAS WITH A JOB GETTING HUNG IN THE QUEUE AND I HAD TO FORCIBLY KILL THAT. THAT TOOK CARE OF THE PROBLEM

Soap adapter communication channel problem

Hi...
While doing Webservices to file scenario, in component monitoring, the soap adapter communication channel is showing as (in small traiangle inyellow color) channel started but inactive

Hi leelaratnam,
Please check that you have only 1 communication channel active and running.
This happens when more than 1 CC is pointing or waiting for the same incoming data.
Also perform a dummy activate (i.e. write somthing in description and activate) in your message mapping and communication channel objects in case you are using PI 7.0
Thanks,
Varun

SOAP : No adapter registered for this channel

hello everybody,
i'm working with a PI 7.1
i have a interface RFC - PI - SOAP.
when i look on Communication Channel Monitor i see this error on my soap CC
No adapter registered for this channel
i restart J2ee and applicate CPA cache refresh.
i tryed to create a new soap cc but no result. still to have this problem.
Any suggestion?
thanks
Alex

HI Alex,
Edit the channel and do some dummy changes and activate again. also go to ID -> Menu Environment -> Clear SLD Data Cache. Also check the cache notifications.
Then perform CPACache refresh using PIDIRUSER and this url.
http://XIHost:JavaPort/CPACache/refresh?mode=delta
http://XIHost:JavaPort/CPACache/refresh?mode=full
If this does not work then you may check Visual Admin -> Soap Adapter service and restart it....
Thanks,
Naveen

SOAP Adapter doesn't find channel

Similar Messages

Maybe you are looking for