A main system configuration difference between a GroupWise system in a clustering environment and a GroupWise system in a regular environment is that you need to create a separate domain to house each GroupWise gateway, including the WebAccess Agent.
The WebAccess Clustering Worksheet lists all the information you will need as you set up the WebAccess Agent and the WebAccess Application in a clustering environment. You should print the worksheet and fill it out as you complete the tasks listed below:
IMPORTANT: NetWare 6.5 provides Apache and Tomcat instead of the Netscape Enterprise Web Server, which was provided on NetWare 6. However, NetWare 6.5 Support Packs currently cannot update an Apache/Tomcat installation that is located on cluster-enabled volume. Consequently, clustering WebAccess with Apache and Tomcat is not currently supported by Novell. However, helpful instructions are available from Tay Kratzer at www.taykratzer.com.
Although several Web servers are supported for use with GroupWise WebAccess in a non-clustered environment, only the Netscape Enterprise Server for NetWare is supported in a clustering environment because it is the only currently supported Web server that runs on NetWare 6. In preparation for installing WebAccess in your clustered GroupWise system, install and set up the Netscape Enterprise Server for NetWare, following the instructions in "Configuring NetWare Enterprise Web Server with Novell Cluster Services" in NetWare Cluster Services Resource Configuration Guide.
As you set up the Netscape Enterprise Server, record the following key configuration information on the WebAccess Clustering Worksheet:
| WEBACCESS CLUSTERING WORKSHEET |
|---|
Under Item 10: Physical Web Servers, list the physical NetWare servers where you are installing the Netscape Enterprise Server software. Under Item 11: Netscape Enterprise Server IP Address, record the secondary IP address of the Netscape Enterprise Server cluster resource that you create. Under Item 12: Netscape Enterprise Server Mode, mark whether you have configured the Netscape Enterprise Server to run in active/active or active/passive mode. In active/active mode, the Netscape Enterprise Server runs on multiple nodes simultaneously; this is the recommended mode. Under Item 13: Netscape Enterprise Server Failover Path, list the nodes in the cluster where you want the Netscape Enterprise Server cluster resource to fail over. Under Item 14: Hardware Virtual Server Information, record the dedicated IP address for the Web site and the document root directory. |
The Netscape Enterprise Server for NetWare does not depend on the functionality of cluster-enabled volumes the way GroupWise does. Because the WebAccess Application will be installed to a subdirectory of the Netscape Enterprise Server installation directory (sys:\novonyx\suitespot\docs\com\novell\webaccess), the WebAccess Application cannot be installed on a cluster-enabled volume. Instead, you will install it to the sys: volume on each node where the Netscape Enterprise Server has been installed.
The considerations involved in planning a domain for the WebAccess Agent are much the same as planning any other domain. In preparation, review "Planning a New Domain", then print and fill out the "Domain Worksheet" in "Domains" in the GroupWise 6.5 Administration Guide.
Keep in mind the following cluster-specific details:
When you have completed the Domain Worksheet, transfer the key information from the Domain Worksheet to the WebAccess Clustering Worksheet.
| WEBACCESS CLUSTERING WORKSHEET |
|---|
Under Item 1: Shared Volume for WebAccess Agent, transfer the domain location from the Domain Worksheet to the WebAccess Clustering Worksheet. Under Item 2: WebAccess Agent Domain Name, transfer the domain name and database directory from the Domain Worksheet to the WebAccess Clustering Worksheet. |
You should plan to cluster-enable the shared volume where the WebAccess Agent domain will reside. For a review of the benefits of cluster-enabling volumes, see Deciding Whether to Cluster-Enable the Shared Volumes Used by GroupWise, which describes the issues in the context of planning MTA and POA installations.
| WEBACCESS CLUSTERING WORKSHEET |
|---|
Under Item 1: Shared Volume for WebAccess Agent, mark Yes under Cluster Enabled?. |
Cluster-enabling relies on successful short name resolution throughout your system. Review Ensuring Successful Name Resolution for GroupWise Volumes, which describes the issues in the context of planning MTA and POA installations.
As with the MTA and the POA, you need to decide which nodes in the cluster would be appropriate locations where the WebAccess Agent volume could fail over. For a review of failover paths, see Determining Appropriate Failover Paths for the Agents, which describes the issues in the context of planning MTA and POA installations.
| WEBACCESS CLUSTERING WORKSHEET |
|---|
Under Item 4: WebAccess Agent Failover Path, list the nodes that you want to have in the WebAccess Agent volume failover path. |
As with the MTA and the POA, the WebAccess Agent needs a secondary IP address and cluster-unique port numbers. As part of planning to install the MTA and POA, you should already have determined the secondary IP address and cluster-unique port numbers for the WebAccess Agent and its MTA as you filled out the IP Address Worksheet. If you do not have a filled-out copy of this worksheet for your system, print it now and fill in current system information.
| WEBACCESS CLUSTERING WORKSHEET |
|---|
Under Item 6: MTA Network Information, transfer the MTA secondary IP address and cluster-unique port numbers from the WebAccess section the IP Address Worksheet to the WebAccess Clustering Worksheet. Under Item 1: Shared Volume for WebAccess Agent, copy the MTA secondary IP address under Cluster Volume IP Address as well, because they are the same. Under Item 8: WebAccess Agent Network Information, transfer the WebAccess Agent secondary IP address (the same as for its MTA) and the cluster-unique WebAccess Agent port number from the WebAccess section of the IP Address Worksheet to the WebAccess Clustering Worksheet. |
As with the MTA and the POA, you can choose to install the WebAccess Agent and its MTA to the sys:\system directory of each node or to a vol:\system directory on the WebAccess Agent volume. For a discussion of these alternatives, see Deciding Where to Install the Agent Software , which describes the issues in the context of planning MTA and POA installations. If you only have one WebAccess Agent for your GroupWise system with several nodes in its failover path, it is an easy choice.
| WEBACCESS CLUSTERING WORKSHEET |
|---|
Under Item 5: MTA Installation Location and Item 7: WebAccess Agent Installation Location, mark whether you will install the WebAccess Agent and its MTA to sys:\system on each node in the cluster or to a vol:\system directory on the WebAccess Agent volume. Also specify where the MTA startup file will be stored. |
As with the MTA and the POA, you can choose whether to run the WebAccess Agent in protected memory. For a review of the benefits of protected memory, see Deciding Whether to Run the Agents in Protected Memory, which describes the issues in the context of planning MTA and POA installations.
You might think that protected memory would not be necessary if you have only one WebAccess Agent for your GroupWise system because it could never fail over to a node where another WebAccess Agent was running. However, because the WebAccess Agent in a cluster is installed into its own domain with its own MTA, this MTA could fail over to a node where another MTA was already running. Therefore, it is safest to load the WebAccess Agent and its MTA into protected memory. Load each agent into its own memory space and mark each memory space as restartable.
| WEBACCESS CLUSTERING WORKSHEET |
|---|
Under Item 8: Load WebAccess Agent and Its MTA in Protected Memory?, mark whether you need to run the WebAccess Agent and its MTA in protected memory. If you do, provide a protected memory address space name for each agent. |
Follow the instructions in Planning the NetWare Agent Installation, then return to this point. After you follow the instructions, you will have a filled-out NetWare® Agent Worksheet to use when you install the MTA.
IMPORTANT: Do not install the NetWare MTA until you are instructed to do so in Setting Up WebAccess in a Cluster.
Aside from the cluster-specific issues discussed in the preceding sections, the considerations involved in planning to install WebAccess are the same in a clustering environment as for any other environment. Review "Planning GroupWise WebAccess", then print and fill out the "GroupWise WebAccess Installation Worksheet" in "Installing GroupWise WebAccess" in the GroupWise 6.5 Installation Guide. When you set up WebAccess in a cluster, you will install the WebAccess Agent and the WebAccess Application in two separate steps:
IMPORTANT: Do not install the WebAccess software until you are instructed to do so in Setting Up WebAccess in a Cluster.
For the WebAccess Agent, fill out items 2 through 12 on the GroupWise WebAccess Installation Worksheet, taking into account the following cluster-specific issues:
| WEBACCESS INSTALLATION WORKSHEET |
|---|
Under Item 2: Installation Directory, take into account your decision recorded on the WebAccess Clustering Worksheet (Item 7: WebAccess Agent Installation Location). Under Item 3: Server Address, transfer the IP address and port number from the WebAccess Clustering Worksheet (Item 8: WebAccess Agent Network Information) filled out during Planning a Secondary IP Address and Cluster-Unique Port Numbers for the WebAccess Agent and Its MTA. Under Item 4: Enable Clustering Support?, mark Yes. This will cause the WebAccess Installation program to customize the WebAccess files for clustering. Under Item 5: Domain Directory Path, transfer the domain directory from the Domain Worksheet you filled out during Planning a New Domain for the WebAccess Agent. |
For the WebAccess Application, fill out items 13 through 19 on the GroupWise WebAccess Installation Worksheet, taking into account the following cluster-specific issues:
| WEBACCESS INSTALLATION WORKSHEET |
|---|
Under Item 13: Web Server Type and Root Directory, mark Netscape Enterprise Server for NetWare if you are using NetWare 6. No other Web server is currently supported for use with GroupWise and Novell® Cluster ServicesTM. The Web server root directory will be sys:\novonyx\suitespot. Under Item 16: Novell Root Directory, do not choose a location on a cluster-enabled volume if you are running the Netscape Enterprise Server in active/active mode; it must be a directory on the sys: volume of the server. If you are using active/passive mode, you can choose a location on a cluster-enabled volume. Just make sure that the Volume Resource load script mounts the volume before starting the Netscape Enterprise Server. |