Bmciiap Ug

BMCImpact Integration for AlarmPoint
User Guide
Supporting
BMC Impact Manager 4.1 BMC Event Manager 4.1 BMC Service Impact Manager 4.1
October 29, 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. DB2 is a registered trademark of International Business Machines Corporation. Oracle is a registered trademark, and the Oracle product names are registered trademarks or trademarks of Oracle 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 AlarmPoint User Guide
About This Book

This book contains detailed information about the BMC Impact Integration for AlarmPoint and is intended for all users. Like most BMC Software documentation, this book is available in printed and online formats. Visit the BMC Software Customer Support page at http://www.bmc.com/support_home to request additional printed books or to view online books and notices (such as release notes and technical bulletins). Some product shipments also include the online books on a documentation CD.
NOTE
Online books are formatted as Portable Document Format (PDF) or HTML files. To view, print, or copy PDF books, use the free Adobe Reader from Adobe Systems. If your product installation does not install the reader, you can obtain the reader at http://www.adobe.com.
The software also offers online Help. To access Help, press F1 within any product, or click the Help button in graphical user interfaces (GUIs).
Related Publications
The following related publications supplement this book and the online Help:
Category Core Documents Document BMC Impact Manager Administrator
Description Describes all procedures for installing, configuring, and running the BMC Impact Manager. Describes all the open issues and changes for BMC Impact Integration for AlarmPoint.
Guide
Notices BMC Impact Integration for AlarmPoint Release Notes
About This Book
Conventions
Conventions
This book uses the following special conventions:
s
All syntax, operating system terms, and literal examples are presented in this typeface. Variable text in path names, system messages, or syntax is displayed in italic text:
testsys/instance/fileName
The symbol => connects items in a menu sequence. For example, Actions => Create Test instructs you to choose the Create Test command from the Actions menu.
Syntax Statements
The following example shows a sample syntax statement:
COMMAND KEYWORD1 [KEYWORD2 | KEYWORD3] KEYWORD4={YES | NO} fileName...
The following table explains conventions for syntax statements and provides examples:
Item Items in italic type represent variables that you must replace with a name or value. If a variable is represented by two or more words, initial capitals distinguish the second and subsequent words. Brackets indicate a group of optional items. Do not type the brackets when you enter the option. A comma means that you can choose one or more of the listed options. You must use a comma to separate the options if you choose more than one option. Braces indicate that at least one of the enclosed items is required. Do not type the braces when you enter the item. Example alias databaseDirectory serverHostName [tableName, columnName, field] [-full, -incremental, -level] (Unix)
{DBDName | tableName} UNLOAD device={disk | tape, fileName | deviceName} {-a | -c} (Unix)
Syntax Diagrams
Item A vertical bar means that you can choose only one of the listed items. In the example, you would choose either commit or cancel. An ellipsis indicates that you can repeat the previous item or items as many times as necessary.
Example {commit | cancel} {-commit | -cancel} (Unix) columnName . . .
Syntax Diagrams
The following figure shows the standard format for syntax diagrams:
statement begins command statement continued on next line
COMMAND
statement continues
required item KEYWORD
optional item
KEYWORD
required choice variableValue variableValue
optional choice
variableValue variableValue
multiple choices
statement ends
variableValue variableValue variableValue variableValue
About This Book
Syntax Diagrams
The following example illustrates the syntax for a DELETE statement. Because the FROM keyword, alias variable, and WHERE clause are optional, they appear below the main command line. In contrast, the tableName variable appears on the command line because the table name is required. If the statement includes a WHERE clause, the clause must contain a search condition or a CURRENT OF clause. (The searchCondition variable appears on the main line for the WHERE clause, indicating that this choice is required.)
DELETE FROM tableName alias
; WHERE searchCondition cursorName CURRENT OF
The following guidelines provide additional information about syntax diagrams:

s
Read diagrams from left to right and from top to bottom. A recursive (left-pointing) arrow above a stack indicates that you may choose more than one item in the stack. An underlined item is a default option. If a diagram shows punctuation marks, parentheses, or similar symbols, you must enter them as part of the syntax. Asterisks are exceptions. An asterisk in a diagram indicates a reference note. In general, MVS commands, keywords, clauses, and data types are displayed in uppercase letters. However, if an item can be shortened, the minimum portion of the MVS command or keyword might be displayed in uppercase letters with the remainder of the word in lowercase letters (for example, CANcel). The following conventions apply to variables in syntax diagrams: Variables typically are displayed in lowercase letters and are always italicized. If a variable is represented by two or more words, initial capitals distinguish the second and subsequent words (for example, databaseName).
Contents
About This Book Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1 Introduction to BMC Impact Integration for AlarmPoint 5 5 6 6 7
15 16 17 17 18 21 23 24 24 24 26 26 29 30 30 30 30 31 33 34 34 35 36 36 39 39 39 39
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC II for AlarmPoint Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Events and BMC II for AlarmPoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Components included with BMC II for AlarmPoint . . . . . . . . . . . . . . . . . . . . . . . . BMC II for AlarmPoint Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2 Planning
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preliminary Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite Products and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3 Installation
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing BMC II for AlarmPoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Install on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Install on a UNIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling BMC II for AlarmPoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Uninstall from a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Uninstall from a UNIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 4 Configuration and Setup
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building AlarmPoint Data in BMC IM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the User Synchronization module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Completing the AlarmPoint Person and Contact Type information . . . . . . . . . . . . . . Configuring Notifications in BMC IM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing the AlarmPoint Server Action Script Set . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Chapter 5
BMC II for AlarmPoint Features
41
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Automatic Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Automatic Stop Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Manual Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Manual Stop Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Standard Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Acknowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Close. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Accept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Reject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Custom Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 PingDevice_mc_host_address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 TraceRoute_mc_host_address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 PingDevice_EventOrigin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 TraceRoute_mc_host_address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Heartbeat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Log file for Heartbeat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Chapter 6 User Synchronization between BMC IM and AlarmPoint 51
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Files Used For User Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Executable Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Before You Run User Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Running User Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Scheduling User Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 For Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 For UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Chapter 7 Troubleshooting 61
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 If There Are Errors During Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 If an Event is Not Propagated to AlarmPoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 If the User Synchronization Module is Not Working . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 If the Heartbeat Service is Not Working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Appendix A Notifications 65
Types of notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 E-mail notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Pager Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Phone Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Fax Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Index 71
10
Figures
BMC II for AlarmPoint functional architecture diagram. . . . . . . . . . . . . . . . . . . . . . . . The Dynamic Data Editor Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notification Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selection Definition for Stop Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notification Policy for Stop Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 37 43 44 45
Figures
11
12
Tables
BMC II for AlarmPoint - Filenames for various platforms. . . . . . . . . . . . . . . . . . . . . . Required Software and Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC II for AlarmPoint Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 24 26 26
Tables
13
14
Chapter
1
16 17 17 18 21
Introduction to BMC Impact Integration for AlarmPoint

