SOAP reciever adapter problem

Hi,
I am getting below error in the adapter monitor for my SOAP recv adapter.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException
This is using external definition. I ported my PI 7.0 content to PI 7.1. I am wondering how external definitions and interfaces will effect with the setting of software component verion " use of interface objects"
Do I need to put as SAP netweaver 7.0 since it is PI 7.0 content.
Can I change this setting any time. How this will effect.
I could not see this adapter error in my 7.0 env. And not in 7.1 SP04.
is there anything i should check here to avoid this error.
Thanks,
Srinivasa

Hey,
> I am wondering how external definitions and interfaces will effect with the setting of software component verion " use of >interface objects"
No, If so Mapping might have failed,
>Do I need to put as SAP netweaver 7.0 since it is PI 7.0 content.
It is good to have latest one
>Can I change this setting any time. How this will effect.
Sure, You can, After upgrade do a Regression Testing.
Cheers
Agasthuri

Similar Messages

Error in Soap Reciever Adapter?

Hi all
Please do suggest resolution of this error in SOAP Reciever adapter
2006-07-04 04:50:47 Error SOAP: error occured: java.io.IOException: invalid content type for SOAP: TEXT/HTML
2006-07-04 04:50:47 Error Exception caught by adapter framework: invalid content type for SOAP: TEXT/HTML
2006-07-04 04:50:47 Error Delivery of the message to the application using connection AFW failed, due to: invalid content type for SOAP: TEXT/HTML.
with regards
subrato kundu

Hi,
Please look at this thread:
DeliveryException:: invalid content type for SOAP: TEXT/HTML
Regards
Vijaya

SOAP Axis adapter - problem with XML formatting

Hello All,
We are using SOAP Axis adapter on our scenario (because of NTLM authenticatiom) and faced a problem that some module in a module chain is pretty-formatting XML message (inserting newlines and spaces).
Receiving WebService is REALLY strict on format and doesn't allow spaces and newlines between XML elements.
Formatting is for sure done already in adapter as in sxmb_moni message is still one-liner.
After different tests this formatting is most likely done by XI30OutboundHandler.
Are there any parameters to prevent this formatting?
If there are no parameters, than maybe there is a standard module to remove this XML indentation?
Where I can found source code for XI30OutboundHandler to check how it is extracting payload from XI message?
Thanks in advance for your answers!
Best Regards,
Artsiom Anichenka

Hi, have you find a solution for this problem?
I've tried set the parameter “disablePrettyXML”, as mentioned in SAP note 1039369 (search for “disabling pretty XML”), but apparently it didn’t work too. Have you tried that?
I still get linefeeds and carriage return in the post requisition to the WebService.
Regards,
Ronaldo Schork.

SOAP REC ADAPTER PROBLEM

Hi Experts,
we are receiving following message from SOAP receiver adapter. Can anyone asisst me?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Missing faultcode; HTTP 200 OK</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Kind Regards,
PM

Hi,
have you seen below thread,
xi adapter framework
please go through below blog,
Http* Errors in XI
regards,
ganesh.

SOAP Receiver Adapter problem (client certificate required)

My Scenario is similar to described in https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3721. [original link is broken] [original link is broken] [original link is broken] I have two PI servers running on one machine. I am trying to post message HTTPS with Client authentication via SOAP adapter from one PI system to SOAP adapter of other PI server. I have done the following configuration.
PI Server AXD - (Client) - Receiver SOAP adapter
PI Server AXQ - (Server) - Sender SOAP Adapter.
Steps in AXD
1. I have created a certificate of AXD in the service_ssl view of key storage.
2. I have imported the AXQ public certificate in to AXD in the TrustedCAs of Key storage
Steps in AXQ
1. I have created a certificate of AXQ in the service_ssl view of key storage.
2. I have imported the AXD public certificate in to AXQ in the TrustedCAs of Key storage.
3. I have created a user in AXQ and assigned the certificate of AXD under usermangement in Security provider to this user.
4. I have added the AXD certificate under Client Authentication tab with require client certificate option checked in the SSL Provider.
5. I have assigned the user created in AXQ in the step above to the Sender Agreement.
Now when I post message from AXD with Configure Client Authentication checked (Here I have selected the certificate of AXD and view as service_ssl) I am getting the following error.
Exception caught by adapter framework: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - java.security.AccessControlException: client certificate required at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:884) at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3
Any pointer to solve this problem is highly appreciated.
Thanks
Abinash

