Processing response message in webservice

Hello,
I'm quite a newbie with webservices and this question may seem quite stoopid but I'll ask it anyway...
I have built a small web service with JAX-RPC. I know that, with the ServiceLifecycle I can process the whole request message, SOAPHeaders and all, in the webservice itself. Does anyone know how can I process the outgoing response messages SOAP headers? I mean other ways than message handlers...
Thanks in advance!
Rami

You may wantto post this in the JWSDP community : https://jwsdp.dev.java.net/

Similar Messages

SOAP Response Message Format for APEX Webservice

Hi,
Can anyone from Oracle post it here about the exact format of the response message from webservice in order to build a report on top of this?
I have this format which is not working
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<getRecordsResponse xmlns="http://www.service-now.com/incident">
<getRecordsResult>
<active>0</active>
<activity_due/>
<approval>not requested</approval>
<approval_set/>
<assigned_to>f298d2d2c611227b0106c6be7f154bc8</assigned_to>
<assignment_group/>
<business_duration>1970-01-01 00:00:00</business_duration>
<business_stc>0</business_stc>
<impact>3</impact>
<incident_state>7</incident_state>
<knowledge>0</knowledge>
<location/>
<made_sla>1</made_sla>
<notify>1</notify>
<number>INC0000060</number>
<opened_at>2012-06-15 04:14:15</opened_at>
<opened_by>glide.maint</opened_by>
<order>0</order>
<parent/>
<parent_incident/>
<priority>4</priority>
<problem_id/>
<reassignment_count>0</reassignment_count>
<reopen_count>0</reopen_count>
<resolved_at/>
<resolved_by/>
<rfc/>
<severity>3</severity>
<short_description>Computer running slow</short_description>
</getRecordsResult>
</getRecordsResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
But below format is working.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<getRecordsResponse xmlns:tns1="http://www.service-now.com/incident">
<tns1:getRecordsResult>
<tns1:active>0</active>
<tns1:activity_due/>
<tns1:approval>not requested</approval>
<tns1:approval_set/>
<tns1:assigned_to>f298d2d2c611227b0106c6be7f154bc8</assigned_to>
<tns1:assignment_group/>
<tns1:business_duration>1970-01-01 00:00:00</business_duration>
<tns1:business_stc>0</business_stc>
<tns1:impact>3</impact>
<tns1:incident_state>7</incident_state>
<tns1:knowledge>0</knowledge>
<tns1:location/>
<tns1:made_sla>1</made_sla>
<tns1:notify>1</notify>
<tns1:number>INC0000060</number>
<tns1:opened_at>2012-06-15 04:14:15</opened_at>
<tns1:opened_by>glide.maint</opened_by>
<tns1:order>0</order>
<tns1:parent/>
<tns1:parent_incident/>
<tns1:priority>4</priority>
<tns1:problem_id/>
<tns1:reassignment_count>0</reassignment_count>
<tns1:reopen_count>0</reopen_count>
<tns1:resolved_at/>
<tns1:resolved_by/>
<tns1:rfc/>
<tns1:severity>3</severity>
<tns1:short_description>Computer running slow</short_description>
</tns1:getRecordsResult>
</getRecordsResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Please let us know so that can work with third parties to integrate webservices
Thanks,
Mehabub

Here is the query that apex is using to extract the individual element
select extractValue(value(t),'/*/number','xmlns="http://www.service-now.com/incident"') "number"
, extractValue(value(t),'/*/severity','xmlns="http://www.service-now.com/incident"') "severity"
from wwv_flow_collections c,
table(xmlsequence(extract(c.xmltype001,'//getRecordsResponse/getRecordsResult','xmlns="http://www.service-now.com/incident"'))) t
where c.collection_name = 'P_RESULTS21'FYI, that extraction method is deprecated starting with 11.2, though APEX still uses it for backward compatibility.
That query works when applied on the first SOAP response you posted :
SQL> select extractValue(value(t),'/*/number','xmlns="http://www.service-now.com/incident"') "number"
2 , extractValue(value(t),'/*/severity','xmlns="http://www.service-now.com/incident"') "severity"
3 from wwv_flow_collections c,
4 table(
5 xmlsequence(
6 extract(c.xmltype001,'//getRecordsResponse/getRecordsResult','xmlns="http://www.service-now.com/incident"')
7 )
8 ) t
9 where c.collection_name = 'P_RESULTS21';
number severity
INC0000060 3
The second SOAP response is not even well-formed so I doubt the query works on it as you claim it does :
<tns1:active>0</active>
...

