Understanding the Product
The Enterprise Scheduler HP Operations Manager for Unix (HP OMU) adapter provides integration of Enterprise Scheduler into HP OMU.
This integration consists of several parts, including:
-
Policies for accepting messages sent by Enterprise Scheduler actions
Enterprise Scheduler actions can be configured to generate HP OMU messages, which are forwarded by the local HP OMU agent to the HP OMU Management Server. These actions are triggered by the occurrence of system or job events configured in Enterprise Scheduler.
-
Policies for monitoring Enterprise Scheduler services
These services may be on the master, backup master, fault monitor and/or agents. Agent monitoring is available for either the original Enterprise Scheduler agent or the high-performance agent for both Unix and Windows systems.
With these applications the HP OMU operator can quickly and easily perform common Enterprise Scheduler tasks from the HP OMU console.
These executables are provided to manage Enterprise Scheduler agents on Unix nodes and provide general access to the Enterprise Scheduler command-line facility.
All of the HP OMU messages generated by Enterprise Scheduler include help text, and many include operator-initiated actions, allowing one-click response to certain problems. Use of these and other standard HP OMU integration points provide an interface familiar to any HP OMU operator.
This manual is not intended to replace the documentation provided with HP OMU and Enterprise Scheduler. Specifically, you need the HP OMU and Enterprise Scheduler documentation appropriate to your installation to achieve a thorough understanding of both products.
System Requirements
-
This integration only works with Enterprise Scheduler version 6.0 or higher.
-
Only HP OMU 9.0 is supported with Enterprise Scheduler.
-
This integration does not place any significant resource requirements on any of the systems beyond what is expected by normal operation of the Enterprise Scheduler and HP OMU products. Refer to the documentation for your versions of Enterprise Scheduler and HP OMU to determine your actual system requirements. Consistent with normal usage of Enterprise Scheduler and HP OMU, the functionality provided by this integration consumes a small amount of system resources on server and agent machines.
-
Enterprise Scheduler must be installed, licensed and fully operational before installing this integration.
-
HP OMU must be installed, licensed and fully operational before installing this integration.
-
The Enterprise Scheduler machine must be a HP OMU managed node. Any Enterprise Scheduler agent nodes that you wish to monitor must also be HP OMU managed nodes. The HP OMU Management Server does not need to be a Enterprise Scheduler client, agent or master node.
Terms to Know
-
Client Manager—As one of two main components of the Enterprise Scheduler architecture, Client Manager services requests from user initiated activities, such as through the Tidal Web Client and from other external sources that utilize the Command Line Interface (CLI) or published Enterprise Scheduler Web services.
-
Event—In the case of HP OMU, an event is any occurrence that can be detected by the monitoring facilities of HP OMU. In the case of Enterprise Scheduler, it is one of a fixed list of system or job states or conditions.
-
HP—The Hewlett Packard Company.
-
MIB—Management Information Base Enterprise Scheduler provides MIBs for HP NNM to identify the trap messages and understand their structure.
-
Object—An object represents a particular entity or resource in a networked systems environment.
-
HP OMU Tool—A HP OMU tool is an icon/link in the Tool Bank that, when triggered by the operator, causes some action to be taken. Starting, stopping and checking the status of the Enterprise Scheduler agent are examples of OMU Tools
-
HP OMU Managed Node—A computer or network device controlled or monitored by HP OMU. Typically this is a computer with a HP OMU intelligent agent installed.
-
HP OMU Management Server—The computer where the HP OMU server software is installed.
-
Policies—The new term for templates.
-
Submap—A submap is a particular view of the network environment. It consists of related symbols that are displayed in a single window.
-
Symbol—A symbol (icon) is a graphical representation of an object.
-
Policy—A policy is an HP OMU component that specifies a set of conditions that determine which events are ignored and which events generate messages in HP OMU. Different types of policies are used for different methods of monitoring, such as message policies, monitor policies, log file policies, SNMP policies, etc. Policies are assigned to and distributed to managed nodes to perform monitoring.
-
Tools—A term used to describe the various installed software applications that is used HP OMU for monitoring.