1
This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC II for AlarmPoint Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Events and BMC II for AlarmPoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Components included with BMC II for AlarmPoint . . . . . . . . . . . . . . . . . . . . . . . . BMC II for AlarmPoint Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1
15
Overview
Overview
BMC Impact Integration for AlarmPoint (BMC II for AlarmPoint) integrates BMC Impact Manager (BMC IM) and AlarmPoint and enables bidirectional flow of information between them. You can use BMC II for AlarmPoint to synchronize events and the notification status between BMC IM and AlarmPoint. BMC IM provides the core functionality for event management and Service Impact Management. AlarmPoint routes notifications to the appropriate users on any device. BMC II for AlarmPoint provides the ability to notify AlarmPoint users on any device if an event in BMC IM meets the notification criteria. BMC II for AlarmPoint also enables AlarmPoint users to interact remotely with BMC IM through two-way devices to update an event status or fix problems. On a single machine, BMC II for AlarmPoint assumes that there is only one cell to be integrated with AlarmPoint. Even if there is more than one cell running on a machine, only one cell is used for integration with AlarmPoint. If more than one cell has to be integrated with AlarmPoint, then the other cells have to propagate events through the integrated cell.
EXAMPLE
If a machine has the following cells:
s s s
cell_a cell_b cell_c
Integration is installed only for cell_a. If you need to notify AlarmPoint about the events in cell_b and cell_c, then the events from cell_b and cell_c should be propagated through
cell_a.
NOTE
Only events from the cell where BMC II for AlarmPoint is installed can be sent to AlarmPoint.
16
BMC II for AlarmPoint Architecture
BMC II for AlarmPoint Architecture

This section presents the functional architecture of BMC II for AlarmPoint. Figure 1 BMC II for AlarmPoint functional architecture diagram.
Events and BMC II for AlarmPoint

With persistent buffering, you can send events from BMC IM to AlarmPoint and receive notification status from AlarmPoint to BMC IM without losing any information in the transfer process. The time taken to process messages in the buffer, depends on the number of messages to be processed.
Chapter 1
17
Components included with BMC II for AlarmPoint
BMC IM processes the events it receives, and sends them to the AlarmPoint Java Client. The AlarmPoint Java Client forwards the events to the AlarmPoint Server, which notifies the user on the specified notification device. When the user responds to the notification using a two-way device, AlarmPoint Java Client processes the response and sends it to BMC IM, which updates the status of the event based on the user response.

The executable and tar files for BMC II for AlarmPoint have different names for different platforms. They are listed in Table 1. Table 1
File Name WIN-IIAP SUN-IIAP AIX-IIAP HPUX-IIAP
BMC II for AlarmPoint - Filenames for various platforms.

Extension .exe .tar.gz .tar.gz .tar.gz Platform Windows SUN AIX HP-UX
For more information about supported platforms, see Table 3 on page 25. All the files in Table 1 comprise the following components:
s
BAROC and Rule files AlarmPoint Server action script set AlarmPoint Java Client XML response action script Heartbeat service User synchronization module
In addition to these components, the .tar.gz files comprise the install and uninstall shell scripts.
BAROC and Rule Files

BMC II for AlarmPoint creates six files in the BMC IM Knowledge Base (KB): ap_classes.baroc, ap_data.baroc, ap_collector.mrl, ap.mrl, ap_associate.mrl, and ap_actions.mrl.
18
The ap_collector.mrl file is a rule file for creating the AlarmPoint collector. It is required for displaying the BMC IM events that are sent to AlarmPoint. The ap.mrl file is a rule file for updating the status of BMC IM events that are sent to AlarmPoint. When an AlarmPoint user responds to a notification, this file updates the status of the corresponding event in BMC IM. The ap_associate.mrl file is a rule file for stopping notifications in AlarmPoint. It associates an existing event in BMC IM and sends information to AlarmPoint for deleting the action record. In BMC Impact Explorer, the ap_actions.mrl file creates menu commands in the Remote Actions submenu for sending manual notifications and manual stop notifications to AlarmPoint. For more information on accessing Remote Actions, see Manual Notifications on page 46. All files with a .baroc extension are files that contain event class definitions and slot definitions for each class. Such files also reside in the Knowledge Base. The ap_classes.baroc file contains the AP_EVENT event class and the slot definitions that are used in adapting event information obtained from AlarmPoint into the format that a cell can understand and process. The ap_data.baroc file defines the data classes for synchronizing groups and users from BMC IM with AlarmPoint.
AlarmPoint Server Action Script Set

BMC II for AlarmPoint comprises the BMCIMxAP.ppx file, which is the action script set that has to be imported into AlarmPoint. This file includes a set of scripts for different notification devices such as e-mail, fax, pager, and phone. AlarmPoint uses the appropriate script to format the notification message sent to the users. When the users respond to the notification, the script set takes corresponding action such as Acknowledge, Accept, Reject, or Close. The script set can also handle user-defined remote actions such as ping and traceroute.
AlarmPoint Java Client XML Response Action Script

BMC II for AlarmPoint also includes the APAgent.xml file, which is the AlarmPoint Java Client XML response action script. BMC II for AlarmPoint renames the original APAgent.xml file as APAgent_Original.xml, and saves the modified APAgent.xml file in the appropriate location. When an AlarmPoint user responds to a notification, the APAgent.xml file executes the response and updates the corresponding event in BMC IM. The APAgent.xml file also executes the command required for a custom action script and sends the result back to the AlarmPoint user.
Chapter 1
19
Heartbeat Service
BMC II for AlarmPoint creates the Heartbeat service, which checks for loss of connection to BMC IM, AlarmPoint Java Client, and AlarmPoint Server at regular intervals. This service is started automatically when the BMC IM cell is started and it runs as a daemon in UNIX and as a service in Windows. The Heartbeat service has a minimum configurable time of 10 seconds. For more information, see Heartbeat on page 50.
User Synchronization Module

The User Synchronization module synchronizes and updates the number of users or groups in BMC IM and AlarmPoint. For example, if any user or group is added to or deleted from BMC IM, the module adds or deletes a user or group to AlarmPoint. But, if any user or group is added to or deleted from AlarmPoint, the module does not add or delete a user or group to BMC IM. This module uses the UserSyncMain.sh file for cells running the UNIX operating system and the UserSyncMain.bat file for those cells running the Windows operating system. It also uses a set of log files for the synchronization of BMC IM and AlarmPoint. For more details, see User Synchronization between BMC IM and AlarmPoint on page 51.
Install and Uninstall Shell Scripts

The install and uninstall shell scripts are provided to install and uninstall BMC II for AlarmPoint on the UNIX platform.
20
BMC II for AlarmPoint Key Features

