15.1 INSTALLING AN SPI
This section provides a summary of the general process for installation of the SPI. Complete documentation for each SPI is provided when you purchase or download the SPI. You also have the option of installing some SPIs during the installation of the management platform.15.1.1 Installation Summary
The summary gives the OVO system administrator a quick look at what it will take to implement your first SPI:- The OpenView Operations management server must be installed before installing an SPI.
- Install the SPI using the software installation program, swinstall. The source depot will be one of three sources: the OVO bundle, an application CD, or the file downloaded from the web site into a directory of your choice.
- Distribute the SPI software components to the managed (target) node. During the initial distribution SPI actions, monitors, and command components are transferred to the node.
- Configure the SPI components that are used to communicate with the target node. For example: the database configuration file is created and remains on the server. It contains the connect information required for the database instance on the target node.
- Assign and distribute the SPI templates onto the target node. Logfile and Monitor templates are pre-configured with the most common logfile messages strings and monitor metrics. The periodic execution of the collector/analyzer program "dbspicao" checks the oracle alert log or determines the value of a metric. The collector/analyzer program is part of the Oracle SPI. Examples of the types of entries in the alert log or metrics that are pre-configured include ORA-00018 max number of session exceeded and ORA-00206 error writing control file. You can customize the frequency of the check, thresholds, message text, actions, and so on. The complete instructions on customizing the templates and available metrics for each type of database are included with the SPI documentation.
|
لطفا منتظر باشید ...
