SOAP Receiver Adapter Target system down

Hi All,
My scenario is SOAP Receiver adapter --- > Portal system (Target system.).
Now team is taking restart of target system. It will take around 1 hr. So my question what will happen to the messages which is received by SOAP Receiver adapter in this time frame. ?

Hi Rajhans ,
All the messages during that period of time will fail with System Error ,We have to re-send these messages manually once the target system is up. In stead of selecting one by one you can set Multiple Selection On option to select the messages in RWB
.Please refer the weblog will give you some idea about the standard reports which can also be used to reprocess the messages.
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414700)ID1051765250DB10924207601714756238End?blog=/pub/wlg/2728
do you have synchronous soap receiver or async?
Regards,
Srinivas

Similar Messages

SOAP Receiver Adapter - Target URL

Hi,
We have a web service scenario, where the Sender is a III Party Java system and PI is the middleware and ECC as our receiver system. We have a wsdl binding generated from SOAMANAGER. We are using the WSDL Endpoint as the Target URL in our SOAP Receiver Adapter. The scenario works perfect with desired results.
Now that webdispatcher comes into place for load balancing and the BASIS team has given a different URL to use in the Target URL of the SOAP Reciver Adapter. The scenario throws the following eorr:-
Adapter Framework caught exception: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 Redirect
Has anyone come acrossed such issues. Looking forward for a solution.
Thanks & Best Regards.
Kris

> Now that webdispatcher comes into place for load balancing and the BASIS team has given a different URL to use in the Target URL of the SOAP Reciver Adapter. The scenario throws the following eorr:-
>
> Adapter Framework caught exception: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 Redirect
>
> Has anyone come acrossed such issues. Looking forward for a solution.
I wonder why your basis team is not able to help you.
It seems that the web dispatcher is not set up correctly.
http://en.wikipedia.org/wiki/HTTP_302

SOAP Receiver adapter target url and method details

Hi Friends,
I am working on file to SOAP interface.
I know using SOAP receiver adapter , we need to have target URL and action.
Here, how client need to give target url and action as they are not aware of these things..please suggest.
Also if we are generating inbound service interface,how they have to handle this from their end.
Thanks
Kishore

Get the WSDL file from ur Third party client and u can use the WSDL file as an External definition in PI and WSDL file also has WSDL URL which u can use in SOAP receiver adapter.
For INbound SOAP case-
Generate the WSDL file in XI and give that WSDL file to ur third party client which will send the data using the WSDL URL mentioned in the file.
refer below blog for understanding in detail:-
How to use SOAP adapter:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
chirag

Soap Receiver adapter , Target URL and Soap Action

HI all,
WIll anyone tell me regarding Soap action, casue , they have given a URL which i have put in Target URL, but i am not able to understand what is SOap action what need to be put in this
Thankign you
Sridhar

i Sridhar,
In XI SOAP adapter we need two things:
SOAP URL: which is endpoint to the webserver.
SOAP action: describes particular method name we wanted to excute on that web applicaiton hosted on the webserver.
WSDL file has normally multiple operations(methods) , so we execute particular method by giving particular action name.
Action is not mandatory parameter i guess, this is in case , when wsdl is exposing only one method(action).
:Normally you can find SOAP Action element under element <SOAP:operation name = "XXX">
Hope this clears.
Cheers,
Div

Receiver Adapter - Target URL/SOAP Action

Hi,
Can I just confirm the following 2 values required on a SOAP Receiver adapter:
Target URL : Location within SOAP:Address tag of WSDL
SOAP Action: SoapAction within SOAP:Operation for relevant Web Service method within WSDL
Cheers,
PaulC.

> Target URL : Value of SOAP:Address tag from web service WSDL
right, it is attribute "soapAction"
> SOAP Action: Value of SOAP:Operation for relevant Web Service method within web service WSDL
right. attribute "location"
check this guide:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4

Issue while passing Target URL dynamically in SOAP Receiver Adapter

Experts,
I am stuck with an issue while passing the Target URL dynamically.
The UDF required for this works just fine. I can see the Target URL in Dynamic Configuration header(The Key is TServerLocation) in SXMB_MONI but the request that I am sending is not reaching the web service.
Some posts have suggested to hard code the Target URL as http://.
Below is the error that I am getting when I hard the Target URL as http://:
<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>RecoverableException</code>
               <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:453)
     at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:131)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:834)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     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 hard code the Target URL as Test (any dummy value), the error that I get is different. (Detailed error shown below)
<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>RecoverableException</code>
               <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: no scheme
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:453)
     at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:131)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:834)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     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>
I've referred the post [Dynamic URL for SOAP receiver adapter;.
I am on PI 7.0.
Any help in this regard is highly appreciated.
Best Regards,
Vijay

