June 2007
Error reporting
Communication Control Toolkit uses the Windows Event Log subsystem to
record errors and other significant events. In addition to the standard event logs
(Security, System, and Application) Communication Control Toolkit creates and
maintains the following Communication Control Toolkit-specific error logs in
the Windows Event Log subsystem:
NCCT Security—Records failed Communication Control Toolkit client
logon attempts and events that may indicate attempts to breach security
(invalid message signatures, message sequence errors, and so on).
NCCT Audit Log—Records adds, moves, and changes of Communication
Control Toolkit users, terminals, addresses, and so on, and bulk imports.
NCCT Error Log—Records unexpected error conditions and program
exceptions, including full stack trace.
Note: The error logs mentioned above are used for new Communication Control
Toolkit components only. Legacy components continue to use the logging
mechanisms used in earlier releases.
SNMP
Communication Control Toolkit supports the generation of application-specific
traps to signal the occurrence of significant events occurring on the server.
Communication Control Toolkit generates Windows events. You can use a
Windows utility to generate traps from these events.
To use SNMP, you must enable and configure it on the server. For detailed
instructions, see the Installation and Maintenance Guide.
Note: For the IPML Service Provider, PeriSNMP provides an SNMP link to the
alarm log file. For more information, see the IPML Distributor Software
Installation Guide.
Performance monitoring
The Windows Performance Monitoring tool (PerfMon.exe) provides access to
system-wide and application-specific performance counters. System-wide
performance information includes information about memory utilization, CPU
usage, .NET CLR statistics, and so on.
Planning and Engineering Guide
Getting started
23