COO Service performance with user objects and app.telemetry

Last update: 4 August 2017

COO Service performance with user objects and app.telemetry

Summary

In environments with a high number of user objects (or a high number of deactivated users) Fabasoft app.telemetry could cause short but recurring COO-Service thread load. To keep the list of users up-to-date the refresh is recurring and takes a few seconds to load all user objects.

Solution

Reduce the refresh interval of your app.telemetry installation by editing the infra.xml of Fabasoft app.telemetry:

  • Locate the infra.xml file on the Fabasoft app.telemetry server (see below)
  • Make a backup of your infra.xml (for example by copying it to infra.xml.backup)
  • Add the following line at line 3 of your infra.xml

 

The parameter "filterrefreshtimeout" defines the refresh interval. (the value is in seconds; 86400 sec = 1 day)
Default Value (without the explained line): 3600 seconds (1 hour)

Example snippet of infra.xml

This is an example of the first lines of an customized infra.xml

<?xml version="1.0" encoding="UTF-8" standalone="no"?>



...
...
...

Location of the infra.xml file

Windows

Windows 2008: C:\ProgramData\Fabasoft app.telemetry\infra.xml
Windows 2003: C:\Documents And Settings\All Users\Application Data\Fabasoft app.telemetry\infra.xml

Linux

/etc/app.telemetry/infra.xml

Applies to

  • Fabasoft Folio (all versions)
  • Fabasoft eGov-Suite (all versions)
  • Fabasoft app.telemetry (>= 2011 Summer Release)