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.
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.
Process Name | Queue/Pipe Files | Description |
|---|---|---|
opcactm Action request | Actreqq/p | Action manager |
Action response | ||
Configuration adapter (HTTPS based) | ||
Subprocess of message receiver, used for bulk transfers | ||
Certification Server Adapter | ||
Ctrlq/p Inform control manager of configuration changes | Control Manager | |
Dispq/p Display Manager to the GUI processes Mpicdmq/p Control display manager Sgmceq/p Display manager change events | Display manager | |
Distribution manager | ||
Forwmgrq/p | Message forward manager | |
Msgkeyq/p Manual acknowledgment Mpicmmq/p Control message manager | Message Manager | |
Message receiver (HTTPS based) | ||
Msgmgrq/p Messages and requests | Message receiver | |
Service engine | ||
Ttnsq/p, Ttnsarq/p | Trouble ticket, notification service man-ager | |
Rqsdbdf Buffer file for request sender Rqsq/p Request sender Input | Request sender | |
Transfer manager | ||
TCP socket server | ||
Administrator User Interface | ||
Operator User Interface | ||
Administrator Operator User Interface | ||
Java User Interface manager | ||
Communication broker (HTTPS based) | ||
Control daemon | ||
Configuration and Deploy | ||
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.
The configuration files in Chapter 19 for more information.
[*] The file is not configured by default.
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.
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.
The error and trace files used with the DCE-RPC and HTTPS agents are shown in Table 13-11. Refer to
the 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 |
Refer to the man pages for the command ovconfchg and for more details on how to modify the
configuration.
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. | |
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.
File Name | Description |
|---|---|
/etc/password | User password file |
/etc/group | Group file |
/sbin/init.d/opcagt | Agent startup and shutdown script |
/etc/rc.config.d/opcagt | Agent startup and shutdown configuration variable file |
/sbin/rc3.d/S#opcagt | Startup sequence number linked to the start/stop script |
/sbin/rc2.d/K#opcagt | Shutdown sequence number linked to the start/stop script |
/etc/services | Internet services, and ito-e-gui for opcuiwww (Java clients) (Server Only). |
/etc/inetd.conf | Service configuration for opcuiwww (Server Only). |
/var/adm/inetd.sec | Not configured by default install; used to limit access to the service ito-e-gui (Server Only). |
/etc/rc.log | Contains system, service and application startup information |
/var/adm/syslog/syslog.log | Operating system log file (HP). This file is not used by OVO by default, but may contain information for troubleshooting. |
/var/adm/sw/swagent.log |