on 03-06-2007 9:41 AM
Hello Guys!.
We have a WSDL definition that requires use header fields. For do this, in other forums, we see that is good, use an XSL mapping without the estandar message mapping.
The objective is:
1 - Interface begins when RFC is called in R/3 system then..
2 - Parameters TELEFONO and BODY of the RFC are passed to wsdl message called Sendmessage. We need pass header parameters too, user, account and password. This parameters not appear in this message.
Someone can help us, how can implement this using XSLT message.
Whe have now this one but, i don´t know if it´s good.
Best regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
we can send the usd and pwd with SOAP webservice URL , but it will be visible.
to avoid this we can use XSLT or JAVA .. please see the below links to get an idea..
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1442 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
Also see the below links may be useful..
See Note 856597
Troubleshooting SOAP Message - XI - /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
/people/kumar.prashant4/blog/2006/07/14/using-rfc-as-webservice-in-webdynpro
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
Regards
Chilla..
<i>Points rewarded if it is useful</i>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Julian,
If I got you correct you need to add few fields in the SOAP header when calling the webservice.
To do this,
1. In your Receiver SOAP adapter, select option "Do Not use SOAP Enevelope".
Selecting this option implies that SOAP adapter will not add its own SOAP Envelope and the output of mapping will be passed to the target system / webservice.
2. Now, use XSL or Java Mapping and create the entire SOAP message ( including the SOAP header , SOAP Body ) in your mapping as expected by the Webservice.
Java and XSL mapping does not validate the source and target message against the XSD and so you can create the payload as expected with the SOAP Header without manually creating the XSD etc.
Regards
Bhavesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
<<<<In your Receiver SOAP adapter, select option "Do Not use SOAP Enevelope".
Selecting this option implies that SOAP adapter will not add its own SOAP Envelope and the output of mapping will be passed to the target system / webservice.<<<<<
I have done exactly what has been suggested but XI is still generating the SOAP document along with the payload(my payload has SOAP envelop, header and body).
I want to supress/remove SOAP document and send only my payload to the webservice.
Does any one has any idea where it needs to be set?
Thanks in advance for your help.
Venkat
venkatmarni@gmail.com
HI Julian,
You can even refer this document which contains all related to webservice scenario.
A must to see doc to get complete Idea of webservice related scenarios
Regards
Abhi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.