Issue resolved... by doing this:
DynamicConfigurationKey key2 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "TAuthKey");
conf.put (key2, "username");
In the advanced tab of the communication channel, set the flag "View Authorization keys", and then added "username" (user to access the dynamic target url) and the password (2 times).
That's it...

Payload at Adapter for System Errors - SOAP receiver adapter

Hi Everybody,
I am working on an Idoc to SOAP asynchronous scenario.
There are connection issues between SOAP adaper and the target webservice.
I need to capture the Idoc number from the message payload for the Erroneous messages at the adapter for the System errors.
Is there any way of capturing field values from the payload (Say, Idoc number) at the SOAP receiver Adapter level.
Helpful answers will be rewarded points.
Thanks & Regards,
Zabiulla

Hey,
I think you need to implement a module inorder to get the payload at receiver adapter module.
As far i concern you can not directly refer the payload in adapter in receiveer communication channel unless you have your own module, which gets the payload. Check the Modules tab in the communication channel and also regarding how to get the payload for error information, follow the steps mentioned in the below link, which gets the payload in file. hop it will resolve your issue.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/snippets/writepayloadtoafilefromAdapter+Module
Regards..
Prasanna..

Dynamic URL in SOAP Receiver adapter

Hi all,
I have a scenario where I am using a SOAP receiver adapter to send a cXML document to some vendors. I need to change the URL based on the vendor number (passed by sender SRM system). So I have created a user-defined function and used in message mapping to assign the right URL to the variable TServerLocation. But the communication channel still prompts for a static URL which appears to be a mandatory field. Even though the DynamicConfiguration tab in Message Monitoring shows that the TServerLocation was correctly assigned, the scenario does not work when I put some dummy in the static URL field like 'dummy' or '*'. Any ideas on how to make the communication channel go for the dynamic URL field and ignore the static URL field? I have already selected the'Use Adapter Specific Message attributes' and 'Variable Transport Binding' check boxes. Am I referring to the correct variable that references the target URL? Also other than the two checkboxes that I mentioned, I am not displayed anything else under "Adapter Specific Message Attributes" section in the comm. channel.
Thanks

James,
I ve just been digging into SAP help, and have tried it too ... Looks like it doesnt work the way it is supposed to.
Anotheer point i found was, in the FILE ADAPTER, when we say ADAPTER SPECIFI ATTRIBUTES , we can select the attirbutes.. This is not possible in a SOAP adapter...
Maybe, we can only access the ADAPTER SPECIIFC ATTIRIBUTES of a SOAP adapter, but cannot set them dynamically.
Let me know if you find something on this issue.
Regards,
Bhavesh

Soap Receiver Adapter - No Response Message

Hi, I've got the following scenario: Idoc - XI - Webservice. I've imported the WSDL from the .NET webservice and used the input and output messages in a syncronous interface. I've setup a SOAP Receiver adapter with the Webservice details. Everything is working fine when I call the webservice and the data is received 100% at the target system, but I am not getting ANY response back on XI.
RECEIVER SOAP ADAPTER Audit LOG:
2008-01-24 16:41:57 Success SOAP: request message entering the adapter with user J2EE_GUEST
2008-01-24 16:41:57 Success MP_LEAVE1
2008-01-24 16:41:57 Success The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.
2008-01-24 16:41:57 Success Acknowledgement creation triggered for type: AckNotSupported
2008-01-24 16:41:57 Success SOAP: completed the processing
2008-01-24 16:41:57 Success SOAP: continuing to response message 83638fb0-ca8a-11dc-b36c-00145eed9500
2008-01-24 16:41:57 Success SOAP: sending a delivery ack ...
2008-01-24 16:41:57 Success SOAP: sent a delivery ack
2008-01-24 16:41:57 Success The message status set to DLVD.
2008-01-24 16:41:57 Success Acknowledgement sent successfully for type: AckNotSupported
Has it got anything to do with the "AckNotSupported" type? Is "AckNotSupported" the default setting for the receiver SOAP adapter? If so, where do I change this setting?
When I call the webservice with the exact same input using a standalone tool, I get the response message back 100%. Any help will be appreciated.
Thanks
Rudi

