SOAP Channel - ADAPTER.HTTP_EXCEPTION

Hi,
I have a receiver SOAP Channel and when i tried sending messages.
Am getting an adapter exception.
Please guide if someone has faced with the same kind of error
Thanks
Sebin
The error response is pasted below.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="HTTP">ADAPTER.HTTP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>HTTP 401 Access Denied</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
Sebin

hi
Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
Description: The request requires user authentication
Possible Tips:
Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
If the error is in Adapter Engine
then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
May be wrong password for user XIISUSER
May be wrong password for user XIAFUSER
for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message
source :: /people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
regards
Ramesh P

Similar Messages

ADAPTER.HTTP_EXCEPTION, HTTP 500 Internal Server Error, in Receiver soap A

Greetings All,
In my scenario i am calling external service of SFDC using receiver soap adapter but i am facing below error in the response.
ADAPTER.HTTP_EXCEPTION, HTTP 500 Internal Server Error
I am creating the soap structure/envelope using Java mapping since need to add additional parameter in soap header.
I am setting the URL in java UDF using parameter TServerLocation.
In comm channel checked "do not use soap envlope" also set the format to text/xml using MessageTransformBean.
The service was working fine when tested in SoapUI tool.
Looking forword for your help and will be appreciated.
Thanks,
Sandip

