Message Headers

This feature is deprecated and will be removed in a future release. Use the configuration described in Mapping Message Headers and Payloads instead.

Solace and Amazon SQS message headers can be created or manipulated using the User-Configured Header Transforms feature.

Solace Headers

Solace headers exposed to the Micro-Integration are documented within the Spring Cloud Stream Binder for Solace documentation.

Amazon SQS supports a maximum of 10 headers. Because of this limitation, the target Micro-Integration automatically maps the following headers individually to Amazon SQS:

solace_correlationId
solace_expiration
solace_applicationMessageId
solace_replyTo (converted from a Destination object into a string in the format <DESTINATION_TYPE>:<DESTINATION_NAME>, for example, QUEUE:replyTo_queue)
solace_replicationGroupMessageId (converted to a string)
sqs_groupId
sqs_deduplicationId

Custom headers are aggregated and mapped to a solace_user_properties header as JSON, for example:

"{"customHeader1":"value1","customHeader2":"value2","customHeader3":"value3"}"

Reserved Message Headers

The following are reserved header spaces:

solace_
scst_
Any headers defined by the core Spring messaging framework. For more information, see Spring Integration: Message Headers.

Any headers with these prefixes (that are not defined by the Micro-Integration or any technology used by the Micro-Integration) may not be backwards compatible in future releases of this Micro-Integration.

Provide feedback