Novell Doc: Novell Teaming 2.0 Installation Guide - Setting Up a High Availability Lucene Configuration

16.2 Setting Up a High Availability Lucene Configuration

16.2.1 Changing from a Local Lucene Index Server

To change from a local Lucene Index Server running on the Novell Teaming server, you must install the Lucene Index Server on two or more remote servers, then reconfigure Teaming for a high availability Lucene configuration.

NOTE:Although it is possible to use the Lucene Index Server on the Teaming server as one of the “remote” Lucene nodes, this is not a recommended configuration. Consider it only if you are restricted to two servers for your Teaming site.

Set up two or more Lucene nodes:
1. Install the Lucene Index Server on each node, as described in Section 14.1, Installing the Lucene Software.
2. (Optional) Copy accumulated index data from the initial Lucene Index Server to each additional Lucene node.
  
  The default location for the index files varies by platform:
  
  Linux:
  
  /var/opt/novell/teaming/lucene
  
  Windows:
  
  c:\Novell\Teaming\lucene
3. Start the Lucene Index Server on each Lucene node, as described in Section 14.3, Managing a Remote Lucene Index Server.
Stop Teaming.

If you have installed the Teaming software on multiple servers, as described in Section 15.0, Running Teaming on Multiple Servers, stop Teaming on all servers, or follow the instructions in Section 16.2.4, Changing Your Lucene Configuration without Teaming Site Down Time.
Run the Teaming Installation program to configure the Teaming server for multiple Lucene nodes.
1. On the Installation Settings page, select Reconfigure Settings, then click Next.
2. On the Choose Installation Type page, select Advanced, then click Next.
3. Click Next to proceed through the installation pages where no changes are needed.
4. On the Lucene Configuration page, fill in the following fields, then click Next.
  
  Lucene configuration type: Select high availability.
  
  Number of high availability search nodes: Specify the number of Lucene nodes where you have installed and started the Lucene Index Server.
5. On the Configure High Availability Search Nodes page, specify the configuration information for each Lucene node from the Advanced Teaming Installation Summary Sheet that you filled out in Section 16.1, Planning a High Availability Lucene Configuration, then click Next.
6. Click Next until you reach the Ready to Install page, then click Install.
7. On the Installation Complete page, click Finish.
8. Start Teaming.
9. (Conditional) If you have multiple Teaming servers, repeat Step 3 on each Teaming server.
Configure the Teaming site for the additional Lucene nodes:
1. Log in to the Teaming site as the Teaming administrator.
2. Click Manage > Site Administration.
3. Expand Manage the Search Index, then click Nodes.
  
  By default, the first Lucene node in the list has Read and Write access, meaning that Teaming updates it as new content is added to the Teaming site. By default, subsequent nodes in the list have Write Only access, meaning that the Teaming software can update content on the server, but users cannot access it. This setting is useful when you need to perform maintenance on a Lucene node, but it is not the setting you want when setting up a new Lucene node.
4. In the User Mode Access box, select Read and Write for all Lucene nodes, click Apply, then click Close.
  
  The new setting is put into effect immediately, so that users immediately have access to the additional Lucene nodes.
Skip to Section 16.3, Testing Your Lucene High Availability Configuration.

16.2.2 Changing from a Single Remote Lucene Index Server

To change from a single remote Lucene Index Servers to a high availability configuration, you must install the Lucene Index Server on one or more additional remote servers, then reconfigure Novell Teaming for additional Lucene nodes.

Bring down your Teaming site:
1. Stop Teaming.
  
  If you have installed the Teaming software on multiple servers, as described in Section 15.0, Running Teaming on Multiple Servers, stop Teaming on all servers, or follow the instructions in Section 16.2.4, Changing Your Lucene Configuration without Teaming Site Down Time.
2. Make sure that the existing remote Lucene Index Server also stops.
Set up one or more additional Lucene nodes:
1. Install the Lucene Index Server on each additional remote server, as described in Section 14.1, Installing the Lucene Software.
2. (Optional) Copy accumulated index data from the initial remote Lucene node to each additional Lucene node.
  
  The default location for the index files varies by platform:
  
  Linux:
  
  /var/opt/novell/teaming/lucene
  
  Windows:
  
  c:\Novell\Teaming\lucene