Following are the key features of BMC II for AlarmPoint.
s
Sending automatic notifications to AlarmPoint users based on the notification criteria. Defining notification criteria independent of the notification method, which includes wired phones, mobile phones, SMS devices, e-mail, pagers, and fax. Providing standard actions such as Acknowledge, Accept, Close and Reject on two-way devices. The two-way devices comprise phone, two-way pager, and email. Configuring and modifying default action scripts to create custom action scripts. Providing information on the status of the notification process in AlarmPoint. Notifying AlarmPoint to stop the notification process when certain user-defined events occur in BMC IM. Detecting loss of connectivity with BMC IM, AlarmPoint Java Client, or AlarmPoint Server. Buffering event messages sent to AlarmPoint Java Client and BMC IM to prevent data loss in case of a temporary loss of connectivity. Synchronizing groups and users from BMC IM with AlarmPoint.
For more information on features, see BMC II for AlarmPoint Features on page 41.
Chapter 1
21
22
Chapter
2
24 24 24 25 25
Planning
This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preliminary Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite Products and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2
Planning
23
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 AlarmPoint. In addition to the detailed information, this chapter includes a worksheet that you can use for planning the installation at your site.
Preliminary Requirements
s
BMC IM, AlarmPoint Java Client, and BMC II for AlarmPoint must be installed on the same machine and the AlarmPoint Primary Server or AlarmPoint Failover Server must be on a different machine. In Windows, AlarmPoint Java Client must be installed as a service and not as an executable. You must run the User Synchronization module immediately after installing BMC II for AlarmPoint. For more information on running the User Synchronization module, see Running User Synchronization on page 55. The recommended screen size for the correct execution of the shell scripts is 1024 * 768 pixels.
Prerequisite Products and Components

Table 2 lists the products and components that must be installed, configured and running in the computing environment before you install BMC II for AlarmPoint. Table 2 Software BMC Impact Manager AlarmPoint Java Client AlarmPoint Server Perl Required Software and Versions Version 4.1 or later 2.0 or later 6.0 or later 5.8.0 or later
NOTE
The required version of Perl is available with the BMC Impact Manager Enabling Components CD.
24
Operating System Requirements
Operating System Requirements

BMC II for AlarmPoint supports the platforms listed in Table 3. Table 3 BMC II for AlarmPoint Supported Platforms
Version Memory 0.5 GB 0.5 GB 0.5 GB 0.5 GB 0.5 GB
Operating System
Windows 2003 Server Windows 2000 Professional Solaris AIX HP-UX
Standard Edition Service Pack 3 8, 9 5.1, 5.2 11.11
NOTE
s s
For the AIX v5.1, you must be in Maintenance Level 5. For the AIX v5.2, you must be in Maintenance Level 3.
Planning Worksheet
Use the worksheet in this section to record information that you will need to provide during the installation and configuration process. Table 4 Planning Worksheet (Part 1 of 2) Response Notes
Information Item or Requirement About BMC II for AlarmPoint

On which operating system are you installing BMC II for AlarmPoint? See Operating System Requirements on page 25. If you are installing BMC II for AlarmPoint on a UNIX machine, what is the root account?
About BMC IM
What is the name of the BMC IM Cell that will be used for BMC II for AlarmPoint?
About AlarmPoint
Chapter 2
Planning
25
Planning Worksheet
Table 4
Planning Worksheet (Part 2 of 2) Response Notes
Information Item or Requirement

What is the path of the AlarmPoint Java Client installation? What is the IP Address or host name of the AlarmPoint Primary Server? What is the IP address or host name of the AlarmPoint Failover Server? Which AlarmPoint User ID should BMC II for AlarmPoint notify when BMC IM is down?
About AlarmPoint Java Client

What is the AlarmPoint Session and Port number for AlarmPoint Java Client? Note: The installation uses the default AlarmPoint Session and Port numbers for the AlarmPoint Java Client.
26
Chapter
3
30 30 30 30 31 33 34 34
Installation
This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing BMC II for AlarmPoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Install on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Install on a UNIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling BMC II for AlarmPoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Uninstall from a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Uninstall from a UNIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 3
Installation
29
Overview
Overview
This chapter provides information about the installation and uninstallation of BMC II for AlarmPoint on cells running the Windows or UNIX operating systems.
Before You Begin

Before you begin the installation, you must check that the cell on which you want to install BMC II for AlarmPoint and the AlarmPoint Java Client is started. For information about operating system requirements and software that needs to be installed before installing BMC II for AlarmPoint, see Planning on page 23. Also, see the Readme.txt file before you begin installation. You must ensure that the APAgent is running as a service prior to installing BMC II for AlarmPoint.
Installing BMC II for AlarmPoint

To Install on a Windows System
1 Double-click the WIN-IIAP.exe file. 2 To accept the End User License Agreement, click Yes. 3 In the Welcome dialog box, click Next. 4 Specify the path where the AlarmPoint Java Client is installed and click Next. 5 In the AlarmPoint Primary Server dialog box, enter the hostname or IP address of
the AlarmPoint Primary Server and click Next. Detecting the AlarmPoint Primary Server might take some time, wait for the next prompt.
6 If a running instance of the AlarmPoint Primary Server is not detected and you
want to proceed with the information entered in step 5, click Yes. To re-enter information entered in step 5, click No.
7 If you know the hostname or IP address of the AlarmPoint Failover Server, click
Yes.
30
To Install on a UNIX System
8 In the AlarmPoint Failover Server dialog box, enter the hostname or IP address of
the AlarmPoint Failover Server and click Next.
9 In the Cell Name dialog box, enter the name of the cell and click Next. 10 In the AlarmPoint UserID dialog box, enter the UserID. This user will be notified
when the BMC Impact Manager goes down.
11 Click Next. 12 Select the Yes, I want to restart my computer now button. 13 Click Finish. NOTE
s s
After the installation, you must restart the computer and not just log off. If you want to upgrade an existing version of BMC II for AlarmPoint, you have to remove the existing installation and then reinstall the upgraded version.

1 Login as root on the target machine. 2 FTP the .tar.gz file to the target machine using the binary mode. 3 Uncompress the .tar.gz file using the following command:
# gzip -d filename.tar.gz
4 Untar the .tar file using the following command:

# tar -xvf filename.tar
This command will create a directory named filename-IIAP. All the files required for the installation of BMC II for AlarmPoint are stored in this directory.
NOTE
The filename will be different for different flavours of UNIX. For more information, see Table 1 on page 18.
5 Run the following command:

cd filename-IIAP
Chapter 3
Installation
31
6 Set $MCELL_HOME properly: A To display the path where cell is installed, run the following command:
echo $MCELL_HOME
B If the path is not displayed in step 6A, then set $MCELL_HOME by executing the
setup_env.sh script from the /etc/mcell/ folder. To do so, use the following
command:
# . /etc/mcell/setup_env.sh
For more information, refer to the BMC Impact Manager Administrator Guide.
7 Run the install.sh script, using the following command:

