Retrieve all connections

The input value of the enforcement that should identify the origin of the message (e.g. a device id). You can use placeholders within this field depending on the connection type. E.g. for AMQP 1.0 connections you can use {{ header:[any-header-name] }} to resolve the value from a message header.

An array of filters. One of the defined filters must match the input value from the message otherwise the message is rejected.

Acknowledgement requests to be included for each message consumed by this source.

Optional filter to be applied to the requested acknowledgements - takes an fn:filter() function expression

Whether reply target is enabled.

The target address where responses of incoming commands from the parent source are published to. The following placeholders are allowed within the target address:

• Thing ID: {{ thing:id }}

• Thing Namespace: {{ thing:namespace }}

• Thing Name: {{ thing:name }} (the part of the ID without the namespace)

• Ditto protocol topic attribute: {{ topic:[topic-placeholder-attr] }}

• Ditto protocol header value: {{ header:[any-header-name] }}

If placeholder resolution fails for a response, then the response is dropped. NOTE Use "command" alias for connections of type "hono".

External headers computed from headers and other properties of Ditto protocol messages.

Contains a list of response types that should be published to the reply target.

The mapping engine used to process incoming and outgoing messages. Available mapping engines are JavaScript, Normalized, ConnectionStatus, RawMessage, Ditto, ImplicitThingCreation, and UpdateTwinWithLiveResponse.

Configuration options specific to the used mapping engine:

JavaScript

• incomingScript (string, required): The mapping script for incoming messages
• outgoingScript (string, required): The mapping script for outgoing messages
• loadBytebufferJS (boolean, optional): Whether or not ByteBufferJS library should be included (default: false)
• loadLongJS (boolean, optional): Whether or not LongJS library should be included (default: false)

Normalized

• fields (string, optional): Comma separated list of fields included in the normalized message (default: all fields included)

ConnectionStatus

• thingId (string, required): The ID of the thing
• featureId (string, optional): The ID of the modified feature (default: ConnectionStatus)

RawMessage

• outgoingContentType (string, optional): The fallback content type for outgoing messages.
• incomingMessageHeaders (object, optional): The fallback headers for incoming messages containing the necessary information to map them to message commands and responses. The relevant header keys are: content-type, ditto-message-subject, ditto-message-direction, ditto-message-thing-id, ditto-message-feature-id and status. The header values may contain placeholder expressions.

Ditto

• no options required

ImplicitThingCreation

• thing (object, required): The template of the thing to be implicitly created

UpdateTwinWithLiveResponse

• dittoHeadersForMerge (object, optional): The Ditto headers to use for constructing the "merge thing" command for updating the twin, may for example add a condition to apply in order to update the twin (default ditto headers: response-required: false, if-match: "*").

Optional conditions to be checked before applying the mapping engine to inbound messages. Can use placeholders and functional expressions.

Optional conditions to be checked before applying the mapping engine to outbound messages. Can use placeholders and functional expressions.

The type of credentials used to authenticate. Either password or public-key.

The username used for the authentication.

The password used for authentication when credentials type password is used.

Public key in PEM base64-encoded format using X.509 syntax. This field is required for credentials type public-key.

Private key in PEM base64-encoded format using PKCS #8 syntax. This field is required for credentials type public-key.