558 Chapter 14: Unity with Lotus Domino
allowed values are 1 (voice only), 3 (voice + fax), 5 (voice + e-mail), and 7 (voice + fax +
e-mail). If a subscriber enables or disables a particular notiﬁcation device (say, a pager) or
modiﬁes the settings of an enabled device, the values in the ﬁelds are updated automatically.
Planning a Unity for Domino Installation
Before installing Unity to utilize Domino mail ﬁles, you should consider several issues. Just
as when installing Unity for Exchange, the question of how Unity will impact the Domino
servers arises. Many areas potentially are affected by Unity’s presence, including storage
space on the servers, network bandwidth availability, CPU utilization, and increase in the
size of certain Domino databases (namely, names.nsf and admin4.nsf). As with Unity for
Exchange, there is one way to inspect these areas: trending.
To fully understand the impact of Unity on a Lotus Domino domain, “before” and “after”
snapshots are needed. All other things being equal, the difference between the two reason-
ably can be attributed to Unity. Of course, Unity has some impact on the Domino servers
within the domain because all voice-messaging trafﬁc is placed on to the data network.
Likewise, Unity can be affected by the deployment of Domino servers and its messaging
and directory infrastructure. Bottlenecks in the system, particularly in the messaging infra-
structure, will be revealed—often quickly.
Trending messaging servers gives a good picture of the before and after affects of Unity.
The “before” snapshot provides an operational baseline. Trending is not required but is pru-
dent, especially if there is a concern about the impact that Unity and uniﬁed messaging
will have on your existing messaging environment. Trending a Domino server is similar to
trending an Exchange server. For recommendations on gathering trending information, see
Chapter 13, “Unity with Microsoft Exchange.” The recommendations there are as applica-
ble to Unity for Domino as they are to Unity for Exchange; the tools are simply different.
The tools available for collecting trending information on a Lotus Domino server are listed
Domino can generate statistics on server and platform use and activity. Together, these
statistics provide information on the processes, networks, and use of the Domino system.
From the Domino Administrator, speciﬁc statistics can be selected for monitoring and can
be viewed in real time, if desired, or logged for later analysis; from the server console, you
can view a representation that uses your predeﬁned colors and text attributes to illustrate
the status of a process. The following system-monitoring tools are used to track and view
the Domino system and are conﬁgured through the Domino Administrator:
• The Monitoring Conﬁguration database (events4.nsf) stores the documents created
for monitoring. These documents deﬁne and conﬁgure the events to monitor and
deﬁne how the event is handled.