Novell GROUPWISE 7 - INTEROPERABILITY GUIDE, Manual

Page: 343 / 485

Implementing WebAccess in a Heartbeat Cluster
34
343
n
ov
do
cx (e
n)
11
Ju
ly 20
08
34
Implementing WebAccess in a
Heartbeat Cluster
You should already have set up at least a basic GroupWise
®
system, as described in Chapter 30,
“Planning GroupWise in a Heartbeat Cluster,” on page 285 , Chapter 31, “Setting Up a Heartbeat
Cluster,” on page 297 , and Chapter 32, “Setting Up a Domain and a Post Office in a Heartbeat
Cluster,” on page 307 . As part of this process, you filled out the “Heartbeat Clustering Worksheet”
on page 293 . If you do not have access to the filled-out worksheet, print the worksheet now and fill
in the clustering information as it currently exists on your system. You need this information as you
implement the WebAccess Agent in a cluster.
Š
Section 34.1, “Understanding the WebAccess Components,” on page 343
Š Section 34.2, “Planning the WebAccess Agent in a Heartbeat Cluster,” on page 343
Š
Section 34.3, “Setting Up the WebAccess Agent in a Heartbeat Cluster,” on page 346
Š Section 34.4, “Testing the WebAccess Agent in a Heartbeat Cluster,” on page 356
Š
Section 34.5, “Managing the WebAccess Agent in a Heartbeat Cluster,” on page 356
Š Section 34.6, “WebAccess Agent Clustering Worksheet,” on page 358
34.1 Understanding the WebAccess
Components
If you are not familiar with GroupWise WebAccess, review “ GroupWise WebAccess Overview ” in
“ Installing GroupWise WebAccess ” in the GroupWise 7 Installation Guide .
As you plan WebAccess in a clustering environment, you must keep in mind that you will plan and
set up two WebAccess components:
Š
WebAccess Agent ( gwinter ) that will be associated with a domain in your GroupWise system
Š WebAccess Application (a Java servlet ) that will be added to your Web server (Apache). The
WebAccess Application is currently not supported on a Heartbeat cluster.
You install the WebAccess Agent on each node in the cluster. You install the WebAccess
Application to your Web server, which must not be clustered. This means that the WebAccess client
login to the Web server at http://
secondary_IP_address /gw/webacc is available only when the Web
server is running.
34.2 Planning the WebAccess Agent in a
Heartbeat Cluster
In a cluster, you need to create a separate domain to house each GroupWise gateway, including the
WebAccess Agent.