# ./install.sh
8 Enter the following information: A Name of the cell (for example, abc-xyz-sun07). B Location of the AlarmPoint Java Client (for example, /opt/invoqsystem/APAgent). C The hostname or IP address of the AlarmPoint Primary Server (for example,
abcd2k123).
D If you want to configure the AlarmPoint Failover Server, enter y, else enter n. E If you have entered y in step 8D, then enter the hostname or IP address of the
AlarmPoint Failover Server (for example, abcd2k456). If you have entered n in step 8D, then enter y again to confirm that you do not want to configure the AlarmPoint Failover Server.
F Detecting the Server might take time.

If a running instance of the AlarmPoint Primary or Failover Server is not detected and you want to re-enter the hostname or IP address, enter y. If you want to proceed with the information entered previously, enter n.
G The AlarmPoint User ID. A notification will be sent to this user when the cell is
down.
9 Set the path using the following command:

. $MCELL_HOME/BMCIIAP/setup_apclient_env.sh
32
Uninstalling BMC II for AlarmPoint
NOTE
s s
This environment variable must be set before you start the BMC IM cell. Before you start the AlarmPoint Agent, you must include the MCELL_HOME directory in the path. BMC II for AlarmPoint will not work if the environment variables are not set correctly.
10 Restart the cell (For more information, refer to the BMC Impact Manager User
Guide). Install will create a folder named BMCIIAP at the following location:
$MCELL_HOME.
WARNING
For machines running the UNIX operating system, a machine might reboot if the administrator has scheduled automated system maintenance. In such a case, you have to follow step 6B on page 32 and step 9 on page 32. Then, you must run the cell and the AlarmPoint Java Client for BMC II for AlarmPoint to function properly.
Uninstalling BMC II for AlarmPoint

During the uninstallation of BMC II for AlarmPoint, the heartbeat service is stopped. The following files in the CELLNAME folder are used by heartbeat service and the uninstall script:
s s s s s s s
mposterbuf.lck msend-execute.bat mposterbuf.buf mposterbuf.pos BMCIMxAP-Message.txt BMCIMxAP-send.log BMCIMxAP-execute.txt
In UNIX, the CELLNAME folder is at the following location:

$MCELL_HOME/BMCIIAP/log/$CELLNAME
Chapter 3
Installation
33
To Uninstall from a Windows System
In Windows, the CELLNAME folder is located in the BMC II for AlarmPoint installation folder. Since these files are also used by the heartbeat service, they might not get deleted after running the uninstall script. In such a case, you must manually remove all files except the available_targets_ALARMPOINT_USERS_lastrun and available_targets_ALARMPOINT_GROUPS_lastrun files.
To Uninstall from a Windows System

1 To begin the uninstall process, click Start. 2 Choose Settings => Control Panel. 3 Double-click Add/Remove Programs. 4 Select BMC Impact Integration for AlarmPoint. 5 Click Remove.
To Uninstall from a UNIX System

1 Run the Uninstall script from the BMCIIAP folder, using the following command:
# ./uninstall.sh
2 Enter the name of the cell (for example, abc-xyz-sun1). 3 To complete the uninstallation, press Enter.
34
Chapter
4
36 36 39 39 39 39
Configuration and Setup

This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building AlarmPoint Data in BMC IM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the User Synchronization module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Completing the AlarmPoint Person and Contact Type information . . . . . . . . . . . . . . Configuring Notifications in BMC IM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing the AlarmPoint Server Action Script Set . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 4
35
Overview
Overview
This chapter contains information on configuring BMC II for AlarmPoint. After you have installed BMC II for AlarmPoint, you need to complete a few tasks in the following order:
s
Build AlarmPoint Data in BMC IM Run the User Synchronization module Complete the AlarmPoint Person and Contact Type information Configure Notifications in BMC IM Import the AlarmPoint Action Script set
You only need to ensure that you have completed all the tasks before you start using BMC II for AlarmPoint.
Building AlarmPoint Data in BMC IM

After you have installed BMC II for AlarmPoint, you need to create AlarmPoint groups and users in BMC IM. You cannot edit the data for existing groups and users. If you need to modify the data, you have to delete the relevant group or user and then recreate that group or user. The groups and users that you create need to be synchronized in AlarmPoint on a regular basis. For more information, see Chapter 6, User Synchronization between BMC IM and AlarmPoint.
To Add an AlarmPoint Group in BMC IM: 1 Click Start => Programs => BMC Impact => BMC Impact Explorer. 2 Enter the login details. 3 Click the Administration tab, and then click the Dynamic Data Editor tab.
The Dynamic Data Editor tab is highlighted in Figure 2 on page 37.
36
Figure 2
The Dynamic Data Editor Tab.
4 In the tree structure, navigate to the cell where BMC II for AlarmPoint is installed
and select ALARMPOINT_GROUPS. For example,
MyGroup => Cell => DATA => ALARMPOINT => ALARMPOINT_GROUPS.
NOTE
If the cell on which you have installed BMC II for AlarmPoint, does not exist under MyGroup, then you must create a new group.
5 To add a new data instance, click the Add data instance button. 6 By default N is displayed in the send_root_cause_and_effects field.
send_root_cause_and_effects is useful for sending the user information about the
root cause of a failure and the effect of the failure. It is not supported in this release of BMC II for AlarmPoint. Enter the group_id. The group ID is used to identify groups in BMC II for AlarmPoint. A group is a collection of users.
Chapter 4
37
NOTE
s
The group_id field is mandatory. Valid options for group_type are Broadcast (B) and Hunt (H). You can enter data for the other fields as required.
On running the User Synchronization module, any leading or trailing spaces in group_id are removed.
7 Click OK. To Add an AlarmPoint User in BMC IM: 1 Click Start => Programs => BMC Impact => BMC Impact Explorer. 2 Enter the login details. 3 Click the Administration tab. 4 Click the Dynamic Data Editor tab. 5 In the tree structure, navigate to the cell where BMC II for AlarmPoint is installed
and select ALARMPOINT_USERS. For example,
MyGroup => Cell => DATA => ALARMPOINT => ALARMPOINT_USERS.
6 To add a new data instance, click the Add data instance button. 7 By default, BMC Software and Main Office are displayed in the company_name
and site fields respectively. You need to change the values in these fields based on the information that you have entered when installing AlarmPoint.
WARNING
If the company name and site that you enter for a user does not match the company name and site you have entered when installing AlarmPoint, that user does not get created in AlarmPoint during synchronization.
8 Enter the person_id and click OK. NOTE

