Message Headers

Solace and Google Cloud Pub/Sub 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.

Message Header Mappings

The following Google Cloud Pub/SubPubsubMessage attributes are mapped to the following message properties: 

Header Name Type Access Description

gcp_pubsub_message_id

string

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().

gcp_pubsub_publish_time

long(seconds)

Read

The time at which the message was published, populated by the Google Cloud Pub/Sub service when it receives the Publish call.

See Google Cloud Pub/Sub PubsubMessage.getPublishTime().

gcp_pubsub_ordering_key

string

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

solace_applicationMessageId

string

Read/Write

The application provided message ID.

solace_applicationMessageType

string

Read/Write

The application provided message type. This value is used by applications only.

solace_correlationId

string

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:

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 versions of this connector.