Summary of Changes to ReportingService.exe.config

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

In ReportingService.exe.config on the machine where the MineMarket Reporting Service is installed:

In the connectionStrings section, the HTTP port number may need to be edited.
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, the server name and HTTP port number may need to be edited.
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">
```
In the security section, the authentication scheme may need to be changed.
Important: IntegratedWindowsAuthentication is recommended if access to MineMarket is using Windows authentication and users accessing OData feeds are all within the same or trusted domain. Other configurations may work, but are not supported by Datamine.
Copy
```
<authentication builtInScheme="IntegratedWindowsAuthentication"/>
```
The port number in the following code must match the port number in BulkTrak.Server.exe.config and BulkTrak.Service.exe.config on the Application Server.
The server name can be updated with the Application Configuration Editor.
Copy
```
<endpoint address="net.tcp://localhost:17040" 
binding="netTcpBinding" 
bindingConfiguration="TCPForServiceStatusNotification" 
contract="IMS.ServiceInstrumentation.WCF.ServiceContracts.IServiceStatusListener" />
```

In the ConsoleAppender section, the logging levels can be changed.

These status messages are only seen if the MineMarket Reporting Service is run in console mode.

<appender name="ConsoleAppender" type="log4net.Appender.ConsoleAppender">
  <layout type="log4net.Layout.PatternLayout">
    <conversionPattern value="%date %-5level %message%newline" />
  </layout>
  <filter type="log4net.Filter.LevelRangeFilter">
    <levelMin value="ERROR" />
    <levelMax value="FATAL" />
  </filter>
</appender>

In the RollingLogFileAppender section, a different path and file name can be specified; the number and size of files can be changed; and the logging levels can be changed.

Copy

<appender name="RollingLogFileAppender" type="log4net.Appender.RollingFileAppender">
  <file value="ReportingServiceLog.txt" />
  <appendToFile value="true" />
  <rollingStyle value="Size" />
  <!-- rolling based on size of file -->
  <maxSizeRollBackups value="3" />
  <!-- there will be 4 files - 1 current, 3 previous rollovers -->
  <maximumFileSize value="50KB" />
  <!-- KB, MB or GB are all permitted sizes -->
  <layout type="log4net.Layout.PatternLayout">
    <conversionPattern value="%date %-5level %message%newline" />
  </layout>
  <filter type="log4net.Filter.LevelRangeFilter">
    <levelMin value="INFO" />
    <levelMax value="FATAL" />
  </filter>
</appender>

In the root section, either logging method can be disabled by commenting it out.

Copy

<root>
  <!-- options for logging level : ALL,DEBUG,INFO,WARN,ERROR,FATAL,OFF - each level enables itself and the levels to the right. -->
  <level value="DEBUG" />
  <!-- this filter is applied before the filters in the appenders -->
  <appender-ref ref="ConsoleAppender" />
  <appender-ref ref="RollingLogFileAppender" />
</root>

Updates and Upgrades

To generate a new file:

Rename the existing ReportingService.exe.config (previously called Application.Reporting.Services.Hosting.Inventory.exe.config) file in the MineMarket\Reporting Services installation folder, so that it can be used for reference purposes.
Run the MineMarket installation package on a separate machine and copy the ReportingService.exe.config file to the MineMarket\Reporting Services installation folder.
Configure the MineMarket Reporting Service as required. See Configure the MineMarket Information Services.

Note: Even for implementations with custom integrations, Datamine does not recommend trying to update configuration files from MineMarket 5.5.0 or earlier.

To manually update an existing file from MineMarket 5.5.1

Add the following dependent assembly in the runtime section.

Copy

<dependentAssembly>
  <assemblyIdentity name="Microsoft.Practices.ServiceLocation" publicKeyToken="31bf3856ad364e35" culture="neutral" />
  <bindingRedirect oldVersion="0.0.0.0-1.3.0.0" newVersion="1.3.0.0" />
</dependentAssembly>