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

23.1 ARCHITECTURE

Let's start by taking a high-level view of OVOW and comparing it to OVOU. The agent technology is functionally the same between the two products. They differ here when the OVOW agent takes advantage of the unique features of the Windows architecture. Some differences are easier to adjust to than others; for example, OVOW policies are similar conceptually to templates that are referred to in OVOU. Table 23-1 shows common platform-specific differences.

Table 23-1. OVOU and OVOW Platform Features

[*] The list is not inclusive

OVOW is a three-tier architecture consisting of the management server, console and the managed nodes. Out-of-the-box, the product includes the following components: a database, automatic discovery, message policies, performance, reporting and graphing tools. The Windows-specific polices that are provided with OVOW are listed here for reference; consult the OVO Windows documentation for the most current list of policies.

The OVOW agents and policies are designed to process and act upon data from the following event sources:

• Windows Event Logfiles (NT/Win2K)

• Perflib (NT/Win2K)

• WMI Store (NT/Win2K)

• System Logfiles

• External Messages (opcmsg command and API)

• SNMP Events

• Custom metrics made available by external programs or scripts

23.1.1 Management Server

The OVO administrator performs system management functions such as deploying agents and policies for all managed nodes via the server. Service management data and policy configurations are stored on the server along with the messages and event notifications.

The server platform uses

Microsoft Management Console (MMC),

Windows Management Instrumentation (WMI), and the

Distributed Component Object Model (DCOM) as core technologies. The OVOW application is a snap-in to the MMC and requires the MMC in order to run. Service management data, and policy configuration information is stored on the server.

23.1.1.1 Microsoft Management Console

The MMC handles the user interface for OVOW. It is the Windows 2000 common application GUI for administering the operating system. OVOW requires MMC to operate.

23.1.1.2 Web-Based Enterprise Management and WMI

WMI is the Microsoft implementation of

Web-Based Enterprise Management (WEBM) to develop a standard technology for accessing management information in an enterprise environment. WEBM is an industry standard initiative by the

Distributed Management Task Force (DMTF). For additional information, visit http://www.dmtf.org/standards/wbem/.

23.1.1.3 Component Object Model and DCOM

The

Component Object Model (COM) provides functions that enable diverse applications to interoperate. DCOM is a protocol that provides support for objects running on the server to communicate with remote systems over the network.

23.1.2 OVOW Management Console

The console provides a

graphical user interface (GUI) to perform routine management tasks, such asChapter 25, "OVOW Implementation Tasks," for additional information about discovery)

23.1.3 Managed Nodes

The agent runs on the managed node and sends exceptions (messages) to the management server based on the deployed policies. The node responds to requests from the server to execute or disable a policy. Performance data collected on the node is made available for viewing in the message browser as monitored thresholds or other graphical performance management or reporting tools. In the event that communications with the server are interrupted, the agent continues to operate, storing messages locally and performing automatic actions. When the server communication is re-established, the stored messages are forwarded to the server.