Advanced Call Web Service

Overview

This plug-in provides functions and smart services for connecting to SOAP-based web services. Where possible it is recommended to utilize the out of the box functionality.

Key Features & Functionality

The Advanced Call Web Service provides support for the following:

  • Support for SOAP attachments
  • Support for Base64 attachments
  • Ability to call web services that do not explicitly declare the requirement for WS-Security UsernameToken in the WSDL policy
  • Ability to call web services that use a self-signed SSL certificate

The attachment provided with the download provides more information and examples. Where possible, use the base product Call Web Service functionality instead.

Anonymous
  • Hi, 

    We are trying to make a call to a SOAP service that requires a signing certificate to be included. We are having problems with the connection, and would like to be able to retrieve the entire call. Does anyone know if there is a way to capture it?

    Thanks!

  • Hello sylvain.furt,

    First of all thank you very much for the development of this plugin.

    On the other hand, we are trying to make a signed request with your plugin but we get a 403 Forbidden, do you know if we can somehow enable a log, or could you tell us how we can get the call we are making?

    Thank you,
    Best regards

  • Hi,

    While trying to access a URL via API, i am getting a status code of 301. When i try to access the same via a browser using the developer tools, i am getting a status code of 200 meaning its a success. Can i please get some suggestions on the same?

    Thanks

  • Per plugin documentation, you should be able to specify the "sslProtocol" property to use TLSv1.2.

  • Hi!,

    I have the same question. Is it possible to make it compatible?

    Thanks!

  • Hi!

    Is it possible to make this compatible with Appian 21.3? (given the base product's removal of TLS1 and TLS1.1 protocols)

    Thanks!

  • Hi,

    In Appian cloud environment  Im using the advanced web service call and the web service end-point WSDL and XSD imports were failing to load due to some network  infrastructure issues.   

    I had to resort to  using Appian OOTB Call Web Service smart service in test process model to isolate root cause analysis because all the advanced web service code is just logging off the root message from exception call stack which results in generic "HTTP transport error: java.net.ConnectException: Connection timed out" message.   For reference we had to use this plugin because web service WSDL / message definitions contain unsupported XSD schema types so we are hand building the XML message requests

    For future support issue trouble shooting I was wondering if anyone knows where in Appian cloud environments the full exception stack might already be logged (I didn't see anything in  tomcat std out log file) or if there is some log configuration changes which I can request of  cloud support team to get them captured.

    Thanks.

    Bob 

  • Hi, 

    Has anyone used the advanced service endpoint smart service where ssl/certifcates are required?   In a cloud Appian environment do I just use the admin console certificates feature  to import certificate or us keystoreDocument & keystoreSystemKey service authentication inputs required.  If latter am I understanding documentation correctly that I need to create a key store with certificate and upload as document to appian cloud environment?

    Thanks.   

  • hello,

    is there a way to define a custom content-type for soap attachments? This plugins uses application/octet-stream by default, but I need to change it in application/pdf.
    Thanks in advance for your time and for support.

    Best regards

    Stefano

  • 'Manually' setting the data for HTTP Basic Authorization in the HTTP Headers input worked. For some reason, I still have to set 'USERNAME_TOKEN_PLAIN_PASSWORD' and use a key otherwise I get a java runtime exception (  java.lang.RuntimeException: Invalid username token configuration provided' ), but it is at least a working solution until something better is found.
    Thank you for the support.