Monitoring OSS Object and Process Availability

The feature is for NONSTOP only

Open System Services (OSS) is an environment for HPE NonStop that provides a user interface and API similar to that of UNIX. It offers the benefits of the UNIX operating system with the features of HPE NonStop.

Availability Monitoring provides for monitoring of processes via object name or process name. However, in the OSS environment, this is only effective if an application accepts the runtime name option, which is rarely the case for POSIX applications, e.g. Tuxedo processes cannot accept the name option. Therefore, the OSS Availability function provides a facility to collect data and report on OSS Objects and OSS Processes.

Availability Monitoring makes use of the EMS Collector (STEMS) to monitor these OSS entities. The setup is made through the UPDOWN Configuration. Refer to UPDOWN Configuration Syntax for details.

HTTPD Objects

In order to monitor the HTTPD object, the following configuration syntax should be used:

SUBSYS UPDOWN

ADD OSSOBJECT (/usr/nonstop/webserver/bin/httpd, 2, HTTPD)

To add the OSS object to a group:

SUBSYS UPDOWN

ADD GROUP (Mywebapp, $DISK1, $DISK2, $DISK1.GUARDIAN.OBJECT, 2, HTTPD, 1)

OSS Configuration Rules

The following rules apply when adding OSS objects to the UPDOWN Configuration:

  • Duplicate <logical-object-name> entries will be rejected on Configuration start-up.

  • Multiple OBJECT definitions are not permitted within a single ADD OSSOBJECT entry.  Where this is required, each must be specified as a separate ADD OSSOBJECT entry.


Provide feedback on this article