on 06-23-2016 4:33 PM
First, I'm relatively new to PI and I'm sure there is an easy way to deal with this. I have to interact with a web service and of course every message is wrapped in a namespace:Envelope. If I define a message type for both the request and the response they are both going to be Envelope but have different schemas. Since the message type has to have the name match the top element, this means I have to have two different Envelopes and that isn't allowed. How do I get around this? Seems like there should be a way to use a message type with a name different that what will be in the actual XML.
So I do have to add authentication in the header (it's specific to the web service). Knowing that, if I understand the responses, I do need to include the header in my data type and I would assume also, turn off soap headers in my channel? This sound right?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Carlton!
In general, when you design message types in PI or import external definitions for third party web services you don't use Envelope tag in it.
Regards, Evgeniy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Carlton,
The best practice is to create/define the message type inside the soap:Body. The envelope can be added via xslt/java mapping and should only be done if you need something on the soap:Header.
Regards,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Carlton,
The target is a Webservice and does it require authentication on the basis of soap header?
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 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.