BII4P

BMC Impact Integration for PATROL
Installation and Configuration Guide
Supporting
BMC Impact Integration for PATROL 7.1
June 2004
Contacting BMC Software

You can access the BMC Software Web site at http://www.bmc.com. From this Web site, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada

Address BMC Software, Inc. 2101 CityWest Blvd. Houston TX 77042-2827 713 918 8800 or 800 841 2031 713 918 8000
Outside United States and Canada

Telephone Fax (01) 713 918 8800 (01) 713 918 8000
Telephone Fax
Copyright 2004 BMC Software, Inc., as an unpublished work. All rights reserved. BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. IBM is a registered trademark of International Business Machines Corporation. All other trademarks belong to their respective companies. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation.
Restricted Rights Legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this address.
Customer Support
You can obtain technical support by using the Support page on the BMC Software Web site or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, please see Before Contacting BMC Software.
Support Web Site

You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this Web site, you can
s s s s s s s
read overviews about support services and programs that BMC Software offers find the most current information about BMC Software products search a database for problems similar to yours and possible solutions order or download product documentation report a problem or ask a question subscribe to receive e-mail notices when new product versions are released find worldwide BMC Software support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers
Support by Telephone or E-mail

In the United States and Canada, if you need technical support and do not have access to the Web, call 800 537 1813. Outside the United States and Canada, please contact your local support center for assistance. To find telephone and e-mail contact information for the BMC Software support center that services your location, refer to the Contact Customer Support section of the Support page on the BMC Software Web site at http://www.bmc.com/support_home.
Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Support can begin working on your problem immediately:
s
product information product name product version (release number) license number and password (trial or permanent)
operating system and environment information machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level
s s s
sequence of events leading to the problem commands and options that you used messages received (and the time and date that you received them) product error messages messages from the operating system, such as file system full messages from related software
BMC Impact Integration for PATROL 7.1 User Guide
Contents
Chapter 1 Introduction to BMC Impact Integration for PATROL 11 12 12 12 13 14 16 17 18 18 19 19 20 20 23 24 26 26 31 31 32 33 34 37 38 38 38 39 40 41 44 44 48 49 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC II for PATROL Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Events and BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Components Included with BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2 Planning
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite Products and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Location Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Planning Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3 Installation
Getting Started Quickly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Installing BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing BMC II for PATROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the CC_HOME Variable Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Completing the Installation on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Files Installed with BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 4 Configuration
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Common Connect Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Custom Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining a Management Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Events That are Suppressed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the Client Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Event Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring and Using Startup Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Updating the mcell.dir file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Updating Knowledge Base Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Chapter 5 Startup and Validation 59
Command Line Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Starting BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Stopping BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Validating Correct Functioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Monitoring Event Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Monitoring PATROL Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Chapter 6 Event Handling 67
About PATROL 7 Event Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Additional Information for the PATROL KM for Event Management . . . . . . . . . 70 Event Class Slots Inherited from the BMC IM Event Class . . . . . . . . . . . . . . . . . . . 71 BMC II for PATROL Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Event Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Chapter 7 Troubleshooting 75
Console Server Authentication Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 imServer Does Not Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 BII4Patrol Terminated at Startup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Console Server Not Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Cannot Access the Management Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Unable to Start BMC II for PATROL as a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Installation Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Missing Cell Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Appendix A Configuration File Parameters Appendix B BMC IM Rules for PATROL Events 81 89
BMC IM Rules for PATROL Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 PATROL Alarms and BMC IM Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 PATROL State Changes and BMC IM Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 PATROL Recovery Actions and BMC IM Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 PATROL Agent Status and BMC IM Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 PATROL Duplicate Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Event Processing and the PATROL KM for Event Management . . . . . . . . . . . . . . 92 Glossary Index 95 111
Figures
Example of Event Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Configuration File Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Event Catalog Definition Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Example bii4p_start.opts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Example mcell.dir Scenario 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Example mcell.dir Scenario 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Example mcell.dir Scenario 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 BMC IM Definition Format for a Remote BMC II for PATROL Instance . . . . . . . . . . 54
Figures
Tables
Required Software and Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC II for PATROL Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Common Connect Configuration Utility Supported Platforms . . . . . . . . . . . . . . . . . . Installation Steps by Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Essential Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Tasks When BMC II for PATROL is Installed with BMC IM . . . . . . . Configuration Tasks When BMC II for PATROL is Separate from BMC IM . . . . . . . Startup Options Defined in bii4p_start.opts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation Variable Locations and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . Command Line Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC IM Event Class Slots for PATROL 7 Managed Systems . . . . . . . . . . . . . . . . . . . Event Status Enumeration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Severity Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Event Management Slots in the PATROL_EV Event Class . . . . . . . BMC IM Slots Inherited by the BMC II for PATROL Event Class . . . . . . . . . . . . . . . . Events Generated by BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . bii4p.conf File parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 19 19 28 33 39 41 50 57 60 68 69 69 70 71 73 82
Tables
10
Chapter
1
12 12 12 13 14 16
Introduction to BMC Impact Integration for PATROL

1
This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC II for PATROL Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Events and BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Components Included with BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1 Introduction to BMC Impact Integration for PATROL
11
Overview
Overview
BMC Impact Integration for PATROL (BMC II for PATROL) transfers event information generated from PATROL Agents to a BMC Impact Manager (BMC IM), where the event information is processed by the event processing engine, called a cell, that resides within the BMC IM instance. The destination for event information from BMC II for PATROL is a BMC Impact Manager cell. BMC II for PATROL uses persistent buffering so that no information is lost, either in obtaining event information from PATROL Agents or in sending the filtered and adapted event information to a cell. BMC II for PATROL works with the following components:
s s s s
BMC Impact Manager (BMC IM) PATROL Agents running any PATROL Knowledge Module PATROL Console Server and RTserver Management Profile (through the Common Connect configuration utility)
BMC II for PATROL Architecture

This section presents a view of the architectural model and an example of data flow in an environment. Figure 1 on page 13 summarizes the functional architecture of BMC II for PATROL.
Events and BMC II for PATROL

With persistent buffering, you can display event information from a PATROL product in the BMC Impact Explorer (BMC IX) without losing any information in the transfer process. BMC II for PATROL integrates the event monitoring and reporting features of PATROL with the flexible event processing technology of BMC IM. PATROL Agents and their associated Knowledge Modules (KMs) store event information. The BMC II for PATROL component subscribes to the PATROL Agents for event information. BMC II for PATROL then filters the event information to determine what should be propagated to a BMC IM. BMC II for PATROL translates the event information to one event class, PATROL_EV, that contains slots to which the
12
incoming event information is assigned. BMC II for PATROL adapts the filtered event information into the Basic Recorder of Objects in C (BAROC) language, the only language understood by the cell, before propagating it to the BMC IM cell to which it is connected.
Example Environment
The following diagram illustrates how event information flows from PATROL Agents to BMC IX consoles in an environment using BMC II for PATROL. Figure 1 Example of Event Flow
1. Events are received by PATROL Agents through PATROL Knowledge Modules 2. Events are communicated through the PATROL Console Server using Common Connect components 3. Events are passed to the BMC Impact Manager through BMC II for PATROL. 4. Events can be viewed with BMC Impact Explorer.
Chapter 1 Introduction to BMC Impact Integration for PATROL
13
Components Included with BMC II for PATROL

The following components are included with BMC II for PATROL.
s s s s s
BMC Impact Integration for PATROL executable Common Connect configuration utility Common Connect Back End Client Runtime Configuration and setup files
BMC II for PATROL Executable

BMC II for PATROL contains the BMC Impact Integration for PATROL executable, BII4Patrol. The executable launches BMC II for PATROL. BMC II for PATROL uses three files in the BMC IM cells default knowledge base: bii4p.mrl, bii4p_collectors.mrl, and bii4p.baroc. The bii4p.mrl file is a BMC IM rule file. It contains a set of rules that are used to manage the flow of PATROL events. The primary purposes of these rules are to:
s s
close alarm events when the alarm has been cancelled in PATROL update or create alarms with enhanced information from PATROL KM for Event Management sources automatically drop duplicate events
The bii4p_collectors.mrl is a rule file for creating collectors. Collectors are required for displaying the event information obtained from PATROL Agents, adapted and sent to a BMC IM, in a BMC IX console. All files with a .baroc extension are files that contain event class definitions and the slot definitions for each class. Such files also reside in the cells Knowledge Base (KB). The bii4p.baroc file contains the PATROL_EV event class and the slot definitions that are used in adapting event information obtained from a PATROL Agent source into the format that a cell can understand and process.
Common Connect Configuration Utility

The Common Connect configuration utility is a required component. It is an independent utility that is designed to configure, but not monitor, PATROL Integration and Common Connect products. You can install it on any supported Solaris or Microsoft Windows system.
14
Common Connect Back End

The Common Connect Back End extends the functionality of the PATROL Console Server to enable connections with the integration components. The Common Connect configuration utility must be connected to a PATROL Console Server with the Common Connect Back End installed.
Client Runtime
The Client Runtime component is required on systems that do not have the PATROL Console Server. After you install the Client Runtime component, the following subdirectories are created under the installation directory:
s s s s s
common Common_Connect Install itools Uninstall
Managed System
In the PATROL environment, any computer system that is linked to the RTserver cloud and included in the management profile is referred to as a managed system. A managed system includes any computer on which a PATROL Agent is installed.
Management Profile
The management profile is a user-defined view of PATROL and Common Connect objects and contains the managed systems, KM packages, and specified event filters that you are currently monitoring. BMC II for PATROL uses the information in the management profile to monitor the specified computer systems and to receive and send event data from them. You use the Common Connect configuration utility to create and edit the management profile that the BMC II for PATROL product requires. The utility allows you to create management profiles that include PATROL Agent managed systems, to load PATROL KMs, and to specify event filters.
Client Configuration File (optional)

The client configuration file informs the PATROL Console Server of keyword and event attribute values for BMC II for PATROL. If you want to use settings other than the default settings for event suppression, you can create a new configuration file using the Common Connect configuration utility.
Chapter 1 Introduction to BMC Impact Integration for PATROL 15
Related Documentation
Related Documentation
For additional information about BMC II for PATROL, see the BMC Impact Integration for PATROL Release Notes. For additional information about PATROL, see the following documentation:
s s s s s s
PATROL Console Server and RTserver Technical Bulletin, Version 7.2.36 PATROL Security User Guide PATROL Knowledge Module for Event Management User Guide PATROL for Microsoft Windows Servers Release Notes, Version 3.0.03 PATROL KM for Event Management online Help PATROL Agent Reference Manual
For additional information about BMC Impact Solutions products, see the following documentation:
s s s s s
s s s s s s s s
BMC Impact Manager Installation Guide BMC Impact Manager System Configuration and Maintenance Guide BMC Impact Event Adapters Installation and Configuration Guide BMC Impact Integration for Remedy AR System Installation and Configuration Guide BMC Impact Integration for PATROL Enterprise Manager Installation and Configuration Guide BMC Impact Event Management Guide BMC Impact Manager Knowledge Base Reference Guide Building a Service Model BMC Impact Explorer User Guide BMC Impact Integration Developers Kit Web Services Developer Guide BMC Impact Integration Developers Kit Web Services API Reference Guide BMC Impact Integration Developers Kit Basic C APIs Developer Guide BMC Impact Integration Developers Kit C APIs Reference Guide
To view the complete BMC documentation library, visit the support page on the BMC Software Web site at http://www.bmc.com/support.html. Log on and select a product to access the related documentation. (To log on if you are a first-time user and have purchased a product, you can request a permanent user name and password by registering at the Customer Support page. To log on if you are a firsttime user and have not purchased a product, you can request a temporary user name and password from your BMC Software sales representative.) The complete BMC Impact Solutions documentation library is available on the BMC Impact Solutions Documentation CD that is included with major releases of the BMC Impact Manager.
16
Chapter
2
18 18 19 19 20 20
Planning
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite Products and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Location Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Planning Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2
Planning
17
Overview
Overview
This chapter provides information about the requirements and computing environment conditions that you should consider as you plan to install BMC II for PATROL. In addition to the detailed information, this chapter includes a worksheet that you can use for planning the installation at your site.
Prerequisite Products and Components

Table 1 lists the products and components that must be installed, configured, and running in the computing environment before you install BMC II for PATROL. Table 1 Required Software and Versions Software BMC Impact Manager PATROL Console Server on either a Microsoft Windows or Solaris system
Version version 3.2 or higher version 7.2.36.02 or higher
SmartSockets RTserver on either a Microsoft version 6.2 or higher Windows or Solaris system The RTserver can be installed under any account. PATROL Agent version 3.5.x or higher The PATROL Agent must be installed and running on each PATROL managed system that you want to monitor.
s s
Web browser
Microsoft Internet Explorer 5.0, 5.5, or 6.x Netscape Navigator 4.7.5 - 4.7.8
BMC II for PATROL is installed using the PATROL common installation utility. The installation utility requires a web browser.
18
Overview
Operating System Requirements

BMC II for PATROL supports the platforms listed in Table 2. Table 2 AIX Solaris HP-UX Linux Red Hat Microsoft Windows 2000 Microsoft Windows 2000 Microsoft Windows XP Microsoft Windows 2003 BMC II for PATROL Supported Platforms Version 5.1 2.8, 2.9 11.0, 11.i 7.3 Server Professional Professional Server Memory 0.5 GB 0.5 GB 0.5 GB 0.5 GB 0.5 GB 0.5 GB 0.5 GB 0.5 GB
Operating System
The Common Connect configuration utility supports the platforms listed in Table 3. Table 3 Solaris Microsoft Windows 2000 Microsoft Windows 2000 Microsoft Windows XP Microsoft Windows 2003 Common Connect Configuration Utility Supported Platforms Version 2.8, 2.9 Server Professional Professional Server Memory 0.5 GB 0.5 GB 0.5 GB 0.5 GB 0.5 GB
Operating System
Security Requirements
BMC II for PATROL, the PATROL Agent, the PATROL Console Server, and the Client Runtime component must operate at the same security level to communicate with each other. Check the security level of previously installed components and be sure to install BMC II for PATROL components at the same level. Refer to the PATROL Security User Guide for information about checking security levels and for setting up security in a PATROL environment.
NOTE
If you do not specify a security level during the installation of BMC II for PATROL, the product components will use security level 0.
Chapter 2
Planning
19
Installation Location Variables
Installation Location Variables

During the installation process, the Installation Utility records where it installs the PATROL and BMC IM components in environment variables. Various components of BMC II for PATROL require the information stored in these variables to function properly. Two important variables are MCELL_HOME and CC_HOME. Throughout this book, all references to MCELL_HOME are represented as %MCELL_HOME% in a Windows environment and $MCELL_HOME in a Unix environment. All references to CC_HOME are represented as %CC_HOME% in a Windows environment and $CC_HOME in a Unix environment.
Installation Planning Worksheet

Use the worksheet in this section to record information that you will need to provide during installation and configuration processes. Information Item or Requirement Where is the mcell.dir file saved? The default location of the mcell.dir file is the MCELL_HOME/etc directory. The directory is usually found in one of the following locations: Microsoft Windows
c:\Program Files\BMC Software\Mastercell\server
Response
Notes
About the BMC II for PATROL component
Unix
opt/mcell
20
Information Item or Requirement Does your computer have Common Connect components installed? If you have previously installed Common Connect components, the CC_HOME variable is set to
Installation Directory/Common_Connect.
Response
Notes
If you are installing Common Connect components for the first time, the CC_HOME variable will be set to
Installation Directory/Common_Connect
during the installation. Ensure that you install the Common Connect components that are appropriate for any other BMC Software products and components on that computer. See Verifying the CC_HOME Variable Setting on page 31. Which operating system is running on that computer? See Operating System Requirements on page 19. Do you plan to install BMC II for PATROL on a Unix system? If so, you must provide the root account login and password for that system during installation. What is the name of the BMC IM that you want to connect to? What is the name of the host on which the BMC IM is running? About the PATROL Console Server What is the default PATROL Console Server ID? See Table 8 on page 50.
Chapter 2
Planning
21
Information Item or Requirement Which operating system is running on that computer? See Table 2 on page 19. Is the Common Connect Back End installed on that computer (must reside on the same machine with the PATROL Console Server)? What account did you use when you installed the PATROL Console Server? If you are installing BMC II for PATROL on a Unix computer, what is the root account and password? What security level are you using with the PATROL Console Server? If you used a security levels higher than 0, you must perform a custom installation in order to use the same security level. Reminder: BMC II for PATROL, the PATROL Agent, the PATROL Console Server, and the Client Runtime component must operate at the same security level. About the RTserver What is the hostname of the computer on which the RTserver is installed and what is the port number through which it connects? See Table 8 on page 50.
Response
Notes
About PATROL Agents and Event Sources What are the names of the PATROL Agents from which you want to receive events? See Defining a Management Profile on page 41 of the Configuration chapter.
22
Chapter
3
24 26 26 31 31 32 33 34
Installation
This chapter presents the following topics: Getting Started Quickly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Installing BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing BMC II for PATROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the CC_HOME Variable Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Completing the Installation on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Files Installed with BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 3
Installation
23
Getting Started Quickly

