Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

Using these parameters you can get something like the following:

Code Block
languagebash
linenumberstrue
# catholic Christmas:
Schedules.Schedule1.DaysOff = * * * 25 12 *
# TimeZone:
Schedules.Schedule1.TimeZone = EST
# Schedule itself:
Schedules.Schedule1.StartTime = 0 0 8 * * 2-6
Schedules.Schedule1.ConnectTime =  0 0 9 * * 2-6
Schedules.Schedule1.DisconnectTime = 0 0 21 * * 2-6
Schedules.Schedule1.TerminateTime = 0 0 21 * * 6


2. How to use assign CRON expression to my current session's schedule

CRON expressions can be also assigned to your current sessions schedules defined in Old-Style Session Schedule Properties:

Code Block
languagebash
linenumberstrue
# weekly from Monday to Friday from 08:00 to 18:00
FixLayer.FixEngine.Session.TestFIXAcceptor1.ConnectTime = 0 0 08 * * 2-6
FixLayer.FixEngine.Session.TestFIXAcceptor1.DisconnectTime = 0 0 18 * * 2-6
FixLayer.FixEngine.Session.TestFIXAcceptor1.TerminateTime = 0 0 18 * * 6
 
# weekly from Monday to Friday from 08:00 to 21:00
FixLayer.FixEngine.Session.TestFIXAcceptor2.ConnectTime = 0 0 8 * * 2-6
FixLayer.FixEngine.Session.TestFIXAcceptor2.DisconnectTime = 0 0 21 * * 2-6
FixLayer.FixEngine.Session.TestFIXAcceptor2.TerminateTime = 0 0 21 * * 6

The same logic is applicable for DefaultStartTime and DefaultTerminateTime properties.Icon

Note

If you are going to use FIXICC as a tool for new schedule management, you need to specify the following setting in FIXEdge.properties:

...

Code Block
languagebash
linenumberstrue
FIXICC.Schedules = true



Note

CRON has the following syntax:

┌──────────── second (0 - 59)
│ ┌───────────── minute (0 - 59)
| │ ┌───────────── hour (0 - 23)
| │ │ ┌───────────── day of month (1 - 31)
| │ │ │ ┌───────────── month (1 - 12)
| │ │ │ │ ┌───────────── day of week (1 - 7: Sunday to Saturday)
| │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
* * * * * *

Support of the CRON expressions is limited by quartz. In particular, specifying both a day-of-week and a day-of-month values is prohibited (you'll need to use the '*' character in one of these fields).

The only note here is that '*' character is used instead of '?' character in compare with quartz.

...


Note

Several CRON expressions can be assigned for each property, they should be delimited by semicolon:

...

Code Block
languagebash
linenumberstrue
# day session is from 8am to 2pm, evening session is from 4pm to 4am next day
FixLayer.FixEngine.Session.TestFIXAcceptor.ConnectTime = 0 0 8 * * *; 0 0 16 * * *
FixLayer.FixEngine.Session.TestFIXAcceptor.DisconnectTime = 0 0 14 * * *; 0 0 4 * * *
FixLayer.FixEngine.Session.TestFIXAcceptor.TerminateTime = 0 0 14 * * *; 0 0 4 * * *



Note

Both formats - CRON expression and HH:MM - can be supported by FIXEdge simultaneously in one schedule. In other words, you session's schedule can be setup in the following way:

Code Block
languagebash
linenumberstrue
FixLayer.FixEngine.Session.TestFIXAcceptor.StartTime = 0 0 8 * * *
FixLayer.FixEngine.Session.TestFIXAcceptor.ConnectTime = 09:00
FixLayer.FixEngine.Session.TestFIXAcceptor.DisconnectTime = 0 58 23 * * *
FixLayer.FixEngine.Session.TestFIXAcceptor.TerminateTime = 23:59

The thing is that HH:MM is just converted to the CRON expression like 0 MM HH * * *.


3. How to keep using my current session's schedule

...

In other words, you may safely use your current configuration if your session's schedule is configured in the following way:

Code Block
languagebash
linenumberstrue
FixLayer.FixEngine.Session.TestFIXAcceptor.StartTime = 08:00
FixLayer.FixEngine.Session.TestFIXAcceptor.ConnectTime = 09:00
FixLayer.FixEngine.Session.TestFIXAcceptor.DisconnectTime = 23:58
FixLayer.FixEngine.Session.TestFIXAcceptor.TerminateTime = 23:59

Please see Old-Style Session Schedule Properties for reference.

...