336 IBM Content Manager OnDemand Guide
15.1  Introduction to full text search in Content Manager 
OnDemand
Content Manager OnDemand users primarily search on the metadata (extracted index 
values) that is associated with documents. By using FTS, you can intelligently search through 
actual document content. To enable FTS, the documents are first parsed and an index is built. 
This index can then be queried by a full text engine.
The FTS feature in Content Manager OnDemand comes with a new server, the Full Text 
Search Server (FTS Server), which handles the text extraction, indexing, and searching of the 
indexed data. This new server offloads the processing of full text data to a machine other than 
your Content Manager OnDemand library and object servers. 
The full text engine is the same search services engine that is used by other IBM products, 
such as DB2 or IBM FileNet P8. It is based on the Lucene engine and allows advanced and 
flexible queries. Users can perform wildcard searches, fuzzy (or similar) searches, proximity 
searches, Boolean searches, and other complex queries.
The full text feature can handle many formats, including Microsoft Office documents, XML 
files, and typical Content Manager OnDemand formats, such as AFP , Line Data, and Adobe 
Portable Document File (PDF).
The FTS feature supports full text indexing of both new and existing data. For new data, the 
FTS Server is configured to index the newly loaded reports by using the Administrator Client. 
For existing data, indexing is invoked by using the Content Manager OnDemand 
command-line utilities or the Content Manager OnDemand Web Enablement Kit (ODWEK) 
Java application programming interface (API).
FTS is enabled through the Content Manager OnDemand folder and allows all clients to take 
advantage of full text queries after the server configuration is complete. Several new Content 
Manager OnDemand folder field types are defined in support of FTS. Search score, highlight, 
and summary are returned, aiding the user in determining whether the document is a good 
match.
15.2  Full text search architecture in Content Manager 
OnDemand
The process of full text indexing can be lengthy in terms of time and processor consumption. 
Therefore, an integration architecture, which decouples the full text engine from the Content 
Manager OnDemand server and keeps the different workloads separate, is required. 
The components and their basic communication are shown in Figure 15-1 on page 337.
Note: Before the release of the FTS option in Content Manager OnDemand, a document 
content-based search was possible by using the server-based text search functionality. 
However, this functionality is limited to AFP , Line, SCS, and PDF documents. It does not 
use an index, but instead the server retrieves the documents and then scans those 
documents for the index values. This method limits the capabilities of the functions to exact 
matches of a query string and might cause workload problems on the Content Manager 
OnDemand server. FTS eliminates these issues and limitations by introducing new 
processing components.