Client Service Monitoring Settings

Client service monitoring settings can be changed using the file ServiceMonitorConfig.xml which is present in the installed AVEVA Work Tasks bin folder.

For more information related to the service monitoring, see Client Service Settings.

Configuration files can be changed for the following settings:

• For enabling or disabling of service monitoring:

  Service monitoring can be enabled or disabled using the configuration attribute ServiceMonitoringEnabled. For enabling monitoring, set ServiceMonitoringEnabled="true". For disabling monitoring, set ServiceMonitoringEnabled="false".

• Whether to Send Alert emails or not:

  By default, emails will be sent to the administrator whenever any service restart happens.

  If the administrator does not want to get alert emails, then set SendAlertEmailsEnabled="false".

• Scheduled maintenance restart of all the AVEVA Work Tasks service can be done in the section MaintainanceRestart.

  By default, this is disabled and this section is commented in the configuration file.

  <!--<MaintainanceRestart RestartAt="" WeeklyRestartDays="" MonthlyRestartMonths="" MonthlyRestartDates=""/>-->

  Uncomment the node MaintainanceRestart in the configuration file, and give the appropriate values. A more detailed explanation of the MaintainanceRestart can be found in Maintenance.

• Changing the default CriticalMemory setting:

  Default CriticalMemory setting can be changed in the DefaultConfig section which affects all AVEVA Work Tasks service.

  Uncomment the CriticalMemory node and set the MemoryLimitInMB value for it. A more detailed explanation of the Critical memory can be found in Critical Memory Limit section.

• Changing the default WarningMemory setting:

  Default WarningMemory setting can be changed in the DefaultConfig section which affects all services. Uncomment the WarningMemory node and set the values for it. A more detailed explanation of the Warning memory can be found in Warning Memory Limit section.

• Changing the service settings for a specific service:

  If the specific service does not want to use the default settings, then it can override it with its own settings. Suppose WFEngine wants to have separate settings, then replace

  "<ServiceConfig Name="WFEngine" />"

  with

  <ServiceConfig Name="WFEngine" MonitorService="true">

  <CriticalMemory MemoryLimitInMB=""/>

  <WarningMemory MemoryLimitInMB="" TimeRangeInMinutes="" RestartAt=""/>

  </ServiceConfig>

  and set the appropriate values.

• Enabling or disabling the service monitoring for a specific service:

  If a specific service should not be monitored, then make MonitorService="false" for that service. By default, it takes the value from the DefaultConfig section where it is enabled.

  After the change, when the client service is restarted, the specified service will not be monitored for maintenance restart, critical memory limit, warning memory limit, and service specific monitoring logics.

  Example: <ServiceConfig Name="CommunicationService" MonitorService="false"/>