3. Start the Lucene Index Server on each Lucene node, as described in Section 14.3, Managing a Remote Lucene Index Server, but do not bring up your Teaming site.
Run the Teaming Installation program to configure the Teaming server for multiple Lucene nodes.
1. On the Installation Settings page, select Reconfigure Settings, then click Next.
2. On the Choose Installation Type page, select Advanced, then click Next.
3. Click Next to proceed through the installation pages where no changes are needed.
4. On the Lucene Configuration page, fill in the following fields, then click Next.
  
  Lucene configuration type: Change server to high availability.
  
  Number of high availability search nodes: Specify the number of Lucene nodes where you have installed the Lucene Index Server.
5. On the Configure High Availability Search Nodes page, specify the configuration information for each Lucene node from the Advanced Teaming Installation Summary Sheet that you filled out in Section 16.1, Planning a High Availability Lucene Configuration, then click Next.
6. Click Next until you reach the Ready to Install page, then click Install.
7. On the Installation Complete page, click Finish.
8. Start Teaming.
9. (Conditional) If you have multiple Teaming servers, repeat Step 3 on each Teaming server.
Configure the Teaming site for the additional Lucene nodes:
1. Log in to the Teaming site as the Teaming administrator.
2. Click Manage > Site Administration.
3. Expand Manage the Search Index, then click Nodes.
  
  By default, the first Lucene node in the list has Read and Write access, meaning that Teaming updates it as new content is added to the Teaming site. By default, subsequent nodes in the list have Write Only access, meaning that the Teaming software can update content on the server, but users cannot access it. This setting is useful when you need to perform maintenance on a Lucene node, but it is not the setting you want when setting up a new Lucene node.
4. In the User Mode Access box, select Read and Write for all Lucene nodes.
5. Click Apply, then click Close.
  
  The new setting is put into effect immediately, so that users immediately have access to the additional Lucene nodes.
Skip to Section 16.3, Testing Your Lucene High Availability Configuration.

16.2.3 Expanding an Existing High Availability Lucene Configuration

After you have set up an initial high availability Lucene configuration, you can add additional Lucene nodes at any time.

Bring down your Teaming site:
1. Stop Teaming.
  
  If you have installed the Teaming software on multiple servers, as described in Section 15.0, Running Teaming on Multiple Servers, stop Teaming on all servers, or follow the instructions in Section 16.2.4, Changing Your Lucene Configuration without Teaming Site Down Time.
2. Stop all Lucene nodes, as described in Section 14.3, Managing a Remote Lucene Index Server.
Set up one or more additional Lucene nodes:
1. Install the Lucene Index Server on each additional remote server, as described in Section 14.1, Installing the Lucene Software.
2. (Optional) Copy accumulated index data from an existing Lucene node to each additional Lucene node.
  
  The default location for the index files varies by platform:
  
  Linux:
  
  /var/opt/novell/teaming/lucene
  
  Windows:
  
  c:\Novell\Teaming\lucene
3. Start the Lucene Index Server on each Lucene node, as described in Section 14.3, Managing a Remote Lucene Index Server, but do not bring up your Teaming site.
Run the Teaming Installation program to configure the Teaming server for the additional Lucene nodes.
1. On the Installation Settings page, select Reconfigure Settings, then click Next.
2. On the Choose Installation Type page, select Advanced, then click Next.
3. Click Next to proceed through the installation pages where no changes are needed.
4. On the Lucene Configuration page, increase the number of nodes in the Number of high availability search nodes field, then click Next.
5. On the Configure High Availability Search Nodes page, specify the configuration information for each additional Lucene node, then click Next.
6. Click Next until you reach the Ready to Install page, then click Install.
7. On the Installation Complete page, click Finish.
8. Start Teaming.
9. (Conditional) If you have multiple Teaming servers, repeat Step 3 on each Teaming server.
Configure the Teaming site for the additional Lucene nodes:
1. Log in to the Teaming site as the Teaming administrator.
2. Click Manage > Site Administration.
3. Expand Manage the Search Index, then click Nodes.
  
  By default, the first Lucene node in the list has Read and Write access, meaning that Teaming updates it as new content is added to the Teaming site. By default, subsequent nodes in the list have Write Only access, meaning that the Teaming software can update content on the server, but users cannot access it. This setting is useful when you need to perform maintenance on a Lucene node, but it is not the setting you want when setting up a new Lucene node.
4. In the User Mode Access box, select Read and Write for all Lucene nodes.
5. Click Apply, then click Close.
  
  The new setting is put into effect immediately, so that users immediately have access to the additional Lucene nodes.
