Web Service Sender

The Web Service Sender submits messages to an external HTTP-based web service. QIE supports five kinds: REST (content encoded), REST (URL encoded), SOAP, Google Cloud Healthcare API, and DICOMweb. Each is tied to a corresponding Web Service Connection. Define the connection first, then select it here. The configuration fields below change based on the connection type.

TLS / certificates

TLS configuration for HTTPS endpoints (including client-authenticated TLS) lives on the Web Service Connection, not on the sender. Configure it once on the connection and every sender that uses the connection inherits it.

Setting up the sender

• Connection covers selecting the web service connection the sender uses.
• REST Web Service Functions, the URL, method, headers, and body fields shared by the REST senders.
• Inspecting requests and responses covers seeing what QIE actually sent and received.

The sender types

• REST (Content Encoded) Sender posts the message as the request body.
• REST (URL Encoded) Function sends values as URL-encoded parameters.
• SOAP Sender submits a SOAP envelope to a WSDL-described service.
• Google Cloud Healthcare API Sender submits to a Google Cloud Healthcare datastore.
• DICOMweb Sender submits studies over DICOMweb using STOW-RS and the related transactions.