This section contains a high-level overview of the steps involved in installing and configuring BMC II for PATROL. Use these steps if you are an experienced user, all other elements (BMC Impact Manager and PATROL) are already installed, the BMC Impact Manager and BMC II for PATROL will be installed on the same server, and you are installing and configuring to a local cell. 1. From the downloaded image, run the setup program. 2. In the Welcome to the Installation Utility, click Next. 3. Review the license agreement, select Accept, and click Next. 4. In the Select Installation Option window, accept the default selection and click Next. 5. In the Select Type of Installation window, select Typical and click Next. 6. In the Specify Installation Directory window, verify that the installation directory is correct and click Next. 7. In the Select System Roles window, verify that the selected roles are correct and click Next. 8. In the Select Products and Components to Install window, select the desired options and click Next. 9. If the Runtime Warning window is displayed, click Next.
NOTE
This warning is displayed if you have a Console Server already installed on the host. Do not install the Client Runtime component if you have the Console Server installed.
10. (Unix only) If the Provide the System Root Account Properties window is displayed, enter the Root login name and password and click Next. 11. If the Enter the Default Client Login and Password window is displayed, enter the login name that is used for the PATROL Console Server. 12. Enter and confirm the password for the login name and click Next. 13. In the Impact Integration Configuration Properties window, enter values for the Enter MCELL_HOME directory, Impact Manager Name, PATROL Console Server ID, and RTServer identify fields and click Next.
24
14. If the RTSERVERS Variable Properties window is displayed, click Next. 15. In the Review Selections and Install window, verify the product and component selections and click Start Install. 16. When the status window reports that the installation is 100% complete, click Next. Then click Finish to close the installation utility, and click Yes in the two Close Window dialog boxes. 17. (Windows only) Restart the host. 18. Create the management profile. 19. Update the bii4p_start.opts file to add the -mprofile value. 20. Verify that the mcell.dir file is correct. Now you are ready to run BMC II for PATROL.
Chapter 3
Installation
25
Overview of Installing BMC II for PATROL
Overview of Installing BMC II for PATROL

BMC II for PATROL is installed by the common installation utility on Windows platforms and Unix platforms. The installation requires you to
s s s
s s s
Specify the installation directory Choose the BMC II for PATROL components that you want to install Enter the default login and password used by BMC II for PATROL, which may be the same login and password used by the PATROL Console Server Specify the root password on Unix machines Configure security settings Perform post-installation file configuration
Installing BMC II for PATROL

You can install BMC II for PATROL using either the Typical or Custom installation type. Regardless of the type of installation you choose, you must repeat this installation process for each computer or virtual server on which you want to install BMC II for PATROL.
Before You Begin

s
Review the installation checklist on page 20. Stop the PATROL Console Server.
NOTE
You must stop the PATROL Console Server before beginning the installation of Common Connect Backend or the installation will fail. Restart the PATROL Console Server when the installation is complete. Close the Common Connect utility if it is open. Set the MCELL_HOME variable before installing on Unix.
26
To Launch the Common Installer 1 From the installation image that has been electronically downloaded and
extracted, or from the product CD, select one of the following options to start the installation utility:
s
(Windows) Run setup.exe. (Unix) Run ./setup.sh. (Unix without a browser) Perform the following steps to launch the installation utility: A. From a command line, change to the directory where the installation utility is located and enter the following command to start the installation Web server:
./setup.sh -serveronly
A message box is displayed that shows the URL to use to connect to the installation Web server. B. On another computer with a browser, start the browser. C. Connect to the installation Web server from the browser to start the installation utility by using the URL that is displayed in the message box on the computer on which you are installing the product.
2 In the Welcome to the Installation Utility window, click Next to begin your
installation.
3 Review the license agreement, select Accept and click Next to continue. To Complete the Windows in the Common Installer
Use Table 4 to help you complete the installation of BMC II for PATROL and Common Connect components. Depending on the installation type and options you select, you may not see all of the listed windows, and you may not see them in the same order listed here. Click Next when you complete your entries and selections on a window.
Chapter 3
Installation
27
Table 4 Window
Installation Steps by Window (Part 1 of 3) Enter or Select Select the I want to install products on this computer now option and click
Next.
Select Installation Option Select Type of Installation
Perform one of the following actions:

s
Select Typical if you want to keep the default security settings. Select Custom if you want to configure the security settings when the Client Runtime option is selected.
Specify Installation Directory
Perform the action that is appropriate for the products or components that you are installing:
s
To install the Common Connect Back End, install on systems which contain the PATROL Console Server. Enter the directory under which the existing PATROL Console Server is installed, if it is not displayed. To install the Common Connect configuration utility, install on Windows or Solaris systems which contain the Console Server or the Client Runtime libraries. Enter the directory in which you want to install the utility or accept the default location. To install the BMC Impact Integration for PATROL, install on systems which contain Console Server or the Client Runtime libraries. Enter the directory in which you want to install the product or accept the default location. To install the Client Runtime (Common Files), install on systems which do not contain the PATROL Console Server. Enter the directory in which you want to install the product or accept the default location. Remember that if the target system is the PATROL Console Server, do not install the Client Runtime.
Note: For first-time installations of the Client Runtime, the default installation directory is C:\Program Files\BMC Software on Microsoft Windows and /opt/bmc on Unix.
The installation process adds new subdirectories below the specified installation directory.
28
Table 4 Window
Installation Steps by Window (Part 2 of 3) Enter or Select

s
Select System Roles
Select Common Services if you are only installing Common Connect components on the same system where the PATROL Console Server is installed. Select Integration Clients if you are only installing BMC II for PATROL or the Client Runtime on a system which does not have the PATROL Console Server. Select both Common Services and Integration Clients if you want to install BMC II for PATROL and Common Connect components on a system that has the PATROL Console Server.
Select Products and Components to Install
Perform the action that is appropriate for the products or components that you are installing:
s
To install the Client Runtime (Common Files) on systems which do not contain the PATROL Console Server, expand Client Runtime Components and select Client Runtime (Common Files). A warning dialog box is displayed, describing when you should or should not install the Client Runtime component. Review the warning and then click Next to continue. To install the Common Connect Back End on systems which contain the PATROL Console Server, expand Common Connect and select
Common Connect Back End. Expand Common Connect Back End and select BMC Impact Integration Client Definitions (MOF). Click Next to continue.
To install the Configuration Utility on systems which contain either the PATROL Console Server or Client Runtime, expand Common Connect and select Configuration Utility - Java Edition. Click Next to continue. To install BMC II for PATROL on any supported platform, expand Integration Clients and select BMC Impact Integration for PATROL. Click Next to continue.
Runtime Warning Box
Verify that you want to install the Client Runtime component on the host. If you do not, click Back to return to the previous window and deselect this option.
Select Level of Security Select a level of security based on information in the PATROL Security User Guide. Indicate whether you are overwriting the current security configurations, and then click Next.
Chapter 3
Installation
29
Table 4 Window
Installation Steps by Window (Part 3 of 3) Enter or Select Perform the following actions:
s
Provide the System Root Account Properties
In the Root Login Name field, enter root. In the Root Login Password field, enter the root password. In the Re-enter the Root Login Password field, enter the root password again to confirm it.
Click Next to continue. Enter the Default Client Enter the following logon and password information: Login and Password s In the Default Client Login field, enter the login name that is used for the PATROL Console Server. Do not enter the domain name.
s
In the Default Client Password and the Re-enter the Default Client Password fields, enter the password that corresponds with the login name for the PATROL Console Server.
Click Next to continue. Impact Integration Configuration Properties Either accept the default information, or enter the following Impact Manager information:
s
In the %MCELL_HOME% field, enter the path to the Impact Manager Home directory. If the server does not contain an Impact Manager, enter the path used for Common_Connect. In the Impact Manager Name field, enter the name of the Impact Manager to which you will connect.
Note: If the Impact Manager name you enter does not exist, your
installation will finish, but the Impact Manager knowledgebase file will not be updated.
s
In the PATROL Console Server ID field, enter the ID of the Console Server. In the RTServer identify field, enter the the RTServer name and port.
Click Next to continue. RTSERVERS Variable Properties window Click Next.
30
Post-Installation Instructions
To Complete the Installation of the Products and Components 1 In the Review Selections and Install window, verify the product and component
selections.
2 Click Start Install. 3 When the installation is complete, click Next. 4 You can view the installation log file or click Finish to exit the installation utility. TIP
When the installation is finished, record the location of the log file that is displayed in case you need to troubleshoot an installation issue.
5 Restart the PATROL Console Server. 6 (Windows only) Restart the host.
After you install BMC II for PATROL, complete the following sections, if applicable for your environment.
s s
Verifying the CC_HOME Variable Setting on page 31 Completing the Installation on Unix on page 32
Verifying the CC_HOME Variable Setting

The Common Connect home environment variable (CC_HOME) must be set on any Unix system on which a Common Connect client, such as BMC II for PATROL, or the configuration utility, is installed to ensure that Common Connect clients can communicate with other components in the environment.
CC_HOME Environment Variable Setting

In this task, you verify that the setting of the CC_HOME environment variable points to the Common_Connect subdirectory under the installation directory.
Chapter 3
Installation
31
The CC_HOME variable should be defined as a system variable, and it must be set to Installation_directory\Common_Connect.
To Check the CC_HOME Setting on a Unix System 1 At a command prompt, enter echo CC_HOME and press Enter. 2 Verify that the CC_HOME variable is defined as
Installation_directory/Common_Connect.
If the CC_HOME variable is not defined as Installation_directory/Common_Connect, continue to To Set the CC_HOME Variable on Unix on page 32.
To Set the CC_HOME Variable on Unix

Based on your shell script, enter one of the following commands and press Enter.
s
CC_HOME = Installation_directory/Common_Connect; export CC_HOME setenv CC_HOME Installation_directory/Common_Connect
To Set the CC_HOME Variable on Windows 1 Open the Control Panel and double-click on the System icon. 2 On the System Properties dialog box, click on the Advanced tab. 3 Click Environment Variables. 4 On the Environment Variables dialog box, click New in the System variables box. 5 On the New System Variable dialog box, enter the variable name and value and
click OK.
6 Click OK to close the Environment Variables dialog box. 7 Click OK to close the System Properties dialog box. 8 Restart the server.
Completing the Installation on Unix

If you are installing BMC II for PATROL on Unix, use the instructions in this section.
32 BMC Impact Integration for PATROL 7.1 User Guide
Files Installed with BMC II for PATROL
To Complete the Installation on Unix 1 Navigate to the installationDirectory/common/bmc directory. 2 Depending on the shell you are using, enter one of the following commands:
s s
C shell: run source ./patrol7rc.csh Bourne shell: run . ./patrol7rc.sh
The applicable variable is reset:

s s s
(AIX) LIBPATH (Solaris and Linux) LD_LIBRARY_PATH (HP-UX) SHLIB_PATH
Files Installed with BMC II for PATROL

Table 5 contains the names and functions of essential BMC II for PATROL files. Table 5 File Name
BII4Patrol bii4p.conf bii4p.map bmciiapi (Windows) libiiapi (Unix) bii4p_strings.cat bii4p.trace bii4p.mrl, bii4p_collectors.mrl, bii4p.baroc
Essential Files Function the BMC II for PATROL executable contains trace parameters, buffer management parameters, and the BMC IM directory contains the mapping information to translate PATROL LEM events to BMC IM events library files for the BMC II for PATROL API catalog files for BMC II for PATROL sets the level of trace messages and configures the trace level BMC IM Knowledge Base (KB) files
cc_be library cc_be catalog (cc_strings.cat,

cc_be_t.dll.sgn)
Common Connect Back End library files Common Connect Back End catalog files
Chapter 3
Installation
33
Uninstalling BMC II for PATROL

The uninstallation process uses the installation utility in uninstall mode. The utility lists the BMC Software products and components in a tree view that allows you to select the ones that you want to uninstall. You may have to manually remove folders, directories, and files that remain after the automated uninstallation is complete.
To Uninstall from a Microsoft Windows System 1 Log on with an account that has administrative privileges. 2 If you are running BMC II for PATROL as a service, enter BII4Patrol -remove at a
command line prompt.
3 From the Microsoft Windows desktop, choose Start => Settings => Control Panel to
open the Control Panel window.
4 Double-click the Add/Remove Programs icon to open the Add/Remove Programs

window.
5 From the list of available programs, select BMC Software Tools and click
Change/Remove.
The web browser is launched.
6 Click Next to navigate the windows until you reach the Select Products and
Components to Uninstall window.
7 Choose the components to uninstall and click Next. 8 In the Review Selections and Uninstall window, click Start Uninstall. 9 When the uninstallation is complete, click Next. 10 You can view the log file or click Finish to exit the utility. TIP
Record the location of the log file in case you need to troubleshoot an uninstallation issue.
34
To Uninstall from a Unix System 1 Log in under the account that you used to install the components. 2 In a terminal window, change directory to the Uninstall subdirectory, which is
found under your installation directory.
3 Enter ./uninstall.sh and press Enter.

The Common Install installation program is launched.
4 Click Next to navigate the windows until you reach the Select Products and
Components to Uninstall window.
5 Choose the components to uninstall and click Next. 6 In the Review Selections and Uninstall window, click Start Uninstall. 7 When the uninstallation is complete, click Next. 8 You can view the log file or click Finish to exit the utility. TIP
Record the location of the log file in case you need to troubleshoot an uninstallation issue.
Chapter 3
Installation
35
36
Chapter
4
38 38 38 39 40 41 44 44 48 49 52 55 57
Configuration
This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Common Connect Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Custom Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining a Management Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Events That are Suppressed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the Client Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Event Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring and Using Startup Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating the mcell.dir file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Knowledge Base Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 4 Configuration
37
Overview
Overview
The following diagram shows the relationships between the management profile, the PATROL Console Server, and BMC II for PATROL. Figure 2 Configuration File Relationships
1. The user defines PATROL managed systems, PATROL KMs, and event filters in the management profile through the Common Connect configuration utility. 2. This file may optionally be modified to allow or prevent the passage of certain events. 3. BMC II for PATROL connects to the PATROL Console Server. 4. The PATROL Console Server uses information from the management profile to connect to managed systems (PATROL Agents). 5. Events from the PATROL Agent are sent to the PATROL Console Server 6. The PATROL Console Server forwards events to BMC II for PATROL.
Common Connect Configuration Utility

The Common Connect configuration utility connects to an RTserver and a PATROL Console Server and lets you share information among the BMC IM, PATROL Agent managed systems, and third party (or non-PATROL) systems. You launch and use the Common Connect configuration utility independently of BMC II for PATROL.
Configuring BMC II for PATROL

This section contains information about the auto-configuration process, a configuration checklist, information about starting the Common Connect configuration utility, and procedures to configure the client configuration file and management profile.
38 BMC Impact Integration for PATROL 7.1 User Guide
Default Configuration
Table 6 contains a checklist that summarizes the configuration procedures which you need to complete to configure BMC II for PATROL when it is installed on the same system as BMC IM. This type of configuration is referred to as a default configuration. During installation, you entered information that the auto-configuration process uses to set the default configuration for running BMC II for PATROL. The default configuration includes
s s s s
updating the bii4p.conf file updating the mcell.dir file updating the bii4p_start.opts file updating the knowledge base (KB) for the local default cell
If you use the default configuration, you need to complete the following tasks:
s s
create a management profile (see page 41). update the bii4p_start.opts file (see page 49).
Use this checklist to preview the tasks to complete and to verify their completion. Table 6 Setup Configuration Tasks When BMC II for PATROL is Installed with BMC IM Task
System A
See
containing BMC II for PATROL and BMC IM(s)

s
Create a management profile Configure startup options in bii4p_start.opts. (optional) Update the bii4p.conf file. (optional) Update the mcell.dir files (optional) Update the BMC IM Knowledge Base files.
Defining a Management Profile on page 41 Configuring and Using Startup Options on page 49 Configuration Files on page 57 Updating the mcell.dir file on page 52 Updating Knowledge Base Files on page 55
39
Custom Configuration
Table 7 contains a checklist that summarizes the configuration procedures which you need to complete to configure BMC II for PATROL when it is installed on a different system from the BMC IM. This type of configuration is referred to as a custom configuration. In a custom configuration, you can overwrite the default configuration entries you made during installation by editing some settings to complete the installation. These changes include
s
creating a management profile and editing the bii4p_start.opts file to add the management profile name as the -mprofile value. updating the mcell.dir file on both the host IM is running and the host BMC II for PATROL is running (see Updating the mcell.dir file on page 52) updating the CC_HOME/etc/bii4p_start.opts file to define the following values: -cell -cserver -rtserver updating the knowledge base (KB) for the default cell copy the bii4p.baroc, bii4p_collectors.mrl, and bii4p.mrl files to the appropriate locations update the .load files under the classes, collectors, and rules directories to add an entry for bii4p and comment out mcxp recompile the KBs
40
Table 7 Setup
Configuration Tasks When BMC II for PATROL is Separate from BMC IM Tasks
System A
See
containing BMC II for PATROL

