on 02-20-2006 3:09 PM
Hi all,
Im trying to configure a Web Service scenario. I have few messages interfaces in this scenario, so my doubt is: I need publish one wsdl per message interface? If I put an asterisk (*) in wsdl interface name it assumes that is for all interfaces that I have in XI?
With adapters I need to create a sender soap adapter per message interface too? Im asking this because when I try to define a sender soap adapter, I have a Default Interface Namespace and Default Interface name to fill
Thanks in advance,
Ricardo.
> Im trying to configure a Web Service scenario. I
> have few messages interfaces in this scenario, so my
> doubt is: I need publish one wsdl per message
> interface? If I put an asterisk (*) in wsdl interface
> name it assumes that is for all interfaces that I
> have in XI?
I was wondering the same few days ago. I would just try, it can't hurt, though my 6th sense tells me it won't work
> With adapters I need to create a sender soap adapter
> per message interface too? Im asking this because
> when I try to define a sender soap adapter, I have a
> Default Interface Namespace and Default Interface
> name to fill
Default is for when no Interface nor NS are specified by the sender. You'll have for sure many Sender Agr. Making many CC it's up to you, but it could be more accurate for monitoring.
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ricardo -
You can have the client dynamically set the interface name and namespace and override the default. Please check Note 856597 - SOAP Adapter FAQ. Relevant portion below:
<i>Q: Can I set the interface name dynamically from the client?
Yes. You can overwrite these XI parameters from the client. To activate this overwriting mode, you need to turn on option "Use Encoded Header" and "Use Query String" in the channel. Then your client can append the interface name using parameter Interface.
For example, interface namespace http://sap.com/test and interface Test can be represented by the url-encoded form of http://sap.com/test^Test as in
#&version=3.0&Interface=http%3A%2F%2Fsap.com%2Ftest%5ETest</i>
Regards,
Jin
Hi Ricardo,
Please have a look at these threads..
/people/kevin.liu/blog/2004/06/28/a-note-on-wsdl-and-xsd-imports
/people/kevin.liu/blog/2005/10/07/a-note-on-wsdl-and-xsd-imports--part-ii
regards,
Prashanth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.