Error in SOAP Sender Adpater

hi
I am SOAP to RFC scenario.. when i am testingthe WSDl from Altova it giving me the follwing error
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message bb9025d0-14a1-11de-bd25-001a4b0aa09f(OUTBOUND) expired.
do i have to change any settings
SV

Hi SV,
I am also getting the same error.
Did you get any solution for this?
I will be grateful to you if you can help me.
Please help!
Thanks & Regards
Gopal

Similar Messages

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.

Error in JMS Sender Adpater

Hi
I am doing Weblogic-PI-File scenario
when i try to pick the XML file from Weblogic JMS queues its giving the follwing error
Error occurred while processing message: 552eec87-b6c3-4035-2675-cc3cd57b5487. Detailed error (if any): com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Error in converting Binary message <?xml version="1.0" encoding="UTF-8"?> <ns0:MT_File_Sender xmlns:ns0="urn:XXXXXXXX.com:JMSReciever"><SalesOrderDetails><MRNNumber>1234</MRNNumber><FirstName>ABC</FirstName><LastName>CDE</LastName><SocialSecurity>1234567890</SocialSecurity></SalesOrderDetails></ns0:MT_File_Sender> to XI message for message: 552eec87-b6c3-4035-2675-cc3cd57b5487: TransportException: No MIME header found
Edited by: S V on Jan 27, 2009 1:08 AM

Hi I am using Weblogic JMS Queues ..
and the connection parameters i am using :
JNDI LOOKUP NAME FOR QUEUE CONNECTION FACTORY:
mm.jms.VendorConnectionFactory
JNDI LOOKUP NAME OF JMS QUEUE: mm.jms.PIOutboundTestQueue
NAME OF JNDI INITIAL CONTEXT: weblogic.jndi.WLInitialContextFactory
JNDI SERVER ADDRESS : t3://vendor.xxx.xxxxxxx.com:6107
JNDI LOGON USER : xxxxxx
JNDI LOGON PWD : XXXXXX
did i miss anything ... or do i have configure anything on JMS sender adpater so that it will convert the text message into Binary

Soap sender adpater issue missing sender interface and namespace in the msg

Hi Expert,
I got a problem when try to using soap sender adapter.
Here is the sceanrio:
Http web service client call ---PI soap sender adapter -some routing data-business system inbound.
Sytem information:
SAP_ABA     700     0019     SAPKA70019     Cross-Application Component
SAP_BASIS     700     0019     SAPKB70019     SAP Basis Component
PI_BASIS     2005_1_700     0019     SAPKIPYJ7J     PI_BASIS 2005_1_700
ST-PI     2008_1_700     0001     SAPKITLRD1     SAP Solution Tools Plug-In
SAP_BW     700     0021     SAPKW70021     SAP NetWeaver BI 7.0
ST-A/PI     01L_BCO700     0000          -     Servicetools for other App./Netweaver 04
Here is my problem. I use soapui trigger a test msg to PI system. But in the sxmb_moni, only sender service is there.
The sender interface and sender namespace is missing. And the msg has error called: :INTERFACE_REGISTRATION_ERROR.
Which means I do not have a inbound interface to process the msg.
But I suppose to redirect the msg to business system.
Here is the configuration:
reciever determination: soap sender service, soap outbound interface, soap interface namespace --> reciever business sytem.
Interface ditermination: soap sender service, soap interface --> receiver interface, receiver namespace.
Sender agreement: soap service, soap itnerface --- soap communication channel
receiver agreement, soap service---> receiver sevice, receiver interface, reciever namespace and reciever cummunication channel
define of soap sender adapter:
soap sernder, with use encoded header and use query string checked and qos as exactly once.
Anyone has any idea here? Many thanks! And most strange thing is yesterday it works and today it failed.
Please kindly help here.
Thanks a lot,
Leon

