After you have installed the Internet Agent in a cluster, you should consider some long-term management issues.
After installing the Internet Agent in your clustered GroupWise system, while the cluster-specific information is fresh in your mind, you should record that cluster-specific information as part of the GroupWise objects in ConsoleOne® so that you can easily refer to it later. Be sure to update the information recorded in the GroupWise objects if the configuration of your system changes.
To permanently record important cluster-specific information for the Internet Agent domain:
In ConsoleOne, browse to and right-click the Domain object, then click Properties.
In the Description field of the Internet Agent domain Identification page, provide a cluster-specific description of the Internet Agent domain, including its resource group IP address and the cluster-unique port numbers used by its MTA.
Click OK to save the Internet Agent domain description.
Select the Internet Agent Domain object to display its contents.
Right-click the MTA object, then click Properties.
In the Description field of the MTA Identification page, record the domain resource group IP address and the cluster-unique port numbers used by the MTA.
This information will appear on the MTA console, no matter which node in the cluster it is currently running on.
Click OK to save the MTA description.
Continue with Recording Cluster-Specific Information about the Internet Agent.
With the contents of the Internet Agent domain still displayed:
Right-click the GWIA object, then click Properties.
Click GroupWise, then click Identification.
In the Description field, record the resource group IP address and the cluster-unique port numbers used by the Internet Agent.
This information will appear on the Internet Agent console, no matter which node in the cluster it is currently running on.
Click OK to save the Internet Agent information.
Continue with Knowing What to Expect in an Internet Agent Failover Situation.
The failover behavior of the MTA for the Internet Agent domain will be the same as for an MTA in a regular domain. See Knowing What to Expect in MTA and POA Failover Situations.
Failover of the Internet Agent itself is more complex. The various e-mail clients (POP3, IMAP4, and LDAP) will receive an error message when the server they were connected to becomes unavailable. Most of the clients do not attempt to reconnect automatically, so the user must exit the e-mail client and restart it to reestablish the connection after the failover process is complete. Fortunately, the Internet Agent restarts quickly in its failover location so users will be able to reconnect quickly.
As with the MTA and the POA, manual migration of the Internet Agent takes longer than failover. In fact, the Internet Agent can seem especially slow to shut down properly, as it finishes its normal processing and stops its threads. For a busy Internet Agent, you might need to wait several minutes for it to shut down properly when you are manually migrating it.