IBM FileNet P8, Version 5.2.1            

What's new in IBM Content Search Services V5.2.1

IBM® Content Search Services V5.2.1 introduces new features and other enhancements to the product.

What's new for installation

Start of change
Zero-downtime upgrades

You might no longer have to perform service outages to apply patches or fix packs. As a result, users can continue to use the application without interruption and improve their productivity during an update.

Restrictions in certain fix packs might limit the use of IBM Content Search Services zero-downtime upgrades. The required environment and procedures for installing patches and fix packs without interrupting full-text indexing and search are available in the readme file that accompanies each patch or fix pack. The new release and the old release cannot be more than one fix pack apart from each other.

End of change

What's new for administrators

Maximum Request Queue Size property
The new Maximum Request Queue Size property controls the limit for the maximum number of outstanding index requests that are produced by an index job. This property is on the General tab for the index job in the administration console. For more information about this property, see Index job throttling.
Text index improvements
You can view indexing information for an object store, such as the number of indexes and the number of documents in each index. Previously, administrators accessed only individual index areas.
Configuration tool changes
The configuration tool, configTool, includes the following new parameters:
  • collectionBaseFolders - For security purposes, you might want to set this parameter to limit the location where IBM Content Search Services full-text indexes can be created, read, written to, and deleted from.
  • directoryTypeForSearch - Sets the type of file system to use for search.
  • enablePriorityStrategy - Enables indexing optimization when the server handles indexing for more full-text indexes than are specified by the maxConcurrentIndexingCollections parameter.
  • indexingProgressWarningTimeMin - When indexing does not progress for the specified amount of time (in minutes), the server issues a warning and a Java core memory dump for debugging purposes.
  • indexingTrace - Turns the indexing trace on or off. When enabled, this feature dumps the content of documents that are sent for indexing with their related metadata to files in the log directory.
  • maxDocumentSizeBytes - Specifies the largest sized document that the server accepts. Documents larger than this size are rejected automatically and not read by the server.
  • queryCacheSizeMB - Sets the amount of space in memory that is allocated to the query cache.
  • queuePriorityCollectionTimeoutMS - When the server handles indexing for more collections than are specified by the maxConcurrentIndexingCollections parameter, the queuePriorityCollectionTimeoutMS parameter specifies the maximum time (in milliseconds) for processing indexing requests for a specific collection.
  • removeStopwordsFromBooleanQuery - Specifies whether stop words are removed from Boolean queries.
  • searchableRefreshRateMS - Sets the frequency for checking whether the index changed and the searchable must be reopened.
  • useQueryCache - Turns the query cache function on or off.

For more information about these new parameters, see Configuration tool parameters.

The default value for the following parameters has changed:
  • inputQueueMemorySize changed from 50 M to 150 M.
  • maxHeapSize changed from 3000 to 4000 on 64-bit systems.
  • numberOfIndexerThreads changed from 4 to 8.
  • numberOfPreprocessingThreads changed from 4 to 8.
  • numberOfTokenizers changed from 10 to 20.
  • outputQueueMemorySize changed from 50 M to 150 M
New administration tool status command
The administration tool, adminTool, includes a new command, serverStatus. This new command provides information about the status of the running IBM Content Search Services server, including information about server uptime and configuration, queue status, the state of various pools and threads, server environment, and JVM.
Monitoring system performance
Additional metrics are available for monitoring system performance by using the monitor.csv output file. This release includes the following new metrics:
  • Total number of add requests that failed
  • Total number of successful add requests
  • Total size of successful add requests (KB)
  • Total number of delete requests that failed
  • Number of concurrent queries
  • Total number of queries

For information about these new metrics, see Monitoring system metrics to improve indexing performance.

What's new for developers

Content Engine Java™ and .NET API developers
The Content Engine Java and .NET APIs include enhancements in support of IBM Content Search Services. For more information about the changes in the APIs to support these enhancements, see What's new for developers.


Last updated: October 2015
wn_css.htm

© Copyright IBM Corporation 2015.