Response message back to Third party vendor webservices

Third party vendor sends messages to a webservice. The SOA application takes the message and puts it into a JMS topic through a mediator with asynchronous interface. All good so far, the system now needs to send a response back to the third party's webservice saying the message processing failed or was successful. For mediator, there are two concepts callback and response. What is the difference between callback and reponse. Which one should I use to send response message back to third party. Do I need OSB for this?
Please suggest the approach for getting this implemented. I am fairly fresh to the SOA components and appreciate help in this regard. I hope I am making sense, if not feel free for more clarification. I am struck on this for atleast a week now.
Thanks

I am using the mediator component which does callback and response as per the SOA user guide. I am not sure, while sending response back to third party, should I be using callback or response. There are no use cases for asychronous interaction using jms topics in Oracle samples examples also.
Looking forward for some help or suggestions
Thanks

Issue in parsing the response of a WebService in Service Link

I am getting issues in connecting an external (non cisco) application via WebService. Appreciate if anyone can help in fixing the issue. I am using 9.3.2 Patch 6.
Connectivity to an external system (a 3rd party application in my firm) was achieved via WebService using the ServiceLink module.
Used the Outbound HTTP/WS Adapter where I am sending request and receiving response (bi-direction).
Successfully constructed and passed the XML request to the WebService.
Received response from the WebService as an XML / Soap Message which is then wrapped with the <Message> tag with the channel-id attribute successfully.
Designed a XSL Transformation (For this WebService, the XSLT did not generated automatically) which, I hope is not being applied properly in CPSC; but working fine outside of CPSC when I have checked the response XML with the XSLT in an online editor (http://www.freeformatter.com/xsl-transformer.html). Everything looks perfect in this editor where I have issues in CPSC.
I am getting a Transformation exception in CPSC and the response message was unable to convert into the nsXML. The exception I am receiving is below. Not sure whether it is due to the namespace or something else..
Note: I am having this issue in this Agent/WebService alone. I have tested with couple other WebServices where I didn't have any issues in getting the response and update the field in CPSC form successfully. So, I believe that there are no issues in the parser in our server.
Exception Received:
org.xml.sax.SAXParseException: Premature end of file. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124) at com.newscale.bfw.util.XMLValidator.validate(XMLValidator.java:147) at com.newscale.is.core.MessageExecutor.processNSTaskTransportMessage(MessageExecutor.java:135) at com.newscale.is.core.MessageExecutor.processTransportMessage(MessageExecutor.java:431) at com.newscale.is.core.MessageExecutor.processSynchronousOutboundMessage(MessageExecutor.java:526) at com.newscale.is.adk.OutboundAdapterUtil.processSynchronousResponse(OutboundAdapterUtil.java:44) at com.newscale.is.adapter.http.HTTPOutboundAdapter.call(HTTPOutboundAdapter.java:190) at com.newscale.is.adapter.http.HTTPOutboundAdapter.processMessage(HTTPOutboundAdapter.java:147) at com.newscale.is.core.MessageRouter.routeMessage(MessageRouter.java:115) at com.newscale.is.core.MessageExecutor.processOutboundMessage(MessageExecutor.java:604) at com.newscale.is.core.MessageExecutor.processMessage(MessageExecutor.java:125) at com.newscale.is.core.QueueListener.handleTextMessage(QueueListener.java:91) at sun.reflect.GeneratedMethodAccessor110.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.camel.component.bean.MethodInfo.invoke(MethodInfo.java:340) at org.apache.camel.component.bean.MethodInfo$1.proceed(MethodInfo.java:237) at org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:168) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:99) at org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:73) at org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:101) at org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71) at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:115) at org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:285) at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:110) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:71) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:322) at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:213) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.UnitOfWorkProcessor.processAsync(UnitOfWorkProcessor.java:150) at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:117) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:71) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:86) at org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:105) at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:561) at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:499) at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467) at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325) at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1059) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1051) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:948) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)
Sample XML File received as response from the WebService – which then wrapped with the <message> tag along with appropriate channel-id.
<message channel-id="10a60e45-65d4-40c0-826f-1a91d2135da0">
<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<ns:ITSPResponse xmlns:ns="urn:PegaRULES:SOAP:BNYMDataITSPTest:Services">
<Output>Test IT Service Portal - 1</Output>
</ns:ITSPResponse>
</soap:Body>
</soap:Envelope>
</message>
XSL Transformation
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="
http://www.w3.org/1999/XSL/Transform" xmlns:ns="urn:PegaRULES:SOAP:BNYMDataITSPTest:Services">
<xsl:template match="/">
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns="urn:PegaRULES:SOAP:BNYMDataITSPTest:Services">
<message>
<xsl:attribute name="channel-id">
<xsl:value-of select="//@*[local-name()='channel-id']" />
</xsl:attribute>
<send-parameters>
<agent-parameter>
<name>Output</name>
<value> <xsl:value-of select="//*[local-name()='Output']" /> </value>
</agent-parameter>
</send-parameters>
</message>
</xsl:template>
</xsl:stylesheet>