s
Create a management profile Configure startup options in bii4p_start.opts. (optional) Update the bii4p.conf file. Update the mcell.dir file.
Defining a Management Profile on page 41 Configuring and Using Startup Options on page 49 Configuration Files on page 57 Updating the mcell.dir file on page 52
System B
containing one or more BMC IM(s)

s
Update the mcell.dir file.
Updating the mcell.dir file on page 52 Updating Knowledge Base Files on page 55
Update the BMC IM Knowledge Base files
Defining a Management Profile

This section contains information about how to define a management profile. For additional details about defining a management profile, see the Common Connect configuration utility online Help.
Starting the Common Connect Configuration Utility

To define a management profile, you must use the Common Connect configuration utility.
41
To Start the Common Connect Configuration Utility

s
In Microsoft Windows, you can launch the utility from Microsoft Windows Explorer or from the command line at an MS-DOS command prompt. In Microsoft Windows Explorer, go to the CC_HOME\bin\Windows-x86 directory, and double-click configstart.bat. At the MS-DOS command prompt window, change directory to CC_HOME\bin\Windows-x86, enter configstart.bat, and then press Enter.
For Solaris, change directory to CC_HOME/bin/platform_operating_system, and locate the configstart.sh file. From the specified path, enter ./configstart.sh and press Enter.
To Define a Management Profile 1 In the configuration utility, choose the File => Connect menu command to open the
Configuration Wizard.
2 Click Next.
The Connect to RTservers window is displayed.
3 Select the appropriate RTserver from the list or enter a new one, and click Next.
The Select Common Connect Service window is displayed.
NOTE
The PATROL Console Server (with Common Connect Back End) is referred to as the Common Connect Service on this wizard window.
4 In Service Name, select the name of the PATROL Console Server and click Next.
The Provide User Credentials window is displayed.
5 Perform the following actions to specify the account under which you installed the
PATROL Console Server: A. In the User Name field, enter the user name for the PATROL Console Server. B. In the Password field, enter the password used by the PATROL Console Server. C. Click Next.
42
The Select Configuration window is displayed.
WARNING
If you enter an incorrect user name or password, the configuration utility hangs, and you must restart it.
6 Select Open/Create Management Profile and click Next.

The Open/Create Management Profile window is displayed.
7 Enter a name for the new management profile or select one from the list, and click
Next.
The Configuration Change Complete window is displayed.
8 Click Finish.
Continue to To Add Managed Systems to the Management Profile.
To Add Managed Systems to the Management Profile 1 In the Common Configuration utility, right-click Managed PATROL Systems. 2 Choose the Add New menu command.
The Managed PATROL System Discovery window is displayed, showing managed PATROL systems residing in the same RTserver cloud.
3 Select the managed PATROL systems you want to monitor and click Next.
The Add Managed Systems Wizard Complete window is displayed.
4 Click Finish.
Continue to To Add PATROL Knowledge Modules to the Management Profile.
To Add PATROL Knowledge Modules to the Management Profile 1 In the Common Connect configuration utility, right-click either Managed PATROL
Systems or the managed PATROL system you want to add PATROL KMs to.
2 Choose the Load KMs menu command.

The KM Packages dialog box is displayed.
43
3 Select the PATROL KMs and KM packages that you want to load and click Next.
The Load KM Packages Wizard Complete dialog box is displayed.
4 Click Finish.
Proceed to Setting Event Filtering on page 48. For additional instructions on defining a management profile, refer to the Common Connect configuration utility online Help. You can also use the Common Connect configuration utility online Help for additional instructions on adding PATROL managed systems and Knowledge Modules.
PATROL Events That are Suppressed

The following PATROL events are filtered by default and are not forwarded to the BMC IM (cell): PATROL Event Diag Disconnect RegApp Unload UpdAppState UpdInstState UpdMachineState WorstApp Description Backward compatibility with v2.0 and v3.0 diagnosis Event is triggered when the console disconnects Application is registered and managed by the agent Event is triggered when the application is unloaded from the agent New or updated application state New or updated instance state New or updated state for the entire agent Application has the worst state of all applications in the agent
To activate these events, you must reconfigure the Common Connect client configuration file. See Modifying the Client Configuration File on page 44. For more information about PATROL standard event classes, see the PATROL Agent Reference Manual.
Modifying the Client Configuration File

This section contains the procedure to modify the client configuration file using the Common Connect configuration utility.
44
This procedure is not required. Modify the client configuration file only if you want to activate or suppress events.
WARNING
You must use the Common Connect configuration utility to define, edit, and save a client configuration file. Do not attempt to edit a configuration file through a text editor.
Activating Suppressed Events

By default, the following events are suppressed, but may be activated in the Edit Client Attributes tab in the Common Connect configuration utility:
s s s s s s s s
Diag Disconnect RegApp Unload UpdMachineState UpdAppState UpdInstState WorstApp
Suppressing Events
You can define any event catalog and class to suppress events using the format shown in Figure 3. Figure 3 Event Catalog Definition Format
catalog;class
Defining the Client Configuration File

This section contains information about how to define the client configuration file using the Common Connect configuration utility.
To Define a Client Configuration File 1 Start the Common Connect configuration utility by using the instructions in
Starting the Common Connect Configuration Utility on page 41.
2 Choose the File => Connect menu command to open the Configuration Wizard.
45
3 Click Next.
The Connect to RTserver(s) dialog box is displayed.
4 Perform one of the following actions to specify the RTserver to which you want to
connect:
s
Click Next to accept the default RTserver name. In the RTserver Name(s) list, change the name of the system on which the RTserver is installed and the port number through which it connects, then click
Next.
The Select Common Connect Service dialog box is displayed.
NOTE
The PATROL Console Server (with Common Connect Back End) is referred to as the Common Connect Service on this wizard dialog box.
5 In the Service Name list, select the name of the PATROL Console Server and click
Next.
The Provide User Credentials dialog box is displayed.
6 Perform the following actions to specify the account under which you installed the
PATROL Console Server: A. In the User Name field, enter the user name. B. In the Password field, enter the password. C. Click Next. The Select Configuration dialog box is displayed.
WARNING
If you enter an incorrect user name or password, the configuration utility hangs, and you must restart it.
7 Select the Modify client configuration file option and click Next.
The Select Common Connect Client dialog box is displayed.
8 In the Common Connect Client pane, select the BII4Patrol option and click Next.
46
NOTE
If BII4Patrol is not displayed, check to be sure that you restarted the PATROL Console Server after installing the Common Connect Back End.
The Open/Create Configuration File dialog box is displayed.
9 Perform the following actions: A In Client Attribute Configuration File field, enter a new file name. B Click Next.
The Edit Client Attributes dialog box is displayed.
10 On the Edit Client Attributes dialog box, select Config_BII4Patrol from the list. 11 Double-click the slot under Value.
A list of suppressed events is displayed.
12 Either change the values in Event_Suppress_List to receive suppressed event types,

or add event types to suppress. When you are finished, click Next. The Configuration Change Complete dialog box is displayed.
WARNING
After you make changes to this file, you must move the cursor to a different line or press Enter to save your changes.
13 Review the information and click Finish.

The client configuration file is saved in
s
Microsoft Windows:
%PATROL_ROOT%\log\cserver\cc_client_config\
Unix or Linux:
$PATROL_ROOT/log/cserver/cc_client_config/
NOTE
If you are using your own event supress list, use the Client Configuration File name in the -cfgid parameter in the bii4p_start.opts file.
47
Setting Event Filtering

After setting up the client configuration file as well as BMC II for PATROL, the PATROL managed systems and the PATROL KMs in the management profile, you can customize filters to show only the PATROL 7.1 events that you want to see in a BMC IM console. The Common Connect configuration utility contains the following filter categories:
s s s s
Date/Time Event Properties Common Attributes Custom Attributes
For more information about event filtering see the Common Connect configuration utility online Help.
Date and Time Filtering

Use the Date and Time filtering category to set up times for BMC II for PATROL to disconnect and reconnect to PATROL Agents. This type of filtering is useful when you want to disconnect BMC II for PATROL for periods of scheduled maintenance.
Event Properties Filtering

The Event Properties category allows you to specify the class, type, and severity level of the events that you want to receive. You must select All Types and set the Event Severity to 2 if you want BMC II for PATROL to automatically close an event when the parameter returns to a normal state. The Event Properties selection adjusts filtering for the entire managed system, including the PATROL KM for Event Management and the notification server, if they have been defined as part of the managed system in the management profile.
Common Attributes Filtering

The Common Attributes category allows you to filter based on the event origin for managed PATROL systems and to view only events with specific event descriptions. The filtering applies to individual PATROL Agents, not to PATROL KMs or the entire managed system.
48
Custom Attributes Filtering

The Custom Attributes category allows you to pass specific events from the PATROL standard event catalog or a KM-specific custom catalog.
Query Filtering
The Query Filter button in the toolbar is not used with BMC II for PATROL.
Configuring and Using Startup Options

BMC II for PATROL uses the bii4p_start.opts file to configure certain startup options without user intervention.
NOTE
The bii4p_start.opts file is located at CC_HOME\etc.
Use of the bii4p_start.opts file has the following advantages:

s s
Interdependencies across different components can be avoided Configuration of the file is simple
Available Startup Options

Table 8 on page 50 contains available startup options and descriptions.
WARNING
Entries in the bii4p_start.opts file are case-sensitive for both Windows and Unix. Ensure that entries (as well as default values) match names of your components in case.
49
All parameters are optional except -mprofile. Table 8 -mprofile Startup Options Defined in bii4p_start.opts (Part 1 of 2) Description Default name of management profile no default (required) Note: The management profile name you enter must exactly match the name entered in the configuration utility (case sensitive). name of the RTserver RTSERVERS environment variable
Note: If RTSERVERS is not defined, bii4p_start.opts will
Startup Option
-rtserver
use tcp:localhost:2059 -cserver name of the PATROL Console Server hostname in uppercase characters
Note: This value is always converted to uppercase.
-cell
BMC Impact Manager to connect to
local hostname in lowercase

Note: Because the -cell
option defaults to the hostname in lowercase, if this option is left blank, you must ensure that your BMC Impact Manager cell name in your mcell.dir file is in lowercase as well. -instance instance name of the BMC II for PATROL process to run The instance name is used to build the server name in the format BII4Patrol_instance. The server name must be listed in mcell.dir. hostname in lowercase
50
Table 8
Startup Options Defined in bii4p_start.opts (Part 2 of 2) Description BMC II for PATROL configuration file Default
bii4p.conf, located at CC_HOME/etc Note: Even if you change the name of the file, bii4p.conf
Startup Option -imConfFile
must be located in the default directory. -debug turns debug on or off Values can be 0 (off) or 1 (on). -cfgid user configuration file ID no default
Note: If you are using your
0 (off)
own event supress list, use the Client Configuration File name in the -cfgid parameter in the bii4p_start.opts file. Configure the bii4p_start.opts file in a text editor, save, then close. Figure 4 contains an example bii4p_start.opts file. In this example, not all fields are defined and BMC II for PATROL will use default values. Figure 4 Example bii4p_start.opts File
eastcoast3 tcp:localhost:2059 CONSOLESERVERHOSTNAME payroll6 bii4p2 bii4p.conf 0
-mprofile -rtserver -cserver -cell -instance -imConfFile -debug -cfgid
Using Startup Options

After configuring the bii4p_start.opts file, you can start BMC II for PATROL in two ways:
s s
as a service from the command line
This section contains information on starting BMC II for PATROL.
51
To Start BMC II for PATROL as a Windows Service 1 Modify the bii4p_start.opts file to define startup options. The -mprofile option is
required.
2 Run BII4Patrol -install 3 Start the BMC II for PATROL process from either the Services applet or by using
the net start command.
NOTE
For additional startup arguments, see Chapter 5, Startup and Validation.
Updating the mcell.dir file

Use the tasks in this section to edit the mcell.dir file in BMC II for PATROL installations where you have installed onto a remote cell or where you are running multiple cells on one server. The mcell.dir file lists the identifying information for all BMC Impact Manager instances (cells) and integration servers to which your implementation can connect and communicate.
NOTE
The location of mcell.dir is configured in bii4p.conf.
The mcell.dir file accessed by BMC II for PATROL must contain definitions for itself and the BMC IM cell(s) to which it connects. The mcell.dir file accessed by a BMC IM cell must contain definitions for itself and the instance of BMC II for PATROL which connects to it.
WARNING
If you point to a cell being used by a previous version of BMC Impact Integration for PATROL, the information in the cell will be overwritten and will no longer function with the previous integration.
52
Review the example configurations shown in Figure 5, Figure 6, and Figure 7 to determine how to modify the mcell.dir file in each system. Then follow the steps in To Edit the mcell.dir File for a Remote Cell on page 54 or To Edit the mcell.dir File for Multiple Instances on page 55.
NOTE
By default, the entry for the local BMC II for PATROL instance is set to cell BII4Patrol_hostname mc hostname:4097
Example Configurations of mcell.dir

WARNING
When editing the mcell.dir file, pay special attention to case for both Windows and Unix. mcell.dir entries must match bii4p_start.opts entries in case.
Use the example information in Figure 5 to configure your mcell.dir file if BMC II for PATROL will connect to a BMC IM cell installed on the same system. Entries in the mcell.dir file are case-sensitive for both Windows and Unix. Figure 5 Example mcell.dir Scenario 1
Points to
mc systema:4097 mc systema:1828 BMC II for PATROL on same system BMC IM cell on same system
Example mcell.dir file

cell cell BII4Patrol_systema bmc_im_cellname_a
Use the example information in Figure 6 to configure your mcell.dir file if BMC II for PATROL will connect to a BMC IM cell installed on a different system. Entries in the mcell.dir file are case-sensitive for both Windows and Unix. Figure 6 System A
cell cell BII4Patrol_systema mc systema:4097 bmc_im_cellname_b mc systemb:1828 BMC II for PATROL on same system BMC IM cell on System B BMC II for PATROL on System A BMC IM cell on same system
Example mcell.dir Scenario 2

Points to
Example mcell.dir files:
System B
cell cell BII4Patrol_systema mc systema:4097 bmc_im_cellname_b mc systemb:1828
53
Figure 7 shows mcell.dir file entries for two instances of an integration running on System A where:
s s s s s
the integrations are called a1 and a2 and reside on System A each instance has its own port number a BMC IM cell, bmc_im_cell1, resides on System B a second BMC IM cell, bmc_im_cell2, resides on SystemC each instance of BMC II for PATROL has its own bii4p_start.opts file Example mcell.dir Scenario 3
Points to mc mc mc mc systema:4097 systema:4098 systemb:1828 systemc:1829
BMC II for PATROL on same system BMC II for PATROL on same system BMC IM cell on System B BMC IM cell on System C
Figure 7 System A
cell cell cell cell
Example mcell.dir file: BII4Patrol_a1 BII4Patrol_a2 bmc_im_cell1 bmc_im_cell2
System B
cell BII4Patrol_a1 mc systema:4097 cell bmc_im_cell1 mc systemb:1828
BMC II for PATROL on System A BMC IM cell on same system BMC II for PATROL on System A BMC IM cell on same system
System C
cell cell BII4Patrol_a2 mc systema:4098 bmc_im_cell2 mc systemc:1829
Editing the mcell.dir File

An integration can connect to the BMC IM instances that are defined in its mcell.dir file. Other BMC IM instances in the network can connect with the integration only if the integration is defined in their mcell.dir files. The instance name is used to identify the specific integration instance in the mcell.dir files of BMC IM instances that are enabled to connect to the integration instance.
To Edit the mcell.dir File for a Remote Cell 1 In a text editor, open mcell.dir.
Entries in mcell.dir are case-sensitive for both Windows and Unix. Use the format described in Figure 8 to configure the integration instance. Figure 8 BMC IM Definition Format for a Remote BMC II for PATROL Instance
cell <integrationhostname> <encryption_code> <integrationhostname>:<port>
2 Add the BMC IM instance that you want the integration to communicate with to
the file, defining them as cells.
54
3 Save and close the mcell.dir file. To Edit the mcell.dir File for Multiple Instances 1 In a text editor, open mcell.dir. 2 Use the format described in Figure 7 when creating entries for multiple instances of
an integration that are running on a single computer.
3 Add the BMC IM instances that you want the integration to communicate with to
the file, defining them as cells.
4 Save and close the mcell.dir file.
Instance Name and Configuration Settings

