Generation

Interoperability Connector Suite User Guide

Validation

When WS-Security Validation is enabled in a source connector, incoming messages must include a Security section in the SOAP header. The SAML Assertion and Timestamp will be validated according to NHIN specifications. If the message does not include a Security node or fails validation, the request will not be processed through the channel and an error will be printed to the server log. The sender will get a generic SOAP fault response. Similarly, when WS-Security Validation is enabled in a destination connector, responses must include a Security section in the SOAP header and will be validated according to NHIN specifications. If the response does not include a Security node or fails validation, the response will not be processed and an error will be printed to the server log. For SSL Manager users, a subset of the normal SSL Manager settings is available for configuring WS-Security validation in source and destination. Parent topic: WS-Security

Interoperability Connector Suite User Guide

Generation Settings

The WS-Security Generation settings for destinations allow specifying a certificate through SSL Manager or manually to an alias in a keystore. SAML assertions and HL7 coded element attributes are also specified in the Generation Settings and include a simple set of entries to start with. An image of WS-Security Generation settings for destinations Parent topic: Generation

Interoperability Connector Suite User Guide

WS-Security

All Interoperability Connectors support WS-Security (web service security) for message validation. Note: It's important to note that, while managing certificates for use with WS-Security is much easier with the SSL Manager plugin, the SSL Manager plugin is not required. If the SSL Manager plugin is not installed, there are fewer options available for WS-Security and the Interoperability Connectors will use the default java keystore for certificate validation. Validation Generation

Interoperability Connector Suite User Guide

Source Connector Options

Option Name Description Convert to JSON If enabled, automatically convert SOAP response payloads to JSON. Expanded JSON Envelope If enabled, the JSON version of the incoming 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. Convert JSON Response to XML If enabled, responses will be converted from JSON to XML. Must Understand If enabled, the mustUnderstand attribute will be added to the To, RelatesTo, Action, and MessageID header elements on all SOAP responses. Validate WS-Security If enabled, a Security section must be present in the SOAP header of any incoming requests. 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 request will not be processed through the channel. See WS-Security for more informat

Interoperability Connector Suite User Guide

Destination Connector Options

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

Interoperability Connector Suite User Guide

XDS.b Destination Connector

XDS.b Sender Settings window The XDS.b Sender supports UDDI and WS-Security Validation and Generation. Operations The XDS.b Sender includes a set of standard operations that most XDS.b web services should support. When using the Default WSDL, you can switch between Registry and Repository modes through the Document Mode toggle. You also have the option of entering a custom WSDL URL and fetching its specific set of operations which will be presented in the Operation dropdown. The Operation dropdown is used when generating the envelope. Envelope The XDS.b Sender includes useful options for generating the outbound envelope. Parent topic: XDS.b Connectors

Generation

Recommendations

Validation

Generation Settings

WS-Security

Source Connector Options

Destination Connector Options

XDS.b Destination Connector

Validation

Generation Settings

WS-Security

Source Connector Options

Destination Connector Options

XDS.b Destination Connector