Configure clustering to provide high availability of servers in an IBM® Lotus® Quickr™ service. There are two aspects to clustering: configuring IBM Lotus Domino® clustering to replicate data across the servers, and configuring a solution for distributing HTTP requests to the servers in the cluster.
About this task
Administering and managing a Lotus Quickr server that is in a cluster is the same as administering and managing a server that is not clustered. With the exception of adjustments to the load balancing hardware and software, you make changes individually to each server by addressing the server directly by its hostname or Domino name when you use any of the following methods or tools:
- Using the browser to sign in to the server and visiting the Site Administration link.
- Using the IBM Lotus Notes® or the Domino Administrator to make changes, usually to the Lotus Domino Directory.
- Setting up the Place Catalog for a cluster encompasses setting up My Places for your cluster.
- Making changes using the file system such as modifying the NOTES.INI file or qpconfig.xml file or inspecting HTTP logs.
Changes made through the Site Administration
link do not replicate; you must make these changes on each server in a cluster.
When you run a qptool
command on a server in a cluster, Lotus Quickr applies the command only to the server on which you run it. The results of the command then replicate to the other servers in the cluster. For example, if you lock a place on one server in a cluster, the place is locked immediately only on that server. The place is locked on the other servers after replication replicates the lock property on the place's databases to the other servers.
Perform the following steps to configure clustered servers:
Creating a Lotus Domino cluster
A Lotus Domino cluster is a group of two to six Lotus Domino servers that provides users with constant access to data, balances the workload between servers, improves server performance, and maintains performance when the size of your enterprise increases. The servers in a cluster contain replicas of databases that you want to be readily available to users at all times. If a user tries to access a database on a cluster server that is unavailable, Domino opens a replica of that database on a different cluster server, if a replica is available. Domino continuously synchronizes databases so that whichever replica a user opens, the information is always identical.
Implementing a method for distributing HTTP requests
You can choose between two methods of distributing HTTP requests to servers in the cluster: load balancing or failover to a "hot-spare." Note that IBM Lotus Quickr requires that HTTP requests sent to one node are continuously sent to that node for a predetermined amount of time known, sometimes referred to as "sticky time."
Modifying scheduled qptool commands in the notes.ini file
You must modify scheduled qptool
commands in server notes.ini files.
Setting up the Place Catalog for a cluster
To ensure that a shared Place Catalog works properly for servers in a cluster, replicate the Place Catalog on the Place Catalog server to the other IBM Lotus Quickr servers in the cluster, and specify the details of the cluster environment in the qpconfig.xml file of each server in the cluster. All servers in a cluster should use the same qpconfig.xml settings.
Parent topic: Installing and upgrading