لطفا منتظر باشید ...
13.18 OVO SERVER AND NODE RESOURCES
One of the most challenging parts of learning about the OpenView platform is remembering what file is located in which directory. The tables in this section are quick references for the binaries, configuration, log, component, and queue files that are located on the server and managed nodes (for HTTPS-based agents and DCE-RPC-based agents). The server stores the platform specific agent configuration files. Reference the Administrators Reference, Volume 2 , for the agent platform-specific file locations.
13.18.1 Processes and Queue Files
Table 13-6 is a quick reference for most of the OVO processes and associated queue files. During run time the processes use the queues and pipes for inter-process communications and temporary data storage. The information listed in the table is for reference only. Chapter 22 covers additional information about the queue files.
13.18.2 Server Directory Structure
The directories on the management server, shown in Figure 13-8, are used for storing the binary (/opt/OV), configuration (/etc/opt/OV), and run time (/var/opt/OV) files. Included for example, are the vendor or customer specific versions of the OVO agent software, actions, commands, and monitors. During distribution, the node-specific flag files are created in the interim distribution directory (/var/opt/OV/share/tmp/OpC/mgmt_sv/distrib) on the server. Prior to transferring the data the configuration is packaged for the appropriate managed node. Details about the OVO agent distribution process are covered in Chapter 14. The Smart Plug-In (add-on components) directories created for the SPI are not included in these tables.
13.18.3 Server Configuration Files
The configuration files in Chapter 19 for more information.
[*] The file is not configured by default.
13.18.4 Managed Node Directory Structure
The following directories on the managed node are used for storing the binary (/opt/OV/bin/OpC), configuration (/var/opt/OV/bin/instrumentation), and run-time (/var/opt/OV) files.
13.18.5 Managed Node Configuration Files
The files nodeinfo and opcinfo (used with prior releases of OVO) are combined into one data file (on HTTPS-based nodes) and the configuration changes to the file are made with either the command /opt/OV /bin/ovconfget locally or /opt/OV /bin/ovconfpar remotely from the OVO server. Refer to the man pages for details about the commands.The configuration file listed in Chapter 19 for more Information on message forwarding concepts.
13.18.6 Error and Log Files
The error and trace files used with the DCE-RPC and HTTPS agents are shown in Table 13-11. Refer tothe HP OpenView Operations Tracing Concepts and User Guide for information on configuring tracing.
| File Name | Description |
|---|---|
| /var/opt/OV/System.txt | Error file |
| /var/opt/OV/share/tmp/OpC/mgmt_sv/cfgchg | Configuration change queue file |
| File Name | Description |
|---|---|
| /var/opt/OV/tmp/OpC | Agent queue files |
| /var/opt/OV/log/OpC/opcerror | Agent error log file |
| Note: Refer to Administrator's Reference Volume 2 for other agent platforms. | |
13.18.7 System Resource Files
The files listed in Table 13-13 are general system resource files that are modified or created by OpenView during the initial installation of the server or managed node.
