Hi, We are using the call web service node to plug in to a third par

David Williams over 7 years ago

Hi,

We are using the call web service node to plug in to a third party web service. We have used this hundreds of times internally with no issue as we have access to the wsdl location to then browse the operations to invoke.

The issue is the third party does not want to expose the wsdl, and at the very least will only make it available temporarily to allow us to browse to it, select the operation, map the inputs and outputs and then hide the wsdl from view again.

The service will still be available, just the wsdl "hidden". The reasons for this are is it against security best practice for the supplier.

So here is my question, what impact could this have on the node running? ... Would it even have an impact? As long as we can map to it initially, is that enough for the node to run as required?

Thanks, David.

Discussion posts and replies are publicly visible

0 Tom Ryan
Appian Employee
over 7 years ago

AFAIK, normally you need to have the WSDL accessible at runtime. Depending on your requirements I think you can resolve this using the Advanced Web Service node:

forum.appian.com/.../Advanced_Web_Service_Configuration.html
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mike Cichy
Appian Employee
over 7 years ago

This is certainly an unusual situation where the WSDL, which is the contract between client and provider of the service is obfuscated from view.
The WSDL is cached for a short period of time but you will need access to it daily to refresh the cache. Can you host the wsdl yourself elsewhere? The location of the wsdl does not have to be the same as the endpoint, so as long as you have access to it, the node will work just fine.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel