on 05-13-2011 6:41 AM
is there miltiple operations possiable in webservice to webservice scenario in pi?
if possiable , can u exaplain .
thanks for help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Yes it is possible to have multiple operations in a webservice hosted by PI.
Create a service interface in PI with multiple operations and for each operation, choose a different message type or external defintion.
Regards
Monika
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Solasu
Agreed you will have only one service interface.
You will have different message mappina and hence different operation mapping for each operation.
Next in ID, while creating interface determination use all such operation mappings for each operation. Create all other ID object using service interface only.
Regards
Monika
yes but i am asking about Receiver aggrement, If we use multiple operations for web service then, that many receiver communication channles must be created bcoz, we have to give SOAP Action for each communication channel for each operation.So, while creating receiver agreement, it takes the combination of sender, receiver service interface of receiver only one right. So, how it is possible.Do u have any idea?
Dear Solasu
We have similar scneario with my client.
Only in case of Soap Adapter you will have the need of multiple actions. This is also possible by using a udf which will dynamically detemine the soap action. You need to ensure in this case that the input should have criteria by which we are able to identify which action to invoke.
Else in this case even after creating multiple operations you will not get benefit. If you have proxy receiver it had worked
Regards
Monika
User | Count |
---|---|
85 | |
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.