Locating Files and Directories
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.
| What | Path |
|---|---|
| Solr Home | $LWE_HOME/solr/ |
| Jetty Libraries | $LWE_HOME/jetty/lib/ |
| Configuration Files | $LWE_HOME/conf/ |
| Logs | $LWE_HOME/logs/ |
System Logs
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.
| Log Name | Function |
|---|---|
| $LWE_HOME/logs/lucid.log | LWE Core operations |
| $LWE_HOME/logs/rails.log | Search, Admin, and Alerts operations |
| $LWE_HOME/logs/click-<collectionName>.log | User click data, for use in relevance boosting (if enabled) |
The LucidWorks Enterprise log is configured by a properties file ($LWE_HOME/conf/log4j.properties). The default is to archive each log every day at Midnight (server time). Additionally, LucidWorks Enterprise limits the number of logs that are archived to a configurable amount (default is to keep all logs). The archived log files are also found in the logs directory under the installation ($LWE_HOME/logs). Once logs are archived, data from archived log files is no longer included in query or index history calculations that appear in the Administration User Interface.
 | Log Rotation on Windows On Windows machines, log rotation of the rails.log file only has been disabled. The other logs will rotate daily, but the rails.log will need to be manually rotated. |