#Protected WebService --> We have a WebService which is Protected.

RE: #Protected WebService --> We have a WebService which is Protected.

Stefan Helzle — Thu, 06 Mar 2025 07:47:48 GMT

Files in Appian cannot be directly accessed by a URL. As far as I remember, this smart service only works with externally hosted WSDL files.

RE: #Protected WebService --> We have a WebService which is Protected.

chitra_sharma — Wed, 05 Mar 2025 20:00:56 GMT

In Call Web Service node, I want to give dynamic URL value from local WSDL file so created a constant which is pointing to XML file in Appian. Now when I put this constant in Dynamic WSDL URL in Call Web Service node, I am able to get services loaded but after calling any operation gives me below error-

An error occurred while reading the WSDL [Document:12345] to create WSInvoker for the service {http://ABC2SW/MVP.asmx/}BPM and the endpoint MVPSoap. The provided URL is not a valid URL format. Please provide a correct absolute URL to the WSDL. (APNX-1-4040-001)

I understand Appian is looking for a URL and instead get constant with no protocol, tried giving file:///accdocs2/324234/324234.xml for same local XML file(got this accdocs by using getcontentobjectdetailsbyid) but services didn't load at runtime and fault says valid services are:

(just blank in last)

Thanks,

Chitra

RE: #Protected WebService --> We have a WebService which is Protected.

Stefan Helzle — Wed, 05 Mar 2025 19:42:16 GMT

I think we need a bit more detail ...

RE: #Protected WebService --> We have a WebService which is Protected.

chitra_sharma — Wed, 05 Mar 2025 18:53:15 GMT

Trying same but getting this error-

The provided URL is not a valid URL format. Please provide a correct absolute URL to the WSDL.

Any help is appreciated.

RE: #Protected WebService -->

We have a WebService which is Protected.

aneeshv — Tue, 14 May 2013 23:28:05 GMT

Just save the XML file locally on the server and point to it dynamically during the run of each process instance using Dynamic WSDL URL and a constant in that expression which points to this new local XML file.

RE: #Protected WebService -->

We have a WebService which is Protected.

moritzw — Tue, 14 May 2013 12:48:00 GMT

How did you solve it? The dynamic WSDLs have to be protected by the same username/password in order for this to work, right?

RE: #Protected WebService -->

We have a WebService which is Protected.

aneeshv — Tue, 14 May 2013 00:43:03 GMT

Ok.. Resolved this issue...

#Protected WebService --> We have a WebService which is Protected.

RE: #Protected WebService --> We have a WebService which is Protected.

RE: #Protected WebService --> We have a WebService which is Protected.

RE: #Protected WebService --> We have a WebService which is Protected.

RE: #Protected WebService --> We have a WebService which is Protected.

RE: #Protected WebService -->We have a WebService which is Protected.

RE: #Protected WebService -->We have a WebService which is Protected.

RE: #Protected WebService -->We have a WebService which is Protected.

RE: #Protected WebService -->

We have a WebService which is Protected.

RE: #Protected WebService -->

We have a WebService which is Protected.

RE: #Protected WebService -->

We have a WebService which is Protected.