Hi guys,
thanks for the input.
Hi Sven,
I have input default interface and namespace.
Hi sivasakthi,
Regarding mistype, it may happen, I will do it again right away.
And the URL is generated by the wsdl toolkit in the directory.
I marked use encoded header and query string in the communication channel.
I will generate the wsdl again and test it again.
Regarding URL(endpoint of web service):
http://hostname:50000/XISOAPAdapter/MessageServlet?channel=:AGSSAL_SOAP:AGSSAL_SOAP_CC&version=3.0&Sender.Service=AGSSAL_SOAP&Interface=urn:a1s_saplivelinkcontent.service.sap.com^MI_O_AS_DELIVERNOTIFY_SOAP
Again thanks for you guys help.
Best regards,
Leon

SOAP Sender Adpater Authentication issue with Siebel

Hello PI experts,
I have developed scenario in which,
SAP PI version: 7.31
Sender : Siebel
Sender Adapter: SOAP
Receiver: SAP ECC
Receiver Adapter: Proxy
Scenario has been configured and wsdl is generated properly. I tested scenario using SOAP UI which gave me proper response.
But when scenario has been tested through Siebel UI, its giving Authorization 401 error.
HTTP/1.1 401 Unauthorized
server: SAP NetWeaver Application Server 7.20 / AS Java 7.31
date: Wed, 20 Aug 2014 05:54:58 GMT
We have tried following approaches:
1. Appending Credentials in URL
2. Siebel team tried sending credentials in their workflow
Referred blog:
http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/03/07/a-closer-look-at-soap-sender-authentication
But in all cases we got same error.
Also, is there any possibility to turn of sender authentication for SOAP adapter ?. I tried approach of removing tags in web.xml but that also dint work.
Please suggest some way
Thanks,
Gaurav Khandelwal

Hi Gaurav,
Can you please check with your basis is that firewall will be open to send data through soap to PI.
Thanks,
Sreenivas

"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>

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

Error in SOAP Sender Communication Channel

Hello Gurus,
I am trying for a SOAP (Axis) -> PI -> IDOC scenario and getting an error while sending message to SOAP Channel.
Message structure used
<?xml version="1.0" encoding="UTF-8"?>
<MaterialData>
<field1>value</field1>
more fields
</MaterialData>
Basically a XML message.
I am getting below error message for Axis (channel monitoring):
MP: exception caught with cause org.xml.sax.SAXException: Bad envelope tag: MaterialData
Can you please let me know what should be the message format when testing Axis? I do not intend to use any SOAP envelope.
I have already referred: Re: SAP PI 7.0 Receiver SOAP Axis (Bad envelope tag: html)
Please help.
Thank you!

Hello,
Can you please let me know what should be the message format when testing Axis? I do not intend to use any SOAP envelope.
Correct me if I'm wrong, but I think you will only be able to plain message to the Axis sender when using REST. See SAP Note 1039369 FAQ XI Axis Adapter, under Sender Adapter General Question 35.
35. Can I post a plain no-soap request (REST) to the sender adapter servlet?
Yes. You need to include a query parameter rest in the request URL, as http://host:port/XIAxisAdapter/MessageServlet?...&rest. For the availability of this feature, refer to Note 1448849.
All the other messages require a SOAP Envelope.
Hope this helps,
Mark

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

XIProxy:PARSE_APPLICATION_DATA , error in soap sender communication channel

HI
I am having soap toABAP proxy synchronous interface , when i test from soap UI tool i am getting the below errro . can any body help me with this error
<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.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIProxy:PARSE_APPLICATION_DATA:
     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1178)
regards
sandeep
Edited by: pendyalas on Jul 27, 2011 5:01 PM

Hello,
can you check the message format defined in repository.
Regards
Vivek

SOAP sender adapter with client authentication

Hi,
Can you please tell me the steps to be followed to configure SOAP sender adpater for HTTPS with client authentication.
Thanks

