Configure the MineMarket Search Service

Use this activity to configure the connection and other settings for the MineMarket Search Service.

This activity can be combined with the activity to Configure the MineMarket Service, which is also done using the MineMarket - Service Config application. This activity updates the ServerSettings.xml file.

The ServerSettings.xml file is used in conjunction with the MineMarketSearchSvc.exe.config file. Changes to the MineMarketSearchSvc.exe.config file are only required if the MineMarket Search Service is installed on a different machine from the MineMarket Service.

The MineMarket Search Service must be stopped before making changes to its configuration. The service can be restarted when configuration is complete.

Activity Steps

On the machine where the MineMarket Search Service is installed, navigate to the MineMarket installation folder and double-click BulkTrak.Config.exe.
The MineMarket Service Config screen opens.
If the MineMarket Search Service is on a separate machine from the MineMarket Service, in the Connection Settings category, update the connection string to the MineMarket database:
1. Complete the following fields.
  - Connection Type—Select from SQLServerNative or OracleODP.
  - Data Source—For Oracle, this is the alias name. For SQL Server, this is the name of the server to which to connect.
  - Initial Catalog
2. Select whether to UseIntegratedSecurity of Windows.
3. If UseIntegratedSecurity is False, enter the UserID and Password.
In the Search Settings category:
1. To use an existing folder for the MineMarket Search Service index, browse for and select the Lucene Directory. This relative or absolute path must be on the server where the MineMarket Search Service is running. To browse for a folder, click the ellipsis (...) to open the Browse For Folder screen.
2. To create a new folder for the MineMarket Search Service index:
  1. Enter the Lucene Directory.
    A message confirming the folder creation displays.
  2. Click Yes.
  3. If a message asking whether to grant administrator permissions to the folder for all authenticated users displays, click Yes.
3. Update the following fields as required.
  - Allow Leading Wildcards—If True, the search term is treated as a 'contains' query. This slows down the search. If False, the search terms is treated as a 'starts with' query. Default: True.
  - Database Select Batch Size—The number of rows that are retrieved per database call. Default: 5,000.
  - Optimise - Maximum Wait Time For Idle—The maximum amount of time the MineMarket Search Service waits for itself to become idle before optimising the search index. After this time has elapsed, the search index is optimised even if the MineMarket Search Service is not idle. Not applicable until the Minimum Time Since Last Run has elapsed. Format: D:HH:MM:SS. Default: 01:00:00.
  - Optimise - Minimum Service Idle Time—The amount of time for which the MineMarket Search Service needs to be idle before optimising the search index. Not applicable until the Minimum Time Since Last Run has elapsed. Format: D:HH:MM:SS. Default: 00:02:00.
  - Optimise - Minimum Time Since Last Run—The minimum amount of time between search index optimisations. This timer persists across restarts of the MineMarket Search Service. For example, if the last optimisation was run at midnight, and the timer is set to 24 hours, and the MineMarket Search Service is stopped at 5:00 a.m. and restarted at 7:00 a.m., then the next optimisation is still at midnight (not considering the impact of waiting for idle time). Format: D:HH:MM:SS. Default: 1:00:00:00.
  Note: Regular index optimisation is important for system performance. Even though searching still works accurately without optimisation, it gets slower as time goes on. Because optimisation takes a few minutes, it is not done every time a record is changed.
  The recommended frequency for optimisation is approximately once per day, but this interval should be increased as the database grows.
4. To schedule automatic rebuilds of the search index:
  1. Click the ellipsis (...) in the Rebuild Scheduling Settings field.
    The Search - Rebuild Scheduling Settings screen opens.
  2. Check Enabled. With regular optimisation of the search index, entire rebuilds are not required frequently. Even if unchecked, manual rebuilds can still be triggered via the Server Settings tab of the Options screen in the MineMarket Client.
  3. Update the Start date and time if required. The earliest possible date and time for starting a scheduled rebuild of the search index. The specified time is used as the run time of day for scheduled rebuilds.
  4. Select the Frequency.
  5. To skip occurrences, update Recur Every. Default: 1.
    Example: To schedule rebuilds for every second Tuesday, set Frequency to Weekly, Recur Every to 2 and Day of Week to Tuesday.
  6. If Frequency is Weekly, select at least one Day Of Week.
  7. If Frequency is Monthly, select the Days.
  8. Click OK.
    The Search - Rebuild Scheduling Settings screen closes.
Click Test.
A message box displays the test result.
If the connection is not successful, determine the correct settings or contact your network administrator or Datamine representative.
If the connection is successful:
1. Click OK.
  The message box closes.
2. Click Save.
3. Click OK.
  The MineMarket Service Config screen closes.
Configure the logon user for the service. See Configure the Logon User for each MineMarket Service.
If the MineMarket Search Service is on a separate machine from the MineMarket Service:
1. Navigate to the MineMarket installation folder on the machine where the MineMarket Search Service is installed and double-click AppConfig.exe.
  The Application Configuration Editor opens.
2. In the Search Service category, 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.
  - Secure Tcp—If True, the security mode for all TCP bindings is Transport. If False, the security mode for all TCP bindings is None. Default: True.
  - Secure Msmq—If True, the security mode for all MSMQ bindings is Transport. If False, the security mode for all MSMQ bindings is None. 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 all related bindings must either be Transport or None. Changing these settings also affects any bindings that have been added to the configuration files for custom integrations.
4. Click OK.
  The Application Configuration Editor closes and updates the MineMarketSearchSvc.exe.config file.