WSDL/SOAP Connection via Process Model or webservicequery() Not Functioning

Hi, all.

We're attempting to establish a connection to an external system from Appian using a WSDL/SOAP endpoint with basic authentication. We are following the process outlined here:

https://docs.appian.com/suite/help/22.1/Choosing_the_Right_Type_of_Integration.html#appian-initiates-the-interactions-with-another-system

Our first attempt via the process model and the Call Web Service Smart Service was partially successful.

We were able to put our endpoint in and choose from the available services, so some limited contact was made; however, once the service was selected and the appropriate variables automatically created, running the process model caused the process to hang on the Call Web Service node, producing no error messages or feedback of any kind and populating no local variables.

Our second attempt via an expression rule and webservicequery() produced similar results, but upon testing it timed out after the service and parameters had been specified.  If we put in an incorrect service it does advise that this service is not available and lists the ones that are, so again, it makes limited initial contact.

In either situation it does not appear to reach the point of authentication, but we tested our credentials, endpoint and services in SoapUI and received a successful response, so both credentials and external service are functioning.

Any ideas what might be blocking this WSDL/SOAP connection? 

  Discussion posts and replies are publicly visible

Parents Reply Children
No Data