The name of the server. The name needs to be unique to the project and any included projects, and not contain spaces.

The mode for this server, either Primary or Standby. If this property is left blank, the default value will be Primary. The Primary and Standby servers need to run on different computers, and only one Primary and one Standby can be defined per cluster. Mode determines which server will be assigned the highest arbitration priority. The arbitration priority is used to work out which server will continue to be 'main' after a 'main-main' situation has occurred (see Alarm Server Side Synchronization).

The name of the cluster to which this Alarm Server will belong. If there is only one cluster defined in the project, you can leave this field blank. The Alarm Server will default to the defined cluster

Any useful comment. This property is optional and is not used at runtime.

The network address(es) of the server being configured. To specify dual network connections to the server, use a comma delimited list. See Network Redundancy.

The port this server will listen on. You can leave this field blank if you are running only one Alarm Server on the machine, in which case the default port number will be used.

Allows legacy connections to the server.

The port the server database will listen on. You can leave this field blank if you are running only one Alarm Server on the machine, in which case the default port number will be used.

Determines whether the alarm server operates in Extended Memory mode (64-bit). Select TRUE to use Extended Memory Mode (see Alarm Server Process).

Determines the order in which alarms are sorted. Select the required algorithm from the drop-down list.

If no algorithm is selected, the alarms will be listed according to "Priority, Alarm State" by default. For example:

P1 Unacknowledged + Active
P1 Acknowledged + Active
P2 Unacknowledged + Active
P2 Unacknowledged + Inactive
P1 Shevled/disabled

Select "Alarm State, Priority" to change the algorithm. The order of the example above would change to the following:

P1 Unacknowledged + Active
P2 Unacknowledged + Active
P2 Unacknowledged + Inactive
P1 Acknowledged + Active
P1 Shevled/disabled

Note: Alarm servers across the system need to have the same algorithm selected. A compiler error will occur if they are different.

If you want to create a customized sort order for alarms in a Situational Awareness project, you can use the parameter [Workspace]AlarmSortOrder.

Schedules archiving to occur every ' number' of days. If set, archiving will occur automatically.

Define where the archived data will be stored.

Note: The volume where data is to be saved should be labeled. This includes any removable storage devices. If this is not the case, archiving will not succeed and a message will display on the SOE page.

Required prefix to the archive folder.