Caché Monitoring Guide - InterSystems Documentation

Generating a WMI Documentation Text File
Event
cacheDBWriteFail
cacheWDStop
cacheWDPanic
cacheLockTableFull
cacheProcessFail
cacheECPTroubleDSrv
cacheECPTroubleASrv
cacheAuditLost
cacheLoggedError
cacheLicenseExceed
cacheAppAlert
Description
Database write failure
Write daemon stalling
Write daemon entering panic mode
Lock table full (out of memory)
Caché process access violation
ECP data server connection in trouble mode
ECP application server connection in trouble mode
System unable to record audit events
Writing severe error to the console log
License request exceeds available or allowed licenses
Generating an application alert by calling the %Monitor.Alert.External method
There are additional events if you are using Ensemble. See Using WMI with Ensemble for details.
The iscprov.dll handles all communications between WMI and Caché and implements both the Caché WMI instance provider
and event provider. The Caché installation registers the file and puts it in the C:\Program Files\Common
Files\Intersystems\Cache directory.
The WMI service loads the provider DLL when requests are made and may unload it after it has been idle for a period of
time. When the DLL is loaded it initiates communication with Caché and starts a ^WMI server process in Caché. That
server process is then terminated when the DLL is unloaded. Depending on how often your script or management application
intends to collect information, you may want to change the default “lifetime” period for instance providers, which is only
thirty seconds. Using the WMI CIM Studio from the \root namespace, expand the class hierarchy for __SystemClass,
__CacheControl, and __ObjectProviderCacheControl. Change the value of the ClearAfter property to allow the Caché instance
provider to remain loaded for a longer period.
Caché writes important messages from the ^WMI server process in the cconsole.log file. It also logs any errors that occur
in the iscprov.dll (which implements the WMI Instance Provider and Event Provider for Caché) in the iscwmi.log file in the
\WINDOWS\system32\WBEM\Logs\ directory.
C.2.1 Using WMI with Ensemble
Ensemble also stores its WMI classes in the root\cache namespace in the WMI repository. Once you compile the Ensemble
WMI classes and they are in the WMI repository, you can manage them in the same manner as described in Using WMI
with Caché.
The Ensemble_LogEvent class is defined as a subclass of the __ExtrinsicEvent class. Ensemble sends a WMI
Ensemble_LogEvent instance whenever it posts an alert to the Ensemble Event Log.
C.3 Generating a WMI Documentation Text File
You can generate a text file of the classes and properties that InterSystems provides for WMI by using the doc entry point
of the Caché ^WMIMOF routine. For example:
Caché Monitoring Guide 121