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

14.5 AGENT CONFIGURATION

The agent configuration is performed through the administrator's GUI or from the command line.

14.5.1 Agent Configuration Files

Information and instructions are provided to the agents via the policies and configuration files. For example, you change the node type from controlled to message allowed via the GUI. After you close the DCE-based node configuration window, the update is immediately sent to the configuration file (nodeinfo) on the managed node and you will see a message about the new configuration in the message browser. HTTPS-based nodes do not use a nodeinfo file. Using the command

opcragt , you can check or change DCE node configuration parameters. For example, the following configuration variable is set using the

opcragt command line:

# cd /opt/OV/bin/OpC/install
# ./opcragt -set_config_var OPC_MAX_ICMP_PINGS=10 nodename
nodename.domain.yourco.com
Node nodename.domain.yourco.com
Done.

The RPC/DCE-based agent configuration files include the following:

• opcinfo
  Uses variables to customize agent behavior for the specific environment; not affected by the node configuration changes.

• nodeinfo
  Contains the node configuration information; overwritten if the node configuration is modified.

• mgrconf
  Configures to what servers the node is allowed to forward messages and determines what servers are allowed to send a request to perform actions on the node. Used within a

  manager of managers (MOM) environment.

Starting with 8.0HTTPS-based agents, the DCE-RPC files are replaced by a policy configuration file. A policy is a template in XML format. Executing the following commands performs changes to the policy files:

ovconfchg
Manipulates settings files, updates the configuration database, and triggers notification scripts.

ovconfpar
Sets and returns configuration parameters remotely.

ovconfget
Returns specified attributes from the configuration database.

Refer to the

HTTPS Agent Concepts and Configuration Guide and the man pages for more information on the policy files.

14.5.2 Server Configuration Files

Similar to the configuration and operation on the managed node, the server processes obtain information and instructions for operational behavior during startup via server policies. For example, the server policy for Event Correlation or Server Regrouping could be configured for the server. Refer to Chapter 20 for more information on HTTPS and OVO security components.

The agent and server process behavior can be altered or enhanced using various configuration variables. The server configuration file locations can be determined during the installation by defining two symbolic path definitions, InstallDir and DataDir. The default directories on the UNIX platform are /opt/OV and /var/opt/OV. You can check the runtime directory paths with the command ovpath. Refer to the man page for syntax details.

14.5.3 The Message Stream Interface (MSI)

Some agent components are external programs written using the OpenView

Application Programming Interfaces (APIs)

The

message stream interface (MSI) provides a program interface for external programs to obtain OVO messages if the message interface is configured to open the message queues for read/write. The APIs are used to create, read, write, and modify the messages. OVO provides the mechanism to enable MSI input or output via the template, node, and server configuration, and the Advance Options window. The event correlation engine is one example of how OVO uses the MSI.

The MSI is covered in more detail in the

OpenView Developers (Software) Toolkit . Refer to the OpenView web site http://openview.hp.com for links to information for software developers.