Summary of Changes to BulkTrak.MarketingService.exe.config

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

In BulkTrak.MarketingService.exe.config on the MineMarket Application Server:

To assist with identifying the source of errors logged in the Windows Event Viewer, the applicationName can be changed to a unique value. A unique value is recommended for multiple installations of MineMarket.

Copy

<exceptionManagement>
  <publisher assembly="cdal" type="Microsoft.ApplicationBlocks.ExceptionManagement.DefaultPublisher" logName="Application" applicationName="MineMarket V5 - Marketing Service" />
</exceptionManagement>

To configure the MineMarket Marketing Service Scheduler, the appropriate DLL file name must be specified as the value in the following code. See how to Configure an Automated Month-End Process (on the MineMarket Server) for more information.
Copy
```
<add key="Plugins" value=""/>
```
The ClientManager port number in the following code listens between the MineMarket Server and MineMarket Marketing Service. This port must match the TCP port specified in the MineMarket Service configuration.
Both the server name and port number can be updated with the Application Configuration Editor.
Copy
```
<wellknown type="Mincom.MineMarket.Server.ClientManager, BulkTrak.Component" url="tcp://localhost:8085/ClientManager" />
```

The server name for the IMSObjectChanged end point in the following code is always localhost, but the port number may be changed if required, and may match the IMSObjectChanged port number for the MineMarket Client.

Copy

<endpoint name="Mincom.MineMarket.IMSChangeNotification.Interfaces.IMSObjectChanged" 
address="net.tcp://localhost:8041/MineMarket/ObjectChangedNotification" 
binding="netTcpBinding" 
bindingConfiguration="TCPForObjectNotification" 
contract="Mincom.MineMarket.IMSChangeNotification.Interfaces.IMSObjectChanged" />

The IMSRegisterClientForNotification port number in the following end point must match the IMSRegisterClientForNotification port number in the BulkTrak.Server.exe.config file on the MineMarket Server.

The server name (but not the port number) can be updated with the Application Configuration Editor.

Copy

<endpoint name="Mincom.MineMarket.IMSChangeNotification.Interfaces.IMSRegisterClientForNotification" address="net.tcp://localhost:8030" binding="netTcpBinding" bindingConfiguration="TCPForRegisterClientForObjectChangeNotification" contract="Mincom.MineMarket.IMSChangeNotification.Interfaces.IMSRegisterClientForNotification" />

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" />
```

A different path and file name can be specified in the following code in the log4net section.

Copy

<appender name="RollingLogFileAppender" type="log4net.Appender.RollingFileAppender">
  <file value="MarketingServiceLog.txt" />
  <preserveLogFileNameExtension value="true" />
  <immediateFlush value="true" />
  <appendToFile value="true" />
  <rollingStyle value="Size" />
  <maxSizeRollBackups value="9" />
  <maximumFileSize value="1MB" />
  <staticLogFileName value="true" />
  <layout type="log4net.Layout.PatternLayout">
    <param name="ConversionPattern" value="%date %-5level %message%newline" />
  </layout>
</appender>

The logging level may need to be changed to INFO or DEBUG in the following code in the log4net section for more information about errors. The DEBUG logging level should only be used while investigating errors.
Copy
```
<root>
  <level value="ERROR" />
  <appender-ref ref="RollingLogFileAppender" />
</root>
```
If system security prevents loading .NET assemblies from network locations (as indicated by the error message "An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed..."), add the following section of code:
Copy
```
<runtime>
  <loadFromRemoteSources enabled="true"/>
</runtime>
```
Further changes may be required. Refer to the Configuration Examples.

Updates and Upgrades

To generate a new file:

Rename the existing BulkTrak.MarketingService.exe.config file in the MineMarket installation folder, so that it can be used for reference purposes.
Perform one of the following steps:
1. Start the MineMarket Marketing Service as a background Windows service.
2. Start the MineMarket Marketing Service in console mode.
  A new version of BulkTrak.MarketingService.exe.config is created.
Configure the MineMarket Marketing Service as required.

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>