OVNM 5.3 - Operations Agent for NonStop Event Management Guide for UNIX

Configuring HP Operations Manager Services 44
5-3-2 Application Component(s)
This view represents the Application environment for a NonStop Server, for example, \EXTDEV, and is intended
to be used in conjunction with NonStop Server Processes and Middleware components.
The following Sections will provide more detail relating to the NonStop Service Map components and is intended
to provide NonStop Administrators with Service ID definitions for each OVNM supplied Service Map component.
Service ID’s are used to forward NonStop EMS event, or when defining where Object thresholds violations event
are to reported within the HP Operations Manager Service Map View. Configuring the Service IDs for both
NonStop EMS Events and Object violation event are accomplished using OVNM Object Configuration Client
(OCC).
5-4 Infrastructure Service Views and Service IDs
There are four Generic Service Map components within the NonStop Server Infrastructure View. The following
diagram shows the top level Service Map components.
Figure 5-4 HP Operations Manager Infrastructure Service Views
• Hardware
This Server Map component is intended to indicate some Hardware Event. Currently there are no OVNM
Default policies that report to the Hardware Component(s). It is the responsibility of NonStop Administrator
to assign which Hardware events are to be reported to the Hardware Component(s).
• Resources
The Resource component is intended to indicate that an Object monitoring violation has occurred. All
violations of Hardware Resources monitored by OVNM default Policies will be sent to one of Resource
Components.
• Networking
This component is used to indicate both network hardware and monitored network Object violations events.
All violation of Network Objects monitored by OVNM default Policies will be sent to one of the Network
Components.
• Security
The Security component is intended to indicate some security event. Currently there are no OVNM Default
policies that report to Security Component.
This pre-configured View allows the NonStop Administrator to easily assign selected EMS events, or monitored
Objects violations (Hardware or OS) to a Service View Component.
The following Service IDs are associated with the components:
NSSOSSSPI:HWR Service ID for NonStop Server OS SPI for Hardware
NSSOSSSPI:RES Service ID for NonStop Server OS SPI for Resources
NSSOSSSPI:NET Service ID for NonStop Server OS SPI for Network
NSSOSSSPI:SEC Service ID for NonStop Server OS SPI for Security