dtSearch Engine API documentation
The dtSearch Text Retrieval Engine provides access to the indexing and searching functions of dtSearch. It has APIs for access from: C/C++; C#, VB.NET, and other .NET languages; Java; and Visual Basic, VBScript, and ASP, using COM.
For C and C++ developers, there is a function-call interface supplemented with a small class library to simplify access to the function-call interface. See Using the dtSearch Engine with C++ and C++ Support Classes.
dtSearch has an API for .NET and for .NET Standard. For .NET API documentation, see dtSearchNetApi2.chm. For .NET Standard API documentation, see dtSearchNetStdApi.chm.
The dtSearch Engine has a JNI wrapper for use from Java. See dtSearchJavaApi.chm.
For these and other scripting languages, the dtSearch Engine has an ActiveX (COM) Automation interface. See COM Interface.
For dtSearch updates and supplemental documentation, please see the dtSearch web site at www.dtsearch.com. A searchable archive of technical support articles is at support.dtsearch.com
dtSearch can search large volumes of text very quickly. It does this by building an index that stores the location of words in your files. Although the dtSearch Engine also has an unindexed search feature for searching without an index, searching without an index is much slower.
Indexing. You can create an index from a collection of files on disk or from data obtained by your program and passed directly to the dtSearch Engine. The dtSearch Engine can create any number of indexes and can incrementally update existing indexes (adding or removing documents). For an overview of how indexes are created and maintained, see Building and Maintaining Indexes and Indexing Databases.
Searching. After you have created one or more indexes, you can use the dtSearch Engine to perform very fast searches of those indexes. A single search can cover any number of indexes. For information on the dtSearch Engine's query syntax, see Search Requests. For information on search settings and efficient searching, see Optimizing Search Performance
Viewing Results. To view the results of a search, the dtSearch Engine can convert a retrieved file to HTML, RTF, or plain text, with hits highlighted. The dtSearch Engine can also generate a search report showing each hit and a specified amount of context, again, in HTML, RTF, or plain text. For information on highlighting hits in various file formats, see Highlighting Hits
Initialization and Installation. The dtSearch Engine consists of a single dynamic library supplemented by optional data files and optional additional dynamic libraries. For information on installing the dtSearch Engine with your application, see Installing the dtSearch Engine.
Sample applications are located in the examples subdirectory of the dtSearch Engine directory. See Samples.
Topic |
Description |
---|---|
Overview of the process of creating and updating indexes. | |
Indexing and searching databases and meta-data in documents. | |
Definitions. | |
dtSearch includes document filters for Office documents, PDF, HTML, emails, and more. | |
How to display retrieved documents with hits highlighted. | |
How to install the dtSearch Engine with your application. | |
The SearchFilter object can be used to limit searches to a complex subset of a document collection, with minimal search-time overhead. | |
How to monitor the progress of an index update. | |
Rules for multithreaded use of the dtSearch Engine. | |
How to use option settings to control indexing and searching. | |
Sample applications. | |
Options to control the processing of searches | |
How to sort search results after a search | |
Search request syntax and features. | |
dtSearch includes an option to automatically recognize dates, email addresses, and credit card numbers in text during indexing. | |
dtSearch provides several mechanisms to control how documents are scored for relevance during a search. |