Timer service
The FTM SWIFT timer service provides a means to automatically send a message at a particular time (for example, at 9:00 a.m. on 31 December 2011), or after a particular amount of time elapses (for example, 45 seconds from now). Such messages are helpful for managing timeout situations, for example, when a response message is not received within a certain time limit, and subsequent action is required. After the specified time elapses, the timer service sends a wake-up message to the service specified in the timer message.
- A node used to set timers in a database table.
- The timer wake-up processor, which is a message flow that periodically
scans the table for timers that expired, and for each expired timer:
- Creates a message containing the information contained in the set timer request
- Sends this message to the destination service specified in the set timer request
- Deletes the corresponding timer record
- A node used to cancel a timer that was set.
You might require more than one scanning frequencies for different types of events. For example, events that are time critical might have to be scanned for once per second, while for other events a scanning frequency of once per minute or once per hour might be sufficient. To help you minimize unnecessary scanning, you can create different timer categories for different scanning frequencies. Each time category has its own database and wake-up processor.