HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations نسخه متنی

15.2 COMPONENTS OF AN SPI

This section describes the components of an SPI, using the Oracle database SPI as an example. Some of the GUI components that are configured out-of-the box include metric alarms, logfile conditions, applications and tools, performance metrics and reports.

15.2.1 Component in the Message Group Bank

The message groups visually organize the types of messages that are currently in the active message browser. The SPI adds a new message group to identify the types of messages that are produced by the SPI components. The SPI components distributed to the managed node provide the agent with messages that are tailored for the application environment the SPI component is designed to monitor. The SPI for the Oracle database includes message groups, application groups, and node groups components for fault, performance and configuration of the database. These SPI messages are delivered to the message browser with context based on the database instance.

15.2.1.1 Database SPI Message Group-Administrator View

An example of the Database SPI message group is shown in Figure 15-1.

15.2.1.2 Database SPI Message Group-Operator View

The Operator view for Motif and Java includes the appropriate message groups as assigned by the administrator in the responsibility matrix of the user bank or user profile.

15.2.2 Component in the Node Group Bank

The node groups is an important area for defining the operator's responsibilities. SPI node groups are created during installation. The administrator uses one of the node groups for initial discovery of the environment on the managed node. During the discovery process the node is probed to collect data that is used to create some of the management components and files. The SPI node groups, along with other node groups (and the message groups), are used to assign operator responsibilities. The node groups represent the database servers and make is easier to deploy policies, add or remove database nodes.

Note

Not all SPIs have a discovery function.

15.2.2.1 Database SPI Node Groups-Administrator View

Figure 15-2 shows an example of the Database SPI node group(s) that are visible to the OV administrator.

15.2.2.2 Database SPI Node Groups-Operators View

The Operators view for Motif and Java includes the appropriate nodes as assigned by the administrator in the responsibility matrix of the user bank or user profile.

15.2.3 Components in the Application Bank

During installation of the SPI, a new Application Group is created. The Application Group for the SPI contains other application groups for managing the initial configuration of the node, managing the components of the SPI, and de-installing the components when necessary.

15.2.3.1 Database SPI Application Groups

Examples of the Database SPI Application Group Hierarchy within the Application Bank are shown in Figures 15-3, 15-4, 15-5, and 15-6.

15.2.4 Components in the Message Source Templates

Installing the SPI on the operating system runs the configuration upload command, opccfgupld to add the SPI components to the Message Source Templates environment on the server. The SPI template components are organized into template groups. This helps to simplify the management and distribution tasks. See Figure 15-7.

15.2.5 The Message Browser

The message browser is tailored for each operator, and appropriate messages from the SPIs will appear in the active browser or the history browser. Some SPI messages are integrated with actions (automatic or operator) and operator instruction text.

15.2.6 Directories and Files on the Management Server

The SPI files and configuration components are located in the appropriate vendor-specific directories until distribution.

15.2.7 Directories and Files on the Managed Node

After the components for the SPI are installed on the managed node, they are located in the appropriate directories along with other OpenView scripts and programs. The path to the files is vendor-platform specific and is shown in Chapter 14, "Agents, Policies, and Distribution." The SPIs are installed in different directories based on managed node platform.

As an example on the HPUX target node, the locations of the SPI binary components are

• /opt/OV/bin/OpC/action

• /opt/OV/bin/OpC/cmds

• /opt/OV/bin/OpC/monitors

The configuration files are located in the directory /var/opt/OV/<spi>/conf. The trace files are located in the directory /var/opt/OV/<spi>/conf. The log files are located in the directory /var/opt/OV/<spi>/log.

The temporary files used during run-time are located in the directory:/var/opt/OV/<spi>/tmp.