Error while posting messages to SOAP sender adapter SP 13

Hi Friends,
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_EBTR_WEBSERVICE:CC_EBTR_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 we are getting a 500 internal server error.
Am not sure what causes the error ? I saw two notes in SDN related to SOAP - J2EE SP13. We are in SP13. Is this the issue ? Wanted to know your opinion before applying the notes.
Thanks & Regards,
Mathew

ABAP & Java stack was on different SP levels.

Similar Messages

Facing Intermittent Error while posting Messages to Queue

HI ,
I am working on a WLI Project which involves the Message Queue, Topic, Message Brokers, JMS Event Generators.
To test the Application,
I have a test page from where I pump in the Messages to the Channel. The messages are being read and the JPD that has subscribed to the Message Broker is getting invoked and is able to Post a response Message to a Queue which is created.
The Message is getting Posted to the Queue properly For some time until I run a single Test at a time
Once I try to do simultaneous test for the Test page I see that the Message is not getting posted to the Queue. And I get a error Message on the Server Console as:
<Error> <WLW> <000000> <Received message without correlationID. MessageID=ID:P<106224.1170871006171.0>>
I am not getting any kind of solution in any forum on how to fix this Issue. and also not sure where exactly is it going wrong.
I am using Weblogic 8.1 SP4 on Windows. Application is deployed on Integration Domain.
Waiting for some solution.
Thanks in Advance!!

Thanks Denis for your Reply.
I was looking in the Bea Docs and it states that we need to set the CorrelationID to the conversationID of the listening Service. So I am not getting how to get the ConversationID of another Service(listening Service) which is trying to read this message from the Queue.
I also tried to set the correlationID to conversationID of the same JPD from which I am sending the message to the Queue. But still I see the same error message .
Also the conversationID for the JPD is null.
I am trying to do as below:
Map jmsHeaders = new HashMap();
String cid=null;
cid = context.getService().getConversationID();
jmsHeaders.put("JMSCorrelationID", cid);
QueueCtrl.setHeaders(jmsHeaders);
QueueCtrl.sendTextMessage(this.mpiMessageDoc);
When I run multiple instance of the JPD which r trying to post to the same Queue simultaneously I get the same error:
<Error> <WLW> <000000> <Received message without correlationID. MessageID=ID:P<106224.1170871006171.0>>
Can any body comment on this Issue?
Thanks in Advance

SOAP Sender Adapter gets error '(401) Unauthorized.'

Hi all,
we are using XI 3.0 and have a scenario with a SOAP Sender Adapter, which is using "HTTPS with Client Authentication". I have configured everything I have found on the forum at Visual Admin and Integration Directory:
Set the UME property ume.logon.allow_cert to TRUE in 'Service-->UME Provider'
Imported client certificate and root CA certificate to 'Service-->Keystore'
Created user with role role SAP_XI_APPL_SERV_USER
Assigned this user to the client certificate in 'Security Provider-->UserManagement'
Added the user to xi_adapter_soap_message and xi_adapter_soap_help in 'Security Provider'
Added the root CA in 'SSL Provider>Dispatcher>Client Authentication' and marked 'Request client certificate.
Added the user to BusinessSystem at tab 'Assigned Users'
Added the user to Sender Agreement at tab 'Assigned Users'.
Our business partner got a certificate of our server and the according PrivateKey is added to 'SSL Provider>Dispatcher>Server Identity'
Unfortunately, our server certificate is not verified by an root CA!!
When the business partner now browse the URL 'https://url:port/XISOAPAdapter/MessageServlet?channel=:BS_3RD_PARTNER:SOAP_SENDER&nosoap=true' on his system, he will get a 'Message Servlet is in Status OK'.
But when he tries to process the URL directly in his messaging system, he gets an error '(401) Unauthorized.'
Any hints what could be the problem between browing the URL in InternetExplorer and sending from the messaging system?
Does it really mean that authorization was successful, when getting 'Message Servlet is in Status OK' in the Browser?
How can I assign an user when not using ClientAuthentication?
I would be very thankful for every help...
Grtz, Juergen

Hi Satish,
could the user or password also be wrong, even if you get 'Message Servlet is in Status OK' when browsing the URL in the Internet Explorer? I would have seen this as a sign, that the user authentication works basically...
Is there a special place to store the password in the Visual Admin, or will the password be used, which is available in the SU01 ?
Grtz,
Juergen

