General Settings

The table below details the general settings for a project. The name, variable name, variable type, description, and default are defined for each setting.

Note: Your Watson™ Explorer Engine search application may or may not require the configuration of these parameters. If the description of the parameters listed here does not clearly identify its potential use in your search application, please contact IBM support for clarification.
Table 1. General Settings
Setting Name Type Description

Enable general debugging



When true, Watson Explorer Engine will print a debugging log in debug-dir. This debugging log is in XML format and can be browsed using the administration tool (see reporting.debug). Do not turn this option on by default as it affects the performance of the software and may quickly fill up the disk.

Default: false

Do not output repository elements in the XML



Reduce the size of the XML output by discarding elements which come from the repository. Should be safe in most case but makes the XML serialization of the Watson Explorer Engine object slightly incorrect.

Default: true

Encrypt the Vivisimo output XML when writing to files



Encrypting XML output will ensure that no critical information (like username & password) is plain-text readable, in particular in temporary files. 3DES encryption is used.

Default: false

Enable general profiling



When true, Watson Explorer Engine will perform light debugging allowing to use the debug log for profiling. Note that debug needs to be turned on for this option to work.

Default: false

Application reporting database directory



The directory to use for the database files for application reporting information.

Default: {install-dir}/data/reporting

The path of a file to which debugging information will be written (use "-" for stderr)



A writeable file (with full path or path relative to the working directory) into which some debugging information will be printed (this is a "lightweight" alternative to the debug-dir option). If debug is not on, only the warning and error messages will be printed.

Enable efficient paging



Retrieves documents from sources in a more efficient manner, allowing a larger number of documents to be returned. This feature is incompatible with certain other Velocity features.

Default: false

Number of documents to cluster when efficient paging is enabled



When efficient paging is enabled, not all documents will be retrieved up front and thus are not available for clustering. This option controls how many of the top-ranked documents will be retrieved and used for clustering.

Default: 200

Enable assertion on errors



Default: false

Maximum documents to process



Default: -1