Configure the MineMarket Information Services

Use this activity to configure the connection and other settings for the MineMarket Information Services.

This activity updates the following files:

DataMartService.exe.config
DataMartAgent.exe.config
DataService.exe.config
ReportingService.exe.config

The MineMarket Information Services must be stopped before making changes to their configuration. The services can be restarted when configuration is complete.

Important: If changing any port numbers, review the summary of all Default Port Numbers.

Activity Steps for Basic Configuration

On the machine where the MineMarket Information Services are installed, navigate to the MineMarket installation folder and double-click AppConfig.exe.
The Application Configuration Editor opens.
In the Data Mart Service category:
1. Update the connection string to the MineMarket Data Mart Database:
  1. Enter the name of the SQL Server that hosts the MineMarket Data Mart database.
  2. Enter the Initial Catalog. If this database does not exist, a database with this name is created automatically when the MineMarket Data Mart Agent is run for the first time. Default: DataMart.
  3. Select whether to use Windows Integrated Security.
  4. If Integrated Security is False, enter the User ID and Password.
2. Update the MineMarket Service Hostname. The name or IP address of the server on which the MineMarket Service runs. Default: localhost.
3. Modify the Secure Tcp and Secure Msmq settings only if required. Default: True.
  Important: If these settings are changed, the security mode for all related bindings must be changed to match. That is, the security mode of related bindings must either all be Transport or all be None. Changing these settings also affects any bindings that have been added to the configuration files for custom integrations.
4. Select whether to Use SSL. This setting must match the setting for the MineMarket Service. See Certificate Management and Configure the MineMarket Service.
5. If Use SSL is True:
  1. Enter the Subject Alternative Name (SAN)specified in the server certificate as the SSL Target Name Override only if DNS cannot be used to resolve the address of the MineMarket Server machine using the server certificate SAN. For example, this field may be required if the MineMarket Server is installed on a virtual machine without access to a shared DNS.
  2. Enter the Keystore folder name where certificates are stored.
6. Leave gRPC Tracers with its default setting of -all (with a prefixed hyphen) unless you need to debug the gPRC communication layer.
7. Select whether to Use Remoting. This setting must match the setting for the MineMarket Service. See Configure the MineMarket Service.
In the Data Mart Agent category:
1. Update the connection string to the MineMarket Data Mart Database.
2. Update the Data Mart Service Hostname if required. Because the MineMarket Information Services are installed together, in most circumstances this can be left as localhost.
3. Update the following settings if required.
  - MineMarket Service Hostname
  - MineMarket Service Port—TCP port that the MineMarket Data Mart Agent uses to communicate with the MineMarket Service. Must match the TCP port specified in the MineMarket Service configuration.
  - Secure Tcp
  - Secure Msmq
  - Use SSL
  - SSL Target Name Override
  - Keystore
  - gRPC Tracers
  - Use Remoting
In the Data Service category:
1. Update the connection string to the MineMarket DataMart Database.
2. Update the following settings if required.
  - MineMarket Service Hostname
  - Secure Tcp
  - Use SSL
  - SSL Target Name Override
  - Keystore
  - gRPC Tracers
  - Use Remoting
In the Reporting Service category, update the following settings if required.
- MineMarket Service Hostname
- Secure Tcp
Click OK.
The Application Configuration Editor closes and updates the configuration files.
Configure the logon user for each service. See Configure the Logon User for each MineMarket Service.

Activity Steps for Data Service Advanced Configuration

Open Windows Notepad or an alternative text editor with administrator permissions.
Open the DataService.exe.config file in the MineMarket installation folder.
In the owinConfiguration section, update the HTTP port number if required.
The port number in the following code must match the HTTP port in the ReportingService.exe.config file.
Copy
```
<owinConfiguration xmlns="http://abb.com/ims/minemarket/hosting/OWINHostConfiguration" baseUri="http://localhost:15002">
```
Save and close the DataService.exe.config file.

Activity Steps for Reporting Service Advanced Configuration

Open Windows Notepad or an alternative text editor with administrator permissions.
Open the ReportingService.exe.config file in the Reporting Services subfolder of the MineMarket installation folder.
In the connectionStrings section, update the HTTP port number if required.
The port number in the following code must match the HTTP port in the DataService.exe.config file.
Copy
```
<add name="DataServicesURL" connectionString="http://localhost:15002/DataServices/v1" />
```
In the owinConfiguration section, update the server name and HTTP port number if required.
The server name must be the name of the server where the MineMarket Reporting Service is installed, and must be accessible from machines where users will access the OData feeds. For example, it may be necessary to use the server's IP address, or a name that is included in the Hosts table on all relevant machines.
The port number in the following code must be unique.
Copy
```
<owinConfiguration xmlns="http://abb.com/ims/minemarket/hosting/OWINHostConfiguration" baseUri="http://localhost:15000">
```
Save and close the ReportingService.exe.config file.

Important: Further changes may need to be made to the configuration files. See the Summary of Changes to the MineMarket Data Mart Service Config File, Summary of Changes to the MineMarket Data Mart Agent Config File, Summary of Changes to the MineMarket Data Service Config File and Summary of Changes to the MineMarket Reporting Service Config File for more information.