EPS Help

The display of the Event Processor Subsystem (EPS) configuration file list is expanded or collapsed in the Configuration Manager table of contents (TOC) pane at the left side of the NonStop Cluster Management Suite (NCMS) window by double clicking on Event Processor Subsystem in the TOC.

Introduction

EPS monitors event messages as they are added to the system log, searches for specific patterns in the messages, and takes a designated action when a pattern match is found.

By default, EPS is configured to send a notification message to the system console for ServerNet system area network (SAN) path failure (X or Y cloud degraded) events and failure events produced by the process keepalive system. You can configure EPS to change these defaults and/or take actions on other event types.


Configuration

EPS is configured with the Eps, EpsFilters, EpsEvents, EpsTemplates, EpsSiteAdmin, and EpsDestinations X resource files.

As the root user, it is recommended that you edit copies of the EPS configuration files to create custom site- and user-specific X resources. Should future releases of EPS include configuration file changes, your custom X resources will be preserved.

The following topics are important to the EPS configuration process:

Configuration File Loading Sequence

This section explains how site- and user-specific resources can be kept separate from the default resources provided with EPS.

The default version of all X resource files used for EPS configuration is located in the /usr/lib/X11/app-defaults directory. However, these defaults may be overridden or augmented with the use of the following environment variables in the X resource loading sequence:

CAUTION: XFILESEARCHPATH, XUSERFILESEARCHPATH, and XAPPLRESDIR are common environment variables used for defining X resources. Changing these variables may affect other X applications.

The loading of X resource configuration files follows a modified version of the standard sequence:
  1. (Standard) Load initial default values.
    1. If $XFILESEARCHPATH is defined, look there for X resource file(s).
    2. Otherwise, load file(s) from /usr/lib/X11/$LANG/app-defaults.
    3. Otherwise, load file(s) from /usr/lib/X11/app-defaults.
  2. (Nonstandard) Load site-specific values.
    1. If $XLOCALFILESEARCHPATH is defined, look there for X resource file(s).
    2. Otherwise, load file(s) from /usr/local/lib/X11/$LANG/app-defaults.
    3. Otherwise, load file(s) from /usr/local/lib/X11/app-defaults.
  3. (Standard) Load user-specific values.
    1. If $XUSERFILESEARCHPATH is defined, look there for X resource file(s).
    2. Otherwise, load file(s) from $XAPPLRESDIR/$LANG.
    3. Otherwise, load file(s) from $XAPPLRESDIR.
    4. Otherwise, load file(s) from $HOME/$LANG.
    5. Otherwise, load file(s) from $HOME.

Creating Site- and/or User-Specific X Resources

To create site- and/or user-specific X resources with the Configuration Manager, perform the following steps:
  1. If you are not familiar with the contents of the EPS configuration files, read through the online help for each file to identify the X resources that you want to create or change.
  2. At the operating system (OS) prompt, copy the default EPS configuration files containing resources that you intend to create/change to the site- and/or user-specific directories identified under Configuration File Loading Sequence.
  3. In the Configuration Manager, select (double click on) Properties Files, then select (single click on) config_prefs.properties.
  4. In the config_prefs.properties file, edit the config.esp.dir entry so it contains the name of the site-/user-specific directory to which you copied the EPS configuration file(s) earlier in this procedure.
  5. Edit the config.eps.filelist entry so it contains the names of the files that you copied for editing.
  6. On the Configuration Manager File menu (at the top of the window), select Update.
Now when you select Event Processor Subsystem, your site-/user-specific EPS configuration files are listed.

Activating Configuration Changes

The X resource loading sequence can be triggered to read the configuration files in more than one way:

Configuration File Details

Take the following links for a description of each of the EPS configuration files: