HPOM/HPOM Server Processes

Note: HP renamed the product called now HP operations manager way too many times. Also it is very inconsistent with using abbreviations. Here we will assume that the term "HP Operations manager" and abbreviations HPOM, OMU, and OVO  mean the same thing :-)

The command to list processes is:opcsv -status

The following processes run on the HP Operations management server.

1. opcactm  Action manager that feeds the action agents with automatic actions, operator-initiated actions, scheduled actions, and application startup and broadcasting information through the control agent. In addition, external instructions are determined using this mechanism.
2. ovoareqsdr  Request sender that informs the control agents to start, stop, or update their local HPOM agents. The request sender is also responsible for the self-monitoring of HPOM manager services, and for the heartbeat-polling of the managed nodes.
3. ovcd  Control daemon that controls and checks the status of processes and components, which are registered with it.
4. opcdispm Display manager that serves HPOM GUIs. The display manager also feeds the action manager with operator-initiated actions, application startup information (not requiring a separate terminal), and broadcasting information issued by operators. It also serves clients connected to the MSI for message and configuration changes. Several HPOM user GUIs may be active at the same time.
5. opcbbcdist  Configuration management adapter between the HP Operations management server and the HTTPS agents that creates instrumentation from existing actions, commands, and monitors, and switches nodeinfo settings into the XPL format used on HTTPS nodes.
6. opcecm Event correlation manager that connects to the server MSI to allow access to and modification of messages from the HPOM message flow by the event correlation (EC) engine. Depending on filters and conditions, the messages are then correlated and written back to HPOM. The messages display in the Message Details window (available from the Message Browser) with the message source MSI opcecm. Like all server processes, the event correlation manager is controlled by the OV Control, ovcd.
7. opcecmas  Annotation server that runs on the management server and obtains data from outside the ECS engine for use within correlation circuits. This process connects to the opcecm process using the standard annotate API. It receives annotate requests for launching external programs and returns the output to the circuit. opcmsgm Message manager that receives messages from the managed nodes through the message receiver (opcmsgrb). The messages can be correlated, regrouped and logged by the message manager running on the management server. The message manager is also responsible for adding annotations, triggering notifications, and forwarding the message to the trouble ticket and notification service manager for external notification and trouble ticket generation.
8. opcforwm Message forwarding manager that relieves the message manager, opcmsgm, of time-consuming tasks (for example, sending messages to remote managers). This relief allows the message manager to manage messages more effectively. On the local “source” management server, the message forwarding manager receives data from the message manager (in the form of messages), the action manager (action responses), and the display manager (message operations such as acknowledge, add annotation, and so on). The message forwarding manager sends data to the message receiver on the “target” management servers. opctss Distribution manager subprocesses that transfer configuration data to the distribution agent through TCP/IP.
9. opcttnsm  Trouble ticket and notification service manager that feeds the external notification interface, as well as the external trouble ticket interface, with message attributes. This manager is an auxiliary process of the message manager designed to ensure high message throughput. If external instructions are specified for a message, the trouble ticket and notification service manager evaluates the help text through the action manager. Whenever the trouble ticket and notification service manager receives a message in its queue, it passes the message on to the trouble ticket interface or the external notification service. It does so by forking and executing the customer-defined program that receives the message (that is, the ticketing interface or the notification service). As soon as this program is finished and exited, a SIGCHLD is sent to the trouble ticket and notification service manager. The manager stops processing the message queue until it receives another SIGCHLD.
10. opcuiwww  Server process that serves the HPOM Java-based operator GUI. This process forwards all communication requests between the Java GUI and the display manager. For each Java GUI, at least one server process is started.
11. opcuihttps  Server process that acts as a proxy between the Java GUI client and the HPOM management server using the HTTPS protocol.
12. opcsvcm  Service engine that maintains the global (operator-independent) service status and can log service changes into the database. By default, remote access to the service engine is disabled. See HPOM Developer’s Reference for information on how to allow remote access to the service engine.

The files used by the HPOM management-server processes reside in the following directory: /var/opt/OV/share/tmp/OpC/mgmt_sv

The following list describes the queue files and pipes that the HPOM management-server processes use. For more information about the HPOM management-server processes themselves, see “Processes on the HPOM Management Server” on page 359:

• actreqp/actreqq Queue or pipe used by the display manager, message manager, TTNS manager, (and action manager) to pass action requests to the action manager.
• actrespp/actrespq Queue or pipe used by the message receiver, request sender, and action manager to pass action responses to the action manager.
• ctrlq/ctrlp Queue or pipe between the display manager and control manager.
• forwmgrp/forwmgrq Queue or pipe used by the message manager, display manager, action manager, and the forward manager to pass data to be forwarded to other management servers.
• magmgrp/magmgrq Queue or pipe between the message dispatcher and the request handler. mpicdmp/mpicdmq Queue or pipe used by the display manager and the message stream interfaces to transfer control sequences for message-change event handling.
• mpicmmp/mpicmmq Queue or pipe used by the message manager and message-stream interfaces to transfer control sequences for message handling through the Message-Stream Interface (MSI).
• mpimmp/mpimmq Queue or pipe used by the message manager and the message-stream interfaces to transfer messages from MSI programs to the message manager.
• msgmgrq/msgmgrp Queue or pipe between the message receiver and message manager.
• opcecap/opcecaq Queue or pipe used to pass messages from the message manager to the event correlation manager. pids Process IDs of the HPOM managers that are controlled by the HPOM control manager, which is also used for self-monitoring. rqsdbf Buffer file used by the request sender to store requests if the control agent on a given managed node cannot be accessed
• rqsp/rqsq Queue or pipe between the request handler and the request sender. Also used by the display manager and the action manager
• ttnsarp/ttnsarq Queue or pipe used by the trouble-ticket manager and action manager when message instructions have to be fetched by the trouble-ticket notification-service (TTNS) manager.
• ttnsq/ttnsp Queue or pipe between the message manager, trouble-ticket manager, and notification-service manager

In addition to its role as the primary manager for the managed nodes, the server functions as the repository for the agent software and components, including templates (which are converted into policies during distribution) and instrumentation (also known as actions, commands, and monitors). These components allow the HPOM administrator to define the systems, devices, and services within the management domain. The components' definition includes specific service levels for monitors, alarms, and corrective actions. The server includes a run-time version of NNM and the HPOM Oracle database. The server could also have other OpenView products installed for local use or for distribution to the nodes (such as SPIs, Service Navigator, ECS Designer, and so on).

Tasks Performed by the Server

The tasks performed by the management server include but are not limited to the following:

• Collecting Data from the managed nodes

• Regrouping Messages (see the definition of this later in this chapter)

• Calling appropriate agents for specified tasks, such as perform actions

• Controlling the database interface, ensuring that the database is operational

• Forwarding messages to other HPOM servers in larger installations

• Installing agent software onto the managed nodes

• Notifying and updating managed node with configuration changes

• System alive monitoring

• Self monitoring

• Forwarding messages to external processes or notification service interface

• Updating and coordinating user interfaces

• Adding messages to the database

• Correlating duplicate messages

• Routing messages to external processes (such as Event Correlation Manager)

• Installing, tracking, and reporting on HPOM licensing

The Management Server Processes

Following are descriptions of the management server processes.

HPOM Management Server:

• Control Manager (opcctlm)— Started by ovspmd, starts all other HPOM server processes except ovoareqsdr and ovoareqhdlr, and spawns database maintenance processes opcdbmsgmv and opchistdwn. Performs license check.

• Action Manager (opcactm)— Communicates instructions via the managed node's control agent to the action agents to perform automatic and operator actions, scheduled actions, application startup, and broadcasting. Provides mechanism for external interface instruction text.

• Message Manager (opcmsgm)— Receives messages from the managed nodes via the message receiver. Performs message correlation, message regroup, log message to database, add annotations, trigger notifications, and forwards message to trouble ticket and notification manager (opcttnsm).

• TT & Notify Mgr (opcttnsm)— Trouble ticket and notification service manager; feeds an external notification interface with the message attributes from HPOM . For example, can be configured to send email to responsible operators when a critical message is received.

• Forward Manager (opcforwm)— Sends messages to the message receiver on other HPOM management servers. Takes input from message manager, action manager (action responses) and the display manager.

• Service Engine (opcsvcm)— Service Navigator configuration manager. Maintains service graph and calculates service status, built-in adapters handle client requests.

• Display Manager (opcdispm)— Sends message to configured operators, receives input from the message manager, and send GUI action and change requests to action manager or control manager.

• Distribution. Manager (opcdistm)— Distributes agent software, communicates with distribution agent on the managed node, controls manager, connects to database, and reads configuration data.

• Cert. Svr Adapter (opccsad)— Certificate server adapter.

• BBC Config Adaptor (opcbbcdist)— HTTPS Configuration Adapter.

• Request Sender (ovoareqsdr)— Sends and receives request for other processes to the control agent.

• Request Handler (ovoareqhdlr)— Handles request from registered services.

• Message Receiver (opcmsgrd)— DCE-RPC based message and action response receiver daemon, communicates with forward manager on other HPOM servers, starts subagent opccmm for socket connection during distribution, and is started by the request sender.

• Message Receiver (opcmsgrb)— HTTPS-based message receiver daemon

• Control Daemon (ovcd)— Takes input from HTTPS communication broker ovbbccb.

• BBC Communications Broker (ovbbccb)— Listens for incoming communication from the managed node on port 383. sent and received.

• Config and Deploy (ovconfd)— Configuration and Deploy Component for HTTPS agents; converts templates to policies and pushes configurations to the managed nods.

• Certification Server (ovcs)— Security Certificate Server.

Other supporting processes are called for specific tasks as required; they do not appear in the output of the HPOM status commands. Some of the supporting processes are listed here:

• opccmm— Communication manager, started by message receiver for socket services during distribution to node and data transfer and communication to other servers.

• opcuiwww— JAVA GUI process used for client connections to the HPOM server. Started by inetd.

• opctss— TCP socket server, receives port number from distribution manager.

• opcuiop— Operator GUI.

• opcuiopadm— Administrator's operator GUI.

• opcuiadm— Administrator GUI.

• opctranm— Executes file transfer to nodes and remote commands on DCE nodes; used during installation and some SPI discovery.

• opc— Called by ovspmd during server startup; triggers startup of the control manager.

• Event Correlation (opcecm)— Event correlation manager requires an ECS policy.

Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotes :  Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce :  Bernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS :  Programming Languages History : PL/1 : Simula 67 : C : History of GCC development :  Scripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month :  How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019