Configure maximum reflex concurrency

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

A limit can be configured on the maximum number of reflex records that can be active at the same time. This limit can be used to control the amount of system resources that the Reflex Monitor application can consume. Once the maximum number of records is active, additional records that wish to activate must wait for the other records to complete. The execution order of records is handled on a first-come, first-serve basis.

The Reflex Concurrency limit is configured by modifying a value in the AVEVA Pipeline Operations for Liquids Configuration file of each server. This value can be different for each server based on your requirements.

To modify the value in the AVEVA Pipeline Operations for Liquids Configuration file for each server

1. Navigate to the following directory: %DNAInstallRoot%\RealTime\config\Settings.

2. Copy the %DNAInstallRoot%\RealTime\config\Settings\LMS.RealTime.Json file to the %DNADataRoot% directory.

3. Open the file in a text editor.

4. Edit the element value "LMS" > "monitorReflex" > "Capacity" as necessary.

   This value controls the maximum number of reflex records that can be active at any given time. By default, this value is zero indicating that the application will not limit the number of of active commands. If the value is set to something other than zero, then the application will limit the number of active commands, and any subsequent commands will wait until the count drops below the limit.

5. Select Save.