### Installing Lucene Search Service using installutil (CMD)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/search-service.md

This command installs the SenseNet Lucene Search Service as a Windows Service on the virtual machine. It uses the .NET Framework's `installutil` tool, which registers the executable as a service. Ensure the user identity running the service has access to the sensenet security database.

```cmd
installutil SenseNet.Search.Lucene29.Centralized.Service.exe
```

--------------------------------

### Configuring Lucene29 Indexing and Query Engines (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/search-service.md

This XML configuration snippet, located within the `<sensenet>` section of the web.config, specifies the indexing and query engine implementations for the Sense/Net Lucene29 search. It sets `IndexingEngine` to `SenseNet.Search.Lucene29.Lucene29CentralizedIndexingEngine` and `QueryEngine` to `SenseNet.Search.Lucene29.Lucene29CentralizedQueryEngine`, directing the web servers to use the centralized search service for these operations.

```XML
<sensenet>
   <lucene29>
      <add key="IndexingEngine" value="SenseNet.Search.Lucene29.Lucene29CentralizedIndexingEngine" />
      <add key="QueryEngine" value="SenseNet.Search.Lucene29.Lucene29CentralizedQueryEngine" />
   </lucene29>
</sensenet>
```

--------------------------------

### Configuring Local Lucene Search Engine (C#)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/lucenesearch.md

This C# snippet demonstrates how to programmatically configure the sensenet repository to utilize the local Lucene search engine. It uses the RepositoryBuilder API, requiring a specified indexDirectoryPath for storing index files locally.

```csharp
repositoryBuilder.UseLucene29LocalSearchEngine(indexDirectoryPath);
```

--------------------------------

### Configuring Security Data and Message Providers (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/search-service.md

This XML snippet within the `<sensenet>` section allows for explicit configuration of security data and message providers. While default values (MSMQ and Entity Framework) are usually sufficient, this section enables customization of `SecurityDataProvider` and `SecurityMessageProvider` if alternative implementations are required for security-related operations.

```XML
<sensenet>
    <providers>   
        <add key="SecurityDataProvider" value="..." />
        <add key="SecurityMessageProvider" value="..." />
    </providers>
</sensenet>
```

--------------------------------

### Configuring Service Tracing Categories (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/search-service.md

This `sensenet/tracing` configuration enables and specifies the categories for real-time tracing within the centralized search service. The `TraceCategories` key accepts a semicolon-separated list of categories like `Query`, `Index`, `Security`, and `System`, which helps in debugging and monitoring service activities. Trace logs are typically generated in the `DetailedLog` folder within the App_Data directory.

```XML
<sensenet>
    <tracing>   
        <add key="TraceCategories" value="Query;Index;Security;System" />
    </tracing>
</sensenet>
```

--------------------------------

### Configuring Security Database Connection String (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/search-service.md

This XML snippet configures the connection string for the security database, typically the content repository database, where security-related tables are stored. The `name` attribute is `SecurityStorage`, and the `connectionString` attribute must be replaced with the actual database connection details. This is crucial for the search service to access security information.

```XML
<connectionStrings>
    <add name="SecurityStorage" connectionString="..." providerName="System.Data.SqlClient" />
</connectionStrings>
```

--------------------------------

### Configuring Centralized Lucene Search Engine (C#)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/lucenesearch.md

This C# snippet illustrates how to programmatically configure the sensenet repository to connect to a centralized Lucene search service. This approach eliminates local indexes, directing all query and indexing operations to an external WCF service.

```csharp
repositoryBuilder.UseLucene29CentralizedSearchEngine();
```

--------------------------------

### Configuring DefaultTopAndGrowth for Lucene Search (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/lucenesearch.md

This XML snippet configures the DefaultTopAndGrowth setting within the lucene29 section. It defines a comma-separated list of values that control the growing number of search results loaded in batches, with 0 indicating that all results should be loaded if criteria are not met by previous batches.

```xml
<lucene29>
   <add key="DefaultTopAndGrowth" value="100,1000,10000,0" />
</lucene29>
```

--------------------------------

### Configuring LuceneRAMBufferSizeMB (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/lucenesearch.md

This XML configuration sets the LuceneRAMBufferSizeMB key, which specifies the amount of RAM (in megabytes) that Lucene may use for buffering added documents and deletions. This buffer is used before the data is flushed to the index directory.

```xml
<lucene29>
   <add key="LuceneRAMBufferSizeMB" value="16.0" />
</lucene29>
```

--------------------------------

### Configuring WCF Service Base Address (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/search-service.md

This XML snippet configures the base address for the WCF service hosted by the centralized search service. It specifies the network protocol (net.tcp), hostname, port, and service path, which is essential for clients to connect to the search service. The `baseAddress` attribute defines the endpoint where the service will be accessible.

```XML
<baseAddresses>
    <add baseAddress="net.tcp://example.com:50123/SenseNetServiceModel/service/SearchService"/>
</baseAddresses>
```

--------------------------------

### Configuring MSMQ Security Channel Queue Name (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/search-service.md

