This section lists and describes the components provided as part of PATROL and provides an overview of the products from other vendors that you can integrate with PATROL.
The following table lists all the components provided as part of PATROL:
PATROL components
Component | Purpose | Dependencies |
---|---|---|
PATROL Central Operator — Microsoft Windows Edition | Like other PATROL Consoles, PATROL Central Operator — Microsoft Windows Edition provides a window into your PATROL environment. PATROL Central Operator — Microsoft Windows Edition works with only the PATROL 7.x architecture; it does not work with the PATROL 3 architecture. |
|
PATROL Central Operator — Web Edition | PATROL Central Operator — Web Edition is a web-based application that provides a window into your PATROL environment. PATROL Central Operator — Web Edition works with only the PATROL 7.x architecture; it does not work with the PATROL 3 architecture. |
|
PATROL Console Server | The PATROL Console Server is used by PATROL 7.x Consoles to communicate with PATROL Agents on managed systems. A primary feature of PATROL monitoring is that you can create views and organize objects according to a specific business need. The PATROL Console Server provides persistency support for those views. In addition, persistent views are maintained in a common format so you can use the same view with multiple 7.x Consoles. |
|
PATROL Operator Console | The graphical work space from which you issue commands and manage the distributed environment monitored by PATROL. The PATROL Console displays all of the monitored computers and applications. With the PATROL Operator Console, you can perform the following tasks:
|
|
PATROL Developer Console | With the PATROL Developer Console, you can do everything you can do with the PATROL Operator Console, along with the following tasks:
|
|
PATROL Event Manager (PEM Console) | With the PEM Console, you can perform the following tasks:
|
|
PATROL Integration Products | Provides an interface between PATROL Agent and third-party enterprise management systems such as HP OpenView Network Node Manager. |
|
PATROL Agent | The core piece of the PATROL architecture that monitors and manages host computers. The PATROL Agent consists of Perform Agent executables (BDS_SDService.exe, which is registered as a service on Windows platforms, and bgscollect.exe ) and the PATROL Agent executable (patrolagent.exe ), which is registered as a service. On the OpenVMS platform, the Agent does not use the Perform Agent executables. The PATROL Agent performs the following tasks:
|
|
PATROL KM | A set of files from which a PATROL Agent receives information about all of the resources, such as databases and file systems, running on a monitored computer. PATROL KMs provide information to the PATROL Agent about the following tasks:
|
|
Agent Query | You can view information about monitored objects through Agent Query. Using this function, you can work with objects outside the PATROL Console window. Instead of viewing objects as icons, you view their names in a tabular format. Results of queries are displayed in the Query results window. You can save queries, then load and reissue them when needed. |
|
PATROL Script Language ( PSL) | Included as part of the PATROL Developer Console is the PATROL Script Language (PSL) that you can use to write parameters, commands, tasks, recovery actions, and discovery procedures for the PATROL Agents. PSL is a fourth-generation language that is both compiled and interpreted, which is similar to programming languages such as C++, C, and Perl. PSL is the native language of PATROL KMs. |
|
PSL Compiler | You can use the PSL Compiler to check the syntax of PSL and to build a PSL library. |
|
PSL Debugger | You can use the PSL Debugger to debug PSL scripts. |
|
PATROL Command-Line Interface | The PATROL Command-Line Interface (CLI) is a program for retrieving object and event information from a PATROL Agent. CLI is designed to connect to a PATROL Agent in instances when a GUI interface is unavailable or when the user is logged onto a host using a terminal emulator (without a TCP/IP stack). CLI has both interactive and non-interactive modes. You can start CLI from a command line and manually submit commands to the CLI. You can also call the CLI within a script and have it run commands that you provide on the command line or in additional CLI script files. |
|