access control list (ACL)
BMC PATROL
A list that is created by using a PATROL Agent configuration variable and that restricts PATROL Console access to a PATROL Agent. A PATROL Console can be assigned access rights to perform console activities, agent-configuration activities, or event-manager activities. The console server uses ACLs to restrict access to objects in the Common Object System (COS) namespace.
BMC ProactiveNet
A list that comprises the WriteLevelSecurity and ReadLevelSecurity fields of BMC Atrium CMDB and BMC ProactiveNet. Access control in BMC ProactiveNet is specified through ACLs defined in a configuration item (CI). ACLs of a CI control which user groups have access to the CI.
BMC Server Automation
A set of permissions that is defined for every system object. The ACL for an object specifies which roles are granted access to the object and what types of actions those roles can perform on the object. Using the ACL defined for any server, you can generate an agent ACL.
agent namespace
Agent Query
In BMC PATROL, a PATROL Console feature that constructs SQL-like statements for querying PATROL Agents connected to the console. Agent Query produces a tabular report that contains information about requested objects and can be used to perform object management activities, such as disconnecting and reconnecting computers. Queries can be saved, reissued, added, or changed. BMC PATROL offers built-in queries in the Quick Query command on the
Tools menu from the PATROL Console main menu bar. See also
Quick Query.
ALL_COMPUTERS class
In BMC PATROL, the highest-level computer class. Attributes assigned to this class are inherited by all computer classes known to BMC PATROL. See also
class and
computer class.
annotated data point
In BMC Impact Solutions, a specially marked point on a parameter graph that provides detailed information about a parameter at a particular moment. The associated data is accessed by double-clicking the data point, which is represented by a user-specified character.
application check cycle
In BMC PATROL, the interval at which application discovery occurs. The PATROL Agent process cache (as opposed to the system process table) is checked to ensure that all application instances and files previously discovered still exist in the cache.
See also application discovery, application discovery rules, prediscovery, process cache refresh, PSL discovery, and simple discovery.
application class
In BMC PATROL, the object class to which an application instance belongs. An application class is also the representation of the class as a container (UNIX) or folder (Microsoft Windows) on the PATROL Console. You can use the developer functionality of a PATROL Console to add or change application classes. See also
class.
application discovery
In BMC PATROL, a PATROL Agent procedure carried out at preset intervals on each monitored computer to discover application instances. When an instance is discovered, an icon appears on the BMC PATROL interface. The application class includes rules for discovering processes and files by using simple process and file matching or PSL commands. Application definition information is checked against the information in the PATROL Agent process cache, which is periodically updated. Each time the PATROL Agent process cache is refreshed, application discovery is triggered.
See also application check cycle, application discovery rules, PATROL Agent process cache, prediscovery, simple discovery, and PSL discovery.
application discovery rules
In BMC PATROL, a set of rules stored by the PATROL Agent and periodically evaluated to find out whether a specific instance of an application class exists in the monitored environment. The rules describe how a PATROL Agent can detect instances of the application on a computer. There are two types of application discovery: simple and PSL. PSL discovery can include prediscovery rules as well as discovery rules.
See also application check cycle, application discovery, prediscovery, simple discovery, and PSL discovery.
application filter
In BMC PATROL, a feature used from the PATROL Console to hide all instances of selected application classes for a particular computer. The PATROL Agent continues to monitor the application instances by running parameter commands and recovery actions.
application instance
An instance of a particular type of application or system resource. The instance processes or attributes can be specified in the configuration for collection and monitoring.
BMC Remedy ITSM
For example, the request entry that is created using a back-end request form when you submit a service request.
application state
The condition of an application class or an application instance. The most common application states are OK, warning, and alarm. An application class or instance icon can also show additional conditions. See also computer state and parameter state.
BMC Remedy AR System
The development state of a deployable application, such as Test or Production. Roles can be mapped to different groups based on application state to limit access to the application during testing or modification. See also deployable application, group, and role.
attribute
BMC Atrium Orchestrator
A name/value pair associated with an XML element.
BMC Atrium Core and BMC Remedy ITSM Suite
A property or characteristic of a class, such as the IP address of a computer system. An attribute equates to a column on a database table or a field on a BMC Remedy AR System form.
A characteristic or property of an object, such as a common-data-model service-model component class. An attribute might contain a value.
A characteristic that is assigned to a BMC PATROL object (computer class, computer instance, application class, application instance, or parameter) and that you can use to monitor and manage that object. Computers and applications can have attributes such as command type, parameter, menu command, InfoBox command, BMC PATROL setup command, state change action, or environment variable. Parameters can have attributes such as scheduling, command type, and thresholds. An attribute can be defined globally for all instances of a class or locally for a particular computer or application instance. An instance inherits attributes from a class; however, an attribute defined at the instance level overrides inherited attributes. See also local level.
BMC Server Automation
A characteristic of a BLPackage.
built-in command
In BMC PATROL, an internal command available from the PATROL Agent that monitors and manages functions such as resetting the state of an object, refreshing parameters, and echoing text. The command is identified by the naming convention
%command_name
. See also
built-in macro variable.
built-in macro variable
In BMC PATROL, an internal variable created and maintained by BMC PATROL for use in built-in commands and PATROL Script Language (PSL). The variable is identified by the naming convention
variable_name
. See also
built-in command.
chart
charting server
class
BMC Atrium Core
Metadata in BMC Atrium CMDB that defines a type of object, usually a configuration item (CI) or relationship. Either of these types of class can store data as a regular class, categorization class, abstract class, or abstract class with data replication. You can also apply the final class and singleton class options to a CI.
- A data storage element. In database terms, a class relates to a table in a database or a form in the Remedy AR System.
- A BAROC-language data structure that defines a type of object used by the cell. A BAROC class is made up of data fields, called slots, that define the properties of the class.
The object classification in BMC PATROL where global attributes can be defined. The attributes are then inherited by instances of the class. An instance belongs to a computer class or an application class. See also application class, computer class, and event class.
command-line argument
In BMC PATROL, an option for starting a PATROL Agent or a PATROL console at the OS command line. PATROL Agent arguments include names of Knowledge Modules (KMs) to load and port numbers for agent-console connection. PATROL console arguments include connection mode (developer or operator), user ID to start the PATROL console, names of KMs to load, and names of files to use.
command text editor
In BMC PATROL, a component that provides basic text editing functions for a PATROL console. The command text editor is commonly used to add or change commands (menu commands, parameter data collection and recovery actions, InfoBox commands, setup commands, and state change actions).
command type
In BMC PATROL, the designation assigned to a command according to its manner of execution. This attribute must be defined for a parameter command, a parameter recovery action, a menu command, an InfoBox command, a configuration command, or a state change action. The PATROL Agent provides two command types: OS and PSL. PATROL Knowledge Modules (KMs) provide additional command types. The developer functionality of a PATROL console can be used to add or change command types.
commit
In BMC PATROL, the process of saving to PATROL Agent computers the changes that have been made to a Knowledge Module (KM) by using a PATROL console. A BMC PATROL user can disable a PATROL console's ability to commit KM changes.
computer class
In BMC PATROL, the basic object class to which computer instances of the same type belong. Examples include Solaris, OSF1, HP, and RS6000. BMC PATROL provides computer classes for all supported computers and operating systems. A PATROL Console with developer functionality can add or change computer classes.
computer instance
In BMC PATROL, a computer that is running in an environment managed by BMC PATROL and represented by an icon on the BMC PATROL interface. A computer instance contains the information and attributes of the computer class to which it belongs. See also
instance.
computer state
In BMC ProactiveNet Performance Management, the condition of a computer. The main computer states are
OK,
warning, and
alarm. A computer icon can show additional conditions, including
no output messages pending,
output messages pending,
void because a connection cannot be established, and
void because a connection was previously established but now is broken. See also
state.
configuration file
BMC Atrium Orchestrator
A file containing configuration information used to communicate with a CDP.
BMC Server Automation
A file used for either of the following purposes:
- Storing configuration information for a program or an operating system. A Windows INI file is an example of a configuration file used for this purpose.
- Defining permissions that determine which clients and users have access to RSCD agents. BMC Server Automation configuration files also control how communication occurs between Network Shell and the console and RSCD agents running on managed servers, and how logging is performed. The primary BMC Server Automation configuration files are the users, exports, and secure files.
See KM configuration file and PATROL Agent configuration file.
connection mode
In BMC PATROL, the mode in which the PATROL Console is connected to the PATROL Agent. The mode can be developer or operator and is a property of the Add Host dialog box (in BMC PATROL 3.x and earlier), an Add Managed System wizard, or another connection method. The connection mode is a global (console-wide) property that can be overridden for a computer instance. See also
PATROL Console.
console module
In BMC PATROL, a program that extends the functionality of PATROL Central and PATROL Web Central. Console modules can collect data, subscribe to events, access Knowledge Module functions, authenticate users, and perform security-related functions. Console modules were formerly referred to as add-ons or snap-ins.
console server
In BMC PATROL, a server through which PATROL Central and PATROL Web Central communicate with managed systems. A console server handles requests, events, data, communications, views, customizations, and security.
container
A custom object that you can create to hold any other objects that you select—such as computers, applications, and parameters—in a distributed environment. In Microsoft Windows, a container is referred to as a folder. You can drag and drop an object into and out of a container icon. However, you cannot drop objects from one computer into another computer. After a container is defined, the object hierarchy applies at each level of the container. That is, a container icon found within another container icon assumes the variable settings of the container in which it is displayed. See also object hierarchy and PATROL Console Charting Server.
BMC Remedy AR System
A component of AR System that is used to store collections of objects and is the underlying data structure for guides and applications. A container is used as the basic storage structure for applications, active link guides, filter guides, and packing lists.
custom view
In BMC PATROL, a grid-like view that can be created in PATROL Central or PATROL Web Central to show user-selected information.
deactivate a parameter
In BMC PATROL, to stop running a parameter for selected computer or application instances. In PATROL Consoles for Microsoft Windows environments, deactivating a parameter stops parameter commands and recovery actions. Deactivating a parameter also deletes the parameter icon from the application instance window without deleting the parameter definition in the KM tree. A deactivated parameter can be reactivated at any time. See also
snooze an alarm and
suspend a parameter.
deactivate an application class
In BMC PATROL, to stop monitoring an application class and all of its instances on selected computer instances. In PATROL Consoles for Microsoft Windows environments, deactivating an application class deletes the application class and all of its instance icons from the computer window without deleting the application class or definition in the KM tree. A deactivated application class can be reactivated at any time. See also
application filter and
deactivate a parameter.
desktop file
In BMC PATROL 3.x and earlier, a file that stores your desktop layout, the computers that you monitor, the Knowledge Modules (KMs) that you load, and your PATROL Console user accounts for monitored objects. You can create multiple desktop files for any number of PATROL Consoles. By default, desktop files always have a .dt extension. In BMC PATROL 7.x, the desktop file is replaced by the
management profile. See also
desktop template file.
desktop template file
In BMC PATROL 3.x and earlier, a file that stores information about the desktop setup of one computer. You can create multiple desktop template files for any number of PATROL Consoles. Each PATROL Console user can apply a template to selected computers on the desktop. By default, desktop template files always have a .dtm extension. See also
desktop file.
desktop tree
In BMC PATROL for Microsoft Windows, one of the views of folders. The desktop tree displays the object hierarchy. See also
KM tree.
developer mode
In BMC PATROL, an operational mode of the PATROL Console that can be used to monitor and manage computer instances and application instances. Developer mode can also be used to customize, create, and delete locally loaded Knowledge Modules (KMs) and commit these changes to selected PATROL Agent computers. See also
PATROL Console.
disable a KM
In BMC Performance Manager, to temporarily or permanently block an application or Knowledge Module (KM) from loading, and to block the PATROL Agent from using that KM. When a KM is disabled (added to the disabled list) in the agent configuration file, the KM files are not deleted from the PATROL Agent computers. However, the PATROL Agent stops using the KM to collect parameter data and run recovery actions. By default, no KMs are disabled. Most KMs are composed of individual application files with a
.km extension. See also
preloaded KM,
static KM, and
unload a KM.
discovery
The act of scanning your environment for configuration data.
BMC Atrium Discovery and Dependency Mapping
Discovery is driven by reasoning, which infers detailed information about hosts and programs and populates the datastore. See also Reasoning Engine.
BMC Server Automation
Discovery creates components by associating component templates with servers.
BMC Capacity Optimization
Discovery identifies the computers with Perform Agents in your network so you can add them to your policy. You can use auto discovery or manual discovery.
event
BMC Atrium Discovery
A change or action, such as creating or updating a software instance, that affects the discovery process. In BMC Atrium Discovery, the Rules Engine (ECA Engine) executes rules in response to events.
BMC Atrium Core
A particular type of change to the instances of specified classes. You can publish an event so that any instance of it is written to the CMDB:Events form. You can receive notification each time an instance of the event occurs when the form is polled.
The occurrence of a change in state, such as the appearance of a task icon, the launch of a recovery action, the connection of a console to an agent, or a change of state in a monitored object (computer class, computer instance, application class, application instance, or parameter) that has significance for the management of a configuration item (CI) or IT service.BMC Remedy AR System and BMC Remedy ITSM
An occurrence in AR System that can trigger other events or workflow. Examples include user interactions with a form (such as opening windows, tabbing from field to field, switching row focus, and so on), state transitions of requests, or any condition that arises when a request is manipulated.
event acknowledgment command
event catalog
In BMC PATROL, a collection of event classes associated with a particular application. BMC PATROL provides a Standard Event Catalog that contains predefined Standard Event Classes for all computer classes and application classes. You can add, customize, and delete an application event catalog only from a PATROL Console in the developer mode. See also
event class and
Standard Event Catalog.
event class
A category of events that you can create as a child of the base event class. You specify how you want the events to be handled by an event manager and what actions you want to be taken when the event occurs. Event classes might be inherited from parent objects, depending on the specific product. The event class defines the type of an event.
A category of events that you can create based on how you want the events to be handled by an event manager and what actions you want to be taken when the event occurs. Event classes are stored in event catalogs and can be added, modified, or deleted only from a PATROL Console in the developer mode. BMC PATROL provides a number of event classes in the Standard Event Catalog, such as worst application and registered application. See also event catalog and Standard Event Catalog.
event class command
In BMC PATROL, a command that is run by the PATROL Agent when certain events occur and that is used in conjunction with an event manager such as the
PATROL Event Manager (PEM). An event class command is specified for the event class that the event is associated with. A command can be one of three types: escalation, notification, or acknowledgment. See also
event acknowledgment command,
event escalation command, and
event notification command.
event escalation command
event escalation period
In BMC PATROL, a period during which an increase in the severity of an event occurs as the result of its persistence. Escalation actions are defined as part of escalation command definitions for event classes and can be triggered only by the PATROL Agent. See also
event escalation command.
event history repository
In BMC PATROL, a circular file where events are stored by the PATROL Agent and accessed by an event manager such as the
PATROL Event Manager (PEM). The file resides on the PATROL Agent computer and retains a limited number of events. When the maximum number of events is reached and a new event is stored, the oldest event is removed in a cyclical fashion. See also
history repository.
event manager
In BMC Performance Manager, a GUI for monitoring and managing events. The event manager can be used with or without the PATROL Console. See also
PATROL Event Manager (PEM).
event notification command
event type
In BMC PATROL, the category that BMC PATROL provides for an event according to a filtering mechanism in an event manager. Event types include information, state change, error, warning, alarm, and response.
event view filter
Event Diary
In BMC PATROL, the part of a PATROL Event Manager (PEM) where you can store or change comments about any event in the event log. You can enter comments at any time from the PATROL Event Manager Details window.
expert advice
In BMC PATROL, comments about, or instructions for dealing with, BMC PATROL events as reported by the PATROL Agent. Expert advice is defined in developer mode or operator mode, in the Event Properties dialog box of a PATROL Console in the PATROL Event Manager.