There are two ways to install LucidWorks Search on-premise:
- You can run the installer in graphical mode, which guides you through a series of dialog boxes, then installs and configures the software.
- You can run the installer in console mode, which limits the installer's interface to the command line. If you do not have access to the graphical user interface of the system you are installing the software on, run the installer in console mode.
For Linux and Mac systems, the install file is called lucidworks-search-installer-2.5.jar.
For Windows systems, the install file is called lucidworks-search-installer-2.5.exe. On Windows, the installer should be run with Administrator privileges to ensure proper installation. During installation, you will be prompted to install LucidWorks Search as a service. While this enables automatic restart, it is not designed as a monitoring or watchdog service that restarts if a dependent process fails.
You must have Java 1.6 or higher (JRE or JDK) installed and in your path before you install LucidWorks Search.
Supported Operating Systems:
- 32-bit and 64-bit versions of Windows XP, Windows Vista, Windows 7 and Windows Server 2003
- Linux-based operating systems with a 2.4 kernel or later
- Mac OS X 10.5+
- CentOS v.5.0+
Apache Solr runs in a Java servlet container and the LucidWorks Search installer automatically installs and configures Jetty, an open source Java servlet container. At this time, Jetty is the only servlet container that can be used with LucidWorks. LucidWorks Search has been designed around using Jetty as the container and it's not possible to run it in any other container.
- Minimum: 2GB RAM
- Recommended for 100,000 to 1,000,000 documents: 4GB-8GB RAM, 2GHz dual-core CPU
- Recommended for greater than 1,000,000 documents: 8GB-16GB RAM, 2.4GHz dual-core CPU
Required disk space depends on the size and number of documents to be indexed. Contact LucidWorks for assistance in determining the disk space needed for your implementation.
If the LucidWorks crawlers will be used to index documents over the network, the server where the LWE-Connectors component is installed must have access to the servers that host the content repositories to be crawled.
If opting-in to the LucidWorks System Usage Monitor, the LWE-Core component must be able to send outgoing encrypted POST requests to https://heartbeat.demo.lucidworks.io.