The reply I got from Cisco Engineering team for this is to get the response as a soap message than XML data.
The tag should not be available in the response received. If we don't have this, the response will still consider as a valid XML / Soap message after wrapped by the tag.
If we have the tag in the response, after wrapping the tag, the format of the response will not be in good format.
Also, Cisco Engineering team has confirmed that it is not possible to remove the tag from CPSC. It should be removed by the WebService providers while sending the response.
For my case, I am consuming the WebService from a tool similar to CPSC where the entire settings has to be changed to send the response format as soap message than XML. So, we need to have another WebService as a middleware! Bad day!

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

Webservice to proxy - response back to webservice

Hello expert,
I am working on webservice to proxy scenario. When request to create purchase order received by PI thru webservice, PI will do proxy call to create purchase order in ECC and send response back.
We don't want to send ECC response back to Webservice, but we would like to send positive response back as soon as PI recieve the message irrespective of what happens in ECC.
Need some advise.
thanks.

>We don't want to send ECC response back to Webservice, but we would like to send positive response back as soon as PI recieve the message irrespective of what happens in ECC.
One way of doing is after sending request to ecc, you can code in proxy as response in the same interface with single field element like mesg receiveed and map that response to soap response on the sender side. (in this case you dont really process the soap request in ecc directly. you do it at later or convenient time or after sending success transfer message). Basically you handle logic in abap proxy side.
Mapping 1 soap request to proxy request (Per business requirement)
Mapping 2 proxy response (status : messg received ) to soap response
Rest are all same. Basically you do SOAP (sender) to PRoxy (receiver) synchronous mode
If you dont want to pass the soap request message directly to ECC and within that timeframe want to send successful mesg from pI itself then you have to design to store the mesg temporarily. What will happen if your ecc is down? How do you handle that situation.

Missing response message in Idoc - WS scenario

Hello
I 'm missing a response message in the follwing scenario:
Idoc-> XI -> Web service (SOAP)
A Matmas idoc is sent from R/3 to XI. In XI the Idoc is
mapped to a SOAP message and sent to a web service.
The Message Interface for the SOAP call is synchronous
and has a PushMaterialSoapOut and a PushMaterialSoapIn
messsage, which is defined in the WSDL from the
web service and imported into XI Repository.
Everything is working fine but I do not get the response
message. The web service has sent the response message. I
have traced the firewall logs and i have seen the
response.
What is wrong? Is it basically possible to have a
scenario like this?
The message must have arrived somewhere, since the web
server does not throw an exception. But where is it?
Thank you in advance
Thomas

Hello Stefan
>Scenarios with IDOCs are always async. Therefore you
>cannot have a response.
Ok, so I have to use BPM.
>How do you want to process the response? What should
>happen in the sender system?
I was thinking about an ALEAUD idoc which is sent back
to R/3. Therefor I have created an synchronous message
interface with the MATMAS idoc as outgoing message and an
ALEAUD as incoming message. Accordingly I have a message
mapping for the response message.
An other reaction to the response message could be to set
the message to status failed. But this is the next issue.
>In some scenarios you might use a BAPI instead of an
>IDOC for synchronous message processing, but this
>depends of many circumstance depending ofyour business
>requirement.
The process in SAP R/3 is fixed. To move to BAPI is not
an option.
Regards
Thomas

