Error in configuring soap adapter

Hai!
Iam working with rfc to webservice scenario.
In that while configuring the soap adapter, the following errors have occured.
SOAP: failed to sign the message due to java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: AccessControlException in Method: apply( Message, CPALookupObject ). The Code-Permission processing failed.
SOAP: error occured: com.sap.aii.messaging.srt.BubbleException: WS-Security privileged action exception [null "null"]; nested exception caused by: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: AccessControlException in Method: apply( Message, CPALookupObject ). The Code-Permission processing failed.
Please! help me in sorting it out.
Regards,
Saritha.

try this link
check with all settings
http://www.****************/Tutorials/XI/RFCtoSOAP/page1.htm

Similar Messages

Error while configuring B2B adapter in Jdev 11.1.1.6

Hi All,
While configuring B2B adapter in jdev 11.1.1.6, i'm getting the following error at the Document definition step,
Unable to connect to URL: https://ip address:port no/integration/services/b2b/B2BMetadataWSPort due to javax.xml.soap.SOAPException: Message send failed: sun.security.validator.ValidatorException: Violated path length constraints
please let me know if anyone of you faced this issue and has a resolution. We have SSL configured and using Rosettanet protocol.
Thanks,
Terry

Terry,
It seems like a SSL issue related to the certificate. Can you make sure that certificate being presented by the server (hosting URL https://ip address:port no/integration/services/b2b/B2BMetadataWSPort) is valid and you have complete cert chain in the keystore of SOA server?
Regards,
Anuj

Error in Sender SOAP Adapter on XI 3.0 SP13

Hi All.
I have an application that sends a SOAP message to XI SOAP Adapter, to reach a synchronous interface. I've generated the .wsdl file from the Integration Directory, within the URL:
http://sapbox:59800/XISOAPAdapter/MessageServlet?channel=:BS_PORTAL:CC_S_SOAP_CREDITO
When I try to reach this URL, I get the successful response:
Message Servlet is in Status OK
I've also created the sender SOAP communication channel, fullfilling the default namespace and default interface correctly.
However, when I use wsnavigator client provided by SAP to prove the scenario, the SOAP message doesn't achieve XI, as the XISOAPAdapter EJB throws some exceptions:
HTTP/1.1 500 Internal Server Error
Connection: close
Server: SAP J2EE Engine/6.40
Content-Type: text/xml; charset=utf-8
Date: Sat, 17 Sep 2005 02:59:12 GMT
<?xml version='1.0'?>

<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>BaseEJBException</code>
 <text><![CDATA[
com.sap.aii.af.mp.processor.ModuleProcessorException
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:278)
 at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
 at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:162)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:508)
 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:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 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:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method process.
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:121)
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
 ... 19 more
Caused by: java.lang.NoSuchMethodError: com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.setDynamicConfigurationMode(I)V
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.createXMBWSBubble(XISOAPAdapterBean.java:1129)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:265)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:562)
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
 ... 20 more
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
I've already done something really similar on SP 9. Can it be a new problem from SP13? Does anyone has any idea?
Thanks in advance.
Deise Lima.

Hi Naveen,
I have configured a SOAP sender adapter in XI 3.0 and is using the URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
Message Servlet is in Status ERROR
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal not instantiated
ModuleProcessorRemote not instantiated
But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
<?xml version="1.0" ?>
http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
<name>CC_WEBSERVICE_SOAP</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>BS_WEBSERVICE</service>
</s:ChannelInfo
I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy or Altova XML Spy we are getting a 500 internal server error.
Am not sure what causes the error

Error in receiver SOAP adapter.

Hi Experts,
scenario name is proxy to soap asynchronous interface
we are getting the below error from the soap receiver communication channel.
-exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException
-Adapter Framework caught exception: null
-Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException
please help us.
regards
elton

can you confirm if you have configured the adapter correctly? Troubleshooting - RFC and SOAP scenarios *** Updated on 20/04/2009 ***
Also it will be a good idea to check with your end application and confirm if they have received the message and if it is a fault message being triggered from their end (potentially data issues) that is showing up as an error in the adapter

