The Data Services configuration file (Miner.Responder.DataServices.exe.config) is an XML file that must be configured to use Responder's Data Services. You may edit the file by opening it in an XML application (such as XML Spy) or by opening it in a simple text editing program (such as Notepad). Miner.Responder.DataServices.exe.config is installed in: Responder\Server\. This file contains several sample configurations in the <miner.responder.server.configuration> section. These sample configurations may be deleted and replaced with those specific to your business.

When entering connection information, remember that you must log into the database as the data owner. Therefore, the User ID must belong to the owner of the data.

Telvent recommends using direct connections to the database. Refer to Esri's ArcGIS for Desktop help for information about setting up direct connections.

You will look for specific XML tags and then edit the properties contained within those tags.

Data Services Configuration

Look for the <Miner.Responder.Server.Configuration> tag. The values within this tag contain connection information for the Responder database. You may create multiple configurations (e.g., Oracle and SQLServer). Each configuration is enclosed with <configuration></configuration> tags. Follow the steps below to configure your Data Services.

1. Open Miner.Responder.DataServices.exe.config and locate the following XML:

<miner.responder.server.configuration default="ConfigurationName">
     <multicast group="239.254.000.007" port="6679" ttl="2"/>
     <queryService server="ServerName" port="2063" enabled="false"/>
     <database>
       <connectionString>Data Source=instance name;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>
     <files>
       <file name="ControlStyles" path="ControlStylesConfig.xml" />
       <file name="ExplorerRules" path="ExplorerRulesConfig.xml" />
       <file name="SubmitRules" path="SubmitRulesConfig.xml" />
       <file name="DataQueries" path="DataQueriesConfig.xml"/>
     </files>
 </configuration>

2. You will set up a <configuration> section for each database you may wish to connect to. You will need to modify the following attributes:
   • configuration name: This is a unique name that identifies this specific connection.
   • queryService server: This is the name of the server that is running query services. You may enable Query Windows Service on multiple servers using a list with spaces between the server names (e.g., server="server1 server2 server3"). Servers hosting Query Windows Service must be allowed to send messages on the Multicast IP group/port.
   • queryService enabled: If you are running Query Services, set this value to True. If not, set it to False.

   Servers hosting Query Windows Service must be allowed to send messages on the Multicast IP group/port.

   • connectionstring: This is the connection information to the Responder server. Enter the server name, user and password necessary to connect to it.

   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 Data Services: 0

   • 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.
   • files: The <files> section includes the paths to several important configuration files. The pathes are automatically set correctly during installation. By default, the these XML files are installed in the same directory as the Data Services configuration file. If these files are moved, the paths must be updated.
3. You can set up additional connections to different database servers. Just copy the XML from step 1 and modify it for another server.
4. Next, identify the connection you wish to enable. Look for the following XML:

<miner.responder.server.configuration default="ConfigurationName">

5. Set the name attribute to match the configuration name you wish to enable.
6. Save and close Miner.Responder.DataServices.exe.config.  

If you have multiple instances of Data Services running on multiple machines (and using the same connection information), the Configuration Name value MUST be the same on all machines. If an instance of Data Services has the same connection information as another instance on another machine, but a different Configuration Name, communication between the Responder components will fail.

You may run diagnostics to test the database and geometric network connections.

If you choose to start the Responder Services (e.g., Data Services) using the Responder Windows Service, you may log off of the machine if you wish. The Responder Services will continue to run until stopped. If you run Responder Services using the individual executable files (e.g., Miner.Responder.DataServices.exe), you must remain logged on to the server. Logging off will stop the Responder Services.

There are a couple cases in which additional configuration in the Data Services configuration file is required.

Refer to Accessing Remote Message Queues to perform the required configuration.