Exception caught by adapter framework: error while processing message to ..

URGENT:
Legacy >XI>R3 interface
SAP XI (file_adapter --> RFC_adapter)
Friends.
 I need your help for next problem above:
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
Thanks very much for your helps
Nota: This error is XIPRO environment.
Message was edited by:
 Cristian Alejandro Toro Salazar
Message was edited by:
 Cristian Alejandro Toro Salazar

Hi Cristian,
>>>>functiontemplate from repository was
this SAP note 730870 - describes your issue
let me know if it helped
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Using SOAP Sender adapter in PI 7.1

Hi Guys,
I've created a sync scenario with SOAP sender adapter, but I have troubles with calling it.
I use following URL: http://<host>:50000/XISOAPAdapter/MessageServlet?channel=:BS_Bus_Sys:CC_SOAP_Test as I did in XI 3.0, but I'm getting error HTTP 400 Bad Request. I'm using the request generated from the IR Configuration.
Has something changed in 7.1 for this type of scenario?
Thanks guys,
Olian

Hi! Olian,
I think u r going in a wrong way. The above given URL is wrong and incomplete one.
The above url comes only after generating the WSDL. You ill gives that URL to ur source team to post their data at which this URL itselfs acts as an Gateway to enter into SAP XI/PI.
The generated WSDL contains URL like this>>
"http:// Host:Port/XISOAPAdapter/MessageServlet?senderParty=&senderService=Business Service&receiverParty=&receiverService=&interface=SenderInterfaceI&interfaceNamespace=http://XXXXXXXX" />
Also follow the below procedure for generating the WSDL.
Except generating WSDL remaining all development steps are same as creating File to Proxy Scenario.
CREATING THE WEBSERVICE IN XI :
1) In Integration Directory, go to Tools tab --> Define Web Services.
2) Now one Wizard window will opens and follow the below steps:
Here donu2019t go for the u2018 Proposed URLu2019, instead specify the URL as::
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>
If there is party then ::
http://host:port/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>.
3) Specify the Source Messageu2019s Message Interface.and remaining other input parameters.
4) Specify the Sender Business Serviceu2019s details:
5) Here, Cross check the details displayed and then click on u2018Finishu2019 button to create the Web Service
document(WSDL)
6) Now Save the WSDL code to the local system. At the bottom u ill get URL based on the above input
URl:
Note: Here in XI there is no XML Testing tool or SOAP client tool to test SOAP messages. That is why most of the people prefer either ALTOVA XML SPY Tool or SOAP CLIENT TOOL or INFO PATH.
If your working on PI 7.1 means::
1) Simply after creating Sender Agreement go to options above to that sender agreement instead of tools menu... and there you can observe 2 options at the bottom side.
a) PUBLISH in SR
b) Generate WSDL.
2) Once after activating your ID componenets just Press or go for option Publish in SR. Then automatically it will generate WSDL and publish that WSDL in the SERVICE REGISTRY. which is latest concept in PI 7.1.
3) Now by entering authentification details you can able to enter into service registry.
There are 4 tabs::
a) Service definitions
b) Publish
c) classifications
d) Manage.
Go for Service definitions::
4) Enter your sender SOAP interface and press GO or enter.
5) Select your interface and then at the bottom u can observe again 4 tabs:
a) General b) End Points c) classifications d) System Details.
6) In the general you can able to see your WSDL URL by again entering Authentification details.
7) Now Click End Points>Test Button>Enter Authentification details-->Seelct your Interface
Note:: Now you can test your scenario in this WEB SERVICE NAVIGATOR.
8) There you can enter you can pass your Input data parameters in your SOAP interface and execute or test your scenario here itself without any using of external tool like Altova XML or SOAP client tool.
I hope the above information will give you a detailed information in generating and testing webservice right.
Regards::
Amar Srinivas Eli

ASMA in SOAP Sender adapter.

Hi All,
Using ASMA under SOAP sender adapter I am trying to get the username of the user . I am referring below links for the same:
/people/michal.krawczyk2/blog/2009/05/26/pixi-pseudo-principal-propagation (referring this only for getting username)
getting user name from sopa header
But while testing through XML SPY , i am getting error :
Com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during parsing of SOAP header.
Please help??.
Thanks
Amit