Error in AXIS SOAP Adapter

Hi Experts,
Cuurently i am working on Synchronous scenario.
My scenario is ABAP Client Proxy> PI>AXIS SOAP ADAPTER(Webservice).
My client requirement is to use UsernameToken security with PasswordDigest.
I have deployed all the relevant .jar files and add the modules related to usernameToken security as per *SAP Note 1039369 FAQ XI Axis Adapter* in Receiver SOAP adapter.
Now when i am pushing the data from R/3 to PI, data is successfully coming to PI however when the data is going outside PI through Receiver AXIS SOAP Adapter in RWB is showing
*The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System*
*The message status set to DLVD*.
Moreover when i am checking the message through SXMB_MONI i cant see the chequred flag for Request message and for response message its giving the following
<?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="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="SOAP">FAULT</SAP:Code>
<SAP:P1>http://schemas.xmlsoap.org/soap/envelope/</SAP:P1>
<SAP:P2>Server.generalException</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>WSDoAllReceiver: security processing failed (actions number mismatch)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
and when i am cheking the trace of Respose message (request for message mapping ) its giving the
<Trace level="1" type="T">Message has no payload</Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_UrlResponse_To_CourseAccessUrlResponse_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Parsing an empty source. Root element expected! at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151).....
Currently SSL is not installed in my PI server.For temperory i am using HTTP instead of HTTPS.
Please provide your valuable inputs on this.
Regards
Anku chopra
Edited by: AnkuChopra on Aug 28, 2009 1:59 PM

Hi Experts,
In my Receiver SOAP adapter module Tab.
As my scenario is synchronous and i required UsernameToken with PasswordDigest security i have added following parameter value in module.(as per SAP Note 1039369 FAQ XI Axis Adapter ).
Processing Sequence.
Module Key
afreq
xireq
wssec
trp
xires
afres
Module configuration
ModuleKey ParameterName parametervalue
xireq handler.type java:com.sap.aii.axis.xi.XI30OutboundHandler
wssec action UsernameToken
wssec handler.type java:com.sap.aii.adapter.axis.ra.handlers.security.WSDoAllSender
wssec passwordType PasswordDigest
wssec pwd.password ********************
wssec user XYZ
trp handler.type java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
trp module.pivot true
xires handler.type java:com.sap.aii.axis.xi.XI30OutboundHandler.
Do we need to do any other configuartion apart from above in parameter value.
While getting response from third party i getting error as WSDoAllReceiver: security processing failed (actions number mismatch)
Do i need to add parameter value for WSDoAllReceiver as well as my scenario is synchronous.
Please help me out on this as i am not able to proceeed further because of the above errro.
Please advice.
regards
Anku Chopra

Error in Receiver SOAP adapter - but ok in sxmb_moni

HI,
i am trying to call a WS wich takes only input. so it is a asynchronous call.
I configured CRM-XI-WS.
My sxmb_moni is ok in XI. But when i check Adapter monitoring it is throwing the following error... any help please..
2008-01-03 16:55:53 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 179). ---> The specified node cannot be inserted as the valid child of this node, because the specified node is the wrong type.
2008-01-03 16:55:53 Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 179). ---> The specified node cannot be inserted as the valid child of this node, because the specified node is the wrong type.
2008-01-03 16:55:53 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 179). ---> The specified node cannot be inserted as the valid child of this node, because the specified node is the wrong type..
2008-01-03 16:55:53 Success The asynchronous message was successfully scheduled to be delivered at Thu Jan 03 17:00:53 CST 2008.

I changed my structure to a smiple structure... still i am getting the error...
even i tried taking the payload from sxmb_moni and tested the mapping in IR .. it is failing... saying: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
my payload is :
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:HSBP_Out_MT xmlns:ns0="http://tsfco:A_TSFCO_CRM_WS_COMM_SWC:CD:HsBpFromCrm">
<Name>test</Name>
</ns0:HSBP_Out_MT>
Edited by: ashok sri on Jan 4, 2008 1:14 AM

EJB Errors When Calling SOAP Adapter

