HP IAP Version 2.0 Administrator Guide (July 2008)

Events feature
s
Table 8 Events features
Feature
Description
Event
Information describing the event or e rror, including the service or
application name.
Machine
The name of the server on which the event is occurring.
IP
The IP address o
f the server on which the event is occurring.
Date
Thedateoftheevent.
Level
The status of the event. In Events, the only status shown is
critical.
Platform Performance
This area of th
e overview provides information from the Storage Status view (see
“Storage Sta
tus” on page 26) . The table on the left displays the number of objects (documents) stored,
the amount of
used and total disk space, the document storage rate, and the do cument index rate for
each domain. The bar graph displays the system’s storage space ratio. The line graph on the right shows
the messages per second that the system stored and updated in the past day, ending with the current
time, as well as the amount of folder updates.
Account Manager Service
The Account Manager Service provides a brief summary of information from the PCC Account Manager
(see “Account Manager (AM)” on page 47). This area displays the number of individual IAP users and
groups, pending users and groups, and the number of IAP repositories. It also displays the number of
synchronization errors, if any, pertaining to IAP user accounts. Synchronization errors ca n be corrected in
the Error Recovery view (see “Account Error Recovery” on page 58).
Partiall
y indexed and CatchAll
This area of the Overview displays the following information:
• Partial
ly indexed: The number of documents that were partially indexe d. (For example,
thesystemmightnothavebeenabletoindextheparticularfile t ype.) These documents
are in the failed indexing repository, which can be viewed in the Account Manager (see
“Account Manager (AM)” on page 47. Click the Repository radiobuttoninAM,clicktheOther
tab, then open the failed indexing repository.
• CatchA
ll: The number of messages in the system’s catchall repository, including messages too
large to be indexed, messages that cannot be parsed, and messages that cannot be routed to a
registered IAP user. The number includes messages that went into catchall from the SMTP portals
as well as those from the smart c ell indexers.
Messages that cannot be parsed have malformed message structures (MIME) or unsupported
char a
cter sets.
Messages that cannot be routed do not correspond to any system routing rule. They are not
recognized as destined for a registered IAP user. Mailing-list messages cannot be routed if the
recipient’s n am e is not included in the message as a destination.
The ca
tchall repository can be viewed in the Acc ount Ma n ager (see
“Account Manager (AM)”onpage47byclickingtheRepository radio button in
AM, clicking the Other tab, then opening the catch-all repository.
The failed indexing and catchall repositories a re automatically created when the system is started.
24
System Status