14.2 THE OVO MANAGEMENT SERVER PROCESSES
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 OVO 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 OVO 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).14.2.1 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 OVO 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 OVO licensing
14.2.3 The Management Server Processes
Following are descriptions of the management server processes.OVO Management Server:- Control Manager (opcctlm)
Started by ovspmd, starts all other OVO 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 OVO. 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 OVO 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 OVO 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 OVO 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 OVO 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.
|
لطفا منتظر باشید ...
