Line Display Services Configuration

The Line Display Service only needs to be configured if Data Services is on a different machine OR if you choose to use a different database login user for this service than Data Services. If you choose to NOT follow the steps below, the Line Display service uses the database connection information in a local or specified instance of Data Services. Follow the steps below to configure the Line Display Service.

Only one Line Display Service per organization can be running at one time.

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.LineDisplayService.exe.config. By default, this file is installed here: \Program Files(x86)\Miner and Miner\Responder\Server.

Look for the following line of XML:

<section name="log4net" type="System.Configuration.IgnoreSectionHandler" />

Copy and paste the following code below the XML shown above:

<section name="miner.responder.server.configuration" type="System.Configuration.IgnoreSectionHandler" />

Search for the following XML line:
```
</system.runtime.remoting>
```

Copy and paste the following code AFTER the line of the XML shown above:

<miner.responder.server.configuration default="ConfigurationName">
    <configuration name="ConfigurationName">
      <multicast group="239.254.000.007" port="6679" ttl="2"/>
      <database>
        <connectionString>Data Source=Instance Name; Initial Catalog=SQL Server Database Name; User ID=Responder User ID; Password=Responder Password</connectionString>
        <providerFactoryClass type="Miner.Data.Access.ProviderFactories.SqlProviderFactory, Miner.Data.Access" />
        <syntaxClass type="Miner.Data.Access.SqlDataSyntax, Miner.Data.Access" />
        <schemaConfigurationFile>DatabaseSchemaConfig.xml</schemaConfigurationFile>
      </database>
      <geodatabase featureClassCaching="true">
        <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>
  </miner.responder.server.configuration>

You will set up a <configuration> section for each database to connect to. 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. This defaults to the local server, but you can enter a different server name, user and password necessary to connect to it.
- syntaxClass: This is default for SQL Server. Update with Miner.Data.Access.OracleDataSyntax, Miner.Data.Access if Oracle is needed.
- geodatabase: The <geodatabase> section contains connection information to the server that hosts the geodatabase. Include 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.
Save and close Miner.Responder.LineDisplayService.exe.config.

To configure the Line Display service to connect to a remote instance of Data Services, change the wellknown client configuration from:

<client>
       <wellknown type="Miner.Responder.Shared.IDataServices, Miner.Responder.Shared" url="msmq://FormatName:DIRECT=OS:.\private$\rxserver/DataServices.rem" />
</client>

to
<="" li="">

<client>
        <wellknown type="Miner.Responder.Shared.IDataServices, Miner.Responder.Shared" url="msmq://FormatName:DIRECT=OS:YourServerName\private$\rxserver/DataServices.rem" />
</client>