You can configure different instance names and configuration settings in the bii4p_start.opts file. Generally, an integration uses only one bii4p.conf file, which is stored in the integration configuration directory. However, if you are going to run multiple instances and would like each instance to have a different configuration, each instance will require its own configuration file. Assigning a configuration file to an instance is done in bii4p_start.opts. The following are options for configuring the instances:
s s
Each instance can run using unique parameters Some instances can run using a default configuration while others run using unique configurations
For information about setting bii4p_start.opts, see Using Startup Options on page 51.
Updating Knowledge Base Files

If you connect to a remote cell or a cell that is not the cell you specified when you installed BMC II for PATROL, you need to copy the BMC II for PATROL Knowledge Base (KB) files to the other cell and then rebuild the KB.
55
To Update KB Files 1 Access one of the following directories:

s
Windows: MCELL_HOME\etc\cellname\kb\classes Unix: MCELL_HOME/etc/cellname/kb/classes
2 Copy the bii4p.baroc file from the CC_HOME\etc (Windows) or CC_HOME/etc

(Unix) directory into the directory you specified in Step 1.
3 Edit the *.load file:

s
Comment out the mcxp entry Add bii4p to the bottom of the file
4 Access one of the following directories:

s
Windows: MCELL_HOME\etc\cellname\kb\rules Unix: MCELL_HOME/etc/cellname/kb/rules
5 Copy the bii4p.mrl file from the CC_HOME\etc (Windows) or CC_HOME/etc (Unix)
directory into the directory you specified in Step 4.

s
Comment out the mcxp entry Add bii4p to the bottom of the file
7 Access one of the following directories:

s
Windows: MCELL_HOME\etc\cellname\kb\collectors Unix: MCELL_HOME/etc/cellname/kb/collectors
8 Copy the bii4p_collectors.mrl file from the CC_HOME\etc (Windows) or

CC_HOME/etc (Unix) directory into the directory you specified in Step 7.

s
Comment out the mcxpcoll entry Add bii4p_collectors to the bottom of the file
56
10 Access the MCELL_HOME\etc\cellname\kb directory. 11 Enter the one of the following commands:
s
(Windows) MCELL_HOME\bin\mccomp manifest.kb (Unix) MCELL_HOME/bin/mccomp manifest.kb
12 Restart the cell if it is already running.
Configuration Files
The bii4p.conf file contains parameters for tracing, the BMC Impact Manager directory file, and buffer management as described in Appendix A, Configuration File Parameters. You can optionally configure TraceConfigFileName and the variables in bii4p.trace to specify how you want to handle trace messages. Table 9 File
bii4p.conf
s
Post-Installation Variable Locations and Definitions Variables

Server DirectoryName
Specifies (required) the path to the target BMC Impact Manager (cell) directory (mcell.dir)
Example: (Local) ServerDirectoryName= MCELL_HOME/etc/ mcell.dir (Remote) ServerDirectoryName= CC_HOME/etc/mcell.dir
Windows: CC_HOME\etc Unix: CC_HOME/etc
TraceConfig FileName
(optional) the path to the trace configuration file

Example: TraceConfigFileName= $CC_HOME/etc/ bii4p.trace
57
Table 9 File
bii4p.trace
s s
Post-Installation Variable Locations and Definitions Variables

ALL SERVICE SYNCH MESSAGES
Specifies (optional) the level of the trace messages on a module/level basis

Example: ALL ALL stderr SERVICE ALL NONE SYNCH ALL NONE MESSAGES ALL NONE
Windows: CC_HOME\etc Unix: CC_HOME/etc
For a complete list of parameters, see Appendix A, Configuration File Parameters.
58
Chapter
5
60 61 63 63 64 65
Startup and Validation

This chapter presents the following topics: Command Line Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping BMC II for PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Validating Correct Functioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Event Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring PATROL Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5 Startup and Validation
59
Command Line Arguments
Command Line Arguments

You can start BMC II for PATROL using command line arguments and use startup arguments to specify special conditions that you want to apply to the application. To use command line arguments to start BMC II for PATROL, see Command Line Arguments on page 60. For ease of use in Microsoft Windows, you can run the BMC II for PATROL client as a Windows service (see To Start BMC II for PATROL as a Windows Service on page 62).
NOTE
If you do not specify the PATROL Console Server and RTserver through command line arguments, BMC II for PATROL will default to the PATROL Console Server or RTserver residing on the local machine.
Command Line Arguments Table

Review the BMC II for PATROL client command line arguments (including startup arguments) for the BII4Patrol.exe file in Table 10. Table 10
-cell
Command Line Arguments (Part 1 of 2) Definition specifies the BMC IM (cell) name to which BMC II for PATROL will connect. The default value is the local host name in lowercase letters. This value can be a local cell or a remote cell. The -cell entry must be defined in the mcell.dir file. specifies the name of the configuration file as you defined it (see Defining a Management Profile on page 41). The configuration file name is case sensitive. Example: -cfgid solar
Command Line Argument
-cfgid
-cserver
specifies the host name of PATROL Console Server to which you are connecting Example: -cserver MY COMPUTER
-debug -f
sets the debug flag. Log information useful for debugging will display displays the batch input file; overrides other input options
60
BMC Impact Integration for PATROL Installation and Configuration Guide
Starting BMC II for PATROL
Table 10
-help
Command Line Arguments (Part 2 of 2) Definition displays command line arguments for BMC II for PATROL specifies the integration configuration file; defaults to bii4p.conf installs BMC II for PATROL as a service specifies the instance name; enter the default local host in lowercase letters management profile name removes BMC II for PATROL from the service database specifies the protocol to be used for connecting, the host name of the real-time server to which you want to connect, and the port number to use for the connection Example: -rtserver tcp:MYCOMPUTER:2059
Command Line Argument
-imConfFile -install -instance -mprofile -remove -rtserver
-version
displays the version number of BMC II for PATROL

This section contains information about startup arguments and instructions on starting BMC II for PATROL.
Before You Begin

Make sure that you know the names of the following components that you want to connect to:
s s s s s s
RTserver name and port number PATROL Console Server management profile BMC II for PATROL port number configuration file BMC IM (cell) name, cell host name, and cell port number
61
To Start BMC II for PATROL from a DOS Prompt 1 Open an MS-DOS command prompt window and change the directory to the path
where the client executable file resides.
EXAMPLE
Enter cd CC_HOME\bin\Windows-x86 and press Enter.
2 Type BII4Patrol and press Enter. 3 The startup script is launched.

For information on other BMC II for PATROL command line arguments, refer to Table 10.
To Start BMC II for PATROL as a Windows Service 1 Ensure that you have used the -install command line argument to set BMC II for
PATROL to run as a service (see Table 10 on page 60).
2 From the Windows task bar, choose Start => Settings => Control Panel => Services =>
BMC Impact Integration for PATROL.
3 In the Services window toolbar click Start. To Start BMC II for PATROL from the Command Line in Unix 1 Change directory to CC_HOME/bin/platform. 2 Select one of the following options, depending on your operating system:
s
In AIX and Solaris environments, type start_bii4p.sh and press Enter. In HP-UX and Red Hat environments, and depending on the shell you are using, run one of the following commands from the installationDirectory/common/bmc directory:
s s
C shell: source ./patrol7rc.csh Bourne shell: run . ./patrol7rc.sh
3 In HP-UX and Red Hat environments only, enter the following command from the
installationDirectory/common/bmc directory: run ./BII4Patrol
62
Stopping BMC II for PATROL
Stopping BMC II for PATROL

This section contains procedures to stop BMC II for PATROL.
To Stop BMC II for PATROL on Windows 1 From the Windows task bar, choose Start => Settings => Control Panel => Services =>
BMC Impact Integration for Patrol.
2 In the Services window toolbar, click Stop. To Stop BMC II for PATROL on Unix 1 Change directory to CC_HOME/bin/platform. 2 Select one of the following options, depending on your operating system:
s s
In AIX, Solaris, and Red Hat environments, type stop_bii4p.sh and press Enter. In HP-UX environments, kill the process or press Ctrl-C.
Validating Correct Functioning

You can validate whether BMC II for PATROL is running correctly on either Unix or Windows platforms by performing the next task.
To Validate that Services are Running Correctly 1 Verify that the BMC II for PATROL process is running:
s
On Unix, enter the following command: ps -ef | grep BII4Patrol
63
On Windows, use one of the following methods: From the Windows task bar, choose Start => Settings => Control Panel => Administrative Tools => Services. Verify that the status of the BMC Impact Integration for Patrol service is Started. In the Windows task bar, right-click and choose the Task Manager menu command; click the Processes tab. The BMC II for PATROL process is running if BII4Patrol.exe is listed on this tab of the Task Manager.
2 Verify that the following events are being received and displayed by the BMC
Impact Explorer (BMC IX) to which the BMC II for PATROL is sending event information:
s
an MC_ADAPTER_START event whose mc_tool_class slot value contains the BII4PATROL 7.1 string an MC_ADAPTER_START event is generated an MC_ADAPTER_CONTROL event whose mc_tool slot value contains the P_AGENT_UP string PATROL_EV events are generated
3 Compare PATROL_EV events in the BMC IX with the PATROL events from the
PATROL console to determine whether they contain the same event information. BMC IX usually contains fewer events than the PATROL Event Manager because the BMC II for PATROL component filters out events and the BMC IM contains rules to update, not create, new events. For information about event filtering in BMC II for PATROL, see Chapter 4, Configuration.
Monitoring Event Load

When BMC II for PATROL has been started, you can estimate the event load by looking at the activity on the cell which BMC II for PATROL is sending event information. Monitor the event load by using the mgetinfo command. This command is available in the BMC IM and its correct use is detailed in the BMC Impact Manager Administrator Guide.
64
Monitoring PATROL Collectors

You can monitor the PATROL objects from PATROL collectors in the BMC Impact Explorer. By default, you can see objects on the Computer and Application Class level. You can also expand the object collector to the PATROL Instance level. To do so, you need to modify the collector file.
To Modify the Collector File 1 Access the MCELL_HOME/etc/cell-name/kb/collectors directory. 2 Open the bii4p_collectors.mrl file for editing. 3 Locate the following paragraph:
## ## ## ## collector PATROL.*.*.* : PATROL_EV where [p_instance: not_equals ] create $THIS.p_instance END
4 Activate the rule by deleting the comment symols # # from the beginning of each
line.
5 Save the file. 6 Recompile the KB using mccomp. See Updating Knowledge Base Files on
page 55.
7 Restart the cell.
65
66
Chapter
6
68 70 71 73
Event Handling
This chapter presents the following topics: About PATROL 7 Event Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Information for the PATROL KM for Event Management . . . . . . . . . Event Class Slots Inherited from the BMC IM Event Class . . . . . . . . . . . . . . . . . . BMC II for PATROL Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 6 Event Handling
67
About PATROL 7 Event Mapping

Events from PATROL 7 managed systems, including systems with the PATROL Knowledge Module (KM) for Event Management, are
s
translated to a format that can be understood by BMC IM using BMC II for PATROL. mapped to the PATROL_EV event class in the BMC IM cells Knowledge Base (KB).
The PATROL_EV event class is defined in the bii4p.baroc file in the KB. The PATROL_EV event class is subordinate to the base event class for BMC IM, called EVENT. In the BMC Impact Manager environment, an event class can have many slots, each one of which is a field in the event class definition. The slot content determines how the incoming event is processed by the BMC IM cell, according to the rules contained in its KB. Table 11 lists the slots for the PATROL_EV event class. Table 11 Slot Name p_agent p_agent_address p_agent_port p_agent_version p_application BMC IM Event Class Slots for PATROL 7 Managed Systems Description the hostname of the PATROL Agent that has reported the event the Internet Protocol (IP) address of p_agent the port number the PATROL Agent is using for communications the version of the PATROL Agent the name of the PATROL KM This slot can be empty when no KM is associated with the event. p_args p_catalog p_class a list of strings containing the event attributes the name of the PATROL Standard Event Catalog or a customized event catalog as displayed in the PATROL Event Manager the name of the PATROL class as displayed in the PATROL Event Manager The value for this slot is usually a string, although the string often consists of an integer. p_diary p_diary_text p_diary_operator p_diary_time p_expectancy mc_host_address the PATROL diary the array of diary text the array of lem management operator the array of lem diary time obsolete the IP address of mc_host
68
Slot Name p_instance
Description the name of the PATROL instance This slot can be empty when no instance is associated with the event.
p_origin p_source_id p_status
the PATROL Origin as displayed in the PATROL Event Manager the value of the Agent Object Identifier needed by event action the PATROL Event Manager event status, displayed as an integer See the definition of status slots for the list of p_status values in Table 12 on page 69.
p_type
the PATROL Type Identifier, displayed as an integer See the definition of severity slot for the list of p_type values in Table 13 on page 69.
p_handler p_node p_owner
obsolete obsolete obsolete Table 12 and Table 13 compare PATROL and BMC IM event statuses and severities. Table 12 Value 0 1 2 3 4 Table 13 Value 0 1 2 3 4 5 Event Status Enumeration PATROL Status OPEN CLOSED ACKNOWLEDGED ESCALATED DELETED Event Severity Mapping PATROL Type OK INFO WARNING MINOR MAJOR CRITICAL BMC Impact Manager Severity OK INFO WARNING MINOR MAJOR CRITICAL BMC Impact Manager Status OPEN CLOSED ACKNOWLEDGED OPEN N/A
69
Additional Information for the PATROL KM for Event Management

The PATROL_EV event class also contains slots for additional information provided by events from a PATROL KM for Event Management notification server that you identified in the management profile. The PATROL KM for Event Management events called NOTIFY_EVENT and REMOTE_NOTIFY_EVENT that are generated with the notification server name are translated to contain the origin name of the event. The events undergo this translation process as they are forwarded by BMC II for PATROL. The additional slots in the PATROL_EV event class that enable the remapping are listed in Table 14. Table 14 Slot Name mc_parameter_value pes pes_custom_id1 pes_custom_id2 pes_tcp_port pes_udp_port pes_icon_name pes_parent_instance pes_param_status pes_alert_date PATROL KM for Event Management Slots in the PATROL_EV Event Class (Part 1 of 2) Description the value of the PATROL PATROL KM for Event Management parameter at the time of alert a Boolean flag to indicate the PATROL PATROL KM for Event Management source a custom identifier assigned to an object a custom identifier assigned to an object the TCP port on which the affected PATROL Agent is listening the UDP port on which the affected PATROL Agent is listening the name of the instance as displayed on the PATROL console, such as oracle_db1 the instance name that is the parent container of instance, such as CPU/CPU the value of the PATROL PATROL KM for Event Management parameter status at the time of the alert the date the alert occurred This is the date on the local mc_host. pes_alert_time the time the alert occurred This is the time on the local mc_host. pes_tz pes_last10 the time zone to which the affected PATROL PATROL KM for Event Management system is set the last ten (10) PATROL PATROL KM for Event Management parameter values preceding and including the current value Values are space delimited, as in 98.11 97.14 95.87.
70
Table 14 Slot Name
PATROL KM for Event Management Slots in the PATROL_EV Event Class (Part 2 of 2) Description the average of the last ten (10) PATROL PATROL KM for Event Management parameter values the times at which the last ten (10) PATROL PATROL KM for Event Management parameter values were collected These map directly with the pes_last10 values. The time value is expressed in seconds since epoch.
pes_ave10 pes_last10_ts
pes_last10_tp pes_user_defined
the length of time, in minutes, between the first PATROL PATROL KM for Event Management parameter value and the last the user defined variable This variable contains the information stored in the variable /_my_APPCLASS_APPINSTANCE_PARAMETER at the time of the alert condition.
pes_alarm_min pes_alarm_max pes_patrol_home
the lowest threshold value of the current alarm range the highest threshold value of the current alarm range
%PATROL_HOME% of the PATROL Agent
Event Class Slots Inherited from the BMC IM Event Class

The BMC II for PATROL event class slots that are inherited from the BMC IM base class EVENT are listed in Table 15. Table 15 Slot Name adapter_host status severity BMC IM Slots Inherited by the BMC II for PATROL Event Class (Part 1 of 3) Description the fully qualified host name of the computer on which BMC II for PATROL is running the event status, corresponds to the PATROL status according to Table 12 on page 69 the severity slot value is based on the PATROL Type according to Table 13 on page 69
71
Table 15 Slot Name mc_host
BMC IM Slots Inherited by the BMC II for PATROL Event Class (Part 2 of 3) Description the fully qualified domain name (FQDN) of the host on which the event occurred Generally, it can be different from the PATROL Agent host name, as in the case of an event reported on a remote Agent by the PATROL KM for Event Management. PATROL does not provide the FQDN. BMC II for PATROL attempts to retrieve the fully qualified name for the event, but if your DNS is not configured correctly, the attempt to retrieve the FQDN may not be successful. In this case, the cell sets the event's mc_location slot to UNKNOWN.
mc_host_class mc_host_address mc_object

