Loading...
Loading...
| Option Name | Description |
|---|---|
| Use Default WSDL | If enabled, will use standard WSDL and operations. To use custom operations, disable this option, provide a WSDL URL, and select Get Operations. |
| WSDL URL | The full URL to the WSDL describing the web service method to be called. Select the Get Operations after entering a URL. |
| Use UDDI | Select Yes to use a UDDI provider to determine the Location URI. Select No to use the default Location URI or provide your own. See UDDI for more information. |
| Location URI | The dispatch location for the port / endpoint defined in the Connector. This field is filled in automatically when you select Get Operations and does not usually need to be changed. If left blank, the default URI defined in the WSDL will be used. |
| Convert Response to JSON | If enabled, responses will be converted from XML to JSON. |
| Expanded JSON Response | If enabled, the JSON version of the response envelope will always use an expanded format where all children are expanded into arrays and objects. The JSON document will be larger and more verbose, but it will also be in a more consistent structure which can make transformation easier. |
| Must Understand | If enabled, the mustUnderstand attribute will be added to the To, RelatesTo, Action, and MessageID header elements on all SOAP responses. |
| Store Full SOAP Payloads | If enabled, the full SOAP XML payload that gets received will be stored in the source map under the key requestSOAPPayload. The full SOAP XML response payload that is sent back will be stored in the response map under the key responseSOAPPayload. Note that enabling this option will increase the amount of memory used by this connector. |
| Validate WS-Security | If enabled, a SignatureConfirmation section must be present in the SOAP header of any response. The SAML Assertion and Timestamp will be validated according to NHIN standards. If the Security node isn't present or doesn't pass validation, the response will be considered an error. See WS-Security for more information. |
| Generate WS-Security | If enabled, a Security section will be generated according to your WS-Security settings and placed in the SOAP header. Additionally SAML Assertions, Timestamp and signatures will be generated per NHIN specifications. See WS-Security for more information. |
| Use SOAP Template | If enabled, the template in the Connector is expected to be the actual SOAP envelope to send to the external SOAP web server. Otherwise, the JSON version of the envelope is expected. |
| Use MTOM | Enables MTOM on the SOAP Binding. If MTOM is enabled, attachments can be added to a table in the Connector settings and dropped into the envelope. See Handling Multipart Payloads / Attachments for more information. |