SOAP Service call Issue

Question

Hello, I am currently trying to make SOAP call to Oracle Right Now(ORN) Enterprise. ORN provides WSDL however I was not able to connect to the WSDL via Web Service smart node, getting 'An error occurred while processing the WSDL . It may not be a valid WSDL 1.1 document. (APNX-1-4041-002)'. tried with third party SOAP test tool and it worked. I am guessing the WSDL is currently not supported by Appian. Is there an another way to make SOAP call other than Web service smart node? I was looking into 'Send HTTP Request Plug-in' plug in. The plug in description says it supports to send SOAP XML to a Web Service but didn't provide further instructions. If someone can provide more high level details implementation direction or any other approach that I can try, I would really appreciated. FYI, the following is the example SOAP XML provided ORN for the operation I want to use. IncidentResponse001.xml admin123 Overheating of the device Email Thank you for reaching out! bob@example.com

Josh · Answer

Sure. The National Weather Service has some information accessible via a SOAP protocol: The WSDL is When you load the endpoint into SOAPUI, you get a list of available services. The one I used is LatLonListZipcode. Here is the sample request: 20191 and the response:

38.9521,-77.3452

Copying and pasting the request into Appian we have:

eric.jun@bitsinglass.com · Answer

HI Josh, My SOAP call is working correctly now, It didn't work first so I thought it was because of WS security header so I was looking into WS related appian function such as wsConfig(). It turns out I wasn't using correct 'soapAction' value. Once I have correct header it did work. Your direction was very very helpful. Thank you very much. The step I followed; 1. Tried to use Web Service smart node, when I test connection WSDL URL, it did throw out not a valid WSDL error message. 2. Use SOAP UI to load WSDL and select the operation that i want to user. Set required values and test the operation and confirmed it was working in SOAP UI. 3. While SOAP UI testing, it did not required any header. 3. Copy the XML from SOAP UI and tested in Appian without header and it failed. 4. Added soapAction and content-Type header configuration it's working as expected. FYI, I tested with 'Web And XML Extensions' Plug in and tested it in SAIL as well and confirmed it's working in SAIL as well. load( local!endpoint: " payoneer--upgrade.custhelp.com/.../soap", /* the SOAP envelope */ local!Body: " IncidentResponse001.xml YOURUSERNAME This Incident for email testing E Email This is mail Header for testing E This is test email body E ", local!misResponse: httppostwithresponse( endpoint: local!endpoint, paramNames: {}, paramValues: {}, headerNames: {"soapAction","Content-Type"}, headerValues: {"SendIncidentResponse","text/xml;charset=UTF-8"}, body: local!Body, user: "appian_client", password: "de@vGpp1h4tAn", domain: null, timeout: 25, proxyHost: null, proxyPort: null, socketTimeout: 25 ), { a!paragraphField( readOnly: true, value: local!misResponse ) } )

Josh · Answer

Hi eric.jun@bitsinglass.com 
 
You can usually use the HTTP Request route for WSDL's that Appian can't handle. I have done this a few times when the WSDL contained types that Appian did not like. 
 
The easiest way to go about this is to load your WSDL into SOAPUI or another application meant for testing services. You can pull out the raw XML request body from SOAPUI and throw that into the body input of the Send HTTP Request plug-in.