mc_object_class
the operating system (OS) version of mc_host the IP address of mc_host the name of the PATROL instance the name of the PATROL KM (application) the name of the PATROL parameter that generated the event This slot can be empty when no BMC IM attribute is associated with the event.
mc_parameter
mc_tool
the host name of the PATROL Agent that created the original event Its syntax is the host name of the PATROL Agent that created the original event, followed by the colon character (:), followed by the port number of the PATROL Agent.
mc_tool_class mc_tool_key
mc_tool_sev
the string BII4PATROL7.1 the PATROL event identifier the PATROL event severity, as displayed in the PATROL Event Manager The severity level is expressed as an integer, with a value ranging from 1 to 5; 5 is the highest severity.
mc_origin_class mc_origin
the string Vagent-major-version.agent-minor-version the hostname of the PATROL Agent that created the original event Its syntax is the hostname of the PATROL Agent that created the original event, followed by the colon character (:), followed by the port number of the PATROL Agent.
mc_origin_key mc_origin_sev
the PATROL event identifier the PATROL severity level, as displayed in the PATROL Event Manager The severity level is expressed as an integer, with a value ranging from 1 to 5; 5 is the highest severity.
72
Table 15 Slot Name mc_ueid
BMC IM Slots Inherited by the BMC II for PATROL Event Class (Part 3 of 3) Description A string formed as follows: BII4Patrol/Agent IP Address/port/lem time/lem ID
mc_incident_time msg
Time stamp the LEM event occurred the text description of the event
BMC II for PATROL Events

Table 16 lists the events that are generated by BMC II for PATROL. Each of these events comes from the mc_tool_class slot in BMC IM. Table 16 Events Generated by BMC II for PATROL Description indicates the integration component has started indicates the integration component has stopped indicates when the PATROL Agent connects or disconnects indicates when the event buffer has overflowed or when events have been discarded
Event Name
MC_ADAPTER_START MC_ADAPTER_STOP MC_ADAPTER_CONTROL MC_ADAPTER_ERROR
Event Files
For a list of the event files included in BMC II for PATROL, see Appendix B, BMC IM Rules for PATROL Events.
73
74
Chapter
7
76 76 77 77 78 78 79 79
Troubleshooting
Use the information in this chapter to help you diagnose and correct problems. Console Server Authentication Fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . imServer Does Not Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BII4Patrol Terminated at Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Console Server Not Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cannot Access the Management Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unable to Start BMC II for PATROL as a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Missing Cell Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7 Troubleshooting
75
Console Server Authentication Fails

An error message resembling the following is displayed:
ERROR:6/11/04 9:30:46 AM:::Error registering batch authentication provider ERROR:6/11/04 9:30:46 AM::120.2003:to Console Server authentication failed ERROR:6/11/04 9:30:46 AM::120.2008:BII4Patrol failed to connect to cserver <SWEDEN>. Reason:<aughentication rejected> INFORM:6/11/04 9:30:46 AM::120.5:BII4Patrol exiting...
Reason
The user ID or password in the cconnect.conf file does not match the Console Server user ID or password.
Action
Use the ccPassword utility under BMCsoftware\common\bmc to update the cconnect.conf file.
imServer Does Not Start

INFORM:6/9/04 12:58:57 PM::120.86:Regesting BMCII trace success ERROR:6/9/04 12:58:57 PM::120.2095:Error in starting imServer <>. Reason:<Service endpoint could not be bound>
Reason
The socket used by BMC II for PATROL is not available.
Action
Use a different port number. Edit the mcell.dir file to change the port number.
76
BII4Patrol Terminated at Startup

ERROR:6/5/04 11:10:03 AM::120.2096:Unable to retrieve directory information for server <qasunpv11>. Reason:<The requested item (such as a slot) does not exist.> ERROR:6/5/04 11:10:03 AM::120.2081:Failed to create imClient object INFORM:6/5/04 11:10:03 AM::120.1:BMC Impact Integration for PATROL 7 stopped. INFORM:6/5/04 11:10:03 AM::120.3:BII4Patrol: Main loop interrupted...
Reason
The cell entry referenced in the bii4p_start.opts file does not exist in the mcell.dir file.
Action
Add the cell entry. Edit the mcell.dir file to add the cell.
Console Server Not Started

ERROR:6/5/04 11:07:59 AM::120.2012:Error! Object </services/PATROL_CCSERVER_PVSUN1> does not exist ERROR:6/5/04 11:07:59 AM::120.2005:Error in initializing bii4p service. Please checkyour RT server INFORM:6/5/04 11:07:59 AM::120.5:BII4Patrol exiting...
Reason
The Console Server is not started on the RTServer cloud.
Action
Start the Console Server. If the Console Server is already running, check the bii4p_start.opts file for errors.
77
Cannot Access the Management Profile

ERROR:6/5/04 11:20:38 AM::120.2011:Opening CC consumer node failed. Please check the status of Management Profile. Reason:<access denied>
Reason
The management profile either does not exist or is in use by another application.
Action
Check the Common Connect configuration utility, PATROL console, or any other application that might use the management profile. Close the management profile and restart BMC II for PATROL.
Unable to Start BMC II for PATROL as a Service

When you attempt to start the service, the following message is displayed:
BII4Patrol.exe - Unable to Locate DLL
Reason
Windows is looking for vul7_t.dll in C:\Program Files\BMC Software\Common_Connect\bin\Windows-x86 but it is located in C:\Program Files\BMC Software\common\bin\Windows-x86 and that's what is set in PATH.
Action
Reboot your server.
78
Installation Fails
The installation terminates abnormally.
Reason
The Console Server was not stopped.
Action
Stop the Console Server and retry installing.
Missing Cell Entry

An error message resembling the following is displayed after starting BMC II for PATROL:
Unabletoretrievedirectoryinformationforserver<romania>requesteditemdoesn'texist/ Failed to create imClient object
Reason
The cell entry is missing from the mcell.dir file.
Action
Edit the mcell.dir file.
79
80
Appendix
Configuration File Parameters

The parameters listed in Table 17 on page 82 can be used in the bii4p.conf configuration file. You can modify the bii4p.conf file before you use your integration or at any time after it is in use. After modifying the bii4p.conf file, you must restart your integration, which is described in Chapter 5, Startup and Validation. To activate non-default parameters, remove the hash preceding the parameter in the bii4p.conf file. To suppress parameters, add a hash before the parameter line.
Appendix A
81
Table 17
Group
bii4p.conf File parameters (Part 1 of 7)
Parameter ServerDirectoryName
Description path and name of the directory file (default file name: mcell.dir). Default path:
MCELL_HOME\etc\mcell.dir (Windows) MCELL_HOME/etc/mcell.dir (Unix)
Connected Impact Manager Instances
BMC Software recommends that you store the

mcell.dir file in the integration working directory or in the MCELL_HOME/etc
directory.
Notes:
s
The mcell.dir file contains a list of all BMC IM instances to which the integration can connect. The integration can use the mcell.dir file supplied with the integration, or it can use the mcell.dir file of a BMC IM instance that is already installed on the same host.
Connection Management
ConnectionSetupTimeOut
maximum time, in seconds, that a CLI command attempts to establish a connection to a cell If the connection with the cell cannot be completely established within this time frame, the command aborts. Default: 10 seconds If the cell is busy with a database cleanup, it may be impossible to connect the CLI with the default values. A database cleanup has a duration limit defined by the EventDBCleanupDurationLimit option, with a default value of 30 seconds. With a default ConnectionSetupTimeOut of 10 seconds, the connection cannot be established within the first 20 seconds of a cleanup.
82
Table 17
Group
Parameter ConnectionPortRange
Description specifies the range of ports to use for outgoing connections For a cell, this applies to forward propagation. It is the port used on the client side (or on the propagating cell side). This is useful only to pass the event through firewalls with high restrictions. Most firewall configurations ignore source port information but require destination port information. However, firewall configuration usually can restrict the source ports as well. The default is (empty).
Connection Management, continued
ConnectionPortReuse
indicates whether or not the ports specified in ConnectionPortRange should be reused as much as possible By default, the cell or CLI tries to reuse ports from the specified range, in the given order. When ConnectionPortReuse=No, for every new connection within the same session, the next free port from the specified range is used. Only when it reaches the end of the range will it restart at the beginning of the range. Default=Yes
Encryption
indicates whether communications are encrypted Valid values:

s s
No Yes (default)
Appendix A
83
Table 17
Group
Parameter MessageBufferKeepSent
Description time, in seconds, to keep sent messages buffered while waiting for an answer Default: 300 seconds
Message Propagation
MessageBufferKeepWait
time, in seconds, that messages are retained in the buffer while waiting for the connection to be established Default: 3600 seconds (one hour)
MessageBufferSize
maximum number of messages that can be stored in the message buffer. Optional. Default: 2000 messages
MessageBufferReconnectInterval period of time, in seconds, between attempts to connect to a BMC IM instance. Optional. Default: 60 seconds
Notes:
s
The value of this parameter cannot be less than 60 seconds. When a connection is established, the integration sends buffered messages that are designated for the BMC IM instance with which the connection is established.
MessageBufferResendCount
number of times to resend unanswered messages Default: 1
84
Table 17
Group Buffered Message Retention
Parameter PersistencyEnabled
Description enables persistency, which specifies additional buffering parameters when the buffer mode is Default Valid values:
s s
No Yes (default)
PersistencyLevel
buffer mode used when the Default buffering mode is specified. This parameter is enabled only when the PersistencyEnabled parameter value is Yes. Optional. Valid values:
s s s
None Low (default) High
Note: These values are case-sensitive and should be entered as shown here.
PersistencyFileName
name of the file in which the buffered messages are stored Default: log_directory\imgw-bii4p.dat
PersistencyCleanupSize Threshold PersistencyCleanupGarbage Threshold
threshold size, in bytes, of the persistency file that activates garbage collection threshold size, as a percentage of file size, of the persistency file that activates garbage collection
Appendix A
85
Table 17
Group Buffered Message Retention, continued
Parameter PersistencyDisconnectRemove Messages
Description indicates whether messages written to the persistency file are deleted when the integration disconnects intentionally from a BMC IM instance Valid values:
s s
No Yes (Default)
Notes:
s
The contents of the file are not deleted when the integration crashes. BMC Software recommends that you add this parameter to the bii4p.conf file and set the value to No.
86
Table 17
Group
Parameter
Description flag that indicates whether tracing is enabled. Optional. Valid values:
s s
Trace Parameters Trace
YES or ON enable tracing (default) NO or OFF disable tracing
TraceSrc
when displaying a trace message, specifies whether to display the source code file name and line number where trace message originated. Optional. Valid values:
s
YES or ON display file name and line number NO or OFF no display of file name and line number (default)
Note: Depending on the location of the trace message, the source may be in the integration or the BMC II for PATROL code.
TraceConfigFileName TraceDefaultFileName
path and file name for the bii4p.trace file. Required if Trace=YES. default destination file to which trace messages are redirected from stderr, when the integration runs as a daemon or a service. Required if Trace=YES. maximum size, in KB, of the trace messages file. Optional. Valid values:
s s
TraceFileSize
0 - No limit
n - size of file in KB
Note: BMC Software recommends that the value of this parameter be no less than 500 KB.
Appendix A
87
Table 17
Group
Parameter
Description number of trace files to be kept in history. Each file is numbered sequentially. Optional. The default value is 5 (which generates up to five shuffled trace files). Valid values:
s s
Trace Parameters, TraceFileHistory
continued
0 No files kept. (default)
n - number of files to keep
TraceFileAppend
when the integration is restarted, specifies whether to append new trace messages to the existing message trace file. Optional. Valid values:
s
YES or ON appends new messages to the
existing trace message file (default) NO or OFF - empties the current trace message file
Miscellaneous
UseLocks
flag that indicates whether synchronization locks are used. Optional. Valid values:
s s
YES or ON use locks (default) NO or OFF do not use locks
Notes:
s
In a single-threaded environment, disabling locks may result in more efficient API operation. You must enable locks in an multithreaded environment. If you include the UseLocks parameter in the bii4p.conf file, set the parameter to YES or ON for threading to work. If UseLocks is not already included in the file, there is no need to add it. The default value for the parameter is ON.
88
Appendix
B
89 90 90 92 92 92 92
BMC IM Rules for PATROL Events

This appendix presents the following topics: BBMC IM Rules for PATROL Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Alarms and BMC IM Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL State Changes and BMC IM Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Recovery Actions and BMC IM Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Agent Status and BMC IM Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Duplicate Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Processing and the PATROL KM for Event Management . . . . . . . . . . . . . .
Appendix B
89

BMC IM processes PATROL events with the following rules:
s s
s s
adapt_alarm_severity (for alarms) adapt_param_status, adap_instance_status, adap_application_status and adap_host_status (for state changes) rule alarm_and_ra (for recovery actions) agent_up_closes_down (for the PATROL Agent)
PATROL Alarms and BMC IM Rules

PATROL parameters have three alarm ranges: Alarm (Alarm1), Warning (Alarm2), and Border (out-of-range). The adapt_alarm_severity rule handles alarm events in the manner described in this section. When any one of the three alarms occurs, PATROL generates an event (Event A). The PATROL event can be seen in the BMC IX as a new OPEN event. The severity of this event depends on the severity of the alarm, such as WARNING or CRITICAL. When the alarm range of the PATROL event parameter changes, a new PATROL event is created, Event B, which reports the change of alarm range. At that time, the rule adapt_alarm_severity closes Event A when Event B arrives, making the status slot of Event A set to CLOSED. The purpose of this rule is to have only one open event at any one time that is related to a PATROL parameter. This rule also applies to different events from the PATROL KM for Event Management that report the same information. If an Alarm/Alarm 1 event is reported by both a NOTIFY_EVENT and a REMOTE_NOTIFY_EVENT by the KM for Event Management the second event that arrives at BMC IM will close the first one. When the first alarm is triggered, an event is generated. When the second alarm is triggered, the state of the parameter is changed, so the first PATROL_EV can be closed and only the second PATROL_EV that corresponds to the second alarm is retained. The PATROL events for alarms belong to Standard Event Catalog classes 11 and 39.
PATROL State Changes and BMC IM Rules

Often state change events correspond to other older events. These state change events can be used to close the older ones. The event information is evaluated by the rules adapt_param_status, adap_instance_status, adap_application_status and adap_host_status.
90
These rules evaluate event information according to the following criteria:

s
Event B is a state change event containing information that the state described by Event A has changed. Accordingly, Event A can be closed, and Event B replaces Event A.
You can see how BMC II for PATROL implements these rules by performing the following procedure for a PATROL console on which there are no alarms. 1. Set an alarm on a logical disk that can reflect the alarm quickly. When the alarm is triggered, you can see the following ALARM events in the PATROL console:
s
Event A of class UpdMachineState reports that the state of your computer is changed. Event B reports a PATROL alarm on the parameter. Event C of the UpdInstState class reports that the state of the corresponding instance is changed. Event D of the WorstApp class reports that the state of the corresponding application is changed.
2. Stop the alarm and observe:

s
Event A2 of the UpdMachineState class reports the state of your computer is changed. It can update Event A. Event B2 from PATROL reports that the alarm on the parameter is cancelled. This event updates Event B. Event C2 of the UpdInstState class reports that the state of the corresponding instance is changed. It can update Event C. Event D2 of the UpdAppState class reports that the state of the corresponding application is changed. It can update Event D.
TheUpdInstState,UpdAppState,WorstApp,andUpdMachineStateeventsarefilteredby default. In this case, only Event B is observed when the alarm is triggered, and Event B2 cancels Event B. The rules adap_instance_status, adap_application_status and adap_host_status are not used. If you want to see all the events discussed, you must set MCXPDropClass to the empty string.
Appendix B
91
Event B can be an instance of PATROL standard event catalog classes 9, 11, 39 or UpdParState (in some cases). Event D also can be an instance of the PATROL classes WorstApp or UpdAppState. Event B2 can be an instance of PATROL standard event catalog classes 9, 16, or UpdParState.
PATROL Recovery Actions and BMC IM Rules

When an alarm is triggered, a recovery action can run in the PATROL environment. When you execute a recovery action, a PATROL event is generated that belongs to the PATROL standard event catalog class 10, 12, or 40. In this case, BMC II for PATROL generates two PATROL_EV events, one for the alarm, Event A, and one for the recovery action, Event B. If Event A is closed, then Event B, for the recovery action, can be closed also according to the rule alarm_and_ra.
PATROL Agent Status and BMC IM Rules

When a PATROL Agent is down, an MC_ADAPTER_CONTROL event is generated with the mc_toolslotsettoAGENT_DOWN.WhenthisPATROLAgentisup,anMC_ADAPTER_CONTROL event is generated with the mc_tools slot set to AGENT_UP. This event can close the previous one according to the rule agent_up_closes_down.
PATROL Duplicate Events