Hi Hemant,
I have couple of questions. Why do we need to import certificate for SOAP WS-Security and from where I can get it?
As far as my scenario goes I am not using message level security.
Secondly what do you mean by TRUSTED/WebServiceSecurity? I don't see any such view inside the Key Storage. I can see a view named just WebServiceSecuity though.
Also I don't have a decentralized adapter installation rather I have two separate PI instances having their own central adapter engine.
Abinash

SOAP Receiver Adapter problem

Hi guys,
I have problem with ABAP Proxy->XI->SOAP scenario. I send data from R/3 via Proxy. I see in the monitor, that message has been processed successfully, however, the SOAP adapter does not send this message to the target. I tried to run a listener on on my local machine on port 80 and sent data from SAP. Again, in monitor successful, but no action in the listener - the message did not arrive. (the adapter was set up to send data to ma local PC). The scenario is async.
Any idea, what could be wrong?
In the receiver SOAP adapter - hoe to set up Target URL? http://<machine>:<port> or w/o port and it is automatically sent to port 80?
Thanx for answers!
Olain.

Hi guys, thanx for answers..
All the systems are in the local network, so no proxy is there. However, in the communication channel monitoring I get error: connection timed out , can be due to invalid adress.. However, If i try to reach the WS from the SOAPui tool, this web service works...
Any other idea?
Olian

Soap Receiver Adapter problem. very urgent..

Hi,
When I am sending data from XI to CRM through soap receiver communication channel I am getting error:
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: Authority check failed
Pls advice urgent.
Regards

Hi Rick,
At fist did you create SOAP fault message mapping in your scenario?
If not then plz do that.
Some links for ur help:
Troubleshooting - RFC and SOAP scenarios *** Updated on 20/04/2009 *** - have a look into this to troubleshoot your SOAP
Fault Message Types - A Demo (Part 1)
Receiver SOAP adapter scenarios:
RFC -> XI -> WebService - A Complete Walkthrough (Part 1)
RFC -> XI -> WebService - A Complete Walkthrough (Part 2)
Regards,
Vinod.

SOAP reciever adapter user authentication

Hi,
I have configured SOAP receiver communication channel using User authentication.
How I can confirm that these credentials are being sent out.
Please let me now where to check these in XI?

Thank You both for your replies.
I observed two things
1) I selected adapter engine in Message Monitoring, in Audit log, it shows
Adapter Framework caught exception: null and the message failed with System Error.
but on Integration Engine it shows all messges are succesfsul
2) I have installed TCP Gateway on my PC, and created two connections with two different port numbers namely 50081, 50082.
In my receiver SOAP channel, I have given URL as http://local PC ip address:50081
When I send message from R3 system it reached XI and messages shows successful in moni,. but I could not see any in TCP Gateway.
Is there anything Iam missing,
Edited by: Vamsi on Jul 9, 2009 3:52 PM

Single SOAP receiver adapter for multiple interfaces

Hi,
I have to send multiple interfaces like Vendor, Customer, Material to one receiver.
I want to configure only one communication channel (receiver SOAP adapter) to send all these interfaces. Is this possible?
Currently I am provided with different URLs from the receiver system as below.
http://host:port/Services/Vendor.wsdl
http://host:port/Services/customer.wsdl
http://host:port/ServicesMaterial.wsdl
I will be having 3 Sender agreement, 3 receiver determination, 3 interface determination and 3 Receiver agreement.
I want only one SOAP reciever adapter which goes inside all the above 3 Receiver agreement.
So When I give the target url as http://host:port/Services, the messages fail.
But When I specify the full targert url in the adapter as http://host:port/Services/Vendor.wsdl then it works.
Which means I would have to create as many communication channel as interfaces.
Is there a work around for this?

