BMC Performance Manager Portal Monitoring and Management Guide

Supporting
BMC Performance Manager Portal version 2.8 Remote Service Monitor version 2.8

February 2010

www.bmc.com

Contacting BMC Software
You can access the BMC Software website at http://www.bmc.com. From this website, 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 USA Telephone 713 918 8800 or 800 841 2031 Fax 713 918 8000

Outside United States and Canada
Telephone (01) 713 918 8800 Fax (01) 713 918 8000

© Copyright 2009–2010 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. Linux is the registered trademark of Linus Torvalds. Oracle is a registered trademark of Oracle Corporation. SAP, SAP BusinessObjects, and Crystal Reports are the trademarks or registered trademarks of SAP AG in Germany and in several other countries. Solaris, Java, JMX, JRE, and Sun are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries. UNIX is the registered trademark of The Open Group in the US and other countries. The information included in this documentation is the proprietary and confidential information of BMC Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and restricted rights notices included in the product 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 BMC Software Customer Support website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, see “Before contacting BMC.”

Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support. From this website, you can
s s s s s s s s

read overviews about support services and programs that BMC offers find the most current information about BMC products search a database for issues similar to yours and possible solutions order or download product documentation download products and maintenance report an issue or ask a question subscribe to receive proactive e-mail alerts when new product notices are released find worldwide BMC 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 or send an e-mail message to customer_support@bmc.com. (In the subject line, enter SupID:<yourSupportContractID>, such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.

Before contacting BMC
Have the following information available so that Customer Support can begin working on your issue immediately:
s

product information — — — product name product version (release number) license number and password (trial or permanent)

s

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 issue 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

3

License key and password information
If you have questions about your license key or password, contact BMC as follows:
s

(USA or Canada) Contact the Order Services Password Team at 800 841 2031, or send an e-mail message to ContractsPasswordAdministration@bmc.com. (Europe, the Middle East, and Africa) Fax your questions to EMEA Contracts Administration at +31 20 354 8702, or send an e-mail message to password@bmc.com. (Asia-Pacific) Contact your BMC sales representative or your local BMC office.

s

s

4

BMC Performance Manager Portal Monitoring and Management Guide

Contents
Chapter 1 Overview of the BMC Performance Manager Portal 15 15 16 17 17 18 18 19 19 20 21 22 22 23 24 25 27 27 28 29 40 42 44 45 46 47 47 49 50 50 50 50 51 51 51 55
5

How BMC Performance Manager Portal fits into BMC Portal . . . . . . . . . . . . . . . . . . . BMC Portal features common to all modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Performance Manager Portal features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How the BMC Performance Manager Portal monitors your infrastructure. . . . . Methods of data collection for Performance Managers . . . . . . . . . . . . . . . . . . . . . . Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Performance Manager Portal module in BMC Portal . . . . . . . . . . . . . . . . . . Remote Service Monitor program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional security for BMC Performance Manager Portal . . . . . . . . . . . . . . . . . . Security requirements for RSMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Infrastructure element credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2 Getting started with the BMC Performance Manager Portal

Verifying the BMC Performance Manager Portal installation . . . . . . . . . . . . . . . . . . . Adding infrastructure elements for agentless monitoring . . . . . . . . . . . . . . . . . . . . . . Verifying an upgrade from an earlier version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating PATROL Agent data into the BMC Performance Manager Portal . . . . . Options for identifying PATROL Agents as elements . . . . . . . . . . . . . . . . . . . . . . . Methods for discovering PATROL Agent data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronization of thresholds and application classes . . . . . . . . . . . . . . . . . . . . . . Integrating infrastructure elements from the BMC Atrium CMDB . . . . . . . . . . . . . . . Viewing object status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Portal and infrastructure status views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Individual parameter history charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter history tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3 Users and administrators

User configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Account Information task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blackout Periods task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Password task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dashboards task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Element Profiles task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Elements task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents

Monitoring On/Off task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Notifications task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Object Groups task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Personal Preferences task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Remote Service Monitors task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Shared Credentials task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Tags task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 User Groups task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Users task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Administrator configuration options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Tasks on the Accounts tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Tasks on the Provider tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Tasks on the Portal tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Chapter 4 Remote Service Monitors 69

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Types of RSMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Communication between the Portal and RSMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Communication between RSMs and elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Communication between RSMs and PATROL Agents . . . . . . . . . . . . . . . . . . . . . . 74 Notifications about RSM system problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 RSM program installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 RSM computer system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Data execution prevention (DEP) configuration for the RSM . . . . . . . . . . . . . . . . . 76 Configure Distributed Component Object Model (DCOM) and Windows Management Instrumentation (WMI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Using the installation wizard to install the RSM program . . . . . . . . . . . . . . . . . . . 84 Using a silent installation to install the RSM program. . . . . . . . . . . . . . . . . . . . . . . 88 Upgrading the RSM Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Clustered RSMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Cluster types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Clustered RSM operating status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Clustered RSM security considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 RSM load-balancing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 RSM failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Clustering RSMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Clustered RSM upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 RSM configuration and maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Configuration and maintenance tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Changing the security level for an RSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Configuring an RSM to use a proxy server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Configuring the RSM to use HTTP protocol to communicate with the Portal . . 103 Changing the credentials for an RSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Changing the maximum heap memory allocated for the Java VM on the RSM 106 Viewing the log files for the RSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Collecting log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Automating basic information gathering for RSM issues . . . . . . . . . . . . . . . . . . . 108 Stopping notifications for Unknown state events . . . . . . . . . . . . . . . . . . . . . . . . . . 108 RSM program uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
6 BMC Performance Manager Portal Monitoring and Management Guide

Using the installation wizard to uninstall the RSM program . . . . . . . . . . . . . . . . 109 Manually uninstalling the RSM program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Using command-line options to uninstall the RSM program . . . . . . . . . . . . . . . . 112 Chapter 5 Performance Managers and application classes 113 114 114 115 115 116 117 118 118 119 120 121 121 121 125 127 129 130 130 131 131 139 139 139 141 142 142 143 144 144 145 145 145 147 147 149 151 152 153 156 160 161 162
7

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters and thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter thresholds and event severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Thresholds and parameter status changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deactivating parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Points to remember while deactivating parameters. . . . . . . . . . . . . . . . . . . . . . . . Derived parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deactivating a parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deactivating a parameter in the Performance Manager Editor solution . . . . . . Solution support for deactivating parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods of remote monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Agentless monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Agent integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing new Performance Managers on the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading Performance Managers on the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Performance Managers from the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Core Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solution Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Custom Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing unpublished custom Performance Managers . . . . . . . . . . . . . . . . . . . . . . Editing published custom Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . Chapter 6 Reports

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter update intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accumulated parameter values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data summarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data retention policies that affect object view content . . . . . . . . . . . . . . . . . . . . . . . . . Retention policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Properties that control the raw data retention policies . . . . . . . . . . . . . . . . . . . . . Properties that control event history retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purging inactive data from the Portal history tables . . . . . . . . . . . . . . . . . . . . . . . Purging unknown and unused events from the event table. . . . . . . . . . . . . . . . . Reports tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time interval controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Top N report for object groups or the account . . . . . . . . . . . . . . . . . . . . . . . . . . . . Health At A Glance report for elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple parameter history charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dashboard parameter charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enterprise reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents

. . . . . . . . . . . . . . . 227 Event integration using AlarmPoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 8 BMC Performance Manager Portal Monitoring and Management Guide . 174 Upgrading to BMC Reporting Foundation 3. . . . . . . 245 Trap error codes . . . . . . . . 201 Maintaining the continuous export to the CDE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Object identifiers (OIDs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Event integration using SNMP traps . . . . . 218 Account integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Changing the retention policy for the CDE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 External CDE movement . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Uninstalling the integration components . . . . . . . . . 174 Publishing and scheduling generated reports . . . . . . . . . . 201 Additional configuration options . . . . . . . . . . . . . . . Crystal Reports 2008 (Designer component). . . . .00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Chapter 8 BMC Performance Manager Portal command-line interface 251 Preparing the client computer for the bpmcli . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .00. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 List content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Trap properties customization . . . . . . . . . . . . . . 228 Combining BMC Performance Manager and PATROL Agent events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 SNMP traps . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . 191 Configuring the datafeed utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Event integration . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Events tab. . . . . . . . . . . . . . . 221 Service Model integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Chapter 7 Portal events and data integration 217 Levels of integration. . . . . . . . . . . . . . . . . . . . . . . . . 253 Data-manipulation commands . . . . . 164 Upgrading to Crystal Reports 2008 (Designer component). . . . . . . . . . 238 BMC-Performance-Manager-Portal-MIB description. . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Report types and details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Parsing SNMP traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and integration components . . . . . . . . . . . . . . . . . . . 219 BMC Performance Manager Portal as a CMDB Consumer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 bpmcli syntax and arguments. . . . . . . . . . . . . . . . . . . . . 218 Portal-wide integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Continuous data export requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Downloading and installing BMC Reporting Foundation 3. 236 MIB files. . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Installing the integration components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Reconciliation rules for infrastructure elements and the BMC Atrium CMDB . . . . . . . 248 Page controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Sample trap . . . . . . . . . . . . . . . . 218 Provider-wide integration . . . . . . . . . . . . . . . . . . . . . . . . . . 219 BMC Atrium CMDB integration . . . . 187 Continuous data export configuration . . 228 Event integration using BMC II Web Services. . . 220 BMC Performance Manager Portal as a CMDB Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Event integration using email notifications . . .

. . . .0 and above . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Changing the security for the BMC Performance Manager Portal . getParameterHistory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding application class occurrences displaying the ACS error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . addPATROL . 305 Report does not contain expected data . . . . 309 Contents 9 . . . . . . 296 RSM computers running Windows require permission changes . .1. . . . . . . . 304 PATROL integration error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 E-mail notification in Microsoft Outlook 2007 does not display the BMC logo and icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . refreshPATROL . 306 Checking log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling alarms and warnings for an application class or parameter globally . . . . . . . . . . . . . . . . refreshDatafeedMetadata . . . . . . .2. . . . . . deleteElements: deleting multiple elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . getParameters. . . . . . . . . . . . . . . . . . . . . . . . . .addElements: adding a single element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Unable to download RSM by using IE 7 or 8 on Windows 2008 . . . . . . . . . . . . . . . . . . Data-extraction commands. . . . . . 298 Unable to close popup windows on IE Minor Versions IE 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Frequently asked questions (FAQs) . . . . Chapter 9 255 257 260 262 263 264 266 269 270 272 276 277 278 281 282 283 BMC Performance Manager Portal command-line interface for BMC Datastore 285 285 287 289 292 295 Configuring the BMC DatastoreCLI . . . . 305 Error message in BusinessObjects Enterprise XI 3. . . . . . . . . . . . . . . . . . . . . . . . . getElements . . . . . . . . . . . . . . . 304 BMC Reporting Foundation 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . getApplicationsForElement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Console Server list is empty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix A BMC Performance Manager Portal troubleshooting and FAQs Monitoring problems. . . . . 299 When you use Management Profiles to integrate data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .00 troubleshooting . . . . . . . . . . . . . . . 299 Reinstalling the application server component of the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 RSM upgrade fails on Windows 2003 SP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . getPortalVersion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 Buffer Cache Hit Ratio and Oracle Dictionary Cache Hit Ratio parameters go into alarm . . . . . . . . . . . . . . . getSubApplications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Specifying RTservers for the BMC Performance Manager Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting the configuration information from BMC Portal on to an HTML file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . exportParameterHistory . . . . . . . . . . . . . . . . . . . . . . . . . savePassword. . . . . . . . . deleteElements: deleting a single element . . . . . . . . . . . . . . . . . . . . . . . . 302 Portal randomly logs out users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . addElements: adding multiple elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 Unable to download reports to csv or text file. . 303 Cannot find errors when data discovery runs as a background process. . . . . . . .

. 316 PATROL Agent health monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 Remote Service Monitor setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 Permissions . . . . . . 345 RSM log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Log files . . . . . . . . . . . . 313 Configure RSM to monitor JMX behind a firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Changing the threshold settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 BMC Performance Manager Portal log file . 318 Appendix C BMC Performance Manager Portal files 319 Configuration files . . . . . . . . . . . . . . . . . . . . . . . 345 Glossary Index 347 355 10 BMC Performance Manager Portal Monitoring and Management Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Performance Manager configuration . . . . . . 311 Self-monitoring Performance Manager . . . . . . . . . . . . . . . . . . . 317 Configuring PATROL Agent monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Remote Service Monitor property files . . . . . 319 BMC Performance Manager Portal property files. . 314 BMC PM Monitor application classes . . . . . . . . . . . . .Appendix B Monitoring the health of the Portal 311 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Configuration file properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . 194 CSV properties in the datafeed. . . . . . . . . . 158 Health At A Glance: Element Events . . . . . . . . . . . . . . . . . . . . . . . . . . . .properties file . 144 Top N: report settings and content . 245 Infrastructure element view of Events tab . . . . . . . . . . . . . . . 225 BMC Performance Manager Portal event integration . . 143 Accumulated parameter values . . . 234 Sample agentless and agent-based events sent from the Portal . 226 Two comparable events from one threshold breach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Affect of status changes on reported parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . .txt file for silent installation . . . . . . . . . . . . . . . . . 263 Figures 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Health At A Glance: Key Parameters . . . . . . . . . . . 47 Buttons to filter parameters on the Status tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Data target lines in the datafeed. 159 Options for multiple parameter history charts . . . . . 161 Comparative parameter history report for one parameter . . . 248 Alerts to Show list on Events tab . . . . . . . . . .properties file . . . . 156 Health At A Glance: Element Status Summary . . . . . . . . . . . . . . .Figures BMC Portal with the BMC Performance Manager Portal module installed . . . . . . 235 OID structure in BMC-Performance-Manager-Portal-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Simplified view of service model integration methods from the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Standard parameter values . . . . . . . . . . . . . . . 154 Health At A Glance: time controls . . . . . . . . . . . . . . . . . . 71 Example of RSMOptions. . . . . . . . . . . 47 Types of Remote Service Monitors . . . . . . . . . . . . . . . . . . . . . . . . . 193 Datafeed cache properties in the datafeed. . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 Sample CSV file for deleting elements with bpmcli . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Performance Manager parameter mapping to Knowledge Module parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Account view on the Status tab . .properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Oracle properties in the datafeed. . . . . . . . . . . . . . . . 195 CDE database structures . . . . 184 Continuous data export process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Alert After threshold options . . . . . . . . . . . . . . 160 Comparative parameter history charts for one element . . . . . . . . . . . . . . . . . . . . . 249 Sample CSV file for adding elements with bpmcli . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Top N: time controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Sample trap for an Element State Change event (part 1 of 2) . . . . . . . . . . . . . . . . . . . 45 Parameter history chart . . . . . . . . . . . . . . . . . . . . . . 161 Example of a typical report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Parameter history table . . . . . 91 Clustered RSMs in the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . .Using data-extraction commands to retrieve input arguments for subsequent commands . . . . . . . . . . 273 RSM setup for monitoring the Portal components . . . . . . . . . . 270 How the Historical Data Export utility uses the startData argument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 12 BMC Performance Manager Portal Monitoring and Management Guide . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Types of events available for object views . . . . . . . . . . . . . . . . . . 166 Report schedule parameters . . . . . . . . . . . 130 Features of the Performance Managers page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Reporting integration prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Additional configuration options for the datafeed utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 RSMs and clustered RSM counterparts . . . . 136 Charts available from the Reports tab . . . . . . . . . . .Tables Highlights of security levels . . . . . . 132 Application class properties . . . . . . . . . . . . . . . . . . . . . 182 BMC Performance Manager report details . . . . . . . . . . . . . . . . . . . . . 265 refreshPATROL arguments . . . . . . . . . . . . . . . . . . . . . . . 256 addElements arguments for adding multiple elements . . . . . . . . . . 249 Basic arguments for bpmcli commands . . . . . . . . . . 134 Supported collection protocols for custom application classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Minimum and maximum values for mapped thresholds . . . . . . . . . . . . . . . . . . . . . . . 232 BMC-Performance-Manager-Portal-MIB . . . . . . . . . . . . . . . . . . . . . 222 Slot names in the base event class populated for the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 addPATROL arguments . . . . 155 Element event attributes in Health At A Glance report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 deleteElements argument for deleting a single element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Differences between Performance Manager and Knowledge Module thresholds . . . . . . . . 44 Application ports for firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Output controls for Reports tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Parameter error codes . . . . 93 Icons for clustered RSM operating status . . . . . . . . . . . . . . . . . . . . . . 74 Authentication information on Logon Information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Page controls on Status tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 PATROL_Portal event class extensions . . . . . . . . . . . . . . . . . . . . . . . . . 264 deleteElements argument for deleting multiple elements . . . . . . 259 Values required for CSV input file for the addPATROL CLI command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Data-manipulation bpmcli commands . . . . . . . . . . . . . . . . . 202 Variables for arimportcmd or dataImport command . . . . . . . . . . . . . . . . . . . . . . 272 Tables 13 . . . . . . . . . . 247 Page controls for Events tab . . . . . . . . . 20 PATROL Agent data required in CSV file . . . . . . . . . . . . . . . . . . . . . . 268 Data-extraction bpmcli commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Options for an RSM silent installation . . . . . . . . . . . . . . . . . . . . . . . 263 deleteElements argument for deleting multiple elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 BMC Performance Manager components required for various reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 addElements arguments for adding a single element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Core Performance Managers and their application classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . 316 Location of BMC Performance Manager Portal property files . . . . . . . . . . . . . .properties file on the RSM computer . . . . . . . . . . . . .properties file . . 276 getParameterHistory arguments . . . . . . . . . . . . . . . . . . . . . . 342 Properties in the rsm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Properties in rsm-RsmHostName. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .exportParameterHistory arguments . . 341 Properties in the padm. . . . . .properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Error messages for PATROL integration . . . . . . . . . . . . . . . . . . . 320 Properties in drmop. 322 Properties in rsmcfg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 JMX credentials on RSMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 14 BMC Performance Manager Portal Monitoring and Management Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 getApplicationsForElement argument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 Properties in portal-PortalWebServer. . . . . 279 getParameters argument .properties file on the RSM computer . . . . . . . . . . . . . . . . . . . . . . . . . . 312 BMC PM Monitor application classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Predefined settings for monitoring the BMC Performance Manager Portal module . . . . . . . . . . . . . . 281 Parameter status values . . . . . . . . . . . 282 getSubApplications argument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .properties file on the RSM computer . . . . . .properties file . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and web server. . . . . . . . . . . . . . . . . . . . . . . . BMC Performance Manager Portal module in BMC Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Infrastructure element credentials . . . . 15 16 17 17 18 18 19 19 20 21 22 22 How BMC Performance Manager Portal fits into BMC Portal BMC Portal—also referred to as the Portal—is composed of a database. . . . . . Security requirements for RSMs . . . . . . . . . . . . . . . . . . . The BMC Performance Manager Portal extends the features in the BMC Portal. . . . . . . . . . . . . . . . . . . . . . . . Remote Service Monitor program. . . . . . and provides the access point for its utilities and modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Components . . . . Methods of data collection for Performance Managers . . . . . . . . .Chapter 1 Overview of the BMC Performance Manager Portal 1 This chapter describes how the BMC Performance Manager Portal module fits into the BMC Portal product and the features in BMC Performance Manager Portal. . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1 Overview of the BMC Performance Manager Portal 15 . . . . . . . . . You access the BMC Portal from a browser on your client (desktop) computer. . . . . . . . . . . enabling you to leverage both agentless technologies and the PATROL Agent to monitor the availability and performance of your business infrastructure. . . . . . . . . . . . . . . . Security . . . . . . . . . How the BMC Performance Manager Portal monitors your infrastructure. . . Additional security for BMC Performance Manager Portal . . . . . . . . . . . . . . . . BMC Performance Manager Portal features . This chapter presents the following topics: How BMC Performance Manager Portal fits into BMC Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . application server. . . . BMC Portal features common to all modules . . .

Icons. 16 BMC Performance Manager Portal Monitoring and Management Guide . users. rights. events. including: s s s s s s s s Account properties Object group names Blackout period scheduling (times when metrics are not collected from the elements) Customization of notification criteria that BMC Portal uses to determine when to notify your personnel about problems in your environment Users and user groups Object views that provide status. and report data Dashboard configuration System and user-defined tagging of objects that you can use to quickly retrieve objects For details about these features. see the BMC Portal Getting Started guide and online Help. and other graphical cues enable you to quickly determine the source of problems. This guide also describes the accounts. NOTE For information about configuring BMC Portal. colors. as well as authentication. At any time. and administrators. users with the applicable permissions can view: s s s s Current status of the infrastructure in the account Lists of the elements and parameters in the account that recently crossed thresholds and triggered events Charts that show how well the elements in the account performed History log of the events in the account Each object view tab provides a high-level view of the account that enables you to access more detailed information. BMC Portal features common to all modules BMC Portal provides many common features across all of its modules.BMC Portal features common to all modules Your user permissions determine the extent to which you can configure and monitor your Portal account. see the BMC Portal Getting Started guide. and permissions.

or when you import them from the Portal user interface. How the BMC Performance Manager Portal monitors your infrastructure The BMC Performance Manager Portal uses Remote Service Monitors (RSMs) to collect metrics about your infrastructure. programs. Reports.” on page 69. Collectively. Performance Managers. To know what to monitor on the specified infrastructure elements. “Remote Service Monitors. Each Performance Manager contains one or more application classes that you can select to monitor operating systems. The infrastructure objects in your account correspond to the computers and devices that compose the IT infrastructure for your business. An RSM is a computer on which you have installed the RSM program. For more information about installing application classes. and Events tabs provide views about your account and the objects that compose the account. “Performance Managers and application classes. Performance Managers that are installed on the Portal are available to all users on the Portal who have the appropriate user permissions. processes. and the application classes that they contain. are installed on the Portal and saved in the Portal database when you select them from an installation CD or EPD website.” on page 113. You organize infrastructure elements into groups to which you assign rights and permissions for users of the Portal. see Chapter 5. see Chapter 4. For more information about installing and configuring the RSM program. the RSM uses Performance Managers. The Status. and more. infrastructure elements and groups are known as infrastructure objects. Each application class contains parameters that define the type of metric to obtain from the infrastructure element. Following installation and configuration of the BMC Performance Manager Portal. files.BMC Performance Manager Portal features BMC Performance Manager Portal features The BMC Performance Manager Portal leverages agentless and PATROL Agent technologies to monitor and report on the performance of the IT infrastructure that supports your business. Depending on the size of your environment and your high availability (HA) requirements. you can implement one or many RSMs. Chapter 1 Overview of the BMC Performance Manager Portal 17 . you can begin adding computers and other devices to the account as infrastructure elements.

you can use the BMC Performance Manager Portal to view performance and availability metrics and status.Methods of data collection for Performance Managers Methods of data collection for Performance Managers Performance Managers contain the applications that obtain performance and availability metrics about the monitored infrastructure objects in your account. if permitted by your user permission. Performance Managers can provide agentless monitoring or can integrate parameter data from a PATROL Agent. After you install the Performance Managers in the Portal. PATROL integration Performance Managers correspond to the PATROL Knowledge Modules (KMs) on the selected agent. you can accept default thresholds or. modify thresholds to reflect the service level agreement (SLA) for your account. based on the operating system of the element. The application classes in PATROL integration Performance Managers retrieve parameter data from PATROL Agents. You can integrate parameter data from version 3. you can configure the elements in your account to use the application classes in the Performance Managers. The RSM program begins collecting metrics about your account within minutes of your adding and configuring the first elements. The application classes in agentless Performance Managers use industry-standard protocols. As you add elements to the account. During element configuration. such as PerfMon and SNMP. As soon as data collection begins. Components The following components compose the BMC Performance Manager Portal: s s BMC Performance Manager Portal module in BMC Portal Remote Service Monitor program 18 BMC Performance Manager Portal Monitoring and Management Guide .5 and later of PATROL Agents. the user interface displays the application classes available for the new elements. and contain mappings to a subset of the parameters in the KM. to retrieve metrics about the performance of the monitored element.

BMC Portal provides the access point to the BMC Performance Manager Portal module and the views that provide the metrics about your monitored infrastructure. the installation program places the BMC Performance Manager Portal on the BMC Portal application server. The RSMs obtain parameter metrics from the monitored elements and send events and parameter metrics to the Portal web server. You use your Internet browser to access the Portal to view data and reports that show the performance and availability of your account. RSM queries the Portal for the corresponding Performance Manager. see the BMC Portal Getting Started guide. Chapter 1 Overview of the BMC Performance Manager Portal 19 . After the RSM retrieves it from the Portal. the Performance Manager remains on the RSM. Figure 1 BMC Portal with the BMC Performance Manager Portal module installed BMC Portal database server RSM computer The programs that compose the BMC Performance Manager Portal module reside on the Portal application server. When you specify an application class that is not on the specified RSM. You install the RSM program on each computer designated as an RSM. Remote Service Monitor program The Remote Service Monitor (RSM) program remotely monitors its assigned elements and sends parameter values to the Portal. web browser web server application server remote elements PATROL Agents BMC Performance Manager Portal module in BMC Portal During installation of BMC Portal.BMC Performance Manager Portal module in BMC Portal Figure 1 shows how the BMC Performance Manager Portal components interact with the BMC Portal. For more information about the individual components of BMC Portal.

“Remote Service Monitors. Security During installation of BMC Portal. see Chapter 4. Table 1 summarizes the key elements for each of the five levels of security.” on page 69. BMC Performance Manager Portal. the installation program installs basic security on the Portal. when the parameter status changes from warning to alarm). The RSM also sends parameter values to the Portal as soon as it detects that a parameter has changed its status (for example. and BMC Portal No cryptographic protection of network traffic No verification of product or data integrity Authentication provided and protected password stored in unattended operations in the PATROL application Minimized security and access control lists (ACLs) in favor of usability and performance Diffie-Hellman used for privacy No SSL authentication of either party to the other s s s s Level 1 s s 20 BMC Performance Manager Portal Monitoring and Management Guide . along with increasingly greater configuration demands. If you intend to integrate data from a PATROL Agent. For more information about the Remote Service Monitor program. The RSM installation program also requests a security level. Table 1 Highlights of security levels (part 1 of 2) Description s Security level Basic security Default level of security employed when you install PATROL. the RSM begins collecting parameter data from the element at the collection intervals specified for each application class. you might need to specify a different security level. When integrating PATROL Agent data.Security After you add an element to the Portal. Basic security (the default) is the lowest level of security. and then sends parameter values to the Portal at the report update interval for the element. Levels 1 through 4 provide increasingly higher levels of security. the security level on the RSM must match the security of the monitored PATROL Agent.

the installation prompts you for an RTserver name and for the necessary security level. If you select Yes. the security on the Portal must match that of the target console servers. To change the security level for the Portal. When you install the BMC Performance Manager Portal module.Additional security for BMC Performance Manager Portal Table 1 Level 2 Highlights of security levels (part 2 of 2) Description s s s Security level Private communications provided by SSL No SSL authentication performed (runs in keyless mode) Defaults to unattended agent restart Private communications and server authentication provided by SSL Certificate provided by agent so that the client can authenticate the agent Client not authenticated back to the agent Defaults to unattended agent restart. For more information about Management Profiles and the RTserver. Chapter 1 Overview of the BMC Performance Manager Portal 21 . can configure for attended agent restart Private communications and mutual authentication of the console and the agent provided by SSL Defaults to unattended agent restart. see the BMC Portal Getting Started guide. see the PATROL Security User Guide. see your PATROL Central documentation. can configure for attended agent restart Level 3 s s s s Level 4 s s Additional security for BMC Performance Manager Portal If you have a PATROL Central environment and want to use Management Profiles to discover PATROL Agents. the installation program asks if you want to discover PATROL Agents in a PATROL Central environment. For more information about security.

you must install an RSM for each security level of the PATROL Agents from which you integrate data. the installation program applies the Basic security (level 0) to the RSM. the installation program prompts you for a security level. This setting enables you to change the security level at a later time. Because an RSM that integrates PATROL Agent parameter values must have the same security level as that of the PATROL Agent. see “Changing the security level for an RSM” on page 101. Infrastructure element credentials During element configuration. If your environment does not use PATROL Agents. the BMC Performance Manager Portal prompts you for authentication credentials that the RSM program can use to access the element. To change the security level on an RSM. using Secure Hash Algorithm (SHA). The credentials for infrastructure elements are encrypted and stored in the Portal database. The Portal encrypts the credentials and sends them to the RSM computers. 22 BMC Performance Manager Portal Monitoring and Management Guide . if necessary. which provides 160-bit cryptographically secure hash of the credentials.Security requirements for RSMs Security requirements for RSMs When installing the RSM program. and the RSM program does not store any element credentials locally.

. . . Verifying an upgrade from an earlier version . . . . . .Chapter 2 Getting started with the BMC Performance Manager Portal 2 This chapter describes activities that you must perform immediately after installing and configuring the BMC Performance Manager Portal module on the Portal or after upgrading to the current version of the Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 25 27 27 28 29 40 42 44 45 46 47 47 Chapter 2 Getting started with the BMC Performance Manager Portal 23 . . . . . . . . . . . . . . . . . Portal and infrastructure status views . . . . . . The scenarios in this chapter acquaint you with the methods for configuring the BMC Performance Manager Portal to monitor your infrastructure. . . . . . . . . . . . Integrating PATROL Agent data into the BMC Performance Manager Portal . . . . . . . . . . . . . Parameter history tables . . . . . . . . . . . . . . . . . Methods for discovering PATROL Agent data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Individual parameter history charts . . . . . . . . . . Options for identifying PATROL Agents as elements . . . . . . . . . Integrating infrastructure elements from the BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding infrastructure elements for agentless monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronization of thresholds and application classes . . . Viewing object status . . . . . . . . . . . . . . . . . . . . . This chapter presents the following topics: Verifying the BMC Performance Manager Portal installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter filtering. . . . . .

you might have a problem with the Portal installation or with the configuration of the element. including the BMC Performance Manager Portal. s s s 24 BMC Performance Manager Portal Monitoring and Management Guide . expand the object tree to display the top-level Infrastructure object group and the objects that it contains. To verify the BMC Performance Manager Portal installation 1 Use the procedure in “Using the installation wizard to install the RSM program” on page 84 to install the RSM program on the Portal computer or another computer designated as an RSM. To test the installation. After adding the element.Verifying the BMC Performance Manager Portal installation Verifying the BMC Performance Manager Portal installation The BMC Portal Getting Started guide describes how to configure the Portal and its modules. If a problem occurs If the status of the element is critical. the status of the new infrastructure element should change to OK. See the troubleshooting appendix in the BMC Portal Getting Started guide or the BMC Portal Installation Guide. This section describes tasks that you can perform to ensure that the BMC Performance Manager Portal is ready to monitor infrastructure. s Verify that a firewall is not preventing the RSM from successfully reaching the computer. select a simple application class. Verify that a firewall is not preventing the RSM from sending data to the Portal. 3 Select the Status tab. 4 In the navigation pane. such as Ping. You can install one of the RSM instances on the Portal computer. Determine whether a network problem is causing the ping command to fail. 2 Use the procedure in “Adding infrastructure elements for agentless monitoring” on page 25 to add one element to the account.

and click Add. click Cancel and install the RSM program. and click Next. “Reports. proceed to step 5. and click Next to open the Elements–Add Infrastructure Element–Identification page. see “Adding infrastructure elements for agentless monitoring” on this page.Adding infrastructure elements for agentless monitoring Where to go from here s Begin adding infrastructure elements. see Chapter 6. See “Using the installation wizard to install the RSM program” on page 84. If this occurs. 4 If the Elements–Add–Type of Element page is displayed. see “Using the installation wizard to install the RSM program” on page 84. otherwise. For more information. select Infrastructure Element. 5 On the Elements–Add Infrastructure Element–Select Remote Service Monitor page. Review the metrics collected about infrastructure elements. s Adding infrastructure elements for agentless monitoring You can quickly add computers and devices for agentless monitoring. and to verify that the element can accept network requests. For more information. NOTE If an instance of the RSM program has not been installed. Before you begin You must have at least one RSM installed and available to the Portal. which measures network latency. Chapter 2 Getting started with the BMC Performance Manager Portal 25 . For more information. the list of Remote Service Monitors is empty. select an RSM. To add an infrastructure element to the BMC Performance Manager Portal 1 Log on with user credentials 2 Click the Configure tab. select Elements to open the Elements page. The following scenario provides the procedure for adding an element and configuring it with the Ping application class.” on page 141. 3 Under Tasks.

When you keep the default value for Collection Interval. and click Next: s When you keep the default value for Report Update Interval Minutes. and click Finish. specify the platform name and group name. After you finish adding the element to the Portal. and click Next.7 and later. the RSM sends parameter values to the Portal every 5 minutes for BMC Portal versions earlier than 2. select the Ping application class. select the platform that corresponds to the host name that you specified in step 7. 8 On the Elements–Add Infrastructure Element–Select Group page. s 11 On the Elements–Add Infrastructure Element–Thresholds page. type test group. 26 BMC Performance Manager Portal Monitoring and Management Guide . specify an element name that appears on all charts and Status pages. and click Next: A From the Element(s) Platform list. you can paste a list of host names in the text box or specify a range of IP addresses. To add many elements. and every 10 minutes for versions 2. If you do not specify a label name. 10 On the Elements–Add Infrastructure Element–Properties and Credentials page.Adding infrastructure elements for agentless monitoring 6 In Element Name (label). 9 On the Elements–Add Infrastructure Element–Application Classes page. B In Group Name. the RSM collects parameter values for the Ping application class once every minute. the host name or IP address is used as the element name. the RSM starts accessing the element to collect parameter values. select Host Name. select the Networking category. When adding multiple elements. type the host name of the computer. review the properties for the Ping application class.7. 7 In the text box. You might need to wait a minute or two before the Portal receives the initial parameter values and updates the Status tab. unless a parameter threshold is violated. and click Next. Where to go from here Begin viewing the parameter metrics collected by the RSM by selecting the Status and Reports tabs. accept the default thresholds. separate host names with commas.

3.3 or later 1 Log on using the Portal administrator credentials (superadmin/superadmin by default). Chapter 2 Getting started with the BMC Performance Manager Portal 27 . 4 Log on as a user and select the Status tab to view the values and status for the infrastructure elements in your account. If you upgraded from BMC Performance Manager Portal 2. After the upgrade.Verifying an upgrade from an earlier version Verifying an upgrade from an earlier version You can view the Performance Managers that were upgraded from version 2. Using the PATROL Agent as a data source. your application classes were migrated to the Performance Manager format and installed on the Portal.1. If you upgraded from BMC Performance Manager Portal 2.5 and later of PATROL Agents. 3 Under Tasks. Integrating PATROL Agent data into the BMC Performance Manager Portal BMC Software has created PATROL integration Performance Managers for many of the KMs. the Status tab should reflect new values collected by the upgraded application classes and RSM for your Portal. see “To upgrade a Performance Manager during a Portal upgrade” on page 127. The BMC Performance Manager Portal can integrate parameter data from version 3. providing mappings to many of those KMs’ parameters.1 and to ensure that the Portal is collecting data following the upgrade. the RSM mines parameter data from the agent and sends it to the Portal. 2 Select the Portal tab. select Performance Managers to open the Performance Managers page and view the list of all the Performance Managers that were upgraded from the earlier version. To verify an upgrade from BMC Performance Manager Portal version 2.

In most cases. The threshold values that you set in the Portal for PATROL integration parameters have no effect on the values set for the parameters in the BMC Performance Manager consoles. 28 BMC Performance Manager Portal Monitoring and Management Guide . you can accept the default parameter thresholds in the PATROL integration application class.Options for identifying PATROL Agents as elements Options for identifying PATROL Agents as elements When you add PATROL Agents to the Portal as elements. you either specify the host names of the agents or use a discovery method to find them. match the KMs with the PATROL integration Performance Managers on the Portal.Web Edition PATROL Central Operator . When you specify the host names or IP addresses. see “PATROL Agent health monitoring” on page 317. you can also choose to monitor the health and availability of the selected PATROL Agents. see “PATROL Agent integration” on page 121. After specifying the host names. or you can modify the default values (during the add process or later). For more information. you must know the KMs that are installed on the managed system and their corresponding Performance Managers in the Portal.Microsoft Windows Edition PATROL Console for Microsoft Windows PATROL Console for UNIX® s Select PATROL Integration to have the BMC Performance Manager Portal discover the agents and the KMs on the agents. To change threshold management to the Portal. and obtain parameter thresholds. The Elements–Add Infrastructure Element–Identification page provides the following options for identifying PATROL Agents and discovering thresholds from versions 3. By default. the PATROL integration Performance Manager names and version numbers match the PATROL KM names and version numbers. When you use this option to discover PATROL Agents. PATROL Configuration Manager. This method uses the thresholds defined in the selected PATROL integration Performance Manager. select the PATROL integration Performance Managers that correspond to the KMs on the agents. For more information about managing thresholds for PATROL Agent elements.5 and later of PATROL Agents: s Select Host Name or IP Address to specify one or more PATROL Agents as elements. threshold management is handled from the PATROL Agent. NOTE The BMC Performance Manager consoles include s s s s PATROL Central Operator . PATROL Knowledge Module for Event Management. access the Properties page for element to change the threshold management preference. When you select one of these options. or other BMC Software products.

The data discovery process can take a long time. This method requires that you specify an RTserver for the Portal to discover Management Profiles on the console server. consider creating Management Profiles that contain the managed systems that you want to add. The CSV file can optionally contain the password to authenticate the user name. select the Status tab. Reports. Events. you can use a combination of the integration options.Methods for discovering PATROL Agent data Methods for discovering PATROL Agent data When you select the PATROL Integration option. To see whether any errors occurred during data discovery. To ensure that you do not stop the Portal from mining data from the agents. which requires that you specify the full path and file name for the desktop file. you can choose from the following discovery options: s Discover agent data from a PATROL Central environment. NOTE s The BMC Performance Manager Solutions CD contains many PATROL integration Performance Managers that provide integration with PATROL parameter data. If your PATROL environment contains a mixture of PATROL architectures. s Discover agent data from a PATROL desktop (DT) file. you can navigate to other pages by clicking the Status. but after you click Commit to initiate the process. When using this option. do not unload the corresponding KM from the PATROL Agent. s s s Use the addPATROL command in the bpmcli to add elements from a list of PATROL Agents. See “addPATROL” on page 260 for more information. Discover agent data from a PATROL Event Translation (PET) file. agent host name. or Configure tab. and user name. See “Cannot find errors when data discovery runs as a background process” on page 304. s s To view the status of the new elements. s Chapter 2 Getting started with the BMC Performance Manager Portal 29 . port number for the PATROL Agent. which requires that you specify the full path and file name for the configuration file. Discover PATROL Agent data by specifying a comma-separated value (CSV) file that contains the element name. which requires that you specify credentials for a PATROL Console Server. locate and view the portal.log file.

select Elements to open the Elements page. Before you begin s The Portal requires an RTserver to access a Management Profile. select PATROL Management Profile(s). select Infrastructure Element. you can specify Management Profiles for the Portal to use to discover PATROL Agents. and click Next. See “Specifying RTservers for the BMC Performance Manager Portal” on page 300. 6 On the Elements–Add Infrastructure Element–Select PATROL Agent for Configuration page. 30 BMC Performance Manager Portal Monitoring and Management Guide . See “Using the installation wizard to install the RSM program” on page 84. and click Next. s s To discover PATROL Agents in a PATROL Central environment 1 Click the Configure tab. If you did not specify an RTserver and security level during installation of the Portal. 2 If the Elements–Add–Type of Element page is displayed.Methods for discovering PATROL Agent data Discovering PATROL Agents in a PATROL Central environment If your business uses the PATROL Central environment to manage infrastructure. and click Next. s The KMs must be loaded on the PATROL Agent. 4 On the Elements–Add Infrastructure Element–Identification page. The discovery process also matches the PATROL integration Performance Managers with the KMs and obtains parameter thresholds from the agent. Consider creating or updating Management Profiles so that you can quickly select the agents that you want. 3 On the Elements–Add Infrastructure Element–Select Remote Service Monitor page. and click Next. Ensure that at least one RSM has been installed and is available to the Portal. select PATROL Integration. specify the object groups for the new elements. 5 On the Elements–Add Infrastructure Element–Select Group page. and click Next. select an RSM to collect data from the discovered agents. you must configure these Portal settings before proceeding. and then click Add. proceed to step 3 on page 42. and under Tasks. see the PATROL Central documentation. otherwise. For more information about the components in the PATROL Central environment.

NOTE The data discovery process can take a long time. During discovery. If you navigate away from this page. specify the credentials to access the selected console server. s To monitor the discovered agents. select Monitor discovered PATROL Agents with PATROL Agent Availability and Health Monitor. s s s s The data discovery process begins. Chapter 2 Getting started with the BMC Performance Manager Portal 31 .Methods for discovering PATROL Agent data 7 On the Elements–Add Infrastructure Element–Console Server Credentials page. and click Apply to All. or port from that which was discovered on the agent. Events. type the credentials in Agent User Name and Agent Password. select a saved credential from the Shared Credentials list. Agent credentials might already be displayed on this page. on the Elements–Add Infrastructure Element–PATROL Agent Credentials page. select the console server. In addition to matching application classes and parameters between PATROL integration Performance Managers and KMs. If the Management Profile had the PATROL Agent credentials saved in the console server’s profile impersonation table. agent name. To provide the credentials for individual agents. the Portal obtains the parameter thresholds from the discovered agents. select the Management Profiles to use. the Console Server list is empty and you cannot continue. B Type the user credentials for the Portal to use to access the console server. you will not be able to view the Results Summary page. specify the credentials for the selected agents. To apply shared credentials to all agents. If your Portal administrator has not specified an RTserver. To apply the same credentials to all agents. and click Next. type the new properties in the corresponding boxes for each applicable agent. or select a saved credential from the list. 9 If necessary. and click Commit. and click Next: A From the list. 8 On the Elements–Add Infrastructure Element–Integrate Managed Systems page. or Configure tab. type the credentials in corresponding Agent User Name and Agent Password boxes. To change the default element name. you can navigate away from this page by clicking on the Status. and click Apply to All.

The discovery process also matches the PATROL integration Performance Managers with the KMs and obtains parameter thresholds from the agent. 2.Methods for discovering PATROL Agent data 10 When the Elements–Add Infrastructure Element–Collect Application and Threshold Data screen shows that it has finished collecting data. s 32 BMC Performance Manager Portal Monitoring and Management Guide .x consoles. After you finish adding the element to the Portal. click Summary to display the Elements–Add Infrastructure Element–Results Summary page. take the following actions: 1. you can use a desktop file to discover PATROL Agents. Under Application Classes. For information about creating a desktop file. On the Configure tab. you can — access the Status tab to view the new parameters and their values — access the log files to check for errors encountered during discovery s Begin viewing measurements collected by the RSM program by selecting the Status and Reports tabs. This page shows the KMs on the agents that matched the available PATROL integration Performance Managers for your Portal. Where to go from here s If you navigated to other tasks or object views during the discovery process. the RSM accesses the PATROL Agent to collect parameter values. You might need to wait a minute or two for the Portal to receive the initial parameter values and update the Status tab.dt) from the console. click Edit. s Using a PATROL desktop file to discover PATROL Agents If your business uses PATROL 3. You must have already saved a desktop file (*. select the element in the navigation pane to open the element Properties page. 11 Click Done to return to the Elements page. Before you begin s You must have at least one RSM installed and available to the Portal. See “Using the installation wizard to install the RSM program” on page 84. see your console documentation. To access element thresholds. View or edit parameter thresholds on the new elements.

Methods for discovering PATROL Agent data To use a PATROL desktop file to discover PATROL Agents 1 Click the Configure tab. type the credentials in corresponding Agent User Name and Agent Password boxes. select PATROL Integration. and click Apply to All. 4 On the Elements–Add Infrastructure Element–Identification page. To provide the credentials for individual agents. In File Name. 2 If the Elements–Add–Type of Element page is displayed. select an RSM to collect data from the discovered agents. proceed to step 3. select a saved credential from the Shared Credentials list. or select a saved credential from the list. type the full path and file name for the desktop file. 8 On the Elements–Add Infrastructure Element–PATROL Agent Credentials page. select Elements to open the Elements page. and click Next: s s Click Browse to select a desktop file. To change the default element name. and under Tasks. 3 On the Elements–Add Infrastructure Element–Select Remote Service Monitor page. specify the credentials for the selected agents. and click Next. and click Apply to All. 6 On the Elements–Add Infrastructure Element–Select PATROL Agent for Configuration page. s To monitor the discovered agents. 7 On the Elements–Add Infrastructure Element–Console Desktop File page. and click Next. 5 On the Elements–Add Infrastructure Element–Select Group page. specify the object groups for the new elements. To apply the same credentials to all agents. type the new properties in the corresponding boxes for each applicable agent. s s s s Chapter 2 Getting started with the BMC Performance Manager Portal 33 . select Infrastructure Element. select Monitor discovered PATROL Agents with PATROL Agent Availability and Health Monitor. and then click Add. and click Next. agent name. or port from that which was discovered on the agent. and click Next. select Console Desktop File(s). and click Next. and click Commit. To apply shared credentials to all agents. type the credentials in Agent User Name and Agent Password. use one of the following options to specify the desktop file. otherwise.

take the following actions: 1. In addition to matching application classes and parameters between PATROL integration Performance Managers and KMs. Where to go from here s If you navigated to other tasks or object views during the discovery process. This page shows the KMs on the agents that matched the available Performance Managers on your Portal. select the element in the navigation pane to open the element Properties page. the RSM accesses the PATROL Agent to collect parameter values. View or edit parameter thresholds on the new elements. the Portal obtains the parameter thresholds from the discovered agents. you can navigate away from this page by clicking on the Status. On the Configure tab. NOTE The data discovery process can take a long time. Events. To access element thresholds. If you navigate away from this page.Methods for discovering PATROL Agent data The data discovery process begins. 2. or Configure tab. After you finish adding the element to the Portal. Under Application Classes. click Summary to display the Elements–Add Infrastructure Element–Results Summary page. 10 Click Done to return to the Elements page. you can — access the Status tab to view the new parameters and their values — access the log files to check for errors encountered during discovery s Begin viewing measurements collected by the RSM program by selecting the Status and Reports tabs. During discovery. you will not be able to view the Results Summary page. You might need to wait a minute or two for the Portal to receive the initial parameter values and update the Status tab. click Edit. s 34 BMC Performance Manager Portal Monitoring and Management Guide . 9 When the Elements–Add Infrastructure Element–Collect Application and Threshold Data screen shows that the Portal has finished collecting data.

and click Next. In File Name.Methods for discovering PATROL Agent data Using a PET file to discover PATROL Agents If your business has a PATROL 3. and click Next. The discovery process also matches the PATROL integration Performance Managers with the KMs and obtains parameter thresholds from the agent. select PET Configuration File(s). and click Next: s s Click Browse to select a PET file. Before you begin s You must have at least one RSM installed and available to the Portal. you can use a PET file to discover PATROL Agents. Chapter 2 Getting started with the BMC Performance Manager Portal 35 . 6 On the Elements–Add Infrastructure Element–Select PATROL Agent for Configuration page. type the full path and file name for the PET file. 2 If the Elements–Add–Type of Element page is displayed. specify the object groups for the new elements. select Infrastructure Element. 7 On the Elements–Add Infrastructure Element–PET File page. 4 On the Elements–Add Infrastructure Element–Identification page. select an RSM to collect data from the discovered agents. select PATROL Integration. otherwise. and under Tasks. 5 On the Elements–Add Infrastructure Element–Select Group page. You must have used the PATROL Event Translation Configuration utility to create a PET file. 3 On the Elements–Add Infrastructure Element–Select Remote Service Monitor page. and click Next. use one of the following options to specify the desktop file. and click Next. s To use a PET file to discover PATROL Agents 1 Click the Configure tab. and then click Add. See “Using the installation wizard to install the RSM program” on page 84. proceed to step 3. and click Next. select Elements to open the Elements page.x environment without a console.

or Configure tab. Events. and click Apply to All. type the new properties in the corresponding boxes for each applicable agent. or select a saved credential from the list. type the credentials in Agent User Name and Agent Password. agent name. To change the default element name. and click Apply to All.Methods for discovering PATROL Agent data 8 On the Elements–Add Infrastructure Element–PATROL Agent Credentials page. s The data discovery process begins. click Summary to display the Elements–Add Infrastructure Element–Results Summary page. specify the credentials for the selected agents. NOTE The data discovery process can take a long time. and click Commit: s To monitor the discovered agents. To apply the same credentials to all agents. the RSM accesses the PATROL Agent to collect parameter values. You might need to wait a minute or two for the Portal to receive the initial parameter values and update the Status tab. To provide the credentials for individual agents. s s s To apply shared credentials to all agents. you can navigate away from this page by clicking on the Status. In addition to matching application classes and parameters between PATROL integration Performance Managers and KMs. the Portal obtains the parameter thresholds from the discovered agents. After you finish adding the element to the Portal. 10 Click Done to return to the Elements page. If you navigate away from this page. select Monitor discovered PATROL Agents with PATROL Agent Availability and Health Monitor. 36 BMC Performance Manager Portal Monitoring and Management Guide . you will not be able to view the Results Summary page. This page shows the KMs on the agents that matched the available Performance Managers for your Remote Service Monitor. 9 When the Elements–Add Infrastructure Element–Collect Application and Threshold Data screen shows that is has finished collecting data. type the credentials in corresponding Agent User Name and Agent Password boxes. select a saved credential from the Shared Credentials list. or port from that which was discovered on the agent. During discovery.

take the following actions: 1. On the Configure tab. To access element thresholds. View or edit parameter thresholds on the new elements. you can — access the Status tab to view the new parameters and their values — access the log files to check for errors encountered during discovery s Begin viewing measurements collected by the RSM program by selecting the Status and Reports tabs. Before you begin s You must have at least one RSM installed and available to the Portal. the row is ignored s s s s s Chapter 2 Getting started with the BMC Performance Manager Portal 37 . 2. You must have a CSV file that contains the following properties (in the order specified) for each new element: PATROL Agent data required in CSV file Notes s s s Table 2 Value element name host name port number user name password value cannot exceed 256 characters if empty. you can identify the agents by uploading the file to the Portal. select the element in the navigation pane to open the element Properties page. See “Using the installation wizard to install the RSM program” on page 84. the row is ignored cannot exceed 256 characters if empty. s Using a CSV file to discover PATROL Agents If you have the PATROL Agents listed in a comma-separated value (CSV) file. the row is ignored cannot exceed 256 characters value is not required cannot exceed 256 characters value is not required if value is present. click Edit.Methods for discovering PATROL Agent data Where to go from here s If you navigated to other tasks or object views during the discovery process. it must be PEM encrypted s s if empty. Under Application Classes.

and click Next: s s Click Browse to select the file. To apply shared credentials to all agents. type the credentials in Agent User Name and Agent Password.Methods for discovering PATROL Agent data To use a CSV file to discover PATROL Agents 1 Click the Configure tab. proceed to step 3. select a saved credential from the Shared Credentials list. 5 On the Elements–Add Infrastructure Element–Select Group page. and click Next. or port from that which was discovered on the agent. select Monitor discovered PATROL Agents with PATROL Agent Availability and Health Monitor. use one of the following options to specify the file. otherwise. 4 On the Elements–Add Infrastructure Element–Identification page. specify the credentials for the agents listed in the CSV file. and click Apply to All. To provide the credentials for individual agents. and click Next. type the new properties in the corresponding boxes for each applicable agent. and click Commit: s To monitor the discovered agents. 6 On the Elements–Add Infrastructure Element–Select PATROL Agent for Configuration page. 3 On the Elements–Add Infrastructure Element–Select Remote Service Monitor page. select an RSM to collect data from the discovered agents. specify the object groups for the new elements. and click Next. agent name. select Infrastructure Element. type the credentials in corresponding Agent User Name and Agent Password boxes. and under Tasks. select Comma Separated Values (CSV file(s). and then click Add. 2 If the Elements–Add–Type of Element page is displayed. s s s s 38 BMC Performance Manager Portal Monitoring and Management Guide . In File Name. and click Next. To apply the same credentials to all agents. 7 On the Elements–Add Infrastructure Element–CSV File page. To change the default element name. and click Apply to All. or select a saved credential from the list. 8 On the Elements–Add Infrastructure Element–PATROL Agent Credentials page. select Elements to open the Elements page. and click Next. select PATROL Integration. type the full path and file name for the file.

select the element in the navigation pane to open the element Properties page. In addition to matching application classes and parameters between PATROL integration Performance Managers and KMs. the Portal obtains the parameter thresholds from the discovered agents. After you finish adding the element to the Portal.Methods for discovering PATROL Agent data The data discovery process begins. or Configure tab. you can navigate away from this page by clicking on the Status. click Edit. Events. 10 Click Done to return to the Elements page. You might need to wait a minute or two for the Portal to receive the initial parameter values and update the Status tab. 2. click Summary to display the Elements–Add Infrastructure Element–Results Summary page. s Chapter 2 Getting started with the BMC Performance Manager Portal 39 . To access element thresholds. Under Application Classes. take the following actions: 1. 9 When the Elements–Add Infrastructure Element–Collect Application and Threshold Data screen shows that is has finished collecting data. View or edit parameter thresholds on the new elements. you can — access the Status tab to view the new parameters and their values — access the log files to check for errors encountered during discovery s Begin viewing measurements collected by the RSM program by selecting the Status and Reports tabs. This page shows the KMs on the agents that matched the available Performance Managers on your Portal. you will not be able to view the Results Summary page. During discovery. On the Configure tab. the RSM accesses the PATROL Agent to collect parameter values. If you navigate away from this page. Where to go from here s If you navigated to other tasks or object views during the discovery process. NOTE The data discovery process can take a long time.

The following conditions can cause discrepancies between the parameter thresholds and application classes in the PATROL integration Performance Managers and the PATROL Agent: s s s changing the parameter thresholds on the PATROL Agent removing application classes on the PATROL Agent adding application classes on the PATROL Agent When you synchronize parameter values. you can also choose to monitor the health and availability of the selected PATROL Agents. The Portal does not synchronize PATROL integration parameters for elements to which an element profile has been applied.list property on page 342 for more information.migrate. s By default. You can provide a list of parameters to exclude from the synchronization process by updating the padm. you will not be able to view or save the Results Summary report. see “Element Profiles task” on page 51. For more information about element profiles.Synchronization of thresholds and application classes Synchronization of thresholds and application classes Not only can you manually change parameter thresholds. the Portal synchronizes the thresholds for all parameters that it discovers for the specified elements. but if you do. When synchronizing thresholds.exclude. See “PATROL Agent health monitoring” on page 317 for more information.threshold.update. See the padm.properties file. you can navigate to other tabs and options on the Portal during the synchronization process. the following limitations apply: s Updating PATROL integration parameters for more than 100 elements can take a long time. 40 BMC Performance Manager Portal Monitoring and Management Guide . but you can synchronize the parameter thresholds and application classes in the PATROL integration Performance Managers with those on the PATROL Agent through the Portal. Like with discovery.

and click Refresh PATROL Integration: s If you select elements from the object tree. 3 On the Elements page. If you do not select elements from the object tree. 4 If necessary. 6 Click Done to return to the Elements page See the Help for more information about synchronizing application classes and threshold values. and click Commit to open the Elements–Refresh PATROL Integration–Collect Application. you can navigate away from this page by clicking on any of the Portal tabs or by selecting another task from the Configure tab. the Portal deletes the element.” NOTE The BMC Performance Manager Portal requires that an infrastructure element have at least one application class assigned to it. modify the selections. During this process. click Refresh PATROL Integration to synchronize the parameter values in the Portal and the PATROL Agent. 5 When the Elements–Refresh PATROL Integration–Collect Application. The Elements–Refresh PATROL Integration–Results Summary page shows the status of the synchronization for the specified elements and PATROL Agents. This can occur if you unload all the KMs on a PATROL Agent and then synchronize the application classes. However. Chapter 2 Getting started with the BMC Performance Manager Portal 41 . if you navigate away from this page. click Summary. optionally select elements in the object tree. Threshold Data page and start the synchronization process. select the Elements task. The synchronization process can take a long time. “BMC Performance Manager Portal command-line interface. To initiate the synchronization from a command line. If the synchronization process removes all of the application classes from an element. see Chapter 8. Threshold Data page shows that it has finished collecting data. 2 On the Elements page.Synchronization of thresholds and application classes To manually synchronize PATROL integration parameters with those on the PATROL Agent 1 Select the Configure tab. the Portal searches the selected elements for PATROL integration application classes. and in the navigation pane. you cannot view the Elements–Refresh PATROL Integration–Results Summary page. the Portal searches all elements in the account for PATROL integration application classes. s The Elements–Refresh PATROL Integration–Select Elements page lists the elements that use PATROL Integration application classes.

2 If the Elements–Add–Type of Element page is displayed. objects in the BMC Atrium CMDB that do not have a trusted host are not included in any of the search results. If you apply a Platform restriction. proceed to step 3. select an RSM to collect data about the discovered infrastructure objects. select Discover from BMC Atrium CMDB. The Portal search queries the BMC. and click Next. To add infrastructure objects from the BMC Atrium CMDB 1 Click the Configure tab. 42 BMC Performance Manager Portal Monitoring and Management Guide . If you apply the Host Name restriction. you can use the Discover from BMC Atrium CMDB option to access filters to restrict the objects that the Portal finds in the BMC Atrium CMDB. The BMC Topology Discovery program is an example of a BMC Software product that populates the trusted host attribute. The BMC Performance Manager Portal also populates this attribute when you add an infrastructure element and assign an operating system application class. otherwise. select Elements to open the Elements page. and click Next.ASSET dataset in the BMC Atrium CMDB. 3 On the Elements–Add Infrastructure Element–Select Remote Service Monitor page. and under Tasks. and click Next. When you identify the infrastructure element. The search results are only as good as the data: s If you apply an IP address restriction. objects in the BMC Atrium CMDB that have an empty platform attribute are not included in any of the search results. and then click Add. select Infrastructure Element. objects in the BMC Atrium CMDB that do not have an IP address are not included in the search results. s s See “BMC Atrium CMDB integration” on page 219 for more information about how the BMC Performance Manager Portal can provide data to and consume data from the BMC Atrium CMDB.Integrating infrastructure elements from the BMC Atrium CMDB Integrating infrastructure elements from the BMC Atrium CMDB You can add BMC Atrium Configuration Management Database (BMC Atrium CMDB) infrastructure objects to the Portal by using the Elements task. 4 On the Elements–Add Infrastructure Element–Identification page.

acme2. All of your selections must have the same platform. type a character string in Host Name. specify the parameters to monitor. Click Select All to select all CIs in the list. 9 On the Elements–Add Infrastructure Element–Thresholds page. set the element thresholds for each parameter. The string that you type has an implied wild card appended to the end. specify the properties and authentication credentials that the RSM must have to access the specified elements. select the objects to add as infrastructure elements. To filter CIs by operating system. 6 If necessary. typing acme would retrieve acme1. type the address in the IP Address text boxes. and acme3 from the BMC Atrium CMDB. 10 Click Finish. then you cannot specify a platform. s 7 On the Elements–Add Infrastructure Element–Application Classes page. on the Elements–Add Infrastructure Element–Select Group page. and click Search: s To filter CIs by host name. s s Select the check boxes to select individual CIs.Integrating infrastructure elements from the BMC Atrium CMDB 5 On the Elements–Add Infrastructure Element–Discover from BMC Atrium CMDB page. If none of the CIs that you selected from the BMC Atrium CMDB had a platform defined for it. select an option from Platform. s B From the search results under CIs Found in the BMC Atrium CMDB. provide the search criteria that the Portal uses to retrieve CIs from the BMC Atrium CMDB. For example. 8 On the Elements–Add Infrastructure Element–Properties and Credentials page. specify the platform and an object group for the new elements: s If at least one of the CIs that you selected from the BMC Atrium CMDB had a platform defined for it. If you select a CI that has a platform specified and a CI that does not have a platform specified. s To filter CIs by IP address. specify the search criteria for the Portal to use when retrieving objects from the BMC Atrium CMDB. the Portal assumes that both CIs have the specified platform. then you can select a platform. and click Next: A Under Search for Configuration Items (CIs). Chapter 2 Getting started with the BMC Performance Manager Portal 43 .

application classes. Select the Configure tab. click Done to return to the Elements page. You might need to wait a minute or two for the Portal to receive the initial parameter values and to update the Status tab. 11 When the Portal has finished adding elements to the database. the Portal remains active and does not time out due to inactivity. When the Portal has finished adding the elements to the database. perform the following actions: 1. 3. After you finish adding the element to the Portal. locate BMC Atrium CMDB Status. In the navigation pane. individual elements. Under General Properties. select the infrastructure object. opens the active Status page in a new window Page control Auto Refresh 44 BMC Performance Manager Portal Monitoring and Management Guide . TIP To view the reconciliation status of the new element. the Done button becomes available. The status icons and color-coded status bars enable you to proactively identify and resolve substandard performance problems before they become severe. 2. Viewing object status The Status tab provides a current snapshot of the objects in the account. You can view the status of the entire account. the RSM accesses the element to collect parameter values.Viewing object status The Elements–Add Infrastructure Element–Progress Page opens. its groups. The Status tab provides the tab controls shown in Table 3: Table 3 Page controls on Status tab (part 1 of 2) Description enables or disables automatic update of the page When selected. You can use the icons at the top of the tab to print the status page or send the page to email recipients. and parameters.

Portal and infrastructure status views Table 3 Page controls on Status tab (part 2 of 2) Description opens a printer-friendly view of the page in a new window opens an email window that contains the active view of the Status tab Page control NOTE If the parameter count exceeds 1000. because one of the objects has a status of alarm. Portal and infrastructure status views The Status tab shows the most recent values received from the RSM. One of the objects in the Infrastructure group has a status of critical alarm. the Expand All and Collapse All buttons do not display on the Status tab. In Figure 2. the status of the account is warning. the account also has a status of alarm. This means that if one parameter for one of the elements in the account has a status of warning and all of the remaining parameters for the other elements have a status of OK. The solid red bar shows that the account has a status of critical. Figure 2 Account view on the Status tab The summary bar shows that one object has a status of critical. Chapter 2 Getting started with the BMC Performance Manager Portal 45 . The object statuses reflect the worst parameter status in the selected object.

the chart shows summarized data values for each hour. The time-interval controls enable you to change the reporting interval for the chart. or parameter on the Status page opens the history chart in a new window. s When you are viewing a time period within 12 hours of the time that you request the chart. When you are viewing a period greater than 12 hours from the collection time. the chart is blank. the red and yellow lines show the alarm and warning thresholds relative to the reported values. Clicking Figure 3 enables you to export the data to a file for use in other applications. By default. application class. Parameter history chart alarm threshold warning threshold 46 BMC Performance Manager Portal Monitoring and Management Guide .Individual parameter history charts Individual parameter history charts Parameter history charts show the parameter values for a selected parameter during a user-specified time. s In Figure 3. If the selected time period has no raw data. the chart shows raw data values. Selecting for a parameter on an element. the parameter history chart shows the raw data values collected during the most recent six hours.

Parameter history tables Parameter history tables Selecting Table View from the list box on the parameter history chart opens the parameter history table for the parameter. as shown in Figure 4 on page 47. click the warning button. shown in Figure 5. Parameter history table Parameter filtering When viewing the status for the element. but you can choose time intervals up to 10 days. enable you to filter the parameters in the list to those that match or exceed the selected status. Clicking Figure 4 enables you to export the raw data to a file for use in other applications. To list parameters in alarm and warning. click the OK button. application class. By default. the Status tab lists the parameters in the selected object and the status of each parameter. The parameter history table shows the values for the raw data collected for the selected parameter. and OK. the table shows the values for the last six hours. Chapter 2 Getting started with the BMC Performance Manager Portal 47 . and application instance objects. warning. The status buttons at the top of the Status tab. Figure 5 Buttons to filter parameters on the Status tab To list parameters in alarm. To list only parameters in alarm. click the alarm button.

Parameter filtering

The status buttons act as toggles.
s s

To apply the filter, click the applicable status button. To remove the filter and show all parameters for the selected object, click the status button again.

48

BMC Performance Manager Portal Monitoring and Management Guide

Chapter

3

3

Users and administrators
This chapter describes how users can configure the BMC Performance Manager Portal for their accounts and how administrators can configure the accounts of their users, their providers, and the BMC Performance Manager Portal. For general configuration procedures that apply to all modules, see the BMC Portal Getting Started guide. This chapter presents the following topics: User configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Account Information task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blackout Periods task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Password task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dashboards task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Element Profiles task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Elements task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring On/Off task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notifications task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Object Groups task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personal Preferences task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Service Monitors task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shared Credentials task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tags task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Groups task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Users task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administrator configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks on the Accounts tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks on the Provider tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks on the Portal tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 50 50 50 51 51 51 55 55 56 59 60 60 60 61 62 62 63 64 64 66

Chapter 3

Users and administrators

49

User configuration options

User configuration options
Each account can have one or more users who can access the Portal to view information about the account and configure the account for their use. The BMC Portal enables administrators to create and configure accounts that grant users Read Only, Full Access, or a combination of rights and permissions for their accounts. The user rights determine the user interface options that a user can see and select. User permissions determine which infrastructure objects that you can view and configure. The Configure tab provides a list of tasks from which you can choose. The following sections describe the tasks available on the Configure tab for users who have Full Access rights for all tasks.

NOTE
This book and the Help describe options and text boxes available to users with Full Access rights for all tasks. If your account does not have full access, you might not see every option.

See the Help and the BMC Portal Getting Started guide for information about accounts, user groups, users, and rights and permissions.

About task
The About task opens a page that contains information about the version of the installed BMC Portal and modules.

Account Information task
The Account Information task opens a page that lists basic information about your account, including account name, language preference for the account, information about the primary account contact, and email format preference for receiving email messages from the Portal.

Blackout Periods task
If your user ID has adequate permissions, you can use the Blackout Periods task to schedule one-time or recurring blackout periods for all objects in the account, for all objects in selected groups, and for individual objects.

50

BMC Performance Manager Portal Monitoring and Management Guide

Change Password task

NOTE
When you delete objects, the blackout periods for those objects are deleted.

You can use blackout periods to keep the Portal from notifying you about problems during times when you know that your system will not be operating, such as during scheduled routine maintenance.

Change Password task
The Change Password task enables users to change their logon credentials. Only users with internal database authentication can use this task. See “Users task” on page 62 for more information about internal database authentication.

Dashboards task
The Dashboards task enables you to create a customizable view, or dashboard, that displays your most important, but possibly disparate, objects in one window (for example, parameters, reports, and HTML pages). Objects in a dashboard display the same live data that the original object displays. You can specify the number of objects to display in the dashboard. That number determines the size of the underlying layout grid in the dashboard window. Each section of the grid represents a place where you can position an object view. The size of an individual displayed object view depends on the number of sections in the grid.

Element Profiles task
The Element Profiles task enables you to create platform-independent descriptions, or profiles, to manage the infrastructure elements in your account. An element profile acts as a template that enables you to quickly change the properties associated with your infrastructure elements. Element profiles are especially useful when you need to manage many elements that share common properties because you can apply a single element profile to multiple objects. When applying the template to elements, you can override thresholds and properties on specified elements.

Chapter 3

Users and administrators

51

Element Profiles task

Using element profiles
You can use the following methods to create and apply element profiles:
s

Create an element profile by explicitly defining profile properties. Create an element profile from an existing element and assign the profile to the element. Apply an existing element profile to a new or existing element. Modify the element profile that is assigned to an element

s

s

s

If you have applied an element profile to an element, you can quickly change the properties for that element and all elements associated with the profile by changing the properties of its element profile or by applying a different element profile.

Properties controlled by element profiles
Element profiles enable you to apply and manage the following properties to many elements at one time:
s s s s

application classes assigned to the elements collection interval for the application class threshold values for parameters credentials and properties required for the application classes, including properties for child classes (when applicable for the application class)

If you remove an element profile from an infrastructure element, the profile properties are copied to the infrastructure element, and any future changes applied to the element profile have no effect on the element.

How the Portal applies element profiles
When you assign an element profile to an element, the following rules apply:
s

Any application classes previously assigned to the element that are not in the element profile are removed from the element. For any application classes previously assigned to the element that are also in the element profile, the Portal retains the application class history data. The thresholds in the element profile supersede any differing thresholds in the application class on the element.

s

52

BMC Performance Manager Portal Monitoring and Management Guide

Element Profiles task

s

Modifications made to an element profile by adding or removing application classes, or by modifying parameter thresholds, affect all assigned elements. When you create an element profile that includes application classes that support discovered instances, the Portal applies the profile properties to each discovered instance. When you assign an element profile, the Portal filters out any application classes in the profile that do not apply to the platform of the element.

s

s

Overriding element profile settings
You can override properties and threshold settings defined by a profile without disassociating the profile from the element.
s s

When you override properties, you can also change authentication credentials. When you override thresholds, you can change warning and alarm threshold values (including the on or off flag) and Alert After properties.

When overriding a profile, the following rules apply:
s

When you override thresholds at the parent level of discovered instances or userdefined instances, then the override propagates to all discovered instances or user defined instances (existing or newly discovered), unless they are already overridden at the child level. When you override thresholds at the parent level of discovered instances or userdefined instances, then at the child level, Global appears in the row for the parameter in the Overridden column. At the parent level, if the same parameter exists, Local appears in the row for the parameter in the Overridden column. When you override thresholds at the instance level, Local appears in the row for the parameter in the Overridden column. When you make threshold changes at the Element-Profile level, and the parent and instance levels are not overridden, then the Overridden column is blank. When you disable an override at the instance level, — if the parent of the instance is overridden, the parent thresholds are used and the label in the row for the parameter is changed to Global in the Overridden column. — if the parent of the instance is not overridden, the Element-Profile thresholds are used, and the Overridden column is blank

s

s

s

s

Chapter 3

Users and administrators

53

Element Profiles task

s

When you disable an override at the parent level, the Element-Profile thresholds are used and the Overridden column is blank In cases where Elements are bound to an Element-Profile, you cannot override the active or inactive state properties of parameters; the Active column is disabled for editing. For more information, see “Deactivating parameters” on page 116.

s

You can use the element Properties page to view thresholds and properties that are overridden for the element.

Changing the report update interval for elements by using element profile
You cannot override the report update interval at the element level. You can change the report update interval by editing the general properties for the element. However, editing the report update interval at the element profile level propagates that change to all elements assigned to that element profile, regardless of any settings at the element level. For example, if the following are the settings for the report update interval:
s s

At the element profile level, the report update interval is set to 10 minutes. Elements that are assigned to this same element profile have report update intervals set at 5 minutes and 15 minutes.

If you then change the report interval at the element profile level to 15 minutes, the report update interval is set to 15 minutes for all of the elements assigned to this element profile, regardless of the settings or changes made at the element level. For more details, see the drmop.default.reporting.interval.minutes property in Appendix C, “BMC Performance Manager Portal files.”

54

BMC Performance Manager Portal Monitoring and Management Guide

If you use a product like BMC Topology Discovery to discover IT objects and populate the BMC Atrium Configuration Management Database (BMC Atrium CMDB). Each infrastructure element corresponds to a system or device in your IT environment. Monitoring On/Off task The Monitoring On/Off task enables you to temporarily stop and restart s s remote data collection for selected objects reporting of collected data from agents Chapter 3 Users and administrators 55 . Following discovery. If you use PATROL Knowledge Modules (KMs) to monitor infrastructure. The discovery process matches the KMs in the agents with integration Performance Managers on the Portal and then obtains parameter thresholds from the agents and applies the thresholds to the parameters in the integration Performance Managers. the Portal can discover the host names of those infrastructure objects.Elements task Elements task The Elements task enables you to add infrastructure elements to the account. You can add many elements at a time by pasting a list of host names into a text box. see “Adding infrastructure elements for agentless monitoring” on page 25. you specify the monitoring attributes for those elements. You can use the following methods to add infrastructure elements: s Add elements by explicitly typing the element names and specifying the monitoring attributes for those elements. The Elements task also enables you to synchronize the parameter thresholds and application classes in the PATROL integration Performance Managers with those on the PATROL Agent. The task also enables you to change the properties associated with elements and to delete elements from the BMC Performance Manager Portal. s s For more information about adding elements to an account. you can configure the Portal to discover PATROL Agents.

Before a user or administrator can create a notification rule for this transport method. a Portal administrator must use the Global Properties page to configure the Portal for AlarmPoint integration. Concise email messages are suitable for pagers and other wireless devices. SNMP traps: The Portal can send SNMP traps for state change and general system problem events. In addition to creating an SNMP notification. Users can create notification rules for the following types of conditions: s state changes. BMC Impact Integration Web Services: You can use the BMC Impact Integration Web Services (BMC II Web Services) component to send state change and general system problem notifications to BMC Impact Manager. which occur when the status of an object changes to a state for which you want the Portal to send a notification general system problems. an RSM stops communicating with the Portal) s Users can configure the following types of notifications: s email messages: The Portal can send long or concise email messages for state change and general system problem events. a provider administrator must use the Notifications page on the Provider tab to configure a target BMC II Web Services server for the Portal. The Notifications task enables you to create rules that specify when and how the Portal sends notifications in response to system problems or state changes. you must also specify the host names of the servers to receive the traps. For more information about configuring the Portal to send notifications to an AlarmPoint server. See “SNMP traps” on page 236. Before a user or administrator can create a notification rule for AlarmPoint. which occur when a system problem prevents the Portal from receiving information about an object (for example. s s s Notification rules specify the following properties: s type of event or system problem to trigger notification length of time that the Portal waits after the change in event severity before sending notification s 56 BMC Performance Manager Portal Monitoring and Management Guide .Notifications task Notifications task When conditions cause an object to violate a threshold or change its state. you can configure the Portal to send state change and general system problem notifications to AlarmPoint. AlarmPoint: If you have AlarmPoint installed. the BMC Portal can send a notification about the event. see “Event integration using AlarmPoint” on page 228 and the BMC Portal Getting Started guide.

and then copy that rule and modify the wait time and notification recipients for the other levels in the escalation order. or AlarmPoint the affected objects (groups or objects within groups) notification recipients s s You can apply the same notification rules to all objects in the account. enabling you to incorporate or establish an escalation procedure. infrastructure email notifications provide the following information: s Element email notifications contain the — status of the element — name of the infrastructure element — date and time at which the event was detected — parent objects of the element — account name for the element — ID for the account Chapter 3 Users and administrators 57 . create one notification rule. you can set multiple notifications for objects. To customize the notifications. Also.Notifications task s transport method that the Portal uses to send notifications: email. TIP To quickly configure notification rules for an escalation procedure. Unless you customize them. You can create notification templates before you create notification rules and specify a template as you create or edit notification rules. The templates specify the subject and message for email notifications and the detail message field for SNMP notifications. you can create notification templates that you can apply to notification rules. SNMP. or you can create a template while creating or editing a notification rule. BMC II Web Services. or you can set different notification rules for each object (or object groups).

if you have selected the When Rules are violated and object is no longer in violation notification rule and the state of the object changes from Alarm to Unknown to OK. Therefore. the notification contains the following information for each parameter of the element that caused the element notification: — name of the infrastructure element — host name of the element — date and time at which the event was detected — application class for the parameter — name of the parameter — parameter status that triggered the event — current parameter value — warning or alarm threshold that was breached — host name for the RSM that detected the event s Parameter email notifications contain the — name of the element — host name of the element — date and time in which the event was detected — application class for the parameter — name of the parameter — parameter status that triggered the event — current parameter value — warning or alarm threshold that was breached — host name for the RSM that detected the event NOTE When the earlier state of the element or parameter is violated.properties file. If you must do so.services. contact BMC customer support.unknown.notification.support property to true. you must not set the value of the websdk. BMC recommends that in the internal. 58 BMC Performance Manager Portal Monitoring and Management Guide . BMC Portal sends the Unknown-OK notifications.ok.Notifications task Also. For example. depending upon the notification rule that is set. BMC Portal sends OK as a Clear notification.

you can select one or more object groups. s s Chapter 3 Users and administrators 59 . you can manage the objects in the object group as a single entity and view reports. You can create any number of object groups. the BMC Portal has the following top-level object groups that contain any object groups that you create: s Dashboards—populated by any module Business—created and populated by the BMC Impact Portal module Exceptions—created and populated by the BMC Performance Exception Detector s s module When you use the BMC Performance Exception Detector module. s Infrastructure—created and populated by the BMC Performance Manager Portal module When you use the BMC Performance Manager Portal module. scheduling blackout periods—Create groups of objects that have the same maintenance schedules. and you can create nested groups (groups that contain groups). Object groups can assist you with the following activities: s creating user permissions—Create groups of objects whose members require the same level of access. status. you must assign each new infrastructure element to at least one object group. User groups provide permission to access specific objects. After creating an object group. Instead of selecting individual objects during user group creation. and events for the group. By default.Object Groups task Object Groups task The Object Groups task enables you to create and modify object groups—containers— to organize the objects in your account. you can select one or more object groups. You choose how to create and organize the object groups in your account. Instead of selecting individual objects while you create a notification rule. Each account must contain at least one object group under one of the top-level object groups. you must assign each new detector to at least one object group. specifying objects to include in user notifications—Create groups of objects to which you assign the same notification criteria.

If you do not see an option to apply a shared credential when specifying credentials and properties for an application class. to provide agentless infrastructure monitoring and to mine parameter data from PATROL Agents. time zone. The BMC Performance Manager Portal module uses Remote Service Monitors. For more information. A user with the necessary permissions can add RSM computers to collect measurement data about the elements in an account. 60 BMC Performance Manager Portal Monitoring and Management Guide .Personal Preferences task Personal Preferences task The Personal Preferences task enables you to control the language. See “RSM program installation” on page 76 for more information about using and configuring RSM computers. The number of RSM computers that you need depends on the number and types of elements in your account and your high availability requirements. you can simultaneously modify the credentials of those elements by updating the properties for the shared credentials. or across multiple elements. Shared Credentials task The Shared Credentials task enables you to define and save credentials that you can apply to one or more elements. See “Security requirements for RSMs” on page 22 for more information about how security levels can affect RSMs. or RSMs (computers in which you have installed the Remote Service Monitor program). refresh rate. the security level of the monitored PATROL agents can also affect the number of RSMs required for your account. then the selected application class is not enabled for shared credentials. and provides the ability to view or suppress object status icons in the object tree when you are logged on with your user name. default view at logon. see the applicable Performance Manager documentation for the application class. If you use PATROL integration Performance Managers. When you apply shared credential to elements. Remote Service Monitors task The Remote Service Monitors task enables you to add and administer Remote Service Monitors for your account. NOTE The ability to apply shared credentials to an element is enabled in application classes. You can define shared credentials that the Portal can use across multiple application classes on a single element.

Tags task Tags are keywords that you can assign to objects in the account. Types of tags The Portal enables the following types of tagging: s system: dynamically and automatically assigned as you create or add objects to the account For example. Because the Portal does not restrict the number of keywords. delete. You can delete a shared credential only if it is not applied to an element. When you modify the properties in a shared credential. edit. Tagging objects with keywords enables you to quickly retrieve a list of objects that have the same keyword associations. s user-defined: represent how you want to monitor and manage your infrastructure Chapter 3 Users and administrators 61 . including those that obtain their properties from an element profile. You cannot explicitly change a system keyword. when you create a new object group. individual users can add keywords that are meaningful to them. s s s Preventing system lockouts on the monitored infrastructure elements Before changing the credentials on the monitored infrastructure. use the Monitoring Off or Blackout Periods task to stop the Portal from monitoring the systems that use the credentials.Tags task Guidelines for using shared credentials Users with the necessary rights can create. the Portal might lock out your systems before you have an opportunity to change the shared credential properties on the Portal. If you remove a shared credential from an infrastructure element. the Portal immediately updates the application class properties for the affected elements. the Portal assigns the object group name as the system keyword for the object. and view lists of elements using a shared credential. s You can apply a shared credential to individual elements or to an element profile. The Portal changes the system keyword if you change the name of its object. the properties in the shared credential are copied to the infrastructure element. If you do not temporarily stop monitoring before you change the system credentials.

enabling you to quickly access views of these objects. Users in the Full Access user group have access to all the features in the Portal and can add new users and user groups. After the initial implementation period has expired. The User Groups task enables you to create new user groups. after implementing changes on critical systems. Each user must belong to at least one user group. 62 BMC Performance Manager Portal Monitoring and Management Guide . users and user groups provide access rights and permissions on managed systems. The default user groups are Full Access and Read Only. You can create user groups that use the BMC Portal database to authenticate users. For example. The Users task enables full-access users to add more users to the account. consider using department names. operating system names. Users task A user is a unique identifier in the Portal that you specify to access the product. and users inherit the rights and permissions from the groups to which they belong. you would remove the tag from these objects. and application names as keywords. Each user must belong to at least one user group. As users are added to the Portal.User Groups task For example. Searching for tagged objects The navigation pane provides a Search box that you can use to retrieve objects tagged with specific system or user-defined keywords. Users inherit the rights and permissions from the groups to which they belong. User Groups task A user group is a collection of users that all have the same rights and permissions. or create user groups that use external directory servers to authenticate users. modify users. and delete users from the account. Together. You can create user groups to organize users according to rights and permissions. you might want to assign a keyword like to_watch to the corresponding infrastructure objects. Rights and permissions are assigned to user groups. You might also consider creating keywords that enable you to respond to temporary conditions. Users in the Read Only user group have read-only rights to all the Portal features and read-only permissions for all objects. they are assigned to one or more user groups.

When you configure LDAP or Active Directory server authentication. s An administrator with both Edit and See Other Providers and Their Accounts permission (a Portal administrator) can edit the provider. s When you use the internal database for authentication (the default option). Chapter 3 Users and administrators 63 . both.Administrator configuration options User authentication The Portal requires that all user names exist in the Portal database. and users for every account on the Portal. Each Portal needs at least one Portal administrator. Administrator configuration options Administrators can have one. A user name can contain spaces. or neither of the following permissions: s s Edit—enables the administrator to edit any accessible properties See Other Providers and Their Accounts—enables the administrator to access all accounts on the Portal The combination of these permissions determines how you can access and configure the Portal or any of the accounts on the Portal. but not consecutive spaces. administrators. Characters allowed for user names When adding users. but you cannot use only a space for the user name. An administrator with these permissions can also configure the Portal. assign account permissions that reflect the responsibilities of the administrator. you can use any combination of Unicode characters. When adding administrators to a provider. regardless of the authentication type configured by the Portal administrator. You can use the User task to change the predefined user credentials. all user information is saved in the internal database. you must create a user in the internal database for each native operating-system user that logs on to the Portal. s s Predefined user The BMC Portal installation program creates a full-access user (with user/user credentials) for the predefined account (My Account). When you configure native operating-system authentication. the Portal creates an internal user for each user specified in the directory server group.

s An administrator with Edit permission (a provider administrator) can configure the provider. but can impersonate all users on the Portal. each Portal has a Portal administrator that can log on by typing superadmin and superadmin for the user name and password. An administrator with this permission cannot edit account properties. and accounts.Tasks on the Accounts tab By default. Administrators with Edit or Edit and See Other Providers and Their Accounts permissions can see the Provider tab and perform the tasks described in this section. 64 BMC Performance Manager Portal Monitoring and Management Guide . and can approve or reject accounts for that provider. configure. Each provider has corresponding properties that affect the overall appearance of the user interface and the defaults that apply to the users and accounts for the provider. s Tasks on the Accounts tab The Accounts tab provides tasks that administrators can use to add. s Each provider has at least one administrator that can access all of the administration tools to maintain the provider properties and settings. each Portal has a provider administrator that can log on by typing admin and admin for the user name and password. s An administrator with See Other Providers and Their Users permission has readonly rights to the provider and Portal configuration. An administrator with neither permission has read-only rights to the provider configuration for that provider and can access all accounts for that provider. s The Help provides detailed information about each of the features on the Provider tab. By default. Tasks on the Provider tab Each organization that offers and supports the BMC Portal is a provider. Also. and approve accounts. See “Tasks on the Accounts tab” on this page. From this tab. administrators for that provider. administrators can help troubleshoot problems for their users by viewing activity logs and by using the Log On option to impersonate their users. administrators who provide support activities can use the tasks on the Accounts tab to proactively support their customers.

administrators assign an account type to the account. When generating the file. Administrators task The Administrators tasks enable administrators to add and modify administrators for a provider.Tasks on the Provider tab Account Types task The Account Types task enables administrators to configure default properties for the following categories of accounts: s s s trial—generally assigned to those trying the product paying—assigned to most users of the product internal—generally reserved for those who support the product and have accounts that they use for testing As accounts are added to the Portal. The page properties that you can change include the s s left and right banner images product name displayed in the Portal user interface and in the Help Licensing Information task The Licensing Information task provides the following subtasks that administrators can use to monitor and manage license usage: s The Performance Managers subtask enables administrators to generate CSV and text files that list the extent to which the accounts in a provider are using the Performance Managers to monitor their infrastructure. you can select all the accounts in the provider or a subset of the accounts. and the account assumes the default properties for the account type. and monitor license usage. maintain licenses. Administrators who have Edit and See Other Providers and Their Accounts permissions can add administrators for the Portal. s The Users subtask enables administrators to establish license thresholds for all accounts on the Portal. The Help provides detailed information about how to generate CSV files. Chapter 3 Users and administrators 65 . Administrators can adjust account settings after assigning the account type. Appearance task The Appearance task enables administrators to customize the user interface for all accounts associated with a provider.

The Help provides detailed information about each of the features on the Portal tab. Remote Service Monitors task When you enter provider administrator credentials (administrator with only Edit permission) during the installation of the RSM program. Properties task The Properties task enables you to add providers and modify provider characteristics. Administrators that have Edit permission can change the properties for their own providers.Tasks on the Portal tab Notifications task The Notifications task on the Provider tab enables you to establish and maintain notification rules that apply to all state change and general system problems events associated with a provider. See “Providerwide integration” on page 218 for more information about the transport methods that you can use. The Remote Service Monitors task enables you to administer shared RSMs for the provider. Licensing Information task The Licensing Information task enables Portal administrators monitor license usage across all accounts on the Portal. they enable you to integrate events from the BMC Performance Manager Portal module with other modules and event management systems. Administrators with Portal permission (both Edit and See Other Providers and Their Accounts permissions) can see the Portal tab and perform these tasks. Tasks on the Portal tab The tasks associated with the Portal tab affect all accounts on the Portal. Administrators who have both Edit and See Other Providers and Their Accounts permissions can change the properties for all providers on the Portal. Global Properties task The Global Properties task enables administrators to set properties that can affect all providers and accounts in the Portal. Because these notification rules apply to all events in a provider. 66 BMC Performance Manager Portal Monitoring and Management Guide . you configure a shared RSM that multiple accounts can use to monitor infrastructure elements.

Performance Managers task RSMs use the application classes contained in Performance Managers to monitor groups of attributes on an infrastructure element. In addition to your ability to install solution application classes on the Portal. See Chapter 5. you configure a global RSM that all accounts on the Portal can use to monitor infrastructure. Administrators can also use this task to import new solution Performance Managers into the Portal. Chapter 3 Users and administrators 67 . “Performance Managers and application classes.Tasks on the Portal tab Mass Email task The Mass Email task enables Portal administrators send email to all or a subset of users and administrators on the Portal.” on page 113 for more information about importing solution Performance Managers and creating and maintaining custom Performance Managers. Administrators can use the Performance Manager Editor (PME) to modify the application classes in solution Performance Managers and to create and modify custom application classes for the accounts on the Portal. The Remote Service Monitors task enables you to administer global computers for the provider. administrators can use the Performance Managers task to create and maintain custom application classes. Remote Service Monitors task When you enter Portal administrator credentials during the installation of the RSM program.

Tasks on the Portal tab 68 BMC Performance Manager Portal Monitoring and Management Guide .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 RSM program installation. 94 RSM failover. . . . . . . . . . . . . . . . . . . . . . . . . 108 Chapter 4 Remote Service Monitors 69 . . . . . . . . . . . . . . . . . . . . . . . . . 95 Clustered RSM upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Configure Distributed Component Object Model (DCOM) and Windows Management Instrumentation (WMI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Stopping notifications for Unknown state events . . . . . . . 74 Notifications about RSM system problems . . . . . . . . . . . . . 96 RSM configuration and maintenance . . . . . . . . . . 93 Clustered RSM operating status . . . . . . . . . . . . . . . . . . 71 Communication between RSMs and elements . . . . . . . . . 106 Collecting log files . . . . . . . . . . . . . . . . . . . . . . . . 74 Communication between RSMs and PATROL Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Data execution prevention (DEP) configuration for the RSM . . . . . . . . . . . . . 95 Clustering RSMs . . . . 96 Configuration and maintenance tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Configuring an RSM to use a proxy server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Changing the maximum heap memory allocated for the Java VM on the RSM 106 Viewing the log files for the RSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Changing the credentials for an RSM. . . . . . . . . . . . . . . . . . . . 107 Automating basic information gathering for RSM issues . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Using the installation wizard to install the RSM program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 4 4 Remote Service Monitors This chapter presents the following topics that describe how to configure the monitoring component for the BMC Performance Manager Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Configuring the RSM to use HTTP protocol to communicate with the Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Using a silent installation to install the RSM program . . . . . . 94 RSM load-balancing . . . . . . . . . . . . . . . . 88 Upgrading the RSM Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . 70 Communication between the Portal and RSMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Changing the security level for an RSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Cluster types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Clustered RSMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 RSM computer system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Types of RSMs . . . . . . . . . . . . . . . . . . . . . . . . 94 Clustered RSM security considerations . . .

Each RSM has a utility program. also known as RSMs. . . Figure 6 on page 71 shows that the accounts in provider ABC can use the same shared RSM. 110 Using command-line options to uninstall the RSM program . .Overview RSM program uninstallation. 112 Overview The Remote Service Monitor (RSM) program runs as a Windows service (BMC Remote Service Monitor service). Types of RSMs The BMC Performance Manager Portal module uses the following types of RSMs to monitor accounts: s A dedicated RSM monitors only the elements in your account. . . . B. . . . . . . . . The accounts that use a shared RSM must belong to the same provider. The RSM Manager utility enables you to view current RSM status and settings. . . . The RSM must be able to resolve network addresses to the elements that it monitors and to the BMC Portal. . . . . 109 Using the installation wizard to uninstall the RSM program . . . . which acts as a single remote agent. . . The RSM does not save thresholds to its local computers. . . . . . . . Users in account D can also use the global RSM to monitor elements. . . . . . . You configure a dedicated RSM by downloading the RSM program from the Portal and installing it on a computer designated as an RSM. . . . . The RSM uses the parameter thresholds that are saved in the Portal database to monitor infrastructure. Figure 6 on page 71 shows a Portal where account D has a single dedicated RSM to monitor its elements. . s 70 BMC Performance Manager Portal Monitoring and Management Guide . . . Computers on which you have installed the RSM program. 109 Manually uninstalling the RSM program. . . and is installed with user credentials. . . . . . . . . . . . . The RSM. . that you can access from the Windows system tray on the RSM computer. . . . . and is installed with administrator credentials for an administrator that has only Edit permission. . . . Users in accounts A. . . . . . . . . . A shared RSM can monitor the elements in multiple accounts in a provider. . . and to configure the RSM. . and C can also use the global RSM. . . . . . . . the RSM Manager. . . . . . . although an account can have more than one dedicated RSM. . . are the components that provide the remote monitoring for the BMC Performance Manager Portal. monitors the elements in the accounts and sends parameter data values to the Portal web server. . . . . . . . . . . . . .

s Your Portal administrator determines the types of RSMs available for your account. An RSM cluster must contain RSMs of the same type.Communication between the Portal and RSMs s A global RSM can monitor elements for all accounts on the Portal. the RSM communicates with the Portal using HTTPS (port 443) and encrypts the data that it collects before sending it to the Portal web server. See “Clustered RSMs” on page 92 for more information about clustered RSMs. shared. Chapter 4 Remote Service Monitors 71 . it sends it to the application server. Administrators and users with adequate permission can download and install the RSM program. which sends the data to the Portal database. and is installed with administrator credentials for an administrator that has Edit and See Other Providers and Their Accounts permissions. A clustered RSM consists of two or more dedicated. or global RSMs configured to act as a single logical RSM. Figure 6 Types of Remote Service Monitors database web browser web server firewall application server shared RSM global RSM dedicated RSM Account A Account B Account C Account D Provider ABC Provider DEF Communication between the Portal and RSMs Each RSM initiates all communication between itself and the Portal web server. When placed inside the firewall. After the web server receives data from the RSM.

it deletes data older than 15 minutes. the RSM resumes normal communication with the Portal after the next heartbeat. If the RSM cannot successfully send the data to the Portal after 15 minutes of repeated attempts. the corresponding RSMs will fail to authenticate with the Portal and will not send parameter data to the Portal. Any data that the RSM drops appears as a data gap on reports. it caches the data and attempts to resend the cached data at the next heartbeat interval.properties file on the RSM computer. The heartbeat also confirms that the Portal and RSM are running the same product version and that they are both using the same user or administrator credentials. For information about changing this property setting. When a disabled user or administrator is enabled or when the credentials are corrected. If the user or administrator ID that installed an RSM becomes disabled or if its credentials are not kept synchronized. program upgrade—The RSM downloads the latest version of the RSM program after an upgrade of the Portal. You can set thresholds on the Properties page for elements. You can view this data on parameter history charts. s s Communication interruptions If an RSM cannot communicate with the Portal. and this process continues on every heartbeat interval until the communication is reestablished. s threshold violations—When the RSM detects a threshold violation for a parameter. NOTE By default the RSM stores cached data for 15 minutes while waiting for a response from the Portal. 72 BMC Performance Manager Portal Monitoring and Management Guide . Types of communication RSM-to-Portal communication falls into one of the following categories: s heartbeat—The RSM attempts to connect to the Portal every 30 seconds to ensure that the connection between the two components still exists. You can change the default time by resetting the MaxStoreAndForwardTime property in the portal-PortalWebServer. parameter report data—The RSM sends current parameter data at the report update interval defined for the element and whenever a parameter violates a threshold. Lengthening the time that the RSM caches data has a direct impact on system memory consumption. it immediately sends the value for all parameters in the associated application class to the Portal. see “Configuring the RSM to use HTTP protocol to communicate with the Portal” on page 103. see Table 56 on page 343. as described in the preceding paragraph.Communication between the Portal and RSMs To configure the RSM to use HTTP to communicate with the Portal.

the RSM sends any cached data that it has not deleted. EXAMPLE You install the BMC Performance Manager Express for Databases solution Performance Manager while installing the Portal. RSM program and BMC Performance Manager Portal upgrades During a Portal upgrade. and data collection stops. Following the upgrade. you specify which RSM will monitor each element. The Portal saves the cached data. See “Clustered RSMs” on page 92 for information about using clustered RSMs in place of non-clustered RSMs. the Portal deploys the Performance Managers to an RSM. it requests the application class from the Portal and the Portal deploys the Oracle application class to the RSM computer. You can assign one RSM (or clustered RSM) to monitor an infrastructure element. The types of measurements that an RSM can collect depend on the Performance Managers installed on the Portal. Chapter 4 Remote Service Monitors 73 .Communication between the Portal and RSMs When communication with the Portal resumes. Following installation. Immediately after upgrading the RSM program. communication stops between the Portal and its RSMs. a user selects the Oracle® application class to monitor a database. Upon receipt of the program. but if the cached data includes threshold violations. When the assigned RSM computer discovers that it does not have the specified application class. RSMs and their assigned elements When you add elements to the account. the Portal does not send notifications. the RSMs determine that they have an earlier version of the RSM program and will request the current version of the RSM program from the Portal. upon request from the RSM. BMC Performance Managers on the RSM The RSM program collects data from its monitored elements and sends that data to the BMC Performance Manager Portal. RSMs resume their communication with the Portal. After Performance Managers are installed. the RSMs will begin upgrading to the new version and will drop their stored data.

If you will use PATROL integration Performance Managers to monitor PATROL Agents. When a firewall sits between an RSM and the monitored element. Dynamic You can specify any port number. Table 4 Application DNS FTP server HTTP HTTPS IMAP server Network Service Port NNTP server Ping POP server rstatd SMTP SNMP SSH server Telnet server Windows a b Application ports for firewalls Port number 53 21 80 a a a Protocol DNS name lookup network socket connection HTTP HTTPS network socket connection 443 143 user 119 specified a b network socket connection network socket connection ICMP network socket connection RPC network socket connection SNMP network socket connection network socket connection WinAPI (IPC$ share) ICMP 110 111 25 161 22 23 TCP 135. Ideally. This configuration specifies the necessary ports for communication between the RSM and its elements. configure the firewall according to the information shown in Table 4 on page 74. Communication between RSMs and PATROL Agents The RSM installation program requests a PATROL security level. 445 UDP 137. specify the security level that matches that of the PATROL Agents. ICMP does not use a port. configure a s 74 BMC Performance Manager Portal Monitoring and Management Guide . s If you will not use PATROL integration Performance Managers to monitor PATROL Agents. you can use the default security level (level 0). 138. or use the default shown. If you will be monitoring PATROL Agents that have different security levels.Communication between RSMs and elements Communication between RSMs and elements RSMs use standard protocols to communicate with their assigned elements and can monitor any IP-addressable computer or device. 139. you should locate an RSM inside the firewall on the same network segment as the elements that it will monitor. The level that you specify must match that of the PATROL Agents that the RSM will monitor.

log on with user credentials and on the Configure tab. See “Notifications task” on page 56 for more information about the different types of notifications. When you create RSM clusters that will integrate PATROL Agents. log on with administrator credentials and on the Provider tab. you can choose from the following options: — Change the security level of the RSM. The network is down. s To configure notifications for dedicated RSMs. select Notifications. Notifications about RSM system problems You can configure the Portal to send notifications when RSM system problems interfere with the infrastructure monitoring. select General System Problems as the rule type. To configure notifications for shared and global RSMs.Notifications about RSM system problems separate RSM for each security level and assign to each RSM only the agents with a security level that matches that RSM. all member RSMs in the cluster must have the same security level. s When configuring the notification rules for RSMs. Chapter 4 Remote Service Monitors 75 . — Install the RSM program on another computer and specify the necessary security level. The number of users exceeds the license threshold for the Portal. See “Changing the security level for an RSM” on page 101. select Notifications. The following conditions can cause general system problems: s s s The Portal does not receive data from the RSM. If the security level that you specify during RSM installation is not sufficient to monitor the PATROL Agents in your environment.

but then does not allow you to continue with the installation or an error message is displayed stating that DEP is blocking the installation program. s s s s s s s “RSM computer system requirements” on page 76 “Data execution prevention (DEP) configuration for the RSM” on page 76 “Configuring the access permissions for DCOM on the RSM computer and on the target computer” on page 78 “Configuring the WMI control” on page 81 “Using the installation wizard to install the RSM program” on page 84 “Using a silent installation to install the RSM program” on page 88 “Upgrading the RSM Program” on page 91 RSM computer system requirements You can install one instance of the RSM program on the BMC Portal computer (or the application server computer in a multiple-computer Portal).RSM program installation RSM program installation This section provides the procedures necessary to install or upgrade the RSM program on the computers designated as RSMs. as shown in Figure 6 on page 71. To resolve this issue. 76 BMC Performance Manager Portal Monitoring and Management Guide . Data execution prevention (DEP) configuration for the RSM When you install the RSM program on a Windows 2003 SP1 computer. The installation program starts. you must configure DEP in your computer properties to recognize the RSM installation program. Computers designated as RSMs reside in the network with the computers and devices that they monitor and inside the firewall.exe file. or on computers designated as RSMs. Ensure that the computers on which you want to install the RSM program meet the minimum system requirements detailed in the BMC Portal Release Notes. the installation program fails to successfully execute the RemoteServiceMonitor. The problem is caused by an enhanced data execution prevention (DEP) feature that Microsoft included in SP1.

When installing the RSM program from the Windows DVD. 13 Click OK to close the System Properties window. and save the program to a temporary directory. or installation files. 11 Click Apply. CD 1. 7 Select Turn on DEP for all programs except those I select. 3 Select Properties. download the RSM installation program. Chapter 4 Remote Service Monitors 77 . 5 Under the Performance heading. 15 Run the RSM installation program. 6 Select the Data Execution Prevention tab. select Settings. 10 Click Open. 14 Restart the RSM computer.Data execution prevention (DEP) configuration for the RSM To configure DEP to recognize the RSM installation program 1 On the Remote Service Monitors page in the Portal. 8 Click Add. 9 Navigate to the folder where you saved the RSM installation program. 12 Click OK. right-click My Computer.exe.exe from one of the following locations to a temporary directory: s s s RSM folder on Windows CD 1 BMCPortalKit\disk1\RSM on Windows DVD folder to which you downloaded files from the EPD website 2 From the Windows Desktop. copy RemoteServiceMonitor. and select RemoteServiceMonitor. 4 Select the Advanced tab.

ensure that the Remote Service Monitor (RSM) computer (the computer where the RSM is installed) has the necessary DCOM and WMI configuration properties. The following are the permissions that must be enabled on the RSM and on the target computer: s s s s s Execute Methods Provider Write Enable Account Remote Enable Read Security Configuring the access permissions for DCOM on the RSM computer and on the target computer To configure the access permissions for DCOM on the RSM computer and on the target computer. and do not restart it until you have configured the access permissions for the DCOM on both the RSM computer and the target computer. both the RSM computer and the target computer (the computer that you want to monitor) must have the appropriate permissions.Configure Distributed Component Object Model (DCOM) and Windows Management Instrumentation (WMI) Configure Distributed Component Object Model (DCOM) and Windows Management Instrumentation (WMI) When monitoring Windows computers using the WMI collector. The RSM computer that monitors the event logs and services must have the following default access permissions enabled in the DCOM properties: s s s s Administrators Interactive Network System To successfully read performance data using WMI-based data collection. use one of the following procedures: s s “To configure the access permissions for DCOM on Microsoft Windows 2000” “To configure the access permissions for DCOM on Microsoft Windows XP and Microsoft Windows 2003” on page 80 Before you begin Stop the RSM. 78 BMC Performance Manager Portal Monitoring and Management Guide .

11 Click OK. and that they have Allow Access permission. log on to the target computer and repeat steps 2 through 11. 12 Using an account that has administrative permissions. 13 Start the RSM. and click Add. perform the following steps: A Select Administrators. System. 2 Click Start => Run. D Select System. click Default Security. 10 In the Registry Value Permissions window. Interactive. click Add. and click Add. The Add Users and Groups window opens.exe and click OK. and click Add. E Click OK. 4 On the Distributed COM Configuration Properties window. log on to the RSM computer that is monitoring the event log. select the local computer. 9 In the Names field. and click Add. twice. verify that the Administrators. click Edit Default. B Select Interactive.Configure Distributed Component Object Model (DCOM) and Windows Management Instrumentation (WMI) To configure the access permissions for DCOM on Microsoft Windows 2000 1 Using an account that has administrative permissions. and Network users are added. 5 Under Default Access Permissions. 3 Enter dcomcnfg. 7 From the List Names From drop-down list. Chapter 4 Remote Service Monitors 79 . select Allow Access (if not already selected). C Select Network. 6 In the Registry Value Permissions window. 8 In the Type of Access field.

If a window opens with the message that more than one object matched the name Administrators. Network and click OK. or Network. 11 Click OK to return to the Component Services window. and repeat steps 2 through 12. 1 Using an account that has administrative permissions.exe and click OK. 7 Under Access Permissions. System. select Edit Default. 2 On the Task Bar. click Add. Interactive. 12 Choose File => Exit. System. select the name that contains only the one word (Administrators. enter Administrators. 14 Start the RSM. or Network). Interactive. click Start => Run. 5 Right-click on My Computers and select Properties. 4 In the Component Services window. and Network users have been added and that Allow Access permission is selected for each. verify that the Administrator.Configure Distributed Component Object Model (DCOM) and Windows Management Instrumentation (WMI) To configure the access permissions for DCOM on Microsoft Windows XP and Microsoft Windows 2003 Before you begin Stop the RSM and do not restart it until you have configured the access permissions for DCOM on both the RSM computer and the target computer. System. 8 In the Access Permissions window. 13 Using an account that has administrative permissions. log on to the RSM computer that is monitoring the event log. 10 In the Access Permissions window. 6 Select the COM Security or Default COM Security tab (depending upon your operating system). expand Component Services and Computers. Interactive. Interactive. 80 BMC Performance Manager Portal Monitoring and Management Guide . 9 In the text box under Enter the object names to select (examples). 3 Enter dcomcnfg. log on to the target computer. System.

To configure the WMI control 1 On the Task bar. 11 In Group or User Names. 3 Double-click Computer Management. 6 Click Security.Configure Distributed Component Object Model (DCOM) and Windows Management Instrumentation (WMI) Configuring the WMI control Use the following procedures to configure and to test the WMI collector: s s s s “To configure the WMI control” on page 81 “To set the inheritance on the name space” on page 82 “To test the WMI collector for CIMV2 name space.” on page 83 “To test the WMI collector for DEFAULT name space” on page 83 The permissions that are added are in addition to the permissions discussed under Configuring DCOM configuration properties. select the following permissions: s s s s s Execute Methods Provider Write Enable Account Remote Enable Read Security 13 Click OK. click Start => Settings => Control Panel. 9 Click Add. select your user name or group name. 12 In Allow Permissions for Administrators. 7 Double-click Root and select CIMV2. 8 Click Security. Computers or Groups. enter your user name or group name in Enter the objects to select and click OK. Chapter 4 Remote Service Monitors 81 . 2 Double-click Administrative Tools. 10 In Select Users. 5 Right-click WMI Control and select Properties. 4 Double-click Services and Applications.

and click OK. click Security.Configure Distributed Component Object Model (DCOM) and Windows Management Instrumentation (WMI) 14 Select DEFAULT. 3 In Permission entries. 6 Click OK. enter your user name or group name in the Enter the objects to select and click OK. 7 Quit the WMI Control snap-in. 5 In Apply onto. 16 Click Add. 4 To modify permissions for the user or group that you selected. Computers or Groups. click This name space and sub name space. To set the inheritance on the name space 1 On the WMI Collector Properties snap-in. 18 In Group or User Names. select the user or group whose permissions you want to modify. Determining whether the RSM can use the WMI collector to access the remote computer You can use wbemtest to determine whether the RSM computer can use WMI to access the remote computer. and then click Edit. 19 In Allow Permissions for Administrators. 15 Click Security. select your user name or group name. select the following permissions: s s s s s Execute Methods Provider Write Enable Account Remote Enable Read Security 20 Click OK. click Allow or Deny next to the permission that you want to allow or deny. 17 In Select Users. in the Permissions list. 82 BMC Performance Manager Portal Monitoring and Management Guide . 2 Click Advanced.

SecEvent. and type wbemtest. Event Log file names. See the error codes in the wbemtest tool for information related to the problem. 7 Click Execute Method. 1 Open a command prompt window. Chapter 4 Remote Service Monitors 83 . 6 Click Connect. 3 Change name space to \\RemoteComputerToBeMonitored\root\DEFAULT. select GetStringValue. 4 Type user: domain\user 5 Type the password for the user.Configure Distributed Component Object Model (DCOM) and Windows Management Instrumentation (WMI) To test the WMI collector for CIMV2 name space.Evt and SysEvent. If this query is successful. 3 Change name space to \\RemoteComputerToBeMonitored\root\CIMV2 4 Type user: domain\user 5 Type the password for the user. 8 Type the following query: select * from Win32_NTEventLogFile and click Apply. 8 In Object Path. To test the WMI collector for DEFAULT name space 1 Open a command prompt window.Evt. 2 Click Connect. AppEvent. 9 In Method. 6 Click Connect. are generated. 7 Click Query.Evt (with paths). it indicates that the 'WMI collector for CIMV2 name space' test has failed. and type wbemtest. and click OK. for example. and there is some problem with the WMI. and click Edit in Parameters. 9 Click Close and Exit. 2 Click Connect. If these log files are not generated. enter StdRegProv.

double click sSubKeyName. select Not NULL. It should be the name of the host to which we have connected from RSM.Using the installation wizard to install the RSM program 10 In Properties. 15 In Properties. on completion of the RSM installation. You can install the RSM program by downloading the installation program file from the Portal or by copying it from the installation media. 11 Double click sValueName. These credentials also determine the RSM type and how the users on the Portal can use the RSM to monitor their accounts. Using the installation wizard to install the RSM program This procedure describes how to install the RSM program on a Windows computer. StdRegProv is available only in root\default name space. 16 Click Close. the installation program requires that you enter credentials that the RSM uses to authenticate itself with the Portal. NOTE Ensure that the SystemDrive where you have installed the operating system. 12 Click Save Object. NOTE The StdRegProv class contains methods that manipulate system registry keys and values. enter "SYSTEM\\CurrentControlSet\\Services\\Tcpip\\Parameters". even if the directory where you want to install RSM is on another drive.xml]} 84 BMC Performance Manager Portal Monitoring and Management Guide . check the value for sValue. 14 Click Edit Out Parameter. such as the C:\ drive has 2 GB or more of free space.Detail=[C:\Windows\ProductRegistry. 17 Click Exit. and click Save Property… . select Not NULL. enter "Hostname". and click Save Property. When you install the RSM program. Otherwise. the RSM installation log file may display an exception as follows: THROWABLE EVENT {Description=[Failed to get product registry]. 13 Click Execute.

10 On the Select directory screen. 4 On the Remote Service Monitors page. 2 Perform one of the following actions: s s s When logged on with user credentials. perform step 2 on page 77 through step 13 on page 77 to configure DEP to recognize the RSM installation program. click the Configure tab. 9 Select I accept the terms of the License Agreement. click the Provider tab. 6 When installing the RSM program on a Windows 2003 SP1 computer. Chapter 4 Remote Service Monitors 85 . and click Next. 7 Run RemoteServiceMonitor. specify a target directory or accept the default location for the program files. click Add to open the Remote Service Monitors–Add page. and click Next.Using the installation wizard to install the RSM program To install the RSM program by downloading the program from the Portal 1 Log on to the Portal. click Next to display the software license agreement. 3 From the Tasks list. 8 On the Introduction screen. click the Portal tab. When logged on with provider administrator credentials. select Remote Service Monitors. When logged on with Portal administrator credentials. 5 Click the Download the Remote Service Monitor program Now link to download the RSM program installation file to a temporary directory on the computer designated as the RSM.exe to extract and start the installation program.

configure the security for unattended mode. see the PATROL Security User Guide. the next screen requests the security level for the RSM. For more information about security. select the security level that corresponds to those agents. If this RSM will integrate parameter data from PATROL Agents. s s Portal Password Confirm Password Fully-Qualified Portal Host Name Portal Secure Port RSM Name the password for the specified user name re-entry of the password for confirmation fully-qualified host name for the Portal web server port on which the Portal receives secure requests from the RSM. 86 BMC Performance Manager Portal Monitoring and Management Guide . To configure an RSM that can monitor all accounts associated with a provider. If you select level 3 or level 4. If you select No. 443 by default host name or alias for the RSM 12 Indicate whether you will use this RSM to integrate data from PATROL Agents. s s If you select Yes. If you plan to monitor PATROL Agents with different security levels. and click Next: Item User Name Description the user name that determines the type of RSM: s To configure an RSM for a single account. you must perform the steps described in “Changing the security level for an RSM” on page 101 to set the correct security for the RSM. type the user name for the account. configure a separate RSM for each security level and assign to each RSM only the agents with a security level that matches that RSM. The security level of the RSM must match that of the PATROL Agents that it monitors. skip to step 13 on page 87. type a user name for an administrator that has only Edit permission (provider administrator credentials). and click Next. and click Next. type a user name for an administrator that has Edit and See Other Providers and Their Accounts permissions (Portal administrator credentials).Using the installation wizard to install the RSM program 11 On the Enter Logon Information screen. enter the following authentication information. If at a later time you decide to use this RSM to integrate PATROL Agent data. To configure an RSM computer that can monitor all accounts on the Portal.

Using the installation wizard to install the RSM program 13 On the Pre-Installation Summary screen. 3 Run RemoteServiceMonitor. At the completion of the installation.exe from one of the following locations to a temporary directory: s s s RSM folder on Windows DVD BMCPortalKit\disk1\RSM on Windows DVD folder to which you downloaded files from the EPD website 2 When installing the RSM program on a Windows 2003 SP1 computer. s s Portal Password Confirm Password the password for the specified user name re-entry of the password for confirmation Chapter 4 Remote Service Monitors 87 . type a user name for an administrator that has only Edit permission (provider credentials). 5 Select I accept the terms of the License Agreement. and click Next: Table 5 Item User Name Authentication information on Logon Information screen (part 1 of 2) Description the user name that determines the type of RSM: s To configure an RSM for a single account. To install the RSM program by copying it from the installation files 1 Copy RemoteServiceMonitor. and click Install. and click Next. click Next to display the software license agreement. 7 On the Enter Logon Information screen. and click Next.exe to extract and start the installation program. review the entries and selections for the monitor installation. specify a target directory or accept the default location for the program files. To configure an RSM that can monitor all accounts on the Portal. To configure an RSM that can monitor all accounts associated with a provider. enter the following authentication information. type the user name for the account. type a user name for an administrator that has Edit and See Other Providers and Their Accounts permissions (Portal credentials). the Install Complete page is displayed. 4 On the Introduction screen. perform step 2 on page 77 through step 13 on page 77. 6 On the Select directory screen.

and click Next. configure the security for unattended mode.Using a silent installation to install the RSM program Table 5 Item Authentication information on Logon Information screen (part 2 of 2) Description fully-qualified host name for the Portal web server port on which the Portal receives secure requests from the RSM. If this RSM will integrate parameter data from PATROL Agents. skip to step 9 on page 88. s s If you select Yes. and click Install. If at a later time you decide to use this RSM to integrate PATROL Agent data. Using a silent installation to install the RSM program A silent installation enables you to launch the RSM installation program and specify installation configuration options from a command line. you must perform the steps described in “Changing the security level for an RSM” on page 101 to set the correct security for the RSM. Perform a silent installation if any of the following scenarios exists in your environment: s You want to run the installation in the background instead of interactively. configure a separate RSM for each security level and assign to each RSM only the agents with a security level that matches that RSM. For more information about security. At the completion of the installation. The security level of the RSM must match that of the PATROL Agents that it monitors. If you select No. s 88 BMC Performance Manager Portal Monitoring and Management Guide . review the entries and selections for the monitor installation. the Install Complete page is displayed. the next screen requests the security level for the RSM. see the PATROL Security User Guide. If you plan to monitor PATROL Agents with different security levels. If you select level 3 or level 4. You are installing to a remote computer that cannot display graphical user interfaces. 443 by default host name or alias for the RSM Fully-Qualified Portal Host Name Portal Secure Port RSM Name 8 Indicate whether you will use this RSM to integrate data from PATROL Agents. 9 On the Pre-Installation Summary screen. and click Next. select the security level that corresponds to those agents.

Using a silent installation to install the RSM program

s

You want to maintain consistent installation configuration values across multiple computers.

You specify the command-line options in a text file, and then specify that file when you launch the installation program from the command line.

Before you begin
s

Copy RemoteServiceMonitor.exe from one of the following locations to a temporary directory: — RSM folder on the Windows BMC Portal DVD — BMCPortalKit\disk1\RSM on Windows BMC Portal DVD — folder to which you downloaded files from the EPD website

s

Configure DEP to recognize the RSM installation program. In silent installations, passwords are displayed in plain text. If you want to encrypt the passwords, run the encryption utility as described in “To encrypt RSM passwords for use in a silent installation” on page 89. Ensure that the SystemDrive where you have installed the operating system, such as the C:\ drive has 2 GB or more of free space, even if the directory where you want to install RSM is on another drive. Otherwise, on completion of the RSM installation, the RSM installation log file may display an exception as follows: THROWABLE EVENT {Description=[Failed to get product registry],Detail=[C:\Windows\ProductRegistry.xml]}

s

s

To encrypt RSM passwords for use in a silent installation 1 Launch the RSM maintenance tool.
See “To launch the Remote Service Monitor Maintenance Tool” on page 98.

2 Select the Encrypt tab. 3 In Password, type the password for the RSM. 4 In Confirm password, retype the password. 5 Click Encrypt.
The encrypted value is displayed in Encrypted password.

Chapter 4

Remote Service Monitors

89

Using a silent installation to install the RSM program

You will use the value in Encrypted password for the PORTAL_PASSWORD and CONFIRM_PORTAL_PASSWORD values when you enter them in the options text file or the command line. See “To install the RSM from a command line.”

To install the RSM from a command line 1 In a text editor, enter the options listed in Table 6 in a file called RSMOptions.txt,
and close and save the file.

NOTE
Include only those options for which you want to specify a value. If you want to use default values, do not include the option in the options file.

Table 6

Options for an RSM silent installation
Description the installation directory where you want to install the RSM The default is C:\BMCSoftware\Remote Service Monitor.

Option (case-sensitive) -P installLocation=installationDirectory

-J PORTAL_HOST_NAME=hostName -J PORTAL_LOGIN=userName

the host name where the Portal is installed the user name required to access the Portal The default is admin.

-J PORTAL_PASSWORD=password

the password required to authenticate the user name The default is admin.

-J CONFIRM_PORTAL_PASSWORD=password reentry of the password to ensure that you typed it correctly in the previous field and to complete the authentication of the user name -J SECURITY_LEVEL=securityLevel if you are integrating with PATROL, the security level that matches the security for the PATROL Console Server The default is 0. Note: If several RT clouds operating at different security levels are communicating through the same Console Server, see the BMC Portal Installation Guide for guidance about choosing the security level.

90

BMC Performance Manager Portal Monitoring and Management Guide

Upgrading the RSM Program

Figure 7 shows an example of the RSMOptions.txt file. Figure 7
-P -J -J -J -J -J

Example of RSMOptions.txt file for silent installation

installLocation=C:\BMCSoftware\Remote Service Monitor PORTAL_HOST_NAME=host.bmc.com PORTAL_LOGIN=admin PORTAL_PASSWORD=admin CONFIRM_PORTAL_PASSWORD=admin SECURITY_LEVEL=0

2 Open a command prompt. 3 Change to the temporary directory in which you copied RemoteServiceMonitor.exe. 4 Enter the following command:
RemoteServiceMonitor.exe -i silent -DOPTIONS_FILE= drive:\path\RSMOptions.txt

The variable drive:\path is the location in which you saved the options file, if it is different from the location of RemoteServiceMonitor.exe. If the path contains spaces, enclose the path and options file name in double quotation marks (for example "C:\Documents and Settings\RSMOptions.txt"). To check the status of the installation, view the RSM installation log file.

If a problem occurs
Check the installation log rsm_install_log.txt for error messages. The installation log is in the %temp% or %tmp% directory.

Where to go from here
After installing the RSM, log on to the Portal with the predefined administrator credentials provided by the installation program to begin configuring the Portal and the selected modules. For details about accessing and configuring the Portal, see the BMC Portal Getting Started guide.

Upgrading the RSM Program
During a Portal upgrade, the RSMs cannot communicate with the Portal. Following completion of the Portal upgrade, the RSM resumes its communication with the Portal. When the RSM detects a mismatch between its program version and the version on the Portal, the RSM obtains the correct version from the Portal. The receipt of the new RSM program initiates the automatic upgrade of the program on the RSM.

Chapter 4

Remote Service Monitors

91

Clustered RSMs

If the RSMs fail to auto-upgrade, see “RSM upgrade fails on Windows 2003 SP1” on page 297.

Clustered RSMs
A clustered RSM provides maximum availability and failover in the event of computer downtime. A clustered RSM appears in the user interface on the Portal as a single logical RSM. In Figure 8, users can choose from three RSMs when configuring their elements. You can select a clustered RSM in place of a non-clustered RSM for all application classes. Figure 8 Clustered RSMs in the Portal
database server

Portal

browser

web server

application server In this scenario, users can choose from RSMs C, D, and G.

RSM A

RSM B

RSM E

RSM F

RSM C

RSM D

RSM G

elements

92

BMC Performance Manager Portal Monitoring and Management Guide

Cluster types

NOTE
Selecting the SNMP Trap Listener application class requires additional setup. For all other application classes, the RSM establishes communication with the monitored computer. In the case of this application class, the monitored computer establishes communication with the RSM. If you specify a clustered RSM, update the configuration of the device (router, switch, or network) to include the IP address or host name of all RSM computers in the cluster as valid monitoring hosts for the element. See the Help for additional information about this application class.

The Help describes how to modify the members in a cluster, view the status history of a cluster, and how to revert from a cluster to individual RSMs.

Cluster types
Table 7 shows how clustered RSMs mirror the usage of their individual RSM counterparts. Table 7 RSMs and clustered RSM counterparts
Clustered RSM dedicated RSM cluster shared RSM cluster global RSM cluster Usage any user in an account all users in all accounts under a single provider all users on the Portal

Individual RSM dedicated RSM shared RSM global RSM

The RSMs that compose the cluster must meet the following requirements:
s

dedicated RSM cluster — The individual RSMs are dedicated RSMs. — The dedicated RSMs are installed with user credentials from the same account. — The cluster is created from the Configure tab on the Remote Service Monitor page.

s

shared RSM cluster — The individual RSMs are shared RSMs. — The shared RSMs are installed with administrator credentials from the same provider. — The cluster is created from the Provider tab on the Remote Service Monitors page.

Chapter 4

Remote Service Monitors

93

Clustered RSM operating status

s

global RSM cluster — The individual RSMs are global RSMs. — The global RSMs are installed with Portal administrator credentials. — The cluster is created from the Portal tab on the Remote Service Monitors page.

When clustering RSMs, you can create clusters of dedicated, shared, or global RSMs, but you cannot mix RSM types in a cluster. For example, you cannot create a cluster that contains one shared and one dedicated RSM.

Clustered RSM operating status
On pages where you select RSMs, the following icons represent the current operating status of the available clustered RSMs: Table 8
Icon

Icons for clustered RSM operating status
Current operating status all members in the cluster are online and have an OK operating status at least one member, but not all, in the cluster is not online all members in the cluster are not online

Clustered RSM security considerations
When you create a cluster for integrating data from PATROL Agents, ensure that each RSM in the cluster has a security level that matches those of the PATROL Agents.

RSM load-balancing
After you create the RSM cluster, the Portal attempts to evenly distribute the elements monitored by the cluster members. The Portal also distributes elements as you assign them to the cluster. However, irrespective of the number of RSMs in a cluster, the parameter capacity of the cluster is the same as that of a single RSM.

94

BMC Performance Manager Portal Monitoring and Management Guide

RSM failover

RSM failover
When a member of the RSM cluster goes offline, the Portal distributes the elements assigned to that RSM among the remaining online members of the cluster. When the RSM becomes available again, the Portal load-balances the assigned elements among the cluster members.

Clustering RSMs
You cluster RSMs to ensure maximum availability and provide a failover RSM in the event of computer downtime. When assigning elements to a cluster, ensure that you do not assign more elements to the cluster than any one individual RSM can handle should the other RSMs in the cluster fail.

Before you begin
Ensure that the RSM program is installed on each computer designated as an RSM for the cluster, and that
s s

each RSM is of the same type (dedicated, shared, or global) for clustered RSMs that will integrate PATROL Agent data, each RSM has the necessary security level

To configure RSMs for a cluster 1 Log on to the Portal:
s

To configure a cluster of dedicated RSMs, log on with user credentials for the account. To configure a cluster of shared RSMs, log on with provider administrator credentials. To configure a cluster of global RSMs, log on with Portal administrator credentials.

s

s

2 Perform one of the following actions:
s s s

When logged on with user credentials, click the Configure tab. When logged on with provider administrator credentials, click the Provider tab. When logged on with Portal administrator credentials, click the Portal tab.

Chapter 4

Remote Service Monitors

95

Clustered RSM upgrades 3 Under Tasks. See the Help for more information about managing RSM clusters. This name represents the cluster in RSM lists. RSM configuration and maintenance This section describes the RSM configuration and maintenance tools and how you can use them to perform the following tasks: s s s s s s s Changing the security level for an RSM Configuring an RSM to use a proxy server Changing the credentials for an RSM Configuring the RSM to use HTTP protocol to communicate with the Portal Changing the maximum heap memory allocated for the Java VM on the RSM Viewing the log files for the RSM Collecting log files 96 BMC Performance Manager Portal Monitoring and Management Guide . click Create RSM Cluster to open the Remote Service Monitors–Add page. click Remote Service Monitors. type a character string that identifies the cluster. 8 Click Save to finish creating the clustered RSM and return to the Remote Service Monitors page. This description appears with the cluster name in RSM lists. Clustered RSM upgrades When upgrading the Portal from version 2. This list shows RSMs that are not in a cluster. 4 On the Remote Service Monitors page. clustered RSMs retain their cluster properties. The new clustered RSM appears in the list as a logical RSM and the RSMs that compose the cluster are removed from the list. type the name for the new cluster.1 or later. select the RSM to include in the cluster. 7 In the list of RSMs. 6 In Description. 5 In Cluster Name.

stop. Remote Service Monitor Manager utility The Remote Service Monitor Manager is a program that enables you to configure. and start the RSM. NOTE You must directly access the RSM Manager on the RSM computer or you must use a remote access program (such as Terminal Services) to access it.Configuration and maintenance tools Configuration and maintenance tools The BMC Performance Manager Portal provides multiple tools that you can use to configure and maintain the RSM. Chapter 4 Remote Service Monitors 97 . The RSM Manager provides the following tabs: s Configure provides the Identification and Properties pages. including Portal (application server) properties and proxy server setup. and select Launch RSM You can also access the RSM Manager by double-clicking . which enable you to change the credentials and properties for the RSM. right-click Manager. The Remote Service Monitor Manager utility resides on the RSM and is accessible from the system tray of the RSM computer. s Status provides the following monitoring information about the RSM: — version number of the RSM program installed on the RSM computer — number of application classes across all elements connected to the RSM — most recent time and date that the RSM attempted to send data to the Portal — number of report messages in the queue waiting to be sent to the Portal — size of the latest report messages sent to the Portal — number of milliseconds required by the RSM to complete the request that transmitted the data to the Portal To access the RSM Manager utility In the system tray on the RSM computer.

you can find the utility in the following location: %RSM_HOME%\RSMversionNumber 2 Enter the following command: RSMMaintenanceTool. Change RSM installation configuration information. If you see this message. RSM Log Monitoring Tool The BMC Remote Service Monitor (RSM) log monitoring feature enables you to locate and diagnose issues in RSM and find workarounds if the issue is already known.log file.cmd NOTE If you had a failed or canceled installation. Collect log files into a zip file that you can send to a BMC Software Customer Support representative for troubleshooting. Pre-configure log monitoring of RSM tied to knowledge articles using the RSM Log Monitoring tool s s s To launch the Remote Service Monitor Maintenance Tool 1 On the RSM computer. and enter the following command: cd %RSM_HOME%\RSMversionNumber If you used the default location for the RSM program. such as memory size and credentials for connecting to the Portal.Configuration and maintenance tools Remote Service Monitor Maintenance Tool The RSM installation program installs a utility that you can use to perform the following tasks: s View installation log files. you might see a message indicating that you need to set RSM_HOME. execute the following command and repeat step 2: set RSM_HOME=installationDirectory You can access the Remote Service Monitor Maintenance Tool from the RSM computer or the installation files. 98 BMC Performance Manager Portal Monitoring and Management Guide . open a command prompt. It shows the warning and severe errors encountered in the rsm.

as the search string: 1.log file and paste the string in the Enter string to search solution text box. You must configure the Log Management solution to get the proactive notification for specific error patterns such as SEVERE. you must manually locate errors in the rsm. NOTE s Some errors do not display as SEVERE or WARNING. specify the string in the Enter string to search solution text box. NOTE Pre-configured Log Monitoring does not send proactive notifications.log file. You can configure the Log Management solution by using specific grep expressions to make the notification precise. WARNING. or OutOfMemory. In the Logs tab. To search for errors in the rsm. s Chapter 4 Remote Service Monitors 99 . Copy and enter the contents from the notification in the text box. you can paste the string in the Enter string to search solution text box. you can diagnose the issue in the rsm. and therefore do not display on the BMC RSM log viewer window. In such cases.Configuration and maintenance tools When you get a notification for an error that has occurred with the RSM service. To use a specific exception that is mentioned in the error notification.cmd 2 On the Logs tab. You can also search for the solution for an exception by using a specific search string that is taken from the error notification. you can perform one of the following search tasks: A. If you do not receive a notification and come across an error in the rsm.log file 1 Launch the BMC Remote Service Monitor Maintenance Tool from the following directory on the Windows operating system: %RSM_HOME%\RSMversionNumber\RSMMaintenanceTool.log file by using this feature. from the RSM Log Monitor pane.

B. 2009 12:05:50 AM executeParamletArgs com. and so on.simple.STDERR> Apr 17.java:574) 2.OutOfMemoryError: unable to create new native thread at java. WARNING.lang.log file that contains the error: 1.bmc.start0(Native Method) at java. In the Logs tab.Configuration and maintenance tools EXAMPLE If you get the following warning exception as an e-mail notification. click RSM Log Monitor.SimpleParamletCo ntainer WARNING: Unexpected error while executing job. The upper panel displays the error messages color-coded based on the type of error such as SEVERE.start(Thread. from the RSM Log Monitor pane.Thread. 4 The lower panel of the log viewer window displays the following information: s s s s s Time .the source class of the file from which the exception is recorded Details .the date and time of the recorded exception Severity .paramlet.patrol. To navigate to the rsm.log. java. if available Exception .Thread.container. copy and paste all the contents of the notification in the Enter string to search solution text box: <R [RSMScheduler_Worker-67].lang.the exception stack trace 100 BMC Performance Manager Portal Monitoring and Management Guide . 2. Click Search Solution for the tool to find the corresponding solution.lang.the details about the exception and an existing solution for the exception. if it is a known issue.the severity of the exception Source . 3 The file opens in the rsmlogFileName log viewer window with two panels. Click Browse to RSM Log and navigate to the log file such as rsm.04/17/09 00:05:50 UTC.patsdk.

If you specify a security level that differs from that which is already in place. Changing the security level for an RSM that coexists with PATROL products When you install the RSM on a computer where PATROL products reside. For information about this utility. see the PATROL Security User Guide or documentation for the specific PATROL product. During installation. entering the correct security when prompted. changing the security level for the PATROL product also changes it for the RSM.Changing the security level for an RSM Changing the security level for an RSM The RSM supports security levels 0 through 4. use one of the procedures described under “RSM program uninstallation” on page 109. the installation program overrides your selection and uses the existing setting. the installation program assigns security level 0. if you do not specify a security level. Changing the security level for an RSM-only computer To change the security level of an RSM computer. 3 Reinstall the RSM program. When an RSM coexists with any PATROL product. 2 Uninstall the RSM program. the installation program assigns their existing security setting to the RSM. run the esstool utility. All products on the computer share the same security level. To determine the security level of an RSM. 1 If the RSM is currently monitoring elements. To uninstall the RSM program. move those elements to a different RSM. s s Changing the security level for an RSM that coexists with PATROL products Changing the security level for an RSM-only computer You can find a brief description of the security levels in Table 1 on page 20. Chapter 4 Remote Service Monitors 101 . If you need to change the security level for all the BMC Software products installed on the same computer. you must reinstall the RSM program and specify the correct security level. The types of BMC Software products installed on the Portal computer and the order in which you installed them determines the method that you use to change the security. see “Policy and role information” in the PATROL Security Guide.

If your network uses proxy autoconfiguration files to direct requests to the proxy server. provide the following properties: A In Server Name. See “To access the RSM Manager utility” on page 97. you can adjust the default settings for the RSM to Portal communication. To configure an RSM to use a proxy server 1 Access the Remote Service Monitor Manager for the RSM to configure. 4 If necessary. If you need to direct RSM communication through a proxy server. select the Portal host name. 3 In the navigation pane under Properties. 2 Select the Configure tab. myproxy. specify the registered host name of the proxy server and not the automatic configuration script address.Configuring an RSM to use a proxy server To install the RSM program. type the local computer name in User Domain. skip to 4C. otherwise. type them in User Name and Password. Configuring an RSM to use a proxy server The RSM monitors the elements in your account and sends the monitoring information directly to the Portal. under Proxy Server. C If the proxy server uses a local account. 102 BMC Performance Manager Portal Monitoring and Management Guide . 4 On the Portal properties page. E In Port Number. use one of the procedures described under “RSM program installation” on page 76. type the port number that receives requests. type the host name or IP address for the proxy server (for example. otherwise.acme. skip to 4D. reassign elements to the RSM.com). type the domain name in User Domain. B If the proxy server uses domain authentication. D If the proxy server requires authentication credentials for access.

select the HTTP option and click Next. This procedure changes the protocol and the port number on which the communication occurs.cmd 2 On the Configuration tab. and select Start RSM. restart the RSM: A Right-click B Right-click and select Stop RSM. under Portal Web Server Port.Configuring the RSM to use HTTP protocol to communicate with the Portal 5 Click Save. 3 While entering the information for the BMC RSM. 5 Click Finish. To configure the RSM to use HTTP protocol to communicate with the Portal 1 Launch the BMC Remote Service Monitor Maintenance Tool from the following directory on the Windows operating system: %RSM_HOME%\RSMversionNumber\RSMMaintenanceTool. NOTE The default HTTP port number is 80. The RSM starts using the HTTP protocol to communicate with BMC Portal. Configuring the RSM to use HTTP protocol to communicate with the Portal If your RSM is on a secure network and you can allow the RSM to communicate with the Portal web server using an unsecured protocol. 6 From the system tray on the RSM computer. Chapter 4 Remote Service Monitors 103 . click Next. 4 Review the changes you made in the review pane and click Next. enter the port number in the Portal Web Server Port text box. To set the port number to another value. you can improve the overall scalability of the RSM if you configure it to use HTTP instead of HTTPS.

3 In the navigation pane under Properties. To use the RSM Manager to change the credentials for an RSM 1 Access the RSM Manager for the RSM. as necessary. When you change the RSM credentials. and select Start RSM. do not provide administrator credentials when you change the credentials. the RSM credentials must also be changed. select the Portal host name.Changing the credentials for an RSM Changing the credentials for an RSM The credentials for the RSM must match its corresponding user or administrator credentials on the Portal. If the credentials change for the user or administrator that installed the RSM program. 6 From the system tray on the RSM computer. Changing the type of an RSM can disable monitoring of its assigned elements. 104 BMC Performance Manager Portal Monitoring and Management Guide . See “To access the RSM Manager utility” on page 97. 2 Select the Configure tab. under Portal Server. For example. if you installed the RSM with user credentials. ensure that you do not provide credentials that change the RSM type. 5 Click Save. Before you begin Ensure that the RSM is connected to the Portal. type the new Portal credentials in User Name and Password. restart the RSM: A Right-click B Right-click and select Stop RSM. 4 On the Portal properties page. You can use the RSM Manager or Remote Service Monitor Maintenance Tool to change RSM credentials.

See “To launch the Remote Service Monitor Maintenance Tool” on page 98. 3 Using one of the following methods. In the system tray of the RSM computer. Ensure that you enter correct information. and click Next. enter a user name for an administrator that has only Edit permission (provider credentials). To configure an RSM that can monitor all accounts on the Portal. C In Confirm Password. enter the password for the specified user name. 2 Change any of the RSM credentials. and Stop RSM and then Chapter 4 Remote Service Monitors 105 . enter the user name for the account. enter the user name that determines the type of RSM: s To configure an RSM for a single account.Changing the credentials for an RSM To use the Remote Service Monitor Maintenance Tool to change the credentials on the RSM 1 Launch the RSM installation tool. s s B In Portal Password. NOTE The RSM Maintenance Tool does not validate the fields. retype the password. A In User Name. enter a user name for an administrator that has Edit and See Other Providers and Their Accounts permissions (Portal credentials). To configure an RSM that can monitor all accounts associated with a provider. restart the RSM: s s Restart the BMC Remote Service Monitor service. right-click select Start RSM.

and Stop RSM and then Viewing the log files for the RSM This procedure describes how to view the log files that the installation program creates when it installs the RSM program. The log files. 4 Using one of the following methods. specify the maximum amount of heap memory that you want to allocate for the RSM. See “To launch the Remote Service Monitor Maintenance Tool” on page 98. In the system tray of the RSM computer. and click Next. are displayed in a table showing the following information: s s s s date and time that each message was recorded in the log file the message severity the message text description of any failures that occurred Messages highlighted in red indicate errors. created during the BMC Portal installation.Changing the maximum heap memory allocated for the Java VM on the RSM Changing the maximum heap memory allocated for the Java VM on the RSM If you experience performance problems with the RSM. you might be advised by BMC Customer Support to change the maximum heap memory allocated for the RSM. 106 BMC Performance Manager Portal Monitoring and Management Guide . right-click select Start RSM. restart the RSM: s s Restart the BMC Remote Service Monitor service. To change the maximum heap memory allocated for the Java VM on the RSM 1 Launch the Remote Service Monitor Maintenance Tool. 2 On the Configuration tab. 3 Click Next twice. and then click Finish. Messages highlighted in yellow indicate warnings.

click Browse to Log to locate and display the log file. if a ZIP utility. See “To launch the Remote Service Monitor Maintenance Tool” on page 98. Collecting log files This procedure creates a zip file that contains RSM log files. Chapter 4 Remote Service Monitors 107 . with the most recent installation displayed first. Tab titles show the date and time of the installation. If you need to contact BMC Customer Support. NOTE On Windows platforms. In %temp%. is not installed on the RSM computer. 2 On the Logs tab. such as Winzip or an equivalent. See “To launch the Remote Service Monitor Maintenance Tool” on page 98. click Zip Logs.Collecting log files To view installation log files 1 Launch the Remote Service Monitor Maintenance Tool. you cannot see the contents of the ZIP file. Alternatively. the program creates RSMLogs. click the button that corresponds to the log file that you want to view: s s s s s Install Log Uninstall Log Autoupgrade Log Configuration Log Application Log The log viewer displays each installation in a separate tab. you can use this procedure to gather RSM log files. 2 On the Logs tab. in the Logs tab. which contains the necessary log files. The ZIP file appears empty when opened. To collect log files for the RSM 1 Launch the RSM Maintenance tool.zip. even though the log files are included in the ZIP file.

the program creates RSMLogs. In %temp%. In such a case. Stopping notifications for Unknown state events You can configure an RSM to stop sending notifications for Unknown state events when it does not collect data for a parameter and the parameter goes into an Unknown state. NOTE If BMC Performance Manager Portal is integrated with BMC Impact Portal. 2 On the Logs tab. the total physical and virtual memory. This file includes information about properties of the operating system such as the patch level. It also displays data gaps in the Parameter History Chart view and No Data in the Parameter History Table view.zip.zip contains the OperatingSystemData. 108 BMC Performance Manager Portal Monitoring and Management Guide . 3 The RSMLogs. To gather basic information of RSM cases 1 Launch the RSM Maintenance tool. version. unknown events might be generated for the business components. If RSM fails to collect the data.Automating basic information gathering for RSM issues Automating basic information gathering for RSM issues The BMC RSM Maintenance Tool allows you to automate basic information gathering for RSM issues. This collects information about the operating system metrics. which contains the necessary log files. the available physical and virtual memory.xml file. the environment variables of the operating system. you cannot stop notifications from being sent. See “To launch the Remote Service Monitor Maintenance Tool” on page 98. BMC Portal shows the earlier status of that parameter. You can use this information to report RSM issues to BMC Customer Support. click Zip Logs. and so on.

See “Using command-line options to uninstall the RSM program” on page 112. Using the installation wizard to uninstall the RSM program 1 On the RSM computer. right-click Restart the RSM computer. 2 In the Control Panel. open the Control Panel.RSM program uninstallation To configure RSM to stop sending notifications for Unknown state events 1 Navigate to %RSM_HOME%\RSMversionNumber\server\rsm\conf\properties\rsm. you can perform a silent uninstallation of the RSM program from a command line. see “Using the installation wizard to uninstall the RSM program” on page 109 If the RSM program is installed on a computer with other BMC Software products that use security. 2 Open the rsmcfg. 4 Restart the RSM service.patsdk. RSM program uninstallation The method that you should use to uninstall the RSM program depends on whether the RSM program is sharing security with other BMC Software products on the RSM computer: s If the RSM program is not installed on a computer with other BMC Software products that use security. and select Exit. 3 Select BMC Remote Service Monitor versionNumber.bmc.CollectionJob. and click Change/Remove. 3 Uncomment com. perform one of the following actions before uninstalling. If the RSM program was upgraded from an earlier version. s Alternatively. see “Manually uninstalling the RSM program” on page 110. double-click Add/Remove Programs to open the Add/Remove Programs window.patrol. regardless of the method that you choose to uninstall the RSM program: s s In the system tray on the RSM computer. Chapter 4 Remote Service Monitors 109 .services.ignoreUnknownState=true.properties file.

click the Portal tab. When logged on with Portal administrator credentials.Manually uninstalling the RSM program 4 On the first page of the uninstallation wizard. s s B From the Tasks list. When logged on with provider administrator credentials. and stop it. 2 Save the following text in a file called DeleteRSM. click the Provider tab. B Select the BMC Remote Service Monitor service. 7 Using the credentials for the deleted RSM. and then open Services. and click Next. click the Configure tab. open Administrative Tools. and click Delete. review the messages for any errors. and select Merge to clean up the registry: REGEDIT4 [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\aecf247c9581b1d626129c65a6 c804dd] [-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\BMC Remote Service Monitor] [-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\BMC Remote Service Monitor] [-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services\BMC Remote Service Monitor] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BMC Remote Service Monitor] [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Environment] "RSM_HOME"=[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Session Manager\Environment] "RSM_HOME"=[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\Session Manager\Environment] "RSM_HOME"=[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment] "RSM_HOME"=- 110 BMC Performance Manager Portal Monitoring and Management Guide . Manually uninstalling the RSM program 1 Stop the BMC Remote Service Monitor service: A On the RSM computer. click Next. 6 On the Summary page. select Remote Service Monitors.reg. right-click on that file. log on to the Portal and delete the RSM: A Perform one of the following actions: s When logged on with user credentials. and click Next. open the Control Panel. select the RSM that corresponds to the uninstalled RSM program. 5 Select BMC Remote Service Monitor. C In the list of RSMs.

\CI.Manually uninstalling the RSM program 3 If security is no longer being used by any other programs on this computer. B Save the following text in a file called DeleteRSMSecurity. perform the following actions. right-click that file.xml If the installation directory is now empty. delete the RSM from the Portal.properties.\..reg. 5 Using the process described in step 7 on page 110. Chapter 4 Remote Service Monitors 111 . s s s s B Delete the following file: %windir%\vpd.xsd installationDirectory\RSMInstalledConfiguration.0] [-HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\PATROL Agent] [-HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\PATROL Security] [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\BMC Software] [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Environment] "BMC_ROOT"=[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Session Manager\Environment] "BMC_ROOT"=[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\Session Manager\Environment] "BMC_ROOT"=[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment] "BMC_ROOT"=- 4 Perform the following actions to delete unnecessary files and directories: A Delete the following directories: s installationDirectory\RSMversionNumber installationDirectory\BMCRemoteServiceMonitorInstallJVM installationDirectory\UninstallBMCRemoteServiceMonitor installationDirectory\InstallationTaskConfiguration. skip to step 4: A Delete the following directory: %BMC_ROOT%. otherwise. you can delete it too. and select Merge to clean up the registry: REGEDIT4 [-HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\Patrol\SecurityPolicy_v3.

"C:\Documents and Settings\RSMUninstallOptions. create a file called RSMUninstallOptions. s s This option specifies the RSM as the product to uninstall.txt file should look as follows: -U productRSM 2 Open a command prompt. 3 Change to the following directory: %RSM_HOME%\UninstallBMCRemoteServiceMonitor\ 4 Enter the following command: uninstall. The RSMUninstallOptions. 112 BMC Performance Manager Portal Monitoring and Management Guide . When the uninstallation is complete. If the path contains spaces. and then specify that file when you launch the uninstallation program from the command line. enclose the path and options file name in double quotation marks (for example.txt"). if it is different from the location of the uninstall. Enter the options directly on the command line when you launch the uninstallation program.txt The variable drive:\path is the location in which you saved the options file. view the RSM uninstallation log file. insert the -U productRSM option.Using command-line options to uninstall the RSM program Using command-line options to uninstall the RSM program You can specify the command-line options for uninstallation in the following ways: s Enter the options in a text file. the command prompt is displayed.txt.exe. To check the status of the uninstallation. s To uninstall the RSM from a command line 1 Using a text editor.exe -i silent -DOPTIONS_FILE=drive:\path\RSMUninstallOptions. Options are case-sensitive. and save the file.

. Deactivating parameters . . Removing Performance Managers from the Portal . . . . . . . . . . . . . . . . . . . . . . Core Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solution Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . You can also obtain new Performance Managers that contain the application classes that you need by purchasing or creating them. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deactivating a parameter in the Performance Manager Editor solution . Methods of remote monitoring . . . . . . Custom Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Derived parameters. . . . . . . . . . . . . . . . . . . . . . Deactivating a parameter . . . Editing Performance Managers . . . . . . . . . . . . . . . . . . . . . . . Parameter thresholds and event severity. . . . . . . . . Parameters and thresholds . . Points to remember while deactivating parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solution support for deactivating parameters . . . . . . . . . . . . . . . . . PATROL Agent integration . . . . . . . . . . . . . . . . . . . . . . . . to monitor the infrastructure in your account. . . . . . . . . . . . . . . . . . . Agentless monitoring . . . . . . . . . Chapter 5 Performance Managers and application classes 114 114 115 115 116 117 118 118 119 120 121 121 121 125 127 129 130 130 131 131 139 139 139 113 . . . . . . . . . . . . . . . . . . . . . . . . . . . Thresholds and parameter status changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and the application classes that they contain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 5 Performance Managers and application classes 5 The BMC Performance Manager Portal provides Performance Managers that contain application classes that you can use to monitor your infrastructure. . . . . . . . . . . . . . . . . Editing published custom Performance Managers . . . . . . . . In addition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . this chapter provides an overview of creating custom Performance Managers. . . . . . . . . . Editing unpublished custom Performance Managers . . . . . . . . . . . Installing new Performance Managers on the Portal . . . . . . Upgrading Performance Managers on the Portal . . . . . . . . . . Types of Performance Managers . . . . . This chapter describes how the BMC Performance Manager Portal uses Performance Managers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

You can assign one or more application classes to any infrastructure element. You can configure parameter thresholds when adding infrastructure elements to the account or at a later time. you can select an application class to monitor the operating system and another to monitor Microsoft Exchange. you can create and modify custom Performance Managers by using the following tools: s BMC Performance Manager Portal SDK—Included with the Portal. To realize the greatest benefit from the reports and notifications. 114 BMC Performance Manager Portal Monitoring and Management Guide . configure thresholds that reflect realistic metrics for your environment. The SDK enables Performance Manager developers to create Performance Managers that use all protocols and collectors supported by the Portal. Telnet. you can log on with user credentials and begin adding infrastructure elements and assigning application classes to gather application and system metrics about the computers and devices in your account. you can still view statistical information gathered for the parameter. When adding the computer as an infrastructure element. the wizard-like series of pages enables you to create and modify custom Performance Managers that use the PerfMon. If you do not set thresholds for a parameter. s Parameters and thresholds Each application class contains a set of related parameters. By setting performance thresholds for the parameters and configuring notification rules. see the BMC Performance Manager Development and Certification Guide on the Documentation CD. Performance Manager Editor—Available when you log on with Portal administrator credentials (Edit and See Other Providers and Their Accounts permissions).Overview Overview The application classes contained in Performance Managers monitor groups of similar attributes on infrastructure elements. but you do not receive notification. Immediately following the installation and initial configuration of the Portal. In addition to Performance Managers from BMC Software. For detailed procedures that describe how to use the SDK. SNMP. you can have the Portal notify you when deteriorating system performance or application problems become severe. EXAMPLE A Windows computer is running Microsoft Exchange. the SDK provides developer tools necessary to create robust custom Performance Managers. and SSH protocols and collectors to gather parameter metrics.

Chapter 5 Performance Managers and application classes 115 . By default. Set an alarm threshold to notify you when a situation first becomes severe. as shown in Figure 9. Set a warning threshold to notify you before a situation becomes severe. you eliminate status changes and notifications for intermittent. you also control when the RSM changes the parameter status by configuring the Alert After options on the Threshold pages. an alarm event is triggered for the parameter. Alarms indicate that a problem has escalated to a severe level.Parameter thresholds and event severity Parameter thresholds and event severity You can configure thresholds for each parameter by specifying parameter threshold values that trigger the following event severities: s Warnings represent the first indication of a problem. the RSM changes the status of a parameter as soon as the RSM detects that a warning or alarm threshold has been breached. momentary performance spikes. the RSM does not notify the Portal of a status change unless the RSM collects five successive measurements that breach the specified threshold value for the specified type. s Thresholds and parameter status changes In addition to setting warning and alarm thresholds. For example. When the RSM measures a value on the monitored element that can trigger an alarm and you have selected the Alarm On option. if the collection interval is 1 minute and you specify 5 for # Times. When the RSM measures a value on the monitored element that can trigger a warning and you have selected the Warning On option. By requiring successive measurements outside the normal range. a warning event is triggered for the parameter. Figure 9 Alert After threshold options s # Times sets the successive number of times that the RSM must measure parameter values outside of the normal range before changing the status.

You can even deactivate parameters whose thresholds cannot be edited such as the text parameters. warning value. 116 BMC Performance Manager Portal Monitoring and Management Guide . the status immediately changes to alarm. Because the RSM measures a more severe status during the next collection interval. s After satisfying the parameter status change. The RSM changes the parameter status to warning after the third collection interval. and the RSM measures warning value. the RSM changes the status after the next collection interval if the RSM measures a value that breaches a more severe threshold. and warning value in three successive collection intervals. suppose that you specify 3 and Alarm or Warning and the RSM measures warning value. However. suppose that you specify 3 and Alarm or Warning. For example. you can choose to deactivate parameters. For example. For steps to deactivate a parameter. BMC Portal enables you to activate or deactivate parameters at the element and element profile level. RSM stops sending data to BMC Portal for that parameter. Deactivating parameters The deactivating parameters feature of the product provides more flexibility by making monitoring more granular. and alarm value. alarm value. The RSM changes the parameter status to alarm when the alarm threshold is breached the specified number of times. However. This feature does not deactivate data collection. see “Deactivating a parameter” on page 118. s — If you select Alarm or Warning s The RSM changes the parameter status to the last threshold type breached after any combination of successive alarms or warnings. The RSM changes the parameter status to warning after the third collection interval. warning value. — If you select Alarm s The RSM changes the parameter status to warning when the warning threshold is breached. all the parameters are active.Deactivating parameters s Type determines the threshold type (alarm or warning) that the parameter must breach. By default. when you deactivate a parameter.

see “Derived parameters. irrespective of the notification rule configured and the earlier status of the element. In cases where Elements are bound to an Element Profile. for the period when the parameter was deactivated. When you deactivate a parameter in Alarm or Warning state. s When a deactivated parameter is activated once again. the Elements inherit the active or inactive state property that you set in the Element Profile. sub-application class. When you activate a deactivated parameter. The history of the deactivated parameter is not deleted.” s s s Chapter 5 Performance Managers and application classes 117 .Points to remember while deactivating parameters Upon deactivation. the parameter is visible on all the tabs with the Unknown icon until data is collected for the activated parameters. the following happens to a deactivated parameter: s The parameter is visible in the Configure and Events tabs and displays the offline icon. s s s NOTE In case of Alarm Point. a notification is sent describing that a parameter in violated state has undergone a state change and is now offline. or a discovered instance. You cannot override the active or inactive state properties of parameters. For more information. deactivation (offline status) is a CLEAR event and Alarm Point does not send notifications for CLEAR events. Points to remember while deactivating parameters You must ensure the following while deactivating parameters: s You must not deactivate all the parameters in an application class. depending on the type of notification rule configured. you see data gaps in the Parameter History Chart view and No Data in the Parameter History Table view. The parameter is hidden in the Status and Reports tabs. The value of derived parameters that depend on other parameters is affected by deactivation of those parameters. You cannot deactivate the Application Collection Status (ACS) parameter. the Active column is disabled for editing. As per Alarm Point. At least one parameter must be active. the product does not send notifications if the parameter goes offline.

elements. EXAMPLE In the Solaris application class. Deactivating a parameter By default. and modifying parameter properties. you can deactivate a parameter while adding or modifying application classes. For element profiles: 1. Value of CPU Usage parameter = Value of CPU User parameter + Value of CPU System parameter If either the CPU User or the CPU System parameter is deactivated. or the Application Collection Status (ACS) parameter might go in to a violated state. or data might not be collected for P3. The values of P1 and P2 come from the collection triggered by RSM for the solution. These parameters derive their values from the values collected for other parameters. the CPU Usage parameter displays No Data row in the Parameter History Table view.Derived parameters Derived parameters Derived parameters do not carry the actual data collected by the RSM. However. where P3 is the derived parameter. If P1 and P3 are active for collection and you deactivate P2. Select an element profile and click Edit to modify the element profile properties. The value for P3 is the arithmetic sum of P1 and P2 (P3 = P1 + P2). the value derived for P3 might not be correct. 118 BMC Performance Manager Portal Monitoring and Management Guide . A. Expand the Tasks object tree and select Element Profiles. consider an application class has three parameters such as P1. 2. P2 and P3. 3. 2 In the navigation pane. element profiles. all the parameters are active. Click an application class and modify the respective parameters. To illustrate. To deactivate a parameter 1 Click the Configure tab.

3 In the Add Performance Managers page. If you want to activate the parameter.Deactivating a parameter in the Performance Manager Editor solution B. Select the application class or the parameter. 5 Select the Active check box to activate the parameter. 2. 2 In the navigation pane. Click Edit to modify the properties of the respective parameters. NOTE If you update the parameter type. For application classes and parameters: 1. To activate or deactivate parameters in the PME solution 1 Select the Portal tab. 3. 4 Click Save. Clear the Active check box to deactivate the parameter. NOTE To use this feature. you must manually select the Active check box. you must log in to BMC Portal as a superadmin. 3 Clear the Active check box to deactivate the parameter. Deactivating a parameter in the Performance Manager Editor solution This feature enables you to deactivate parameters of the application classes in the Performance Manager Editor (PME) solution. the Active check box is cleared and the parameter is deactivated. select Performance Managers. click Add Application Class. The parameter status changes to offline. Expand the Properties object tree to display the infrastructure element. Chapter 5 Performance Managers and application classes 119 . click Add Parameter. 4 In the Add Application Class page.

in a Performance Manager.privatekey</map> <map name="passphrase">APPLICATION.fingerprint</map> </property-mapping> <parameter-value>PARAMLET. By default. when you want to deactivate the MountedDriveFromFUN parameter in the Active-instruction application class.Solution support for deactivating parameters Solution support for deactivating parameters BMC Portal enables you to deactivate parameters by default.commandOutput</parameter-value> </paramlet-call> <active-instruction type="false"/> </parameter-definition> 120 BMC Performance Manager Portal Monitoring and Management Guide . all parameters in the Performance Manager are active.password</map> <map name="privatekey">APPLICATION. the parameter definition is as illustrated below: <parameter-definition name="MountedDriveFromFUN"> <display-name>Mounted drive from fun</display-name> <description>Mounted Drive</description> <value-type base="integer"/> <value-analysis-definition> <alert-rule alert-on="alarm-or-warning" alert-after-count="2"/> <custom-attribute name="minValue" value="0"/> <custom-attribute name="maxValue" value="100"/> <custom-attribute name="direction" value="ascending"/> <threshold-definition enabled="true" name="warning"> <custom-attribute name="value" value="10"/> </threshold-definition> <threshold-definition enabled="true" name="alarm"> <custom-attribute name="value" value="20"/> </threshold-definition> </value-analysis-definition> <paramlet-call> <paramlet>patsdk-commandshell</paramlet> <solution>patsdk-commandshell-solution</solution> <property-mapping> <map name="hostname">APPLICATION. include the <active-instruction type="false"/> tag.protocol</map> <map name="userName">APPLICATION.port</map> <map name="protocol">APPLICATION.userName</map> <map name="password">APPLICATION.passphrase</map> <map name="fingerprint">APPLICATION.hostname</map> <map name="port">APPLICATION. For example. To deactivate parameters by default in a Performance Manager 1 In the parameter definition of the Performance Manager’s application definition xml file.

You can explicitly add PATROL Agents as elements and specify the corresponding PATROL integration Performance Managers. PATROL Agent integration If your organization uses PATROL Agents to monitor and manage your IT infrastructure. such as PerfMon and SNMP. you can accept or modify parameter thresholds. the Portal applies the global thresholds to the instance. the Portal obtains local thresholds for each instance from its PATROL Agent. that parameter is deactivated by default. sub-application class.Methods of remote monitoring NOTE You must not deactivate all the parameters in an application class. you must provide authentication credentials and properties that the application class can use to access the element and obtain performance data. and you specify the <active-instruction type=''false"/> tag in the parameter definition of the application definition xml file. Methods of remote monitoring The types of Performance Managers installed on your Portal determine the methods of remote monitoring that you can configure for the elements in your account. At least one parameter must be active. Chapter 5 Performance Managers and application classes 121 . As you specify application classes for infrastructure elements. or a discovered instance. If you do not have PATROL Agents installed in your IT environment. to obtain metrics from the target infrastructure elements. Agentless monitoring The agentless Performance Managers use industry-standard protocols. In addition. which enable the RSM to mine parameter values from the PATROL Agents and integrate agent-based data into the Portal. The type of collector used to obtain data and the type of application class determine the type of information that you need to provide. this is the only type of Performance Manager that you need to install on your Portal. you can use PATROL integration Performance Managers. If you choose the discovery method. or you can have the Portal discover the PATROL Agents and the parameter thresholds. 2 When you add an element by using the upgraded Performance Manager. If thresholds do not exist for an instance.

Parameter mapping between Performance Managers and Knowledge Modules To illustrate the parameter mapping between a Performance Manager and a Knowledge Module (KM). 122 BMC Performance Manager Portal Monitoring and Management Guide . Generally. Figure 10 Performance Manager parameter mapping to Knowledge Module parameters Integration Performance Manager for Coffee Pots Pot Capacity Pot Location Pot Monitor Pot Operating Status Pot Level Pot Metric Coffee Pot Knowledge Module potCapacity potType potLocation potMonitor potOperStatus potLevel potMetric potStartTime lastStartTime potTemperature Pot Temperature You can use the BMC Performance Manager Portal SDK to create PATROL integration Performance Managers that mine data from a PATROL Agent. The PATROL Integration Performance Manager for Coffee Pots has parameters that map to seven out of the 10 parameters in the Coffee Pot KM. consider the example shown in Figure 10 on page 122. the conventions shown in Table 9 show how the minimum and maximum parameter thresholds in KMs map to the parameter threshold ranges in PATROL integration Performance Managers. Threshold mapping between Performance Managers and Knowledge Modules The parameter properties in Performance Managers differ somewhat from those in KMs. you can use the Elements task or the bpmcli to synchronize the application classes and thresholds on Performance Manager with those on PATROL Agents. See the BMC Performance Manager Development and Certification Guide on the Documentation CD for detailed information about creating Performance Managers. See “Integrating PATROL Agent data into the BMC Performance Manager Portal” on page 27 for more information.PATROL Agent integration After configuring the PATROL integration Performance Managers.

PATROL Agent integration Table 9 Minimum and maximum values for mapped thresholds Performance Manager parameter thresholds PATROL Agent parameter thresholds border range is active for the agent parameter minimum and maximum border values match the agent parameter thresholds border range is inactive for the agent parameter and the Y-autoscale=No border range is inactive for the agent parameter and the Y-autoscale=Yes minimum and maximum border values match the minimum and maximum Y-axis values minimum and maximum border values are unbounded Chapter 5 Performance Managers and application classes 123 .

the corresponding alarm threshold is set to False. If the PATROL Border threshold triggers an alarm. the alarm threshold is set to True. If the PATROL Border range is nonzero–to-nonzero and it triggers an alarm. the alarm threshold is set to the PATROL Border maximum value. the warning threshold is set to True. s s s s border thresholds (Boolean) s s Alarm1 and Alarm2 thresholds are inactive. Border threshold is active. event instantly. the corresponding warning threshold is set to False. or after recovery 124 BMC Performance Manager Portal Monitoring and Management Guide . the warning threshold is set to the PATROL Border maximum value. Table 10 Differences between Performance Manager and Knowledge Module thresholds (part 1 of 2) PATROL Integration Performance Manager adaptation s PATROL KM threshold condition border thresholds (numeric) s Notes These threshold conditions are the only instances where a PATROL Border alarm sets a warning or alarm threshold for a Performance Manager parameter. Border threshold is active and is configured for warning and alarms.PATROL Agent integration Table 10 lists the types of parameters that do not have a one-to-one correlation and shows how the thresholds appear in the mapped parameters. s s s s parameter configured to trigger An event is triggered instantly. after n occurrences. If the PATROL Border range is greater-than-zero to greaterthan-zero and it triggers an alarm. Alarm1 and Alarm2 thresholds are inactive. If the PATROL Border threshold triggers a warning. If the PATROL Border range is 0–0 and it triggers a warning. The minimum is set to the PATROL Border minimum value. The alarm direction is set to ascending. If the PATROL Border range is greater-than-zero to greaterthan-zero and it triggers a warning.

As soon as RSMs are installed or upgraded.1 or later. If you upgraded from BMC Performance Manager Portal 1. When you installed the Portal. you can log on as a user and begin using the application classes contained in the Performance Managers to begin monitoring elements.2 or installed the BMC Performance Manager Portal for the first time. the new Performance Managers have a status of Unpublished. the installation program prompted you to insert the BMC Performance Manager Solutions CD or CD image. See “To upgrade a Performance Manager during a Portal upgrade” on page 127 for more information about publishing upgraded Performance Managers. the installation program copied the corresponding PAR files (including the application classes that they contain) to a staging directory on the Portal application server. it must be installed in the Portal database and have a status of Published. Chapter 5 Performance Managers and application classes 125 . the BMC Performance Manager Portal scanned the staging directory for those files and installed them in the Portal database. The warning range is extended so that it is contiguous with the start of the alarm range. the Performance Managers have a status of Published. If you upgraded from BMC Performance Manager Portal 2. During Portal startup.Installing new Performance Managers on the Portal Table 10 Differences between Performance Manager and Knowledge Module thresholds (part 2 of 2) PATROL Integration Performance Manager adaptation Notes PATROL KM threshold condition Alarm1 and Alarm2 ranges are Warning and alarm thresholds both active or both ranges are set to match and alarm direction is set to trigger the same state ascending. numeric threshold is inactive Boolean threshold is set to false and inactive boundary values between Alarm1 and Alarm2 are not contiguous The numeric threshold is set to 0 and is disabled. Installing new Performance Managers on the Portal Before you can use a Performance Manager. The Boolean threshold is set to false. The BMC Performance Manager Portal does not support noncontiguous threshold ranges. When you selected the Performance Managers from the CD or CD image.

You install a Performance Manager from a CD or CD image that is not part of the BMC Portal installation program. add an infrastructure element and select the new application classes. you might need to click the Performance Managers task in the navigation pane. select Performance Managers to open the Performance Managers page. The Performance Manager appears in the list of Performance Managers and has a status of Published. 126 BMC Performance Manager Portal Monitoring and Management Guide . You download a Performance Manager from the BMC Software Electronic Product Distribution (EPD) website. and select the Portal tab. 2 Log on to the BMC Portal with Portal administrator credentials. or add the new application classes to existing elements. The Portal installs the PAR file in the database. 3 Under Tasks in the navigation pane. To begin using the new application classes. NOTE To have the Performance Managers page reflect status changes. 4 Click Upload to open the Performance Managers–Upload page. 5 Click Browse to open a file selection dialog box.Installing new Performance Managers on the Portal The following conditions require that you manually install new Performance Managers on the Portal: s You use the BMC Performance Manager Portal SDK to create Performance Managers. and navigate to the PAR file from one of the following sources: s s the location of the PAR file that you used in step 1 PerformanceManagerName. log on as a user. s s To manually install a Performance Manager 1 Place the Performance Manager’s (PAR) file in a known location on your file system or have the Performance Manager CD available.par on the Performance Manager CD 6 Select the PAR and click Upload.

The procedures in this section s s s remove the earlier version of the Performance Manager change the status of the newer version to Publishing and then Published update any affected infrastructure elements with the new version of the application classes in the Performance Manager When an upgrade occurs on an existing application class. the following information is migrated to the new version of the application class: s s s application class properties and user configurations parameter threshold settings parameter history data To upgrade a Performance Manager during a Portal upgrade Use this procedure to upgrade each performance manager. You must verify that all of the RSMs are updated to the latest version and that they are all running before you can publish the Performance Manager solutions. s 1 When you use the BMC Portal installation program to upgrade the Portal. and select the Portal tab. individually. and resolutions for the latest patches and hot fixes available for the current version of BMC Portal. do not start publishing another solution until the first shows the upgraded version. check the Customer Support website at http://www.Upgrading Performance Managers on the Portal Upgrading Performance Managers on the Portal If you install or import a PAR file that replaces an earlier version of its Performance Manager on your Portal. individually. the new Performance Manager appears on the page for the Performance Manager. log on to the BMC Portal with Portal administrator credentials. Chapter 5 Performance Managers and application classes 127 . technical bulletins.bmc. WARNING s After you have installed BMC Portal. Install the patches and hot fixes. Then you must publish the Performance Manager solutions one by one. select any or all Performance Managers from the BMC Performance Manager Solutions CD or CD image on your hard drive. Ensure that you perform the BMC Portal Performance Managers (solution) upgrades only after installing the latest patches. 2 After the Portal installation. but with a status of Unpublished. If a solution is in the process of publishing.com/support to see the flashes.

3 Under Tasks in the navigation pane. and the previous Performance Manager shows a status of Published before starting to publish another Performance Manager. 5 After the first Performance Manager has completed the publishing process. Insert the BMC Performance Manager Solutions CD in a disk drive that you can access from your file system. The Performance Managers that you selected from the BMC Performance Manager Solutions CD appear in the list of Performance Managers and have a status of Unpublished. until all of the Performance Managers show a status of Published. one-by-one. WARNING Do not start publishing a Performance Manager when another Performance Manager is in the process of publishing. and the earlier versions of those Performance Managers have a status of Published or In Use. Wait until the process is complete. To upgrade a Performance Manager by importing the new version’s PAR file 1 Place the PAR file for the Performance Manager in a location that you can access through your file system: s Download the Performance Manager file from the EPD website to your chosen location. 128 BMC Performance Manager Portal Monitoring and Management Guide . select a Performance Manager and click Publish. The status for the current version of the new Performance Manager changes to Publishing and then Published. select Performance Managers to open the Performance Managers page. select Performance Managers to open the Performance Managers page. individually. 4 On the Performance Managers page.Upgrading Performance Managers on the Portal 3 Under Tasks in the navigation pane. repeat step 4 for each remaining Performance Manager in the list. s 2 Log on to the BMC Portal with Portal administrator credentials. and select the Portal tab. The status for the earlier version of each new Performance Manager changes to Upgrading and then is removed from the page.

and if necessary. C Click Upload. Removing Performance Managers from the Portal The following procedure permanently deletes selected custom or solution Performance Managers from the Portal database. The new version of the Performance Manager appears in the list and has a status of Unpublished.Removing Performance Managers from the Portal 4 Import the PAR file: A Click Upload to open the Performance Managers–Upload page. NOTE To have the Performance Managers page reflect status changes. B Click Browse to open a file selection dialog box. 5 Select the Performance Manager and click Publish. To remove a Performance Manager from the Portal 1 Ensure that the Portal is not using the Performance Manager to monitor infrastructure elements. and the earlier version has a status of Published or In Use. remove its corresponding application classes from any elements that use them. 3 Under Tasks in the navigation pane. and select a file. The status for the current version of the Performance Manager changes to Publishing and then Published. The status for the earlier version of the Performance Manager changes to Upgrading and then is removed from the page. select Performance Managers to open the Performance Managers page. Chapter 5 Performance Managers and application classes 129 . 2 Log on with Portal administrator credentials and select the Portal tab. You cannot delete a Performance Manager if any of its application classes are currently monitoring infrastructure elements. you might need to click the Performance Managers task in the navigation pane to refresh the page. The affected infrastructure elements begin using the updated application classes.

For each Performance Manager. The core Performance Managers include application collectors. you can delete multiple Performance Managers. 5 Select the Performance Manager to delete. The Portal supports the following types of Performance Managers: s s s core solution custom Core Performance Managers Core Performance Managers are those that are included with the BMC Performance Manager Portal. Types of Performance Managers The Performance Managers page lists the Performance Managers available to the users on the Portal. Table 11 Core Performance Managers and their application classes Application classes Domain Name Server Ping SNMP Trap Listener s s s s s s Performance Manager BMC PM for Lightweight Protocols–DNS BMC PM for Lightweight Protocols–Ping BMC PM for SNMP Traps BMC PM Monitor BMC PM for Lightweight Protocols–Port Monitor Network Service Port BMC PM Portal App Server Monitor BMC PM Portal Datafeed Monitor BMC PM RSM Monitor BMC PM Web Server Monitor BMC PM Portal App Server Monitor BMC PM PATROL Integration Monitor PATROL Agent Availability and Health Monitor PATROL Agent Availability and Health Monitor 130 BMC Performance Manager Portal Monitoring and Management Guide . and click Delete. verify that the Performance Manager that you want to delete does not have any assigned elements. click Delete to confirm the deletion. 6 On the Performance Managers–Delete page. which typically have names that begin with BMC PM Collector for. If necessary. the list includes its type.Types of Performance Managers 4 In the Elements column. and the Performance Managers listed in Table 11.

the PME creates and opens a copy of the selected Performance Manager in the editor. and provides the starting point for accessing all of the features required to administer Performance Managers on your Portal. enables Portal administrators to create custom application classes for the Portal and its users.Solution Performance Managers If you did not select any Performance Managers from the Solutions CD during installation of the Portal. The BMC Portal Help provides detailed procedures for creating. You can install BMC Software solution Performance Managers from a Solutions CD. When you edit a published custom Performance Manager. In this copy. Solution Performance Managers Solution Performance Managers are those that you can obtain from BMC Software or BMC Software partners. you can use the Performance Manager Editor to delete it from the Portal database. Custom Performance Managers If you cannot obtain a solution Performance Manager to monitor the infrastructure or applications in your environment. or command shell protocols to collect data. You cannot edit or delete a core Performance Manager. You cannot edit a solution Performance Manager from BMC Software. described in Table 12. by downloading them from the BMC Software EPD website. and administering Performance Managers and the application classes that they contain. SNMP. you can edit any custom or solution application class that uses PerfMon. NOTE This section provides some information about custom Performance Managers. acts as the main page for the PME. A series of Portal pages. Chapter 5 Performance Managers and application classes 131 . or from developers who use the Performance Manager SDK. or those created with the BMC Performance Manager Portal SDK. you can create custom Performance Managers. known collectively as the Performance Manager Editor (PME). If a solution Performance Manager is not in use. editing. you can still use the application classes in the core Performance Managers to monitor infrastructure elements. The Performance Managers page.

or Core shows one or more of the following states for the Performance Manager: s Publishing s Published s Unpublished s Upgrading s Publish Failed . enabling you to confirm the deletion of the selected Performance Managers selects the check boxes of all Performance Managers Note: You can edit only one Performance Manager at a time. Table 12 Item Buttons Upload opens the Performance Managers–Upload page. Custom. s You can access the Performance Managers task and PME when you log on with Portal administrator credentials and select the Portal tab. enabling you to edit the selected solution or custom Performance Manager opens the Performance Managers–Confirm Delete page. the first step in creating a custom Performance Manager opens the Performance Managers–Edit page. Unselect All clears the check boxes of all Performance Managers Name Version Type Status name of the Performance Manager version number of the Performance Manager identifies the type of Performance Manager: Solution. enabling you to add solution Performance Managers or those created with the Performance Manager SDK to the Portal opens a File Save or File Download box. On the Performance Managers page. solution Performance Managers and those created with the Performance Manager SDK have a Type of Solution.Custom Performance Managers s On the Performance Managers page. Performance Managers created with the PME have a Type of Custom.failureReason s In Use shows the number of elements on the Portal currently being monitored with application classes in the Performance Manager shows the number of element profiles that contain one or more of the application classes in the Performance Manager Features of the Performance Managers page Description Export Publish Create Edit Delete Performance Managers list Select All Elements Profiles 132 BMC Performance Manager Portal Monitoring and Management Guide . enabling you to save the PAR file to your local file system publishes the selected Performance Managers opens the Performance Managers–Create page.

and add application classes in the copy that is automatically created by the PME s The PME cannot create Performance Managers that integrate data from PATROL Agents. See the BMC Performance Manager Development and Certification Guide on the Documentation CD. EXAMPLE You can create an operating system Performance Manager that contains the following application classes: s s s Solaris Using SNMP Windows Using PerfMon Linux® Using Command Shell Chapter 5 Performance Managers and application classes 133 . Each application class can have only one collector. and an application class is composed of organized groups of subapplications.Custom Performance Managers With the PME. To create PATROL integration Performance Managers. you must use the BMC Performance Manager Portal SDK. you can use the following methods to create custom Performance Managers: s read a definition file that contains attributes that you can use to build a custom application class edit a custom Performance Manager and edit its application class. Application class properties Each Performance Manager is composed of at least one application class. but a Performance Manager can contain application classes that each use a different collector.

Child classes can require unique properties and credentials. use regular expressions to specify thresholds for numeric parameters. Multiple-instance application classes can exist many times on a monitored element. for example. Capacity. the higher the load. and Performance are child classes of the Oracle parent class. parameter parameter type a data point or measurement. child class groupings of similar parameters within the parent class Example: In BMC Performance Manager Express for Oracle. Availability. — For all multiple-instance application classes. the lower the amount of free space. s parent class an application that contains parameters that monitor similar attributes A parent class also has a root application instance that contains the Application Collector Status parameter. — For some multiple-instance application classes. specify warning and alarm conditions that the notification recipient receives about the warning or alarm 134 BMC Performance Manager Portal Monitoring and Management Guide . the less available space for the user (lesser value triggers alarm) alarm and warning thresholds s s s for string parameters. which also determines other parameter characteristics: s s s s s string float integer Boolean long alarm direction specifies whether a lesser or greater value indicates deterioration of the monitored parameter Example: s for CPU load. a computer has many running processes. you can specify the instances to monitor. for example. available disk space one of the following types. the slower the computer (greater value triggers alarm) s for available disk space.Custom Performance Managers The PME enables you to customize the properties that compose an application class described in Table 13: Table 13 Property instance type Application class properties (part 1 of 2) Description either of the following types: s Single-instance application classes can exist only once on a monitored element. for example. the Performance Manager enables you to discover instances on the monitored element. a computer can have only one system uptime. set default minimum warning and alarm thresholds for Boolean parameters.

Multiple-instance application classes can monitor more than one instance of an application on any computer. you can create the following types of application classes. you create an application class by specifying a command. After it is published. An operating system application class is an example of this type because you can monitor only one instance of an operating system on any computer. and then provide the required credentials and properties for those instances. Should the discovered instance no longer exist on the element. the Portal enables you to remove that instance from the element. Data collection requirements With the PME. Many multiple-instance application classes enable you to discover instances on the target elements as you add elements to the Portal or as you add an application class to existing elements.Custom Performance Managers Table 13 Property Application class properties (part 2 of 2) Description minimum and maximum values for the parameter that s s parameter value range set the ranges on charts prohibit entry of invalid warning and alarm ranges by users data modifications operations that display the numeric parameter value (on the Reports and Status tabs) in a format that differs from the raw measurement format. Chapter 5 Performance Managers and application classes 135 . s Performance Manager publishing Before you and your users can use the application classes in a new or edited Performance Manager. which correspond to the type of information that the application class will monitor: s Single-instance application classes can monitor one instance of an application on any computer. you must publish the Performance Manager. Application classes that monitor log files or processes are examples of this type because you can monitor more than one log file or process on any computer. you can select the discovered instances to monitor. When the discovery process is finished. For some collection protocols. you can create new application classes by specifying a definition file. not available for Boolean and string parameters Types of application classes When you use the PME. users with adequate permission can select an application class and assign it to an infrastructure element. Definition files contain attributes and other information that you can use to build the application class.

which shows the status of the collector. This table also shows the input files or commands that you might need to create application classes with the supported protocols. one instance for each process. You cannot view or edit collector parameters in the PME. 136 BMC Performance Manager Portal Monitoring and Management Guide .Custom Performance Managers Table 14 shows the collection protocols that you can use to create custom application classes with the PME. Application classes that use the Command Shell collector can use either the SSH or Telnet protocol to obtain parameter data. Command Shell collector You can use the Command Shell collector to create application classes from command shell output issued by one or more commands. you must provide a command that the RSM program runs to obtain the initial data from the target element. Table 14 Supported collection protocols for custom application classes Definition files and input properties command that returns parameter values HTML files saved from PerfMon Performance graphs MIB files Collection protocol Command Shell (SSH/Telnet) PerfMon SNMP In addition to the parameters that you customize. each application class also includes the Application Collector Status (ACS) parameter. When creating application classes that use this collector. You can then use the command and the output in the PME to create the application class. but users of your custom Performance Manager can see them when setting thresholds and when accessing element views on the Status tab. The ps command returns values for multiple instances. TIP Run commands on a representative computer until the command produces the required output. EXAMPLE s s The uptime command returns values for a single instance. Command shell application classes can define parameters that return a single value (single instance) or more than one value (multiple instances).

the application class must provide the following items: s for each instance. Chapter 5 Performance Managers and application classes 137 . PerfMon collector When creating application classes that use the PerfMon collector. disk space). Windows XP. An application class that uses the PerfMon collector must have the following characteristics: s unique application class name (specified in the PME) unique parameter names that have the same PerfMon Performance Object unique PerfMon Performance Object and Counter pairs for each parameter in the application class PerfMon Performance Object and Counter pairs that do not identify a parameter previously deleted from the application class s s s Users who select custom application classes that use the PerfMon collector can provide shared credentials to authenticate the RSM. a valid regex that identifies the parameter value The PME has instance and regex testers to validate your regular expressions. The BMC Portal Help provides procedures that describe how to create application classes that use the Command Shell collector. A definition file can specify parameters that report on multiple instances (for example. You can create a PerfMon definition file in the Performance Monitor (PerfMon) on the Windows 2000. The BMC Portal Help provides procedures that describe how to create application classes that use the PerfMon collector and the definition files required to create them. or Windows 2003 operating system. you can have the PME upload PerfMon definition files that have an HTML file type. s Users who select custom application classes that use the Command Shell collector can provide shared credentials to authenticate the RSM.Custom Performance Managers Also. a valid regular expression (regex) that identifies the instance and the identifier for the instance for each parameter in an instance.

The PME will let you specify more top-level parameters. ensure that you do not place more than 20 application classes in the top (or root) application instance. you can upload the primary and dependent MIBs when creating an SNMP application class. but the RSM cannot obtain more than 20 top-level parameter values. When creating the application class. if that information is contained in the specified MIB. If necessary. at least one instance name in the source MIB file is cryptic and does not represent the parameters that it contains. If a parameter name in the instance more closely represents the instance content. the selected parameter name represents the instance name on the Status tab. When using SMNP application classes to monitor infrastructure. Should you require more than 20 of the top-level parameters in the top-level instance. 138 BMC Performance Manager Portal Monitoring and Management Guide . The PME can parse and use the parameter name and data type from the MIB. To create application classes that use the SNMP collector. By default. ensure that the MIBs used to create the application class are also loaded on the snmpd daemon on the target element. The BMC Portal Help provides procedures that describe how to create application classes that use the SNMP collector. When users select the application class to monitor infrastructure. split the parameters between two application classes. Frequently. you must upload SNMP MIB files that the PME can use as the definition files to create parameters. you can choose to have the parameter name represent the instance name.Custom Performance Managers SNMP collector The SNMP collector is used to create application classes that use Object Identifiers (OIDs) to provide unique identifiers for the parameters in the application class. the BMC Performance Manager Portal populates an internal MIB library with many commonly referenced MIBs. An application class that uses the SNMP collector must have the following characteristics: s s s s unique application class name (specified in the PME) unique parameter names in the application class unique Object Identifier (OID) for each parameter in the application class OIDs that do not identify a parameter previously deleted from the application class NOTE Many MIBs that you can download from the Internet have dependencies on other MIBs.

Editing published custom Performance Managers The PME enables you to select and edit published custom Performance Managers. In addition. regardless of how often you edit the application classes in the unpublished Performance Manager. you can s s s s change the properties of an application class (but you cannot change collectors) add and remove instances (subapplications) add and remove parameters modify parameter properties Editing unpublished custom Performance Managers When you create a new Performance Manager. The PME enables you to modify any of the properties for the Performance Manager and the properties in an application class. Chapter 5 Performance Managers and application classes 139 . the PME assigns a version number of 1. the version number remains the same. you can s s s add application classes to a Performance Manager modify existing application classes in a Performance Manager remove application classes from a Performance Manager When editing an application class.Editing Performance Managers Editing Performance Managers The manner in which the PME interacts with the Performance Manager depends on the state or type of Performance Manager being edited. When you select a published Performance Manager to edit. Until you publish the Performance Manager. The PME increments the last two digits of the version number only for a published custom Performance Manager. the PME creates a copy that you can edit. The PME uses the short name as the PAR file name for the Performance Manager.0. The new version number is displayed on the Performance Managers–Edit page.00. s s Editing unpublished custom Performance Managers Editing published custom Performance Managers You can make minor changes to the properties of a Performance Manager by changing the Performance Manager display name and its internal short name.

the following restrictions apply: s If you had assigned application classes from the earlier version of the Performance Manager to infrastructure elements. s NOTE This situation would occur only if you had created a JMX application class with the Application Class Editor in an earlier version of the Portal or in PATROL Express. the JMX application classes are removed from the elements and the data associated with the deleted application classes will be deleted from the database. When you edit custom Performance Managers.01) as the display name and version. and opens the new Performance Manager in the editor. the PME creates a new Performance Manager with My PM for Coffee Pots (version 2. publishing the edited copy updates the elements so that they use the edited version of the application classes.0. If the selected Performance Manager contains application classes that use the JMX collector. 140 BMC Performance Manager Portal Monitoring and Management Guide .Editing published custom Performance Managers EXAMPLE If you select My PM for Coffee Pots (version 2. After you publish the edited Performance Manager.0.00). the JMX application classes are not copied to the editable version of the Performance Manager.

. . . . 143 Accumulated parameter values. . . . . . . . . . . . .00. . . . . . . . . . . . . . . . Crystal Reports 2008 (Designer component). . . . . . . . . 160 Dashboard parameter charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Multiple parameter history charts . . . . . . . . . . . . . . . . . 144 Data retention policies that affect object view content . . . . . . . . . . . . . . . . . . . . 174 Upgrading to BMC Reporting Foundation 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Configuring the datafeed utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and integration components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Standard parameter values . . . . . . . . . . . . . . . . . . . 202 External CDE movement . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . 187 Continuous data export configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Report types and details . . . . . . . . . . . . . . . . . . . 145 Retention policies . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Upgrading to Crystal Reports 2008 (Designer component) . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 6 6 Reports This chapter describes the available reporting options and presents the following topics: Overview . . . . . . . . . 162 Installing the integration components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Purging inactive data from the Portal history tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Maintaining the continuous export to the CDE database . . . . . . . . . . . . . . . . . 190 Continuous data export requirements . . . . . . . . . . . . . . . . . . . . . . . . . 145 Properties that control the raw data retention policies . . . . . . .2. . . . . . . . . . . . . . . . . 201 Additional configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Changing the retention policy for the CDE database. . . 153 Health At A Glance report for elements . . . . . . . . . . . . . . . . . . . . 142 Parameter update intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Publishing and scheduling generated reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Downloading and installing BMC Reporting Foundation 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .00. . . . . . . . . . . . . . . . . . . . . . . 152 Top N report for object groups or the account . . . . . . . . . . . . . . . . . . . . . . 144 Data summarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Purging unknown and unused events from the event table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Time interval controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Properties that control event history retention . . . . . . . . . . . . . . . . . . . . . . . . . 206 Chapter 6 Reports 141 . . 184 Uninstalling the integration components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Reports tab . . 161 Enterprise reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

default. In addition to these reporting options. Regardless of parameter status. the RSM sends the values for all parameters in the application class to the Portal.minutes property in Appendix C.” s When any parameter in an application class changes its status.reporting. In addition to these reports. a parameter might have additional raw data values between report update intervals. You can then use Crystal Reports® 2008 (Designer component) to generate on-demand reports. 142 BMC Performance Manager Portal Monitoring and Management Guide .Overview Overview The Portal provides embedded reports that you can access from the Reports tab. as illustrated in Figure 11 on page 143. which is less often than or equal to the frequency of data collection (collection interval). “BMC Performance Manager Portal files. Parameter update intervals The frequency at which the RSM sends parameter data to the Portal is determined by an element’s report update interval and the status of the parameters in the application class. which you set for each application class. or schedule periodic reports from the data in the CDE database. see the drmop.interval. For more information. s The report update interval determines the minimum frequency at which the RSM sends parameter values to the Portal. Therefore. you can configure the Continuous Data Export (CDE) utility to send raw parameter data to an external database. the RSM sends parameter values to the Portal at this frequency. this chapter also describes the way in which the Portal receives report data from the RSM and how the Portal summarizes and saves data in the Portal database instance. Unlike the collection interval. depending on the statuses for the parameters in an application class. you set the report update interval for each element.

Although the parameters in the top two charts never changed status. depending on the time period of the chart) at each chart interval.Standard parameter values Figure 11 Affect of status changes on reported parameter values These charts show the raw parameter values for parameters in the same application class. unless a parameter status change occurs. their values were reported each time that the other parameter changed status. the Portal shows raw data values (or averaged values. the RSM sends the last data value that it collected during the report update interval. You can view the values for parameter data on the Status and Reports tabs. Standard parameter values For most parameters. Chapter 6 Reports 143 . Figure 12 Standard parameter values 1 2 3 4 5 4 3 2 1 1 2 3 4 5 4 3 data values collected from the parameter 1-minute collection interval 5-minute report update interval 5 1 4 data values sent to the Portal On parameter history charts. as shown in Figure 12. The Portal saves this value in the database as raw data for the parameter.

the Portal receives data at least once every five minutes—more often if infrastructure parameters go in and out of warning and alarm states. half-hour data to produce the charts. Data summarization The data summarization process creates a data point that is the average of the raw data from the previous half hour. EXAMPLE The RSM collects a data point every minute and sends report data to the Portal once every five minutes. suppose that you set the report update interval to 15 minutes. The Portal saves this accumulated parameter value in the database as raw data for the parameter. 144 BMC Performance Manager Portal Monitoring and Management Guide . The Portal uses raw and summarized. At 10 minutes after the end of each half hour. Immediately after the end of each half hour. some charts might not show data for the most recent day. depending on the end time specified for the chart. as shown in Figure 13.Accumulated parameter values Accumulated parameter values Some application classes contain parameters that require the RSM to total the collected data values and send the totaled value to the Portal. Because the Portal computes a daily data point after the end of the day. Using this scenario. Summarizing raw data into half-hour and daily data points reduces the data retrieval effort required to generate reports that span large time intervals. the Portal database computes the average value for the two data points and creates a single halfhour data point. See the documentation or Help for application classes for more information. the Portal database bundles the six data points (or more if there were warnings or alarms) into a single half-hour summarized data point. Figure 13 Accumulated parameter values 1 2 3 4 5 4 3 2 1 1 2 3 4 5 4 3 data values collected from the parameter data values sent to the Portal 1-minute collection interval 5-minute report update interval 15 11 18 On parameter history charts. the Portal shows totaled values at each chart interval. For example.

or hardware failure). Retention policies The amount and types of data stored in the Portal database are controlled by data retention policies. to 1 or 2 days. Properties that control the raw data retention policies The Portal is optimized to run with the default retention policies. This rollover period also determines the amount of data that is deleted when a partition is dropped. BMC recommends that you set history retention for 7 days. To control the amount of data retained in the Portal database. can cause the Portal to lose data that was not summarized (in the event of a Portal downtime caused by maintenance.properties file on the Portal application server and modify the following properties: s portal. However. the retention policy purges data from raw data tables sooner than it does from the hourly or daily tables. Database performance is optimized for a 14day retention of raw data if the report update interval is higher than 5 minutes. Because the Portal collects and stores raw data faster than it summarizes hourly and daily data.retention sets the number of days that the database retains raw parameter data values. The rollover period for a data type sets the frequency at which the Portal stops writing data to one partition and starts writing it to a new partition. — Increasing the retention period can adversely impact database performance and requires more disk space. Controlling the amount of historical data that is stored in the Portal database enables the Portal to quickly return the requested charts.value. Data summarization and data retention policies of parameter data determine the data that is used by the Portal to generate the various object views.parameter. the raw data tables grow faster than the summarized tables. Chapter 6 Reports 145 . — Significantly decreasing the retention period.Data retention policies that affect object view content Data retention policies that affect object view content The Portal stores parameter data in partitions in the database and then the database purges data by dropping an entire partition. you can access the drmop. upgrades. Should you need to change them.history.

schedulehours enables you to schedule the external summarization.element. — The value of this property must match the value for the portal.enabled and the portal. See “Top N report for object groups or the account” on page 153. see “Configuration files” on page 319 and Table 51 on page 322.history. — Increasing the retention period requires more disk space. by default.history.element.summarizationDataPoint. — Increasing the retention period requires more disk space.parameter. so disabled summarization would cause those reports to display with missing data.parameter. 146 BMC Performance Manager Portal Monitoring and Management Guide .externalsummarization.schedulehours properties to enable external summarization.enabled enables you to configure the external summarization by using the database task instead of using the BMC Portal application server. then the task is scheduled to run at 2 A. s portal.history. BMC recommends a setting of 92 days. BMC recommends that you set the value at 92 days.Properties that control the raw data retention policies s portal.retention property. However. You must modify the portal.history. such as blackout and monitoring off.retention sets the number of days that the database keeps summarized parameter values. s portal. — Reducing this retention period reduces the time period in which you can chart data points.externalsummarization. some of the reports include summarized data points.externalsummarization.parameter.history.statusHistory.parameter. s s For more information about the properties file and its attributes. portal.history. portal.history.parameter.M. If you set portal.disabled enables you to disable the summarization of raw data.parameter. Although this property has a default value of 428 days.history.retention sets the number of days that the database keeps element status changes. Although the default value of this property is 428 days.externalsummarization.enabled=true. This avoids the usage of the BMC Portal application server for the BMC Portal summarization task.history.summarization.externalsummarization.summarizationDataPoint.parameter. every day.

but BMC recommends setting this at 14 days.event.history. Chapter 6 Reports 147 . The policy takes the number of days specified.event. By default. To retain 100 days of data.history. s The data retention policy uses the number of days specified in the portal.retention = 100 s If you use the following recommended values.history. you must specify one of the valid time values in the property file.history. portal. the Portal saves each event for at least 100 days. 1 day’s worth of events are purged — portal. Longer retention periods can affect the response time of the Events tab and the Health At A Glance report (which also contains event history data). the Portal saves seven day’s worth of data in a partition. The data retention policy uses the specified number of days to determine when the database purges event partitions.period sets frequency at which event data rolls over to a new partition. When the database drops a partition.event.rollover.rollover.history.history. — portal. and then rounds up the value. but uses extra disk space.event.event.history.period = WEEK — portal. the Portal saves one days worth of events in a partition and drops a partition when it has finished saving 14 partition’s worth of data (14 days).period = DAY — portal.Properties that control event history retention Properties that control event history retention The event history partition size and the frequency at which the partition is purged are controlled by the following properties: s portal. multiplies that by the number of days in the rollover period.retention property to determine the number of partitions to retain. This inactive data is not displayed in the Portal.rollover. the Portal must keep 15 weeks (105 days) worth of data. When changing the rollover period.retention sets the number of days of event data to save in the database. See page 328 for valid time values.event.retention = 14 Purging inactive data from the Portal history tables The Portal history tables are not deleted. which can cause performance issues in the Portal.event. even after deleting an instance or node from the Portal. EXAMPLE s If you use the following default values. Specifying a longer rollover period means that more data is deleted when the Portal database drops a partition.

(For details. you must use the exportParameterHistory to collect historical data before purging inactive data. the Oracle UNDO table space usage can reach 100 percent.summarizationDataPoint. see “Data-extraction commands” on page 270). However. Monday.history.” 1 To enable purging of inactive data. The first time the purge script runs.enabled =false 2 To set the day or days when you want the purge to occur. the UNDO tables space usage returns to normal automatically once the purge is complete.purgepsdp.Purging inactive data from the Portal history tables If you use the Continuous Data Export (CDE) database to store BMC portal data for reporting. depending on the amount of inactive data accumulated between the weekly purges. during the purging process. If you set the purge script to run on a weekly basis. or if you do not need the historical data. change the following property to true: portal. NOTE When this feature is enabled. To purge inactive data The properties used to purge inactive data are in the drmop. the UNDO table space usage should return to normal within 2 to 4 hours after each subsequent purge. see Appendix C. You do not need to run exportParameterHistory if data has already been exported by using exportParameterHistory.6 sets the job to run on Sunday. it could take from 2 to 8 hours for the UNDO table space usage to return to normal. For example.cleaninactiveparameter.parameter.parameter. you can enter multiple valid values and separate them by a comma (no spaces). “BMC Performance Manager Portal files. Use the following procedure to purge inactive data: “To purge inactive data” on page 148. set the portal. then run the exportParameterHistory command to collect the inactive data for reporting purposes. 148 BMC Performance Manager Portal Monitoring and Management Guide . and Friday. a value of 1.2. Otherwise.properties configuration files.history. For details. depending on how much inactive data there is to purge.scheduledays property by using the following valid values: s s s s s s s 1 = Sunday (default and recommended value) 2 = Monday 3 = Tuesday 4 = Wednesday 5 = Thursday 6 = Friday 7 = Saturday If you want the job to run the purge on more than one day.

change the value of the following property to true: portal.cleanunknownevents.m.parameter. see Appendix C. If you do not want to save those events.” 1 To purge unknown events. “BMC Performance Manager Portal files. This property only allows you to schedule the purge on the hour.history.schedulehours property by using the following valid values: 10 through 19 (the default value) Setting the property to 10 schedules the purge for 10:00 a.m.enabled=false Chapter 6 Reports 149 . 11 schedules the purge for 11:00 a.properties configuration files.purgepsdp. when an instance or element or application is deleted. set the portal. for example.schedulehours=19 Purging unknown and unused events from the event table The retention policy for the event table does not clean up the events that occurred that are unused.events. up to 19.purgepsdp. You cannot add minutes.m. The time set for this property is the time on the database server. Use the following procedures to purge unknown and unused events: s s “To purge unknown events” on page 149 “To purge unused events” on page 150 To purge unknown events The properties used to purge events are in the drmop.history. reducing the load on the Portal and the database while preventing any locking issues. For more information. you can set a purging job schedule that cleans up those events.history..Purging unknown and unused events from the event table 3 To set the scheduled hours when you want the purge to occur. Some times Ok-Unknown and Unknown-OK events are generated and fill the table. which schedules the purge for 7:00 p. For example: portal. The jobs used to remove unknown and unused events execute with partitions in mind. and so on.parameter.purgeunknown.

scheduledays property to one or more of the following valid values: s s s s s s s 1 = Sunday (default and recommended value) 2 = Monday 3 = Tuesday 4 = Wednesday 5 = Thursday 6 = Friday 7 = Saturday To use these values in combination. The time set for this property is the time on the database server.6 3 To schedule the time on the day or days when you want the unknown events purged. For example: portal.cleanunusedevents.events. For more information. change the value of the following property to true: portal.properties configuration files.purgeunknown.events. the following value sets the purge to occur on Sunday and Friday: portal.schedulehours=19 To purge unused events The properties used to purge events are in the drmop. change the portal.) through 23 (which sets the value to 11:00 p. separate them by a comma.Purging unknown and unused events from the event table 2 To schedule the day or days when you want the unknown events purged.scheduledays=1. see Appendix C.events.” 1 To purge unused events.m.history. or 7:00 p.m.).enabled =false 150 BMC Performance Manager Portal Monitoring and Management Guide . For example.purgeunused.purgeunknown.history.purgeunknown.history.history.schedulehours property by using the following valid values: Valid values for this property are 0 (the default value that sets the value to midnight or 12:00 a.events. change the portal.m.events.purgeunknown. The default setting is 19.history. “BMC Performance Manager Portal files.

The time set for this property is the time on the database server.schedulehours property by using the following valid values: Valid values for this property are 0 (the default value that sets the value to midnight or 12:00 a.events.purgeunused. You can view data collected during a different period by adjusting the report time range. separate them by a comma. The charts on the Reports tab vary.6 3 To schedule the time on the day or days when you want the unused events purged.Reports tab 2 To schedule the day or days when you want to purge unused events.purgeunused. Table 15 shows the charts available for each view.history.scheduledays property by using the following valid values: s s s s s s s 1 = Sunday (default and recommended value) 2 = Monday 3 = Tuesday 4 = Wednesday 5 = Thursday 6 = Friday 7 = Saturday To use these values in combination. The default setting is 19.history. the following value sets the purge to occur on Sunday and Friday: portal. depending on the active view of the Reports tab.events.m. Table 15 Charts available from the Reports tab (part 1 of 2) Infrastructure element view Account view Object Group view Application class view Report Parameter history chart (single chart) Parameter history chart (multiple charts) Parameter history table + + + Chapter 6 Reports Parameter view + 151 Instance view .history.history.events.purgeunused. Example: portal.scheduledays=1.). change the portal.events. For example. or 7:00 p.purgeunused.m.m.) through 23 (which sets the value to 11:00 p.schedulehours=19 Reports tab The Reports tab provides charts that show performance metrics for selected parameters. change the portal.

Time interval controls Table 15 Charts available from the Reports tab (part 2 of 2) Infrastructure element view Account view Object Group view Application class view Report Top N Health At A Glance + + + On all charts. you can use to export the chart data to a file. and the chart contains data points through January 20. s Hourly intervals—When selecting Hours. 152 BMC Performance Manager Portal Monitoring and Management Guide Parameter view Instance view . For example. See the BMC Portal Help for information about accessing and customizing the object views on the Reports tab.M. the x-axis shows January 20. — Hourly reports end with the current hour of data. you can control page content by using the time controls to adjust the time interval of interest. if on January 20 you select Now and a 14-day interval. All charts show the data summarized in data points that represent one day. For example. the data points represent raw data. you request a report for the last 24 hours. You can choose to view chart data in daily and hourly intervals. if at 7:30 A. — When showing 12 to 168 hours of data. s Daily intervals—When selecting Days. TIP Where available. you can choose to show from 1 to 184 days worth of data on the chart. a tooltip shows the value of the data point. the report ends with 8:00 A. Time interval controls For many object views. the data points represent summarized values of hourly data.M. — When you view 1 to 10 hours of data. you can choose to show from 1 to 168 hours’ worth of data on the chart. Daily charts end with the current day of data. when you roll the mouse pointer over a data point.

the Top N report is displayed. the chart shows 12 hourly data points on the x-axis that start with January 6 at 7:00 A. You might not see the summarized parameter values for a new element for 30–40 minutes after adding the element. you can choose to view as many as 50 elements at a time. If you select 12 hours ending on January 6 at 6:00 P. For example.M. Figure 14 Top N: report settings and content Chapter 6 Reports 153 . as shown in Figure 14 on page 153. When viewing this report.M. The parameter performance and the number of available elements that use the parameter determine which elements appear in the report. Top N report for object groups or the account When you select the account or an object group from the navigation pane..Top N report for object groups or the account The ending date and time selection represents the right-most data point on the x-axis on a chart. and end with January 6 at 6:00 P. This report compares the history of a selected parameter across a specified number of elements. you can quickly view the five elements that have the least amount of remaining memory.M.

s s application classes from which to select a parameter This list contains all application classes in the selected Performance Manager.Top N report for object groups or the account Report settings The following settings determine which element charts appear in the report. Time settings The Top N time controls provide predefined time periods for this report. as shown in Figure 15. s names of parameters that return numeric values For parameters in subapplications. this list contains only those Performance Managers found in the selected group. s predefined times from which you can choose to view the report Top or Bottom selection from the performance drop-down list s s selection from a drop-down list for the maximum number of elements in the report Performance Manager name selected from a drop-down list When you select an object group in the navigation pane. Figure 15 Top N: time controls 154 BMC Performance Manager Portal Monitoring and Management Guide . the list shows the subapplication name followed by the parameter name (SubapplicationName|ParameterName).

The length of the other bars is determined by their average value. To change the time that you wait for the report to appear before a timeout occurs.job.minutes property. For more information about this property. Table 16 Item Output controls for Reports tab Description exports parameter data points from the report to an external data file You can specify the column and row delimiters.Top N report for object groups or the account Report content After you click Show Report to adjust the report content settings.topn.reports. this report might time out before the data is displayed. which opens the Parameter History Chart for the parameter TIP If your account contains a very large number of elements.batch. Output options You can use the output controls described in Table 16 to print or export parameter data from a Top N report. see page 324. modify the value of the drmop. relative to that of the top bar.timeout. The top bar spans the entire available space. the report shows the following information about each element: s name of the element Clicking the element name opens the Status tab for the element. s s s s . writes the selected report to a PDF file Chapter 6 Reports 155 . s icon that represents the current status of the element and the most recent (raw) value for the parameter minimum summarized value reported for the parameter during the specified period maximum summarized value reported for the parameter during the specified period average summarized value of the parameter reported during the specified period The bar represents the average value of the parameter during the selected period.

and most of the data in this report is not available until you select a time range.Health At A Glance report for elements Health At A Glance report for elements When you select an infrastructure element from the navigation pane. You can click to view the report in a PDF file. Figure 17 Health At A Glance: Element Status Summary 156 BMC Performance Manager Portal Monitoring and Management Guide . Time controls The time controls set the time range for all charts and graphs in this report. shown in Figure 17. From the time controls. as shown in Figure 16. contains the charts that show the history of the element’s status and the parameters that caused events during the specified time. This report contains charts that provide an overview of the status of the element. From Adobe Acrobat. you can select one of the predefined time ranges. you can save the report to your file system or send it to a printer. Figure 16 Health At A Glance: time controls Element Status Summary This section of the report. you can view the Health At A Glance report.

In this case.Health At A Glance report for elements Status by Time The pie chart in this section shows the statuses for the selected element during the specified time.exclude_time) × 100% s s s s By default. suppose that you added the element to the Portal during the previous 18 hours and you specified 24 hours for the report period. Clicking opens the Parameter History Chart for the corresponding parameter. For example. Offline. The bar color represents the alert status of the parameter. Top Parameters Causing Alerts This section shows all of the parameters in the element that triggered an alarm or warning notification during the specified period. the Offline status would represent six hours of the (24-hour) pie. Each section represents the percentage of time during the specified time range that the element spent in that status. Element Attributes This section shows the following information about the selected element: s fully-qualified host name of the element operating system of the element list of application classes monitoring the element icon that represents the current status of the element and the hours and minutes that the element has been in its current state element availability (hours and minutes and the percentage of time that the element was in OK) during the specified period The Portal uses the following formula to compute availability: up_time/(total_time . Blackout. the Portal uses the following statuses for up_time and exclude_time: — up_time: OK and Warning — exclude_time: None. and Unknown Chapter 6 Reports 157 . NOTE The Offline status represents all times when the Portal has no data for the element.

a history chart. For each parameter. If an element is in a blackout period during the reporting time and the availability formula excludes blackout periods from the formula. shows the parameter values for the time range specified in the time controls at the top of the page. s actual time (hours and minutes) and the percentage of time that the element had a status of OK during the specified period actual time (hours and minutes) and the percentage of time that the element was in Critical during the specified period actual time (hours and minutes) and the percentage of time that the element was in Warning during the specified period s s Key Parameters This section shows the top four key parameters for the selected Performance Manager on the element. the element availability is NA. the Unknown status is an aggregation of the Unknown. you can modify the availability properties described on page 324. similar to the one shown in Figure 18. Offline. Figure 18 Health At A Glance: Key Parameters 158 BMC Performance Manager Portal Monitoring and Management Guide . s To change the statuses included with these values.Health At A Glance report for elements s When computing availability. and None statuses.

When an application class contains more than four key parameters. the Key Parameters list shows No key parameters to display. Figure 19 Health At A Glance: Element Events Table 17 lists the attributes shown for each event. which represents an infrastructure element name of the element object groups to which the element belongs date and time when the state change occurred Chapter 6 Reports 159 . The following parameter conditions or attributes determine the sort order for the key parameters. Table 17 Item Event severity icon Object type icon Element Group Time Element event attributes in Health At A Glance report (part 1 of 2) Description represents the severity of the event . the sort order of the key parameters determines the top parameters for the specified time range. Click select key parameters to view to change the key parameters shown in the charts. and which parameters appear in the report: s s s severity level parameter priority alphabetization Element Events This section lists the events that occurred on the element during the specified time.Health At A Glance report for elements NOTE If key parameters are not defined for the application class.

You can show up to 10 parameters on the page by selecting an option from Number of Charts to Display.Multiple parameter history charts Table 17 Item Element event attributes in Health At A Glance report (part 2 of 2) Description name of the parameter and the value that triggered the event for events that triggered notification. instance. By default. where each chart uses the same element name. Figure 20 shows the report options that affect all parameter charts in the report. Figure 20 Options for multiple parameter history charts Number of charts on page time-interval options You can use this report in the following ways: s to view many parameters from the same element. whichever is fewer. s to compare the same parameter on multiple infrastructure elements Figure 22 on page 161 is an example of charts that display the same parameter name for different elements. the Notified link provides a list of notification recipients Description Details Multiple parameter history charts When you select an instance or an application class from the navigation pane. this report shows the first two parameters in the application class. you can view multiple parameter history charts. or application class Figure 21 is an example of the default view of this report. or the number of parameters in the application. 160 BMC Performance Manager Portal Monitoring and Management Guide .

Figure 22 Comparative parameter history report for one parameter The parameter name is the same in all charts. Use the option lists and application class. you can create a dashboard that enables you to quickly view and compare the performance of key parameters on these computers. if you are responsible for a specific set of computers that provide a critical business service.Dashboard parameter charts Figure 21 Comparative parameter history charts for one element The element name is the same in all charts. and each chart displays the values for a different parameter. to export the data values for the applicable chart. Chapter 6 Reports 161 . Dashboard parameter charts Infrastructure dashboards enable you to create and save views of important element metrics. and parameter. For example. and each chart displays the parameter values for a different element. Click above each chart to adjust the element name.

these names are used interchangeably. you can add dashboard sections that contain parameter history for one parameter or sections that contain data values for as many as six parameters.com/support. NOTE Before you begin You need a user name and password for the BMC Software Electronic Product Download (EPD) site.2.Enterprise reports When creating dashboards that contain parameter values. The BMC Performance Manager Portal product includes a set of report templates that you can use with the CDE database to provide a variety of operational reports based on Portal data. In the document.1.00 is also referred as SAP® BusinessObjects™ Enterprise XI 3. and integration components BMC Reporting Foundation 3. You can register and obtain credentials at http://www.00. 162 BMC Performance Manager Portal Monitoring and Management Guide .2. Crystal Reports 2008 (Designer component). Enterprise reports In addition to the embedded reports that you can access from the Reports tab. you can also generate reports by running Crystal Reports 2008 (Designer component) against parameter data in the CDE database. For charts that contain multiple parameters.bmc. Downloading and installing BMC Reporting Foundation 3. the chart legend and chart line styles and colors differentiate the parameters.

2009. If you must have the BMC Datastore product and were active on a support contract for any of the products below prior to July 1. The BMC Datastore product is no longer available to new licensees of BMC Performance Manager Reporting.Original Version BMC Proactive Service Desk Package BMC Service Impact Manager PATROL Integration for DashBoard PATROL Reporting for Networks BMC Performance Manager Portal BMC Performance Assurance for Servers s You will need to obtain your own Oracle license if you were not active on support for BMC Performance Manager Portal prior to July 1. this document refers to those specifically by name. References to the "database" in this document refer to either the BMC Datastore product or your own licensed version of Oracle. BMC Software bundled Oracle as the BMC Datastore product. you must have the BMC Portal database installed (Default instance name: BMCREPO in the installation screen). In the email message. In the prior releases of this product.r.mm s s Product list: — — — — — — — — — — — — — — — — — — — — — — — — — — BMC Application Performance and Analytics BMC Enterprise Event Manager BMC Event and Impact Management BMC Event Manager BMC Event Manager . 2009.2. send an email message to ProductionControl@BMC.com to obtain a copy of this software.00. and NOTE s Before installing BMC Reporting Foundation 3.Enterprise BMC Event Manager .Downloading and installing BMC Reporting Foundation 3.Original Package BMC Impact Explorer BMC Impact Manager BMC Impact Manager Adapters BMC Impact Manager Service Components (500 pack) BMC Impact Portal BMC Impact Standalone Node BMC Impact Web Console . interchangeably. provide the following information: — Company name — Valid support ID — BMC Datastore version — BMC Datastore platform — BMC Performance Manager Portal version V.Business User BMC Performance Analysis for Servers BMC Performance Assurance for Virtual Servers BMC Performance Management BMC Performance Management Reporting BMC Performance Manager Console BMC Performance Manager Reporting BMC Portal .00. Chapter 6 Reports 163 . Crystal Reports 2008 (Designer component).2. If instructions differ between the use of your own licensed version of Oracle and the BMC Datastore product.

Installing the integration components To download BMC Reporting Foundation 3.00 and Crystal Reports 2008 (Designer component).Designer component 5 Select BMC Performance Manager Operational Crystal Reports. see SLN000015109081.com/epd and log on. You must select I agree in the Export Compliance Disclaimer and TRIAL AGREEMENT panes. 164 BMC Performance Manager Portal Monitoring and Management Guide . 4 Select the following components: s s BMC Reporting Foundation .2. To obtain a license key for BMC Reporting Foundation 3.2. s s Installing the integration components Installing the integration components is a manual operation that is performed on the Report Server host computer. see SLN000015109080. To install Crystal Reports 2008 (Designer component). 3 Follow the instructions to select BMC Performance Manager Portal latestVersion.2. 6 Download the BMC_PM_Reports. and extract the BMC_PM_Reports.bmc. 7 Install the BMC Reporting Foundation 3. NOTE s To install BMC Reporting Foundation 3.xml files. and integration components 1 Go to http://webapps.00.00 and Crystal Reports 2008 (Designer component) product.00. Crystal Reports 2008 (Designer component).biar and BMC_PM-BusinessView.2. 2 Follow the instructions for completing the Export Validation & License Terms page. contact BMC Customer Support.Server Component Crystal Reports 2008 .zip file.

You need a user name and password with the BusinessObjects Enterprise 3. BMC Performance Manager Portal and BMC Datastore BMC Performance Manager Portal and database must be configured for continuous data export (CDE). run the following command on the Portal host computer: bpmcli -portal portalWebServerHostName -login superadmin -pass superadmin -c refreshDatafeedMetadata where portalWebServerHostName is the Portal Web Server host computer.00 is installed.Installing the integration components Before you begin The following prerequisites must be met: Table 18 Reporting integration prerequisites Prerequisite BMC Reporting Foundation 3.1 Administrator rights to log on to Business View Manager and Java InfoView.2. see “Continuous data export configuration” on page 190. Note: The BusinessObjects Enterprise XI 3. After Performance Managers have been collecting data for several hours. Product or component Reports Server Chapter 6 Reports 165 . 64-bit middleware connectivity is not supported. BMC recommends that you should install 32-bit database middleware connectivity client to connect to CMS database from a 64-bit machine where BMC Reporting Foundation 3. Therefore. For information about configuring the CDE database instance. and the correct superadmin user name and password are inserted.00 on the same computer.2. you must have 32-bit database client and BMC Reporting Foundation 3.00 and Crystal Reports 2008 (Designer component) host computers. For the reports that you want to generate. You need a Windows Administrator user name and password for the BMC Reporting Foundation 3. You need a user name and password for the CDE database.2. Unless specified. the appropriate Performance Managers listed in Table 19 on page 166 must be installed and collecting data.1 compiled as the 32-bit native binary is designed to use 32-bit data source middleware connectivity.00 must be installed In case of 64-bit operating system.2.

AS Red Hat Linux 4.0 ES.5.Installing the integration components Table 19 Report BMC Performance Manager components required for various reports (part 1 of 2) Performance Managera BMC Performance Manager Express for Unix/Linux Application class or Knowledge Module appropriate application classes for the operating systems in your environment: s s s s s s BMC Performance Manager Availability Report AIX HP-UX Linux Red Hat Linux 3.0 ES.0 ES. AS Red Hat Linux 4.01 PATROL KM for Microsoft Windows Operating System PATROL KM for Unix 166 BMC Performance Manager Portal Monitoring and Management Guide .0 ES.01 BMC Performance Manager Integration with PATROL for UNIX and Linux 9.0 ES. AS Solaris BMC Performance Manager Top N CPU Usage BMC Performance Manager Express for Unix/Linux appropriate application classes for operating systems in your environment: s s s s s s AIX HP-UX Linux Red Hat Linux 3.3. AS Red Hat Linux 4. AS Solaris BMC Performance Manager Express for Windows appropriate application classes for operating systems in your environment: s s s s Windows 2000 Windows 2003 Windows XP Windows BMC Performance Manager Logical Domain Report BMC Performance Manager Zone and Pool Report BMC Performance Manager Express for Unix/Linux appropriate application classes for the operating systems in your environment: s s s s s s AIX HP-UX Linux Red Hat Linux 3.0 ES. AS Solaris BMC Performance Manager Express for Windows appropriate application classes for the operating systems in your environment: s s s s Windows 2000 Windows 2003 Windows XP Windows BMC Performance Manager Integration with PATROL for Microsoft Windows Servers 3.

0 ES. AS Red Hat Linux 4. AS Solaris BMC Performance Manager Top N Process CPU Usage BMC Performance Manager UNIX® Health Report BMC Performance Manager Express for Unix/Linux BMC Performance Manager Express for Windows BMC Performance Manager Express for Unix/Linux Unix Process Windows Process appropriate application classes for the operating systems in your environment: s s s s s s AIX HP-UX Linux Red Hat Linux 3.0 ES.0 ES.0 ES. AS Red Hat Linux 4.Installing the integration components Table 19 Report BMC Performance Manager components required for various reports (part 2 of 2) Performance Managera BMC Performance Manager Express for Unix/Linux Application class or Knowledge Module appropriate application classes for operating systems in your environment: s s s s s s BMC Performance Manager Top N File System Usage Report AIX HP-UX Linux Red Hat Linux 3. AS Solaris BMC Performance Manager Windows Health Report BMC Performance Manager Express for Windows appropriate application classes for operating systems in your environment: s s s s Windows 2000 Windows 2003 Windows XP Windows a You can use Performance Managers or PATROL KMs with PATROL Integration.0 ES. AS Red Hat Linux 4. Chapter 6 Reports 167 . or both.0 ES. AS Solaris BMC Performance Manager Top N File System Space Usage Report BMC Performance Manager Express for Unix/Linux appropriate application classes for operating systems in your environment: s s s s s s AIX HP-UX Linux Red Hat Linux 3.

s s s 1 Choose Start => Programs => BusinessObjects XI 3. if it is not present user name that has the BusinessObjects Enterprise XI 3.biar file NOTE s For BMC Performance Manager for Web Application Servers. import the BMC_for_SAP_Reports. 5 Browse to the BMC_PM_Reports.Installing the integration components To import the BMC_PM_Reports. For BMC Performance Manager for Oracle Fusion. 7 In the Destination environment page.biar file. leave this field blank. and click Next.biar file. specify that password. 168 BMC Performance Manager Portal Monitoring and Management Guide . 8 Click Next. and click Next to begin the import process. 4 Click Browse next to the BIAR file field. Else.1 Administrator privileges. unless your BusinessObjects Enterprise XI 3. import the BMC_VS_CrystalReports. For BMC Performance Manager for SAP. choose Business Intelligence Archive Resource (BIAR) File in the Source list. For BMC Performance Manager for Virtual Servers.biar file.2.biar file. accept the default language.biar file. import the BMC_for_Web_Application_Servers_Reports. import the BMC_for_Oracle_Fusion_Reports. 3 In the Source environment page. 6 Select the file.1 environment is configured to use a different authentication method a If you have set a password for the Administrator while installing BMC Reporting Foundation 3. 2 In the Import Wizard. if it is not present password for the user name Authentication Enterprise.1 => BusinessObjects Enterprise => Import Wizard. enter or confirm the following information: CMS Name User Name Passworda host name of the destination Central Management Server (CMS).00.

17 In the Select application folders and objects page. and then click Next. Chapter 6 Reports 169 . 16 Select the Import all instances of each selected object option. and click Next. confirm that the Import recipients used by selected publication option is selected. 18 In the Import options for universes and connections page. The Import Progress dialog box opens. 11 In the Incremental import page. clear the following check boxes: s s s s s s Import profiles Import encyclopedia objects Restore full cluster server configuration Import node(s) from a different cluster Import custom access levels Import remote connections and replication jobs 10 In the Import scenario page. click Next. click Next. The Preparing for import page displays the following selections: s s 1 Folders selected 10 Objects selected This page might remain open for several minutes. NOTE The Import Progress dialog box should not display any errors or significant warnings encountered during the import process. click Next. 20 Click Finish. click Next. click Next. 12 In the A note on importing server groups page. click Next. The title of the page then changes to Ready to Import. 19 In the Import options for publications page. click Select All.Installing the integration components 9 In the Select objects to import page. 14 In the Categories page. click Next. 15 In the Folders and objects page. 13 In the User and groups page.

unless your BusinessObjects Enterprise XI 3.xml file. specify that password. click Choose XML.xml file NOTE s For BMC Performance Manager for Web Application Servers. 7 Select BMC_PM-BusinessView. 22 When importing is complete.Installing the integration components 21 (optional) Click View Detail Log to view the import process log details. 170 BMC Performance Manager Portal Monitoring and Management Guide . click Done. import and refer to the BMC_for_SAP-BusinessView.1 Administrator privilege. To import the BMC_PM-BusinessView.xml file. enter or confirm the following information: System User Name Passworda Authentication a host name of the Central Management Server (CMS). choose Tools => Import. 6 In the Import dialog box. For BMC Performance Manager for Oracle Fusion. import and refer to the BMC_for_Web_Application_Servers-BusinessView. For BMC Performance Manager for Virtual Servers. s s s 1 Choose Start => Programs => BusinessObjects XI 3. if it is not present password for the user name Enterprise. 23 Log on to Java InfoView as an Administrator and verify that all the reports and their instances are imported. import and refer to the BMC_VS-BusinessView. and then browse to BMC_PM-BusinessView.00. 2 In the Log On to BusinessObjects Enterprise dialog box. leave this field blank. For BMC Performance Manager for SAP. 3 Click OK. 4 In the Welcome to Business View Manager window.xml file.1 environment was configured to use a different authentication method If you have set a password for the Administrator while installing BMC Reporting Foundation 3.xml. import and refer to the BMC_for_Oracle_Fusion-BusinessView.1 => BusinessObjects Enterprise => Business View Manager.xml and click Open. if it is not present user name that has the BusinessObjects Enterprise XI 3. Else.2. 5 In the Business View Manager menu. click Cancel.xml file.

Installing the integration components 8 Select the root level of the hierarchy. 9 Confirm that the Preserve CUID when importing objects option is selected.Prompt Group 2 DROCR_BPMConnection DROCR_BPMElements DROCR_BPMFoundation DROCR_BPMPromptElements DROCR_BPMView To modify the business view to point to the CDE database 1 Choose Start => Programs => BusinessObjects XI 3. 10 Select the Overwrite if CUID exists option. 4 Double-click DROCR_BPMConnection. 3 In the Business View Manager. The root level of the hierarchy has the form CMSserverName [userName]. 11 Click OK. The BMC_PM folder is created in the Repository Explorer pane of the Business View Manager.1 computer where you have imported the .xml files. in the Repository Explorer pane. 2 Log on to the BusinessObjects Enterprise XI 3. 14 (optional) Confirm that the following components are displayed under the BMC_PM folder: s s s s s s s s DROCR_BPMAccountElements DROCR_BPMAccountElements .1 => BusinessObjects Enterprise => Business View Manager. click Yes. 12 In the confirmation dialog box. expand the BMC_PM folder.biar and .xml file is imported and the following message is displayed: Business views have been imported successfully 13 Click OK to close the dialog box. The BMC_PM-BusinessView. Chapter 6 Reports 171 .Prompt Group DROCR_BPMAccountElements .

13 Choose File => Save. Connection test completed successfully message appears.Installing the integration components 5 In the Object Explorer pane. and click OK. If the connection is successful. 10 In the Set Data Connection Password dialog box. choose Tools => Test Connectivity. click OK. enter a string in the form: instanceName (for example BMCCDE) The instance name must exist in the tnsnames. right-click DROCR_BMCConnection. 12 Click OK. mercury:1521/bmccde) If database client and BMC Reporting Foundation 3.00 exist on same computer. 7 In the Oracle Server dialog box. enter the CDE database credentials. expand Oracle Server.2. 172 BMC Performance Manager Portal Monitoring and Management Guide .00 exist on the same computer. and select Edit Connection. Unless you changed them. Note: You must install 32-bit database client on the BMC Reporting Foundation 3. enter the following information: Service If the database server and BMC Reporting Foundation 3. 6 In the Choose a Data Source dialog box. User ID Password OS authentication user name for the CDE database instance password for the user name leave the box unchecked 8 Click Finish. enter a string in the form: serverName:port/cdeDatastoreInstanceName (for example.00 computer if you have CMS database on the other computer.2. you can use the following default credentials: s s user name: CDE password: CDE 11 In the Business View Manager. 9 In the Choose a Data Source dialog box.ora file.2.

and click OK: System User Name Passworda Authentication a host name of the Central Management Server (CMS). enter or confirm the following information. 2 In the Log On to BusinessObjects Enterprise dialog box.1 environment was configured to use a different authentication method If you have set a password for the Administrator while installing BMC Reporting Foundation 3. change the value to CDE. if it is not present password for the user name Enterprise. click Cancel. For example.2. if you are using the default BMC Datastore. expand Tables.ELEMENT. specify that password.1 Administrator privilege. B Edit the Qualified Table Name property. B Edit the Qualified Table Name property. 6 Update the value of the Qualified Table Name property of the ACCOUNT table: A Select the table and navigate to Property Browser under Object Explorer. leave this field blank. 7 Update the value of the Qualified Table Name property of the ELEMENT table: A Select the table and navigate to Property Browser under Object Explorer. Chapter 6 Reports 173 . if you are using the default BMC Datastore. 3 In the Welcome to Business View Manager window.Installing the integration components To change the reports definition 1 Choose Start => Programs => BusinessObjects XI 3. change the value to CDE. For example. C Save the change and accept all subsequent prompts. unless your BusinessObjects Enterprise XI 3.1 => BusinessObjects Enterprise => Business View Manager. if it is not present user name that has the BusinessObjects Enterprise XI 3.ACCOUNT. 5 In Object Explorer.00. Else. The BMC_PM folder appears in the Repository Explorer pane of the Business View Manager. 4 Double-click DROCR_BPMFoundation.

2.2. 8 Restart the Server Intelligence Agent (hostName) service.00 on a new computer and migrating the existing database to the new computer” on page 177. For more information. 4 Double-click DROCR_BPMAccountElements. Upgrading to Crystal Reports 2008 (Designer component) Uninstall Crystal Reports XI Release 2.2.00 in the following ways: s Upgrade from the existing Crystal Reports Server. 3 In the Business View Manager.1 computer where you have installed the . Install BMC Reporting Foundation 3. you must create the .Upgrading to Crystal Reports 2008 (Designer component) C Save the change and accept all subsequent prompts.2. 2 Log on to the BusinessObjects Enterprise XI 3.1 => BusinessObjects Enterprise => Business View Manager. and then install Crystal Reports 2008 (Designer component). Upgrading to BMC Reporting Foundation 3. in the Repository Explorer pane.xml files. expand the BMC_PM folder. For more information.00 You can upgrade to BMC Reporting Foundation 3. 174 BMC Performance Manager Portal Monitoring and Management Guide .biar file.2. s Upgrading from existing Crystal Reports Server Before upgrading to BMC Reporting Foundation 3.00. see “Installing BMC Reporting Foundation 3. To refresh the list of values for Account/Elements selection lists 1 Choose Start => Programs => BusinessObjects XI 3. For information about installing Crystal Reports 2008 (Designer component).biar and .00 on a new server and migrate the existing database to the new server. see SLN000015109081. see “Upgrading from existing Crystal Reports Server”. 5 Click Refresh Status.

Else. specify that password. leave this field blank. choose Business Intelligence Archive Resource (BIAR) File in the Destination list. ensure that the following check boxes are selected: s s s Import folders and objects Import discussions associated with the selected reports Import application folders and objects 11 In the A note on importing universes page. 13 In the Folders and objects page. click Select All. 7 Click Browse next to the BIAR file field. Chapter 6 Reports 175 . 6 In the Destination environment page. choose BusinessObjects Enterprise XI Release 2 in the Source list. 3 In the Source environment page.biar extension. 12 In the A note on importing object rights page. if it is not present password for the user name Authentication Enterprise.biar file 1 Choose Start => Programs => BusinessObjects => Crystal Reports Server => Import Wizard. click Next to begin the creation process. 9 Specify a name for the file with the . 8 Browse to the location where you want to create the new .Upgrading to BMC Reporting Foundation 3. unless your Crystal Reports Server environment is configured to use a different authentication method a If you have set a password for the Administrator. 4 Enter the following information: CMS Name User Name Passworda host name where the Crystal Reports Server component is installed user name that has the Crystal Reports Server Administrator privileges. 2 In the Import Wizard. 10 In the Select objects to import page. and click Next. 5 Click Next.2.00 To create the . click Next.biar file. click Next.

00 from Crystal Reports Server component: 1. The title of the page then changes to Ready to Import.biar file. click Next.1 (BMC Reporting Foundation 3.2.biar file” on page 168. and then click Next. After successfully creating the .xml file” on page 170. Import the BMC_PM-BusinessView.00 14 Select the Import all instances of each selected report and object package option. NOTE The Import Progress should not display any errors or significant warnings encountered during the creation process.Upgrading to BMC Reporting Foundation 3. click Select All. 176 BMC Performance Manager Portal Monitoring and Management Guide . Uninstall the Crystal Reports Server component. and then click Next. The Preparing for import page displays the following selections: s s 2 Folders selected N Objects selected This page might remain open for several minutes.00.2. as described in “To import the BMC_PM_Reports. see SLN000015109080. 20 Log on to Java InfoView as an Administrator and verify that all the reports and their instances are created. 18 (optional) Click View Detail Log to view the process log details. 19 When the . 15 In the Select application folders and objects page. 2. complete the following tasks to upgrade to BMC Reporting Foundation 3. 3. 4. Import the created .2. as described in “To import the BMC_PM-BusinessView.2. Install BMC Reporting Foundation 3.xml file. For more information about installing BusinessObjects Enterprise XI 3.00).biar file is created. 17 Click Finish.biar file. The Import Progress dialog box opens. click Done. 16 In the A note on importing reports page.

leave this field blank. 3 In the Source environment page. see SLN000015109080.00. To migrate the existing database to the new computer 1 Choose Start => Programs => BusinessObjects XI 3.1 => BusinessObjects Enterprise => Import Wizard. specify that password.2. 2 In the Import Wizard. 5 Click Next.00 Installing BMC Reporting Foundation 3.00 is installed user name that has the BMC Reporting Foundation 3. if it is not present password for the user name Enterprise. accept the default language.2. 4 Enter the following information: System User Name Passworda Authentication a host name of the Central Management Server (CMS). if it is not present password for the user name Authentication Enterprise.00 environment is configured to use a different authentication method a If you have set a password for the Administrator while installing BMC Reporting Foundation 3. Chapter 6 Reports 177 . if it is not present user name that has the Crystal Reports Server Administrator privilege.2. choose BusinessObjects Enterprise XI Release 2 in the Source list. Else.2.Upgrading to BMC Reporting Foundation 3.00 Administrator privileges.2. and click Next to begin the import process. specify that password. Else. unless your BMC Reporting Foundation 3. unless your Crystal Reports Server environment was configured to use a different authentication method If you have set a password for the Administrator.2.00 on a new computer and migrating the existing database to the new computer To install BMC Reporting Foundation 3. leave this field blank. enter or confirm the following information: CMS Name User Name Passworda host name of the server where BMC Reporting Foundation 3.2. 6 In the Destination environment page.00.

178 BMC Performance Manager Portal Monitoring and Management Guide . 13 In the Incremental import page. then click Next. select Import recipients used by selected publications. The Import Progress dialog box opens. click Next.2. click Select All.00 7 Click Next. 14 In the A note on importing object rights page. click Select All. 15 In the Folders and objects page. 20 Click Finish. 12 Click Next. 11 Select the Automatically rename objects if an object with that title exists in the destination folder option. and click Next. 8 In the Select objects to import page. The title of the page then changes to Ready to Import. The Preparing for import page displays the following selections: s s N Folders selected N Objects selected This page might remain open for several minutes. click Next. 10 In the Import scenario page. select the I want to update the destination system by using the source system as a reference option. click Next. ensure that the following check boxes are selected: s s s Import folders and objects Import discussions associated with the selected reports Import application folders and objects 9 In the A note on importing universes page. 19 In the A note on importing reports page. click Next.Upgrading to BMC Reporting Foundation 3. and then click Next. 18 In the Import options for publications page. 17 In the Select application folders and objects page. 16 Select the Import all instances of each selected object option.

3 Enter the password for the Administrator. Before you begin s You must have the BMC Reporting Foundation 3.00 installed and configured. 23 Import the BMC_PM-BusinessView. 22 When importing is complete. you can schedule it. you must have the Java InfoView component of BMC Reporting Foundation 3.xml file” on page 170. you must save the report as the .Publishing and scheduling generated reports NOTE The Import Progress should not display any errors or significant warnings encountered during the import process.1 => BusinessObjects Enterprise => BusinessObjects Enterprise Java InfoView.xml file. You can publish the report by using Java InfoView.rpt file. After publishing the report. After generating a report.2. click Done. Chapter 6 Reports 179 .2.1 Java InfoView component. 24 Log on to Java InfoView as an Administrator and verify that all the reports and their instances are imported. You need a user name and password to log on to BusinessObjects Enterprise XI 3. For more information. 2 In the Log On to InfoView window. To use the BusinessObjects InfoView report portal. see “To import the BMC_PM-BusinessView. if not provided by default.00 installed. Publishing and scheduling generated reports You can generate a report by using Crystal Reports 2008 (Designer component) that can be scheduled to run immediately or periodically. 21 (optional) Click View Detail Log to view the import process log details. enter Administrator as the user name. s s To publish a report by using BusinessObjects Enterprise Java InfoView 1 Choose Start => Programs => BusinessObjects XI 3.

click Browse next to the Filename field. 2 In the Log On to InfoView window. 180 BMC Performance Manager Portal Monitoring and Management Guide . NOTE If you have set a password for the Administrator while installing BusinessObjects Enterprise XI 3. 9 Browse to the .rpt file created by using Crystal Reports 2008 (Designer component). To schedule a report by using BusinessObjects Enterprise Java InfoView 1 Choose Start => Programs => BusinessObjects XI 3. 13 Enter description or key words for the report.Publishing and scheduling generated reports NOTE If you have set a password for the Administrator while installing BusinessObjects Enterprise XI 3. 4 Click Log On. and then select Crystal Reports.1. 3 Enter the password for the Administrator. 6 Navigate to Public Folders => BMC_PM. 10 Select Use description from report and Keep saved data. 11 Click General Properties. 12 Enter title for the report that you want to display in Java InfoView.1 => BusinessObjects Enterprise => BusinessObjects Enterprise Java InfoView. 8 On the Crystal Reports page.1. enter Administrator as the user name. 7 Click Add. 14 Click OK. 5 Click the Document List tab. specify that password. specify that password. 4 Click Log On. if not provided by default. Report gets added to Java InfoView.

Specify which Central Management Server to use. or other formats such as Adobe Portable Document Format (. choose one of the following options to schedule the report: s s s Now: run the report immediately. see Table 21 on page 185. Once: run the report once. 9 Click Recurrence under Schedule. and then select Schedule. If you do not choose an option. do not change the Filters settings. For a list of reports installed with BMC Portal and their input properties. file. 13 (optional) Under Parameters. and SQL. at a scheduled date and time.1 online Help. Specify settings for printing the report. Specify events to wait for and events to trigger upon completion. Choose the report format: default Crystal Reports format (. Modifying these settings requires expert knowledge of Crystal Reports. 12 (optional) Configure the following report settings: Destination Format Print Settings Scheduling Server Group Events Specify the recipients of the report (inbox. 10 In the Run object list. see the BusinessObjects Enterprise XI 3.Publishing and scheduling generated reports 5 Click the Document List tab. from a time in the past until the present. Daily. enter the schedule properties. the default will be used. specify values for the parameters that are required to schedule the report: Chapter 6 Reports 181 . 11 To run the report periodically. For information about these options.rpt). 8 Click Actions. WARNING s s To use a standard report template. the BMC Portal CDE database schema. Hourly. and so on).pdf). 6 Navigate to Public Folders => BMC_PM. and so on: run the report periodically at a scheduled date and time. 7 Select the report title that you want to schedule.

If you choose an option other than Custom Date Range. No starting date means that the report will contain all available data before the end date. Time Range Type 182 BMC Performance Manager Portal Monitoring and Management Guide .Publishing and scheduling generated reports A Click Edit or the parameter value hyperlink to change the value. you can choose from database information. NOTE Some parameters have default values. click OK. In some cases. The report is for a defined portion of each day in the reporting period (for example.M. No ending date means that the report will contain all available data from the starting date to the present. The report is for a continuous period from the starting date and time to the ending date and time. Time Range the starting and ending times of the report These times are interpreted in conjunction with the Time Range Type parameter. and so forth Starting time for start day. to 5 P. the value for Date Range is ignored. B After entering a selection. ending time for end day Starting/Ending time for everyday Date Range the starting and ending dates of the report Comments If you choose the Custom Date Range option. The Include this value option has no effect on the data that is reported.M. Table 20 provides information about the parameters: Table 20 Report schedule parameters (part 1 of 2) Parameter Name Date Range Type Parameter value a range such as number of days.). 8 A. values are required for Date Range. number of weeks.

Monday and Friday).rpt) allows you to navigate to details by clicking elements in the report. AccountElements ELEMENT_NAME. which is suitable for printing. and each account may have access to different elements. 14 Click Schedule. The page displays the scheduled instance and indicates whether the status is Running or Pending. Multiple accounts may be available. Normally this parameter is used to set the work week. AccountElements ACCOUNT_NAME the elements that will be included in the report Changing this parameter will change the information that is displayed in the report. The report instance gets generated at the specified time and date.Publishing and scheduling generated reports Table 20 Report schedule parameters (part 2 of 2) Parameter Name Day of Week Parameter value a set of days of the week Comments You can select any set of days. WARNING This step fails if no data is in the database. Figure 23 on page 184 shows a sample PDF report. or if the connection to the database fails. The native Crystal Reports format (. Chapter 6 Reports 183 . contiguous or non-contiguous (for example.

and worst transaction response times.Report types and details Figure 23 Example of a typical report Report types and details Several types of reports are provided. to show overall health. 184 BMC Performance Manager Portal Monitoring and Management Guide . and so on. best.

/usr) s average value s maximum value s minimum value a bar chart that shows the percent average process CPU usage for each monitored element for each monitored element s s s s s BMC Performance Manager Top N Process CPU Usage Report Top ‘N’ Process CPU Utilization element name process name average value maximum value minimum value Chapter 6 Reports 185 . for each s element name monitored element: s host name s number of alarms during the report period s CPU Utilization s Memory Utilization s Paging s Swap s Disk I/O a bar chart that shows the percent average CPU usage for each monitored element for each monitored element: s s s s Report name BMC Performance Manager Availability Report BMC Performance Manager Top N CPU Usage Report Top ‘N’ % Avg CPU Usage element name percent average CPU usage percent maximum CPU usage percent minimum CPU usage Top ‘N’ % BMC Performance Manager Top N File Used File System System Usage Report a bar chart that shows the percent average file system in use for each monitored element for each monitored element s s s s s element name file system (for example. /usr) average value maximum value minimum value BMC Performance Manager Top N File System Space Usage Report Top ‘N’ File System Available Space a bar chart that shows the amount for each monitored element of free space in megabytes for each monitored element s element name s file system (for example.Report types and details Table 21 contains details of the BMC Performance Manager reports that you can select: Table 21 BMC Performance Manager report details (part 1 of 3) Chart title Elements Availability Chart description Table description a bar chart that shows the number for each monitored element: of parameter threshold breaches in the following parameters.

or Alarm state for the following parameters: s s s s s s for each monitored parameter and element: s s s s Available Memory Current Queue Length Disk Time Pagefile Fault Rate Paging File Usage Total CPU Usage element name average value maximum value minimum value BMC Performance Manager Zone and Pool Report Solaris Container Report: Pools and Zones graph that shows the average value for each parameter: of following parameters in 'Stacked Bar Chart' format: s element name s host name s Zone CPU Utilization (%) s average value s Zone Memory Utilization (%) s Zone CPU Shares (Count) s Zone Swap Space Used (MB) s Pool CPU Utilization (%) s Pool CPU Idle Time (%) s Pool CPU IO Wait (%) s Pool Used (%) graph that shows the average value for each parameter: of following parameters in 'Stacked Bar Chart’ format: s element name s host name s Logical Domain CPU s average value Utilization (%) s Logical Domain Memory Allocated (GB) s Logical Domain Status (Status) s Logical Domain Virtual CPU Count (Count) BMC Performance Manager Logical Domain Report Logical Domain Report 186 BMC Performance Manager Portal Monitoring and Management Guide .Report types and details Table 21 BMC Performance Manager report details (part 2 of 3) Chart title Health Summary Chart description pie charts that show whether monitored elements in the OK. Warning. Warning. or Alarm state for the following parameters: s s s s s s s Report name BMC Performance Manager UNIX Health Report Table description for each monitored parameter and element: s s s s CPU Usage Disk I/O Requests in Queue Memory Free Network Errors Page Fault Rate Swap Space Percent Available Transfer Request Workload element name average value maximum value minimum value BMC Performance Manager Windows Health Report Health Summary pie charts that show whether monitored elements in the OK.

half red all green s s If no data is available for a parameter. A blank cell indicates that no parameters are in the state listed in the column heading. Uninstalling the integration components Uninstalling the integration components is a manual operation that is performed on the Report Server host computer. Parameter states OK + + + + + Warning + + + Alarm Pie chart color all yellow all red half yellow. no data appears in the table in the report. no pie chart appears for that parameter. The task comprises the following procedures: s s “To remove folders” on page 188 “To remove the business view” on page 188 Chapter 6 Reports 187 . If a parameter has never had a state change.Uninstalling the integration components Table 21 BMC Performance Manager report details (part 3 of 3) Chart title System Availability Report Chart description table that provides the percentage of system availability for each selected element Table description for each monitored element: s s s Report name BMC Performance Manager System Availability Report element name date system availability status The following rules apply to health reports: s The following table describes how pie chart color is determined. A plus sign (+) in a cell indicates that one or more parameters are in the state listed in the column heading.

7 Select the BMC_PM folder. 2 In the Log On to InfoView window. leave this field blank.1 environment was configured to use a different authentication method If you have set a password for the Administrator while installing BMC Reporting Foundation 3.Uninstalling the integration components To remove folders 1 Choose Start => Programs => BusinessObjects XI 3. 188 BMC Performance Manager Portal Monitoring and Management Guide . click OK. NOTE If you have set a password for the Administrator while installing BusinessObjects Enterprise XI 3. enter Administrator as the user name.1 => BusinessObjects Enterprise => BusinessObjects Enterprise Java InfoView. 6 Navigate to Public Folders => BMC_PM. 2 In the Log On to BusinessObjects Enterprise dialog box.1 Administrator privilege. To remove the business view 1 Choose Start => Programs => BusinessObjects XI 3.1. 4 Click Log On. if it is not present user name that has the BusinessObjects Enterprise XI 3. unless your BusinessObjects Enterprise XI 3. 3 Enter the password for the Administrator. specify that password. 9 In the confirmation dialog box. Else. The folder is removed.1 => BusinessObjects Enterprise => Business View Manager. if not provided by default. if it is not present password for the user name Enterprise.2. 5 Click the Document List tab.00. specify that password. enter or confirm the following information: System User Name Passworda Authentication a host name of the Central Management Server (CMS). 8 Click Organize and select Delete.

Chapter 6 Reports 189 . click Cancel. 6 In the confirmation dialog box. The business view is removed. and then click Delete. click Yes. select the BMC_PM folder. 5 In the Repository Explorer. 4 In the Welcome to Business View Manager window.Uninstalling the integration components 3 Click OK.

see “exportParameterHistory” on page 272. and whenever a parameter threshold is breached. To start a process that exports summarized data to the target database. but each target CDE database or file impacts the performance of the Portal. known as the report update interval. as illustrated in Figure 24. or a combination of test files and CDE databases. You can use the exported data to create reports in a reporting program such as Crystal Reports 2008 (Designer component). You can configure multiple targets. After you customize the configuration files. You can also backfill the CDE database with historical (summarized) parameter data. s Figure 24 Continuous data export process application server Portal database external CDE database browser web server RSM monitored elements 190 BMC Performance Manager Portal Monitoring and Management Guide . NOTE s The datafeed utility supports CDE databases on Oracle Database 10g Enterprise Edition with the Partitioning option. the Portal datafeed utility exports raw parameter data at the frequency at which it receives data from the RSM. You can optionally configure the Portal datafeed utility to save this raw parameter data to external Oracle databases (CDE databases).Continuous data export configuration Continuous data export configuration The RSM sends parameter data to the Portal at regularly scheduled intervals. CSV (test) files.

PASSWORD= datafeed_password. DB.Continuous data export requirements Continuous data export requirements Configuring the datafeed utility to export data to a test file or Oracle CDE database requires that you use the following files and datastore CLI options: s datafeed. the old data in the CDE database might not appear in BMC Reporting Foundation 3. unless you perform the following actions: s While running the createDatafeedSchema datastore CLI option.TABLEOWNER. DB. For more information about this bpmcli command.USERNAME= datafeed_user. run this option by using the datastore CLI to add the required data structures to the target database. run the refreshDatafeedMetadata command. which are purged according to the retention time provided by the user when prompted by this datastore CLI option.) s You can ignore the ORA-00955 and ORA-02275 error messages if they appear while you are running datastore CLI with the createDatafeedSchema option.properties file. indexes. and procedures used to create and purge partitions.properties: This template property file is used to create a property file for each target database. Parameter data is saved in 30-minute partitions. Inside the sampleDatafeedTarget. see page 264.USERNAME. Chapter 6 Reports 191 . The data structures include tables. and DB. you must first create the necessary database structures in the target database. the values for DB. if you were using CDE. and views to facilitate querying. the summary data tablename needed for the historical data export. To properly configure the target CDE database.2.TABLEOWNER= datafeed_user. DB. To ensure that you can successfully query all of the parameter data stored in your CDE database. The property file contains the tablename for the continuous data export. use the same user name and password for the CDE database that was used in the earlier BMC Portal version.PASSWORD should be the same as the values used while running the createDatafeedSchema option (for example. s createDatafeedSchema: When exporting data to a CDE database. DB. The property file also contains some configuration properties for the target database. and metadata tablenames that are used for querying the two export utilities.00. s sampleDatafeedTarget. NOTE When you are upgrading from an earlier version of BMC Portal. s datafeedJob: This datastore CLI option creates a job in the target CDE database that provides a data-retention policy for the continuous data export data.properties: This file contains settings for the test CSV file and the directory name that contains the property files that describe the target CDE database.

You should specify a CSV file for testing purposes only. Table 22 on page 202 contains optional configuration properties that you can set.properties template file. or both by modifying the properties in the datafeed. as described in the following procedure. use the procedure in “Changing the retention policy for the CDE database” on page 201. 3. CSV file. use the procedure in “Configuring the target datafeed clients” on page 192.properties file. For environments with clustered application servers. To add the necessary tables to a CDE database. Configuring the target datafeed clients You configure the datafeed utility to export parameter data to a CDE database.properties file to scan a directory for export property files and enable the datafeed utility. Also.properties file at one of the following locations on the Portal application server: — On Windows: %BMC_PORTAL_KIT_HOME%\appserver\websdk\tools\jboss\server\all\conf\ properties\drmop — On Solaris: $BMC_PORTAL_KIT_HOME/appserver/websdk/tools/jboss/server/all/conf/ properties/drmop 192 BMC Performance Manager Portal Monitoring and Management Guide . To specify the target CDE databases and to control which parameters are exported by the datafeed utility. To establish a data retention policy for the CDE database. use the procedure in “Specifying the target CDE databases” on page 199 to configure the property files based on the sampleDatafeedTarget. To update the attributes in the datafeed.Configuring the datafeed utility Configuring the datafeed utility To configure the datafeed utility and target clients. 2. repeat these procedures for each application server in the cluster. 1. perform the following procedures in the order shown. 4. use the procedure in “Configuring a target CDE database” on page 195 to configure the target database and execute the createDatafeedSchema option by using the datastore CLI. To configure the target datafeed clients 1 Locate the datafeed.

datafeed.timetolive.timetoidle.timetoidle.clients=com.rsmcommunication.patrol.impl.000 unique applications. uncomment the property setting that corresponds to your Portal size. s portal. Figure 25 Data target lines in the datafeed.portal%3Aname%3DDataFeedAppPathCache.\ #com.rsmcommunication. To export data to a test CSV file only.portal.clients=com.bmc. #portal.seconds=3600 To determine whether you need to modify the cache properties. Figure 26 Datafeed cache properties in the datafeed.seconds=86400 indicates that the cache will hold items that are actively reused from the cache up to a day before flushing them and causing the system to recalculate the ApplicationPath.patrol. as shown in Figure 26.patrol.JdbcDataFeedClient.datafeed.JdbcDataFeedClient # CSV -. To export data to a test CSV file and an Oracle database.datafeed.JdbcDataFeedClient. The following properties control the size of the cache and when items are removed from the cache: s portal.configDir property below.apppathcache.apppathcache.CsvDataFeedClient 3 To modify the cache properties for the datafeed utility. enable the data clients for the parameter data by uncommenting the lines that correspond to your client preference: s s s To export data to an Oracle database only. Chapter 6 Reports 193 .rsmcommunication.impl.seconds=3600 indicates that the cache can hold unused items for up to an hour. uncomment the second highlighted line.impl.datafeed.bmc. # Uncomment the following line to feed data to a CSV file #portal.portal. s portal.size=15000 #portal.apppathcache.datafeed.properties file # JDBC # Uncomment the following line to feed data to JDBC target(s) and be sure # to set the portal.patrol.apppathcache.seconds=86400 #portal.portal.bmc.clients=com.datafeed.Configuring the datafeed utility 2 Using Figure 25 as a guide.apppathcache.apppathcache. #portal. you can monitor the MemoryStoreHitCount and MissCountNotFound properties on the JMX console at http://PortalHostName/jmx-console/HtmlAdaptor?action=inspectMBean&name= com.datafeed.bmc. uncomment the first highlighted line.impl.datafeed.bmc.timetolive.datafeed.Client to use for testing purposes only.configDir property below. uncomment the third and fourth highlighted lines.datafeed.size=15000 indicates that the cache can hold the ApplicationPath for 15.portal.datafeed.properties file # Datafeed cache properties # Below values are the defaults if not set #portal.datafeed.rsmcommunication.datafeed.JdbcDataFeedClient.CsvDataFeedClient # # BOTH # Uncomment the following two lines to feed data to both a CSV file and JDBC target(s) # and be sure to set the portal.patrol.

Configuring the datafeed utility 4 When exporting parameter data to an Oracle database.properties file #------------------------------------------------------------------------------#JDBC PROPERTY -. #Each property file found configures a separate JDBC target db with its own #column mapping. see “Configuring a target CDE database” on page 195.JdbcDataFeedClient. uncomment the portal.configDir setting to specify the directory where you will place the properties file for the target database. The directory that you specify cannot contain any property files other than the CDE properties file. #------------------------------------------------------------------------------#The datafeed utility will scan the following directory for property files.CsvDataFeedClient. #portal.filenameRoot property and substitute /directoryPath/csvDatafeedFileName for the path and prefix to use for the file names for your CSV files. specify the path and file name. use the portal. as shown in Figure 27. s s s To create the properties file for the target database.CsvDataFeedClient.configDir=c:/datafeed 5 To specify the properties for the test CSV file client. B To insert a header line in the CSV files.Must be set to enable JdbcDataFeedClient. all CSV files contain a header line. use the default setting (true) for the portal. and timestamp format properties. A Under PATH AND FILENAME.printHeader property. as shown in Figure 28.JdbcDataFeedClient. #Please note while specifying configDir use forward (/) slash as directory #separator for both Unix and Windows. 194 BMC Performance Manager Portal Monitoring and Management Guide . By default. new header line. under CSV PROPERTIES. Figure 27 Oracle properties in the datafeed. NOTE Use the forward slash (/) as the directory separator on both Windows and UNIX. The directory that you specify must exist and contain the CDE properties file before you restart the Portal application server.

CsvDataFeedClient. To view valid values for the timestamp format. restart the Portal application server.com/j2se/1.Please use forward slash (/) as directory separator for # both Windows and UNIX.html.Platform.. see the following website: http://java.CsvDataFeedClient. portal. e.Hostname.properties file.g.printHeader=true # # # # # # # TIMESTAMP FORMAT Uncomment the following line to specify a timestamp format in the CSV file. uncomment the portal. See the below URL for valid values: http://java.sun.0/docs/api/java/text/SimpleDateFormat.CsvDataFeedClient.Configuring the datafeed utility C To change the timestamp format. # Example header line: Timestamp. # # To specify a custom location for the file.0/docs/api/java/text/SimpleDateFormat.Solution Name. Chapter 6 Reports 195 .: "Fri Aug 25 14:35:01:703 GMT 2006" portal.dateFormat=EEE MMM dd HH:mm:ss:SSS z yyyy 6 If you are exporting data to a test CSV client only. Figure 28 CSV properties in the datafeed. Figure 29 contains a view of the database structure.sun. D Save the datafeed. to create the required database structures in the target CDE database. Also.CsvDataFeedClient. The default timestamp format produces a timestamp similar to Wed Jul 12 20:45:44 GMT 2006..5.html The default of EEE MMM dd HH:mm:ss:SSS z yyyy produces. otherwise.filenameRoot=c:/dir/csvdatafeedfilename # HEADER LINE # This property determines whether a header line is placed in the output files.5.com/j2se/1.Element. # portal.csv. proceed to “Specifying the target CDE databases” on page 199 Configuring a target CDE database This section describes how to update and run the createDatafeedSchema option by using the datastore CLI. uncomment the line below and # specify the destination.dateFormat property and change the default value (EEE MMM dd HH : mm : ss : SSS z yyyy).properties file #------------------------------------------------------------------------------# CSV PROPERTIES #------------------------------------------------------------------------------# PATH AND FILENAME # The default location for the csv output file # is <portalinstalldir>/appserver/websdk/bin/csvdatafeed_20060704. Table 22 on page 202 contains optional configuration properties that you can set.

Configuring the datafeed utility Figure 29 CDE database structures metadata tables summarized parameter data (Historical Data Export utility) raw parameter data (Continuous Data Export utility) 196 BMC Performance Manager Portal Monitoring and Management Guide .

. see the BMC Portal Installation Guide.Configuring the datafeed utility Before you begin You must have an existing target Oracle CDE instance. Chapter 6 Reports 197 . you can rerun the BMC Datastore installation program to create an instance for the target CDE database. If you have a licensed copy of Oracle Database 10g Enterprise Edition. s To configure a target database 1 Ensure that you have configured the BMC Datastore CLI. and correct the default tablespace if it is wrong: DatastoreCliBMCCDE. use it to create an instance for the target database... TABLESPACE_NAME -----------------------------ARSYSTEM ARTMPSP DATA01 DATA02 .... TABLESPACE_NAME -----------------------------DATAFEED Current CDE users and its default tablespaces are .sh sys "sys as sysdba" set_default_tablespace A sample output file is displayed as follows: List of all the available tablespaces are .bat sys "sys as sysdba" set_default_tablespace DatastoreCliBMCCDE. See the BMC Portal Installation Guide for information about creating the continuous database export (CDE) database instance.. For configuring the BMC Datastore CLI.. USERNAME||''||DEFAULT_TABLESPACE ---------------------------------------------------------CDE DATAFEED Please correct the default tablespace if it is wrong.. You can use one of the following methods to define the target instance: s If you use the BMC Datastore for the Portal. Default tablespace should be one of following. 2 Execute the following Datastore CLI command.

Even if two duplicate users are created. navigate to the command prompt in the %DATASTORE_HOME%\utility directory and enter: DatastoreCliBMCCDE cde_username cde_password datafeedJob 198 BMC Performance Manager Portal Monitoring and Management Guide . This allows the schema to be upgraded for the correct user name and tablespace. you can use ORACLE_BASE as an equivalent to DATASTORE_HOME if all of the following conditions exist: s s You have created a utility folder under ORACLE_BASE You have copied the BPM_Datastore_Utility folder under ORACLE_BASE\utility 3 Navigate to the command prompt in the /data1/BMCSoftware/Datastore/utility/BPM_Datastore_Utility directory: DatastoreCliBMCCDE cde_username cde_password createDatafeedSchema NOTE Ignore the ORA-00955 and ORA-02275 messages. 4 At the prompt. enter the number of days for which you want to retain granular data and the hourly-summarized data. the CDE schema creation validates the correct user and enables you to select the correct CDE user name and password that you used while configuring the JDBC Datafeed properties file.Configuring the datafeed utility CDE Username: cde Default CDE Tablespace: datafeed old 1: alter user &CDE_USER default tablespace &CDE_DEFAULT_TABLESPACE new 1: alter user cde default tablespace datafeed User altered. 5 If you want to change the period for retaining granular and hourly-summarized data. NOTE If you have your own Oracle license. This enables you to create Oracle jobs to purge old partitions from the PARAMETER_DETAIL and PARAMETER_SUMMARY tables and to create new partitions.

TABLE. If you create multiple properties files from the sampleDatafeedTarget. the utility encrypts the password and saves the file. This template file contains the Oracle properties for the target CDE database. and type the new password. delete the encrypted value.URL=jdbc:oracle:thin:@datafeedhost:1521:FEEDDB 3 Modify the values for DB. DB.URL property. #Provide information for the credentials to be used to connect to the database. It also lists the properties that control which parameters that the datafeed utility will export to the CDE database.USERNAME=cde DB.TABLE. This template is on the Portal application server at one of the following locations: s s On Windows: %BMC_PORTAL_KIT_HOME%\appserver\util\BPM_Datafeed On Solaris: $BMC_PORTAL_KIT_HOME/appserver/util/BPM_Datafeed 2 To specify a valid URL for the CDE database. # jdbc:oracle:thin:@hostname:port:ORACLE_SID DB. and DB. including data filters and the failover file location (in the event of a write failure to the database. open the file.TABLE.PASSWORD.OWNER=cde Every time the datafeed utility reads this file. but the file must have .properties file. you can find the file at this location). updating the following highlighted line with the target CDE database information: # Provide valid JDBC URL to database data is to be written to.USERNAME. The values of DB. If you need to change the password. ensure that the files do not specify the same target Oracle database.properties file to the directory that you specified in step 4 on page 194. it verifies whether the password is encrypted.properties file.PASSWORD=cde DB. Chapter 6 Reports 199 . modify the DB. If it appears as plain text. you create and configure a copy of this file for each database. To specify the target CDE database 1 Copy the sampleDatafeedTarget.OWNER and DB.USERNAME should be the same. To specify multiple CDE databases.OWNER. You can assign any name to the new file.Configuring the datafeed utility Specifying the target CDE databases The following procedure describes how to modify the properties in the sampleDatafeedTarget. DB.properties as the file extension.

the datafeed utility exports all parameter records. ApplicationPath. Use the exported data in the file to identify the internal ParameterDefinitionName values on which to filter data for the target database. s The datafeed utility interprets regular expression patterns as filters. When you specify filters for all four attributes. 6 Repeat step 1 on page 199 through step 5 for each target database.ApplicationPath properties. 7 Restart the BMC Portal application server. After you obtain the ParameterDefinitionName values that you need.ProviderName. See “To specify the target CDE database” on page 199. s s s The sampleDatafeedTarget. and ParameterDefinitionName are the only data attributes with which you can filter data. The datafeed utility begins sending parameter data at the next report update interval time. reconfigure the datafeed. The filtering affects target CDE databases and failover files. The filtering does not apply to the CSV test files.properties to export data to a test CSV file. and INCLUSIVE_REGEX. The ParameterDefinitionName is the internal name for the parameter and is not accessible from the user interface. If you do not apply a filter to any of the parameter attributes. the parameter record is ignored. If any one of the data attributes is not defined.Configuring the datafeed utility 4 To filter the data exported by the datafeed utility to a CDE database. which are created when the utility cannot connect to the target CDE database. configure the datafeed.properties file contains sample regex patterns that you can use to filter data. s ProviderName. then the parameter record passes that particular filter. 200 BMC Performance Manager Portal Monitoring and Management Guide . a parameter record must match all four filters to be exported. INCLUSIVE_REGEX. To obtain internal names.ParameterDefinitionName. otherwise.AccountName. INCLUSIVE_REGEX. AccountName.properties to export data to the target database. 5 Save this file. provide a regular expression for the INCLUSIVE_REGEX.

perform the steps in the following procedure. The frequency at which you need to update these tables depends on how often. TIP To ensure that you capture all changes. Chapter 6 Reports 201 . which sets the retention policy for the applicable CDE database. To change a retention policy for the target database 1 Ensure that you have performed the steps in “To configure a target database” on page 197. type the number of days of data to retain. 2 Navigate to the command prompt in the /data1/BMCSoftware/Datastore/utility/BPM_Datastore_Utility directory: DatastoreCliBMCCDE cde_username cde_password datafeedJob 3 At the prompt. and press Enter. s s s s s s you add new accounts you add new elements to an account you update application definitions by upgrading solution Performance Managers you update application definitions by modifying custom Performance Managers you add application classes to or remove application classes from an element the Portal discovers new application instances on an element To ensure that the metadata tables accurately reflect the objects in your account. Maintaining the continuous export to the CDE database The metadata tables in the CDE database do not automatically update as you add elements to the account or change element configuration. described on page 264. To change the retention period for the CDE database. The target CDE database stores the exported parameter data in 30-minute partitions and deletes partitions when their age exceeds the number of days specified in the retention policy. run the refreshDatafeedMetadata command. run a nightly script that executes the refreshDatafeedMetadata command.Changing the retention policy for the CDE database Changing the retention policy for the CDE database When you run the datafeedJob datastore CLI option. it prompts you for the number of days to retain data.

datafeed.maximumsize defines the maximum file size for the CSV file in megabytes (MB) Valid values: s s Additional configuration options for the datafeed utility (part 1 of 5) Description 0 (default value) defines the file size as unlimited a positive whole number that defines the maximum file size in megabytes (MB) (you cannot use a fraction) By default this property is commented. the creation date is updated.parameter.queued.csv When you uncomment this property.csvfile.datafeed.queued. the csv file name includes the name of the csv file. you can use the properties listed in Table 22 to configure the target database. The default and recommended value is 3 million (3000000). in the following format: csvfilename_yyyyMMdd.datafeed.limit overrides the default number of parameters in the queue to send from the Portal to the CDE database or test file When the total number of queued parameters exceeds the value set by this attribute.csvfile. and the time is appended to the default file name in the following format: csvfilename_yyyyMMdd_HHmmss.csv Example: portal.Additional configuration options Additional configuration options If necessary. which can happen if the datafeed client cannot keep up with the volume of data being sent by the Portal.datafeed.parameter.limit=3000000 202 BMC Performance Manager Portal Monitoring and Management Guide .maximumsize=200 portal. This attribute enables you to prevent the Portal from running out of memory. the queue discards all additional parameter values for as long as the value is exceeded. Example: portal. Table 22 Property datafeed. and the date the file was created. By default.properties file portal.

Additional configuration options Table 22 Property Additional configuration options for the datafeed utility (part 2 of 5) Description modifies the thread pool size The time required for the datafeed utility to process the data for a single data point can exceed the time required for the Portal to write a single data point to the Portal database.bmc. Datafeed thread pool size controls how many threads are available to the datafeed utility to save data to the datafeed database.enabled=false portal.externalCDE. you can monitor the QueuedTaskCount property on the JMX console at http://PortalHostName:9378/jmxconsole/HtmlAdaptor?action=inspectMBean&name= com. ensure that you have set portal. To enable the datafeed utility to keep up with the Portal’s database.datafeed.size=10 portal.externalCDE. consider increasing this setting.datafeed.patrol.enabled=true Valid values: s s 4 (default and recommended value) 0 to 23 Example: portal.datafeed.threadpool.externalCDE. Example: portal.size portal.portal%3Aname%3DDataFeed.threadpool. schedulehours determines the time (in 24-hour format) at which the external CDE movement is scheduled (time of the database server) To use this property.datafeed.datafeed.externalCDE. the datafeed utility is multi-threaded.schedulehours=4 Chapter 6 Reports 203 .externalCDE.enabled determines whether the external movement of granular data from BMC Portal database to the external database is enabled This data is moved by using the database task instead of the BMC Portal application server.datafeed. To determine whether you need to modify the thread count property. Valid values: s s false (default value) true (recommended) Example: portal.datafeed. On large Portals where the datafeed utility must process data from a large number of RSMs.

parameter. portal. schedulehours determines the time (in 24-hour format) at which the external HDE movement is scheduled (time of the database server) To use this property.externalCDE.datafeed. refreshhours 24 (default and recommended value) 1 to 24 Example: portal.schedulehours=3 Note: If you have configured external summarization. see portal.enabled=true Valid values: s s 3 (default and recommended value) 0 to 23 Example: portal.history.parameter.externalHDE. ensure that the time that you specify is one hour ahead of the time when the external summarization takes place. Valid values: s s false (default value) true (recommended) Example: portal. For more information.externalHDE.externalHDE.schedulehours.externalsummarization.datafeed.externalsummarization.datafeed. ensure that you have set portal.datafeed.enabled=false portal.externalHDE.externalHDE.Additional configuration options Table 22 Property Additional configuration options for the datafeed utility (part 3 of 5) Description determines the duration for exporting the granular data to the external database Valid values: s s portal.history.datafeed.externalCDE.datafeed. 204 BMC Performance Manager Portal Monitoring and Management Guide .enabled determines whether the external movement of hourly summarized data from BMC Portal database to the external database is enabled This data is moved by using the database task instead of the BMC Portal application server.refreshhours=24 Note: You should not modify this property unless recommended otherwise by BMC Customer Support.enabled and portal.datafeed.

you might want to increase the value for this property.portal%3Aname%3DDataFeed. For large Portals that process data from several RSMs.refreshhours=24 Note: You should not modify this property unless recommended otherwise by BMC Customer Support.bmc. you can monitor the QueuedTaskCount property on the JMX console.POOLSIZE controls the size of each connection pool created for each CDE database This property controls the number of threads available to process the datafeed data and save it to the CDE database. Sample value: DB.BATCHSIZE changes the size of the batched inserts to be sent to the database s Providing values significantly larger than 1.000 causes more communication between the Portal and the CDE database.Additional configuration options Table 22 Property Additional configuration options for the datafeed utility (part 4 of 5) Description determines the duration for exporting the hourly data to the external database Valid values: s s portal.datafeed. Providing values significantly smaller than 1. To help determine how well the datafeed utility is keeping up with the Portal.POOLSIZE=10 Chapter 6 Reports 205 . refreshhours 24 (default and recommended value) 1 to 24 Example: portal.properties DB.BATCHSIZE=1000 DB.externalHDE.patrol.datafeed.externalHDE. sampleDatafeedTarget. which you can find at http://PortalHostName:9378/jmx-console/ HtmlAdaptor?action=inspectMBean&name= com.000 causes the process to consume more memory on the Portal. s Sample value: DB. causing the Portal to become less efficient in communicating the data to the CDE database.

see the following website for valid locale values: http://java. BMCCDE stands for the BMC Continuous Data Export database server instance.csv). CDEDBPassword stands for the Continuous Data Export database user password.5. and you are using Continuous Data Export (CDE) or History Data Export (HDE) for your business reports. 206 BMC Performance Manager Portal Monitoring and Management Guide . If necessary.CSVFILE.sun. the product provides you an alternate option to transfer the data from the BMC Performance Manager Portal datastore database to the CDE datastore database. the following abbreviations and variables are used: s s s s s s BMCPDS stands for the BMC Performance Manager Portal database server instance. Configuring the external CDE movement During the CDE movement.ROOT LOCALE changes the locale If this property is not set. Sample value: LOCALE-en.0/docs/api/java/util/Locale. FAILURE. CDEDBUserName stands for the Continuous Data Export database user.com/j2se/1. feeddb_datafeed_table_20060710.000 parameters in your environment. set it to match the locale of the Portal application server.csv extension (for example. portalDBUserName stands for the BMC Performance Manager Portal database user name. NOTE In this section. data from the BMCPDS server is moved to the PARAMETER_DETAIL table in the CDE datastore database.html. portalDBPassword stands for the BMC Performance Manager Portal database user password.US External CDE movement If BMC Portal is monitoring more than 200.External CDE movement Table 22 Property Additional configuration options for the datafeed utility (part 5 of 5) Description specifies a failover file location Sample value: c:/datafeed/errordump/feeddb_datafeed_table The failover file name contains a unique identifier that includes the date and a .

you can use the exportParameterHistory and refreshDatafeedMetadata commands. see the BMC Portal Monitoring and Management Guide. NOTE The old CDE movement mechanism is disabled for the PARAMETER_DETAIL table. NOT NULL) PARAMETER_VALUE (VARCHAR2(4000)) PARAMETER_STATUS (VARCHAR2(128)) PARAMETER_PREVIOUS_STATUS (VARCHAR2(128)) In the PARAMETER_DETAIL table. SAMPLE_TIMESTAMP_UTC. whenever required. However. see “To create filters” on page 213.External CDE movement The PARAMETER_DETAIL table contains the following columns: s s s s s PARAMETER_GUID (VARCHAR2(32). For more information about applying filters. The CDE movement does not move data to the PARAMETER_PREVIOUS_STATUS column. configure the external CDE movement on the primary application server and then on the secondary application server. You can also apply filters on the CDE movement. The CDE movement also provides the direct database feed approach for the exportParameterHistory BMC Performance Manager Command Line Interface (BPMCLI) that is used for History Data Export (HDE). rather than continuously moving data at five-minute intervals. NOT NULL) SAMPLE_TIMESTAMP_UTC (TIMESTAMP(0). the feature moves data only to the PARAMETER_GUID. ensure that the old CDE mechanism that you configured is working. PARAMETER_VALUE. For more information about the commands. the HDE export populates all the columns in the PARAMETER_SUMMARY table. you must schedule the CDE movement once each day. This feature moves the granular data once each day. If two or more BMC Performance Manager Portal application servers are clustered. However. Before you begin s Before configuring the external CDE movement. s Chapter 6 Reports 207 . Therefore. and PARAMETER_STATUS columns when the CDE movement occurs.

in the datafeed.externalHDE.properties file.refreshhours=24 entry. in the datafeed.properties file.External CDE movement To configure the external CDE movement 1 Open the datafeed.enabled=false entry to portal. NOTE BMC recommends that you retain the default duration set for refreshhours.enabled=true.properties file.externalHDE.enabled=true. retain the default duration of 24 hours in the portal.datafeed. NOTE If you have configured external summarization. 3 To transfer the data to CDE.refreshhours=24 entry. retain the default duration of 24 hours in the portal.externalCDE.properties file. modify the time (24-hour format) in the portal.datafeed.datafeed. 5 To enable the external HDE movement.enabled=false entry to portal.datafeed. 4 In the datafeed. 6 To transfer the data to HDE. modify the time (24-hour format) in the portal. in the datafeed. contact BMC Customer Support.properties file located at: BMC_PORTAL_KIT_HOME\appserver\websdk\tools\jboss\server\all\conf\ properties\drmop or $BMC_PORTAL_KIT_HOME/appserver/websdk/tools/jboss/server/all/conf/ properties/drmop 2 To enable the external CDE movement.schedulehours=3 entry and specify a suitable time at which you want to schedule the transfer. modify the portal.externalCDE.externalCDE. 208 BMC Performance Manager Portal Monitoring and Management Guide .externalHDE.schedulehours=4 entry and specify a suitable time at which you want to schedule the transfer. If you want to modify the duration for exporting the granular data to the external database. 7 In the datafeed.datafeed.externalHDE. ensure that the time that you specify in step 6 is one hour ahead of the time when the external summarization takes place.externalCDE.datafeed. in the datafeed. modify the portal.datafeed.properties file.properties file.datafeed.

old new 1: grant create any view to &1 1: grant create any view to CDE Grant succeeded.sql file./DatastoreCliBMCPDS. contact BMC Customer Support. go to the %DATASTORE_HOME%\utility\BPM_Datastore_Utility directory. On Solaris. If you want to modify the duration for exporting the granular data to the external database. 9 By using the command prompt. enter .sh instead of DatastoreCliBMCCDE. 11 Open the %DATASTORE_HOME%\utility\BPM_Datastore_Utility\scripts\create_psdp_tb. old new 1: grant IMP_FULL_DATABASE to &1 1: grant IMP_FULL_DATABASE to CDE Grant succeeded.sh instead of DatastoreCliBMCPDS. 8 Log on to the BMCCDE server. and .External CDE movement NOTE BMC recommends that you retain the default duration set for refreshhours. 10 Enter the following command: DatastoreCliBMCCDE sys "sys as sysdba" grant_bmccde CDEDBUserName The output of the command will be similar to the following: old new 1: grant create database link to &1 1: grant create database link to CDE Grant succeeded./DatastoreCliBMCCDE. 12 Modify the value of ORADATA_LOCATION to the fully-qualified path of the database files. use shell instead of the command prompt. Chapter 6 Reports 209 . old new 1: grant create materialized view to &1 1: grant create materialized view to CDE Grant succeeded. NOTE The commands entered in the procedure are valid on Microsoft Windows.

14 Use Notepad to open the ORACLE_HOME\network\admin\tnsnames. 15 Append the following contents to the file: BMCPDS_SID= (DESCRIPTION= (ADDRESS_LIST= (ADDRESS= (PROTOCOL=TCP) (HOST=BMCPDSServerHostName) (PORT=1521)) ) (CONNECT_DATA= (SERVICE_NAME=BMCPDS) ) ) 16 Set the value of HOST to the host name of the BMCPDS server.ora file.External CDE movement 13 Enter the following command: DatastoreCliBMCCDE CDEDBUserName CDEDBPassword create_psdp_tb The output of the command will be similar to the following: Tablespace created. 17 Enter the following command to create a database link: DatastoreCliBMCCDE CDEDBUserName CDEDBPassword createDbLink portalDBUserName portalDBPassword The output of the command will be similar to the following: Database link created 18 Enter the following command to test the database link from the BMCCDE server to the BMCPDS server: DatastoreCliBMCCDE CDEDBUserName CDEDBPassword testDBLink The output of the command will be similar to the following: Database link connection is successful 19 Enter the following command: DatastoreCliBMCCDE CDEDBUserName CDEDBPassword external_cde_proc The output of the command will be similar to the following: 210 BMC Performance Manager Portal Monitoring and Management Guide .

Disabling the foreign key Table altered. 24 2010-02-12 08:00:00 0 external_cde_proc. NOTE Ensure that you specify a time ahead of the time that you entered in the datafeed. The output of the command will be similar to the following: Enter the hour at which you want to schedule the CDE import (HH24): 5 PL/SQL procedure successfully completed. 20 Enter the following command: DatastoreCliBMCCDE CDEDBUserName CDEDBPassword schedule_import_from_pe_to_cde This prompts you to specify the time when you want to schedule the data movement from the CDE_DATAFEED_CACHE table of the BMC Portal database instance to the PARAMETER_DETAIL table of the BMCCDE instance.50.10. Package body created. 29 2010-02-13 05:00:00 21 Enter the following command: DatastoreCliBMCCDE CDEDBUserName CDEDBPassword schedule_import_from_pe_to_hde This prompts you to specify the time when you want to schedule the data movement from the HDE_DATAFEED_CACHE table of the BMC Portal database instance to the PARAMETER_SUMMARY table of the BMCCDE instance. Disabled the foreign key No errors. Session altered. SYSTIMESTAMP ------------------------------------------------------------------12-FEB-10 07.328000 AM -06:00 WHAT||''||JOB||''||NEXT_DATE||''||FAILURES ---------------------------------------------------------------cde_part_maint.properties file to schedule the transfer of data to CDE. Chapter 6 Reports 211 .import_from_pe_to_cde.External CDE movement Package created.maintain_parameter_summary(90).maintain_parameter_detail(30). 23 2010-02-12 21:00:00 0 cde_part_maint.

maintain_parameter_detail(30). 2 Go to the %DATASTORE_HOME%\utility\BPM_Datastore_Utility directory..csv generated.35.maintain_parameter_summary(90).import_from_pe_to_cde.import_from_pe_to_hde. SYSTIMESTAMP ------------------------------------------------------------------12-FEB-10 07.718000 AM -06:00 WHAT||''||JOB||''||NEXT_DATE||''||FAILURES ------------------------------------------------------------------cde_part_maint. To determine the values for filters 1 Log on to the BMCPDS server.51. 29 2010-02-13 05:00:00 external_cde_proc.External CDE movement NOTE Ensure that you specify a time ahead of the time that you entered in the datafeed. filter_sample.. 30 2010-02-13 04:00:00 Applying filters for CDE and HDE You can determine the values that can be used in the filters for CDE and HDE.csv . 23 2010-02-12 21:00:00 0 cde_part_maint.properties file to schedule the transfer of data to HDE. Session altered. The output of the command will be similar to the following: Enter the hour at which you want to schedule the HDE import (HH24): 4 PL/SQL procedure successfully completed. 3 Enter the following command: DatastoreCliBMCPDS portalDBUserName portalDBPassword filter_sample The output of the command will be similar to the following: Generating filter_sample. Please use this file to create the filters 212 BMC Performance Manager Portal Monitoring and Management Guide . 24 2010-02-12 08:00:00 0 external_cde_proc.

An underscore (_) in the pattern matches exactly one character. 3 Use Notepad to open the create_filters.csv file.name stands relates to the ProviderName in the filter_sample.csv file.sql file.csv file. To create filters 1 Log on to the BMCPDS server.csv file. s s s s s s s 5 Go to the %DATASTORE_HOME%\utility\BPM_Datastore_Utility directory. 2 Go to the %DATASTORE_HOME%\utility\BPM_Datastore_Utility\scripts directory. 6 Enter the following command: DatastoreCliBMCPDS portalDBUserName portalDBPassword create_filters Chapter 6 Reports 213 . start and partition). The pattern '%' cannot match a null character.csv file. 4 Use the following information to edit the file: s pi. ai. ‘%art%’ indicates that it will match any string that contains the pattern between the % characters (for example.definitionname relates to the ParameterDefinitionName in the filter_sample.csv. wa. You can use these values to determine the required filters. When you are using the LIKE command. filter_sample. wp.companyname relates to the AccountName in the filter_sample. s s s s Provider Account Application name Parameter definition name TIP Use Microsoft Excel to view the filter_sample. A percent sign (%) in the pattern can match zero or more characters.External CDE movement This command generates a sample output file. which shows the values for the following levels.applicationname relates to the ApplicationName in the filter_sample.

log generated. refresh_metadata.log file: DatastoreCliBMCPDS portalDBUserName portalDBPassword validate_export_metadata 214 BMC Performance Manager Portal Monitoring and Management Guide . Elapsed: 00:00:04. Elapsed: 00:00:00.log file is generated. 3 Enter the following command to get the latest metadata: DatastoreCliBMCPDS portalDBUserName portalDBPassword manual_refresh_metadata 4 The manual_refresh_metadata. 2 Go to the %DATASTORE_HOME%\utility\BPM_Datastore_Utility directory. 5 To verify the metadata that will be filtered for the CDE transfer. enter the following command to view the validate_export_metadata. while.External CDE movement The output of this command will be similar to the following: PL/SQL procedure successfully completed. PL/SQL procedure successfully completed.13 Table analyzed. Elapsed: 00:00:00.. The output of the command will be similar to the following: Metadata Refresh Starting. Materialized view created. Elapsed: 00:00:02. This may take a To get the latest metadata information related to application classes and accounts 1 Log on to the BMCPDS server.87 Created the filters and MV_CDE_EXPORT_CONFIG Generated create_filters..03 Creating the filters and MV_CDE_EXPORT_CONFIG.07 Metadata Refresh completed.log.

0 .. To verify that the external CDE movement has been enabled. Restarting the BMC Performance Manager application server You must log in to the computer where you have installed BMC Portal. validate_export_metadata. To check CDE or HDE error messages 1 Log on to the BMCPDS server.2. run the reports on the CDE or HDE database to ensure that the data has been successfully transfered on the database..log file contains the following message: externalCDEEnabled=true Checking CDE or HDE error messages On the day following the BMC Performance Manager Portal application server restart. Restart the BMC Performance Manager Portal application server to apply the changes that you made on BMC Portal. 2 Go to the %DATASTORE_HOME%\utility\BPM_Datastore_Utility directory.2. ensure that the portal. 3 Enter one of the following commands: s s DatastoreCliBMCPDS portalDBUserName portalDBPassword progress 24 DatastoreCliBMCCDE CDEDBUserName CDEDBPassword progress 24 Chapter 6 Reports 215 .log generated. Disconnected from Oracle Database 10g Enterprise Edition Release 10.0.External CDE movement The output of the command will be similar to the following: Generating the list of the metadata which will be exported to CDE.64bit Production With the Partitioning and Data Mining options To synchronize the metadata refresh with CDE Enter the refreshDatafeedMetadata BPMCLI command as described in “refreshDatafeedMetadata” on page 264.

216 BMC Performance Manager Portal Monitoring and Management Guide .External CDE movement In the preceding commands. Check the error messages in the log file. 24 represents the number of hours for which you want to fetch the login messages from the PORTAL_LOG table. The preceding commands generate the progress.log file.

. . . . . . Event integration using AlarmPoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provider-wide integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List content . . . . . . . BMC Performance Manager Portal as a CMDB Provider . . . . . . . . . . . . . . Account integration. . . . . . . . . This chapter presents the following topics: Levels of integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Object identifiers (OIDs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC-Performance-Manager-Portal-MIB description . . . . . . . . . . . . . . . . . . . . . . . MIB files . . . . . . . . . . . . . . . . . . . . . . . . . Sample trap. . . . . . . . . . . . . . BMC Performance Manager Portal as a CMDB Consumer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event integration using email notifications. . . . . . . . . . . . . . . . . . . . . . . Trap error codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Page controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Portal-wide integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Model integration . . . . . . . . . BMC Atrium CMDB integration . . . . . . . . . . . . . . . . . . . the Portal can send those events to other products that can use or manage events. . . . . . . . . . . . . . . . . . . .Chapter 7 218 218 218 219 219 220 221 221 224 226 226 227 228 228 233 236 236 237 238 239 243 245 246 247 248 249 7 Portal events and data integration When infrastructure elements exceed thresholds and trigger events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event integration . . . Chapter 7 Portal events and data integration 217 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event integration using BMC II Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parsing SNMP traps . . . . . . Events tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event integration using SNMP traps . . . . . . . . . . . . . . Combining BMC Performance Manager and PATROL Agent events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trap properties customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reconciliation rules for infrastructure elements and the BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . .

s s “Event integration using AlarmPoint” on page 228 Before you can configure AlarmPoint notifications. which affects all users and accounts on the Portal. you can access and modify the options in the Notifications task on the Provider tab to integrate event data with other modules or products. For more information about configuring Portal-wide integration. 218 BMC Performance Manager Portal Monitoring and Management Guide . s “Event integration using email notifications” on page 226 “Event integration using SNMP traps” on page 227 Before you can configure SNMP notifications. by using the Global Properties page on the Portal tab.Levels of integration Levels of integration The Portal enables you to configure different levels of integration with other Portal modules and BMC products. Portal administrators also must access the Global Properties page to specify an AlarmPoint server to receive notifications from the Portal. When configured. see the following topics: s s “BMC Atrium CMDB integration” on page 219 “Service Model integration” on page 224 To configure AlarmPoint notifications. The extent to which you can configure the Portal depends on the credentials that you use to log on to the Portal. which affects all accounts in a provider. you must specify a SNMP server to receive notifications from the Portal. After you log on. a Portal administrator must access the Global Properties page to specify an AlarmPoint server to receive notifications from the Portal. Provider-wide integration Administrators with Edit permission can establish provider-wide (or enterprise level) integration. Portal-wide integration Administrators with Edit and See Other Providers and Their Users permissions can establish Portal-wide integration. these notification rules trigger notifications for all events (of the specified type) for all accounts in a provider.

s s “Event integration using AlarmPoint” on page 228 Before users can configure AlarmPoint notifications. such as software. and people. see the following topics: s “Event integration using email notifications” on page 226 “Event integration using SNMP traps” on page 227 Before you can configure SNMP notifications. BMC Atrium CMDB integration The BMC Atrium Configuration Management Database (BMC Atrium CMDB) is a repository of configuration items (CIs). a provider administrator must specify a BMC II Web Services server to receive notifications from the Portal. network and related databases. The BMC Atrium CMDB stores the attributes for CIs and the relationships between them. the CI is updated in the BMC Atrium CMDB. hardware. When you specify the BMC Remedy Action Request System (BMC Remedy AR System) properties and credentials. the Portal sends objects to the BMC Atrium CMDB whenever you add an infrastructure element to the Portal. a Portal administrator must access the Global Properties page to specify an AlarmPoint server to receive notifications from the Portal. When you add application classes to an infrastructure element or remove them from an element. you must specify a BMC II Web Services server to receive notifications from the Portal. you must specify a SNMP server to receive notifications from the Portal.Account integration s “Event integration using BMC II Web Services” on page 228 Before you can configure BMC II Web Services notifications. For more information about configuring account integration. s “Event integration using BMC II Web Services” on page 228 Before users can configure BMC II Web Services notifications. Account integration Users with full access rights for notifications can access and modify the options in the Notifications task on the Configure tab to integrate event data with other modules or products. Chapter 7 Portal events and data integration 219 . documentation.

BMC Performance Manager Portal as a CMDB Consumer NOTE During installation of the Portal (or Portal application server). Consumer programs can use this information in many ways. like BMC Performance Manager Portal. you can use the Portal to enable infrastructure monitoring for those objects. act as a consumer and a provider. s s BMC Performance Manager Portal as a CMDB Consumer If you use a product like BMC Topology Discovery to discover IT objects and populate the BMC Atrium CMDB. s CMDB Providers gather information about CIs and store this information in the BMC Atrium CMDB. If you did not have a BMC Atrium CMDB at the time of installation. to create relationships among the CIs. CMDB Consumers use information from the BMC Atrium CMDB. “Integrating infrastructure elements from the BMC Atrium CMDB” on page 42 describes how to add an infrastructure element to the Portal by selecting (or consuming) information from the BMC Atrium CMDB. Provider programs provide the base content used by the consumer programs. such as to associate trouble tickets with computers or programs. or to build a service model in a cell. Programs known as CMDB Providers feed CIs to the BMC Atrium CMDB. Programs known as CMDB Consumers use the CIs. the installation program prompted you for a BMC Remedy AR System server name and credentials. you can log on with Portal administrator credentials and provide the server name and credentials on the Global Properties page. Some products. You can access this page when you log on to the Portal with Portal administrator credentials. eliminating the need to enter this information multiple times. ensure that the credentials and properties for the BMC Atrium CMDB have been configured on the Global Properties page. NOTE Before searching for infrastructure objects in the BMC Atrium CMDB. BMC Topology Discovery is an example of a BMC Software product that acts as a CMDB Provider. 220 BMC Performance Manager Portal Monitoring and Management Guide .

The CI also includes impact relationships. the application classes that you select determine what information is placed into the BMC Atrium CMDB. If you do not want to wait for the scheduled reconciliation task. in the ARBASE\AR System\Admin directory or s DataImport. For information about configuring SIM extensions. Without reconciliation rules. The Properties page for an infrastructure element shows the reconciliation status for the element under BMC Atrium CMDB Status. a reconciliation program enters the element properties into the BMC.BMC Performance Manager Portal as a CMDB Provider BMC Performance Manager Portal as a CMDB Provider When you add an element to the Portal. In addition to configuring the BMC Remedy AR System Server properties in the Portal. you can use the BMC Remedy User program to manually reconcile the element properties. Reconciliation rules for infrastructure elements and the BMC Atrium CMDB To reconcile data from the BMC Performance Manager Portal. Chapter 7 Portal events and data integration 221 .ASSET dataset in the BMC Atrium CMDB. which you can see if you have added the BMC SIM CMDB extensions to the BMC Atrium CMDB. and it writes an error to the log file. see the BMC Impact Solutions Planning and Installation guide. generally once a day.BPM dataset in the BMC Atrium CMDB. the Portal adds the CI and its relationships to other CIs to the BMC.exe under BMC Remedy AR System. After you add infrastructure elements to the account. The reconciliation is a scheduled task that runs on the BMC Atrium CMDB. including the reconciliation tokens. you must also import the reconciliation rules. Any events triggered for an application class are not populated with a reconciliation ID until after reconciliation occurs. If the selected application classes contain information to generate the required details. To import reconciliation rules into the BMC Atrium CMDB 1 Verify if you have: s arimportcmd.bat under the ARBASE\ARSystem\dataimporttool directory. the Portal does not add any information to the BMC Atrium CMDB. the reconciliation program uses reconciliation rules.

you must install dataimporttool on the computer. if chosen. you can omit this option.bat file. This option identifies a TCP specific port. enter either of the following commands for each of the required files (Table 23 on page 222 describes the options’ variables): arimportcmd -x server -u userName -p password -a tcpPort -o fileName -l logFile -e 179 -D 4 or dataImport -x server -u userName -p password -a tcpPort -o fileName -l logFile -e 179 -D 4 Table 23 Variable server userName password tcpPort Variables for arimportcmd or dataImport command (part 1 of 2) Description host name for the BMC Atrium CMDB server user name to log on to the BMC Atrium CMDB password that authenticates the user name TCP port number for the server This value is important when there are multiple servers in an environment. 222 BMC Performance Manager Portal Monitoring and Management Guide . If the value is 0. 2 Depending on your setup. ARBASE represents the root installation directory for the Remedy components.Reconciliation rules for infrastructure elements and the BMC Atrium CMDB NOTE To run the DataImport.

Do not import all the three files: s s s reconrules21. -e refers to duplicate field.arx (if you have CMDB 7. It defines how the BMC Remedy AR System processes the records that contain request IDs.Reconciliation rules for infrastructure elements and the BMC Atrium CMDB Table 23 Variable fileName Variables for arimportcmd or dataImport command (part 2 of 2) Description full path and file name of the file being imported You must execute the arimportcmd or dataimport command on the following set of files (in the following order): Set 1: dataset. It refers to the ID number of the field to check for duplicate data.1) reconrules75.6) You can find these files at the following location on the Portal application server: s On Windows: %BMC_PORTAL_KIT_HOME%\appserver\util\BPM_CMDB On Solaris: $BMC_PORTAL_KIT_HOME/appserver/util/BPM_CMDB s logFile full path and file name of the optional log file NOTE Do not change values of the -D 4 (duplicate ID) and -e 179 (duplicate field) variables. which imports the dataset definition Set 2: Any of the reconciliation rules. Option 4 updates the old record with the new record’s data. s -D refers to duplicate ID. depending upon the CMDB version that you have. Note: Import any one of the following files depending upon your CMDB version.5) reconrules76. s Chapter 7 Portal events and data integration 223 .arx (if you have CMDB 7. Option 179 refers to the instance ID. which duplicate those already in the form.arx (if you have CMDB 2.arx.

The impact relationships define the infrastructure relationships in the service model.Service Model integration Service Model integration How you provide infrastructure object data for service models depends on whether you have BMC Atrium CMDB installed. If you do not have the BMC Atrium CMDB in place. you can configure the Portal to send impact relationships for infrastructure object data directly to the cell. s When you have BMC Atrium CMDB installed. perform one of the following actions: s To configure the Portal to send CIs to the BMC Atrium CMDB. s To configure the Portal to provide infrastructure data for service models 1 Log on to the Portal with Portal administrator credentials. To implement this method. you can configure the Portal to add infrastructure CIs into the BMC Atrium CMDB. s The settings under Direct Service Model Integration take effect if you clear the text boxes in the BMC Atrium Configuration Management Database Settings section. you can create service models. specify the settings under Direct Service Model Integration. 224 BMC Performance Manager Portal Monitoring and Management Guide . select Global Properties. To implement this method. To configure the Portal to send impact relationships for the service model. and select the Portal tab. you need the BMC Impact Solutions kit. When the CIs are reconciled. Figure 30 provides a high-level view of the methods you can use to provide infrastructure object data for service models. specify the settings under BMC Atrium Configuration Management Database Settings. 3 On the Global Properties page. you need the BMC Atrium CMDB and the BMC Impact Solutions kit. 2 In the navigation pane.

Service Model integration Figure 30 Simplified view of service model integration methods from the Portal Portal CIs CMDB Portal object models Impact Manager (cell) Following direct service model integration configuration. the Portal sends the infrastructure object data required for the service model to the cell. Chapter 7 Portal events and data integration 225 . see the BMC Impact Solutions: Service Model Administrators Guide. For information about adding service components to a service model or monitoring service components. whenever you add an element to the Portal and apply application classes that are enabled for BMC Atrium CMDB integration.

Event integration Event integration The BMC Performance Manager Portal sends events when s s an agentless parameter changes state (state change events) the RSM changes state (general system problems events) When configuring notifications for provider-wide notifications.email . 226 BMC Performance Manager Portal Monitoring and Management Guide . for example) connectSNMP provides enterprise-wide event consolidation and management for PATROL environments email AlarmPoint by AlarmPoint Systems . They are not structured. Figure 31 BMC Performance Manager Portal event integration BMC Performance Manager Portal (Portal) SNMP event third-party SNMP manager (Tivoli.page . you can specify the transports shown in Figure 31 to integrate state changes or general system problems events with other products. which limits their use to simple integrations.SNMP event Impact Integration for PEM Impact Integration Web Services PATROL Enterprise Manager (PEM) Remote Service Monitor detects condition on monitored system and sends event to the Portal BMC Service Impact Manager BMC Performance Managers shows real-time impact of IT problems on IT and business services BMC Event Manager filters and correlates events and automates corrective action BMC Impact Legend event flow viewable event data (Java-based console) manages events and event policies Event integration using email notifications You can configure notification rules that send event email messages to named recipients.voice mail . Email messages provide a subset of the information passed in the event.

When you have both types configured. The MIB extensions used by the Portal enable you to translate the information contained in the Portal traps for use with other products. s If you configure provider-level notification rules that use the SNMP transport. When configuring status change notification rules. versions 1 and 2. you can configure the Portal to send SNMP traps to one or more computers. and the time to wait after the event occurs before sending the trap. that trap has a bmcPMPortalNotificationType of 2. SNMP traps can be used to integrate with BMC Software event managers and third-party event managers. For information about configuring the Portal to send SNMP traps.4. MIB files map numeric object identifiers (OIDs) (such as 1. the circumstances under which the Portal should send the trap. you can select Element and Parameter as the object type. that trap has a bmcPMPortalNotificationType of 1. See page 243 for more information. MIB files are extensible. Chapter 7 Portal events and data integration 227 . This transport method supports status change and general system problems events.1. the Portal sends two notifications for each event. When an element value or RSM state triggers the Portal to send an enterprise-wide SNMP trap.Event integration using SNMP traps Event integration using SNMP traps When logged on as a user or provider administrator.3. see “SNMP traps” on page 236.11) used by most SNMP queries into more meaningful names (and vice versa). you might not want to have user-level notification rules that also use the SNMP transport (and send notifications to the same target computers).6. you can specify the type of threshold violations. and most hardware and software companies define their MIBs as extensions of some universal industrystandard MIB file. The Portal MIB files support SNMP traps. The Portal sends traps when the following events occur for any infrastructure object in the account: s s s a parameter changes state an infrastructure element changes state an RSM changes state When configuring user notification rules for SNMP traps. s When a parameter or element value violates a rule that triggers a user notification trap.

If you configure provider-level notification rules that use the AlarmPoint transport. you can configure the Portal to send notifications to AlarmPoint. When administrators create AlarmPoint notifications from the Provider tab or when users create AlarmPoint notifications from the Configure tab. 228 BMC Performance Manager Portal Monitoring and Management Guide . If the BMC II Web Services server was configured for high availability (HA). When you have both types configured. element. you might not want to have user-level notification rules that also use the AlarmPoint transport. it tries the secondary BMC II Web Services server. you can use the Notifications task to configure the Portal to send events to an AlarmPoint server. the Portal sends two notifications for each event. For more information about configuring a BMC II Web Services server for HA. you can configure notification rules for the Portal to send notifications to BMC Impact Manager (BMC IM) through the BMC Impact Integration Web Services server (BMC II Web Services). By using scripts provided on the installation DVD and CD1 for your Portal operating system. you can configure the Portal to send notifications to the primary BMC II Web Services server. The Portal can use an insecure or secure web-based connection to send events to the BMC II Web Services server. if one is specified. When the Portal cannot connect to the primary server. you can also specify a secondary BMC II Web Services server. See the BMC Portal Getting Started guide for detailed procedures about how to configure AlarmPoint integration.Event integration using AlarmPoint Event integration using AlarmPoint If you have AlarmPoint installed. a Portal administrator must use the Global Properties page to configure the Portal for AlarmPoint integration. Before users or provider administrators can create notification rules for AlarmPoint. see the BMC Impact Integration Web Services Server Installation and Configuration Guide. Configuring the Portal to send data to a BMC II Web Services server When logged on as an administrator for a provider. The Portal always tries to send events to the computer identified as the primary BMC II Web Services server. BMC II Web Services maps parameter-level notifications from the Portal in the event format for BMC Impact Manager solutions. and general system problem events to the designated AlarmPoint server. the Portal can send parameter. Event integration using BMC II Web Services When logged on as a user or provider administrator.

obtain a signed certificate from a certificate authority. The BMC Impact Integration Web Services Installation and Configuration Guide describes how to generate these keys. See the BMC Portal Help for detailed information about specifying the BMC II Web Services Server. select Use HTTPS. For information about importing the certificate. See the BMC Impact Integration Web Services Server Installation and Configuration Guide for information about obtaining a certificate from a certificate authority. you must select Use HTTPS when specifying the BMC II Web Services Server and BMC IM. 3. see “Importing the certificate for the BMC II Web Services Server. See the BMC Portal Help for detailed instructions. Log on to the Portal with administrator credentials and configure the BMC II Web Services Server to which the Portal will send events. See the BMC Portal Help for detailed instructions. For secure communications in a production environment. s To enable and configure secure communications using a self-signed certificate between the Portal application server and the BMC II Web Services Server. s For secure communications between the BMC Portal and the BMC II Web Services Server in a development or testing environment.” 2. Chapter 7 Portal events and data integration 229 .Event integration using BMC II Web Services Configuring secure event integration with BMC Impact Solutions These guidelines summarize the main tasks of sending events securely between the BMC Portal and BMC II Web Services. To specify secure communications. Importing the certificate for the BMC II Web Services Server To configure secure communications between the Portal and the BMC II Web Services Server. generate a self-signed public key and self-signed private key. While logged on as an administrator. Import a secure certificate from the BMC II Web Services Server into the Portal application server. perform the following actions: 1. select the Provider tab and add a notification rule that uses the BMC II Web Services transport.

5 At the Trust this certificate password prompt. 2 Locate the Keytool utility in one of the following directories: s s On Windows: %BMC_PORTAL_KIT_HOME%/appserver/websdk/tools/jdk/jre/bin On Solaris: $BMC_PORTAL_KIT_HOME\appserver\websdk\tools\jdk\jre\bin 3 Type the following command: Keytool -import -file directory\iiwscertificate. you also must import the SSL certificate for the BMC II Web Services Server to the Portal application server. 6 Restart the Portal application server. select yes.Event integration using BMC II Web Services In addition to using the Portal interface to specify the BMC II Web Services Server.cer -keystore directory\cacerts You can find cacerts in one of the following directories: s On Windows: %BMC_PORTAL_KIT_HOME%/appserver/websdk/tools/jdk/jre/lib/security On Solaris: $BMC_PORTAL_KIT_HOME\appserver\websdk\tools\jdk\jre\lib\security s 4 At the Enter keystore password prompt. 230 BMC Performance Manager Portal Monitoring and Management Guide . type changeit. To import the BMC II Web Services secure certificate to the Portal application server 1 Copy the secure certificate file from the BMC II Web Services Server to the Portal application server.

The BMC II Web Services Server and the BMC Impact Solutions also populate additional slots.Event integration using BMC II Web Services Using default insecure event integration with BMC Impact Solutions To enable and configure insecure communications between the Portal application server and the BMC II Web Services Server. select the Provider tab and add a notification rule that uses the BMC II Web Services transport. The base event class slots listed in Table 24 represent the content of the event as it progresses from the BMC Performance Manager Portal to the BMC Impact Manager cell. While logged on as an administrator. See the BMC Portal Help for detailed instructions. for example: Windows 2003-Using Perfmon|Disk) the assigned name for the RSM that reported the event the literal value: BPMPV2 mc_host mc_host_address mc_host_class mc_incident_time mc_object mc_object_class mc_origin mc_origin_class Chapter 7 Portal events and data integration 231 . Log on to the Portal with administrator credentials and configure the BMC II Web Services Server to which the Portal will send events. Table 24 Slot adapter_host CLASS Slot names in the base event class populated for the Portal (part 1 of 2)a Description the server name for the BMC Portal server the type of event being generated (PORTAL_PARAMETER_STATE_CHANGE. Ensure that you do not select Use HTTPS. such as mc_arrival_time (the time stamp of the event arrival at the BMC Impact Solutions network). 2. See the BMC Portal Help for detailed instructions. perform the following actions: 1. Solaris) the time of the event the instance or application class (if no instance exists) the qualified hierarchy for the object (including parent instance and application classes separated by | as a delimiter. PORTAL_RSM_STATE_CHANGE for RSM state changes) the host name of the managed element the IP address associated with the managed element the type of element (for example. BMC Impact solutions base event class BMC Impact Solutions have a base event class that defines the content of the events (called slots) that the BMC Impact Manager cell can process.

Table 25 PATROL_Portal event class extensions Description the account associated with the event the parent groups that contain the element associated with the event the display name of the managed element PATROL_Portal slots patrolAccountName patrolGroupName patrolElementName patrolParameterErrorCode error code patrolParameterThreshold the threshold value breached 232 BMC Performance Manager Portal Monitoring and Management Guide . shown in Table 25. Warning. see the BMC Impact Manager Knowledge Base Reference Guide.Event integration using BMC II Web Services Table 24 Slot Slot names in the base event class populated for the Portal (part 2 of 2)a Description an internal identifier for the event (GUID) severity (same as the severity slot) the parameter name the value that caused the event the internal identifier (GUID) of the nearest parent application instance that has a mapping to a CMDB CI (always the same object referenced by mc_smc_id) the CMDB reconciliation ID of the nearest parent application instance which has a mapping to a CMDB CI the server name for the BMC Portal server the literal value: BMC Portal Server a text description of the event the severity of the event (Info. In addition to the common slots in the base event class. automated processes such as event filtering by BMC Service Impact Manager or BMC Event Manager could also change in the future. the Portal uses the PATROL_Portal event class to provide extended slots for event content from the Portal. Critical) mc_origin_key mc_origin_sev mc_parameter mc_parameter_value mc_smc_alias mc_smc_id mc_tool mc_tool_class msg severity a For more information about the slots in the base event class. Because the slots in the PATROL_Portal event class extension. are subject to change with emerging event-integration technology.

Custom events generated by PATROL KMs or PATROL integration Performance Managers using event triggers are available in the Portal. PATROL integration Performance Managers contain many of the parameters found in their corresponding KMs and obtain their parameter values from the PATROL Agent. Not all events that the PATROL Agent generates are available in the Portal. s “Overlapping agentless and agent-based monitoring” on page 234 describes how you can trigger two distinct events for one threshold breach. only a subset of the parameters from PATROL KMs are available in the Portal because of fundamental technical differences between the product architectures. You can encounter this situation when you introduce agentless monitoring in an environment that uses PATROL Agents to monitor and manage infrastructure. but to be usable by an event manager. Also. Chapter 7 Portal events and data integration 233 . they must be sent from the PATROL Agent to BMC PATROL EM.Combining BMC Performance Manager and PATROL Agent events Combining BMC Performance Manager and PATROL Agent events This section describes situations in which duplicate events are sent to BMC PATROL Enterprise Manager (BMC PATROL EM) when you use multiple event management technologies to monitor the same systems. s “Using PATROL integration Performance Managers with PATROL Agent-based monitoring” describes how you can trigger two comparable events from a single threshold breach. an event is triggered by the Portal and another one is triggered by the PATROL Agent. Using PATROL integration Performance Managers with PATROL Agent-based monitoring Duplicate events can occur when you use PATROL Agent-based management on a computer and also use PATROL integration Performance Managers to remotely monitor the same applications on the same computer. Figure 32 on page 234 shows how a "disk full" event detected independently by each management system creates duplicate events for a single parameter. When one of these common parameters breaches one of its thresholds.

234 BMC Performance Manager Portal Monitoring and Management Guide .Combining BMC Performance Manager and PATROL Agent events Figure 32 Two comparable events from one threshold breach BMC PATROL EM disk full disk full Portal existing integration PATROL Agent-based Management PATROL integration Performance Managers (remote management) managed server Overlapping agentless and agent-based monitoring Similar events can occur when you use PATROL Agent-based management to manage a computer and also use the agentless Performance Managers in the Portal to remotely monitor the same computer. while very similar. the disk events are sent by both management components and have similar. Figure 33 on page 235 illustrates the event flow that results from overlapping monitoring. In the example. information about the computer. This situation results in events that. the agentless Performance Managers contain parameters that the PATROL KMs. In the scenario shown in Figure 33 on page 235. based on a single threshold breach. but not identical. also monitor. are not the same. running on the agent.

this causes duplicate events to be sent to the BMC PATROL EM event manager for a single parameter’s threshold breach—one from the agent side and another from the Portal side. Unlike the example in Figure 32 on page 234. the application class. Correlate the duplicate events in an event manager such as BMC PATROL EM. BMC EM. parameters. This action results in losing the ability to monitor the deactivated threshold.Combining BMC Performance Manager and PATROL Agent events Figure 33 Sample agentless and agent-based events sent from the Portal BMC PATROL EM disk event disk event Portal existing integration PATROL Agent-based management agentless Performance Managers managed server A solution Performance Manager that is monitoring the same parameters as an agentmanaged server might have a threshold exception at the same time as a PATROL KM. s s Chapter 7 Portal events and data integration 235 . As the example in Figure 33 shows. you can use the following options: s Use the Notifications task to exclude notifications sent from systems in which you have configured PATROL integration Performance Managers. Deactivate one of the parameter thresholds in either the BMC Performance Manager Portal or the PATROL Agent. How to avoid duplicate events To eliminate duplicate state change events. and instances are different from those in the PATROL KM. or a third-party product.

s WEBSDKV10-MIB— For more information about this MIB. you can choose to use SNMP version 1 or SNMP version 2 traps. modify the value of the snmp. BMC-Performance-Manager-Portal-MIB—If you install the BMC Performance s Manager Portal module.max. see page 339. On the BMC Portal installation DVD. this MIB defines all SNMP events from this module. The Portal triggers Parameter State Change traps when the status of a parameter changes. these traps have different meanings.process property. see the BMC Portal Getting Started guide. When a Parameter State Change also affects the state of the element. When configuring enterprise integration and user notification integration. For more information about this property. Not all Parameter State Changes result in a state change for the element.events. TIP To change the maximum number of parameters that the Portal can send in a trap. 236 BMC Performance Manager Portal Monitoring and Management Guide .to.parameter. the Portal also triggers an Element State Change trap.SNMP traps SNMP traps The BMC-Performance-Manager-Portal-MIB provides the following traps: s s s Parameter State Change RSM State Change Element State Change Although related. the Portal will trigger an RSM State Change event if it fails to receive a heartbeat message from the RSM. MIB files The BMC Performance Manager Portal module provides MIBs that you can use to translate SNMP traps sent from the product. you can find the MIB files under the util\BPM_MIB (Windows) or util/BPM_MIB (Solaris) directory. If you choose to receive notification when a general system problem occurs.

See BMC Portal Getting Started. Figure 34 provides an overview of the general structure of a BMC Performance Manager Portal OID. 2. If the previous digit is 1. [0.. 3 . you can find the MIB files at the following locations on the Portal application server: s s On Windows: %BMC_PORTAL_KIT_HOME%\appserver\util\BPM_MIB On Solaris: $BMC_PORTAL_KIT_HOME/appserver/util/BPM_MIB Object identifiers (OIDs) OIDs are used by SNMP queries to identify individual pieces of data and are identified in the MIB file. 1031 . { 1–3 | 1–n } . { 0 | 1 } . 5 . the possible values for this digit are 1. Figure 34 OID structure in BMC-Performance-Manager-Portal-MIB . 6 .n] indicates that the trap originated from a BMC Software product A value of 5 in this position indicates that the OID is from the BMC-Performance-Manager-Portal-MIB. or 3. 1 . 4 . Chapter 7 Portal events and data integration 237 .Object identifiers (OIDs) Following installation. If the previous digit is 0. the possible values for this digit are 1–n. A value of 7 indicates that the OID is from the WEBSDK10-MIB. 1 . 1 .. indicates the type of value that this OID represents: 0 represents notification 1 represents object This number increments for nodes that contain multiple instances for an OID.

1. and 3.Y. 238 BMC Performance Manager Portal Monitoring and Management Guide .1. — Y identifies the type of notification.3.3.4. For traps generated from the BMC Performance Manager Portal. 2.1.4.6. The version 1 header information includes a generic type. where — X identifies the source of the trap.6. and then filter or process the trap content as needed.1. 2.1. the version of SNMP version that you use has an effect on the following OIDs: s .0: The value of this OID is another OID that identifies the type of trap. Valid values are 1.1. s s s s 1: Parameter State Change 2: RSM State Change 3: Element State Change Version 1 traps include some additional header information that is not included in version 2 traps.1.1.1. and a specific type field.3.0.X.3.1. and represents the Portal up time. .3.6.3.6.0: This OID is identified as time ticks.1. the generic type is always 6 (enterprise-specific event). Valid values are 1.2.1.1.0.6.4.1031.6. This trap identifier OID looks like .1.Parsing SNMP traps Parsing SNMP traps Although the property OIDs in SNMP version 1 and version 2 are the same.0 in version 2 traps enable you to determine the trap type.3.1. The specific type identifies the type of notification.1. a sender OID.1. and 3: s s s 1: Parameter State Change 2: RSM State Change 3: Element State Change The specific type field in the header of version 1 traps and the value corresponding to OID . The valid value for the BMC Performance Manager Portal is 5.

3.3.6.1.1.1.0 .5.1.1.0.4.6.5.4.1031.1.1.1.3.1.BMC-Performance-Manager-Portal-MIB description BMC-Performance-Manager-Portal-MIB description This MIB defines the event traps sent from the BMC Performance Manager Portal.1031.1031.5.6.0) .6.1.1.4.3.1.2 bmcPMPortalRsmStateChange RSM state change notification (from up to down or from down to up) Each state change contains the following nodes: s bmcPMPortalAccountName s bmcPMPortalHostName s bmcPMPortalDetectedTimeUtcStr s bmcPMPortalRsmName s bmcPMPortalRsmState s bmcPMPortalDetectedTime s bmcPMPortalRsmClusterName s bmcPMPortalRsmClusterState s bmcPMPortalNotificationType Chapter 7 Portal events and data integration 239 .0.3.2. Table 26 OID .1 BMC-Performance-Manager-Portal-MIB (part 1 of 5) Type time ticks Index Node name and description represents the up time for the Portal bmcPMPortalParameterStateChange parameter state change notification Each state change contains the following nodes: s bmcPMPortalAccountName s bmcPMPortalGroupName s bmcPMPortalHostName s bmcPMPortalApplicationName s bmcPMPortalApplicationInstanceName s bmcPMPortalParameterName s bmcPMPortalParameterValue s bmcPMPortalParameterState s bmcPMPortalDetectedTimeUtcStr s bmcPMPortalRsmName s bmcPMPortalElementName s bmcPMPortalParameterErrorCode s bmcPMPortalParameterThresholdValue s bmcPMPortalDetectedTime s bmcPMPortalRsmClusterName s bmcPMPortalNotificationType s bmcPMPortalApplicationHierarchy bmcPMPortalNotifications (. Table 26 describes each OID in an event trap.1.

BMC-Performance-Manager-Portal-MIB description

Table 26
OID

BMC-Performance-Manager-Portal-MIB (part 2 of 5)
Type Index Node name and description bmcPMPortalElementStateChange element state change notification Each state change trap contains the following nodes: s bmcPMPortalAccountName s bmcPMPortalGroupName s bmcPMPortalHostName s bmcPMPortalApplicationName s bmcPMPortalApplicationInstanceName s bmcPMPortalParameterName s bmcPMPortalParameterValue s bmcPMPortalParameterState s bmcPMPortalDetectedTimeUtcStr s bmcPMPortalRsmName s bmcPMPortalElementName s bmcPMPortalElementState s bmcPMPortalParameterErrorCode s bmcPMPortalParameterThresholdValue s bmcPMPortalDetectedTime s bmcPMPortalRsmClusterName s bmcPMPortalNotificationType s bmcPMPortalApplicationHierarchy

.1.3.6.1.4.1.1031.5.0.3

bmcPMPortalObjects (.1.3.6.1.4.1.1031.5.1) .1.3.6.1.4.1.1031.5.1.1 string (300 characters) bmcPMPortalAccountName name of the account that contains the element that triggered the notification A trap can contain only one account name, and the account name is unique in the provider. For general system problems traps, this string contains
s s s

Shared when a problem occurs on a shared RSM Global when a problem occurs on a global RSM the account name when a problem occurs on a dedicated RSM

.1.3.6.1.4.1.1031.5.1.2.x

string (300 yes characters)

bmcPMPortalGroupName name of the group or groups that contains the element that triggered the notification Elements can be members of more than one group, and all affected groups are included in the notification.

240

BMC Performance Manager Portal Monitoring and Management Guide

BMC-Performance-Manager-Portal-MIB description

Table 26
OID

BMC-Performance-Manager-Portal-MIB (part 3 of 5)
Type string (255 characters) Index Node name and description bmcPMPortalHostName host name or IP address of the object that triggered the notification This value might be the host name or IP address of the element or of the RSM.

.1.3.6.1.4.1.1031.5.1.3

.1.3.6.1.4.1.1031.5.1.4.x

string (64 yes characters)

bmcPMPortalApplicationName application class responsible for triggering the notification The application name is not necessarily unique on an element, and the trap can contain multiple application names.

.1.3.6.1.4.1.1031.5.1.5.x

string (810 yes characters)

bmcPMPortalApplicationInstanceName instance in the application class that is responsible for triggering the notification Application instances are unique in an application class but are not required to be unique among application classes. This OID is populated for instances in multiple-instance application classes and discovered instances.

.1.3.6.1.4.1.1031.5.1.6.x

string (255 yes characters)

bmcPMPortalParameterName parameter that triggered the notification Parameter names are unique in an application instance but might not be unique among application classes. The trap can contain multiple parameter names.

.1.3.6.1.4.1.1031.5.1.7.x

string (128 yes characters)

bmcPMPortalParameterValue parameter value that triggered the notification The trap contains a parameter value for each parameter that triggered a notification.

.1.3.6.1.4.1.1031.5.1.8.x

integer

yes

bmcPMPortalParameterState parameter state that triggered the notification: s 0: OK s 1: warning s 2: noncriticalalarm s 3 criticalalarm Multiple parameter states are possible.

Chapter 7

Portal events and data integration

241

BMC-Performance-Manager-Portal-MIB description

Table 26
OID

BMC-Performance-Manager-Portal-MIB (part 4 of 5)
Type string (255 characters) Index Node name and description bmcPMPortalDetectedTimeUtcStr time (formatted) at which the event that triggered the notification occurred

.1.3.6.1.4.1.1031.5.1.9

.1.3.6.1.4.1.1031.5.1.10

string (255 characters) integer

bmcPMPortalRsmName name of the RSM that detected the state change

.1.3.6.1.4.1.1031.5.1.11

bmcPMPortalRsmState current state of the RSM: s 0: up s 3: down

.1.3.6.1.4.1.1031.5.1.13

string (300 characters) string (255 yes characters)

bmcPMPortalElementName name of the monitored element that triggered the notification

.1.3.6.1.4.1.1031.5.1.14.x

bmcPMPortalParameterErrorCode Performance Manager-specific code that describes the condition that triggered the notification See “Trap error codes” on page 246. This OID is not populated if the error does not have an error code.

.1.3.6.1.4.1.1031.5.1.15

integer

bmcPMPortalElementState state of the element after the State Change Event: s 0: OK s 1: warning s 2: noncriticalalarm s 3: criticalalarm s 4: nodata

.1.3.6.1.4.1.1031.5.1.17.x

string (256 yes characters) number of milliseconds (64 characters) string (225 characters)

bmcPMPortalParameterThresholdValue parameter threshold value that was breached

.1.3.6.1.4.1.1031.5.1.18

bmcPMPortalDetectedTime number of milliseconds since January 1, 1970, that the Parameter or Element State Change occurred bmcPMPortalRsmClusterName name of the clustered RSM If the RSM is not clustered, this value is blank.

.1.3.6.1.4.1.1031.5.1.19

242

BMC Performance Manager Portal Monitoring and Management Guide

Trap properties customization

Table 26
OID

BMC-Performance-Manager-Portal-MIB (part 5 of 5)
Type integer Index Node name and description bmcPMPortalRsmClusterState current state of the clustered RSM:
s s s

.1.3.6.1.4.1.1031.5.1.20

0: up 1: warn 3: down

If the RSM is not clustered, this value is blank. .1.3.6.1.4.1.1031.5.1.21 integer bmcPMPortalNotificationType feature origin of the event: s 1: enterpriseIntegration s 2: userNotification If you configure both enterprise integration and user notification, in many instances the Portal will send duplicate traps for a single event. Use the bmcPMPortalNotificationType object to parse the origin of the event. .1.3.6.1.4.1.1031.5.1.22 string (8192 characters) bmcPMPortalApplicationHierarchy specifies the full hierarchy of the application instance responsible for the parameter that caused the state change Application instances are separated by delimiters so that you can easily determine multiple levels of application instances and the exact parameter that caused the state change. .1.3.6.1.4.1.1031.5.1.23 string (255 characters) bmcPMPortalEventReason provides a detailed description about the problem that caused the event

Trap properties customization
This section describes some of the properties that you can change to affect the trap header or trap content. You customize trap properties by modifying the internal.properties file, which is located in the following directories:
s

On Windows: %BMC_PORTAL_KIT_HOME%\
appserver\websdk\tools\jboss\server\all\conf\properties\

s

On Solaris:
$BMC_PORTAL_KIT_HOME/appserver/websdk/tools/jboss/server/all/conf/properties/

Chapter 7

Portal events and data integration

243

Trap properties customization

################################################# # SNMP Trap Version, possible values are 1 or 2 # ################################################# # default is snmp v1. snmp.trap.version=1 snmp.trap.max.recv.size=13000

For changes to take effect, you must restart the Portal after modifying the internal.properties file.

Changing the SNMP trap version sent by the Portal
By default, the Portal sends SNMP traps in SNMP version 1 format. To change to version 2, modify the value of the snmp.trap.version property.

Changing the SNMP trap size for the Portal
By default, the Portal can transmit traps as large as 1,300 bytes. To increase the trap size that the Portal can send, modify the value of the snmp.trap.max.recv.size property.

244

BMC Performance Manager Portal Monitoring and Management Guide

Sample trap

Sample trap
Figure 35 provides an example of an enterprise integration trap (identified by the bmcPMPortalNotificationType node) for an Element State Change event. The highlighted regions show the OIDs and their corresponding values. The annotations describe the OIDs. Figure 35 Sample trap for an Element State Change event (part 1 of 2)

Trap(v1) received from host snmp_server.acme.com(172.18.52.17) at Apr 6, 2006 12:21 PM. Enterprise Oid : .1.3.6.1.4.1.1031.5 (.iso.org.dod.internet.private.enterprises.1031.5) , Specific Type : 3,
account name: The trap can contain only one account. Object ID: .1.3.6.1.4.1.1031.5.1.1.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.1.0) STRING: Acme

Object ID: .1.3.6.1.4.1.1031.5.1.2.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.2.0) event object group name: The element that triggered the STRING: mygroup1 was a member of two object groups. Object ID: .1.3.6.1.4.1.1031.5.1.2.1 (.iso.org.dod.internet.private.enterprises.1031.5.1.2.1) STRING: mygroup2
host name: An Element State Change event can contain Object ID: .1.3.6.1.4.1.1031.5.1.3.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.3.0) only host names, not IP addresses. STRING: computer1.acme.com application name: The applications in the trap correspond to Object ID: .1.3.6.1.4.1.1031.5.1.4.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.4.0) the parameters that triggered the notification. STRING: SSHD Object ID: .1.3.6.1.4.1.1031.5.1.4.1 (.iso.org.dod.internet.private.enterprises.1031.5.1.4.1) STRING: SSHD Object ID: .1.3.6.1.4.1.1031.5.1.4.2 (.iso.org.dod.internet.private.enterprises.1031.5.1.4.2) STRING: SSHD application instance name: The instances in the trap Object ID: .1.3.6.1.4.1.1031.5.1.5.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.5.0) correspond to the parameters that triggered notification. STRING: com_acme-DRPM3-performance Object ID: .1.3.6.1.4.1.1031.5.1.5.1 (.iso.org.dod.internet.private.enterprises.1031.5.1.5.0) STRING: com_acme-DRPM3-performance Object ID: .1.3.6.1.4.1.1031.5.1.5.2 (.iso.org.dod.internet.private.enterprises.1031.5.1.5.0) STRING: com_acme-DRPM3-performance

Object ID: .1.3.6.1.4.1.1031.5.1.6.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.6.0) In this example, three parameters in the element breached STRING: Application Collection Status parameter thresholds. Object ID: .1.3.6.1.4.1.1031.5.1.6.1 (.iso.org.dod.internet.private.enterprises.1031.5.1.6.1) STRING: Banner display Object ID: .1.3.6.1.4.1.1031.5.1.6.2 (.iso.org.dod.internet.private.enterprises.1031.5.1.6.2) STRING: Port Responding Object ID: .1.3.6.1.4.1.1031.5.1.7.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.7.0) parameter values that triggered notification STRING: true Object ID: .1.3.6.1.4.1.1031.5.1.7.1 (.iso.org.dod.internet.private.enterprises.1031.5.1.7.1) STRING: SSH-1.99-OpenSSH_4.1 Object ID: .1.3.6.1.4.1.1031.5.1.7.2 (.iso.org.dod.internet.private.enterprises.1031.5.1.7.2) STRING: true Object ID: .1.3.6.1.4.1.1031.5.1.8.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.8.0) the parameter state that triggered notification: In this trap, INTEGER: 0 parameter states changed to 0 (OK). Object ID: .1.3.6.1.4.1.1031.5.1.8.1 (.iso.org.dod.internet.private.enterprises.1031.5.1.8.1) INTEGER: 0 Object ID: .1.3.6.1.4.1.1031.5.1.8.2 (.iso.org.dod.internet.private.enterprises.1031.5.1.8.2) INTEGER: 0
time indicating when the state change occurred Object ID: .1.3.6.1.4.1.1031.5.1.9.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.9.0) STRING: Thu, 6 Apr 2006 17:22:12 +0000 name of the RSM that detected the state change Object ID: .1.3.6.1.4.1.1031.5.1.10.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.10.0) STRING: Main Office RSM

names of parameters whose values triggered notification:

Object ID: .1.3.6.1.4.1.1031.5.1.13.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.13.0) name of the element in the Portal STRING: computer1

Chapter 7

Portal events and data integration

245

Trap error codes

Figure 35

Sample trap for an Element State Change event (part 2 of 2)

Object ID: .1.3.6.1.4.1.1031.5.1.14.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.14.0) Performance Manager-specific codes that describe the STRING: 98 problem that triggered the event Object ID: .1.3.6.1.4.1.1031.5.1.14.1 (.iso.org.dod.internet.private.enterprises.1031.5.1.14.1) STRING: 98 Object ID: .1.3.6.1.4.1.1031.5.1.14.2 (.iso.org.dod.internet.private.enterprises.1031.5.1.14.2) STRING: 98 Object ID: .1.3.6.1.4.1.1031.5.1.15.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.15.0) state of the element after the state change INTEGER: 0 Object ID: .1.3.6.1.4.1.1031.5.1.17.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.17.0) parameter threshold that was breached STRING: 0.0 Object ID: .1.3.6.1.4.1.1031.5.1.17.1 (.iso.org.dod.internet.private.enterprises.1031.5.1.17.1) STRING: 0.0 Object ID: .1.3.6.1.4.1.1031.5.1.17.2 (.iso.org.dod.internet.private.enterprises.1031.5.1.17.2) STRING: 0.0
timestamp indicating when the state change occurred Object ID: .1.3.6.1.4.1.1031.5.1.18.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.18.0) STRING: 1144344132703 if the RSM is a clustered RSM, the name of the cluster Object ID: .1.3.6.1.4.1.1031.5.1.19.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.19.0) STRING: type of notification; in this case, enterprise integration Object ID: .1.3.6.1.4.1.1031.5.1.21.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.21.0) INTEGER: 1

Object ID: .1.3.6.1.4.1.1031.5.1.22.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.22.0) in the Performance instance in the Oracle application. STRING: Oracle | Performance

application hierarchy: In this example, the event occurred

Object ID: .1.3.6.1.4.1.1031.5.1.23.0 (.iso.org.dod.internet.private.enterprises.1031.5.1.23.0) detailed description of the problem that caused of the STRING: New Violation: The status of computer1 is OK event

Trap error codes
Table 27 lists the generic parameter error codes that might appear in the bmcPMPortalParameterErrorCode node. For error codes that are specific to the Performance Managers in use on your Portal, see the Help or Getting Started guide for the applicable Performance Managers. Table 27 Parameter error codes (part 1 of 2)
0 success 4 unknown host name 8 database SQL problem—error with the SQL command being run against a database 10 prohibited host—the host used was in the prohibited host list 11 network unavailable—the network was not available at the time of execution 12 network path unavailable—a network path to the named host is not available at this time 98 invalid credentials—authentication credentials were not correct or otherwise could not be used to authenticate execution 99 no data—collection could be performed, but no data was available 101 process down—the process being monitored was unavailable

Error code Description

246

BMC Performance Manager Portal Monitoring and Management Guide

You can use the time controls at the top of the tab to change the time period for viewing alert history. and for parameters. Table 28 lists the event object views and the types of events available on each view. Table 28 account object group element application class parameter Types of events available for object views Element events + + + + + + Parameter events Object view Chapter 7 Portal events and data integration 247 . an element can appear in this list more than once. These parameter values are saved as event history data in the Portal database and appear on the Events tab. The Events tab provides history logs that show. for object groups. By default. Because multiple events can occur on an element. and they are also saved as raw data. s You can view events for the entire account. for a specific time range. An element appears on the Events tab when at least one of its parameters violates an alarm threshold. the RSM sends the parameter value to the Portal (along with the values for other parameters in the application class). this tab shows events from the previous 24 hours. for elements. s A parameter appears on the Events tab when its status changes. when elements and parameters changed to an alert status (warning or alarm) and when they changed to a different alert status.Events tab Table 27 Parameter error codes (part 2 of 2) Error code Description 102 credentials conflict—the credentials being used conflict with another set of credentials already accessing the same resource 103 account locked out—the account being used for authentication is locked out 200 configuration unavailable—configuration needed to execute was not available 210 configuration corrupt—the configuration was available but was corrupt and unusable Events tab When the RSM detects that a parameter has changed to or from an alert (warning or alarm) status.

When you are viewing events for both. s When you select Parameters or Elements + Parameters.events.param. the list can contain a maximum of 300 events. the list includes every parameter that violated its threshold value and the parameter value.limit property on page 326. To change this default value.List content List content When viewing alerts for infrastructure elements.limit property on page 325.limit property on page 325. — When listing parameter events.element. if you had configured notifications so that the Portal would send SNMP traps.element. the list can contain a maximum of 300 events. the icon for element events and the icon for parameter events enable you to differentiate between the two event types. see the portal. s When you select Elements. see the portal. see the portal. Similarly. To change this default value. Figure 36 Infrastructure element view of Events tab 248 BMC Performance Manager Portal Monitoring and Management Guide . Objects to show The Objects to Show list is available from the element view of events and enables you to view element or parameter events. If the values of other parameters also violates threshold settings during the time that the element is in that status. To change this default value. you can use a variety of page controls to adjust the number of alerts on the Events tab. the Portal would send a single trap for the element status change. the description shows the parameter that caused the status to change for the element.events.events. the list can contain a maximum of 600 events (300 of each event type). or both. Figure 36 provides an example of an events list that contains both element and parameter events. the description does not update to show those parameters. — When listing parameter events and element events.param. When listing element events.

When you use this option. These options displays all active alerts for the specified alert type. s To view active and resolved alerts.element. You can filter the list by time by adjusting the time control options.Page controls Alerts to show The Alerts to Show list. the description does not update to show those parameters. select Active Alarms. see the portal.events. Page control Chapter 7 Portal events and data integration 249 . the description shows the parameter that caused the status to change for the element. To change this default value. is available for the account and object group views and enables you to filter the list of events by the type of event. Active Warnings. For each event. or Active Alarms and Warnings.limit property on page 325. Table 29 Page controls for Events tab (part 1 of 2) Description updates the page at the refresh rate or stops the Portal from updating the page Select the On option when you select one of the Active options from the Alerts to Show list. select All. shown in Figure 37. By default. the list shows the events that caused the status to change for the element. the list can contain a maximum of 300 alerts. If the values of other parameters also violated threshold settings during the time that the element is in that status. Alerts to Show list on Events tab s Figure 37 Page controls The Events tab also has the page controls listed in Table 29. To view only active alerts.

250 BMC Performance Manager Portal Monitoring and Management Guide . Page control time controls totals icons and totals for each state during the specified time period. for example. See page 153 for a complete description of the time controls.Page controls Table 29 Page controls for Events tab (part 2 of 2) Description opens the active Events tab in a new window settings that you can change to view events from a different time period Click Update after changing the time-interval controls.

. . . . . . . . . . . . . . . . . . . . . . . getApplicationsForElement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The bpmcli can also query the Portal database for infrastructure objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . refreshDatafeedMetadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . getElements . . . . . . . . . . . addElements: adding multiple elements . . . . . . . . getSubApplications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . getParameterHistory . . . . . . . . . . . . . . bpmcli syntax and arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . exportParameterHistory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . refreshPATROL . . . . . . . . . . . . . Data-manipulation commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 8 BMC Performance Manager Portal command-line interface 8 The BMC Performance Manager Portal command-line interface (bpmcli) enables Portal users and administrators to add and delete infrastructure elements without interacting with the user interface. . . . . . . . . enabling you to integrate the Portal data with other systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . deleteElements: deleting multiple elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . getParameters. . . Data-extraction commands. . . . . This chapter presents the following topics: Preparing the client computer for the bpmcli . . . . . . . . . . . . . . . . . . . . addElements: adding a single element. . . . . . . . . . . . savePassword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . addPATROL . . deleteElements: deleting a single element . . . . . . . . . . . . . . 252 253 254 255 257 260 262 263 264 266 269 270 272 276 277 278 281 282 283 Chapter 8 BMC Performance Manager Portal command-line interface 251 . . . . . . . getPortalVersion . . . . . . . . . . . . . . .

the commands return the following message: (404) Not Found. You do not need to use the Portal or RSM computer. install JRE 1.bat (Windows) or bpmcli. NOTE If you try running the bpmcli against earlier versions of BMC Performance Manager Portal. but you must run bpmcli from that location.sh (Solaris) You can copy the files to any location.Preparing the client computer for the bpmcli Preparing the client computer for the bpmcli Before you can use the bpmcli to manage infrastructure objects. You can find the files in the following locations: — product media for your operating system: s s s Windows DVD: util\BPM_CLI Solaris DVD: util/BPM_CLI — Portal application server: s s On Windows: %BMC_PORTAL_KIT_HOME%\appserver\util\BPM_CLI On Solaris: $BMC_PORTAL_KIT_HOME/appserver/util/BPM_CLI — RSM computer (Windows only): c:\Program Files\BMC Software\Remote Service Monitor\RSMversionNumber \util\BPM_CLI To prepare the client computer to run the bpmcli 1 Navigate to the bpmcli files on the application server.jar bpmcli. 2 Copy the following files to the client computer: s s bpmcli.5. Before you begin s If necessary. RSM computer. Locate the necessary files for the bpmcli.0_06 or later on the client computer and verify that Java is in the path. you must prepare the client computer so that it meets the necessary requirements for the utility. You can install the bpmcli on any Microsoft Windows or Sun® Solaris computer that has network access to the Portal. 252 BMC Performance Manager Portal Monitoring and Management Guide . or installation media.

-login UserName specifies the user who is executing the command s Only users who are members of the Full Access user group can execute data manipulation bpmcli commands. Table 30 Argument -portal PortalWebServerName Basic arguments for bpmcli commands (part 1 of 2) Definition specifies the fully-qualified host name of the Portal (for multiplecomputer installations. The basic command-line syntax for the bpmcli is as follows: bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c command -q Table 30 lists the basic arguments that you can use with any bpmcli command. The command might also have additional arguments. Other arguments are included with their corresponding commands. The specified user can execute bpmcli commands against objects in the user’s account. Users who are members of the Full Access or Read Only user group can access the data extraction commands. and the command that you want to execute. the Portal web server) When you run the bpmcli from a Windows Portal web server. you must specify this argument. 443. and port number necessary to communicate with the Portal. When run from a computer other than the Portal web server or from any Solaris computer. -p PortNumber specifies the port number on which the bpmcli receives data from the Portal web server The port number is required only if the web server does not use the default port. bpmcli assumes localhost.bpmcli syntax and arguments bpmcli syntax and arguments Each complete command line contains arguments that specify the Portal host name. See “Datamanipulation commands” on page 254 and “Data-extraction commands” on page 270. you can omit the Portal host name. s s Chapter 8 BMC Performance Manager Portal command-line interface 253 . See page 270. See page 254. user credentials.

To execute bpmcli commands in a batch file. Only users who are members of the Full Access user group can execute the bpmcli commands in this section. not recommended) uses HTTP to communicate with the Portal By default. ‘-ep’) or when the password contains only one character (for example.com -login user -pass '-ep' -c addElements -h databaseserver.Data-manipulation commands Table 30 Argument Basic arguments for bpmcli commands (part 2 of 2) Definition specifies the password for the user Enclose the password in single quotes (' ') when a password contains a special character (for example. Table 31 Command addElements: adding a single element addElements: adding multiple elements Data-manipulation bpmcli commands (part 1 of 2) Syntax Page bpmcli -portal PortalWebServerName -p PortNumber -login UserName 255 -pass UserPassword -c addElements -h ElementHostName -e ElementName -ep ProfileName -r RSMName -platform PlatformName -g ObjectGroupName bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c addElements -platform PlatformName -f FileName 257 254 BMC Performance Manager Portal Monitoring and Management Guide . the bpmcli uses HTTPS to communicate with the Portal.acme. Data-manipulation commands The commands in this section enable you to add data to and delete it from the Portal. When you specify -unsecure. -unsecure (optional. All commands are case sensitive. 'g'). Table 31 shows the syntax for each complete bpmcli command that falls into this category (the specific command is shown in bold text). you must add a call to the individual commands.com -e DatabaseServer -ep Databases -platform "Windows 2000" -r "Portal RSM" -g Databases -pass UserPassword -c command -q specifies the command (optional) suppresses return messages Do not use this argument with data extraction commands. Users who are only members of user-defined user groups cannot run the bpmcli commands. the bpmcli transmits passwords as plain text.acme. For example: bpmcli -portal myportal.

Syntax bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c addElements -h ElementHostName -e ElementName -ep ProfileName -r RSMName -platform platformName -g ObjectGroupName Chapter 8 BMC Performance Manager Portal command-line interface 255 . If you do not provide the element name. bpmcli uses the host name or IP address for the element name.addElements: adding a single element Table 31 Command Data-manipulation bpmcli commands (part 2 of 2) Syntax bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c addPATROL -email "EmailAddresses" -f AgentFileName -r RSMName -g ObjectGroupName Page 260 addPATROL deleteElements: deleting a bpmcli -portal PortalWebServerName -p PortNumber -login UserName single element -pass UserPassword -c deleteElements -e ElementName deleteElements: deleting multiple elements bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c deleteElements -f FileName 262 263 264 266 refreshDatafeedMetadata bpmcli -portal PortalWebServerName -p PortNumber -login adminName -pass adminPassword -c refreshDatafeedMetadata refreshPATROL bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c refreshPATROL -email "EmailAddresses" -f ElementFileName bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c savePassword savePassword 269 addElements: adding a single element When adding a single element. you must provide the following properties: s s s s s host name or IP address of the element existing profile name to apply to the element existing RSM or RSM cluster to monitor the element operating system of the element existing object group that you will assign to the element You can also provide the element name.

You must specify this argument if you do not include the -e argument. -g ObjectGroup name of the existing object group to which the elements will belong Enclose multiple-word object group names in quotation marks. you can use the arguments in Table 32 with the addElements command. 256 BMC Performance Manager Portal Monitoring and Management Guide . -platform PlatformName name of the platform as it appears in the following list: s s s s s s s s s s s s s s s s AIX HP-UX Linux Network Firewall Network Load Balancer Network Router Network Switch Open VMS Other Solaris Storage Tru64 UNIX Windows Windows 2000 Windows 2003 Windows XP Enclose multiple-word platform names in quotation marks. you must include the -e argument. Table 32 Argument -h ElementHostName addElements arguments for adding a single element Definition fully-qualified host name or IP address of the element If you do not include this optional argument. you must include the -h argument.addElements: adding a single element Arguments In addition to the basic bpmcli arguments shown in Table 30 on page 253. -ep ProfileName name of an existing element profile Enclose multiple-word profile names in quotation marks. -r RsmName name of an existing RSM or RSM cluster to monitor the elements Enclose multiple-word RSM names in quotation marks. -e ElementName display name for the element If you do not include this optional argument. Enclose multiple-word element names in quotation marks.

PlatformName Figure 38 on page 258 contains an example of valid content for the CSV file. [ElementDisplayName]. Chapter 8 BMC Performance Manager Portal command-line interface 257 . RsmName. ObjectGroupName. profile [ProfileName] s addElements: adding multiple elements To add multiple elements. you must first list each element’s properties in a commaseparated value (CSV) file.com user name: user password for user: user host name of the element: databaseserver. element [ElementName]. platform [PlatformName]. msg [added element]. element [ElementName]. user [UserName]. host [HostName].addElements: adding multiple elements Sample command The following command adds a single element that has the following properties: s s s s s s s s s web server name of the Portal: myportal.acme. group [GroupName]. using the following format.acme. so the bpmcli assumes that the port is the default. user [UserName]. msg [ReasonForFailure].com -login user -pass user -c addElements -h databaseserver.acme. rsm [RsmName].acme. platform [PlatformName]. profile [ProfileName] FAILURE. group [GroupName].com element name: DatabaseServer element profile name: Databases RSM: Portal RSM platform: Windows 2000 object group name: Databases bpmcli -portal myportal. one of the following messages is displayed. rsm [RsmName]. and then specify that file name in the command: HostName or IPAddress. ElementProfileName. host [HostName]. Return messages After execution of the command.com -e DatabaseServer -ep Databases -platform "Windows 2000" -r "Portal RSM" -g Databases The port is not specified. 443. depending on whether the addition was successful: s SUCCESS.

com. If you omit a property from the file. an error message is displayed.com."Windows Servers". and \n\r."Acme RSM". See Figure 38. and the file must contain five commas."" computer2. that property applies to all elements in the file. If a required property is not specified at the command prompt or in the file. If a property is specified in the command line and not in the file. s s s Any value that you specify on the command line is superseded by an existing value for the property in the CSV file."Windows Settings".acme."Windows Servers". \n. If the file does not contain the following properties. the command-line value is used.. Files that contain multi-byte characters must be saved in UTF-8 format.Acme1.acme. If the file does not contain the element name."UNIX Settings"."Linux" The following rules apply to the CSV file: s The file must contain the host name or IP address of each element."AIX" computer3."Acme RSM". you must still include the comma delimiter for that property.addElements: adding multiple elements Figure 38 Sample CSV file for adding elements with bpmcli computer1.acme."My Computer". the bpmcli uses the host name or IP address for the element name. s s s s s Syntax bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c addElements -platform PlatformName -f FileName 258 BMC Performance Manager Portal Monitoring and Management Guide .com."Windows Settings". The bpmcli supports the following end-of-line terminators: \r."UNIX Servers". you must specify the missing properties on the command line: — group name — RSM or RSM cluster name — element profile name — platform name When you specify the property from the command line."Acme RSM".

msg [added element]. -f CsvFileName Sample command bpmcli -portal myportal. group [GroupName]. platform [PlatformName]. you can use the arguments in Table 33 with the addElements command. msg [ReasonForFailure].txt Return messages After execution of the command. platform [PlatformName]. the bpmcli returns one of the following messages for each element specified in the CSV file. -r RsmName name of an existing RSM or RSM cluster to monitor the elements (if not specified in the file) Enclose multiple-word RSM names in quotation marks. group [GroupName]. Table 33 addElements arguments for adding multiple elements name of the CSV file that contains the element properties Files that contain multi-byte characters must be saved in UTF-8 format. -platform PlatformName name of the platform as it appears in Table 32 on page 256 Enclose multiple-word platform names in quotation marks. -g ObjectGroup name of the existing object group to which the elements will belong (if not specified in the file) Enclose multiple-word object group names in quotation marks. element [ElementName]. host [HostName]. rsm [RsmName]. host [HostName]. user [UserName]. user [UserName]. -h ElementHostName -ep ProfileName fully-qualified host name or IP address of the element name of an existing element profile Enclose multiple-word profile names in quotation marks. profile [ProfileName] s Chapter 8 BMC Performance Manager Portal command-line interface 259 .acme.com -login user -pass user -c addElements -platform AIX -f NewElements. rsm [RsmName].addElements: adding multiple elements Arguments In addition to the basic bpmcli arguments shown in Table 30 on page 253. element [ElementName]. profile [ProfileName] FAILURE. depending on whether the addition was successful: s SUCCESS.

in the order listed. When the add operation is complete on the Portal. but the addPATROL command requires slightly different information. Successful completion of the command does not imply that the add operation was completed on the Portal. s s s Table 34 Value element name (optional) host name the PATROL Agent host name or IP address This value cannot exceed 256 characters. The bpmcli supports the following end-of-line terminators: \r. password PATROL API Encrypted (PEM API) password If you specify a shared credential instead of a user name. If the file does not contain the element name. and authentication (user name and password or shared credential) for each PATROL Agent. Each row in the file must contain the comma-separated values in Table 34. The Portal synchronizes the thresholds for the newly added PATROL integration Performance Managers with their corresponding values on the PATROL Agents. as follows: s The file must contain the host name. port number. the Portal sends a summary report to each recipient identified by the -email argument. This value cannot exceed 256 characters. leave this value blank. port number user name or shared credential the PATROL Agent port number the user name used to log on to the PATROL Agent or the name of a shared credential This value cannot exceed 256 characters. \n. The CSV file is similar to that described in “Using a CSV file to discover PATROL Agents” on page 37. The PATROL integration Performance Managers assigned to the elements are based on the KM application classes found on the corresponding PATROL Agents. the bpmcli uses the host name or IP address for the element name. and \n\r. Values required for CSV input file for the addPATROL CLI command Description the element used in the Portal This value cannot exceed 256 characters.addPATROL addPATROL The addPATROL command initiates the process that adds elements to the Portal based on a list of PATROL Agents that you specify in a CSV file. Successful completion of this command means that the add operation was started on the Portal. 260 BMC Performance Manager Portal Monitoring and Management Guide .

threshold. formatted in HTML.exclude.properties file. see the padm. the Portal synchronizes the thresholds for all parameters that it discovers for the specified elements.list property on page 342 for more information.update.locking property on page 341.migrate. you can run only one synchronization operation (addPATROL or refreshPATROL) at a time.migrate. The following circumstances can cause an error: s insufficient rights: The specified user does not have Full Access rights to element properties. each user in the list receives an email message. s Syntax bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c addPATROL -email "EmailAddresses" -f AgentFileName -r RSMName -g ObjectGroupName Arguments In addition to the basic bpmcli arguments shown in Table 30 on page 253.addPATROL By default. By default. that contains the Summary report that the Portal displays following PATROL Agent discovery. To configure the Portal to enable multiple synchronization operations. Chapter 8 BMC Performance Manager Portal command-line interface 261 . -email ListOfEmailAddresses (optional) comma-separated list of email addresses enclosed in quotation marks If you include this argument. You can provide a list of parameters to exclude from the synchronization process by updating the padm. you can use the arguments in Table 35 with the addPATROL command. multiple synchronization processes: Another synchronization operation is already in progress. Table 35 Argument -f CsvFileName addPATROL arguments (part 1 of 2) Description name of the CSV file that contains the PATROL Agent properties Files that contain multibyte characters must be saved in UTF8 format. See the padm.

the bpmcli returns the following message: PATROL add element process started If an error occurs when attempting to start the add process. you must provide the element name for the element. deleteElements: deleting a single element When deleting a single element. an error or warning message is displayed. If problems were encountered with a particular element. Sample command bpmcli -portal myportal.you@acme. When the add process is finished. -r RsmName -g ObjectGroup name of the existing object group to which the elements will belong (if not specified in the file) Enclose multiple-word object group names in quotation marks.acme.deleteElements: deleting a single element Table 35 Argument addPATROL arguments (part 2 of 2) Description name of an existing RSM or RSM cluster to monitor the elements Enclose multiple-word RSM names in quotation marks. the email report contains an error description for each affected element.com" Return message After execution of the command.txt -g myGroup -r myRsm -email "me@acme. You cannot delete an element by specifying its host name or IP address. a summary report is emailed to each recipient identified in the -email argument.com -login user -pass myPassword -c addPATROL -f myElements. Syntax bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c deleteElements -e ElementName 262 BMC Performance Manager Portal Monitoring and Management Guide .com.

Chapter 8 BMC Performance Manager Portal command-line interface 263 .deleteElements: deleting multiple elements Argument In addition to the basic bpmcli arguments shown in Table 30 on page 253. \n\r. one of the following messages is displayed. you can use the argument in Table 35 on page 261 with the deleteElements command. element [ElementName] FAILURE. element [ElementName] s deleteElements: deleting multiple elements To delete multiple elements. user [UserName]. \n.com The bpmcli supports the following end-of-line terminators: \r. Figure 39 Sample CSV file for deleting elements with bpmcli "My Computer" Acme1 computer3. you must provide a CSV file that contains the element name for each element to delete.acme. depending on whether the addition was successful: s SUCCESS.com -login user -pass user -c deleteElements -e MyElement Return messages After execution of the command. msg [deleted element]. user [UserName]. Sample command bpmcli -portal myportal.acme. The CSV file cannot contain host names or IP addresses. msg [ReasonForFailure]. Table 36 Argument -e ElementName deleteElements argument for deleting a single element Description element to delete Enclose multiple-word element names in quotation marks.

element names. application classes. msg [ReasonForFailure]. Run this command as often as necessary to keep the metadata tables current with the Portal. element [ElementName] FAILURE. user [UserName].refreshDatafeedMetadata Syntax bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c deleteElements -f FileName Arguments In addition to the basic bpmcli arguments shown in Table 30 on page 253. msg [deleted element]. element [ElementName] s refreshDatafeedMetadata This command initiates the process that updates the Continuous Data Export (CDE) metadata tables with new element and parameter data.txt Return messages After execution of the command.com -login user -pass user -c deleteElements -f Elements. Table 37 Argument -f FileName deleteElements argument for deleting multiple elements Description file that contains names of element to delete Sample command bpmcli -portal myportal. 264 BMC Performance Manager Portal Monitoring and Management Guide . described on page 190. The metadata tables include the account name. and parameters that correspond to the data exported by the Continuous Data Export utility. TIP To ensure that you capture all changes. the bpmcli returns one of the following messages for each element in the CSV file. user [UserName].acme. you can use the argument in Table 37 with the deleteElements command. depending on whether the deletion was successful: s SUCCESS. run a nightly script that executes this command.

com -login superadmin -pass superadmin -c refreshDatafeedMetadata -status s s Return messages After execution of the command.acme.com -login superadmin -pass superadmin -c refreshDatafeedMetadata bpmcli -portal myportal. Arguments In addition to the basic bpmcli arguments shown in Table 30 on page 253.com -login superadmin -pass superadmin c refreshDatafeedMetadata -abort bpmcli -portal myportal.acme. Run "-c refreshDatafeedMetadata -status" to get updates on the progress. you can use the argument in Table 38 with the refreshDatafeedMetadata command.acme. you must provide credentials for a Portal administrator. Table 38 Argument -abort -status deleteElements argument for deleting multiple elements Description stops the active refresh operation returns information about the progress of the current refresh operation Sample commands s bpmcli -portal myportal.refreshDatafeedMetadata Syntax bpmcli -portal PortalWebServerName -p PortNumber -login adminName -pass adminPassword -c refreshDatafeedMetadata To execute the refreshDatafeedMetadata command. the bpmcli returns the following message: Request submitted. Chapter 8 BMC Performance Manager Portal command-line interface 265 .

the return message could contain one of the following status values: s s s Completed In progress Failed refreshPATROL The refreshPATROL command initiates the process that synchronizes application classes and threshold values between PATROL integration Performance Managers and their corresponding PATROL Agents.bmc. 266 BMC Performance Manager Portal Monitoring and Management Guide . the bpmcli returns the following message: ==================================================================== Datafeed Target: DB: jdbc:oracle:thin:@south-a2f.PARAMETER_DETAIL ==================================================================== Status: Completed Process start: 4/12/07 5:28:33 PM CDT Process end: 4/12/07 5:28:33 PM CDT Number of accounts processed: created: 0 updated: 2 Number of elements processed: created: 0 updated: 4 Number of applications processed: created: 0 updated: 12 Number of parameters processed: created: 0 updated: 35 ==================================================================== Depending on the status of the utility.com:1521:BMCPDS USER: DATAFEED_USER TABLE: DATAFEED_USER.com:1521:BMCPDS USER: DATAFEED_USER TABLE: DATAFEED_USER.PARAMETER_DETAIL ==================================================================== Status: Aborted Process start: 4/12/07 5:28:33 PM CDT Process end: 4/12/07 5:28:33 PM CDT Number of accounts processed: created: 0 updated: 2 Number of elements processed: created: 0 updated: 4 Number of applications processed: created: 0 updated: 12 Number of parameters processed: created: 0 updated: 35 ==================================================================== After execution of the command with a -status argument. Successful completion does not imply that the synchronization operation was completed successfully. Successful completion of this command means that the refresh operation was started on the Portal.refreshPATROL After execution of the command with a -abort argument.bmc. the bpmcli returns the following message: ==================================================================== Datafeed Target: DB: jdbc:oracle:thin:@south-a2f.

migrate.exclude. see “padm. \n. which contains the detailed status about the threshold synchronization. the Portal refreshes the thresholds for all parameters that it discovers for the specified elements.refreshPATROL When issuing the refreshPATROL command.migrate. The following rules apply to data synchronization: s You cannot run this command if the Portal is in the process of a synchronization process that was initiated from the UI (Refresh PATROL Integration). By default. During synchronization that was initiated from the refreshPATROL command. the bpmcli uses the host name or IP address for the element name.properties file. you can run multiple synchronization operations at a time (addPATROL or refreshPATROL).locking” on page 341. You can provide a list of parameters to exclude from the refresh process by updating the padm. the command attempts to synchronize every element to which a PATROL integration Performance Manager has been assigned. multiple synchronization processes: This error occurs only if you disable multiple synchronization operations. you can also request a Summary report. both processes will run. you can specify a text file that contains a list of the element names to process. you cannot use the UI to initiate another synchronization process. If two users initiate concurrent refreshPATROL processes.list property on page 342 for more information. If you specify an email address. and \n\r. If you do not specify a file. The following rules apply to the file: s The file must contain the host name or IP address of each element. s s By default. See the padm. s Syntax bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c refreshPATROL -email "EmailAddresses" -f ElementFileName Chapter 8 BMC Performance Manager Portal command-line interface 267 . s s The following circumstances can cause an error: s insufficient rights: The specified user does not have full-access rights to element properties.threshold.update. The bpmcli supports the following end-of-line terminators: \r. If the file does not contain the element name. To configure the Portal to enable only one synchronization operation at a time.

the bpmcli returns the following message: PATROL threshold refresh started If an error occurs when the command attempts to start the refresh process. Sample command bpmcli -portal myportal.com -login user -pass user -c refreshPATROL -email "myemail@acme. When the synchronization process is finished. For any invalid element names. a summary report is emailed to each recipient identified in the -email argument.acme.com" -f elements. -f FileName (optional) UTF-8 file that contains a list of the element names to synchronize. If problems were encountered with a particular element. an error is included in the Summary report. that contains the Summary report that the Portal displays following threshold synchronization.refreshPATROL Arguments In addition to the basic bpmcli arguments shown in Table 30 on page 253. the email report contains an error description for each affected element. formatted in HTML. 268 BMC Performance Manager Portal Monitoring and Management Guide . enclosed in quotation marks If you include this argument. you can use the arguments in Table 39 with the refreshPATROL command.com.acme. Otherwise. an error or warning message is displayed.youremail. Table 39 Argument refreshPATROL arguments Description -email ListOfEmailAddresses (optional) comma-separated list of email addresses. the command synchronizes all elements on which PATROL integration Performance Managers are collecting parameter values.txt Return message After execution of the command. each user in the list receives an email message. one element per line Use this option to limit the elements synchronized to those listed in the file.

pw file to a different directory on the same computer. The bpmcli. you can omit the -pass password argument when you use the corresponding user name to execute other bpmcli commands.acme.pw file on the computer on which it was created. the bpmcli returns one of the following messages.com -login user -pass user -c savePassword Return messages After execution of the command.pw file can store a single password for different users.pw) on the client computer. You can move the bpmcli. After using this command to save the bpmcli.savePassword savePassword The savePassword command saves the user password in an encrypted file (bpmcli.jar file. Observe the following rules for using the bpmcli. in the directory where you placed the bpmcli. Syntax bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c savePassword Arguments This command uses only the basic bpmcli arguments shown in Table 30 on page 253. you cannot use the passwords that you saved from the original computer.pw file: s s s You can use a saved bpmcli.pw file to another computer. If you copy the bpmcli. depending on whether the command was successful: s s saved password for userName ERROR: failed to save password for userName command: -c savePassword -login UserName -pass password Chapter 8 BMC Performance Manager Portal command-line interface 269 . and subsequent use of the savePassword command for the same user overwrites the existing saved password. Sample command bpmcli -portal myportal. The savePassword command has no additional arguments.pw file.

the second line contains the returned values. 270 BMC Performance Manager Portal Monitoring and Management Guide . you must first execute the getElements. Many of these commands depend on the return values of another command for their arguments. and the arrows show where the returned value is used in the subsequent command. getApplicationsForElement. Users who are members of only user-defined user groups cannot run the bpmcli commands. EXAMPLE To retrieve parameter history values. The first line in each group is the command. Figure 40 Using data-extraction commands to retrieve input arguments for subsequent commands Users that are members of the Full Access or Read Only user group can access the data-extraction commands. as illustrated in Figure 40. and getSubApplications commands to retrieve the GUIDs necessary to run the subsequent commands.Data-extraction commands Data-extraction commands The commands in this section enable you to retrieve data from the database.

"null" 3.acme."1aa9wr8228ax".acme."1aa9wr8228ax"."null" "1aa9wr8228bi"."Network"."1aaaaZZZZml4"."OK" Chapter 8 BMC Performance Manager Portal command-line interface 271 . Using a GUID that was returned from the previous command."Solaris"."Swap". Using a GUID that was returned from the previous command."Processors". issue commands similar to the following scenario: 1.acme."1aaaaZZZZml4"."1aa9wr8228ax"."1aa9wr8228ax".com"."null" "1aa9wr8228dc"."Memory"."1aa9wr8228ax"."1aa9wr8228ax"."null" "1aa9wr8228c2"."1aa9wr8228ax".0". type the following command to retrieve the GUIDs for the child applications in the application class: bpmcli -login user -pass user -portal myportal."1aa9wr8228ax".acme."Paging".acme."CPU".Data-extraction commands EXAMPLE To retrieve the value for the CPU Usage parameter. type the following command to retrieve the parameters for the application class: bpmcli -login user -pass user -portal myportal. type the following command to retrieve the GUIDs for the top-level applications on the element: bpmcli -login user -pass user -portal myportal."Data Storage"."1aa9wr8228ax"."null" "1aa9wr8228cv"."CPU usage"."1aa9wr8228ax".com -c getApplicationsForElement -guid x0et6qwx2u612 The following result is returned: "dr2al_solaris_cmdshell_base"."0."1aa9wr8228ax"."null" "1aa9wr8228bn"."null" 2."1aa9wr8228ax".com -c getSubApplications -guid 1aaaaZZZZml4 The following result is returned: "1aa9wr8228bq"."1aa9wr8228ax". "1aaaaZZZZml41Og8On640f49wr8228b0".com -c getElements The following result is returned: "mickey"."null" 4."null"."null" "1aa9wr8228c1".com -c getParameters -guid 1aa9wr8228b0 The following result is returned: "1aaaaZZZZml41Og8On640f49wr8228ay"."x0et6qwx2u612". Type the following command to retrieve the GUID for the elements on the Portal: bpmcli -login user -pass user -portal myportal."1aa9wr8228ax"."1aa9wr8228ax"."System Performance"."null" "1aa9wr8228b0"."mickey."null". Using a GUID that was returned from the previous command."1aa9wr8228ax".

the exportParameterHistory command exports historical summarized data to the same external database. which is described on page 190). 272 BMC Performance Manager Portal Monitoring and Management Guide . For each parameter in the external database. which complements the Continuous Data Export utility (CDE. The Continuous Data Export utility continuously writes specified raw parameter values to an external database. Some of the commands have no dependencies on other commands and no other commands have any dependencies on them for extracting data from the database. Table 40 Command exportParameterHistory Data-extraction bpmcli commands Order of Execution Syntax NA bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c exportParameterHistory -startDate "yyyy/mm/dd hh:mm:ss" bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c getApplicationsForElement -guid ElementGuid bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c getElements bpmcli -portal PortalWebServerName -p PortNumber -login adminName -pass adminPassword -c getParameterHistory -guid ParameterGuids -minutes MinutesOfHistory -summarize bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c getParameters -guid ApplicationClassGuid bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c getPortalVersion bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c getSubapplications -guid ApplicationClassGuid Page 272 getApplicationsForElement 2 276 getElements 1 277 getParameterHistory 5 278 getParameters 4 281 getPortalVersion NA 282 getSubApplications 3 283 exportParameterHistory This data extraction command runs the Historical Data Export utility. Table 40 lists the data-extraction commands and the order in which they must be executed.exportParameterHistory In addition to the syntax for each bpmcli command.

you configure the Portal to continuously export raw data values to an external database. it will end. You also configure the Portal to continuously export raw data values for selected parameters to an external database. EXAMPLE You might run the exportParameterHistory command in the following scenarios: s On February 1. and then ends. To configure the exportParameterHistory and refreshDatafeedMetadata commands to run without a CDE database instance. The utility adds summarized data values to the external database until it finds parameter data. If you specify January 1 to fill in the data gaps.exportParameterHistory NOTE You can also configure the Historical Data Export utility to run in the absence of a CDE database instance. you begin using the Portal to monitor your infrastructure. The exportParameterHistory command looks for the oldest data point in the external database and compares it with the start date. To populate the external database with the historical data values between February 1 and June 1. you begin using the Portal to monitor your infrastructure. Figure 41 January 1 How the Historical Data Export utility uses the startData argument June The utility does not add data for these gaps. you run the exportParameterHistory command. Chapter 8 BMC Performance Manager Portal command-line interface 273 . On February 1. the utility adds summarized values for January 1 to January 10. Period with data Period without data Syntax bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c exportParameterHistory -startDate "yyyy/mm/dd hh:mm:ss" To execute the exportParameterHistory command. if you specify January 1 as the start date and the utility finds data values for January 10. On June 1. the utility will stop when it finds data. On June 1. As illustrated in Figure 41. If the Historical Data Export finds data at the start date. s You cannot use the exportParameterHistory command to fill in data gaps. you must provide credentials for a Portal administrator. you modify the Continuous Data Export utility to export additional parameters to the external database. see “Alternate configuration settings for Historical Data Export commands” on page 275. you run the exportParameterHistory command. To capture parameter data values for the newly specified parameters.

acme. the following message is returned: No external datasource configuration files found! 274 BMC Performance Manager Portal Monitoring and Management Guide .com -login superadmin -pass superadmin -c exportParameterHistory -startDate "2007/02/01 00:00:00" s The following command aborts the current export operation: bpmcli -portal myportal.acme. you can use the arguments in Table 41 with the exportParameterHistory command. Table 41 Arguments -startDate dataStartDate exportParameterHistory arguments Description start date on which to synchronize historical data for all parameters in the external database Use the following format to specify the date and enclose the date in quotation marks: "yyyy/mm/dd hh:mm:ss" The argument uses the time zone of the Portal administrator who is executing the command.com -login superadmin -pass superadmin -c exportParameterHistory -status Return messages If you did not configure the datafeed.acme. beginning at February 1.properties file.com -login superadmin -pass superadmin -c exportParameterHistory -abort s The following command returns information about the current data export operation: bpmcli -portal myportal. 2007: bpmcli -portal myportal. -abort -status stops the active export operation returns information about the progress of the current export operation Sample commands s The following command exports historical data.exportParameterHistory Arguments In addition to the basic bpmcli arguments shown in Table 30 on page 253.

exportParameterHistory

After execution of the command with a -status argument, the bpmcli returns a message similar to the following example:
=============================================================== Status: In progress Process start: 2/20/07 5:02:12 PM CST Process end: 2/20/07 5:02:27 PM CST Number of parameters processed: 1 of 3 Number of data points processed: 0 of 43 ===============================================================

Depending on the status of the utility, the return message could contain one of the following status values:
s s s s

Aborted Completed In progress Failed

Alternate configuration settings for Historical Data Export commands
The exportParameterHistory and refreshDatafeedMetadata commands update the CDE database instance with historical parameter data. These commands process the parameters that are defined by the ParameterDefinitionName property. For more information about this property, see “To configure a target database” on page 197. Use the following procedure to configure the utility scripts to run these commands to run in the absence of a CDE database instance.

To configure the utility scripts to run Historical Data Export commands without a CDE database instance 1 In your JDBC target property file, comment out the
DB.TABLE.NAME=PARAMETER_DETAIL property, as shown in the following example:
# Table used for Continuous Data Extract #DB.TABLE.NAME=PARAMETER_DETAIL

2 Ensure that the SUMMARYTABLE property is configured with default values, as
shown in the following example:
# Table used for Historical Data Extract DB.SUMMARYTABLE.NAME=PARAMETER_SUMMARY

Chapter 8 BMC Performance Manager Portal command-line interface

275

getApplicationsForElement

3 If you changed the values for the thread and connection pool sizes, change them to
the following default values:
s s

portal.datafeed.threadpool.size=10 DB.BATCHSIZE=1000

4 Restart the Portal application server.

getApplicationsForElement
This data extraction command returns the application classes and corresponding GUIDs for each top-level application class on an element. The command does not return the entire hierarchy for the application classes.

NOTE
Do not use the -q (quiet) argument when executing a data extraction command; otherwise, the command returns nothing.

Syntax
bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c getApplicationsForElement -guid ElementGuid

Arguments
In addition to the basic bpmcli arguments shown in Table 30 on page 253, you can use the argument in Table 42 with the getApplicationsForElement command. Table 42
Argument -guid guid

getApplicationsForElement argument
Description GUID for the infrastructure element

Sample command
bpmcli-portal myportal.acme.com -login user -pass user -c getApplicationsForElement -guid E4smxqZZZE0FxkA8o2z60erunkhzz0wy

276

BMC Performance Manager Portal Monitoring and Management Guide

getElements

Return messages
After successful execution of the command, the bpmcli returns the following message for each top-level application class on the element:
"InternalApplicationClassName","ApplicationClassGuid", "ParentApplicationClassGuid","RootApplicationClassGuid", "ReconciliationId"
s

The value RootApplicationClassGuid will equal that of ApplicationClassGuid. Because this command returns the top-level application class, the value for ParentApplicationClassGuid will be null. Ping, Microsoft SQL Server, and Unix Process–Using Command Shell are examples of InternalApplicationClassName.

s

s

If an error occurs, one of the following messages is returned: ========================================================
ERROR: Element: 'Guid' does not exist or does not belong to this account.

============================================================== ========================================================
ERROR: BMC-MOP10001E:Authentication failed for user <user name>.

==============================================================

getElements
This data extraction command returns the names for all elements in the account of the user executing the command. You can limit the results of the command by using standard operating system commands to filter the results. For example, in Figure 40 on page 270, grep is piped through the getElement command to limit the results to a specific element.

NOTE
Do not use the -q (quiet) argument when executing a data extraction command; otherwise, the command returns nothing.

Chapter 8 BMC Performance Manager Portal command-line interface

277

getParameterHistory

Syntax
bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c getElements

Arguments
This command uses only the basic bpmcli arguments shown in Table 30 on page 253.

Sample command
bpmcli -c getElements -portal myportal.acme.com -login user -pass user

Return messages
After successful execution of the command, the bpmcli returns the following message for each element in the account:
"ElementName","ElementGuid","ElementHostName", "ElementOperatingSystem","ElementProfileName","ReconciliationId"

If an error occurs, the following message is returned:
=================================================================== ERROR: BMC-MOP10001E:Authentication failed for user <user name>. ===================================================================

getParameterHistory
This data extraction command returns parameter history for the specified parameters.
s

If you specify the -summarize argument, the command returns available summarized data values for the specified number of minutes. — Raw data is summarized at 30-minute intervals on the hour and half hour. Should you request summarized data at 11:42 A.M., the return message contains data points for the summarized points and a point that summarizes the last 12 minutes of raw data. — If you want to compare the summarized return data with the parameter history table, specify at least 24 hours in the parameter history table.

278

BMC Performance Manager Portal Monitoring and Management Guide

getParameterHistory

s

If you do not specify the -summarize argument, the command returns raw data values for the specified number of minutes.

NOTE
Do not use the -q (quiet) argument when executing a data extraction command; otherwise, the command returns nothing.

If the value specified in the -minutes argument spans more data than the amount actually stored in the Portal database for the parameter, the command returns all the available data and does not return an error message. This condition can occur for new parameters or when you request data for a period that exceeds the retention period. Depending on when you run this command, the amount of summarized data returned by the command might be less than you expected. See “Retention policies” on page 145 and “Data summarization” on page 144 for more information about how the Portal summarizes and retains data.

Syntax
bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c getParameterHistory -guid ParameterGuids -minutes MinutesOfHistory -summarize

Arguments
In addition to the basic bpmcli arguments shown in Table 30 on page 253, you can use the arguments in Table 43 with the getParameterHistory command. Table 43
Argument -minutes MinutesOfHistory -guid ParameterGuids

getParameterHistory arguments
Description number of minutes of parameter history data to return list of parameter GUIDs To specify more than one parameter, separate the GUIDs with commas and enclose the entire argument in "".

-summarize

returns summarized data If you do not specify this argument, the command returns raw data values.

Chapter 8 BMC Performance Manager Portal command-line interface

279

getParameterHistory

Sample commands
The following command retrieves summarized parameter history for the previous 48 hours for three parameters:
bpmcli -portal myportal.acme.com -login user -pass user -c getParameterHistory -guid "D5c4o05ZZKa89m12sin50esmep9qr0pn, D5c4o05ZZKa89m12sin50esmep9qr0pp, D5c4o05ZZKa89m12sin50esmep9qr0pl" -minutes 2880 -summarize

The following command retrieves raw parameter history data for the previous 48 hours for three parameters:
bpmcli -portal myportal.acme.com -login user -pass user -c getParameterHistory -guid "E4smxqZZZE0FxkA8o2z60erunkhzz0wy, E4smxqZZZE0FxkA8o2z60erimlhzz0yd, E4smxqZZZE0FxkA8o2z60erybjhzz0zz" -minutes 2880

Return messages
Commands that specify the -summarize argument return fewer data points than commands that do not specify the -summarize argument. If you specify a GUID that does not have any history data, the bpmcli does not provide a return message for the corresponding parameter. After successful execution of the command, the bpmcli returns the following message for each parameter:
"ParameterGuid","NumberOfDataPoints","TimestampForDataPoint1","ValueF orDataPoint1","TimestampForDataPoint2","ValueForDataPoint2",…

The TimestampForDataPoint2 is the UNIX Epoch (the number of milliseconds since January 1, 1970 00:00:00 GMT) for the value that was measured by the RSM or summarized by the Portal.

EXAMPLE
"D5c4o05ZZKa89m12sin50esmep9qr0pp","6","1159405200000","1.0","1159408800000" ,"1.0","1159412400000", \ "1.0","1159416000000","1.0","1159419600000","1.0","1159452000000","1.0" "D5c4o05ZZKa89m12sin50esmep9qr0pn","6","1159405200000","0.0","1159408800000" ,"0.0","1159412400000", \ "0.0","1159416000000","0.0","1159419600000","0.0","1159452000000","0.0" "D5c4o05ZZKa89m12sin50esmep9qr0pl","6","1159405200000","1.0","1159408800000" ,"1.0","1159412400000", \ "1.0","1159416000000","1.0","1159419600000","1.0","1159452000000","1.0"

280

BMC Performance Manager Portal Monitoring and Management Guide

getParameters

When the command specifies an invalid GUID, an error message is returned for the parameter:
"InvalidGuid","0","Unknown parameter

getParameters
This data extraction command returns the parameters for the specified application class or subapplication class.

NOTE
Do not use the -q (quiet) argument when executing a data extraction command; otherwise, the command returns nothing.

Syntax
bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c getParameters -guid ApplicationClassGuid

Arguments
In addition to the basic bpmcli arguments shown in Table 30 on page 253, you can use the argument in Table 44 with the getParameters command. Table 44
Argument -guid guid

getParameters argument
Description GUID for the application or subapplication class

Sample command
bpmcli -portal myportal.acme.com -c getParameters -login user -pass user -guid C4smw5cZZB1naz8D 6nC80er5bzbij05z

Chapter 8 BMC Performance Manager Portal command-line interface

281

"ParentAppGuid".status. ==================================================================== getPortalVersion The getPortalVersion command returns the version number of the BMC Performance Manager Portal module on the specified BMC Portal.warning websdk.status.unknown websdk.critical If an error occurs."ParameterStatus" Table 45 shows the returned value for the ParameterStatus and its corresponding status.status. Table 45 Parameter status values Status OK Monitoring Off Blackout Unknown Warning Critical (alarm) Returned value websdk. the bpmcli returns the following message for each parameter in the specified application class: "ParameterGuid".status.ok websdk.off websdk.blackout websdk. Syntax bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c getPortalVersion 282 BMC Performance Manager Portal Monitoring and Management Guide . "ParameterValue". the following message is returned: ==================================================================== ERROR: Application: 'Guid' does not exist or does not belong to this account.status.status.getPortalVersion Return messages After successful execution of the command."ParameterDisplayName".

"RootApplicationClassGuid". the bpmcli returns the following message for each subapplication in the specified application class or subapplication: "SubApplicationGuid". "ParentApplicationClassGuid".com -c getSubApplications -login user -pass user -guid C4smw5cZZB1naz8D 6nC80er5bzbij05z Return messages After successful execution of the command. Table 46 Argument -guid guid getSubApplications argument Description GUID for the application or subapplication class Sample command bpmcli -portal myportal. "ReconciliationId" Chapter 8 BMC Performance Manager Portal command-line interface 283 . Syntax bpmcli -portal PortalWebServerName -p PortNumber -login UserName -pass UserPassword -c getSubApplications -guid ApplicationClassGuid Arguments In addition to the basic bpmcli arguments shown in Table 30 on page 253. you can use the arguments in Table 46 with the getSubApplications command.acme. Sample command bpmcli -portal myportal."SubApplicationDisplayName".com -login user -pass user -c getPortalVersion getSubApplications This data extraction command returns the child classes (subapplications) in the specified application class or subapplication.acme.getSubApplications Arguments This command uses only the basic bpmcli arguments shown in Table 30 on page 253.

the following message is returned: ==================================================================== ERROR: Application: 'Guid' does not exist or does not belong to this account. the value for ReconciliationId is null. If an error occurs.getSubApplications NOTE If the parent application class on the element has not been reconciled in the BMC Atrium CMDB at the time that the command is executed. ==================================================================== 284 BMC Performance Manager Portal Monitoring and Management Guide .

see the BMC Datastore Installation Guide. . Chapter 9 BMC Performance Manager Portal command-line interface for BMC Datastore 285 . . .7. see the BMC Portal Installation Guide. . . Disabling alarms and warnings for an application class or parameter globally . . . . . . . . . . If you are using your own Oracle license.10 of BMC Datastore. . . . . . . . . . Finding application class occurrences displaying the ACS error . . . . . . . . If you are using version 2. . . . . . . . . . . . Before you begin You must ensure that BMC DatastoreCLI has been configured and tested correctly before executing the commands. . . . on the Windows and Solaris operating systems. . Exporting the configuration information from BMC Portal on to an HTML file . This chapter presents the following topics: Configuring the BMC DatastoreCLI . . . 285 287 289 292 Configuring the BMC DatastoreCLI You can execute database queries by using the BMC DatastoreCLI. . . . . . . . . . on the Windows and Solaris operating systems. . .Chapter 9 BMC Performance Manager Portal command-line interface for BMC Datastore 9 The BMC Performance Manager Portal command-line interface for BMC Datastore enables Portal users and administrators to execute database queries by using the BMC DatastoreCLI.

portalDBUserName stands for the BMC Performance Manager Portal database user name. enter the following: s s $DATASTORE_HOME instead of %DATASTORE_HOME% . navigate to %DATASTORE_HOME%\utility\BPM_Datastore_Utility and use the following syntax to execute the commands: DatastoreCliBMCPDS. CDEDBUserName stands for the Continuous Data Export database user.sh scripts. ensure that as an operating system user. you are a member of the ora_dba group (Windows) and the dba group (Solaris). portalDBPassword stands for the BMC Performance Manager Portal database user password. Any operating system user can execute these commands if they have the write permission on the utility folder.Configuring the BMC DatastoreCLI NOTE s If you have your own Oracle license. use the ORACLE_BASE environment variable instead of the DATASTORE_HOME environment variable. the following abbreviations and variables are used: s s s s BMCPDS stands for the BMC Performance Manager Portal database server instance. s 286 BMC Performance Manager Portal Monitoring and Management Guide . you should have the execute permission on the scripts./DatastoreCliBMCPDS.sh instead of DatastoreCliBMCPDS. CDEDBPassword stands for the Continuous Data Export database user password. On Solaris. While running the DatastoreCLI commands by using the sysdba option. wherever applicable. s s s To execute the commands 1 Navigate to the BMC Datastore computer where BMCPDS is installed.bat portalDBUserName portalDBPassword Command NOTE s The commands entered in the procedure are valid on Windows. In this section. 2 At the command prompt. s s To execute the . BMCCDE stands for the BMC Continuous Data Export database server instance.bat.

sh instead. enter ./DatastoreCliBMCCDE. This functionality enables you to: s s s disable the alarm threshold for a parameter disable the warning threshold for a parameter set the value of the Alert After N Times attribute to a user-specified value for the parameter passed as the argument You can assign a value ranging from 1 to 999 to this attribute. On Solaris. 4 At the command prompt. you can disable the alarm or warning for an application class or a parameter globally. Chapter 9 BMC Performance Manager Portal command-line interface for BMC Datastore 287 . To disable the alarms and warnings for an application class or parameter globally NOTE The DatastoreCliBMCPDS command is valid on Windows.bat. To execute the .bat cde cde progress 24 3 Navigate to the BMC Datastore computer where BMCCDE is installed.sh instead of DatastoreCliBMCCDE.sh scripts. enter . you should have the execute permission on the scripts. navigate to %DATASTORE_HOME%\utility\BPM_Datastore_Utility and execute the following command: DatastoreCliBMCCDE.Disabling alarms and warnings for an application class or parameter globally EXAMPLE DatastoreCliBMCPDS. s Disabling alarms and warnings for an application class or parameter globally Using the Portal.bat cde cde progress 24 NOTE s The commands entered in the procedure are valid on Windows.bat cdeDBUserName cdeDBPassword Command EXAMPLE DatastoreCliBMCCDE. On Solaris./DatastoreCliBMCPDS.

the elements that contain the string Windows. the parameters that contain the string Space. and to see whether warning or alarm is enabled for the parameter. enter the following command: DatastoreCliBMCPDS portalDBUserName portalDBPassword disableWarningFlag applicationClassPattern parameterNamePattern elementNamePattern accountPattern 288 BMC Performance Manager Portal Monitoring and Management Guide . enter the following command: DatastoreCliBMCPDS portalDBUserName portalDBPassword disableAlarmFlag applicationClassPattern parameterNamePattern elementNamePattern accountPattern EXAMPLE The following command disables the alarm threshold for the Available Space parameter. and for all accounts: DatastoreCliBMCPDS pe pe disableAlarmFlag "%%" "Available Space" "%Solaris%" "%%" 5 To disable the warning threshold for a parameter. and to check whether warning or alarm is enabled for the parameter.Disabling alarms and warnings for an application class or parameter globally 1 Log on to the BMC Performance Manager Portal database server (BMCPDS). for all the elements that contain the string Solaris. 3 To get the current value for the Alert After N Times attribute for a parameter. 2 Go to the Datastore\utility\BPM_Datastore_Utility directory. disableWarningFlag. enter the following command: DatastoreCliBMCPDS portalDBUserName portalDBpassword checkAlertFlag applicationClassPattern parameterNamePattern elementNamePattern accountPattern EXAMPLE The following command searches the application instances that contain the string C:. Use the pattern provided in the checkAlertFlag command for the disableAlarmFlag.html file to check the current value of the Alert After N Times attribute for a parameter. This file is generated in the utility directory. and setAlarmAfterNTimes commands. and the account named My Account: DatastoreCliBMCPDS pe pe checkAlertFlag "%C:%" "%Space%" "%Windows%" "My Account" NOTE s Confirm the output of the checkAlertFlag command in the checkAlertFlag. for all application instances. s 4 To disable the alarm threshold for a parameter.

the parameters that contain the string Space. the elements that contain the string Windows. 2 Go to the %DATASTORE_HOME%\utility\BPM_Datastore_Utility directory. enter the following command: DatastoreCliBMCPDS portalDBUserName portalDBPassword setAlarmAfterNTimes applicationClassPattern parameterNamePattern elementNamePattern accountPattern attributeValue EXAMPLE The following command sets the value of the Alert After N Times attribute to 999 for the application instances that exactly match the string C:. Chapter 9 BMC Performance Manager Portal command-line interface for BMC Datastore 289 . Finding application class occurrences displaying the ACS error Using the BMC Datastore CLI. and the My Account account: DatastoreCliBMCPDS pe pe disableWarningFlag "%C:%" "%Space%" "%Windows%" "My Account" 6 To set the value of the Alert After N Times attribute for a parameter. the Available Space parameter. use the root_application_collection_status as the parameterNamePattern.Finding application class occurrences displaying the ACS error EXAMPLE The following command disables the warning threshold for the application instances that contain the string C:. To find occurrences of the ACS error 1 Log on to the BMC Performance Manager Portal database server (BMCPDS). NOTE To search or set the alarm or warning threshold for the Application Collection Status parameter. and all the elements in the Super account: DatastoreCliBMCPDS pe pe setAlarmAfterNTimes "C:" "Available Space" "%%" "Super" 999 7 Restart the BMC Performance Manager Portal application server. you can search and find the application classes and errors thrown by the application classses that display in the Application Collection Status (ACS) parameter.

On Solaris. enter ./DatastoreCliBMCPDS.sh instead of DatastoreCliBMCPDS. 290 BMC Performance Manager Portal Monitoring and Management Guide .Finding application class occurrences displaying the ACS error 3 Enter the following command by using the BMC Datastore CLI: DatastoreCliBMCPDS pe pe find_acs_errors "%internalApplicationNamePattern%" "%ACSErrorTextPattern%" NOTE The commands entered in the following procedure are valid on Windows.html file in the BPM_Datastore_Utility directory. which contains the output of the ACS error for the specifed application class. 4 This command generates an find_acs_errors.

html file output lists all occurrences of all the application classes that display all types of ACS errors.html file output lists all the occurrences of the windows application class displaying the credentials ACS error. as shown below: DatastoreCliBMCPDS pe pe find_acs_errors "%%" "%%" The find_acs_errors.html file output lists all the occurrences of the solaris application class displaying all of the different ACS errors for that application class.Finding application class occurrences displaying the ACS error EXAMPLE In the following command. as shown below: DatastoreCliBMCPDS pe pe find_acs_errors "%%" "%unknown%" The find_acs_errors. It also enables you to find out different ACS error messages for the same application class. s If you enter the solaris in internalApplicationNamePattern and leave the ACSErrorTextPattern blank. This format enables you to find out the number of occurrences of an application class displaying the ACS errors. s If you leave internalApplicationNamePattern blank and enter unknown in ACSErrorTextPattern blank.html file output lists all occurrences of all the application classes that display the unknown ACS error. as shown below: DatastoreCliBMCPDS pe pe find_acs_errors "%solaris%" "%%" The find_acs_errors. s If you leave internalApplicationNamePattern and ACSErrorTextPattern blank. as shown below: DatastoreCliBMCPDS pe pe find_acs_errors "%windows%" "%credentials%" The find_acs_errors. Chapter 9 BMC Performance Manager Portal command-line interface for BMC Datastore 291 . DatastoreCliBMCPDS pe pe find_acs_errors "%internalApplicationNamePattern%" "%ACSErrorTextPattern%" s If you enter windows in internalApplicationNamePattern and credentials in ACSErrorTextPattern.

This is useful for documentation and for audit purposes and generates an HTML file containing the details about the elements in BMC Portal and their corresponding details. enter . To export the configuration details 1 Log on to the BMC Performance Manager Portal database server (BMCPDS). BMC recommends that you create a separate export file for each group or account. s NOTE If you export all the data without using the group or account filters. for better readability. the size of the export file is large./DatastoreCliBMCPDS.Exporting the configuration information from BMC Portal on to an HTML file Exporting the configuration information from BMC Portal on to an HTML file You can export a list of elements and element configuration details by executing the export_configuration_info command by using the BMC Datastore CLI. you must enter the nameOfTheObjectgroup and nameOfTheAccount arguments as filters: s nameOfTheObjectgroup – the object group name within your BMC Portal user account nameOfTheAccount . On Solaris.the end user account name in BMC Portal. a file containing 500. 292 BMC Performance Manager Portal Monitoring and Management Guide . s In the preceding command.000 parameters could reach a size of 146 MB. For example.sh instead of DatastoreCliBMCPDS. 2 Go to the Datastore\utility\BPM_Datastore_Utility directory. Therefore. this is a larger export because it contains more information than the object group filtering parameter. 3 Enter the following command by using the BMC Datastore CLI: DatastoreCliBMCPDS pe pe export_configuration_info "%nameOfTheObjectgroup%" "%nameOfTheAccount%" NOTE The commands entered in the following procedure are valid on Windows.

This command creates a list of the configuration information in an HTML format which belongs to either the group or the account. s 4 This generates the export_configuration_info. Elements and thresholds that have inherited element profile values and elements that have over-ridden the element profile values. Elements and thresholds that do not use element profile values s s Each listing has a table containing the following columns: s s s s s s s s s s s s s s s ACCOUNT PROFILENAME (If this exists) GROUP_NAME ELEMENT_NAME APPLICATIONNAME INSTANCENAME PARAMETER_NAME WARNINGMINVALUE WARNINGENABLE ALARMMINVALUE ALARMENABLE ALERTAFTERNTIMES ALERTQUALIFIER GROUPHIERARCHY (Complete hierarchy for the groups separated by '/') APPCLASSHIERARCHY (Complete hierarchy for the instances separated by '/') Chapter 9 BMC Performance Manager Portal command-line interface for BMC Datastore 293 .Exporting the configuration information from BMC Portal on to an HTML file s Both arguments are case-sensitive. Because both these arguments are also optional you can run the command without entering any arguments by passing nameOfTheObjectgroup and nameOfTheAccount as empty arguments.html file that contains lists describing the following details: s Elements and thresholds that have inherited the element profile values and elements that have not over-ridden the element profile values.

s DatastoreCliBMCPDS pe pe export_configuration_info '' '' This creates the export_configuration_info.html file containing details of nameOfTheObjectgroup=Group1 in all accounts.html file containing details of all groups in all accounts.html file containing details of nameOfTheObjectgroup=Group1 in nameOfTheAccount=Account1. s DatastoreCliBMCPDS pe pe export_configuration_info 'Group1' '' This creates the export_configuration_info.html file containing details of all groups in nameOfTheAccount=Account1.Exporting the configuration information from BMC Portal on to an HTML file EXAMPLE s DatastoreCliBMCPDS pe pe export_configuration_info 'Group1' 'Account1' This creates the export_configuration_info. s DatastoreCliBMCPDS pe pe export_configuration_info '' 'Account1' This creates the export_configuration_info. 294 BMC Performance Manager Portal Monitoring and Management Guide .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unable to download RSM by using IE 7 or 8 on Windows 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . BMC Reporting Foundation 3. . . . . . . presenting the following topics: Monitoring problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying RTservers for the BMC Performance Manager Portal . Reinstalling the application server component of the Portal . . Error message in BusinessObjects Enterprise XI 3. . . . . . . .Appendix A 296 296 297 298 299 299 300 300 301 301 302 302 303 304 304 305 305 306 308 309 BMC Performance Manager Portal troubleshooting and FAQs A This appendix describes how to diagnose and fix monitoring problems. . . . . . . . . . . . . . . . . . . . . Portal randomly logs out users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking log files . . . . . . . . . PATROL integration error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSM upgrade fails on Windows 2003 SP1 . . . . . . . . Appendix A BMC Performance Manager Portal troubleshooting and FAQs 295 . . . . . . . . . . . . . . . . . . . . . . . . . . . . When you use Management Profiles to integrate data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequently asked questions (FAQs) . . . . . . . . Unable to download reports to csv or text file. . . . . . . . . . . . . . . . . . . . . . Buffer Cache Hit Ratio and Oracle Dictionary Cache Hit Ratio parameters go into alarm . . . .0 and above . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSM computers running Windows require permission changes . . . . . . . Cannot find errors when data discovery runs as a background process. . . . . . . . . . . . . . . . . . . Unable to close popup windows on IE Minor Versions IE 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .00 troubleshooting . . Changing the security for the BMC Performance Manager Portal . . . . Report does not contain expected data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Console Server list is empty. . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-mail notification in Microsoft Outlook 2007 does not display the BMC logo and icons. . . . . . . . . . . . . . . . . .

For information about monitoring the health and availability of the Portal.Monitoring problems Monitoring problems Monitoring problems can occur because s configuration prerequisites on the monitored elements have not been met for a particular application class configuration prerequisites have not been met on the RSM for a particular application class the RSM cannot communicate with the Portal the RSM has stopped monitoring its assigned elements s s s The Help provides information about the prerequisites for the target elements and the RSM computers. “Monitoring the health of the Portal” on page 295.timeoutException:bpm-monprod-wmi-process Problems connecting to host ciz-adamrsm2:9779: (JMX Paramlet) RSM computers running Windows require permission changes If you installed the RSM program on a computer running Windows 2003 SP1 and that RSM will use the PerfMon collector to monitor its elements. use regedit32 to add a permission to those target computers. the Help provides troubleshooting assistance for all collectors. as described in the following procedures. Also.dr1we_prm. 296 BMC Performance Manager Portal Monitoring and Management Guide . see Appendix B. The Portal Monitoring application or other JMX based collectors (that is. JBoss) Solution. displays the following error message in the Application Collection Status parameter: patsdk-bpm-mon-solution.

2 On the Control Panel. However. By default. By default. and under Performance. the permission applies to this key and all its subkeys. The PerfMon collectors begin collecting data during the next collection cycle. click the Advanced tab. select Start => Settings => Control Panel. RSM upgrade fails on Windows 2003 SP1 If you installed the RSM program on Windows 2003 SP1 computers without preparing them as described in “Data execution prevention (DEP) configuration for the RSM” on page 76 and in the BMC Portal Installation Guide. the permission applies to this key and all its subkeys.RSM upgrade fails on Windows 2003 SP1 To update the registry key on a target Windows 2000 computer 1 Highlight the following Perflib key. the installation failed. To add the Remote Service Monitor program to DEP 1 On the RSM computer. and from the main menu. To update the registry key on a target Windows 2003 or Windows XP computer 1 Highlight the following Perflib key. click Settings. choose Security => Permissions: \HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Perflib 2 Verify that the NETWORK service is present and has Read access. Appendix A BMC Performance Manager Portal troubleshooting and FAQs 297 . you can configure DEP and rerun the RSM installation program after the Portal upgrade if you perform following procedure. The PerfMon collectors begin collecting data during the next collection cycle. and select Permissions: \HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Perflib 2 Verify that NETWORK SERVICE is present and that it has Read access to this key. click Advanced. 3 On System Properties. 4 On Settings. select System. right-click the key.

click Add. To download RSM by using IE 7 or 8 on Windows 2008 1 In Internet Explorer (IE). click Add. and then click Sites. and click Open. 298 BMC Performance Manager Portal Monitoring and Management Guide . protectedmodeoff. the download failed with the error. After the computer restarts. and select C:\Windows\temp\rsminstall. 6 Click OK until you exit the Control Panel. and close IE. click Trusted sites. 3 Clear Require server verification (https:) for all sites in this zone.Privacy settings. Even if you added the site as a trusted site and allowed it from the IE Options . 2 Click Security. 7 Restart the RSM computer. 6 Log on to BMC Portal by using the same user name and password that you were using to add the RSM. and repeat the procedure for adding an RSM. RSM is downloaded successfully. the download failed displaying the same error.com).exe. 5 Click Close.Unable to download RSM by using IE 7 or 8 on Windows 2008 5 On the Data Execute Prevention tab. the auto upgrade begins for the RSM program. select Tools => Internet Options. Unable to download RSM by using IE 7 or 8 on Windows 2008 If you were running Windows 2008 and tried to download RSM by using Internet Explorer (IE) 7 or 8. 4 In Add this website to the zone where the current website is displayed (https://hostname.

7 Re-open Internet Explorer and log in to BMC Portal. and click Add.Unable to close popup windows on IE Minor Versions IE 7. clear the Require server verification (https:) for all sites in this zone check box. and close the Internet Explorer window. The Bubble Popup Window opens. and click Sites. enter about:blank. 8 Select the Status tab. 11 On the Bubble Popup Window. To work around this problem 1 Open Internet Explorer. Appendix A BMC Performance Manager Portal troubleshooting and FAQs 299 . 5 In Add this website to the zone. 4 On the Trusted Sites dialog box. You will now be able to close the Bubble Popup Window. When you use Management Profiles to integrate data. click Close. the Portal must be configured to access an RTserver. If you did not configure RTserver access during installation.0 and above. 6 Click Close. Console Server list is empty If you are integrating PATROL data by specifying a Management Profile. 9 Select Element Click Expand All if More Sub Applications Exists.0 and above Unable to close popup windows on IE Minor Versions IE 7. Use one of the following methods to configure RTservers and PATROL security.0 and above You are not able to close popup windows on IE Minor Versions IE 7. 3 Select Trusted Sites. 10 Click Blue Dotted Icon. the Console Server list is empty. 2 Select Tools => Internet Options => Security tab.

but the order in which you list RTservers establishes a failover priority. and then click Finish to start upgrading the changes for the RTserver. click Next until you reach the end of the installation program.Reinstalling the application server component of the Portal Reinstalling the application server component of the Portal You can configure the RTserver for the Portal by reinstalling the application server component of the Portal. use one of the following procedures to configure an RTserver for the BMC Performance Manager Portal. Specifying RTservers for the BMC Performance Manager Portal If you want to discover PATROL Agents and parameter thresholds from a PATROL Central environment but you did not specify an RTserver during Portal installation. change the selection to Yes. 300 BMC Performance Manager Portal Monitoring and Management Guide . and provide the name of the RTserver and the security level for the PATROL Agents.tcp:YourHost:2059). 2 Add the RTSERVERS variable and set it to the locator string (for example. and select Next. run the installation program on the Portal computer (or Portal application server). 2 When prompted for whether you want the Portal to discover PATROL Agents. 3 Follow the remaining instructions. To specify RTservers in Windows 1 Locate the system environment variables. The installation program displays the values that it saved in the installation log file. tcp:MyHost:2059. 4 Unless you need to make any other changes. 3 Restart the BMC Portal Windows service. To reinstall the application server component of the Portal 1 Using the upgrade procedures described in the BMC Portal Installation Guide. The Portal can access only one RTserver at a time. and select the BMC Performance Manager Portal.

and 6 A. see the information about changing the security level after installation. you can take help of your Oracle DBA to increase the SGA memory to the maximum possible value on your computer. Changing the security for the BMC Performance Manager Portal If you did not specify a security level during installation. ignore the alert notification for the Buffer Cache Hit Ratio and Oracle Dictionary Cache Hit Ratio parameters when Oracle GATHER_STATS_JOB runs between 10 P. you must change the default security assigned for the Portal. If you are using BMC Datastore. see the BMC Datastore Installation Guide for information about the SGA memory. If you do not have sufficient hardware to increase the memory. If you are using your own Oracle license. In the BMC Portal Getting Started guide.com:2059 export RTSERVERS 3 Save the file and restart the BMCPortalAppserver process. and 6 A. increase the SGA memory for the BMC Portal Database instance (Default name: BMCPDS).Changing the security for the BMC Performance Manager Portal To specify RTservers in Solaris 1 In the following directory. Buffer Cache Hit Ratio and Oracle Dictionary Cache Hit Ratio parameters go into alarm When Oracle GATHER_STATS_JOB runs between 10 P.domain. To work around this problem.M. If you want the Portal to discover agents of a different security level.M.M. the Buffer Cache Hit Ratio and Oracle Dictionary Cache Hit Ratio parameters go into an alarm state.sh: InstallationDirectory/appserver/websdk/bin/ 2 On any line after the first line in the file..M. open run. the installation program assigned security level 0 (the default level) to the BMC Portal (and BMC Performance Manager Portal). add the following lines: RTSERVERS=tcp:RtServer. Appendix A BMC Performance Manager Portal troubleshooting and FAQs 301 .

2 Navigate to Tools => Internet Options => Advanced. 5 Access the BMC Portal website to download and save reports from BMC Portal. You can download and save the reports by configuring the security settings for your browser. This happens because you have not installed the client certificate. 3 In the Advaced tab. and access the Reports tab of BMC Portal to export reports containing information about newly added elements with application classes or history reports.htm format. To install the client certificate 1 Navigate to Microsoft Outlook 2007. you are not able to download the reports to csv or text file to a location on your local computer. 302 BMC Performance Manager Portal Monitoring and Management Guide . 3 On the Certificate dialog box. You must install the client certificate on each Portal that sends email notifications. 4 Click Install Certificate. E-mail notification in Microsoft Outlook 2007 does not display the BMC logo and icons If you are using Microsoft Outlook 2007 and you receive an e-mail notification. click View Certificate.Unable to download reports to csv or text file Unable to download reports to csv or text file When you use Internet Explorer on English and non-English language environments. 4 Clear the Do not save encrypted pages to disk check box. The following error message is displayed: Unable to open the site. the e-mail does not display the BMC logo and icons properly. scroll to the Security section. 2 Open the status change mail and save the mail in the . To configure the security settings for your browser 1 Open Internet Explorer.

1.Portal randomly logs out users 5 On the Certificate Import Wizard.war\WEB-INF\web. The product displays the The import was successful message. change the attribute session timeout to -1. %BMC_PORTAL_KIT_HOME%\appserver\websdk\tools\jboss\server\all\deploy\we bsdk. and click Next. 7 Click Finish.sar\conf\web. click Next.sar\portal. click Yes to confirm the security warning. you must modify the following xml files.sar\drmop. the product redirects you to the login page. %BMC_PORTAL_KIT_HOME%\appserver\websdk\tools\jboss\server\all\modules\d rmop. 8 On the Security Warning message that appears.xml 2. Portal randomly logs out users If you are using BMC Portal and leave it idle for some time. To stop BMC Portal from logging you out randomly.xml 3.xml You must set the session-timeout value to the following: <session-timeout>-1</session-timeout> Appendix A BMC Performance Manager Portal troubleshooting and FAQs 303 . %BMC_PORTAL_KIT_HOME%\appserver\websdk\tools\jboss\server\all\deploy\jbo ssweb-tomcat55. 6 Ensure that the Automatically select the certificate store based on the type of certificate (default) option is selected.war\WEB-INF\web. to change the session timeout to infinite. and click any link.

If these actions do not resolve the problem. check the hostname and port number is right and agent is running. Verify that the padmr-mbean. you cannot access the Summary page to see if the Portal encountered any errors. you can access other tabs in the Portal while the Portal continues discovering the data in a background process. Using the JMX console. Ensure that the host is listed in the hosts file or in DNS.par file is included in the RSM deployment. The Portal cannot find the specified host. the Summary page lists any errors that occurred during discovery. Table 47 Message Cannot connect to agent name. cannot encrypt password Cannot connect to agent name. Ping the host and the PATROL Agent and port.Cannot find errors when data discovery runs as a background process Cannot find errors when data discovery runs as a background process When you are using the PATROL Integration option to discover PATROL Agents and their thresholds. Cannot connect to agent name. invalid host name The rempadm process is down Timeout when trying to talk with remote padm Error messages for PATROL integration Action to take Verify that you provided the correct credentials and that the agent ACL allows the specified user to connect with PEM authorization. And the security level of agent is the same as RSM. Because of the lengthy discovery process. or denied by agent ACL Cannot connect to agent name. Table 47 lists the error messages that you might see on the user interface or in the log files and provides some instructions for handling the error or problem. 304 BMC Performance Manager Portal Monitoring and Management Guide . Contact BMC Software Customer Support. invalid user name or password. located in the following directory: s s (Windows) %BMC_PORTAL_KIT%\appserver\websdk\tools\jboss\server\all\log (Solaris) $BMC_PORTAL_KIT/appserver/websdk/tools/jboss/server/all/log PATROL integration error messages You might encounter problems when using the PATROL Integration option to discover PATROL Agents and their thresholds. when you navigate to other pages in the Portal. contact BMC Software Customer Support. increase the timeout or reduce the workload on the PATROL Agent. Verify that you provided the correct credentials and that the agent ACL allows the specified user to connect with PEM authorization.log file. but you can access the portal. however.

This problem occurs when the Report Application Server (RAS) returns the default maximum of 20. 7 Click Save & Close.00 troubleshooting BMC Reporting Foundation 3.1=> BusinessObjects Enterprise => BusinessObjects Enterprise Central Management Console.000 records. 6 Change the Maximum Concurrent Report Jobs (0 for unlimited) option to 0 to set the number of maximum concurrent report jobs to unlimited. Appendix A BMC Performance Manager Portal troubleshooting and FAQs 305 . Error message in BusinessObjects Enterprise XI 3.2.00 troubleshooting This section provides troubleshooting information for enterprise reporting. 2 Log on to the Central Management Console as an Administrator. 4 Right-click Report Application Server and select Properties.1 When you try to view a report.BMC Reporting Foundation 3. 8 Restart the Report Application Server.2. you may receive the following error message: Maximum processing time or maximum records limit reached. Use the following procedures to increase the maximum number of records: To configure the Report Application Server 1 Choose Start =>Programs => BusinessObjects XI 3. 5 Change the Number of database records to read when previewing or refreshing a report (-1 for unlimited) option to -1 to set the number of database records to be read to unlimited. 3 Click Servers.

1 => BusinessObjects Enterprise => Business View Manager. Confirm that the Server Intelligence Agent (hostName) service is running (Start => Programs => Administrative Tools => Services).1 and the CDE database 1 Choose Start => Programs => BusinessObjects XI 3.” Check the DROCR_BPMAccountElements list of values. see Chapter 7 of the BMC Performance Manager Portal Monitoring and Management Guide. If the elements that you selected for the report were added to the Portal recently. s s s s s s s To confirm connectivity between BusinessObjects Enterprise XI 3.00 services are running (Start => Programs => BusinessObjects XI 3.1 and the CDE database. For more information. Check the connectivity between BusinessObjects Enterprise XI 3. For more information. Use the Central Configuration Manager to confirm that other BMC Reporting Foundation 3. confirm that the RefreshDatafeedMetadata command is successfully executed.1 and the CDE database. as described in “To confirm connectivity between BusinessObjects Enterprise XI 3.Report does not contain expected data Report does not contain expected data If the report contains no data or does not contain data from the latest reporting period. Perform the procedure in “To refresh the list of values for Account/Elements selection lists” on page 174. Confirm that the report date and time that you selected are within the CDE database retention period.1=> BusinessObjects Enterprise => Central Configuration Manager). enter or confirm the following information: 306 BMC Performance Manager Portal Monitoring and Management Guide . see Chapter 7 of the BMC Performance Manager Portal Monitoring and Management Guide.2. perform the following troubleshooting steps: s Confirm that BMC Performance Manager components listed in Table 21 on page 185 are collecting data in the Portal. 2 In the Log On to BusinessObjects Enterprise dialog box. as described in “To check the DROCR_BPMAccountElements list of values” on page 307.

7 Choose Tools => Test Connectivity button. click Cancel. if it is not present password for the user name Enterprise. unless your BusinessObjects Enterprise XI 3. and then double-click DROCR_BPMConnection. You must re-enter the password to confirm that it is correct. 4 In the Welcome to Business View Manager window. 8 Click OK.1 environment was configured to use a different authentication method If you have set a password for the Administrator while installing BMC Reporting Foundation 3.1 => BusinessObjects Enterprise => Business View Manager. as described in step 9 on page 172 user name password NOTE The password is not visible.00. 2 In the Log On to BusinessObjects Enterprise dialog box. Else.2. 6 Confirm that the following information is correct: s s s connection string. To check the DROCR_BPMAccountElements list of values 1 Choose Start => Programs => BusinessObjects XI 3. 3 Click OK. leave this field blank. 5 Expand the BMC_PM folder. If the connection is successful. if it is not present user name that has the BusinessObjects Enterprise XI 3. specify that password. the Connection test completed successfully message appears. enter or confirm the following information: Appendix A BMC Performance Manager Portal troubleshooting and FAQs 307 .1 Administrator privilege.Report does not contain expected data System User Name Passworda Authentication a host name of the Central Management Server (CMS).

4 In the Welcome to Business View Manager window. Else. 3 Click OK. if it is not present password for the user name Enterprise.r\Logging. s Check the Windows Event Logs for events with a source that begins with “BusinessObjects_” (for example. unless your BusinessObjects Enterprise XI 3.00. BusinessObjects_CMS). This list of values executes on demand If this message does not appear. leave this field blank.00 Logging directory: BMCReportingFoundationInstallationDirectory\Business Objects\BusinessObjects Enterprise vv. contact BMC Software Customer Support. specify that password.2. s The directory path might have changed during installation.Checking log files System User Name Passworda Authentication a host name of the Central Management Server (CMS). 5 Expand the BMC_PM folder. 308 BMC Performance Manager Portal Monitoring and Management Guide . 6 Click Clear Instance. 7 Confirm that the Schedule Status field contains the following message: There is no scheduled List of Values instance.2. and then double-click DROCR_BPMAccountElements. The Clear Instance button becomes unavailable.1 environment was configured to use a different authentication method If you have set a password for the Administrator while installing BMC Reporting Foundation 3. Checking log files You can diagnose some problems by checking log files. if it is not present user name that has the BusinessObjects Enterprise XI 3. click Cancel. Check the log files in the BMC Reporting Foundation 3.1 Administrator privilege.

Does having remote offices affect the number of RSM computers required? Yes. Therefore. Keep the RSM estimating guidelines in mind so that the RSMs in each remote location can accommodate the Performance Managers you plan to run at those sites. The CDE database should have a configuration equivalent to the Portal database. Is the minimum RSM configuration required even if I am managing only a few systems in these locations? No. as you add managed servers. and activity in your environment. If only a few systems are being monitored. Can I deploy fewer RSM computers than recommended? The actual number of RSMs necessary for your environment might vary based on the actual hardware configuration. and how the estimates provided by the BMC Performance Manager Portal Performance and Scalability Guidelines Installation Notes. Remote monitoring across a WAN is generally not recommended (though it is possible in limited situations). you will likely need at least one RSM for each remote location.Frequently asked questions (FAQs) Frequently asked questions (FAQs) The following are questions frequently posed by customers with regard to performance and scaling. We do not recommend clustering of RSMs (in a single cluster) located at different WAN locations as it might put extra network load. What is the impact on the scale estimates if Continuous Data Export (CDE) is used? CDE is designed to put minimum impact on the Portal. Appendix A BMC Performance Manager Portal troubleshooting and FAQs 309 . the size of the system required is reduced. as we distribute the elements to available RSMs of a cluster in round robin fashion. For a new installation. compare the actual parameter counts observed in your environment to the original estimates to adjust the RSM counts as necessary. number of elements and parameters.

310 BMC Performance Manager Portal Monitoring and Management Guide . application server. in the case of a failure. or RSM impact performance and scale estimates? Clustering addresses continued operation in the event of a failure. The scale estimates represent the minimum number of computers required to support a given workload. If you implement clustering. and not performance. The estimates should be used to ensure that.Frequently asked questions (FAQs) How will clustering of the web server. the remaining components continue to operate. you will need additional computers.

. . . . . . . . . . . . . . Performance Manager configuration . . . . . . . Self-monitoring Performance Manager . . . . . . . . . . . . . . . . . . . . Changing the threshold settings . . Configuring PATROL Agent monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Permissions. . . . . . . . . . . . . . . . . . PATROL Agent health monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure RSM to monitor JMX behind a firewall . . . . . . . . . . . . . .Appendix B 311 312 312 313 314 316 316 317 318 318 B Monitoring the health of the Portal This appendix presents the following topics: Overview . . . . . . . . . . . . . . . . . Overview The BMC Performance Manager Portal module provides the following tools that you can use to monitor the health and performance of the Portal: s a self-monitoring Performance Manager that monitors the status of the Portal components an application class that monitors the status of a PATROL Agent s Appendix B Monitoring the health of the Portal 311 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC PM Monitor application classes . . . . . . . . . . . . . . Remote Service Monitor setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

you must log on with these credentials. You cannot use the Performance Manager Editor (PME) to modify this Performance Manager. the installation program creates predefined settings for the predefined provider and account. named Portal Monitoring. the installation program creates the predefined settings described in Table 48. Permissions When you install the BMC Portal. that you can use for self-monitoring accounts To manage this provider. log on with Portal credentials. Table 48 provider Predefined settings for monitoring the BMC Performance Manager Portal module Description default provider. In addition to these settings. To access the self-monitoring application classes in BMC PM Monitor. and you should not use the SDK to change its properties. when you install the BMC Performance Manager Portal module. Predefined credentials superadmin / superadmin Portal hierarchy level account default account named Portal Monitoring.Self-monitoring Performance Manager Self-monitoring Performance Manager The BMC Performance Manager Portal module includes BMC PM Monitor. a core Performance Manager that enables you to monitor the health and performance of the following Portal components: s s s s s Portal application server Portal web server RSM Continuous Data Export (Datafeed) utility PATROL integration This Performance Manager is installed by default during installation of the BMC Performance Manager Portal module. that you can use to monitor the Portal portalmon/portalmon 312 BMC Performance Manager Portal Monitoring and Management Guide . Immediately following installation. you can log on as a Portal administrator and see this Performance Manager on the Performance Managers page.

or the Portal. you must set up at least one RSM to monitor your production RSMs. the Portal Monitoring provider does not have an administrator. — Global RSMs can monitor elements for all users on the Portal. you can configure a dedicated RSM that monitors the Portal components. — Shared RSMs can monitor elements for all users in a provider. By installing the RSM using the credentials for the portalmon user. Appendix B Monitoring the health of the Portal 313 . consider the following issues: s When configured as a shared or dedicated RSM. — Dedicated RSMs can monitor elements for all users in an account. To specify a shared RSM with the BMC PM Monitor application classes.Remote Service Monitor setup Remote Service Monitor setup When setting up an RSM to monitor the Portal components. set up a separate RSM and enter the credentials for the Portal Monitoring administrator. the Portal Monitoring provider. an RSM cannot monitor itself. you might consider the scenario illustrated in Figure 42 on page 314. The RSM that you specify to monitor the Portal component must belong to the portalmon user. including users under the Portal Monitoring provider. The portalmon user belongs to a different account and provider than other users on your Portal. If you do not use global RSMs in your environment. set up a separate RSM and enter the credentials for the Portal Monitoring user account (portalmon/portalmon). This figure shows typical user accounts under the DEFAULT provider and the Portal Monitoring account under the Portal Monitoring provider. You must create an administrator for this provider before you can install a shared RSM. To specify a dedicated RSM to monitor the Portal components. By default. s Based on these issues.

Configure RSM to monitor JMX behind a firewall The Portal Monitoring application or other JMX-based collectors (JBoss Solution) generate the following error in the Application Collection Status parameter: patsdk-bpm-mon-solution.dr1we_prm. 314 BMC Performance Manager Portal Monitoring and Management Guide . Consider installing this RSM with the self monitoring (portalmon/portalmon) credentials.Configure RSM to monitor JMX behind a firewall Figure 42 RSM setup for monitoring the Portal components database web browser web server firewall application server shared RSM global RSM dedicated RSM Account A Account B Account C Portal Monitoring account Portal Monitoring DEFAULT TIP You can install one instance of the RSM on the Portal computer. Use the following steps to configure the RSM so that you can monitor JMX behind a firewall.timeoutException:bpm-monprod-wmi-process Problems connecting to host ciz-adamrsm2:9779: (JMX Paramlet) This JMX time out occurs because of the environmental constraints of the Jboss server when it is behind a firewall.

11=-Djava.useLocalHostname=true NOTE Use the next available number for additional parameters in the rsmwrapper.patsdk.rmi.java.JmxParamlet.additional.java.conf file.additional.hostname=<NAT'ed IP address or External IP address of this RSM> wrapper. 4 Verify that JBoss JMX metrics collection starts.10=-Djava. B Turn on debugging for the JMX collector in the RSM.solutions. restart the RSM.additional.properties file.10=-Djava. add the other two parameters as wrapper. If the problem is still unresolved.additional.11=Djava.11.useLocalHostname=true s EXAMPLE wrapper.level=FINEST com.properties: s s com. Appendix B Monitoring the health of the Portal 315 . For example:. if wrapper. A Capture screens that show the details of the grayed out JMX parameters.additional. please add the following two lines to %RSM_HOME%\RSMversionNumber\tools\jdk\jre\lib\logging.server.bmc.java.server.patsdk.89 wrapper.jmx.java.9 is the last java additional parameter in the file.bmc.java.rmi.additional.additional.server.conf file on each RSM that you want to monitor for JMX metrics: s wrapper.10 and wrapper.patrol.rmi. 3 Save the file and restart the RSM.Configure RSM to monitor JMX behind a firewall To monitor JMX behind a firewall 1 Open following ports in the firewall: s s s RmiPort–9785 RMIObjectPort–9786 Naming Service–9779 2 Add the following two entries in the %RSM_HOME%\RSMversionNumber\conf\rsmwrapper.rmi.45.java.solutions.67.hostname=123. C On the RSM machine.patrol.java.JmxDiscoveryParamlet.server.jmx.level= FINEST D After modifying the logging.

BMC PM PATROL Integration Monitor BMC PM Web Server Monitor monitors the following Portal web server processes and the operating system on the web server: s s Solaris: BMCPortalWebserver Windows: BMCPortalWebserver. and monitoring activity on the RSM monitors the rempadm. add the Portal components as elements and select the applicable BMC PM Monitor application classes. After logging on. Windows operating system performance. you must log on with the user credentials described in Table 48 on page 312. 316 BMC Performance Manager Portal Monitoring and Management Guide .exe process mines parameter data from the PATROL Agent.exe process.BMC PM Monitor application classes BMC PM Monitor application classes BMC PM Monitor contains the application classes listed in Table 49. Table 49 BMC PM Monitor application classes Description monitors the JBoss program. BMC PM RSM Monitor monitors the JBoss program.exe Performance Manager configuration To use the application classes in BMC PM Monitor. and displays information about the monitoring activity on the application server: s s Application class name BMC PM Portal App Server Monitor BMCPortal. see the Help. see “Continuous data export configuration” on page 190. For more information about the parameters in each application class.exe (Windows) BMCPortal (Solaris) BMC PM Portal Datafeed Monitor monitors the performance of the Continuous Data Export (Datafeed) utility For more information about the Datafeed utility. communication metrics from the RSM. operating system performance. and the following Portal application server processes. the BMCRSM.exe process on the RSM The rempadm.

and specify the host name on which you installed the Portal application server. if necessary.PATROL Agent health monitoring EXAMPLE To monitor the application server: 1. PATROL Agent health monitoring PATROL Agent Availability and Health Monitor is a core application class that monitors the health and status of the PATROL Agents from which the Portal is mining parameter data. On the Application Classes page. Log on to the Portal as the portalmon user. Finish adding the application server by specifying the required credentials and by modifying the thresholds. On the Configure tab. select Self Monitoring from the Select Category list. and select BMC PM App Server Monitor for the appropriate operating system. 2. The parameters in this application class provide the following information about the monitored PATROL Agents: s whether the PATROL Agent was restarted after the most recent collection interval by the RSM description of any errors that occurred when the RSM tried to connect to the PATROL Agent whether the RSM can establish a connection to the PATROL Agent on the specified host name and port number of milliseconds required for the PATROL Agent to execute the remote PSL command that was initiated from the RSM s s s Appendix B Monitoring the health of the Portal 317 . 4. 3. select the Elements task.

s You cannot use the element Properties page to explicitly add this application class to an element. Changing the threshold settings When you choose to apply the PATROL Agent Availability and Health Monitor application class to PATROL integration elements. s When you use the PATROL Integration option to add elements. The Portal applies the properties that you specify for the PATROL Agents on the Add Elements pages. the Portal sets two parameter thresholds and does not enable alert notifications. you can choose to have the Portal apply the application class to any PATROL integration element that does not have the application class. you can choose to have the Portal apply the application class to all discovered PATROL Agents.Configuring PATROL Agent monitoring Configuring PATROL Agent monitoring You can apply this application class when you add elements to the Portal or when you refresh thresholds. When you use the Refresh PATROL Integration option to update thresholds. 318 BMC Performance Manager Portal Monitoring and Management Guide . You can modify threshold settings from the element Properties page for the applicable elements.

. . . . . . . . . . . . . . . . . . . . . . . . Appendix C BMC Performance Manager Portal files 319 . . . . . . BMC Performance Manager Portal log file . . . . . . However. . . . . . . . . . . . . . . . . . . . . . . . . .Appendix C BMC Performance Manager Portal files C This appendix describes the configuration files used by the BMC Performance Manager Portal and log files that you can use to diagnose problems. . . . . Generally. . . . . . . . . Log files . . . . . the user interface provides screens that you can use to change properties for the BMC Performance Manager module. . . . . . . . . . . . . . . . . . . . . . 319 320 320 321 345 345 345 Configuration files The BMC Performance Manager Portal saves most of its configuration settings in property files. . . . . . you should use the configuration options on the BMC Performance Manager Portal user interface to change the properties for this module. . . . . . . Configuration file properties . you might encounter a situation that requires you to locate and edit one of these files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Performance Manager Portal property files . . . . . . . . . . . . . . . . . . . instead of editing the configuration files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSM log files. . . . . . . . . . . . . . . . . . . . . . . . . . This appendix presents the following topics: Configuration files . . . . . Remote Service Monitor property files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generally. . . . . . .

You can find this file in the following location: %RSM_HOME%\RSMversionNumber\server\rsm\conf\properties\rsm\ 320 BMC Performance Manager Portal Monitoring and Management Guide . This module saves properties in the following files: s drmop. contains the display name and description attributes for the RSM (for example. Table 50 Operating system Windows UNIX Location of BMC Performance Manager Portal property files Location %BMC_PORTAL_KIT_HOME%\appserver\websdk\tools\jboss\server\all \conf\properties\drmop $BMC_PORTAL_KIT_HOME/appserver/websdk/tools/jboss/server/all/ conf/properties/drmop Remote Service Monitor property files The Remote Service Monitor program saves properties in the following files on the RSM computer: s rsm-RsmHostName. You can find this file in the following location: %RSM_HOME%\RSMversionNumber\server\rsm\conf\properties\rsm\ s rsm.properties—available in the following location.com.properties—defines many default and customizable properties for the BMC Performance Manager Portal s padm.properties—contains timeout values that you can customize for application classes that use the SNMP or command shell collectors.properties—contains the path to the directory that contains the properties files that configure target files and databases for continuous data export parameter data You must restart the Portal after modifying any of the properties in these files.BMC Performance Manager Portal property files BMC Performance Manager Portal property files Table 50 shows the location for the BMC Performance Manager Portal module’s property files on the Portal application server.properties).properties—contains timeout and scheduling information for integrating data from PATROL Agents s datafeed.acme. rsm-server1.

acme.xml—contains default settings for creating the RSM log files. You can find this file in the following location: %RSM_HOME%\RSMversionNumber\server\rsm\deploy\patsdk.properties).sar\META-INF Do not edit this file unless instructed by BMC Software Customer Support.com.properties—defines how the RSM communicates to the Portal (for example. portal-server1. You must restart the Portal after modifying any of the properties in these files. Appendix C BMC Performance Manager Portal files 321 . You can find this file in the following location: %RSM_HOME%\RSMversionNumber\server\rsm\conf\properties\rsm\ s jboss-service. Configuration file properties Table 51 on page 322 through Table 57 on page 344 list properties that configure the BMC Performance Manager Portal.Configuration file properties s portal-PortalWebServer.

default.7.reporting.7 and later) 15 30 60 For the change to take effect.default.7. The report update interval default is 10 minutes for fresh installations of BMC Portal version 2. enabledeleteinactiveinstance property enables and disables the inactive application instance deletion feature Valid values: s true (default) = inactive application instance deletion is enabled false = inactive application instance deletion is disabled s Example: drmop.00 or later.interval.7) 10 (default for version 2. Setting drmop.properties file (part 1 of 19) Description determines the default value for Report Update Interval Valid values (in minutes): s s s s s drmop.applicationinstance.reporting.minutes 5 (default for versions earlier than 2. you must restart the Portal after applying the new value.interval.reporting. element and element profile settings that existed prior to the change continue to use the settings they used prior to the change.applicationinstance. enabledeleteinactiveinstance=true 322 BMC Performance Manager Portal Monitoring and Management Guide .minutes=5 causes all elements and element profiles created after this value is set to have 5 minutes as their default report update interval. Example: drmop.minutes=5 drmop.Configuration file properties Table 51 Property Properties in drmop. However.interval. Previous versions and previous installations that are updated to version 2.00 or later retain the 5-minute default.default.

If you restart the Portal after 3 days.enabledeleteinactiveinst ance property is enabled. For example.applicationinstance.applicationinstance. Appendix C BMC Performance Manager Portal files 323 . the inactive instances will never be deleted. even those that were inactive for 3 days. the inactive instances will never be deleted.applicationinstance. and the tallying of time to determine when an instance is considered inactive begins from that point forward. if the monitor off mode or blackout duration exceeds the value of the this property. For example. all inactive instances are not deleted. If you restart the Portal on a schedule or at a rate that occurs more frequently than the value of the drmop.properties file (part 2 of 19) Description sets the discovered inactive instance retention time in minutes Valid values are positive whole numbers. or when an element comes out of blackout. maxinactiveminutes time is reset. the drmop.applicationinstance. these instances will be deleted. the instances underneath the element are considered inactive. However. maxinactiveminutes is set to 4320 minutes (or 3 days).maxinactiveminutes Whenever you restart the Portal service. If the drmop. maxinactiveminutes=4320 Warnings: s When an element is in monitor off mode. and you set the max inactive minutes to 1440 minutes (one day) or more. maxinactiveminutes property. The default value is 4320 minutes (or 3 days). if you regularly restart the Portal every night. s drmop. Example: drmop.Configuration file properties Table 51 Property Properties in drmop.applicationinstance. the inactive instances are deleted 3 days after the Portal is restarted (if they remain inactive).applicationinstance. by default drmop.

availability.properties. minutes=30 324 BMC Performance Manager Portal Monitoring and Management Guide .allow.batch.availability.reports. By default. blackout period.formula. offline. change the following properties: drmop. exclude_time=None.exclude_time) * 100% Valid values: s s s s s s blackout none offline OK unknown warning To change the statuses in up_time and exclude_time.reports.job. Unknown drmop. change drmop.timeout. Offline.availability. after which a timeout occurs Example: drmop.batch. users can change the host name of an existing element.reports. change=true drmop.properties.properties file (part 3 of 19) Description indicates whether a user can change the host name of an element Any value except true is considered false. Blackout.exclude_time formula used to calculate element availability By default the following formula includes warning and OK times in up_time and includes none.formula.reports.formula.reports.Configuration file properties Table 51 Property Properties in drmop.formula.reports.element.timeout.up_time sets the statuses to include in and exclude from the drmop.hostname.topn. Example: drmop.job. warning drmop.element.allow.minutes specifies the maximum number of minutes for data to appear on the Top N report (account and element views on the Reports tab). and unknown times in exclude_time: availability =up_time/(total_time .up_ time= Ok.availability.topn.hostname.

the Events tab shows a maximum of 300 element alerts. you must open the drmop.properties file.events.ldap.limit sets the maximum number of element alerts to show on the Events tab when you select Elements from Objects to Show or All from Alerts to Show Valid values are positive whole numbers.to.events.hosts.element.ula. Example: portal.limit=300 portal. and uncomment the enable.alternate.alternate.element. Example: portal.events. Example: portal.param.search property.param.return sets the maximum number of CIs to return for BMC Atrium CMDB discovery searches Valid values are positive whole numbers. the Events tab shows a maximum of 600 element and parameter alerts.return=100 portal. Valid values: s enable.ldap.element.max. adds security so that users cannot delete all of the users in the DEFAULT FULL ACCESS user group This property is commented out in the drmop. To activate this property.limit sets the maximum number of element and parameter alerts to show on the Events tab when you select Elements + Parameters from Objects to Show Valid values are positive whole numbers.hosts. By default.ldap.properties file.events.alternate.cmdb.limit=600 Appendix C BMC Performance Manager Portal files 325 .element.search false = the DEFAULT FULL ACCESS user group can be deleted true = the DEFAULT FULL ACCESS user group cannot be deleted s Example: enable.ula.to.Configuration file properties Table 51 Property Properties in drmop.ula.search. By default.cmdb.search.search=true portal.max.properties file (part 4 of 19) Description when uncommented and set to true.

param. it does not restrict the internal status propogation.events.patrol. However. For example. 326 BMC Performance Manager Portal Monitoring and Management Guide .param.limit portal.bmc. Example: portal. ignoreUnknownState property in the rsmcfg. BMC recommends that you use the com.services.CollectionJob.unknown specifies whether the unknown events appear in the event table Valid values: s false (default) = unknown events appear in the event table true = unknown events do not appear in the event table s Example: portal.properties that restricts the creation of the unknown status.properties file (part 5 of 19) Description sets the maximum number of parameter alerts to show on the Events tab when you select Parameters from Objects to Show Valid values are positive whole numbers. because the product propogates the state changes through the internal Unknown status.prevent. you receive notifications for state changes from Warning to Unknown to Warning.Configuration file properties Table 51 Property Properties in drmop.events.events.limit=300 portal.patsdk. By default.unknown=false Note: This property allows you to prevent the creation of unknown events and notifications.events. the Events tab shows a maximum of 300 parameter alerts.prevent.

history. Example: portal.history. however.properties file (part 6 of 19) Description sets the number of days that the database keeps element status changes. such as blackout and monitoring off s portal.event.statusHistory.retention property.retention The value of this property must match the value for the portal.summarizationData Point.statusHistory.element.event.element.Configuration file properties Table 51 Property Properties in drmop. this value is used to calculate the number of partitions to keep in the database Valid values are positive whole numbers or positive numbers with a single-digit decimal (for example. Appendix C BMC Performance Manager Portal files 327 . s s Example: portal. BMC recommends that you set the value at 92 days.retention specifies the number of days’ worth of event data to retain. Although the default setting is 100.period property and rounds up.event.5). retention=428 portal. Increasing the retention period requires more disk space. the database multiplies the number of days specified in the portal. The default value is 428 days.history.history.rollover.history. BMC recommends a setting of 14.retention=14 See page 147 for more information about event retention.element.history. To calculate the number of partitions to drop. 1.

or parameter went into unknown states Valid values: s false (default. works with the portal. cleanunknownevents.history. recommended value) = purging of unknown events is disabled true = purging of unknown events is enabled s Example: portal.purgeunknown.history.history.event.history.event.period HALF_HOUR HOUR HALF_DAY DAY (default) WEEK MONTH YEAR BMC recommends that you set this property value to DAY.period=DAY See page 147 for more information about event retention.history.event.purgeunknown. cleanunknownevents. 328 BMC Performance Manager Portal Monitoring and Management Guide .Configuration file properties Table 51 Property Properties in drmop.retention property to determine when to purge a partition from the database Valid values: s s s s s s s portal.events. which saves one day’s worth of data in event partitions. application class. portal.enabled determines whether purging is enabled or disabled for all unknown events that were generated when an element.rollover.properties file (part 7 of 19) Description sets the period for saving data in an event partition in the database.events.enabled=false For details. see “Purging unknown and unused events from the event table” on page 149.rollover. Example: portal.

Monday. and Friday. The time set for this property is the time on the database server. schedulehours determines the hour when the Retention Job to purge unknown events begins to run Valid values are 0 (12:00 a.history.events.events.events.6 sets the job to run on Sunday.m.m.Configuration file properties Table 51 Property Properties in drmop.m. Example: portal. Example: portal.).purgeunknown. see “Purging unknown and unused events from the event table” on page 149. or midnight) through 23 (11:00 p.2.history. For example.history. schedulehours=19 For details.history. The default and recommended value is 19 (7:00 p.m.purgeunknown.events. a value of 1. Appendix C BMC Performance Manager Portal files 329 .purgeunknown. The value must represent an hour between 12:00 a. scheduledays=1 For details.m. portal. scheduledays 1 = Sunday (default and recommended value) 2 = Monday 3 = Tuesday 4 = Wednesday 5 = Thursday 6 = Friday 7 = Saturday If you want the job to run on more than one day.). see “Purging unknown and unused events from the event table” on page 149. and 11:00 p.properties file (part 8 of 19) Description sets the days on which the retention job to purge unknown events runs Valid values: s s s s s s s portal.purgeunknown. you can enter multiple values and separate them by a comma (no spaces). No minutes are recognized.

a value of 1. see “Purging unknown and unused events from the event table” on page 149.purgeunused. 6 sets the job to run on Sunday.history.events. cleanunusedevents. portal.events. see “Purging unknown and unused events from the event table” on page 149.events.history.Configuration file properties Table 51 Property Properties in drmop.properties file (part 9 of 19) Description determines whether purging is enabled or disabled for all unused events that were generated by elements. Example: portal.purgeunused.purgeunused.history.events. appclass. you can enter multiple values and separate them by a comma (no spaces).purgeunused.history.2. Monday. enabled=false For details. scheduledays=1 For details. or parameters that were deleted or that do not exist Valid values: s s portal. and Friday. 330 BMC Performance Manager Portal Monitoring and Management Guide .enabled false (default) = purging is disabled true = purging is enabled Example: portal. For example.scheduledays determines the days on which the retention job to purge unused events runs Valid values: s s s s s s s 1 = Sunday (default and recommended value) 2 = Monday 3 = Tuesday 4 = Wednesday 5 = Thursday 6 = Friday 7 = Saturday If you want the job to run on more than one day.cleanunusedevents.

history.agentstatushistory.history. or midnight) through 23 (11:00 p.m.websdk.m.events.properties file (part 10 of 19) Description determines the time (the hour on the hour) when the retention job to purge unused Events runs Valid values are 0 (12:00 a.activitylog.history. which retains the RSM status history for 30 days. schedulehours portal.events. Example: portal. see “Purging unknown and unused events from the event table” on page 149.websdk.history.websdk.agentstatushistory.). Example: portal.m. The default and recommended value is 30.history. and 11:00 p. Example: portal. portal.activitylog. retention=30 Appendix C BMC Performance Manager Portal files 331 .Configuration file properties Table 51 Property Properties in drmop.). retention=100 portal. retention determines the number of days that the database retains the history for remote server monitor (RSM) status Valid values are positive whole numbers.m.schedule hours=19 For details. No minutes are recognized.websdk.history. The default and recommended value is 100.m. The default and recommended value is 19 (7:00 p.purgeunused. The value must represent an hour between 12:00 a. The time set for this property is the time on the database server.retention determines the number of days that the database retains the websdk activity log Valid values are positive whole numbers. which retains the websdk activity log for 100 days.purgeunused.

websdk. The default and recommended value is 45.retention=12 portal. parameterstatushistory.websdk.websdkalertjob.retention =0.websdk. If the Portal is heavily loaded.properties file (part 11 of 19) Description determines the number of days that the database retains the history for RSM message Valid values are positive whole numbers or positive numbers with a single-digit decimal (for example.history. The default and recommended value is 0.history.history.websdk. the database job clears these alert notifications from the database.Configuration file properties Table 51 Property Properties in drmop.5 portal.history.websdk. Example: portal.websdkalertjob. which retains the history for one-half of a day. the alert notification may not be sent.history. The default and recommended value is 12.history.websdk.retention portal.rsmmessage.rsmmessage.5). Example: portal. 1. This means that if the earlier alert notifications have not been cleared for the last 45 days.parameterstatushistory. and resource contention occurs. but remains in the alert history. Example: portal.retention determines the number of days that the database keeps history for websdk alert job Valid values are positive whole numbers.5. retention determines the number of days that the database keeps parameter status history Valid values are positive whole numbers. retention=45 332 BMC Performance Manager Portal Monitoring and Management Guide .

1.jmsmessages.properties file (part 12 of 19) Description portal.delete. The default and recommended value is 14 (which is the same as the portal.jmsmessages.enable determines whether unwanted JMS messages are purged at startup Valid values: s true (default and recommended) = unwanted JMS messages are purged at startup false = JMS messages are not purged at startup s Example: portal.5).history.retention determines the number of days that the database retains the history for event notification Valid values are positive whole numbers or positive numbers with a single-digit decimal (for example.history.websdk.event.websdk. retention=14 portal.history.eventnotification.Configuration file properties Table 51 Property Properties in drmop.delete.history.history.retention default) Example: portal.enable =true Appendix C BMC Performance Manager Portal files 333 .eventnotification.

alertjob.alertjob. thus causing the notifications that are hung to resume automatically.parameter.enable false = (default) purging is not enabled at start up true = (recommended) enables purging of all existing alert jobs at startup portal. This setting reduces the startup time of BMC Portal and causes any notifications that are hung to resume automatically.truncate. Once you restart BMC Portal. you must set the property to the default value. disabled=true 334 BMC Performance Manager Portal Monitoring and Management Guide . Once you restart BMC Portal.history. you must restart the BMC Portal application server.properties file (part 13 of 19) Description determines whether purging is enabled at startup for all existing alert jobs Valid values: s s portal.truncate.history. Example: portal.enable= false portal. Changing this value to false prevents you from creating those reports.summarization.parameter. After you set the value to true. false. You should enable this property only if BMC Supports recommends you to do so. This makes restarting BMC Portal easy.enable removes all the alert jobs from the memory.history.disabled determines whether the Portal summarizes raw data Many of the reports use only summarized data.truncate.history.summarization. Example: portal.history. you must set the properties to false.Configuration file properties Table 51 Property Properties in drmop. You do not need to restart BMC Portal again.alertjob.

BMC Portal performs the summarization only once every day instead of once in every half an hour. then the task is scheduled to run at 2 A. determines whether the external summarization is enabled configured to use the database task instead of using the BMC Portal application server This helps avoid using the BMC Portal application server for the BMC Portal summarization task.parameter.parameter.properties file (part 14 of 19) Description portal. enabled=true.history. The Top N reports display the data until the last summarization was performed. enabled and the portal. Note: s You must modify the portal.history. enabled=false portal.externalsummarization.parameter.history.externalsummarization.parameter.M. schedulehours properties to enable external summarization.history. After you have set this property.Configuration file properties Table 51 Property Properties in drmop.parameter. s s Appendix C BMC Performance Manager Portal files 335 . determines the time at which the external summarization schedulehours is scheduled (time of the database server) If you set portal. by default.history.parameter.history.externalsummarization. Example: portal. every day.externalsummarization.externalsummarization.externalsummarization.

see “Purging unknown and unused events from the event table” on page 149.enabled false (default) = purging is disabled true = purging is enabled Example: portal.history.parameter. 336 BMC Performance Manager Portal Monitoring and Management Guide .cleaninactiveparameter.parameter.history. portal. you can enter multiple values and separate them by a comma (no spaces).summarizationDataPoint.summarization DataPoint.parameter. 6 sets the job to run on Sunday.purgepsdp. application classes. see “Purging inactive data from the Portal history tables” on page 147. Example: portal. For example.history. cleaninactiveparameter. scheduledays determines the days on which the retention job to purge inactive data runs Valid values: s s s s s s s 1 = Sunday (default and recommended value) 2 = Monday 3 = Tuesday 4 = Wednesday 5 = Thursday 6 = Friday 7 = Saturday If you want the job to run on more than one day.properties file (part 15 of 19) Description determines whether purging is enabled or disabled for inactive data that was generated for elements.2. Monday. and Friday.history.Configuration file properties Table 51 Property Properties in drmop. a value of 1.purgepsdp. scheduledays=1 For more details.parameter. or parameters that were deleted or that do not exist Valid values: s s portal.enabled=false For more details.

properties file (part 16 of 19) Description determines the time (the hour on the hour) when the retention job to purge inactive data runs Valid values are 10 (10:00 a. Example: portal.summarizationDataPoi nt.element. schedulehours portal.history.history.m. No minutes are recognized. The default and recommended value is 19 (7:00 p. and 7:00 p.m. schedulehours=19 For more details. The value must represent an hour between 10:00 a. the default value is 428 days.) through 19 (7:00 p.history.m.parameter.parameter.purgepsdp. see “Purging unknown and unused events from the event table” on page 149.summarizationData Point.).m.retention determines the number of days that the database keeps summarized parameter values s Increasing the retention period requires more disk space. s s Example: portal.retention=92 Appendix C BMC Performance Manager Portal files 337 .history. BMC recommends a setting of 92 days.purgepsdp.parameter. portal.m. however. The time set for this property is the time on the database server.).Configuration file properties Table 51 Property Properties in drmop. Reducing this retention period reduces the time period in which you can chart data points.

However. retention=14 portal. or hardware failure). Significantly decreasing the retention period.private.history.properties file (part 17 of 19) Description sets the number of days that the database retains raw parameter data values Database performance is optimized for a 14-day retention of raw data if the report update interval is higher than 5 minutes.queueWatcher. workerThreads=10 portal.value.size= 2097152 338 BMC Performance Manager Portal Monitoring and Management Guide .parameter.file. Example: portal.ssh. s Default value: portal.rsmcommunication. BMC recommends that you set history retention at 7 days.Configuration file properties Table 51 Property Properties in drmop.file.value. to 1 or 2 days.history.ssh.size sets the number of bytes for the maximum size of the SSH private key file Most private key files are small.parameter.key. upgrades. s portal.retention Increasing the retention period can adversely impact database performance and requires more disk space.queueWatcher. workerThreads sets the number of worker threads created to watch queues and process incoming data Do not modify this property unless instructed to do so by Customer Support.max.max.private. can cause the Portal to lose data that was not summarized (in the event of a Portal downtime caused by maintenance.rsmcommunication. Example: portal. Setting a maximum size value keeps users from accidentally specifying a file of an incorrect type.key.

transaction.timeout portal. Example: portal.upgrade. Example: snmp. Please do not decrease the timeout below the default values.events. or 5 minutes.process specifies the maximum number of parameters included in an SMNP trap Valid values are positive whole numbers.timeout.sec specifies the number of seconds that the Portal waits for the RSM to return the instance discovery results.max.protocol=http snmp. Example: portal. The default time out is 108000 seconds (30 hours).max.to.events.protocol protocol used to download RSM from the Portal Valid values: s s http (default) https Example: rsm.sec=300 rsm. The default discovery time is 300 seconds.timeout=108000 portal.download.timeout.transaction.properties file (part 18 of 19) Description specifies the time out in seconds for the process of solution upgrade.utd. The default maximum number of parameters in a trap is 5.process=5 Appendix C BMC Performance Manager Portal files 339 . It can cause the solution upgrade to fail on large size portal.download.parameter.parameter.upgrade.utd.Configuration file properties Table 51 Property Properties in drmop. after which a timeout occurs Valid values are positive whole numbers.to.

Configuration file properties Table 51 Property Properties in drmop.properties file (part 19 of 19) Description determines whether the application instance name is sent in the SNMP trap for singleton application instances Valid values: s s snmp.and Parameter-level notifications. you must restart the Portal after applying the new properties.trap. you see the following results: s false (default)--Windows Event Log Monitor | Portal Log true--Windows Event Log Monitor | Portal Log | Log Count s This applies for both Element.showlastapp=false 340 BMC Performance Manager Portal Monitoring and Management Guide .trap.trap.showlastapp determines whether the last application in the application hierarchy is displayed in the SNMP trap Valid values: s false (default)-.last application in the hierarchy is not displayed true-. For change to take effect. Example: snmp.showappinstsingleton=false snmp.trap.application instance name is sent For change to take effect.showappinstsingleton false (default)-. you must restart the Portal after applying the new properties.application instance name is not sent true-.last application in the hierarchy is displayed s For example. if Windows Event Log Monitor | Portal Log | Log Count is the hierarchy sent in the SNMP trap. Example: snmp.

locking padm.patsdk. the parameters go into an unknown state and generate unknown events.locking=true padm. Using this property improves the notification feature because the unknown events are not generated.schedule. Example: padm.patsdk. CollectionJob. set the value of the com.services. When there is no data collected for parameters.CollectionJob. The product also does not generate any unknown events for the infrastructure elements and therefore does not send notifications for unknown events.i gnoreUnknownState=true com.bmc.patsdk. there is a possibility that unknown events are generated for the Business components.Configuration file properties Table 52 Property Properties in rsmcfg.migrate.properties file (part 1 of 2) Description restricts the PATROL Agent refresh (synchronization) process to one user when set to true If a user attempts to synchronize the thresholds of integration Performance Managers while another user is running this operation.CollectionJob.schedule.bmc. If BMC Performance Manager Portal is integrated with Impact Portal.ignoreUnknownState Table 53 Property Properties in the padm.services.ignoreUnknown State property to true. To stop this from happening.patrol. These unknown events fill up the EVENT table and hamper the product’s performance and notifications. If RSM fails to collect data.migrate.limit sets a limit on the number of migration jobs that can be scheduled without pause Example: padm. Example: com.bmc.migrate. BMC Performance Manager Portal shows the previous status of that parameter and displays No Data in the Chart or Table view.migrate.services.patrol. the second user gets an error message.properties file Description stops unknown events from filling up the EVENT table.patrol.limit=25 Appendix C BMC Performance Manager Portal files 341 .

update.migrate.xml./DB2EEE_DIAGLOG/ DiagLogO padm.properties.schedule.Configuration file properties Table 53 Property Properties in the padm.wait.update.max padm.migrate.wait=10 padm.list=/LOGMON/ LOGStatus.schedule.xml file.migrate.migrate. To update the properties in rsm-RsmHostName-xmbean. which you should never edit.migrate.wait sets the number of seconds that the migration collector pauses when the schedule limit is reached Example: padm. DisplayName Description Version a This file is reinitialized from the rsm-RsmHostName-xmbean.threshold.migrate.threshold.list provides a list of comma separated application class/parameter name pairs to exclude during threshold synchronization For each parameter.max=100 padm.timeout sets the number of seconds that the migration collector waits for a response from the PATROL Agent before a timeout occurs Example: padm.timeout=1000 Table 54 Property Properties in rsm-RsmHostName. 342 BMC Performance Manager Portal Monitoring and Management Guide .propertiesa file on the RSM computer Description name of the RSM that displays in the user interface description for the RSM computer version number of the RSM program Do not edit this value.exclude./DB2_DIAGLOG/DiagLogOK.migrate.wait.schedule.properties file (part 2 of 2) Description sets the maximum number of PATROL Agents that can be migrated at one time Example: padm.migrate.schedule. edit rsm-RsmHostName.exclude. use the following format and specify the PATROL names for the application class and parameter: /InternalApplicationClassName/InternalParameterName Example: padm.

the RSM ignores the value and uses 60000 milliseconds.propertiesa file on the RSM computer (part 1 of 2)b Description URL that the RSM uses to authenticate itself with the Portal whenever it initiates communication with the Portal defines the authentication credentials used to connect to the Portal Credentials are encrypted by the installation program.patsdk-snmp.timeout patsdk-snmp-solution.patsdkcommandshell. the RSM requests jobs to perform and uploads data if necessary. Name name of the Portal Appendix C BMC Performance Manager Portal files 343 .showWholeTrap =false Table 56 Property Properties in portal-PortalWebServer.patsdk-snmp-trap .timeout patsdk-snmp-solution. AuthenticationHostUrl AuthenticationInfo HeartbeatInterval frequency with which the RSM contacts the Portal once it has authenticated and established a session On each heartbeat. Master flags this Portal as the master Portal to which this RSM communicates (out of possibly many Portals) This information is used primarily for determining when the RSM needs to upgrade itself.properties file on the RSM computer Description number of seconds that the Command Shell collector waits for a value before timing out number of seconds that the SNMP collector waits for a value before timing out determines whether the Portal displays the whole value of the the trapped process parameter Valid values: s s patsdk-commandshell-solution. MaxStoreAndForwardTime sets the time in milliseconds that the RSM holds unsent messages in memory before discarding them The default time is 900000 milliseconds (15 minutes).showWholeTrap true=Portal displays the whole trap false (default)=Portal displays part of trap Example: patsdk-snmp-solution.Configuration file properties Table 55 Property Properties in the rsm.MatchedTrapContents. the Portal will respond with new or updated configuration for jobs if any remain to be assigned. the RSM follows a command to upgrade when the command comes from the master Portal. MatchedTrapContents.patsdk-snmp-trap. Specify a value of 60000 or higher. If you specify less than 60000.

344 BMC Performance Manager Portal Monitoring and Management Guide .xml. You must restart the RSM after changing any of the properties in this file. the password is set to admin: admin=admin If you change the user name in jmx-consoleroles. modify portal-PortalWebServer. you must also change the user name value in this file. the user name is set to admin: admin=JBossAdmin.propertiesa file on the RSM computer (part 2 of 2)b Description determines whether the RSM uses SSL to communicate with the Portal not supported in this release number of milliseconds the RSM waits to receive a response to a connection to the Portal number of milliseconds that the RSM waits to connect to the Portal After the connection is established.properties.HttpInvoker rsm/server/rsm/conf/props/jmx-console-roles.properties.properties rsm/server/rsm/conf/props/jmx-console-users. which you should never edit. UseCompression Timeout ConnectionTimeout a This file is initialized from the portal-PortalWebServer-xmbean. b Table 57 File name JMX credentials on RSMs Property userName=JBossAdmin.Configuration file properties Table 56 Property UseSsl Properties in portal-PortalWebServer.properties userName=password By default.HttpInvoker By default. the Timeout attribute defines how long the connection remains open waiting for a response.xml file. To update the properties in portal-PortalWebServer-xmbean.

BMC Performance Manager Portal log file To help diagnose monitoring errors that occurred on the Portal. you can access the portal.nn log file. You can find this file in the following location: %RSM_HOME%\RSMversionNumber\server\rsm\deploy\padmr-mbean. The RSM runs as a Java Service Wrapper.Log files Log files Log files can help you diagnose problems encountered by the BMC Performance Manager Portal components. You can find both log files in the following location on the RSM computer: %RSM_HOME%\RSMversionNumber\server\rsm\log\ To help diagnose problems that might occur when mining data from the PATROL Agents.log file. wrapper. you can access the padm-err.sar\padmbase\log Appendix C BMC Performance Manager Portal files 345 .log is used to diagnose problems in cases where the RSM is not getting any s CPU time or when it appears to be hung. located in the following directory: s s (Windows) %BMC_PORTAL_KIT%\appserver\websdk\tools\jboss\server\all\log (Solaris) $BMC_PORTAL_KIT/appserver/websdk/tools/jboss/server/all/log RSM log files The RSM provides the following files that you can use to diagnose problems with the RSM: s rsm*.log helps diagnose problems that the RSM has when monitoring infrastructure elements.

RSM log files 346 BMC Performance Manager Portal Monitoring and Management Guide .

The most common application severities are OK. See also dedicated RSM. Users can view and select a clustered RSM to collect parameter data from an element as if it was a dedicated. B backbone On the Internet or other wide area network. The collection interval is sometimes referred to as the monitoring interval. application severity The condition of an application class or an application instance. also.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Glossary A application class The object class to which an application instance belongs. the backbone represents the physical location (company name) of the computer in the network. You can set the collection interval for an application class when you add an element to the account or at a later time. In BMC Performance Manager Portal. PerfMon. Glossary 347 . and shared RSM. the representation of the class as a container (UNIX) or folder (Windows) on the PATROL console. shared. or global RSM. collection interval The interval at which the RSM collects parameter values for the parameters in an application class. global RSM. warning. Compare with report update interval. For example. collector A module of the RSM program that measures and gathers parameter values on the monitored elements. An application class or instance icon can also show additional conditions. and PATROL data from the monitored elements. C clustered RSM Two or more physical Remote Service Monitors (RSMs) clustered to run as a single entity. and alarm. the collector modules can gather SNMP. a set of paths that local or regional networks connect to for long-distance interconnection.

desktop file See PATROL desktop file. D dedicated RSM An RSM that is located with your monitored systems. operations personnel might be notified within five minutes of a problem occurrence. and is installed by a user in the account. A custom Performance Manager is composed of custom application classes. The Portal enables you to specify an encoding system when you save data to a file. You can access the PME when you log on to the Portal with Portal administrator credentials. manipulating. through a process of shuffling. and a director after one hour (if the problem still exists). Compare with global RSM and shared RSM. escalation procedure The process of referring a problem up the chain of command. a manager would learn of it after 15 minutes. E element profile An element profile acts as a template that you can apply to multiple elements and enables you to quickly change the properties associated with your infrastructure elements. For example. encoding system A method of assigning binary codes to represent characters of data. and processing the bytes using logical operations. measures only the elements in an account. cryptographic hash An algorithm that takes an entire message and. custom application class An application class created from the Portal pages that compose the Performance Manager Editor (PME). Compare with custom Performance Manager and solution Performance Manager.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 core Performance Manager A Performance Manager provided with BMC Performance Manager Portal and available for use whether or not you install Performance Managers from a Solutions CD or another source. Custom application classes are contained in custom Performance Managers. 348 BMC Performance Manager Portal Monitoring and Management Guide . Element profiles are especially useful when you need to manage many elements that share common properties. custom Performance Manager A Performance Manager created with the PME. generates a small fingerprint or message digest of the data.

Instances can be specified (processes and logs) or automatically discovered by the RSM (disk drives and network interfaces) or PATROL Agent. infrastructure element An addressable object that can be monitored. Glossary 349 . I impersonation Posing as another user to gain access to an account. The first digit of the status code defines the class of response.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 F Full Access A permission or right that enables you to fully configure the account. H HTTP response code A three-digit integer that indicates the result of the attempt to understand and satisfy an HTTP request. Compare with dedicated RSM and shared RSM. and by setting up the goals and thresholds that correspond to the service level agreement. K Knowledge Module (KM) A set of files that define how a PATROL Agent gathers. instance A monitored device. and is installed and maintained by a Portal administrator. Administrators can impersonate a user to assist with account configuration and troubleshooting. KMs are loaded by a PATROL Agent and a PATROL console. or application on an infrastructure element. A KM file can contain the actual instructions for monitoring objects or simply contain a list of KMs to load. by adding and deleting elements and groups. such as a managed system in PATROL. process. The last two digits do not have any categorization role. within the limits specified by the administrator. log. and presents data about resources running on a monitored computer. processes. the Portal attributes the user activity to the administrator. G global RSM An RSM that is located in a centralized data center (possibly outside your company). The BMC Performance Manager Portal can mine parameter data from PATROL Agents when you install PATROL integration Performance Managers on the Portal. It can monitor the elements for many accounts. During user impersonation.

Parameters have thresholds and can trigger warnings and alarms. parameter severity The condition of a parameter. See also Performance Manager. P PAR file An archive file that contains the components for a Performance Manager. Parameters can display data in various formats. The most common parameter severities are OK. PAR files can contain one or more application classes. If the value returned by the parameter triggers a warning or an alarm. Parameters are run by a PATROL Agent or an RSM computer. 350 BMC Performance Manager Portal Monitoring and Management Guide . Knowledge Module information.x and earlier. text. logical RSM See clustered RSM. and console layout information for PATROL Central. monitoring interval See collection interval.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 L latency The time between the initial request for data and the beginning of the actual data transfer. Management Profile A user profile for PATROL Central Operator – Windows Edition and PATROL Central Operator – Web Edition that is stored by the console server. parameter The monitoring element of the BMC Performance Manager Portal. warning. and alarm. information about systems that you are currently managing. A Management Profile is similar to a session file and contains information about custom views. your current view of the PATROL environment. The format of the MIB is defined as part of the SNMP. SNMP uses standardized MIB formats that allow any SNMP tool to monitor any device defined by a MIB. M Management Information Base (MIB) Management Information Base (MIB). the RSM sends an event to the Portal web server. A formal description of a set of network objects that can be managed using the Simple Network Management Protocol (SNMP). and Boolean. such as numeric. Management Profiles replace the desktop files and session files that were used in PATROL 3.

A simple regular expression is a sequence or a pattern of characters that is matched against a string of text during searches and replace operations. regular expressions are used in pattern matching and substitution operators. regular expression Sometimes referred to as regex. Remote Service Monitor (RSM) The BMC Performance Manager Portal component that provides remote monitoring of the elements in your account. The RSM polls the elements in your account at regular collection intervals and sends parameter data to the Portal upon detection of parameter status changes. Regular expressions are used for configuring text thresholds. Performance Managers are contained in PAR files that you can install from Solution CDs or by loading from the Portal tab in the BMC Performance Manager Portal. Portal administrators can add new providers and can send email to all administrators and users on the Portal. and accounts. PATROL desktop file A file created by PATROL Console for Microsoft Windows and PATROL Console for UNIX. Desktop files usually have a . Additionally. Glossary 351 . Portal administrators use superadmin/superadmin to log on as a Portal administrator. Unless changed by the administrator. a stand-alone event manager (PEM). Portal administrator An administrator that has both Edit and See Other Providers and Their Accounts permissions.dt extension. See also PAR file. Performance Manager A collection of one or more logically-related application classes that have been packaged together to provide infrastructure monitoring for business-critical computers or applications. Portal administrators can view the Accounts. PATROL Integration products. The combination of the dataset and the Reconciliation Identity is unique. and SNMP consoles. and approve or reject account requests for that provider. The agent is used to monitor and manage host computers and can communicate with the PATROL console.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 PATROL Agent The core component of PATROL architecture. R Reconciliation Identity An attribute that uniquely identifies a BMC Atrium CMDB object for a given dataset. provider administrator An administrator with only Edit permission can view the Accounts and Provider tabs and can configure provider properties. Provider. administrators. and Portal tabs and configure global defaults that affect the Portal and all providers on the Portal.

Compare with collection interval. The PATROL Central component that delivers application data among the PATROL Central components. Simple Network Management Protocol (SNMP) Simple Network Management Protocol. global RSM. RSA stands for Rivest. the RSM also sends parameter data to the Portal at the report update interval for each element. It also provides monitoring statistics about your account. report update interval Regardless of parameter status. start and stop the RSM. can monitor the systems and devices of more than one account. Depending on the setup of your account. shared RSM An RSM that is located in a centralized data center. and Adleman. Shamir. and shared RSM. See also Remote Service Monitor (RSM). This utility enables you to configure. See also dedicated RSM. When you apply shared credentials to an element. RSA algorithm A public-key encryption system based on the factoring problem. The protocol governing network management and the monitoring of network devices and their functions. Compare with dedicated RSM and global RSM.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 Regardless of parameter status. you can quickly change the credentials for the element when the credentials change on the monitored elements by updating the properties for a set of shared credentials. and is installed and maintained by a provider administrator who has Edit permission. You can view these parameter values on the Status and Reports tabs. 352 BMC Performance Manager Portal Monitoring and Management Guide . You can view parameter values that triggered an alert status on the Events tab. the frequency at which the RSM sends the most recentlycollected parameter data to the Portal. the developers of the RSA public-key encryption system and the founders of RSA Data Security (now RSA Security). The RSM also sends parameter values when it detects that a parameter has changed to or from an alert status. RTserver Real Time server. your administrator might control the location and maintenance of the RSMs that monitor your account. S shared credential Authentication credentials that you can save and apply to many elements in the account. Remote Service Monitor Manager A utility for the RSM program that you access from the system tray of the RSM computer.

the device responds with the requested information.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 SNMP community string A user name or password that allows access to the statistics of a router or other device when sending SNMP traps. it gets the server’s fingerprint. Within the PATROL Agent. solution Performance Manager A Performance Manager installed from a Solutions CD. If the community string is correct. SSH Secure Shell. Network administrators use SSH to remotely control web and other kinds of servers. SNMP trap A condition which. SSH commands are encrypted. If the community string is incorrect. the device simply ignores the request. store and forward A mechanism that ensures that if an event cannot reach its destination. Compare with core Performance Manager and custom Performance Manager. or created using the BMC Performance Manager SDK. When an SSH client connects to an SSH server. it is saved in a file and sent when a viable connection to the destination becomes available. downloaded from the BMC Software EPD website. results in an SNMP agent issuing a trap message to other SNMP agents and clients. SSH fingerprint Each SSH server has a unique host fingerprint. The client can then optionally verify the server’s fingerprint in an internal database. when satisfied. all events can be translated to SNMP traps and forwarded to SNMP managers. Sometimes known as Secure Socket Shell. or prompt the user for the fingerprint. Glossary 353 . SSH is a UNIX-based command interface and protocol for securely accessing a remote computer.

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 354 BMC Performance Manager Portal Monitoring and Management Guide .

described 50 account reports 153 account types settings for providers 65 Account Types task. described 65 application class disabling alarm or warning 287 application class editor. described 134 multiple instances 135 parameters and thresholds 114 publishing 135 requirements 135 single instance 135 types 135 application classes. described 65 accounts predefined name for new Portal 63 predefined name for self monitoring 312 Accounts tab tasks for administrators 64 ACE. custom command shell collector 136 data collection requirements 135 PerfMon collector 137 publishing application classes 135 SNMP collector 138 Application Collector Status parameter 136 application server component on the Portal 19 Applying filters for CDE and HDE 212 arimportcmd command for importing reconciliation rules 222 Index 355 . See importing Performance Managers or creating Performance Managers addPATROL command in bpmcli 260 administrator for Portal-wide configuration 63 administrator for provider-wide configuration 64 administrator permissions 63 administrator tabs Accounts tab 64 Portal tab 66 Provider tab 64 Administrators task. 137. 142 collectors 136.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 About task. described 134 alarm direction in a parameter. 121 security requirements 74 alarm and warning thresholds in a parameter. described 134 AlarmPoint. described 65 agent integration Performance Managers. See PATROL integration Performance Managers agent-based monitoring adding infrastructure elements to account 30–36 described 18 minimum and maximum values for mapped thresholds 122 monitoring the PATROL Agent 317 parameter mappings between KMs and Performance Managers 122 security requirements 75 threshold mappings between KMs and Performance Managers 122 agentless monitoring adding infrastructure elements to account 25 described 18. 257 adding a clustered RSM for the account 95 adding infrastructure elements to account adding objects in the BMC Atrium CMDB 42 agent-based monitoring 30–36 agentless monitoring 25 using the command-line interface (bpmcli) 255 adding Performance Managers to the Portal. described 50 Account Information task. See PME ACS. See PME application class reports 160 application classes characteristics 133 collection interval 20. event integration with the Portal account level integration 56 enterprise level integration 228 Alerts to Show list on Events tab 249 allocating Java heap memory for the RSM Java VM 106 allowed characters user names 63 Appearance task. See Application Collector Status parameter activity logs to view user activity viewing user activity logs 64 adapter_host slot name 231 addElements command in bpmcli 255. 138 custom 135–138 definition files 135 described 114 instance types.

130 BMC PM Monitor (core Performance Manager) 130. 186 BMC Performance Manager Portal rsm-RsmHostName.properties configuration file 342 BMC Performance Manager Portal CLI. described 42 searching the BMC. See BMC II Web Services BMC Impact Manager solutions. contacting 2 BMC. See CLI for BMC Performance Manager Portal BMC Performance Manager Portal SDK 114 BMC Performance Manager Portal.ASSET dataset in the BMC Atrium CMDB 42 BMC_PM-BusinessView. described 17 BMC Performance Manager System Availability Report 187 356 BMC Performance Manager Portal Monitoring and Management Guide . event integration with Portal 231 BMC Performance Manager Availability Report 166 BMC Performance Manager Logical Domain Report 166. 312 BMC Remote Service Monitor service 70 BMC Reporting Foundation 3. importing 170 BMC-Performance-Manager-Portal-MIB described 239 location after installation 237 location on CD 236 OID described 237 bmcPMPortalAccountName OID 240 bmcPMPortalApplicationHierarchy OID 243 bmcPMPortalApplicationInstanceName OID 241 bmcPMPortalApplicationName OID 241 bmcPMPortalDetectedTime OID 242 bmcPMPortalDetectedTimeUtcStr OID 242 bmcPMPortalElementName OID 242 bmcPMPortalElementState OID 242 bmcPMPortalElementStateChange OID 240 bmcPMPortalEventReason OID 243 bmcPMPortalGroupName OID 240 bmcPMPortalHostName OID 241 bmcPMPortalParameterErrorCode OID 242 bmcPMPortalParameterName OID 241 bmcPMPortalParameterState OID 241 bmcPMPortalParameterStateChange OID 239 bmcPMPortalParameterThresholdValue OID 242 bmcPMPortalParameterValue OID 241 bmcPMPortalRsmClusterName OID 242 bmcPMPortalRsmClusterState OID 243 bmcPMPortalRsmName OID 242 bmcPMPortalRsmState OID 242 bmcPMPortalRsmStateChange OID 239 bpmcli commands See also CLI for BMC Performance Manager Portal addElements 255 addPATROL 260 deleteElements 262.properties 343 AuthenticationInfo property in portalPortalWebServer.00 downloading and installing 162 BMC Software.xml file. overview 228 configuring non-secure event integration 231 configuring secure event integration 229 high availability configuration 228 importing SSL certificate 229 user account notifications 56 BMC Impact Integration Web Services. described 50 BMC Atrium CMDB as a source for infrastructure elements 55 BMC Performance Manager Portal as a consumer 220 BMC Performance Manager Portal as a provider program 221 changing the number of hosts to return when adding elements 325 configuring for the Portal 221 filtering infrastructure objects 43 importing reconciliation rules 221 integration with Portal. 263 exportParameterHistory 272 getApplicationsForElement 276 getElements 277 getParameterHistory 278 getParameters 281 getPortalVersion 269.2. 324 avoiding duplicate events 233 BMC Performance Manager Zone and Pool Report 166.properties 343 auto refresh for object views 44 availability report formula 157. 186 BMC PM for Lightweight Protocols–DNS (core Performance Manager) 130 BMC PM for Lightweight Protocols–Ping (core Performance Manager) 130 BMC PM for Lightweight Protocols–Port Monitor (core Performance Manager) 130 BMC PM for SNMP Traps (core Performance Manager) 93.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 authentication credentials for monitoring 22 AuthenticationHostUrl property in portalPortalWebServer. 282 getSubApplications 283 B base event class for event integration 231 base event class slot names 231 Blackout Periods task.ASSET dataset 42 BMC Atrium CMDB Consumers 220 BMC Atrium CMDB Status for an element 44 BMC Atrium CMDB. receiving data from Portal 219 BMC DatastoreCLI executing database queries 285 exporting element configuration details 292 finding ACS errors 289 BMC II Web Services configuring event integration.

multiple parameters 160 parameter history.properties 343 portal-PortalHostName-xmbean.properties 341 Command Shell collector guidelines for custom application classes 136 timeout value for application classes 343 command-line interface for Performance Manager data.bmc. See BMC Atrium CMDB collection interval for application classes 20.xml 321.properties 320 portal-PortalHostName. See CLI for BMC Performance Manager Portal common slots in the base event class 231 communication between Portal and RSM 71.properties 320 rsmcfg. 66. 322 jboss-service. top-level object group 59 configuring 95 described 71 security considerations 94 upgrades 96 CMDB. 66 Mass Email 67 Monitoring On/Off 55 Notifications 56. 344 rsm.patsdk. single parameter 46 checking CDE or HDE error messages 215 child classes described 134 element profiles 52 CI.patrol.CollectionJob. receiving data from Portal 224 Change Password task.ignoreUnkn ownState property in rsmcfg.properties 341 rsm-RsmHostName. 73 communication interruptions between RSM and Portal 72 components of BMC Performance Manager Portal 18 configuration files datafeed. 67 Shared Credentials 60 C calculating element availability 157 CDE Configuring the external CDE movement 206 configuring the external CDE movement 208 cell. 320 drmop.properties 344 jmx-console-users. 342 configuration items in BMC Atrium CMDB 219 configuration tasks About 50 Account Information 50 Administrators 65 Appearance 65 Blackout Periods 50 Change Password 51 Dashboards 51 Element Profiles 51 Elements 55 Global Properties 66 Licensing Information 65. 105 changing SNMP trap version 244 changing the maximum number of hosts to return from the BMC Atrium CMDB 325 characters allowed user names 63 charts dashboard 161 list of all charts available on Reports tab 151 parameter history.xml 321 jmx-console-roles.properties 344 padm.properties 191.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 refreshDatafeedMetadata 264 refreshPATROL 266 savePassword 269 user restrictions 253 Business.services. 142 collection methods. 66 Object Groups 59 Performance Managers 67 Personal Preferences 60 Properties 66 Remote Service Monitors 60. described 51 changing RSM credentials 104.properties 320. See data collection methods for Performance Managers collectors for custom application classes Command Shell 136 PerfMon 137 SNMP 138 com. See configuration items in BMC Atrium CMDB CLASS slot name 231 CLI for BMC Performance Manager Portal See also bpmcli commands adding a single element to the Portal 255 adding multiple elements to the Portal 257 deleting a single element from the Portal 262 deleting multiple elements from the Portal 263 exporting parameter history data to external database 272 getting all the elements in an account 277 getting child classes from specified application classes 283 getting parameter history for specified parameters 278 getting parameters from specified elements 281 getting the Portal version number 282 getting top-level applications in an element 276 hiding the user password 269 preparing client computer 252 refreshing metadata for CDE database 264 refreshing PATROL integration parameters 266 saving the user password in an encrypted file 269 synchronizing PATROL parameter thresholds in the Portal 266 user restrictions 253 clustered RSMs Index 357 .properties 320.

history.parameter.parameter.properties file 199 deactivating parameters 116 parameters in application classes 119 parameters in element profile 118 parameters in Performance Manager Editor solution 119 deactivating parameters 116 solution support 120 dedicated RSMs.PASSWORD property in sampleDatafeedTarget.enab led 146 portal.arx file 223 DB.BATCHSIZE property in sampleDatafeedTarget.OWNER property in sampleDatafeedTarget.xml file 170 installing reporting components 164 integration prerequisites 165 modifying business view to point to CDE database 171 publishing and scheduling enterprise reports 179 CSV file defining maximum size 202 CSV input files using to add elements with bpmcli 257.parameter.history. 259.period 147 overview 145 portal.properties file 205 DB. 37 using to refresh PATROL and Portal parameters 266 CSV output files datafeed output file 193. 261 using to delete elements with bpmcli 263.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 Tags 61 User Groups 62 Users 62 Configure tab 50–63 Configuring the external CDE movement 206 ConnectionTimeout property in portalPortalHostName. described 70 default (predefined) user account for the Portal 63. 121 data collection requirements for application classes 135 Data Execution Prevention.disabled 146.properties file 199 DB.events.parameter.retention 145. top-level object group 59 data collection methods for Performance Managers agentless 18. 192.statusHistory.rollover. 276 DB.parameter.externalsummarization.properties file 191.history. See DEP configuration for RSM program data extraction commands in bpmcli 270 data gaps 73 data modifications in custom application classes 135 data retention properties for object views drmop.summarizationDataPoint.sche dulehours 146 portal.history. 320 datafeedJob 191 dataImport command for importing reconciliation rules 222 dataset. gathering RSM log files 107.history. 327 portal.summarization.externalsummarization.history.biar file 168 importing BMC_PM-BusinessView. 334 datafeed utility 190–206 datafeed. 334 portal.lag.POOLSIZE property in sampleDatafeedTarget. 338 data summarization for report data 144.TABLE. 194–200 Performance Manager license information 65 custom application classes collectors 136–138 described 135–138 custom Performance Managers described 131 editing 139 customer support 3 customizing instance names for SNMP application classes 138 D Dashboards task.periods 147 drmop. 312 default user for the predefined account 63.value.events. 121 PATROL Agent integration 18. 108 continuously exporting data from the Portal 190–206 core Performance Managers BMC PM Monitor 312 delivered with the Portal 130 described 130 createDatafeedSchema file 191.history.properties file 205. 87 overriding in an element profile 53 Crystal Reports 2008 (Designer component) importing BMC_PM_Reports.properties 344 Console Server list is empty when integrating PATROL data 299 methods for PATROL integration 29 security considerations 21 consumer program for the BMC Atrium CMDB 220 contacting Support. 202.properties file 199 DB.history.retention 146.ret ention 146. 312 definition files for custom application classes 135 358 BMC Performance Manager Portal Monitoring and Management Guide . described 51 dashboards with parameter history charts 161 Dashboards. 192 credentials for monitoring avoiding system lockouts on the monitored computer 61 changing for an RSM 104.USERNAME property in sampleDatafeedTarget. 105 changing for the JMX console on the RSM 344 for monitoring infrastructure 22 for RSM program 86. 337 portal.element. 264 using to integrate PATROL parameter data 29.

events.batch. 322 drmop. 324 Element Profiles task described 51 effect on PATROL Agent integration 40 overriding properties and thresholds 53 element report data.ldap. using to integrate PATROL parameter data 32 direct service model integration 224 discovering instances on elements 135 discovering PATROL Agents using CSV files 37 using Management Profiles 30 using PATROL desktop files 32 using PET files 35 DisplayName property in rsm-RsmHostName.default. 262.formula.minutes property 155. 60 prohibiting users from changing host names 324 report update interval 142 elements and their RSMs 73 Elements task.search 325 encrypting the user password (bpmcli) 269 enterprise integration AlarmPoint 228 BMC Impact Solutions 228 described 66. 249 in Health At A Glance report 159 element host name. 218 email messages 226 events from PATROL Agents 233 SNMP traps 227 enterprise reports importing BMC_PM-BusinessView.applicationinstance.default.availability.reporting. sending from RSM to Portal 72 element reports 156 element status by time in Health At A Glance report 157 element status summary in Health At A Glance report 156 elements adding to the account 25. 131 RSMs from the Portal 109 DEP configuration for RSM program 76 Derived parameters 118 Description property in rsm-RsmHostName.up_time property 324 drmop. 263 Performance Managers from Portal 129.interval.properties 342 desktop files.alternate. 29.xml file 170 installing reporting components 164 integration prerequisites 165 publishing and scheduling enterprise reports 179 error codes in SNMP traps 246 error messages for PATROL integration 304 event class extensions for PATROL_Portal 232 event history data retention 147 event integration BMC Impact Solutions 228–232 email messages 226 SNMP traps 227 event severity for parameters.interval.availability. configuring thresholds 115 event table purging 149 retention policy 149 events purge unused 150 Events tab Alerts to Show list 249 described 247 Objects to Show list 248 page controls 249 time interval controls 152 Exceptions.properties configuration file 320.properties 342 DNS port configuration for firewall 74 drmop.change property 324 drmop.job.properties. described 55 email messages as notifications account level 56 enterprise level 226 enable.timeout.applicationinstance.minutes property 322 drmop.hostname. 255.reports.lag. 312 overview 139 published custom Performance Managers 139 solution Performance Managers 131 unpublished Performance Managers 139 element attributes in Health At A Glance report 157 element availability 157 element events in Events tab 248.period property 147 drmop.formula.reports.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 Delete option in PME 132 deleteElements command for bpmcli 262. prohibiting users from changing 324 element profile.periods property 147 drmop. 263 deleting discovered instances 135 elements from the Portal 55.exclude_time property 324 drmop.history. 257 described 55 multiple element management 51.history.reporting. top-level object group 59 exclude_time property for availability 324 excluding PATROL integration parameters to refresh 267 Export option in PME 132 E Edit option in PME 132 Edit permission for administrators 63 editing Performance Managers core Performance Managers 131.element.reports.rollover.maxinactiveminutes 323 drmop.ula. report update interval 54 Index 359 .enabledeleteinactiveinstance property 322 drmop.minutes 142 drmop.allow.topn.events.

71 H HA. top-level object group 59 installation Crystal Reports 2008 (Designer component) 164 Performance Managers on Portal 125 RSM program 76 verifying. changing on the RSM 106 heartbeat.ROOT property in sampleDatafeedTarget.CSVFILE. data points on 152 HTTP port.AccountName property in sampleDatafeedTarget.ProviderName property in sampleDatafeedTarget. BMC Performance Manager Portal 24 installation directory for RSM program 111 installing the RSM program copying from installation media 87 downloading program from the Portal 85 executing from a command line 90 locating installation log 91 G gaps in parameter data 73 general system problems described 75. ability to change for an element 324 hourly charts.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 exporting parameter data values comparative parameter history reports 161 from a parameter history chart 46 from a parameter history table 47 Top N report 155 exportParameterHistory 148 exportParameterHistory command for bpmcli 272 HDE.log 345 wrapper. firewall configuration 74 F failover for RSMs 95 FAILURE.xml file 170 certificate for BMC II Web Services Server 229 PAR files 125 Performance Managers 125 reconciliation rules for the BMC Atrium CMDB 221 inactive data. described 67. described 66 global RSMs. purge from history tables 148 INCLUSIVE_REGEX. 282 getPortalVersion command for bpmcli 282 getSubApplications command for bpmcli 283 getting the latest metadata information 214 Global Properties task.log 345 filtering infrastructure objects in BMC Atrium CMDB 43 parameter data on the Status tab 47 filters applying for CDE and HDE 212 creating 213 determining the values for filters 212 firewall configuration for application ports 74 formula for availability report 324 FTP port.properties file 200 INCLUSIVE_REGEX. firewall configuration 74 HTTPS port. See Historical Data Export utility Health At A Glance report adjusting availability formula 157. communication from RSM to Portal 72 HeartbeatInterval property in portalPortalHostName. firewall configuration 74 impact relationships in the BMC Atrium CMDB 221 impersonating users 64 importing BMC_PM-BusinessView. 324 described 156 printing 156 health monitoring for Portal 312 heap memory. 236 notifications for all accounts in a provider 66 notifications for user accounts 56 RSMs 75 traps 240 getApplicationsForElement command for bpmcli 276 getElements command for bpmcli 277 getParameterHistory command for bpmcli 278 getParameters command for bpmcli 281 getPortalVersion command 269.log 345 RSM installation log file 91 rsm*.properties file 200 INCLUSIVE_REGEX.ApplicationPath property in sampleDatafeedTarget. See BMC II Web Services IMAP server port.properties file 206 file locations BMC Performance Manager Portal module configuration files 320 portal. firewall configuration 74 full access rights and permissions 50 I IIWS.properties file 200 infrastructure status view for status 45 Infrastructure. See high availability 360 BMC Performance Manager Portal Monitoring and Management Guide .properties 343 hierarchy of an application class 133 high availability BMC II Web Services server 228 clustered RSMs 92 Historical Data Export utility configuring for use with no CDE database instance 275 exportParameterHistory command 272 refreshDatafeedMetadata 264 host names.

synchronizing thresholds and application classes 266 L Licensing Information tasks.properties 320.properties 320. described 65.properties 344 jmx-console-users.log 304. 66 Licensing tasks.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 instance name in SNMP application class 138 instance type in an application class.properties 343 maximum number of hosts to return from BMC Atrium CMDB.properties file on RSM 344 K key parameters in Health At A Glance report 158 KMs. refreshing for CDE database 264 methods of data collection agentless 121 PATROL Agent integration 121 MIB for Performance Manager Portal 237 module configuration files BMC Performance Manager Portal 319 jboss-service. described 55 J jboss-service.nn 345 portal. using to integrate PATROL parameter data configuring 30 described 29 specifying RTserver for discovering agent thresholds 300 manually uninstalling the RSM program 110 Mass Email task. described 65 load balancing RSMs 94 loading PAR files 125. preventing 61 log files collecting Portal log files for Support 107 collecting RSM log files for Support 107. 126 LOCALE property in sampleDatafeedTarget.properties 320 drmop.properties 343 MaxStoreAndForwardTime property in the portalPortalHostName. allocating heap memory for Java VM 106 metadata getting the latest information 214 synchronizing metadata refresh with CDE 215 metadata. enterprise integration 228 enterprise management systems 237 Portal-wide integration 218 provider-wide integration 218 Service Impact Manager 224 SNMP traps. 345 RSM installation 91 rsm. 341 portal-PortalHostName-xmbean. 108 padm-err.properties 320 monitoring interval.xml 321 module properties datafeed. described 67 Master property in portal-PortalHostName.properties 72 mc_host slot name 231 mc_host_address slot name 231 mc_host_class slot name 231 mc_incident_time slot name 231 mc_object slot name 231 mc_object_class slot name 231 mc_origin slot name 231 mc_origin_class slot name 231 mc_origin_key slot name 232 mc_origin_sev slot name 232 mc_parameter slot name 232 mc_parameter_value slot name 232 mc_smc_alias slot name 232 mc_smc_id slot name 232 mc_tool slot name 232 mc_tool_class slot name 232 memory for the RSM.log file 345 viewing RSM log files 107 wrapper.xml configuration file 321 jmx-console-roles. described 134 instances.xml 321 rsm.log file 345 logical RSMs. See collection interval Monitoring On/Off task. enterprise integration 227 interaction among BMC Performance Manager Portal components 19 internal account types 65 interval at which RSM sends report data to Portal 142 interval at which the RSM collects data 20. changing 325 MaxStoreAndForwardTime property in portalPortalHostName.properties file on RSM 344 jmx-console-users.properties 320 rsm-RsmHostName.properties 344 padm. 142 M Management Profiles. 322 jmx-console-roles. See clustered RSMs logs that show user activity 64 Index 361 . discovering on elements 135 integrating Portal with other products account integration 219 AlarmPoint 218.properties file 206 lockouts on systems. 219 BMC Atrium CMDB 219 BMC Impact Solutions.

described 134 parameter value range in custom application classes 135 parameters deactivating 116 deactivating from application classes and parameters 119 deactivating from element profile 118 deactivating in Performance Manager Editor solution 119 derived 118 parsing SNMP traps for product integration 238 password administration. described 56 notification templates for notification rules 57 notification transports BMC II Web Services 228–232 described 56 email messages 57 SNMP traps 227 notifications for RSM general system problems 75 Notifications task described 56. described 59 object identifier. 126 uninstalling 129 upgrading by importing individual PAR files 128 upgrading during a Portal upgrade 127 parameter disabling alarm or warning 287 parameter collection interval 20. firewall configuration 74 notification rules.migrate. 249 362 BMC Performance Manager Portal Monitoring and Management Guide .list property 342 padm.schedule.nn log file 345 page controls Events tab 248.limit property 341 padm.properties file 320.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 monitoring the Portal components 312 monitors.update.migrate. See OID object views data policies 145 Events tab 247 Reports tab 151–161 Status tab 44 time interval controls 152.locking property 341 padm.schedule.timeout property 342 padm. 341 padm-err. See application classes parameter thresholds configuring event severity 115 configuring for PATROL integration application classes 28 configuring status changes 115 overview 114 parameter type in an application class.migrate. See Shared Credentials task PATROL Agent Availability and Health Monitor (core Performance Manager) 130 PATROL Agent Availability and Health Monitor application class 317 PATROL Agent integration additional security requirements 21 avoiding duplicate events 233 communication between RSM and PATROL Agents 74 effect of element profiles 40 N Name property in portal-PortalHostName. 66 using to avoid duplicate events 233 O object group reports 153 Object Groups task. 160 Status tab 44 page description for Performance Managers page 132 PAR files deleting 129 described 125 importing 126 installing 125.migrate.schedule. 154 Objects to Show list on Events tab 248 OID individual descriptions 239 structure description for MIB 237 Ok-Unknown events purging 149 overriding element profile settings 53 overview of Portal 15 P padm.migrate.properties 343 Network Service Port firewall configuration 74 NNTP Server port.exclude. 142 parameter data filtering by status 47 gaps 73 RSM communication type 72 parameter events in Events tab 248.wait.wait property 342 padm. See RSMs msg slot name 232 multiple parameter history charts 160 multiple-instance application classes 135 Reports tab 152.threshold. 249 parameter history charts dashboard views 161 Health At A Glance report 157 multiple parameters 160 single parameter 46 Top N report 155 parameter history tables 47 parameter mapping for PATROL integration Performance Managers 122 parameter sets.migrate.max property 342 padm. 154.

externalHDE.history.apppathcache.CsvDataFeedClient.datafeed.element.return property 325 portal.hosts.element.datafeed.param.datafeed.timetolive. using to integrate PATROL parameter data 32 PATROL Event Translation.dateFormat property 195 portal.patsdk-snmp-trap .retention property 327 portal.to.refreshhours property in datafeed.queued.retention property 327 portal.properties file 193 portal.properties file 203 portal.element. monitoring 312 Portal credentials 63 Portal history tables purging inactive data 147 Portal integration AlarmPoint 228 service model 219.limit property 248. using to integrate PATROL parameter data 35 Ping application.event.timeout property 343 patsdk-snmp-solution.datafeed.history.timeout property 343 patsdk-snmp-solution.datafeed.maximumsize 202 portal.param.alertjob.refreshhours property in datafeed.prevent. 121 publishing 135 removing from the Portal 129 solution 131 upgrading 127 verifying upgrades 27 Performance Managers license reports for accounts in a provider 65 Performance Managers page.externalHDE.externalHDE.threadpool.limit property 325 portal.cmdb.history.rollover. 27 threshold configuration 28 threshold discovery 28 threshold mapping 122 PATROL_Portal event class extensions 232 patsdk-commandshell-solution.MatchedTrapContents.size property 276 portal. described Performance Managers agentless 18.externalCDE.datafeed.properties file 193 portal.properties file 204 portal.datafeed. described 131 POP server port.events.unknown property 326 portal.properties file 205 portal.properties file 204 portal.enabled property in datafeed.patsdk-snmp. 50 permissions for monitoring Portal components 312 Personal Preferences task.apppathcache.datafeed.history.showWholeTrap property 343 paying account types 65 PerfMon collector 137 Performance Manager Editor.size property in datafeed.datafeed.truncate.event.apppathcache.size property in datafeed.enabled property in datafeed.schedulehours property in datafeed.CsvDataFeedClient.threadpool.events.events.period property 328 Index 363 .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 error messages 304 parameter mapping 122 Performance Managers described 121 properties file 341 RSM security requirements 75 setting the maximum number of Agents to refresh at a time 342 synchronizing more than 100 elements 40 synchronizing thresholds and application classes 266.limit property 248. 342 PATROL desktop files.filenameRoot property 194 portal.properties file 203 portal. 224 SNMP traps 227 Portal overview 15 Portal status view 45 Portal tab tasks for administrators 66 portal. 121 automatic installation 125 core 130 custom 131 deleting 129 deployed to RSMs 73 described 17 editing custom published Performance Managers 139 editing unpublished Performance Managers 139 importing 126 installed on the Portal 73 installing manually 126 location in the Portal 17 methods of data collection 18 overview 73 PATROL integration 18. schedulehours property in datafeed.search.enable 334 portal.seconds property in datafeed.datafeed. firewall configuration 74 Portal administrator 63 Portal administrator credentials 86 Portal and RSM communication 71 Portal application server component of the Portal 19 Portal components. described 132 Performance Managers task. described 67 permissions and rights for users 17.seconds property in datafeed.limit property in datafeed. described 60 PET files. firewall configuration 74 PME.properties file 202 portal. 326 portal.externalCDE.datafeed.statusHistory.timetoidle. See PET files PATROL Integration option for adding elements 29 PATROL integration Performance Managers See also PATROL Agent integration described 18.properties file 203 portal.CsvDataFeedClient.parameter.externalCDE.properties file 193 portal.datafeed.events.datafeed.properties file 204 portal.max.patsdkcommandshell. See PME.printHeader property 194 portal. 325 portal.csvfile.

cleanunknownevents .parameter.delete.disabled property 334 portal.purgeunused.purgeunknown.retention property 332 portal.summarizationDataPoint. 275 refreshing object views 44 refreshPATROL command for bpmcli 266 remote monitoring agent-based 18.eventnotification.websdk.retention property 338 portal.file. element profile change 54 364 BMC Performance Manager Portal Monitoring and Management Guide .retention property 331 portal.parameter. 121 Remote Service Monitors task.events.queueWatcher.parameter.size property 338 portal.history.events. described 66 provider administrator 64 provider administrator credentials 86 provider credentials 64 provider program for the BMC Atrium CMDB 220.parameter.websdk.schedulehours 150 portal.retention property 333 portal.scheduledays property 330 portal.scheduledays 148 portal.history. 345 portal.parameter. 67 Remote Service Monitors.events.history. 72 report update interval.schedulehours 149 portal. 221 provider reports 65 Provider tab tasks for administrators 64 proxy server configuration for an RSM 102 Publish option in PME 132 publishing Performance Managers 135 purge event table 149 purge events unused 150 R read-only permission for administrators 64 read-only rights and permissions for users 50 refreshDatafeedMetadata command for bpmcli 264.cleanin activeparameter.purgeunused.history.history.schedulehours property 331 portal.retention property 331 portal.enabled property 328 portal.purgepsdp.properties configuration file 343 portal-PortalHostName-xmbean.history. RSM computer 76 primary user.history.timeout.cleanin activeparameter. firewall configuration 74 predefined settings account 63.parameter.history. described 60.purgeunknown.xml configuration file 344 ports.parameter.history.cleanunknownevents . 312 Portal administrator 64 provider administrator 64 user 63.history.history. See RSMs RemoteServiceMonitor.history.retention property 332 portal.purgeunknown.parameter.purgeunused.transaction. 42.websdkalertjob. 154 report for provider 65 report update interval affect of state change on interval 142 described 20.history.scheduledays 150 portal.scheduledays property 329 portal.history.agentstatushistory.websdk. 156 retention policies for data 145 standard parameter values 143 summarization of data 144 time interval controls 152.history.history. 66.purgeunknown.utd.max.history.summarizationDataPoint.schedulehours property 337 portal.summarization.timeout property 339 portal.events.ssh.history.retentio n property 337 portal.exe file for a command line installation 89 removing Performance Managers 129 report data account view 153 application class view 160 infrastructure element view 156 object group view 153 printing 155.purgeunknown.purgepsdp.jmsmessages.history.history.purgepsdp.workerThreads property 338 portal.sec property 339 portal-PortalHostName.websdk.websdk.events.history.history.JdbcDataFeedClient.cleanunusedevents.activitylog.scheduledays property 336 portal. program upgrade for RSMs 72 prohibited characters user names 63 Properties task.events.properties file 194 portal.events.history.configDir property in datafeed.key.upgrade.ena bled property 330 portal. 312 prerequisites for monitoring.enabled 148 portal.purgeunknown.rsmmessage.enable property 333 portal.rsmcommunication.retention property 332 portal.log file 304.parameterstatushistory.value.private.websdk. 121 agentless 18.purgepsdp.history.enabled 149 portal.schedulehours property 329 portal.parameter.events.history.summarizationDataPoint.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 portal. described 50 printing object views Health At A Glance report 156 Status tab 45 Top N report 155 product support 3 profiles for elements See element profiles.enabled property 336 portal.events.

overview 73 types 70 rstatd firewall configuration 74 RTservers specifying for Solaris Portal 301 specifying for Windows Portal 300 Index 365 . determining 101 security requirements 22 shared 66. 60 failover 95 global 67. locating 91 load balancing 94 log files 345 log monitoring 99 notifications about system problems 75 overview 17 problems with Windows 2003 296 program upgrade 72 proxy server. cached data on the RSM 72 communication with elements 74 communication with PATROL Agents 74 communication with Portal 71. location 345 RSM security changing the security level 101 requirements 22 rsm*.xml 321 rsm. 87 installation directory.properties configuration file 341 RSMOptions. 112 wrapper. 70 stopping notifications for Unknown state events 108 store and forward.properties 320 rsm-RsmHostName. setting 103 installation log file. default 111 installing from a command line 90 installing from installation media 87 installing from Portal 85 log file location 345 preparing to install the program 76 RSM Manager utility 97 rsm*. 186 zone and pool 166.log file. 71 HTTP communication to Portal. 50 RSM configuration files jboss-service.properties 320 RSM log file 345 RSM log monitoring 98 RSM Monitor Maintenance Tool 99 searching for errors 99 RSM Maintenance Tool changing heap memory allocated for Java VM 106 changing RSM credentials 105 collecting RSM log files 107 gather basic information 108 launching the utility 98 silent installation 90 silent uninstallation 112 viewing RSM log files 107 RSM Manager utility changing RSM credentials 104 configuring HTTP communication with Portal 103 configuring RSM to use a proxy server 102 described 97 launching 97 RSM program See also RSMs allocating heap memory for the Java VM on RSM 106 collecting log files for Support 107. location 345 service name 70 system requirements 76 uninstalling 109. 108 configuring for Portal monitoring 313 installation credentials 86. 110. 105 changing maximum heap memory 106 changing the credentials for the JMX console 344 changing the security level 101 clustering 95 communication interruptions with Portal.xml 321 portal-PortalHostName-xmbean. 186 Reports tab 151–161 restrictions for editing Performance Managers core 131. 187 logical domain 166.log file 107. 72 configuring to stop sending notifications for Unknown state events 109 data gaps 73 dedicated 70 deleting from Portal 109 described 19. 312 custom 140 solution 131 retention policies CDE data 201 changing retention time 327.protocol property 339 rsm. 338 report data. 334.log file.txt file 91 rsmcfg.txt file for a silent installation from a command line 91 rsm-RsmHostName.properties file 343 rsm_install_log. configuring 102 searching for errors 99 security level. 345 rsm.properties configuration file 342 RSMs See also RSM program assigned to elements 73 automating gathering of basic information 108 changing credentials 104.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 reports availability 166. described 145 retention policies for report data 337 rights and permissions for users 17.download.

described 131 solution support deactivating parameters 120 solutions.recv. 342 system lockouts. 192.properties file 191.parameter.max.to. See Secure Hash Algorithm (SHA) shared credentials custom PerfMon application classes 137 custom Telnet and SSH application classes 137 described 60 Shared Credentials task.trap.trap. firewall configuration 74 SNMP collector described 138 MIB dependencies 138 problems with more than 20 top-level parameters 138 SNMP collector timeout value 343 SNMP firewall configuration 74 SNMP Trap Listener application class and clustered RSMs 93 SNMP traps account-level notifications 56 BMC-Performance-Manager-Portal-MIB 236 changing maximum trap size 244 changing SNMP trap version 244 changing the maximum number of parameters in a trap 236 customizing trap properties 243 error codes 246 MIB description 239 OID description 237 parsing SNMP traps 238 provider level notifications 227 sample trap 245 user notifications 219 snmp. 218 notifications for user accounts 56 status filtered by parameter status 47 infrastructure status view 45 portal status view 45 return values from bpmcli 282 Status tab 44 store and forward for RSM. described 61 tasks for configuration About 50 366 BMC Performance Manager Portal Monitoring and Management Guide . preventing 61 system requirements for RSM program 76 T table. See Performance Managers SSH collection protocol 136 SSH Server port.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 S sample SNMP trap 245 sampleDatafeedTarget. parameter history 47 tabs Accounts 64 configure 50 Events 247 Portal 66 Provider 64 Reports 151–161 Status 44 Tags task.events.process property 236.showlastapp property 340 snmp.trap. customer 3 synchronizing thresholds and KM application classes 266.version property 244 solution Performance Managers. overview 73 summarization of report data 144 support.max. 199 SDK for creating Performance Managers 114 Secure Hash Algorithm (SHA) 22 security additional security for Portal 21 changing for an RSM that co-exists with PATROL products 101 changing for an RSM that does not coexist with PATROL products 101 changing for the BMC Performance Manager Portal 301 clustered RSMs 94 how the installation program assigns security to an RSM 101 requirements for RSM 21 RSM security for agentless monitoring 74 RSM security for PATROL Agent integration monitoring 75 security level changing 101 described 20 determining for the RSM 101 See Other Providers and Their Accounts permission for administrators 63 self monitoring for the Portal components 312 service model integration BMC Atrium CMDB 219 direct to cell 224 service name for Remote Service Monitor 70 severity slot name 232 SHA. firewall configuration 74 state changes notification for the enterprise 66. described 66.size property 244 snmp. 339 snmp.trap. 70 silent mode installing RSM program 88 uninstalling RSM program 112 single-instance application classes 135 size of SNMP traps sent by Portal 244 slot names in the base event class populated for the Portal 231 SMTP server.showappinstsingleton property 340 snmp. described 60 shared RSMs.

312 restrictions for using bpmcli 253 user credentials 86 User Groups task. 154 Timeout property in portal-PortalHostName.properties 344 user configuration options 50 impersonating 64 predefined in Portal 63.00 174 UseCompression property in portalPortalHostName. communication from RSM to Portal 72 time interval controls for object views 152. 67 Shared Credentials 60 Tags 61 User Groups 62 Users 62 technical support 3 Telnet collection protocol 136 Telnet server port. changing 244 Version property in rsm-RsmHostName. 66 Object Groups 59 Performance Managers 67 Personal Preferences 60 Properties 66 Remote Service Monitors 60. firewall configuration 74 templates for configuring elements See element profiles.2.properties 344 timeout values for application classes 343 Top N report changing the timeout wait period for the report 155. 110. Performance Manager 27 upgrading Crystal Reports 2008 (Designer component) 174 to BMC Reporting Foundation 3. templates for notification rules 57 thresholds configuring for parameters 26. 66.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 Account Information 50 Administrators 65 Appearance 65 Blackout Periods 50 Change Password 51 Dashboards 51 Element Profiles 51 Elements 55 Global Properties 66 Licensing Information 66 Mass Email 67 Monitoring On/Off 55 Notifications 56. discovering in background process 304 refreshing PATROL integration 41.properties on RSM 344 V verifying BMC Performance Manager Portal installation 24 verifying Performance Manager upgrades 27 version of SNMP trap. 324 described 153 exporting parameter data 155 printing 155 top parameters causing alerts in Health At A Glance report 157 top-level object groups 59 traps. described 62 user name allowed characters 63 user notification. SNMP changing maximum trap size 244 changing SNMP version 244 changing the maximum number of parameters in a trap 236 error codes 246 parsing 238 sample trap 245 trial account types 65 troubleshooting being logged out of BMC Portal 303 cannot find errors when data discovery runs in the background 304 closing popup windows 299 Console Server list is empty 299 downloading reports to csv or text file 302 downloading RSM fails 298 monitoring problems 296 parameters go into alarm 301 PATROL integration requires security change on Portal 301 RSM requires permission changes for PerfMon 296 RSM upgrade fails on Windows 2003 SP1 297 U uninstalling Performance Managers 129 uninstalling the RSM program 109. 112 Unknown-OK events purging 149 up_time property for availability 324 updating registry key on Windows operating system 297 upgrades clustered RSMs 96 effect on communication between Portal and RSMs 73 Performance Managers 127 RSM 91 verifying. described 62 UseSsl property in portal-PortalHostName. 266 synchronizing with KM application classes 266 violations.properties 342 Index 367 . 115 mapping for PATROL integration 122 overriding in an element profile 53 PATROL integration. See notifications Users task.

described 236 Windows operating systems application classes. firewall configuration 74 Windows operating systems.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 W warning and alarm thresholds in a parameter. described 134 WEBSDKV10-MIB.log file 345 368 BMC Performance Manager Portal Monitoring and Management Guide . problems for RSM computers 296 wrapper.

Notes .

*926601* *926601* *926601* *926601* *106629* .

Sign up to vote on this title
UsefulNot useful