By means of the elements of this system configuration entry, which can be found in the instance-specific
config/tuning.xml file, the operation of Fiona can be optimized.
clearCachesFrequency: Number of commands or exported files after which the Tcl Server clears its cache.
export: Parameters for optimizing the export:
acceptableFailures: The maximum number of file export failures not causing the export process to terminate.
maxNumberOfExportedObjects: The maximum number of files a Template Engine slave exports before the master replaces it with a new slave.
maxParallelExports: The maximum number of slaves of a Template Engine master exporting data simultaneously. This value should only be increased, if the export does not fully occupy the system, i. e. if unused CPU and I/O resources still exist. At least one slave should always be available for external requests, meaning that
maxParallelExports should always be less than
maxRecursionLevel: The maximum recursion depth in nested NPSOBJ instructions.
timeout: The maximum number of seconds the Template Engine master waits for a slave to export the file assigned to it.
usesAllThreshold: The maximum number of files on which a file may depend. If this number is exceeded, the dependencies are replaced with a single general dependency.
indexing: The following parameters ensure that during high system load not too many documents need to be indexed at once and that during low system load not too much time elapses between two indexing processes.
filterTimeout: Time (in milliseconds) the Verity filter application (located in bin/IF below the Instance directory) may take for filtering a blob (default: 300, used by the SES). The filters use the value 0 to switch off the timeout.
interval: Period of time after which the accumulated documents are indexed at the latest.
maxBulkSize: Maximum number of documents that may accumulate without starting an indexing process (i. e. indexing is forced to take place when this number is exceeded).
optimizationInterval: The interval at which the Search Engine Server optimizes its collections. 0 or a negative value disables optimization.
jobMaxLogLength: The value of this entry determines the maximum number of log entries that are to be kept.
master: Defines parameters that refer to the main instance of the respective application.
cm: Defines the optimization parameters of the Content Management Server.
busySlavesWarningThreshold: Specifies the number of busy slaves reached or exceeded that causes a warning to be written to the log file. If no value has been specified, or the value is
0 or less, or greater than
maxSlaves is used. Alteratively, a percentage can be specified which then refers to the value of
70% results in a warning threshold of 4 slaves.
maxSlaves: Maximum number of slaves permitted to run simultaneously.
minIdleSlaves: Minimum number of idle slaves. The master server ensures that at least this number of slaves are ready to accept requests.
slaveExecArguments: Command line arguments passed to a slave.
ses: Defines the optimization parameters of the Search Engine Server. This elements has the same subelements as
slaveExecMaxFailures: Maximum number of slave execution failures after which the master server terminates.
slaveIdleTimeout: Time in seconds after a slave not processing a request is considered idle.
slaveShutdownTimeout: Time in seconds a slave may take to terminate.
slaveStartupTimeout: Time in seconds after which an executed slave must be ready.
te: Defines the optimization parameters of the Template Engine. This element has the same subelements as
minStreamingDataLength: The size in KB a main content of a version or the contents of a resource needs to have for the application to send it to the Search Engine Server via the streaming interface. If this value is zero, streaming is not used and the data is inserted into the payload sent to the Search Engine Server instead. The Content Management Server also uses streaming when communicating with the HTML-GUI.
slave: Defines parameters relating to the slave instances of the respective applications.
masterTimeout: Number of milliseconds a slave communicating with the master server waits for it to fully read the data. If the data could not be read in this period of time, the slave terminates assuming that the communication between itself and the master is disturbed. 0 (zero) means, that no timeout is used (the slave waits forever).
maxNumberOfRequests: The maximum number of requests a slave accepts.
requestTimeout: The time in seconds after which a slave running idle closes its connection to the client to be free for new requests.
streamingTicketValidityTimeInterval: The value of this entry determines how long streaming tickets are valid. The value is given as an integer number which is interpreted as the period of time in seconds. A streaming which is ticket older than specified here is deleted.
userManProxy: Settings of the user manager proxy.
true(which is the default) enables the authentication cache. This value should be set to
falsewith external user managers.