Scheduler tasks and calendar
- Operational data
- Operational data has a lifecycle and a related FSM model for runtime behavior. It defines scheduled activities to gather data and raise events.
- Configuration data
- Configuration data that defines the monitored interfaces. Summary event monitoring requires one scheduler task object for each interface that is monitored.
- PAYMENT_RELEASE_SERVICE
A scheduler task uses a calendar group to schedule periodic triggers. The scheduling is configured using schedule entries with the type codes RELEASE_PAYMENTS and CHANGE_BUSINESS_DAY, which belong to the calendar group. The scheduler task and calendar group are related by an entry in the CAL_OBJ_REL table. In the FTM OAC, you can view the calendar groups that belong to a scheduler task as well as add and remove them (see Managing calendar group assignments).
The Store and Release sample application has one scheduler task 'Payment Release Service', which is linked to one calendar group, called 'Payment Release Service Calendar Group'. The Payment Release Service in this sample application has two responsibilities: to change the current business day (Service Participant's processing date) and to release payments. To achieve these two activities, the scheduler task uses the calendar group associated with it. Within this calendar group are two schedule entries, one to change the business day and one to release payments. The time at which these activities occur at are held in the schedule entry's OPEN_TIME field. Furthermore, the schedule entry can target specific days of the week by setting MON_FLAG, TUES_FLAG, and so on, to either 'Y' or 'N'. For demonstration purposes, both schedule entries have all days of the week flags set to 'Y', including Saturday and Sunday.