SlideShare une entreprise Scribd logo
1  sur  370
Télécharger pour lire hors ligne
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                       Telephone        713 918 8800 or           Fax                713 918 8000
                    2101 CITYWEST BLVD                                      800 841 2031
                    HOUSTON TX 77042-2827
                    USA
 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   read overviews about support services and programs that BMC offers
s   find the most current information about BMC products
s   search a database for issues similar to yours and possible solutions
s   order or download product documentation
s   download products and maintenance
s   report an issue or ask a question
s   subscribe to receive proactive e-mail alerts when new product notices are released
s   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   sequence of events leading to the issue
s   commands and options that you used
s   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.
s   (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.
s   (Asia-Pacific) Contact your BMC sales representative or your local BMC office.




4      BMC Performance Manager Portal Monitoring and Management Guide
Contents
     Chapter 1              Overview of the BMC Performance Manager Portal                                                                        15
     How BMC Performance Manager Portal fits into BMC Portal . . . . . . . . . . . . . . . . . . .                                                15
        BMC Portal features common to all modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                                     16
        BMC Performance Manager Portal features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                                     17
        How the BMC Performance Manager Portal monitors your infrastructure. . . . .                                                              17
        Methods of data collection for Performance Managers . . . . . . . . . . . . . . . . . . . . . .                                           18
     Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .         18
        BMC Performance Manager Portal module in BMC Portal . . . . . . . . . . . . . . . . . .                                                   19
        Remote Service Monitor program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                             19
     Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   20
        Additional security for BMC Performance Manager Portal . . . . . . . . . . . . . . . . . .                                                21
        Security requirements for RSMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                          22
        Infrastructure element credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                          22

     Chapter 2              Getting started with the BMC Performance Manager Portal                                                               23
     Verifying the BMC Performance Manager Portal installation . . . . . . . . . . . . . . . . . . .                                              24
     Adding infrastructure elements for agentless monitoring . . . . . . . . . . . . . . . . . . . . . .                                          25
     Verifying an upgrade from an earlier version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                               27
     Integrating PATROL Agent data into the BMC Performance Manager Portal . . . . .                                                              27
         Options for identifying PATROL Agents as elements . . . . . . . . . . . . . . . . . . . . . . .                                          28
         Methods for discovering PATROL Agent data. . . . . . . . . . . . . . . . . . . . . . . . . . . . .                                       29
         Synchronization of thresholds and application classes . . . . . . . . . . . . . . . . . . . . . .                                        40
     Integrating infrastructure elements from the BMC Atrium CMDB . . . . . . . . . . . . . . .                                                   42
     Viewing object status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .            44
         Portal and infrastructure status views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                           45
         Individual parameter history charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                          46
         Parameter history tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                 47
         Parameter filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .             47

     Chapter 3              Users and administrators                                                                                              49
     User configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                 50
        About task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .         50
        Account Information task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                     50
        Blackout Periods task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                 50
        Change Password task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                    51
        Dashboards task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .              51
        Element Profiles task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                51
        Elements task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .           55


                                                                                                                              Contents             5
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
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   114
Parameters and thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                114
    Parameter thresholds and event severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                             115
    Thresholds and parameter status changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                               115
Deactivating parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .              116
    Points to remember while deactivating parameters. . . . . . . . . . . . . . . . . . . . . . . .                                      117
    Derived parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .              118
    Deactivating a parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                 118
    Deactivating a parameter in the Performance Manager Editor solution . . . . . .                                                      119
    Solution support for deactivating parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .                                 120
Methods of remote monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                     121
    Agentless monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .               121
    PATROL Agent integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                     121
Installing new Performance Managers on the Portal . . . . . . . . . . . . . . . . . . . . . . . . . .                                    125
Upgrading Performance Managers on the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                                   127
Removing Performance Managers from the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . .                                      129
Types of Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                      130
    Core Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                      130
    Solution Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                          131
    Custom Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                          131
Editing Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                     139
    Editing unpublished custom Performance Managers . . . . . . . . . . . . . . . . . . . . . .                                          139
    Editing published custom Performance Managers . . . . . . . . . . . . . . . . . . . . . . . .                                        139

Chapter 6              Reports                                                                                                           141
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   142
Parameter update intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                 142
   Standard parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                     143
   Accumulated parameter values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                         144
Data summarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .             144
Data retention policies that affect object view content . . . . . . . . . . . . . . . . . . . . . . . . .                                145
   Retention policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .            145
   Properties that control the raw data retention policies . . . . . . . . . . . . . . . . . . . . .                                     145
   Properties that control event history retention . . . . . . . . . . . . . . . . . . . . . . . . . . . .                               147
   Purging inactive data from the Portal history tables . . . . . . . . . . . . . . . . . . . . . . .                                    147
   Purging unknown and unused events from the event table. . . . . . . . . . . . . . . . .                                               149
Reports tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .    151
   Time interval controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .              152
   Top N report for object groups or the account . . . . . . . . . . . . . . . . . . . . . . . . . . . .                                 153
   Health At A Glance report for elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                              156
   Multiple parameter history charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                         160
   Dashboard parameter charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                      161
Enterprise reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .        162


                                                                                                                       Contents            7
Downloading and installing BMC Reporting Foundation 3.2.00, Crystal Reports
                  2008 (Designer component), and integration components . . . . . . . . . . . . . . . . 162
               Installing the integration components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
               Upgrading to Crystal Reports 2008 (Designer component). . . . . . . . . . . . . . . . . . 174
               Upgrading to BMC Reporting Foundation 3.2.00 . . . . . . . . . . . . . . . . . . . . . . . . . . 174
               Publishing and scheduling generated reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
               Report types and details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
               Uninstalling the integration components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
            Continuous data export configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
               Continuous data export requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
               Configuring the datafeed utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
               Changing the retention policy for the CDE database . . . . . . . . . . . . . . . . . . . . . . . 201
               Maintaining the continuous export to the CDE database . . . . . . . . . . . . . . . . . . . 201
               Additional configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
               External CDE movement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

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

            Chapter 8             BMC Performance Manager Portal command-line interface                                                          251
            Preparing the client computer for the bpmcli . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
            bpmcli syntax and arguments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
            Data-manipulation commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254


8   BMC Performance Manager Portal Monitoring and Management Guide
addElements: adding a single element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                          255
   addElements: adding multiple elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                            257
   addPATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .        260
   deleteElements: deleting a single element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                          262
   deleteElements: deleting multiple elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                             263
   refreshDatafeedMetadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                264
   refreshPATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .          266
   savePassword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .        269
Data-extraction commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .               270
   exportParameterHistory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .               272
   getApplicationsForElement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                    276
   getElements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .      277
   getParameterHistory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .            278
   getParameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .       281
   getPortalVersion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .         282
   getSubApplications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .           283

Chapter 9              BMC Performance Manager Portal command-line interface for BMC
                       Datastore                                                     285
Configuring the BMC DatastoreCLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                      285
Disabling alarms and warnings for an application class or parameter globally . . .                                                    287
Finding application class occurrences displaying the ACS error . . . . . . . . . . . . . . . .                                        289
Exporting the configuration information from BMC Portal on to an HTML file . . .                                                      292

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


                                                                                                                       Contents           9
Appendix B              Monitoring the health of the Portal                                                                            311
            Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
            Self-monitoring Performance Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
                Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
                Remote Service Monitor setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
                Configure RSM to monitor JMX behind a firewall . . . . . . . . . . . . . . . . . . . . . . . . . 314
                BMC PM Monitor application classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
                Performance Manager configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
            PATROL Agent health monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
                Configuring PATROL Agent monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
                Changing the threshold settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

            Appendix C              BMC Performance Manager Portal files                                                                           319
            Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
               BMC Performance Manager Portal property files. . . . . . . . . . . . . . . . . . . . . . . . . . 320
               Remote Service Monitor property files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
               Configuration file properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
            Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
               BMC Performance Manager Portal log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
               RSM log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

            Glossary                                                                                                                               347


            Index                                                                                                                                  355




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



                                                                                                                    Figures        11
Using data-extraction commands to retrieve input arguments for subsequent
              commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
            How the Historical Data Export utility uses the startData argument . . . . . . . . . . . . 273
            RSM setup for monitoring the Portal components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314




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


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




14   BMC Performance Manager Portal Monitoring and Management Guide
Chapter


                                                                                                                            1
Overview of the BMC Performance
1




Manager Portal
      This chapter describes how the BMC Performance Manager Portal module fits into
      the BMC Portal product and the features in BMC Performance Manager Portal.

      This chapter presents the following topics:

      How BMC Performance Manager Portal fits into BMC Portal . . . . . . . . . . . . . . . . . . .                                                15
         BMC Portal features common to all modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                                     16
         BMC Performance Manager Portal features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                                     17
         How the BMC Performance Manager Portal monitors your infrastructure. . . . .                                                              17
         Methods of data collection for Performance Managers . . . . . . . . . . . . . . . . . . . . . .                                           18
      Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .         18
         BMC Performance Manager Portal module in BMC Portal . . . . . . . . . . . . . . . . . .                                                   19
         Remote Service Monitor program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                             19
      Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   20
         Additional security for BMC Performance Manager Portal . . . . . . . . . . . . . . . . . .                                                21
         Security requirements for RSMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                          22
         Infrastructure element credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                          22




How BMC Performance Manager Portal fits
into BMC Portal
      BMC Portal—also referred to as the Portal—is composed of a database, application
      server, and web server, and provides the access point for its utilities and modules.
      You access the BMC Portal from a browser on your client (desktop) computer.

      The BMC Performance Manager Portal extends the features in the BMC Portal,
      enabling you to leverage both agentless technologies and the PATROL Agent to
      monitor the availability and performance of your business infrastructure.



                                                 Chapter 1        Overview of the BMC Performance Manager Portal                                   15
BMC Portal features common to all modules


                Your user permissions determine the extent to which you can configure and monitor
                your Portal account. At any time, users with the applicable permissions can view:

                s   Current status of the infrastructure in the account
                s   Lists of the elements and parameters in the account that recently crossed
                    thresholds and triggered events
                s   Charts that show how well the elements in the account performed
                s   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. Icons, colors, and other graphical cues enable you
                to quickly determine the source of problems.



BMC Portal features common to all modules
                BMC Portal provides many common features across all of its modules, including:

                s   Account properties
                s   Object group names
                s   Blackout period scheduling (times when metrics are not collected from the
                    elements)
                s   Customization of notification criteria that BMC Portal uses to determine when to
                    notify your personnel about problems in your environment
                s   Users and user groups
                s   Object views that provide status, events, and report data
                s   Dashboard configuration
                s   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.


                     NOTE
                For information about configuring BMC Portal, see the BMC Portal Getting Started guide. This
                guide also describes the accounts, users, and administrators, as well as authentication, rights,
                and permissions.




16     BMC Performance Manager Portal Monitoring and Management Guide
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. The Status, Reports, and Events tabs provide views about
        your account and the objects that compose the account.

        Following installation and configuration of the BMC Performance Manager Portal,
        you can begin adding computers and other devices to the account as infrastructure
        elements. You organize infrastructure elements into groups to which you assign rights
        and permissions for users of the Portal. Collectively, infrastructure elements and
        groups are known as infrastructure objects. The infrastructure objects in your
        account correspond to the computers and devices that compose the IT infrastructure
        for your business.



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. An RSM is a computer on which you have
        installed the RSM program. Depending on the size of your environment and your
        high availability (HA) requirements, you can implement one or many RSMs. For
        more information about installing and configuring the RSM program, see Chapter 4,
        “Remote Service Monitors,” on page 69.

        To know what to monitor on the specified infrastructure elements, the RSM uses
        Performance Managers. Each Performance Manager contains one or more application
        classes that you can select to monitor operating systems, programs, files, processes,
        and more. Each application class contains parameters that define the type of metric to
        obtain from the infrastructure element.

        Performance Managers, 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, or when you import them from the Portal user interface.
        Performance Managers that are installed on the Portal are available to all users on the
        Portal who have the appropriate user permissions. For more information about
        installing application classes, see Chapter 5, “Performance Managers and application
        classes,” on page 113.




                                  Chapter 1   Overview of the BMC Performance Manager Portal   17
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.
                Performance Managers can provide agentless monitoring or can integrate parameter
                data from a PATROL Agent. After you install the Performance Managers in the
                Portal, you can configure the elements in your account to use the application classes
                in the Performance Managers.

                The application classes in agentless Performance Managers use industry-standard
                protocols, such as PerfMon and SNMP, to retrieve metrics about the performance of
                the monitored element. As you add elements to the account, the user interface
                displays the application classes available for the new elements, based on the
                operating system of the element. During element configuration, you can accept
                default thresholds or, if permitted by your user permission, modify thresholds to
                reflect the service level agreement (SLA) for your account.

                The application classes in PATROL integration Performance Managers retrieve
                parameter data from PATROL Agents. PATROL integration Performance Managers
                correspond to the PATROL Knowledge Modules (KMs) on the selected agent, and
                contain mappings to a subset of the parameters in the KM. You can integrate
                parameter data from version 3.5 and later of PATROL Agents.

                The RSM program begins collecting metrics about your account within minutes of
                your adding and configuring the first elements. As soon as data collection begins, you
                can use the BMC Performance Manager Portal to view performance and availability
                metrics and status.




Components
                The following components compose the BMC Performance Manager Portal:

                s   BMC Performance Manager Portal module in BMC Portal
                s   Remote Service Monitor program




18      BMC Performance Manager Portal Monitoring and Management Guide
BMC Performance Manager Portal module in BMC Portal


                 Figure 1 shows how the BMC Performance Manager Portal components interact with
                 the BMC Portal.

Figure 1       BMC Portal with the BMC Performance Manager Portal module installed
                                                                                        The programs that compose the BMC Performance
                                 BMC Portal                                             Manager Portal module reside on the Portal
                                                                                        application server. The RSMs obtain parameter
                                database server                                         metrics from the monitored elements and send
                                                               RSM computer
                                                                                        events and parameter metrics to the Portal web
                                                                                        server.

                                                                                        When you specify an application class that is not
                                                                                        on the specified RSM, RSM queries the Portal for
                                                                                        the corresponding Performance Manager. After
                                                                                        the RSM retrieves it from the Portal, the
                                                                                        Performance Manager remains on the RSM.
                   web server    application server
 web browser




                                       remote elements               PATROL Agents




BMC Performance Manager Portal module in BMC Portal
                 During installation of BMC Portal, the installation program places the BMC
                 Performance Manager Portal on the BMC Portal application server. BMC Portal
                 provides the access point to the BMC Performance Manager Portal module and the
                 views that provide the metrics about your monitored infrastructure. You use your
                 Internet browser to access the Portal to view data and reports that show the
                 performance and availability of your account.

                 For more information about the individual components of BMC Portal, see the BMC
                 Portal Getting Started guide.



Remote Service Monitor program
                 The Remote Service Monitor (RSM) program remotely monitors its assigned elements
                 and sends parameter values to the Portal. You install the RSM program on each
                 computer designated as an RSM.




                                                         Chapter 1    Overview of the BMC Performance Manager Portal                        19
Security


                  After you add an element to the Portal, the RSM begins collecting parameter data
                  from the element at the collection intervals specified for each application class, and
                  then sends parameter values to the Portal at the report update interval for the
                  element. The RSM also sends parameter values to the Portal as soon as it detects that
                  a parameter has changed its status (for example, when the parameter status changes
                  from warning to alarm).

                  For more information about the Remote Service Monitor program, see Chapter 4,
                  “Remote Service Monitors,” on page 69.




Security
                  During installation of BMC Portal, the installation program installs basic security on
                  the Portal. If you intend to integrate data from a PATROL Agent, you might need to
                  specify a different security level.

                  The RSM installation program also requests a security level. When integrating
                  PATROL Agent data, the security level on the RSM must match the security of the
                  monitored PATROL Agent.

                  Table 1 summarizes the key elements for each of the five levels of security. Basic
                  security (the default) is the lowest level of security. Levels 1 through 4 provide
                  increasingly higher levels of security, along with increasingly greater configuration
                  demands.

                  Table 1      Highlights of security levels (part 1 of 2)
                   Security level        Description
                   Basic security         s   Default level of security employed when you install PATROL,
                                              BMC Performance Manager Portal, and BMC Portal

                                          s   No cryptographic protection of network traffic

                                          s   No verification of product or data integrity

                                          s   Authentication provided and protected password stored in
                                              unattended operations in the PATROL application

                                          s   Minimized security and access control lists
                                              (ACLs) in favor of usability and performance
                   Level 1                s   Diffie-Hellman used for privacy

                                          s   No SSL authentication of either party to the other




20         BMC Performance Manager Portal Monitoring and Management Guide
Additional security for BMC Performance Manager Portal


        Table 1      Highlights of security levels (part 2 of 2)
         Security level        Description
         Level 2                s   Private communications provided by SSL

                                s   No SSL authentication performed (runs in keyless mode)

                                s   Defaults to unattended agent restart
         Level 3                s   Private communications and server authentication provided by
                                    SSL

                                s   Certificate provided by agent so that the client can authenticate the
                                    agent

                                s   Client not authenticated back to the agent

                                s   Defaults to unattended agent restart; can configure for attended
                                    agent restart
         Level 4                s   Private communications and mutual authentication of the console
                                    and the agent provided by SSL

                                s   Defaults to unattended agent restart; can configure for attended
                                    agent restart




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 security on the Portal must match that of the target
        console servers. When you install the BMC Performance Manager Portal module, the
        installation program asks if you want to discover PATROL Agents in a PATROL
        Central environment. If you select Yes, the installation prompts you for an RTserver
        name and for the necessary security level.

        For more information about security, see the PATROL Security User Guide.

        To change the security level for the Portal, see the BMC Portal Getting Started guide.

        For more information about Management Profiles and the RTserver, see your
        PATROL Central documentation.




                                     Chapter 1   Overview of the BMC Performance Manager Portal        21
Security requirements for RSMs



Security requirements for RSMs
                When installing the RSM program, the installation program prompts you for a
                security level. Because an RSM that integrates PATROL Agent parameter values must
                have the same security level as that of the PATROL Agent, you must install an RSM
                for each security level of the PATROL Agents from which you integrate data.

                If your environment does not use PATROL Agents, the installation program applies
                the Basic security (level 0) to the RSM. This setting enables you to change the security
                level at a later time, if necessary.

                To change the security level on an RSM, see “Changing the security level for an RSM”
                on page 101.



Infrastructure element credentials
                During element configuration, the BMC Performance Manager Portal prompts you
                for authentication credentials that the RSM program can use to access the element.
                The credentials for infrastructure elements are encrypted and stored in the Portal
                database, using Secure Hash Algorithm (SHA), which provides 160-bit
                cryptographically secure hash of the credentials. The Portal encrypts the credentials
                and sends them to the RSM computers, and the RSM program does not store any
                element credentials locally.




22      BMC Performance Manager Portal Monitoring and Management Guide
Chapter


                                                                                                                   2
Getting started with the BMC
2




Performance Manager Portal
     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. The scenarios in this chapter acquaint
     you with the methods for configuring the BMC Performance Manager Portal to
     monitor your infrastructure.

     This chapter presents the following topics:

     Verifying the BMC Performance Manager Portal installation . . . . . . . . . . . . . . . . . . .                                     24
     Adding infrastructure elements for agentless monitoring . . . . . . . . . . . . . . . . . . . . . .                                 25
     Verifying an upgrade from an earlier version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                      27
     Integrating PATROL Agent data into the BMC Performance Manager Portal . . . . .                                                     27
         Options for identifying PATROL Agents as elements . . . . . . . . . . . . . . . . . . . . . . .                                 28
         Methods for discovering PATROL Agent data. . . . . . . . . . . . . . . . . . . . . . . . . . . . .                              29
         Synchronization of thresholds and application classes . . . . . . . . . . . . . . . . . . . . . .                               40
     Integrating infrastructure elements from the BMC Atrium CMDB . . . . . . . . . . . . . . .                                          42
     Viewing object status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   44
         Portal and infrastructure status views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                  45
         Individual parameter history charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                 46
         Parameter history tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .        47
         Parameter filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .    47




                                  Chapter 2       Getting started with the BMC Performance Manager Portal                                23
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, including the BMC Performance Manager Portal. This section describes
                tasks that you can perform to ensure that the BMC Performance Manager Portal is
                ready to monitor infrastructure.

                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.

                    You can install one of the RSM instances on the Portal computer.

                 2 Use the procedure in “Adding infrastructure elements for agentless monitoring”
                    on page 25 to add one element to the account.

                    To test the installation, select a simple application class, such as Ping.

                 3 Select the Status tab.

                 4 In the navigation pane, expand the object tree to display the top-level Infrastructure
                    object group and the objects that it contains.

                    After adding the element, the status of the new infrastructure element should
                    change to OK.

                If a problem occurs

                If the status of the element is critical, you might have a problem with the Portal
                installation or with the configuration of the element.

                s   Verify that a firewall is not preventing the RSM from successfully reaching the
                    computer.

                s   Verify that a firewall is not preventing the RSM from sending data to the Portal.

                s   Determine whether a network problem is causing the ping command to fail.

                s   See the troubleshooting appendix in the BMC Portal Getting Started guide or the
                    BMC Portal Installation Guide.




24      BMC Performance Manager Portal Monitoring and Management Guide
Adding infrastructure elements for agentless monitoring


      Where to go from here

      s   Begin adding infrastructure elements. For more information, see “Adding
          infrastructure elements for agentless monitoring” on this page.

      s   Review the metrics collected about infrastructure elements. For more information,
          see Chapter 6, “Reports,” on page 141.




Adding infrastructure elements for agentless
monitoring
      You can quickly add computers and devices for agentless monitoring. The following
      scenario provides the procedure for adding an element and configuring it with the
      Ping application class, which measures network latency, and to verify that the
      element can accept network requests.

      Before you begin

      You must have at least one RSM installed and available to the Portal. For more
      information, see “Using the installation wizard to install the RSM program” on
      page 84.

      To add an infrastructure element to the BMC Performance Manager Portal

      1 Log on with user credentials

      2 Click the Configure tab.

      3 Under Tasks, select Elements to open the Elements page, and click Add.

      4 If the Elements–Add–Type of Element page is displayed, select Infrastructure
          Element, and click Next; otherwise, proceed to step 5.

      5 On the Elements–Add Infrastructure Element–Select Remote Service Monitor
          page, select an RSM, and click Next to open the Elements–Add Infrastructure
          Element–Identification page.


              NOTE
          If an instance of the RSM program has not been installed, the list of Remote Service
          Monitors is empty. If this occurs, click Cancel and install the RSM program. See “Using the
          installation wizard to install the RSM program” on page 84.




                           Chapter 2   Getting started with the BMC Performance Manager Portal      25
Adding infrastructure elements for agentless monitoring


                 6 In Element Name (label), specify an element name that appears on all charts and
                    Status pages.

                    If you do not specify a label name, the host name or IP address is used as the
                    element name.

                 7 In the text box, type the host name of the computer, select Host Name, and click
                    Next.

                    To add many elements, you can paste a list of host names in the text box or specify
                    a range of IP addresses. When adding multiple elements, separate host names with
                    commas.

                 8 On the Elements–Add Infrastructure Element–Select Group page, specify the
                    platform name and group name, and click Next:

                   A From the Element(s) Platform list, select the platform that corresponds to the host
                        name that you specified in step 7.

                    B In Group Name, type test group.

                 9 On the Elements–Add Infrastructure Element–Application Classes page, select the
                    Networking category, select the Ping application class, and click Next.

                10 On the Elements–Add Infrastructure Element–Properties and Credentials page,
                    review the properties for the Ping application class, and click Next:

                    s   When you keep the default value for Report Update Interval Minutes, the RSM
                        sends parameter values to the Portal every 5 minutes for BMC Portal versions
                        earlier than 2.7, and every 10 minutes for versions 2.7 and later, unless a
                        parameter threshold is violated.

                    s   When you keep the default value for Collection Interval, the RSM collects
                        parameter values for the Ping application class once every minute.

                11 On the Elements–Add Infrastructure Element–Thresholds page, accept the default
                    thresholds, and click Finish.

                    After you finish adding the element to the Portal, the RSM starts accessing the
                    element to collect parameter values. You might need to wait a minute or two
                    before the Portal receives the initial parameter values and updates the Status tab.

                 Where to go from here

                 Begin viewing the parameter metrics collected by the RSM by selecting the Status and
                 Reports tabs.




26      BMC Performance Manager Portal Monitoring and Management Guide
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.1 and to
      ensure that the Portal is collecting data following the upgrade.

      If you upgraded from BMC Performance Manager Portal 2.1, your application classes
      were migrated to the Performance Manager format and installed on the Portal. If you
      upgraded from BMC Performance Manager Portal 2.3, see “To upgrade a
      Performance Manager during a Portal upgrade” on page 127.

      To verify an upgrade from BMC Performance Manager Portal version 2.3 or
      later

      1 Log on using the Portal administrator credentials (superadmin/superadmin by
        default).

      2 Select the Portal tab.

      3 Under Tasks, 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.

      4 Log on as a user and select the Status tab to view the values and status for the
        infrastructure elements in your account.

        After the upgrade, the Status tab should reflect new values collected by the
        upgraded application classes and RSM for your Portal.




Integrating PATROL Agent data into the BMC
Performance Manager Portal
      BMC Software has created PATROL integration Performance Managers for many of
      the KMs, providing mappings to many of those KMs’ parameters. Using the PATROL
      Agent as a data source, the RSM mines parameter data from the agent and sends it to
      the Portal. The BMC Performance Manager Portal can integrate parameter data from
      version 3.5 and later of PATROL Agents.




                          Chapter 2   Getting started with the BMC Performance Manager Portal      27
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. When you specify the
                host names or IP addresses, you can accept the default parameter thresholds in the
                PATROL integration application class, or you can modify the default values (during
                the add process or later). The Elements–Add Infrastructure Element–Identification
                page provides the following options for identifying PATROL Agents and discovering
                thresholds from versions 3.5 and later of PATROL Agents:

                s   Select Host Name or IP Address to specify one or more PATROL Agents as
                    elements. When you select one of these options, you must know the KMs that are
                    installed on the managed system and their corresponding Performance Managers
                    in the Portal. After specifying the host names, select the PATROL integration
                    Performance Managers that correspond to the KMs on the agents. In most cases,
                    the PATROL integration Performance Manager names and version numbers match
                    the PATROL KM names and version numbers.

                    This method uses the thresholds defined in the selected PATROL integration
                    Performance Manager. By default, threshold management is handled from the
                    PATROL Agent. To change threshold management to the Portal, access the
                    Properties page for element to change the threshold management preference.

                    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, PATROL Configuration Manager, PATROL Knowledge
                    Module for Event Management, or other BMC Software products.


                        NOTE
                    The BMC Performance Manager consoles include

                    s   PATROL Central Operator - Web Edition
                    s   PATROL Central Operator - Microsoft Windows Edition
                    s   PATROL Console for Microsoft Windows
                    s   PATROL Console for UNIX®


                s   Select PATROL Integration to have the BMC Performance Manager Portal discover
                    the agents and the KMs on the agents, match the KMs with the PATROL
                    integration Performance Managers on the Portal, and obtain parameter thresholds.
                    When you use this option to discover PATROL Agents, you can also choose to
                    monitor the health and availability of the selected PATROL Agents. For more
                    information, see “PATROL Agent health monitoring” on page 317.

                For more information about managing thresholds for PATROL Agent elements, see
                “PATROL Agent integration” on page 121.




28      BMC Performance Manager Portal Monitoring and Management Guide
Methods for discovering PATROL Agent data



Methods for discovering PATROL Agent data
        When you select the PATROL Integration option, you can choose from the following
        discovery options:

        s   Discover agent data from a PATROL Central environment, which requires that
            you specify credentials for a PATROL Console Server.

            This method requires that you specify an RTserver for the Portal to discover
            Management Profiles on the console server. When using this option, consider
            creating Management Profiles that contain the managed systems that you want to
            add.

        s   Discover agent data from a PATROL desktop (DT) file, which requires that you
            specify the full path and file name for the desktop file.

        s   Discover agent data from a PATROL Event Translation (PET) file, which requires
            that you specify the full path and file name for the configuration file.

        s   Discover PATROL Agent data by specifying a comma-separated value (CSV) file
            that contains the element name, agent host name, port number for the PATROL
            Agent, and user name.

            The CSV file can optionally contain the password to authenticate the user name.

        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.

        The data discovery process can take a long time, but after you click Commit to initiate
        the process, you can navigate to other pages by clicking the Status, Events, Reports, or
        Configure tab.

        s   To view the status of the new elements, select the Status tab.
        s   To see whether any errors occurred during data discovery, locate and view the
            portal.log file. See “Cannot find errors when data discovery runs as a background
            process” on page 304.

        If your PATROL environment contains a mixture of PATROL architectures, you can
        use a combination of the integration options.


             NOTE
        s   The BMC Performance Manager Solutions CD contains many PATROL integration
            Performance Managers that provide integration with PATROL parameter data.

        s   To ensure that you do not stop the Portal from mining data from the agents, do not unload
            the corresponding KM from the PATROL Agent.




                            Chapter 2   Getting started with the BMC Performance Manager Portal    29
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,
                you can specify Management Profiles for the Portal to use to discover PATROL
                Agents. The discovery process also matches the PATROL integration Performance
                Managers with the KMs and obtains parameter thresholds from the agent. For more
                information about the components in the PATROL Central environment, see the
                PATROL Central documentation.

                Before you begin

                s   The Portal requires an RTserver to access a Management Profile. If you did not
                    specify an RTserver and security level during installation of the Portal, you must
                    configure these Portal settings before proceeding.

                    See “Specifying RTservers for the BMC Performance Manager Portal” on page 300.

                s   The KMs must be loaded on the PATROL Agent.

                s   Consider creating or updating Management Profiles so that you can quickly select
                    the agents that you want.

                s   Ensure that at least one RSM has been installed and is available to the Portal. See
                    “Using the installation wizard to install the RSM program” on page 84.

                To discover PATROL Agents in a PATROL Central environment

                1 Click the Configure tab, and under Tasks, select Elements to open the Elements
                    page, and then click Add.

                2 If the Elements–Add–Type of Element page is displayed, select Infrastructure
                    Element, and click Next; otherwise, proceed to step 3 on page 42.

                3 On the Elements–Add Infrastructure Element–Select Remote Service Monitor
                    page, select an RSM to collect data from the discovered agents, and click Next.

                4 On the Elements–Add Infrastructure Element–Identification page, select PATROL
                    Integration, and click Next.

                5 On the Elements–Add Infrastructure Element–Select Group page, specify the
                    object groups for the new elements, and click Next.

                6 On the Elements–Add Infrastructure Element–Select PATROL Agent for
                    Configuration page, select PATROL Management Profile(s), and click Next.




30     BMC Performance Manager Portal Monitoring and Management Guide
Methods for discovering PATROL Agent data


7 On the Elements–Add Infrastructure Element–Console Server Credentials page,
  specify the credentials to access the selected console server, and click Next:

  A From the list, select the console server.

      If your Portal administrator has not specified an RTserver, 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.

8 On the Elements–Add Infrastructure Element–Integrate Managed Systems page,
  select the Management Profiles to use, and click Next.

9 If necessary, on the Elements–Add Infrastructure Element–PATROL Agent
  Credentials page, specify the credentials for the selected agents, and click Commit.

  If the Management Profile had the PATROL Agent credentials saved in the console
  server’s profile impersonation table, Agent credentials might already be displayed
  on this page.

  s   To monitor the discovered agents, select Monitor discovered PATROL Agents with
      PATROL Agent Availability and Health Monitor.

  s   To change the default element name, agent name, or port from that which was
      discovered on the agent, type the new properties in the corresponding boxes for
      each applicable agent.

  s   To apply the same credentials to all agents, type the credentials in Agent User
      Name and Agent Password, and click Apply to All.

  s   To apply shared credentials to all agents, select a saved credential from the
      Shared Credentials list, and click Apply to All.

  s   To provide the credentials for individual agents, type the credentials in
      corresponding Agent User Name and Agent Password boxes, or select a saved
      credential from the list.

  The data discovery process begins. 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.


       NOTE
  The data discovery process can take a long time. During discovery, you can navigate away
  from this page by clicking on the Status, Events, or Configure tab. If you navigate away
  from this page, you will not be able to view the Results Summary page.




                    Chapter 2   Getting started with the BMC Performance Manager Portal   31
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, click Summary to
                    display the Elements–Add Infrastructure Element–Results Summary page.

                    This page shows the KMs on the agents that matched the available PATROL
                    integration Performance Managers for your Portal.

               11 Click Done to return to the Elements page.

                    After you finish adding the element to the Portal, 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.

                Where to go from here

                s   If you navigated to other tasks or object views during the discovery process, 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.

                s   View or edit parameter thresholds on the new elements. To access element
                    thresholds, take the following actions:

                    1. On the Configure tab, select the element in the navigation pane to open the
                       element Properties page.

                    2. Under Application Classes, click Edit.


                Using a PATROL desktop file to discover PATROL Agents
                If your business uses PATROL 3.x consoles, you can use a desktop file to discover
                PATROL Agents. The discovery process also matches the PATROL integration
                Performance Managers with the KMs and obtains parameter thresholds from the
                agent.

                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.

                s   You must have already saved a desktop file (*.dt) from the console. For information
                    about creating a desktop file, see your console documentation.


32     BMC Performance Manager Portal Monitoring and Management Guide
Methods for discovering PATROL Agent data


To use a PATROL desktop file to discover PATROL Agents

1 Click the Configure tab, and under Tasks, select Elements to open the Elements
  page, and then click Add.

2 If the Elements–Add–Type of Element page is displayed, select Infrastructure
  Element, and click Next; otherwise, proceed to step 3.

3 On the Elements–Add Infrastructure Element–Select Remote Service Monitor
  page, select an RSM to collect data from the discovered agents, and click Next.

4 On the Elements–Add Infrastructure Element–Identification page, select PATROL
  Integration, and click Next.

5 On the Elements–Add Infrastructure Element–Select Group page, specify the
  object groups for the new elements, and click Next.

6 On the Elements–Add Infrastructure Element–Select PATROL Agent for
  Configuration page, select Console Desktop File(s), and click Next.

7 On the Elements–Add Infrastructure Element–Console Desktop File page, use one
  of the following options to specify the desktop file, and click Next:

  s   Click Browse to select a desktop file.
  s   In File Name, type the full path and file name for the desktop file.

8 On the Elements–Add Infrastructure Element–PATROL Agent Credentials page,
  specify the credentials for the selected agents, and click Commit.

  s   To monitor the discovered agents, select Monitor discovered PATROL Agents with
      PATROL Agent Availability and Health Monitor.

  s   To change the default element name, agent name, or port from that which was
      discovered on the agent, type the new properties in the corresponding boxes for
      each applicable agent.

  s   To apply the same credentials to all agents, type the credentials in Agent User
      Name and Agent Password, and click Apply to All.

  s   To apply shared credentials to all agents, select a saved credential from the
      Shared Credentials list, and click Apply to All.

  s   To provide the credentials for individual agents, type the credentials in
      corresponding Agent User Name and Agent Password boxes, or select a saved
      credential from the list.




                    Chapter 2    Getting started with the BMC Performance Manager Portal   33
Methods for discovering PATROL Agent data


                    The data discovery process begins. 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.


                        NOTE
                    The data discovery process can take a long time. During discovery, you can navigate away
                    from this page by clicking on the Status, Events, or Configure tab. If you navigate away
                    from this page, you will not be able to view the Results Summary page.


                9 When the Elements–Add Infrastructure Element–Collect Application and
                    Threshold Data screen shows that the Portal has finished collecting data, click
                    Summary to display the Elements–Add Infrastructure Element–Results Summary
                    page.

                    This page shows the KMs on the agents that matched the available Performance
                    Managers on your Portal.

               10 Click Done to return to the Elements page.

                    After you finish adding the element to the Portal, 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.

                Where to go from here

                s   If you navigated to other tasks or object views during the discovery process, 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.

                s   View or edit parameter thresholds on the new elements. To access element
                    thresholds, take the following actions:

                    1. On the Configure tab, select the element in the navigation pane to open the
                       element Properties page.

                    2. Under Application Classes, click Edit.




34     BMC Performance Manager Portal Monitoring and Management Guide
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8
51822208 bpm-portal-agentless-monitoring-v2-8

Contenu connexe

Tendances (10)

80 w0324 1_a
80 w0324 1_a80 w0324 1_a
80 w0324 1_a
 
Abap tips
Abap tipsAbap tips
Abap tips
 
Sap s4 hana 1709 op sap api-master guide
Sap s4 hana 1709 op sap api-master guideSap s4 hana 1709 op sap api-master guide
Sap s4 hana 1709 op sap api-master guide
 
Ppm7.5 web services
Ppm7.5 web servicesPpm7.5 web services
Ppm7.5 web services
 
Converting_from_Flare_to_FrameMaker
Converting_from_Flare_to_FrameMakerConverting_from_Flare_to_FrameMaker
Converting_from_Flare_to_FrameMaker
 
Hi path 3000 &amp; 5000 v8 manager c administrator documentation issue 6
Hi path 3000 &amp; 5000 v8 manager c administrator documentation   issue 6Hi path 3000 &amp; 5000 v8 manager c administrator documentation   issue 6
Hi path 3000 &amp; 5000 v8 manager c administrator documentation issue 6
 
myBRMS
myBRMSmyBRMS
myBRMS
 
Edm Requirements Specification Sample
Edm Requirements Specification SampleEdm Requirements Specification Sample
Edm Requirements Specification Sample
 
7358948 questionnaire-mm
7358948 questionnaire-mm7358948 questionnaire-mm
7358948 questionnaire-mm
 
Domino access for ms outlook
Domino access for ms outlookDomino access for ms outlook
Domino access for ms outlook
 

En vedette (18)

Cocinamos pizza
Cocinamos pizzaCocinamos pizza
Cocinamos pizza
 
Anatomia fisiologia humana (1)
Anatomia fisiologia humana (1)Anatomia fisiologia humana (1)
Anatomia fisiologia humana (1)
 
Recetario imaginario
Recetario imaginarioRecetario imaginario
Recetario imaginario
 
Understanding camera angles and how we can incorporate
Understanding camera angles and how we can incorporateUnderstanding camera angles and how we can incorporate
Understanding camera angles and how we can incorporate
 
Mise en-scene
Mise en-sceneMise en-scene
Mise en-scene
 
Digi sound Studio Workshop
Digi sound Studio WorkshopDigi sound Studio Workshop
Digi sound Studio Workshop
 
what is twitter for?
what is twitter for?what is twitter for?
what is twitter for?
 
Fonts used
Fonts usedFonts used
Fonts used
 
Evaluation question 7
Evaluation question 7Evaluation question 7
Evaluation question 7
 
Recetario imaginario
Recetario imaginarioRecetario imaginario
Recetario imaginario
 
How to use photoshop
How to use photoshopHow to use photoshop
How to use photoshop
 
Evaluating my front and back cover
Evaluating my front and back coverEvaluating my front and back cover
Evaluating my front and back cover
 
Audience research[1]
Audience research[1]Audience research[1]
Audience research[1]
 
Pppb slide
Pppb slidePppb slide
Pppb slide
 
50states robert sloban
50states robert sloban50states robert sloban
50states robert sloban
 
Planning
PlanningPlanning
Planning
 
Mengatur Blogger Blog
Mengatur Blogger BlogMengatur Blogger Blog
Mengatur Blogger Blog
 
Questionnaire results
Questionnaire resultsQuestionnaire results
Questionnaire results
 

Similaire à 51822208 bpm-portal-agentless-monitoring-v2-8

AltiGen Acm Administration Manual
AltiGen Acm Administration ManualAltiGen Acm Administration Manual
AltiGen Acm Administration Manual
CTI Communications
 
Performance Benchmarks for Bloombase Spitfire StoreSafe Encryption Security S...
Performance Benchmarks for Bloombase Spitfire StoreSafe Encryption Security S...Performance Benchmarks for Bloombase Spitfire StoreSafe Encryption Security S...
Performance Benchmarks for Bloombase Spitfire StoreSafe Encryption Security S...
Bloombase
 
Service desk release_enu
Service desk release_enuService desk release_enu
Service desk release_enu
gauravneo_007
 
Parallels Business Automation - Standard Provider Guide
Parallels Business Automation - Standard Provider GuideParallels Business Automation - Standard Provider Guide
Parallels Business Automation - Standard Provider Guide
webhostingguy
 
Fscm91sbil b1109
Fscm91sbil b1109Fscm91sbil b1109
Fscm91sbil b1109
shivram2511
 
Aix student guide system administrations part 2 problem determination
Aix student guide system administrations part 2   problem determinationAix student guide system administrations part 2   problem determination
Aix student guide system administrations part 2 problem determination
Yogesh Sharma
 
Pengenalan kepada Pentaho
Pengenalan kepada PentahoPengenalan kepada Pentaho
Pengenalan kepada Pentaho
Hisyammudin
 

Similaire à 51822208 bpm-portal-agentless-monitoring-v2-8 (20)

AltiGen Acm Administration Manual
AltiGen Acm Administration ManualAltiGen Acm Administration Manual
AltiGen Acm Administration Manual
 
AltiGen M A X C S A C M 6
AltiGen M A X C S  A C M 6AltiGen M A X C S  A C M 6
AltiGen M A X C S A C M 6
 
Hfm install
Hfm installHfm install
Hfm install
 
AltiGen Cdr Manual
AltiGen Cdr ManualAltiGen Cdr Manual
AltiGen Cdr Manual
 
Pc 811 troubleshooting_guide
Pc 811 troubleshooting_guidePc 811 troubleshooting_guide
Pc 811 troubleshooting_guide
 
Xen app getting-started-guide
Xen app getting-started-guideXen app getting-started-guide
Xen app getting-started-guide
 
Fortimanager admin-40-mr3
Fortimanager admin-40-mr3Fortimanager admin-40-mr3
Fortimanager admin-40-mr3
 
Key manager oper_guide
Key manager oper_guideKey manager oper_guide
Key manager oper_guide
 
Faronics Insight Tech Console User guide
Faronics Insight Tech Console User guideFaronics Insight Tech Console User guide
Faronics Insight Tech Console User guide
 
Performance Benchmarks for Bloombase Spitfire StoreSafe Encryption Security S...
Performance Benchmarks for Bloombase Spitfire StoreSafe Encryption Security S...Performance Benchmarks for Bloombase Spitfire StoreSafe Encryption Security S...
Performance Benchmarks for Bloombase Spitfire StoreSafe Encryption Security S...
 
Service desk release_enu
Service desk release_enuService desk release_enu
Service desk release_enu
 
Parallels Business Automation - Standard Provider Guide
Parallels Business Automation - Standard Provider GuideParallels Business Automation - Standard Provider Guide
Parallels Business Automation - Standard Provider Guide
 
8 2-sp1 administering-broker
8 2-sp1 administering-broker8 2-sp1 administering-broker
8 2-sp1 administering-broker
 
Troubleshooting guide
Troubleshooting guideTroubleshooting guide
Troubleshooting guide
 
Microsoft India - Technical Overview on Windows Server 2008 R2 Whitepaper
Microsoft India - Technical Overview on Windows Server 2008 R2 WhitepaperMicrosoft India - Technical Overview on Windows Server 2008 R2 Whitepaper
Microsoft India - Technical Overview on Windows Server 2008 R2 Whitepaper
 
Fscm91sbil b1109
Fscm91sbil b1109Fscm91sbil b1109
Fscm91sbil b1109
 
Cm peoplesoft admin
Cm peoplesoft adminCm peoplesoft admin
Cm peoplesoft admin
 
Aix student guide system administrations part 2 problem determination
Aix student guide system administrations part 2   problem determinationAix student guide system administrations part 2   problem determination
Aix student guide system administrations part 2 problem determination
 
Mohamed Elhosni PFE Report
Mohamed Elhosni PFE ReportMohamed Elhosni PFE Report
Mohamed Elhosni PFE Report
 
Pengenalan kepada Pentaho
Pengenalan kepada PentahoPengenalan kepada Pentaho
Pengenalan kepada Pentaho
 

Dernier

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Safe Software
 
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Safe Software
 
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
Victor Rentea
 
Architecting Cloud Native Applications
Architecting Cloud Native ApplicationsArchitecting Cloud Native Applications
Architecting Cloud Native Applications
WSO2
 

Dernier (20)

Vector Search -An Introduction in Oracle Database 23ai.pptx
Vector Search -An Introduction in Oracle Database 23ai.pptxVector Search -An Introduction in Oracle Database 23ai.pptx
Vector Search -An Introduction in Oracle Database 23ai.pptx
 
TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
TrustArc Webinar - Unlock the Power of AI-Driven Data DiscoveryTrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
 
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
 
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
 
ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke
ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemkeProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke
ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke
 
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
 
presentation ICT roal in 21st century education
presentation ICT roal in 21st century educationpresentation ICT roal in 21st century education
presentation ICT roal in 21st century education
 
Biography Of Angeliki Cooney | Senior Vice President Life Sciences | Albany, ...
Biography Of Angeliki Cooney | Senior Vice President Life Sciences | Albany, ...Biography Of Angeliki Cooney | Senior Vice President Life Sciences | Albany, ...
Biography Of Angeliki Cooney | Senior Vice President Life Sciences | Albany, ...
 
DBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor PresentationDBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor Presentation
 
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
 
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
 
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost SavingRepurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
 
ICT role in 21st century education and its challenges
ICT role in 21st century education and its challengesICT role in 21st century education and its challenges
ICT role in 21st century education and its challenges
 
Strategies for Landing an Oracle DBA Job as a Fresher
Strategies for Landing an Oracle DBA Job as a FresherStrategies for Landing an Oracle DBA Job as a Fresher
Strategies for Landing an Oracle DBA Job as a Fresher
 
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot TakeoffStrategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
 
Architecting Cloud Native Applications
Architecting Cloud Native ApplicationsArchitecting Cloud Native Applications
Architecting Cloud Native Applications
 
WSO2's API Vision: Unifying Control, Empowering Developers
WSO2's API Vision: Unifying Control, Empowering DevelopersWSO2's API Vision: Unifying Control, Empowering Developers
WSO2's API Vision: Unifying Control, Empowering Developers
 
Introduction to Multilingual Retrieval Augmented Generation (RAG)
Introduction to Multilingual Retrieval Augmented Generation (RAG)Introduction to Multilingual Retrieval Augmented Generation (RAG)
Introduction to Multilingual Retrieval Augmented Generation (RAG)
 
FWD Group - Insurer Innovation Award 2024
FWD Group - Insurer Innovation Award 2024FWD Group - Insurer Innovation Award 2024
FWD Group - Insurer Innovation Award 2024
 
DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam
DEV meet-up UiPath Document Understanding May 7 2024 AmsterdamDEV meet-up UiPath Document Understanding May 7 2024 Amsterdam
DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam
 

51822208 bpm-portal-agentless-monitoring-v2-8

  • 1. 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
  • 2. 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 Telephone 713 918 8800 or Fax 713 918 8000 2101 CITYWEST BLVD 800 841 2031 HOUSTON TX 77042-2827 USA 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.
  • 3. 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 read overviews about support services and programs that BMC offers s find the most current information about BMC products s search a database for issues similar to yours and possible solutions s order or download product documentation s download products and maintenance s report an issue or ask a question s subscribe to receive proactive e-mail alerts when new product notices are released s 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 sequence of events leading to the issue s commands and options that you used s 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
  • 4. 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. s (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. s (Asia-Pacific) Contact your BMC sales representative or your local BMC office. 4 BMC Performance Manager Portal Monitoring and Management Guide
  • 5. Contents Chapter 1 Overview of the BMC Performance Manager Portal 15 How BMC Performance Manager Portal fits into BMC Portal . . . . . . . . . . . . . . . . . . . 15 BMC Portal features common to all modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 BMC Performance Manager Portal features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 How the BMC Performance Manager Portal monitors your infrastructure. . . . . 17 Methods of data collection for Performance Managers . . . . . . . . . . . . . . . . . . . . . . 18 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 BMC Performance Manager Portal module in BMC Portal . . . . . . . . . . . . . . . . . . 19 Remote Service Monitor program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Additional security for BMC Performance Manager Portal . . . . . . . . . . . . . . . . . . 21 Security requirements for RSMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Infrastructure element credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Chapter 2 Getting started with the BMC Performance Manager Portal 23 Verifying the BMC Performance Manager Portal installation . . . . . . . . . . . . . . . . . . . 24 Adding infrastructure elements for agentless monitoring . . . . . . . . . . . . . . . . . . . . . . 25 Verifying an upgrade from an earlier version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Integrating PATROL Agent data into the BMC Performance Manager Portal . . . . . 27 Options for identifying PATROL Agents as elements . . . . . . . . . . . . . . . . . . . . . . . 28 Methods for discovering PATROL Agent data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Synchronization of thresholds and application classes . . . . . . . . . . . . . . . . . . . . . . 40 Integrating infrastructure elements from the BMC Atrium CMDB . . . . . . . . . . . . . . . 42 Viewing object status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Portal and infrastructure status views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Individual parameter history charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Parameter history tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Parameter filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Chapter 3 Users and administrators 49 User configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 About task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Account Information task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Blackout Periods task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Change Password task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Dashboards task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Element Profiles task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Elements task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Contents 5
  • 6. 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
  • 7. 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 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Parameters and thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Parameter thresholds and event severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Thresholds and parameter status changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Deactivating parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Points to remember while deactivating parameters. . . . . . . . . . . . . . . . . . . . . . . . 117 Derived parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Deactivating a parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Deactivating a parameter in the Performance Manager Editor solution . . . . . . 119 Solution support for deactivating parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Methods of remote monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Agentless monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 PATROL Agent integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Installing new Performance Managers on the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Upgrading Performance Managers on the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Removing Performance Managers from the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Types of Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Core Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Solution Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Custom Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Editing Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Editing unpublished custom Performance Managers . . . . . . . . . . . . . . . . . . . . . . 139 Editing published custom Performance Managers . . . . . . . . . . . . . . . . . . . . . . . . 139 Chapter 6 Reports 141 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Parameter update intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Standard parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Accumulated parameter values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Data summarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Data retention policies that affect object view content . . . . . . . . . . . . . . . . . . . . . . . . . 145 Retention policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Properties that control the raw data retention policies . . . . . . . . . . . . . . . . . . . . . 145 Properties that control event history retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Purging inactive data from the Portal history tables . . . . . . . . . . . . . . . . . . . . . . . 147 Purging unknown and unused events from the event table. . . . . . . . . . . . . . . . . 149 Reports tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Time interval controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Top N report for object groups or the account . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Health At A Glance report for elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Multiple parameter history charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Dashboard parameter charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Enterprise reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Contents 7
  • 8. Downloading and installing BMC Reporting Foundation 3.2.00, Crystal Reports 2008 (Designer component), and integration components . . . . . . . . . . . . . . . . 162 Installing the integration components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Upgrading to Crystal Reports 2008 (Designer component). . . . . . . . . . . . . . . . . . 174 Upgrading to BMC Reporting Foundation 3.2.00 . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Publishing and scheduling generated reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Report types and details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Uninstalling the integration components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Continuous data export configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Continuous data export requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Configuring the datafeed utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Changing the retention policy for the CDE database . . . . . . . . . . . . . . . . . . . . . . . 201 Maintaining the continuous export to the CDE database . . . . . . . . . . . . . . . . . . . 201 Additional configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 External CDE movement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Chapter 7 Portal events and data integration 217 Levels of integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Portal-wide integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Provider-wide integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Account integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 BMC Atrium CMDB integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 BMC Performance Manager Portal as a CMDB Consumer . . . . . . . . . . . . . . . . . . 220 BMC Performance Manager Portal as a CMDB Provider . . . . . . . . . . . . . . . . . . . 221 Reconciliation rules for infrastructure elements and the BMC Atrium CMDB . 221 Service Model integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Event integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Event integration using email notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Event integration using SNMP traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Event integration using AlarmPoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Event integration using BMC II Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Combining BMC Performance Manager and PATROL Agent events. . . . . . . . . 233 SNMP traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 MIB files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Object identifiers (OIDs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Parsing SNMP traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 BMC-Performance-Manager-Portal-MIB description. . . . . . . . . . . . . . . . . . . . . . . 239 Trap properties customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Sample trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Trap error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Events tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 List content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Page controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Chapter 8 BMC Performance Manager Portal command-line interface 251 Preparing the client computer for the bpmcli . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 bpmcli syntax and arguments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Data-manipulation commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 8 BMC Performance Manager Portal Monitoring and Management Guide
  • 9. addElements: adding a single element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 addElements: adding multiple elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 addPATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 deleteElements: deleting a single element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 deleteElements: deleting multiple elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 refreshDatafeedMetadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 refreshPATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 savePassword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Data-extraction commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 exportParameterHistory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 getApplicationsForElement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 getElements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 getParameterHistory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 getParameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 getPortalVersion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 getSubApplications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Chapter 9 BMC Performance Manager Portal command-line interface for BMC Datastore 285 Configuring the BMC DatastoreCLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Disabling alarms and warnings for an application class or parameter globally . . . 287 Finding application class occurrences displaying the ACS error . . . . . . . . . . . . . . . . 289 Exporting the configuration information from BMC Portal on to an HTML file . . . 292 Appendix A BMC Performance Manager Portal troubleshooting and FAQs 295 Monitoring problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 RSM computers running Windows require permission changes . . . . . . . . . . . . . . . . 296 RSM upgrade fails on Windows 2003 SP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Unable to download RSM by using IE 7 or 8 on Windows 2008 . . . . . . . . . . . . . . . . 298 Unable to close popup windows on IE Minor Versions IE 7.0 and above . . . . . . . . 299 When you use Management Profiles to integrate data, Console Server list is empty . . 299 Reinstalling the application server component of the Portal . . . . . . . . . . . . . . . . 300 Specifying RTservers for the BMC Performance Manager Portal . . . . . . . . . . . . 300 Changing the security for the BMC Performance Manager Portal . . . . . . . . . . . 301 Buffer Cache Hit Ratio and Oracle Dictionary Cache Hit Ratio parameters go into alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 Unable to download reports to csv or text file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 E-mail notification in Microsoft Outlook 2007 does not display the BMC logo and icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Portal randomly logs out users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Cannot find errors when data discovery runs as a background process. . . . . . . . . . 304 PATROL integration error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 BMC Reporting Foundation 3.2.00 troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Error message in BusinessObjects Enterprise XI 3.1. . . . . . . . . . . . . . . . . . . . . . . . 305 Report does not contain expected data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Checking log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Frequently asked questions (FAQs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Contents 9
  • 10. Appendix B Monitoring the health of the Portal 311 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Self-monitoring Performance Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 Remote Service Monitor setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Configure RSM to monitor JMX behind a firewall . . . . . . . . . . . . . . . . . . . . . . . . . 314 BMC PM Monitor application classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Performance Manager configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 PATROL Agent health monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 Configuring PATROL Agent monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Changing the threshold settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Appendix C BMC Performance Manager Portal files 319 Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 BMC Performance Manager Portal property files. . . . . . . . . . . . . . . . . . . . . . . . . . 320 Remote Service Monitor property files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Configuration file properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 BMC Performance Manager Portal log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 RSM log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 Glossary 347 Index 355 10 BMC Performance Manager Portal Monitoring and Management Guide
  • 11. Figures BMC Portal with the BMC Performance Manager Portal module installed . . . . . . . 19 Account view on the Status tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Parameter history chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Parameter history table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Buttons to filter parameters on the Status tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Types of Remote Service Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Example of RSMOptions.txt file for silent installation . . . . . . . . . . . . . . . . . . . . . . . . . 91 Clustered RSMs in the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Alert After threshold options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Performance Manager parameter mapping to Knowledge Module parameters . . 122 Affect of status changes on reported parameter values . . . . . . . . . . . . . . . . . . . . . . . 143 Standard parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Accumulated parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Top N: report settings and content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Top N: time controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Health At A Glance: time controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Health At A Glance: Element Status Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Health At A Glance: Key Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Health At A Glance: Element Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Options for multiple parameter history charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Comparative parameter history charts for one element . . . . . . . . . . . . . . . . . . . . . . . 161 Comparative parameter history report for one parameter . . . . . . . . . . . . . . . . . . . . . 161 Example of a typical report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Continuous data export process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Data target lines in the datafeed.properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Datafeed cache properties in the datafeed.properties file . . . . . . . . . . . . . . . . . . . . . . 193 Oracle properties in the datafeed.properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 CSV properties in the datafeed.properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 CDE database structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Simplified view of service model integration methods from the Portal . . . . . . . . . . 225 BMC Performance Manager Portal event integration . . . . . . . . . . . . . . . . . . . . . . . . . 226 Two comparable events from one threshold breach . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Sample agentless and agent-based events sent from the Portal . . . . . . . . . . . . . . . . . 235 OID structure in BMC-Performance-Manager-Portal-MIB . . . . . . . . . . . . . . . . . . . . . 237 Sample trap for an Element State Change event (part 1 of 2) . . . . . . . . . . . . . . . . . . . 245 Infrastructure element view of Events tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Alerts to Show list on Events tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Sample CSV file for adding elements with bpmcli . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 Sample CSV file for deleting elements with bpmcli . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Figures 11
  • 12. Using data-extraction commands to retrieve input arguments for subsequent commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 How the Historical Data Export utility uses the startData argument . . . . . . . . . . . . 273 RSM setup for monitoring the Portal components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 12 BMC Performance Manager Portal Monitoring and Management Guide
  • 13. Tables Highlights of security levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 PATROL Agent data required in CSV file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Page controls on Status tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Application ports for firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Authentication information on Logon Information screen . . . . . . . . . . . . . . . . . . . . . . 87 Options for an RSM silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 RSMs and clustered RSM counterparts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Icons for clustered RSM operating status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Minimum and maximum values for mapped thresholds . . . . . . . . . . . . . . . . . . . . . . 123 Differences between Performance Manager and Knowledge Module thresholds . 124 Core Performance Managers and their application classes . . . . . . . . . . . . . . . . . . . . 130 Features of the Performance Managers page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Application class properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Supported collection protocols for custom application classes . . . . . . . . . . . . . . . . . 136 Charts available from the Reports tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Output controls for Reports tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Element event attributes in Health At A Glance report . . . . . . . . . . . . . . . . . . . . . . . 159 Reporting integration prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 BMC Performance Manager components required for various reports . . . . . . . . . . 166 Report schedule parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 BMC Performance Manager report details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Additional configuration options for the datafeed utility . . . . . . . . . . . . . . . . . . . . . 202 Variables for arimportcmd or dataImport command . . . . . . . . . . . . . . . . . . . . . . . . . 222 Slot names in the base event class populated for the Portal . . . . . . . . . . . . . . . . . . . 231 PATROL_Portal event class extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 BMC-Performance-Manager-Portal-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Parameter error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Types of events available for object views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Page controls for Events tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Basic arguments for bpmcli commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Data-manipulation bpmcli commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 addElements arguments for adding a single element . . . . . . . . . . . . . . . . . . . . . . . . . 256 addElements arguments for adding multiple elements . . . . . . . . . . . . . . . . . . . . . . . 259 Values required for CSV input file for the addPATROL CLI command . . . . . . . . . 260 addPATROL arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 deleteElements argument for deleting a single element . . . . . . . . . . . . . . . . . . . . . . . 263 deleteElements argument for deleting multiple elements . . . . . . . . . . . . . . . . . . . . . 264 deleteElements argument for deleting multiple elements . . . . . . . . . . . . . . . . . . . . . 265 refreshPATROL arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Data-extraction bpmcli commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Tables 13
  • 14. exportParameterHistory arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 getApplicationsForElement argument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 getParameterHistory arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 getParameters argument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Parameter status values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 getSubApplications argument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Error messages for PATROL integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Predefined settings for monitoring the BMC Performance Manager Portal module . . 312 BMC PM Monitor application classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Location of BMC Performance Manager Portal property files . . . . . . . . . . . . . . . . . . 320 Properties in drmop.properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Properties in rsmcfg.properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Properties in the padm.properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Properties in rsm-RsmHostName.properties file on the RSM computer . . . . . . . . . . 342 Properties in the rsm.properties file on the RSM computer . . . . . . . . . . . . . . . . . . . . 343 Properties in portal-PortalWebServer.properties file on the RSM computer . . . . . . 343 JMX credentials on RSMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 14 BMC Performance Manager Portal Monitoring and Management Guide
  • 15. Chapter 1 Overview of the BMC Performance 1 Manager Portal This chapter describes how the BMC Performance Manager Portal module fits into the BMC Portal product and the features in BMC Performance Manager Portal. This chapter presents the following topics: How BMC Performance Manager Portal fits into BMC Portal . . . . . . . . . . . . . . . . . . . 15 BMC Portal features common to all modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 BMC Performance Manager Portal features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 How the BMC Performance Manager Portal monitors your infrastructure. . . . . 17 Methods of data collection for Performance Managers . . . . . . . . . . . . . . . . . . . . . . 18 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 BMC Performance Manager Portal module in BMC Portal . . . . . . . . . . . . . . . . . . 19 Remote Service Monitor program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Additional security for BMC Performance Manager Portal . . . . . . . . . . . . . . . . . . 21 Security requirements for RSMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Infrastructure element credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 How BMC Performance Manager Portal fits into BMC Portal BMC Portal—also referred to as the Portal—is composed of a database, application server, and web server, and provides the access point for its utilities and modules. You access the BMC Portal from a browser on your client (desktop) computer. The BMC Performance Manager Portal extends the features in the BMC Portal, enabling you to leverage both agentless technologies and the PATROL Agent to monitor the availability and performance of your business infrastructure. Chapter 1 Overview of the BMC Performance Manager Portal 15
  • 16. BMC Portal features common to all modules Your user permissions determine the extent to which you can configure and monitor your Portal account. At any time, users with the applicable permissions can view: s Current status of the infrastructure in the account s Lists of the elements and parameters in the account that recently crossed thresholds and triggered events s Charts that show how well the elements in the account performed s 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. Icons, colors, and other graphical cues enable you to quickly determine the source of problems. BMC Portal features common to all modules BMC Portal provides many common features across all of its modules, including: s Account properties s Object group names s Blackout period scheduling (times when metrics are not collected from the elements) s Customization of notification criteria that BMC Portal uses to determine when to notify your personnel about problems in your environment s Users and user groups s Object views that provide status, events, and report data s Dashboard configuration s 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. NOTE For information about configuring BMC Portal, see the BMC Portal Getting Started guide. This guide also describes the accounts, users, and administrators, as well as authentication, rights, and permissions. 16 BMC Performance Manager Portal Monitoring and Management Guide
  • 17. 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. The Status, Reports, and Events tabs provide views about your account and the objects that compose the account. Following installation and configuration of the BMC Performance Manager Portal, you can begin adding computers and other devices to the account as infrastructure elements. You organize infrastructure elements into groups to which you assign rights and permissions for users of the Portal. Collectively, infrastructure elements and groups are known as infrastructure objects. The infrastructure objects in your account correspond to the computers and devices that compose the IT infrastructure for your business. 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. An RSM is a computer on which you have installed the RSM program. Depending on the size of your environment and your high availability (HA) requirements, you can implement one or many RSMs. For more information about installing and configuring the RSM program, see Chapter 4, “Remote Service Monitors,” on page 69. To know what to monitor on the specified infrastructure elements, the RSM uses Performance Managers. Each Performance Manager contains one or more application classes that you can select to monitor operating systems, programs, files, processes, and more. Each application class contains parameters that define the type of metric to obtain from the infrastructure element. Performance Managers, 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, or when you import them from the Portal user interface. Performance Managers that are installed on the Portal are available to all users on the Portal who have the appropriate user permissions. For more information about installing application classes, see Chapter 5, “Performance Managers and application classes,” on page 113. Chapter 1 Overview of the BMC Performance Manager Portal 17
  • 18. 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. Performance Managers can provide agentless monitoring or can integrate parameter data from a PATROL Agent. After you install the Performance Managers in the Portal, you can configure the elements in your account to use the application classes in the Performance Managers. The application classes in agentless Performance Managers use industry-standard protocols, such as PerfMon and SNMP, to retrieve metrics about the performance of the monitored element. As you add elements to the account, the user interface displays the application classes available for the new elements, based on the operating system of the element. During element configuration, you can accept default thresholds or, if permitted by your user permission, modify thresholds to reflect the service level agreement (SLA) for your account. The application classes in PATROL integration Performance Managers retrieve parameter data from PATROL Agents. PATROL integration Performance Managers correspond to the PATROL Knowledge Modules (KMs) on the selected agent, and contain mappings to a subset of the parameters in the KM. You can integrate parameter data from version 3.5 and later of PATROL Agents. The RSM program begins collecting metrics about your account within minutes of your adding and configuring the first elements. As soon as data collection begins, you can use the BMC Performance Manager Portal to view performance and availability metrics and status. Components The following components compose the BMC Performance Manager Portal: s BMC Performance Manager Portal module in BMC Portal s Remote Service Monitor program 18 BMC Performance Manager Portal Monitoring and Management Guide
  • 19. BMC Performance Manager Portal module in BMC Portal Figure 1 shows how the BMC Performance Manager Portal components interact with the BMC Portal. Figure 1 BMC Portal with the BMC Performance Manager Portal module installed The programs that compose the BMC Performance BMC Portal Manager Portal module reside on the Portal application server. The RSMs obtain parameter database server metrics from the monitored elements and send RSM computer events and parameter metrics to the Portal web server. When you specify an application class that is not on the specified RSM, RSM queries the Portal for the corresponding Performance Manager. After the RSM retrieves it from the Portal, the Performance Manager remains on the RSM. web server application server web browser remote elements PATROL Agents BMC Performance Manager Portal module in BMC Portal During installation of BMC Portal, the installation program places the BMC Performance Manager Portal on the BMC Portal application server. BMC Portal provides the access point to the BMC Performance Manager Portal module and the views that provide the metrics about your monitored infrastructure. You use your Internet browser to access the Portal to view data and reports that show the performance and availability of your account. For more information about the individual components of BMC Portal, see the BMC Portal Getting Started guide. Remote Service Monitor program The Remote Service Monitor (RSM) program remotely monitors its assigned elements and sends parameter values to the Portal. You install the RSM program on each computer designated as an RSM. Chapter 1 Overview of the BMC Performance Manager Portal 19
  • 20. Security After you add an element to the Portal, the RSM begins collecting parameter data from the element at the collection intervals specified for each application class, and then sends parameter values to the Portal at the report update interval for the element. The RSM also sends parameter values to the Portal as soon as it detects that a parameter has changed its status (for example, when the parameter status changes from warning to alarm). For more information about the Remote Service Monitor program, see Chapter 4, “Remote Service Monitors,” on page 69. Security During installation of BMC Portal, the installation program installs basic security on the Portal. If you intend to integrate data from a PATROL Agent, you might need to specify a different security level. The RSM installation program also requests a security level. When integrating PATROL Agent data, the security level on the RSM must match the security of the monitored PATROL Agent. Table 1 summarizes the key elements for each of the five levels of security. Basic security (the default) is the lowest level of security. Levels 1 through 4 provide increasingly higher levels of security, along with increasingly greater configuration demands. Table 1 Highlights of security levels (part 1 of 2) Security level Description Basic security s Default level of security employed when you install PATROL, BMC Performance Manager Portal, and BMC Portal s No cryptographic protection of network traffic s No verification of product or data integrity s Authentication provided and protected password stored in unattended operations in the PATROL application s Minimized security and access control lists (ACLs) in favor of usability and performance Level 1 s Diffie-Hellman used for privacy s No SSL authentication of either party to the other 20 BMC Performance Manager Portal Monitoring and Management Guide
  • 21. Additional security for BMC Performance Manager Portal Table 1 Highlights of security levels (part 2 of 2) Security level Description Level 2 s Private communications provided by SSL s No SSL authentication performed (runs in keyless mode) s Defaults to unattended agent restart Level 3 s Private communications and server authentication provided by SSL s Certificate provided by agent so that the client can authenticate the agent s Client not authenticated back to the agent s Defaults to unattended agent restart; can configure for attended agent restart Level 4 s Private communications and mutual authentication of the console and the agent provided by SSL s Defaults to unattended agent restart; can configure for attended agent restart 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 security on the Portal must match that of the target console servers. When you install the BMC Performance Manager Portal module, the installation program asks if you want to discover PATROL Agents in a PATROL Central environment. If you select Yes, the installation prompts you for an RTserver name and for the necessary security level. For more information about security, see the PATROL Security User Guide. To change the security level for the Portal, see the BMC Portal Getting Started guide. For more information about Management Profiles and the RTserver, see your PATROL Central documentation. Chapter 1 Overview of the BMC Performance Manager Portal 21
  • 22. Security requirements for RSMs Security requirements for RSMs When installing the RSM program, the installation program prompts you for a security level. Because an RSM that integrates PATROL Agent parameter values must have the same security level as that of the PATROL Agent, you must install an RSM for each security level of the PATROL Agents from which you integrate data. If your environment does not use PATROL Agents, the installation program applies the Basic security (level 0) to the RSM. This setting enables you to change the security level at a later time, if necessary. To change the security level on an RSM, see “Changing the security level for an RSM” on page 101. Infrastructure element credentials During element configuration, the BMC Performance Manager Portal prompts you for authentication credentials that the RSM program can use to access the element. The credentials for infrastructure elements are encrypted and stored in the Portal database, using Secure Hash Algorithm (SHA), which provides 160-bit cryptographically secure hash of the credentials. The Portal encrypts the credentials and sends them to the RSM computers, and the RSM program does not store any element credentials locally. 22 BMC Performance Manager Portal Monitoring and Management Guide
  • 23. Chapter 2 Getting started with the BMC 2 Performance Manager Portal 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. The scenarios in this chapter acquaint you with the methods for configuring the BMC Performance Manager Portal to monitor your infrastructure. This chapter presents the following topics: Verifying the BMC Performance Manager Portal installation . . . . . . . . . . . . . . . . . . . 24 Adding infrastructure elements for agentless monitoring . . . . . . . . . . . . . . . . . . . . . . 25 Verifying an upgrade from an earlier version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Integrating PATROL Agent data into the BMC Performance Manager Portal . . . . . 27 Options for identifying PATROL Agents as elements . . . . . . . . . . . . . . . . . . . . . . . 28 Methods for discovering PATROL Agent data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Synchronization of thresholds and application classes . . . . . . . . . . . . . . . . . . . . . . 40 Integrating infrastructure elements from the BMC Atrium CMDB . . . . . . . . . . . . . . . 42 Viewing object status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Portal and infrastructure status views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Individual parameter history charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Parameter history tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Parameter filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Chapter 2 Getting started with the BMC Performance Manager Portal 23
  • 24. 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, including the BMC Performance Manager Portal. This section describes tasks that you can perform to ensure that the BMC Performance Manager Portal is ready to monitor infrastructure. 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. You can install one of the RSM instances on the Portal computer. 2 Use the procedure in “Adding infrastructure elements for agentless monitoring” on page 25 to add one element to the account. To test the installation, select a simple application class, such as Ping. 3 Select the Status tab. 4 In the navigation pane, expand the object tree to display the top-level Infrastructure object group and the objects that it contains. After adding the element, the status of the new infrastructure element should change to OK. If a problem occurs If the status of the element is critical, you might have a problem with the Portal installation or with the configuration of the element. s Verify that a firewall is not preventing the RSM from successfully reaching the computer. s Verify that a firewall is not preventing the RSM from sending data to the Portal. s Determine whether a network problem is causing the ping command to fail. s See the troubleshooting appendix in the BMC Portal Getting Started guide or the BMC Portal Installation Guide. 24 BMC Performance Manager Portal Monitoring and Management Guide
  • 25. Adding infrastructure elements for agentless monitoring Where to go from here s Begin adding infrastructure elements. For more information, see “Adding infrastructure elements for agentless monitoring” on this page. s Review the metrics collected about infrastructure elements. For more information, see Chapter 6, “Reports,” on page 141. Adding infrastructure elements for agentless monitoring You can quickly add computers and devices for agentless monitoring. The following scenario provides the procedure for adding an element and configuring it with the Ping application class, which measures network latency, and to verify that the element can accept network requests. Before you begin You must have at least one RSM installed and available to the Portal. For more information, see “Using the installation wizard to install the RSM program” on page 84. To add an infrastructure element to the BMC Performance Manager Portal 1 Log on with user credentials 2 Click the Configure tab. 3 Under Tasks, select Elements to open the Elements page, and click Add. 4 If the Elements–Add–Type of Element page is displayed, select Infrastructure Element, and click Next; otherwise, proceed to step 5. 5 On the Elements–Add Infrastructure Element–Select Remote Service Monitor page, select an RSM, and click Next to open the Elements–Add Infrastructure Element–Identification page. NOTE If an instance of the RSM program has not been installed, the list of Remote Service Monitors is empty. If this occurs, click Cancel and install the RSM program. See “Using the installation wizard to install the RSM program” on page 84. Chapter 2 Getting started with the BMC Performance Manager Portal 25
  • 26. Adding infrastructure elements for agentless monitoring 6 In Element Name (label), specify an element name that appears on all charts and Status pages. If you do not specify a label name, the host name or IP address is used as the element name. 7 In the text box, type the host name of the computer, select Host Name, and click Next. To add many elements, you can paste a list of host names in the text box or specify a range of IP addresses. When adding multiple elements, separate host names with commas. 8 On the Elements–Add Infrastructure Element–Select Group page, specify the platform name and group name, and click Next: A From the Element(s) Platform list, select the platform that corresponds to the host name that you specified in step 7. B In Group Name, type test group. 9 On the Elements–Add Infrastructure Element–Application Classes page, select the Networking category, select the Ping application class, and click Next. 10 On the Elements–Add Infrastructure Element–Properties and Credentials page, review the properties for the Ping application class, and click Next: s When you keep the default value for Report Update Interval Minutes, the RSM sends parameter values to the Portal every 5 minutes for BMC Portal versions earlier than 2.7, and every 10 minutes for versions 2.7 and later, unless a parameter threshold is violated. s When you keep the default value for Collection Interval, the RSM collects parameter values for the Ping application class once every minute. 11 On the Elements–Add Infrastructure Element–Thresholds page, accept the default thresholds, and click Finish. After you finish adding the element to the Portal, the RSM starts accessing the element to collect parameter values. You might need to wait a minute or two before the Portal receives the initial parameter values and updates the Status tab. Where to go from here Begin viewing the parameter metrics collected by the RSM by selecting the Status and Reports tabs. 26 BMC Performance Manager Portal Monitoring and Management Guide
  • 27. 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.1 and to ensure that the Portal is collecting data following the upgrade. If you upgraded from BMC Performance Manager Portal 2.1, your application classes were migrated to the Performance Manager format and installed on the Portal. If you upgraded from BMC Performance Manager Portal 2.3, see “To upgrade a Performance Manager during a Portal upgrade” on page 127. To verify an upgrade from BMC Performance Manager Portal version 2.3 or later 1 Log on using the Portal administrator credentials (superadmin/superadmin by default). 2 Select the Portal tab. 3 Under Tasks, 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. 4 Log on as a user and select the Status tab to view the values and status for the infrastructure elements in your account. After the upgrade, the Status tab should reflect new values collected by the upgraded application classes and RSM for your Portal. Integrating PATROL Agent data into the BMC Performance Manager Portal BMC Software has created PATROL integration Performance Managers for many of the KMs, providing mappings to many of those KMs’ parameters. Using the PATROL Agent as a data source, the RSM mines parameter data from the agent and sends it to the Portal. The BMC Performance Manager Portal can integrate parameter data from version 3.5 and later of PATROL Agents. Chapter 2 Getting started with the BMC Performance Manager Portal 27
  • 28. 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. When you specify the host names or IP addresses, you can accept the default parameter thresholds in the PATROL integration application class, or you can modify the default values (during the add process or later). The Elements–Add Infrastructure Element–Identification page provides the following options for identifying PATROL Agents and discovering thresholds from versions 3.5 and later of PATROL Agents: s Select Host Name or IP Address to specify one or more PATROL Agents as elements. When you select one of these options, you must know the KMs that are installed on the managed system and their corresponding Performance Managers in the Portal. After specifying the host names, select the PATROL integration Performance Managers that correspond to the KMs on the agents. In most cases, the PATROL integration Performance Manager names and version numbers match the PATROL KM names and version numbers. This method uses the thresholds defined in the selected PATROL integration Performance Manager. By default, threshold management is handled from the PATROL Agent. To change threshold management to the Portal, access the Properties page for element to change the threshold management preference. 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, PATROL Configuration Manager, PATROL Knowledge Module for Event Management, or other BMC Software products. NOTE The BMC Performance Manager consoles include s PATROL Central Operator - Web Edition s PATROL Central Operator - Microsoft Windows Edition s PATROL Console for Microsoft Windows s PATROL Console for UNIX® s Select PATROL Integration to have the BMC Performance Manager Portal discover the agents and the KMs on the agents, match the KMs with the PATROL integration Performance Managers on the Portal, and obtain parameter thresholds. When you use this option to discover PATROL Agents, you can also choose to monitor the health and availability of the selected PATROL Agents. For more information, see “PATROL Agent health monitoring” on page 317. For more information about managing thresholds for PATROL Agent elements, see “PATROL Agent integration” on page 121. 28 BMC Performance Manager Portal Monitoring and Management Guide
  • 29. Methods for discovering PATROL Agent data Methods for discovering PATROL Agent data When you select the PATROL Integration option, you can choose from the following discovery options: s Discover agent data from a PATROL Central environment, which requires that you specify credentials for a PATROL Console Server. This method requires that you specify an RTserver for the Portal to discover Management Profiles on the console server. When using this option, consider creating Management Profiles that contain the managed systems that you want to add. s Discover agent data from a PATROL desktop (DT) file, which requires that you specify the full path and file name for the desktop file. s Discover agent data from a PATROL Event Translation (PET) file, which requires that you specify the full path and file name for the configuration file. s Discover PATROL Agent data by specifying a comma-separated value (CSV) file that contains the element name, agent host name, port number for the PATROL Agent, and user name. The CSV file can optionally contain the password to authenticate the user name. 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. The data discovery process can take a long time, but after you click Commit to initiate the process, you can navigate to other pages by clicking the Status, Events, Reports, or Configure tab. s To view the status of the new elements, select the Status tab. s To see whether any errors occurred during data discovery, locate and view the portal.log file. See “Cannot find errors when data discovery runs as a background process” on page 304. If your PATROL environment contains a mixture of PATROL architectures, you can use a combination of the integration options. NOTE s The BMC Performance Manager Solutions CD contains many PATROL integration Performance Managers that provide integration with PATROL parameter data. s To ensure that you do not stop the Portal from mining data from the agents, do not unload the corresponding KM from the PATROL Agent. Chapter 2 Getting started with the BMC Performance Manager Portal 29
  • 30. 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, you can specify Management Profiles for the Portal to use to discover PATROL Agents. The discovery process also matches the PATROL integration Performance Managers with the KMs and obtains parameter thresholds from the agent. For more information about the components in the PATROL Central environment, see the PATROL Central documentation. Before you begin s The Portal requires an RTserver to access a Management Profile. If you did not specify an RTserver and security level during installation of the Portal, you must configure these Portal settings before proceeding. See “Specifying RTservers for the BMC Performance Manager Portal” on page 300. s The KMs must be loaded on the PATROL Agent. s Consider creating or updating Management Profiles so that you can quickly select the agents that you want. s Ensure that at least one RSM has been installed and is available to the Portal. See “Using the installation wizard to install the RSM program” on page 84. To discover PATROL Agents in a PATROL Central environment 1 Click the Configure tab, and under Tasks, select Elements to open the Elements page, and then click Add. 2 If the Elements–Add–Type of Element page is displayed, select Infrastructure Element, and click Next; otherwise, proceed to step 3 on page 42. 3 On the Elements–Add Infrastructure Element–Select Remote Service Monitor page, select an RSM to collect data from the discovered agents, and click Next. 4 On the Elements–Add Infrastructure Element–Identification page, select PATROL Integration, and click Next. 5 On the Elements–Add Infrastructure Element–Select Group page, specify the object groups for the new elements, and click Next. 6 On the Elements–Add Infrastructure Element–Select PATROL Agent for Configuration page, select PATROL Management Profile(s), and click Next. 30 BMC Performance Manager Portal Monitoring and Management Guide
  • 31. Methods for discovering PATROL Agent data 7 On the Elements–Add Infrastructure Element–Console Server Credentials page, specify the credentials to access the selected console server, and click Next: A From the list, select the console server. If your Portal administrator has not specified an RTserver, 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. 8 On the Elements–Add Infrastructure Element–Integrate Managed Systems page, select the Management Profiles to use, and click Next. 9 If necessary, on the Elements–Add Infrastructure Element–PATROL Agent Credentials page, specify the credentials for the selected agents, and click Commit. If the Management Profile had the PATROL Agent credentials saved in the console server’s profile impersonation table, Agent credentials might already be displayed on this page. s To monitor the discovered agents, select Monitor discovered PATROL Agents with PATROL Agent Availability and Health Monitor. s To change the default element name, agent name, or port from that which was discovered on the agent, type the new properties in the corresponding boxes for each applicable agent. s To apply the same credentials to all agents, type the credentials in Agent User Name and Agent Password, and click Apply to All. s To apply shared credentials to all agents, select a saved credential from the Shared Credentials list, and click Apply to All. s To provide the credentials for individual agents, type the credentials in corresponding Agent User Name and Agent Password boxes, or select a saved credential from the list. The data discovery process begins. 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. NOTE The data discovery process can take a long time. During discovery, you can navigate away from this page by clicking on the Status, Events, or Configure tab. If you navigate away from this page, you will not be able to view the Results Summary page. Chapter 2 Getting started with the BMC Performance Manager Portal 31
  • 32. 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, click Summary to display the Elements–Add Infrastructure Element–Results Summary page. This page shows the KMs on the agents that matched the available PATROL integration Performance Managers for your Portal. 11 Click Done to return to the Elements page. After you finish adding the element to the Portal, 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. Where to go from here s If you navigated to other tasks or object views during the discovery process, 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. s View or edit parameter thresholds on the new elements. To access element thresholds, take the following actions: 1. On the Configure tab, select the element in the navigation pane to open the element Properties page. 2. Under Application Classes, click Edit. Using a PATROL desktop file to discover PATROL Agents If your business uses PATROL 3.x consoles, you can use a desktop file to discover PATROL Agents. The discovery process also matches the PATROL integration Performance Managers with the KMs and obtains parameter thresholds from the agent. 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. s You must have already saved a desktop file (*.dt) from the console. For information about creating a desktop file, see your console documentation. 32 BMC Performance Manager Portal Monitoring and Management Guide
  • 33. Methods for discovering PATROL Agent data To use a PATROL desktop file to discover PATROL Agents 1 Click the Configure tab, and under Tasks, select Elements to open the Elements page, and then click Add. 2 If the Elements–Add–Type of Element page is displayed, select Infrastructure Element, and click Next; otherwise, proceed to step 3. 3 On the Elements–Add Infrastructure Element–Select Remote Service Monitor page, select an RSM to collect data from the discovered agents, and click Next. 4 On the Elements–Add Infrastructure Element–Identification page, select PATROL Integration, and click Next. 5 On the Elements–Add Infrastructure Element–Select Group page, specify the object groups for the new elements, and click Next. 6 On the Elements–Add Infrastructure Element–Select PATROL Agent for Configuration page, select Console Desktop File(s), and click Next. 7 On the Elements–Add Infrastructure Element–Console Desktop File page, use one of the following options to specify the desktop file, and click Next: s Click Browse to select a desktop file. s In File Name, type the full path and file name for the desktop file. 8 On the Elements–Add Infrastructure Element–PATROL Agent Credentials page, specify the credentials for the selected agents, and click Commit. s To monitor the discovered agents, select Monitor discovered PATROL Agents with PATROL Agent Availability and Health Monitor. s To change the default element name, agent name, or port from that which was discovered on the agent, type the new properties in the corresponding boxes for each applicable agent. s To apply the same credentials to all agents, type the credentials in Agent User Name and Agent Password, and click Apply to All. s To apply shared credentials to all agents, select a saved credential from the Shared Credentials list, and click Apply to All. s To provide the credentials for individual agents, type the credentials in corresponding Agent User Name and Agent Password boxes, or select a saved credential from the list. Chapter 2 Getting started with the BMC Performance Manager Portal 33
  • 34. Methods for discovering PATROL Agent data The data discovery process begins. 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. NOTE The data discovery process can take a long time. During discovery, you can navigate away from this page by clicking on the Status, Events, or Configure tab. If you navigate away from this page, you will not be able to view the Results Summary page. 9 When the Elements–Add Infrastructure Element–Collect Application and Threshold Data screen shows that the Portal has finished collecting data, click Summary to display the Elements–Add Infrastructure Element–Results Summary page. This page shows the KMs on the agents that matched the available Performance Managers on your Portal. 10 Click Done to return to the Elements page. After you finish adding the element to the Portal, 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. Where to go from here s If you navigated to other tasks or object views during the discovery process, 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. s View or edit parameter thresholds on the new elements. To access element thresholds, take the following actions: 1. On the Configure tab, select the element in the navigation pane to open the element Properties page. 2. Under Application Classes, click Edit. 34 BMC Performance Manager Portal Monitoring and Management Guide