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 Google Cloud Pub/Sub message headers can be created or manipulated using the User-Configured Header Transforms feature.
Message Header Mappings
The following Google Cloud Pub/Sub PubsubMessage attributes are mapped to Solace message properties:
| Header Name | Type | Access | Description |
|---|---|---|---|
|
|
|
Read |
The ID of the message, assigned by the Google Cloud Pub/Sub service when the message is published. See Google Cloud Pub/Sub PubsubMessage.getMessageId(). |
|
|
|
Read |
The time at which the message was published, populated by the Google Cloud Pub/Sub service when it receives the Publish call. |
|
|
|
Read |
The Google Cloud Pub/Sub message’s ordering key. See Google Cloud Pub/Sub PubsubMessage.getOrderingKey(). |
The following Solace message headers marked with Read access are automatically forwarded to Google Cloud Pub/Sub messages, while headers with Write access can be set using the User-Configured Header Transforms feature.
| Header Name | Type | Access | Description |
|---|---|---|---|
|
|
|
Read/Write |
The application provided message ID. |
|
|
|
Read/Write |
The application provided message type. This value is used by applications only. |
|
|
|
Read/Write |
The correlation ID for the message. |
solace_dmqEligible
|
boolean
|
Write | Set the Solace message’s dmqEligible header. |
solace_expiration
|
long
|
Write | Set the time at which the Solace message is set to expire. |
solace_priority
|
int
|
Write | Set the Solace message’s priority. |
solace_senderId
|
string
|
Read | The Sender ID for the Solace message. |
solace_senderTimestamp
|
long
|
Read | The time at which the Solace message was published. |
solace_sequenceNumber
|
string
|
Read | The application-defined sequence number set on the Solace message. |
Reserved Message Headers
The following are reserved header spaces:
-
solace_ -
scst_ -
gcp_pubsub | goog -
Any headers defined by the core Spring messaging framework. For more information, see Spring Integration: Message Headers.
Headers with these prefixes may not be backwards compatible in future versions of this Micro-Integration, even if they are not currently defined by the Micro-Integration or any technology used by the Micro-Integration.