This `appSettings` configuration defines the MSMQ queue name used for security messaging, allowing the centralized search service to receive security update messages. The `value` attribute must be set to the specific MSMQ queue name, and this setting is required on both the service and all web servers to enable communication for security activities.

```XML
<appSettings>
    <add key="SecurityMsmqChannelQueueName" value="..." />
</appSettings>
```

--------------------------------

### Defining Lucene29 Configuration Section (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/lucenesearch.md

This XML configuration snippet shows how to define the sensenet/lucene29 section group within a .NET application's configuration file (e.g., web.config). This section is essential for adding and managing various Lucene-specific settings.

```xml
<sectionGroup name="sensenet">
  <section name="lucene29" type="System.Configuration.NameValueFileSectionHandler" />
</sectionGroup>
```

--------------------------------

### Setting Index Lock File Wait Timeout (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/lucenesearch.md

This configuration determines the duration, in seconds, that the system will wait for other processes or the current writer to clean up the index lock file during startup or shutdown. In a development environment, setting this to a lower value can significantly speed up scenarios involving frequent site restarts in Visual Studio.

```XML
<lucene29>
   <add key="IndexLockFileWaitForRemovedTimeout" value="120" />
</lucene29>
```

--------------------------------

### Configuring WCF Client Endpoint for Search Service (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/search-service.md

This `system.serviceModel` configuration defines the WCF client endpoint used by web servers to communicate with the centralized search service. It specifies the `net.tcp` binding, the service address, and the contract (`ISearchServiceContract`), ensuring proper client-side connectivity. The `address` attribute must match the base address configured on the service side.

```XML
<system.serviceModel>
   <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />
   <bindings>
      <netTcpBinding>
         <binding name="NetTcpBinding_ISearchServiceContract" />
      </netTcpBinding>
   </bindings>
   <client>
      <endpoint address="net.tcp://example.com:50123/SenseNetServiceModel/service/SearchService"
                binding="netTcpBinding"
                bindingConfiguration="NetTcpBinding_ISearchServiceContract"
                contract="SenseNet.Search.Lucene29.Centralized.Common.ISearchServiceContract"
                name="NetTcpBinding_ISearchServiceContract">
      </endpoint>
   </client>
</system.serviceModel>
```

--------------------------------

### Specifying Lucene Query Engine (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/lucenesearch.md

This XML configuration sets the QueryEngine key in the lucene29 section, defining the full class name of the Lucene query engine implementation. This engine is responsible for retrieving query results, with the default being the local query engine.

```xml
<lucene29>
   <add key="QueryEngine" value="SenseNet.Search.Lucene29.Lucene29LocalQueryEngine" />
</lucene29>
```

--------------------------------

### Configuring Lucene Lock Delete Retry Interval (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/lucenesearch.md

This setting specifies the number of seconds the system waits while attempting to delete an existing index lock file during the startup process. For development environments, reducing this value can help accelerate the startup and shutdown cycles when frequently restarting the site in Visual Studio.

```XML
<lucene29>
   <add key="LuceneLockDeleteRetryInterval" value="60" />
</lucene29>
```

--------------------------------

### Specifying Lucene Indexing Engine (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/lucenesearch.md

This XML configuration sets the IndexingEngine key in the lucene29 section, specifying the full class name of the Lucene indexing engine implementation. This engine is responsible for writing document data to the index, with the default being the local indexing engine.

```xml
<lucene29>
   <add key="IndexingEngine" value="SenseNet.Search.Lucene29.Lucene29LocalIndexingEngine" />
</lucene29>
```

--------------------------------

### Configuring LuceneMergeFactor (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/lucenesearch.md

This XML snippet configures the LuceneMergeFactor setting, which determines how often segment indices are merged by addDocument(). Smaller values use less RAM and result in faster searches on unoptimized indices but slower indexing, while larger values offer faster indexing at the cost of more RAM and slower unoptimized searches.

```xml
<lucene29>
   <add key="LuceneMergeFactor" value="10" />
</lucene29>
```

--------------------------------

### Setting Index Lock File Removal Notification Email (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/lucenesearch.md

This parameter defines the email address of an operator to whom a notification email should be sent if the index lock file was not cleaned up by another process during startup, potentially indicating that the index is locked. For this feature to function, the sender address must be configured in the `notification` config section using the `NotificationSender` entry.

```XML
<lucene29>
   <add key="IndexLockFileRemovedNotificationEmail" value="admin@example.com" />
</lucene29>
```

--------------------------------

### Configuring Lucene Max Merge Docs (XML)

Source: https://github.com/sensenet/sn-search-lucene29/blob/develop/docs/lucenesearch.md

This setting controls the largest segment (by document count) that Lucene may merge with other segments. Smaller values (e.g., less than 10,000) are optimal for interactive indexing to limit pause durations, while larger values are better suited for batched indexing and improved search performance. It expects an integer value.

```XML
<lucene29>
   <add key="LuceneMaxMergeDocs" value="[int.MaxValue]" />
</lucene29>
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.