s
Only the person_id, company_name, and site fields are mandatory. You can enter data for the other fields as required. It is recommended that you also enter data in the person_name field. On running the User Synchronization module, any leading or trailing spaces in person_id are removed.
38
Running the User Synchronization module
By default, the AlarmPoint users you create in BMC IM are disabled the first time you import them into AlarmPoint, and you need to activate them. For more information on activating users in AlarmPoint, see AlarmPoint User Manual Version 6.0.
Running the User Synchronization module

For more information, see Running User Synchronization on page 55.
Completing the AlarmPoint Person and Contact Type information

For more information, see AlarmPoint User Manual Version 6.0.
Configuring Notifications in BMC IM

You can use the event selector and event policy mechanism available in BMC IM to configure AlarmPoint notifications. Selectors act as a mechanism to select the event, while policies specify the selector, notification method, and users to be notified. Using the Event Management Policies Editor in BMC IM, you can define how an event should be processed by the cell after it has been received. For more information on the Event Management Policies Editor, see BMC Impact Explorer User Guide, BMC Impact Web Console User Guide, or BMC Event Management Administrator Guide.
Importing the AlarmPoint Server Action Script Set

The AlarmPoint Server Action Script Set includes a set of scripts for different notification devices such as e-mail, phone, pager, and fax. BMCIMxAP.ppx is the AlarmPoint Server Action Script Set that comes with the BMC II for AlarmPoint installation pack. You can find the BMCIMxAP.ppx file in the BMCIIAP folder. You have to import this file on the machine where the AlarmPoint Server is installed. Before you can import the BMCIMxAP.ppx file, you need to copy the file to the server. If you have defined both, the AlarmPoint Primary Server and the AlarmPoint Failover Server, then you have to import the BMCIMxAP.ppx file on both the servers.
Chapter 4 Configuration and Setup 39
Importing the AlarmPoint Server Action Script Set
NOTE
You must FTP the BMCIMxAP.ppx file in binary mode only. The file can get corrupted if it is in ASCII mode.
For more information on importing the Action Script Set into AlarmPoint, see AlarmPoint User Manual Version 6.0. After you have imported the BMCIMxAP.ppx file, you need to change the status of each script from Test to Production. By default, the status of the scripts that have been imported into AlarmPoint is Test. For more information on changing the status of the scripts, see AlarmPoint User Manual Version 6.0.
40
Chapter
5
42 42 44 46 46 47 47 47 47 47 48 48 48 48 48 49 50 50
BMC II for AlarmPoint Features

This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic Stop Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual Stop Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acknowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Custom Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PingDevice_mc_host_address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TraceRoute_mc_host_address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PingDevice_EventOrigin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TraceRoute_mc_host_address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Heartbeat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log file for Heartbeat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5 BMC II for AlarmPoint Features
41
Overview
Overview
This chapter provides information about the features of BMC II for AlarmPoint. The following are the important features of BMC II for AlarmPoint:
s
Automatic Notification Manual Notification Standard Actions Custom Actions History Heartbeat
Automatic Notifications
BMC II for AlarmPoint enables you to send Automatic Notifications from BMC IM to AlarmPoint. The event selection criteria determines which events cause notifications to be sent to AlarmPoint. In BMC II for AlarmPoint, you can also send FYI Notifications. To enable Automatic Notifications and FYI Notifications, you must create the following:
s
Notification Service Selector Notification Policy
BMC II for AlarmPoint provides templates for Notification Service, Selector, and Notification Policy. You can create your own Notification Service, Selector, and Notification Policy by referring to these templates. Figure 3 on page 43 shows the creation of a Notification Policy using a notification template in BMC Impact Explorer version 4.1.
42
Automatic Notifications
Figure 3
Notification Template.
Notification Service
The User Synchronization module creates the AlarmPoint and AlarmPoint_FYI services that should be used while sending automatic notifications and automatic FYI notifications respectively. The Notification service is also created at the time of the BMC II for AlarmPoint installation.
Selector
The selection criteria determines which events cause a notification to be sent to AlarmPoint. Selectors are used to set the selection criteria. For example, if the selection criteria is set to CRITICAL events, then only CRITICAL events will cause a notification to be sent to AlarmPoint.
43
Automatic Stop Notification
Notification Policy
In BMC II for AlarmPoint, depending on the Notification Policy, events cause notifications to be sent to AlarmPoint. Selectors are used by the Notification Policy to select events. The Notification Policy decides the users who will receive the notification. It uses the Notification Service to send notifications to users.
NOTE
While creating the Notification Policy, use the AlarmPoint and AlarmPoint_FYI services which are created by the User Synchronization module For more information on Notification Policies, refer to the BMC Event Management Administrator Guide.

Following are the steps to stop automatic notifications from being sent to AlarmPoint:
1 In the Selection Definition section of the Selector, enter the following selection
condition:
is_replied_from_AP==NO
Figure 4
Selection Definition for Stop Notification.
44
2 You must create the following type of Notification Policy:

s
The Notification Policy should be for ACK or Assigned type of events. In the Notification Text box, enter the keyword StopNotification. In the Notify box, enter the User ID to whom the notification is to be sent. Notification Policy for Stop Notification.
Figure 5
NOTE
If you reopen an event and want to stop the notification, you can do so by choosing the Stop Notification in AlarmPoint option in the Remote Actions menu.
45
Manual Notifications
Manual Notifications
Using the following procedure, you can manually send a notification from BMC Impact Explorer to AlarmPoint:
1 To select an event, click on it. 2 Right-click on the selected event. 3 Click Actions => Remote Actions => Notify via AlarmPoint. 4 In the User box, enter the User ID or Group ID of the AlarmPoint user who needs to
be notified.
5 Click Execute. NOTE

Events notified manually, do not go to the collector.
Manual Stop Notification

