SAS 9.2 Enterprise Business Intelligence Server Monitoring with HP OpenView Operations for Windows 7.x
The SAS 9.2 Enterprise BI/HP OVOW monitoring package consists of a SAS Enterprise BI Server Smart Plug-In (SPI) downloaded from an active OVOW installation, sample SAS environment definition files, and these installation instructions, delivered in a ZIP archive. The custom SPI is installed on the OVOW manager machine. The supplied Policies and Instrumentation are deployed to managed nodes from there using the standard OVOW mechanisms. On each monitored SAS node, a systems administrator creates a SAS environment description file that defines which SAS Enterprise BI server types to monitor on the local node and the directories where those servers are located. The supplied OpenView instrumentation uses these definition files to derive paths to the SAS Enterprise BI servers’ log files and control scripts.
Differences between the SAS 9.1.3 and SAS 9.2 Smart Plug-Ins
With the release of SAS 9.2, there are significant differences in how SAS EBI servers are monitored.
There are changes in how log files are created, named, and rolled-over. Log names now typically include the SAS application context, the server name, the file creation date, and the SAS server’s process ID.
For SAS 9.1.3, there was a single, dated instance of a server’s log for the current day. Starting or restarting an EBI server would cause it to append to that current day’s log. For SAS 9.2 servers, the process ID will change with each new invocation of the SAS server, so there may be multiple instances of logs for a given date, each with a unique process ID.
In SAS 9.1.3, rolling logs automatically roll-over to a new file at approximately midnight local time, irrespective of server activity. In SAS 9.2, rolling logs automatically roll over to a new file after midnight, but only if there is new server activity. This means that there may not be an active log file for one or more days for a given SAS server instance.
The SPI for SAS92 uses special Policies and Instrumentation to facilitate monitoring for these new log behaviors:
For UNIX systems, a helper script associated with the SAS server’s OpenView Process Monitor maintains a UNIX hard link from a generic log name (e.g. – MetadataServer.log) to the current log file instance. The script also notes restarts of the SAS server instance by comparing the active server’s process ID to a copy of the process ID in use as of the last polling interval. If they differ, the script re-links the generic log to the current day’s log instance with the new process ID. The SAS server’s associated OpenView Logfile Entry policies simply track the generic log name.
For Windows systems, the sas92spi_logfile_path.bat helper script returns the name of the current day’s log instance, if it exists. If it doesn’t exist, it returns the name of an idle log file,