Content Search Guide

CHAPTER 11

Search Options Reference

This chapter describes the search options you can configure in exteNd Director:

For more information    For background information, see Setting Search Options.

 
Top of page

Copy document contents into the DRE?

Indicates whether to copy document contents into the exteNd Director Dynamic Reasoning Engine (DRE) when the document is imported and indexed.

Key in config.xml

Default

Tips

Set method

com.sssw.cm.fetch.store.content.repository name

false

  • Set to false to avoid the overhead of storing the same information in two places: the Content Management (CM) repository and the DRE database.

  • Set to true to allow you to extract and back up document content using the DRE Administration console and execute keyword searches.

IMPORTANT:   This option must be set to true to enable keyword searching.

EbiDataFetcherDelegate.setStoreContent()

You can configure this option:

 
Top of page

Debug during import?

Indicates whether to dump document contents to the console as documents are indexed for debugging purposes.

Key in config.xml

Default

Tips

com.sssw.cm.fetch.dump.imported.data

false

  • Set to true to get a greater degree of detail than tracing CM and Search logs when documents are imported and indexed.

  • Set to false to avoid performance overhead.

You can configure this option:

 
Top of page

Enable link to the Search subsystem?

Indicates whether to activate Autonomy and Search subsystem interactions with the CM subsystem—including importing, indexing, and searching.

Key in config.xml

Default

Tips

com.sssw.cm.search.enable.repository name

false

  • Set to true to enable interaction between the CM repository and the Search subsystem.

  • Set to false to disable all interactions between Autonomy and the CM subsystem, including conceptual search.

IMPORTANT:   You must set the value to true to use Autonomy and the Search subsystem.

You can configure this option:

 
Top of page

Importable file extensions

Specifies the extensions of binary formats that you can import into the DRE.

Key in config.xml

Default

Tips

com.sssw.cm.fetch.extensions

.html;.sgml;.xml;.txt;.rtf;.pdf;.xls;.xls;.ppt;.ppt

The number and order of importable extensions must match the number and order of importable MIME types.

You can configure this option:

NOTE:   Binary files without extensions are treated as text files.

 
Top of page

Importable MIME types

Specifies the MIME types of binary formats that you can import and index in the DRE. The following MIME types are supported:

You can configure this option:

 
Top of page

Index custom document metadata?

Indicates whether custom document metadata (extension metadata) field values should be indexed. Custom metadata is application-specific information about content that you define in the CM subsystem as fields in document types. Custom metadata helps to categorize content, making it easier to search.

Key in config.xml

Default

Tips

Set method

com.sssw.cm.fetch.process.extn.metadata.repository name

true

  • Set to true to index custom metadata.

  • Set to false to ignore custom metadata and index only standard metadata and/or content.

EbiDataFetcherDelegate.setProcessExtnMeta()

You can configure this option:

 
Top of page

Index document content?

Indicates whether document content should be indexed.

Key in config.xml

Default

Tips

Set method

com.sssw.cm.fetch.process.content.repository name

true

  • Set to true to index document content.

  • Set to false to ignore document content and index only standard and/or custom document metadata.

EbiDataFetcherDelegate.setProcessContent()

You can configure this option:

 
Top of page

Index standard document metadata?

Indicates whether standard document metadata should be indexed. Standard metadata is descriptive information about content that is automatically attached to every document. Examples of standard metadata are title, author, and creation date.

Key in config.xml

Default

Tips

Set method

com.sssw.cm.fetch.process.metadata.repository name

true

  • Set to true to index document standard metadata.

  • Set to false to ignore standard document metadata and index only document content and/or custom document metadata.

EbiDataFetcherDelegate.setProcessMeta()

You can configure this option:

 
Top of page

Index port

Specifies the port number used by the DRE for indexing:

Key in config.xml

Default

Set method

com.sssw.cm.search.indexport.repository name

52001

