The Sun Cluster HA for Lotus product consists of the Lotus Domino server made highly available by running it in the Sun Cluster environment.
To run Sun Cluster HA for Lotus under Sun Cluster, you must:
Install and configure Sun Cluster (which includes Sun Cluster HA for Lotus) using the instructions in Chapter 3, Installing and Configuring Sun Cluster Software
Complete the Lotus Domino pre-installation tasks described in your Lotus Domino documentation
Install and configure Lotus Domino using the instructions in your Lotus Domino documentation
(Lotus Domino 4.6.3 only) Optionally, install and configure partitioned servers, using the instructions in "Installing and Configuring Lotus Domino Partitioned Servers"
Configure Lotus Domino to run under Sun Cluster using the hadsconfig(1M) command
Verify the Sun Cluster HA for Lotus configuration
The procedures described in this chapter assume that you are familiar with the Sun Cluster concepts of disksets, logical hosts, physical hosts, switchover, takeover, and data services.
Before you install and configure Sun Cluster HA for Lotus, you first must install and configure the Sun Cluster framework. Then use the procedures in the following sections to install and configure Sun Cluster HA for Lotus.
You can install Lotus Domino primary server binaries and partitioned server binaries on either the local disk of each cluster node or on a shared disk. If you choose to install Lotus Domino binaries or partitioned server binaries on the local disk, you must install them on all cluster nodes. Always install data directories on the shared disk.
Installing the binaries on the shared disk eases administration and consumes less disk space, but increases down time during application upgrades, because the application must be brought down for the duration of the binary upgrade.
Installing the binaries locally on each node preserves high availability during failover, and also reduces downtime during future upgrades of the application. You can upgrade the binaries on a node that is not currently hosting the application, switch the application over to that node, then upgrade the binaries on the original node. The application remains available except for during the brief switchover period.
Lotus Domino servers can be set up as HTTP, POP3, IMAP, NNTP and LDAP servers. Some restrictions exist when you include Lotus Domino servers and Sun Cluster HA for Netscape servers in the same cluster. Use the general guidelines outlined in Table 13-1 to determine which Lotus Domino server tasks to specify during installation.
When assigning port numbers, do not use ports already reserved by Sun Cluster or Solaris. See "Default Port Numbers Reserved by Sun Cluster" for details.
Table 13-1 Lotus Domino Server Options - General Guidelines
Server Task |
Client Types Supported |
Limitations |
Default Port |
HTTP |
Web browsers (Netscape Navigator, Microsoft Internet Explorer, and others) |
When Netscape Enterprise Server and Lotus HTTP server are both installed in one cluster, assign an unused port number to Netscape Enterprise Server. |
80 |
IMAP |
Internet mail clients using Post Office Protocol 3 (POP3) or Internet Message Access Protocol |
When Netscape Mail and the Lotus IMAP server are both installed in one cluster, assign an unused port number to Netscape Mail. |
110 (POP3) 143 (IMAP) |
LDAP |
Internet Directory Clients using Lightweight Directory Access Protocol (LDAP) |
When Netscape Directory Server and the Lotus LDAP server are both installed in one cluster, assign an unused port number to Netscape Directory Server. |
389 |
NNTP |
Internet news readers using Network News Transfer Protocol (NNTP) |
When Netscape Collabra Server and the Lotus NNTP server are both installed in one cluster, assign an unused port number to Netscape Collabra Server. |
119 |
SMTP/MIME |
Internet mail clients using Simple Mail Transfer Protocol (SMTP) |
When Netscape Messaging Server (or Netscape Mail Server) and Lotus SMTP/MIME are both installed in one cluster, assign an unused port number to the Netscape application. |
n/a |