Hi.
I have created WSDL file using below URL:
http://ISVSAPPIDEV:50100/XISOAPAdapter/MessageServlet?channel=:BS:CC_SOAP_Sender
Actually its a synchronous SOAP -PI - RFC scenario. When i am pinging the PI through XML spy(ASMA AND Transport Binding is UNCHECKED in soap sender channel) i am getting the response back from RFC, but when i am pinging after chking the ASMA and Transport Binding in SOAP sender adapter i am getting this error(the message is itself not reaching the PI):
Com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during parsing of SOAP header.
Thanks
Amit

Another SOAP Sender adapter "com.sap.aii.af.mp.module.ModuleException" erro

I am working on a synchronous scenario SOAP <-> XI <-> RFC.
This worked fine, when I run it without SOAP adapter, direct via XI Pipeline.
Now I want to use the SOAP sender adapter, but get the error as described below this post.
As this is a real new XI installation, some patches or updates might be required to make it work. Or some adapter modules ?
Any suggestions on how to solve this problem will be rewarded.
What worries me a bit is the line " " in the error description.
Extra info: I use SoapSonar as a test webservice client. The error is the message as received in te test client.
<?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>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/xi/645_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#9 $)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:427)
 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:160)
 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>

Hi Chandravadhana,
The colon should be there :
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
The inbound address for SOAP messages is: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel
Regards
Suraj

HTTP Call to SOAP Sender Adapter

Hi All,
I'm working on a scenario where i plan to use SOAP Sender Adapter for receiving Plain HTTP Calls from the client.
The purpose behind this exercise is to have control over the message flow in case of sender HTTP protocol in XI.
I configured a SOAP channel and used the option 'DO Not Use SOAP Envelope'. But when i post the message to the adapter engine using a HTTP client, it fails.
Can somebody guide me in this case.
Regards,
Anurag

Hi,
>>>But when i post the message to the adapter engine using a HTTP client, it fails.
with which error ?
Regards,
Michal Krawczyk

File to RFC - error while processing message to remote system:com.sap.aii.

Hi
i m working on File to RFC scenario. the records are getting displayed in sender CC and receiver CC. But in receiver CC i m also getting the following error:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user.
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user.
It was working fine few hours earlier but showing this error now. i was giving a SUBMIT program , but stopped that now.
But still facing the same problem. and in SXMB_MONI its showing recorded for Outbound processing.
could anyone help.

Hi
I am Facing Following Error When I am trying to call SAP Screen through JCO.jar
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user
Please Guide Whethere it is possible to call SAP screen Through JCO.jar ot NOT
Please HELP if it is possible to Call SAP screen through JCO.jar with step and Code
Thanks
Vivek

INVALID_QUEUE_NAME : Error while scheduling message using qRFC

Hello SDNers
We are currently performing our PI 7.1 upgrade and one of our scenario uses a Sender SOAP of the type EOIO. We tried executing this scenario in PI 7.1 XID environment and in it worked fine without any errors but in our PI 7.1 QA environment it is giving the following errors
<?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="INTERNAL">SCHEDULE_ERROR</SAP:Code>
<SAP:P1>XBQOC___*</SAP:P1>
<SAP:P2>INVALID_QUEUE_NAME</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while scheduling message using qRFC (queue name = XBQOC___*, exception = INVALID_QUEUE_NAME)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can you please exaplian what could be the issue we are facing.
Thanks.
Kiran
Edited by: Kiran Sakhardande on Oct 22, 2008 4:08 PM

HI Kiran,
Have gone throgh the following link?
INVALID_QUEUE_NAME
Regards
Sridhar Goli

Error while posting IDoc

Hi,
i am getting the following error while posting an IDoc: Program parameters for LS XXXXXXXX 2002 have not been set. Please suggest what can be the possible reason for it and the probable solution.

First ,
check the partner profiles in R3,
i.e. a logical system is defined for XI , particluar Message type is added on inbond side and selected the releavnt messge type and and process code. this is all in WE20.
defining a logical system is in SALE.
then ditribute u r the model in BD 64
once every thing is OK in R3
on PI.
create a RFC destination of type R3 which points to R3 , try remote log-on .
this will be used in receiver chaneel
and check u r receiver chaneel is defined under Business system of R3, and BS refers to same client where partner profiles are defined.
and one of the following should be in place.
check 'apply control record from payload' if ur explictly passing Control record from mapping
otherwise,
check sender service and receiver service in Receiver agreement and select appropriate systems.
Regds,
Suresh