Similar to sending a manual notification to a user, you can stop a notification using the following procedure:
1 To select an event, click on it. 2 Right-click on the selected event. 3 Click Actions => Remote Actions => Stop Notification in AlarmPoint.
Once you click Stop Notification in AlarmPoint, any notification or escalation for the selected event is stopped in AlarmPoint.
46
Standard Actions
Standard Actions
When you receive a notification on a notification device, you can send a standard action to BMC II for AlarmPoint. BMC II for AlarmPoint updates the status in BMC IM, depending on the type of standard action you send. The four types of standard actions in BMC II for AlarmPoint are:
s
Acknowledge Close Accept Reject
Acknowledge
When you acknowledge a notification using a notification device, BMC II for AlarmPoint will update the status of event to ACK in BMC IM.
Close
When you close a notification using a notification device, BMC II for AlarmPoint will update the status of event to CLOSE in BMC IM.
Accept
When you accept a notification using a notification device, BMC II for AlarmPoint will change the ownership of the event in BMC IM. You are updated as the owner of the event and the status of the event is updated to Assigned.
Reject
When you reject a notification using a notification device, BMC II for AlarmPoint updates the operation log to indicate that you have rejected the event. In BMC IM, the status remains OPEN.
47
Custom Actions
Custom Actions
You can send a custom action to BMC IM from a notification device. BMC IM executes the requested action and sends the result back to the notification device. The four types of custom actions in BMC II for AlarmPoint are:
s
PingDevice_mc_host_address TraceRoute_mc_host_address PingDevice_EventOrigin TraceRoute_EventOrigin
PingDevice_mc_host_address
When you request for this custom action, BMC II for AlarmPoint will ping the host in the mc_host_address slot and send the result back to you.
TraceRoute_mc_host_address
When you request for this custom action, BMC II for AlarmPoint will traceroute the host in the mc_host_address slot and send the result back to you.
PingDevice_EventOrigin
When you request for this custom action, BMC II for AlarmPoint will ping the host in the mc_origin slot and send the result back to you.
TraceRoute_mc_host_address
When you request for this custom action, BMC II for AlarmPoint will traceroute the host in the mc_origin slot and send the result back to you.
48
History
NOTE
The mc_host_address and mc_origin slots are stored in BMC IM.
History
In BMC IM, when a user is notified about a problem through AlarmPoint, the status
of the notification is updated in the events Notification Log section. The actual message, Contact type and User fields are updated in the Notification Log section.
EXAMPLE
s
Message Delivered, Contact type: EMAIL, User: Abc Xyz Started Notification to AlarmPoint, Contact type: EMAIL, User: Abc Xyz
Any error that occurs on the AlarmPoint side is also displayed in the Notification Log section.
EXAMPLE
s
Invalid Person or Group ID '11111' requested. Invalid ScripSet 'BMCIMxAP' requested.
If you respond to a notification using the notification device, your response is updated in the Operations Log section of the event. The following example shows the format of the message that is recorded in the Operations Log section if you respond to a
notification and close the event.
EXAMPLE
9/15/04 9:33 PM by Abc Xyz Message Closed Similar messages are recorded in the Operations Log section of the event for Accept, Reject, and Acknowledge.
49
Heartbeat
Heartbeat
In BMC II for AlarmPoint, the Heartbeat service checks that the BMC IM, AlarmPoint Java Client, AlarmPoint Primary Server, and AlarmPoint Failover Server are running at regular time intervals. If the AlarmPoint Java Client, AlarmPoint Primary Server, or AlarmPoint Failover Server goes down, the Heartbeat service creates a critical event in BMC IM. If BMC IM goes down, then it notifies the AlarmPoint user that BMC IM is down. For more information, see Heartbeat Service on page 20.
Log file for Heartbeat

The Heartbeat service creates the BMCIMxAP_Heartbeat.log file. This file is used to log information for the Heartbeat service and is stored at the following location:
BMCIIAP/log/cellname
The file stores information about when the Heartbeat service is started and when it is stopped. It also stores error information such as, mcell.dir not found or cellname is wrong, and so on.
50
Chapter
6
52 53 55 55 58 58 59
User Synchronization between BMC IM and AlarmPoint

6
This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Files Used For User Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Run User Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running User Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling User Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . For Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . For UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 6
51
Overview
Overview
User Synchronization synchronizes the users and groups between BMC IM and AlarmPoint. The flow of data is from BMC IM to AlarmPoint. Only information which is mandatory to create a user or group in AlarmPoint flows from BMC IM to AlarmPoint. The user or group created in AlarmPoint (through User Synchronization) is in Disabled status. After the user or group is created, other details of the user or group, such as configuration of the notification devices, need to be added later by the AlarmPoint administrator. For more information on adding user details, see AlarmPoint User Manual Version 6.0.
NOTE
s
If you add users or groups in BMC IM, they are reflected in AlarmPoint after running User Synchronization. If you delete users or groups only in AlarmPoint, the change is not reflected in BMC IM even after running User Synchronization. In such a case, BMC II for AlarmPoint will reflect that these users or groups exist even though they are not actually present in AlarmPoint. If you want BMC II for AlarmPoint to show that the users or groups are deleted, then these users or groups have to be deleted from both, AlarmPoint and BMC IM.
User Synchronization synchronizes the users or groups only with the active AlarmPoint Server. If you want to work with the AlarmPoint Primary Server and the AlarmPoint Failover Server at the same time, the AlarmPoint administrator should make sure that both the servers refer to the same database.
52
Files Used For User Synchronization
Files Used For User Synchronization

The following set of files are used for user synchronization between BMC Impact Manager and AlarmPoint:
Executable Files
For Windows
s s s s s
im_notification_service_data.exe sim2ap.exe to_delete.exe sim2ap_delete.exe UserSyncMain.bat
For UNIX
s s s s s
im_notification_service_data.pl sim2ap.pl to_delete.pl sim2ap_delete.pl UserSyncMain.sh
The Lib directory is also required for user synchronization on UNIX machines.
Chapter 6
53
Log files
Log files
All log files are stored at the following location:
BMCIIAP/log/cellname
Following is a list of the log files:

s s s s
APClientResponse.log usersync.log usersync_batch.log im_notification_service_data.log
APClientResponse.log
This file stores the AlarmPoint Client Response corresponding to the addition and deletion of users and groups.
usersync.log
This file contains the output of the UserSyncMain.sh file. If the User Synchronization module does not work, you must check this log file first.
usersync_batch.log
The usersync_batch.log file stores the standard output of User Synchronization. It also stores standard errors that occur when the User Synchronization module is running.
im_notification_service_data.log
Data generated due to failure during creation of a service is stored in the im_notification_service_data.log file.
54
Before You Run User Synchronization
Before You Run User Synchronization

s
User Synchronization requires Perl version 5.8.0 or later. The PATH environment variable should contain the path of the Perl executable.
EXAMPLE
echo $PATH /opt/perl/bin
The PERL5LIB environment variable should contain the path of the lib directory of the Perl version.
EXAMPLE
echo $PERL5LIB /opt/perl/lib/5.8.0
Running User Synchronization

1 Running the command:
s
For Windows: At the command prompt, run the following command: UserSyncMain.bat cell name
For UNIX: At the command prompt, run the following command: UserSyncMain.sh cell name
2 The command in step 1 executes the UserSyncMain.bat or the UserSyncMain.sh file.

