IBM FileNet P8, Version 5.2.1            

Preparation phase

The following components are involved in the preparation phase: the application that submits the index job, such as Administration Console for Content Platform Engine, and the text search subsystem dispatcher. Configure the operation of the text search subsystem dispatcher to optimize indexing performance or to control system resources. The dispatcher can use a significant amount of system resources for text extraction.

The following table describes the steps in the preparation phase.

  Step Description Related information
1 Index request submission An index request is generated for an object when Content Platform Engine or an application creates, updates, or deletes an object that belongs to a CBR-enabled class. The application might be the administration console or a custom application that calls Content Engine API methods.

A batch of index requests can also be generated at one time as part of an index job. An index job is automatically created when you choose a CBR-enabled class or object to be indexed in the administration console. An index job is also created when you manually choose to reindex a selected index in an index area.

For information about creating an index job using the administration console, see Creating an index job.
2 Index determination Content Platform Engine determines the index area and the target index file to update for the index request. For information about how Content Platform Engine determines the index for an object, see Resource statuses and object index entry assignment.
3 Index request batching The Content Platform Engine subsystem dispatcher groups the index request with other index requests to form an index batch. The target full-text index is the same for all index requests in a batch. For information about accessing the following properties in the administration console, see Accessing subsystem configuration properties:
Maximum batch size for indexing
The maximum number of objects in a single batch that can be submitted to an index server for indexing.
4 Text extraction A worker thread for the subsystem dispatcher converts any binary documents to text documents. An example of a binary document is a Microsoft Word document. The index request object might have zero or more content elements that are binary documents. For information about accessing the following properties in the administration console, see Accessing subsystem configuration properties:
Maximum worker threads for text extraction
The maximum number of worker threads for text extraction.

For more information about text extraction, see Controlling text extraction.

5 Index server workload rebalancing For load balancing purposes, the subsystem dispatcher checks if a different index server must be assigned to the target full-text index.

To control the way that index servers are assigned to full-text indexes, you can create affinity groups to dedicate index servers to particular index areas.

For information about creating affinity groups, see Creating an affinity group.

For more information about rebalancing, see Index server workload rebalancing.

6 Index batch submission A worker thread for the subsystem dispatcher submits the text document as part of an index batch to an index server. The phrase text document refers to the text that is indexed for a Content Platform Engine object. For information about accessing the following properties in the administration console, see Accessing subsystem configuration properties:
Maximum lease interval for indexing
The maximum amount of time for a worker thread to process a batch.
Maximum worker threads for indexing
The maximum number of workers for indexing.


Last updated: March 2016
csscbr_indexing_overview.htm

© Copyright IBM Corporation 2016.