Skip to Section 16.3, Testing Your Lucene High Availability Configuration.

16.2.4 Changing Your Lucene Configuration without Teaming Site Down Time

Teaming site down time can be avoided only if you have installed the Novell Teaming software on multiple servers, as described in Section 15.0, Running Teaming on Multiple Servers.

To change to a high availability Lucene configuration in a multiple Teaming server configuration:

Set up two or more Lucene nodes:
1. Install the Lucene Index Server on each node, as described in Section 14.1, Installing the Lucene Software
2. Start the Lucene Index Server on each Lucene node, as described in Section 14.3, Managing a Remote Lucene Index Server.
Stop Teaming on one server.

The other Teaming servers remain in service for users and continue to communicate with the original Lucene Index Server.
Run the Teaming Installation program on the Teaming server that you stopped to configure it for multiple Lucene Index Servers.
1. On the Installation Settings page, select Reconfigure Settings, then click Next.
2. On the Choose Installation Type page, select Advanced, then click Next.
3. Click Next to proceed through the installation pages where no changes are needed.
4. On the Lucene Configuration page, fill in the following fields, then click Next.
  
  Lucene configuration type: Select high availability.
  
  Number of high availability search nodes: Specify the number of Lucene nodes where you have installed the Lucene Index Server.
5. On the Configure High Availability Search Nodes page, specify the configuration information for each Lucene node from the Advanced Teaming Installation Summary Sheet that you filled out in Section 16.1, Planning a High Availability Lucene Configuration, then click Next.
6. Click Next until you reach the Ready to Install page, then click Install.
7. On the Installation Complete page, click Finish.
Start the reconfigured Teaming server.
Access the reconfigured Teaming server and prevent access to the additional Lucene nodes:

IMPORTANT:All Teaming servers must be reconfigured before any of them access the additional Lucene nodes.
1. Log in to the reconfigured Teaming server as the Teaming administrator, using the server hostname rather than your Teaming site URL.
2. Click Manage > Site Administration.
3. Expand Manage the Search Index, then click Nodes.
  
  By default, the first Lucene node in the list has Read and Write access, meaning that Teaming updates it as new content is added to the Teaming site. By default, subsequent nodes in the list have Write Only access, meaning that the Teaming software can update content on the server, but users cannot access it. When setting up a high availability Lucene configuration without Teaming site down time, you need to prevent write access during the reconfiguration process.
4. In the User Mode Access box, change Write Only to No Access for the additional Lucene nodes.
5. Click Apply, then click Close.
  
  The new setting is put into effect immediately, so that the reconfigured Teaming server does not communicate with the additional Lucene nodes.
Reconfigure the rest of the Teaming servers:
1. Stop each Teaming server.
2. Repeat Step 3 to configure each Teaming server for the additional Lucene nodes.
3. Start each reconfigured Teaming server.
Access the reconfigured Teaming site and allow write access to the additional Lucene nodes:
1. Log in to the reconfigured Teaming as the Teaming administrator.
2. Click Manage > Site Administration.
3. Expand Manage the Search Index, then click Nodes.
4. In the User Mode Access box, change No Access to Write Only for the additional Lucene nodes.
5. Click Apply, then click Close.
  
  The new setting is put into effect immediately, so that the reconfigured Teaming servers can now communicate with the additional Lucene nodes, although user access is still disallowed.
Reindex the Teaming site, so that the additional Lucene nodes are updated with the same index data that the original Lucene Index Server has:
1. On the Site Administration page, click Index.
2. Select Home Workspace, so that the entire Teaming site is reindexed.
3. Select the additional Lucene nodes, but do not select any previously existing nodes.
4. Click OK to start the indexing.
  
  Depending on the size of your Teaming site, reindexing can be a time-consuming process. However, because one or more previously existing Lucene Index Servers are still servicing the Teaming site, users are not affected by the reindexing process.
5. When the reindexing is completed, click Close.
Make the additional Lucene nodes available to Teaming users:
1. On the Site Administration page, expand Mange the Search Index, then click Nodes.
2. In the User Mode Access box, change Write Access to Read and Write for the additional Lucene nodes.
3. Click Apply, then click Close.
  
  The new setting is put into effect immediately, so that Teaming users have additional Lucene Index Servers available as they use the Teaming site.

Linux:	/var/opt/novell/teaming/lucene
Windows:	c:\Novell\Teaming\lucene