SST Operations Bridge Concepts Guide

SST/OB Components and Architecture 10
2-3 SST/OB Components
2-3-1 HP SST NonStop Agent Components
The SST/OB installation on the HP NonStop Server installs the following components on the NonStop Server.
• AOBMGR
This is the main manager SST/OB process, running as a process pair to make the solution fault-tolerant.
This process monitors all the SST/OB components on the HP NonStop Server and starts them in case of
failures.
• Readers
The Reader processes on the HP NonStop Server are responsible for reading data from the TDF/ATD files
in the BASE24 environment. A single NonStop backend can have multiple reader processes, one for each
logical network configured within the environment. Each reader can be started in the desired CPU to
balance the load. The reader(s) pass the information to the status collector processes. The reader processes
are responsible for polling the ATD/TDF files to check for changes. The minimum polling interval is 15
seconds.
• EMON Process
The EMON is responsible for passing on the EMS events information from the collectors to the Event Logger
Service on the SST/OB Application Server on the Windows environment.
• Status Collector
The Status Collector process(s) is responsible for collecting information from the reader(s) and passing it on
to the DB Writer.
• DB Writer
DB Writer process is responsible for collecting information from the Status Collector(s) and writing it to the
temporary Host Database.
• Host DB
Host DB is a temporary database, which acts as a store and forward file to deal with network outage
problems. The data in Host database is written by DB Writer process. Multiple writer processes use file-
locking facility to synchronize data writing to this SAF (Store and Forward) database. The database size
can be configured as per customer requirement.
• Query Server
The Query Server is the SST/OB Feeder component, which feeds the collected data from the temporary
database to the Elink on the HP NonStop Server.
2-3-2 Communication Channel
SST/OB uses an independent communications process residing on both HP NonStop Server and the front-end
SST/OB Application Server as the communication channel between the SST/OB Application Server and the HP
NonStop host(s). Acting as a gateway for the NonStop environment, the channel host running on the NonStop
system passes structured information to the SST/OB Application Server through its service. It is the middleware
between the backend and front-end components of SST/OB. Its configuration is handled through the ELKCONF
file on the HP NonStop Server and a configuration file on the SST/OB Application Server.