hi kantheri,
For this, we have to fill the TargetURL and the SOAPAction in Receiver Communication channel dynamically.
So, we need to write UDF in Message Mappings using DynamicConfiguration to fill the TargetURL and the SOAPAction Dynamically.
DynamicConfigurationKey keyURL = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","THeaderSOAPACTION");
DynamicConfigurationKey targetURL=DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","TServerLocation");
// access dynamic configuration
DynamicConfiguration conf = (DynamicConfiguration) container
.getTransformationParameters()
.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
conf.put(keyURL,"Soap action");
conf.put(targetURL,"target url");
return "";
In this UDF, we are filling the TargetURL in u201CTServerLocationu201D message attribute and SOAPAction in u201CTHeaderSOAPActionu201D message attribute.
So, whenever we execute this corresponding operation these values will be filled in receiver communication channel at runtime.
TargetURL- Give some dummy URL or http://
SOAPAction - *
regards,
ganesh.

SOAP reciever channel inactive

I have a SOAP reciever adapter but in RWB communication channel monitoring it shows tobe "Started but inactive"
Can anyone suggest any possible reason and solution

Hi,
please have a look here:
SOAP Adapter Started but not active
Regards
Patrick

Problem with Dynamic Configuration 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 SNDPRN of Idoc.
If SNDPRN = 100 , message has to go to http://10.190.25.16:8210/file/receiver
   SNDPRN = 200 , message has to go to http://20.180.26.16:8210/file/receiver
It is working correctly when I tried for single receiver. When I' tried to use DynamicConfiguration, it is coming in SOAP document but it is not working and not passing to correct channel. According to this note 1039369, I mentioned the following modules.
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
Error Axis:    error in invocation: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Error MP:     Exception caught with cause java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Error           Exception caught by adapter framework: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
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: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Kindly let me know if anyone has any idea what might be wrong?
Thanks
Deepthi

I have a similar problem. I also like to add some header fields to my message und that's way I'm trying to use the AXIS adapter. (Axis adapter FAQ question 30) Unfortunately I'm getting exactly the same error message:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Deepthi, you wrote that you have missed one jar file. Can you remember which file it was?

Problem to invoke SOAP Sender Adapter

Hi,
i've got a problem to invoke the SOAP sender adapter. The returned exception says:
"Some of the IS access information is not available. SLDAcess property may be set to true, but SLD is not available."
I can access the SLD web client and I have also refreshed the SLD runtime cache. The J2EE engine had a shutdown due to an "out of memory error", could it be that some things have become upside down there?
Regards,
Heiko

hi,
restart your j2ee server and try again.
naveen

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

Receiver SOAP adapter problem

Hi,
I am getting the following error in moni when i try to consume a webservice. Even SOAP scenarios that were working fine before also are throwing the same error.I have checked some threads regarding the same error and did as mentioned in the same, but of no use. I executed that webservice alone and it is working fine. Any help on this will be appreciated.
<?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>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/PLAIN</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Regards,
Sudheer.

Hi Sudheer,
Let me confirm again...From XI , you are making a SOAP call using the SOAP receiver adapter..right ?
If that is the case and you are telling sometimes it works and sometimes it doesnot, it indicates the SOAP service you are invoking from XI due to some reason is sending back non-soap response...
we had encountered scenarios couple of time like this because the user we were using to execute the SOAP call had expired and the SOAP service was returning and HTTP-UNauthorized message back and then in MONI it would show up as the same error as what your are getting.
To check this, (the request/response going back and forth), in my earlier post i suggested using the TCP gateway...
Thanks.

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.

SOAP reciever adapter problem

Similar Messages

Maybe you are looking for