Duplicate events that occur when BMC II for PATROL is started are closed according to the rule patrol_duplicates.
Event Processing and the PATROL KM for Event Management

If the PATROL KM for Event Management is loaded and the notification server is identifiedinthemanagementprofile,NOTIFY_EVENTandREMOTE_NOTIFY_EVENTeventsare sent to BMC II for PATROL. In addition to the instance of the PATROL_EV class for all PATROL events, additional processing is performed for PATROL KM for Event Management events. The value of the second item of the string value of the p_args slot contains a list of 32 values that populate slots with the prefix pes. The mc_parameter_value slot is also populated for the PATROL KM for Event Management events; its value is set at the time of the alert.
92
The rule es_priority handles the PATROL KM for Event Management events, NOTIFY_EVENT and REMOTE_NOTIFY_EVENT. For example, an alarm is generated for a disk when its available space is below a defined value, as in LDldFreeSpacePercent < 5. The PATROL KM for Event Management component is loaded on the PATROL console. This alarm generates two events, Event A and Event B.
s
Event A is a PATROL event that you can see in a BMC IX console with a message of the form 'Alarm # 1 of global parameter
LDldFreeSpacePercent' triggered on . . . '
Event B is a NOTIFY_EVENT or REMOTE_NOTIFY_EVENT. The second argument of the argument list p_args is a long string that contains 32 comma-separated values. Only by using this single long string is it possible to reconstruct Event A completely. This string provides additional information that will populate the pes_xxx slots.
When BMC II for PATROL receives Event A, it generates an instance of the class with the information available about the alarm. The pes_xxx slots remain empty because that information is not available. The PATROL_EV is sent to the BMC IM as Event PA. When BMC II for PATROL receives Event B, all the information about the NOTIFY_EVENTorREMOTE_NOTIFY_EVENT,exceptthesecondargumentoftheargument list, is dropped. BMC II for PATROL extracts the information from the argument list and creates a new instance of PATROL_EV. This PATROL_EV is actually the same PATROL_EV as created from Event A, except that the pes_xxx slots are populated. The PATROL_EV is sent to the BMC IM as Event PB. Since Events PA and PB are the same except for the pes_xxx slots, PA is updated with the value of these slots from PB and PB is dropped according to the rule es_priority.
Appendix B
93
94
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Glossary
A
alarm An indication that a parameter for an object has returned a value within the alarm range or that application discovery has discovered that a file or process is missing since the last application check. An alarm state for an object can be indicated by a flashing icon, depending on the configuration of a console preference. See also warning. API See Application Program Interface (API). Application Program Interface (API) A set of externalized functions that allow interaction with an applications. attribute A characteristic that is assigned to a 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, 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.
B
BAROC language Basic Recorder of Objects in C. A structured language used to create and modify class definitions. A class definition is similar to a structure in the C programming language. The elements in a structure are called slots. BMC II See BMC Impact Integration product. BMC IM See BMC Impact Manager.
Glossary
95
BMC IWC See BMC Impact Web Console. BMC Impact Database Gateway (BMC IDG) The interface that enables BMC Impact Manager events to be exported to a relational database. BMC Impact Explorer (BMC IX) A console with which you can connect to any number of BMC Impact Managers, examine the events stored in them, and perform event and service management activities. BMC Impact Explorer Server (BMC IXS) The configuration server that administrators use to manage user access to BMC Impact Managers resources. The BMC Impact Explorer Server runs as a daemon on Unix platforms and as a service on the supported Windows platforms. Synonym: MCCS. BMC Impact Integration (BMC II) product An interface that enables the synchronized, bidirectional flow of events and data between a BMC Impact Manager instance and another BMC Software product or a specific third-party product. BMC Impact Manager (BMC IM) The BMC Impact product that provides automated event and service-impact management. It runs as a service on supported Windows platforms and as a daemon on Unix platforms, and can be distributed throughout a networked enterprise and connected in various topologies to support IT goals. BMC Impact Web Console (BMC IWC) The HTML GUI for service-model component monitoring and reporting that allows access to business views of the environment. BMC IX See BMC Impact Explorer. BMC IXS See BMC Impact Explorer Server.
C
cell The event processing engine that collects, processes, and stores events within a BMC Impact Manager instance. Each cell uses the information in the associated Knowledge Base to identify the type of events to accept and how to process and distribute them. child collector A collector contained within another collector.
96
PATROL Enterprise Manager Console Server Connection User Guide
class A BAROC-language data structure that defines a type of object used in BMC Impact Manager. A class is made up of data fields, called slots, that define its properties. collector An event grouping whose content is defined by its collector rule. Collectors are displayed in the BMC Impact Explorer and are defined in the BMC Impact Manager Knowledge Base. See also collector rule. collector rule A type of rule defined in the Knowledge Base that defines how events from a cell are organized and presented in the BMC Impact Explorer. Collector definitions are written in Master Rule Language (MRL). collector set A group of collectors, organized in a parent-child hierarchy, that performs progressive filtering of those incoming events that match the top-level (parent collector) criteria. A collector set selects a set of events and organizes them for display in the BMC Impact Explorer. Common Connect Back End A core component that resides on the console server. It manages the consumer and provider nodes that are created to handle events on behalf of Common Connect clients. It implements event handlers, object and event filters, and scheduling activities. Common Connect client A PATROL Console, PATROL Integration product, or third-party vendor application that exchanges events and integrates with a PATROL Console Server that has the Common Connect Back End component installed. Common Connect configuration utility A standalone, platform-independent, Java-based client with a graphical user interface. The Common Connect configuration utility is essential to the configuration of Common Connect clients. The configuration utility enables you to
s s
define configuration files that are unique to each Common Connect client define management profiles that specify the PATROL Agent, and Common Connect clients that you want to monitor; apply event filters to PATROL Common Connect client events; and set scheduling intervals in which to receive or block events originating from PATROL and Common Connect clients
Common Connect server The Common Connect program that awaits and fulfills requests from Common Connect clients in the same or other computers. The Common Connect server and the Common Connect Back End reside on the PATROL Console Server.
Glossary
97
common service A computer that processes data from managed systems and facilitates communications between managed systems and console systems. See also console system and managed system. configuration file The configuration file defines the keywords that determine how the PATROL Integration server communicates with the PATROL Integration client. console See BMC Impact Explorer. console server A server through which PATROL Central communicates with managed systems. A console server handles requests, events, data, communications, views, customizations, and security. console system A computer that hosts user desktop applications, such as consoles, viewers, and Web browsers. See also common service and managed system.
D
Delete phase The event-processing phase in which Delete rules are evaluated and actions are taken to ensure that data integrity is maintained when an event is deleted from the repository during the cleanup process. Delete rule An event-processing rule that is used to clean up obsolete information when an event is deleted from the repository. Delete rules are evaluated when an event is deleted, and they take actions to ensure that data integrity is maintained. distribution CD or tape A CD or tape that contains a copy of one or more BMC Software products and includes software and documentation (user guides and online help systems). dynamic collector A special type of collector that, in response to events, can add or remove event collectors from the cell during runtime.
E
environment variable A variable used to specify settings, such as the program search path for the environment in which PATROL runs. You can set environment variables for computer classes, computer instances, application classes, application instances, and parameters.
98
event 1) An occurrence or change in a monitored object or application. An event can be a user action or a system occurrence. 2) BMC II for PATROL captures events by collecting messages from the managed systems. 3) In PATROL, the occurrence of a change, such as the appearance of a task icon, the launch of a recovery action, the connection of a console to an agent, or a state change in a monitored object (computer class, computer instance, application class, application instance, or parameter). Events are captured by the PATROL Agent, stored in an event repository file, and forwarded to BMC II for PATROL. event class A BAROC class that is a child of the base event class, EVENT, and that defines a type of event. Event Diary The part of an event manager (PEM) where you can store or change comments about any event in the event log. You can enter commands at any time from the PATROL Event Manager Details window. event manager A graphical user interface for monitoring and managing events. The event manager can be used with or without the PATROL Console. event message A text message related to a PATROL event, such as PATROL Integration Warning: Host node disconnected - [host name]. event propagation The act of forwarding events and maintaining their synchronization among multiple BMC Impact Managers. event repository See repository. event type The PATROL-provided category for an event according to a filtering mechanism in an event manager. Event types include information, state change, error, warning, alarm, and response. Events View The BMC Impact Explorer user interface for viewing and manipulating event data. Execute phase The event-processing phase in which Execute rules are evaluated and, if conditions are met, specified actions are performed.
Glossary
99
Execute rule An event-processing rule that performs actions when a slot value changes in the event repository. Execute rules are evaluated during the Execute phase of event processing. Often, the resulting actions are internal actions, but you can use the execute primitive in a rule to call an external executable.
F
Filter phase The event-processing phase in which Filter rules are evaluated to determine which events need additional processing or are unneeded and are to be discarded. Filter rule An event-processing rule that determines whether a specific type of event should be passed as is, subjected to further processing, or discarded as unwanted during the Filter phase.
I
interface class A BAROC class that defines the programming interface used by an MRL rule primitive, such as get_external, to return data from an external program. At cell startup, an interface class is loaded into memory. The cell invokes the executable defined in an argument of the primitive. The executables value is returned by the interface. internal base class A BAROC internal class that defines the required structure for the base class from which a group of product classes is derived. internal event An event that is created by the cell during event processing. An internal event is processed in the same way as an incoming event. All internal events are processed before any new incoming external events are processed.
K
kb directory The default directory in which a BMC Impact Manager Knowledge Base is located. The directory and basic product definitions are created during installation. key The seed encryption key. If the destination BMC Impact Manager or BMC Impact Integration product has a key value, all clients must encrypt their communications using the same key value. Knowledge Base (KB) A collection of information that forms the intelligence of a BMC Impact Manager instance and enables it to process events and perform service-impact-management activities. This
100 PATROL Enterprise Manager Console Server Connection User Guide
information includes event class definitions, Service-Model component definitions, record definitions, interface definitions, collector definitions, data associations, and processing rules. Knowledge Module (KM) A set of files from which a PATROL Agent receives information about resources running on a monitored computer. A KM file can contain the actual instructions for monitoring objects or simply a list of KMs to load. KMs are loaded by a PATROL Agent and a PATROL Console. KMs provide information for the way monitored computers are represented in the PATROL interface, for the discovery of application instances and the way they are represented, for parameters that are run under those applications, and for the options available on object pop-up menus. A PATROL Console in the developer mode can change KM knowledge for its current session, save knowledge for all of its future sessions, and commit KM changes to specified PATROL Agent computers.
L
.load file A file that specifies the order in which a directorys files are to be loaded and read by a BMC Impact Manager instance.
M
managed object Any object that PATROL manages. See parameter. managed object file (MOF) A file that contains keyword and event attribute values for a PATROL Integration module. These values define how the integration module interacts with a Common Connect client and the Common Connect environment. managed system A systemusually a computer on which a PATROL Agent is runningthat is added (connected) to a PATROL Console to be monitored and managed by PATROL and that is represented by an icon on the PATROL interface. A system with resources that are managed or monitored by a BMC Software product, such as a computer on which a PATROL Agent is running. See also console system and common service. management event Events which are not displayed but which change the status of a current event (such as changing from open to acknowledge). management profile A user profile for PATROL Central that is stored by the console server. A management profile is similar to a session file and contains information about custom views, your current view of the PATROL environment, information about systems that you are currently managing,
Glossary 101
Knowledge Module information, and console layout information for PATROL Central. Management profiles replace desktop files and session files that were used in PATROL 3.x and earlier. manifest.kb A central locator file that specifies the locations of the directories that make up a Knowledge Base. The manifest.kb file is used by the compiler to load the Knowledge Base source files for compilation. MAP file A text file that defines the translation of a message between one event format and another. Master Rule Language (MRL) A compact, declarative language used to define rules and collectors for processing and organizing events. Uncompiled rule and collector source files have a .mrl file extension. mccomp The rules compiler. Rules are written in the Master Rule Language (MRL). The platform-independent compiler converts them to byte code that the cell can read and process. mcell.conf file The configuration file that contains configuration options for a BMC Impact Manager instance. It is in the $MCELL_HOME/etc/ directory on Unix platforms and in the %MCELL_HOME%\etc\ directory on supported Windows platforms. mcell.dir file The file that lists the cells to which a product component can connect and communicate. The information for each cell includes: its name, its encryption key, and its host name and port number. This file is in the $MCELL_HOME/etc/ directory on Unix platforms and in the %MCELL_HOME%\etc\ directory on supported Windows platforms. mcell.modify file The file that lists the slots that affect the mc_modification_date slot. When a specified slot is modified, the time stamp of the modification is reset in the mc_modification_date slot. mcell.propagate file The configuration file that specifies the slot values that are synchronized during event propagation between cells. It is in the $MCELL_HOME/etc/ directory on Unix platforms and in the %MCELL_HOME%\etc\ directory on supported Windows platforms. mcell.trace file The configuration file that specifies the BMC Impact Manager trace information that should be recorded and the location to which it is written. It is in $MCELL_HOME/etc/ directory on Unix platforms and in the %MCELL_HOME%\etc\ directory on supported Windows platforms. metaclass See internal base class.
102
MetaCollector A virtual collector that contains a group of collectors from multiple BMC Impact Manager instances. It exists only in the BMC Impact Explorer, and you can customize it. .mrl file A file that contains rule and collector definitions written in the Master Rule Language (MRL). Event and service management processing rules and collectors are stored in .mrl files, and in compiled .wic files.
N
New phase The event-processing phase in which the New rules are evaluated to determine which events in the repository should be updated with new information from new incoming events. This is the last opportunity to prevent an event from entering the repository. New rule An event processing rule that is evaluated during the New event processing phase, and can update events stored in the repository (mcdb) with fresh information from new incoming events. node A BMC Impact Manager instance that can receive only events originating on the local host system.
O
open event An event that may require action. An OPEN status indicates that an event has not yet been examined, or that neither an operator nor an automated process has been assigned responsibility for the event.
P
parameter The monitoring element of PATROL. Parameters are run by the PATROL Agent; they periodically use data collection commands to obtain data on a system resource and then parse, process, and store that data on the computer that is running the PATROL Agent. Parameters can display data in various formats, such as numeric, text, stoplight, and Boolean. Parameter data can be accessed from a PATROL Console, PATROLVIEW, or an SNMP console. Parameters have thresholds and can trigger warnings and alarms. If the value returned by the parameter triggers a warning or an alarm, the PATROL Agent notifies the PATROL Console and runs any recovery actions associated with the parameter. parent collector A collector that contains child collectors to form a collector set.
Glossary
103
PATROL Agent The core component of PATROL architecture. The agent is used to monitor and manage host computers and can communicate with the PATROL Console, a stand-alone event manager (PEM), PATROLVIEW, and SNMP consoles. From the command line, the PATROL Agent is configured by the pconfig utility; from a graphical user interface, it is configured by the xpconfig utility for Unix or the wpconfig utility for Windows. PATROL application The object classfor example, CPU, printer, or diskto which an instance and related parameters belong. In the object hierarchy, an application belongs to a specific computer or node. PATROL Console The graphical user interface from which you launch commands and manage the environment monitored by PATROL. The PATROL Console displays all of the monitored computer instances and application instances as icons. It also interacts with the PATROL Agent and runs commands and tasks on each monitored computer. The dialog is event-driven so that messages reach the PATROL Console only when a specific event causes a state change on the monitored computer. A PATROL Console with developer functionality can monitor and manage computer instances, application instances, and parameters; customize, create, and delete locally loaded Knowledge Modules and commit these changes to selected PATROL Agent computers; add, modify, or delete event classes and commands in the Standard Event Catalog; and define expert advice. A PATROL Console with operator functionality can monitor and manage computer instances, application instances, and parameters and can view expert advice but not customize or create KMs, commands, and parameters. PATROL event class A category of events that you can create according to 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. PATROL provides a number of event classes in the Standard Event Catalog, such as worst application and registered application. PATROL instance A computer or discovered application that is running in an environment managed by PATROL. An instance has all the attributes of the class that it belongs to. A computer instance is a monitored computer that has been added to the PATROL Console. An application instance is discovered by PATROL. phase (rule) A specific stage of event processing. There are eight sequential phases to event processing and two nonsequential phases, each with a corresponding rule type.
104
port A number that designates a specific communication channel in TCP/IP networking. Ports are identified by numbers. BMC Impact Manager communicates using the ports specified during installation. Propagate phase The event-processing rule phase in which Propagate rules are evaluated to determine the events to be forwarded to another cell or to an Integration product. Propagate rule An event-processing rule that is used to forward events to other BMC Impact Managers in the managed domain. Propagate rules are evaluated during the Propagate phase of event processing. propagated event An event that is forwarded from one cell to another cell or to an Integration product during the Propagate phase of event processing. propagation The transmission of status values from underlying objects up to their parent objects for example, the transmission of an alert from the parameter level up to the node level.
R
recovery action A procedure that attempts to fix a problem that caused a warning or alarm condition. A recovery action is defined within a parameter by a user or by PATROL and triggered when the returned parameter value falls within a defined alarm range. Refine rule A rule evaluated during the first phase of event processing to validate an incoming event and, if necessary, to collect any additional data needed before further processing can occur. Regulate phase The event-processing phase, in which Regulate rules are evaluated and, if true, collect duplicate events for a time period and, if a specified threshold of duplicates is reached, passes an event to the next processing phase. Regulate rule An event processing rule that processes repetitive (duplicate) events or events that occur with a specified frequency. With a Regulate rule, you can create a new event based on the detection of repetitive or frequent events. See also Regulate phase. repository The storage facility in which event information is stored.
Glossary
105
RTserver cloud Linking of multiple RTservers in your PATROL environment to provide flexibility and load balancing. If an RTserver in your environment fails, another RTserver in the RTserver cloud picks up the load and the PATROL components continue to communicate. rule A conditional statement that, if determined to be true, executes actions. The cell evaluates events by comparing each event to a series of rules during event processing. Rules are grouped in phases that are processed one by one. The order in which rules are evaluated during a particular phase is based on the order in which they were loaded. When all the rules in one phase are evaluated, the cell moves to the next phase. rule engine See cell. rule type A designation of a rule that applies to a specific phase of event processing. The cell processes rules within the context of the associated event-processing phase and in the order in which the rules were loaded from the rule file.
S
server The computer program that provides services to other computer programs on the same or different computers. It fulfills the requests made by the client programs. Also, server refers to the computer on which the server program runs. See also client. Service Level Agreement (SLA) An agreement that defines the required availability of a business service to its consumers. service-level- agreement component A type of Service Model component that represents service-level agreements and metrics. service level metric (SLM) A measurement of some aspect of service delivery. Service Model (SM) An extensible system for defining the various resources that combine to deliver business services, for modeling their behaviors and functional relationships, and for managing the delivery of the resulting services. Service-Model component (SMC) A logical or physical resource that participates in the delivery of services. There are four types of Service-Model components: connectivity components, IT components, logical components, and service level agreement components. An SMC can provide services to or consume services from another component. In technical terms, a Service-Model component is any data class that is a subclass of the MC_SM_COMPONENT base class.
106
Service-Model-component relationship The association of two Service-Model components. There are two types of component relationships: impact and null. See also impact relationship, null relationship. Services View The BMC Impact Explorer user interface for viewing Service-Model components and their relationships and for viewing and managing the events that affect service availability. shadow component A component that is a copy of a component existing on another cell. Shadow components are used when setting up distributed Service Models. slot An attribute in a BAROC class definition. A class definition consists of one or more slots. Each slot has a data type and can have specific attributes, called facets, that can control the values that the slot can have or control aspects of a class instances processing. A class that is a subclass to another class inherits all the slots of the parent class. slot change The process of updating the slot value of a class instance. slot propagation The process by which slot changes are synchronized among cells. slot value The value associated with a particular slot (attribute) of a class instance. slot value pair A slot name and its associated slot value. SM See Service Model. SMC See Service Model component. statbld.conf file The configuration file for the StateBuilder utility. It is in the $MCELL_HOME/etc/ directory on Unix platforms and in the %MCELL_HOME%\etc\ directory on supported Windows platforms. statbld.trace file The configuration file that specifies the trace information to be collected for the StateBuilder utility and where it should be written. It is in the $MCELL_HOME/etc/ directory on Unix platforms and in the %MCELL_HOME%\etc\ directory on supported Windows platforms.
Glossary
107
state The condition of an object (computer instance, application instance, or parameter) monitored by PATROL. The most common states are OK, warning, and alarm. Object icons can show additional conditions. See also state change action. StateBuilder utility The utility, statbld, that periodically consolidates the data in a cells transactions file (xact) and writes the saved state of the cell to a repository (mcdb). state change action An action that is stored, maintained, and initiated by the PATROL Console when the console is notified by the PATROL Agent that a monitored object has changed state. The action, or command, executes on the computer on which the console is running, not the computer on which the agent is running. status
s
For events, an indication of the events management. Possible values are: Open, Acknowledged, Closed. For Service-Model components, an indication of the relative availability of an IT resource. Possible values are: Unavailable, Impacted, At Risk, Maintenance, Available, Unknown, None.
store and forward A mechanism that ensures that if an event cannot reach its destination, it is saved in a file and sent when a viable connection to the destination becomes available. stored event An event that has been processed by the cell and stored in the event repository. Only stored events are returned by queries and are: displayed in BMC Impact Explorer, returned by the mquery CLI command, or referenced by the Using and Update clauses of an MRL rule.
T
Timer phase The event-processing phase in which Timer rules for the delayed execution of another rule type are evaluated. This phase spans the New, Abstract, Correlate, and Execute phases of event processing. Timer rule An event-processing rule that triggers the delayed execution of another type of rule.
U
Update phase See New phase.
108 PATROL Enterprise Manager Console Server Connection User Guide
Using clause An MRL rule clause used to access dynamic data and to query events.
W
warning An indication that a parameter has returned a value that falls within the warning range. See also alarm. wildcard A type of pattern matching that uses the asterisk character (*) to represent any number of different characters, and the question mark character (?) to represent a single unknown character.
Glossary
109
110
Index
Symbols
$CC_HOME 20 $MCELL_HOME 20 %CC_HOME% 20 %MCELL_HOME% 20 definition formats 54, 55 BMC Software Common Installation utility Review Selections and Install page 31 BMC Software, contacting 2 buffering buffer, maximum size 84 MessageBufferReconnectInterval parameter 84 MessageBufferSize parameter 84 reconnect interval 84
A
ACK BMC IM event status 69 action PATROL recovery 92 adapter_host slot, event class 71 alarm PATROL event 90 alarm events PATROL KM for Event Management 93
C
CC_HOME 20 -cell 60 cell BMC IM instance 12 -cfgid 60 client configuration file 47 client executable 62 Client Runtime 15 CLOSED BMC IM event status 69 commands ./uninstall.sh 35 echo $CC_HOME 32 Common Connect Back End and configuration 15 configstart.bat 42 configuration files multiple files, using 55 parameters 82 TraceConfigFileName parameter 87 Configuration Wizard closing 47 Configuration Change Complete page 47 Connect to RT Server(s) page 42, 46 defining client configuration files 42, 45 Edit Client Attributes page 47 Open/Create Configuration page 47 Provide User Credentials page 42, 46 Select Common Connect Client page 46 Select Configuration page 43, 46 starting 42, 45 configuring configuration file parameters 82
B
Basic C APIs multiple integration instances 55 batch files configstart.bat 42 BMC II for PATROL events, duplicate 92 installation, supported platforms 19 MC_ADAPTER_CONTROL event 73 MC_ADAPTER_ERROR event 73 MC_ADAPTER_START event 73 monitor event load 64 recovery action, PATROL 92 validate operations on Unix 63 validate operations on Windows 64 BMC IM event status 69 ACK 69 CLOSED 69 OPEN 69 BMC IM instance cell 12 BMC IM severity status CRITICAL 69 OK 69 BMC Impact Manager
Index
111
multiple integration instances 55 Trace parameter 87 TraceConfigFileName parameter 87 TraceDefaultFileName parameter 87 TraceFileAppend parameter 88 TraceFileHistory parameter 88 TraceFileSize parameter 87 TraceSrc parameter 87 connecting maximum reconnect interval 84 to Impact Managers 54, 55 ConnectionPortRange configuration parameter description 83 ConnectionPortReuse configuration parameter 83 ConnectionSetupTimeOut configuration parameter 82 CRITICAL BMC IM severity status 69 -cserver 60 customer support 3
F
-f 60
H
-help 61
I
-imConfFile 61 initializing multiple integration instances 55 -install 61 installation platforms supported 19 -instance 61 integrations multiple instances, running 55
D
-debug 60 defining BMC Impact Manager instances 54, 55 deploying procedures for multiple integration instances 55 directories $PATROL_ROOT/log/cserver/cc_client_config/ 47 /opt/bmc 28 \Program Files\BMC Software 28 duplicate events BMC II for PATROL 92
K
KM. See Knowledge Module Knowledge Module. See KM
M
managed system and configuration 15 management profile creating a duplicate 44 defining 44 MC_ADAPTER_CONTROL BMC II for PATROL event 73 MC_ADAPTER_ERROR BMC II for PATROL event 73 MC_ADAPTER_START BMC II for PATROL event 73 MC_ADAPTER_STOP 73 mc_host slot, event class 72 mc_host_address slot, event class 68, 72 mc_host_class event class slot 72 slot, event class 72 mc_object slot, event class 72 mc_object_class slot, event class 72 mc_origin slot, event class 72 mc_origin_class slot, event class 72
E
editing mcell.dir file 54, 55 encryption Encryption parameter 83 Encryption configuration parameter 83 event alarm, PATROL 90 state change, PATROL 90 event class, BMC II for PATROL slot 71 event load monitor, BMC II for PATROL 64 event status BMC IM 69 PATROL 69 events PATROL KM for Event Management alarm 93 events, duplicate BMC II for PATROL 92
112
mc_origin_key slot, event class 72 mc_origin_sev slot, event class 72 mc_parameter slot, event class 72 mc_parameter_value PATROL KM for Event Management slot 70 mc_tool slot, event class 72 mc_tool_class slot, event class 72 mc_tool_key slot, event class 72 mc_tool_sev slot, event class 72 mcell.dir file defining BMC Impact Manager instances 54, 55 editing 54, 55 MCELL_HOME 20 MessageBufferKeepSent configuration parameter 84 MessageBufferKeepWait configuration parameter 84 MessageBufferReconnectInterval configuration parameter description 84 MessageBufferResendCount configuration parameter 84 MessageBufferSize configuration parameter description 84 messages buffer, capacity 84 Microsoft Internet Explorer 18 -mprofile 61 multithreading UseLocks parameter requirement 88 PATROL_EV event class slot 68 p_application PATROL_EV event class slot 68 p_args PATROL_EV event class slot 68 p_catalog PATROL_EV event class slot 68 p_class PATROL_EV event class slot 68 p_expectancy PATROL_EV event class slot 68 p_instance PATROL_EV event class slot 69 p_origin PATROL_EV event class slot 69 p_source_id PATROL_EV event class slot 69 p_status PATROL_EV event class slot 69 p_type PATROL_EV event class slot 69 parameters configuration file 82 ConnectionPortRange 83 ConnectionPortReuse 83 ConnectionSetupTimeOut 82 Encryption 83 MessageBufferKeepSent 84 MessageBufferKeepWait 84 MessageBufferReconnectInterval 84 MessageBufferResendCount 84 MessageBufferSize 84 PersistencyCleanupGarbageThreshold 85 PersistencyCleanupSizeThreshold 85 PersistencyDisconnectRemoveMessages 86 PersistencyEnabled 85 PersistencyFileName 85 PersistencyLevel 85 ServerDirectoryName 82 TraceConfigFileName 87 TraceDefaultFileName 87 TraceFileAppend 88 TraceFileHistory 88 TraceFileSize 87 TraceSrc 87 UseLocks 88 PATROL alarm event 90 event class PATROL_EV 12 recovery action 92 recovery action in BMC II for PATROL 92 state change event 90 PATROL Agent 18 up, down events 92 PATROL Console Server 18 and installation 15 specifying a server for connection 42, 46
N
Netscape Navigator 18
O
OK BMC IM severity status 69 OPEN BMC IM event status 69 operations, validate BMC II for PATROL on Unix 63 BMC II for PATROL on Windows 64
P
p_agent PATROL_EV event class slot 68 p_agent_address PATROL_EV event class slot 68 p_agent_port
Index
113
PATROL event status 69 PATROL KM for Event Management alarm events 93 PATROL_EV event class PATROL, 12 persistency parameters 85 PersistencyCleanupGarbageThreshold configuration parameter 85 PersistencyCleanupSizeThreshold configuration parameter 85 PersistencyDisconnectRemoveMessages configuration parameter 86 PersistencyEnabled configuration parameter 85 PersistencyFileName configuration parameters 85 PersistencyLevel configuration parameter description 85 pes PATROL KM for Event Management slot 70 pes_alarm_max PATROL KM for Event Management slot 71 pes_alarm_min PATROL KM for Event Management slot 71 pes_alert_date PATROL KM for Event Management slot 70 pes_alert_time PATROL KM for Event Management slot 70 pes_ave10 PATROL KM for Event Management slot 71 pes_icon_name PATROL KM for Event Management slot 70 pes_last10 PATROL KM for Event Management slot 70 pes_last10_tp PATROL KM for Event Management slot 71 pes_last10_ts PATROL KM for Event Management slot 71 pes_param_status PATROL KM for Event Management slot 70 pes_parent_instance PATROL KM for Event Management slot 70 pes_patrol_home PATROL KM for Event Management slot 71 pes_tcp_port PATROL KM for Event Management slot 70 pes_tz PATROL KM for Event Management slot 70 pes_udp_port PATROL KM for Event Management slot 70 pes_user_defined PATROL KM for Event Management slot 71 platforms installation of BMC II for PATROL 19 procedure verifying the setting of the CC_HOME environment variable 31 procedures deploying multiple integration instances 55 editing mcell.dir file 54, 55 product support 3 propagation MessageBufferKeepSent parameter 84 MessageBufferKeepWait parameter 84 MessageBufferReconnectInterval parameter 84 MessageBufferResendCount parameter 84 MessageBufferSize parameter 84 parameters list 84
R
receive thread UseLocks parameter requirement 88 recovery action, PATROL 92 recovery action PATROL, in BMC II for PATROL 92 -remove 61 RTserver 18, 61 specifying a server for connection 46 -rtserver 61
S
security level 19 ServerDirectoryName configuration parameter 82 severity slot, event class 71 slot adapter_host, event class 71 BMC II for PATROL event class 71 event class mc_host_class 72 mc_host, event class 72 mc_host_address, event class 68, 72 mc_object, event class 72 mc_object_class, event class 72 mc_origin, event class 72 mc_origin_class, event class 72 mc_origin_key, event class 72 mc_origin_sev, event class 72 mc_parameter, event class 72 mc_tool, event class 72 mc_tool_class, event class 72 mc_tool_key, event class 72 mc_tool_sev, event class 72 severity, event class 71 status, event class 71 slots PATROL KM for Event Management mc_parameter_value 70 pes 70 pes_alarm_max 71 pes_alarm_min 71
114
pes_alert_date 70 pes_alert_time 70 pes_ave10 71 pes_icon_name 70 pes_last10 70 pes_last10_tp 71 pes_last10_ts 71 pes_param_status 70 pes_parent_instance 70 pes_patrol_home 71 pes_tcp_port 70 pes_tz 70 pes_udp_port 70 pes_user_defined 71 PATROL_EV event class p_agent 68 p_agent_address 68 p_agent_port 68 p_application 68 p_args 68 p_catalog 68 p_class 68 p_expectancy 68 p_instance 69 p_origin 69 p_source_id 69 p_status 69 p_type 69 specifying default trace message destination file 87 integration_name.trace file, path and alternate name 87 locks, when to use 88 trace files, number to save 88 trace files, size 87 trace messages, appending new 88 trace messages, origin 87 trace, enabling 87 state change PATROL event 90 status slot, event class 71 support, customer 3 parameters in Basic C APIs configuration files 87 TraceConfigFileName parameter 87 TraceDefaultFileName parameter 87 TraceFileAppend parameter 88 TraceFileHistory parameter 88 TraceFileSize parameter 87 TraceSrc parameter 87
U
Uninstall pages Review Selections and Uninstall 34 Select Products and Components to Uninstall 34 up, down events PATROL Agent 92 UseLocks configuration parameter description 88
V
validate operations BMC II for PATROL on Unix 63 BMC II for PATROL on Windows 64 verifying $CC_HOME environment variable 31 %CC_HOME% environment variable setting 31 -version 61
T
technical support 3 Trace parameter 87 TraceConfigFileName configuration parameter 87 TraceConfigFileName parameter 87 TraceDefaultFileName configuration parameter 87 TraceFileAppend configuration parameter 88 TraceFileHistory configuration parameter 88 TraceFileSize configuration parameter 87 TraceSrc configuration parameter 87 TraceSrc parameter 87 tracing
Index
115
116
END USER LICENSE AGREEMENT

