Interview Web Service configuration
mrIWeb is configured via a
web.config file. The InterviewService is similarly configured via its own
web.config file.
Web service configuration defines the configuration parameters that are available for mrIWeb.
Configuration parameters that are applicable to the InterviewService
BrowserCapabilities
Supported by InterviewWebService?: Yes
Doctype
Supported by InterviewWebService?: Yes
Only used when format=html is requested.
EngineMaxRetries
Supported by InterviewWebService?: Yes
EngineRetryTimeout
Supported by InterviewWebService?: Yes
HTMLOptions
Supported by InterviewWebService?: Yes
Only used when format=html is requested.
ImageLocation
Supported by InterviewWebService?: Yes
Only used when format=html is requested.
ImageCacheURL
Supported by InterviewWebService?: Yes
Supports both full and relative URLs.
Full URL:
<appSettings>
<add key="ImageCacheURL" value="http://WebServer/SPSSMR/ImageCache/ImageCache.aspx"/>
</appSettings>
Relative URL:
<appSettings>
<add key="ImageCacheURL" value="../ImageCache/ImageCache.aspx" />
</appSettings>
InterviewReview
Supported by InterviewWebService?: No
Is not currently used in mrIWEB.
LocalImageCacheURL
Supported by InterviewWebService?: Yes
Only used when format=html is requested.
Mode
Supported by InterviewWebService?: Yes
RegisteredEngines
Supported by InterviewWebService?: Yes
RegistrationPW
Supported by InterviewWebService?: No
Not supported as the InterviewService does not implement engine registration.
RegistrationWS
Supported by InterviewWebService?: No
Not supported as the InterviewService does not implement engine registration.
TemplateLocation
Supported by InterviewWebService?: Yes
Only used when format=html is requested.
UseImageCache
Supported by InterviewWebService?: Yes
X-Frame-Options
Supported by InterviewWebService?: Yes
This custom header prevents the UNICOM Intelligence application HTML code from being encapsulated within a frame-set. Websites that are vulnerable to being encapsulated within a frame-set are susceptible to a variety of vulnerabilities including but not limited to cross-frame scripting, and user interface redress attack.
The following methods can be used to configure the setting:
▪Add the following <customHeaders> section to the mrIWebweb.configfile:
<httpProtocol>
<customHeaders>
<add name="X-Frame-Options" value="deny" />
</customHeaders>
</httpProtocol>
The value options are:
▪deny - The page cannot be displayed in a frame, regardless of the site attempting to do so.
▪sameorigin - The page can only be displayed in a frame on the same origin as the page itself. sameorigin is the recommended value.
▪allow-from uri - The page can only be displayed in a frame on the specified origin.
Change the setting's value to deny in Microsoft Internet Services (IIS) under: [Your_Server_Name] > Sites > mriWeb > HTTP Response Headers > X-Frame-Options.
Additional supported parameters
The InterviewService supports one additional parameter that mrIWeb does not support.
RegisteredEnginesFile
Supported by InterviewWebService?: Yes
mrIWeb assumes that the RegisteredEngines.xml file resides in the same directory. Since the InterviewWebService uses the engine registration information from mrIWeb, it needs to be informed of the file location.
This is set by the installer to: \Interviewer Server\Server\mrIWeb\RegisteredEngines.xml
The engines specified by the RegisteredEngines.xml file are merged with those specified by the RegisteredEngines parameter (with the parameter taking priority).
mrIWeb uses the HKLM\SOFTWARE\SPSS\mrInterview\3\Interviewing\DefaultThreadPoolSize registry setting to control the number of request handler threads. The InterviewService performance tuning parameters are defined via a standard WCF parameters in the web.config file. See the Microsoft MSDN article, “ServiceThrottlingBehavior”
See
See also