EbiDataFetcherDelegate.setIndexPort()

You can configure this option:

 
Top of page

Install directory for binary document text filters

Specifies where Autonomy OmniSlave binary document text filters are installed.

Key in config.xml

Default

Tips

com.sssw.cm.fetch.binary.filters.dir

C:\exteNd\exteNd Director\Autonomy\OmniSlaves

Specify the directory where the Autonomy OmniSlave technology is installed

You can configure this option:

 
Top of page

Name of DRE database

Specifies the name of the DRE database that fetches documents from the Default CM repository.

Key in config.xml

Default

Tips

Set method

com.sssw.cm.search.repository.Default

com.sssw.cm.Default

If you override the default, make sure all search options that are specified for this database reflect the new name.

EbiDataFetcherDelegate.setDestRepository()

You can configure this option:

 
Top of page

Name of DRE host

Specifies the host name or IP address of the DRE that fetches documents from the default CM repository.

Key in config.xml

Default

Set method

com.sssw.cm.search.host.Default

localhost

EbiDataFetcherDelegate.setHost()

You can configure this option:

 
Top of page

Number of deleted documents to batch up

Specifies the number of deleted documents to batch up before removals are reflected in the DRE.

Key in config.xml

Default

Tips

com.sssw.cm.search.synch.removes.batch.size.repository name

100

This setting is relevant only if batch synchronization is enabled (com.sssw.cm.search.synch.mode is set to 1), as described in Synchronization mode.

You can configure this option:

 
Top of page

Operations that trigger immediate synchronization

Specifies the operations on documents that trigger immediate synchronization to reflect changes to metadata or content.

Key in config.xml

Default

Tips

com.sssw.cm.search.synch.docops.repository name

add; update; remove; checkin; checkout; publish; uncheckout; unpublish; unlock; rollback

This setting is relevant only if immediate synchronization is enabled (com.sssw.cm.search.synch.mode is set to 0), as described in Synchronization mode.

You can configure this option:

 
Top of page

Query port

Specifies the port number on which the DRE expects to receive queries.

Key in config.xml

Default

Set method

com.sssw.cm.search.queryport.repository name

52000

EbiDataFetcherDelegate.setQueryPort()

You can configure this option:

 
Top of page

Support binary document formats?

Indicates whether to enable support for indexing documents in binary formats.

Key in config.xml

Default

Tips

com.sssw.cm.fetch.handle.binary.repository name

true

  • Set to true to index documents developed in applications that produce binary formats, such as Adobe Acrobat and Microsoft Word and PowerPoint.

  • Set to false if you are indexing documents in text formats only—including XML, HTML, and other text documents.

You can configure this option:

 
Top of page

Symbol for concatenating multivalue custom metadata values before indexing

Specifies the delimiter symbol to use for concatenating multivalue custom metadata values before they are indexed into the DRE. You must specify a delimiter, because Autonomy does not support multivalue properties.

Key in config.xml

Default

Set method

com.sssw.cm.fetch.multivalue.delim.repository name

/

EbiDataFetcherDelegate.setMultiValueDelim()

You can configure this option:

 
Top of page

Synchronization mode

Specifies how the DRE propagates changes to documents in the CM repository.

Key in config.xml

Default

Tips

com.sssw.cm.search.synch.mode.repository name

0

(immediate mode)

  • Set to 0 for immediate mode—Propagate changes as soon as they occur. You can specify events to trigger synchronization in this mode, as described in Operations that trigger immediate synchronization.

  • Set to 1 for batch mode—Propagate changes as a scheduled or periodic background task. You can specify the number of deleted documents to batch up before removals are reflected in the DRE, as described in Number of deleted documents to batch up.

You can configure this option:



Copyright © 2004 Novell, Inc. All rights reserved. Copyright © 1997, 1998, 1999, 2000, 2001, 2002, 2003 SilverStream Software, LLC. All rights reserved.  more ...