The configuration file under $CADENAS_SETUP/filesystems.cfg
controls whether caching of the CADENAS_DATA index files should take place:
Variant A: We recommend not to combine search server and $CADENAS_DATA on the same server.
If you follow the recommendation, then please activate the index files caching, because otherwise the search server does not work efficiently. Now the cadenas_data/index directory will be replicated. Local hard disk storage has to be available accordingly.
Variant B: If search server and $CADENAS_DATA are on the same server, the caching is not necessary.
USECACHEFS=1 (default = 0 = off)
Select 1 if you have set either the option Catalogs, search and database via AppServer [Catalog browsing, search and database with AppServer] or Catalogs and search via AppServer [Catalog browsing and search with AppServer] or Search via AppServer [Search with AppServer] in PARTadmin and the PARTapplicationServer and $CADENAS_DATA are not on the same server.
Declaration of the caching directory
SYNCDIR=$CADENAS_USER/cache_index
=> Thus the cache index is stored under "C:\windows\system32\config\systemprofile\cache_index". If this is not wanted, then any other path can be adjusted.
![]() | Note |
---|---|
Due to PARTapplicationServer's own caching an additional Windows File Caching is not necessary.[14] It can possibly slow down the search on the server significantly. |
![]() | Note |
---|---|
A diagram showing the different caching methods can be found at Section 1.3.5.4, “Caching methods for data storage and operation ”. |