Adding session engines to an UNICOM Intelligence Interviewer server manually
Each interview session engine runs within its own w3wp.exe worker process. These worker processes can become unstable when their CPU or memory usage is high. You can avoid this problem by adding more interview session engines to your UNICOM Intelligence Interviewer servers, as long as the computers that are hosting the engines have sufficient memory. This automatically adds extra worker processes to improve fault tolerance.
You can add multiple interview session engines when you run the installation program. To add them later, complete the following steps:
1 In Internet Information Services (IIS) Manager, add a new application pool named SPSSmrInterviewPool2.
Set .Net Framework version to .NET Framework v4.0.30319, and set Managed pipeline mode to Integrated.
2 In the Application Pools dialog box, select the new application pool, and then click Advanced Settings. The Advanced Settings dialog box opens.
3 Set the following fields:
Identity: Specify the UNICOM Intelligence anonymous user. The UNICOM Intelligence anonymous user and password is defined during UNICOM Intelligence installation.
Idle Time-out (minutes): 0
Regular Time Interval (minutes): 0
4 Click OK to return to the main IIS screen.
5 Right‑click the web server under Sites from the Connections tree list, and then click Add Application. The Add Application dialog box opens.
6 Set the following fields:
Alias: mrIEngWS2
Application pool: SPSSmrInterviewPool2.
Physical path:
[INSTALL_FOLDER]\IBM\SPSS\DataCollection\7\Interviewer Server\Server\mrIEngWS
7 Click OK to return to the main IIS screen.
8 Select the application you just created, and then double-click the Handler Mappings icon under the IIS section. The Handler Mappings Options dialog box opens.
9 Right-click any of the Handler Mappings option, and then click Add Script Map. The Add Script Map dialog box opens.
10 Set the following fields:
Request path: *.dll
Executable:
[INSTALL_FOLDER]\IBM\SPSS\DataCollection\7\Interviewer Server\Server\mrIEngWS2\mrIEngWS.dll
where [INSTALL_FOLDER] is the directory in which UNICOM Intelligence is installed.
Name: mrIEngWS2
11 Click Request Restrictions, and then select the Invoke handler only if requests is mapped to and File or folder options on the Mapping tab.
12 Click OK to return to the Add Script Map dialog. Click OK again, and then click Yes when prompted to allow the ISAPI extension. After clicking Yes, you return to the main IIS screen.
13 Select the mrIEngWS2 application you just created, and then double-click the Authentication icon under the IIS section. The Authentication options appear.
14 Select Anonymous Authentication, and then click Edit in the Actions pane. The Edit Anonymous Authentication Credentials dialog opens.
15 Click Set, and then click Application pool identity. Click OK to return to the Edit Anonymous Authentication Credentials dialog; and then click OK to the main IIS screen.
16 Exit from the IIS application.
17 Open the Windows registry, and then add the new Interview Engine URL to the registry as a string in the following location:
\HKEY_LOCAL_MACHINE\Software\SPSS\mrInterview\3\Interviewing\LocalEngineURLs
For example:
LocalEngineURLs='http://blueserver/mrIEngWS','http://blueserver/mrIEngWS2'
18 Log on as a user who has trusted user access to DPM. This is typically the installing or running user.
19 Go to the following folder:
[INSTALL_FOLDER]\IBM\SPSS\DataCollection\7\Interviewer Server\Server
20 Run RegIntSvr.exe to register the new engine with the web server.
Making the session engines available to the Phone Participants and Review Interviews activities
1 On the Accessory Server, go to C:\InetPub\wwwroot\SPSSMR\CatiInt, and then open the Web.config file.
2 Add the following definition to the <appSettings> section:
<add key="ALTERNATE_INTERVIEW_ENGINES" value="engine_names"/>
where engine_names is a comma-separated list of interview engine URLs. For example:
<add key="ALTERNATE_INTERVIEW_ENGINES" value=" http://redserver/mriengws2, http://redserver/mriengws, http://blueserver/mriengws2"/>
3 Save the file, and then close it.
4 Repeat the preceding steps for the Web.config file at ReviewInterview.
See