The following table shows the location of some directories that may be needed to effectively work with LucidWorks Enterprise. These paths are all relative to the "LWE Home" directory ($LWE_HOME) which is specified when running the installer.
|Documentation|| $LWE_HOME/docs/ (PDF format) and $LWE_HOME/lwe-core/doc/ (HTML format)
|Logs||$LWE_HOME/logs/ (See below for log file list)|
|LucidWorks Indexes|| $LWE_HOME/solr/cores/collection_name/data/
|Solr Source Code|| $LWE_HOME/solr-src/
|Editing Configuration Files on Windows|
LucidWorks Enterprise holds configuration files open after reading them, which may cause problems on Windows systems that do not allow editing open files. In this case, stop LucidWorks Enterprise before editing files on Windows to be sure the edits are saved properly.
LucidWorks Enterprise records system activities to rolling log files located in the $LWE_HOME/logs directory of the installation. The table below describes the main purpose of the various log files.
|$LWE_HOME/logs/core.<YYYY_MM_DD>.log||LWE Core operations, including information from crawling activities|
|$LWE_HOME/logs/core-stderr.log||Errors from Jetty startup|
|$LWE_HOME/logs/core-stdout.log||Messages from Jetty startup|
|$LWE_HOME/logs/request.<YYYY_MM_DD>.log||API requests from front-end systems (Search, Admin and Alerts) to the back-end LWE Core|
|$LWE_HOME/logs/ui.log||Information from the Rails application, which runs the Search, Admin and Alerts components|
|$LWE_HOME/logs/ruby-stderr.log||Errors from Ruby startup|
|$LWE_HOME/logs/ruby-stdout.log||Messages from Ruby startup|
|$LWE_HOME/logs/click-<collectionName>.log||User click data, for use in relevance boosting (if enabled)|
|$LWE_HOME/logs/alert_trace.log||Alert heartbeat that checks for new alerts to run|
|$LWE_HOME/logs/google_connectors.feed.log||SharePoint crawling operations. Note, this file can also include a number in the name, such as google_connectors.feed0.log, etc.|
The LucidWorks Enterprise Core log is configured by a properties file ($LWE_HOME/conf/log4j.xml). The default is to create a distinct log per date (server time). Only data from the most recent core.YYYY_MM_DD.log file is included in query and index history calculations that appear in the Admin User Interface.
|Rotation of the ui.log File|
On Windows machines, log rotation of the ui.log file only has been disabled. The LWE Core log will still be date specific, but the ui.log will need to be manually rotated.