Community Component 25.4
Community Component Help

# Configure Knowledge Discovery Components

To use document tracking with an SQL back end, you must use the Knowledge Discovery document tracking library, which is included in the Content component ZIP package. You can store this library in any accessible location, and then configure the location in your components.

You must then configure your components to use the SQL document tracking back end. The DIH, Content component, Connector Framework Server (CFS), and CFS Connectors support document tracking.

After configuration, a Knowledge Discovery component automatically adds itself to the `Source` table on startup.

NOTE: If you retire a component, OpenText recommends that you leave the entry in the `Source` table, because existing records might refer to the source of the retired component.

To configure a component for document tracking

1. Open the component configuration file in a text editor.

2. (DIH only) Turn on document tracking by setting the `DocumentTracking` parameter to `True` in the `[Server]` section of the DIH configuration file.

       [Server]
       DocumentTracking=True

   NOTE: If you are using DIH in a unified configuration, set the `DocumentTracking` parameter to `True` in the `[DistributionSettings]` section.

3. Create a `[DocumentTracking]` configuration section.

4. In this `[DocumentTracking]` section, set the `Backend` parameter to `Library`.

5. Set `LibraryPath` to the absolute path to your document tracking library. In the default installation, the library is located in the `modules` directory, and the library name is `dt_odbc.dll` (on Windows), or `libdt_odbc.so` (on UNIX).

6. Set `ConnectionString` `ConnectionString` to the connection string to use, with subparameters set for your setup. For example:

       ConnectionString=DSN=MyDSN

   Set the parameters consistent with your environment. On Linux, the connection string cannot contain spaces.

   On Linux, you can set the `Driver` subparameter to the path to your SQL ODBC driver shared object. OpenText recommends that you use the ANSI version of libraries.

   TIP: On Linux, if you use a DSN in your connection string, and you see `File not Found` errors in your logs, try specifying the driver explicitly in the `ConnectionString` configuration parameter:

       ConnectionString=Driver=/freetds/inst/lib/libtdsodbc.so;DSN=mydsn

7. Set any other configuration parameters for document tracking. For more information, refer to the Content component Reference. For example:

       [DocumentTracking]
       MaxEventsPerFile=500
       TimeoutSeconds=20
       UIDFieldName=UID

   NOTE: Connectors generate the document ID strings, and add them to the `UIDFieldName` field, so you must not use a field that already exists for another purpose.

8. Save and close the configuration file.

   Restart the component for your changes to take effect.

Copyright 2025 Open Text
Version 25.4 | Last updated October 2025

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery Community Component 25.4

Topic Title: Configure Knowledge Discovery Components