Why using a search server?

The search server speeds up the search (full-text search, variable search, geometrical search).

Implementing a search server does not change any processes. Everything remains the same for the user.

Whether or not a search server should be implemented mainly depends on the type of installation.

Install search server as service (via installation routine)

The respective dialog box appears in the course of a client-server installation in the server installation section.

Install search server as service (via command line) + Launching the server (service)

Register the search server (pssearchctrl.exe) in the "bin" directory via command line as service with the parameter "-install".

pssearchctrl -install

Command line: Install service with "pssearchctrl -install"

	Note
	Do not mix up "pssearchctrl" and "pssearchserver". "pssearchctrl" starts and controls the search server.

Commands:

Search server activation in configuration file

Perform the activation under $CADENAS_SETUP/partsol.cfg -> section [REMOTESEARCH] -> Key enabled -> Values: 0 = 0ff; 1 = on

If the search server is off, then the search is locally performed on the client via PARTdataManager.

CACHE activation

	Note
	Caching is officially available as of version 9.04 (as of v9.03 not yet well-engineered, experimental). If a search server is activated, caching of the index files is recommended due to performance reasons, if CADENAS_DATA and search server are not operating on the same server.

	Note
	Recommendation for multi site installations: We recommend to install a central search server at the head quarter. CADENAS_DATA (catalogs) should be replicated to a file server of the respective secondary locations. In this replication the Lucene index files do not have to be included.

The configuration file is found under %cadenas_setup%/filesystems.cfg.

	Note
	The following excerpt of the configuration file shows the caching settings, but may possibly differ at release v9.04. In preceding release versions the setting options are similar.

[CACHEFS(psearchserver)]
#Caching activation
USECACHEFS=1
#Root directory, which has to be cached
CACHEROOT=$CADENAS_DATA/index
#Cache directory
SYNCDIR=$CADENAS_USER/cache_index
#which regex under CACHEROOT not to cache
 (ignore completely)
NOCACHE=.*index.cfg|.*index.idx
#Regular expressions under CACHEROOT, which have to be synchronized to $SYNCDIR
 and have to be checked concerning changes
SYNCLOCAL=.*lucene.*|.*geoindex.*|.*index.ic2t|.*index0.ic2t|.*index0.c2t|.*index.0.node.*
 |.*index.0.data.*
#Sync settings
# as of which KB size copying happens in a side thread
SYNCINLINELIMIT=100
# Interval, wherein changes are checked
SYNCCHECKSECONDS=180
# Number of Sync Threads, which check for changes on the filer at the same time
MAXSYNCTHREADS=100

Important settings:

Due to index file caching it is also possible to operate search server and $CADENAS_DATA on different servers.

More detailed information is found here: