-
HP OpenView VantagePoint Operations for UNIX Developer’s Toolkit Application Integration Guide Edition 5 Manufacturing Part Number: B7492-90003 Version A.07.00 January 2002 © Copyright 2002 Hewlett-Packard Company.
-
Legal Notices Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty.
-
Intel Corporation. Intel Itanium Logo: Intel, Intel Inside and Itanium are trademarks or registered trademarks of Intel Corporation in the U.S. and other countries and are used under license. Java is a U.S. trademark of Sun Microsystems, Inc. Microsoft is a U.S. registered trademark of Microsoft Corporation. MS-DOS is a U.S. registered trademark of Microsoft Corporation. Netscape and Netscape Navigator are U.S. trademarks of Netscape Communications Corporation. OpenView is a registered U.S.
-
-
Contents 1. An Introduction to Integrating Partner Applications with VPO Why Integrate with VPO? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP OpenView Partnerships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A Word about Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating Partner Solutions with VPO . . . . . . . . . . . . . . . . . . . . . . .
-
Contents Integrating Applications into the Application Bank. . . . . . . . . . . . . . . . . . . . . . . . . . Integrating via APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NNM Integration Through the VPO GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating via NNM Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 63 65 66 2.
-
Contents Types of VPO Monitor Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating Monitors into VPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sending Values Over the VPO Monitoring API or Command . . . . . . . . . . . . . . . MIB Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Advanced Options for a Message Source Template . . . . . . . . . . . . . . . . .
-
Contents NNM Applications in VPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Structure of NNM Applications in VPO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Integrating Additional NNM Applications into VPO . . . . . . . . . . . . . . . . . . . . . . 161 4. Using the VPO Application Programming Interfaces In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-
Contents Functions to Send Monitor Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functions of the Connection API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functions to Connect to the Management Server . . . . . . . . . . . . . . . . . . . . . . . . . Functions of the Application Configuration API. . . . . . . . . . . . . . . . . . . . . . . . . . . . Functions to Configure VPO Applications . . . . . . . . . . . . . . . . . . . . . . .
-
Contents 6. Integration Facilities of the HP OpenView NNM Core Platform In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OpenView Windows API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maps, Submaps, and Symbols . . . . . . . . . . . . . . . . . . . . . .
-
Contents Separator Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case Insensitive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pattern Matching Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Files for Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-
Contents 12
-
Printing History The manual printing date and part number indicate its current edition. The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. the manual part number will change when extensive changes are made. Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, you should subscribe to the appropriate product support service.
-
-
Conventions The following typographical conventions are used in this manual. Table 1 Typographical Conventions Font Meaning Example Book or manual titles, and man page names Refer to the VPO Administrator’s Reference Volume I and the opc(1M) manpage for more information. Emphasis You must follow these steps. Variable that you must supply when entering a command At the prompt, enter rlogin username. Parameters to a function The oper_name parameter returns an integer response.
-
Table 1 Typographical Conventions Font Meaning Example Computer Bold Text that you enter At the prompt, enter ls -l Keycap Keyboard keys Press Return. [Button] Buttons in the user interface Click [OK].
-
VPO Documentation Map HP OpenView VantagePoint Operations (VPO) provides a set of manuals and online help that help you use the product and understand the concepts underlying the product. This section describes what information is available and where you can find it. NOTE HP OpenView VantagePoint Operations (VPO) has been renamed to HP OpenView Operations (OVO) for UNIX. The name change has not yet been fully implemented across the VPO software and documentation.
-
VPO Manuals This section provides an overview of the VPO manuals and their contents. Table 2 VPO Manuals Manual Description Media VPO Installation Guide for the Management Server Designed for administrators who install VPO software on the management server and perform initial configuration. Hardcopy PDF This manual describes: • Software and hardware requirements • Software installation and de-installation instructions • Configuration defaults Provides you with an understanding of VPO on two levels.
-
Table 2 VPO Manuals Manual Description Media VPO Software Release Notes Describes new features and helps you: PDF only • Compare features of the current software with features of previous versions. • Determine system and software compatibility. • Solve known problems. VPO Supplementary Guide to MPE/iX Templates Describes the message source templates that are available for MPE/iX managed nodes. This guide is not available for VPO on Solaris.
-
Additional VPO-related Products This section provides an overview of the VPO-related manuals and their contents.
-
Table 3 Additional VPO-related Manuals Manual Description Media HP OpenView Event Correlation Designer for NNM and VPO If you purchase HP OpenView Event Correlation Designer for NNM and VPO, you receive the following additional documentation. HP OpenView ECS Configuring Circuits for Explains how to use the ECS Designer product in the NNM and VPO environments. Hardcopy PDF NNM and VPO VPO Online Information The following information is available online.
-
-
About VPO Online Help This preface describes online documentation for the HP OpenView VantagePoint Operations (VPO) Motif and Java-based operator graphical user interfaces (GUIs). Online Help for the Motif GUI Online information for HP OpenView VantagePoint Operations (VPO) Motif graphical user interface (GUI) consists of two separate volumes, one for operators and one for administrators. In the operator’s volume, you will find the HP OpenView VPO Quick Start describing the main operator windows.
-
❏ Help Instructions Instructions about the online help system itself for new users. ❏ Printing Facility Printing facility, which enables you to print any or all topics in the help system. (An HP LaserJet printer is required to print graphics.) To Access Online Help You can access the help system in any of the following ways: ❏ F1 Key Press F1 while the cursor is in any active text field or on any active button. ❏ Help Button Click [Help] in the bottom of any window.
-
Online Help for the Java-based GUI The online help for the HP OpenView Vantage Point Operations (VPO) Java-based graphical user interface (GUI) helps operators to become familiar with and use the VPO product. Types of Online Help The online help for the VPO Java-based GUI includes the following information: ❏ Tasks Step-by-step instructions. ❏ Concepts Introduction to the key concepts and features. ❏ References Detailed information about the product.
-
-
1 An Introduction to Integrating Partner Applications with VPO Chapter 1 27
-
An Introduction to Integrating Partner Applications with VPO Why Integrate with VPO? Why Integrate with VPO? A successful system management solution must satisfy a customer’s requirements for unified management across all platforms and all applications in a distributed environment. These requirements can seldom be satisfied by a single vendor, making partnerships essential to extend the functions and scope of a system management solution.
-
An Introduction to Integrating Partner Applications with VPO Why Integrate with VPO? In addition to the standard functionality of VPO, the Developer’s Toolkit provides a powerful C-library of Application Programming Interfaces (APIs), including: ❏ Operator APIs to operate on VPO messages, message events, and applications responses, for example to own or disown a message.
-
An Introduction to Integrating Partner Applications with VPO Why Integrate with VPO? These features make VPO ideally suited as an integration framework for other applications or solutions which address the system and network management market. Integration with VPO is especially attractive to partners who provide solutions in the following areas: ❏ Other system management functional areas, such as backup, spooling, job scheduling, security, or accounting.
-
An Introduction to Integrating Partner Applications with VPO Why Integrate with VPO? HP OpenView Partnerships The major benefit resulting from an integration with VPO is the increased customer value of the integrated solution. VPO is the industrial standard for problem management and supports a wide range of platforms which have either been developed internally, or by partners.
-
An Introduction to Integrating Partner Applications with VPO Integrating Partner Solutions with VPO Integrating Partner Solutions with VPO The ultimate goal of any integration must be to create an integration package that enables VPO and the partner solution to work so closely together that they are perceived by the customer as one powerful, integrated solution. Figure 1-1 shows an overview of the integration process.
-
An Introduction to Integrating Partner Applications with VPO Integrating Partner Solutions with VPO We use the term tight integration if the capabilities offered by VPO are fully exploited to maximize the uniformity of the integrated solution. For example, consider integrating a business solution with VPO.
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview VPO Conceptual Overview This section introduces the key concepts behind the operation of VPO, to help clarify more detailed discussions of the VPO integration capabilities in later chapters.
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview To achieve efficient operation and problem management, information must be gathered from the controlled elements and resources. VPO Agents are installed on managed nodes throughout the management domain which gather status information, messages, and monitoring values from a range of sources. SNMP agents, hosted on any system or IP device, are also fully supported by VPO.
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview The implementation of VPO can be scaled from the management of smaller workgroups, running business critical applications, to the management of world-wide distributed computing environments with thousands of systems. VPO also supports competitive management approaches, for example, follow-the sun.
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview Problem Management with VPO Regardless of the message source, VPO gathers the elements of daily operations and problem management by employing the following procedures: ❏ Collecting Gathering information about the status of the computing environment. ❏ Processing Selecting important or critical status information and making it available on the central system in a consolidated fashion.
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview Collecting Management Information VPO provides extensive collection services for management information. The agents gather management information originating from a variety of sources and when an exception is detected, they generate messages from the collected information.
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview Threshold Monitors The threshold monitoring capability of VPO is also a source of messages. It enables you to manage nodes more proactively by tracking the development of potential problems. When the predefined threshold for a monitored object is exceeded, a message is generated. VPO can collect monitoring information for basic system variables by accessing the SNMP Management Information Base (MIB).
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview Processing and Consolidating Information VPO offers extensive tools for the management of messages. Messages collected at the managed nodes are automatically forwarded to an appropriate management server. To minimize network traffic, and to avoid overloading the user with irrelevant messages, filter conditions can be specified.
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview Presenting the Information to the User The typical working environment for a VPO user consists of the following main windows in the Motif-based GUI: ❏ IP Map ❏ Managed Nodes ❏ Message Groups ❏ Message Browser ❏ Application Desktop The content of these windows depends on the tasks and responsibilities assigned to a particular user; users only see the objects and messages for which they are responsible and can access only tho
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview IP Map Window VPO includes the full network management features of HP OpenView Network Node Manager. These include network discovery and mapping, and the presentation of critical network events occurring in the managed computing environment. Figure 1-2 IP Map Window The IP Map window provides the operator with a topological view of the network. This can be either a view of the entire network or of a specific submap.
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview Managed Nodes Window The Managed Nodes window is the logical or system view of the managed environment for which the operator is responsible. Each node (or group of nodes) is represented by an icon. VPO changes the color of these icons to reflect the current status of the node according to the messages received into the Message Browser.
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview Message Groups Window The Message Groups window displays the message groups for which an operator is responsible. Messages are usually grouped by function, location, application, or other logical classification. Figure 1-4 Message Groups Window VPO changes the color of these icons to reflect the current status of the message group according to the active messages in the Message Browser.
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview Application Desktop Window The Application Desktop window displays icons for each management application that can be accessed by a particular operator. From this window, an operator can start daily problem management tasks. Some applications can be customized to provide either full or partial functionality.
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview Message Browser The Message Browser displays all messages received from the operator’s managed environment, including all nodes for which the operator is responsible, and which belong to message groups assigned to the operator.
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview Acting on the Information Provided VPO offers several mechanisms for responding to events. When an event occurs that requires a non-interactive, corrective action, you can configure VPO to run the configured action automatically. These actions can be activated either from the management server and/or directly by the agents.
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview Customizing VPO VPO provides a wide range of elaborate customization capabilities so that it can be easily adapted to manage diverse IT environments. It can be configured to collect messages and SNMP traps from any source, and to monitor any variable of interest. Once the management information is collected, all follow-on activities can be configured to suit your IT requirements.
-
An Introduction to Integrating Partner Applications with VPO VPO Conceptual Overview The VPO Java-based Operator User Interface In addition to the standard Motif-based operator GUI, VPO also provides a Java-based operator GUI. The Java-based GUI provides nearly the same functionality as the Motif-based GUI—see the VPO Software Release Notes for information about the differences between the two GUIs.
-
An Introduction to Integrating Partner Applications with VPO Integration Benefits to Partners Integration Benefits to Partners VPO is a leading framework for Integrated Network and System Management (INSM) so when integrating with VPO, a partner solution becomes a component of an INSM solution used to manage a complete IT environment. Integration into VPO increases the customer’s perceived value of a partner solution and makes it attractive to market segments that it might be unable to address on its own.
-
An Introduction to Integrating Partner Applications with VPO Integration Benefits to Partners Specific Benefits for Integrators in the NIM, NSM, and INSM Markets The following discussion is based on the popular classification of the IT management market into the following segments: ❏ Network Infrastructure Management (NIM) ❏ Networked System Management (NSM) ❏ Integrated Network and System Management (INSM) ❏ Service Management NIM Market Segment Management solutions providing problem management for this s
-
An Introduction to Integrating Partner Applications with VPO Integration Benefits to Partners NSM Market Segment Management solutions for this market segment deal with computer systems, databases and applications connected over a network. This includes solutions for print and storage management, for configuration management solutions, or for database and application management solutions. Solutions for the NSM segment integrate into VPO to prepare a management solution to become part of an INSM solution.
-
An Introduction to Integrating Partner Applications with VPO Integration Benefits to Partners Service Management Market Segment The following solutions should also consider VPO integration: ❏ Service providers Chapter 1 53
-
An Introduction to Integrating Partner Applications with VPO Integration Facilities Provided by VPO Integration Facilities Provided by VPO VPO is designed to provide the maximum flexibility for integrators, so the mechanisms underlying VPO functionality are configurable to a high degree. This enables you to customize VPO installations to the specific needs of your customers.
-
An Introduction to Integrating Partner Applications with VPO Integration Facilities Provided by VPO Threshold Monitoring The preceding sections described the integration of events of which VPO could read some type of text, for example, text written to a logfile or associated with an SNMP trap.
-
An Introduction to Integrating Partner Applications with VPO Integration Facilities Provided by VPO ❏ Performance metrics Use the embedded performance component to collect performance counter and instance data. The platform-generic metrics can be used to answer most questions about a system’s global configuration, CPU, disk, swap, and memory usage. The typical metrics vary by platform but are available on most platforms and are generally useful for drill down and diagnosis on a particular system.
-
An Introduction to Integrating Partner Applications with VPO Integration Facilities Provided by VPO Working with Message Templates You can use message templates to filter and suppress messages, reformat message text, and link actions and instructions with a message. You can define message templates using the Message Source Templates window that is accessible to both the VPO administrator and the VPO template administrator.
-
An Introduction to Integrating Partner Applications with VPO Integration Facilities Provided by VPO A condition consists of a match condition part that determines to which events detected in the message source the condition applies. Among other message attributes, the message text can be used in the match condition. You can specify patterns using regular expressions which the message text must match.
-
An Introduction to Integrating Partner Applications with VPO Integration Facilities Provided by VPO Adding Instructions, Annotations, and Actions to a Message Template The previous section described how you can use conditions to filter messages so that operators are not overwhelmed by a flood of messages of varying importance. A further function of VPO lets you completely rephrase the text of a message so that it can be easily understood by an operator.
-
An Introduction to Integrating Partner Applications with VPO Integration Facilities Provided by VPO VPO provides the following mechanisms to support problem resolution and self-attended operation: ❏ Message Instructions These help an operator to solve the problem at hand. They describe the available automatic and operator-initiated actions, give advice about manual steps for solving the problem, and provide any additional explanation that might be useful to an operator.
-
An Introduction to Integrating Partner Applications with VPO Integration Facilities Provided by VPO ❏ Operator-initiated Actions VPO provides a mechanism to offer predefined actions that must be started by an operator. This is useful if an action requires human interaction, or if an action must be tailored to the detected event, or if human judgement is required. As with automatic actions, on the successful completion of an action, the related message can be acknowledged automatically.
-
An Introduction to Integrating Partner Applications with VPO Integration Facilities Provided by VPO Integrating Applications into the Application Bank Any tools that can help operators and administrators in their assigned tasks should be integrated into the VPO Application Bank. This is the utility used to define the capabilities of operators. The VPO administrator can set up different Application Desktops for each VPO operator.
-
An Introduction to Integrating Partner Applications with VPO Integration Facilities Provided by VPO Integrating via APIs VPO provides a set of APIs which can be grouped according to their functions as follows: ❏ VPO Operator APIs This group of APIs enable certain actions to be immediately performed on VPO data. These APIs include: • VPO Data API • VPO Interface API This group of APIs enables external applications to register with VPO to receive information.
-
An Introduction to Integrating Partner Applications with VPO Integration Facilities Provided by VPO ❏ VPO Configuration APVPO This group of APIs enables applications to connect to the VPO database and configure VPO object directly in the database without using the GUI.
-
An Introduction to Integrating Partner Applications with VPO Integration Facilities Provided by VPO NNM Integration Through the VPO GUI VPO features a default integration with NNM, providing the operator with the ability to start ovw applications from the VPO GUI. This functionality is available in both the local case, where the NNM system is installed on the VPO management server, and in the remote case, where NNM is installed on a server other than the VPO management server.
-
An Introduction to Integrating Partner Applications with VPO Integration Facilities Provided by VPO Integrating via NNM Functionality The HP OpenView Network Node Manager (NNM) consists of two main parts: HP OpenView Windows (ovw) and the HP OpenView SNMP Event System. The HP OpenView Windows API supports the creation and manipulation of maps, submaps and symbols, and allows the generation of dialogs for user interaction. It is intended for the development of applications that need to use these features.
-
2 Integrating Solutions with VPO Chapter 2 67
-
Integrating Solutions with VPO Deciding Which Integration Capabilities to Use Deciding Which Integration Capabilities to Use The different integration capabilities provided by VPO are summarized in the previous chapter. This chapter discusses the advantages and disadvantages of different integration capabilities to help you to plan and design an integration package. It is important to decide whether the integration capabilities to be used are available on the management server or on the managed nodes.
-
Integrating Solutions with VPO Deciding Which Integration Capabilities to Use When integrating a partner solution it is recommended that you create a new template for that solution whenever possible. This prevents any possibility of the conditions defined for the new solution conflicting with previously defined conditions. In some circumstances, however, this may result in the generation of similar messages from different sources.
-
Integrating Solutions with VPO Deciding Which Integration Capabilities to Use Table 2-1 shows where the different message sources are handled, and lists any limitations: Table 2-1 Message Source Management Message Source Managed On Logfile Encapsulation Managed Nodes API or command line interface to managed nodes: passing a message by way of opcmsg(1|3) or opcagtmsg_send(3) Managed Nodes Threshold Monitoring Managed Nodes This applies to all types of threshold monitors, both for monitors for whic
-
Integrating Solutions with VPO Defining an Integration Strategy Defining an Integration Strategy This section describes how to select a suitable integration strategy for your solution, based on your integration starting point: ❏ Starting with an existing integration into VPO (aimed at the NSM market segment). ❏ Starting with an existing integration into HP OpenView Network Node Manager (NNM) (aimed at the NIM market segment). ❏ Starting from scratch No previous HP OpenView integration available.
-
Integrating Solutions with VPO Defining an Integration Strategy Adapting an Existing VPO Integration for VPO A.07.00 NOTE If you need to integrate into VPO a partner solution that was integrated into a previous (and recent) version of VPO, any integration points introduced with VPO version A.07.00 will not be used. In addition, you may have to recompile the application with the libraries from the latest version of the VPO software, if those libraries have been changed.
-
Integrating Solutions with VPO Defining an Integration Strategy Leveraging From an Integration into NNM If you currently use NNM, it is worth remembering that, as a VPO network operator, you can work in a way that is similar to the role of the typical NNM operator. VPO provides the preconfigured network operators netop and itop to whom the IPMap application, and the Network and SNMP message groups are assigned by default.
-
Integrating Solutions with VPO Defining an Integration Strategy SNMP Event Configuration SNMP traps are configured using the SNMP Trap Templates. An SNMP Trap Template is automatically generated by a conversion command that takes the NNM SNMP Event Configuration as input. By using the SNMP Trap Template, the following additional features are available for customers migrating from NNM: ❏ VPO provides automatic and operator-initiated actions which can be started on demand by authorized operators.
-
Integrating Solutions with VPO Defining an Integration Strategy Powerful GUI Application Integration In NNM, applications can be integrated into menus or the toolbar by way of Application Registration Files (ARFs). The same mechanism is also available in VPO. See “Integrating External Applications into the VPO GUI” on page 144 for more information.
-
Integrating Solutions with VPO Defining an Integration Strategy Monitoring Facilities The Data Collection and Threshold Monitoring facility of NNM can be used to monitor numeric MIB values. Alternatively, you can configure monitor templates for VPO managed nodes to use the VPO threshold monitoring facility.
-
Integrating Solutions with VPO Defining an Integration Strategy Alternative Message Sources SNMP traps are only one of several different message sources for VPO. Logfile templates can be used to generate messages on VPO managed nodes in which a powerful pattern-matching mechanism is applied locally to forward relevant messages to the management server. Network traffic is only necessary when a filtered message is transmitted by way of a reliable remote procedure call (RPC) connection.
-
Integrating Solutions with VPO Defining an Integration Strategy Starting from Scratch To integrate a partner solution that is not currently integrated into either NNM or VPO, first make sure that you have a complete understanding of the way in which operators use the GUIs, and the underlying concepts of the two OpenView products. Based on this knowledge, you can start to define the functional specification of the integrated solution.
-
Integrating Solutions with VPO Defining an Integration Strategy Obtaining Coexistence of NNM and VPO Integrations If you plan to integrate your product into both NNM and VPO, you can choose between the following two strategies: 1. Develop an integration package for NNM and transform this into an VPO integration package. The VPO integration package resulting from this approach is not improved. 2. Develop an integration package for NNM and develop a separate integration package for VPO.
-
Integrating Solutions with VPO Defining an Integration Strategy Figure 2-3 Comparison of Integration Strategies NNM Integration Migrate VPO Integration Maintain/Update NNM Integration Migrate NNM Integration Migrate Start Point Maintain/Update VPO Integration Maintain/Update Rethink/ Enhance Full VPO Integration Maintain/Update NNM Integration Maintain/Update Full VPO Integration Maintain/Update Strategy 1: Strategy 2: Develop an integration package for NNM and transform this into a V
-
Integrating Solutions with VPO Defining an Integration Strategy Strategy 1: Use Transformed NNM Integration in VPO This strategy has the following advantages: ❏ Requires little integration effort You don’t need all the advanced features of VPO, and you don’t need to identify new integration capabilities. ❏ The VPO integration will work in the same way as the NNM integration. This means an easy switchover for operators that used NNM and will continue with VPO.
-
Integrating Solutions with VPO Summary of the Integration Process Summary of the Integration Process The outcome of any integration is an integration package that contains VPO configuration information. Depending on the product you are integrating, you may need to modify the software of the partner solution or even implement additional processes, for example, when using the VPO APIs. In this case, the integration package would contain other items in addition to the VPO configuration information.
-
Integrating Solutions with VPO Summary of the Integration Process • Interfaces to trouble-ticket and notification systems • Tools for operators and administrators that are to be integrated into the VPO Application Desktop • Platforms that will be supported 3. If required, modify the partner solution software or implement additional processes. You can implement additional processes using programming languages or shell scripts, depending on whether you will use the VPO APIs or the command line interfaces.
-
Integrating Solutions with VPO The Role of Configuration Data in an Integration The Role of Configuration Data in an Integration Figure 1-1 on page 32 shows an overview of the integration process in which it distinguishes between defining an integration strategy and implementing an integration. The figure shows that the result of an integration process is an integration package which enables the partner solution and VPO to work together smoothly.
-
Integrating Solutions with VPO The Role of Configuration Data in an Integration To download configuration data from VPO you can either select Actions:Server->Download Configuration... from the menu of the administrator’s GUI or use the configuration download command opccfgdwn(1M) at the command line. Both methods download configuration information into a tree structure of flat files. You can later upload configuration information into the VPO internal database using the opccfgupld(1M) command.
-
Integrating Solutions with VPO The Role of Configuration Data in an Integration Figure 2-4 Handling VPO Configuration Information VPO Administrator’s GUI VPO Administrator’s GUI 6. 1. Integration Engineer 1. VPO Operator 6. VPO Management Server VPO Management Server 2. 5. 1. 3. Internal Database Configuration Flat Files Integration Project 4. 6.
-
3 Using the Integration Capabilities of the VPO Motif-based GUI Chapter 3 87
-
Using the Integration Capabilities of the VPO Motif-based GUI In This Chapter In This Chapter This section describes how to use features of the VPO administrator’s GUI to integrate applications into VPO.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Event Integration Through Messages This section describes in more detail the various methods provided by the VPO GUI that can be used to generate an integration package. Configuring Messages in the Message Source Templates Window Any problem that causes the partner solution to generate an error message, should also trigger a VPO message.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Figure 3-1 Accessing the Template Configuration Windows Add/Modify Logfile VPO Administrator’s GUI Choose: [Window: Message Source Templates] Add/Modify opcmsg Messages Template Administrators’ GUI Message Source Templates Add/Modify Threshold Monitors Add/Modify SNMP Traps Global Advanced Options for all conditions Global Message CorrelationOptions for all conditions Add/Modify MPE/iX Console Messages Add
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Figure 3-2 Message Source Templates Window The following sections describe the VPO message sources and the ways in which they can be used to integrate with VPO. For more detailed information about the message sources, refer to the VPO Administrator’s Guide to Online Information and the VPO Concepts Guide.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Defining Templates for Logfile Encapsulation If an application writes events into a logfile, the VPO logfile encapsulator can interpret these events and incorporate them in the VPO Message Browser.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Figure 3-3 Add/Modify Logfile Window For information about the fields in the Add/Modify Logfile window, see the VPO Administrator’s Guide to Online Information.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Using the Logfile Monitoring Options This section describes how to use the encapsulator options for different types of logfile. The options Close After Read and Message On No Logfile must be considered in each individual situation. The options File to be Read and Command to be Executed enable VPO to observe any type of file, including entire directories or binary files.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages ❏ Logfiles that decrease in size You may find that some logfiles may get smaller if they are completely overwritten by the writing process. It is not possible to recognize new information as the encapsulator stores only the file status, and not the status of its contents. To read this type of logfile, select the “Read from begin (Always)” option.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Defining Templates for SNMP Trap Interception If an application generates SNMP traps, VPO can intercept them and incorporate them into the Message Browser. Figure 3-4 shows the window for adding an SNMP trap template. Figure 3-4 Add/Modify SNMP Trap Window For information about the fields in the Add/Modify SNMP Trap window, see the VPO Administrator’s Guide to Online Information.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Defining Templates for MPE/iX Console Message Interception VPO can intercept all MPE/iX console messages, and it uses the default categorization and grouping defined in the templates provided with the VPO software. Figure 3-5 Add/Modify MPE/iX Console Messages Window For information about the fields in the Add/Modify MPE/iX window, see the VPO Administrator’s Guide to Online Information.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Defining Templates for Messages Sent to the VPO Message Interface opcmsg(1|3) This section describes how to create or modify a template that intercepts messages sent to the VPO message interface - the function opcmsg(1|3) of the Agent Message API. The partner solution can use the VPO message C library routine opcmsg(3) or command opcmsg(1) to route messages in the standard VPO format to any VPO agent.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Figure 3-6 Add/Modify VPO Interface Messages Window For information about the fields in the Add/Modify VPO Interface Messages window, see the VPO Administrator’s Guide to Online Information.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Defining Templates for Threshold Monitors This section describes the different types of monitors that are available, and how to define your own monitors using the VPO administrator’s GUI. Overview of VPO Monitoring Capabilities VPO enables the monitoring of numeric values that are determined either by: ❏ Program Calling a program at regular intervals that submits a numeric value to VPO.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages A second mechanism, specifically for polling MIB variables and referred to as MIB Data Collection, is also provided by VPO. In contrast to threshold monitors, this mechanism can be configured to store the collected data which can be used to analyze trends in monitored variables by plotting the values against time.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages • Even if the object for which a MIB variable is monitored is not running a VPO intelligent agent, the threshold monitor can still reduce the network load. In this case, it is recommended to use an intelligent agent running on a machine located close to the monitored object. Additional network load caused by MIB variable polling is, therefore, restricted to a small part of the network.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Using Threshold Monitoring to Generate Messages You can configure VPO to monitor managed nodes at regular time intervals, during which the monitored value is calculated and compared against a threshold value. If the threshold is exceeded, whether a message is generated depends on the type of monitor selected and on the “history” of values relative to the reset value.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages The monitor agent checks the received values against the configured thresholds and creates user-defined messages for any exceeded threshold values. This happens for the values of all types of objects (program, external or SNMP MIB) that arrive at the monitor agent.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Message Generation Policies and Message Filtering Threshold monitoring enables you to choose either a minimum or maximum threshold: ❏ Maximum threshold monitoring As long as the values received from the monitored object are less than the threshold value, no messages are generated. If the values reach or exceed the threshold value, then VPO generates the configured message for this object.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages ❏ Message generation continuously VPO generates a message each time the monitored value is either: • equal to or greater than the threshold for maximum threshold monitoring, or • equal to or less than the threshold for minimum threshold monitoring. The frequency of the message generation in this case depends on the configured polling interval.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Figure 3-8 Message Generation Policies For Maximum Thresholds A) Message on crossing threshold with Reset value Threshold Reset Message Generation B) Message on crossing threshold without Reset value Threshold Message Generation C) Message every time Threshold Message Generation B) can be seen as a special case of A), where Threshold is equal to Reset.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Types of VPO Monitor Available VPO supports the following types of threshold monitor: ❏ Monitoring With User-defined Programs or Scripts This method uses a program or script provided by the user that is invoked by the VPO Monitor Agent (opcmona). It collects the monitored value and transmits it to the VPO management server using the opcmon(1|3) C library API or command.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages In this instance, is the fully qualified hostname of the management server and is one of the following: C for English environments japanese for Japanese environments Figure 3-9, Setting Performance Thresholds, shows how to enter the syntax explained above in threshold monitor templates.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages ❏ SNMP MIB variables VPO can also monitor SNMP MIB variables. VPO queries SNMP MIB variables on the agents at defined intervals, and checks the output against the threshold values. If the result is above the maximum or below the minimum threshold value, VPO generates a message that is sent to the management server by way of the message agent. Monitor scripts or programs should be provided by the integrator.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Integrating Monitors into VPO A separate monitor is defined for each type of value to be monitored. You can specify message and suppress conditions for the monitor templates in the same way as for other message sources. To display a list of monitors, select the appropriate group in the Message Source Templates window. To open this window, choose Window: Message Source Templates from any of the toplevel windows.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages You can set conditions for a monitor template using the Condition No. window in the same way as for other message sources. For information about the fields in the Condition No. window for monitors, see the VPO Administrator’s Guide to Online Information. As in all condition definition windows, an [Instructions...
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Sending Values Over the VPO Monitoring API or Command VPO provides an API and a command opcmon(1|3) to allow applications to send monitoring values from the managed nodes to the VPO management server. This API/command should be used at the managed nodes for distributed, exception-based management.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Figure 3-11 Interaction Between the Monitor Agent and opcmon(1|3) Monitor Script (Provided by customer) Call script Evaluate current status of monitored object Call opcmon() Return Return Monitor Agent opcmon Check interval Check parameters; Check values received from opcmon Pass information to Monitor Agent No Is name/value pair received? Generate error message Yes Compare received value with th
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages MIB Data Collection Setting up MIB Data Collection is described in detail in the section “Collecting MIB Data” in the Managing Your Network with HP OpenView Network Node Manager manual.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Setting Advanced Options for a Message Source Template You can specify advanced options for all message sources in the Advanced Options window. This includes options for pattern-matching and whether messages are copied or diverted to the Server or Agent Message Stream Interface.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Output to Agent and Server Message Stream Interface (MSI) You can choose whether to output messages to a message stream interface so that they can be accessed by external applications, or to disable these features entirely. When disabled, messages matching the message conditions cannot be accessed by processes using the server or agent MSI.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Setting Message Correlation Options for a Message Source Template You can specify message correlation options for all message sources in the Message Correlation window. This includes the setting of message keys and message key relations, and options for the processing of duplicate messages.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Figure 3-13 Message Correlation Window For information about the fields in the Message Correlation window, see the VPO Administrator’s Guide to Online Information.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Suppression of Duplicate Messages You can set the Duplicate Message Suppression Mode so that VPO suppresses: ❏ All duplicate messages that match a particular condition. ❏ All duplicate messages whose input events are identical. ❏ All duplicate messages whose output messages are identical.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Figure 3-14 shows how duplicate messages are suppressed.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Setting Options for a Message Source Template Click on the [Options] button in the Message Source Templates window to specify options for Local Logging of messages, and for the treatment of unmatched messages. If a message or trap does not match either a message condition or a suppress condition, the message is flagged as unmatched.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Adding Instructions to a Message Source Template See “Adding Instructions, Annotations, Automatic- and Operator-initiated Actions” on page 136.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Setting Message and Suppress Conditions This section describes: ❏ Setting conditions for incoming messages ❏ Setting conditions for incoming SNMP traps Setting Conditions for Incoming Messages The Message and Suppress Conditions window enables you to specify which messages are to be intercepted from the source and forwarded to the management server, and which messages are to be discarded.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Figure 3-15 shows the Message and Suppress Conditions window. Message conditions are indicated by the plus (+) sign in the second column, suppress matched conditions by the minus (-) sign, and suppress unmatched conditions by the equals (=) sign. Figure 3-15 Message and Suppress Conditions Window When you choose to add or modify a condition, the Condition No. window shown in Figure 3-16 is displayed.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Figure 3-16 Condition No. Window for a Message Condition The Condition No. window for a suppress condition, contains only a Description field, and fields to specify the different parts of the Match Condition. For information about the fields in the Condition No. window, see the VPO Administrator’s Guide to Online Information.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Setting Custom Message Attributes for a Message Condition Custom message attributes allow you to add your own attributes to a message. This means that in addition to the default message attributes like severity, date, time, object, or application, you can extend VPO messages with attributes of your choice, for example, the attribute “Customer” or the attribute “SLA” for service level agreements.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages In the Custom Message Attributes window, the Name fields define the name of the attribute which is then displayed as an additional column in the browser windows. The Value fields display the value of the attribute.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Setting Conditions for Incoming SNMP Traps The window used to define an SNMP Trap condition, shown in Figure 3-18, differs slightly in the Match Condition fields from the one used to define a message condition. Note that when defining a suppress condition, only the Match Condition part of the window is displayed. Figure 3-18 SNMP Trap Condition No.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Using SNMP Trap Templates Converted from NNM SNMP Trap Configuration Files In comparison with the NNM SNMP trap configuration files, VPO trap templates provide additional features that can be exploited for the manipulation of SNMP traps. NNM events are configured by associating the enterprise ID, generic and specific SNMP trap number with an NNM event message, a severity and an event category.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Converting NNM SNMP Trap Configuration Files to VPO Trap Templates For NNM integrated solutions, a conversion tool is provided to convert SNMP trap configuration files into a VPO SNMP Trap Template. The conversion tool is part of the VPO product. In NNM, the SNMP Trap configuration is done using the application xnmtrap which maintains the configuration file trapd.conf.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Convert NNM SNMP Trap configuration files to VPO SNMP Trap templates, as follows: 1. Run the command: ovtrap2opc This creates a new application directory, including the converted trap template file, and uploads the template to the VPO database. 2. Assign the trap template to the management server. 3. Distribute new template to management server. 4. Restart operator sessions.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages Hints and Tips for Event Integration from Message Sources This section provides a summary of the recommended methods to integrate events from the various VPO message sources. ❏ Use the VPO templates to filter important messages from those that are less acute. Effective filtering ensures that the Message Browsers of responsible operators do not become cluttered by messages of low severity.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages ❏ Carefully consider whether to forward all unmatched messages to the VPO management server. The forwarding of unmatched messages has the following associated advantages and disadvantages: • The analysis of unmatched messages in the design phase can help to improve your definitions of message and suppress conditions so that these messages can be matched in the customer’s environment.
-
Using the Integration Capabilities of the VPO Motif-based GUI Event Integration Through Messages ❏ It is recommended to enable the output of messages to the agent and server message stream interface (MSI) in the Message Condition Advanced Options window for the following reasons: • The server MSI can always be globally disabled using the Configure Management Server window. By default, the server MSI is disabled.
-
Using the Integration Capabilities of the VPO Motif-based GUI Adding Instructions, Annotations, Automatic- and Operator-initiated Actions Adding Instructions, Annotations, Automaticand Operator-initiated Actions This section describes how to add message annotations and instructions to a message received by the VPO management server, and how to define automatic- and operator-initiated actions for a message.
-
Using the Integration Capabilities of the VPO Motif-based GUI Adding Instructions, Annotations, Automatic- and Operator-initiated Actions If you choose to specify an Instruction Text Interface (where an external program is called to provide the instruction text) you must already have defined this interface by selecting Actions: Utilities: Instruction Interfaces... from the Node Bank menu.
-
Using the Integration Capabilities of the VPO Motif-based GUI Adding Instructions, Annotations, Automatic- and Operator-initiated Actions When providing instruction text, it is useful to use a common, structured text format.
-
Using the Integration Capabilities of the VPO Motif-based GUI Adding Instructions, Annotations, Automatic- and Operator-initiated Actions Adding Actions and Annotations to a Message You can choose whether certain actions are performed when a message is received. These actions are either: ❏ Operator-initiated actions An operator-initiated action prompts the operator to start certain actions manually to solve the problem generating the message.
-
Using the Integration Capabilities of the VPO Motif-based GUI External Notification and Trouble-ticket Service External Notification and Trouble-ticket Service This section describes how to configure the VPO interfaces to external notification services and trouble ticket services. The VPO administrator can define notification services, for example, e-mail, pager, beeper, etc., and can setup a schedule as to when each service is to be used.
-
Using the Integration Capabilities of the VPO Motif-based GUI External Notification and Trouble-ticket Service Figure 3-22 Notification Schedule Window You can set up the notification services to be scheduled in the Notification Methods window. You can open this window by clicking on the [Modify] button in the Notification Schedule window. To set up a notification service, you need to supply a name for the service, and the pathname of the program or shell script that is called to perform the notification.
-
Using the Integration Capabilities of the VPO Motif-based GUI External Notification and Trouble-ticket Service Figure 3-23 Notification Methods Window Figure 3-24 shows the window used to define the schedule for a particular day. You can access this window by clicking on the relevant day button in the upper part of the Notification Schedule window. For each day of the week, you can specify which notification services to use at what time.
-
Using the Integration Capabilities of the VPO Motif-based GUI External Notification and Trouble-ticket Service Defining Trouble Ticket Services To define trouble ticket services, select Actions: Utilities->Trouble Ticket... from the Node Bank menu. This opens the Trouble Ticket window shown in Figure 3-25. Figure 3-25 Trouble Ticket Window You can use this window both to enable the use of a trouble ticket system, and to specify which program forwards the message to the trouble ticket system.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI Integrating External Applications into the VPO GUI This section describes various ways to integrate applications into the graphical user interface of VPO. You can use this section to compare the different methods and then choose the most suitable for your application.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI Figure 3-26 VPO Application Bank Almost any application can be integrated into the Application Desktop. Applications with an X-window user interface run in an X-window environment, others run in terminal windows. NOTE To display the NNM GUI through the VPO Java GUI, you must have an X Window System server running on the VPO Java GUI client system.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI Figure 3-27 VPO Multi-level Menus For each new menu item, there must be a corresponding action or sub-menu. You will need to use application registration files (ARFs) to associate programs with menu selections. Menus can be enabled or disabled depending on certain selection rules which specify the type and number of nodes that must be selected in a map window before a menu item becomes active.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI There are two main methods by which an application can be integrated into VPO: ❏ If the application is already integrated into the HP OpenView windows, then an application registration file (ARF) exists and the application is referred to as an “OpenView windows application”. These applications are integrated into VPO either as OV Applications or as OV Services.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI Table 3-1 Runs as user: Output method: Comparison of Application Integration Types VPO Application OpenView Application OpenView Service • Predefined at configuration. • UNIX user of operator who started the VPO GUI. • Can be overwritten by operator using “customized setup”. • Can be predefined at configuration. • Terminal • Terminal • Window displayed by VPO.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI Advantages Gained by Integrating VPO Applications It is recommended to incorporate an application as a VPO Application for the following reasons: ❏ The Application Desktop is the main place for applications that belong to the operators working environment and responsibilities.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI Integrating VPO Applications VPO applications are those that are integrated directly into VPO rather than by way of NNM. For these applications you can: ❏ Invoke them on the VPO management server and on all VPO managed nodes that are configured as VPO controlled nodes. ❏ Invoke them on several nodes in parallel.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI For all three types of VPO application, you must define a user name. In addition, for applications that use an input/output window, the user’s password is required. The user name, used to run the application, can be different for the same application for each of the operators. The following is a description of the user/password mechanisms used in VPO: ❏ VPO application with No Window option (e.g.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI You can avoid specifying a password if you define an .rhosts entry on the managed node with the specified user name. This method should only be used for terminal applications, and if no terminal emulator is available on the managed node.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI Integrating HP OpenView Windows Applications HP OpenView windows applications are applications already integrated into the HP OpenView platform. These applications are defined through OV application registration files (ARFs), and may then be integrated into VPO. Depending on the integration method, these applications are referred to as either OV Applications or OV Services.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI HP OpenView Applications HP OpenView applications integrated as OV Applications present the related application as an icon in the Application Desktop. Double-clicking on the icon starts that action as described in the ARF. Note that OV Applications do not present the related menu items in the VPO submaps, even if the corresponding ARF contains menu items.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI Integrating Applications into the Application Desktop This section describes how to define the following using the VPO GUIs: ❏ VPO application(s) ❏ OV application(s) ❏ OV service(s) For each OV Application or OV Service that you want to define, VPO needs the OV ARF in addition to the specifications done in the GUI.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI Adding VPO Applications Use the Add VPO Application window shown in Figure 3-28 to add an VPO application. To access this window, select Actions: Application->Add VPO Application... from the menu bar of the Application Bank window. Figure 3-28 Add VPO Application Window For information about the fields in the Add VPO Application window, see the VPO Administrator’s Guide to Online Information.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI Adding OpenView Applications You can add an OV application in the Add OV Application window shown in Figure 3-29. To access this window, select Actions: Application->Add OV Application... from the Application Bank window. Figure 3-29 Add OV Application Window For information about the fields in the Add OV Application window, see the VPO Administrator’s Guide to Online Information.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI Adding an OpenView Service You can add an OV service in the Add OV Service window shown in Figure 3-30. To access this window, select Actions: Application->Add OV Service... from the Application Bank window. Figure 3-30 Add OV Service Window For information about the fields in the Add OV Service window, see the VPO Administrator’s Guide to Online Information.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI Using NNM-integrated Applications With VPO This section describes how applications that are already integrated into NNM can be accessed by way of VPO, or can be integrated in different ways. Applications that are part of NNM are referred to as “NNM Applications” whereas applications that are manually added are referred to as “Additional Applications”.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI In addition to the standard user (opc_op), VPO provides a predefined network user (netop) and a predefined network administrator (itop): ❏ The netop environment allows the network user to perform all actions that a typical network (NNM) operator would have available, without the VPO configuration capabilities.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI Structure of NNM Applications in VPO In the Application Bank similar applications are grouped together into Application Groups. NNM applications are typically grouped into the following application groups: Net Activity, Net Config, SNMP Data, NNM Tools, OV Services, and X-OVw. Applications that use the symbol class SW_Utils are always started on the management server.
-
Using the Integration Capabilities of the VPO Motif-based GUI Integrating External Applications into the VPO GUI 162 Chapter 3
-
4 Using the VPO Application Programming Interfaces Chapter 4 163
-
Using the VPO Application Programming Interfaces In This Chapter In This Chapter This section describes the concept and facilities of the application programming interfaces (APIs) provided with the VPO Developer’s Toolkit.
-
Using the VPO Application Programming Interfaces Overview of the VPO APIs Overview of the VPO APIs VPO provides several APIs to VPO functions which enable a knowledgeable user to enhance the operations and problem management of VPO. This chapter provides an overview of all available APIs—they are described in more detail in the VPO Developer’s Reference.
-
Using the VPO Application Programming Interfaces Overview of the VPO APIs Figure 4-1 on page 167 gives an overview of the VPO User APIs, and the groups of functions included in each API. The VPO Developer’s Toolkit also provides interfaces to the HP OpenView NNM platform functions: OpenView Windows and the OpenView SNMP System. These integration facilities are described in Chapter 6, Integration Facilities of the HP OpenView NNM Core Platform,.
-
Using the VPO Application Programming Interfaces Overview of the VPO APIs Figure 4-1 Overview of the VPO User APIs VPO Operator API Data API Interface API Server Message API Agent Message API Agent Monitor API VPO Configuration API Connection API Application Configuration API Application Group Configuration API Message Group Configuration API Message Regroup Condition Configuration API Node Configuration API Node Hierarchy Configuration API Template Configuration API User Profile Configuration API User Con
-
Using the VPO Application Programming Interfaces Overview of the VPO APIs Figure 4-2 illustrates the information exchange between VPO and the APIs.
-
Using the VPO Application Programming Interfaces Overview of the VPO APIs Table 4-1 on page 169 gives an overview of the location of the VPO APIs.
-
Using the VPO Application Programming Interfaces Overview of the VPO APIs Table 4-1 Location of the VPO APIs API Location User Configuration API Management Server Distribution API Management Server Synchronization API Management Server 170 Chapter 4
-
Using the VPO Application Programming Interfaces The VPO Interfaces The VPO Interfaces The following interfaces to VPO can be accessed by way of the Interface API: Interface Description Server Message Stream Interface Enables VPO messages to be output from the server message stream to an external application. NOTE Agent Message Stream Interface Enables VPO messages to be output from the agent message stream to an external application.
-
Using the VPO Application Programming Interfaces The VPO Interfaces Figure 4-3 Messages Interaction of VPO Service APIs with the Server/Agent Message Flows Legacy Link Interface Action Requests Action Responses Server Message Stream Interface Messages Copy or Divert Application Response Interface Message Event Interface Messages VPO GUI Internal Message Stream VPO DB VPO Management Server Action Requests Action Responses Messages Managed Node Running VPO Agent Messages Agent Message Stream
-
Using the VPO Application Programming Interfaces The VPO Interfaces Overview of the Server Message-Stream Interface The VPO management server’s message-stream interface provides access to the internal message stream of the VPO management server. Processes may connect to the message-stream interface on VPO’s management server either in parallel or in series. Multiple connections to the MSI are organized by means of order numbers.
-
Using the VPO Application Programming Interfaces The VPO Interfaces The routines return an error/ok code, with errors being logged in the file: /var/opt/OV/log/OpC/mgmt_sv/opcerror Access to the Server Message-stream Interface If an application registers at the Message Stream Interface, VPO checks the setting of the Enable Message Stream Interface checkbox in the Server Configuration window. If the interface is enabled, the message manager passes the message down to the next check.
-
Using the VPO Application Programming Interfaces The VPO Interfaces VPO’s Serial MSI Configuration File The name of each MSI instance and the order number assigned to it are stored in the configuration file /etc/opt/OV/share/conf/OpC/mgmt_ sv/msiconf. Both parallel and serial connections from the MSI are possible at any point in the serial chain. The start number 0 (zero) is allocated by default to the event-correlation manager, opcecm.
-
Using the VPO Application Programming Interfaces The VPO Interfaces Modifying Message IDs Generally speaking, if an MSI instance modifies a message, a new message-ID is generated when the instance sends the message back to the MSI. However, there are exceptions: no new message-ID is generated if the message has either been diverted to the MSI (that is, no other copy of the message exists either inside or outside the MSI) or an MSI instance sends an unmodified message back to the MSI.
-
Using the VPO Application Programming Interfaces The VPO Interfaces Serial MSI Configuration: Example Scenario Figure 4-4 on page 177 illustrates how messages are distributed in a scenario where five processes are connected to the MSI: counter, opcecm, procA, procB and loadmon (load monitor). Incoming messages go first to counter, then in series to opcecm, then in parallel to both procA and procB. Finally the message is passed in series to the instance loadmon.
-
Using the VPO Application Programming Interfaces The VPO Interfaces Overview of the Agent Message Stream Interface The Agent Message Stream Interface allows you to tap the message flow of a VPO managed node to enable additional message processing by external applications before a message is sent to the management server. This can help to reduce the amount of network traffic considerably. A typical external application might be an event correlation engine, for example ECS.
-
Using the VPO Application Programming Interfaces The VPO Interfaces Figure 4-5 shows an overview of how to integrate a legacy system using the Legacy Link Interface. To do this, a legacy link process must be running on the management server; this process is shaded in gray in the figure. The legacy link process must manage the communication with the legacy systems, and also communicate with the management server processes using the functions of the Legacy Link Interface.
-
Using the VPO Application Programming Interfaces The VPO Interfaces Structure of the Legacy Link Process Figure 4-6 is a flowchart to illustrate the order in which the API functions are used when a legacy system is fully integrated. The legacy link process in this description is a process that runs on the management server.
-
Using the VPO Application Programming Interfaces The VPO Interfaces Figure 4-6 Using the Legacy Link Interface to Integrate a Legacy System START Call opcif_open() 3 times Open 3 interface instances to: (1) send messages, (2) receive action requests, (3) send action responses Establish communication with legacy system Wait for incoming data: - From Legacy System: messages or action responses - From VPO server: action requests Data From Legacy System? Yes Read data originating from legacy system No D
-
Using the VPO Application Programming Interfaces The VPO Interfaces Overview of the Message Event Interface The Message Event Interface enables an application running on the VPO management server to register for and receive Message Events. A message event is generated whenever the status of a VPO message changes in any way. For example, a message event can be generated if an annotation is added to a message, if the ownership of a message changes, etc.
-
Using the VPO Application Programming Interfaces The VPO Interfaces Access to Message Events If an application registers for message events of the OPCSVIF_MSG_ EVENTS interface, the read queue for this interface instance is created by VPO and accessed by the client, see Figure 4-8 on page 187. The display manager registers the instance and writes all desired message events to this queue. To use this interface, it is not necessary to enable it in the configuration of the management server.
-
Using the VPO Application Programming Interfaces The VPO Interfaces Overview of the Application Response Interface The Application Response Interface enables an external application to register for and receive Application Responses from VPO applications that have been started by the Application API opcappl_ start(). VPO generates an application response whenever the status of a running application changes.
-
Using the VPO Application Programming Interfaces The VPO Interfaces Read and Write Access to the VPO Message Stream Figure 4-7 on page 186 shows the difference between the three types of process that access the VPO message interface. Read-write applications are message processing programs that read messages and then modify attributes or create new messages depending on the input flow. Any resulting messages are then written back to the VPO message stream.
-
VPO Action Manager Managed Node action queue VPO Message Receiver action queue (Correlation engine; correlation interface) copy to (Correlation frontend) msg queue copy to / divert to output mode no READWRITE interface open no output (Agent as external message source) msg queue msg allowed for output yes OPCSVIF_ EXTMSGPROC_ READWRITE action request msg queue no OPCSVIF_ EXTMSGPROC_ READ msg Message Manager output on interface enabled OPCSVIF_ OPCSVIF_ OPCSVIF_ EXTAGT_ EXTAGT_ EXTAGT
-
Using the VPO Application Programming Interfaces The VPO Interfaces Figure 4-8 Communication With the Display Manager Apply for functionality (opcif_open()) arsp Action Manager ctrlq VPO Interface Application Display Manager update config Inst 1 GUI me Inst 2 Interface Instance 1 update config me me configured ? me Display Receiver me arsp init() arsp configured arsp meq meq Interface Instance 2 arspq ? Key: me = Message Event meq = Message Event Queue arsp = Application Response arspq =
-
Using the VPO Application Programming Interfaces The VPO Operator APIs The VPO Operator APIs This group of APIs enable actions to be directly performed on VPO data. These APIs include: API Description VPO Data API API to get/set information in VPO data structures.
-
Using the VPO Application Programming Interfaces The VPO Operator APIs The VPO Interfaces and the VPO Operator API — A Comparison Figure 4-9 shows the different methods by which the VPO Interfaces and the VPO Operator API access VPO data. The VPO Interfaces must open an interface to the information flow on the agent or server; register to receive or send information; be given permission to receive or send that information; and finally close the interface.
-
Using the VPO Application Programming Interfaces The VPO Configuration APIs The VPO Configuration APIs This group of APIs accesses VPO configuration data. These APIs include: API Description Connection API API to connect to and disconnect from the VPO database; it contains the functions opc_connect() and opc_ disconnect() Application Configuration API (New with VPO A.05.
-
Using the VPO Application Programming Interfaces The VPO Configuration APIs Template Configuration API (New with VPO A.05.00) API to configure message source templates and template groups; it contains the functions opctempl*() User Profile Configuration API (New with VPO A.05.00) API to configure VPO user profiles; it contains the functions opcprofile_ *() User Configuration API (New with VPO A.05.00) API to configure VPO users; it contains the functions opcuser_*() Distribution API (New with VPO A.05.
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Summary of VPO API Functions Functions of the VPO Data API Functions to Manipulate VPO Data Structures See the man page opcdata_api(3) for information about these functions and opcdata(3) for information about the VPO data-specific structures.
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Table 4-3 Overview of the Data Access and Creation Functions Function Call Description opcdata_get_long() Get long value of specified attribute opcdata_get_str() Gets string value of specified attribute opcdata_insert_element() Inserts a copy of the given element at given index opcdata_ladd() Adds an element to the specified list opcdata_ldel() Deletes an element from the specified list opcdata_lget_len() Returns th
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the VPO Iterator See the man page opciter(3) for more information about these functions. Table 4-4 Overview of the Iterator Functions Function Call Description opciter_begin() Sets the iterator to the first element and returns its pointer.
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions The VPO Data Structures Table 4-5 Overview of the VPO Data Structures VPO Data Type Description OPCDTYPE_ACTION_REQUEST Defines a VPO action request OPCDTYPE_ACTION_RESPONSE Contains the response of a previously started action OPCDTYPE_ANNOTATION Contains a message annotation OPCDTYPE_APPLIC Defines a VPO application OPCDTYPE_APPLIC_RESPONSE Contains the response of a previously started VPO application OPCDTYPE_APPL_
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Table 4-5 Overview of the VPO Data Structures VPO Data Type Description OPCDTYPE_NODE_CONFIG Contains a complete definition of a VPO managed node with all its attributes OPCDTYPE_NODE_GROUP Defines a VPO node group OPCDTYPE_NODEHIER Defines a VPO node hierarchy OPCDTYPE_REGROUP_COND Contains configuration information about a message regroup condition OPCDTYPE_TEMPLATE_INFO Contains the most necessary information to de
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the VPO Service APIs Functions to Access the VPO Interface Table 4-6 Overview of the VPO Service API Functions Function Call Description opcif_close() Terminate a connection to the interface opcif_get_pipe() Returns pipefd of its interface input queue opcif_open() Opens an instance of the Server/Agent MSI, Legacy Link Interface, Message Event Interface, or Application Response Interface opcif_read() Read i
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the Server Message API Functions to Manipulate Messages Table 4-8 Overview of the Server Message API Functions Function Call Description opcanno_add() Adds an annotation to an existing message opcanno_delete() Deletes an annotation from a message opcanno_get_list() Gets a list of all existing annotations for a message opcanno_modify() Modifies an existing message annotation opcmsg_ack() Acknowledges an a
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the Agent Message API Functions to Send/Acknowledge Messages Table 4-9 Overview of the Agent Message API Functions Function Call Description opcagtmsg_ack() Acknowledges the specified message opcagtmsg_send() Writes a message into the queue of the message interceptor opcmsg() Writes a message into the queue of the message interceptor Chapter 4 199
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the Agent Monitor API Functions to Send Monitor Values Table 4-10 Overview of the Agent Monitor API Functions Function Call Description opcagtmon_send() Writes a monitor value/name pair into the queue of the monitor agent opcmon() Writes a monitor value/name pair into the queue of the monitor agent 200 Chapter 4
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the Connection API Functions to Connect to the Management Server Table 4-11 Overview of the Connection API Functions Function Call Description opc_connect() Connect to the VPO database to get access. opc_disconnect() Disconnect from the VPO database.
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the Application Configuration API Functions to Configure VPO Applications Table 4-12 Overview of the Application API Function Function Call Description opcappl_add() Adds a VPO application opcappl_delete() Deletes a VPO application opcappl_get() Gets the full configuration of a VPO application opcappl_get_list() Gets a list of all configured applications opcappl_modify() Modifies a VPO application opcap
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the Application Group Configuration API Functions to Configure VPO Application Groups Table 4-13 Overview of the Application API Function Function Call Description opcapplgrp_add Adds an application group opcapplgrp_assign_ applgrps() Assigns application groups to a specified application group opcapplgrp_assign_appls() Assigns applications to a specified application group opcapplgrp_deassign_ applgrps() De
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the Message Group Configuration API Functions to Configure VPO Message Groups Table 4-14 Overview of the Message Group Configuration API Functions Function Call Description opcmsggrp_add() Adds a message group to the VPO database opcmsggrp_delete() Removes a message group from the VPO database opcmsggrp_get_list() Gets a list of all message groups opcmsggrp_modify() Modifies an existing message group 204
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the Message Regroup Condition Configuration API Function to Configure VPO Message Regroup Conditions Table 4-15 Overview of the Message Regroup Condition Configuration API Functions Function Call Description opcmsgregrp_add() Creates a new regroup condition opcmsgregrp_delete() Deletes a given regroup condition opcmsgregrp_get() Gets the attributes of a given regroup condition opcmsgregrp_get_list() Gets a
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the Node Configuration API Function to Configure VPO Managed Nodes Table 4-16 Overview of the Node Configuration API Function Function Call Description opcconf_get_nodes() Gets all configured nodes from the database opcnode_add() Adds a managed node to the database and the VPO node bank hierarchy opcnode_assign_templates() Assigns templates and template groups to a node opcnode_deassign_ templates() Deassi
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Function to Configure VPO Node Groups Table 4-17 Overview of the Node Configuration API Function Function Call Description opcnodegrp_add() Adds a node group to the database opcnodegrp_assign_nodes() Assigns nodes to a node group opcnodegrp_assign_ templates() Assigns templates or template groups to a node group opcnodegrp_deassign_nodes() Deassigns nodes from a node group opcnodegrp_deassign_ templates() Deassigns te
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the Node Hierarchy Configuration API Functions to Configure VPO Node Hierarchies Table 4-18 Overview of the Node Hierarchy Configuration API Functions Function Call Description opcnodehier_add() Adds a new node hierarchy opcnodehier_add_layoutgrp() Adds a new layout group opcnodehier_copy() Copies a node hierarchy opcnodehier_delete() Deletes a node hierarchy opcnodehier_delete_ layoutgrp() Deletes an em
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Table 4-18 Overview of the Node Hierarchy Configuration API Functions Function Call Description opcnodehier_move_ layoutgrps() Moves layout groups into another layout group opcnodehier_move_nodes() Moves a node from one location to another Chapter 4 209
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the Template Configuration API Function to Configure VPO Templates Table 4-19 Overview of the Template Configuration API Functions Function Call Description opctempl_delete() Deletes an existing template from the VPO database opctempl_get_list() Gets a list of all templates from the VPO database opctemplfile_add() Adds templates to the VPO database opctemplfile_get() Gets details of the template and writes
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions to Configure VPO Template Groups Table 4-20 Overview of the Template Configuration API Functions Function Call Description opctemplgrp_add() Adds a new template group to the database opctemplgrp_assign_ templates() Assigns templates to a template group opctemplgrp_deassign_ templates() Deassigns templates from a template group opctemplgrp_delete() Deletes a template group from the VPO database opctemplgrp_get
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the User Profile Configuration API Functions to Configure VPO User Profiles Table 4-21 Overview of the User Profile API Function Function Call Description opcprofile_add() Adds a user profile opcprofile_assign_ applgrps() Assigns application groups to a user profile opcprofile_assign_appls() Assigns applications to a user profile opcprofile_assign_ profiles() Assigns user profiles to a user profile opcpro
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the User Configuration API Functions to Configure VPO Users Table 4-22 Overview of the User API Function Function Call Description opcuser_add() Adds a VPO user opcuser_assign_applgrps() Assigns application groups to a VPO user opcuser_assign_appls() Assigns applications to a VPO user opcuser_assign_nodehier() Assigns a node hierarchy to a VPO user opcuser_assign_profiles() Assigns profiles to a VPO user
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the Distribution API Functions to Distribute Configuration to Managed Nodes Table 4-23 Overview of the Distribution API Function Function Call Description opc_distrib() Distributes the VPO agent configuration to managed nodes.
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions Functions of the Server Synchronization API Functions to Modify and Update Configuration Data Table 4-24 Overview of the Server Synchronization API Functions Function Call Description opc_inform_user() Informs all affected user interfaces opcsync_inform_server() Synchronizes the server processes after configuration changes opcsync_inform_user() Informs all affected users of any changes to data configuration opctransacti
-
Using the VPO Application Programming Interfaces Summary of VPO API Functions 216 Chapter 4
-
5 Integrating with VantagePoint Navigator 217
-
Integrating with VantagePoint Navigator In This Chapter In This Chapter HP OpenView VantagePoint Navigator is an add-on component of HP OpenView VantagePoint Operations. It enables you to manage your IT environment while focusing on the IT services you provide. See the VP Navigator Concepts and Configuration Guide for more information. When using the standard VantagePoint Navigator product, service configuration is done with the command line tool opcservice.
-
Integrating with VantagePoint Navigator In This Chapter ❏ C++ APIs of the service engine • The Query Interface for Service Status and Attributes • The Registration Interface for Service Status Changes These APIs are C++ interfaces and come complete with: • opcsvcapi.h header file • libopcsvcapi.sl shared library Use an ANSI C++ (aCC) compiler. See also the man page opcsvc_api(3) for more information.
-
Integrating with VantagePoint Navigator The VantagePoint Navigator Architecture The VantagePoint Navigator Architecture The following figure gives an overview over the general architecture of the service engine of VantagePoint Navigator.
-
Integrating with VantagePoint Navigator The VantagePoint Navigator Architecture The service engine has the following components: ❏ The service adapter manipulates the service data (configuration tasks). ❏ The message adapter gets messages and message change events from the VPO management server. ❏ The session adapter performs operational tasks. ❏ The status engine core calculates the status and maintains the data structures. ❏ The logging adapter is responsible for persistent service logging.
-
Integrating with VantagePoint Navigator The XML Data Interface The XML Data Interface The XML Data Interface uses filesystem sockets as communication mechanism. The request adapter of the service engine binds to the socket and listens for requests. Each request is handled by a request handler in parallel. If a new request comes in, it opens a filesystem socket over which it communicates with the new client. The client writes the request into the socket after a successful connection.
-
Integrating with VantagePoint Navigator The XML Data Interface You can test your XML commands interactively using the opcsvcterm program. This is an interface to the service engine that inputs XML into stdin and outputs XML to stdout. See also the man page opcsvcterm(1M). See the VPO Developer’s Reference for more information about the XML syntax.
-
Integrating with VantagePoint Navigator The C++ APIs The C++ APIs The VPO Developer’s Toolkit provides the following C++ interfaces for VantagePoint Navigator: ❏ Query interface for service status This interface allows you to request the status of a service as well as some basic attributes of the service. ❏ Registration interface for service status changes This interface allows you to register for service status changes.
-
Integrating with VantagePoint Navigator The C++ APIs The Registration Interface for Service Status Changes A client sends a registration request to the interface in the service engine which describes which events the client wishes to receive. The request is in XML format. The registration manager parses the XML registration structure and passes it to the core engine. The XML structure for the registration interface is defined in the operations.dtd (which also includes the service.dtd).
-
Integrating with VantagePoint Navigator The C++ APIs Figure 5-2 Registration Condition for Service Structure Service Register up to a specified level: Register for all services: For example: svc_1 svc_2 3 For example: 226 Chapter 5
-
6 Integration Facilities of the HP OpenView NNM Core Platform Chapter 6 227
-
Integration Facilities of the HP OpenView NNM Core Platform In This Chapter In This Chapter This chapter describes the integration facilities of HP OpenView Network Node Manager, the core platform of the VPO Developer’s Toolkit.
-
Integration Facilities of the HP OpenView NNM Core Platform Overview Overview When you are working on an application that is to be integrated into the Network Node Manager Platform, it is useful to consider the following different data domains: ❏ SNMP MIB data ❏ Topology data ❏ OpenView object database These domains are shown in Figure 6-1 and are described in the following sections.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API The OpenView Windows API This API enables a VPO partner to create and manipulate maps and submaps, and also to generate dialog for user interaction. It is intended for the development of applications that take advantage of these features.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API • Map and Submap Routines The OVw API contains many routines that are used to operate on maps and submaps. These routines let you create and modify submaps, as well as retrieve information about maps and submaps. A few OVw API routines let you change the background images of submaps.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API Maps, Submaps, and Symbols A map is a collection of OVW objects and their relationships. Users don’t view maps directly - they view windows called submaps that display a subset of map information. Users, not applications, create maps. Users can create several maps, and they can also view maps control which applications operate on the various maps.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API Figure 6-2 VPO Symbol Palette The HP OpenView programmer’s interface lets your application create symbols and submaps that show object hierarchies and connections (e.g., WAN connections). This is described in detail in the OVW Developer’s Guide. Symbol Type Registration ASCII Files can also be used to define symbol classes and subclasses in OpenView Windows.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API ClusterView: An Example of an Integrated Map Application The ClusterView application is integrated into OpenView Network Node Manager and allows to display and monitor MC/ServiceGuard clusters from the HP OpenView environment in a distributed commercial environment.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API The “MC/ServiceGuard Cluster” submap displays the nodes and packages configured in the cluster. In MC/ServiceGuard terminology, a package is a collection of network resources and high availability services managed together such that a single package can be moved between nodes within a cluster in order to make it highly available.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API HP OpenView Data: Objects and Fields The OpenView database is used by applications to store a wide range of information about network objects. An object is an internal representation of a logical or physical entity or resource that exists somewhere in a computer network. It consists of a unique object identifier and a set of fields that specify all the characteristics of the object.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API Fields are object attributes stored in the OVW database that can be seen as the building blocks from which objects are constructed.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API While the field type specifies the data type of the field, the field flags specify how the field is treated by OpenView Windows. OVW provides the flexibility to treat fields in different ways. There are five types of flags (behavior) that can be applied to fields. The examples given behind a field flag item are taken from the Field Registration File: ❏ List This field is a List of the specified type.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API ❏ Locate A locate operation may be done on the Locate field. This field will appear in the Locate: By Attribute dialog box.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API The OpenView SNMP API The OpenView SNMP API provides the following functions: ❏ SNMP Communications API and Related Commands A command interface and a programmer’s interface to SNMP communication functions. ❏ SNMP Configuration API An API for SNMP configuration purposes. ❏ Topology Data It stores information about the network topology in a topology database. Each component is described in a separate section.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API The remaining fields contain agent status, configuration, and metrics. The read-write fields may be written from your integrated application (SNMP “sets”), or from VPO applications. All fields can be read from your application (SNMP “gets”), from the SNMP MIB Browser, or plotted over time by the xnmgraph application. Data may also be included in trap messages sent by the agent.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API Table 6-3 SNMP Communications API Functions Category Function Name for Event-Driven X Applications Function Name for Traditional Applications Description Session Management OVsnmpXOpen OVsnmpOpen Establishes an active SNMP session. OVsnmpXClose OVsnmpClose Terminates an active SNMP session, and frees associated resources.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API Table 6-3 SNMP Communications API Functions Function Name for Traditional Applications Description Category Function Name for Event-Driven X Applications Message Setup and Manipulation OVsnmpCreatePdu Allocates an SNMP Protocol Data Unit (PDU) data structure. A PDU contains an SNMP message. OVsnmpAddNullVarBind, OVsnmpAddTypedVarBind Used in conjunction with SNMP Set, Get, GetNext and SNMPv2 Inform Requests.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API Table 6-3 SNMP Communications API Functions Category Function Name for Event-Driven X Applications Function Name for Traditional Applications Description Communications OVsnmpXSend OVsnmpSend Sends an SNMP message in non-blocking mode. Resources associated with the PDU are deallocated with this call, unless an error occurs.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API Related Commands The following commands related to SNMP communication are available: ❏ snmpwalk(1) - query a node repeatedly using SNMP GetNext requests ❏ snmpnext(1) - query a node using SNMP GetNext request ❏ snmpset(1) - issue an SNMP Set request ❏ snmpget(1) - query a node using SNMP Get request ❏ snmptrap(1) - issue an SNMP Trap For more details, see the corresponding man pages.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API SNMP Configuration API The SNMP Configuration API provides programmer access to the SNMP Configuration Database. This database is the repository on the management station for configuration information that controls the behavior of a SNMP Session.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API Table 6-4 SNMP Communications API Functions Category Function Name Description Database Access OVsnmpConfOpen Open the SNMP configuration database for subsequent access. OVsnmpConfClose Close the SNMP configuration database. OVsnmpConfDbName Obtain the pathname of the SNMP configuration database.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API Table 6-4 SNMP Communications API Functions Category Function Name Description Editing (cont.) OVsnmpConfParseEntry Allocate and initialize an OVsnmpConfEntry structure with the values extracted from a configuration string in the format of an ovsnmp.conf(4) configuration file entry. OVsnmpConfFreeEntry Deallocate all memory associated with the specified OVsnmpConfEntry structure.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API Table 6-4 SNMP Communications API Functions Category Function Name Description Administration OVsnmpConfReadCntl Read the current SNMP configuration database administration record. This record contains options which control run-time caching and use of the backward compatibility configuration file. OVsnmpConfStoreCntl Update the current SNMP configuration database administration record.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API The SNMP configuration can also be done interactive with the tool xnmsnmpconf.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API Topology Data VPO provides a topology manager that automatically discovers and maintains a database of TCP/IP nodes and connections. This database includes fields that describe each node’s functionality, address, and status. If a device has an SNMP agent, then that agent’s identification is used to determine its capabilities and how it should be represented on VPO maps.
-
Integration Facilities of the HP OpenView NNM Core Platform The OpenView Windows API 252 Chapter 6
-
7 Creating and Distributing an Integration Package Chapter 7 253
-
Creating and Distributing an Integration Package In This Chapter In This Chapter The final stage of the integration process is to create an integration package for distribution to customers. You will find that the configuration download/upload utility of VPO will play an important role in the creation of the integration package.
-
Creating and Distributing an Integration Package In This Chapter The VPO configuration upload command opccfgupld(1M) can be used at the customer’s site to upload the configuration information into the local VPO installation.
-
Creating and Distributing an Integration Package Structure of VPO Configuration Files Structure of VPO Configuration Files The behavior and capabilities of VPO are determined by configuration information stored in a relational database. This information can be downloaded into a tree structure of flat files. The structure of this file tree is shown in Figure 7-1.
-
Creating and Distributing an Integration Package Structure of VPO Configuration Files Figure 7-2 Structure of a VPO Configuration File Tree (cont.) download.dsf C Usually this is: /var/opt/OV/share/tmp/OpC_appl/\ REGROUP regroup.dat TEMPLATES CONSOLE console.dat EC ec.dat ECCIRCUITS INTERFACE interface.dat LOGFILE logfile.dat MONITOR monitor.dat SCHEDULE schedule.dat TEMPLGROUP templgroup.dat TRAP trap.
-
Creating and Distributing an Integration Package Downloading Configuration Information Downloading Configuration Information You can download configuration information either by using the VPO administrator’s GUI, or from the command line using the opccfgdwn(1M) command. Both methods enable you to select the parts of the configuration that you want to download. For example, instead of downloading the entire configuration, you may choose to download only the templates.
-
Creating and Distributing an Integration Package Downloading Configuration Information To download configuration data: 1. Open the Download Configuration Data window in the VPO administrator’s GUI. Select Actions: Server->Download Configuration 2. Select the parts of the VPO configuration that you want to download. Figure 7-3 shows the Download Configuration Data window.
-
Creating and Distributing an Integration Package Downloading Configuration Information 3. If you click on any of the buttons between [Applications…] and [Users and Profiles…] a second window opens that lets you choose the parts of the configuration to be downloaded more precisely. Figure 7-4 Select Templates to Download Window 4. Clicking on the button [Write Spec. File] lets you write a specification file that you can use for downloading the configuration data at a later point in time.
-
Creating and Distributing an Integration Package Downloading Configuration Information For example, assume that you want to download a configuration file tree into the directory: /var/opt/OV/share/tmp/OpC_appl/newConf The name of the specification file is download.dsf, and the download command expects that the directory contains a subdirectory C, for the English version of VPO, and that the specification file resides there.
-
Creating and Distributing an Integration Package Downloading Configuration Information Preparing to Download: Adding Executables If the integration package contains threshold monitors, automatic actions, or operator-initiated actions to be performed on the managed nodes, you must make sure that the VPO agents can find the required executables (programs or scripts). ❏ Check whether the program/script already exists on the managed node, for example, if it is part of the OS or part of a monitored application.
-
Creating and Distributing an Integration Package Downloading Configuration Information Prepare an executable for distribution by VPO as follows: 1. Place the executable into a source directory from which VPO will fetch it during the configuration downloading. On the VPO management server, use the directory: /var/opt/OV/share/databases/OpC/mgd_node/customer A 3-level directory hierarchy below this directory is predefined according to vendor, platform, and OS.
-
Creating and Distributing an Integration Package Downloading Configuration Information 5. Advise the VPO administrator, for example, in the documentation of the integration package, to distribute the new configuration information to the required managed nodes. In the Install/Update VPO Software and Configuration window, the administrator must distribute Actions, Monitors or Commands, depending on the requirements of the integration.
-
Creating and Distributing an Integration Package Uploading Configuration Information Uploading Configuration Information The opccfgupld(1M) command can only be issued by user root, and you must specify at least the name of the directory under which the configuration information is stored.
-
Creating and Distributing an Integration Package Uploading Configuration Information These examples assume that a file tree containing configuration information has already been created, using either the VPO administrator’s GUI or the opccfgdwn(1M) command. The configuration file tree is assumed to be in the directory: /var/opt/OV/share/tmp/OpC_appl/newConf Example 1: Uploading in Add Mode (Default) This is the most straightforward way to use opccfgupld(1M).
-
Creating and Distributing an Integration Package Uploading Configuration Information Example 2: Uploading in Replace Mode This example is similar to Example 1, except that Replace mode is used. You will see that, even though one of the templates already exists in the VPO database, it is overwritten by the upload command and no warning is issued.
-
Creating and Distributing an Integration Package Uploading Configuration Information Assume that the default template for VPO message interception contains the following conditions: condition 1 condition 2 condition 3 and that the partner solution needs the following additional conditions: new condition a new condition b If the configuration file tree contains a template for VPO message interception containing the two new conditions above, enter: /opt/OV/bin/OpC/opccfgupld -add -subentity \ /var/opt/OV/sha
-
Creating and Distributing an Integration Package Uploading Configuration Information You can obtain this sequence of conditions as follows: 1. Copy the VPO default template for message interception, containing the following conditions: condition 1 condition 2 condition 3 2. Remove all conditions except “condition 2”. 3. Add the new conditions needed to integrate the partner solution. You will now have the following sequence of conditions: condition 2 new condition a new condition b 4.
-
Creating and Distributing an Integration Package Uploading Configuration Information 270 Chapter 7
-
A Syntax Used in VPO Configuration Files Appendix A 271
-
Syntax Used in VPO Configuration Files In This Chapter In This Chapter This appendix provides a detailed description of the syntax used by the configuration download command opccfgdwn(1M) to store VPO configuration information in flat files which in turn are required by the configuration upload command opccfgupld(1M).
-
Syntax Used in VPO Configuration Files Notation Used Notation Used In this appendix, the syntax is described using a BNF grammar. Keywords are written in boldface, non-terminal symbols are written in italics. The symbol “ε” represents an empty string The symbol “|” separates alternatives of which one is to be selected. Square brackets “[” and “]” are used for grouping parts of a rule.
-
Syntax Used in VPO Configuration Files General VPO Syntax Rules General VPO Syntax Rules The following syntax rules apply to all VPO configuration files: # In the first column indicates a comment; all text until the new line is treated as comment. separators Blanks, tabs, new lines keywords Individual keywords are used, all in uppercase. strings All strings must be enclosed in quotes (“string”). Quotes within a string must be preceded by a backslash (\).
-
Syntax Used in VPO Configuration Files Configuration Files for Templates Configuration Files for Templates This section describes the syntax used in configuration files that describe templates for the following message sources: logfiles, SNMP traps, MPE/iX console messages, and messages passed to VPO by the message interface opcmsg(1|3). In the following grammar examples, you will find that the configuration file can have the keyword SYNTAX_VERSION followed by a number at the beginning.
-
Syntax Used in VPO Configuration Files Configuration Files for Templates Table A-1 Template Syntax Versions Syntax Version VPO Version Keyword Description 4 A.04.00 ECS Keywords for event correlation. CIRCUIT_FILE 3 A.03.00 SCHEDULE Keywords for scheduled actions. Major Keyword for new severity states. Minor MPI_AGT_DIVERT_ MSG Keywords for the agent message stream API.
-
Syntax Used in VPO Configuration Files Configuration Files for Templates Since the syntax descriptions for the configuration files of all these templates share most rules, they are presented here as one grammar.
-
Syntax Used in VPO Configuration Files Configuration Files for Templates logdefopts ::= [ | | ] | e logoption ::= LOGPATH | EXEFILE | READFILE | INTERVAL | CHSET | FROM_LAST_POS | ALWAYS_FROM_BEGIN | FIRST_FROM_BEGIN | NO_LOGFILE_MSG | CLOSE_AFTER_READ snmpdefopts ::= [ | ] | e condefopts ::= [ | ] | e opcdefopts ::=
-
Syntax Used in VPO Configuration Files Configuration Files for Templates SUPP_DUPL_COND | SUPP_DUPL_IDENT | SUPP_DUPL_IDENT_OUTPUT_MSG | SEPARATORS | ICASE | DISABLED conditions ::= [MSGCONDITIONS | SUPPRESSCONDITIONS SUPP_UNM_CONDITIONS ] | e msgconds ::= DESCRIPTION CONDITION SET | e suppressconds ::= DESCRIPTION
-
Syntax Used in VPO Configuration Files Configuration Files for Templates SERVICE_NAME | MSG_KEY | MSGKEY | MSG_REL_BLANK ACK | MSGKEYRELATION ACK | SERVERLOGONLY | AUTOACTION | OPACTION | TROUBLETICKET [ACK | e] | NOTIFICATION | MPI_SV_COPY_MSG | MPI_SV_DIVERT_MSG | MPI_SV_NO_OUTPUT | MPI_AGT_COPY_MSG | MPI_AGT_DIVERT_MSG | MPI_AGT_NO_OUTPUT | MPI_IMMEDIATE_LOCAL_ACTIONS | HELPTEXT | HELP | INSTRUCTION_TEXT_INTERFACE
-
Syntax Used in VPO Configuration Files Configuration Files for Templates EUCKR | EUCTW | GB2312 | BIG5 | CCDC | UTF8 | UCS2 severities ::= | e severity ::= [ Unknown | Normal | Warning | Minor | Major| Critical ] nodelist ::= | node :: = IP [ | e] | DEC | SNA | NOVELL | OTHER ipaddress::= ...
-
Syntax Used in VPO Configuration Files Template Examples Template Examples Example of a VPO Logfile Template The following example is a configuration file for a logfile template: LOGFILE “Su (10.x/11.x HP-UX)” DESCRIPTION “HP-UX 10.x/11.
-
Syntax Used in VPO Configuration Files Template Examples Example of a VPO Message Source Specification The following example is a configuration file for the VPO message interface used to intercept messages sent by opcmsg().
-
Syntax Used in VPO Configuration Files Template Examples Example of an SNMP Trap Template File SNMP “SNMP 6.0 Traps” DESCRIPTION “Message Conditions for SNMP Trap Interception” SEVERITY Normal APPLICATION “SNMPTraps” MSGGRP “SNMP” FORWARDUNMATCHED MSGCONDITIONS # from EVENT RMON_Rise_Alarm .1.3.6.1.2.1.16.0.1 “Threshold Alarms” Warning DESCRIPTION “RMON_Rise_Alarm” CONDITION $e “.1.3.6.1.2.1.
-
Syntax Used in VPO Configuration Files Template Examples threshold <$5>; value = <$4>. (Sample type = <$3>; alarm index = <$1>)” HELPTEXT “This event is sent when an RMON device falls below a preconfigured threshold.
-
Syntax Used in VPO Configuration Files Configuration Files for Monitors Configuration Files for Monitors The following describes the syntax that is used in configuration files for threshold monitors. These files must fit the syntax rules related to . It is recommended to put the keyword SYNTAX_VERSION followed by the number of the current version at the beginning of a configuration file.
-
Syntax Used in VPO Configuration Files Configuration Files for Monitors MPI_AGT_WPY_MSG | MPI_AGT_DIVERT_MSG | MPI_AGT_NO_OUTPUT | MPI_IMMEDIATE_LOCAL_ACTIONS | SUPP_DUPL_COND | SUPP_DUPL_IDENT | SEPARATORS | ICASE | DISABLED supp_dupl ::= | RESEND | COUNTER_THRESHOLD | COUNTER_THRESHOLD RESET_COUNTER_INTERVAL | RESEND COUNTER_THRESHOLD | RESEND COUNTER_THRESHOLD
-
Syntax Used in VPO Configuration Files Configuration Files for Monitors monconds ::= | e moncond ::= THRESHOLD [ | ] | RESET [ | ] OBJECT duration ::= FOR | e pattern ::= [ SEPARATORS | e ] [ ICASE | e ] action ::= [ ACTIONNODE | e ] [ ANNOTATE | e ] [ ACK | e ] [SEND_MSG_AFTER_LOC_AA ] | e condition_id ::= CONDITION_ID | e severity ::= [ Unknown | Normal | Warning
-
Syntax Used in VPO Configuration Files Configuration Files for Monitors Example of a VPO Monitor Template The following text shows the definition of a monitor for which the VPO intelligent agent calls a program every 10 minutes to determine disk usage.
-
Syntax Used in VPO Configuration Files Syntax for Message Pattern Matching Syntax for Message Pattern Matching Table A-2 shows the components of the VPO pattern-matching language that can be used to write expressions to match incoming messages. You can combine individual components to form complex patterns. Table A-2 VPO Pattern Matching Language Component Description Ordinary Characters Ordinary characters are expressions that represent themselves.
-
Syntax Used in VPO Configuration Files Syntax for Message Pattern Matching Table A-2 VPO Pattern Matching Language Component Description Bracket Expressions: The brackets “ [ ” and “ ] ” are used as delimiters to group expressions. To increase performance, avoid brackets wherever they are superfluous. In the pattern ab[cd[ef]gh] all brackets are unnecessary - abcdefgh is equivalent. Expressions with brackets are used frequently with the Alternative Operator or the NOT Operator.
-
Syntax Used in VPO Configuration Files Syntax for Message Pattern Matching Table A-2 VPO Pattern Matching Language Component Description Variables The matched string can be assigned to a variable that you can use to recompose messages or as a parameter for action calls. To define a parameter, add the string: .parametername before the closing bracket. For example, the pattern: ˆerrno: <#.number> - <*.
-
Syntax Used in VPO Configuration Files Syntax for Message Pattern Matching Table A-2 VPO Pattern Matching Language Component Description Assign-toVariable Operator In addition to being able to use a single expression, such as <*> or <#> to assign a string to a variable, it is also possible to use the assign-to-variable operator to build up a complex sub-pattern composed of a number of operators. The assign-to-variable operator uses the same square brackets as in other bracket expressions.
-
Syntax Used in VPO Configuration Files Syntax for Message Pattern Matching Table A-2 VPO Pattern Matching Language Component Description NOT Operator The not operator ( ! ) must be used with delimiting square brackets, for example: The pattern above matches all text that does not contain the string WARNING. The NOT operator may also be used with complex sub-patterns, for example: SU <*> + <@.tty> -<*.
-
Syntax Used in VPO Configuration Files Syntax for Message Pattern Matching Table A-2 VPO Pattern Matching Language Component Description Numeric Range Operators The pattern for constructing complex expressions with these operators, is: The square brackets are part of the syntax and must be provided as literals in the pattern. The sub-pattern can be a simple numeric operator, for instance <#> or <2#>.
-
Syntax Used in VPO Configuration Files Pattern Matching Pattern Matching It is important to understand how VPO pattern matching works, especially in conjunction with assignment to parameters. When matching the pattern: <*.var1><*.var2> with the string abcdef, it is not immediately clear which substring of the input string will be assigned to each variable.
-
Syntax Used in VPO Configuration Files Pattern Matching Patterns without expression anchoring can match any substring within the input line. Therefore, patterns such as: this is number<#.num> are treated in the same way as: <*>this is number<#.num><*> Separator Characters The separator characters used in <_> and <@> can be specified for each pattern. The user enters the separators in the pattern definition mask; default characters are the blank and tab characters.
-
Syntax Used in VPO Configuration Files Pattern Matching Pattern Matching Examples Table A-3 Pattern Matching Examples Format Recognized Messages Error Will recognize any message containing the keyword “Error” at any place in the message. panic Matches all messages containing “panic”, “Panic”, “PANIC”, etc., at any place, if case insensitive mode is used. logon|logoff Recognizes any message containing the keyword “logon” or “logoff ”. ˆgetty: <*.msg> errno<*><#.
-
Syntax Used in VPO Configuration Files Configuration Files for Applications Configuration Files for Applications This section describes the syntax used in configuration files for applications.
-
Syntax Used in VPO Configuration Files Configuration Files for Applications } APPLICATION_TYPE application_node_list ::= [ | PATTERN_OTHER ] | e node_ident ::= _OPC_MGMTSV_ | IP | IP | SNA | DEC | NOVELL | OTHER application_login_list ::= [PLTFRM_FAMILY_NAME USER_NAME PASSWORD ] application_type_
-
Syntax Used in VPO Configuration Files Configuration Files for Applications Example of a VPO Application Configuration File The following is an example of an Application Configuration File for an VPO application. This file is part of the VPO default configuration.
-
Syntax Used in VPO Configuration Files Syntax and Length of VPO Object Names Syntax and Length of VPO Object Names Syntax checks are automatically performed when entering information in the corresponding fields of the GUI. For more information about length limitations of VPO object names, see the VPO Reporting and Database Schema.
-
B Notification Services and Trouble Ticket Systems Appendix B 303
-
Notification Services and Trouble Ticket Systems In This Chapter In This Chapter VPO uses the following parameters both when calling a notification service and when forwarding a message to a trouble ticket system: 304 Appendix B
-
Notification Services and Trouble Ticket Systems Parameters for Notification and Trouble Ticket Services Parameters for Notification and Trouble Ticket Services VPO uses the following parameters both to call a notification service and to forward a message to a trouble ticket system: Table B-1 Parameters for Notification Services and Trouble Ticket Systems Parameter Number Description 1 Unique message number 2 Node name 3 Node type: • HP 9000/700, HP Series 9000/800, HP Series 3000/900 • Sun SPARCst
-
Notification Services and Trouble Ticket Systems Parameters for Notification and Trouble Ticket Services Table B-1 Parameters for Notification Services and Trouble Ticket Systems Parameter Number Description 10 Name of object 11 Message severity: normal, warning, critical 12 List of responsible VPO operators 13 Message text 14 Instruction text (if available) 15 Custom message attribute(s) (if available) 16 Number of suppressed duplicate messages Note that: ❏ Date and time are mentioned in t
-
Notification Services and Trouble Ticket Systems Example of a Trouble Ticket Parameter List Example of a Trouble Ticket Parameter List Table B-2 Example of a Trouble Ticket Parameter List Parameter Passed Value 1 617dfe6374f1.02.0f.88.78.43.00.00.00 2 hpbbxyz3.bbn.hp.
-
Notification Services and Trouble Ticket Systems Example of a Trouble Ticket Parameter List 308 Appendix B
-
C Symbols for Application Integration Appendix C 309
-
Symbols for Application Integration Available Symbols for Application Integration Available Symbols for Application Integration The VPO symbol type is a combination of the parameter and the parameter in the syntax: _ The default symbol type used in the English version of the VPO Application Desktop is .
-
D About VPO Man Pages 311
-
About VPO Man Pages In this Appendix In this Appendix This appendix describes the man pages available in the following areas: ❏ Man Pages in VPO ❏ Man Pages for VPO APIs ❏ Man Pages for HP OpenView VantagePoint Navigator ❏ Man Pages for the VPO Developer’s Kit APIs 312 Appendix D
-
About VPO Man Pages Accessing and Printing Man Pages Accessing and Printing Man Pages You can access the VPO man pages from the command line, from online help, or in HTML format on your management server.
-
About VPO Man Pages Man Pages in VPO Man Pages in VPO This section describes man pages in VPO. Table D-1 VPO Man Pages Man Page Description call_sqlplus.sh(1) Calls SQL*Plus. inst.sh(1M) Installs VPO software on managed nodes. inst_debug(5) Debugs an installation of the VPO agent software. ito_op(1M) Launches the VPO Java-based operator or VantagePoint Navigator GUI. opc(1|5) Starts the VPO GUI.
-
About VPO Man Pages Man Pages in VPO Table D-1 VPO Man Pages Man Page Description opcagtreg(1M) Registers subagents. opcagtutil(1M) Parses the agent platform file, and performs operations with extracted data. opcaudupl(1M) Uploads audit data into the VPO database. opcaudwn(1M) Downloads audit data into the VPO database. opccfgdwn(1M) Downloads configuration data from the database to flat files. opccfgout(1M) Configures condition status variables for scheduled outages in VPO.
-
About VPO Man Pages Man Pages in VPO Table D-1 VPO Man Pages Man Page Description opcmack(1) Acknowledges a VPO message by specifying the message ID. opcmgrdist(1M) Distributes the VPO configuration between management servers. opcmom(4) Provides an overview of VPO MoM functionality. opcmomchk(1) Checks syntax of MoM templates. opcmon(1) Forwards the value of a monitored object to the VPO monitoring agent on the local managed node. opcmsg(1) Submits a message to VPO.
-
About VPO Man Pages Man Pages for VPO APIs Man Pages for VPO APIs This section describes man pages for VPO application program interfaces (APIs). Table D-2 VPO API Man Pages Man Page Description opcmon(3) Forwards the value of a monitored object to the VPO monitoring agent on the local managed node. opcmsg(3) Submits a message to VPO.
-
About VPO Man Pages Man Pages for HP OpenView VantagePoint Navigator Man Pages for HP OpenView VantagePoint Navigator This section describes man pages for the HP OpenView VantagePoint Navigator. Table D-3 VantagePoint Navigator Man Pages Man Page Description opcservice(1M) Configures HP OpenView VantagePoint Navigator. opcsvcconv(1M) Converts service configuration files of HP OpenView VantagePoint Navigator from the previous syntax to the Extensible Markup Language (XML).
-
About VPO Man Pages Man Pages for the VPO Developer’s Kit APIs Man Pages for the VPO Developer’s Kit APIs This section describes man pages for the VPO Developer’s Kit application program interfaces (APIs). Table D-4 VPO Developer’s Toolkit Man Pages Man Page Description msiconf(4) Configures the VPO message manager. opc_comif_close(3) Closes an instance of the communication queue interface. opc_comif_freedata(3) Displays free data that was allocated by opc_comif_read().
-
About VPO Man Pages Man Pages for the VPO Developer’s Kit APIs Table D-4 VPO Developer’s Toolkit Man Pages Man Page Description opcif_api(3) API to work with the VPO Message Stream Interface. opciter(3) VPO iterator to step through opcdata container. opcmsg_api(3) Manages VPO messages. opcmsggrp_api(3) Manages VPO message groups. opcmsgregrpcond_api(3) Creates and modifies VPO message regroup conditions. opcnode_api(3) Configures VPO managed nodes.
-
Index A accessing man pages command line, 313 HTML format, 313 add OpenView service window, 158 add OV application window, 157 add VPO application window, 156 add/modify logfile window, 93 add/modify MPE/iX console message window, 97 add/modify SNMP trap window, 96 add/modify template window, 89 add/modify threshold monitor window, 111 add/modify VPO interface window, 98 adding actions to a message, 139 adding an OpenView service, 158 adding annotations to a message, 139 adding conditions, 125 adding instru
-
Index monitor template example, 289 SNMP trap template example, 284 configuration upload, 85 Connection API summary of functions, 201 conventions, document, 15 custom message attributes setting for a condition, 127 customizing VPO, 48 event integration from message sources hints and tips, 133 external notification services, 140 defining, 140 manually forwarding to, 143 D data access and creation functions, 192 Data API summary of functions, 192 Developer’s Kit APIs man pages, 319 Developer’s Toolkit docum
-
Index adding annotations, 59 message templates, 57 threshold monitoring, 55 integrating via notification services, 61 integrating via the application bank, 62 integrating via trouble ticket services, 61 integrating VPO applications, 150 integrating with VPO, 28 integration facilities choosing a capability, 68 integration facilities of VPO, 54 integration methods external applications into the VPO GUI, 144 integration package, 32, 84 adding executables, 262 creating, 254 distributing, 254 downloading configu
-
Index read/write access to, 185 MIB data collection, 101, 115 modifying conditions, 125 monitoring maximum threshold monitoring, 105 MIB data collection, 101 minimum threshold monitoring, 105 threshold monitoring, 100 monitoring capabilities of VPO, 100 monitoring MIB variables, 101 Motif GUI documentation, 23–24 MPE/iX console message interception, 97 defining templates for, 97 MSI example serial scenario, 177 instance names, 175 message distribution, 177 message ID, 176 order numbers, 175 server configura
-
Index Regroup Condition Configuration API overview of functions, 205 related documentation additional, 20–21 Advanced Security, 20 Developer’s Toolkit, 20 ECS Designer, 21 online, 21, 23–25 PDFs, 17 print, 18–19 SunMC, 20, 21 S serialized Server MSI, 173 Server Message API overview of functions, 198 summary of functions, 198 Server Message Stream Interface, 171 access to, 174 overview, 173 server message stream interface output to, 117 setting message and suppress conditions, 124 SNMP event configuration, 7
-
Index VPO agents, 35 VPO APIs locations, 169 summary of functions, 192 VPO conceptual overview, 34 key features, 34 OpenView product family, 34 VPO Configuration APIs, 64 Application Configuration API, 190 Application Group Configuration API, 190 Connection API, 190 Distribution API, 191 Message Group Configuration API, 190 Message Regroup Condition Configuration API, 190 Node Configuration API, 190 Node Hierarchy Configuration API, 190 overview, 190 Server Synchronization API, 191 Template Configuration AP
