Developer Documentation Library > Interviewer - Server > Configuration and customization > Web configuration files > Settings for the Interviewing Activity Reports activity
 
Settings for the Interviewing Activity Reports activity
The Interviewing Activity Reports activity provides a snapshot of how busy the interviewer session engines are at the time the report is run. Supervisors use these reports to see which projects are using each engine, how many interviews are running on each engine, and what the current percentage load is for each engine.
The activity’s Web.config file controls how the reports run.
File name and location
C:\InetPub\wwwroot\SPSSMR\SessionEngineReports\Web.config
Percent loaded warning and error limits
The reports mark engines where the percentage load is high or excessively high. The defaults are 80% and 95% respectively. You can change these settings as follows:
<add key="SPSS_PercentLoadWarningLimit" value="80"/>
<add key="SPSS_PercentLoadErrorLimit" value="95"/>
Time-out delay for communication with the web service
The activity reports request the information they need from the Web Service that is running on each interviewing server. In order that the reports show accurate snapshots the reporting activity waits a maximum of five seconds to receive a response before assuming that a server is inactive. This time-out delay is defined as a number of milliseconds in the SPSS_SessionEngineTimeout setting and can be changed if necessary:
<add key="SPSS_SessionEngineTimeout" value="5000"/>
Web status reports
The Web Status report shows the status of each web server, and which engines are registered or failed for each web server. For more information, see Web Status report.
The engine registration service provides input for the report. The following parameters control interaction with the engine registration service:
SPSS_WebServerTimeout: The interval (in milliseconds) after which a server is marked as “Failed”.
RegistrationPW and RegistrationURL settings in the registry.
In most situations, you can use the default values for all of these settings. However, if https is used internally to connect to the cluster, you might need to change the RegistrationURL registry setting to use https.
See also
Web configuration files