Scenario We are using XML Spy to call a Message Interface exposed through a SOAP Communications Channel. That is, an outbound adapter. We are running XI Version 3.0, SP9 with patches.
The location is our URL is
<soap:address location="http://sapxidev:50000/XISOAPAdapter/MessageServlet?channel=:Taxpayer:Sender_SOAP&version=3.0&Sender.Service=Taxpayer&Interface=urn%3Ador.state.fl.us%5ESUTARC_Verification_Sync_Out_MI" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
The respone is com.sap.aii.af.mp.module.ModuleException
The server logs indicate three relevant error messages:
Message 1
Failed to set up the adapter for channel c67c0ccb7f583d7693678bb1288644ff;
caused by java.lang.Exception: Bubble configuration error: parameter 'XI.InterfaceNamespace' is missing
Message 2
the required parameter XI.InterfaceNamespace is missing
Message 3
Path to object does not exist at localejbs, the whole lookup name is ejbContexts/sap.com/com.sap.aii.af.app/ModuleProcessorBean/localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean.
Any ideas?
Thanks in advance!

HI Paul,
did you put a default namespace and interface name in the SOAP Adapter config of the communication channel in the IB?
It is under the Default XI Parameter in the SOAP Adapter.
That should solve this problem, don´t ask me why it says Default if is is mandatory.
Cheers
Stefan

Configure Soap Adapter for compress, gzip.

HI to all experts,
do anyone know how can configure a soap adapter with the parameter for compress, gzip.
i found a document which explain so:
localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
XMBWS.XMLEncoding Content-Type charset iso-8859-1
XMBWS.TransferEncoding Content-Transfer-Encoding base64
XMBWS.Encoding Content-Encoding gzip
XMBWS.AcceptEncoding Accept-Encoding compress, gzip
but i f i insert this parameter the adapter give me back a response :
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Could not access envelope: Unable to create envelope from given source: ; nested exception is com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Unable to create envelope from given source:.
seems that it have any difficult to read the payload.
let me know if anyone have an idea.
best Regards
Claudio.

Hi Stefan,
is it enough this response?
POST HTTP/1.0
Accept: /
Accept-Encoding: compress, gzip
Host: 10.180.160.29:8080
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
Content-ID: <[email protected]>
Content-Disposition: attachment;filename="[email protected]"
Content-Type: text/xml; charset=iso-8859-1
Content-Description: SOAP
Content-Transfer-Encoding: base64
Content-Encoding: gzip
Content-Length: 1292
SOAPACTION:
X-XMB_WS_ENCODED: version=3.0&MessageClass=ApplicationMessage&ProcessingMode=asynchronous&MessageId=478ce922-7b48-04b0-0200-00000ab44471&TimeSent=2008-01-16T13%3A36%3A45Z&Sender.Party=%3A%3A&Sender.Service=BS_SAP_TC3_700&Receiver.Party=%3A%3A&Receiver.Service=BS_IRIS_TXI&Interface=http%3A%2F%2Fgenerali.it%2Fmerge%2FUTILITY%2F01%2Firis%5EMI_COMPAGNIE_RES&QualityOfService=ExactlyOnce
i get it by TCPGatway.
thanks a lot.
Claudio.

Error while Testing SOAP Adapter In XI

Hi Frndz
I am trying to test my SOAP adapter which i have exposed as a webservice. I testing this from the WSNavigator which throws the following error:
HTTP/1.1 500 Internal Server Error
Connection: close
Set-Cookie: <value is hidden>
Set-Cookie: <value is hidden>
Server: SAP J2EE Engine/6.40
Content-Type: text/xml; charset=utf-8
Date: Thu, 15 Dec 2005 12:24:19 GMT
<?xml version='1.0'?>

<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>DeliveryException</code>
 <text><![CDATA[
com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 404 : Not Found
 at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:144)
 at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:512)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:141)
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
I have used this url for the Webservice:
http://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:CVXSABSR_TEST_SENDER:CVXSACC_TEST_SENDER
I am unable to figure out where the problem is.
Any ideas to solve this?
Thanks in Advance
DhanyaR Nair

