Facility Administration and Message Logging

This chapter describes Y2K Compliance Assessment Tool facilities and explains how and where messages are logged. The tool's debugging messages are written to the individual services log files in the registry.

This chapter consists of the following sections:

Error Message Storage

Error messages are written to log files in C:\Program Files\CSCOpx\log. Each file assumes the name of the process that generates the error. Because messages are continuously appended to these files, you might want to occasionally remove the files. The files are re-created automatically.

Scheduling Scheme

The Y2K Compliance Assessment Tool has a self-contained scheduling mechanism that is configured automatically during installation.

Process Status

Any user can view the status of any process by selecting Admin > System Admin > Process Status. Only users with administrator privileges can start and stop processes. Table 5-1 shows possible back-end processes and their expected statuses.

Table 5-1: Back-End Process Status

Name	Description	State
CMLogger	Used by Java back-end processes and clients to get error messages from message catalogs.	Running but busy flag set
DIServer	Imports and adds devices to the inventory.	Running normally
EDS	A system service that distributes application and network events among Essentials components.	Running normally
EssentialsDbMonitor	A system service that monitors the accessibility of the database engine, which helps to ensure that the system is not started until the database engine is ready. All database-dependent back-end processes depend on this process.	Running normally
EssentialsOSG	Sybase's open server gateway that allows Java programs to connect to the Y2K Compliance Assessment Tool database.	Running normally
IcServer	Routinely collects inventory updates from managed devices. Inventory updates are acquired through SNMP queries on MIBs in the devices that maintain inventory information.	Running normally
RmeOrb	One of the system services that is the object request broker (ORB) part of CORBA.	Running normally
RmeOrbLocationService		Running normally
Web Server		Running normally

Table 5-2 describes the possible process states.

Table 5-2: Process Status Defined

State	Definition
Administrator has shut down this server	The administrator or another program has shut down the process.
Failed to run	The process has failed by exiting or sending a failed init message.
Never started	The process is not configured for autostart. The process must be started manually.
Program started - No mgt msgs received	The process has started but the status has not been reported to the process manager.
Running but busy flag set	The process has successfully started, but does not participate in process management messaging.
Running normally	The process has successfully started and is reporting status.
Transient terminated	The process has completed its function and has terminated normally.

Table of Contents