PI 7.11 process SOAP message with Attachments failed

Hello,
we have a scenario where the sender (3rd-Party) start a sync call via PI to a receiver (SAP BW system).
The receiver send a response with attachment. SAP processed the message successfully but sender could not processed message because the SOAP header do not have the attribut Content-Transfer-Encoding.
with this attribut I could tell the sender that the attachments are more then 7bit.
How to can I set this attribut into the SOAP header in the SAP PI?
Or have someone an other idee?
Thanks and regards
Martin

Have a look at at MultipartHeaderBean and MessageTransformBean at [http://help.sap.com/saphelp_nwpi711/helpdata/en/cd/5af7c0c994e24fb0d0088443513de2/frameset.htm|http://help.sap.com/saphelp_nwpi711/helpdata/en/cd/5af7c0c994e24fb0d0088443513de2/frameset.htm]
It talks about content ID, content description, content type, content disposition but it does not mention Content-Transfer-Encoding.
Regards
Asif

Error: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, 447). --- Input string was not in a correct format.

Hi All,
We have a scenario of FTP-->PI---> Webservice. While triggering the data in the FTP, it is failing in the PI with the below error
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, 447). ---> Input string was not in a correct format.
Can you please help?

Hi Raja- It seems to be a data quality issue.
Check for the value @ 1447 position in the xml message that you are trying to send to web service..
may be a date filed/decimal value which is not in expected format.

In Synch comm, what happens to response message if sender fails?

Hi All,
I have came up with the following question:
I have a synchronous scenario type: WS -> PI -> Proxy.
Lets say that the external system is able to consume the Web Service, and send the data to PI, and from there to the SAP ERP. SAP ERP starts processing the message (calling function, BAPIs, etc). During that execution the external system for some how cuts its connection (session) to the WS that PI is exposing.
What will happen then?
In SAP ERP I will have some processes that were executed, the response message will be sent back to PI, but not to the legacy system. So the data will not be consistent, as ERP was able to perform its process but the Legacy system will never know that these were done, so I will have an unbalanced scenario.
One of my questions is, will SAP ERP know that the connection between the legacy system and PI was cut, and there for ERP will stop, cancel or not perform its processes?
If the response message was sent back to PI by the ERP, but this message could not reach the legacy system. How can we let know the legacy system that ERP did all of its processes and that it should "update" their data according to the response message sent by ERP?
As we all know, we can not re-process a synchronous message. So, what will be the best way to mantaining the consistency of the DATA between the two systems (ERP - Legacy)?
Thanks and regards,
Felipe

One of my questions is, will SAP ERP know that the connection between the legacy system and
PI was cut, and there for ERP will stop, cancel or not perform its processes?
There is a possibility of triggering an alert when your Target system is down (i suppose this is what you mean when you say connection is cut)....the udf can be implemented in a mapping.....just check the blog:
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
from the blog:
We can use this code in the Exception Handler block of the try u2013 catch block of the code to
publish the JMS message, and, whenever the JMS service was down, the Exception handler block is
called and the Alert is triggered to the Operations Support team.
check if this suits your requirement
Regards,
Abhishek.

SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPT

Hi there,
I am trying to publish a file from SAP as web service using XI and SOAP Adapter.
I am using ABAP proxy to get the data into XI.
Designing and Configuration in XI has no problems because when i use File adapter the data is trasmitted to FTP server.
But when I used SOAP Reciever adapter I am getting following error in RWB
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/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Error during parsing of SOAP header.
Scenario: SAP ABAP Proxy -> XI -> WebService. Asynchronous.
SOAP Receiver adaptor.
Target URL http://<host>:<port number >/sap/xi/engine?type=entry&version=3.0&Sender.Service=SAPDC2653&Interface=urn:bzttest:00:hsa:test%5EOB_MI_BZT_TEST&QualityOfService=ExactlyOnce
Do not use SOAP Envelop is checked.
SOAP Action http://sap.com/xi/WebService/soap1.1
What i am missing here? How should I solve this problem?
Any help is appreciated,
Thx,
Yogi