Hi Andrews and Ravi
Thanks for the quick response.
Andrews the Message Servlet is in OK status, as it reponded from checking the url given by you.
What should i try next?
Ravi i checked the url for checking the Comm Channel. There are two IDs associated with the Channel
1>Object ID
2> ObjectVersion ID
with the ObjectVersionID , we are getting the following error and with ObjectID we got the proper response 
with ObjectVersion ID
http://<host>:<port>//XISOAPAdapter/HelperServlet?action=GetChannelInfo&channelID=<Object version ID>
response:
<?xml version="1.0" ?>
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<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.SOAP_EXCEPTION</code>
- <text>
- <![CDATA[
com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Channel object with Id Channel:a9f7f390671e11daa2300012799e22c2 not available in CPA Cache.
 at com.sap.aii.af.service.cpa.LookupManager.getCPAObject(LookupManager.java:202)
 at com.sap.aii.af.mp.soap.web.HelperServlet.processGetChannelInfo(HelperServlet.java:455)
 at com.sap.aii.af.mp.soap.web.HelperServlet.doGet(HelperServlet.java:131)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 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:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
 ]]>
</text>
</s:SystemError>
</detail>
</SOAP:Fault>
with the object id
http://<host>:<port>/XISOAPAdapter/HelperServlet?action=GetChannelInfo&channelID=<Object ID>
Response
<?xml version="1.0" ?>
- <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>ea30ed2ccc243fe49b7c2c5646ed3b2d</channelID>
<name>CVXSACC_TEST_SENDER</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>CVXSABSR_TEST_SENDER</service>
</s:ChannelInfo>
with the url
http://<host>:<port>/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:CVXSABSR_TEST_SENDER:CVXSACC_TEST_SENDER
Response
<?xml version="1.0" ?>
- <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>ea30ed2ccc243fe49b7c2c5646ed3b2d</channelID>
<name>CVXSACC_TEST_SENDER</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>CVXSABSR_TEST_SENDER</service>
</s:ChannelInfo>
How should i proceed ? Any idea frndz
Thanks in Advance
DhanyaR Nair

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

Error in configuring Mail Adapter

Hello Friends,
I am working in XI 2.0
I am trying to configure the Outbound file adapter for sending the Mail.
and i configure my adapter as
File adapter java class
classname=com.sap.aii.messaging.adapter.ModuleXMB2File
mode=XMB2FILE
##Adress for XMB endpoint
XMB.httpPort=8220
XMB.httpService=/mailSender
##File Adapter specific parameters
file.createDir=1
file.targetDir=e:/oraclejdbc/mail
file.targetFilename=mail.txt
#file.writeMode=append
file.writeMode=overwrite
uncomment and adjust parameters for using a dispatcher ***
Dispatcher.class=com.sap.aii.messaging.adapter.ConversionDispatcher
Dispatcher.namespace=namespace1
namespace1.ConversionDispatcher.logPayload=true
##namespace1.MailClient.contentType=text/html
namespace1.Service.1=MailClient
namespace1.MailClient.class=MailSender
namespace1.MailClient.smtpHost=POWAI
namespace1.MailClient.smtpPort=25
namespace1.MailClient.from=[email protected]
namespace1.MailClient.to=[email protected]
namespace1.MailClient.subject=NewXI Message
namespace1.MailClient.contentType=text/html
And when I am trying to start the adapter engine it gives me error as
Tue Nov 23 10:46:47 IST 2004 *****
10:46:47 (4115): File adapter listener initialized successfully
10:46:47 (8200): Conversion dispatcher 2.0.0904 initializing
10:46:47 (4024): Attempt to initialize file adapter failed with
java.lang.NullPointerException
10:46:47 : Error(s) in adapter configuration parameters found:
10:46:47 (4108): Unable to start file adapter (not initialized)
If any one know please help me to solve this problem.
Thanks & Regards,
Gaurav Jain

Could you check, if the file Mail.jar is installed correctly in your Adapter Framework folder and the starting program of the Adapter Framework (e.g. runadapter.bat or install_service.bat) is enhanced with this library file?
Regards
Stefan

