text: OnDemand 
  database  Index 
  structure 
  Objects 
  
  *Figure 15-1 Full text search components and communication*
  
  **15.2.1 Full Text Search Server**
  
  The Full Text Search Server (FTS Server) provides a full document processing pipeline that 
  includes text extraction from binary formats, a wide range of encoding support, and language 
  processing in various languages. The flow of data during indexing depends on the 
  configuration and environment. For example, the following process occurs in a single-server 
  configuration: 
  
  (cid:2) Document contents and properties are sent from the Content Manager OnDemand 
  repository through FTS Exporter to the FTS Server. 
  
  (cid:2) FTS then preprocesses the data, including text extraction, language identification, 
  tokenization, and language analysis on the documents. 
  
  (cid:2) After preprocessing, the document content is stored in the FTS index. 
  
  The FTS Server comes with text extractors for many varied document types, including 
  Microsoft Office formats and XML. However, for AFP and Line Data, text extraction occurs 
  within the FTS Exporter. Images do not contain text, and they are not supported in FTS. 
  
  **15.2.2 Index structure**
  
  The FTS Server creates a binary Lucene index that is stored on the FTS Server. The index is 
  segmented into logical groupings called*collections*. The segmentation model is designed to 
  parallel the data table segmentation model in Content Manager OnDemand. For each 
  application group data table, which has data that is indexed in the FTS Server, a collection is 
  created on the FTS Server. Therefore, FTS collections maintain a one-to-one relationship 
  with Content Manager OnDemand data tables. Collections are created with the following 
  naming convention: 