Hey
you are confusing between a response and an acknowledgement.
response and acknowledgement and not one and the same thing.
response is basically used when you send some query to the receiver system and expect a set of value(s) for your query.for e.g sending a query to a Database(JDBC) or SAP system(RFC)
and acknowledgement is just a notification that the message was receiver by the receiver correctly,it does not returns you a set of value(s).
now coming to your question,ALEAUDIT IDOC is generated when an IDOC is posted,since in your case you are not posting and IDOC,instead your are sending it ,i m not sure if ALEAUDIT will be generated or not,one thing that will come to your rescue is that every receiver SOAP adapter expects a HTTP response(irrespective of you explicitly asking it or not).
a HTTP 200 means that messages were posted successfully,and HTTP 500 means application error,get this HTTP response and send it back to the SAP system,most probably you would need to use BPM for this.
Thanx
Aamir
Edited by: Aamir Suhail on Jan 24, 2008 11:26 AM

Soap receiver adapter exception

Hi,
I am using SOAP receiver adapter to access a web service that is hosted on SAP Web AS (in this case it is the integration server Web AS). I use the web services navigator to test the web service and the web service works fine. The name of the web service is 'RemoteCrossReferenceProcessor' and it has one operation 'crossReference'.
But with the soap adapter, I am getting OperationNotFoundException in the logs and my web service is not getting accessed. Here is the server log:
<u><i>An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:RemoteCrossReferenceProcessor'; Key name:'SoapRequestWrapper' key value:'crossReference'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#
#1.5#0003BA0FF9EA0022000000840000688D0003F9349A3C2D61#1118429251382#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######b40aca80d9be11d994360003ba0ff9ea#SAPEngine_System_Thread[impl:5]_47##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: NO_BACK_SYSTEM_IN_HOPLIST:#http://sapsand1:8000/sap/xi/engine?type=entry#</i></u>
Here is adapter configuration:
Transport Protocol:HTTP
Message Protocol:SOAP 1.1
Adapter Engine:Integration Engine
Target URL: http://<server_name>>:50000/RemoteCrossReferenceProcessor/Config?style=document
User:
Password:
Default SOAP Action:
I imported the WSDL into the external definition and used the messages from the WSDL for defining my interface mappings.
I am using XI 3.0 SR1 (SP 09).
I am out of ideas as to why the SOAP adapter is not calling my web service. Please help me with your suggestions.
Thanks and Regards.

