| Oracle® Enterprise Manager Configuration Change Console User's Guide 10g Version 10.2.0.5 for Windows or UNIX Part Number E15313-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Configuration Change Console User's Guide 10g Version 10.2.0.5 for Windows or UNIX Part Number E15313-01 |
|
|
PDF · Mobi · ePub |
An option available to a notification recipient to approve and take responsibility for a pending notification.
Installed on individual monitored devices, the agent collects change event data, such as information about specific files, processes or user accounts, as well as inventory information (CPU usage, memory capacity, etc.), and reports it to the Configuration Change Console server.
An actual module that is part of the agent that is responsible for a specific type of monitoring. For instance, file monitoring is done by a specific File Watch agent module.
A mapping of component instances that relates and should be named after your business applications; ie: the "Finance" application.
Alpha-Numeric identification number physically associated with a hardware device, used for inventory purposes within your organization.
A configuration of what actions to take when certain events occur that are tied to a component or component instance.
An event that has been reconciled with a Change Management server and a ticket has been found that indicates this change should happen. There are many factors that are considered during reconciliation.
In terms of the dashboards, a baseline is a calculated expected value for the given time period based only on change rates. For instance, in the past month if you expect X changes per day, then the baseline for today's change count would be X.
Hierarchical classification system used in change management servers. See also CTI. For Change management systems that have a two level hierarchy, the levels are typically called Category and Sub-Category.
A file deletion, creation, modification, rename; A process start or stop; A user login or logoff; etc.
A user defined blueprint of an important elements (both internal and external) that makes up an application used in the monitored environment. An an example, the Finance application may have a database component, an application server component, a firewall component, one or more patch components that define changes that will occur in a patch. A component can be very granular describing a single rule in an application, or can be very broad to cover many rules across every application.
Elements associated with a component's internal capabilities, for example Registry key values, database tables, LDAP configuration items, etc.
A granular element of a policy definition for an industry standard such as COBIT, PCI, or ITIL.
A categorization specifically for the BMC Remedy Change Management Server. The category indicates the overall classification of a ticket, the type indicates the individual subset of the classification, and the item denotes the individual object. For example, you could have a CTI that listed the category, Software, the type Finance, and the item Application Server. See Categorization.
A user that has been detected by an agent over the course of monitoring. The user may have been detected because the user logged in or out of a device. The user could also be detected if a file change was made by the user.
The difference in minutes between a time displayed on a managed device and the time displayed on the server if the two clocks are not synchronized. If a discrepancy exists, all generated notifications will factor the deviation time into the time stamp.
A computer or server within your infrastructure. This can be a physical device or a single virtual operating system instance.
An administrator defined grouping of devices with similar applications, operating systems, and/or purposes.
A ticket that is created in a Change Management server that does not typically require all of the normal approvals because the IT operations staff is trying to solve a critical problem and there is no time to wait for approvals.
All People, users, devices in your organization and the associated rule sets and rules used for monitoring within the Configuration Change Console.
In terms of pending notifications, an option available to a notification's recipient to forward the notification to the next person in the Escalation path.
The forwarding path a notification follows when its recipient is unable to respond within a specific time frame. Notifications are usually forwarded to the next highest manager within the organizational hierarchy until a manager is reached that has no higher manager.
A file deletion, creation, modification, rename; A process start or stop; A user login or logoff; a database table change, read, etc.
The monitoring of files, processes, or users related to, but outside of an application. These could also be referred to OS monitoring.
In terms of the Configuration Change Console an individual file to be monitored for change events.
In terms of the Configuration Change Console, information pertaining to storage capacity and available disk space for a specified device.
A region near the top of most screens that let you choose various options to limit the details shown in the window.
An industry standard compliance structure such as COBIT, PCI, ITIL. These frameworks define policies and controls to ensure your IT organization is adhering to the standard.
A probe module state where the probe collects and queues data but does not report it to the Configuration Change Console.
The managed devices within your organization which are monitored by the Configuration Change Console.
An instance of an object; The most common instance is the component instance. You can define a component then assign that component to more or one device. Each of these assignments results in a single component instance.
The monitoring of elements intrinsic to the internal operation of an application, such as registry keys, database tables, or LDAP configuration items.
A person configured within the Configuration Change Console that is ranked above another within the organizational hierarchy.
A definition of the content of an SNMP message. For SNMP monitoring, a MIB can be imported into the server so that object IDs that are represented as a series of numbers can be converted to human readable descriptions of the events.
A message generated by the Configuration Change Console to alert an administrator of a change event, resource consumption threshold, user login/logoff, or error occurrence.
An option within the Configuration Change Console to change an authorization status, or create an exception to a predefined time window.
A group that contains another group. For example a group named Computers that contained another group named Production would be the parent group. While multiple groups can be assigned to a single parent group, each group can have only one parent.
The complete directory tree location for a stored file, starting from the individual device drive and ending at the directory in which the file is stored. Applicable for file names and process names.
The persons, roles, and teams that interact with the Configuration Change Console user interface.
Someone who can log in and view data within the Configuration Change Console using their configured user name and password.
A person configured within the Configuration Change Console who shares the same rank as another person within the organizational hierarchy.
For Change Management integration, a planned change is ticket that has its planned start or planned end time in the future. This means that the ticket is set up to define a change to happen in the future.
A policy is a structure that maps directly to an industry standard such as PCI, Cobit, ITIL. A policy has controls to ensure your IT organization is adhering to the standard.
A set of objects that come with the Configuration Change Console. You can save a copy of a predefined object to use it your configuration. Examples include components, frameworks, policies, components.
Main email address for a Person. The primary email address is used by the Configuration Change Console for notification purposes.
An indicator as to the importance of an event or notification defined in an Audit Action. For notifications, a notification can follow a more direct, or more roundabout escalation pattern depending on its priority.
A resource used by a running software application that performs a single task. The Configuration Change Console monitors processes to verify what programs are being run, and what changes are occurring while they are in use.
The deletion of information once it has reached a predefined expiration date. For example, Database Purging.
In terms of Pending Notifications, an option available to a notification recipient to assign responsibility for a notification to another person within the organization.
A Person configured within the Configuration Change Console who can view all screens except for Configuration and Administration screens.
A machine used to connect to the Configuration Change Console server. In broader terms any machine used to access a central machine.
A single monitoring definition inside of a component rule set. For instance, specifying to monitor c:\windows\system32 would be a single rule.
A type of rules to add to a component for monitoring. Rule Sets are tied directly to the agent modules available on the given device. For instance, one rule set is the File Rule Set. You can add the File Rule Set to a component, then define rules for that Rule Set.
A monitoring capability where events are detected by taking snapshots at set intervals and comparing the output from two successive snapshots.
Simple Network Management Protocol. Used in SNMP servers for SNMP notifications. The Configuration Change Console can be configured to generate notifications of change events through SNMP. The Agents can also monitor traps from any system that can send traps.
A configured person within the Configuration Change Console suite who has access to all configuration and visualization screens, as well as additional advanced administrative screens.
An administrator defined grouping of configured persons sharing similar responsibilities within the monitored environment.
An assignment of a Person to a Team. Team assignment is important for Team Device Limiting features.
A option within the Configuration Change Console that allows an administrator to prevent users from viewing information for devices they are not assigned through their defined team membership.
Used in the to define an percentage limit for items ranging from unauthorized events to database table space.
When reviewing change event data, the time period for the data set. The Configuration Change Console provides Yearly, Monthly, Weekly, Daily, Hourly, and 15 Minute, Last 7 days, Last 30 days Time scale options. Not all screens always have all scale options available.
An event that was not reconciled with a Change Management server because no audit action or category component assignment was configured.
An event that was reconciled with a Change Management Server, but no open ticket was found indicating this change should have happened.
The process of pushing a new monitoring configuration to one or more agents. If you change component definitions and many other configurations, you must perform an Update Agents action.
A user on a monitored device (OS user) or inside an application (Component Internal User). Users can be associated with a configured Person in the Configuration Change Console through person to user assignments.
|
 Copyright © 2003, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