NOTICE
BY OPENING THE PACKAGE, INSTALLING, PRESSING AGREE OR YES OR USING THE PRODUCT, THE ENTITY OR INDIVIDUAL ENTERING INTO THIS AGREEMENT AGREES TO BE BOUND BY THE FOLLOWING TERMS. IF YOU DO NOT AGREE WITH ANY OF THESE TERMS, DO NOT INSTALL OR USE THE PRODUCT, PROMPTLY RETURN THE PRODUCT TO BMC OR YOUR BMC RESELLER, AND IF YOU ACQUIRED THE LICENSE WITHIN 30 DAYS OF THE DATE OF YOUR ORDER CONTACT BMC OR YOUR BMC RESELLER FOR A REFUND OF LICENSE FEES PAID. IF YOU REJECT THIS AGREEMENT, YOU WILL NOT ACQUIRE ANY LICENSE TO USE THE PRODUCT. This Agreement (Agreement) is between the entity or individual entering into this Agreement (You) and BMC Software Distribution, Inc., a Delaware corporation located at 2101 CityWest Blvd., Houston, Texas, 77042, USA or its affiliated local licensing entity (BMC). You includes you and your Affiliates. Affiliate is defined as an entity which controls, is controlled by or shares common control with a party. IF MORE THAN ONE LICENSE AGREEMENT COULD APPLY TO THE PRODUCT, THE FOLLOWING ORDER OF LICENSE AGREEMENT PRECEDENCE APPLIES: (1) WEB BASED LICENSE AGREEMENT WITH BMC, (2) WRITTEN LICENSE AGREEMENT WITH BMC, (3) SHRINK-WRAP LICENSE AGREEMENT WITH BMC PROVIDED WITH THE PRODUCT, AND (4) THIS ELECTRONIC LICENSE AGREEMENT WITH BMC. In addition to the restrictions imposed under this Agreement, any other usage restrictions contained in the Product installation instructions or release notes shall apply to Your use of the Product. PRODUCT AND CAPACITY. Software means the object code version of the computer programs provided, via delivery or electronic transmission, to You. Software includes computer files, enhancements, maintenance modifications, upgrades, updates, bug fixes, and error corrections. Documentation means all written or graphical material provided by BMC in any medium, including any technical specifications, relating to the functionality or operation of the Software. Product means the Software and Documentation. License Capacity means the licensed capacity for the Software with the pricing and other license defining terms, including capacity restrictions, such as tier limit, total allowed users, gigabyte limit, quantity of Software, and/or other capacity limitations regarding the Software. For licenses based on the power of a computer, You agree to use BMC's current computer classification scheme, which is available at http://www.bmc.com or can be provided to You upon request. ACCEPTANCE. The Product is deemed accepted by You, on the date that You received the Product from BMC. LICENSE. Subject to the terms of this Agreement, as well as Your payment of applicable fees, BMC grants You a non-exclusive, non-transferable, perpetual (unless a term license is provided on an order) license for each copy of the Software, up to the License Capacity, to do the following: A. install the Software on Your owned or leased hardware located at a facility owned or controlled by You in the country where You acquired the license; B. operate the Software solely for processing Your own data in Your business operations; and C. make one copy of the Software for backup and archival purposes only (collectively a License). If the Software is designed by BMC to permit you to modify such Software, then you agree to only use such modifications or new software programs for Your internal purposes or otherwise consistent with the License. BMC grants You a license to use the Documentation solely for Your internal use in Your operations. LICENSE UPGRADES. You may expand the scope of the License Capacity only pursuant to a separate agreement with BMC for such expanded usage and Your payment of applicable fees. There is no additional warranty period or free support period for license upgrades. RESTRICTIONS: You agree to NOT: A. disassemble, reverse engineer, decompile or otherwise attempt to derive any Software from executable code; B. distribute or provide the Software to any third party (including without limitation, use in a service bureau, outsourcing environment, or processing the data of third parties, or for rental, lease, or sublicense); or C. provide a third party with the results of any functional evaluation or benchmarking or performance tests, without BMC's prior written approval, unless prohibited by local law. TRIAL LICENSE. If, as part of the ordering process, the Product is provided on a trial basis, then these terms apply: (i) this license consists solely of a nonexclusive, non-transferable evaluation license to operate the Software for the period of time specified from BMC or, if not specified, a 30 day time period (Trial Period) only for evaluating whether You desire to acquire a capacity-based license to the Product for a fee; and (ii) Your use of the Product is on an AS IS basis without any warranty, and BMC, ITS AFFILIATES AND RESELLERS, AND LICENSORS DISCLAIM ANY AND ALL WARRANTIES (INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT) AND HAVE NO LIABILITY WHATSOEVER RESULTING FROM THE USE OF THIS PRODUCT UNDER THIS TRIAL LICENSE (Trial License). BMC may terminate for its convenience a Trial License upon notice to You. When the Trial Period ends, Your right to use this Product automatically expires. If You want to continue Your use of the Product beyond the Trial Period, contact BMC to acquire a capacity-based license to the Product for a fee. TERMINATION. This Agreement shall immediately terminate if You breach any of its terms. Upon termination, for any reason, You must uninstall the Software, and either certify the destruction of the Product or return it to BMC. OWNERSHIP OF THE PRODUCT. BMC or its Affiliates or licensors retain all right, title and interest to and in the BMC Product and all intellectual property, informational, industrial property and proprietary rights therein. BMC neither grants nor otherwise transfers any rights of ownership in the BMC Product to You. Products are protected by applicable copyright, trade secret, and industrial and intellectual property laws. BMC reserves any rights not expressly granted to You herein. CONFIDENTIAL AND PROPRIETARY INFORMATION. The Products are and contain valuable confidential information of BMC (Confidential Information). Confidential Information means non-public technical and non-technical information relating to the Products and Support, including, without limitation, trade secret and proprietary information, and the structure and organization of the Software. You may not disclose the Confidential Information to third parties. You agree to use all reasonable efforts to prevent the unauthorized use, copying, publication or dissemination of the Product. WARRANTY. Except for a Trial License, BMC warrants that the Software will perform in substantial accordance with the Documentation for a period of one year from the date of the order. This warranty shall not apply to any problems caused by software or hardware not supplied by BMC or to any misuse of the Software. EXCLUSIVE REMEDY. BMCs entire liability, and Your exclusive remedy, for any defect in the Software during the warranty period or breach of the warranty above shall be limited to the following: BMC shall use reasonable efforts to remedy defects covered by the warranty or replace the defective
Software within a reasonable period of time, or if BMC cannot remedy or replace such defective copy of the Software, then BMC shall refund the amount paid by You for the License for that Software. BMC's obligations in this section are conditioned upon Your providing BMC prompt access to the affected Software and full cooperation in resolving the claim. DISCLAIMER. EXCEPT FOR THE EXPRESS WARRANTIES ABOVE, THE PRODUCT IS PROVIDED AS IS. BMC, ITS AFFILIATES AND LICENSORS SPECIFICALLY DISCLAIM ALL OTHER WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. BMC DOES NOT WARRANT THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE, OR THAT ALL DEFECTS CAN BE CORRECTED. DISCLAIMER OF DAMAGES. IN NO EVENT IS BMC, ITS AFFILIATES OR LICENSORS LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES RELATING TO OR ARISING OUT OF THIS AGREEMENT, SUPPORT, AND/OR THE PRODUCT (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, LOST COMPUTER USAGE TIME, AND DAMAGE OR LOSS OF USE OF DATA), EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND IRRESPECTIVE OF ANY NEGLIGENCE OF BMC OR WHETHER SUCH DAMAGES RESULT FROM A CLAIM ARISING UNDER TORT OR CONTRACT LAW. LIMITS ON LIABILITY. BMCS AGGREGATE LIABILITY FOR DAMAGES IS LIMITED TO THE AMOUNT PAID BY YOU FOR THE LICENSE TO THE PRODUCT. SUPPORT. If Your order includes support for the Software, then BMC agrees to provide support (24 hours a day/7 days a week) (Support). You will be automatically re-enrolled in Support on an annual basis unless BMC receives notice of termination from You as provided below. There is a free support period during the one year warranty period. A. Support Terms. BMC agrees to make commercially reasonable efforts to provide the following Support: (i) For malfunctions of supported versions of the Software, BMC provides bug fixes, patches or workarounds in order to cause that copy of the Software to operate in substantial conformity with its thencurrent operating specifications; and (ii) BMC provides new releases or versions, so long as such new releases or versions are furnished by BMC to all other enrolled Support customers without additional charge. BMC may refuse to provide Support for any versions or releases of the Software other than the most recent version or release of such Software made available by BMC. Either party may terminate Your enrollment in Support upon providing notice to the other at least 30 days prior to the next applicable Support anniversary date. If You re-enroll in Support, BMC may charge You a reinstatement fee of 1.5 times what You would have paid if You were enrolled in Support during that time period. B. Fees. The annual fee for Support is 20% of the Softwares list price less the applicable discount or a flat capacity based annual fee. BMC may change its prices for the Software and/or Support upon at least 30 days notice prior to Your support anniversary date. VERIFICATION. If requested by BMC, You agree to deliver to BMC periodic written reports, whether generated manually or electronically, detailing Your use of the Software in accordance with this Agreement, including, without limitation, the License Capacity. BMC may, at its expense, perform an audit, at your facilities, of Your use of the Software to confirm Your compliance with the Agreement. If an audit reveals that You have underpaid fees, You agree to pay such underpaid fees. If the underpaid fees exceed 5% of the fees paid, then You agree to also pay BMCs reasonable costs of conducting the audit. EXPORT CONTROLS. You agree not to import, export, re-export, or transfer, directly or indirectly, any part of the Product or any underlying information or technology except in full compliance with all United States, foreign and other applicable laws and regulations. GOVERNING LAW. This Agreement is governed by the substantive laws in force, without regard to conflict of laws principles: (a) in the State of New York, if you acquired the License in the United States, Puerto Rico, or any country in Central or South America; (b) in the Province of Ontario, if you acquired the License in Canada (subsections (a) and (b) collectively referred to as the Americas Region); (c) in Singapore, if you acquired the License in Japan, South Korea, Peoples Republic of China, Special Administrative Region of Hong Kong, Republic of China, Philippines, Indonesia, Malaysia, Singapore, India, Australia, New Zealand, or Thailand (collectively, Asia Pacific Region); or (d) in the Netherlands, if you acquired the License in any other country not described above. The United Nations Convention on Contracts for the International Sale of Goods is specifically disclaimed in its entirety. ARBITRATION. ANY DISPUTE BETWEEN YOU AND BMC ARISING OUT OF THIS AGREEMENT OR THE BREACH OR ALLEGED BREACH, SHALL BE DETERMINED BY BINDING ARBITRATION CONDUCTED IN ENGLISH. IF THE DISPUTE IS INITIATED IN THE AMERICAS REGION, THE ARBITRATION SHALL BE HELD IN NEW YORK, U.S.A., UNDER THE CURRENT COMMERCIAL OR INTERNATIONAL, AS APPLICABLE, RULES OF THE AMERICAN ARBITRATION ASSOCIATION. IF THE DISPUTE IS INITIATED IN A COUNTRY IN THE ASIA PACIFIC REGION, THE ARBITRATION SHALL BE HELD IN SINGAPORE, SINGAPORE UNDER THE CURRENT UNCITRAL ARBITRATION RULES. IF THE DISPUTE IS INITIATED IN A COUNTRY OUTSIDE OF THE AMERICAS REGION OR ASIA PACIFIC REGION, THE ARBITRATION SHALL BE HELD IN AMSTERDAM, NETHERLANDS UNDER THE CURRENT UNCITRAL ARBITRATION RULES. THE COSTS OF THE ARBITRATION SHALL BE BORNE EQUALLY PENDING THE ARBITRATORS AWARD. THE AWARD RENDERED SHALL BE FINAL AND BINDING UPON THE PARTIES AND SHALL NOT BE SUBJECT TO APPEAL TO ANY COURT, AND MAY BE ENFORCED IN ANY COURT OF COMPETENT JURISDICTION. NOTHING IN THIS AGREEMENT SHALL BE DEEMED AS PREVENTING EITHER PARTY FROM SEEKING INJUNCTIVE RELIEF FROM ANY COURT HAVING JURISDICTION OVER THE PARTIES AND THE SUBJECT MATTER OF THE DISPUTE AS NECESSARY TO PROTECT EITHER PARTYS CONFIDENTIAL INFORMATION, OWNERSHIP, OR ANY OTHER PROPRIETARY RIGHTS. ALL ARBITRATION PROCEEDINGS SHALL BE CONDUCTED IN CONFIDENCE, AND THE PARTY PREVAILING IN ARBITRATION SHALL BE ENTITLED TO RECOVER ITS REASONABLE ATTORNEYS FEES AND NECESSARY COSTS INCURRED RELATED THERETO FROM THE OTHER PARTY. U.S. GOVERNMENT RESTRICTED RIGHTS. The Software under this Agreement is commercial computer software as that term is described in 48 C.F.R. 252.227-7014(a)(1). If acquired by or on behalf of a civilian agency, the U.S. Government acquires this commercial computer software and/or commercial computer software documentation subject to the terms of this Agreement as specified in 48 C.F.R. 12.212 (Computer Software) and 12.211 (Technical Data) of the Federal Acquisition Regulations (FAR) and its successors. If acquired by or on behalf of any agency within the Department of Defense (DOD), the U.S. Government acquires this commercial computer software and/or commercial computer software documentation subject to the terms of this Agreement as specified in 48 C.F.R. 227.7202 of the DOD FAR Supplement and its successors. MISCELLANEOUS TERMS. You agree to pay BMC all amounts owed no later than 30 days from the date of the applicable invoice, unless otherwise provided on the order for the License to the Products. You will pay, or reimburse BMC, for taxes of any kind, including sales, use, duty, tariffs, customs, withholding, property, value-added (VAT), and other similar federal, state or local taxes (other than taxes based on BMCs net income) imposed in connection with the Product and/or the Support. This Agreement constitutes the entire agreement between You and BMC and supersedes any prior or contemporaneous negotiations or agreements, whether oral, written or displayed electronically, concerning the Product and related subject matter. No modification or waiver of any provision hereof will be effective unless made in a writing signed by both BMC and You. You may not assign or transfer this Agreement or a License to a third party without BMCs prior written consent. Should any provision of this Agreement be invalid or unenforceable, the remainder of the provisions will remain in effect. The parties have agreed that this Agreement and the documents related thereto be drawn up in the English language. Les parties exigent que la prsente convention ainsi que les documents qui sy rattachent soient rdigs en anglais.
SW Click EULA 071102
Notes
*47680* *47680* *47680* *47680*

