KM
See Knowledge Module
KM configuration file
KM list
In BMC Performance Manager, a list of KMs used by a PATROL Agent or PATROL Console. See also
Knowledge Module (KM).
KM Migrator
KM package
KM tree
In BMC PATROL, a feature in Microsoft Windows only that displays computer classes, application classes and their customized instances in the knowledge hierarchy, and the Standard Event Catalog. A PATROL Console in operator mode can view only the KM tree; only a PATROL Console in developer mode can change KM properties and attributes. See also
desktop tree and
Knowledge Module (KM).
knowledge hierarchy
In BMC Performance Manager, the rules by which objects inherit attributes or have attributes assigned to them. (In PATROL Consoles for Microsoft Windows environments, classes of objects are represented in the Computer Classes and Application Classes sets of folders on the KM tree.) Properties and attributes of a customized instance override those defined for the class to which the instance belongs.
Knowledge Module package
Knowledge Module (KM)
In BMC Performance Manager, a set of files from which a PATROL Agent receives information about resources running on a monitored computer. A KM file can contain the actual instructions for monitoring objects or simply a list of KMs to load. KMs are loaded by a PATROL Agent and a PATROL Console. KMs provide information for the way monitored computers are represented in the BMC PATROL interface, for the discovery of application instances and the way they are represented, for parameters that are run under those applications, and for the options available on object pop-up menus. A PATROL Console in developer mode can change KM knowledge for its current session, save knowledge for all of its future sessions, and commit KM changes to specified PATROL Agent computers. A KM file contains the source code for a BMC PATROL application. See also
commit,
KM configuration file,
KM list,
KM Migrator,
KM tree,
load KMs, and
version arbitration.
load applications
load KMs
In BMC Performance Manager, to place KM files into memory for execution. After configuration and during startup, the PATROL Agent loads the KM files that are listed in its configuration file and that reside on the PATROL Agent computer. When a PATROL Console connects to the PATROL Agent, the KM versions that the agent executes depend on whether the console has developer or operator functionality. See also
Knowledge Module (KM) and
version arbitration.
local history
In BMC Performance Manager, the history (the stored parameter values) for an object or instance. See also
local level.
local history retention period
In BMC Performance Manager, the length of time set by the user, during which stored parameter values for an object or instance are retained.
local level
In BMC Performance Manager, the BMC PATROL hierarchy level of a computer instance or an application instance. An object (instance) at the local level inherits properties and attributes that are defined globally. When properties and attributes are customized locally for an individual instance, they override inherited attributes.
managed object
In BMC Performance Manager, any object that BMC PATROL manages. See also
object.
managed system
In BMC Performance Manager, a system—usually a computer on which a PATROL Agent is running—that is added (connected) to a PATROL Console to be monitored and managed by BMC PATROL. A managed system is represented by an icon on the BMC PATROL interface.
management profile
In BMC Performance Manager, a user profile for PATROL Central and PATROL Web Central that is stored by the console server. A management profile is similar to a session file and contains information about custom views, your current view of the BMC PATROL environment, information about systems that you are currently managing, Knowledge Module (KM) information, and console layout information for PATROL Central. Management profiles replace
desktop files and
session files that were used in BMC PATROL 3.x and earlier.
master agent
message retries
In BMC Performance Manager, the number of times that the PATROL Console will resend a message to the PATROL Agent. Message retries is a feature of User Datagram Protocol (UDP) only. The greater the number of message retries, the more time the PATROL Console will give the PATROL Agent to respond before deciding that the agent connection is down and timing out. The number of message retries multiplied by message timeout (in seconds) is the approximate time allowed for a connection verification. See also
heartbeat,
message timeout, and
reconnect polling.
message time-out
Unable to render {include} The included page could not be found.
message window
multigraph container
In BMC Performance Manager, a custom object into which you can drop parameter objects to be plotted as charts. See also
PATROL Console Charting Server.
object
- An item that can be inserted into a dashboard; for example, a chart, link, or Active-X control.
- A generic term for anything that is displayed in the user interface.
See also class.
BMC Capacity Optimization
Any BMC Capacity Optimization item displayed in the scope pane or results pane in the Microsoft Management Console (MMC). You can double-click an object in the scope pane to access properties for that object in the results pane, or right-click an object to select several options from a menu. Each BMC Capacity Optimization component contains objects specific to that component. For example, in Investigate, objects are any items that comprise a policy, such as domains or computers.
A computer class, computer instance, application class, application instance, parameter, or container (folder) in an environment that BMC PATROL manages. Objects have properties and are assigned attributes (command types, parameters, menu commands, InfoBox commands, setup commands, state-change actions, and environment variables). Parameter objects use data-collection commands to obtain values from classes and instances. See also object class, object hierarchy, Object icon, and object window.
object class
In BMC ProactiveNet Performance Management, a data structure that defines a type of object. An object class can be a
Basic Recorder of Objects in C (BAROC) language data structure in the Knowledge Base of a cell. An object class can also be a Common Data Model (CDM) data structure in BMC Atrium Configuration Management Database (BMC Atrium CMDB). An object class is made up of data fields, called attributes (slots), that define its properties. See also
event class and
object.
object hierarchy
In BMC Performance Manager, the structure of object levels in BMC PATROL. On the BMC PATROL interface, computers contain application folders (containers) that represent a loaded Knowledge Module (KM), application folders contain one or more application instances, and application instances contain parameters.
Object icon
BMC Capacity Optimization
A graphical representation of specifications for:
- Domains
- Computers
- Application instances
- Alert sets
- Alerts
- Alert metrics and conditions
- Filters
- Mail, script, and SNMP trap actions
BMC PATROL
A graphical representation of a computer instance, application class, application instance, parameter, or container (folder) in an environment managed by BMC PATROL. See also object, object hierarchy, and object window.
object window
In BMC Performance Manager, an open object container (folder) that might contain application class icons, application instance icons, parameter icons, custom containers (folders), and shortcuts. The object window is displayed when you double-click the object icon. See also
application instance,
computer instance,
object, and
Object icon.
operating system account
operator mode
In BMC Performance Manager, an operational mode of the PATROL Console that can be used to monitor and manage computer instances and application instances. This mode cannot be used to customize or create Knowledge Modules (KMs), commands, or parameters. See also
PATROL Console.
override a parameter
In BMC Performance Manager, to disable or change the behavior of a local BMC PATROL application parameter. The changes to the parameter are local to the managed system running the parameter and are stored in the agent configuration database. To override parameters, you must be granted specific permissions by a BMC PATROL Administrator through the PATROL User Roles file. See also
PATROL roles.