IBM FileNet P8, Version 5.2.1            

Overview of Content Search Services

IBM® Content Search Services consists of index and search servers that are created and registered at the FileNet® P8 domain level. The Content Platform Engine’s text search dispatcher passes index and search requests to Content Search Services servers. The text search dispatcher is configured in the text search subsystem.

The servers in a domain are available to all of the object stores in the domain. For multiple sites in a domain, servers in a site can access only the object stores that belong to the same site. The individual servers in a domain can be enabled or disabled, impacting all of the objects stores that they service. Content Search Services can be disabled or enabled at the object store level as well.

Content Search Services supports multiple languages. When configuring an object store for indexing, you must select the languages of the content that will be indexed for that object store.

An index belongs to an index area, and an index area is dedicated to a single object store. An index area is a file system directory that contains the information necessary to perform full-text indexing that is updated and queried by Content Search Services. An object store can have one or more index areas. You can have multiple index areas for an object store on a single file system, or you can distribute multiple index areas across file systems for an object store.

Index areas can be placed in affinity groups. An affinity group associates index servers with index areas, so that the servers can only access the index areas in the group. Index areas can also have property partitions. Property partitions group objects into separate indexes in accordance with the value of an object property. These features potentially improve CBR indexing and query performance.

Instances of the Document, Annotation, Folder, and CustomObject classes and subclasses can be indexed. For instances of a class to be indexed, you enable the class for content based retrieval (CBR-enabled). String-valued properties of these classes can be CBR-enabled as well.

Indexing is done automatically for all CBR-enabled objects and properties. Because the indexing operation is a batched, asynchronous operation, its results are not immediately evident.

Client applications submit full-text search requests, which are processed by the search servers. Client applications include the administration console (if searching a single object store), vendor clients such as reporting tools, and custom applications that use the Content Engine API.



Last updated: October 2015
p8pcc080.htm

© Copyright IBM Corporation 2015.