HI Dani,
I was looking for this error and I found this post AXIS SOAP Receiver. This post says about other errors, but sugests many ideas to found the soluction, like:
1- non-deployed all AXIS jars; (but in this case it deployed all)
2- Exists this note for one erro in AXIS: (https://service.sap.com/sap/support/notes/1028961).
3- this document (http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b092777b-ee47-2a10-17b3-c5f59380957f) that have sets for header parameters. This is interesting becouse one of this parameters is obligatory but isn't filled, can occur error like "null object".
By the way, you can check if have update to AXIS (http://ws.apache.org/axis/), becouse isn't a SAP application and in other systems can have this error.
I hope this helps,
Romerito Silva

Problem in testing SOAP receiver adapter using SOAP UI

Dear Experts,
I'm trying to test my SOAP receiver adapter as mentioned in the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/21844. [original link is broken] [original link is broken] [original link is broken] But, my request from ECC proxy keeps failing in XI communcation channel monitor. I've configured my receiver adapter http://ip:8080/mockSoapHTTPBinding and kept the authentication as NONE. Can any of you suggest?
ip - is my system ip shown in ipconfig.
mockSoapHTTPBinding - is the path.
Thanks.

What is the error of the messages? Are the messages leaving the SOAP adapter?
Please try both:
1. Go to Runtime Workbench -> Component Monitoring -> Adapter Engine -> Test message. Then, execute the message directly without the intermediate of the Proxy sender. This will allow you to check only the receiver SOAP.
2. Please use the TCPGateway tool attached from the note below. It will be a "man-in-the-middle" between the target WS and the Receiver SOAP channel, tracking the whole HTTP/SOAP message. Check if the message is well-formed.
[Note 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=856597]
under question "Q: How can I trace the whole message?"

SOAP receiver adapter digest authentization

Hallo,
I have scenario with SOAP receiver adapter configured as follow:
Adapter Type: SOAP
Transport Protocol: HTTP
Message Protocol: SOAP 1.1
Adapter Engine: Integration Serer
Target URL: http://localhost:8099/webservices/test_v1_1_2
Configure User Authentication
User: ****
Pasword:****
but WS need digest HTTP authentication and SOAP adapter send in header Authentication: Basic.
Hou can I change authentication method for SOAP protocol?
Thx

Hallo,
I solved this problem by using AXIS framework. I hope that this short instruction help to someone.
1. In SOAP receiver CC you have to set up Transport Protocol to HTTP(AXIS) and Message protocol to AXIS
2. Now you can switch Authentication to Digest (NOW adapter will still send Basic!!! Digest Authorization is Supported only by the following handler: com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender)
3. On Module tabs in section Module configuration change type HTTPSender to CommonHTTPSender:
(trp handler.type java:com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender)
4. Save and Activate
Before you start to use AXIS framefork you have to deploy necessary library.
This thread help:
Re: How to install SOAP Axis adapter and where is it available ??
Be carefull, for digest authorization you have to linked Optional library "Jakarta-Commons HttpClient" too.
Good luck.
JK

SOAP Receiver adapter error. SOAP CALL Failed

Hi ,
I am implementing scenario R/3->RFC adapter->XI->SOAP REceiver adapter->Web Service (Synchronous). I am getting the error.
SOAP: call failed
SOAP: error occured: java.net.ConnectException: Connection timed out
Message log is as below.
Any clue ?
Thanks & Regards,
Mathew
2005-10-31 18:59:58
Success
output
1130810398454
The message was successfully received by the messaging system. Profile: XI URL: http://host:Port/MessagingSystem/receive/AFW/XI
2005-10-31 18:59:58
Success
output
1130810398458
Using connection AFW. Trying to put the message into the request queue.
2005-10-31 18:59:58
Success
output
1130810398458
Message successfully put into the queue.
2005-10-31 18:59:58
Success
output
1130810398459
The message was successfully retrieved from the request queue.
2005-10-31 18:59:58
Success
output
1130810398459
The message status set to DLNG.
2005-10-31 18:59:58
Success
output
1130810398460
Delivering to channel: CC_CALCULATOR
2005-10-31 18:59:58
Success
output
1130810398564
SOAP: request message entering the adapter
2005-10-31 19:03:07
Success
output
1130810587497
SOAP: call failed
2005-10-31 19:03:07
Error
output
1130810587497
SOAP: error occured: java.net.ConnectException: Connection timed out
2005-10-31 19:03:07
Error
output
1130810587498
Exception caught by adapter framework: Connection timed out

Hi Mathew,
Check if the webservice is availble??? Based on the error below, it looks like the message is timing out at the Adapter Engine level waiting for the connection to make the webservice call...
Prasad

SOAP Receiver Adapter issue

Hello there,
I am using a SOAP receiver adapter. The URL contains the format - https://<XYZ.com>/car/soap/Sync?login=username&pass=password
Now, if I configure the channel by using the "Configure User Authentication", the data is not getting posted at target.
But if I provide the user id / pwd in the URL, it gets posted.
I don't want to use the user id / pwd in the URL but at the sametime, the WS team is not ready to change the format of the URL.
Can I use "Query String" to handle that? If yes, how? If no, what options I have?
Thanks for your precious input and time.
Abhi

Thanks Suraj!
Have you tried this:
url : https://<XYZ.com>/car/soap/Sync
and Configure User Authentication option set
I haven't tried it that way. I am not sure whether that will work, as WS team told me that I am required to put in the whole URL. But thanks for your suggestion, I will give it a try that way.
also try specifying the SOAP action as per your wsdl file
SOAP Action is not Mandatory, so I am not using that.
Thanks,
Abhi

SOAP Receiver Adapter Always "Running"

I have a SOAP receiver adapter that is working fine. I call an MDM web service, which sends a response, but I do not need it. I have tried a synchronous and asyncronous interface. Both work fine.
But...with both, the communication channel monitor in RWB always shows a Short Log of "running".
Is this right? I expected that the Short Log value would reset to inactive or something.
Processing Details...
2009-01-28 10:13:29 Success Message successfully received by messaging system. Profile: XI URL: http://snadc80i:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2009-01-28 10:13:29 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2009-01-28 10:13:29 Success Message successfully put into the queue.
2009-01-28 10:13:29 Success The message was successfully retrieved from the receive queue.
2009-01-28 10:13:29 Success The message status set to DLNG.
2009-01-28 10:13:29 Success Delivering to channel: SOAP_MDMIn_MDMUpdateRecord
2009-01-28 10:13:29 Success MP: Entering module processor
2009-01-28 10:13:29 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
2009-01-28 10:13:29 Success SOAP: request message entering the adapter with user J2EE_GUEST
2009-01-28 10:13:29 Success SOAP: completed the processing
2009-01-28 10:13:29 Success SOAP: sending a delivery ack ...
2009-01-28 10:13:29 Success SOAP: sent a delivery ack 2009-01-28 10:13:29 Success MP: Leaving module processor
2009-01-28 10:13:29 Success The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System. 2009-01-28 10:13:29 Success The message status set to DLVD.
Thanks,
Keith

Short Log only displays the status of communication channel. So if it says running, then it would mean that the channel is in running status. When not in use, it doesn't get deactivated itself. I guess "running" is what people wait to see
Regards,
Prateek

SOAP Receiver Adapter Target system down

Similar Messages

Maybe you are looking for