These files execute all the other perl or executable files in the following sequence:
Chapter 6
55
A sim2ap.pl
This file is required for addition of users and groups. The usersync.log file stores any errors which occur during the execution of the sim2ap.pl file. The sim2ap.pl file creates an AlarmPoint command string by using information such as the platform of the cell. It sends the AlarmPoint command string to the AlarmPoint manager and gets a response from the AlarmPoint client. It then displays the output to the end user by parsing this response. The following files are used to calculate the number of users or groups to be added:
s s
available_targets_ALARMPOINT_USERS_lastrun available_targets_ALARMPOINT_GROUPS_lastrun
B im_notification_service_data.pl
This file calculates the number of users and groups available. It stores them in the following files:
s s
available_targets_ALARMPOINT_USERS available_targets_ALARMPOINT_GROUPS
The im_notification_data.baroc file is created for the following services:

s s
ALARM POINT NOTIFICATION ALARM POINT NOTIFICATION_FYI
C to_delete.pl This file creates the users_to_delete and groups_to_delete files. The number of users or groups to be deleted in this session of user synchronization are stored in these files.
The following files are used to calculate the number of users or groups to be deleted:
s s s s
available_targets_ALARMPOINT_USERS available_targets_ALARMPOINT_GROUPS available_targets_ALARMPOINT_USERS_lastrun available_targets_ALARMPOINT_GROUPS_lastrun
NOTE
Information regarding the User Synchronization modules last run is stored in these files. These files are used in the current run also. These files are very important and should NOT be deleted.
56
D sim2ap_delete.pl
This file uses the groups_to_delete and users_to_delete files to delete users and groups. The sim2ap_delete.pl file creates an AlarmPoint command string by using information such as the platform of the cell. It sends the AlarmPoint command string to the AlarmPoint manager and gets a response from the AlarmPoint client. It then displays the output to the end user by parsing this response.
E Lib directory
The Time.pm file is stored in this directory. The Time.pm file is a standard library file which manipulates time related operations for the perl files.
NOTE
s
For Windows users: Instead of installing perl, the perl files are converted to executable files using a conversion software. Thus, the Lib directory is not required. The code of the command strings that are sent to the AlarmPoint server or AlarmPoint client and are received from the AlarmPoint Java Client, are different for Windows and UNIX platforms. This is because AlarmPoint treats the Windows and UNIX platforms differently.
Chapter 6
57
Scheduling User Synchronization
Scheduling User Synchronization

For Windows
The procedure to schedule User Synchronization in Windows is as follows:
1 Click Start => Settings => Control Panel. 2 Double-click Scheduled Tasks. 3 In the Scheduled Tasks window, double-click Add Scheduled Task. 4 In the Welcome dialog box, click Next. 5 Click Browse. 6 Select the UserSyncMain.bat file and click Open. 7 Select when you want to perform the task and click Next. 8 Set the Start Time. 9 Select the frequency of performing the task. 10 Set the Start Date and click Next. 11 Enter the user name. 12 Enter the password. 13 Confirm the password and click Next. 14 To complete the procedure of scheduling User Synchronization, click Finish.
58
For UNIX
For UNIX
The procedure to schedule User Synchronization in UNIX is as follows:
1 Add a cron job using the following command:

crontab -e
2 Add the details for scheduling User Synchronization. 3 Save the crontab file and exit using the following command:
:wq
Chapter 6
59
For UNIX
60
Chapter
7
62 62 63 63 64
Troubleshooting
This chapter presents the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If There Are Errors During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If an Event is Not Propagated to AlarmPoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If the User Synchronization Module is Not Working. . . . . . . . . . . . . . . . . . . . . . . . . . . If the Heartbeat Service is Not Working. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7 Troubleshooting
61
Overview
Overview
This section provides troubleshooting information regarding issues that you might encounter while installing, configuring, and using BMC II for AlarmPoint.
If There Are Errors During Installation

s
Read the readme.txt file carefully. Check if there is sufficient disk space available for installation. Check the version of BMC IM. BMC II for AlarmPoint supports version 4.1 or later. Check the version of the AlarmPoint Java Client. BMC II for AlarmPoint supports version 2.0 or later. Check the version of the AlarmPoint Server. BMC II for AlarmPoint supports version 6.0 or later. Check the version of Java. BMC II for AlarmPoint supports version 1.4.0. Check if the path of the environment variables is set correctly. During installation on Windows, if Error Number 1628 is displayed, you must complete the following procedure:
A Close the installation process. B Remove any previous installation. C Restart the machine. D Restart the installation.
62
If an Event is Not Propagated to AlarmPoint
If an Event is Not Propagated to AlarmPoint

s
For UNIX machines, check if the environment variables are set properly. For more information, see the warning on page 33. Check the APAgent.xml file for the correct configuration of the AlarmPoint Primary Server and the AlarmPoint Failover server. The AlarmPoint Failover Server will not get activated if this file is not configured properly. Check if there are notification policies in BMC IM for escalation to AlarmPoint. For example, the notification policy and the stop notification policy. Check if the AlarmPoint Service is present in the MC_CELL_DATA data class. In the AlarmPoint Server, check that all Persons and Groups are enabled. For all users, check if the notification devices are configured in AlarmPoint. Check if AlarmPoint Java Client is running. Check if AlarmPoint action scripts have been imported into AlarmPoint and are in production mode.
If the User Synchronization Module is Not Working

s
Read the following files:

s
usersync.log usersync_batch.log APClientResponse.log
Check the version of Perl. BMC II for AlarmPoint supports version 5.8.0 or later. Check the user and group details such as company name and site. These details are case sensitive. Care should be taken to check that the details entered in BMC IM and AlarmPoint are the same. Also, see the Note on page 52. Check the PATH and PERL5LIB environment variables.
Chapter 7 Troubleshooting
63
If the Heartbeat Service is Not Working
If the Heartbeat Service is Not Working

