Package com.epam.fixengine.scheduler

package com.epam.fixengine.scheduler
This package contains scheduler for start/stop sessions.
Sсheduling of session start/stop action is used syntax similar to UNIX cron daemon.
The CRON expression consist from 5 fields separated by white space that represents a set of times. Each part is intended as:
  1. Minutes sub-pattern. During which minutes of the hour should the task been launched? The values range is from 0 to 59.
  2. Hours sub-pattern. During which hours of the day should the task been launched? The values range is from 0 to 23.
  3. Days of month sub-pattern. During which days of the month should the task been launched? The values range is from 1 to 31. The special value "L" can be used to recognize the last day of month.
  4. Months sub-pattern. During which months of the year should the task been launched? The values range is from 1 (January) to 12 (December), otherwise this sub-pattern allows the aliases "jan", "feb", "mar", "apr", "may", "jun", "jul", "aug", "sep", "oct", "nov" and "dec".
  5. Days of week sub-pattern. During which days of the week should the task been launched? The values range is from 0 (Sunday) to 6 (Saturday), otherwise this sub-pattern allows the aliases "sun", "mon", "tue", "wed", "thu", "fri" and "sat".

The star wildcard character is also admitted, indicating "every minute of the hour", "every hour of the day", "every day of the month", "every month of the year" and "every day of the week", according to the sub-pattern in which it is used.
Every sub-pattern can contain two or more comma separated values ("59 11 * * 1,2,3,4,5").
Values intervals are admitted and defined using the minus character.("59 11 * * 1-5").
The slash character can be used to identify step values within a range. It can be used both in the form */c and a-b/c. The subpattern is matched every c values of the range 0,maxvalue or a-b.("*/5 * * * *").
Also it's possible to combine more scheduling patterns into one, with the pipe character ("0 5 * * *|8 10 * * *|22 17 * * *").

See more detailed here: cron4j