The load balancing feature distributes UNICOM Intelligence Interviewer - Server Admin users evenly between the instances of a single activity. To improve performance, you can create multiple activity instances on the IIS server. The instances can be hosted on a single server or on different clustered servers. Load balancing is supported in a clustered environment.

This load balancing feature is completely separate from the load balancing feature for the interviewing engine, which distributes interviews between the Interviewing computers in a cluster. For information about load balancing for UNICOM Intelligence Interviewer - Server Admin see Load balancing interviewing engines.

When UNICOM Intelligence Interviewer - Server Admin load balancing is running, it writes information about its activity to a DMN*.log file (the log level is “trace”). For more information, see Log files.

UNICOM Intelligence Interviewer - Server Admin load balancing can be used to load balance requests to UNICOM Intelligence Interviewer - Server Admin activities, but external load balancers can also be used. When external load balancers are used, all requests for a single user session must be sent to the same UNICOM Intelligence Interviewer - Server Admin instance. In other words, the user sessions need to be persistent and failover is not supported. You can setup load balancing with an external load balancer by using URLs that depict different virtual directories, rather than simply using IP addresses for the different websites. For example, you could load balance multiple mriWeb virtual directories by configuring the external load balancer to balance the load between http://server1/mrIweb1, http://server1/mrIWeb2, and so on.