s
In Windows, check if the heartbeat service is running. IN UNIX, check if the heartbeat daemon is running. Check the heartbeat frequency that is set in the BMCIMxAPHeartBeat.ini file. The heartbeat frequency must not be below 10 seconds. Check if your cell is configured properly in the mcell.dir files located at the following path:
/etc/mcell and $MCELL_HOME/etc
64
Appendix
A
66 66 68 69 70
Notifications
This appendix presents the following topics: Types of notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-mail notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pager Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phone Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fax Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix A Notifications
65
Types of notifications
Types of notifications
Notifications are sent to the users depending on the Notification Policy in BMC IM. The following are the different types of notifications:
s
E-mail Pager Phone Fax
E-mail notification
The e-mail notification includes a description of the event that has caused the notification and a list of the following BMC IM Event Slots:
s
Event Type Event Time Object Class Tool Tool Class Parameter
Before you send a reply to this e-mail, you must add one of the following responses after the word RESPONSE in the subject line.
s s s s s s s s
ACKNOWLEDGE CLOSE ACCEPT REJECT PINGDEVICE_MC_HOST_ADDRESS TRACEROUTE_MC_HOST_ADDRESS PINGDEVICE_EVENTORIGIN TRACEROUTE_EVENTORIGIN
66
E-mail notification
NOTE
s s
The existing subject line must not be disturbed. There should be no space between the last word of the existing subject line and the word RESPONSE. There should be a space between the word RESPONSE and the next word. The text of the original e-mail should be included in the reply and should not be disturbed.
s s
The following is an example of an e-mail notification sent for a CRITICAL event.
EXAMPLE
Response "CLOSE" not recognized for: DDDDDD on xyz.adprod.abc.com. Additional Event Information ----------------------------------------Event Type Event Time Object Object Class Tool Tool Class Parameter : : : : : CRITICAL : 9/15/2004 6:47:27 PM : itnode
If you would like to reply to this e-mail, simply reply with the word "RESPONSE" followed by your choice in the subject line. Your response choices are: ACKNOWLEDGE, CLOSE, ACCEPT, REJECT, PINGDEVICE_MC_HOST_ADDRESS, TRACEROUTE_MC_HOST_ADDRESS, PINGDEVICE_EVENTORIGIN, TRACEROUTE_EVENTORIGIN. (Please make sure to include the original message in your reply. Following is used by the server to identify the e-mail: [FEABF7CE-1294-0543-BEC8-2B29043C655B].)
67
Pager Notification
Pager Notification
The pager notification includes a description of the event that has caused the notification and a list of the following BMC IM Event Slots on the first screen:
s
The next screen of the pager gives you the option to Reply or Delete. If you choose to reply, then you must send one of the following responses:
s
ACKNOWLEDGE CLOSE ACCEPT REJECT PINGDEVICE_MC_HOST_ADDRESS TRACEROUTE_MC_HOST_ADDRESS PINGDEVICE_EVENTORIGIN TRACEROUTE_EVENTORIGIN.
NOTE
The reply should not include any text apart from these responses.
68
Phone Notification
Phone Notification
The phone notification includes a description of the event that has caused the notification and a list of the following BMC IM Event Slots:
s
Once this information is over, you will be given menu options for the following responses:
s
ACKNOWLEDGE CLOSE ACCEPT REJECT
You can choose a specific response by pressing a specific digit button on your phone. For example, press one to select the ACKNOWLEDGE response, press two to select the CLOSE response, and so on.
69
Fax Notification
Fax Notification
The fax notification includes a description of the event that has caused the notification and a list of the following BMC IM Event Slots:
s
There is no response mechanism available for the fax notification.
70
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
Index
A
Accept 47 Acknowledge 47 Action Script Set 19 AlarmPoint 63 AlarmPoint group 36 AlarmPoint Server Action Script Set 39 AlarmPoint user 38 Automatic Notifications 42 Automatic Stop Notification 44
F
Fax Notification 70 Features 21 formats, syntax diagrams 7
G
group_id 37
B
BAROC and Rule Files 18 BMC II for AlarmPoint 26 BMC Software, contacting 2 Build 36
H
Heartbeat 50 Heartbeat Service 20, 64 Help, online 5 History 49
C
Close 47 Components 18 Configure Notifications 36 conventions, documentation 6 Custom Actions 48 customer support 3
I
Import 36 Install 30 installation 30
L
Log file for Heartbeat 50 Log files 54
D
documentation information 5, 6
E
electronic documentation 5 E-mail notification 66 Errors During Installation 62 Event 63 Event Management Policies Editor 39 Executable Files 53
M
Manual Notifications 46 Manual Stop Notification 46
N
Notification Policy 44 Notification Service 43
Index
71
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
O
online Help 5
P
Pager Notification 68 person_id 38 Phone 69 Phone Notification 69 PingDevice_EventOrigin 48 PingDevice_mc_host_address 48 Planning Worksheet 26 Prerequisite Products and Components 24 product support 3 publications, related 5
R
Reject 47 related documentation 5 related publications 5 Running User Synchronization 55
S
Scheduling User Synchronization 58 Selector 43 Standard Actions 47 support, customer 3 syntax statement conventions 6 syntax, format for diagrams 7
T
technical support 3 TraceRoute_mc_host_address 48 Troubleshooting 61 Types of notifications 66
U
Uninstall 34 uninstallation 30 User Synchronization Module 20, 63
X
XML Response Action Script 19
72
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
*50316* *50316* *50316* *50316*

*50316*

Bmciiap Ug

Uploaded by

Document Information

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

Bmciiap Ug

Uploaded by

Copyright:

Available Formats

BMCImpact Integration for AlarmPoint

October 29, 2004

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 AlarmPoint User Guide

About This Book

About This Book

BMC Impact Integration for AlarmPoint User Guide

Example {commit | cancel} {-commit | -cancel} (Unix) columnName . . .

required item KEYWORD

required choice variableValue variableValue

variableValue variableValue variableValue variableValue

About This Book

; WHERE searchCondition cursorName CURRENT OF

The following guidelines provide additional information about syntax diagrams:

BMC Impact Integration for AlarmPoint User Guide

BMC II for AlarmPoint Features

BMC Impact Integration for AlarmPoint User Guide

BMC Impact Integration for AlarmPoint User Guide

BMC Impact Integration for AlarmPoint User Guide

Introduction to BMC Impact Integration for AlarmPoint

Introduction to BMC Impact Integration for AlarmPoint

cell_a cell_b cell_c

BMC Impact Integration for AlarmPoint User Guide

BMC II for AlarmPoint Architecture

BMC II for AlarmPoint Architecture

Events and BMC II for AlarmPoint

Introduction to BMC Impact Integration for AlarmPoint

Components included with BMC II for AlarmPoint

Components included with BMC II for AlarmPoint

BMC II for AlarmPoint - Filenames for various platforms.

BAROC and Rule Files

BMC Impact Integration for AlarmPoint User Guide

Components included with BMC II for AlarmPoint

AlarmPoint Server Action Script Set

AlarmPoint Java Client XML Response Action Script

Introduction to BMC Impact Integration for AlarmPoint

Components included with BMC II for AlarmPoint

User Synchronization Module

Install and Uninstall Shell Scripts

BMC Impact Integration for AlarmPoint User Guide

BMC II for AlarmPoint Key Features

BMC II for AlarmPoint Key Features

Introduction to BMC Impact Integration for AlarmPoint

BMC II for AlarmPoint Key Features

BMC Impact Integration for AlarmPoint User Guide

Prerequisite Products and Components

BMC Impact Integration for AlarmPoint User Guide

Operating System Requirements

Operating System Requirements

Windows 2003 Server Windows 2000 Professional Solaris AIX HP-UX

Standard Edition Service Pack 3 8, 9 5.1, 5.2 11.11

Information Item or Requirement About BMC II for AlarmPoint

Planning Worksheet (Part 2 of 2) Response Notes

Information Item or Requirement

About AlarmPoint Java Client

BMC Impact Integration for AlarmPoint User Guide

Before You Begin

Installing BMC II for AlarmPoint