Say there's a bapi/rfc that you want to call on an R/3 backend (e.g. 4.6c). On it's own, the R/3 system cannot expose the rfc/bapi as a web service, but XI can. So in this case, the scenario would be:
WS client -> XI -> R/3
When XI "exposes" a web service, it is exposing a service for a receiving system (in the above example, the R/3 system). XI itself does not provide or contain the service implementation. When XI exposes a web service, it is always done via the sender soap adapter (i.e. if soap adapter is used). Receiver soap adapter is used to call or consume an actual web service from an external application.
Regards,
Jin

Exception caught during processing mail message

I am getting the following error in CC monitoring for my sender mail adpater:
exception caught during processing mail message; java.io.IOException: invalid IMAP status response; not finding * STATUS, but 001I NO The requested item could not be found.
Please tell me how to resolve ?

NOw when i changed the protocol from IMap to POP3 the error is
exception caught during processing mail message[18]; com.sap.aii.af.mp.processor.ModuleProcessorException: Error during processing local bean: localejbs/AF_modules/MessageTransformBean caused by: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at AF_modules, the whole lookup name is localejbs/AF_modules/MessageTransformBean.

SOAP : response message contains an error Application/UNKNOWN/APPLICATION_E

Hi All,
I am working in a Proxy to SOAP synchronous scenario. Message is processing successfully through IE but i am getting the below error in receiver (SOAP) communication channel.
SOAP : response message contains an error Application/UNKNOWN/APPLICATION_ERROR.
Please suggest what will be possible way out to resolve this issue.
Thanks,
Priya Ranjan

Dear Priya
Have you configured Fault Message for this scenario.
This kind of error is generally thrown by the end target system where the message is not processed succesfully due to some error in there system.
Sourabh

WSRM Adapter replaced with soap in PO7.4. Getting error "Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error"

Hello All,
We have scenario proxy->pi->webservice. In older versions of PI system they used wsrm adapter at receiver side and it's working fine.
Receiver interface is asynchronous. So no response structute is present and receiver service is business component(since receiver is a third party).
During migration, we have replaced the receiver adapter with SOAP adapter and used message protocol as SOAP 1.1 but the message is failing and in communication channel it is showing error "Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error". In this case the receiver interface is stateless xi 3.0 compatible(re using the old), after changing it to just stateless also issue persists.
In target url field if i prefix the url with "http" then above mentioned error is occurring otherwise if i use the hostname:port/path.. then it is giving error
"soap: Call failed: com.sap.aii.af.sdk.xi.srt.BubbleException: Unsupported protocol". So maintaing the url as http://hostname:port/pat.....
As in old channel wsrm channel there is no userid and password, i haven't given any userid/pwd in receiver channel.
used the bean sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean with parameters
Module Key = soap
Parameter Name = noSOAPMakeSysErrFromResponseFault
Parameter Value = false
and
xmbws.No SOAPIgnoreStatus = true
but not successful.
Please help me. I got stcuk here.

Hello Jannus,
The connectivity is working fine. Network team has confirmed it. I doubt that any strucutre(header) difference might be present in message when sending with wsrm adapter compared to sending with soap adapter.
Please let me know the exact difference between soap and wsrm functionality in receiving end.
By considering the structure issue, i have checked the "do not use soap envelope" check box, then i got error "Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type"
Then i used message transform bean, but not successful.
Regards,
Ch.Venkat.

SOAP Receiver Response Message

I have setup the following scenario:
Create PO in EBP --> XI --> Webservice
In the Repository I have set up both the outbound and inbound message interfaces as Synchronous. The interface mapping has been setup to map both the request and response messages.
In the Directory I have set up the SOAP receiver adapter and the receiver/interface determination and receiver agreement for EBP as the sender system and the external webservice as the receiver party/service.
When I create a purchase order in EBP the webservice is called successfully and the PO gets created on the target system. The webservice returns a response message which I am expecting to see via SXMB_MONI but is not currently showing!! Is there some Directory configuration that I am missing?
Any pointers would be appreciated.
Regards
Mark Briggs

Hi Mark,
>>>>n the Repository I have set up both the outbound and inbound message interfaces as Synchronous
is your scenario sync or async?
do the ID config with ID wizzard if you're not sure
if will guide you
if you have a sync scenario you shoudl see and error
if you have no response withint the timeout
do you see that in the calling application or in the XI ?
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Processing response message in webservice

Similar Messages

Maybe you are looking for