Message Headers
Solace and Azure Service Bus message headers can be created or manipulated using the User-Configured Header Transforms feature.
Solace Headers
Solace headers exposed to the connector are documented in the Spring Cloud Stream Binder for Solace PubSub+ documentation.
Azure Service Bus Headers
The connector supports dynamic messages and maps critical message attributes between a PubSub+ event broker and Azure Service Bus.
Dynamic Headers
The connector supports Azure Service Bus partitioning and message sessions of the Azure Service Bus by setting the following headers:
| Header Name | Type | Access | Description |
|---|---|---|---|
|
|
|
Read |
sets a session ID of a message in the message header. |
|
|
|
Read |
sets a partition key in the message header. |
The session ID has higher priority than the partition key. When both azure_partition_key and azure_session_id headers are set, the value of the session ID overwrites the value of the partition key.
Header Mapping Between Solace and Azure Service Bus
The connector facilitates seamless integration by mapping specific headers between Solace and Azure Service Bus:
-
SolaceHeaders.CORRELATION_ID to ServiceBusMessageHeaders.CORRELATION_ID -
SolaceHeaders.APPLICATION_MESSAGE_ID to ServiceBusMessageHeaders.MESSAGE_ID
Reserved Message Headers
The following are reserved header spaces:
-
solace_ -
scst_ -
Any headers defined by the core Spring messaging framework. See Spring Integration: Message Headers for more info.
Any headers with these prefixes (that are not defined by the connector or any technology used by the connector) may not be backwards compatible in future releases of this connector.