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 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 in the Spring Cloud Stream Binder for Solace documentation.
SFTP Source Headers
The following file-related headers are injected into each Solace message. The example values in the following table are for the sub1/sub2/employee.csv file from the SFTP source located at sftp://host:port/rootDirectory/ .
| Header Name | Type | Description |
|---|---|---|
|
|
|
The name of the file (with no leading path), for example: employee.csv |
|
|
|
The local absolute path to the file. In the example, the file is downloaded to the local working directory /tmp/.solace/input-0/sub1/sub2/employee.csv |
|
|
|
The path of the file relative to the root directory of the SFTP source, for example: sub1/sub2/employee.csv |
|
|
|
The parent directory of the file, for example: sub1/sub2/ |
|
|
|
A long (converted to String) value containing the file size, for example, |
|
|
|
A long (converted to String) value, representing the last modified time in milliseconds, for example, |
|
|
|
The offset of the event in the file, for example, For a file with headers, the offset starts at 1 for the first data line. |
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.
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.