Hello Sandip, I hope you are doing fine!
I`m not sure if you are using a sync or async scenario...
The behavior that you describe is the expected behavior for SOAP receiver adapter in nosoap mode, asynchronous case.
The explanation that lies behind it is that in nosoap mode the bahavior is just similar to pure HTTP communication. An HTTP 4/5 error received from the target server is treated as HTTP internal error and logged into AFW as an error. The message in an asynchronous scenario without acknowledgements is normally seen as successful on IE side as it is successfully sent to the target system. It can be even successfully consumed by the target webservice, but for amo other reason, the HTTP request from SAP PI to the target system returns HTTP 500 error.
If you ask for system delivery acknowledgements, you should get a non-successful delivery acknowledgement.
In synchrnous scenarios, when a response is expected, the behavior is different.
If this is a sync scenario, there is an official patch released on the service marketplace. SAP Note 1533195 is released.
In addition to deploying the patch, apply the additional configuration steps. As per this note, for the default module
sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
you will need to set:
Module Key = soap
Parameter Name = noSOAPMakeSysErrFromResponseFault
Parameter Value = false
If you need to bypass the HTTP errors in the communication with the target system, you need to apply note 1055678.
To apply it, just add for the default module
sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean in your receiver
channel, Modules tab the following:
Module Key = soap
Parameter Name = XMBWS.NoSOAPIgnoreStatusCode
Parameter Value = false
If you need any SOAP fault related behavior or any other SOAP related feature, you should setup the channel to run normal SOAP mode, since as already mentioned nosoap mode is used now.
In addition, check note:
856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter
section "1. Sender Connection"
Q: I get a server error "500 Internal Servler Error" from the
adapter's servlet. What went wrong?
and get the trace to give you more details of the error.
One more thing, VERY IMPORTANT.
I STRONLGY recommend you to update all XI-PI components to latest patch available in the Service Marketplace. Thery are:
XITOOLS, XIESR, XIAF, XIAFC, MESSAGING, XIGUI. Some of them might not be present depending on the release of you system. e.g: 3.0, 7.0, 7.1
I hope this helps you.
Cheers
Jorge Eidelwein

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

SOAP receiver adapter configuration issue

Hi Everyone,
When I am trying to excute a sync scenario from SAP<>XI<>Webservice from Integration engine , I am getting the below error message.
Error while sending message: com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Cannot process the message because the content type 'text/xml; charset=utf-8' was not the expected type 'application/soap+xml; charset=utf-8'.
In the receiver SOAP adapter, I have configured Transformation module where I kept the MessageTransformationBean in processing sequence as a priority and also provided the module configuration.
ModuleKey: transform
ParameterName: Transform.ContentType
Parameter Value: application/soap+xml;charset=utf-8.
But still get the above error message in the communication channel. I am using certificates in my configuration that were deployed in visual Admin.
In the adapter configuration, I have just provided the Target URL, Configured User Authentication, certificate authentication and SOAP action.
Can anyone help me.. how to rectify the issue.....
Thanks in advance,
Hareen

HI Hareen,
I decided to give SOAP1.2 using the standard SOAP Adapter a try
There are a few noticeable differences between the request message of SOAP1.1 and SOAP1.2
1.) SOAP 1.1 uses a different namespace from SOAP 1.2. For SOAP 1.1 it is "http://schemas.xmlsoap.org/soap/envelope/" while for SOAP 1.2 it is "http://www.w3.org/2003/05/soap-envelope".
2.) SOAP 1.2 does not use SOAPAction in its header.
3.) Content type is also different, for SOAP 1.1 it is "text/xml" while for SOAP 1.2 it is "application/soap+xml"
So a sample request for SOAP 1.1 would be like this:
Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://sampleaction"
While for 1.2 it is:
Content-Type: application/soap+xml;charset=UTF-8;action="http://sampleaction"
The SOAP action is moved to the content type (experts please correct me on this).
Based on the differences, you need:
1.) Construct the correct SOAP Envelope for request message mapping and remove it for the response mapping
2.) Use MessageTransformBean to change content type
3.) Leave SOAPAction as blank
I think dynamic soap action is no longer possible because the action is hardcoded in the module configuration (please correct).
Hope this helps,
Mark

SOAP Header in SOAP Receiver adapter

Hi All,
I am doing a Proxy to Webservice scenario where webservice requires the SOAP request as below.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP-ENV:Header>
 <mh:CustomHeader xmlns:mh="http://schemas.test.com/customHeader">
 <mh:MessageData>
 <mh:MessageId>12345</mh:MessageId>
 <mh:Timestamp>2004-06-09T14:41:44Z</mh:Timestamp>
 </mh:MessageData>
 </mh:CustomHeader>
 <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/04/secext">
 <wsse:UsernameToken>
 <wsse:Username>test</wsse:Username>
 <wsse:Password>test123</wsse:Password>
 </wsse:UsernameToken>
 </wsse:Security>
 </SOAP-ENV:Header>
 <SOAP-ENV:Body>
 </SOAP-ENV:Body>
Need your help to understand how can we achieve this using Standard SOAP adapter to customize the Header part as it requires to include "<mh:CustomHeader " & "UsernameToken".
Or Do i need to go for adapter module development to create this SOAP request.
Please provide your suggestion to achieve this scenario.
Thanks & regards
Ashwin
Edited by: ashwin dhakne on May 17, 2010 5:32 PM

Hi all,
Created a below target payload in a message mapping with SOAP Header & Body part as per the requirement.
In SOAP receiver communication channel, checked the option " Do Not Use SOAP Envelope".
But while executing an sceanrio, i am facing an error in SOAP receiver channel as Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
And if i don't check the option " Do Not Use SOAP Envelope" it gives an error as
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Unable to obtain service binding,error=Payload Envelope is not a known message for TestWebserviceService.
Please provide your suggestions to handle this issue.
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:Envelope xmlns:ns1="http://schemas.test.com/CustomrHeader">
<ns1:Header>
<ns1:CustomrHeader>
<ns1:MessageData>
<ns1:MessageId>Constant</ns1:MessageId>
<ns1:Timestamp>Constant</ns1:Timestamp>
</ns1:MessageData>
<ns1:Security>
<ns1:UsernameToken>
<ns1:Username>Constant</ns1:Username>
<ns1:Password>Constant</ns1:Password>
</ns1:UsernameToken>
</ns1:Security>
</ns1:CustomrHeader>
</ns1:Header>
<ns1:Body>
<ns1:Details>
<ns1:Information>
<ns1:Title>Test</ns1:JobTitle>
</ns1:Information>
<ns1:Contacts>
<ns1:Street>Test Drive</ns1:Street />
</ns1:Contacts>
</ns1:Details>
</ns1:Body>
</ns1:Envelope>
Thanks
Ashwin
Edited by: ashwin dhakne on May 18, 2010 5:47 PM
Edited by: ashwin dhakne on May 18, 2010 5:48 PM
Edited by: ashwin dhakne on May 18, 2010 5:48 PM

XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION

Dear All,
My SOAP receiver communication channel in production server has the following error:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error.
I am in process of finding the root cause for the issue.
I welcome your suggestions.
Regards,
Venu V

Hi,
Yes the channel was working fine. I have contacted the target system ppl. They are saying that they did not receive any messages. To resend the messages my channel should work without errors rt then only I can process.
Does it a problem of network or issue with the WS?
Thanks & Regards,
Venu V

XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 404 Not Found

Hi,
The scenario is ECC-XI-SOAP(Asynchronous). We are getting the below mentioned error in SOAP reciver channel:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 404 Not Found
Channel Configuration:
Target URL:
http://<hostname>:<port>/bpm/com/xyzprocess/SomeIntermediateEvent?wsdl=binding&mode=ws_policy
Tried with
http://<hostname>:<port>/bpm/com/xyzprocess/SomeIntermediateEvent as well
Conversion parameters:
Checked Do Not Use Soap Envelope
Appreciate any help in this regards.
Regards,
Vishal

Can you share with us the HTTP Headers for the Request?
POST http://server/sap/xi/engine?type=entry&version=3.0&Sender.Service=BusService&Interface=http://company.com/abc/CommonAck%5EMI_CommonAck_ia HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://sap.com/xi/WebService/soap1.1"
User-Agent: Jakarta Commons-HttpClient/3.1
Host: server
Content-Length: 560
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xir="http://www.dummy.org/response/">
<soapenv:Header/>
<soapenv:Body>
<xir:responseInput>
<Id>007</Id>
<Flag>10</Flag>
</xir:responseInput>
</soapenv:Body>
</soapenv:Envelope>
You can use the MessageTransformBean to correct the content type.
Thanks for the suggestion Mark.I am using MessageTransformBean but still the same issue.
Parameter Name:Transform.ContentType
Parameter Value:text/xml;charset=utf-8
Edited by: Vishal.P.Kulkarni on Oct 17, 2011 6:27 AM
Edited by: Vishal.P.Kulkarni on Oct 17, 2011 6:29 AM

XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error

I'm getting this message in RWB when trying to send an order:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Weird thing is, other orders have been successfully to the same partner.
Is this something on my side or the receivers side?
What does HTTP 500 Internal Server Error mean and how to fix?
Thanks,
Jeff

More info on this problem:
Discovered that the HTTP 500 error only occurs when a "change" file is sent:
I send an order create file to a partner using a SOAP adapter. They receive it successfully.
I make a change to the sales order and send that file. It uses the same Config Scenario, receiver determination, receiver agreement and comm. Channel.
But this file shows an HTTP 500 error in the RWB.
I send it right after the first order create file, so no overloading is happening, etc.
Conenctivity to the url is fine because the create file went through.
I don't know what else it could be. Any other info/log in RWB to look at to help decipher the error?

Error in SOAP channel in SAP PI 7.31

Hey Experts,
We have a scenario in which we send IDOCs to our Business Partners via a SOAP channel. It is an asynchronous scenario. However, we are getting the following error:
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: apply( Message, CPALookupObject ). Message: SecurityException in method: apply( Message, CPALookupObject ). WSSEThread-Exception: SecurityException in method: run(). Message: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. To-String: com.sap.security.core.policy.exceptions.ProcessException: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. Key: 0153; To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: run(). Message: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. To-String: com.sap.security.core.policy.exceptions.ProcessException: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. Key: 0153. To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: apply( Message, CPALookupObject ). WSSEThread-Exception: SecurityException in method: run(). Message: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. To-String: com.sap.security.core.policy.exceptions.ProcessException: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. Key: 0153; To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: run(). Message: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. To-String: com.sap.security.core.policy.exceptions.ProcessException: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. Key: 0153
If anyone has some information or views to share on this, kindly do so. I have attached a screenshot for your reference.
Regards,
Pritish

Hi Jens,
Thank you very much for your prompt reply to my post. We did go through the note and since we are on Patch 11, we are not sure exactly how relevant it is to us.
However, I would be much obliged if you could clear up one thing. We are using an SOAP adapter to send IDOCs, and the note that you have advocated pertains to an IDOC adapter.
Will the note still be able to help?
Regards,
Pritish

Use of variable header XHeaderName1 in SOAP sender adapter

Hi all,
I have a doubt regarding the use of adapter-specific attributes in SOAP sender adapter. In specific:
the SOAP client should be able to pass a variable with the SOAP request (XHeaderName1 header variable) and this should be available in mapping (Dynamic configuration)
I've already checked the [help page|http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm] but it seems I'm doing something wrong.
I tried with those settings in SOAP adapter configuration:
Keep headers checked
XHeaderName1 = Test
I try to call the SOAP adapters in the following 2 ways, but none works (the value is not available in message mapping with Dynamic configuration)
1. Pass "Test" value xxxx in SOAP Header as a tag
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <SOAP-ENV:Header>
 *<Test>xxxx</Test>*
 </SOAP-ENV:Header>
 <SOAP-ENV:Body>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
2. Pass "Test" value xxxx in SOAP URL
http://host:50000/XISOAPAdapter/MessageServlet?channel=p:s:c&version=3.0&Sender.Service=...&Interface=...&Test=xxxx
Could anyone give me a hint about how to pass those values in the SOAP call and eventually the correct config. of SOAP sender ?
Thanks a lot,
Manuel

Hi Manuel,
Could you give a bit more detail on how you handled the SOAP message yourself.
I have a similar issue. I am consuming a non SAP Web Service which requires a non-standard token element to be passed back. I have created a an RFC sender to SOAP reciever scenario which works fine for the inital logon and returns the token it expects in the follow up messages.
At present I'm at a loss so your help would be much appreciated. We have got round the immediate issue by creating and sending the SOAP message directly from SAP WAS.
Could we use the XI Adapter and ABAP proxy in a similar way?
Thanks,
Tim J.

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 while passing URL Dynamically in SOAP AXIS adapter..!!

Hi ,
Idoc> XI>SOAP-AXIS
I am doing a scenario where I need to pass the URL dynamically in SOAP-AXIS adapter by taking the RCVPRN of Idoc.
If
RCVPRN = 100 , message has to go to http://10.190.25.16:8210/file/receiver
RCVPRN = 200 , message has to go to http://10.190.25.16:8210/file/receiver2
RCVPRN = 300 , message has to go to http://10.190.25.16:8210/file/receiver3
I used the below UDF and it is working correctly and generating the URL dynamically .
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey keyHeader1 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/SOAP", "TServerLocation");
conf.put(keyHeader1, a);
return "";
The value is coming in SOAP document as expected like below.
<sap:DynamicConfiguration xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:Record namespace="http://sap.com/xi/XI/System/SOAP" name="TServerLocation">http://10.190.25.16:8210/file/receiver3</sap:Record>
</sap:DynamicConfiguration>
I used the below Configuration modules in receiver SOAP-AXIS adapter as suggested in Note 1028961.
AF_Adapters/axis/AFAdapterBean ---> afreq
AF_Adapters/axis/HandlerBean ---> xireq
AF_Adapters/axis/HandlerBean ---> dc
AF_Adapters/axis/HandlerBean ---> remover
AF_Adapters/axis/HandlerBean ---> trp
AF_Adapters/axis/HandlerBean ---> xires
AF_Adapters/axis/AFAdapterBean ---> afres
xireq -> handler.type-> java:com.sap.aii.axis.xi.XI30OutboundHandler
dc -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
dc ---> key.1 ---> write http://sap.com/xi/XI/System/SOAP TServerLocation
dc ---> location.1 ---> context
dc ---> value.1 ---> transport.url
remover ---> handler.type ---> java:com.sap.aii.axis.soap.HeaderRemovalHandler
remover ---> namespace ---> http://sap.com/xi/XI/Message/30
trp ---> handler.type ---> java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
trp ---> module.pivot ---> true
xires ---> handler.type ---> java:com.sap.aii.axis.xi.XI30OutboundHandler
and I am getting the below error in SOAP-AXIS channel at the point java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender.
2009-03-02 15:23:44 Success Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
2009-03-02 15:23:45 Error Axis: error in invocation: (500)internal server error
2009-03-02 15:23:45 Error MP: Exception caught with cause (500)internal server error
2009-03-02 15:23:45 Error Exception caught by adapter framework: (500)internal server error
2009-03-02 15:23:46 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: (500)internal server error: (500)internal server error.
2009-03-02 15:23:46 Error The message status set to NDLV.
Kindly let me know if anyone has any idea what might be wrong?
Note : The given URL is correct one because I cross checked by passing them normally by giving directly in adapter and they are all working and the message is going to receiver.
Thanks
Deepthi

Hi Stefan,
>> dc -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
>> dc ---> key.1 ---> write http://sap.com/xi/XI/System/SOAP TServerLocation
>> dc ---> location.1 ---> context
>> dc ---> value.1 ---> transport.url
>> Try read instead of write
When I tried with this, I am getting the below error "Connection refused ".
Success Axis: entering HandlerBean
Success Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
Error Axis: error in invocation: java.net.ConnectException: Connection refused
Error MP: Exception caught with cause java.net.ConnectException: Connection refused
Error Exception caught by adapter framework: ; nested exception is: java.net.ConnectException: Connection refused
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: ; nested exception is: java.net.ConnectException: Connection refused: java.net.ConnectException: Connection refused.
Success The message status set to WAIT.
It is going successfully when I tried sending directly. Looks like Dynamic Configuration is not working for SOAP-AXIS.
Any Suggestion?
Thanks
Deepthi.

Target URL in the Receiver SOAP channel in PI 7.11

Hi
I have designed integrated Configuration in PI 7.11 and i have SOAP sender and SOAP receiver. SOAP sender is fine but for SOAP receiver i have an issue with the target URL that i selected.
Initially the receiver was ABAP proxy with HTTP connection as we dont have ABAP related adapters in AAE i used SOAP. But i have used the same URL that is the Target host configured in the HTTP ABAP connection to the target system. Then i am getting the following error at the receiver comm channel
Message processing failed. Cause: com.sap.aii.af.sdk.xi.util.URI$MalformedURIException: no scheme
I am sure i am doing a mistake, the URL i am using is wrong as it is not meant for SOAP calls. Please suggest me what needs to be done here.

..I am sure i am doing a mistake, the URL i am using is wrong as it is not meant for SOAP calls. Please suggest me what needs >>to be done here
You are using Integrated configuration with PI 7.1 EHP1 version. That means SOAP supports as PI native protocol (XI) for PROXY scenario. So, you have to create soap receiver adapter and choose message protocol as XI.
Integrated configuration occurs in java stack engine and XI adapter(proxy) not exists there. Only if you do classical processing (IE) then you can use XI adapter at the receiver side. Thats the reason you dont find XI adapter in the integrated configuration.
Hope I answered your question

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 Channel - ADAPTER.HTTP_EXCEPTION

Similar Messages

Maybe you are looking for