Error while posting the CREMAS03 Idoc

Hi
I a getting the Error while posting CREMAS03 idoc from File
The ERROR: Status 65 ,Error in ALE Servics: Cross Company code does not exits..
but when i cheked with the functional guys , the comany code exits..
Any one have any idea
SV

Hey,
    seems you have given wrong enteries for logical system in sale or in WE20(patrner profile)
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.

SOAP Sender Adapter Not working

We have the following Synchronous sceanrio: Third Party System <> PI <> SAP ECC
The interface works well in our DEV and PreProd environments but has stopped working in our QA environment.
The SOAP Sender Adapter is giving me the following error:
failed to initialize: org.apache.axis.ConfigurationException:
java.lang.ClassNotFoundException: ------------------------- Loader Info -------------------------
ClassLoader name: library:com.sap.aii.af.axisproviderlib] Living status: alive Direct parent loaders: system:Frame library:com.sap.base.technology.facade library:engine.j2ee14.facade] Resources:
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/axis.jar
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-discovery-0.2.jar
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-logging-1.0.4.jar
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-net-1.0.0-dev.jar
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/wsdl4j-1.5.1.jar
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/xmlsec-1.4.0.jar
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/wss4j-1.5.6.jar
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/opensaml-1.0.1.jar
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/xalan-2.6.0.jar
Currently the Quality of Service for the communication channel is set to "Best Effort" because it is a Synchronous Interface. However if I change the Quality of Service to "Exactly Once" the message is received by PI without any problems. So the problem is specific to Synchronous.
I tried to create a new communication channel and use that but that didnt help.
We have checked on the server and all the above mentioned .jar files are all in place.
I have compared the Processing Sequence and Module Configuration of the Module tab (for the communication channel) with the other environments and everything seems to be fine.
Any help would be much appreciated.
Thanks,
Krishneel

Hi Krishna,
ClassLoader name: library:com.sap.aii.af.axisproviderlib] Living status: alive Direct parent loaders: system:Frame library:com.sap.base.technology.facade library:engine.j2ee14.facade] Resources:
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/axis.jar
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-discovery-0.2.jar
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-logging-1.0.4.jar
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-net-1.0.0-dev.jar
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/wsdl4j-1.5.1.jar
Have you deployed the following Jar.
commons-discovery-0.2.jar
○ commons-logging-1.0.4.jar
○ commons-net-1.0.0-dev.jar
○ wsdl4j-1.5.1.jar
Refer this
http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm
Edited by: Debashish Roy on Jul 18, 2011 10:10 AM

'Keep Header' Option in SOAP sender adapter not working

Hi all
I have exposed a webservice using a SOAP sender adapter in XI. A SOAP client is sending request to this service.
The SOAP request has some elements in the header like wssecurity and ws addressing tags.
When I remove the header elements and send the request my scenario works as expected but when I include the header fields I get a time out in my soap client application and cannot see any message, any where on XI. Can somebody help me understand why this is happening.
Thanks
Dilip

Hi Stefan
In my scenario it is ok if XI ignores the soap header tags it does not understand. I want the system to ignore the header tags and go ahead and process only the payload.
But unfortunately I keep getting a time out whenever I send a request with the header tags. When I remove the header I can sucessfully post documents.
I tried increased the time out to 5 min but still continue to get the problem. So am sure the problem is not exactly related to timeout, but due to the header tags.
What do you suggest?
Regards
Dilip

Invocation of SOAP Sender Adapter using Apache SOAP

Hi,
I'm trying to invoke the XI SOAP Sender Adapter using the Apache SOAP API. It seems that my message header is missing a few parameters (see exception below). Does anybody know which to set?
Regards,
Heiko
==========
Exception:
<?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>Exception</code>
 <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:502)
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
 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:507)
 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:392)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
 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:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged1(Native Method)
 at java.security.AccessController.doPrivileged(AccessController.java:321)
 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: java.lang.Exception: Bubble configuration error: parameter 'XI.InterfaceNamespace' is missing
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.getParaRequired(XISOAPAdapterBean.java:895)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.createDefaultMessageHeader(XISOAPAdapterBean.java:942)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:214)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:496)
 ... 22 more
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Hi Heiko,
You are missing the Namespace Parameter in the sender soap adapter configuration in XI3.0
Thanks
Prasad

Error while posting messages to SOAP sender adapter SP 13

Similar Messages

Maybe you are looking for