You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

The article is relevant for clients who are going to upgrade the FIXEdge to version 6.0 and higher.


Since FIXEdge 6.0 and FIXICC 2.10.1 new functionality of session schedule management has become available. This instruction provides the answers on how to upgrade your current sessions schedule in order to support new functionality.

Please note, that new Scheduler functionality uses the same notion of schedule properties as old one:

1.How to use new session's schedule functionality with CRON expressions

In order to use new schedule management functionality, then follow the steps below:

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

    Please use this FIXICC manual for details regarding new schedule management functionality available in FIXICC.

    FIXICC.Schedules = true
  2. If you are not going to use FIXICC in terms of new schedule management functionality or/and you would like to configure sessions schedule via configuration file, you may ignore "FIXICC.Schedules" property. Here are the steps which should be performed to configure the schedule via

    1. First of all you need to define the Schedule entity in The common Schedule structure is defined in the following way:

      Schedules.<name of schedule>.<section of schedule> = <cron expression>[;<cron expression>....]

      Below is the example how to setup some "default" session's schedule:

    2. Then you need to assign the defined schedule to the specific session which should use it:

Refer to New-Style Session Schedule Properties article for details.


If you have old-style schedule properties specified (including DefaultStartTime and DefaultTerminateTime) as well as new schedule assigned to the same session, then new schedule will be apllied, while all old-style properties will be ignored;

1.1. How to assign one schedule to several sessions

In case you have several sessions which use the same schedule, you may assign one schedule to several sessions.

If we use DefaultSchedule defined above, we can assign it to several sessions (say, TestFIXAcceptor1 and TestFIXAcceptor2) in the following way:

1.2. How to specify days off and time zone for my schedule

New session schedule management functionality provides possibility to specify Time Zone and Days Off to have more flexible schedule.

Using these parameters you can get something like the following:

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:

The same logic is applicable for DefaultStartTime and DefaultTerminateTime properties.


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


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.


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


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:

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 order to keep using your current session's schedule, no additional actions are required.

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

Please see Old-Style Session Schedule Properties for reference.

Also, you may continue using properties DefaultStartTime and DefaultTerminateTime.

  • No labels