Open Architecture
The open architecture of the Enterprise Manager application is constructed from separate component modules and libraries to allow the greatest flexibility in configuration. This allows users to create their own component modules to read specific information formats and perform the actions that meet their requirements.
Each component of the diagram is described briefly to emphasis the power and flexibility of the system.
-
A management application is an application or system that Enterprise Manager is configured to monitor. It can be a server (e.g. Internet Information Server on Windows), a network management application such as HP OpenView, or a PC management application such as LANDesk Manager or a real world piece of equipment (e.g. air conditioning unit in a computer room).
-
A Scanner is the component that monitors changes in the application status (e.g. updates to a log file or changes in the contents of a database table) and passes the details of the change to Enterprise Manager.
-
A Decoder is the component that converts the new data received from the scanner into a format suitable for processing against the Policy Rules Base.
-
The Policy Rules Database is the compiled form of the rules set that Enterprise Manager uses to match events to actions. The rules base implements the users' knowledge and experience in managing and supporting the application or system.
-
Core of Enterprise Manager: This is the central part of Enterprise Manager that loads and controls all functions. It contains the rules and correlation engine that process each event, matches the events against the rules and initiates the specified actions.
- Script Files are used to manage the loading and operation of the Enterprise core and to store script instructions for managed devices that can be applied by the rules.
- Extensions are modules that perform specific functions invoked by the rules to provide the next action. Extensions can be written in any programming language.
- Rules Builder provides a graphical interface as the entry point for defining and constructing the Policy rules database. Rules are text based.
- Outputs and Actions can be many different types to many different systems.
<< Back
