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 Agent is faster and more stable when it runs on the same server with its domain. In a cluster, creating a separate domain for the WebAccess Agent ensures that the WebAccess Agent and its domain always fail over together.
Section 39.5, WebAccess Clustering Worksheet lists all the information you 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:
Before you install WebAccess, your Web server must already be set up and running in the cluster. Make sure that it can fail over and fail back successfully.
As you set up your Web server, record the following key configuration information on the WebAccess Clustering Worksheet:
|
WEBACCESS CLUSTERING WORKSHEET |
|---|
|
Under Item 7: Physical Web Servers, list the nodes in the cluster where you are installing the Web server software. Under Item 8: Web Server IP Address, record the secondary IP address of the Web server resource that you create. Under Item 9: Hardware Virtual Server Information, record the dedicated IP address for the Web site and the document root directory. |
Because the WebAccess Application is installed to a subdirectory of the Web server installation directory (directory\com\novell\webaccess), the WebAccess Application cannot be installed on a shared disk. Instead, you will install it to each node in the cluster where the Web 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 8 Administration Guide.
Keep in mind the following cluster-specific details:
When you specify the location for the domain directory on the Domain Worksheet, include the physical disk in your shared disk system where you want the domain directory to be located.
Do not concern yourself with the GroupWise agent information on the Domain Worksheet. You can stop with item 10. You will plan the MTA installation later.
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: Resource Group for WebAccess Agent, transfer the shared disk from the Domain Worksheet to the WebAccess Clustering Worksheet. Under Item 2: WebAccess Agent Domain Name, transfer the domain name and directory from the Domain Worksheet to the WebAccess Clustering Worksheet. |
The WebAccess resource group is similar to the domain and post office resource groups you have already set up, as described in Section 36.5, Planning GroupWise Resource Groups and Creating GroupWise Resource Groups. The WebAccess resource group contains a domain whose only role is to connect the WebAccess Agent into your clustered GroupWise system. It also contains two agent service resources, one for the MTA that services the domain and one for the WebAccess Agent.
|
WEBACCESS CLUSTERING WORKSHEET |
|---|
|
Under Item 1: Resource Group for WebAccess, specify the network name and other required information for the WebAccess resource group. |
To ensure successful short name resolution, add entries for the WebAccess network name to support your preferred methods of short name resolution, as described in Configuring Short Name Resolution.
As with the MTA and the POA, the WebAccess Agent needs cluster-unique port numbers. As part of planning to install the MTA and POA, you should already have determined the IP address and cluster-unique port numbers for the WebAccess Agent and its MTA as you filled out the Network 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 1: Resource Group for WebAccess, transfer the WebAccess resource group IP address. Under Item 4: MTA Network Information, transfer the cluster-unique MTA port numbers from the WebAccess section of the Network Address Worksheet to the WebAccess Clustering Worksheet. Under Item 6: WebAccess Agent Network Information, transfer the cluster-unique WebAccess Agent port number from the WebAccess section of the Network 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 each node in the cluster or to the shared disk of the WebAccess resource group. 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.
|
WEBACCESS CLUSTERING WORKSHEET |
|---|
|
Under Item 3: MTA Installation Location and Item 5: WebAccess Agent Installation Location, mark whether you will install the WebAccess Agent and its MTA to each node in the cluster or to the shared disk of the WebAccess resource group. Also specify where the MTA startup file will be stored. |
Follow the instructions in Planning the MTA Installation, then return to this point. After you follow the instructions, you will have a filled-out Windows Agent Worksheet to use when you install the MTA.
IMPORTANT:Do not install the Windows MTA until you are instructed to do so in Section 39.3, 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 Summary Sheets
in Installing GroupWise WebAccess
in the GroupWise 8 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 Section 39.3, 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 Server Information: Installation Directory, take into account your decision recorded on the WebAccess Clustering Worksheet (Item 5: WebAccess Agent Installation Location). Under Server Address, transfer the IP address and port number from the WebAccess Clustering Worksheet (Item 6: WebAccess Agent Network Information) filled out in Planning Cluster-Unique Port Numbers for the WebAccess Agent and Its MTA. Under Gateway Directory: Domain Directory Path, transfer the domain directory from the Domain Worksheet you filled out in 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 Web Server Information, mark the Web server you have installed in your cluster and specify the Web server root directory. Also, specify a directory on the Web server where you want to install the WebAccess Agent configuration file. the default is c:\novell. |