Error using Sender SOAP adapter over HTTPS

Hi experts,
Few weeks ago, i developed an interface as follows: SOAP <-> XI <-> RFC.
I tested the functionality using Altova and everything went well, with HTTP.
However, when i use HTTPS it fails throwing these error messages (pop ups):
"HTTP error: could not post file"......
"Error sending the soap data"
I have reviewed the SSL certificates installation and everything seems to be ok, but currently i am stuck and do not know how to fix this.
I have also change the ID comm channel from HTTP to HTTPS with client aut.
Is there any special service i have to activate? (XI services and SPIGATE are already done)
Could you please assist?
Thanks in advance and best regards,
David

David,
have a look @ these threads...u may get some help!!!
Sender Soap with HTTPS
https Soap Adapter
Regards
Biplab

Error while using soap adapter in webservice to sap system scenario

Hi everybody,
i got the error while using saop adapter in scenario(sender webservice----->sap system)
error is
HTTP error:couldnot post file
'/XISOAPAdapter/MessageServlet:Channel=:BS1:SPA.&
version+3.0&sender.Service=BS1&interface=http%3ASP%5OUTBOUND'on server 'XI03'(500)

check with ur basis people

Time out error in receiver soap adapter

Hi,
My scenario is file to soap file with out BPM.I am using a currency converter wsdl.
I am getting a time out error in soap receiver channel.
Do i need to change the time out parameter?Where do i change that?Please help me to solve it out.
Following are the errors in the soap communication channel.
SOAP: call failed: java.net.ConnectException: Connection timed out
SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: java.net.ConnectException: Connection timed out
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: java.net.ConnectException: Connection timed out
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: Connection timed out: java.net.ConnectException: Connection timed out. Setting message to status failed.
Regards
Divia

Hi Prateek,
Thanks for your replay. I am able to open the URL from XI/PI.
I tried by testing the same URL by using XI 3.0, its working fine and i am getting required data, but in PI 7.1 i am getting an error.
Error is:
In MONI:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection refused: connect
In RWB:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect
What could be the reason?
Regards,
Venu

Invalid Content Type Error in Receiver SOAP Adapter

Hello Experts,
Is there a solution for this problem?
I am getting the following error in one of my receiver SOAP adapters:
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:...:com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML
I have checked the message I am sending to the receiver adapter and it is XML, ok. After checking this thread: Re: Error in soap receiver adapter and SAP note 856597 I used the TCPGateway program to check what the web service is answering to the adapter request and I found the problem is due to an authentication failure. The TEXT/HTML is an error page the SAP WebAS that hosts the webservice is sending out as response saying no login method succeeded.
However... The webservice URL and basic authentication information, the user and password, are configured correctly. I double checked it and I can also run the webservice using that information directly with wsnavigator on that WebAS.
Checking the request message I found out that the root problem is that the adapter is not sending out a basic authentication request as configured. It is actually sending a header with SAP SSO2 (single signon) ticket instead.
The most strange thing is that I configured another channel exactly the same way and it sends a basic authentication header as it should and works correctly.
So as a workaround I am using this new channel instead of the problematic one but why is the original sending SSO2 tickets? It is configured exactly the same as other channels. I think that SAP SSO authentication is not even supported by XI SOAP channels!!!???
Thanks in advance for your kind responses.
-Sam.

Shabarish:
Thanks for the link, but the real issue is not the request message (regarding your blog) but that the reply from the webservice is the standard HTML page informing no login module succeeded because the adapter is deciding completely on its own that it should use SAP single signon ticket instead of basic authentication as configured.
Volker:
I have performed full and delta cache refreshes to see if the channel performs as configured in the ID but it doesn't. It insists in trying to use SSO2 ticket instead of basic authentication.
I am sure this is an ugly bug in the WEBAS Java, more so because an identically configured channel does use the basic authentication as it should. Anyone knows about a SAP note regarding this? I have performed many searches on the support service but haven't retrieved anything significant.
Thanks for your help guys!
-Sam.

Error in configuring soap adapter

Similar Messages

Maybe you are looking for