on 02-20-2012 10:03 AM
Hi Experts,
we have scenario Proxy to SOAP for this inteface is it possible to provide the webservice from PI side.
if yes please let me know the steps.
i know the process how to provide the webservice when the SOAP adapter at sender side.
1) through sender agreement---->Display WSDL.
2) Tools---->Disply WSDL
is it poassible to provide the webservice when SOAP adapter at receiver end by using 2 nd process?
HI
is it poassible to provide the webservice when SOAP adapter at receiver end by using 2 nd process?
You have to invoke the Webservice as described with the targetURL and SOAPACTION where you speify what kind of service is required .
Regards,
Krishna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
we have scenario Proxy to SOAP for this inteface is it possible to provide the webservice from PI side.
if yes please let me know the steps.
i know the process how to provide the webservice when the SOAP adapter at sender side.
1) through sender agreement---->Display WSDL.
2) Tools---->Disply WSDL -
> yes that is possiable for only sender side as webservice because sender always consumer
is it poassible to provide the webservice when SOAP adapter at receiver end by using 2 nd process?
No that is not possiable to import WSDl File In receiver agreement because receiver always Provider .
in ESR:
wsdl file ll be imported in External defination as external message.
in ID:
in receiver Comm.channel -> call the soap URL and Soap Action(not manadatary)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
In case of "* to SOAP" scenarios, PI is the web service consumer, not the server. This means that it does not provide the .wsdl. Instead, you should receive the .wsdl file from a 3rd party responsible for the receiver system. Then you import this .wsdl file into ESR as External Definition, then use it to create Service Interface, Message Mapping and similar, like normally. And in Integration Directory, you need to provide the target URL and SOAP Action in the receiver Communication Channel.
Hope this helps,
Greg
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.