Query Windows Service Configuration

Configuration of this service is not required, but it may improve the performance of your Data Services, especially if you have a large number of users. Follow the steps below to configure the Query Windows Service.

The Query Windows Service may reside on any server, but it does require installation (though not execution) of Responder Server. The Responder business services (e.g., Data Services, Prediction Services, etc.) do NOT need to be running on the same machine as the Query Windows Service, although they can be.

NOTE: We recommend using direct connections to the database. Refer to Esri's ArcGIS for Desktop help for information about setting up direct connections.

Open Miner.Responder.QueryWindowsService.exe.config. By default, this file is installed here: \Program Files (x86)\Miner and Miner\Responder\Server.

Look for the following bit of XML:

<channels>
<channel ref="msmq" isServer="false" ComputerName="ServerName" />
<channel ref="tcp" port="2063" />
</channels>

The ComputerName attribute points to the Responder server. Change "ServerName" to the name of your Responder server. This attribute does not accept "." as a valid value indicating the local server. You must enter the server name.
Save and close Miner.Responder.QueryWindowsService.exe.config

Optional XML Configuration

Search for </log4net> in the configuration file and add the following XML below it:

<configuration name="ConfigurationName">
    <multicast group="239.254.000.006" port="6679" ttl="2"/>
    <database>
      <connectionString>Data Source=instance name;Min Pool Size=2;User ID=Responder user ID;Password=Responder password</connectionString>
      <providerFactoryClass type="Miner.Data.Access.ProviderFactories.OracleProviderFactory, Miner.Data.Access"/>
      <syntaxClass type="Miner.Data.Access.OracleDataSyntax, Miner.Data.Access"/>
      <schemaConfigurationFile>DatabaseSchemaConfig.xml</schemaConfigurationFile>
    </database>
    <geodatabase>
      <server>geodatabase server name</server>
      <instance>geodatabase server instance</instance>
      <database>SQL server database name</database>
      <user>GIS user ID for the database owner</user>
      <password>GIS user password</password>
      <version>version name</version>
      <dataset>dataset name</dataset>
      <network>geometric network name</network>
    </geodatabase>
</configuration>

First, you will set up a <configuration> section for each database to which you need to connect. You will need to modify the following attributes:
- configuration name: This is a unique name that identifies this specific connection.
- connectionstring: This is the connection information to the Responder server. Enter the server name, user and password necessary to connect to it.
  
  TIP:
  Min Pool Size: This optional attribute in the connection string sets the minimum number of pooled database connections. When the number of pooled connections exceeds the Min Pool Size setting any idle connections will be disconnected without falling below that Min Pool Size threshold. Recommended Min Pool Size setting for Prediction Services: 2
- geodatabase: The <geodatabase> section contains connection information to the server that hosts the geodatabase. Inlude the server name and instance. If you're using a SQLServer, enter the database name. Also include the user name and password to login as well as the version, dataset and network.
You can set up additional connections to different database servers. Just copy the XML from step 2 and modify it for another server.
Next, identify the connection to enable. Add the following XML:
```
<miner.responder.server.configuration default="ConfigurationName">
```
Set the name attribute to match the configuration name to enable.