Message Headers
This section lists the headers you can map for the Micro-Integration for Salesforce.
To map and transform Solace and Salesforce message headers and payloads, see Mapping Message Headers and Payloads.
Headers for Salesforce as a Source
This section lists the headers you can map when Salesforce is configured as a source.
Salesforce Source Headers
There are no source message headers.
Solace Target Headers
| Name | Type | Description |
|---|---|---|
scst_targetDestination
|
String
|
A dynamic destination for the message. |
solace_applicationMessageId
|
String
|
The message ID (a string for an application-specific message identifier). |
solace_applicationMessageType
|
String
|
The application message type. |
solace_correlationId
|
String
|
The correlation ID of the message. |
solace_dmqEligible
|
Boolean
|
Indicates whether the message is eligible to be moved to a dead message queue (DMQ). |
solace_expiration
|
Long
|
The UTC time (in milliseconds, from midnight, January 1, 1970 UTC) when the message is supposed to expire. |
solace_httpContentEncoding
|
String
|
The HTTP content encoding header value from interaction with an HTTP client. |
solace_isReply
|
Boolean
|
Indicates whether the message is a reply to another message. |
solace_priority
|
Integer
|
The message priority value in the range of 0-255, or -1 if it is not set. |
solace_senderId
|
String
|
The sender ID for the message. |
solace_senderTimestamp
|
Long
|
The send timestamp (in milliseconds, from midnight, January 1, 1970 UTC). |
solace_sequenceNumber
|
Long
|
The sequence number. |
solace_timeToLive
|
Long
|
The number of milliseconds before the message is discarded or moved to a dead message queue (DMQ). |
Headers for Salesforce as a Target
This section lists the headers you can map when Salesforce is configured as a target.
Solace Source Headers
| Name | Type | Description |
|---|---|---|
solace_applicationMessageId
|
String
|
The message ID (a string for an application-specific message identifier). |
solace_applicationMessageType
|
String
|
The application message type. |
solace_correlationId
|
String
|
The correlation ID of the message. |
solace_deliveryCount
|
Integer
|
The number of times the message has been delivered to clients. |
solace_destination
|
String
|
The destination this message was published to. |
solace_discardIndication
|
Boolean
|
Indicates whether one or more messages have been discarded prior to the current message. |
solace_dmqEligible
|
Boolean
|
Indicates whether the message is eligible to be moved to a dead message queue (DMQ). |
solace_expiration
|
Long
|
The UTC time (in milliseconds, from midnight, January 1, 1970 UTC) when the message is set to expire. |
solace_httpContentEncoding
|
String
|
The HTTP content encoding header value from interaction with an HTTP client. |
solace_isReply
|
Boolean
|
Indicates whether the message is a reply to another message. |
solace_priority
|
Integer
|
The message priority value in the range of 0-255, or -1 if it is not set. |
solace_receiveTimestamp
|
Long
|
The receive timestamp (in milliseconds, from midnight, January 1, 1970 UTC). |
solace_redelivered
|
Boolean
|
Indicates whether the event broker has delivered the message to the API before. |
solace_senderId
|
String
|
The sender ID for the message. |
solace_senderTimestamp
|
Long
|
The send timestamp (in milliseconds, from midnight, January 1, 1970 UTC). |
solace_sequenceNumber
|
Long
|
The sequence number. |
solace_timeToLive
|
Long
|
The number of milliseconds before the message is discarded or moved to a dead message queue (DMQ). |
Salesforce Target Headers
| Name | Type | Description |
|---|---|---|
scst_targetDestination
|
String
|
A dynamic destination for the message. |
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.