Hello Appian practitioners,
Following the notes from this discussion,
I tried creating a WEB-API to load a locally available WSDL within the 'Call Web Service' smart service.
My web-api returns the following httpResponse
a!httpResponse( /* * Set an HTTP header that tells the client that the body of the response * will be a CSV attachment. */ headers: { a!httpHeader( name: "Content-Disposition", value: "attachment; filename=" & char(34) & local!username & ".xml" & char(34) ) }, /* * Create a CSV value of 'local!user' and place it in the response body. */ body: rule!TS_test_ProfileXML() /* XML Contents */ )
However, the call web-service is still not able to detect the WSDL.
Appreciate all your help!
Discussion posts and replies are publicly visible
I never did this, as it might become a problem over time in case the password needs to be changed.
Did you try to set the content type header to "text/xml" and remove the Content-Disposition header?
Yes, I did try adding the content-type and removing content-disposition, but without success.
Would you recommend any other way of consuming the local wsdl file?
Did you test your API using Postman or SoapUI?
AFAIK there is no simple way to use a local WSDL.
The original WSDL is hosted on an internal server connected via VPN.
All I want to do is to change the soap address location to the latest server and call the new SOAP WSDL.
Any idea if I can do that using Appian's WEB-API? Or shall I host the XML on a different server?
Hi Stefan,
I have seen your older discussion here where you've recommended using Web-api. If possible, can you share a sample code with me?