Understand the Monitor Batch Transfer process

Note: For information on overriding default configuration settings, see Modify configuration settings.

The settings shown below specify the parameters for the Monitor Batch Transfer process—largely timing parameters. The example indicates standard default settings.

"MonitorBatchTransfer":

{

"LogFile": "monitorBatchTransfer.log",

"CheckIn": true,

"CriticalProcess": true,

"CheckinTimeout": 60,

"HotAssertDelay": 10,

"DebugMode": false,

"CheckinSleepInterval": 30,

"TicketingOperationsStartupDelay": 10,

"TicketingOperationsInterval": 10,

"ScheduleHeartBeat": 15,

"ScheduleHeartBeatDelay": 20,

"ScheduleSyncInterval": 25,

"ScheduleSyncDelay": 40,

"MaxDegreeOfParallelism": 2

},

Where:

• "LogFile" is the name of the log file to which errors are generated when the debug level is defined as verbose. This value should be a valid file name.

• "CheckIn" is a true/false value indicating whether or not the Batch Transfer Monitor should check into the RealTime service at startup.

• "CriticalProcess" is a true/false value indicating whether or not the Batch Transfer Monitor should check into the RealTime service as a critical process.

• "CheckinTimeout" is an integer value indicating the maximum number of seconds between check-ins before the Monitor Batch Transfer process is declared dead.

• "HotAssertDelay" is an integer value indicating the number of seconds that the Batch Transfer Monitor waits to begin operations after the RealTime service asserts as Hot.

• "DebugMode" is a true/false value indicating if the Batch Transfer Monitor should be operating in debug mode. When DebugMode is set to true, additional information will be printed to the Batch Transfer Monitor log file.

• "CheckinSleepInterval" is an integer value indicating the number of seconds between each attempted check-in by Batch Transfer Monitor.

• "TicketingOperationsStartupDelay" is an integer value indicating the number of seconds that the primary processing loop of Batch Transfer Monitor will wait before beginning operations after the RealTime service has asserted as Hot and the HotAssertDelay has expired.

• "TicketingOperationsInterval" is an integer value indicating the number of seconds between each computational process of all batchXfer records to be processed by the Batch Transfer Monitor application. This value will correspond to the number of seconds between each update seen in the easy Extended Operator Station (ezXOS) by Controllers. As this value is reduced, the Batch Transfer Monitor will consume additional resources on the RealTime server. Increasing this value may increase performance of other applications.

• "ScheduleHeartBeat" is an integer value indicating the number of seconds between each attempt to write the ScheduleHeartBeat to the Historical database.

• "ScheduledHeartBeatDelay" is an integer value indicating the number of seconds after the RealTime service has asserted as Hot and the HotAssertDelay has expired that the schedule heartbeat will wait before attempting to write to Historical database.

• "ScheduleSyncInterval" is an integer value indicating the number of seconds between each automatic attempt to synchronize the Historical Ticketing database with the RealTime Ticketing cache.

• "ScheduleSyncDelay" is an integer value indicating the number of seconds after the RealTime service has asserted as Hot and the HotAssertDelay has expired that the automatic schedule synchronization will wait before attempting to synchronize the Historical Ticketing database with the RealTime Ticketing cache.

• "MaxDegreeOfParallelism" is an integer value that specifies the maximum number of concurrent threads that the monitorBatchTransfer process will use to process batch transfers. If the parameter is absent or has a value of zero, the default value of 2 will be used.