A high availability Lucene Index Server configuration must include at least two different servers (either physical or virtual), referred to as “nodes” in the Vibe installation program. Lucene nodes in a high availability configuration can be set up on Linux servers, Windows servers, or both.
Each Lucene node must have its own independent directory structure for index files. The default location for the index files for the Lucene Index Server varies by platform:
|
Linux: |
/var/opt/novell/teaming/lucene |
|
Windows: |
c:\Novell\Teaming\lucene |
As you plan your high availability Lucene configuration, you can use the Advanced Vibe Installation Summary Sheet to record the options you want to use.
|
ADVANCED VIBE INSTALLATION SUMMARY SHEET |
|---|
|
Under High Availability Lucene Configuration, specify the number of Lucene nodes that you want in your high availability Lucene configuration. |
Each Lucene node needs a unique name, a descriptive title, and a static IP address. The name and title identify the node in the Vibe administrative interface. Typically, the Lucene Index Server listens on RMI port 1199 on its server, but you can configure it to use a different port number if the default port number is already in use.
|
ADVANCED VIBE INSTALLATION SUMMARY SHEET |
|---|
|
Under High Availability Lucene Configuration, specify the name, description, IP address, and RMI port number for each Lucene node. |
If you have already accumulated index data on your initial Vibe server, you can choose to copy the index files to the Lucene nodes, or you can reindex the Vibe site after the new Lucene nodes are running. Depending on the amount of accumulated index data, reindexing can be a time-consuming process.
The Vibe server and the Lucene nodes must not have a firewall between them. The RMI protocol used for the Lucene Index Server port works only within a trusted local area network (LAN).