The message sampling processor consumes messages in from a specified message store and sends them to a configured sequence. This process happens in a preconfigured the messages to a sequence at a configured interval. This message processor does not ensure reliable messaging.
Message sampling processor parameters
Following are the additional parameters you can set when adding a message sampling processor:
| Parameter Name | Description | Required | |||
| Name | The name of the message sampling processor. | Yes | |||
| Message Processor Provider | The name of the message processor provider. | Yes | |||
| Sequence | The sequence to which the message sampling processor injects consumed messages. | Yes | |||
| Message Store | The message store from which the message sampling processor consumes messages. | Yes | |||
Processor State (is.active) | Activate (true) or Deactivate (false) | No. The default is Activate (true). | |||
Sampling Interval (interval) | Interval in milliseconds in which processor consumes messages | No. The default value is 1000. | |||
Sampling Concurrency ( | The number of messages the processor consumes at a time | No. The default is value is 1. | |||
Quartz Configuration File Path ( | Quartz configuration file path. This properties file contains the Quartz configuration | No | |||
Cron Expression ( | Cron expression to be used to configure the retry pattern | No | Pinned Servers (pinnedServers) | A comma-separated list of server names where the message processor should be started, so that when you start the message processor on an ESB server, it is only started on that server if the server name is in this list. This is useful when you have multiple ESB instances in a cluster. No |
Samples
For samples illustrating how to use the message sampling processor, see:
...