Hello,
Check out this SAP NOTE
[Note 891877 - Message-specific configuration of HTTP-Security|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=891877]
Check out below blog for step by step process.
/people/rahul.nawale2/blog/2006/05/31/how-to-use-client-authentication-with-soap-adapter
Hope this will help.
Nilesh
Edited by: Nilesh Kshirsagar on May 28, 2009 11:31 AM

Soap sender Qos

Hi
I am facing error in soap sender posting from soap UI. I want to send the soap request asynchronous.
could you please tell me how to change the QOS,tried with QOS as EO in sender channel.

Hi
Try appending &QualityOfService=ExactlyOnce at the end of your soap URL
http://host:port /XISOAPAdapter/MessageServlet?senderParty=& senderService=FS& interface=IF&receiverParty=&receiverService=TS&interfaceNamespace=IFNamespace
for more Soap related error refer the note 856597
Regards,
Srinivas

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.

Error 401 while sending SOAP Request to XI

hi friend ..
i am getting Error 401 while sending SOAP Request to XI..
can u suggest me where may be the error?
thanks..

Hi,
Refer these threads:
Testing XI SOAP scenario via XMLSpy
Re: SOAP Sender ADAPTER 401 No Authorisation
Re: XI Web Service - Code: (401) Unauthorized.
Try soap client https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9b16d790-0201-0010-4e9b-baa5f42830d8
Regards
Suraj

SAP PI 7.1 SOAP sender 500 internal server error

Hello!
We would like to receive messages from our business partner. As the partner sends EDIFACT we have to use the conversion from EDIFACT-text to EDIFACT-xml. That's why we have to use SOAP instead of plain HTTP.
As the partner already sent messages over X.400 we just added a SOAP communication channel and used this channel in the sender agreement instead of the X.400 communication channel.
We sent the following link to the customer:
http://<server>:<j2ee port>/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<SOAP sender communication channel>
One question: is the <service> the communication component used for the partner?
At the moment the partner receives a 500 error message. Due to our network partner the message reaches the PI system.
Due to the information I found that also a message parsing error can cause a 500 error message I would like to add the processing sequence:
Does anyone have an idea how to solve this problem?
Thanks a lot!
Regards
Christian

Hi Christian
You can refer to the following SAP Library link on how to configure the SOAP sender.
Configuring the Sender SOAP Adapter - Configuring the SOAP Adapter in the Integration Directory/PCK - SAP Library
For the URL, the <service> is the Communication Component that the SOAP channel belongs to.
Using the example below, the value would be P_B2B_:BC_:CC_S_SOAP_
Actually SAP recommends a new alternative for the URL. If you scroll right to the end of the library link above.
You have configured the sender SOAP adapter. You can trigger a call to the sender SOAP adapter using either of the following URLs. However, SAP recommends you to use the second option.
http://hostname:portname/XISOAPAdapter/MessageServlet?channel=partyname:service name:channelnameIf you have not created a party, enter channel=servicename:channelname.
http://hostname:port name/XISOAPAdapter/MessageServlet?senderParty=name of the sender party<&senderService>=name of the sender service<&interface>=name of the interface<&receiverParty>=name of the receiver party<&receiverService>=name of the receiver service<&interfaceNamespace>=name of the interface namespace
You can get this by generating the WSDL from the Sender Agreement object (Sender Agreement -> Display WSDL). The generated URL will be at the last section of the WSDL.
Also, please note that modules cannot be added to the SOAP sender adapter, also mentioned in the link.
You cannot add your own modules to this adapter.
An alternative would be to receive the EDIFACT Flat file as it is, and write it to at temporary File/FTP location. Then have a second channel pick it up, you can configure the second channel with module to convert it to EDIFACT XML.
Lastly, regarding the issue about the partner getting HTTP 500 error. Please check if you are able to see any error logs in the communication channel. It might give you some pointers as to what might be wrong - invalid sender agreement, etc, etc.
Rgds
Eng Swee

Error in SOAP Sender Adpater

Similar Messages

Maybe you are looking for