*47680*

BII4P

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BII4P

Uploaded by

Copyright:

Available Formats

BMC Impact Integration for PATROL

Installation and Configuration Guide

Contacting BMC Software

United States and Canada

Outside United States and Canada

Restricted Rights Legend

Support Web Site

Support by Telephone or E-mail

Before Contacting BMC Software

BMC Impact Integration for PATROL 7.1 User Guide

BMC Impact Integration for PATROL 7.1 User Guide

BMC Impact Integration for PATROL 7.1 User Guide

BMC Impact Integration for PATROL 7.1 User Guide

Introduction to BMC Impact Integration for PATROL

Chapter 1 Introduction to BMC Impact Integration for PATROL

BMC II for PATROL Architecture

Events and BMC II for PATROL

BMC Impact Integration for PATROL 7.1 User Guide

BMC II for PATROL Architecture

Chapter 1 Introduction to BMC Impact Integration for PATROL

BMC II for PATROL Architecture

Components Included with BMC II for PATROL

BMC II for PATROL Executable

Common Connect Configuration Utility

BMC Impact Integration for PATROL 7.1 User Guide

BMC II for PATROL Architecture

Common Connect Back End

common Common_Connect Install itools Uninstall

Client Configuration File (optional)

BMC Impact Integration for PATROL 7.1 User Guide

Prerequisite Products and Components

Version version 3.2 or higher version 7.2.36.02 or higher

BMC Impact Integration for PATROL 7.1 User Guide

Operating System Requirements

Installation Location Variables

Installation Location Variables

Installation Planning Worksheet

About the BMC II for PATROL component

BMC Impact Integration for PATROL 7.1 User Guide

Installation Planning Worksheet

Installation Planning Worksheet

BMC Impact Integration for PATROL 7.1 User Guide

Getting Started Quickly

Getting Started Quickly

BMC Impact Integration for PATROL 7.1 User Guide

Getting Started Quickly

Overview of Installing BMC II for PATROL

Overview of Installing BMC II for PATROL

Installing BMC II for PATROL

Before You Begin

BMC Impact Integration for PATROL 7.1 User Guide

Installing BMC II for PATROL

Installing BMC II for PATROL

Select Installation Option Select Type of Installation

Perform one of the following actions:

Specify Installation Directory

BMC Impact Integration for PATROL 7.1 User Guide

Installing BMC II for PATROL

Installation Steps by Window (Part 2 of 3) Enter or Select

Select System Roles

Select Products and Components to Install

Runtime Warning Box

Installing BMC II for PATROL