BMC ProactiveNet Administrator Guide

BMC ProactiveNet
Administrator Guide
Supporting
BMC ProactiveNet version 8.5
October 2010
www.bmc.com
Contacting BMC Software

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

Address
BMC SOFTWARE INC

2101 CITYWEST BLVD
HOUSTON TX 77042-2827 USA
Telephone
1 713 918 8800

or
1 800 841 2031
Fax
1 713 918 8000
Outside United States and Canada

Telephone
+01 713 918 8800
Fax
+01 713 918 8000
Copyright 2009 - 2010 BMC Software, Inc.
BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are
registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in
other countries. All other BMC trademarks, service marks, and logos may be registered or pending
registration in the U.S. or in other countries. All other trademarks or registered trademarks are the
property of their respective owners.
BladeLogic and the BladeLogic logo are the exclusive properties of BladeLogic, Inc. The BladeLogic
trademark is registered with the U.S. Patent and Trademark Office, and may be registered or pending
registration in other countries. All other BladeLogic 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.
AIX, Active Memory, Current, DB2, Domino, IBM, Informix, Lotus, Notes, Tivoli, and WebSphere are
trademarks or registered trademarks of International Business Machines Corporation in the United States,
other countries, or both.
Linux is the registered trademark of Linus Torvalds.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks
of their respective owners.
Crystal Reports is a trademark or registered trademark of SAP AG in Germany and in several 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. UNPUBLISHEDRIGHTS 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
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
read overviews about support services and programs that BMC offers
find the most current information about BMC products
search a database for problems similar to yours and possible solutions
order or download product documentation
download products and maintenance
report a problem or ask a question
subscribe to receive proactive e-mail alerts
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:
product information
product name
product version (release number)
license number and password (trial or permanent)
operating system and environment information
machine type
operating system type, version, and service pack or other maintenance level such as PUT or PTF
system hardware configuration
serial numbers
related software (database, application, and communication) including type, version, and service pack or
maintenance level
sequence of events leading to the problem
commands and options that you used
messages received (and the time and date that you received them)
product error messages

messages from the operating system, such as file system full
messages from related software
License key and password information

If you have questions about your license key or password, contact BMC as appropriate for your location:
(USA or Canada) Contact the Order Services Password Team at 1 800 841 2031, or send an e-mail message to
ContractsPasswordAdministration@bmc.com.
(Europe, the Middle East, and Africa) Fax your questions to EMEA Contracts Administration at +31 20 354 8702, or send
an e-mail message to password@bmc.com.
(Asia-Pacific) Contact your BMC sales representative or your local BMC office.
BMC ProactiveNet Administrator Guide
Contents
Chapter 1
Getting started with the BMC ProactiveNet Administration Console
21
Accessing the BMC ProactiveNet Administration Console
....................................21
Launching the BMC ProactiveNet Administration Console on Windows
computers
..............................................................................................................22
Launching the BMC ProactiveNet Administration Console on Solaris
computers
..............................................................................................................24
Using the Search function in the BMC ProactiveNet Administration Console
......................................................................................................................................26
Configuring cell connection properties to the BMC ProactiveNet Server
.............30
Specifying ports in cell connection properties
................................................32
Setting BMC ProactiveNet Server connection properties
.........................................33
Logging out of and into the BMC ProactiveNet Server from the BMC ProactiveNet
Administration Console
.................................................................................................34
Changing your BMC ProactiveNet Administration Console password
...............35
BMC ProactiveNet profiles
............................................................................................36
Accessing online Help
....................................................................................................36
Chapter 2
Managing BMC ProactiveNet Agents
37
Adding Agents
................................................................................................................37
Editing an agent
..............................................................................................................39
About Remote Agents
...................................................................................................39
Local Agents vs. Remote Agents
.......................................................................40
Adding remote agents
.........................................................................................40
Editing remote agents
........................................................................................43
Connecting, disconnecting, and restarting agents
..........................................44
Deleting a remote agent
......................................................................................45
How do Tunnel Agents work?
......................................................................................46
Installing tunnel agents
..................................................................................................48
Tunnel proxy setup
........................................................................................................52
Adding a proxy agent to the BMC ProactiveNet Server
................................53
Adding the agent to connect through the proxy agent
..................................54
Adding a tunnel agent to the BMC ProactiveNet Server
...............................55
Converting an HTTP/HTTPS Agent to a TCP Agent
...............................................55
Converting an HTTP/Secure or HTTP Agent to HTTPS Agent
.............................56
Convert TCP Agent to HTTP/HTTPS Agent
.............................................................57
Configuration properties
...............................................................................................58
Contents
Available properties
............................................................................................59
Properties used by Tunnel Agent
......................................................................60
SSL TCP/IP Agent
..........................................................................................................61
Connecting to Agents using SSL
.......................................................................61
Converting a TCP Agent to SSL-TCP/IP Agent
.............................................61
Configuring a SSL TCP/IP Agent
...............................................................................62
Creating new keystore for the agent controller
...............................................63
Creating new keystore for the agent
.................................................................64
Updating the Agent keystore with new self-signed certificate
.....................65
Updating the Agent keystore with an existing (CA signed) certificate
.......66
Updating the Agent Controller keystore with a new self-signed
certificate
...............................................................................................................67
Updating the Agent Controller keystore with an existing (CA signed)
certificate
...............................................................................................................68
Examples for Configuring SSL TCP/IP Agents
..............................................69
TCP Proxy Agent
............................................................................................................74
Adding a TCP Proxy Agent
...............................................................................75
Limitations
............................................................................................................77
Chapter 3
Managing devices
79
Summary of devices
.......................................................................................................79
Using device aliases
........................................................................................................80
Avoiding duplicate devices
...........................................................................................81
Creating a device
............................................................................................................82
Selecting monitors for the device
................................................................................85
Editing devices
................................................................................................................86
Duplicating devices
........................................................................................................87
Deleting devices
..............................................................................................................88
Creating a monitor template
.........................................................................................89
Adding a device from a template
.................................................................................90
Applying templates to a single device
.........................................................................93
Warning message
.................................................................................................95
Applying templates to multiple devices
.....................................................................95
Editing an existing template
...............................................................................96
Deleting a Template
.............................................................................................98
Changing device associations
.......................................................................................98
Limitations
............................................................................................................99
Domain name
..................................................................................................................99
Adding a domain name
....................................................................................100
Editing a domain name
.....................................................................................100
Deleting a domain name
...................................................................................100
Port name
.......................................................................................................................101
Adding a port name
..........................................................................................101
Editing a port name
...........................................................................................102
Delete Port name
................................................................................................102
Choosing monitors for the device
.............................................................................103
Creating a group
...........................................................................................................104
Group checklist
..................................................................................................105
Working with Dynamic Groups or Rule-based Groups
..............................105
Applying rules to Dynamic Groups
................................................................106
Defining Group display
....................................................................................107
Group made by existing groups
......................................................................107
Group made by specifying rules
.....................................................................108
Adding Child Groups
..................................................................................................109
Editing Groups
..............................................................................................................111
Deleting Groups
............................................................................................................111
Chapter 4
Managing monitors
113
BMC ProactiveNet monitors
.......................................................................................113
Working with Monitors
...............................................................................................113
Monitor Wizard
.............................................................................................................115
Script monitors
..............................................................................................................115
Add Script monitors
..........................................................................................116
Edit Script monitors
...........................................................................................127
Monitor Wizard script example
.......................................................................128
Aggregate monitors
......................................................................................................132
Resource Pool
................................................................................................................132
Advantages of Resource Pool monitors
..........................................................133
Create a Resource Pool monitor type
..............................................................133
Create a Resource Pool monitor instance
.......................................................136
Find a Resource Pool monitor instance in the BMC ProactiveNet Operations
Console
................................................................................................................137
Edit a Resource Pool monitor instance
...........................................................137
Edit a Resource Pool monitor type
..................................................................137
Delete a Resource Pool monitor
.......................................................................138
Special notes
.......................................................................................................138
Abnormality Index Monitor
........................................................................................139
Creating an Abnormality Index monitor
........................................................140
Monitored attributes
..........................................................................................140
Configuration attributes
...................................................................................140
Control attributes
...............................................................................................141
Setup and dependencies
...................................................................................142
Contents
Miscellaneous information
...............................................................................143
SNMP
..............................................................................................................................143
External setup requirements to create SNMP monitor instances
...............143
Defining a SNMP monitor
................................................................................143
Compile the required MIBs
..............................................................................143
Creating an SNMP monitor type
.....................................................................144
Performance limitations
....................................................................................149
Creating an SNMP monitor instance
..............................................................149
Editing an SNMP monitor type
......................................................................151
Deleting an SNMP monitor type
.....................................................................151
Troubleshooting
.................................................................................................152
JMX
..................................................................................................................................152
JMX monitoring support
..................................................................................152
External setup requirements
............................................................................153
Creating a JMX monitor type
...........................................................................158
Example to create JMX monitor on BMC ProactiveNet Server
...................164
Editing a JMX monitor type
.............................................................................166
Delete a JMX monitor type
...............................................................................166
File monitor
....................................................................................................................167
File monitoring support
....................................................................................167
External setup requirements to create file monitor
......................................168
Create a File monitor type
................................................................................168
Creating a File monitor instance
......................................................................179
Editing a File monitor type
...............................................................................181
Deleting a File monitor type
.............................................................................181
Limitations
..........................................................................................................182
Windows Management Instrumentation
..................................................................183
............................................................................183
Creating a Windows Management Instrumentation monitor type
............184
Creating a Windows Management Instrumentation monitor instance
...............189
Setting up Agentless monitoring for a WMI monitor
..................................190
Editing a WMI monitor type
...........................................................................191
Delete a WMI monitor type
..............................................................................191
Special notes
.......................................................................................................192
Windows Performance Counter
................................................................................192
Setting up Agentless Monitoring for a Windows Performance Counter
monitors
..............................................................................................................192
Creating a Windows Performance Counter monitor type
...........................193
Creating a Windows Performance Counter monitor instance
....................198
Editing a Windows Performance Counter monitor type
.............................200
Delete a Windows Performance Counter monitor type
...............................200
Special notes
.......................................................................................................201
Exporting monitors
.......................................................................................................201
Additional information about exporting monitors
.......................................201
Monitor new subcategory
............................................................................................202
Creating a new monitor subcategory
..............................................................203
Limitations
..........................................................................................................203
Compile MIB
..................................................................................................................204
MIB Compiler features
......................................................................................204
Using the MIB Compiler
...................................................................................204
Import adapter monitor types
....................................................................................205
Transfering files to agents
..........................................................................................206
Example:
.............................................................................................................210
Organizing Custom Monitors
.....................................................................................211
Creating new categories of monitors
.........................................................................211
Example to create a new monitor category
...................................................212
Chapter 5
Working with data adapters
215
High level flow description
.........................................................................................215
Product terminology and name mapping
.................................................................218
Prerequisites
..................................................................................................................218
Adapter for BMC PATROL prerequisites
......................................................218
Adapter for BMC Performance Manager Portal prerequisites
...................219
Verifying adapter for HP OM prerequisites
..................................................219
Verifying adapter for IBM Tivoli Monitoring prerequisites
........................220
Adapter for System Center Operations Manager (SCOM) 2007
prerequisites
.......................................................................................................221
Adapter for BMC TM ART prerequisites
.......................................................221
BMC VMware Adapter
....................................................................................222
Import monitor types
...................................................................................................222
Adapters overview
.......................................................................................................223
Adapter for BMC PATROL
..............................................................................224
Adapter for BMC Performance Manager Portal
...........................................224
Adapter for HP OM overview
.........................................................................225
Adapter for IBM Tivoli overview
....................................................................227
Adapter for System Center Operation Manager (SCOM) 2007
..................229
BMC TM ART adapter overview
....................................................................230
BMC VMware Adapter
....................................................................................231
Best practices
......................................................................................................238
Adapters auto-sync feature
.........................................................................................239
Features of auto-sync framework
....................................................................239
Adapter time stamps in BMC ProactiveNet
............................................................241
Contents
Target Availability monitor type

................................................................................242
Deployment scenarios
..................................................................................................242
Performance sizing
.......................................................................................................244
Post-adapter Wizard recommendations
....................................................................244
Managing Thresholds using BMC ProactiveNet with adapters
.................245
Setting intelligent thresholds
...........................................................................245
Tuning abnormality Thresholds
......................................................................246
Limitations
.....................................................................................................................246
BMC VMware Adapter limitations
.................................................................247
Blackout period behavior
............................................................................................249
BMC Performance Manager Portal
.................................................................249
Blackout periods in multiple ProactiveNet Server deployment
.................250
Adding adapters
...........................................................................................................250
Adding an adapter for BMC PATROL
...........................................................251
Adding an adapter for BMC Portal
.................................................................282
Adding an adapter for HP OM
.......................................................................286
Adding an adapter for IBM Tivoli Monitoring
............................................299
Adding an adapter for SCOM 2007
.................................................................311
Adding an adapter for BMC TM ART
...........................................................322
Adding a BMC VMware Adapter
..................................................................331
Editing adapters
............................................................................................................334
Adding a new application class into an existing adapter instance
.............335
Deleting adapters
..........................................................................................................336
Viewing adapter details
...............................................................................................337
Searching instances
............................................................................................338
Viewing and deleting instances marked for deletion
..............................................339
Recreating deleted instances
.......................................................................................340
Show Auto-Sync progress
...........................................................................................340
Enabling data collection
..............................................................................................341
Disabling data collection
..............................................................................................341
Creating a DES encrypted password
.........................................................................342
Generating a report for instances marked for deletion
...........................................342
Chapter 6
Integrating with the BMC Atrium CMDB
345
Benefits of BMC Atrium CMDB integration
.............................................................345
User scenario
.................................................................................................................346
Creating and editing publication filters in the BMC ProactiveNet Administration
Console
...........................................................................................................................348
Understanding Atrium Filters
....................................................................................351
Viewing publication history
........................................................................................352
Viewing computer system CIs
....................................................................................353
10
Chapter 7
Configuring and using Remote Actions/Diagnostics
355
What are Remote Actions/Diagnostics?
...................................................................355
Properties files
...............................................................................................................356
Creating Remote Actions
.............................................................................................357
Defining the performance managed remote actions
....................................359
Defining the remote action rule and task
.......................................................362
Assigning roles to actions
.................................................................................367
Providing Remote Actions credentials
......................................................................367
Working with credential records for event management rules option
......368
Working with credential records for events
..................................................369
Triggering Remote Actions
.........................................................................................374
Defining the remote action policy
..................................................................374
Executing remote actions
..................................................................................377
Adding the AlarmPoint integration
................................................................378
.............................................................................................379
Generating Remote Action results
.............................................................................380
Macros for Remote Action
...........................................................................................380
Troubleshooting remote actions
.................................................................................383
Remote actions\diagnostics exit codes
.....................................................................384
Chapter 8
Setting up diagnostic commands
387
Diagnostics wizard
.......................................................................................................387
Script
..............................................................................................................................388
Register a user-defined Script command
.......................................................388
Editing script commands
..................................................................................394
Deleting script commands
................................................................................395
Creating a detailed diagnostic script for Windows
......................................395
Log file
............................................................................................................................396
Registering a user-defined log file command
................................................396
Editing a log file command
..............................................................................401
Deleting a log file command
............................................................................401
Preconfigured commands
...........................................................................................402
Top processes for BMC PATROL
....................................................................402
Top processes for Solaris
..................................................................................403
Top processes for Linux
....................................................................................405
Top processes for Windows
.............................................................................408
Top EJBs for WebSphere
...................................................................................409
Top Servlets for WebSphere
.............................................................................410
WebLogic active info
.........................................................................................412
Top SQL statements for Oracle
........................................................................412
Contents
11
Top SQL statements for MS SQL

....................................................................414
Top IP traffic
.......................................................................................................416
Oracle top wait events
.......................................................................................418
pronet.conf entries
.............................................................................................420
Oracle top table-spaces
.....................................................................................420
WebLogic active info - JMX
..............................................................................422
Solaris system configuration
...........................................................................425
Windows system configuration
.......................................................................426
JVM diagnostics
.................................................................................................427
JVM MoreInfo detailed diagnostics
................................................................429
Examining Detailed Diagnostics for BMC TM ART monitors
....................429
Examining Detailed Diagnostics for HP OM monitors
................................432
Top 10 VMs by balloon size on an ESX server
...............................................436
Top 10 VMs by CPU usage on an ESX server
................................................436
Top 10 VMs by memory usage on an ESX server
.........................................437
Top 10 VMs by network usage on an ESX server
.........................................438
Top 10 VMs by balloon memory size on a Virtual Center
...........................438
Top 10 VMs by CPU usage on a Virtual Center
............................................439
Top 10 VMs by Memory usage on a Virtual Center
.....................................439
Top 10 VMs by Network usage on a Virtual Center
.....................................440
Top 10 VMs by balloon memory size on a Resource Pool
...........................441
Top 10 VMs by CPU usage on a Resource Pool
............................................441
Top 10 VMs by memory usage on a Resource Pool
......................................442
Top 10 VMs by balloon memory size on a cluster
........................................443
Top 10 VMs by CPU usage on a cluster
..........................................................443
Top 10 VMs by Memory usage on a cluster
...................................................444
Application Diagnostics for BMC AppSight integrations
...........................445
User-defined commands
..............................................................................................450
Configuration of poll driven detailed diagnostics
...................................................451
Chapter 9
Administering BMC ProactiveNet
455
SSL server certificate for Apache server
....................................................................455
Creating a Real SSL server certificate for the Apache Server
......................455
Removing the pass-phrase at Apache startup time
......................................457
Changing the pass-phrase on the private key file
.........................................457
Creating and using your own certificate authority (CA)
............................457
Configuring the Apache web server to accept HTTPS connection only
.....................................................................................................................................458
Removing the pass-phrase window displayed during Apache startup
.....................................................................................................................................459
BMC ProactiveNet Security
.........................................................................................459
12
Securing port communication

..........................................................................460
Security related FAQs
.......................................................................................461
Customizing the BMC ProactiveNet Operations Console
......................................467
Customizing event text
.....................................................................................467
Customizing the logo on the Operations Console
........................................469
Adding background images
.............................................................................470
Changing the default number of breadcrumbs displayed in the operations
console
.................................................................................................................471
Improving performance when the navigation tree is loaded in the
operations console
.............................................................................................472
Changing the maximum number of configuration items in a folder
.........472
Configuring the operations console to automatically switch views
..........473
Scheduling downtime
..................................................................................................474
Adding a downtime schedule
..........................................................................476
Editing or deleting a downtime schedule
......................................................479
Special notes
.......................................................................................................480
Changing the default BMC ProactiveNet Agent TCP control port
......................480
Determining which TCP control ports are being used
...........................................482
Device application monitors and TCP control ports
..............................................484
Admin tunneling through HTTP
...............................................................................484
Firewalls and BMC ProactiveNet interfaces
..................................................485
Dealing with TCP/IP port restrictions
...........................................................485
Dealing with NAT
.............................................................................................486
Activating the APACHE proxy server
............................................................487
Admin tunnel limitations
.................................................................................488
Fine tuning BMC ProactiveNet system components
...............................................488
Important information for all configuration files
..........................................489
BMC ProactiveNet Server - Solaris edition
....................................................489
BMC ProactiveNet Server Windows edition
..............................................490
BMC ProactiveNet Agent Windows edition
..............................................491
Chapter 10
Managing users
493
Overview
........................................................................................................................493
Default users, user groups and roles
.........................................................................494
Users
...............................................................................................................................494
Adding or editing users
....................................................................................495
Associating user(s) to user groups
..................................................................497
Deleting users
.....................................................................................................497
User Groups
...................................................................................................................498
Adding or editing user groups
........................................................................498
Deleting user groups
.........................................................................................499
Contents
13
Roles and Permissions

..................................................................................................500
Defining or editing roles and permissions
.....................................................500
Deleting roles and permissions
........................................................................501
Configuring the system for external authentication
................................................502
Chapter 11
Deploying multiple ProactiveNet Servers
507
Multiple ProactiveNet Server deployment overview
............................................507
Configuring an originating ProactiveNet Server
.........................................508
Configuring a central ProactiveNet Server
...................................................511
Chapter 12
Setting up web transactions
513
System requirements
....................................................................................................514
How and where do I begin?
.............................................................................514
Backward compatibility
....................................................................................515
Web transaction capture screen field descriptions
..................................................516
Menu bar options
...............................................................................................516
Buttons
.................................................................................................................518
Planning a Web Transaction
.......................................................................................520
Creating a web transaction
..........................................................................................522
Need for the transaction file
............................................................................522
Launching the Web Transaction Capture tool
...............................................523
Recording a new Web Transaction
.................................................................523
Creating a test monitor
......................................................................................528
Playing a transaction file created with the Web Transaction Capture tool
529
Working with a previously recorded web transaction
................................531
Recording another transaction in the same user session
.............................531
Authentication
...............................................................................................................531
How to insert authentication information?
....................................................532
Subtransactions
.............................................................................................................533
Working with subtransactions
.........................................................................534
Configuring a Web Transaction monitor
..................................................................535
Web transaction test utility
..........................................................................................538
Pop-up Windows
..........................................................................................................539
System authentication pop-up Windows
.......................................................539
Browser pop-up Windows
...............................................................................541
Exporting Web Transaction files
................................................................................541
Editing Web Transaction files
.....................................................................................542
Editing Web Transaction files created in BMC ProactiveNet 7.0 and later
542
Editing Web Transaction files created prior to BMC ProactiveNet 7.0
......547
14
Content match for Web Transaction monitor

...........................................................547
Best practices to record content match
...........................................................548
International characters
....................................................................................548
Extra line feed characters
..................................................................................548
Web Transaction macro
...............................................................................................549
Types of Web Transaction macros
..................................................................550
Managing Web Transaction macros
................................................................551
Usage scenarios
..................................................................................................553
Limitations of Web Transaction capture
...................................................................555
Chapter 13
Working with event management policies
561
Displaying the Infrastructure Management node
....................................................561
Event management policy types
................................................................................562
Out-of-the-box event management policies
..............................................................563
How event management policies work
.....................................................................566
Event management policy workflow overview
............................................566
Event selectors
....................................................................................................567
Event selector groups
........................................................................................568
Event selection criteria
......................................................................................569
Timeframes
.........................................................................................................569
Evaluation order of event policy types
...........................................................570
How dynamic enrichment event management policies work
...............................571
External enrichment data sources
...................................................................571
How to create a new local timeframe
........................................................................573
How to add a notification service (notification policies only)
...............................575
How to create and edit a dynamic enrichment source file
.....................................576
Using the sample PATROL messaging text translation dynamic enrichment
source file
............................................................................................................578
How to create an event selector and specify event selection criteria
....................581
Alias formulas
...............................................................................................................585
Working with Event Alias Formulas
..............................................................585
Devices with multiple IP addresses
................................................................590
Creating new standard event management policies
...............................................591
Creating a new standard blackout policy
.....................................................592
Creating a new component based enrichment policy
.................................597
Creating a new component based blackout policy
.......................................602
Creating a new closure policy
.........................................................................606
Creating a new correlation policy
..................................................................609
Creating a new enrichment policy
.................................................................613
Creating a new escalation policy
....................................................................618
Creating a new notification policy
.................................................................622
Contents
15
Creating a new propagation policy

................................................................626
Creating a new recurrence policy
...................................................................628
Creating a new remote action policy
..............................................................631
Creating a new suppression policy
................................................................631
Creating a new threshold policy
.....................................................................634
Creating a new timeout policy
........................................................................638
Enabling and disabling out-of-the-box standard event management policies
...
640
Creating a new dynamic enrichment event management policy
.........................641
Enabling out-of-the-box dynamic enrichment event management policies
........653
Enabling a dynamic enrichment blackout policy
..........................................654
Enabling a dynamic enrichment location policy
...........................................657
Enabling a dynamic enrichment service contact policy
...............................661
Enabling a dynamic enrichment PATROL message text translation
policy
...................................................................................................................665
Importing dynamic enrichment source
.....................................................................669
Verifying that the policy is running
...........................................................................670
Editing event selection criteria
....................................................................................671
Deleting an event selector
............................................................................................672
Troubleshooting event management policies
...........................................................672
Chapter 14
Working with the dynamic data editor
677
Displaying the Infrastructure Management node
....................................................677
Dynamic data definition using the Dynamic Data Editor
......................................678
Navigating the Dynamic Data Editor
........................................................................678
Filtering and sorting the Data List
.............................................................................680
Filtering slots
.....................................................................................................680
Sorting data fields
..............................................................................................681
Working with data instances
......................................................................................683
Adding a new data instance
............................................................................683
Editing slots
.......................................................................................................685
Exporting data
....................................................................................................686
Chapter 15
Creating and using user-defined policies
689
Understanding user-defined event policy types
......................................................689
Understanding event processing rules (MRL) for policy types
.............................689
Format of event processing rules for policy types
........................................689
How a rule for a policy type is processed
......................................................690
Sources of information about rules
.................................................................690
User-defined event policy type creation
...................................................................691
Creating user-defined policy types
.................................................................691
16
Defining the policy data class for a new policy type

....................................691
Defining presentation names for a new policy type
.....................................693
Creating the event processing rule(s) for a new policy type
.......................694
Chapter 16
Working with BMC ProactiveNet Infrastructure Management
697
Default BMC ProactiveNet Infrastructure Management service model
..............697
Roles and permissions
.......................................................................................699
Walkthrough
..................................................................................................................699
Displaying the out-of-the-box real-time service model
...............................699
Sampling context-sensitive information
.........................................................701
Managing files on remote systems
..................................................................702
Packaging support files
.....................................................................................703
Launching remote actions
................................................................................704
Common BMC ProactiveNet Infrastructure Management tasks
...........................706
Navigating the interface
....................................................................................706
Displaying and understanding the Details and Administer tab data
...................708
Details tab data
...................................................................................................708
Administer tab data
...........................................................................................711
Editing infrastructure relationships
...........................................................................712
Creating logical components
.......................................................................................714
Deleting components
....................................................................................................714
Usage reporting
.............................................................................................................715
Executing Remote Actions
...........................................................................................716
Reloading cell configuration
.......................................................................................716
Forcing event propagation
..........................................................................................718
Collecting metrics
.........................................................................................................718
Executing other actions
................................................................................................719
Audit log parameters
..................................................................................................719
Supported component or application types
..................................................720
Sample logs
.........................................................................................................721
Audit log properties in the ias.properties file
................................................721
Creating the support package
.....................................................................................722
Slots for specifying support files
.....................................................................723
UNIX processing note
.......................................................................................724
Reviewing the audit log of the support package
..........................................725
Background to BPPM Infrastructure Management
.................................................726
How a product component registers and communicates with the IAC
...
726
Registering a remote cell with the Impact Administration Cell
.................726
Recreating an Impact Administration Cell
....................................................727
Unregistering with the IAC
..............................................................................728
Contents
17
Remote actions
...................................................................................................728
Displaying remote cells in the Infrastructure Management tab after upgrading the
BMC ProactiveNet Server
............................................................................................731
Chapter 17 Using the BMC ProactiveNet Administration Console for service monitoring 733
BMC ProactiveNet Administration Console Services Editor tab
..........................733
Monitoring business services in BMC ProactiveNet
...............................................733
Opening a Service Model View
.......................................................................734
Viewing service component instances through the navigation pane
........735
Finding service component instances to view
...............................................737
Viewing information about a service component
.........................................738
Searching for provider and consumer components
................................................739
Viewing a service components SLM agreements
...................................................740
Viewing property and performance data about a cell
............................................741
The General subtab
............................................................................................741
The Workload subtab
........................................................................................742
The Components subtab
...................................................................................743
Editing Service Model data in the BMC ProactiveNet Administration Console .
743
Managing Service Model components
...........................................................743
Managing Service Model component relationships
.....................................748
Launching BMC Atrium Explorer from the BMC ProactiveNet Administration
Console
...........................................................................................................................753
Using a customized SSL certificate to create a secure connection to the BMC
Atrium CMDB
..............................................................................................................753
Associate monitors to CIs through the BMC ProactiveNet Administration
Console
...........................................................................................................................754
Associate monitors to CI in Service Model View
..........................................755
Associating monitors to a CI and verifying that they are associated
.........756
Associate a monitor to a CI when CI Alias is unknown to the BMC
ProactiveNet Server
...........................................................................................757
Associating a monitor to a CI in the Monitor edit page
...............................758
How aliases are used depends on how the BMC ProactiveNet Servers are
deployed
..............................................................................................................758
Chapter 18
Managing cells
759
Production cells and test cells
....................................................................................759
Cell configuration tasks
...............................................................................................760
Configuring mcell.conf parameters
.................................................................761
Creating cell-specific configuration files
........................................................764
Configuring event slot propagation
................................................................765
18
About mcell.dir, the cell directory file

............................................................768
Configuring passive connections
....................................................................770
Configuring slots for time stamping
...............................................................771
Configuring encryption
....................................................................................772
Configuring cell exception handling
...............................................................777
.......................................................................................777
Starting or stopping the cell
.......................................................................................778
Stopping or starting a cell on UNIX computers
............................................779
Starting or stopping a cell on Windows computers
....................................780
Creating and managing cell groups
..........................................................................781
Monitoring event performance
...................................................................................784
Monitoring client to cell interactions
.........................................................................786
Configuring cell tracing
...............................................................................................787
Configuring mcell.trace
....................................................................................788
Configuring a destination for cell trace output
.............................................789
Sending trace output to another cell
...............................................................791
Event processing errors
.....................................................................................792
Automatic notification of trace configuration changes
................................793
Interpreting cell execution failure codes
...................................................................793
Using the BMC ProactiveNet Administration Console to manage cells
.............795
Connecting or disconnecting a cell
..................................................................795
Viewing cell information
..................................................................................795
Chapter 19
Configuring StateBuilder and gateways
797
Understanding the StateBuilder and gateways
.......................................................797
StateBuilder configuration file
.........................................................................798
statbld return codes
...........................................................................................799
Gateway configuration
......................................................................................799
Exporting events
...........................................................................................................805
Modifying a statbld.conf file to export events
...............................................805
Modifying a gateway.export file to export events
........................................806
Configuring tracing for StateBuilder
.........................................................................807
Troubleshooting the StateBuilder process
................................................................807
Chapter 20
Setting up data views for external reports
809
External reports benefits
..............................................................................................809
Performance considerations
.......................................................................................809
Creating dataviews
......................................................................................................810
Populating dataviews
...................................................................................................811
Types of information available in dataviews
..........................................................811
Default dataviews
..............................................................................................811
Contents
19
Configuration information
.........................................................................................824
Performance (stats, raw) information
........................................................................825
Rate (rolled up, condensed) information
..................................................................826
Baseline information
.....................................................................................................827
Event information
.........................................................................................................827
All alarms and events information
............................................................................828
Command line option
..................................................................................................829
Sample data dictionary
................................................................................................829
Create ASA database interface
....................................................................................831
Installing the ASA ODBC driver
....................................................................831
Downloading and installing Crystal Reports
...........................................................833
Connect to ASA database through Crystal Reports
.....................................835
Accessing the ASA database through Microsoft Excel
...........................................835
Creating sample reports using Microsoft Excel
............................................836
Appendix A
mcell.conf file parameters
841
Action result event parameters
...................................................................................841
Cell configuration parameters
....................................................................................842
Cell failover configuration parameters
......................................................................844
Client communication parameters
.............................................................................846
Encryption parameters
.................................................................................................849
Event repository cleanup parameters
........................................................................849
Heartbeat parameters
...................................................................................................852
Internal cell monitor parameters
................................................................................854
KB parameters
...............................................................................................................855
Propagation parameters
...............................................................................................855
Deprecated MessageBuffer propagation parameters
...................................857
Reporting client connection parameters
....................................................................858
Service model parameters
...........................................................................................859
State Builder parameters
..............................................................................................859
Trace parameters
...........................................................................................................860
20
1
Getting started with the BMC
ProactiveNet Administration
Console
Accessing the BMC ProactiveNet
You can access BMC ProactiveNet Administrative functions in the following ways:
the BMC ProactiveNet Administration Console
the Command Line Interface (CLI); for details, see the BMC ProactiveNet Command
Line Interface Reference Manual
the BMC ProactiveNet Performance Management Web Services Server; for details
see the BMC ProactiveNet Performance Management Web Services Server Getting
Started Guide
These administrative functions allow you to modify and manage the BMC
ProactiveNet Server and the BMC ProactiveNet Agent network management areas,
such as adding or deleting users, groups, monitored devices, applications, and
services, or changing event notifications and thresholds. All operational procedures
in this guide (unless explicitly mentioned) use the BMC ProactiveNet
Administration Console interface. For details about using the CLI commands, see the
BMC ProactiveNet Command Line Interface Reference Manual.
Some administrative options are also available through the BMC ProactiveNet
Operations Console. For details, see the BMC ProactiveNet User Guide.
Chapter 1 Getting started with the BMC ProactiveNet Administration Console 21
Before you begin

Ensure that you have successfully installed the BMC ProactiveNet Administration
Console on the computer that is hosting the BMC ProactiveNet Server. For
installation instructions, see the BMC ProactiveNet Getting Started Guide.
Connection protocols used to access the BMC ProactiveNet

Server
The BMC ProactiveNet Administration Console can connect to the BMC
ProactiveNet Server using one of the following methods:
Direct: Use this connection protocol when BMC ProactiveNet components are
installed on computers that reside on the same side of the firewall. All
functionality in the Administration tab (General Administration, Event
Management Policies, Dynamic Data Editor, and Infrastructure Management) and
the Services Editor tab in the BMC ProactiveNet Administration Console is
accessible through this connection protocol.
HTTP Tunnel: Use this connection protocol when the BMC ProactiveNet Server
and the BMC ProactiveNet Administration Console are installed on computers

that reside on different sides of the firewall. Only the General Administration
functionality in the Administration tab is accessible through this connection
protocol. The Event Management Policies, Dynamic Data Editor, Infrastructure
Management, and Services Editor tabs will be grayed out.
In an HTTPS environment, BMC ProactiveNet encrypts the information relay from

the Web interface. The Administration Console uses Secured Socket Layer (SSL)
connections and encryption to connect to the BMC ProactiveNet Server.
For more information on Secure Login, see the BMC ProactiveNet Troubleshooting
Guide.
Launching the BMC ProactiveNet Administration Console on

Windows computers
Perform the following procedure to start the administration console on Windows
computers.
22 BMC ProactiveNet Administrator Guide
To launch the BMC ProactiveNet Administration Console on Windows computers

1 On the computer where the BMC ProactiveNet Server is installed, go to Start =>
Programs => BMC ProactiveNet Server => BMC ProactiveNet Administration
Console.
2 In the BMC ProactiveNet Administration Console Logon screen, specify the
following information:
Name or IP Address of the BMC ProactiveNet Server that you want to connect
to.
User name with access rights to the BMC ProactiveNet Server. The default is
admin.
Password corresponding to the user name. The default is admin.

The type of connection to use to connect to the BMC ProactiveNet Server, either
Direct or HTTP Tunnel.
For details about the connection types, see Accessing the BMC ProactiveNet
Administration Console on page 21.
3 Click OK.
The BMC ProactiveNet Administration Console is displayed as shown in the
following figure.
Multiple Administration Consoles on Windows computers

You can have multiple BMC ProactiveNet Administration Consoles open on the
same system. Any new installation of the BMC ProactiveNet Administration Console
will be a fresh installation. If a previous version of the Administration Console
already exists on a system and you try to install the Administration Console again,
the following message is displayed:
ProactiveNet Admin is already installed in the system. This
installation will be a fresh installation and will not upgrade
previous Admin.
For troubleshooting information, see the BMC ProactiveNet Troubleshooting Guide.
Launching the BMC ProactiveNet Administration Console on

Solaris computers
Perform the following procedure to start the administration console on Solaris
computers.
To launch the BMC ProactiveNet Administration Console on Solaris computers

1 On the Solaris computer where the BMC ProactiveNet Server is installed, from a
command line, enter the following command:
pw admin
Note
For remote utilization of BMC ProactiveNet Administration Console, source the

profile using the .tmcsh script located in the /usr/pw/pronto/bin directory
before entering the pw admin command.
2 Specify the following information:
Name or IP Address of the BMC ProactiveNet Server that you want to connect
to.
User name with access rights to the BMC ProactiveNet Server. The default is
admin.
Password corresponding to the user name. The default is admin.

The type of connection to use to connect to the BMC ProactiveNet Server, either
Direct or HTTP Tunnel.
For details about the connection types, see Accessing the BMC ProactiveNet
Administration Console on page 21.
3 Click OK.
The BMC ProactiveNet Administration Console is displayed as shown in the
following figure.
Using the Search function in the BMC ProactiveNet

The Search function provides a method for finding BMC ProactiveNet resources and
enables you to search for monitors by applying various filters. This is useful in cases
where you want to change all monitors on an existing agent or change all monitors
in a certain group. The monitors listed in the search result can be edited. Also, you
can select multiple monitors in the search result and edit common control attributes
among them.
You access the Search function from the Edit menu in the Administration =>
General Administration view. For details about how to perform a search, see To
use the search function in the BMC ProactiveNet Administration Console on page
28.
The following filters can be applied to the search:
Search for Monitors using the Group filter: When the user selects the Group filter
to search for monitors, the remaining search filters are disabled and the user is
presented with a list of groups to select from. After the user selects a group and
clicks the Search option, the search result displays the list of all monitors that
belong to the selected group.
Search for Monitors using the Source Agent filter: When the user selects the
Source Agent filter to search for monitors, the remaining search filters are
disabled and the user is presented with a list of Agents associated with BMC
ProactiveNet Server. After the user selects an Agent and clicks the Search option,
the search result displays the list of all monitors that have the selected Agent as
the Source Agent.
Search for Monitors using the Target Device filter: When the user selects the
Target Device filter to search for monitors, the remaining search filters are
disabled and the user is presented with a list of devices associated with BMC
ProactiveNet Server. After the user selects a device and clicks the Search option,
the search result displays the list of monitors on the selected device.
Search for Monitors using the Monitor Type filter: When the user selects the
Monitor Type filter to search for monitors, the remaining filters are disabled and
the user is presented with a list of Monitor types for the available monitors.
Monitor type option 'ALL' is also allowed.
Note
Previously, the list of Managed object types was presented to the user. Now,
the list of Monitor Types is displayed. Managed object types like 'Device' are
eliminated from the list now.
When the user selects a Monitor type, the user can refine the search criteria using
Attribute Name-value conditions. The Attribute Name-value conditions has the
following:
List of configuration and control attributes for the selected Monitor type
List of operators (Contains, Does not contain, Starts with, Equals, Does not
Equal, Less than, Greater than)
Field to specify attribute value
The user can select an attribute from the list, specify the attribute value, and select
the operator to be applied to the selected attribute and its value. For example, if a
user selects an attribute 'Statistics Poll Interval', specifies the attribute value as '20
min' and selects the operator as 'Equals', it implies that the search result should
display those monitors whose attribute 'Statistics Poll Interval' equals '20 min'.
The user can specify multiple Attribute Name-value conditions, by using the
'MORE' option.
If there are multiple Attribute Name-value conditions, users can also indicate
whether all the attribute Name-value conditions should be matched or any one of
the specified attribute Name-value conditions can be matched.
Note
When Monitor type option 'ALL' is selected, only the control attributes
(PollRate, PollTimeout, DataCollect) and Source Agent attributes are allowed to
be used.
The search results show a list of all monitors fulfilling the search criteria. When the
search result is displayed, the user can do one of the following:
Select one of the monitors and edit/delete the selected monitor
Select multiple or all monitors and edit common control attributes
Select multiple or all monitors and delete them
To use the search function in the BMC ProactiveNet Administration Console

1 From the menu bar in the BMC ProactiveNet Administration Console, choose
Edit => Search.
2 In the Search for Monitors window, select the required filter option (select the
radio button on left), and its associated value from the list.
If you select Monitor Type, you can further refine your search by using the
Attribute, Operator, and Attribute Value fields.
Figure 1 on page 29 shows the Search for Monitors window with the Monitor
Type search criteria selected.
Figure 1: Search for Monitors with Monitor Type refining
3 Click OK.
4 The results of the search are displayed in the Search Results window as shown in
Figure 2 on page 30.
Figure 2: Example of Search Results
5 In the Search Results window, perform the following actions:

To edit a monitor, select the required monitor from the list and click Edit.
To edit common control attributes of all monitors retrieved by the Search
function, click Edit All.
To delete a monitor, select the required monitor from the list and click Delete.
Click Cancel to close the Search Results window.
Configuring cell connection properties to the

The first Impact Manager (cell) that you install is connected automatically to the
BMC ProactiveNet Server. If you create additional cells, the connection between
BMC ProactiveNet Server and each additional cell must be configured.
To configure cell connection properties

1 From the menu bar, choose Edit => Configure Administration Settings.
2 In the Configure Administration Settings dialog box, click the Impact Managers
tab.
3 Select a cell or cell group.
4 If necessary, click Advanced to display the Cell Properties section of the dialog
box.
Note
If you select a cell group, changes are applied to all the cells contained in the cell
group. If you select a single cell, changes are applied only to the individual cell.
5 Use Table 1 on page 31 to set cell connection properties as required.
Table 1: Cell connection properties
Property
Description
Name
displays the name of the cell whose properties you are changing
Host
displays the name of the host computer where the cell is installed
Port
displays the port number the cell uses to connect to the host computer
Timeout
specifies the length of time the console waits to receive data from the cell; default is 30
seconds
BMC ProactiveNet saves any negative Timeout values that you type as positive values.
Refresh Freq
sets the time interval between polls of the cell; default is 60 seconds
BMC ProactiveNet saves any negative Refresh Freq values that you type as positive values.
Attempts
sets the number of times the console attempts to connect to a cell; default is 10
BMC ProactiveNet saves any negative Attempts values that you type as positive values.
Connect Freq
time interval between connection attempts; default is 5 seconds

BMC ProactiveNet saves any negative Connect Freq values that you type as positive values.
Encrypted Mode enables and disables encryption of data between the console and the cell; default is
enabled (selected)
Auto Connect
enables and disables automatic connection to the cell at logon; default is disabled (cleared)
Auto Switch
enables and disables automatic and continuous switching of the connection from the
backup cell to the primary cell after failover, using the value set in Connect Freq as the
interval; default is disabled
Property
Description
Use Port Range
enables and disables using a specified range of local ports (on the console) for
establishing a connection between the console and a cell.
Designating a port range is useful if the console must communicate to a cell through a
firewall with only specific ports available for communication. The console scans through
the specified port range until a port is connected to the cell or the connection fails
because the port range is exhausted.
For using port range, once you select the Use Port Range check box, BMC
ProactiveNet automatically changes the Min Port No. and Max Port No. values to 1.
You must have at least four open ports within the port range, including the Min Port
No. and the Max Port No.
Min Port No.
specifies the lower limit of the port range
Max Port No.
specifies the upper limit of the port range
Auto Bind
enables and disables the automatic connection attempt of the console to the first network
card it encounters. Clear this option to bind to a specific IP address.
If only one network card exists, ensure that Auto Bind is selected. See Specifying ports in
cell connection properties on page 32 for additional information.
IP Address
specifies the IP address assigned to the local network card to which the console connects;
available only if Auto Bind is cleared
To apply IP address, encrypted mode, and maximum and minumum port cell
connection properties to connections to the jserver
By default, when you use the Administration Console to configure connections to a
remote cell, those changes are not applied to connections opened by the jserver to the
remote cell. To extend the connection properties to the connections opened by the
jserver, follow these steps:
1 In a text editor, open the pw/admin/etc/ix.properties file.
2 Set pronet.admin.applyCellConnectionPropertiesInJserver=true.
3 Save and close the file.
4 Restart the Administration Console.
Specifying ports in cell connection properties

The following circumstances require that you provide more specific information
about communications between the console and the cell:
Setting BMC ProactiveNet Server connection properties
the presence of a network interface card (NIC) between the console and the cell
the presence of a firewall between the console and the cell
using a multi-homed computer for the console
In these circumstances, you must select Use Port Range and specify the limits of the
port range and then select either Auto Bind or a particular IP address.
The Auto Bind option configures the console to connect to an NIC before it can
connect to a cell. If you specify no particular NIC, the console automatically attempts
to connect to the first NIC it encounters.
On a multi-homed computer, you can specify the NIC by selecting the IP address
that the card is using from the IP Address list box. If Auto Bind is not enabled, you
must specify a port range for the network card to which the console binds.
Note
If the console is running on a computer that is acting as a gateway between multiple

subnets, the network card that you bind to must be on the same subnet as the cell to
which the console connects.
Setting BMC ProactiveNet Server connection

properties
In addition to adding and deleting connections in the console configuration, you
must configure the connections themselves, as described in this section.
To configure a BMC ProactiveNet Server

1 From the menu bar of the BMC ProactiveNet Administration Console, choose
Edit => Configure Administration Settings.
2 In the Configure Administration Settings dialog box, click the Login Servers tab.
3 Modify any of the BMC ProactiveNet Server configuration parameters listed in
Table 2 on page 34, as needed:
Logging out of and into the BMC ProactiveNet Server from the BMC ProactiveNet Administration Console
Table 2: BMC ProactiveNet Server Configuration Parameters

Field
Description
Heartbeat Rate
specifies the frequency, in minutes, at which the console sends a signal to the
connected BMC IAS to determine whether the BMC IAS is functioning. The default
heartbeat rate is 1.
Enable Port Range
specifies the maximum and minimum port number for the console to use in
establishing a connection to a BMC IAS
Designating a port range is useful if the console must communicate to a cell
through a firewall with only specific ports available for communication. The
console scans through the ports in the specified range until a port, local to the
console, is connected to the cell or fails because the port range is exhausted.
Auto Reconnect
enables and disables automatic attempts to reconnect to the BMC ProactiveNet

Server when the connection has been dropped
The Administration Console will attempt to reconnect to the server at the
Frequency and for the Number of Retries that you specify. If, after the final try the
server is still not reconnected, an error message is displayed stating that the server
is down, and you must manually restart the server and log back on to the
Administration Console.
A status message is displayed in the status area of the Administration Console
showing the number of reconnection attempts.
4 Click Apply to save the changes, or click OK to save and exit the dialog box.
Logging out of and into the BMC ProactiveNet

Server from the BMC ProactiveNet
You can log out of the BMC ProactiveNet Server and log in from the BMC
ProactiveNet Administration Console interface without closing the console.
To log out of the BMC ProactiveNet Server from the Administration Console
Server => Logout.
2 In the Logout Confirmation dialog box, click Yes.
Changing your BMC ProactiveNet Administration Console password
To log on to the BMC ProactiveNet Server from the Administration Console

Server => Login.
2 In the BMC ProactiveNet Administration Console Logon screen, specify the
following information, enter the password for the user name that you are using to
log on to the BMC ProactiveNet Server and click OK.
The default password is admin.
Changing your BMC ProactiveNet

Administration Console password
To keep your password secure, you should change it periodically.
To change the BMC ProactiveNet Administration Console password

1 From the menu bar, choose Server => Change Password.
2 In the Change Password dialog box, in the Old Password box, enter your current
password.
3 In the New Password and Confirm New Password boxes, enter a new password.
4 Click OK.
Your password for the BMC ProactiveNet Administration Console logon is
changed immediately.
Note
If you forget your password, your administrator must clear the encrypted form of
your password from the configuration file. The next time that you log on, you will
enter a new password, and you will be prompted to confirm it. This operation
sets your new password.
In a setup where LDAP authentication is used, administrators must change
password from the LDAP server and not within the BMC ProactiveNet

BMC ProactiveNet acknowledges the following two types of profiles when logging
into the product:
Admin
User
BMC ProactiveNet Administrator manages profiles (and access rights) for individual
users.
Admin profile
Administrators have unlimited access to BMC ProactiveNet. They can configure the
environment, define individual user profiles, and perform full administrative
functions.
User profile
The BMC ProactiveNet administrator creates user profiles, and can restrict users
access to BMC ProactiveNet features. The user profile (as set by the administrator)
governs the functionality available to each user in the BMC ProactiveNet Operations
Console.
BMC ProactiveNet enables the administrator to assign access rights at both micro
and macro levels.
Accessing online Help

Choose Help => Online Help to access online versions of the BMC ProactiveNet
documentation. Context sensitive Help is provided through Help buttons on the
various dialog boxes and windows within the BMC ProactiveNet Administration
Console.
2
Managing BMC ProactiveNet
Agents
Adding Agents
Use the Add Agent option to add an agent after a device has already been set up.
To set up the device and the agent simultaneously, see About Remote Agents on
page 39.
The BMC ProactiveNet local agent (BMC ProactiveNet Agent) resides on the
computer where the BMC ProactiveNet Server is installed. Remote agents are agents
that reside on computers outside of the BMC ProactiveNet Server.
To add an agent after the device is set up

1 If not already done, install the agent software on the system where you want to
add the agent.
For information about installing the agent software, see the BMC ProactiveNet
Getting Started Guide.
2 In the Administration Console, in the Administration => General
Administration tab, expand the Devices folder.
a Drill down to the Instance level.
b Right-click the instance where you want to add the agent and click Agent =>
Add Agent.
3 In the Add Agent window, enter data in the required fields and select a
Connection option.
Chapter 2 Managing BMC ProactiveNet Agents 37
Adding Agents
Control Port - The default control port (TCP connection port) is 12124. Change
the port if 12124 is forbidden by a firewall or if it is being used by an existing

application.
To change the port, click Close, and then see Changing the default BMC
ProactiveNet Agent TCP control port on page 480.
Agent Name - BMC ProactiveNet inserts the device name that you specified.
Agent IP Address - BMC ProactiveNet inserts the IP Address (or name of the
Agent if using DNS) that you specified in the IP Address field when you
created the device.
Associated Device - BMC ProactiveNet lists devices with the same IP address.
By default, the one created on the previous screen is selected.
Connection Options.
Direct Access using TCP/IP - Select if the remote agent uses TCP/IP.
Direct Access using SSL TCP/IP - Select if the remote agent uses SSL TCP/IP.
HTTP Tunnel Proxy - Select if the remote agent uses an HTTP Tunnel. For
installation and configuration of the remote agent, see Installing tunnel

agents on page 48.
TCP Proxy - Select if the remote agent uses TCP Proxy. For further details,
see TCP Proxy Agent on page 74.
4 Click Next to create the agent.

When the agent is created, a second Add Agent window is displayed, in which
you can choose the monitor for the device
5 Choose the monitor.

6 Follow the procedure in Choosing monitors for the device on page 103.
To view the new agent, expand (or close and expand) the Agents folder. To view
the monitor, expand (or close and expand) the Monitors folder.
If a problem occurs while you are adding an agent, BMC ProactiveNet displays an
error message. For more information, see SSL server certificate for Apache server
on page 455.
Editing an agent
Editing an agent
You can edit the properties of the BMC ProactiveNet Agent by using the BMC
ProactiveNet Administration Console.
To edit agent properties

1 In the Administration Console in the Administration => General
Administration tab, open the Advanced Options folder.
2 Expand the Agent folder and locate the agent from the list.
3 Right-click the agent and select Edit.
4 In the Edit Remote Agent dialog box, change the values as necessary and click
OK.
About Remote Agents

The BMC ProactiveNet Agent is responsible for spawning the creation of monitors,
collecting data, and delivering data to BMC ProactiveNet Server for storage in the
database.
Remote Agents are those agents that reside on computers outside BMC ProactiveNet
Server. The Local Agent (aka BMC ProactiveNet Server Agent) resides on BMC
ProactiveNet Server.
Figure 3 on page 40 shows how to associate any number of BMC ProactiveNet
Agents with a BMC ProactiveNet Server. BMC ProactiveNet Agent cannot be
connected to more than one server simultaneously. Once a BMC ProactiveNet Server
is disconnected from a BMC ProactiveNet Agent, the BMC ProactiveNet Agent
becomes available to be connected to any another BMC ProactiveNet Server.
About Remote Agents
Note
If BMC ProactiveNet Server or BMC ProactiveNet Agent is rebooted or shut down
for any reason, or if the network goes down, everything reconnects automatically on
restart.
Figure 3: Connecting Server and Agents
Local Agents vs. Remote Agents

Generally, all monitors that require direct access to the devices local resource will
require an agent to be on that same computer. For example, to parse a log file, the
agent will need to reside on the device where the log file exists in order to access it.
An easy way to know if an agent is required on the device for which you want to
add a monitor is by noting the configuration parameters for the monitor. If 'Source
Agent' is one of the configuration parameters, then you have the ability to run the
monitor from any BMC ProactiveNet Agent. Two exceptions apply:
Windows monitors - These system monitors have a Source Agent configuration
parameter, but can monitor systems without an agent.
Agents status monitors must always be done from BMC ProactiveNet Server
source agent.
Note
BMC ProactiveNet Agent residing on the BMC ProactiveNet Server must

always be labeled BMC ProactiveNet Server for this monitor to work correctly.
Adding remote agents

Use this procedure to add new BMC ProactiveNet Agents to the computer where the
BMC ProactiveNet Server is installed.
About Remote Agents
To add agents
Administration tab, expand the Advanced Options folder, right-click the Agent
folder and select Add Remote Agent.
The Add Device and Agent window is displayed.
2 In the Add Device and Agent window, enter the following required information
and click Next.
Device Type - Select a device type from the list.
Device Name - Enter a descriptive name for the device.
IP Address - Enter the IP address (or name of the Agent if using DNS) you are
adding to the BMC ProactiveNet system. Example: 208.176.147.83.
3 Specify Control attributes on Control tab.

4 Click Next.
5 Specify Group Membership on the Groups Tab.
6 Click Next to open the Remote Diagnostics tab.
Protocol Types rexec, rlogin, rsh, ssh, and telnet. Select a Protocol Type from
the list.
PortNo Enter the port number where the remote service is running. Initially,
the default PortNo of the selected Protocol Type is displayed.
Local User Name Mandatory when using the rsh and rlogin Protocol Type.
The user name on the local system from where the DD is fired. Enter the Local
User Name.
Remote User Name Mandatory for all Protocol Types. Enter the Remote User
Name.
Remote User Password Mandatory for rexec, rlogin, telnet, and ssh Protocol
Types. Enter the Remote User Password. Confirm the Remote User Password.
Remote System Prompt Mandatory when using rlogin and telnet Protocol
Types.
About Remote Agents
Note
The user should give a complete remote system prompt while using rlogin
and telnet protocols. For example, if the remote system prompt is

[root@kadamba root]#, then the user should enter correctly in the remote
system prompt field. If the user uses partial system prompt, i.e. # instead of
[root@kadamba root]#, then the system is prevented from logging into the
remote device. The maximum number of characters supported for remote
system prompt is 512 characters.
The rhosts file works only on the rhosts authentication. There is no password-
based authentication. It is users responsibility to set the proper rhosts

authentication before using the rhost protocol.
For details about protocol types, see Diagnostics wizard on page 387.
7 Click Next to open the Baseline tab.

8 If required, select the device from which baseline values of existing monitors
must be copied to new monitors being created on the new device.
9 Click Next.
10 In the window that seeks server connection details, fill in the required fields.
Control Port - The default Control Port (TCP connection port) is 12124. Change
the Control Port when 12124 is forbidden by a Firewall, or because it is being

used by an existing application.
To change, click Close, then see: TCP Control Ports. For a Windows Agent, see:
Changing BMC ProactiveNet Agent (NT/2000/2003) Control Port. Otherwise,
accept the default 12124 and continue with the next step.
Agent Name - The default value is the Device Name specified on the previous
screen.
Agent IP Address - The default value is the IP Address (or name of the Agent if
using DNS) entered in the IP Address field.
Associated Device - The lists devices with the same IP address are listed. By
default, the one created on the previous screen is selected.
11 In the window that seeks server connection details, select a Connection option.
Select Direct Access using TCP/IP option if the remote agent uses TCP/IP.
Select Direct Access using SSL TCP/IP option if the remote agent uses SSL TCP/
IP. For more information, see SSL TCP/IP Agent on page 61.
About Remote Agents
Select HTTP Tunnel Proxy option if the remote agent uses an HTTP Tunnel.
Refer Tunnel Agent topic for information on installation and configuration of

the remote agent.
Select TCP Proxy option if the remote agent is to be proxied behind another
TCP Remote Agent. TCP Proxy Agent on page 74.
12 Click Next to create the agent and add monitors.

When the agent is created, the second Add Agent window is displayed to allow
selection of monitors for the device.
a Choose the monitor.
b Follow the procedure detailed in Choosing monitors for the device on page
103.
To view the new agent, expand (or close/expand) the Agents folder. To view the
monitor, expand (or close/expand) the Monitors folder.
For information, see SSL server certificate for Apache server on page 455.
To view the new agent, expand (or close/expand) the Agents folder. To view the
monitor, expand (or close/expand) the Monitors folder.
13 Select the monitors to be created on the Agent.
14 Click Finish.
BMC ProactiveNet registers the new agent and creates the specified monitors.
The status of each action is listed on the screen.

15 Click OK to complete the procedure.
Editing remote agents

When the system date/time has been changed on an Agent computer, then the
Agent must be restarted to resume data collection. You can also use the BMC
ProactiveNet Administration Console to edit remote agent properties.
To edit remote agent properties

1 In the Administration Console, expand the Advanced Options and Agents
folders.
About Remote Agents
2 Right-click the Agent to be edited and select Edit. The Edit Remote Agent
window is displayed.
3 Choose from the following:
Control Port - The default Control Port (TCP connection port) is 12124. You
change the Control Port when 12124 is forbidden by a Firewall, or because it is

used by an existing application.
To change, click Close, then see: About TCP Control Ports. For a Windows
Agent, see: Changing BMC ProactiveNet Agent (NT/2000/2003) Control Port.
Otherwise, accept the default 12124 and continue with the next step.
To change, click Close, then see: About TCP Control Ports. For a Windows
Agent, see: Changing BMC ProactiveNet Agent (NT/2000/2003) Control Port.
Otherwise, accept the default 12124 and continue with the next step.
Agent Name - Edit or rename the agent. (You cannot edit or rename 'BMC
ProactiveNet Server').
Agent IP Address - Change the agent IP address.

Associated Device - Device associated with this agent.
4 Click OK.
Note
If you have changed any values, click OK before doing a reconnect. If you do not
click OK, changes made will not be saved.
Connecting, disconnecting, and restarting agents

Use the Administration Console to connect, disconnect, and restart local and remote
agents.
To connect, disconnect, and restart agents

Administration tab, expand the Advanced Options folder and then the Agent
folder.
2 Right-click the Agent to be connected, disconnected, or restarted.
Connect Agent - Select to connect the Agent to this BMC ProactiveNet Server.
If dimmed, the agent is already connected.
About Remote Agents
Disconnect Agent - Select to disconnect the Agent from this BMC ProactiveNet
Server. If dimmed, this agent is already disconnected.
Restart Agent - Select to restart the Agent. (This works only if the agent status
is 'Connection Active').
Deleting a remote agent

When you delete an Agent from the Advanced folder, the device corresponding to
the Agent remains in the Devices folder, but all monitors which relied upon the
Agent are deleted (i.e., system monitors of the Agent or monitors using the Agent as
source IP).
Note
On deleting an Agent, the Administration Console displays the message 'all
monitors associated with Agent will be deleted'. This can be construed as that the
device will also be deleted, which is not always the case. To remove the device,
which contained the Agent, you need to delete it from the Devices folder using the
Administration Console. However, if you create a new device/agent pair, a certain
number of default monitors are automatically added (i.e., Agent Status, Node Ping,
System, and so on).
When the agent is deleted, these default monitors also get deleted. If there are no
other monitors tied to the device at this point, the device also gets deleted. If you
wish to permanently remove the Agent, you need to use the un-install function.
To delete an agent
1 From the Administration Console in the Administration => General
Administration tab, expand the Advanced Options folder and then the Agent
folder.
2 Right-click the Agent to delete, and select Delete.
If the Remote Agent is currently monitoring applications, a Warning message is
displayed.
Note
Do not delete BMC ProactiveNet Server! It must always appear in the Agent
folder. The Confirm Deletion window is displayed.
3 Click OK.
To confirm that the agent has been deleted, close and expand the Agents folder.
Tech tip
To permanently remove the Agent, you must uninstall it. For UNIX or Linux Agents,
you can uninstall the agent whether the Administration Console is open or not. For
Windows Agents, however, you must close the Administration Console first.
For instructions for uninstalling the agent, see the BMC ProactiveNet Getting Started
Guide.

When BMC ProactiveNet Server is outside the firewall, and BMC ProactiveNet
Agent is inside, using an HTTP tunnel aids in BMC ProactiveNet Agent deployment
without any changes to the Firewall configuration.
Note
In case BMC ProactiveNet Server is inside the firewall and BMC ProactiveNet Agent
is outside, this type of tunneling will not work. In such cases, it is best to open the
Firewall for outgoing connections on port 12124 and use normal TCP/IP Agents.
Alternatively, you could open the Firewall to incoming connections on port 80 and
make agents Tunneled Agents. However, this results in additional load on the CPU.
Most Firewall configurations allow outgoing connections on port 80. HTTP tunnel
acts as a virtual socket connecting BMC ProactiveNet Agent (inside the Firewall) to
BMC ProactiveNet Server (outside the Firewall). BMC ProactiveNet HTTP proxies
send and receive messages on behalf of the Agent Controller and Agent.
The Agent side of the HTTP Proxy acts as the HTTP client which sends POST to
Apache Web servlet on BMC ProactiveNet Server. From the Agent and Agent
Controller point of view, a simple socket connection is being used (which just
happens to be over a tunnel).
Figure 4: Tunneled Agent Connections - Proxy Embedded in Agent
BMC ProactiveNet Server identifies proxies using the tunnel ID assigned to the
Agent during installation. The Tunnel ID is stored in the Agents pronet.conf file. If
the assigned tunnel ID does not match the actual tunnel ID set in pronet.conf file, the
Agent will not connect. The pronet.conf file also tells the Agent proxy which URL to
connect to. As shown in the figure 'Tunneled Agent Connections - Proxy Embedded
in Agent', the URL should point to the Apache Web servlet on BMC ProactiveNet
Server.
Note
The Agent Tunnel always uses port 12124. To change the port number because of a
conflict, you must open the pronet.conf file and change it there. You cannot change
the port number via the console.
Supported modes
Tunnel Agents run both in HTTP and HTTPS mode, but, it is not advised to use
secure tunneling.
Limitations
Tunnel Agents put additional load on CPU usage and I/O of the host computer
due to embedded HTTP proxy. The impact is proportional to the amount of data
being collected by the Agent. Generally, it is an additional 1-5 percent on CPU usage.
Tunnel Agent connection is virtual, and requires Agent proxy to connect before
data transfer. Adding/editing monitors to Tunnel Agents requires more time.

Tunnel Agent does not perform as well as standard BMC ProactiveNet Agents.
Although there is no limit on how much data can be collected with a tunnel
Agent, in general, poll frequencies and number of instances supported will not be
as high as regular BMC ProactiveNet Agents.
AIX agents cannot be connected in secure tunnel mode.

The .jre file used in Red Hat Linux versions 7.1 and 9 is 1.3.1, and .jre on BMC
ProactiveNet Server is 1.4.2. Due to this mismatch in the .jre files, BMC
ProactiveNet Agent cannot connect in the Tunnel mode.
Windows Server will not perform the desired number of retries as mentioned by
the pronet.conf entry "pronet.apps.agent.pollperiod.allowednoreplies.tcp=2"

when an agent is unreachable. The agent will be set as AgentUnreachable
immediately.
Note
The process 'tunnelproxy', which shows up under 'pw process list', is the one that
takes care of tunnel connections on the server side. However, this does not affect the
way tunnel agents are configured.

This section provides procedures for how to install tunnel agents based on your
operating system.
To install tunnel agents

1 Log on to the Agent computer as 'root' (Solaris, AIX, Linux, and HP-UX) or with
Administrative privileges (Windows).
2 Insert the BMC ProactiveNet CD.
3 Follow the appropriate instructions given below based on the operating system of
the Agent computer.
To install a Solaris Agent as a tunnel agent

1 Open Command prompt.
2 Go to CD (Disc 2) => BMC ProactiveNet Agent => Solaris folder.
3 Execute setupagent.sh specifying Tunnel as additional parameter. The actual
command is as follows:
./setupagent.sh tunnel
4 On the prompt, specify the installation path.

For example: /datadisk/tunnelagent
5 Accept the Terms and other prompts.
6 On the prompt, specify the unique Tunnel ID. For example: MyTunnel33. The
Tunnel ID is an alphanumeric string (maximum length 32 characters). Special
characters and spaces are not supported.
7 This Tunnel ID is stored in pronet.conf file on the Agent computer.
installDirectory /pw/pronto/custom/conf/pronet.conf
8 Enter 'true' when prompted to 'Allow Secure Tunneling'. This is optional. Secure
mode includes Authenticated, Encrypted, and Compressed methods for sending
information through the Tunnel.
9 Specify BMC ProactiveNet Server location on the following prompt:
Enter the server name/IP address that you want to connect to:
Location is the name or IP Address of the host. For non-DNS environments,

include the computer and domain name (server.mycompany.com).
In case BMC ProactiveNet Server is using a port other than 80, you need to
append that server port number to the IP address. For BMC ProactiveNet
Server using port 8080, specify Server IP as xxx.xxx.xxx.xxx:8080.
10 The installation program records the information, and completes the installation.
On completion of the process, the message 'Proactive Agent Installation
Completed' is displayed.
To install an AIX Agent as a tunnel agent

2 Go to CD (Disc 2) => BMC ProactiveNet Agent => AIX folder.

For example: /datadisk/tunnelagent.
This Tunnel ID is stored in pronet.conf file on the Agent computer.
<installedpath>/pw/pronto/custom/conf/pronet.conf
7 Enter 'false' when prompted to 'Allow Secure Tunneling'. AIX agents cannot be
configured in secure mode

append that server port number to the IP address. For example: for BMC
ProactiveNet Server using port 8080, specify Server IP as xxx.xxx.xxx.xxx:8080.
To install a Linux Agent as a tunnel agent

2 Go to CD (Disc 2) => BMC ProactiveNet Agent => Linux folder.

For example: /datadisk/tunnelagent.
<installedpath>/pw/pronto/custom/conf/pronet.conf

To install an HP-UX Agent as a tunnel agent

2 Go to CD (Disk 2) => BMC ProactiveNet Agent => HPUX folder.

For Example: /datadisk/tunnelagent.
installDirectory /pw/pronto/custom/conf/pronet.conf

To install a Windows Agent as a tunnel agent

1 Run cmd.exe.
2 Go to CD (Disc 2) => BMC ProactiveNet Agent => Windows folder.
Tunnel proxy setup
3 Execute Agentx.x_byyy.exe (x.x is the BMC ProactiveNet Release and yyy is the
build number) by running the following command:
Agentx.x_Byyy.exe tunnel
4 On the Install shield window, navigate through the screens, accept terms, and
specify the path for installation.
Install shield starts the installation process. It prompts for the Tunnel ID and
Server name.
5 Specify Tunnel ID and Server Name.

a Tunnel ID It is an alphanumeric string with maximum 32 characters (no
special characters or spaces allowed). This ID is stored in the Agents
pronet.conf file.
b Server Name/IP Address Name/IP Address of the host computer. For nonDNS environments, be sure to include the computer name plus the domain
name (server.mycompany.com). If BMC ProactiveNet Server is using a port
other than 80, you need to append that Server port number to the IP address.
For example, suppose the Server is using the alternate HTTP port 8080. When
specifying the Server IP for this field, the IP to enter would be xxx.xxx.xxx.xxx:
8080.
6 Click Next.
You are prompted to select the mode (secure/standard).
7 Select as required and click Finish.
Tunnel proxy setup

If multiple remote agents are present behind the firewall, it is possible to use one
agent as a Proxy Agent. The proxy agent collects data from other agents and delivers
it to BMC ProactiveNet Server via http tunneling.
Proxy agent provides the following advantages:
Reduces the number of connections across the firewall
Minimizes the communications overhead introduced by secure HTTP tunneling
The Proxy agent is installed as a Tunnel Agent. It collects data from other remote
agents (normal TCP Agents) and communicates with BMC ProactiveNet Server.
Tunnel proxy setup
All NON-tunnel agents should be installed as normal TCP type. Any tunnel agent
that uses proxy agent needs to be installed as a tunnel agent with the proxy on a
different computer.
Adding a proxy agent to the BMC ProactiveNet Server

Select a computer with minimal or no monitors for hosting Proxy Agent (so it can
devote its resources to communication).
To add Proxy Agent to the BMC ProactiveNet Server

Administration tab, expand the Advanced Options folder.
2 Select the Agent folder, right click and select Add Remote Agent.
3 In the Add Device and Agent window, select the Device Type.
4 Specify the Device Name and IP Address. For example: Device Type = Server,
Device Name = Gandaki, IP Address = 192.168.3.62.
5 Select the Agent Installed on Device option.
6 Click Next. The following window is displayed.
Figure 5: Window 2 of Add Device and Agent window
7 In Connection to Server, select HTTP Tunnel Proxy.

Tunnel proxy setup
8 Specify Tunnel ID. For example: MyTunnel33.

9 Select On same machine as agent.
10 Click Finish.
Only default monitors will be created.
Adding the agent to connect through the proxy agent

BMC ProactiveNet Server uses the Tunnel ID to determine the agent to use as proxy.
Note that only tunneling agents can be used as proxy agents.
To add an agent to collect through the proxy agent

Administration tab, expand the Advanced Options folder.
2 Select the Agent folder, right click and select Add Remote Agent.
3 Select/specify Device Type, Device Name, and IP Address.
4 Select Agent Installed on Device option.
5 Click Next.
6 In the next window that displays, select HTTP Tunnel Proxy.
7 Specify Tunnel ID. For example: MyTunnel33.
8 Select On same machine as agent.
9 Click Next to view the list of default monitors.
10 On the Add Device and Agent window listing Default Monitors, clear Ping
monitor (under Network tab).
11 Click Finish. Alternatively, click Next through the various monitors. When you
get to Ping monitor, specify the IP address of the proxy agent computer as the
Source Agent. Otherwise the monitor will not be created due to firewall
constraints.
Repeat the process for other remote agents to collect via the proxy agent.
Converting an HTTP/HTTPS Agent to a TCP Agent
Adding a tunnel agent to the BMC ProactiveNet Server

The procedure is same as adding remote agents. Under Connection to server option,
Select Behind Firewall using HTTP Tunnel Proxy.
Specify the Tunnel ID and Port details.
Converting an HTTP/HTTPS Agent to a TCP

Agent
You can use the Administration Console to change the connection protocol of an
agent from HTTP/HTTPS to TCP.
To convert an HTTP/HTTPS-based Tunnel agent to TCP-based agent

1 In the Administration console, go to Advanced Options => Agent.
2 Right-click the agent instance and click Disconnect Agent.
3 Open pronet.conf file on the remote agent computer.
Note
The pronet.conf file is available in the agentHome\Agent\custom\conf folder. If

the pronet.conf file is not available under agentHome\Agent\custom\conf
directory, check for the file under agentHome\Agent\pronet\conf
4 Comment the following lines:
pronet.ipc.proxy.serverproxy.url
pronet.ipc.proxy.agentproxy.isruninternally=false
pronet.ipc.tunnel.authenticate=false
pronet.ipc.tunnel.compress=false
pronet.ipc.tunnel.encrypt=false
pronet.ipc.tunnel.mac=false
5 Restart Remote Agent.
Converting an HTTP/Secure or HTTP Agent to HTTPS Agent
6 In the Administration console in the Administration => General Administration

tab, expand the Advanced Optionsfolder and then the Agent folder.
7 Right-click the agent instance and click Edit.
8 On the Edit screen, change the connection type to TCP/IP and click OK.
The Agent reconnects during the next poll. However, the agent can be manually
reconnected at anytime.
Converting an HTTP/Secure or HTTP Agent to

HTTPS Agent
agent from HTTP to HTTPS.
To convert an HTTP agent to an HTTPS agent

Note
pronet.conf file is available under a gentHome \Agent\pronto\conf folder.
Ensure that duplicate pronet.conf files are not present under a gentHome \Agent
\custom\conf\pronet.conf. In case another file is present, you can either delete
that file or make the modifications on this file.
4 For the tunnel agents which were running under HTTP in secure mode, delete the
following lines:
pronet.ipc.tunnel.authenticate=True
pronet.ipc.tunnel.compress=True
pronet.ipc.tunnel.encrypt=True
pronet.ipc.tunnel.mac=True
5 For agents outside the server's network, qualify the server name. For example:
pronet.ipc.proxy.serverproxy.url=https://aqua.bmc.com/controller/
com.proactivenet.ipc.tunnel.Outside
6 The IP Address of the server can also be used. For example:

pronet.ipc.proxy.serverproxy.ip=https://209.11.112.186/controller/

10 On the Edit screen, change the connection type to HTTP Tunnel Proxy and click
OK.

agent from TCP to HTTP/HTTPS.
To convert a TCP agent to an HTTP/HTTPS agent

Note
pronet.conf file is available under <Agent Home>\Agent\pronto\conf folder.
Please make sure that duplicate pronet.conf files are not present under <Agent
Home>\Agent\custom\conf\pronet.conf. In case another file is present, you can
either delete that file or make the modifications on this file.
4 Add the following lines:
pronet.ipc.proxy.agentproxy.isruninternally=true
pronet.ipc.tunnel.inside.terminalid=<tunnelid>(UNIQUE)
5 To convert the TCP Agents to HTTP Agent in secure mode, add the following
properties in the pronet.conf file:
pronet.ipc.tunnel.authenticate=true
pronet.ipc.tunnel.compress=true
pronet.ipc.tunnel.encrypt=true
pronet.ipc.tunnel.mac=true
6 For agents outside the server's network, qualify the server name. For example:
For HTTP:
pronet.ipc.proxy.serverproxy.url=http://aqua.bmc.com/controller/
For HTTPS:
pronet.ipc.proxy.serverproxy.url=https://aqua.bmc.com/controller/
7 The IP Address of the server can also be used. For example:
For HTTP:
pronet.ipc.proxy.serverproxy.ip=http://209.11.112.186/controller/
For HTTPS:
pronet.ipc.proxy.serverproxy.ip=https://209.11.112.186/controller/
11 On the Edit screen, change the connection type to HTTP Tunnel Proxy and click
OK.
BMC ProactiveNet Agent installation has separate configuration files available at
two locations in the BMC ProactiveNet Agent installation directory:
agentHome /Agent/pronet/conf/pronet.conf
agentHome /Agent/custom/conf/pronet.conf
Properties available in pronet.conf file available under custom/conf/ overrides the

properties available in the other pronet.conf file.
For BMC ProactiveNet Agents installed as TCP, pronet.conf file is not available
under custom/conf/ directory.
Available properties
Note
Secure Tunnel agents can be configured only on MS Windows platform.

During Tunnel Agent installation, some of the properties are set in pronet.conf file
available under custom/conf/ directory. The change are based on user input.
For NON_SECURE mode installations, the properties are set as follows:
pronet.ipc.proxy.serverproxy.url=http\://luni/controller/
pronet.ipc.tunnel.inside.terminalid=bismi
"pronet.ipc.proxy.serverproxy.url" provides the information about the server
proxy handling URL to which tunnel agent needs to communicate. This property
is commented in the pronet.conf file under \pronto\conf\ directory.
"pronet.ipc.tunnel.inside.terminalid" specifies the unique Tunnel ID for the Agent.
The Tunnel ID is specified during the Tunnel Agent installation. The default value
is set as 1 in the pronet.conf file under \pronto\conf\ directory.
"pronet.ipc.proxy.agentproxy.isruninternally" is the most important property. It
determines whether to start the Agent Tunnel proxy or not. In case this property
is not set, the Agent Tunnel Proxy will not be started. The default value in
pronet.conf file under \pronto\conf\ directory.
For SECURE mode installations, the properties are set as follows:

pronet.ipc.proxy.serverproxy.url=http\://luni/controller/
pronet.ipc.tunnel.inside.terminalid=test1
pronet.ipc.tunnel.authenticate=true
pronet.ipc.tunnel.compress=true
pronet.ipc.tunnel.encrypt=true
pronet.ipc.tunnel.mac=true
The first three properties are similar to the NON_SECURE installation. Remaining
four properties provide the authentication. The default values for the four
properties is set to false in the pronet.conf file under \pronto\conf\ directory.
"pronet.ipc.tunnel.authenticate" provides the verification that the remote terminal
is the same remote terminal that was communicated with last time.
"pronet.ipc.tunnel.compress" specifies compression. Compression may save some
bytes and randomizes the data. This results in higher quality encryption.
"pronet.ipc.tunnel.mac" verifies that data has not been tampered with. It will very
likely be discovered and handled in case of encryption.
"pronet.ipc.tunnel.encrypt" provides the encryption status. Encryption makes it
extremely difficult to view or even tamper with data.
Properties used by Tunnel Agent

Web proxy can be configured using the following properties:
pronet.ipc.tunnel.inside.httpproxy.name=<IP Address of Web proxy server>
pronet.ipc.tunnel.inside.httpproxy.port=<Port of Web proxy server>
pronet.ipc.tunnel.inside.httpproxy.user=<User name for Web proxy server>
pronet.ipc.tunnel.inside.httpproxy.password=<Password for Web proxy server>
The system uses default values for the following unchangeable properties:
pronet.ipc.tunnel.security.signatureKeyAlgorithm = DSA(ONLY DEFAULT)
pronet.ipc.tunnel.security.signatureKeyProvider=SUN(ONLY DEFAULT)
pronet.ipc.tunnel.security.signatureKeySize=1024(ONLY DEFAULT)
pronet.ipc.tunnel.security.signatureAlgorithm= SHA1withDSA(ONLY DEFAULT)
pronet.ipc.tunnel.security.signatureProvider=SUN(ONLY DEFAULT)
pronet.ipc.tunnel.security.secureRandomAlgorithm= SHA1PRNG(ONLY DEFAULT)
pronet.ipc.tunnel.security.secureRandomProvider=SUN(ONLY DEFAULT)
pronet.ipc.tunnel.security.keyAgreeParamSize=512(ONLY DEFAULT)
pronet.ipc.tunnel.security.keyAgreeAlgorithm=DH(ONLY DEFAULT)
pronet.ipc.tunnel.security.keyAgreeProvider= SunJCE(ONLY DEFAULT)
pronet.ipc.tunnel.security.keyAgreeAlgorithmParameterSpec=
javax.crypto.spec.DHParameterSpec(ONLY DEFAULT)
pronet.ipc.tunnel.security.cipherParamSize=56(ONLY DEFAULT)
pronet.ipc.tunnel.security.cipherAlgorithm=DES(ONLY DEFAULT)
pronet.ipc.tunnel.security.cipherMode=CBC(ONLY DEFAULT)
pronet.ipc.tunnel.security.cipherPadding= PKCS5Padding(ONLY DEFAULT)
pronet.ipc.tunnel.security.cipherProvider= SunJCE(ONLY DEFAULT)
pronet.ipc.tunnel.security.macAlgorithm= HmacMD5(ONLY DEFAULT)
pronet.ipc.tunnel.security.macProvider= SunJCE(ONLY DEFAULT)
pronet.ipc.tunnel.security.macKeyAlgorithm= HmacMD5(ONLY DEFAULT)
pronet.ipc.tunnel.security.macKeyProvider= SunJCE(ONLY DEFAULT)
pronet.ipc.tunnel.security.macKeySize=64(ONLY DEFAULT)
SSL TCP/IP Agent
SSL TCP/IP Agent

By default, SSL-TCP agent connections use the following SSL configurations:
128 bits of encryption
RSA keys
SSL_RSA_WITH_RC4_128_SHA cipher suite
SSLv3 ssl version
The connections are authenticated both on BMC ProactiveNet Server and the Agent
using a certificate issued by the BMC ProactiveNet Certificate Authority (to use
certificates issued by another CA, contact support).
Connecting to Agents using SSL

Follow the steps given below to connect to agents using SSL-based TCP/IP
connections.
To connect to agents using SSL

1 Install an agent as a TCP agent.
2 Set pronet.conf file.
From the agent end, create a custom/pronet.conf file under the BMC
ProactiveNet home directory to configure the remote agent to accept SSL TCP/
IP connections from the server.
Set the property in the pronet.conf file to:
pronet.apps.agent.conntype=ssltcp
3 Restart the Agent.

4 Configure the agent on the server using the 'SSL TCP/IP' mode from the
Converting a TCP Agent to SSL-TCP/IP Agent

agent from TCP to SSL-TCP/IP agent.
To convert a TCP agent to an SSL-TCP/IP agent

1 Use the Administration Console to disconnect the existing TCP agent.
2 Add the following line to the file installDirectory /pw/custom/conf/pronet.conf
pronet.apps.agent.conntype=ssltcp
3 Restart the agent

4 Edit the remote agent connection type in the Administration Console to change to
'SSL-TCP'
5 Click OK.
6 Reconnect the agent using the Administration Console or CLI.

Secure communication between an Agent and the Agent controller is achieved by
configuring an Agent to be SSL Agent. (Refer to online documentation on how to
add a Remote Agent.)
This secure communication has the following default settings:
Trust and key management for the Agent Controller is driven by the pnserver.ks
and for Agent is driven by pnAgent.ks, keystores present in the /pw/pronto/

conf/ directory.
Trust management and key management are driven by keystores which can be
created using the keytool utility. The keystores for the Agent Controller & Agent
are specified using the following pronet.conf entries, respectively:
pronet.apps.ipc.ssl.context.controller.keystore.filename
pronet.apps.ipc.ssl.context.Agent.keystore.filename
The public-private keypairs for the Agent and Agent Controller are generated
using the RSA algorithm.
Password that is necessary for these keystores is specified in the .ks_pass file
present in the same (/pw/pronto/conf/) directory.
BMC ProactiveNet supports the following protocol suites by default for Agent-
Agent controller communication:
SSL_RSA_WITH_RC4_128_SHA
SSL_DH_anon_WITH_RC4_128_MD5
SSL_DH_anon_WITH_DES_CBC_SHA
SSL_DH_anon_WITH_3DES_EDE_CBC_SHA
SSL_DH_anon_EXPORT_WITH_RC4_40_MD5
SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA
This list is specified using the pronet.conf entry pronet.apps.ipc.ssl.enabledsuites,

which can be enhanced, depending on the type of certificates to be used.
Changing security configuration

SSL configuration of BMC ProactiveNet can be configured broadly, in the following
areas:
Create a new keystore for Agent and/or Agent Controller
To enable Agent to use a new self signed/existing certificates
To enable Agent Controller to use a new self signed/existing certificates
Limitations
As of BMC ProactiveNet 7.1 only keystore in jks format is supported. Though it
may be configurable from java.security, java.policy and pronet.conf entries, it is

not verified.
BMC Software recommends using the keytool provided as part of the BMC
ProactiveNet product only, with no other JRETM/JVMTMs installed on the same

system or at least not present in the path.
Creating new keystore for the agent controller

You can create a new keystore and use this keystore for trust and key management
for the Agent controller.
To create a new keystore for the agent controller

1 Issue the following keytool command to generate a new keystore:
keytool -keystore <path>/<keystore-name> alias <alias-name> -genkey
keyalg RSA.
This command will generate a new public-private key pair. This public key will
be wrapped in a certificate by default. This key pair along with the certificate
will be stored in the keystore file mentioned in the keystore option. Use the
RSA algorithm to generate the key pair as it is supported by default. Additional
configurations required to be changed are listed under Default Configuration
section.
2 The keystore for the Agent controller can be specified in the, pronet.conf entry
pronet.apps.ipc.ssl.context.controller.keystore.filename. Enter the
path to the newly generated keystore in this entry.
3 For trust management, add certificates into this keystore by issuing the following
command:
keytool -keystore <path> -import -alias <alias-name> -file <certificate-path>.
Type in yes when the tool prompts Trust this certificate? [no]:.
All the certificates added like this will be trusted by the Agent controller.
4 Password for this keystore must be specified in the .ks_pass file present in the /
pw/pronto/conf/ directory.
5 Restart the Agent controller for the changes to take effect.
Creating new keystore for the agent

You can create a new keystore and use this keystore for trust and key management
for the Agent.
To create a new keystore for the agent

1 Issue the following keytool command to generate a new keystore:
keytool -keystore <path>/<keystore-name> alias <alias-name> -genkey
keyalg RSA.
This command will generate a new public-private key pair. This public key will
be wrapped in a certificate by default. This key pair along with the certificate
will be stored in the keystore file mentioned in the keystore option. Use the
RSA algorithm to generate the key pair as it is supported by default. Additional
configurations required to be changed to use any other algorithm are
mentioned later.
2 The keystore for the Agent can be specified in the,
pronet.apps.ipc.ssl.context.Agent.keystore.filename pronet.conf entry.
Enter the path to the newly generated keystore in this entry.
3 For trust management, add certificates into this keystore by issuing the following
command:
keytool -keystore <path> -import -alias <alias-name> -file <certificate-path>.
All the certificates added like this will be trusted by the Agent.
4 Password for this keystore must be specified in the .ks_pass file present in the
installDirectory /pw/pronto/conf/ directory.
5 Restart the Agent controller for the changes to take effect.
Updating the Agent keystore with new self-signed certificate

The following procedure assumes that the default pnAgent.ks and pnserver.ks files
are being used. If you want to use your own keystore files then the file name must be
specified correctly in the keystore option when you update the keystore.
To update the agent keystore with a new self-signed certificate

1 Generate a key pair for the Agent by running the following command:
keytool -keystore " installationDirectory \Agent\pronto\conf\pnAgent.ks"
alias ALIAS -genkey keyalg RSA.
2 Export the newly generated key into a certificate:

keytool keystore " installationDirectory \Agent\pronto\conf\pnAgent.ks"
alias<ALIAS> -export file "certificate name"
The alias provided must match with the alias provided while generating the
keys in the previous step. Unless the destination directory is specified, the
certificate will be generated in the users home directory.
3 Make this as a trusted certificate on the Agent controller end:
Copy the certificate generated above, onto the Agent controllers computer.
Now import this certificate as a trusted certificate into the pnserver.ks keystore
by executing the following command:
keytool -keystore "<Server Installation Dir>\pw\pronto\conf\pnserver.ks"
import -alias ALIAS -file "PATH\certificate name"
Note
Alias provided above must be a new Alias. See TCP Proxy Agent on page 74
for further information.
The certificate name provided must be the name of the certificate, which was
supplied when the Agents certificate was created. The PATH is the path to the
directory where the certificate is kept.
After this step the certificate copied onto the Agent controller computer can be
deleted.
4 Restart the server and the Agent for the changes to take effect.
Updating the Agent keystore with an existing (CA signed)

certificate
To update the agent keystore with an existing certificate

1 Import the existing key pair of the Agent into the pnAgent.ks file:
Create a pkcs12 format file using the existing keypair and the certificate using the
openssl tool:
openssl pkcs12 -export -inkey key name -in certificate name -out server-new file
name.pkcs12
Note
The openssl tool is shipped as part of the BMC ProactiveNet product and can be
found in installationDirectory /pw/apache/bin or installationDirectory \pw
\ApacheGroup\Apache\bin directory.
This can be imported as a key entry, into the existing JKS format keystore using
the IBMs freely downloadable KeyMan tool.
2 Import the existing certificate of the Agent into the pnserver.ks file:
Copy the Agent certificate onto the Agent controller computer. Now import this
certificate as a trusted certificate into the pnserver.ks keystore using the command:
keytool -keystore " installationDirectory \pw\pronto\conf\pnserver.ks" import

-alias ALIAS -file "PATH\Certificate name"
Note
Alias provided above must be a new Alias. Refer Troubleshooting for further
information.
The certificate name provided must be the name of the Agents certificate. The
PATH is the path to the directory where the certificate is kept. Type in yes when
the tool prompts Trust this certificate? [no]:. After this step the certificate copied
onto the Agent controller computer can be deleted.
3 Restart the server and the Agent for the changes to take effect.
Updating the Agent Controller keystore with a new selfsigned certificate

To update the agent controller keystore with a new self-signed certificate

1 Generate a key pair for the Agent controller by running the following command:
keytool -keystore " installationDirectory \pw\pronto\conf\pnserver.ks" alias
ALIAS -genkey keyalg RSA.
keytool keystore " installationDirectory \pw\pronto\conf\pnserver.ks" alias
ALIAS -export file "Certificate name"
The alias provided must match with the alias provided while generating the keys
in the previous step. Unless the destination directory is specified, the certificate
will be generated in the users home directory.
3 Make this as a trusted certificate on the remote Agents end:
Copy the certificate generated above, onto the Agents computer. Now import
this certificate as a trusted certificate into the pnAgent.ks keystore by executing
the following command:
keytool -keystore " installationDirectory \Agent\pronto\conf\pnAgent.ks"

import -alias ALIAS -file "PATH\certificate name"
Note
information.
supplied when the Agent controllers certificate was created. The PATH is the
path to the directory where the certificate is kept.
After this step the certificate copied onto the Agents computer can be deleted.
This step has to repeated for all the remote SSL TCP/IP Agents the Agent
controller is connected to.
4 Restart the server and all the SSL TCP/IP Agents for the changes to take effect.
Updating the Agent Controller keystore with an existing (CA

signed) certificate
To update the agent controller keystore with an existing certificate

1 Import the existing key pair of the Agent controller into the pnserver.ks file:
Procedure is same as mentioned in Updating the Agent keystore with an existing
(CA signed) certificate on page 66.
2 Import the existing certificate of the Agent controller into the pnAgent.ks file:
Copy the Agent controllers certificate onto the remote Agents computer. Now
import this certificate as a trusted certificate into the pnAgent.ks keystore by
executing the following command:
keytool -keystore " installationDirectory \Agent\pronto\conf\pnserver.ks"
import -alias ALIAS -file "PATH\Certificate name"
Note
information.
The certificate name provided must be the name of the Agents certificate. The
PATH is the path to the directory where the certificate is kept.
After this step the certificate copied onto the Agents computer can be deleted.
This step will have to be repeated for all the Agents the Agent controller is
connected to.
3 Restart the server and the all Agents for the changes to take effect.
Examples for Configuring SSL TCP/IP Agents

This section provides example procedures for configuring SSL TCP/IP agents with
different keystore certificates.
Configuring a remote agent to present a new self-signed

certificate
This procedure provides an example configuration.
To configure a remote agent to present a new self-signed certificate

1 Generate a key pair for the agent by running the following command:
keytool -keystore " installationDirectory \agent\pronto\conf\pnagent.ks" alias
Note
The ALIAS provided must be a new alias.

keytool keystore " installationDirectory \agent\pronto\conf\pnagent.ks" alias
ALIAS -export file "certificate name"
The ALIAS provided must match with the alias provided while generating the
keys in the previous step. Unless the destination directory is specified, the
certificate will be generated in the users home directory.
3 Make this as a trusted certificate on the agent controller end:
Copy the certificate generated above onto the agent controllers computer. Now
import this certificate as a trusted certificate into the pnserver.ks keystore by
keytool -keystore " installationDirectory \pw\pronto\conf\pnserver.ks" -import alias ALIAS -file "PATH\certificate name"
supplied when the agents certificate was created. The PATH is the location to the
directory where the certificate is stored.
After this step the certificate copied onto the agent controller computer can be
deleted.
Note

4 Restart the server and the agent for the changes to take effect.
Configuring a remote agent to present an existing

certificate
To configure a remote agent to present an existing certificate

1 Import the existing key pair of the agent into the pnagent.ks file:
Create a pkcs12 format file using the existing keypair and the certificate. Run the
following openssl command to achieve this:
openssl pkcs12 -export -inkey key name -in certificate name -out new file
name.pkcs12
Download IBM KeyMan tool, which is available for free download and import the
pkcs12 format file generated above, into pnagent.ks file.
Note
The openssl tool is shipped along with Apache and can be found in:
installationDirectory \pw\ApacheGroup\Apache\bin\
2 Import the existing certificate of the agent into the pnserver.ks file:
Copy the agent certificate onto the agent controller computer. Now import this
certificate as a trusted certificate into the pnserver.ks keystore by executing the

following command:
keytool -keystore " installationDirectory \pw\pronto\conf\pnserver.ks" import -alias ALIAS -file "PATH\certificate name"
The certificate name provided must be the name of the agents certificate. The
PATH is the location to the directory where the certificate is stored.
After this step the certificate copied onto the agent controller computer can be
deleted.
Note

3 Restart the server and the agent for the changes to take effect.
Configuring the agent controller to present a new selfsigned certificate

To configure the agent controller to present a new self-signed certificate

1 Generate a key pair for the agent controller by running the following command:
keytool -keystore " installationDirectory \pw\pronto\conf\pnserver.ks" alias
Note

keytool keystore " installationDirectory \pw\pronto\conf\pnserver.ks" alias
ALIAS -export file "certificate name"
The alias provided must match with the alias provided while generating the keys
in the previous step. Unless the destination directory is specified, the certificate
will be generated in the users home directory.
3 Make this as a trusted certificate on the remote agents end:
Copy the certificate generated above onto the agents computer. Import this
certificate as a trusted certificate into the pnagent.ks keystore by executing the
following command:
keytool -keystore " installationDirectory \agent\pronto\conf\pnagent.ks" import -alias ALIAS -file "PATH\certificate name"
supplied when the agent controllers certificate was created. The PATH is the
location to the directory where the certificate is stored.
The Agent's controller's certificate, which was copied onto the agent's computer,
can now be deleted. This step has to be repeated for all the remote agents (which
use SSL TCP/IP) and which are connected to the agent controller.
Note
The ALIAS provided must be a new ALIAS.

4 Restart the server and all the agent(s) for the changes to take effect.
Note
To ease the transfer of agent's controller certificate to remote agents, the
following steps can be considered:
On the server, update the local agent's pnagent.ks with the agent controller's
new certificate (as mentioned above).
Transfer this pnagent.ks onto all the remote agents (which use SSL TCP/IP)
using Transfer Files to Agents feature.
Configuring the agent controller to present an existing

certificate
To configure the agent controller to present an existing certificate

1 Import the existing key pair of the agent controller into the pnserver.ks file:
Create a pkcs12 format file using the existing keypair and the certificate. Run the
following openssl command to achieve this:
openssl pkcs12 -export -inkey key name -in certificate name -out new file
name.pkcs12
Download IBM KeyMan tool, which is available for free download and import the
pkcs12 format file generated above, into pnserver.ks file.
Note
The openssl tool is shipped along with Apache and can be found in:
installDirectory \pw\ApacheGroup\Apache\bin\
2 Import the existing certificate of the agent controller into the pnagent.ks file:
Copy the agent controllers certificate onto the remote agents computer. Now
import this certificate as a trusted certificate into the pnagent.ks keystore by
keytool -keystore " installationDirectory \agent\pronto\conf\pnagent.ks" import -alias ALIAS -file "PATH\certificate name"
The certificate name provided must be the name of the agent controllers
certificate. The PATH is the location to the directory where the certificate is stored.
Type in yes when the tool prompts Trust this certificate? [no]:. After this
step the certificate copied onto the agents computer can be deleted. This step will
have to be repeated for all the agents (which use SSL TCP/IP)connected to the
agent controller.
Note
3 Restart the server and the all agents for the changes to take effect.
Note
To ease the transfer of agent's controller certificate to remote agents, the following
steps can be considered:
TCP Proxy Agent
4 On the server, update the local agent's pnagent.ks with the agent controller's new
certificate (as mentioned above).
5 Transfer this pnagent.ks onto all the remote agents (which use SSL TCP/IP) using
Transfer Files to Agents feature.
Note
All the above examples assume that you are using the default pnagent.ks and
pnserver.ks keystore files. These keystores, as mentioned in the Default
Configuration, can be configured.
Refer Troubleshooting Section for frequently observed errors and their possible
solutions.
TCP Proxy Agent

TCP Proxy Agent can be used if multiple remote agents exist behind the firewall. It is
possible to use one agent as Proxy Agent, which collects data from other agents and
delivers it to BMC ProactiveNet Server.
How does a TCP Proxy Agent work?

Any normal TCP agent can act as a proxy, collect data from agents behind it and
send them to BMC ProactiveNet Server over TCP. With the use of TCP Proxy, there
will be a dedicated connection between BMC ProactiveNet Server and ProxyAgent.
Messages can flow faster even in the environments that have network latency.
The main advantage of this feature over HTTP Tunnel is that a new connection
between proxy agent and BMC ProactiveNet Server is not created for each message
that is to be delivered to the server. Messages can flow to and from within a single
TCP Connection between agent proxy and BMC ProactiveNet Server.
Figure 6: Flow Chart of TCP Agent Proxy
TCP Proxy Agent
Features of a TCP Proxy Agent

The TCP Proxy Agent has the following features:
Any TCP/IP Agent can be used as a Proxy Agent.
To add a remote agent behind a TCP/IP Agent, select the TCP Proxy option and
a TCP Agent from list. The drop-down will list all the TCP Proxy capable Agents
on the Server.
When Proxy Agent gets disconnected from the Server, all agents will also get
disconnected and the status of these agents is shown as Proxy Agent Unreachable.
No configuration is required on the agent to make a TCP Agent act as a Proxy.
The only requirement is that the agent version should be 7.1 or higher.
For proxy communication to be secure, use a SSL/TCP Agent as the Proxy Agent.
TCP/IP Agents will have the capability to automatically detect messages to other
proxied agents and forward them correspondingly.
Messages from remote agents are sent to the agent controller using the dedicated
TCP connection established between TCP agent and Agent Controller.
Note
The following Agents cannot be configured as a TCP Proxy Agent:

HTTP Tunnel Agents.
BMC ProactiveNet Agents prior to 7.1 Version.
TCP Proxied Agents (Agents using a TCP Proxy to connect to the server).
Adding a TCP Proxy Agent

Use the Administration Console to add a TCP Proxy agent.
To add a TCP Proxy Agent

1 In the Administration Console in the Administration General Administration tab,
expand the Advanced Options.
2 Select the Agent folder, right click and choose Add Remote Agent.
TCP Proxy Agent
The Add Device and Agent window displays as shown in Figure 7 on page 76.
Figure 7: Configuration tab of Add Device and Agent window
3 In the Add Device and Agent window, select the Device Type.
4 Specify the Device Name and IP Address.
For example: Device Type = Server, Device Name = PN1, IP Address = 192.168.1.66.
5 Select the Agent Installed on Device option.
TCP Proxy Agent
6 Click Next. The following window is displayed.

Figure 8: Add Device and Agent window - continued
7 Select TCP Proxy as the Connection to Server option.

8 Select the Agent from the list containing the TCP Proxy capable agents. Select a
computer with minimal or no monitors as the Proxy Agent (so it can devote its
resources to communication).
9 Click Finish.
Note
Only default monitors will be created.
Limitations
If a TCP Proxy Agent is disconnected or shutdown, then all the agents behind it
will be unreachable.
If the Agent is behind a firewall, then the firewall has to be configured to allow
incoming connection to the Proxy Agent for the port on which Agent is listening
Windows Server will not perform the desired number of retries as mentioned by
the pronet.conf entry "pronet.apps.agent.pollperiod.allowednoreplies.tcp=2"

when an agent is unreachable. The agent will be set as AgentUnreachable
immediately.
TCP Proxy Agent
3
Managing devices
Summary of devices
You add devices to BMC ProactiveNet through the Device folder on the
When you add a device for BMC ProactiveNet to monitor, you are initially presented
with the Add Device window in which you identify the device by type.
BMC ProactiveNet offers the following device type categories:
AppServer
DBServer
Firewall
MailServer
Other
RemoteAgent
Router
Server
Switch
WebServer
BMC ProactiveNet automatically creates a set of default monitors for each device
type. After you add a device to BMC ProactiveNet, you can choose to monitor
applications residing on the device or collect statistics from its Management
Information Base (MIB), as described in the following sections.
Chapter 3 Managing devices 79
For detailed information about individual BMC ProactiveNet monitors, see the BMC
ProactiveNet Monitor Guide.

BMC ProactiveNet uses aliases to associate internal and external events to devices.
Device alias are generated when a device is created. They can be generated
automatically by BMC ProactiveNet or you can define them.
BMC ProactiveNet compares the device aliases from events with the alias defined for
each device, and when a match is found, the event is associated with the device that
matches the alias.
Aliases generated automatically are prefixed with BMC_ComputerSystem and use
the following naming conventions, depending on how the device is generated:
BMC_ComputerSystem:deviceid
BMC_ComputerSystem:deviceName
BMC_ComputerSystem:fullyQualifedDomainName
BMC_ComputerSystem:devicename_ip (if BMC_ComputerSystem:deviceName is a
duplicate)
BMC_ComputerSystem:reconid (if device is from the BMC Atrium CMDB)
When the BMC ProactiveNet cell receives an event, the event is processed as follows,
depending on whether the event is internal or external:
For internal events, BMC ProactiveNet compares the device ID from the device
alias with the device ID from the event and if a match is found, then the event is
associated with the device.
For external events, BMC ProactiveNet compares other alias values, such as
BMC_ComputerSystem:deviceName or
BMC_ComputerSystem:fullyQualifiedDomainName, with the event mc_sms_alias
slot value, which contains device information. If a match is found, then the event
is associated with the device.
If no matches are found, then the event does not get associated to any device.
When a device is created, update, or deleted in the Administration Console, the
device is also created, updated, or deleted in the BMC ProactiveNet cell.
WARNING
If a device is associated with multiple domains, the domain of the device must be the
same domain captured by the mc_host event or aliasing will fail.

In BMC ProactiveNet, a device can be created in the following ways:
through one of the following adapters:
BMC PATROL Adapter
BMC Portal Adapter
BMC adapter for VMware
System Center Operation Manager (SCOM) Adapter
BMC Transaction Management Application Response Time (BMC TM ART)
Adapter
IBM Tivoli Monitoring

HP Operations Manager
manually by using the Administration Console, a Command Line Option, or BMC
ProactiveNet Performance Management Web Services
integrating with the BMC Atrium CMDB
When duplicate devices are created

Duplicate devices could result if multiple different sources that use different naming
conventions are used to create the devices; for example, if the PATROL adapter uses
the host name of the computer where the device is located to name the device and
the BMC Atrium CMDB uses the IP address of the computer where the device is
located to name the device, then duplicate device instances would be created in BMC
ProactiveNet.
When duplicate devices are not created

Duplicate devices are not created in the following situations:
Devices are created by only one source.
Creating a device
Devices are created from different sources independently.

The different sources use the same naming convention when creating the devices;
for example, IP address, host name, or fully qualified domain name.
Device aliases are created by using alias formulas
Best practices for device creation

To avoid creating duplicate devices,
Ensure that the device is created using the fully qualified domain name of the host
computer where the device is located.
Ensure that if the device is referenced from multiple adapters that each adapter
uses the fully qualified domain name of the device.
Creating a device
Before you add devices, have the following information available:
A list of devices (by type) to add
DNS names, if you want to add devices by name
IP addresses, if you want to add devices by their IP address
For servers, a list of applications running on each server and a checklist of
applications that you want to monitor
For adding SNMP devices, a list of MIBs and community strings for each device.
BMC ProactiveNet Server uses the community string as a password for MIB
access. If you do not enter a community string, the default community string,
public, is used.
Note
If you are not using the DNS, ensure that the BMC ProactiveNet Server IP
address exists on the DNS server, mail server, or hosts file. This should have
been completed during BMC ProactiveNet Server installation. If the IP address
is not included, BMC ProactiveNet cannot poll the device and issues an error
message. To verify the BMC ProactiveNet Server environment settings, see the
BMC ProactiveNet Getting Started Guide.
Creating a device
To create a device
1 In the BMC ProactiveNet Administration Console, select the Devices folder, right
click, and select Add => Device.
2 In the Add Device window, enter the required information in the Configuration
tab.
Device Type - Select a Device Type from the list.
Note
Ensure that you select the correct Device Type. It is used by Probable Cause
Analysis algorithm to determine correlations between events and abnormalities
within the system. If the Device type is not accurate, it alters Probable Cause
Analysis behavior. Example, if a computer is a Web Server, set Device Type as
WebServer (and not just Server).
Device Name - Specify the name of the device. If the device name is a DNS
name, then the device name will be filled in automatically if it has not already
been set. This may take a few moments.
Note
Ensure that you do not use any special characters, such as /, in the device
name. If the device name includes special characters, then you cannot see the
monitors for the device when you click on the device name in the Grid view of
the BMC ProactiveNet Operations Console.
DNS Name / IP Address - Specify the devices IP address. The address
127.0.0.1 is the loop back address for any computer and should not be added to
the Device List. If the device IP address has a DNS name, then the device name
will be filled in automatically if it has not already been set.
Tag - Select a descriptive tag about the device that you are creating. Click the
plus icon
to display the Enter Tag Details dialog box, where you can
select the Tag Class as None, Location, Building, Department, or Owner, and
enter a Tag Value. For example, if the device that you are creating is located in
a particular city, you would select Location as the Tag Class and then specify
the city where the device is located as the Tag Value. Click Add to enter the
values that you specify, and then click Finish to return to the Add Device
dialog box.
Aliases - Add one or more aliases to the device that you are creating. Use
device aliases to associate events to the device, so that remote actions can be
performed on those associated events. For details about remote actions, see
Configuring and using Remote Actions/Diagnostics on page 355.
Secondary IPs - View any secondary IP addresses associated with the device
that you are creating, if that device has multiple IP addresses. The first IP
Creating a device
address that is associated with the Device Name that you specify is used as the
primary IP address. Any additional IP addresses are used as secondary IP
addresses. If no secondary IP addresses exist, then N.A is displayed in this
field. To view all secondary IP addresses, click on the ellipses button.
Note
Only devices that have been synchronized with the BMC Atrium CMDB
display secondary IP addresses. Manually created devices will not display
secondary IP addresses even if multiple IP addresses exist for that device.
Device Description - Enter a description about the device that you are creating.
Agent Installed on Device - Select this option if you have installed a BMC
ProactiveNet Agent on this device. Some monitors require that an agent be

installed on the target device.
3 Click the Control tab to edit the control attributes.

Information in the Control tab tells the BMC ProactiveNet Server about the
desired data collection and polling frequencies for the device. You can accept the
defaults or change them as required.
SNMP Data Collection - Select this option to enable BMC ProactiveNet Server
to collect data for the entire device. If this option is not selected, data collection
for the device stops (or for new devices, never starts). This flag lets you set up
monitors for devices that may not yet be online. Or, you can conduct
maintenance on existing devices without generating events.
SNMP Read Community String - The Community String acts as a password
for BMC ProactiveNet Server access to the device MIB. To change this entry,
you must have prior knowledge of how this device is set up. For example, if
this device is set up for the Community String snmpget, then enter snmpget.
SNMP Retries - Specifies how many times (count) BMC ProactiveNet Server
must request data from the device before reporting an event. Default is 2 retries.
SNMP Timeout - Specifies the duration (seconds) BMC ProactiveNet Server
must wait for data from the device before reporting an event. Default is 2 seconds.
SNMP Use V2 - Select this option if the device is using version 2 of the protocol.
4 Click the Group Tab and enter the required information.

This tab enables you to add a device and its monitors to one or more groups.
Optionally, you may associate the device with a group. A group is used to
logically organize devices and monitors by department, geographic area, or
service. Assigning a device to a group also enables the system administrator to
restrict or allow access to certain devices by group. If you want the device to be
associated with a group, select the group name here.
5 Click the Remote Actions/Diagnostics tab and enter the required information.
Protocol Types Select a protocol type from the list. The supported protocols
are psExec, ssh (Secure Shell), and telnet.
PortNo Default port number of the selected Protocol Type is displayed.

Remote User Name Enter the remote user name. This is mandatory for all
Protocol Types.
Remote User Password Enter the remote user password. Mandatory for
psExec, ssh, and telnet protocol types. Confirm the remote user password.
Note
You should give a complete remote system prompt while using telnet protocols.
For example, if the remote system prompt is [root@kadamba root]#, then you
should enter correctly in the remote system prompt field. You should not use a
partial system prompt, for example, # for [root@kadamba root]#, which might
prevent the system from logging into the remote device. The maximum number
of characters supported for remote system prompt is 512 characters.
For detailed information about Remote Actions, see Configuring and using
Remote Actions/Diagnostics on page 355.
6 Open the Baseline tab.
By default, no device is selected when you access the Baseline tab. When you
select a device to copy baseline values from, then for all monitors being added
to the new device, a corresponding monitor is searched on the selected device.
If matching monitors are present, then all baseline values (hourly and weekly)
are copied from the existing monitor to the new monitor instances being created.
7 Click Finish to save your actions and execute all remaining actions (using
defaults).
This opens a summary panel. Click Finish.

Based upon the Device Type selected in the Configuration tab, the system
automatically pre-selects some default monitors and pre-selects the Monitor tab. For
example, for the Device Type 'Server', the NodePing monitor is pre-selected; and if
Editing devices
an agent is installed on the device, System and TCP/IP and Agent Status Monitors
are pre-selected, and the System Tab is pre-selected. You can add additional
monitors for the applications and components installed on the device.
To select monitors for a device

1 Select the monitors that you want to create for this device.
If the device has more than one application that needs monitoring, for example,
a server running Mail and IP services, select all of the monitors here using the
various tabs, or go back and add the monitors later.
2 Click Next.
First the Creating... Monitor screen opens, followed by the configuration
windows for each monitor you selected.
The Configuration window contains specific entry fields, as shown in this

example. Refer to the BMC ProactiveNet Monitor Guide for detailed instructions
regarding setting the parameters for the monitors.
Notice that each monitor also has a Control tab, which specifies the data
collection and polling frequency for individual Application, Intelliscope, or
SNMP Monitors. And similar to the Configuration tab, the input fields in the
Control tab vary depending on the selected monitor.
Click Skip if you have selected several monitors to add and you change your
mind about one of them or you are uncertain about an entry field
Clicking Skip moves on to the next monitors configuration. The skipped
monitor is not added. The program continues normally. When the last monitor
is configured, the Summary screen appears to show what was created.
3 Click Finish.
To view the new device listing, expand (or close and expand) the corresponding
device folder.
Editing devices
Perform the following steps to modify an existing device.
To edit devices
Devices published from the BMC Atrium CMDB cannot be edited in the BMC
ProactiveNet Administration Console. Also, you cannot edit a device alias for a
published device.
Duplicating devices
1 In the Administration Console, expand the Device folder

2 Expand the device type folder, and select the device to edit.
3 Right click on the device and select Edit.
4 On the Configuration tab, make any required changes.
5 On the Control tab, make any required changes.
6 Click OK.
If you make changes on the Control tab, all SNMP-based monitors are updated.
However, if a Distributed Interface MIB Monitor instance exists on the device and
you make any changes on the Control tab, the Affected SNMP-based Auto
Discovery-enabled Monitors window is displayed.
7 Select the monitor to which to apply the new control settings.
8 Click OK.
Duplicating devices
You use the Duplicate option to use an existing device and its monitors as a
prototype for creating a new device. For example, if you have three servers with four
similar applications that you want to monitor, you can add the first server with the
applications, and then use that server as a template for creating the other two
servers. For each additional server, you only need to enter the new IP address or
DNS name.
To duplicate a device
1 In the Administration Console, expand the Devices folder.
2 Expand the device type folder, and select the device that you want to duplicate.
3 Right-click the device and select Duplicate.
4 In the Duplicate Device window, configure information on the Configuration,
Control, and Group tabs, as required.
The Duplicate option enables you to use the highlighted device and its monitors
as a prototype for creating a new device. For example, if you have 3 servers with 4
similar applications that you want to monitor, you can add the first server with
Deleting devices
the applications, and then use that server as a template for creating the other two.
For each additional server, you only need to enter the new IP address or DNS name.
Note
The Duplicate option does not save or store information. If you want to save
the information for future use when creating the same monitors on different
devices, use the Create Template feature.
The Duplicate option does not duplicate or capture line graphs and absolute
instance thresholds for auto-created SNMP objects like Interface and DLCI.
However, these details are captured for custom SNMP monitors that you
create using the Monitor Wizard.
Deleting devices
Auto-discovered devices can be deleted, if there are no auto-discovered monitor
instances under the devices. You can delete one or many devices at a time from the
Administration Console or through executing CLI commands.
Note
You cannot delete devices that are published from the BMC Atrium CMDB.
To delete a single device

1 In the Administration Console, expand the Devices folder.
2 Expand the device type folder, and select the device that you want to delete.
3 Right-click the device and select Delete.
4 In the Confirm Deletion window, click OK to delete the device.
After a pause, the window closes and a beep signals deletion. To confirm that the
delete operation was successful, close and then expand the Devices folder and
verify that the device is no longer listed.
To delete multiple devices

1 Expand the Device folder and continue to expand the folders to display the
devices.
2 Select one or more devices (use shift key to select multiple devices).
3 Right-click on the open space of the screen and click Delete.

4 Click OK on the confirmation message. BMC ProactiveNet deletes the selected
device and returns to Administration Console screen.
To return to Administration Console without deleting the selected device, click
Cancel.

The easiest way to develop a template is to start with an existing device. For
example, if you have a cluster of 10 systems that you want to provision for
monitoring, add one of the systems using the Administration Console, and then
create a template to add the other nine.
You can create a template in the Administration Console or from the command line.
Note
The Create Template command is not supported for Resource Pool Monitors and
Abnormality Index Monitors.
To create a template using the Administration Console

1 In the Administration Console, drill down to an instance of a device in the Device
folder.
2 Right-click on the device and select Create Template.
The Create Template window is displayed.
3 In the Create Template window, specify a name for the template.

4 If you want the template to save control parameters such as collect data, stats poll
interval, stats timeout, and so on, select the Preserve control attributes option.
5 Select or clear the existing monitors of the device.
6 Click Add to create a template with the selected options.
Note
In the Administration Console, the Templates folder does not update
automatically when you add or delete templates. You must close and then
reopen the Templates folder to reflect changes.
Templates can capture absolute instance thresholds and line graphs.

Autosync-created devices, groups, and monitor instances are not part of the
template.
To create a template using the command line interface

1 Run the following command:
pw template add templateName -d device
Use -savecontrol to save control parameters in the template.
In general, you should not save control attributes to a template. Usually you want
the same control parameters for all instances of a monitor, but you can control the
global defaults by editing the monitor defaults. If you save the control parameters
to the template, and then later change the monitor defaults, the monitors created
with the template will retain the old value because the template takes precedence
over the monitor defaults. So, set control parameters in the template only if it is
important that these monitors have specific individual settings. For more
information, see the BMC ProactiveNet Command Line Interface Reference Manual.
2 Verify that the template exists.
The template created can be found on the computer that hosts the BMC
ProactiveNet Server at /usr/pronto/usr_config/templates/ templateName.
Note
The Create Template command does not duplicate or capture line graphs and
absolute instance thresholds for auto-created SNMP objects like Interface and
DLCI. However, these details are captured for custom SNMP monitors that you
create by using the Monitor Wizard.

Templates enable you to create devices quickly or add a set of monitors to many
devices using a single blueprint. You can replicate and save the definition of every
monitor on the device, which is useful when you want to create the same monitors
on different devices. Using templates means you do not have to re-create the
monitors every time you want to add them to a different device. You save the
templates for later use or edit them as necessary. This significantly streamlines and
automates the administration process.
Also, if you have a cluster of servers and you want to monitor each with the same set
of monitors, you can create one template to provision all of the systems. You can use
the template repeatedly to provision new servers that are added to the cluster. For
example, you have a series of URLs to monitor and the URLs are identical except for
the host name. If you want to keep the control parameters the same for all the URLs,
you can create a template for this URL by using a macro for the hostname portion of
the URL, example, http://$(HOST)/search.jsp?keyword=java.
For more information about creating templates and using macros, see the BMC
ProactiveNet Command Line Interface Reference Manual.
To add a device from a template

1 Launch the Administration Console.
2 Right-click the Device folder, and select Add From Template => Samples.
3 Select one of the sample templates.
4 Enter the required information in the Configuration tab
Device Type - Select a device type from one of the ten categories in the list.
Device Name - Specify the name of the device. If the device name is a DNS
name, then the device name will be filled in automatically if it has not already
been set. This may take a few moments.
Note
Ensure that you do not use any special characters, such as /, in the device
name. If the device name includes special characters, then you cannot see the
monitors for the device when you click on the device name in the Grid view of
the BMC ProactiveNet Operations Console.
DNS / IP Address - Enter the device's IP address. The address 127.0.0.1 is the
loopback address for any computer and should not be added to the Device List.
If the device IP has a DNS name, then the device name will be filled in
automatically if it has not already been set.
Tag - Select a descriptive tag about the device that you are creating. Click the
plus icon
to display the Enter Tag Details dialog box, where you can
select the Tag Class as None, Location, Building, Department, or Owner, and
enter a Tag Value. For example, if the device that you are creating is located in
a particular city, you would select Location as the Tag Class and then specify
the city where the device is located as the Tag Value. Click Add to enter the
values that you specify, and then click Finish to return to the Add Device
dialog box.
Aliases - Add one or more aliases to the device that you are creating. Use
device aliases to associate events to the device, so that remote actions can be
performed on those associated events. For details about remote actions, see
Configuring and using Remote Actions/Diagnostics on page 355.
Secondary IPs - View any secondary IP addresses associated with the device
that you are creating, if that device has multiple IP addresses. The first IP
address that is associated with the Device Name that you specify is used as the
primary IP address. Any additional IP addresses are used as secondary IP
addresses. If no secondary IP addresses exist, then N.A is displayed in this
field. To view all secondary IP addresses, click on the ellipses button.
Note
Only devices that are synchronized with the BMC Atrium CMDB display
secondary IP addresses. Manually created devices will not display secondary
IP addresses even if multiple IP addresses exist for that device.
Device Description - Enter a description about the device that you are creating.
Agent Installed on Device - Select this option if you have installed a BMC
ProactiveNet Agent on this device. Some monitors require that an agent be

installed on the target device.
5 Click the Control tab to edit the control attributes.

Information in the Control tab tells BMC ProactiveNet about the desired data
collection and polling frequencies for the device. You can accept the defaults or
change them as required.
SNMP Data Collection - Select this option to enable BMC ProactiveNet Server
to collect data for the entire device. If this option is not selected, data collection
for the device stops (or for new devices, never starts). This flag lets you set up
monitors for devices that may not yet be online. Or, you can conduct
maintenance on existing devices without generating events.
SNMP Read Community String - Community string acts as a password for
BMC ProactiveNet Server access to the device MIB. To change this entry, you
must have prior knowledge of how this device is set up. For example, if this
device is set up for the Community String 'snmpget', then enter snmpget.
Default is 'public'.
SNMP Retries - Specifies how many times (count) BMC ProactiveNet Server
must request data from the device before reporting an event. Default is 2 retries.
SNMP Timeout - Specifies how long (seconds) BMC ProactiveNet Server must
wait for data from the device before reporting an event. Default is 2 seconds.
SNMP Use V2 - Select this option if the device is using version 2 of the protocol.
6 Click the Group tab and enter the required information.

The Group tab enables you to add a device and its monitors to one or more
groups. Optionally, you may associate the device with a group. A group is used
to logically organize devices and monitors by department, geographic area, or
service. Assigning a device to a group can also allow the system administrator to
restrict or allow access to certain devices by group. If you want the device to be
associated with a group, select the group name here.
7 Click Next.
8 Click Finish.
A summary panel is displayed.

You can apply a template to an existing device to add a set of monitors using a single
blueprint.
To apply a template to a device

1 In the Administration Console, expand the Device folder and continue to expand
the folders to display the device to which you want to apply a template.
2 Select the device, right-click, and select Apply Template.
You can apply a sample template or a user-created template.
3 Select the template to apply.
If the device does not have all the parameters required for this template, you
must enter certain parameters. See Adding a device from a template on page 90
for input information.
If the device has all parameters required for the template, the Apply Template
samp test window is displayed as shown in Figure 9 on page 94:
Figure 9: Select/Clear monitors
4 Select or clear the options as needed.

5 Click Next.
6 Click Finish.
If a particular device does not have an agent with respect to the template, you
must enter agent information. See Adding Agents on page 37.
Warning message
If a template specific to an operating system is applied to another operating system,
the following warning message is displayed:
Figure 10: Error Message displayed when the wrong template is applied

You can apply a template to more than one device at a time.
To apply a template to multiple devices

1 In the Administration Console, expand the Device folder and continue to expand
the folders to display the devices to which you want to apply a template.
2 Press the Shift key while selecting multiple devices.
3 Right-click on the open space of the window and select Apply Template.
You can apply either a sample template or a template that you created.
4 Select the template to apply.
If the device does not have all the parameters required for this template, you
must enter certain parameters. See Adding a device from a template on page 90
for input information.
If the device has all parameters required for the template, the following
window appears:
Figure 11: Select/Clear monitors
5 Select or clear the options as needed.

6 Click Next.
7 Click Finish.
The Apply Template Summary window is displayed. This window shows all
the changes that you made to the devices.
8 Click Finish.
Editing an existing template

Perform the following steps to edit an existing template.
To edit an existing template

1 Right-click the template.
2 Click Edit.
3 On the Edit Template window, make required changes.
Note
Templates can capture absolute instance thresholds and line graphs. Threshold
values can also be edited.
4 Click Syntax Check to validate the syntax of the template.
In case of any errors in the syntax, BMC ProactiveNet displays an error message.
5 Click OK to return to the Edit window and correct the entry.

Figure 12: Syntax Check - Edit Template
6 After making all necessary changes and checking the syntax, click OK.
Deleting a Template
Perform the following steps to delete a template.
To delete a template,
1 Right-click the template to delete.
2 Click Delete.
3 In the Confirm Deletion window, click OK.

Monitors are associated to at least one device, and this feature will give you the
flexibility to change the device association from one device to another device.
This feature will be activated if more than one device is available in the server,
and the selected monitor is a ghost monitor.
If any of the selected monitors is not a ghost monitor, then this feature will not be
activated.
To change the device association of multiple monitors

1 Click Edit => Change Device Association.
2 The Select new device dialog box is displayed.
This dialog box lists all the devices supported by the selected monitors along
with a search utility. The search utility lists all the devices including the current
device.
3 Enter the initial letters of the name of the device that you want to search for in the
search box and click Go.
Selection will be set to the first matching device and that device will be
highlighted.
4 Click OK.
Domain name
5 In the Confirm Change Device Association dialog box, click OK.

The monitor is now associated with the selected device.
Note
When Device Association of monitor is changed, all open events or events for
those instances are closed. Any configured event actions will be executed.
Imported events associated with the Changed Device Association monitor
instance will be closed. If the error condition still continues, then a new event or
event is triggered after the duration defined in threshold.
Limitations
The closed event count is displayed incorrectly in the Device Matrix page. Device
Matrix page will include the closed events of the updated instance in the previous
parent device. The closed events of the updated monitor instances can be viewed
by clicking on the Closed Event Count of the new parent device.
For monitors with source agent in disconnected state, changing device association
is not applicable.
Domain name
The Domain Name feature enables you to truncate the domain name portion of
elements added to the Device folder.
For example, without this feature, adding two servers to the Device listing shows:
server1.mycompany.com
server2.mycompany.com
After entering the domain name mycompany.com using this feature, adding these
same two servers, the domain name is truncated and the Device listing shows:
server1
server2
This feature is not retroactive for existing devices. Listings entered before the use of
the domain name feature that already include mycompany.com remain unchanged.
Also, if you delete the domain name mycompany.com, the previously truncated
device listings remain truncated.
Domain name
Adding a domain name

There is only one Domain Name file; additional Domain Names files cannot be
created nor can the existing file be deleted. There are no Control attributes even
though the tab appears on the domain name window.
To create a domain name entry

1 Expand the Advanced Options and Domain Name folder.
2 Right-click the Domain Names file.
3 Select Edit.
The Edit Domain Name window is displayed.
4 In the Name field, specify the Domain Name you want to truncate.
5 Click Add.
The name appears in the Truncated Names box.
6 After adding each domain name you want to truncate to the Truncated Names
box, click Add.
7 When all names have been added, click OK. To stop the operation, click Cancel.
When you add any device using this Domain Name, the domain name portion is
automatically truncated.
Editing a domain name

You cannot edit a domain name that appears in the Truncated Names list. Instead,
you must first delete the Domain Name using the procedure described in the Delete
Domain Name topic, and then enter the Domain Name again using the Add Domain
Name procedure.
Deleting a domain name

If you want to modify the Domain Names entry, you must first delete the existing
name and then add the name again using the Add Domain Name procedure.
Port name
To delete a domain name

1 Expand the Advanced Options and Domain Names folder.
2 Right-click the Domain Names file.
3 Select Edit.
The Edit Domain Name window displays with a list of truncated names.
4 In the Truncated Names window, select the listings you want to delete.
5 Click Delete.
The names are removed from the list of truncated names.
6 Click OK.
Port name
Port Name (TCP Control Port) is used to add a Port Monitor to any device that
appears on the Device list.
Port Name entries are used to add and edit Device configurations. For more
information, see TCP Control Ports. The instructions assume that the Administration
Console is open.
Adding a port name

Perform the following procedure to add a port name.
To add a port name to a device

1 Expand the Advanced Options folder.
2 Right-click the Port Name folder.
3 Click Add Port Name.
The Add Port Name window is displayed.
4 In the Port Name field, specify a name for the port.
Port name
5 In the Port Number field, enter the port number.

For example, to monitor Agent port you would enter: Agent as the Port Name
and 12124 as the Port Number.
6 Click Next.
Note
The message 'failed to create port name' indicates that you have entered a Port
Number or Port Name already in use. If this occurs, click OK on the window,
change your settings, and try again.
The Summary of Created Monitors window is displayed.
7 Click Finish.
8 To view the new Port Name, expand (or close and expand) the Port Name folder.
The new port name now appears on the list.
Editing a port name

Perform the following procedure to edit a port name.
To edit a port name for a device

1 In the Administration Console, expand the Advanced Options and Port Name
folders.
2 Right-click the Port Name file to edit and select Edit.
The Edit Port Name window is displayed.
3 Change the Port Name as desired.
Note
You cannot edit the Port Number. To change the Port Number, you must delete
the Port Name file and then create it again using the desired Port Number.
4 Click OK.
Delete Port name

Perform the following procedure to delete a port name.
To delete a port name from a device

1 In the Administration Console, expand the Advanced Options and Port Name
folders.
2 Right-click the Port Name file to delete and select Delete.
The Confirm Deletion window is displayed.

To verify that the Port Name is deleted, close and then expand the Port Name
folder. The Port Name will no longer be listed under the Port Name folder.

Based on the device type that you selected in the Configuration tab, the system
automatically pre-selects some default monitors and the Monitor tab. For example,
for the Server device type, the NodePing monitor is pre-selected; if an agent is
installed on the device, System and TCP/IP and Agent Status Monitors are preselected, and the System tab is pre-selected. You can add additional monitors for the
applications and components installed on the device.
To choose monitors for a device

1 Select the monitors that you want to create for this device.
If the device has more than one application that needs monitoring (for example,
a server running Mail and IP services), select the applicable monitors using the
various tabs, or go back and add the monitors later.
2 Click Next.
The Creating Monitor window opens, followed by the configuration window
for each monitor that you selected.
The Configuration window contains specific entry fields, as shown in this

example. For further information see, Monitor Guide for detailed instructions
in setting the parameters for the monitors.
Each monitor also has a Control tab, which specifies the data collection and
polling frequency for individual Application, Intelliscope, or SNMP monitors.
Creating a group
And similar to the Configuration tab, the input fields in the Control tab vary
depending on the selected monitor.
Click Skip if you have selected several monitors to add and you change your
mind about one of them or you are uncertain about an entry field.
Clicking Skip moves on to the next monitors configuration. The skipped
monitor is not added. The program continues normally. When the last monitor
is configured, the Summary screen appears to show what was created.
3 Click Finish.
To view the new device listing, expand (or close and expand) the
corresponding device folder.
To view the new device listing, expand (or close and expand) the
corresponding device folder.
Use the ProxyAgent category for all dedicated computers used for monitoring.
The Source Agent list on the Creating Monitor window lists only the BMC
ProactiveNet Server, local agent, and agents running on the device under
ProxyAgent. To view other available agents, click More from the list for Source
Agents.
Creating a group
The Group category represents a collection of monitored resources that you define.
To make information easier to find and manage, groups corresponding to a variety
of real-world relationships (such as by city, a specific department, or the type of
resource, etc.) are set up. There is no limit on the number of groups you can define.
Groups can also provide a means of access control. As you set up user views,
reports, and events, you can filter access by using groups.
The Group function lets you select individual devices, applications, and interfaces
added to the BMC ProactiveNet database, and put them together into a single unit
(group) for management purposes.
Before creating a group, add all corresponding devices, interfaces, and applications
to the BMC ProactiveNet database, and complete at least one poll.
Avoid creating a single group with hundreds or thousands of monitors. Not only
does this reduce the usefulness of the group, it can also hamper the performance of
Probable Cause Analysis if the group is used as a filter. When creating a group that
encompasses a large number of monitors or devices, it is best to create it from
smaller groups that have real meaning in terms of function, dependency, or
topological relationships. For example, if you are grouping devices according to
network topology, BMC ProactiveNet recommends a maximum of 254, i.e., the
number of addresses in a length-24 class-C subnet.
Creating a group
Group checklist
Have the following information available before using the Group function:
A list of devices, applications, and/or interfaces to group
A unique name for the group and an informative description
To add a new group from the Add Group window

1 From the administration console, select the Group folder, right-click and select
Add Group.
2 In the Add Group window, in the Group Name field, specify a name (maximum
length of 60 characters; no spaces) for the group you want to create.
3 In the Group Description field, enter description of the group.
4 Select Group made by selected each Managed Object to create the new group.
5 Click Next.
The Add instances window is displayed.
6 Select the Monitored Resource in the left pane, and click Add to move it to the
right pane. Alternatively, use the Search for Devices field to search and select the
device.
You can add multiple Monitored Resources to a group, and if required, create a
group of aggregate monitors.
Similarly, click Remove to remove objects from the right pane.

7 Click Finish to add the group to the Administration Console.
If required, click Close to cancel the operation.
The newly added Group is now available under the Group folder.
Working with Dynamic Groups or Rule-based Groups

BMC ProactiveNet enables you to create dynamic groups or rule-based groups that
automatically update their content based on the given rule. A rule is a combination
of a pattern match on entity name, entity tag, and monitor-type filter. These groups
contain only monitor instances.
Creating a group
Assume that an organization has offices in three different locations Chicago, Perth,
and Copenhagen. Each office has two departments Planning and Procurement.
Scenario 1
Assume that you have multiple devices that have names based on the location of
each office. For example, assume that all devices in Perth have names starting with
"PERTH". You can create a group that consists of only those URL monitors that
belong to the Perth office. With rule-based groups, you can create a rule with the
name pattern match PERTH.* on devices and a monitor-type filter for all URL
monitors. BMC ProactiveNet consolidates all the URL monitor instances that match
PERTH.* in one dynamic group. When new instances are added or existing
instances are removed from the device, they are also added or removed from the
dynamic group.
Scenario 2
Assume that you have some devices that are dedicated to the Planning department
in all the 3 locations. Let us assume the devices are tagged as dept=planning. To
create a dynamic group that contains entities that are used by planning department,
you can attach the tag pattern match dept.*planning on devices. BMC ProactiveNet
consolidates all the instances associated with the devices with matching tag in the
group.
Note that the name and tag pattern match work independently. If you have a device
whose name does not match the name pattern string but has a matching tag, BMC
ProactiveNet includes all those monitor instances in the dynamic group.
Applying rules to Dynamic Groups

You can use a regular expression to apply a rule to a group. BMC ProactiveNet uses
a regular expression as pattern match on group, device, instance name, and tag. The
name pattern match can be applied to only of the chosen entities - group, device, or
monitor instance.
Tag pattern match is applied to the tag string. You can also specify a selected list of
monitor types or you can choose to add all instances irrespective of the monitor type
filter.
Pattern match on entity name

If your entity is a group and name regex pattern matches a group name, BMC
ProactiveNet considers all instances for that group.
Creating a group
If your entity is a device and name regex pattern matches a device name, BMC
ProactiveNet considers all instances for that device.
If your entity is a monitor instance and name regex pattern matches an instance
name, BMC ProactiveNet considers all instances whose names match that pattern.
Pattern match on tag

You can tag entities with meaningful information such as location, owner,
department, and so on.
If your entity is a group and tag regex pattern matches a group tag, BMC
ProactiveNet considers all the instances in that group.
If the chosen entity is device and tag regex pattern matches a device tag, BMC
ProactiveNet considers all that instances associated to that device.
If your entity is a monitor instance and tag regex pattern matches an instance
name, BMC ProactiveNet considers all instances whose tag match that pattern.
Monitor-type filter
All instances that result from the above pattern match are then checked for the
monitor-type filter.
If you choose a set of monitor types, BMC ProactiveNet considers only those
instances whose monitor type matches the selected types and discards the rest.
Every instance has a monitor type.
If you do not specify monitor type, BMC ProactiveNet considers all the instances.
Defining Group display

You can choose to display group names in the following two ways:
Flat - Select this to display groups created on the server in a fixed and flat manner.
By default, this option is selected.
Hierarchical - Select this to display groups in a classified manner.
Group made by existing groups

Groups can also be created by grouping existing groups. The groups attached to the
main group, in this case, are child groups.
Creating a group
To create a new Group with the existing groups

1 From the Administration Console, select the Group folder, right-click and select
Add Group.
2 In the Add Group window in the Group Name field, specify a name (maximum
length of 60 characters; no spaces) for the new group.
3 In the Group Description field, specify a description for the group.
4 Select Group made by grouping existing groups option to create a subgroup of
existing groups.
5 Click Next.
6 In the Select Group dialog box, select the groups to be added from the list of
existing groups and click Add.
Group made by specifying rules

Groups can also be created by specifying rules; these groups are known as rule
based groups. Rule based groups are dynamic groups.
To create a new Group by specifying rules

1 From the Administration Console, select the Group folder, right-click and select
Add Group.
2 In the Add Group window in the Group Name field, specify a name (maximum
length of 60 characters; no spaces) for the new group.
3 In the Group Description field, specify a description for the group.
4 Select Group made by specifying rules.
5 Click Next. The Select Group window is displayed.
6 Select the Group Name, Device Name, or Monitor Instance Name.
7 Specify the Pattern Match. Instances which belong to any of the matching group
name, device name or monitor instance name are automatically included as the
members of this group. This supports all Java Regular Expression pattern match.
Adding Child Groups
8 Select the Monitor Types that need to be associated to the group. Select All to
include all the monitor types, or select Selected to associate the selected monitor
types.
9 Click Add or Remove to add or remove the selected monitor types.
10 Click Show Members to display the list of monitor types that match the pattern.
11 Click Finish. The rule based group is created and listed under the group folder.
12 Click Close to return back to the Administration Console without creating the
group.
Adding Child Groups

You can use the Administration Console to add child groups to the groups that you
create.
To add a new child group to the selected group

1 From the Administration Console, expand the Group folder, right-click on a
group, and select Add Child Group.
2 In the Add Child Group dialog box, complete the screen options.
Group Name Specify a name (maximum length of 60 characters; no spaces)
for the new group.
Tag - Specify tag value to search or group the objects. You can enter multiple
name-value pairs, text, or include both (name-value pair and text). This gives
you the option to group objects in different forms. Click icon + to select a
default tag class. The Enter Tag Details screen opens. Select Tag Class from the
list and enter a tag value, click Add to append tag class and value. Click Finish.
Note
The tag specified by you is not considered as a default class. You cannot enter
special characters &"/<>' in the tag field.
Editing Tag Value on Enter Tag Details screen. Select a tag value and click edit.
Make the necessary modifications in Tag Value text box and click Set to add the
changes.
Deleting a Tag Value on Enter Tag Details screen. Select a tag value and click
Delete, dialog box is displayed with the options Yes or No. click Yes to delete
the tag value.
Adding Child Groups
Group Description Specify a meaningful description for the group. This
description will be displayed in the group matrix screen, when you bring the
mouse over the group name.
Group made by selecting Managed Objects and grouping existing groups -
Select this option to create a new group.
3 Click Next.
The Monitored Resources/Group Members window is displayed.
4 Select the Monitored Resource in the left panel, and click Add to move it to the
right panel. Alternatively, use the Search for Devices field to search and select the
device. You can add multiple Monitored Resources to a group, and if required,
create a group of aggregate monitors.
Similarly, click Remove to remove objects from the right panel.
5 Click Next.
The Add Group screen is displayed.
6 Click Add.
The Group Chooser window is displayed.
7 Select the groups to be added from the list of existing groups.
Note
Refer Search Groups for information on how to locate groups.

Click Parent Group to add the group being created to the existing parent group(s).
Click Add New, only if you need to create a new parent group.
After adding resources to the group, click the appropriate action button.
Note
For details about creating Resource Pool monitors, see Resource Pool on page 132.
The newly added Group is now available under the Group folder.
Editing Groups
Editing Groups
Perform the following steps to edit groups.
To edit an existing group,

1 Right-click the Group and click Edit Group.
2 In the Edit Group dialog box, make required changes, and click Finish.
BMC ProactiveNet updates the group information in its database. Alternatively,
click Close to cancel the operation.
Deleting Groups
Perform the following steps to delete groups.
To delete a group
1 Right-click the Group and click Delete.
The Confirm Deletion window is displayed.
2 Click OK.
Note
When a group is deleted, BMC ProactiveNet does not update all event rules that
refer to the group. Although the Edit Event Rules screen does not show the
associated group, the database entry corresponding to the event rule still records
reference to the deleted group. Such events rules are invalid and do not work.
To correct the event rules, open the edit screen and save the event rule again to
wipe out reference to the deleted group.
Deleting Groups
4
Managing monitors
BMC ProactiveNet monitors
BMC ProactiveNet hosts an extensive set of out-of-the-box monitors that collect
performance data from an extensive suite of applications, databases, middleware,
firewalls, servers, network devices, and load balancers.
For details, see the BMC ProactiveNet Monitor Guide.

From the Administration Console, you can view all monitors added to the local
system by category and further organized by type. You can edit or delete existing
monitors, as well as create new monitors using monitor templates. You can also add
or delete Key Performance Indicator (KPI) attributes for each monitor type.
To edit a monitor instance

1 In the Administration Console, from the Administration tab, select the General
Administration subtab.
2 Expand the Monitors folder and select the monitor instance that you want to edit.
The Edit Monitor Type window is displayed.
3 On the Configuration tab, make any required changes.
4 On the Control tab, make any required changes.
5 On the Group tab, change the group assignment of the monitor, as required.
Chapter 4 Managing monitors 113
This enables you to add monitors to one or more groups. Optionally, you may
associate the monitor with a group. A group is used to logically organize
monitors by department, geographic area, or service. Assigning a monitor to a
group also enables the system administrator to restrict or allow access to certain
monitors by group. If you want the monitor to be associated with a group, select
the group name here.
6 Click OK to save the edits and close the Edit Monitor Type window.
To delete a monitor instance

2 Expand the Monitors folder and right-click the monitor that you want to delete.
3 Click Delete.
BMC ProactiveNet displays the Confirm Deletion window.
The monitor instance is deleted.
To add or remove Key Performance Indicator (KPI) attributes for a monitor type
2 In the Administration Console, select the General Administration tab and rightclick the monitor to delete.
3 From the menu bar, choose Tools=>KPI Administration.
BMC ProactiveNet displays the Confirm Deletion window.
The KPI Administration dialog box is displayed.
4 From the Monitor Type list, choose the monitor type for which you want to add
or remove KPI attributes.
A list of attributes for the selected monitor type is displayed.
5 In the KPI column for the attributes that you want to add or remove as Key
Performance Indicators:
select the KPI check box to add the corresponding attribute as a KPI
Monitor Wizard
deselect the KPI check box to remove the corresponding attribute from the KPIs
for that monitor type
Monitor Wizard
BMC ProactiveNet Monitor Wizard is a powerful interface that enables
administrators to create custom monitors with variable number of attributes.
The monitors that can be added include:
Script-based monitors
Resource Pool monitors
SNMP monitors
JMXTM Monitors
SQL Query monitors
Windows Management Instrumentation Monitors
Windows performance Counter monitors
Once the monitor is created and monitor instances are established, data is fed into
the BMC ProactiveNet where it establishes a baseline for analysis, reporting,
graphing, and troubleshooting. The new data can be combined with other
information in the system to find problems on the objects being monitored.
When you use the Monitor Wizard, you define a new 'service monitor' and add it to
the BMC ProactiveNet. A service monitor is an entity that gathers important data
from a device, application, or service for the purpose of monitoring mission-critical
business parameters. These monitors do not contain any default Absolute or
Signature thresholds. You can set them using the Operations Console.
Script monitors
Script Monitors integrate business-specific monitoring scripts with BMC
ProactiveNet. This enables presentation of business data alongside performance
data. For example, you could see the relationship between the number of orders
entered per hour and the response time experienced by the order entry group. These
monitors can be either legacy or newly written executable scripts that pull critical
Script monitors
data from network devices, servers, or any data source where performance data is
deemed to be important.
BMC ProactiveNet Monitor Wizard is ideally suited for creating such script monitors.
Add Script monitors

There are five steps needed to create a new script-based service monitor.
Step 1: Define the Script

Note
It is beyond the scope of this manual to document programming practices. Contact
your System Administrator if you need help creating the program/script.
The script can be any existing or new executable or script (shell or perl) that can read
'Command Line Arguments' and write to a standard output in the form of
'Variable=value'. A script and the program it calls can contain up to 30 input
parameters and 30 output variables. This enables more flexibility in defining multifunction service monitors.
BMC ProactiveNet invokes the script in the following format:
Script -[config|stat|create|delete] <ip_address> <timeout_seconds>
<input_param1>... <input_paramN>
Note
If the script is running on Linux OS and ksh is used as the programming language,
then signal 15 should be processed in the script, in case the timeout Agent terminates.
Arguments in the script should be the following:
First argument: -config, -stat, -create, or -delete.
Second argument: IP address of the target device or application.
Third argument: Timeout value for the script to return output values.
The Script should use this timeout value and ensure script execution finishes within
the timeout seconds. It is the responsibility of the script to kill hanging commands
spawned by it and that do not finish within the timeout seconds.
Script monitors
Following these arguments could be any number of the input parameters. The
output must use the following format, each variable on a separate line:
output_var1=value
output_var2=value
output_varX=value
Note that names of all input and output parameters should be the same as defined in
the registration process explained in later sections. Output variable values are
returned on the standard output device (stdout).
There are two types of polls in the BMC ProactiveNet. Depending on the type of
poll, the first argument passed to the script program is either '-config' or '-stat'.
Config Poll gathers configuration information, such as version of the application
running. By default, the configuration poll is scheduled once a day. Configuration

data is not plotted as data in graphs, rather, it is used for label and descriptive
information. Config polls accept any type of data.
Stat Poll gathers information for which the user wants to graph, report, and
receive alerts. By default, the Stat poll is scheduled at 15 minutes interval.
Create can be used to display errors while creating a monitor.

Delete can be used to do the cleanup, if needed, when deleting monitors (i.e.,
temporary working files, etc.)
If the output value is 'NO_DATA' (for numeric value), BMC ProactiveNet does not
plot a data point in the graph, and no event is triggered.
Note
Monitor Wizard currently limits user-defined scripts data in the range -2147483648
to 2147483647 (integer) and -2147483.648 to 2147483.647 (floating point). The
workaround for collecting data that exceeds this limitation is to scale the program
output downward and collect it in the appropriate unit (i.e., collect file size in MB
instead of Bytes).
Poll rates for both Config and Stat polls may be modified via the Administration
Console by editing the service monitors instance Control tab.
Monitors should have an Availability attribute only when it can be clearly identified
that the monitor can be polled. For example, if a Process Monitor is created when the
process is running, it can be polled. Other examples include file system monitor or
disk monitor.
For batch or shell-script files, ensure that all necessary environment variables are
specified and that execution paths are explicitly defined. For UNIX scripts, ensure
that the proper shell is specified at the beginning of the script. If the Service Monitor
Script monitors
program depends on certain variables (such as library and execution paths), then
they must be defined in a wrapper script that specifies a shell and defines the
variables before invoking the program. This is necessary because the Service Monitor
program does not inherit any environment when it is executed by the BMC
ProactiveNet Agent.
Explanatory text and other extraneous output from the script will not interfere with
data collection. If an output line does not begin with the name of a registered output
variable, it is ignored.
The Script can contain optional input parameters. While registering the script using
the Monitor Wizard, an input parameter can be indicated as optional by not selecting
the Required Field check box. Similarly, an input parameter can be indicated as
mandatory by selecting the Required Field check box.
Step 2: Integrate the script into BMC ProactiveNet

Once you have defined the program/script, you need to transfer the program/script
and its dependencies to BMC ProactiveNet. If used with BMC ProactiveNet Agents,
transfer the script and its dependencies to the remote computer where the BMC
ProactiveNet Agent is installed.
Click Transfer in Monitor Definition Script Create screen, to transfer, no need to
define script if you use this option.
For instructions about transferring the script, see Transfering files to agents on page
206.
The program/script (and any dependencies) should be placed in the following
designated directory on BMC ProactiveNet Server and its BMC ProactiveNet Agent,
if necessary creating the directory:
UNIX: /usr/pw/pronto/usr_apps/bin
Windows: C:/Program Files/Agent/pronto/usr_apps/bin
Once placed in this directory, information will not be overwritten whenever you
upgrade BMC ProactiveNet.
1 Log on to BMC ProactiveNet Server as 'root'.
2 Copy the program/script and any dependencies into the /usr/pw/pronto/usr_apps/
bin directory. If directory does not exist, create it.
3 Enter the chmod command for the script: chmod =x <script_file>.
4 Log out of the system.
Script monitors
Step 3: Register the New Script monitor

After integrating the script into BMC ProactiveNet, use the Administration Console
to register the new script monitor. This registration process enables the
administrator to define the name, input, and output of the new service monitor, as
well as define default values and other important parameters. The new service
monitor can then be activated to monitor any applicable device, application, or
server in the network. The following information must be specified by the
administrator registering the new service monitor.
Complete this procedure to register a Service Monitor. This procedure uses the
example numberusers.sh as the script file. Example of a script file, Monitor Wizard
Script Example, is provided in this section.
1 Open the command line interface and enter the following commands:
cd /usr/pw/pronto/usr_apps/bin
ls
Verify the numberusers.sh script file is listed.

chmod 555 numberusers.sh
pw admin
2 Log on to the Administration Console using your logon name and password.
3 From the Tools Menu, navigate to Tools => Monitor Wizard => Script.
The Monitor Wizard window is displayed and existing monitors (if any) are listed.
4 Click Add to display the Monitor Definition screen.
a For this example, enter Number of Users. Maximum of 20 characters, with no
blank input or illegal characters, such as / &/ * ><!\.
b In the Filename of Executable for the Monitor field, specify numberusers.sh.
Again, no illegal characters are allowed.
c Monitor Category
Choose the BMC ProactiveNet category that you want this new monitor to be
displayed under in the Administration Console. Alternatively, click New to create a
new monitor subcategory that will be displayed under the Other category in the
Administration Console. Refer New Monitor Subcategory topic for more information
on this.
1 Requires RemoteAgent check box
This option should be selected when the script collects information about the
computer on which the script runs. When this option is selected, 'Source Agent' is
Script monitors
hidden and defaults to the IP address of the device under which you create the
monitor instance.
Select SunTMOS option for 'OS Platforms Supported'. In this example,
numberusers.sh script supports only SunOS.
Select all OS options supported by the script you are integrating.
1 Do not select Record More Info option.
Select Record more info option, if your script outputs any errors using Attribute
name=Error:Error text". In this example, numberusers.sh script does not support
returning any error information.
1 In the Input Parameters tab, leave Name and Default Value fields blank.
You should define input parameters expected by your script here. These are passed
on command line to script whenever script is executed. You can give a default value,
which will appear as default while creating instances for this monitor. The script
Script monitors
numberusers.sh does not expect any input parameters and therefore it is left blank
here.
Figure 13: Monitor Definition
1 Click Output Configuration Variables tab.

a In the Name field, specify INFO (upper case).
b From the Type list, select String. Note that the Unit field is inactivated.
Script monitors
Note
Only the first 254 characters of an Output Configuration attribute are
displayed in the Administration and Operations Consoles. To display the
attribute fully, limit the length of the attribute to less than 254 characters.
Figure 14: Output Configuration Variables
2 Click Output Statistics Variables tab.

Figure 15: Output Statistics Variables
Script monitors
a In the Name field, specify USERS (upper case).
Note
While creating script monitor, data availability is added by default and

cannot be edited. To define other stats attributes, you must enter a different
name other than Data Availability else monitor will not be created.
b From the Type list, select Integer.
c Select the unit from the list. You can also specify the units. After creating the
monitor the newly specified unit will be available in the list, for other monitor
types also. Ensure that none of the below-mentioned string or characters are
given while defining a new unit:
$$ * + , ; ^ & " < > '
Note
If None is selected as the unit of measurement of an attribute, then the attribute
does not display any unit of measurement on the Show Graph page in the
Operations Console.
7.1 SP4 Onwards, the new stats attribute Data Availability is introduced, which
notifies users about being unsuccessful in getting data from the script. Data
availability is 100% if script executes successfully else data availability is 0%.
1 From the list, select the Measure As value.
Type of computation on the result data. Supported computation types include:

DELTA: Value recorded will be (Value in Current Poll - Value in Previous Poll).
RATE: Value recorded will be [(Value in Current Poll - Value in Previous poll)/
Duration].
RAW: Value recorded will be the same data as retrieved from the source of data.
If you specify DELTA or RATE as the Measure As value and data is being
provided by a counter or any other monotonically increasing data source, then the
script must be able to detect a rollover or reset condition of the data source and
output NO_DATA.
1 Select KPI to indicate the key attributes.
KPI enables ranking key performance attributes. On selecting KPI, graph by
default option is also selected to display the graph in the Operations Console.
The selected attribute is displayed by default when a graph is generated. For
non selected attributes ranking is not set.
Script monitors
2 Graph Default - At least one attribute must be selected. Attributes selected are
displayed by default when a graph is generated. If none is selected, an error is
displayed when you attempt to create the monitor. Attributes not selected here
will still be displayed in the Custom Graph area on the Operations Console, but
will need to be manually selected on the graphing page.
3 Do not select the Normal Distribution option.
It is important to understand the significance of this setting since it impacts
how condensed data, baseline data, and report data are actually calculated.
(Baseline data and report data are derived from the condensed hourly
samples). How Normal Distribution is set determines how raw data points are
converted into condensed hourly samples.
Hourly samples are made up of a max value, avg value, and min value for that
hour. When Normal Distribution is selected, the highest data point for that
hour is taken as the maximum value, the average value is the true average of all
points, and the lowest data point is taken as the minimum value.
If Normal Distribution is NOT selected, then the maximum value is derived
only after neglecting the top 10% of data points, the average value is taken from
the median value, and the minimum value is derived after neglecting the
bottom 10% of data points.
Examples of attributes with Normal Distribution=true are: Availability, Total
CPU, FileSize. For these attributes you do NOT want to discard any values
when converting to hourly samples. Instead, you want the absolute high and
absolute low recorded.
Examples of attributes with Normal Distribution=false are: Ping Response
Time and WebURLResponseTime.
The reason is that response time measurements typically have a few
fluctuations that are way outside the normal range and skew the hourly
calculations if included. Instead the extremes at the upper and lower end are
discarded.
4 Click OK.
a You will receive the following message. Click OK.
The Monitor Wizard window now displays the Application Monitor 'Number of
Users'.
1 Close the Monitor Wizard window.
You are now ready to add instances to this monitor.
Step 4: Activate the New Script monitor

Once a new service monitor is created and registered on the BMC ProactiveNet, it is
activated via the BMC ProactiveNet Administration Console and you are ready to
add monitor instances. The new service monitor will appear in the same menu as
other BMC ProactiveNet service monitors listed under the Other category. This
Script monitors
monitor can be activated or inactivated via the Administration Console on any of the
applicable resources in the system.
Complete the steps given below to add an instance to the new monitor using the
Device folder.
Note
If the device already exists, go to step 5.

1 Right-click the Device folder on the Administration Console and click Add Device
(or right-click the device of interest, if already present).
The Add Device screen is displayed. From this screen, using the new service
monitor you can configure an instance for a device or application.
2 From the Device Type list, select Server.
3 In the IP Address field, enter the IP address of your BMC ProactiveNet Server.
4 Click Next.
The Add Device - Select Monitors to Create window is displayed.
5 On the Add Device - Select Monitors to Create window, click Other and select
Number of Users.
You can also choose to add additional monitors. If necessary, you can also cancel
these monitors later using Skip button. The monitor will be available on the panel
as per the Monitor Category selected in the monitor wizard while creating the
monitor type.
6 Click Next. This gives you access to the configuration and control tabs.
7 On the Configuration tab, specify an instance name.
8 If required, modify the default values on the Control tab.
Skip: If you selected several monitors from the Select Monitors to Create
window, or there are default monitors associated with the device, this option
enables you to ignore monitors you do not want added and automatically
moves to the next part of the configuration process.
Add: Click this button to add the monitor instance listed at the top of the
screen, and then continue to use add as needed.
Next: Click this button if there is only one monitor instance to add.
Script monitors
Finish: Click this option at the beginning of the process to automatically add all
monitor instances selected and create instance names for them. This also closes
the Monitor Wizard.
9 Click Finish.
10 Click Done in the Summary of Created Monitors window.
11 Refresh the Device folder to show the new Service Monitor Instance called
'Number of Users'.
Step 5: Test the Script monitor

Complete the procedure given below to test a Service Monitor:
1 Open the Operations Console and click Custom Graphs.
2 Select a Group Filter (if any)
3 Select the Monitor Type 'Number of users'.
4 Click Next to open the Monitor Instance section
5 Select the instance to be graphed.
Figure 16: Custom graph
Script monitors
6 Click Apply to open the Create Graph screen.

7 Make your selections and then click Generate Graph.
The Number of Users 'USERS' graph is displayed.
Note
The number of Stats attributes per monitor type is limited to 50 and number of
Config attributes allowed is limited to 30, and the total number of attributes
(inclusive of both Stats and Config) is limited to 80. A maximum of 30 input
variables per monitor type is allowed.
Edit Script monitors

The power of the Monitor Wizard is its ability to include customer-defined metrics,
or even business metrics obtained from other sources.
Once a Service Monitor has been created, editing it is quite simple.
To edit a script monitor

1 From the Tools Menu, select the monitor class you want to edit.
2 Select the monitor you want to edit and click Edit.
3 Make necessary changes and click OK.
Note
Refer Register the New Service Monitor section for details.

BMC ProactiveNet updates the monitor and registers the changes.
Warning message
If you have not performed the previous step of creating the script monitor, you will
receive a warning message.
Delete Script monitors

Follow the steps given below to delete a Registered Service Monitor.
Script monitors
To delete a script monitor

1 From the Tools Menu, select the monitor class you want to delete.
2 Select the monitor you want to delete and click Delete.
3 On the Delete Confirmation window, click OK to confirm that you want to delete
the monitor.
BMC ProactiveNet deletes all the instances of that monitor type.
Note
If for some reason the jserver is restarted while deleting a Script Monitor, the
Delete operation may not be executed properly.
Monitor Wizard script example

An example script called 'sampleMetaAPI' is provided in the following directory:
/usr/pw/pronto/examples/MetaAPI
sampleMetaAPI script:
#!/bin/csh -e
if ($#argv != 4) then
echo "Usage:sampleMetaAPI -[config|stat|create|delete] [ip] [timeout]
[userName]"
exit 1
endif
if ("$1" == "-stat") then
set Number = `ps -u$4 | wc -l
`
set ActNum = 0
if ($Number > 1) then
@ ActNum = $Number - 1
endif
echo "NO_OF_PROCESSES=$ActNum
"
exit 0
endif
if ("$1" == "-config") then
echo "INFO = ùname -a
`"
exit 0
endif
Description of sampleMetaAPI script

This example script is available only for UNIX agents and not for Windows agents.
The example script accepts userId as an input parameter and returns the number of
processes belonging to the given user.
Script monitors
To define a service monitor using this example script, refer 'Define a new Service
Monitor' section.
Copy the script and place it in the /usr/pw/pronto/usr_apps/bin directory.
While registering this example script as a new Service Monitor
1 Define an Output Statistics Variable as follows:
a Specify NO_OF_PROCESSES (uppercase) as the name.
b Select Integer as the Type and None for Unit.
2 Define an Output Configuration Variable as follows:
a Specify INFO (uppercase) as the Name.
b Select String as Type.
3 Define an Input Parameter as follows:
a Specify USER as Name.
b Select the Required Field check box.
c Enter a default value (optional).
Creating a more info link for the script monitor

Information from the Monitor Wizard can be made to appear in the 'More Info'
screen that can be accessed from the graphs of BMC ProactiveNet.
The More Info link is used primarily for error reporting. If an error occurs during a
Stats poll, the error can be recorded in the database by using the following syntax in
the custom script:
ATTRIBUTE NAME=ERROR Error String
For example, if the shell script reads:

echo NO_OF_USERS=ERROR Not able to retrieve the information
Then, the message Not able to retrieve the information is logged into the
system.
Script monitors
If your Service Monitor script writes anything starting with ERROR: it can be made
available as 'More Info' text. You can have as many lines as you want; each separate
line needs to precede with the xxx=ERROR syntax as shown above.
Reserved attributes and words for the script monitor

Reserved attribute names appear to the left of the '=' sign in the output:
Data Availability - The only values allowed for this attribute in stats data are 0 or
100
Reserved words in data appear to the right of the '=' sign in the output:
NO_DATA - Results in nothing being plotted, i.e., a data gap
NO_RESPONSE - Results in a dashed line being plotted
ERROR followed by text - Results in text being stored as 'More Info'
If DATA AVAILABILITY returns a value of 0, all other attributes are
automatically assigned a value of NO_RESPONSE, regardless of what is actually

output by the user's Service Monitor program.
If a particular output statistics variable does not appear on a poll, its value
defaults to 0 (integer or floating-point). Values of NO_RESPONSE or NO_DATA

must be supplied explicitly by the program/script if they are to be plotted as such.
If a particular statistics variable outputs more than one value on a poll, only the
last value will be stored.
Bundle a script to be distributed to Remote Agents

1 On BMC ProactiveNet Server computer, create a temporary directory. For
example: /tmp/workdir
2 In /tmp/workdir, create pronto/usr_apps/bin by running the following command:
mkdir -p pronto/usr_apps/bin
3 Copy the script to be distributed into the /tmp/workdir/pronto/usr_apps/bin
directory.
Script monitors
4 Create ProactiveNet.mf file that contains the following entries:

Version: 1.0
Name: Broadcast script
Type: Agent
Path: .
Build: 225
Desc: Push scripts to agents
OS: Linux:SunOS:HP-UX:AIX:SunOS x86:Windows
Date: 1126776391141
Mode: pronto/usr_apps/bin/<Name of the Executable>:755
Vendor: BMC ProactiveNet, Inc.
AgentVersion: 6.0
MinVersion: 6.0
MinBuild: 225
5 Create a jar file for install_package by running the following command in /tmp/
wordir:
/usr/pw/jre/bin/jar cvf Name of the bundle.jar *
The above step creates a Name of the bundle.jar file under /tmp/workdir.
Use the .jar file with install_package to distribute the script to the desired agents.
1 On BMC ProactiveNet Server computer, change to C-shell and execute the
following:
csh
2 Source the BMC ProactiveNet environment file. Execute the following:
source /usr/pw/pronto/bin/.tmcsh
3 Run install_package in CLI mode.
install_package Path of Distribution Jar file directory -os all -package
Distribution jar file name -agent Desired Agent Names (comma separated)
For example:
install_package /tmp/workdir -os all -package DistributeScript.jar -agent all
Aggregate monitors
Aggregate monitors
These monitors are based on Groups. Unlike other BMC ProactiveNet monitors,
these monitors are not device centric.
Resource Pool monitor and Abnormality Index monitor can be applied to groups
spread across devices. These monitors work with existing data from included groups.
Resource Pool Monitor
Resource Pool
Resource Pool Monitors have variable number of Stats attributes. They can monitor
complex combinations of metrics and monitor higher-level abstractions like pools or
clusters. Creating a monitor at this level enables setting thresholds that are otherwise
not possible.
Resource Pool monitor is a grouping of monitors. Value for each of the attributes
monitored by the Resource Pool Monitor is calculated based on the latest value from
each of the underlying instances.
Resource Pool Monitor is only available on the Local agent (BMC ProactiveNet
Agent on BMC ProactiveNet Server)
A few examples of when a Resource Pool monitor can be created:
You have a pool of Web servers. Although there is a monitor for each Web server
in the pool, it has limited use since the monitor is at a granular level. To learn how
the pool as a whole is performing is desirable and therefore you would like to
have a monitor that reports stats at the pool level. You actually want to know how
the 'pool' is performing as an aggregate of all the Web servers as opposed to
knowing how each Web server is performing.
The scenario given above can also be applied to application server clusters and
other applications that are used in a pool fashion.
You have an application that consists of many processes. Although it is useful to
monitor each process separately, it is also desirable to know how all the processes
together are performing (in terms of performance metrics). Aggregating all the
performance metrics enables you to easily see 'application level' performance
metrics as opposed to always seeing the individual components.
Resource Pool
Advantages of Resource Pool monitors

High-level abstract monitoring
Resource Pool Monitors allow for monitoring a group of like monitors as a single
logical entity. This provides a high-level overview of performance and availability.
Reduced Events
Critical events can be restricted to ONLY trigger if the entire pool of resources
degrades. Individual resources should not cause critical events.
Full Monitor functionality
Resource Pool Monitors provide all features of regular BMC ProactiveNet

monitors like real-time statistics, baselines, threshold events and abnormalities,
reporting, etc., with the exception of the following:
Data is polled from the BMC ProactiveNet repository.
Polling interval for the Resource Pool Monitor must be greater than the highest
polling interval of any single monitor in the pool.
Flashcheck feature is not supported.
Create a Resource Pool monitor type

Perform the following procedure to create a Resource Pool monitor.
To create a Resource Pool monitor

1 Log on to the Administration Console using your logon name and password.
2 Navigate to Tools => Monitor Wizard => Resource Pool
The Monitor Wizard window is displayed and existing monitors (if any) are
listed.
3 Click Add to display the Monitor Definition window.

The monitor definition screen for Resource pool monitors can also be accessed
from the folders. Expand Aggregate Monitors Folder and right-click Resource
Pool. Select Define Monitor Type.
4 Enter the Input Requirements.

Monitor Display Name - Unique name of the new monitor, as it will be
displayed throughout the BMC ProactiveNet.
Resource Pool
Monitor Name - Unique name of the new monitor type that will be created
Monitor Category - Choose the category under which the new monitor will
appear in the Administration Console.
5 Click Load Monitor Types. This populates the remaining fields on the right side
of the window. In 7.5, this attribute is enhanced to load monitor types manually.
Enter either exact name (case sensitive) or partial/initial name (case insensitive)
of the monitor types and then click load button or press enter to list all the
monitor types available.
6 Select the appropriate options.
User-defined names for attributes (displayed at the monitor instance level) are
not displayed during creation of Resource Pool Monitor Types for Windows
Performance Counter and Web Transaction monitor pools. Example, Web
Transaction monitor instances may have different names (user-defined) for
subtransactions (response time). However, the Resource Pool Monitor displays
attributes as response time1, response time 2, etc and does not use the userdefined names.
Monitor Types - Select the monitor type from the list. All registered and
licensed monitors are displayed.
Attributes - For the selected monitor type, all Stats Attribute display names
along with units are displayed. You can choose the attributes to be aggregated.
Average
- Sum of all data points for each instance-attribute and divided by
the total number of instances.
Maximum
- Sort the data points from the various instances and take the
highest value.
Median
- Sort the data points from the various instances and take the middle
value.
Minimum
- Sort the data points from the various instances and take the
lowest value.
Standard
Deviation - Reports the standard deviation over the set of points
for that set of data points.
- Sum of all data points for each instance-attribute.
Sum
Note
Only the first 254 characters of a Output Configuration attribute are

displayed in the Administration and Operations Consoles. To display the
attribute fully, limit the length of the attribute to less than 254 characters.
Resource Pool
7 Click Add.
The Selected attributes table above is populated with information you entered.
The first three columns display information chosen in the previous step. The
remaining columns can be edited for further refinement of the monitor.
Attribute Names Name of the attributes.
Function Type - Select the function type from the list.
Percentile - Value that would report that X% of the monitors and below is
reporting. (0 being the min, 100 being the max, 50 being the median) If
percentile is selected, then the Weightage combo box is enabled to select the
appropriate nth weightage factor.
Attribute Display Name - Unique name of the attribute as it will be
displayed in BMC ProactiveNet on configurations screens and graphs. By

default, the attribute display name is blank but it is mandatory to choose a
unique, logical name.
Scale - This editable field is the value by which the raw stats data has to be
multiplied. This can be used to scale down or scale up the stats data. By
default, it is set to 1.
Select KPI to indicate the key attributes.

default option is also selected to display the graph in the Operations Console. The
selected attribute is displayed by default when a graph is generated. For non
selected attributes ranking is not set.
Graph Default - At least one attribute must be selected. Attributes selected are

Normal Distribution - It is important to understand the significance of this
setting, since it impacts how condensed data, baseline data, and report data are
actually calculated.
(Baseline data and report data are derived from the condensed hourly samples).
How Normal Distribution is set determines how raw data points are converted
into condensed hourly samples. Hourly samples are made up of a max value, avg
value, and min value for that hour.
When Normal Distribution is selected, the highest data point for that hour is
taken as the maximum value, the average value is the true average of all points,
and the lowest data point is taken as the minimum value.
Resource Pool
If Normal Distribution is NOT selected, then the maximum value is derived only
after ignoring the top 10% of data points, the average value is taken from the
median value, and the minimum value is derived only after ignoring the bottom
10% of data points.
Test - Click Test to test data collection by the monitor for the attributes selected.
The test results are based on RAW data collected by the monitor
Note
To delete a row from the Selected Attributes table, select the particular row and
click Remove.
8 After entering details of the monitor setup, click Create Monitor. The system sets
up the new monitor and returns to the wizard window.
9 Click Close.
The new monitor type is now available from the Administration Console in the
category chosen when the monitor type was created. You can now use this
monitor type to add instances.
Create a Resource Pool monitor instance

Once the new monitor is registered in the BMC ProactiveNet, an instance of it can be
created via the BMC ProactiveNet Administration Console.
License for using the Resource Pool is required for creating Resource Pool monitor
Instances.
To create a Resource Pool monitor instance

1 Go to Aggregate Monitors => Resource Pool folder.
2 Right-click Resource Pool and select Add.
3 Select the Resource Pool Monitor type to create its instance.
Depending on the selection, BMC ProactiveNet will display appropriate
monitor instance creation screen. Complete the Configuration and Control tabs
and click Finish.
BMC ProactiveNet creates the monitor instance and displays the status. Click
OK to exit.
The new instance is listed under Resource Pool folder grouped based on the
Monitor Type. For example, the Web URL monitor instance (URL 1) will be
listed under Resource Pool => Web URL => URL 1.
Resource Pool
Find a Resource Pool monitor instance in the BMC

ProactiveNet Operations Console
After you have created a Resource Pool monitor, it is displayed in the Group Matrix
in the BMC ProactiveNet Operations Console.
To access a Resource Pool Monitor Instance in the Operations Console

1 In the BMC ProactiveNet Operations Console, click Group Matrix.
The groups added earlier through group operations are displayed.
2 Click any group.

The Monitor Name displayed with the three red dots icon is a group with a
Resource Pool monitor instance.
Edit a Resource Pool monitor instance

Use the Administration Console to edit a Resource Pool monitor instance.
To edit a Resource Pool monitor instance

1 In the Administration Console, go to Aggregate Monitors => Resource Pool =>
Monitor Type and select the monitor instance that you want to edit.
2 Right-click the instance to edit.
3 Select Edit.
4 After making the required changes, Click OK to save the changes.
Edit a Resource Pool monitor type

Once a Resource Pool Monitor has been created, editing it is quite simple.
To edit a Resource Pool monitor type

1 In the Administration Console, navigate to Tools => Monitor Wizard =>
Resource Pool.
2 Select the monitor you want to edit and click Edit.
Resource Pool
3 Make necessary changes. For input descriptions, see Create a Resource Pool
monitor type on page 133.
Note
You cannot edit the Monitor Type field.
4 Click Update Monitor.
BMC ProactiveNet registers the changes.
Delete a Resource Pool monitor

Follow the steps given below to delete a Resource Pool Monitor.
To delete a Resource Pool monitor

Resource Pool
BMC ProactiveNet deletes all monitor instances that belong to the monitor type
from the Monitor Wizard window and from the Administration Console.
Special notes
In dataview tables for Resource Pool Monitors, the source IP (SRCIP) will be
displayed as RESOURCE POOL, a device to which all resource pool monitors are
attached.
Some attributes are specific to the operating system. Consider operating system
dependencies while selecting attributes for Resource Pool Monitors.
If the error Cannot find Agent on PN Server is displayed when you try to
create a Resource Pool Monitor, set pronet.apps.agent.localagentid=local
agent ID in usr/pw/custom/conf/pronet.conf file.
The number of Stats attributes per Resource Pool Monitor type is limited to 50.
The values reported by RPM are based on the poll frequency of the RPM and the
underlying monitors. If multiple data points are available when the RPM poll
frequency does not match that of the individual monitors, only the latest data
point is considered. For example, if the RPM is polling at 10 minutes interval and
the underlying monitors are polling at 5 minute, then the RPM considers the latest
data point.
Suppose the RPM is reporting average availability. Say the availability of monitor
A is 100% and 100%, and that of monitor B is 0 and 100%. In this case the RPM
considers only the second data point for each monitor, i.e, 100%. However, if the
poll frequency of the RPM and underlying monitors was same, then in first poll
the availability would have been 50%, and in the second poll it would be 100%.
To avoid any confusion on reported values, BMC ProactiveNet recommends due
consideration for setting RPM poll frequency.
For wizard level timeout during Load:
pronet.agent.controller.attributechoice.timeout=120. If you want to
change the value of timeout for wizard side load, then to get the new value in
effect and restart the agent controller after changing the value on server side's
pronet.conf.

Abnormality Index Monitors depict the overall health of a group of monitor
instances, based on the number of abnormalities generated for the monitors. All
abnormalities occurring for monitor instances in a group can be pooled to get the
overall health of the group.
This monitor collects all abnormal events that occurred for the monitor instances in a
group. For example, to view a consolidated health report of five monitor instances of
different monitor types, add these five instances to a group and add an Abnormality
Index Monitor instance to the group. This monitor instance will then report on the
abnormality level of the group, which serves as an early warning system.
The group health is considered good when the reported abnormality index is low; as
the group health deteriorates, the reported abnormality index increases:
Abnormality Index of 0% means the monitored group is working as expected, where
as a value moving towards 100% means that the health of the monitored group is
deteriorating.
The procedure to view and graph Abnormality Index Monitor output is same as
other BMC ProactiveNet monitors. However, the main differences are as follows:
Only a single instance of this monitor can be created per group.
Abnormality Index Monitor is only available on the local agent.
Abnormality Index Monitor is listed in the group matrix under the corresponding
group.
Abnormality Index Monitor reports based on abnormal events. The abnormal
events are based on baseline violations. For example, if a monitor reports zero
availability, this may not be considered for Abnormality Index calculations even
though an event may get generated in BMC ProactiveNet.
Creating an Abnormality Index monitor

Perform the following procedure to create an Abormality Index monitor.
To create an Abnormality Index Monitor

1 Expand Aggregate Monitor folder.
2 Right-click Abnormality Index.
3 Click Add Abnormality Index.
Monitored attributes
Total Abnormalities (#) - Total number of events generated over the statistics poll
period.
Abnormality Index (%) - Depicts the overall abnormality level (health) of the
group in percentage. Abnormality Index of 0% means the monitored group is

working as expected. A value moving towards 100% means that the health of the
monitored group is deteriorating.
Monitor Instance Count (#) - Number of monitor instances presently associated
with the group.
Hourly Baseline Abnormalities (#) - Total number of abnormalities based on
hourly baseline.
Weekly Baseline Abnormalities (#) - Total number of abnormalities based on
weekly baseline.
Configuration attributes
The Abormality Index monitor has the following configuration attributes.
Input fields
Instance Name - Specify a name for the monitor instance. This is displayed on
folders, graphs, lists, etc. Example, Abnormality Index Group1.
Tag - Specify tag value to search or group the objects. You can enter multiple name-
value pairs, text, or include both (name-value pair and text). This gives you the
option to group objects in different forms. Click icon + to select a default tag class.
The Enter Tag Details screen opens. Select Tag Class from the list and enter a tag
value, click Add to append tag class and value. Click Finish.
Note
The tag specified by you is not considered as a default class. You cannot enter
special characters &"/<>' in the tag field.
Editing Tag Value on Enter Tag Details screen. Select a tag value and click edit.
Make the necessary modifications in Tag Value text box and click Set to add the
changes.
Deleting a Tag Value on Enter Tag Details screen. Select a tag value and click
Delete, dialog box is displayed with the options Yes or No. click Yes to delete the
tag value.
Associate to Device - Select the device with which the monitor instance must
be associated. The monitor instance is listed under the Device with which you
associate it and also under the Aggregate Monitors => Resource Pool Monitors
folder.
If you select None, the monitor is not associated with any device. The monitor
instance created is listed only under the Aggregate Monitors => Resource Pool
Monitors folder.
Group - Select the group with which the monitor instance must be associated.
Alternatively, click New to access the Add Group window and define a new
group to associate the monitor instance with.
System fields
No system-populated configuration attributes are associated with Abnormality
Index Monitors.
Control attributes
The Abnormality Index Monitor has the following Control attributes.
Collect Data - Select/clear check box to enable/disable data collection for the
monitored component. By default, data collection is enabled (check box selected).
Statistics Poll Interval - Specify the time interval between two consecutive
Statistical data polls.
Statistics Poll Timeout - Specify the time-out period for each poll of statistical
data. If no data is available at the end of this interval, system records zero
availability and proceeds with the next scheduled poll.
Special notes
Abnormality Index Monitor records NO_DATA for monitored attributes when it
is not connected to the database.
More info messages are recorded when no monitors are present in the group on
which the Abnormality Index Monitor is created.
Abnormality Index Monitor reports data about all abnormal events recorded for
the underlying monitors. Due to the nature of this association, the reported
abnormality count is governed by the individual poll times of the underlying
monitors. For example, if an underlying monitor has a violation check based on
duration (say 30 minutes) the event is recorded as abnormal only after 30 minutes,
and in the following poll. In this case the abnormality Index monitor will report
this event only in the poll following the completion of this 30 minutes and the
immediate poll of that particular monitor.
Monitor configuration
There are no additional configuration requirements for this monitor. Maintain the
default configuration of BMC ProactiveNet.
Setup and dependencies

External setup
There are no external setup requirements for this monitor.
External dependencies
There are no external dependencies for this monitor.
SNMP
Miscellaneous information
For information on troubleshooting, refer Troubleshooting section.
For information on supported versions, refer Support section on BMC Web site
SNMP
The Monitor Wizard is used to create custom SNMP monitors. These monitors can
be configured to collect data for the selected OIDs. For example: The number of TCP
connections in a router or a PC can be monitored by specifying the OID
corresponding to TCP node.
External setup requirements to create SNMP monitor instances

1 SNMP agent must be running on the target host, from which we are trying to
retrieve SNMP data.
2 Ensure that valid OIDs are specified during the registration process. For example,
creating a monitor instance based on Cisco OIDs, but specifying a non-Cisco
product as the target host would be inappropriate and no data would be collected
for the Cisco OIDs.
Defining a SNMP monitor

Follow the steps given below to define an SNMP Monitor:
Compile the required MIBs

The required standard and/or enterprise MIBs can be compiled using the MIB
compiler tool.
Note
For information regarding the MIB Compiler tool, see MIB Compiler features on
page 204.
SNMP
This step is necessary before we can proceed to registration process. Refer Using the
MIB Compiler topic for details.
Creating an SNMP monitor type

Perform the following procedure to create an SNMP monitor type.
To create an SNMP monitor type

1 Log on to the Administration Console using your login name and password.
2 Navigate to Tools => Monitor Wizard => SNMP
listed.

4 Specify the Input Requirements.
Monitor Display Name - Unique name of the monitor, as it will be displayed
throughout BMC ProactiveNet.
Monitor Name - Unique Name of the monitor type that will be created.
Monitor Category - Category under which the monitor will appear in the
Administration Console. Click New to create a subcategory to be created and

displayed under the Other category in the Administration Console. Refer
Monitor New Subcategory topic for more information.
5 Click Load. This loads all the pre-compiled MIBs into the Available MIBs list.
6 From the Available MIBs list, select a MIB. In 7.5, this attribute has been enhanced
to load MIBs manually. Enter either exact MIB(s) name (case sensitive) or partial/
initial name (case insensitive) of MIB(s) and click Load button or press Enter to
list all the MIBs available.
7 Select the required attributes that are displayed under MIB Root and click Add.
The Selected Attributes table is populated with the MIB node information you
selected. The first three columns display information chosen in the previous
step. The remaining columns can be edited for further refinement of the monitor.
Alternatively, use Add using OID option in Create SNMP Monitor screen, to
manually add the OIDs.
Perform the following additional steps to manually add the OID:
SNMP
a Click Add using OID option in Create SNMP Monitor screen. Input for OID
Specific Row window opens.
b Enter the OID.
c Check Do Validation to verify the OID.
d Click Ok to open Required Information window.
e Enter the following information.
Source Agent: Select the source agent. For local monitoring, this must be the
same as the target IP; for remote monitoring, the source agent selected, must
have administrative privileges on the remote computer.
Target Device: Specify the name/IP address of the computer on which the
OID is to be monitored.
Port: Specify the port on which the application is listening.

Version: Select the SNMP version (V1, V2c or V3) from the list.
Community String: Specify the community string for the SNMP device. This
string limits SNMP access to the device. Default is public.
f Click OK to add the OID to the selected attributes table. If the OID is not valid,
an error message is displayed.
g Click OK to return to Please Enter Required Information screen.
Figure 17: Selected Attributes Table
OID OID value of the selected MIB node.

OID Name Name of the selected MIB node.
MIB Name RFC name of the selected MIB.
SNMP
Attribute Type Indicates whether the value is statistic or configuration
parameter.
In BMC ProactiveNet 7.5 and later, the system automatically validates and
assigns the attribute type as either configuration or statistics. Prior to 7.5, the
attribute type had to be validated and assigned manually.
Note
Only the first 254 characters of a Output Configuration attribute are displayed
in the Administration and Operations Consoles. To display the attribute fully,
limit the length of the attribute to less than 254 characters.
Attribute Display Name - Unique name of the Attribute, as it will be
displayed. By default, the Attribute Display Name is blank but it is

mandatory to choose a unique, logical name.
Measure As - This column supports Raw, Delta, and Rate data types.
Rate - Rate of change of data between two polls is recorded and displayed.
Delta - Difference (change) in the data between two polls is recorded and
displayed.
Raw - Data value retrieved is recorded without any further processing.
Examples on how to calculate raw and delta values for any

monitor?
Example 1: If the monitors polling interval is 60 seconds and polls at a time of t
with a value of 30. Next, the monitor polls at a time of t+60s with a value of 60.
Delta calculation:
Value of data point at t+60 = new value at "t+60" - old value at "t"
= 60 30
= 30
Rate Calculation:
Value of data point at t+60 = (new value at "t+60" - old value at "t") / (Poll Interval)
= (60 - 30) / 60
= 0.5 per sec.
SNMP
Example 2: If the monitors polling interval is 60 seconds and time of poll is t with
a value of 10. If a manual flash check is done at a time of t+30s with a value of 30
and the next poll is at t+60s with a value of 60. Each flash check is considered as a
data point.
Delta Calculation:
= 30 10
= 20
Value of data point at t+60 = new value at "t+60" - old value at "t+30"
= 60 - 30
= 30
Rate Calculation:
Value of data point at t+30 = new value at t+30 - old value at t) / (Poll Interval)
= (30 - 10 ) / 30
= 0.666 per sec
Value of data point at t+60 = (new value at t+60 - old value at t+30) / (Poll Interval)
= (60 - 30 ) / 30
= 1 per sec.
Scale Multiplier factor to store Statistics data and Configuration (numeric only)
data values. This value can be modified to scale-down or scale-up the statistics
and configuration data.
Note
For configuration data, if data retrieved is non-numeric, then the scale factor
will not be applied even if it is set. In such cases, appropriate logging can be
found in log file.
Unit - Unit of measurement for a statistics and configuration attribute. Select the
unit from the list. You can also specify the units. After successful monitor creation,
the newly specified unit will be available in the list, for all monitor types. If
SNMP
required, the unit can be changed. Ensure that none of the below-mentioned
string or characters are given while defining a new unit:
$$ * + , ; ^ & " < > '


Normal Distribution - It is important to understand the significance of this setting
since it impacts how condensed data, baseline data, and report data are actually
calculated.
When Normal Distribution is selected, the highest data point for that hour is taken
as the maximum value, the average value is the true average of all points, and the
lowest data point is taken as the minimum value.
10% of data points.
Note
Values for the columns Measure As, Graph Default, and Normal Distribution
cannot be specified if the selected Attribute Type is Config.
At least one Stats attribute must be selected per monitor type and also, one of the
Stats attribute must have the Graph Default option selected.
Test - Click Test to test data collection by the monitor for the attributes selected.
The test results are based on RAW data collected by the monitor.
SNMP
1 After entering the details of monitor setup, click Create Monitor.

The system sets up the new monitor and returns to the wizard window.
The Monitor type is now available in the Administration Console. Click Close
if you are finished, or click Edit to modify an existing monitor type on the list
or delete a monitor type on the list.
Performance limitations
Only one columnar (Tabular) OID is allowed per monitor type. However, any
number of child OIDs of that particular tabular OID is available for selection.
Config attributes allowed is limited to 30 and the total number of attributes

(inclusive of both Stats and Config) is limited to 80.
Creating an SNMP monitor instance

After registering the SNMP Monitor with the BMC ProactiveNet, an instance of it
can be created via the Administration Console. The monitor created is listed under
the category selected during instance creation.
Complete the steps given below to add an instance of the new monitor using an
existing device on the Device folder.
To create an SNMP monitor instance

1 On the Administration Console, expand the Device folder until you see the device
on which you want to add the monitor instance.
2 Right-click the device and select Add Monitor.
3 Drill down and select the monitor you want to add.
Note
If you have selected MIB Nodes from SNMP tables, then the Configuration tab is
as shown below.
4 In the Configuration tab, specify an instance name and other parameters, as
required.
SNMP
From 7.5 onwards, TargetIP/HostName field is changed to Target Device for all
VAM monitor instances. Prior to 7.5, If DNS Name is given to TargetIP/
HostName; it used to resolve to IP Address and was displaying this stored IP
Address while editing the instance. But now from 7.5 onwards it will retain the
DNS name in Target Device field when user edits the instance.
Click Load to select the Index Value from the list.
5 Use the Control tab to modify the defaults, if required.
Skip: If you have selected several monitors from the Select Monitors to Create
window, or there are default monitors associated with the device, click this
button to ignore monitors you do not want added. You then automatically
move to the next part of the configuration process.
Add: Click this to add the monitor instance listed at the top of the screen, and
then continue to use add as needed.
Next: Click this if there is only one monitor instance to add.

Finish: Click this at the beginning of the process to automatically add all
monitor instances selected. This also automatically creates instance names to

close the Monitor Wizard.
If V3 is the specified SNMP version on the configuration screen, SNMP V3
details tab is enabled.
6 Modify details as required.

Engine ID - Specify the engine ID configured on the SNMP agent.
Alternatively, click LOAD and select from the drop down list. If no value is
specified, BMC ProactiveNet automatically detects the engine ID.
User Name (Security Name) - Specify the user name to access the SNMP agent.
Context Name - Specify the context name (if) configured on the SNMP agent.
Context ID - Specify the context ID (if) configured on the SNMP agent.
Authorization Protocol - Select the authorization protocol (MD5 or SHA) to use.
Authorization Password - Specify the authorization password to access the
SNMP agent.
Privacy Protocol - Select the privacy protocol (CBC-DES) to use.

Privacy Password - Specify the privacy password to access the SNMP agent.
7 Click Finish.
SNMP
8 Click Finish in the Summary of Created Monitors window.

9 Refresh the Device folder in the Administration Console to view the new SNMP
Monitor Instance.
Editing an SNMP monitor type

Once a SNMP Monitor type has been created, you can edit the monitor type to
include new attributes, delete or edit existing attributes.
To edit an SNMP monitor type

1 In the Administration Console, navigate to Tools => Monitor Wizard => SNMP
Monitor
2 Select the monitor you want to edit and click Edit. For input descriptions, refer
Register the SNMP Monitor.
3 Make necessary changes. The changes take effect only after the focus is taken off
the edited field.
Click Remove to delete either one selected attribute or multiple attributes at a
time.
4 Click Update Monitor

BMC ProactiveNet registers the modified monitor type again and also updates
the existing instances, if any.
Deleting an SNMP monitor type

Follow the steps given below to delete a SNMP Monitor.
To delete an SNMP monitor

1 In the Administration Console, navigate to Tools => Monitor Wizard => SNMP
Monitor.
JMX
BMC ProactiveNet deletes the monitor and removes it from the Monitor
Wizard window and the Administration Console. All monitor instances of this
monitor type will also be deleted.
Troubleshooting
In BMC ProactiveNet 7.5 and later, if SNMP monitor type consists of attributes
which were added using Add using OID without validation, then these will be
validated during the monitor instance creation.
For Pre-7.5 agents, NO DATA will be recorded for such attributes.

pronet.conf.
JMX
Use the JMX Monitor Wizard to create new monitor types to collect data from
Application servers. The new monitors can have variable number of statistic and
configuration attributes (MBean Attributes).
JMX monitoring support

Currently, JMX monitoring support is provided for the following JMX reference
implementations:
Tomcat 4.1, 5.0.30, 5.5.7
JBoss 3.2.6, 4.0.1
WebLogic 6.1, 7.0, 9.0
SunTM JavaTM Virtual computer 1.5
WebSphere 5.1
JMX

The Application server to be monitored must be running on the target device.
JBoss 3.2.6
1 Start the JBoss 3.2.6 Application Server. No extra steps need to be performed to set
up the server for JMX monitoring.
2 Copy JBoss 3.2.6 jbossall-client.jar to Agent Dir/pw/apps3rdparty/jmxvamlib/
jboss/3.2.6.
3 The jbossall-client.jar file can be found at JBoss-install-location/client.
4 Enter the Target IP and the port number on which the JNP connector is configured
to listen. Choose the Mbeans and create the monitor type.
To get the JNP Connector port number:
1 Navigate to JBoss-installation/server/server-name/conf
2 Edit jboss-service.xml and look for the below line:

<attribute name="Port">1099</attribute>
3 Ensure that bindAddress is not bound only to a particular host, otherwise

remote monitoring will not be possible.
The default value for the JNP Connector port is 1099.
JBoss 4.0.1
1 Start the JBoss 4.0.1 Application Server. No extra steps need to be performed to set
up the server for JMX monitoring.
2 Copy jbossall-client.jar from <JBoss installed directory>/client/ to <Agent Dir>/
pw/apps3rdparty/jmxvamlib/jboss/4.0.1 directory.
3 The jbossall-client.jar file can be found at <JBoss-install-location> /client.
4 Enter the Target IP and the port number on which the JNP connector is configured
To get the JNP Connector port number:
1 Navigate to JBoss-installation/server/server-name/conf
JMX
2 Edit jboss-service.xml and look for the below line:


<attribute name="Port">1099</attribute>
3 Ensure that 'bindAddress' is not bound only to a particular host, otherwise remote
monitoring will not be possible.
The default value for the JNP Connector port is 1099.
JVM 1.5
Specify the following parameters for the JVM 1.5 application type, for
unauthenticated access:
Dcom.sun.management.jmxremote.port=44444 (note: any unused port)
Dcom.sun.management.jmxremote.authenticate=False
Dcom.sun.management.jmxremote.ssl=False
Specify the following parameters for the JVM 1.5 application type, for authenticated
access:
Dcom.sun.management.jmxremote.port=44444 (note: any unused port)
Dcom.sun.management.jmxremote.authenticate=True
Dcom.sun.management.jmxremote.ssl=False
Tomcat 4.1 / 5.0

Enable JMX on the Tomcat Application Server:
Check and enable JMX entries in the server.xml file. This file is available in
Tomcat Installation Directory/conf. (This is the default configuration. JMX is

enabled.)
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
debug="0"/>
<Listener
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
debug="0"/>
Update jk2.properties and add the following information to enable mx4j:

mx.port=1099
mx.enabled=true
mxjrmpPort
mx.jrmpPort=1099
mx.jrmpHost=<hostname of the computer where Tomcat is running>
The jk2.properties file is available in Tomcat Installation Directory/conf.

JMX
Copy the following .jar files to the common/lib directory of the Tomcat installation:
mx4j.jar
mx4j-tools-1.1.1.jar
mx4j-remote.jar
The files are available under /usr/pw/monitors/shared/apps3rdparty/mx4j

Restart Tomcat Application server.
Tomcat 5.5
1 Start the JVM with JMX enabled. To do this on a Windows system, go to Start =>
Configure Tomcat.
2 In the Java tab, enter Dcom.sun.management.jmxremote.port=port-no in the
Java options field.
Passwords and access control for remote monitoring should be set up on the
Tomcat system to be monitored.
3 Specify the user name (Principal) and password (Credentials) in the
jmxremote.password file.
4 In the jmxremote.access file, assign a level of access, such as Read-Only or ReadWrite, to the user specified above.
The properties specified above should be used to connect to the JMX Agent.
5 Restart Tomcat Application Server.
WebLogic 6.1
1 Start the WebLogic 6.1 Application Server. No extra steps need to be performed to
set up the server for JMX monitoring.
2 Copy weblogic.jar from WebLogic installed directory/server/lib/ to Agent Dir/pw/
apps3rdparty/jmxvamlib/weblogic/6.1 directory.
3 Enter the Target IP and the port number on which the T3 connector is configured
To get the port on which the T3 connector is configured to listen:
1 Run the Administration Server, and open WebLogic Administration Console.
JMX
2 In the left panel of the console, select the server that has been started.
3 Click Configurations => General.
Value of the T3 connector listen Port is listed here. By default, 7001 is the default port
on which T3 Connector is configured to listen.
WebLogic 7.0
2 In the left panel of the console, select the server that has been started.
3 Click Configurations => General.
Value of the T3 connector listen Port is listed here. By default, T3 Connector is
configured to listen on port 7001.
WebLogic 9.0
2 In the left panel of the console, click Environments => Servers.
JMX
3 Click the name of the server that has been started.

Value of the T3 connector listen port will be listed here. By default, T3 Connector is
configured to listen on port 7001.
WebSphere 5.1
1 Start the WebSphere Application Server. No extra steps need to be performed to
2 Copy the following jars from WebSphere installed directory/lib/ to Agent Dir/pw/
apps3rdparty/jmxvamlib/websphere/5.1 directory:
admin.jar
bootstrap.jar
ffdc.jar
idl.jar
iwsorb.jar
j2ee.jar
jflt.jar
jmxc.jar
jmxx.jar
pmi.jar
pmiclient.jar
ras.jar
sas.jar
soap.jar
utils.jar
wasjmx.jar
wsexception.jar
wssec.jar
JMX
3 Copy the following jars from WebSphere Installed Directory/java/jre/lib/ext to

<Agent Dir>/pw/apps3rdparty/jmxvamlib/websphere/5.1 directory:
log.jar
mail.jar
4 Copy the following jar from WebSphere Installed Directory/java/jre/lib/ext to

<Agent Dir>/pw/apps3rdparty/jmxvamlib/websphere/5.1 directory:
security.jar
Note
For Solaris installation of WebSphere, copy ibmjsse.jar from <Web Sphere

Installed Directory>/java/jre/lib/ext to <Agent Dir>/pw/apps3rdparty/
jmxvamlib/websphere/5.1 directory and rename it as security.jar.
5 Enter the Target IP and the port number on which the SOAP connector is
configured to listen. Choose the Mbeans and create the monitor type.
To get the port number on which the SOAP connector is configured to listen:
1 Start the Application server.
2 Log on to the Administration Console.
3 On the left panel, click Servers => Application Servers.
4 Click the name of the server that is displayed on the right side.
5 In the Configuration tab, click End-Points.
6 Click SOAP Connector Address. By default, the port number is set to 8880.
Creating a JMX monitor type

Complete the steps given below to create a JMX Monitor.
To create a JMX monitor

2 Navigate to Tools => Monitor Wizard => JMX.
JMX
listed.
Note
4 Enter the input requirements.
Monitor Display Name - Specify a unique name for the new monitor. This is
displayed across the BMC ProactiveNet system. The name cannot exceed 58
characters.
Monitor Name - Specify a unique name for the new monitor that can be
cryptic. This name must not exceed 17 characters with no spaces. (For internal
use only)
Monitor Category - Choose the category in which the new monitor must
appear in the Administration Console. This also establishes correlations for the
Probable Cause engine. Alternatively, click New to create a new monitor
subcategory to be displayed under the Other category in the Administration
Console. Refer Monitor New Subcategory topic for more information.
Application Type - Select the Application Server name and version for which
the monitor type must be created. Currently supported application types are
Tomcat 4.1, Tomcat 5.0, JVM 1.5, Tomcat 5.5, WebLogic 7.0, WebSphere 5.1,
JBoss 4.0.1, WebLogic 9.0, JBoss 3.2.6, and WebLogic 6.1.
JNDI Name - Specify the JNDI lookup name of the JMX Agent on the target
computer. Default JNDI Names for the various application servers are:
JBoss 3.2.6 - jmx/rmi/RMIAdaptor
JBoss 4.0.1 - jmx/rmi/RMIAdaptor
JVM 1.5 - jmxrmi
Tomcat 4.1 - jrmp
Tomcat 5.0 - jrmp
Tomcat 5.5 - jmxrmi
WebLogic 6.1 - weblogic.management.adminhome
WebLogic 7.0 - weblogic.management.adminhome
JMX
WebLogic 9.0 - weblogic.management.mbeanservers.domainruntime

Initial Context - Specify the Initial Context Factory used to establish connection
with the JMX Agent on the target computer. Default Initial Context values for
the various application servers are:
JBoss 3.2.6 - org.jnp.interfaces.NamingContextFactory
JBoss 4.0.1 - org.jnp.interfaces.NamingContextFactory
Tomcat 4.1 - com.sun.jndi.rmi.registry.RegistryContextFactory
Tomcat 5.0 - com.sun.jndi.rmi.registry.RegistryContextFactory
WebLogic 6.1 - weblogic.jndi.WLInitialContextFactory
WebLogic 7.0 - weblogic.jndi.WLInitialContextFactory
Source Agent - Select the source agent here. For local monitoring, this must be
the same as the target IP; for remote monitoring, the source agent selected here
must have administrative privileges on the remote computer.
Target IP/Host Name - Specify the IP address or host name of the system
where the Application server is running.
Port - Specify the port on which the JMX Agent in the application is listening.
Principal - Specify the Principal (user name) required to connect to the
Application server.
Credentials - Specify the credentials (password) for the Principal to connect to
the Application server.
Load - Click this to load the list of attributes associated with the application
server selected.
7.5 onwards, the MBean's are grouped based on common name-value pair from
MBean's object name. Prior to 7.5, the MBean Tree showed a flattened 2 level view.
Attributes - This displays a list of attributes associated with the application
server selected. From the list, you can select attributes to associate with the
monitor you are creating.
Add - Click this to move selected attributes from the Attributes to the Selected
Attributes section. The attributes that you select here are associated with the
monitor being created.
JMX
Remove - Click this to remove selected attributes from the Selected Attributes
section.
Figure 18: Selected Attributes section
Attribute Name - Name of the MBean attribute.

MBean Name - Name of the MBean.
Attribute Type - Indicate whether the attribute is configuration or statistic
parameter.
7.5 onwards, the system automatically validates and assigns the attribute type as
either configuration or statistics. Prior to 7.5, the attribute type had to be validated
and assigned manually.
Note
Only the first 254 characters of an output configuration attribute are displayed in
the Administration and Operations Consoles. To display the attribute fully, limit
the length of the attribute to less than 254 characters.
Attribute Display Name - Unique name of the attribute as it will be displayed
in configuration screens and graphs in BMC ProactiveNet. By default, the

Attribute Display Name is blank, but it is mandatory to choose a unique,
logical name.
Measure As - Select the type of calculation to be done on the attribute value.
This column supports Rate, Delta, and Raw data types. Ideally, Rate and Delta
measures must be used for variables that return counter types.
displayed.
Record the data as raw when no further processing is required.

monitor?
JMX
Delta calculation:
= 60 30
= 30
Rate Calculation:
= (60 - 30) / 60
= 0.5 per sec.
data point.
Delta Calculation:
= 30 10
= 20
= 60 - 30
= 30
Rate Calculation:
= (30 - 10 ) / 30
= 0.666 per sec
= (60 - 30
) / 30
= 1 per sec.
JMX
Scale - Select the value the raw statistics data and configuration (numeric only)
data has to be multiplied with. This can be used to scale down or scale up the
statistics and configuration data. By default, it is set to 1. For example, you can
change a value set in bytes to kilobytes or megabytes by using the Scale and Unit
fields. The upper boundary of an attribute value is (2147483647/1000). For
example, if the value retrieved for an attribute is 2147483647, the scaling value can
be entered as 0.001 (if you want to divide it by 1000).
Note
For configuration data, if data retrieved is non-numeric, then scale factor will
not be applied even if it is set. In such cases appropriate logging can be found
in log file.
Unit - Select the unit from the list. You can also specify the units. After creating
the monitor the newly specified unit will be available in the list, for other monitor
types also. Ensure that none of the below-mentioned string or characters are given
while defining a new unit:
$$ * + , ; ^ & " < > '



Normal Distribution - This setting impacts the way condensed data, baseline
data, and report data are actually calculated.
(Baseline data and report data are derived from condensed hourly samples).
Normal Distribution setting determines the way raw data points are converted
10% of data points.
CPU, and FileSize. For these attributes you do NOT want to discard any values
JMX
absolute low recorded. Examples of attributes with Normal Distribution=false are:
Ping ResponseTime, WebURLResponseTime. The reason is that response time
measurements will typically have a few fluctuations that are way outside the
normal range and would skew the hourly calculations if included. Instead, the
extremes at the upper and lower end are discarded.
Test: Click Test to validate data collection for the Mbean attributes selected before
you create the monitor. This helps to check whether the value of the attribute can
be retrieved from the Application server with the input attributes entered. This
also helps to verify whether the attribute value exceeds the graphing limits; thus,
you can appropriately adjust the scale factor before creating the monitor type.
1 After entering details of the monitor setup, click Create Monitor. The system
creates the new monitor and returns to the wizard window.
2 Click Close.
category chosen when the monitor type was created. You can now use this monitor
type to add instances.
Example to create JMX monitor on BMC ProactiveNet Server

This section provides an example of how to create a JMX monitor.
External setup
1 Navigate to installDirectory /pw/jboss/server/minimal-jms.
2 Copy jmx-invoker-service.xml file to installDirectory /pw/jboss/server/minimaljms/deploy directory.
3 Go to installDirectory /pw/jboss/client directory and copy jbossall-client.jar to
installDirectory /pw/apps3rdparty/jmxvamlib/jboss/4.0.1.
Creating the monitor type

2 Navigate to Tools => Monitor Wizard => JMX.
JMX
3 Select Jboss 4.0.1 as the Application Server name and version for which the
monitor type must be created.
4 Select BMC ProactiveNet Server as the Source Agent.
5 Specify localhost as the target IP and 1100 as the port number.
6 Click Load to load the list of MBean attributes associated with the selected Jboss
4.0.1.
7 Select the attributes required and click Add.
The chosen attributes are displayed in the Selected Attributes table and will be
associated with the monitor you are creating. 7.5 onwards, the system
automatically validates and assigns the attribute type as either configuration or
statistics. Prior to 7.5, the attribute type had to be validated and assigned manually.
8 Click Create Monitor to create the monitor type.
Create a JMX Monitor Instance

Once the new monitor is registered in the BMC ProactiveNet system, an instance of
it can be created via the BMC ProactiveNet Administration Console. The new
monitor will appear in the menu of the Administration Console in the category
chosen when it was created. This monitor instance can be created or deleted via the
Administration Console on any of the applicable resources in the system.
existing device on the Device folder:
1 From the Administration Console, expand the Device folder until you see the
device on which you want to add the monitor instance.
3 Drill down and select the monitor you want to use.
4 On the Configuration tab, specify an instance name and other parameters, as
required.
From 7.5 onwards, TargetIP/HostName field is changed to Target Device for all
VAM monitor instances. Prior to 7.5, If DNS Name is given to TargetIP/
HostName; resolved to IP Address and was displaying this stored IP Address
while editing the instance. 7.5 Onwards, it will retain the DNS name in Target
Device field when user edits the instance.
5 Click Next.
JMX
6 In the Control tab, modify the default values, if required.

Button Options
Skip - If you have selected multiple monitors from the Summary of Created
Monitors window or there are default monitors associated with the device,
click Skip to ignore monitors you do not want added and automatically move
to the next part of the Configuration process.
Add - Click Add to add the monitor instance listed at the top of the screen, and
then continue to use Add as required.
Next - Click Next if there is only one monitor instance to add.

Finish - Click Finish at the beginning of the process to automatically add all
monitor instances selected and close the Monitor Wizard.

Editing a JMX monitor type

Once a JMX monitor has been created, editing its properties is quite simple.
To edit a JMX monitor

1 In the Administration Console, navigate to Tools => Monitor Wizard => JMX.
2 Select the monitor whose properties you want to change, and click Edit. For input
descriptions, refer Create JMX Monitor Type section.
3 Make changes to the monitor properties, as required.
4 Click Update Monitor.
BMC ProactiveNet registers changes made to the monitor properties.
Delete a JMX monitor type

Follow the steps given below to delete a JMX monitor.
File monitor
To delete a JMX monitor

1 In the Administration Console, navigate to Tools => Monitor Wizard => JMX.
2 Select the monitor you want to delete, click Delete.
BMC ProactiveNet deletes the monitor from both the Monitor Wizard and the
Administration Console. All instances of this monitor are also deleted from the
system.
Troubleshooting
change the value of timeout for wizard side load, then to get the new value in effect
and restart the agent controller after changing the value on server side's pronet.conf.
File monitor
File monitor wizard can be used to create a new monitor type, which can collect data
from log files. Using this wizard, you will be able to create a new monitor type with
a variable number of statistical (stats) and/or configuration (config) attributes. You
can select and choose the list of stats and/or configured attribute(s) from one or
more than one log file that you want to monitor. This considers only last line of a log
file during data collection or for time stamp, lines from last poll to current poll is
considered. If the file is not refreshed, no data will be recorded. Negative values are
allowed for stats attributes. For monitoring of the file, this monitor requires a BMC
ProactiveNet Agent to be installed and running on the target computer.
File monitoring support

File monitors are supported on the following platforms:
Solaris
Windows
Linux
X86
File monitor
External setup requirements to create file monitor

The log file must be present on the system hosting the source agent.
The log file(s) should have at least Read Permission.
Create a File monitor type

Follow the steps given below to create a File Monitor.
To create a File monitor

2 Navigate to Tools => Monitor Wizard => File.
3 On the Monitor Wizard - File dialog box, click Add to display Create File Monitor
screen.
4 Enter the required inputs.
Monitor Display Name - Display name of the monitor type. The monitor type
is identifiable with the display name in the Administration Console and the
Operations Console. Example: test_File. Display Name should begin with an
alphabet, can contain underscores and spaces, can have 58 characters, and must
be unique. The name can contain a numeral but should not begin with one. If
the monitor display name is not specified, the monitor name is used by default.
Monitor Name - Specify a unique name for the new monitor that can be
cryptic. This name must not exceed 17 characters with no spaces (For internal
use only).
Monitor Category - Choose the category in which the new monitor must
Console.
Source Agent Select the BMC ProactiveNet Agent from which the file needs
to be loaded.
Directory Name Enter absolute path of a directory from which files are to be
loaded, and Click on Load button to load all files from the directory.
Select File Select the file to be monitored. In 7.5, this attribute has been
enhanced to load both file name and directory manually. Enter either file name
File monitor
or directory (case sensitive) or partial/initial file name, directory, or both file

name (case insensitive) and click Load button to list all the available file names
and directories.
File Contents Preview The first 10 lines of the selected file will be displayed.
Delimiters A delimiter is a character that separates data in the single record
into different columns. Each column can be taken as a different attribute. The
default delimiters available are Tab, Semicolon, Comma, space, and other.
Choose other delimiter to customize any other character other than the
available delimiters.
Treat Consecutive delimiters as one Click this to treat more than one
(consecutive) delimiters as one delimiter.
Column Number(s) to Extract You can enter the Column number(s) of the
selected file(s) and multiple column numbers are allowed, with comma as a
delimiter.
Select Clicking this option will display the first 10 lines of the file in tabular
form using selected delimiter. You have to select the column(s) to be monitored.
Click OK to display the column numbers in the Column Number(s) to Extract
field.
Use last line inserted only During each poll, only last line of the log file is
processed to get data. If the file is not updated, then NO_DATA will be
recorded for that poll. By default, this option is enabled. This option is
provided to retain pre 7.5 behavior.
Use TimeStamp in File - During each poll, all the lines inserted between the
last poll and current poll will be processed to get data based on matched
patterns (inputs), if any. During poll, if monitor finds multiple lines based on
matched patterns (inputs), then only the last line which matches the pattern
(input) will be recorded in the database. TimeStamp used for recording the
data is picked up from this record.
Note
This option is supported for attributes from one file only.

Date/Time Format Displays format of date and time in the log file. If this
format does not match with the format in File, then data will be recorded with
agents timestamp. The supported formats are the ones, which are supported
by java.text.SimpleDateFormat.
If date and time are from different columns, then use + as delimiter
between date and time for input date/time format.
File monitor
Date/Time Column Number Displays columns positions from which date
and time to be picked.
If date and time are from different columns, then use + as delimiter
between date column and time column.
Validation is done only to check if column number exists in the file and not
for the data under that particular column.
If date and time are from different columns, then date/time format sequence
and the column sequence mentioned here should be matched.
Example for Date/Time Format across the Columns:
If date is from column 2 and time is from column 3, then input for Date/Time
format is MM/YY+HH:MM:SS and input for Date/Time Column Number is 2+3.
Figure 19: Monitor Wizard - Select Columns
Click Cancel to return to Create File Monitor screen.

Add Click add to add attributes into the Selected Attributes List.
Remove Click Remove to remove the Selected Attribute(s) from the Selected
Attributes list.
Add Composite Only stats attributes will be considered. Click Add
Composite, Add Composite screen is displayed.

Add Composite Attribute Details
Data Point Select the stats attributes from the drop-down menu.
Literal Enter the Numerical value for the calculation.
File monitor
Operator Lists mathematical and logical operators which can be used in
conjunction with Data points and Literals to construct a formula
Append Click Append, to move the data point /Literal/Operator selected,
to the right-hand pane.
How to add composite attribute?

Stats1 + Stats2
Stats1 and Stats2 are the stats attributes.

To construct the formula Stats1 + Stats2:
1 From the Data Point drop-down menu, select attribute Stats1, and then click
Append.
2 From the Operator drop-down menu, select + operator and then click Append.
3 From the Data point drop-down menu, select attribute Stats2 and then click
Append.
Formula will be constructed on the right-hand panel.
Stats1 + 100
Stats1 is the stats attributes.

To construct the formula Stats1 + 100:
1 From the Data Point drop-down menu, select attribute Stats1, and then click
Append.
2 From the Operator drop-down menu, select + operator and then click Append.
3 Enter 100 in the Literal field, and then click Append.
Specifying AVAILABILITY attribute

Note
This monitor has the AVAILABILITY attribute support. To define the Availability
attribute, you have to define composite attribute with logical operators. The display
name for this attribute should be AVAILABILITY in capital letters.
The availability attribute is either 0 or 100. The availability attribute records 0, if the
constituent Stats attributes records NO DATA. If the availability is 0, then all the
stats attributes records NO DATA irrespective of the value retrieved from the file.
File monitor
For example, if we have two stats attributes, Stats1 and Stats2, to record the
availability of 100% for this monitor, consider the following:
&& - both Stats1 and Stats2 should have the value 100, in case availability
attribute is constructed using Stats1 && Stats2.
|| - Stats1 or Stats2 should have the value 100 in case availability attribute is
constructed using Stats1 || Stats2.
Click OK to construct the composite attribute. If formula is not valid or data
entered is invalid, an error message Formula is not well Formed is displayed.
Figure 20: Selected Attributes
Data Source For monitor internal use.

Attribute Display Name Unique name of the attribute as it will be displayed in
configuration screens and graphs in BMC ProactiveNet. By default, the Attribute

Display Name is blank, but it is mandatory to choose a unique, logical name.
Measure As - Select the type of calculation to be done on the attribute value. This
column supports Rate, Delta, Raw, bytes to Mb, and bytes to Kb. Ideally, Rate and
Delta measures must be used for variables that return counter types.
displayed.
Raw - Data value retrieved is recorded without any further processing. Record
the data as raw when no further processing is required.
Examples on How to Calculate Raw and Delta Values for

any monitor?
Delta calculation:
File monitor
= 60 30
= 30
Rate Calculation:
= (60 - 30) / 60
= 0.5 per sec.
data point.
Delta Calculation:
= 30 10
= 20
= 60 - 30
= 30
Rate Calculation:
= (30 - 10 ) / 30
= 0.666 per sec
= (60 - 30
) / 30
= 1 per sec.
Bytes to Mb Retrieved value will be converted from bytes to megabytes.
File monitor
Bytes to Kb Retrieved value will be converted from bytes to kilobytes.

Scale - Select the value the raw statistics data and configuration (numeric only)
data has to be multiplied with. This can be used to scale down or scale up the
statistics data and configuration data. By default, it is set to 1. For example, you
can change a value set in bytes to kilobytes or megabytes by using the Scale and
Unit fields. The upper boundary of an attribute value is (2147483647/1000). For
example, if the value retrieved for an attribute is 2147483647, the scaling value can
be entered as 0.001 (if you want to divide it by 1000).
Note
in log file.
Unit - Select the unit from the list. You can also specify the units. After creating
the monitor the newly specified unit will be available in the list, for other monitor
types also. Ensure that none of the below-mentioned string or characters are given
while defining a new unit:
$$ * + , ; ^ & " < > '


File monitor
10% of data points.
normal range and would skew the hourly calculations if included. Instead, the
Attribute Type Indicate whether the attribute is configuration, statistic, or input
attribute.
7.5 Onwards, the system automatically validates and assigns the attribute type as
Record Value - Check this option for the attributes to be considered for data
collection. If this option is unchecked, then the attributes will not be considered
for data collection.
Note
Stats attribute will record data only if input attribute matches with file contents,
else stats attributes will record no data.
Test Click Test to validate data collection for the File attributes selected before
be retrieved from the log file with the input attributes entered. This also helps to
verify whether the attribute value exceeds the graphing limits; thus, you can
appropriately adjust the scale factor before creating the monitor type.
After successful Test, Test Poll Results dialog box displays the results. Click Close
to close Test Poll Results screen.
2 Click Cancel to close the Monitor Definition File Monitor Wizard without
creating the new monitor.
The new monitor type is available from the Administration Console in the category
chosen when the monitor type was created. You can use this monitor type to add
instances.
Example
Following is an example to record response code and bytes transferred from apache
access_log using File Monitor:
File monitor
1 Select Tools => Monitor Wizard => File

2 Click Add to launch Monitor Definition-File-Create window
Figure 21: Monitor Definition-File-Create window
3 Select the Source Agent from where the access_log file needs to be loaded.
4 Enter the directory name where the access_log file is located and click on load
button to load all files from the directory.
5 From Select File drop-down menu, select access_log file.
File monitor
6 Select Space as the delimiter and check Treat consecutive delimiters as one.
Figure 22: Select Attributes
7 To record response code and bytes transferred, select columns 9 and 10, and click
OK.
8 Click on Add button to add the attributes.
9 Click on Test button to validate data collection for the selected attributes.
10 Click on Create Monitor button to create the monitor type.
11 For creation of a File Monitor Instance, see Creating a File monitor instance on
page 179.
If the response code and bytes transferred from a specific IP address is to be
monitored, mention that IP address as an input attribute.
File monitor
Follow steps 1 through 6, select columns 1, 9, and 10 and click OK.

Figure 23: Select Columns
Figure 24: Selected Attributes
Change the Attribute Type of IPAddress to Input.

Click on Test button to validate data collection for the selected attributes.
Enter the IP Address and click OK.
Click on Create Monitor button to create the monitor type.
File monitor
Creation of file monitor instance

Figure 25: Instance Creation window
Refer Creation of File Monitor Instance for more details.

Enter the IP address in the IP Address Field to monitor the response code and bytes
transferred from that specific IP address.
Creating a File monitor instance

Once the new monitor is registered in the BMC ProactiveNet system, an instance of
it can be created via the BMC ProactiveNet Administration Console. The new
monitor will appear in the menu of the Administration Console in the category
chosen when it was created. This monitor instance can be created or deleted via the
Administration Console on any of the applicable resources in the system.
Follow the steps given below to add an instance of the new monitor using an
To create a File monitor instance

1 From the Administration Console, expand the Device folder until you see the
device on which you want to add the monitor instance.
File monitor
4 On the Configuration tab, specify an instance name and other parameters, as

required.
5 Click Next.
6 In the Control tab, modify the default values of the control attributes, if required.
Collect Data - Select/clear check box to enable/disable data collection for the
monitored component. By default, data collection is enabled (check box selected).
Statistics Poll Interval - Specify the time interval between two consecutive
Statistical data polls. Default is 15 minutes.
Statistics Poll Timeout - Specify the time-out period for each poll of statistical
data. Default is 2 minutes.
Configuration Poll Interval - Specify the time interval between two
consecutive Configuration data polls. Default is 24 hours (One day).
Configuration Poll Timeout Specify the timeout period for each
configuration data poll. Default is 2 minutes.
The monitor instance will be listed under the selected group.
Button options
Skip - If you have selected multiple monitors from the Summary of Created
Monitors window or there are default monitors associated with the device, click
Skip to ignore monitors you do not want added and automatically move to the
next part of the Configuration process.
Close Click Close to close the instance creation window without applying any
changes.
Next - Click Next if there is only one monitor instance to add.


File monitor
Editing a File monitor type

Once a File Monitor type has been created, you can edit the monitor type to include
new attributes, delete, or edit existing attributes.
To edit a File monitor

1 In the Administration Console, navigate to Tools => Monitor Wizard => File.
Create File Monitor Wizard.
Deleting a File monitor type

Follow the steps given below to delete a File monitor.
To delete a File monitor

1 In the Administration Console, navigate to Tools => Monitor Wizard => File.
2 Select the monitor you want to delete, click Delete.
BMC ProactiveNet deletes the monitor from both the Monitor Wizard and the
system.
No Data and No Response conditions

NO_DATA - Results in nothing being plotted, i.e., a data gap.
Use last line inserted - NO DATA will be recorded if the monitored file is not
refreshed since last poll or if the input attribute does not match with the file
contents. Composite attribute will record NO DATA if at least one of the
constituent stats attribute records NO DATA.
Use TimeStamp NO DATA will not be recorded if the monitored file is not
refreshed since last poll. An appropriate message is logged.
NO_RESPONSE - Results in a dashed line being plotted.
NO RESPONSE will be recorded if the monitored file is unavailable at the

specified location.
File monitor
Limitations
Stats attributes with negative values are allowed; however, only if the value
returned is -1, no data is collected.
File Monitors do not support circular log files.

File Monitors do not support binary files.
File Monitors does not list files from mapped drives.
Monitor type supports collecting data from maximum of five files.
Special notes
In case of Use Stamp from file, basically the file is read batch-wise. By default, size
of 10 MB data will be read at a time. The size of the buffer can be changed by
changing the value for the following property: installDirectory /pw/monitors/shared/
GenMonBase/GenMonBase.conf max.buffer.size.in.mb=10
Load Attribute Choice option is displayed in the following conditions:

If the monitor type is defined for one file and it has at least one input attribute.
If more than one input attributes are added from one file, then the load
attribute choice is displayed for all the input attributes.
Before upgrading to 7.5 version, if the file monitor types and its instances are
created with input attribute (monitor type defined for single file only). Then
update that monitor types, after upgrading to 7.5 version.
For multiple load attribute choices, following conditions have to be met:

Loading the choices for first input is always dependent on the file only.
Loading the choices for the second input is dependent on file and the value
entered for the first.
Loading the choices for the subsequent inputs is dependent on the previously
entered input attributes.
Input attributes are displayed in the order they are added while creating
monitor type.

pronet.conf.

Use the Monitor Wizard to create a new Windows Management Instrumentation
monitor. This monitor can collect data from Microsoft Windows NT, 2000, 2008,
Vista, and XP systems using Windows Management Instrumentation (WMI) service.
To create this monitor, the WMI service Agent must be running on the target device.
Note
User Name and Password is mandatory for remote monitoring while for local
monitoring User Name and Password is not mandatory. For Windows Vista and
Windows 2008, user name and password of the BMC ProactiveNet Agent's Service
Log On account is mandatory.

WMI service is preinstalled in the following: Windows Server 2003, Windows XP,
Windows Me, Windows 2000 and WinVista.
Additional configuration is required for Windows XP and 2003
Microsoft has incorporated a stringent security model in Windows XP and 2003. All
remote connections to a Windows XP (configured as Workgroup) computer,
irrespective of the authentication credentials at either end, will be authenticated as
Guest connections. Hence, WMI requests to Windows XP computers would fail.
Note
If a Windows XP computer is configured to be part of a Domain model, there are no

such issues.
The suggested fix to overcome this problem is to moderate the default security policy.
To modify security settings

1 Go to Start => Control Panel => Administrative Tools => Local Security Policy
=> Local Policies => Security Options.
2 Locate the following policy: 'Network access: Sharing and security model for local
accounts'.
3 Change the default value as follows: 'Guest only local users authenticate as
Guest' to 'Classic local users authenticate as themselves'.
WMI Core1.5 must be installed manually on the following: Windows NT 4.0
Windows NT
The out-of-box Windows NT SP4 platform does not have WMI service installed.
WMI installation can be downloaded from Microsoft Web site. Download
wmicore.exe and ensure it is successfully installed.
Note
There is a known bug that prevents access to Windows XP/2003 computers from
Windows NT4 computers. That is, running the monitor with source agent as NT 4
computer and the target IP that of Windows XP/2003 computers fails. Hence, this
scenario is currently not supported.
Refer knowledge base article 282949.
Creating a Windows Management Instrumentation monitor

type
Complete the steps given below to create a Registered Windows Management
Instrumentation Monitor.
To create a Windows Management Instrumentation monitor

2 Navigate to Tools => Monitor Wizard => Windows Management
Instrumentation.
The Monitor Wizard screen is displayed and existing monitors (if any) are listed.

Monitor Display Name - Specify a unique name for the monitor as this will be
displayed across BMC ProactiveNet system.
Monitor Name - Specify a unique name, which can be cryptic, for the monitor.
(For internal use only)
Monitor Category - Select the category in which the new monitor must be
displayed in the Administration console. This also establishes correlations for

the Probable Cause engine. Alternatively, click New to create a new monitor
subcategory and display it under the Other category in the Administration
Console. For more information, refer Monitor New Subcategory topic.
Source Agent - Select the BMC ProactiveNet Agent on which the monitor must
be created. Select any BMC ProactiveNet Agent here that can communicate
with the WMI service on the target computer. You can change the agent later
when defining new instances to monitor WMI services on different systems.
Target IP/Host Name - Select the host IP of the computer where the WMI
service you want to monitor is running. IP value specified here is used only for
defining the monitor type. You can define a different value when defining
instances to monitor WMI services on various systems.
User - Specify a user name with administrative privileges to access the target
host. The value you specify here is used only to define the new monitor type.
You can specify a different value when defining different instances to monitor
WMI services on various systems.
Password - Specify the password corresponding to the user name specified above.
Load Namespaces - Click this to load the various WMI namespaces on the system.
Add - Click this to add selected WMI namespaces to the Selected Attributes
section.
Remove - Click this to remove selected namespaces from the Selected
Attributes section.
4 Click Load Namespaces. In 7.5, this attribute is enhanced to load namespaces

manually. Enter either exact namespace (case sensitive) or partial/initial
namespace (case insensitive) and then click load button or press enter to list all
the namespaces available.
Namespaces - WMI namespace under which classes are arranged.
Class - Name of the WMI class.
Instance - Instance of the WMI class. This can be modified during monitor
instance creation if all 'properties' from a single 'class' are selected.
Properties - Properties associated with the specified WMI class.
5 Click Add. The Selected Attributes section is populated with the attributes that
you have selected.
Figure 26: Selected Attributes section
Namespace - The WMI namespace under which classes are arranged.

Class - Name of the WMI class.
Instance - Instance of the WMI class.
Property - Properties associated with the specified WMI class.
Attribute Type - Indicate whether the attribute is statistic or configuration
parameter.
7.5 onwards, the system automatically validates and assigns the attribute type as
Note
Only the first 254 characters of a Output Configuration attribute are displayed in

logical name.
Measure As - Type of computation on the result data. This column supports
Rate, Delta, and Raw data types. Ideally, Rate and Delta measures must be
used for variables that return counter types.
displayed.
Record the data as raw when no further processing is required.

monitor
Delta calculation:
= 60 30
= 30
Rate Calculation:
= (60 - 30) / 60
= 0.5 per sec.
data point.
Delta Calculation:
= 30 10
= 20
= 60 - 30
= 30
Rate Calculation:
= (30 - 10 ) / 30
= 0.666 per sec

= (60 - 30
) / 30
= 1 per sec.
Scale - Value raw statistics data and configuration data has to be multiplied with.
This can be used to scale down or scale up the statistics data and configuration
data. For example, you can change a value set in bytes to kilobytes or megabytes
by using the Scale and Unit fields. The upper boundary of an attribute value is
(2147483647/1000). For example, if the value retrieved for an attribute is
2147483647, the scaling value can be entered as 0.001 (if you want to divide it by
1000).
Note
in log file.
Unit - Unit of measurement for a statistics and configuration data attribute. Select
the unit from the list. You can also specify the units. After creating the monitor the
newly specified unit will be available in the list, for other monitor types also. The
unit can be changed, as required. This could be very useful, for example in
situations where you have to change the unit of measurement from KB to MB.
Ensure that none of the below-mentioned string or characters are given while
defining a new unit:
$$ * + , ; ^ & " < > '
displayed on the graph by default. If no attribute is selected, an error is displayed

when you attempt to create the monitor. The attributes not selected here are still
displayed in the Custom Graph area on the Operations Console, but need to be
manually selected on the graphing page.
10% of data points.
Test - Click Test to validate data collection for the WMI attributes selected before
be retrieved from the WMI service with the input attributes specified. This also
helps to verify whether the attribute value exceeds the graphing limits; thereby,
you can appropriately adjust the scale factor before creating the monitor type.
Note
2 Click Close.
Creating a Windows Management

Instrumentation monitor instance
Once a new Windows Management Instrumentation monitor is registered in the
BMC ProactiveNet system, its instance can be created via the Administration
Console. The new monitor instance is listed in the category selected during monitor
creation.
Follow the steps given below to create an instance of the new monitor using an
To create a Windows Management Instrumentation monitor instance

1 In the Administration Console, expand the Device folder until you see the device
on which you want to create the monitor instance.
3 Drill-down and select the monitor you want to use.
4 In the Configuration tab, specify the instance name and other parameters, as
required.
From 7.5 onwards, TargetIP/HostName field is changed to Target Device for
all VAM monitor instances. Prior to 7.5, If DNS Name is given to TargetIP/
HostName; it used to resolve to IP Address and was displaying this stored IP
Address while editing the instance. But now from 7.5 onwards it will retain the
DNS name in Target Device field when user edits the instance.
5 Click Next.
6 On the Control tab, modify the default attribute values, if required.
Skip - If you have selected multiple monitors from the Select Monitors to
Create window, or there are default monitors associated with the device, click
Skip to ignore monitors that you do not want added and automatically move to
the next step of the configuration process.
Next - Click Next if you want to add a single monitor instance.


8 Refresh the Device folder to display the new service monitor created.
Setting up Agentless monitoring for a WMI monitor

You can set up a WMI monitor for the Windows computer without installing the
BMC ProactiveNet Agent on it.
To setup agentless monitoring

1 On the Windows computer to monitor, log on with Administrative privileges.
a Run the command services.msc from the command prompt or go to Start =>
Control Panel => Administrative Tools => Services.
b Select ProactiveNet Agent Service.
c Double-click or on right clicking ProactiveNet Agent Service, select Properties.

d Click on Log on tab.
e On selecting This Account, enter a valid user name. Enter Password and reenter password to Confirm Password
f Click on Apply.
g Click on OK.
2 Restart the Service for the changes to take effect.
Editing a WMI monitor type

Once the Windows Management Instrumentation monitor is created, editing its
properties is quite simple.
To edit a WMI monitor

Windows Management Instrumentation.
2 Select the monitor whose properties you want to edit and click Edit. For input
descriptions, refer Create a Windows Management Instrumentation Monitor Type
section.
3 Make changes as required and click Update Monitor.
BMC ProactiveNet registers the changes made to the monitor properties.
Delete a WMI monitor type

Perform the following procedure to delete a WMI monitor.
To delete the Windows Management Instrumentation monitor

Windows Management Instrumentation.
A window listing all Windows Management Instrumentation monitors created
is displayed.
2 Select the Windows Management Instrumentation monitor you want to delete,

and click Delete.
BMC ProactiveNet deletes the monitor from both the Monitor Wizard and
system.
Special notes

This option is available for Windows OS only. These monitors can collect all data
types provided by Windows Performance Counters.
For Local Monitoring: Run the Windows Agent on the system to be monitored.
For Remote Monitoring: Run the Windows Agent on the source IP. Ensure
administrative rights are available on the target computer.
Setting up Agentless Monitoring for a Windows Performance

Counter monitors
You can set up a Windows Performance Counter monitor for the Windows
computer without installing the BMC ProactiveNet Agent on it.
To set-up Windows Performance Counter Monitor for the Windows computer

without a BMC ProactiveNet Agent
1 On the Windows computer to monitor, configure a valid user account with
Administrative privileges.
2 Select a BMC ProactiveNet Agent (Windows) computer and configure BMC
ProactiveNet Agent service to run under the valid user account (the account set
up in step 1).
a Go to Start => Settings => Control Panel.
b Double-click Services.
c Double-click BMC ProactiveNet Agent Service to view Service Properties.
d Click Log On tab.
e Select This Account, and enter the NT User account and Password in the
respective fields (the account set up in step 1).
f Restart the BMC ProactiveNet Agent service.
3 Launch BMC ProactiveNet Administration Console, and create a device on the
Agent for the non-agent computer to monitor.
a Right-click Devices and click Add Device.
b Select the Device Type for the remote computer, and specify its name.
c Click Finish.
Close and open the Devices node, to view the non-agent computer in the
Devices list.
4 Return to the Administration Console, and explore the Devices node.

5 Right-click the non-agent computer, and navigate to click Windows Performance
Counter.
6 On the Windows Performance Counter Monitor Create screen,
a Select BMC ProactiveNet Agent computer (set up in step 2) as the Source Agent.
b All other input fields are the same as for the basic monitor.
7 Click Finish to create the Windows Performance Counter Monitor for the nonagent computer.
Creating a Windows Performance Counter monitor type

Complete the steps given below to create a Registered Service for Windows
Performance Counter Monitor:.
To create a Windows Performance Counter monitor

2 Navigate to Tools => Monitor Wizard => Windows Performance Counter

4 Enter the Input Requirements.
Monitor Display Name - The unique name of the new monitor as it will be
displayed throughout the BMC ProactiveNet system. This is restricted to 58

characters.
Monitor Name - For internal use only, the unique name for the new monitor
that can be cryptic and cannot exceed 17 characters with no spaces.
Monitor Category - Choose the category under which the new monitor will
Console. Refer Monitor New Subcategory topic for more information.
Source Agent - Select source agent here. For local monitoring, this should be
same as the Target IP. For remote monitoring, the source agent selected needs
to have administrative privileges on the remote computer.
Target IP Address - Host IP where data is collected by the given Source Agent.
5 Click Load counters. This populates the remaining fields. Select the appropriate
options.
Performance Object - Names of the Performance Object that contains counters
and instances. In 7.5 and onwards, this attribute has been enhanced to load
performance objects manually. Enter either exact performance object name
(case sensitive) or partial/initial performance object names (case insensitive)
and then click Load button or press Enter to list all the counters and properties
matching available of the entered performance object. The list of object,
instances, and counters is populated based on the performance data collected in
MOMs SDKPerformanceView.
Select Instances - Names of instances of the performance object selected. Note
that this does not define the instance, but only the counters from the target
computer. You can add more than one instance, but it must be done one at a
time. If only one instance is selected, you can change this instance when
creating monitor instances.
Select Counters - Counter names corresponding to the selected Performance
Object.
Note
If a Performance object (for example, .NET CLR Data, .NET CLR
Networking,.NET Data Provider for sqlServer and .NET Data Provider for
Oracle) has zero or more instances, but none present while creating monitor
type using Windows Performance Counter wizard, the wizard does not list the
performance counters for these objects.
6 Click Add.
The Selected Attributes table below is populated with information you entered.
The first three columns display information chosen in the previous step. The
remaining columns can be edited for further refinement of the monitor.
Figure 27: Selected Attributes Table
Counter - Populated based on information from previous step.

Instance - Populated based on information from previous step.
Object - Populated based on information from previous step.
Attribute Type - Indicates whether the attribute is statistic or configuration
parameter.
In BMC ProactiveNet 7.5 and later, the system automatically validates and assigns
the attribute type as either configuration or statistics. Prior to 7.5, the attribute
type had to be validated and assigned manually.
Note
Only the first 254 characters of an output configuration attribute are displayed in

logical name.
Measure As - This column supports Rate, Delta, and Raw data types.
Delta - Difference (change) in data between two polls is recorded and
displayed.
Record the data as Raw when no further processing is required.
Note
Rate and Delta measures should ideally be used for variables that return
counter types.

monitor
Delta calculation:
= 60 30
= 30
Rate Calculation:
= (60 - 30) / 60
= 0.5 per sec.
data point.
Delta Calculation: Value of data point at t+30 = new value at "t+30" - old value at
"t"
=30 10
=20
=60 - 30
=30
Rate Calculation: Value of data point at t+30 = new value at t+30 - old value at t) /
(Poll Interval)
= (30 - 10 ) / 30
= 0.666 per sec
= (60- 30) / 30
= 1 per sec.
Scale - This editable field is the value by which the raw statistics data and
configuration data has to be multiplied. This can be used to scale down or scale
up the statistics data and configuration data. For example, you can change a value
set in Bytes to Kbytes or MBytes using the Scale and Unit fields. The upper
boundary of an attribute value is (2147483647/1000). For example, if the value
retrieved for an attribute is 2147483647, the scaling value can be entered as 0.001
(if you want to divide it by 1000).
Note
in log file.
Unit - Unit of measurement for a statistics and configuration attribute. Select the
unit from the list. You can also specify the units. After creating the monitor the
newly specified unit will be available in the list, for other monitor types also. The
unit can be changed, as needed. This could be helpful, for example, in a situation
where you may need to change the unit from GB into MB. Ensure that none of the
below-mentioned string or characters are given while defining a new unit:
$$ * + , ; ^ & " < > '
Graph Default - At least one attribute must be selected. The attributes selected are
displayed by default when a graph is generated. If none are selected, an error will
be displayed when you attempt to create the monitor. The attributes not selected
here will still be displayed in the Custom Graph area on the Operations Console,
but will need to be manually selected on the graphing page.
Normal Distribution - It is important to understand the significance of this
setting, since it impacts how condensed data, baseline data, and report data are
actually calculated.
10% of data points.
normal range and would skew the hourly calculations if included. Instead the
Test: Click Test to test data collection by the monitor for the attributes selected.
The test results are based on RAW data collected by the monitor.
Note
1 When satisfied with the monitor setup, click Create Monitor.
The system sets up the new monitor and returns to the wizard window.
1 Click Close if you are done with creating the monitor.

The new monitor is now available in the category chosen when the monitor
was being created. You can now use this monitor to add instances.
Creating a Windows Performance Counter monitor instance

After registering the Windows Performance Counter Monitor with the BMC
ProactiveNet system, an instance of it can be created via the Administration Console.
The new Service Monitor is listed under the category selected during instance
creation. This also provides options to edit or delete these instances.
To create a Windows Performance Counter monitor instance

1 In the Administration Console, expand the Device folder until you see the device
on which you want to add the monitor instance.
4 In the Configuration tab, add an instance name and other parameters, as required.
In BMC ProactiveNet 7.5 and later, TargetIP/HostName field is changed to
Target Device for all VAM monitor instances. Prior to 7.5, If DNS Name was
given to TargetIP/HostName; it used to resolve to IP Address and was
displaying this stored IP Address while editing the instance. But now from 7.5
onwards it will retain the DNS name in Target Device field when user edits the
instance.
5 Click Load.
6 Click Next to modify the Control attributes.
7 In the Control tab, modify default values, if required.
Skip: If you have selected several monitors from the Select Monitors to Create
window, or there are default monitors associated with the device, click Skip to
ignore monitors you do not want added and automatically move to the next
step of the configuration process.
Add: Click Add to add the monitor instance listed at the top of the screen, and
Next: Click Next if there is only one monitor instance to add.

Finish: Click Finish at the beginning of the process to automatically add all

9 Refresh the Device folder to show the new Service Monitor Instance.
Editing a Windows Performance Counter monitor type

Once a Windows Performance Counter Monitor has been created, editing it is quite
simple.
To edit a Windows Performance Counter monitor

Create a Windows Performance Counter Monitor Type section.
Note
Configuration attribute type support is available only from version 7.0.
Monitors created prior to this version can have only stats attributes.
7.5 onwards, the system automatically validates and assigns the attribute type
as either configuration or statistics. Prior to 7.5, the attribute type had to be

validated and assigned manually.
3 Make changes as required and click Update Monitor.

BMC ProactiveNet registers the changes made.
Delete a Windows Performance Counter monitor type

Follow the steps given below to delete a Windows Performance Counter Monitor.
To delete a Windows Performance Counter monitor

BMC ProactiveNet deletes the monitor and removes it from the Monitor
Wizard window and the Administration Console. All monitor instances of this
monitor type will also be deleted.
Note
If for some reason the jserver is restarted while deleting a Windows

Performance Counter Monitor, the Delete operation may not get executed
properly.
Exporting monitors
Special notes
Exporting monitors
The Export feature enables you to seamless export custom Monitor Wizard monitors
across different BMC ProactiveNet Servers.
To export monitors
1 Click Tools => Monitor Wizard => Export
This launches a window listing all Monitor Wizard monitors created on the
particular system.
2 Select one, more, or all of the available monitors.

3 Specify the Monitor Bundle File Name. This is the name of the Bundle being
exported.
4 Click Export to export the selected monitors.
5 Click OK on the confirmatory message.
6 Click Close to exit.
Additional information about exporting monitors

The exported monitors are bundled into a single jar. The name of the jar is the same
as specified in the Export Dialog. The jars created during export will be available in /
usr/pw/monitors/downloads (on the server) for you to import to a different setup.
During import, the monitors being imported are validated for the database tables,
directory names and the supported Operating systems.
On import, the global absolute threshold values, global signature threshold values,
and global abnormality threshold values are also imported.
Note
After exporting the Monitor from one server to another, Jserver needs to be
restarted to view the threshold set in HTML UI.
Refer Install Package topic for more information on this utility.
Users can export a user-defined monitor type, which creates a package. This package
can be imported to another BMC ProactiveNet Server using the Install_package
command. Refer Install Package topic for details.
BMC ProactiveNet does not support export of Resource Pool monitors, and they are
not be available in the Export window.
Limitations for exporting monitors

7.1 export features will not work for the thresholds with the properties of ==,=<,=>.

Custom monitors (monitors created using the Monitor Wizard) can be set to be
displayed under user-defined categories.
While creating a new monitor using the Monitor Wizard, you can choose to group it
under one of the pre-defined monitor types available or create a new subcategory.
This subcategory gets listed under the Other monitor category.
Creating a new subcategory to group custom monitors can be useful in the following
situations:
If none of the predefined monitor categories available are appropriate
When there are a large number of custom monitors, the Other monitor category
can get too long
Creating a new monitor subcategory

All Custom Monitor Definition screens allow you to choose a predefined Monitor
Category with which to associate your custom monitor. However, if required, you
can choose to define a new monitor subcategory to associate your custom monitor with.
Figure 28: Access Add New Monitor Category window
To define a new monitor subcategory

1 From the Monitor Definition screen, click New next to the Monitor Category field.
The Add New Monitor Category window is displayed.
2 Specify a name for the subcategory.

The subcategory that you define here is always listed under the predefined
Monitor Category 'Other'.
Limitations
New monitor categories cannot be created for Resource Pool Monitors.
There is no utility currently available to edit a user-defined monitor category.
To edit a user-defined monitor category manually,

Navigate to the individual monitor directory under /usr/pw/monitors/monitors
and edit the <monitor name> monitor group file to reflect the new category
name and in the prescribed syntax.
Restart the jserver.

There is no utility available to delete a user-defined monitor category.
To delete a monitor category manually, delete all the monitor types associated
with the category.
A newly created subcategory will not be displayed immediately in the Monitor
Category list in the same session.
Compile MIB
Compile MIB
MIB Compiler tool is used to compile Standard MIBs and other enterprises MIBs.
These compiled MIBs can then be used by the SNMP Monitor Wizard to create
SNMP monitors.
MIB Compiler features

A Graphical Interface to compile SNMP MIBs.
MIBs RFC1155-SMI, RFC1213-MIB, SNMPv2-SMI, SNMPv2-CONF, SNMPv2-TC
CAIUxOS, CAIW2KOS-MIB, and CAINT4OS-MIB are shipped with the tool.

These are sample MIBs for reference. For more specific requirements, compile
customized MIBs as required.
Compiled MIBs are stored in a server location as individual serialized objects.

Identifies compilation-related issues such as Duplicate MIBs, IMPORTS clause
failure.
Synchronization problems that may occur due to compilation from multiple BMC
ProactiveNet Administration consoles are resolved by using locks. Hence,

multiple BMC ProactiveNet Administration consoles cannot compile a MIB
simultaneously.
Note
Standard RFC MIB definitions can be downloaded from the Internet and
Enterprise MIB definitions can be downloaded from the respective company
Web sites.
Limitation and workaround

Limitation: MIB Compiler does not list files from mapped drives.
Workaround: Manually provide complete path for files from the mapped drives.
Using the MIB Compiler

The MIB Compiler feature is activated from the Administration Console.
To use the MIB Compiler

1 Log into the Administration Console using your login name and password.
2 Select Compile MIBs option from the Tools menu.
Note
MIBs shown in the Compiled MIBs list box, are shipped by default.
3 Click Compile New to access the FileChooser window. In the window select the
MIB file(s), which is/are to be compiled.
The MIB file needs to reside on the system where BMC ProactiveNet
Administration Console is running.
4 Click Compile.
If the compilation of the MIB is successful, the compiled MIB is stored as a
serialized object in /usr/pronto/usr_apps/mibs on the BMC ProactiveNet Server

computer.
In case an existing compiled MIB is complied again (edited), BMC ProactiveNet
compiles the MIB and keeps it in memory. The existing MIB is not over-written
with changes. To save the new compiled MIB, delete the existing MIB before
compiling the MIB with changes.
5 Click Refresh to reload the list of compiled MIBs.

6 Click Cancel to close the tool.
Error messages
If compilation fails, due to a syntax error, the line number and error log are
displayed. In all other cases, the error message is displayed.
If there is an error due to MIB dependencies, first compile the requested MIB and
then try to recompile the MIB.

You can import monitor types for the following adapters:
BMC PATROL
HP OpenView (HP OVO)

System Centre Operations Manager (SCOM) 2007
To import monitor types

2 Navigate to Tools => Import Adapter Monitor Types And Add Adapter =>
adapterName.
3 Follow the steps detailed in Import monitor types on page 222.

After a script monitor is defined, the corresponding script(s) and any dependent
file(s) need to be deployed on the required agent(s) so that monitor instances may be
created and run from those agents. Script(s) and any dependent file(s) needed for the
operation of Script DDs may also need to be deployed on required agent(s) in order
to run those DDs on those agent(s). A need may also arise to distribute arbitrary
file(s) (Example: keystore file containing new self-signed or CA-signed certificates)
from BMC ProactiveNet Server to various connected agents. This can be done using
the transfer files to agents functionality. Transfer Files to Agents enables the user to
select files that need to be transferred to agent(s) and optionally also specify a single
destination directory on the agent(s) where all the files will be transferred. The user
can also select the agent(s) to transfer file(s). If you do not have the proper access
rights, then the Transfer files to agents feature is disabled.
Note
This feature is available only on local installations of the BMC ProactiveNet

Administration Console and is not supported on remote installations of the BMC
The Transfer Files to Agents feature can be accessed from the Administration Console.
To transfer files to agents

1 Log into the Administration Console using your login name and password.
2 Select Transfer Files to Agents option from the Tools menu.
This functionality can also be accessed from:
Script: Monitor Wizard under Tools menu.

Script: Diagnostics Wizard under Tools menu.
Figure 29: Transfer Files to Agents screen 1
The first screen that is displayed enables the user to choose the files to transfer
and select the agents to transfer the files to. Optionally the user can also choose to
explicitly specify the destination directory on the agent.
3 Click Browse to choose the files that need to be transferred. Files can be specified
by inputting their complete locations (absolute filenames) into the text box
(multiple files must be separated by commas with no spaces between filenames).
This field is mandatory. If the input is not given, an error message is displayed.
4 Select Specify Destination on Agent(s) and enter the destination directory name.
This is optional and can be used when the desired destination directory is
different from the default value of AgentInstallDir/pw/pronto/usr_apps/bin. If
not selected the default destination directory will be used.
Note
When explicitly specifying the destination directory on the agent, the entered
text will be appended to the AgentInstallDir/pw directory (Example: if a

particular agent was installed on /apps/agent1 and if the specified destination
directory was scripts, then the actual destination directory will be/apps/
agent1/pw/scripts. Hence the destination directory name should not be
absolute and should not contain the string AgentInstallDir/pw.
When script monitor scripts are being transferred to agents, the destination
directory should not be explicitly specified. Script monitor can only run scripts
from the AgentInstallDir/pw/pronto/usr_apps/bin directory and hence the
Default Destination on agent(s) is the right option to use.
5 After the transfer operation is complete, the selected agents are restarted to enable
their proper operation. In case a restart is not required (Example: in cases where
files transferred do not require an agent restart for correct operation), then the
check box Restart agent(s) after transfer should be unchecked. In most cases an
agent restart is recommended.
Note
Older agents (with versions prior to 7.1) cannot be prevented from restarting.
6 Select the Operating System using Select the OS filter for agent(s). This will be
useful when many agents are configured on Proactive Server. A list of connected
agents corresponding to the selected operating system is displayed in the table.
7 Select the Agents from the table. This input is mandatory and at least one agent
must be selected. If the input is not given, an error message is displayed.
8 Click Next.
BMC ProactiveNet opens Transfer File(s) to Agent(s) confirmation screen.
File(s) selected for transfer, Destination on agent(s) and Agent(s) selected are
listed in this screen. This enables you to verify the selection to ensure correctness.
9 Click Close if you want to abort transferring the files.

10 Click Previous to go back to the first screen.
11 Click Transfer to proceed with the file transferring.
BMC ProactiveNet opens Transfer File(s) to Agent(s) status screen.
Once the transfer operation is complete, the View Status button is enabled.
12 Click View Status to view the status of file transfer.
BMC ProactiveNet opens Transfer File(s) to Agent(s) transfer details screen.
Verify the details of the file transfer operation. Agents to which, files could be
transferred correctly will display Success in their Status column. Agents to
which, files could not be transferred correctly will display Failure in their
Status column and their Detailed Status column will display the exact reason
for the failure. The following detailed statuses are supported at this time.
Table 3: Detailed statuses
No
Detailed Status text
Comment
Agent uninitialized
Agent was not initialized or the agent ID was invalid. Retry

the operation.
Initial message sending failed
Agent could not be prepared for the transfer operation.

Check the status of the agent as it might have been
disconnected before the transfer operation started.
File transfer timedout
The file transfer operation timed out. This will occur if the
agent is slow to respond. Check the status of the agent and
retry.
File transfer error
Error occurred while transferring the file. For the exact cause
of the error the debug log files should be examined.
File transfer failed
File transfer operation failed. For the exact cause of the error
the debug log files should be examined.
Update failed
Agent could not process already transferred files. For the

exact cause of the error the debug log files for the agent
should be examined
Update denied
Agent update is not allowed as per the setting of the property

pronet.apps.agent.upgrade. Change the value of the property
pronet.apps.agent.upgrade to true to allow the agent to be
updated with transferred files and retry transfer.
Invalid update package
Package containing files that are to be transferred was

invalid. This should never occur! For the exact cause of the
error the debug log files for the agent should be examined.
Update package unbundling failed Extracting the transferred files from the transfer package
failed. This should never occur! For the exact cause of the
error the debug log files for the agent should be examined.
13 Click Finish.
Note
Files can only be transferred to directories on the agents that are in the agents
install path. For example, if an agent is installed in /home/agent1, then files

transferred to this agent can only be transferred to locations under the /home/
agent1/pw hierarchy and it is not possible to transfer file to, for instance, files
to /usr, /, /home/agent1 or other directories on the agent computer.
Multiple files can only be transferred to one destination directory on the agent.
If each file needs to be transferred to a separate directory then this can only be
done one file at a time.
Example:
The following example describes a possible use for the Transfer files to agents
functionality.
1 A keystore file (pnagent.ks) containing a new self-signed certificate needs to be
transferred to all connected agents. This can be done by executing the following
steps
2 Invoke the functionality from the Tools Menu by selecting the Transfer Files to
Agents menu option. This invokes the first screen of the functionality.
3 Click the Browse button which displays a File Chooser dialog. Navigate to the
location of the keystore file and select it.
4 Select the Specify destination on agents(s) radio button and enter the following
text into the text field pronto/conf.
5 Select the Select all agents checkbox located at the bottom of the table containing
the list of all connected agents. This will select all agents in the list.
6 Click the Next button. This displays the confirmation screen where the
information entered in the first screen can be verified. If this information is correct
then click the Transfer button.
7 The next screen shows the status of the file transfer operation. Once this operation
is complete, the View Status button is enabled. Click this button which displays
the final screen.
8 The final screen displays the status of the file transfer operation for each selected
agent. If the status was Failure then the Detailed Status column shows the exact
failure reason.
9 Verify that the selected files were transferred to the correct destination on the agent.

The Monitor Wizard of BMC ProactiveNet helps to create custom monitors easily
and quickly to meet specific requirements. By default, BMC ProactiveNet lists these
monitors under the Other tab in the Administration Console. However, as the
number of such custom monitors/APIs increases, it becomes essential that we
organize these monitors for easy access via the GUI.
The monitor creation (using the Monitor Wizard) process enables you to select a
category for the new monitor. For Example, Application => App Servers. By default,
the monitor category is 'Other'.

In addition to selecting one of the predefined categories, you can also create and
specify your own monitor categories. This setting controls where the monitor
appears in the Add Monitor menu, and how the monitor is correlated in Probable
Cause Analysis.
To create new categories of monitors

1 Edit /usr/pronto/conf/monitor_groups
To add a single top-level category, example: CompanyXYZ, add the following
line anywhere in the file.
CompanyXYZ | CompanyXYZ
To create subcategories underneath the new top-level category, change the

above line to:
CompanyXYZ | CompanyXYZ | Sub1, Sub2, Sub3
2 Edit *.monitorGroup file in each custom monitor directory under /usr/pw/

monitors/monitors and add the following line:
CategoryName | _MonitorUniqueName
For CategoryName, put Sub1, Sub2, or Sub3.

For MonitorUniqueName, specify a unique name for the monitor. Example, If you
are editing the file /usr/pw/monitors/monitors/_FooBar/_FooBar.monitorGroup,
then the MonitorUniqueName is _FooBar.
Note
The monitor wizard monitors name begins with an underscore.
For example:
Sub1 | _MonitorUniqueName
3 Restart jserver by running the following command:

#pw p r jserver
4 After restart, launch the Java Admin.
To verify changes made

1 Right-click a device.
The Add Monitor menu should contain the new top-level menu
(CompanyXYZ) with the specified submenus (Sub1, Sub2, and Sub3).
2 If you selected a Monitor Wizard under Tools => Monitor Wizard, when
creating the new custom monitor, the Monitor Category combo box should
contain additional choices:
CompanyXYZ
CompanyXYZ > Sub1

CompanyXYZ > Sub2
CompanyXYZ > Sub3
So, for new monitors, you can just select the new monitor category in the GUI
(editing _MonitorUniqueName.monitorGroup file is not required).
Example to create a new monitor category

The following example recaps the process detailed above:
We have 10 monitors listed under the Other category. 5 WebMetrics monitors
(WebMetrics1 WebMetrics5) and 5 SalesMetrics monitors (SalesMetrics1
SalesMetrics5).
Requirements:
Add a new top-level monitor category: ProactiveNet
Add two subcategories: WebMetrics and SalesMetrics
Steps to organize the monitors:

1 Add the following line in /usr/pronto/conf/monitor_groups
ProactiveNet | ProactiveNet | SalesMetrics, WebMetrics
2 Edit _WebMetrics*.monitorGroup files for the 5 WebMetrics monitors.

Example, the line added to file: /usr/pw/monitors/monitors/_WebMetrics1/
_WebMetrics1.monitorGroup would be:
WebMetrics | _WebMetrics1
3 Make similar changes for the other WebMetrics and SalesMetrics monitors.
4 Restart jserver by running the following command:
# pw p r jserver
5 Launch the Administration Console after restart.

6 Got to Device => Add Monitor.
The new submenu would be: ProactiveNet => WebMetrics => SalesMetrics
The 5 WebMetrics montors would be listed under WebMetrics and the 5
SalesMetrics monitors would be listed under SalesMetrics.
Similarly, the Monitor Wizard displays 3 new monitor categories that you can assign
new monitors to:
ProactiveNet
ProactiveNet => WebMetrics
ProactiveNet => SalesMetrics
Limitations
Limitation: On upgrade, the /usr/pronto/conf/monitor_groups file is overwritten.
Workaround: Back up this file before the upgrade, and replace it after the upgrade to
retain changes. Changes made to the monitor's *.monitorGroup files are preserved
during upgrade.
5
Working with data adapters
Adapters facilitate the synchronization of performance data collected by specific
monitoring solution into BMC ProactiveNet for further analysis. Adapters that can
import monitor types are BMC PATROL, BMC Performance Manager Portal (BPM),
HP Operations Manager, IBM Tivoli Monitoring, and System Center Operations
Manager (SCOM). Adapters with out-of-the-box monitor types include BMC TM
ART and BMC VMware Adapter.
Data adapters provide a mechanism for external applications to funnel data into
ProactiveNet. A data adapter is like a conduit from an external application such as
BMC PATROL, BMC Performance Manager Portal, Microsoft System Service
Chapter 5 Working with data adapters 215
Operations Manager (SCOM), HP OpenView Operations Manager (OVO), and IBM

Tivoli Monitoring.
Figure 30: Flow diagram for adapters with import monitor type
Figure 31: Flow diagram for out-of-the-box adapters

This section provides terminology from different monitoring solutions and how they
are mapped to BMC ProactiveNet.
Table 4: Product terminology and name mapping
BPM
PATROL
HP OM
IBM Tivoli
Monitoring
SCOM
BMC TM ART BMC

VMware
Adapter
Adapter
display
name
BMC Portal BMC

PATROL
HP OM
IBM Tivoli
Monitoring
SCOM 2007 BMC TM

ART
BMC
VMware
Adapter
Monitor
type term
application
class
application
class
monitor
type
agent type
object type
monitor
type
PATROL
agent
HP OM
agent
ITM
Monitoring
agent
Windows
BMC TM
device
computer
ART
host class of Central host
the selected
object type
Device term element
monitor
type
Prerequisites
Before you configure and use adapters, make sure that you have all of the following
prerequisites installed and operating.
Adapter for BMC PATROL prerequisites

At least one of the BMC ProactiveNet Agents must be configured to run the
Integration Service.
WARNING
BMC does not recommend enabling the Integration Service on the local BMC
ProactiveNet Agent installed with the BMC ProactiveNet Server. The
Integration Service conflicts with BMC ProactiveNet Server processes.
You can enable the Integration Service on the remote Agent during installation or
you can enable the Integration Service after installation. For instructions, see the
Prerequisites
Ensure that you have credentials necessary to connect to the Integration Service.
The versions of the Integration Service and Integration Service CLI must be the same.
Adapter for BMC Performance Manager Portal prerequisites

BMC Performance Manager Portal version 2.6 or above.
BMC Performance Manager Portal must be running.
The user account to be used for importing the adapter must:
exist in the BMC Performance Manager Portal
have access rights to the web service running on the portal
have access rights to the BMC Performance Manager Portal data store being used
The instance level query patch must be present at the portal end.
If the appropriate BMC Portal fix (patch) is not applied, the BMC ProactiveNet
Administration console displays the following message while creating a new
adapter or while editing the existing adapter:
ProactiveNet is unable to create the BMC Portal Adapter because
the configured BMC Portal does not have the required Instance
Level Query patch installed. Please contact BMC Support to obtain
the required patch for BMC Portal.
Update the following patches for the instance level query:

For version 2.6.00, apply patch 2.6.00.080. To apply the patch go to:
2.6.00\2.6.00.030\2.6.00.060\2.6.00.080
For version 2.7.00, apply patch 2.7.00.040. To apply the patch go to:
2.7.00 or 2.7.00.050
Verifying adapter for HP OM prerequisites

The BMC ProactiveNet adapter for HP OM requires the following component
installations on the Integration Services computer for successful data collection:
An HP OM agent
Prerequisites
(for Windows) HP Performance Agent 4.7

(for Solaris) HP Performance Agent C.04.70.000
(for Linux) HP Performance Agent C.04.71.000
(for IBM AIX) HP Performance Agent C.04.70.000
(for all platforms) HP Operations Agent 08.52.006
Enable the Integration Service during ProactiveNet Server installation. For details,
refer to the procedure in the BMC ProactiveNet Getting Started Guide.
At least one of the BMC ProactiveNet Agents must be configured to run the
WARNING
BMC does not recommend enabling the Integration Service on the local BMC
ProactiveNet Agent installed with the BMC ProactiveNet Server. The
Integration Service conflicts with BMC ProactiveNet Server processes.
You can enable the Integration Service on the remote Agent during installation or
you can enable the Integration Service after installation. For instructions, see the
Note
BMC adapters for BMC PATROL, HP OM, and BMC Performance Manager
Portal use the same Integration Services. You can use a single Integration
Service for any combination of the adapters.
You can use the provided XML files for common SPIs, or edit the files for your
specific requirements. You can also create an XML file for custom SPIs. If you plan
to use SPI XML files, you must prepare them before you import them into HP
OM. For details, see XML files for SPIs on page 294.
Verifying adapter for IBM Tivoli Monitoring prerequisites

The BMC ProactiveNet adapter for IBM Tivoli Monitoring requires the following
conditions for successful data collection:
IBM Tivoli Monitoring Monitoring 6.1 or 6.2
In the IBM Tivoli Monitoring application, ensure the following:
A user name and password are defined for Simple Object Access Protocol (SOAP)
Prerequisites
SOAP is configured without a Secure Sockets Layer (SSL)

Enable the Integration Service during ProactiveNet Server installation. For details,
refer to the procedure to enable the PATROL Proxy in the BMC ProactiveNet
Note
During ProactiveNet Server installation, select Enable Patrol\HP OM Proxy to
enable the Integration Service, or follow the instructions to enable the
Integration Service for a Windows agent. BMC adapters for BMC PATROL, HP
OM, and IBM Tivoli Monitoring use the same Integration Service and you can
use a single Integration Service for any combination of the adapters.
Prepare XML files to import IBM Tivoli Monitoring agents (for details, see XML
files for IBM Tivoli Monitoring agents on page 306).
Adapter for System Center Operations Manager (SCOM) 2007

prerequisites
The root management server (RMS) user name must be specified to load the
SCOM objects.
User accounts created in active directory must be a member of the domain user
group.
.NET 3.0 must be present on the BMC ProactiveNet Agent. The BMC ProactiveNet
Agent computer must be running Windows 2003 or higher.
SCOM 2007 or higher should be present and running on the same computer as the
BMC ProactiveNet Agent.
Adapter for BMC TM ART prerequisites

The adapter for BMC Transaction Management Application Response Time (BMC
TM ART) requires a fully deployed and functional installation of BMC TM ART for
successful data collection.
The following BMC TM ART versions are supported:
For synthetic transaction monitoring: BMC TM ART version 3.6 with latest
patches, including patch PATXZ.3.6.00.C26b
For real and synthetic transaction monitoring: BMC TM ART version 3.7 with
latest patches, including patch PATXZ.3.7.00.C09
For details about implementing a BMC TM ART environment, refer to BMC

Transaction Management Application Response Time Central Installation and Setup Guide
and User Guide.
BMC VMware Adapter

The BMC VMware Adapter requires the following environment for successful data
collection:
The Virtual environment managed by Virtual Center 2.5 and/or ESX Server 3.5.X
or higher.
All the ESX server (hosts), Cluster Compute Resources, Resource Pools and the
Virtual Machines are auto discoverable.
VMware tools must be installed on all the Virtual Machines (VMs).

If you want to install BMC ProactiveNet Agent on the Virtual Center (VC) server,
ensure that the ports used by the Apache of BMC ProactiveNet will not conflict
with those used by BMC VMware Adapter.
Data collection collection for performance counters must be enabled in VMWare.

The user account used to create BMC VMware Adapter instance should have at
least read-only privileges for the leaf node in VC server.
Enable remote connection to the VC server without creating a new certificate. If
necessary, see VMware product documentation for details.

Monitor type import is a one-time activity that imports the details of the
performance collecting entities into BMC ProactiveNet. The monitor import process
is an essential prerequisite for automatically synchronizing (auto-sync) the
performance data between a third-party performance monitoring solution and BMC
ProactiveNet.
For example, by initiating a monitor type import process for BPM Performance
Portal solutions, BMC ProactiveNet imports the details of all the application classes
Adapters overview
that are configured on the BMC Performance Manager Portal and maps them to
ProactiveNet monitor types.
For information about how to import monitor types for data adapters, see the
following sections:
Adding an adapter for BMC PATROL on page 251
Adapter for BMC Performance Manager Portal on page 224
Adding an adapter for HP OM on page 286
Adding an adapter for IBM Tivoli Monitoring on page 299
Adding an adapter for SCOM 2007 on page 311
Adding an adapter for BMC TM ART on page 322
Adding a BMC VMware Adapter on page 331
Adapters overview
To deploy BMC ProactiveNet for analytics and to auto-sync the performance data
that is being collected by BMC Performance Manager Portal application classes into
BMC ProactiveNet, you must complete the following activities.
Specify the credentials to initiate the import monitor type wizard for BMC
Performance Manager Portal. Follow the steps listed in the wizard to import all
the application classes into BMC ProactiveNet.
Configure the adapter to auto sync the performance data collected by the BMC
Portal application classes into BMC ProactiveNet at periodic intervals.
To achieve auto-sync, you will have to create an adapter instance by invoking the
adapter creation wizard and specify the application classes and devices which are
intended to auto-sync.
Note
Both the Import monitor type and auto-sync is a one time activity to configure the
performance data collected by the BMC Performance Manager Portal application
classes into BMC ProactiveNet .
For detailed information about adding adapters, see Adding adapters on page 250.
Adapters overview
Adapter for BMC PATROL

The adapter for BMC PATROL facilitates pulling of performance data from existing
BMC PATROL solutions into BMC ProactiveNet. Using the adapter, you can import
BMC PATROL application classes into BMC ProactiveNet. The Adapter periodically
synchronizes the performance data collected by these application classes into BMC
ProactiveNet.
Figure 32: Adapter for BMC PATROL architecture
Adapter for BMC Performance Manager Portal

The adapter for BMC Portal facilitates importing performance data from existing
BMC BPM solutions into BMC ProactiveNet. Using the adapter, you can import
BMC Portal application classes into BMC ProactiveNet and periodically synchronize
the performance data collected by these application classes from Portal agents into
BMC ProactiveNet.
Adapters overview
Figure 33: Adapter for BMC Performance Manager Portal architecture
Adapter for HP OM overview

This section provides an overview of the concepts and procedure for using the BMC
ProactiveNet adapter for HP OM.
The BMC ProactiveNet adapter for HP OM collects numerical system and network
monitoring performance data from HP OM and displays the data in BMC
ProactiveNet for in-depth and probable-cause analysis. Using the adapter, you can
import HP OM application classes into BMC ProactiveNet and automatically
Adapters overview
synchronize the performance data collected by these application classes into BMC
ProactiveNet. Figure 34 on page 226 illustrates the major components of the adapter
architecture.
Figure 34: Adapter for HP OM architecture
Configuring and creating an adapter instance starts in the BMC ProactiveNet

Administration Console where you connect to an Integration Service, and provide
information to connect to the HP OM server (not shown in the figure). The adapter
queries the HP OM server for a list of agents that you can select to build a
monitoring environment. The adapter then loads XML files, which contain HP OM
Smart Plug-In (SPI) specifications, to show the list of monitor types that you can
import. After importing the monitor types you can select application classes to monitor.
After creation of the adapter instance, the Integration Service communicates directly
with the HP OM agents. The adapter synchronizes the monitor information with
BMC ProactiveNet for display in the Operations Console.
BMC ProactiveNet includes several XML files for common SPIs. You can use the
XML files as-is, edit the files, or create files for custom-designed SPIs.
Adapters overview
Note
The Integration Service is built on the PATROL Proxy server infrastructure. Onscreen BMC ProactiveNet elements sometimes refer to the PATROL Proxy server.
However, The adapters for BMC PATROL, HP OM, and IBM Tivoli Monitoring all
use the same Integration Service.
The following table provides information about configuring and using the BMC
ProactiveNet adapter for HP OM:
Task
Reference
Use, edit, or create an XML file for use with HP OM

Smart Plug-Ins (SPIs)
See XML files for SPIs on page 294
Verify that you have all prerequisites for the adapter
See Verifying adapter for HP OM prerequisites on

page 219
Add the BMC ProactiveNet adapter for HP OM
See Adding an adapter for HP OM on page 286
Modify the list of monitored attributes
See Modifying the list of monitored HP OM

attributes on page 292
View Detailed Diagnostics and current information

(FlashCheck) about the monitored attributes
See Examining Detailed Diagnostics for HP OM

monitors on page 432
Refer to detailed information about the HP attributes Refer to HP OM documentation
Adapter for IBM Tivoli overview

This section provides an overview of the concepts and procedure for using the BMC
ProactiveNet adapter for IBM Tivoli.
The BMC ProactiveNet adapter for IBM Tivoli Monitoring collects numerical system
and network monitoring performance data from IBM Tivoli Monitoring, and
displays the data in BMC ProactiveNet for in-depth and probable-cause analysis.
Using the adapter, you can import IBM Tivoli Monitoring application classes into
BMC ProactiveNet and automatically synchronize the performance data collected by
Adapters overview
these application classes into BMC ProactiveNet. Figure 34 on page 226 illustrates
the major components of the adapter architecture.
Figure 35: Adapter for IBM Tivoli Monitoring architecture
Configuring and creating an adapter instance starts in the BMC ProactiveNet

Administration Console where you connect to the IBM Tivoli Monitoring Integration
Service, and provide information to connect to the Tivoli Enterprise Monitoring
Server (TEMS). The adapter loads all agents from the TEMS using XML files, which
contain IBM Tivoli Monitoring agent specifications, to build a monitoring
environment. In the environment, you choose monitor types to import and then
select the application classes to monitor.
The adapter for IBM Tivoli Monitoring communicates, via a SOAP service, with the
TEMS. The adapter synchronizes the monitor information with BMC ProactiveNet to
display in the Operations Console.
BMC ProactiveNet includes several XML files for common IBM Tivoli Monitoring
agents. You can use the XML files as-is, edit the files, or create files for customdesigned agents.
Adapters overview
Note
The Integration Service is built on the PATROL Proxy server infrastructure. Onscreen BMC ProactiveNet elements sometimes refer to the PATROL Proxy server.
However, The adapters for BMC PATROL, HP OM, and IBM Tivoli Monitoring all
use the same Integration Service.
The following table provides information about configuring and using the BMC
ProactiveNet adapter for IBM Tivoli Monitoring:
Task
Reference
Use, edit, or create an XML file for use with IBM

Tivoli Monitoring agents
See XML files for IBM Tivoli Monitoring agents on

page 306
Verify that you have all prerequisites for the adapter
See Verifying adapter for IBM Tivoli Monitoring

prerequisites on page 220
Add the BMC ProactiveNet adapter for IBM Tivoli

Monitoring
See Adding an adapter for IBM Tivoli Monitoring

on page 299
Modify the list of monitored attributes
See Modifying the list of monitored IBM Tivoli

Monitoring attributes on page 305
Refer to detailed information about the Tivoli

attributes
Refer to IBM Tivoli documentation
Adapter for System Center Operation Manager (SCOM) 2007

The adapter for SCOM 2007 facilitates pulling of performance data from existing
System Center Operations Manager (SCOM) 2007. Using the adapter, you can import
the SCOM Managed object types into BMC ProactiveNet and periodically auto-sync
the performance data collected by their associated performance rules into BMC
ProactiveNet. This adapter communicates with SCOM installation using the
Microsoft provided C# library.
Adapters overview
Figure 36: Adapter for SCOM 2007 architecture
BMC TM ART adapter overview

The adapter for BMC TM ART integrates data collected by BMC TM ART Central
into BMC ProactiveNet Server for analysis and root-cause drill down. The adapter
collects data from all the monitors that are configured and enabled for data
collection in the BMC TM ART application. The adapter uses the set of servlet APIs
that are available as part of BMC TM ART Central to access and collect the required
metrics.
Adapters overview
Figure 37: BMC TM ART architecture
Note
BMC Software recommends that you set up a separate front-end server for BMC
ProactiveNet data collection to prevent performance impacts to other interactive
BMC TM ART users.
BMC VMware Adapter

As part of virtualization support, the BMC VMware Adapter enables BMC
ProactiveNet to monitor the VMware infrastructure. This adapter can remotely
monitor the Virtual Center (VC) server (host) using web services, securely.
The BMC VMware Adapter adapter discovers the VMware entities such as ESX
servers, Virtual Machines (VMs), clusters, resource pools and their relationships, on
a periodic basis. The same information will be used for statistical and configuration
polls. This can detect the VMotion events as soon as they occur on VC. Performance
monitoring is achieved using a single connection to the given VC server.
This adapter can leverage the probable cause analysis functionality of BMC
ProactiveNet by treating each VM as a separate device. You can visualize the
Adapters overview
performance problems of VMware infrastructure using the out-of-box reports and

the feature-rich reports that you can generate from the collected data. This adapter
can provide the snapshot of the VMware environment by executing detailed
diagnostics on event conditions (or on demand).
The VMs (with operating system and tools installed) are not discovered until DNS
reconfiguration is complete.
VI client sometimes shows blank DNS/device name for VMs, in summary page. If
the discovery and/or VMotion happens during that time frame, it can potentially
result in duplicate device at end of BMC ProactiveNet (one with DNS name and the
other with IP address).
Performance data gets collected by Virtual Center, but not by the ESX Server for
some attributes like Memory Usage for Resource Pool. In these cases, adapters
targeting ESX Server, will record NO_DATA for these attributes.
The DD window displays an IP address instead of a blank if the DNS is not
configured for a VM.
Tune the following parameters as shown and restart the BMC ProactiveNet Server
and BMC ProactiveNet Agent.
On the computer that hosts the BMC ProactiveNet Server, edit the following
parameters in the pronet.conf file:
pronet.apps.agent.pollperiod.allowednoreplies.tcp=0 to 20
pronet.apps.agent.pollperiod.initnoreplies=2 to 20
pronet.apps.detailDiagnostics.waitQueueSize=5 to 10
pronet.jvm.maxthreadlimit=2000 to 10000
pronet.apps.agent.agentmon.agentstatusrefreshperiod=60000 to 180000
On the computer that hosts the BMC ProactiveNet Server, edit the following
parameters in the pnagentcntl.conf file:
Change the maxheap to 1024m
On the computer that hosts the BMC ProactiveNet Agent, change the following
parameters in the pronet.conf file:
pronet.apps.agent.watchdog.sleeptime=40000 to 120000
pronet.jvm.maxthreadlimit=2000 to 10000
On the computer that hosts the BMC ProactiveNet Agent (pnagent.conf)

Change the maxheap to 1536m
Adapters overview
Note
If a user is created, added, or provided with the right set of permissions in the
VMware Virtual Center and if the user is unable to create the BMC VMware
Adapter, try restarting the VMware Virtual Center Server service.
Performance data recorded for cluster and Resource Pool entities matches the
data displayed in VI client, currently. But, Virtual Center re-records these values
over time and those changes will not be reflected in the data of BMC
ProactiveNet .
When you create a new adapter instance or edit an existing adapter instance on
BMC ProactiveNet 7.7.00.001, it is mandatory to enter the port, protocol and

URL. If the remote agent is version 7.7 these entries are not applicable. The BMC
adapter for VMware continues to use the conf entries in the
VMwareAdapter.conf file, until the remote agent is upgraded to 7.7 .00.001.
Empty clusters (which do not have an ESX) will not be monitored.

Even if there is no data collection for a Resource Pool in Virtual Center, BMC
ProactiveNet would continue recording the last performance data point from the
Virtual Centers database (as per VMwares functionality).
Figure 38: VMware Architecture
Adapters overview
BMC VMware Adapter Features

The BMC VMware Adapter can:
be instantiated targeting a VC or an ESX server.
perform monitoring by using a single connection to the VC/ESX server from each
BMC ProactiveNet Agent.
remotely monitor the VC/ESX server using Web Services securely (HTTPS by
default).
discover hosts and VMs as devices in BMC ProactiveNet along with relationships.
discover clusters, resource pools, folders, and data centers as groups in BMC
ProactiveNet along with relationships.
encompass the devices and related monitor instances under the groups created for
VC and ESX server.
represent different devices/groups with appropriate icons.

discover changes in VMware infrastructure on a periodic basis.
represent the physical relationships between the hosts and VMs as part of the
Device Matrix.
represent the logical relationships between entities like clusters/resource pools
and hosts/VMs as part of the Group Matrix.
represent the mix and match of both the above views as part of Group Tree.
detect VMotion events as soon as they occur in VC.
leverage the probable cause analysis functionality by treating each VM as a
separate device in BMC ProactiveNet.
visualize the performance issues using out-of-box reports like Top/Bottom N VMs/
Hosts by CPU/Memory.
trigger Detailed Diagnostics (DDs) on detection of an event condition or on
demand. See
Top 10 VMs by balloon size on an ESX server on page 436

Top 10 VMs by CPU usage on an ESX server on page 436
Top 10 VMs by memory usage on an ESX server on page 437.
Adapters overview
Top 10 VMs by network usage on an ESX server on page 438

Top 10 VMs by balloon memory size on a Virtual Center on page 438
Top 10 VMs by CPU usage on a Virtual Center on page 439
Top 10 VMs by Memory usage on a Virtual Center on page 439
Top 10 VMs by Network usage on a Virtual Center on page 440
Top 10 VMs by balloon memory size on a Resource Pool on page 441
Top 10 VMs by CPU usage on a Resource Pool on page 441
Top 10 VMs by memory usage on a Resource Pool on page 442
Top 10 VMs by balloon memory size on a cluster on page 443
Top 10 VMs by CPU usage on a cluster on page 443
Top 10 VMs by Memory usage on a cluster on page 444
functions from BMC ProactiveNet Agent running on Solaris and any supported
platform of Windows.
help view the statistical data for a particular instance at any given time using the
FlashCheck feature.
VMware entities can be filtered based on ESX, CLUSTER, RESOURCEPOOL, VM
and ESX/VM. If an adapter already exists, its behavior will remain. ESX Server is
the default option while targeting to a Virtual Center and VM is the default option
targeting to an ESX Server.
An event is recorded as soon as VMotion occurs on Virtual Center, if the target
host is also monitored by BMC ProactiveNet server.
An event will be generated for every detected VMotion and the details can be
viewed from all event page in the BMC ProactiveNet Operations Console.
Continues to collect stats and config data for the hosts and VMs managed by the
VC to which the adapter is targeted to, even if the VC becomes unreachable.
VMware adapter monitors VMwares vSphere environment managed by vCenter
Server.
Adapters overview
The device and group folders represent the physical and logical hierarchy as seen in
Figure 39 on page 236 and Figure 40 on page 236.
Figure 39: Device Hierarchy
Figure 40: Group Hierarchy
Adapters overview
Failover for BMC VMware Adapter

Data collection failover for BMC VMware Adapter is applicable when the monitored
VC is down and the VC system availability in BMC ProactiveNet is shown as 0%.
However, the ESX and the VM under the VC will be operational.
This feature enables the adapter to collect performance data of hosts and its
underlying VMs. This is accomplished by directly connecting to hosts and fetching
data over the new connection to host, when a connection refused exception occurs.
When connection to the VC is established, the adapter falls back to VC connection
and resumes data collection for every VMware entity over that connection.
Failover is enabled based on the following conditions:
If you have enabled the failover check box and specified the credentials (right/
wrong) for all the hosts in failover input screen, failover is enabled.
If you have enabled failover check box but did not provide credential information
and selected Finish button on the monitor type selection screen, failover is disabled.
If you have enabled the failover check box and provided credentials (right/
wrong) for at least one of the hosts, failover is partially enabled.
The failover status information will be available in Summary Details panel of the
adapter creation screen. While providing credentials for hosts during edit/create of
adapter, you must use the tab to move around the fields, otherwise the input
credentials will not be effective.
Failover is applicable only for ESX and VMs. During failover from VC to ESX, data
collection will happen only for ESX and VMs. Resource Pool and Cluster system
monitor will record NO DATA and VC System monitor will record availability as 0%.
In case of partially enabled failover, data collection will happen only for those hosts
and underlying VMs for which credentials have been provided.
Host system will show availability as 0 for incorrect host credentials.
Hosts and underlying VMs for which the user did not provide credentials will
record NO DATA.
For each host, on providing credentials, a new connection will be created for which
data collection will occur. When VC is accessible, data collection will resume over
VC connection and all host connections will be closed.
By default, the failover is triggered after three polls. This count is controlled by the
VMwareAdapter.conf property. The same condition is valid during fallback to VC.
Once the failover is triggered, the actual regrouping of instances in poll managers
may take more time than the actual poll frequency depending upon the number of
Adapters overview
instances. During failover if the autosync is triggered, autosync will not proceed and
will get scheduled for the next autosync poll.
Note
There would be a gap in data collection during Failover and Fallback.
If the password is changed on the virtual center/server for the username by
which the adapter instance has been created, then the password must be changed
through editing the adapter for VMware.
Best practices
This section lists best practices for the adapters listed.
BMC PATROL, BMC Portal, and SCOM 2007

While adding or editing adapters, in <MONITOR_TYPES> filter, if you select the
<MONITOR_TYPES> so that the total instances available for selected

<MONITOR_TYPES> exceeds 20000 (without applying any scoping filter), the
following warning message is displayed.
The < MONITOR_TYPES > filter set may potentially exceed the limit
of instances being created in ProactiveNet.
This is not recommended.
Adjust the <MONITOR_TYPES> filter to limit the instances to
<INSTANCE_COUNT_LIMIT>
While executing a BMC adapter for PATROL VMware, the target patrol agent
should monitor the virtual centre in physical view.
BMC VMware Adapter

Monitor the VMware environment using BMC ProactiveNet, at the Virtual Center
or cluster level, in its entirety.
All the adapter instances targeting to same Virtual Center/ESX Server are
strongly recommended to use FQDN/IP address consistently. Failure to comply

with this can result in duplicate device creation in BMC ProactiveNet for the same
Virtual Center/ESX Server.

Each of the adapters (BMC PATROL, BMC Performance Manager Portal, HP OM,
SCOM, BMC TM ART, and BMC VMware Adapter) automatically synchronizes the
configuration data with its external source on a regular interval. This is based on the
adapter auto-sync poll interval. The auto-sync ensures that changes in the source
product are reflected in the BMC ProactiveNet Server. All monitor instances that are
created, deleted, or updated in the source product are reflected in BMC ProactiveNet
ONLY after an auto-sync is performed during the auto-sync poll. By default, autosync is performed once a day but can be changed to occur less or more frequently
depending on the environment. However performance will be impacted at some
point if it is run too frequently. BMC ProactiveNet has enhanced the auto-sync poll
frequency of BMC PATROL to 15 minutes, by default.
The auto-sync framework detects all unique instances of a monitor type and creates
these instances automatically on the selected BMC ProactiveNet Server. The unique
instances are loaded on the devices, groups and monitors where the monitor is created.
The auto-sync ensures that changes in the source product are reflected in the BMC
Note
Synchronization frequency will have an impact on the performance of the system.
Whenever n number of application classes are imported, n+1 application classes
loaded for auto discovery due to inclusion of a target availability monitor. This is
applicable for BMC PATROL, BMC Portal, HP OM, and BMC TM ART adapters.
Features of auto-sync framework

Following are the features of the Auto-Sync framework:
Auto-sync changes for instances, associated devices and groups
Remove instances that do not exist after a pre-specified period of time
Delete instances and recreate them when required
Auto-sync changes for instances, associated devices and

groups
The auto-sync framework dynamically detects and creates monitor instances, its
associated devices and groups, during periodic auto-sync poll. For example, the
SCOM process monitor detects all devices, groups and its processes and creates a
monitor instance, device and groups for each of the process.
If an instance gets deleted at the source, the Auto-Sync Engine internally marks the
instance as disabled.
Removing instances that no longer exist after a specified

period of time
If the instance continuously does not load over a specified time (by default, seven
days), the automatically created instance is removed from ProactiveNet Server.
You can configure the length of time before an unavailable instance is removed by
adjusting the pronet.autodiscovery.cleanuptime property in the pronet.conf
file, located in the PNETinsallDir \pw\pronto\conf directory. Specify the time in
seconds. By default, the time is 604800 s, which is seven days
Deleting and recreating instances whenever required

All auto-created monitor instances can be deleted and later be recreated whenever
required. The method used for deletion is same as deleting any other BMC
ProactiveNet monitor instance. The auto-Sync engine deletes such adapter instance
but retains all unique information of the adapter instance so that it can be recreated
later.
Recreate path helps to recover the auto-created monitor instance, which is deleted
accidentally. There is no time limit for recreation. You will be able to re-create the autocreated instance until the adapter exists, even if the instance is not available at the
target. However, in the subsequent auto-sync poll, action will be performed
depending on the availability of the instance at the target.
Note
By default, all auto-synced devices are of type Server. You can change the device
type of these devices using the Administration Console.
When a deleted monitor instance is recreated, data collected previously by the
deleted monitor is lost and cannot be retrieved.
To configure existing auto-sync groups as child to a regular group.

1 Right-click the existing regular group and select Edit Group.
2 Click Next on the subsequent screens without making any changes.
3 On the Step 3 Add groups screen, click Add and select the required auto-sync
groups.
4 Click Finish to view the auto-sync group as child group under the regular group.
To auto-sync and add adapters, see Adapters auto-sync feature on page 239.

This section describes how the time stamp is calculated by third-party applications
and displayed in BMC ProactiveNet.
During every poll, the adapter compares the previously recorded time stamp and the
current time stamp for each instance. If the time stamps are different, the adapter
treats this as a new data point and records the data.
If the time stamps are same, the adapter treats this as an old data point and drops the
current time and increments the duplicate-poll counter from its internal cache. The
adapter continues to drop unchanged data points until the counter reaches the
adjustable number (by default, 6) of duplicate data polls. When the adapter exceeds
the duplicate-poll counter (for example, on the 7th poll), the adapter poll records
NO_DATA and displays No Fresh Data. The time stamp for the NO_DATA poll is
calculated as follows:
lastRecordedTime + [(duplicatePollCounter+1)*pollFrequency]
For example, for the following data:

lastRecordedTime = 8:00 A.M
duplicatePollCounter = 6
pollFrequency = 5 minutes
the time stamp for the NO_DATA poll is calculated as follows:

8:00 + [(6+1)*5] = 8:35
After recording a NO_DATA point, the adapter continues to drop unchanged data
points until it detects a new data point. When the adapter receives a new data point,
the adapter resets its internal counter.

A Target Availability monitor type determines the status of the device from which
data is collected. When you add an adapter instance for the following data adapters,
one Target Availability monitor is created for every adapter instance:
Adapter for BMC PATROLPATROL_Proxy_Availability monitor
Adapter for BMC Performance Manager Portal adapter
BPM_DataStore_Availability monitor
Adapter for BMC TM ARTTMART_Target_Availability monitor

Adapter for HP OMHP_AGENT_CONN_INFO monitor
Adapter for IBM Tivoli MonitoringITM_AGENT_CONN_INFO monitor
If you upgraded to BMC ProactiveNet 8.0, the Target Availability monitor type is not
available for existing adapters. You can add the Target Availability monitor type by
editing the existing adapters in the current version.
This section describes the designing of BMC ProactiveNet Server and BMC
ProactiveNet Agents for different Patrol deployments. It is assumed that one Patrol
agent will have 1000 attributes that BMC ProactiveNet will be monitoring. If
parameters are less, then you can attach more number of Patrol agents to a BMC
ProactiveNet Server and vice-versa.
One BMC ProactiveNet Server can scale to 500K Attributes
Number of Patrol Agents: 500 (Assuming 1000 Attributes per Agent)
Number of PN Agents: 6 (90K attributes per Agent)
Patrol Proxy Agents: Depends on Number of different networks
Example 1:
500 Patrol Agents Scattered across 3 Networks
Total number of attributes to be monitored, 500 * 1000 = 500K
Number of BMC ProactiveNet Servers required: 1
Number of BMC ProactiveNet Agents required: 6

Number of Patrol Proxy Agents: 3 (One per Network)
Figure 41: Deployment architecture
Example 2:
2000 Patrol Agents Scatters across 3 Networks
Number of BMC ProactiveNet Servers required: 4
Number of BMC ProactiveNet Console servers required: 1
Number of BMC ProactiveNet Agents required: 24 (6 per BMC ProactiveNet server)
Example 3:
5000 Patrol Agents Scatters across 5 Networks
Performance sizing

Number of BMC ProactiveNet Servers required:10
Number of BMC ProactiveNet Console Servers required:1
Number of BMC ProactiveNet Agents required:60 (6 per BMC ProactiveNet server)
Hosting multiple BMC ProactiveNet agents on same

physical server
From the examples its imperative that at least 6 BMC ProactiveNet Agents are
required to gather data from 500 Patrol agents. All BMC ProactiveNet Agents can be
installed on a same physical server and can host 20K instances of adapters and
totally about 90K attributes (parameters) each. You need to reserve 1G of memory
and 6% of CPU for each BMC ProactiveNet Agent.
Performance sizing
For performance sizing and configuration requirements for the BMC ProactiveNet
Server and the BMC ProactiveNet Agent, see the BMC ProactiveNet Performance
and Scalability Guidelines.

After setting up the Adapters for data collection, a few key areas of the BMC
ProactiveNet need to be configured to realize the value of the BMC ProactiveNet. See
the BMC ProactiveNet Administration Guide for setting up Services, Groups, or
Views and BMC ProactiveNet User Guide for setting up Event Threshold and Event
Rules. Set up the intelligent thresholds of BMC ProactiveNet so that you can
leverage baseline values. Setting of thresholds while using BMC ProactiveNet with
adapters is explained in the following section.
Note
Setting thresholds should be done after Adapter Monitor Type Import and creating
Adapters.
Managing Thresholds using BMC ProactiveNet with adapters

Normally BMC ProactiveNet should be used for events when it is configured to
import data from third party sources or from PATROL/Portal. This uses dynamic
thresholds which reduces false events, and generates all the events and
abnormalities within BMC ProactiveNet. The probable cause analysis (PCA)
correlation can be used to isolate any probable causes related to the service events/
violations.
The underlying thresholds in PATROL/Portal (or other third party products) can
still be used, but administration becomes more tedious if there are overlapping
thresholds set in both products.
Setting intelligent thresholds

Intelligent Thresholds in BMC ProactiveNet are thresholds that leverage the baseline
as a dynamic baseline. One of the primary reasons for bringing third party
performance data into BMC ProactiveNet is to leverage intelligent thresholding. This
is very important for performance metrics as opposed to Availability metrics as
Availability metrics is a type of metric which generates events using pure static
thresholds. Performance metric thresholds, however, derive a large benefit from
being converted into Intelligent thresholds (which leverages the baseline). It is
recommended that all Key Performance Indicator (KPI) threshold settings from the
third party product should be converted into the intelligent thresholds of BMC
ProactiveNet. Other non-KPI thresholds from the third party product may not be
required and could possibly be removed since BMC ProactiveNet automatically
generates abnormalities even if an event threshold is not set.
Note
Availability metrics: For metrics which may NOT require Intelligent thresholds
(like Availability) moving those threshold settings into BMC ProactiveNet keeps
all administration of thresholds in one system. However, this may not always be
possible. For example, some threshold types from third party products may not
translate into BMC ProactiveNet thresholds. If the threshold is needed it may
make sense to retain it in the third party product.
Key Performance Indicator (KPI) threshold settings: When setting Intelligent
thresholds the static component of the Intelligent threshold can be lower than the
threshold in the third-party product. This is because the baseline will be used as
an additional filter on the threshold setting and reduces the number of false
events even if the threshold setting is lower than its previous setting.
Limitations
Tuning abnormality Thresholds

Abnormality thresholds control the Abnormalities that are generated in BMC
ProactiveNet. These are automatically enabled for all metrics in the system. In
general, the Abnormality thresholds need not be set or tuned, but in rare cases the
settings may require turning if they are receiving too many abnormalities or not
enough thresholds. The primary setting concerned with the baseline type specifies
which baseline to determine if the metric within the normal range of behavior. By
default the Adapter metrics will be set to ALL baseline type. For KPI metrics which
follow a clear hourly pattern the BL type can be set to Hourly. This ensures that all
abnormal behavior is caught and can be correlated correctly when doing probable
cause analysis.
Limitations
This section lists limitations that apply to all adapters and limitations that are
specific to certain adapter types.
Limitations common to all adapters

Configuration attributes that have large value more than 254 characters will get
truncated.
Auto-sync for adapters is not supported through the command line interface.
BMC does not recommend changing the timestamp of the adapters. If the
timestamp is changed, this will cause either a gap in the data or data overlap for a
particular period depending on the time zone.
BMC Performance Manager Portal limitations

Some of the performance metrics returned may have values greater than maximum
value of integer. If this occurs, incorrect statistical values will be collected.
BMC PATROL limitations

If auto-synced monitor instances do not have any stat attributes then those
instances will reflect in Administration Console, but not in HTML UI.
During the period of adapter import, if there is no data collection for any
attributes, instances, and application classes in PATROL agent then those

attributes, instances and application classes cannot be imported.
Limitations
If PATROL adapters are being created and targeted to the same PATROL agent
through different Integration Services, then the monitor instances will not display
in the proper hierarchy in the device matrix of Operations Console.
Some of the performance metrics returned may have values greater than
maximum value of integer. If this occurs, incorrect statistical values will be collected.
BMC TM ART adapter limitations

The BMC TM ART adapter for BMC ProactiveNet has the following limitations:
The transaction monitor type supports up to 50 custom timer attributes for
synthetic transactions, and up to 20 custom counter attributes for synthetic and

real transactions. Custom timers and custom counters are listed alphabetically, as
received BMC TM ART Central, from but only the first 50 timers and first 20
counters are monitored.
The following special characters, when used in the names of project, location, and
transaction monitors, appear as underscores in BMC ProactiveNet: ' " & , < > / :
BMC VMware Adapter limitations

BMC ProactiveNet Server monitoring selective ESX servers may face the
following problems in case of VMotion of VMs:
On VMotion detection from a host to another host that is not monitored by
BMC ProactiveNet, the VM will be displayed at the top level (without any
hierarchy). On next auto-sync poll, all the instances created on this device will
be marked for deletion.
Data collection gaps for brief periods can occur due to failed Web service
communication with VC/ESX server. Restart the BMC ProactiveNet Agent, if the
data collection does not resume in a reasonable time frame.
Device hierarchy may not be properly displayed, if Virtual Center runs out of a
VM which is managed by the same Virtual Center.
Only one VM will be discovered by BMC ProactiveNet randomly, if there is an IP
conflict across VMs.
Initial connection to Virtual Center/ESX Server may take longer than normal.
Connections opened with Virtual Center/ESX Server will be left over till they get
auto closed by the Virtual Center/ESX Server after the pre-configured time limit,
in case of Agent restart, adapter deletion, change of source Agent. However,
restarting Virtual Center would cause new connections to be open.
Limitations
If the VM discovered is a part of the Windows workgroup (DNS name ends with
a . in the VI client for these VMs) and the VM was already added to BMC
ProactiveNet as a device in some other channel (for example, as a BMC
ProactiveNet Agent, PATROL Agent), it results in a duplicate device.
Sometimes, there can be a difference between the VM list viewed from the VI
client and accessed programmatically (case ID with VMware for the same is 372022).
This adapter may fail to detect VMotion events occasionally, for example, when
the Virtual Center returns blank/null DNS Name and/or IP Address.
Empty Resource Pool or Clusters will not be discovered for both logical or
physical hierarchies.
Filtering based on Resource Pool discovers more entities.

In some include/exclude scenarios parent entities are discovered even though
they are explicitly specified in exclude criteria. This maintains both device and
group hierarchies.
FlashCheck is timed out, if the adapter instance created using BMC ProactiveNet
agent version 7.7 on BMC ProactiveNet server version 7.7.
After upgrading from version 7.7, VMotion may not be handled gracefully for
existing VMware adapter instances until the next autosync poll.
When you connect to an ESX, filtering on either include or exclude based on
CLUSTER is not a valid criteria.
Whenever a Virtual Machines availability is below 100%, then its state and time
stamp is recorded as more information.
For some of the attributes in BMC ProactiveNet, NO DATA is recorded, as the
attributes are not present at the target. This is applicable when the adapter to
VSphere 4.0 is targeted. For example, VM CPU monitor types the CPU Resources
Extra (ms), CPU Resources Guaranteed (ms) attributes are not available in
VSphere 4.0.
Data is not collected for the entity and displays the message Excluding the
entity from polling due to an issue with vc.
Failover for BMC VMware Adapter limitations

For successful failover, at least one stats poll should have occurred successfully to
the connected virtual centre.
After agent or server restart, if virtual centre is not up, then failover to ESX will
not start automatically. After a period if the virtual centre is accessible, then
fallback to virtual centre will not start automatically. You will have to restart the
agent to resume data collection.
Enable/Disable data collection is not applicable when data collection is
happening through failover to ESX.
If data collection is taking place with failover to ESX and if you disable data
collection, data collection will end. If you again enable data collection, it will not
resume with failover to ESX.
VMotion will not be detected during failover and all the metrics related to
VMotion will show NO DATA.
ESX 3.0 is not supported.

Blackout period of the actual data source of the adapters:

Table 5: Blackout periods for BMC Performance Manager Portal
Parameter Status
Data filled by BPM Adapter
More Info
DISABLED
NO DATA
Monitoring status is 'OFF' at BMC

Portal.
BLACKOUT
NO DATA
Specified parameter is in
BLACKOUT status
REMOVED
NO DATA
Specified parameter has been

removed from the BMC Portal.
BMC PATROL
Table 6: Blackout periods for BMC PATROL
Parameter Status
Data filled by BPM Adapter
DISABLED/
NO DATA
BLACKOUT/REMOVED
More Info
Corresponding Application class/Instance/
Parameter is suspended/deleted/no fresh
data available
Adding adapters
SCOM 2007
Table 7: Blackout periods for SCOM 2007
SCOM Application Status
Data filled by BMC ProactiveNet monitor instance

DATA_AVAILABILITY
Other attributes
Unreachable/service not
running
0%
NO DATA
Maintenance mode
100%
NO DATA
BMC TM ART blackout period behavior

If a BMC TM ART project moves into a black-out period, then the respective monitortype instance in BMC ProactiveNet is marked for deletion. During a black-out
period, BMC TM ART does not return values of the project and its transactions.
VMware
Table 8: Blackout periods for VMware
VMware Application Status
Data filled by BMC ProactiveNet monitor instance

DATA_AVAILABILITY
Unreachable/service not
running
0%
Other attributes
NO DATA
Blackout periods in multiple ProactiveNet Server deployment

When a child ProactiveNet Server enters a blackout period, events from the child
ProactiveNet Server are not propagated to the central ProactiveNet Server.
Therefore, BLACKOUT events that appear in the child ProactiveNet Server do not
appear in the central ProactiveNet Server.
Adding adapters
You can add the following adapters to BMC ProactiveNet:
Adding adapters
Adapter
Reference
BMC PATROL
Adding an adapter for BMC PATROL on page 251
BMC Portal
Adding an adapter for BMC Portal on page 282
HP OM
Adding an adapter for HP OM on page 286
Adding an adapter for IBM Tivoli Monitoring on page 299
SCOM 2007
Adding an adapter for SCOM 2007 on page 311
BMC TM ART
Adding an adapter for BMC TM ART on page 322
BMC VMware Adapter
Adding a BMC VMware Adapter on page 331
Best practice
When adding an adapter, it is recommended to specify the FQDN name instead of

the IP address or the partial DNS name as the device name. This avoids the creation
of a duplicate device.
Adding an adapter for BMC PATROL

You can add an adapter for BMC PATROL using either of the following methods:
automated workflow (recommended). For instructions see Adding an adapter
for BMC PATROL using the automated workflow on page 252.
manual method. For instructions see Adding an adapter for BMC PATROL
manually on page 259
Supported platforms
The following platforms are supported, when you create adapters for BMC PATROL
from a BMC ProactiveNet Agent.
Red Hat Linux
Microsoft Windows
Solaris SPARC
Adding adapters
Adding an adapter for BMC PATROL using the automated

workflow
The automated workflow feature provides a seamless process for automatic
configuration of remote BMC PATROL agents and loaded Knowledge Modules
(KMs) into the BMC ProactiveNet. This reduces the manual efforts required to
integrate the performance and configuration data from PATROL Agents and KMs
into BMC ProactiveNet.
As a user, you only have to configure the PATROL Agent to connect to the
Integration Service. You do not have to re-import the monitor types whenever there
is a new application class or changes to existing parameters.
Note
The version of the PATROL Agent must be 3.8.50 and later.

All the adapters created manually will continue to function. Automated workflow is
invoked with BMC ProactiveNet Agents version 8.5. Existing adapter instances
created manually require you to manually re-import monitor types for new
application classes or changes to existing classes, if not converted to automated
workflow.
Automated workflow eliminates manual configuration procedures and automatically:
Configuring PATROL Agents with the Integration Service on page 252
Importing monitor types and creating an adapter instance on page 252
Configuring PATROL Agents with the Integration Service

Automated workflow enables the PATROL Agent to automatically connect to the
Integration Service, register itself, and start sending performance data to the
Integration Service. The PATROL Agent is added to the default profile called
"_SA_DEFAULT_" in the Integration Service. The Integration Service uses the
Staging Adapter (a component of the Integration Service) to accept inbound
connections from the PATROL Agents. This default Staging Adapter profile is
created during the Integration Service startup (if not already available). You cannot
remove this profile. For added flexibility and scalability, the Integration Service
configures multiple Staging Adapter profiles and provides the ability to run multiple
Staging Adapter instances.
Importing monitor types and creating an adapter instance

Automated workflow imports monitor types and creates an adapter instance
whenever a remote agent configured with the Integration Service is added to the
BMC ProactiveNet Server. Once the remote BMC ProactiveNet Agent is added to the
Adding adapters
server, all the application classes that are loaded in the PATROL Agents are added to
the server. All instances pertaining to these application classes are made part of the
newly created adapter instance. This adapter instance polls for performance data
more frequently compared to the earlier instance.
Deleting the remote BMC ProactiveNet Agent also deletes the associated adapter
instance. This is true even for PATROL Agents earlier than version 3.8.50, once they
are configured manually with the Integration Service. However, all information
pertaining to application classes (such as KPI, graph by default, and so on) may not
be synchronized.
Converting a manually created adapter instance into an automated workflowenabled instance

To convert a manually created adapter instance into an automated workflowenabled instance, run the following command:
pw adapter -type patrol -enable_motype_sync <instance_name>
where <instance_name> is the name of the manually created adapter instance.
Features of automated workflow

Automated workflow:
Automatically creates a profile of type SA_ADAPTER in the Integration Service
(only for PATROL Agents version 3.8.50 or later)
Imports monitor types

Creates adapter instances
Discovers and creates monitor instances
Imports new KMs as BMC ProactiveNet monitor types every minute (by default)
Re-imports changes to KMs every minute (by default)
Limitations
You cannot use a local BMC ProactiveNet Agent installed on a BMC ProactiveNet
Server.
Automated workflow imports all the monitors loaded in the PATROL Agent as
there is no option to select specific monitors.
Adding adapters
Automated workflow imports all devices and monitor instances without any filter
option. You can edit the adapter instance after its creation to change the monitor
type selection and/or apply filters. Once you edit the adapter instance, it is
converted to the manual workflow.
It is not possible to distinguish between PATROL Adapters created manually and
those created using the automated workflow.
If you have converted a manual adapter instance to automated workflow, you
cannot revert to the manual adapter instance except to edit the adapter.
Automated workflow does not import thresholds automatically. You must
manually import thresholds using the pw adapter get_thresholds CLI command.
If you edit the automated workflow-enabled monitor instance and change the
monitor type, fetching of the new application classes added on the PATROL
Agent will stop.
You cannot enable automated workflow when you have upgraded a remote BMC
ProactiveNet Agent with Integration Service and changed the default password
but have not created an adapter instance.
If multiple BMC ProactiveNet Agents connected to different Integration Services
and running on different ports are installed on the same Solaris system,
automated workflow will work only for the first agent connected to the server.
User scenarios
The table below lists the use cases under which you will use automated workflow.
Use case
Steps to be performed
If you are performing a fresh

installation of the BMC ProactiveNet
Agent with the Integration Service
enabled during the installation
Automated workflow is invoked automatically
If you are performing a fresh

installation of the BMC ProactiveNet
Agent without the Integration Service
enabled during the installation
1 Disconnect the remote agent.

2 Manually enable the Integration Service. For
information about this, see the BMC ProactiveNet

3 Restart the remote agent.

4 Reconnect the remote agent.
Performing the steps above invokes automated workflow.
Adding adapters
If you have installed a remote agent

earlier than version 8.5
Automated workflow cannot be enabled.
If you have upgraded the remote agent

and enabled the Integration Service
using the default password
Having adapter instances: Existing adapter instances

continue to function as is. You can manually convert
them into an automated workflow-enabled instances. See
the Converting a manually created adapter instance into
an automated workflow-enabled instance on page 253
section.
Not having adapter instances: Disconnect and reconnect
the remote agent after the upgrade to the latest version.
If you have upgraded the remote agent Perform the procedure in use case #2 after upgrading the
without enabling the Integration Service remote agent.
If you do not want automated

workflow to be invoked on a given
BMC ProactiveNet Agent (to distribute
load or for any other reason)
1 Do not enable the Integration Service during

installation.
2 Manually enable the Integration Service. For
information about this, see the BMC ProactiveNet

3 Manually create the adapter instance.

7
If have more than one manually created

adapter instance connected to a single
Integration Service and upgraded the
BMC ProactiveNet remote Agent to
version 8.5
To convert any one of the manually created adapter

instances to automated workflow, delete the other
adapter instances (delete the associated monitor instances
also) and use the CLI command on the selected adapter
instance. For information about the CLI command, see
Converting a manually created adapter instance into an
automated workflow-enabled instance on page 253.
Adding a PATROL adapter using automated workflow

To add a PATROL adapter using automated workflow:
1 If the PATROL Agent is of version 3.8.50 or later, start the agent for it to be
registered with the Integration Service (running on a BMC ProactiveNet Agent).
2 If PATROL Agent is of version 3.8.50 or earlier, manually configure the PATROL
Agent registered with the Integration Service (running on a BMC ProactiveNet
Agent).
3 Add the remote BMC ProactiveNet Agent to the BMC ProactiveNet Server.
4 To check the progress of the adapter creation, right-click the Agent node in the
Administration Console and select the required option.
Adding adapters
Note
Creating a PATROL adapter fails if the remote agent does not get connected while
adding it to the server. In this case, delete the remote agent and add it once again.
Some attributes displayed in the BMC ProactiveNet Server may not be present in
the PATROL server. For such attributes, no data is collected.
Although an adapter instance created using automated workflow polls for
performance data every minute, some of the parameters/instances on PATROL

may take a longer time to collect data.
In case a parameter is deleted from PATROL, the same parameter does not get
deleted from BMC ProactiveNet, and NO_DATA is recorded for this parameter.
Configuring PATROL Agents version 3.8.50

If you have not specified the INTEGRATIONSERVICES variable while installing the
PATROL Agent version 8.5, you must configure the PATROL Agent. You can
configure the PATROL agent in any of the following ways:
Using the command line
Run the following command:
PATROLAgent -integrationservice tcp:<IntegrationServiceHost>:
<StagingAdapterPort> -p <PATROLAgentPort>
where,
<IntegrationServiceHost> is the system in which the Integration Service is running
<StagingAdapterPort> is the port number that the PATROL Agent registers
automatically with the Integration Service. The default port number is 3183.
<PATROLAgentPort> is the port number of the PATROL Agent. The default port
number is 3181.
Using the environment variable

Run the following command to set the INTEGRATIONSERVICES environment variable:
set INTEGRATIONSERVICES=tcp:<Integration Service
Host>:<StagingAdapterPort>
where,
Adding adapters
INTEGRATIONSERVICES is the environment variable.

Using the PATROL Configuration Manager rule

For information about PATROL Configuration Manager (PCM), see PATROL
Configuration Manager User Guide and BMC Performance Manager Consoles Release
Notes.
To configure the PATROL Agent using the PCM rule, run the following command:
"/AgentSetup/integration/integrationServices" = { REPLACE =
"tcp:<IntegrationServiceHost>:<StagingAdapterPort>"}
where,
You can add upto a maximum of four instances of the Integration Service, separated
by commas as follows:
"/AgentSetup/integration/integrationServices" = { REPLACE = "
tcp:<IntegrationServiceHost1>:<StagingAdapterPort>,
tcp:<IntegrationServiceHost4>:<StagingAdapterPort>"}
If you are using more than one instance of the Integration Service
Start the PATROL Agent using the command line, environment variable, or apply
the configuration using PCM to register the PATROL Agent to the Integration
Service for PATROL for failover. If IntegrationServiceHost1 is down, the PATROL
Agent connects to IntegrationServiceHost2. To use the failover option, run the
following command:
PatrolAgent -integrationservice tcp:<IntegrationServiceHost1>: <StagingAdapterPort>,
tcp:<IntegrationServiceHost2>: <StagingAdapterPort> -p <PatrolAgentPort>
Adding adapters
Unbinding the PATROL Agent from an Integration Service

For PATROL Agents configured using the command line and environment
variable, stop the PATROL Agent and restart it for unregistering.
For PATROL Agents registered using PCM, remove the rule from PCM to
unregister.
Configuring security for the validation of the Integration Service for PATROL
For PATROL Agents running at security levels ranging from 0 to 2, the out-of-thebox setting at the PATROL Agent skips the validation of the Integration Service.
However, you can modify this behavior using the following steps:
1 Run the regeditcommand to add the security_mode attribute to the Integration
Service policy of the PATROL Agent under the CLIENT folder.
The security_mode attribute can have the following values:
NO_AUTH - This is the default value. In this case, the PATROL Agent does not
validate the Integration Service for PATROL.
KNOWN_HOST - This value denotes that the PATROL Agent has to validate the
Integration Service for PATROL. For this, the public key of the Integration Service
must be available in the secure key store of the PATROL Agent. If it is not
available, the connection with the Integration Service is rejected.
If you are using UNIX, see the Configuring security on UNIX systems on page
259 section.
2 Perform the following steps to export the public key:
a From the BMC ProactiveNet Administration Console, click Tools =>
Configure => Integration Service.
b Enter the parameters for BMC PATROL and click Next.
c Click the Configure Integration Service button to configure the Integration
Service with the PATROL Agent.
d Click Finish once the configuration is complete.
e From the File menu, select Export Key.
f In the File Name field, enter the name of the file into which you want to export
the public key.
g Click OK.
Adding adapters
3 Apply the security configuration using the pconfig -host <PatrolAgent Host> port <PatrolAgentPortNumber> <PublicKey.cfg > command.
where,
<PatrolAgentHost> is the system in which the PATROLAgent is installed.
<PatrolAgentPortNumber> is the port at which the PATROL Agent is running.
The default port number is 3181.
<PublicKey.cfg> is a file name you define to export the public key into a file.
For multiple instances of the Integration Service, you need to import the public keys
for each Integration Service into the PATROL Agent.
For security level 3, the export certificate of the Integration Service for PATROL is
made available to the PATROL Agent by adding it to the pointed by the client policy
of the PATROL Agent. As part of the security handshake, the PATROL Agent
validates the certificate of the Integration Service, with the certificate authority.
For security level 4, both the PATROL Agent and the Integration Service must have
their own certificates as well as each other's export certificates, in their respective
client and server policies. As part of the security handshake, both the PATROL
Agent and the Integration Service validate each other's export certificate with the
certificate authority.
Configuring security on UNIX systems

1 To provide an enhanced level of security on UNIX systems, edit the proxy.plc
policy file at /etc/patrol.d/security_policy_v3.0/.
2 Add the security_mode attribute under the [CLIENT] section of the file, as
shown below:
security_mode = "KNOWN_HOST"
Adding an adapter for BMC PATROL manually

To manually configure integration with PATROL agents, you must perform the
following tasks:
configure profiles on the PATROL proxy
import monitor types
create an adapter instance
Adding adapters
Configuring the profiles on the PATROL Proxy
This section provides information about accessing and configuring existing profiles
in the PATROL Proxy Server.
Accessing the PATROL Proxy Server
You can access the PATROL Proxy Server from the BMC ProactiveNet
Administration Console or as a standalone application.
To access the PATROL Proxy Server from the BMC ProactiveNet Administration
Console
1 Log on to the Administration console.
2 Right-click Adapters to display the pop-up menu, and select Import Monitor
Types And Add Adapter => BMC PATROL.
Alternatively, you can also launch BMC PATROL Proxy Configuration from
Administration Console => Tools => Configure => BMC PATROL Proxy.
3 On the Import BMC PATROL Application Classes screen, complete the text boxes
and selections, and click Next.
4 On the Import PATROL Application Classes page, click Configure PATROL
Proxy to launch the PATROL Proxy Server and click Close.
To add a profile from the PATROL Proxy Server

1 Access the PATROL Proxy Server.
2 Under Profiles, right-click the profile to add, and select Add Profile.
To modify a profile from the PATROL Proxy Server

2 Under Profiles, click the profile and edit the attributes.
To remove a profile from the PATROL Proxy Server

2 Under Profiles, right-click the profile to delete, and select Remove Profile.
Adding adapters
To add an agent to a profile

2 Under Profiles, right-click the profile, and select Add Agent.
3 In the Input dialog box, type the agent host name or IP address, and click OK.
To specify the port number as you add the host name or IP address, use one of
the following formats:
agentName:portNumber
IPAddress:portNumber
The specified agent name appears under the profile and a status message is
displayed in the output window.
4 If the user name or password of the PATROL Agent differ from those of the
profile, clear the Inherited check box and edit the values.
To remove an agent from a profile

1 Access the PATROL Proxy Server, if required.
2 Expand the profile to view the current agents.
3 Right-click the agent and select Remove Agent to remove the agent.
4 Click Apply or OK.
To modify agent attributes in a profile

This procedure describes how to override the profile attributes for individual agents.
By default, the agents inherit their properties from the profile, enabling you to easily
manage attributes across the profile. To maximize the benefits of a profile, limit the
number of attribute changes to individual agents.
1 Access the PATROL Proxy Server, if required.
2 Expand the profile to view the current agents.
3 Select the agent. The agent attributes appear in the tabular region to the right of
the profile. By default, check boxes in the Inherited column show that the agent
attributes are inherited from the profile.
Adding adapters
4 Locate the attribute to modify, and clear its Inherited check box.
5 Under Value, update the attribute value.
6 Repeat steps 4 and 5 as required, and click Apply or OK.
Importing desktop, comma-separated and PATROL Event Translation files

You can import desktop files (DT), comma-separated files (CSV), or PATROL
Event Translation (PET) files.
A desktop file (.dt) stores the desktop layout for the PATROL Classic console and
contains information regarding the computers being monitored, the KMs that are
loaded as well as PATROL Console user accounts for monitored objects. Desktop
files contain the list of host computers and the connection attributes for each
computer. You can create desktop files with the PATROL Console for UNIX and
PATROL Console for Microsoft Windows . For detailed information about creating
a desktop file, see the documentation for your console.
The PET file (config.pet) resides on the PATROL Enterprise Manager (PEM) and
defines the PATROL Agents to which it connects and receive alerts. PET files
contain the host name, user account, password, protocol, and so forth for each
PATROL Agent identified to PEM. You can use the PATROL Integration
Configuration Utility (xpetconf) to create a PET file. For more information about
using this utility to create PET files, see the PATROL Enterprise Manager Installation
and Configuration Guide.
CSV files are created manually. Each line in the CSV file corresponds to a
PATROL Agent and contains the attributes in Table 9 on page 262. Any line that
begins with the # character is excluded from processing.
The standard CSV file syntax is as follows:
1=HOST_CONFIG,
2=hostName,
3=defaultAccount/password,
4=agentPort,
5=Protocol,
6=heartbeat,
7=pollingInterval,
8=timeOut
9=retries
Table 9: CSV file properties

Attribute
Description
HOST_CONFIG
header value for the agent record

Note: HOST_CONFIG must always be all uppercase for all operating
systems.
Adding adapters
Attribute
Description
hostName
PATROL Agent host name or IP address

This value cannot exceed 256 characters.
user name to log on to the PATROL Agent/DES-encrypted password
defaultAccount/password
The value for the user name cannot exceed 256 characters.
For more information about creating a DES encrypted password, see
Creating a DES encrypted password on page 342.
agentPort
port on which the PATROL Agent runs
Protocol
connection protocol to the host computer
heartbeat
number of seconds between attempts to keep the UDP connection open
pollingInterval
number of seconds between attempts to reconnect to the host computer

if the connection is lost
timeOut
number of seconds of no communication after which the p3Adapter

determines that the connection is lost
retries
number of times the p3Adapter attempts to reconnect to the host

computer before it determines that the connection is lost
Example
"HOST_CONFIG,hpux-shr-s02,patqa1/FA4E70ECE75A743C19F,3190,TCP,
300,3,5,5"
To import individual profiles into the PATROL proxy using the Configure
PATROL Proxy interface
1 On the Import PATROL Applications screen, click Configure PATROL Proxy to
open the PATROL Proxy Configuration screen.
2 Type a profile name and select a security level, and click OK.
3 On the PATROL Proxy Configuration screen, right-click Profiles and select Add
Profile.
4 Double-click the Profiles folder to view the new folder for the profile.
5 Select its folder to view the attributes for the new profile. The profile attributes are
applied to all agents in the profile.
6 Right-click the profile and select Add Agent to add an agent to the new profile.
7 Type the name of the agent, and click OK.
8 Repeat step 6 and step 7 to add more agents if required.
Adding adapters
9 Expand the profile to view the agents in the profile.

10 Select an agent name to view or modify the agent attributes.
11 Click OK to save and close the PATROL Proxy Configuration screen.
To import profiles into the PATROL proxy from the Console Server
1 On the Import PATROL Applications screen. Click Configure PATROL Proxy to
open the PATROL Proxy Configuration screen.
2 Right-click Profiles, and select Import Profile=>From Console Server .
3 On the Import from Console Server screen, complete the text boxes and selections,
and click Next:
Table 10: Configuration properties for profiles on the PATROL proxy
Item
Description
Enter the RT Server Connection

String
Type the RT Server Connection String
Select Console Server
Select the appropriate Console Server from the list.
Console Server Username
Type the credentials to connect the Console Server
Console Server Password

Security Level
Select a security level.
4 On the Import from Console Server screen, select the relevant profiles and click
List Agents.
5 Select the Available Agents and click Next.
6 Select the relevant option:
To create a new profile for the PATROL proxy, select Create New Profile. Type
the required details.
To add to an existing profile, select Add to Existing Profile. Select the
Available Profiles from the list.
7 Click Save Changes.

8 Click Finish to add the agents to the Profile.
9 Repeat step 5 and step 6 to add more agents if required.
Adding adapters
For more information on enabling BMC PATROL Proxy for Windows Agent, see
Importing monitor types for the adapter for BMC PATROL

The monitor type corresponds to the type of object, in this case, PATROL Agents.
After editing monitor types for the adapter for BMC PATROL, you can re-import
them into BMC ProactiveNet Server without losing baselines or raw data history.
Note
When you import monitor types, only the attributes that are collecting data during
the specified time period can be imported.
To include attributes that collect data after the original import, re-import the monitor
types.
To import and add monitor types for BMC PATROL

2 Select the Adapters folder, right-click and select Import Monitor Types And Add
Adapter => BMC PATROL.
Alternatively, you can also launch Import and Add Monitor Types from
Administration Console => Tools => Import Monitor Types And Add
Adapter => BMC PATROL.
3 On the Import BMC PATROL Application Classes screen, complete the text boxes
and selections, and click Next:
Table 11 on page 265 lists the input fields for Configuration and Control tabs.
Table 11: Configuration and Control tabs for BMC PATROL
Input Fields
Description
Configuration Tab
Instance Name
Type an instance name or have the proxy derive the instance name by
selecting an option from the menu.
Source Agent
Select BMC ProactiveNet Server.
PATROL Proxy Agent

Hostname/IP
Type the fully-qualified host name or IP address of the computer on which

the PATROL Proxy Agent is installed.
PATROL Proxy Agent Port
Type the port on which the proxy agent runs. Unless directed otherwise by
BMC Customer Support, use port 3182.
Adding adapters
Input Fields
Description
Administrator User Name/

Password
Type the user name and password for the Proxy Agent.
Skip Import
If you select the check box and click Next. The Add BMC PATROL Adapter
screen is displayed to add the adapter with already imported monitor types.
If this option is disabled it indicates that no monitor types are imported.
Control Tab
Statistics Poll Interval
Select the time interval between two consecutive statistical data polls. Default
is 5 minutes.
Statistics Poll Timeout
Select the time-out period for each poll of statistical data. Default is 2 minutes.
4 On the PATROL Application Classes screen, click Configure PATROL Proxy to

configure PATROL proxy. For more information, see Adding an adapter for
BMC PATROL on page 251. If you want to load the BMC PATROL Application
Classes click Next.
5 On the Import BMC PATROL Application Classes screen, select the monitor types
to import. Click the + icon to expand the monitor types or click Select All to
import all the monitor types of the adapter and click Close.
Do not click Next as this will create a new adapter instance.
Note
The green check mark indicates the imported monitor types.
The green check mark with a lock indicates the monitor type is in use.
The X indicates the imported object type is marked for deletion.
6 Click Close to exit without importing monitors and click Next.

The Import BMC PATROL Application Classes Summary screen is displayed
7 Perform one of the following actions:
Click Close to close the Wizard.
Click Next to add monitor types.
To re-import the modified PATROL Knowledge Modules(KM) to BMC

ProactiveNet Server
Adding adapters
2 Right-click Adapters to display the pop-up menu, and select Import and BMC
PATROL.
3 In the BMC PATROL Application Classes screen, complete the text boxes and
selections, and click Next.
4 In Import PATROL Application classes screen, click Next.
5 In the Import BMC PATROL Application Classes screen, the modified application
classes is displayed in bold.
Newly added parameters are displayed in green color as NEW.
Deleted parameters are displayed in brown color as DELETED.
Click Next to add the changes to BMC ProactiveNet Server.
Note
While re-importing, edit option for application class will not be available for
editing. This option is available for the classes which are not imported earlier.
6 In the Review Application classes Import/Unimport Warnings screen, click
Continue to re-import the new classes.
Note
Data collection will be stopped for the selected application classes during reimport. Data collection will resume once re-import is complete.
7 In the Import BMC PATROL Application Classes Summary screen, click Close.
This screen displays the successfully re-imported application classes.
8 In the BMC ProactiveNet Administration Console, right-click Adapters to display
the pop-up menu. Select the existing BMC PATROL adapter and click Edit.
9 In the Edit BMC PATROL screen, click Next.
10 Ensure that the re-imported application classes are selected for autosynchronization and click Next. Follow the steps in the wizard to trigger the autosynchronization.
Filtering devices and instances

You can filter monitor instances to be auto-discovered at the device or instance level.
Including filter types
Adding adapters
Include Filters tab provides an option to add filter patterns for filtering the monitor
instances to be auto-discovered. Filters are provided at the device or instance level.
Table 12: Include filters
Field Name
Description or action
Device Filter Type

a
Entity Type
Select the required entity from the list
Select
Pattern Matching
g h i
Select BMC PATROL Names for instance auto-sync of each configured

monitored type. Use the drop-down button to view the details of
PATROL agents that are configured in the PATROL proxy.
b
c d e
Enter a pattern name for BMC PATROL Name. Instance auto-sync of

each configured monitored type has to be done for the BMC PATROL
device names which have to fulfill the entered pattern name.
By default the Pattern Matching field is *, that is, all monitor instances
will be auto-discovered for the selected monitor types. For exclude
filter type, the Pattern Matching field is blank, that is, none of the
monitor instances will be excluded for the selected monitor types. See
b
footnote
.
Instance Filter Type

Monitor Type
The monitor types selected for auto-discovery are listed here. If a

monitor type selected has parent-child hierarchy, only the lower most
monitor type selected in the hierarchy will be listed. (Instance filters
cannot be added for the parent monitor types in the selected hierarchy).
Select a monitor type from the list.
Attribute
Pattern Matching
All attributes for the selected monitor type are listed here. Select an
attribute from the list.
b
Type a string pattern in this field to match. See footnote
Add
Click Add to add the filter for a particular monitor type and attribute.
Update
To update the filter patterns select the corresponding row in the

Selected Filters table and click Update.
Delete
To delete the filter patterns select the corresponding row in the Selected
Filters table and click Delete.
OR / AND
OR and AND radio buttons are provided at the right corner. The
default option selected is OR. The filter patterns added for different
monitor type and attribute combinations are applied with a logical OR
during auto-discovery of instances. Select AND option if filter patterns
added are for different attributes of the same monitor type and you
need AND behavior.
Selected Filters
The instance filters that were added are displayed in a table.
Adding adapters
Field Name
a This is applicable for BMC VMware Adapter.

b â: Matches all the elements starting with a.
c [0-9]: Matches all the elements having numeric values.
d 192.168: Matches all the elements whose hostname/IP address has "192.168".
e [a-zA-Z] Matches all the elements whose name has small and capital letters.
f device 1|device 2|device 3 Matches one of the elements mentioned (device 1, device 2 or device 3).
g * - Matches all the elements.
h \s Matches all the elements whose name has space in it.
i z$ - Matches all the elements whose name ends with z.
OR / AND mode of applying instance filters
OR and AND modes are applicable only when multiple filters are defined. Multiple
filters with different combinations of monitor type and attribute are allowed only if
the combinations are unique. There is an additional requirement for the AND mode
where the monitor type of all filters must be the same.
The filter patterns added for different monitor type and attribute combinations are
listed in the Selected Filters row of the Table 12 on page 268. These filter patterns
can be applied with either OR mode or AND mode during auto-discovery of
monitor instances based on the selection. However, when only a single filter is
defined these modes are not applicable.
OR mode:
This mode is applicable only when multiple filters are defined where each filter is a
unique combination of monitor type and attribute. In such a case, the filters defined
are applied with a logical OR during auto-discovery of instances.
AND mode:
This mode is applicable only when multiple filters are defined for the same monitor
type but different attributes. When this mode is selected, the filters defined are
applied with a logical AND during auto-discovery of instances.
Adding adapters
Note
Instance level filter is available only if the source Agent selected is version 7.7 and
above.
The Pattern Matching field accepts only string or alphanumeric patterns. If you
type a numeric value as a pattern for an attribute, it will be considered as a string

while matching it with the monitor instances to be auto-discovered.
If you need to apply the AND option for some monitor types and the OR option
for others, you must create two adapter instances. In the first adapter instance,
select the AND option and add filter patterns for the same monitor type with
different attribute combinations. In the second adapter instance, select the OR
option and add filter patterns for the other monitor type and attribute combinations.
Similar procedure applies for filtering instances BMC Portal, and BMC TM ART
adapters.
Special Note:
Multiple filters with the same combination of monitor type and attribute are not
allowed. For example, the following set of filters are not allowed:
Monitor Type
Attribute
Pattern Matching
BMC TM ART Transaction
Location Name
Houston
Location Name
Sunnyvale
Location Name
Austin
In case such a scenario needs to be supported, use a single filter with the required
monitor type and attribute and define the pattern as
Multiple strings separated by the | character if you need OR behavior (for
example, Houston|Sunnyvale|Austin)
or
Multiple strings separated by the & character if you need AND behavior (for
example, ^South&Texas$)
For Example, the following filter is allowed.

Monitor Type
Attribute
Pattern Matching
Location Name
Houston|Sunnyvale|Austin
Examples for Instance filters
Adding adapters
Example 1
Adapter Type: PATROL
Use Case:
All the monitor instances of the selected monitor types must be auto-discovered. But,
filters need to be applied for a couple of monitor types to auto-discover a sub-set of
the available instances of those types.
Include Filters applied:
Filter 1:
Monitor Type: VSM_VMOTION_VM
Attribute: Instance Name
Filter Pattern: VMotion$
Filter 2:
Monitor Type: Logical Disks
Filter Pattern: _Total
Mode: OR
Table 13: Selected Filters (OR mode)
Monitor Type
Attribute
Pattern Matching
VSM_VMOTION_VM
Instance Name
VMotion$
Logical Disks
Instance Name
_Total
Result:
All the monitor instances for all the selected monitor types will be auto-discovered
except for monitor types VSM_VMOTION_VM and Logical Disks where the filters
defined above will be applied (in OR mode). For these two monitor types, only those
monitor instances which have instance name ending with VMotion OR instance
name equal to _Total (exact match) will be auto-discovered respectively.
Excluding filter types
The Exclude Filters tab enables you to select all the devices (or add filter patterns for
all the devices) containing monitor instances that are not required to be autoChapter 5 Working with data adapters 271
Adding adapters
discovered and to add the instance filters for the monitored instances that are not
required to be auto-discovered.
The procedure for adding exclude filters is the same as adding include filters. For
more information, see Table 12 on page 268.
Creating an adapter for BMC PATROL instance

To create an adapter instance, use the following procedure.
To create an adapter instance

1 On the Import BMC PATROL Application Classes screen, select the monitor types
to import. Click the + icon to expand the monitor types or click Select All to
import all the monitor types of the adapter and click Next.
2 On the Import BMC PATROL Application Classes Summary screen, click Next.
3 On the Add BMC PATROL Adapter screen, select the application classes for auto
synchronization the click Next.
4 On the Set Filter Details screen, select the device and instance to set the filters. For
including and excluding filters, see Filtering devices and instances on page 267.
Device level and instance level filtering is available for BMC PATROL.
5 On the Schedule Auto-sync Polls screen, select the desired option and click Next.
Input field
Description
Periodic
Schedules auto-sync poll periods at a specific poll interval. For

example, if you select the poll period as 24 hours, then auto-sync occurs
after every 24 hours.
Daily
Schedules auto-sync poll periods at a specific time in a day. For

example, if you want to schedule auto-sync at 5.00 AM, then select 5.00
AM.
Weekly
Schedules auto-sync poll periods at specific day of the week. For

example, if you select auto-sync at 5.00 AM on Sunday, then you select
5.00 AM and Sunday.
Periodic
Auto-sync Poll Interval
Select the time interval between two consecutive auto-sync polls.

Default is 15 minutes.
Auto-sync Poll Timeout
Select the timeout period for each poll of auto-sync data. Default is 15
minutes.
Adding adapters
Input field
Description
Daily
Auto-sync Poll Time
Select the time in a day at which auto-sync poll is to happen.
Time Zone
Select the target time zone. By default, it displays BMC ProactiveNet

Server time zone.
minutes.
Weekly
Auto-sync Poll Time
Time Zone

Server time zone.
Days of the Week
Select the day on which the auto-sync poll is to happen. Select all to
trigger the auto-sync poll on all days of the week.
minutes.
Note
At any point, click Finish to display Summary Details for Adapter screen.
6 On the Summary Details for Adapter screen, click Finish.
If all the devices are selected for include filter by entering the pattern match as
*, a warning message is displayed.
First progress bar displays the loading of instances for the selected application
classes/monitor types. The status of the progress bar count gets updated as the
instance is loaded for each monitor types.
A second progress bar displays the auto-sync progress, this starts when the
available instances are loaded. The status of the progress bar count gets
updated as the auto-sync for each loaded instances is done.
Note
You can check the progress using the show discovery option after closing the
Progress dialog.
Virtualizing BMC PATROL

BMC PATROL adapter interprets the virtualized environment and provides
infrastructure for the virtual server solutions of BMC PATROL.
Adding adapters
Note
If the same virtual center is monitored by two PATROL agents and a PATROL
adapter is created for the two agents. The device hierarchy of the virtual center
toggles between the PATROL agents depending on the auto-sync of the adapter.
Table 14 on page 274 lists the enhancements for BMC PATROL

Table 14: Enhancements for BMC PATROL
Virtual Center
BMC PATROL console
BMC PATROL adapter
View as shown in the

virtual center
BMC PATROL console displays both Supports both physical and logical view.
the views.
Virtual Center, ESX Host

and Virtual Machine
Displays as application classes. BMC Creates devices for VC, ESX Host and
a
PATROL does not support as device. Virtual Machines.
VMotion
Updates parent and child

relationship information and
maintains historical data.
Updates parent and child relationship

information and maintains historical data.
a ESX and Virtual machine devices are displayed with a different icon.
PATROL Proxy Server maintenance

Use the procedures in this section to update credentials on the PATROL Proxy
Server, gather information about the current configuration, and save the
configuration settings
Following the installation of PATROL Proxy Server, perform the following steps to
reset the credentials for the PATROL Proxy Server.
To use the PATROL Proxy CLI to change the administrator password

This procedure changes the administrator password for a PATROL Proxy Server that
is running on the specified port and does not affect any other instances that might be
installed on other ports.
Whenever possible, use the PATROL Proxy CLI command in this procedure to
change the administrator password.
Note
Only the user who initially launched the PATROL Proxy Server has write
permissions to change the configuration settings of the port-specific configuration file.
Adding adapters
1 Navigate to the bin directory installed in <proactivenet installation directory>pw/

pproxy/PNS.
A sample from Linux computer is:
cd/pnetagent/pw/pproxy/PNS/Linux-2-3-x86-nptl/bin
Type the following command to launch the PATROL Proxy CLI and establish a
connection to the PATROL Proxy Server:
connect -host hostName -port portNumber -username admin -password admin
2 Type the following command to change the password from admin:
config -attribute -set -user admin -password newPassword
3 Confirm that the password was changed by typing the following command:
config -commit
USER=admin
RESULT=UPDATE_SUCCESS
RESULT=COMMIT_SUCCESS
To reset the administrator password to its default value without using the
PATROL Proxy CLI
1 Stop the PATROL Proxy Server process.
2 From a command line, type the following command:
pproxsrv -port portNumber -resetpassword
Where portNumber represents the port number on the PATROL Proxy Server
on which to change the password.
This command restarts the PATROL Proxy Server instance, resets the current
administrator password to admin, and then stops the PATROL Proxy Server
instance. When the PATROL Proxy Server restarts, it starts with the default
user name and password combination (admin/admin).
To change the administrator password to a specific value without using the

PATROL Proxy CLI
1 Stop the PATROL Proxy Server instance.
2 Using plain text, set the BMC_PPROX_PWD environment variable to the new
password.
3 Type the following command to launch the PATROL Proxy Server:
Adding adapters
pproxsrv -port portNumber -resetpassword
Where portNumber represents the port number on the PATROL Proxy Server
on which to change the password.
This command restarts the PATROL Proxy Server instance and reset the
administrator password to the value specified by the BMC_PPROX_PWD
environment variable, and then stops the PATROL Proxy Server instance.
When the PATROL Proxy Server restarts, it starts with the new password.
Viewing agent connection status in the BMC ProactiveNet

Operations Console
The Integration Service provides an abstraction wherein it by preloading a
connection status instance and connection status Knowledge Module (KM) for each
PATROL Agent (it exists only in the Integration Service database). The device, the
Integration Service instance, represents the connection status agent.
The connection status agent appears in the BMC ProactiveNet Operations Console in
the same manner as any other device, and includes the monitor types within the
device, the instances for the monitor types, and their parameters.
For each PATROL Agent, a separate instance of the connection status KM is created
within the connection status agent having new monitor type and has the new
monitor type AGENT_CONN_INFO. Each instance of the connection status KM has
the following parameters:
AGENT CONNECTION_STATUS - Boolean parameter that represents the
PATROL Agent connection status
A value of 0 for CONNECTION_STATUS indicates that the Integration Service is

not connected to the PATROL Agent.
Connection Update Time - last updated time of the PATROL Agent in the
Integration Service with its polling cycle or reconnection attempts
Number of Instances - total number of instances loaded on the PATROL Agent

Number of Parameters - total number of parameters loaded on the PATROL Agent
Number of Applications - total number of applications loaded on the PATROL
Agent
Note
If the Integration Service cannot resolve the DNS name of the PATROL Agent, all the
monitor instances corresponding to that PATROL Agent are listed under the device
with IP address of the system running the Integration Service.
Adding adapters
To view the agent connection status using the BMC ProactiveNet Operations
Console
1 In the operation console, click the Event Console tab, and then select All Devices.
2 Select the Integration Service instances from the list of devices.
3 On the All Devices page, select the monitor device (where the monitor type is
AGENT_CONN_INFO).
4 Click the Tools icon
, and then click Show Graph(s).
To check other attributes of a Agent connection status

1 On the Graph Display page, click the Attributes and indicators tab.
2 Select the required attributes to monitor.
3 In the Graph Options section, select Show each Attribute on a separate Graph
and click Generate Graphs(s).
To generate event for offline agents

1 Select the required monitor instances
2 Click the Tools icon
, click Threshold => Absolute Global Threshold.
3 On the Edit Thresholds - Absolute Global Thresholds page, enable the threshold
for the attribute AGENT Connection Status and severity Critical.
4 In the Comparison menu, select the option Equal and click Apply.
The Events are displayed for the offline agents on the BMC ProactiveNet
Operations Console.
Filtering devices and instances

You can filter monitor instances to be auto-discovered at the device or instance level.
Including filter types
Include Filters tab provides an option to add filter patterns for filtering the monitor
instances to be auto-discovered. Filters are provided at the device or instance level.
Adding adapters
Table 15: Include filters

Field Name
Device Filter Type

a
Entity Type
Select the required entity from the list
Select
Pattern Matching
g h i
Select BMC PATROL Names for instance auto-sync of each configured

monitored type. Use the drop-down button to view the details of
PATROL agents that are configured in the PATROL proxy.
b
c d e
Enter a pattern name for BMC PATROL Name. Instance auto-sync of

each configured monitored type has to be done for the BMC PATROL
device names which have to fulfill the entered pattern name.
By default the Pattern Matching field is *, that is, all monitor instances
will be auto-discovered for the selected monitor types. For exclude
filter type, the Pattern Matching field is blank, that is, none of the
monitor instances will be excluded for the selected monitor types. See
b
footnote
.
Instance Filter Type

Monitor Type
The monitor types selected for auto-discovery are listed here. If a

monitor type selected has parent-child hierarchy, only the lower most
monitor type selected in the hierarchy will be listed. (Instance filters
cannot be added for the parent monitor types in the selected hierarchy).
Select a monitor type from the list.
Attribute
Pattern Matching
All attributes for the selected monitor type are listed here. Select an
attribute from the list.
b
Type a string pattern in this field to match. See footnote
Add
Click Add to add the filter for a particular monitor type and attribute.
Update
To update the filter patterns select the corresponding row in the

Selected Filters table and click Update.
Delete
To delete the filter patterns select the corresponding row in the Selected
OR / AND
OR and AND radio buttons are provided at the right corner. The
default option selected is OR. The filter patterns added for different
monitor type and attribute combinations are applied with a logical OR
during auto-discovery of instances. Select AND option if filter patterns
added are for different attributes of the same monitor type and you
need AND behavior.
Selected Filters
The instance filters that were added are displayed in a table.
Adding adapters
Field Name
a This is applicable for BMC VMware Adapter.

b â: Matches all the elements starting with a.
c [0-9]: Matches all the elements having numeric values.
d 192.168: Matches all the elements whose hostname/IP address has "192.168".
e [a-zA-Z] Matches all the elements whose name has small and capital letters.
f device 1|device 2|device 3 Matches one of the elements mentioned (device 1, device 2 or device 3).
g * - Matches all the elements.
h \s Matches all the elements whose name has space in it.
i z$ - Matches all the elements whose name ends with z.
OR / AND mode of applying instance filters
OR and AND modes are applicable only when multiple filters are defined. Multiple
filters with different combinations of monitor type and attribute are allowed only if
the combinations are unique. There is an additional requirement for the AND mode
where the monitor type of all filters must be the same.
The filter patterns added for different monitor type and attribute combinations are
listed in the Selected Filters row of the Table 12 on page 268. These filter patterns
can be applied with either OR mode or AND mode during auto-discovery of
monitor instances based on the selection. However, when only a single filter is
defined these modes are not applicable.
OR mode:
This mode is applicable only when multiple filters are defined where each filter is a
unique combination of monitor type and attribute. In such a case, the filters defined
are applied with a logical OR during auto-discovery of instances.
AND mode:
This mode is applicable only when multiple filters are defined for the same monitor
type but different attributes. When this mode is selected, the filters defined are
applied with a logical AND during auto-discovery of instances.
Adding adapters
Note
above.

while matching it with the monitor instances to be auto-discovered.
Similar procedure applies for filtering instances BMC Portal, and BMC TM ART
adapters.
Special Note:
Multiple filters with the same combination of monitor type and attribute are not
allowed. For example, the following set of filters are not allowed:
Monitor Type
Attribute
Pattern Matching
Location Name
Houston
Location Name
Sunnyvale
Location Name
Austin
In case such a scenario needs to be supported, use a single filter with the required
monitor type and attribute and define the pattern as
Multiple strings separated by the | character if you need OR behavior (for
example, Houston|Sunnyvale|Austin)
or
Multiple strings separated by the & character if you need AND behavior (for
example, ^South&Texas$)
For Example, the following filter is allowed.

Monitor Type
Attribute
Pattern Matching
Location Name
Examples for Instance filters
Adding adapters
Example 1
Adapter Type: PATROL
Use Case:
All the monitor instances of the selected monitor types must be auto-discovered. But,
filters need to be applied for a couple of monitor types to auto-discover a sub-set of
the available instances of those types.
Include Filters applied:
Filter 1:
Monitor Type: VSM_VMOTION_VM
Filter Pattern: VMotion$
Filter 2:
Monitor Type: Logical Disks
Filter Pattern: _Total
Mode: OR
Table 16: Selected Filters (OR mode)
Monitor Type
Attribute
Pattern Matching
VSM_VMOTION_VM
Instance Name
VMotion$
Logical Disks
Instance Name
_Total
Result:
All the monitor instances for all the selected monitor types will be auto-discovered
except for monitor types VSM_VMOTION_VM and Logical Disks where the filters
defined above will be applied (in OR mode). For these two monitor types, only those
monitor instances which have instance name ending with VMotion OR instance
name equal to _Total (exact match) will be auto-discovered respectively.
Excluding filter types
The Exclude Filters tab enables you to select all the devices (or add filter patterns for
all the devices) containing monitor instances that are not required to be autoChapter 5 Working with data adapters 281
Adding adapters
discovered and to add the instance filters for the monitored instances that are not
required to be auto-discovered.
The procedure for adding exclude filters is the same as adding include filters. For
more information, see Table 12 on page 268.
Launching PATROL Configuration Manager

You can launch the PATROL Configuration Manager (PCM) from the BMC
ProactiveNet Administration Console. From the Tools menu, choose Configure =>
BMC PATROL Agents. For more information, see the PATROL Configuration
Manager User Guide and BMC Performance Manager Consoles Release Notes .
Adding an adapter for BMC Portal

Perform the following procedure to add an adapter for the BMC Portal.
To import and add monitor types for BMC Portal

2 Select the Adapters folder, right-click and select Import Monitor Types And Add
Adapter => BMC Portal. The BMC Portal Application Classes screen is displayed.
Administration Console => Tools => Import Monitor Types And Add
Adapter => BMC Portal.
Table 17: Configuration and Control tabs for BMC Portal
Input Fields
Description
Configuration Tab
Instance Name
Specify a name for the adapter instance.
Source Agent
Select the name/IP address of the BMC ProactiveNet Agent to host the new
adapter instance.
BMC Portal IP/Host Name
Specify a target system name or IP where BMC Portal Web Server is running.
BMC Portal Port
Port of the BMC Portal.
BMC Portal User Name
Specify a user name required to connect to BMC Portal.
Adding adapters
Input Fields
Description
BMC Portal Password
Specify the password required to connect to BMC Portal.
Use HTTPS
Select the check box to connect to BMC Portal through SSL.
BMC Portal Datastore Host

IP/Name
Specify the IP/Host Name where the BMC Datastore is running.
BMC Portal Datastore

Instance Name
Specify a database instance name of BMC Datastore.
BMC Portal Datastore Port
Specify the port where the BMC Datastore is running.
BMC Portal Datastore User

Name
Specify a user name required to connect to BMC Datastore.
BMC Portal Datastore

Password
Specify a password required to connect to BMC Datastore.
Skip Import
If you select the check box and click Next. The Add BMC Portal Adapter
screen is displayed to directly add the adapter with already imported monitor
types. If this option is disabled it indicates that no monitor types are imported.
Control Tab
Specify the time interval between two consecutive statistical data polls.
Specify the time-out period for each poll of statistical data. Default is 2 minutes.
Configuration Poll Interval
Specify the time interval between two consecutive configuration data polls.
Default is 24 hours (One day).
Configuration Poll Timeout
Specify the timeout period for each configuration data poll. If no data is
available at the end of this period, the system records Zero availability and
proceeds with the next scheduled poll. Default is 2 minutes.
3 Click Next and select the monitor types to import. Click the + icon to expand the
monitor types. Click Select All to import all the monitor types.
Note
The X mark indicates the imported object type is marked for deletion.
4 Click Next. A summary of the imported application classes are displayed.
Adding adapters
Note
Click Next to add monitor types
Text parameters in BPM Portal will be config attributes in BMC ProactiveNet.
Statistical parameters returning integer values shall be statistical attributes in
BMC ProactiveNet.
If you choose to add monitor types then perform the following steps:
5 On Add BMC Portal Adapter screen, select the monitor types to add. Click the +
icon to expand the monitor types or click Select All to add all the monitor types
of the adapter.
6 Click Close to exit without creating the auto-synced devices and instances.
7 Click Next.
For including and excluding filters, see Filtering devices and instances on page
267. Device level and instance level filtering is available for BMC Portal.
8 At any point, click Finish to display Summary Details for Adapter screen.
9 Click Next. The scheduler screen is displayed.
Choose Periodic, Daily, or Weekly options that give you the flexibility to
schedule auto-sync poll periods:
Periodic Enables you to schedule auto-sync poll periods at a specific poll
interval. For example, if you select the poll period as 24 hours, then every autosync occurs after every 24 hours.
Daily Enables you to schedule auto-sync poll periods at specific time in a
day. For example, if you want to schedule auto-sync at 5.00 AM, then you
have to select time as 5.00 AM.
Weekly Enables you to schedule auto-sync poll periods at specific day of
the week. For example, if you select auto-sync at 5.00 AM on Sunday, then
you select time as 5.00 AM and select Sunday.
Periodic:
Auto-sync Poll Interval - Specify the time interval between two consecutive
auto-sync polls. Default is 24 hours.
Adding adapters
Auto-sync Poll Timeout - Specify the timeout period for each poll of auto-
sync data. Default is 15 minutes.
Daily:
Auto-sync Poll Time Specify the time in a day at which auto-sync poll is to
happen.
Time Zone Specify the target time zone. By default, it displays BMC
ProactiveNet Server time zone.
Weekly:
Auto-sync Poll Time Specify the time in a day at which auto-sync poll is to
happen.
Days of the Week Select the day on which the auto-sync poll is to happen.
Select all to trigger the auto-sync poll on all days of the week.
10 Click Next. To display Summary Details for Adapter screen.

This gives the information about the number of monitor types, devices
included and excluded for auto-sync. If all the devices are selected for include
filter by entering the pattern match as *, a warning message is displayed.
11 Click Finish to display Auto-sync Progress window.

The first progress bar displays loading of instance for the selected application
instance is loaded for each monitor type.
A second progress bar displays the auto-sync progress, this starts when the
12 Click Close in Auto-sync Progress screen to return to Administration Console.
Adding adapters
Auto-sync progress can be checked later. To check the progress, expand the
Adapters folder, right-click on the monitor and select Show Auto-Sync Progress.
Once the device, instances, and groups are auto-synced, then auto-synced
devices, instances, and groups are displayed with a special icon as shown below.
Figure 42: Auto-synced devices and monitors screen (BMC Administration
Console)
Figure 43: Auto-synced devices and monitors screen (BMC Portal Console)
Adding an adapter for HP OM

Adding an adapter for HP OpenView Operations Manager (OVO) involves the listed
tasks.
Adding adapters
Task reference
Verifying adapter for HP OM prerequisites on page 219
Connecting the adapter for HP OM to the Proxy Server on page 287
Configuring an HP OM environment on the Proxy Server on page 288
Importing HP OM monitor types on page 290
Importing HP OM application classes and creating an adapter instance on page 291
The tasks are linked in one graphic interface, but you can skip tasks depending on
your current environment and requirements. The first time you configure an
adapter, though, you need to perform each task, in order.
Connecting the adapter for HP OM to the Proxy Server

The Proxy Server enables communication between the adapter and the ProactiveNet
Server.
Use the following procedure to connect the adapter for HP OM to the Proxy Server.
Before you begin

Before you begin, verify that your environment satisfies the requirements listed in
Verifying adapter for HP OM prerequisites on page 219.
To connect to the Proxy Server

1 In the Administration Console, select and right-click the Adapters folder, and
choose Import Monitor Types And Add Adapter => HP OpenView.
2 In the Import Monitor Types And Add Adapter dialog box, on the Configuration
tab, complete the required information as detailed in the following table:
Table 18: Configuration tab for HP OM adapter
Input Fields
Instance Name
Type a unique instance name for the HP OM adapter.

You can also select an item from the Insert Macro list to more easily
identify the adapter instance. For example, enter an instance name and
select HP OVO Proxy Agent Hostname/IP to add the $(DNSIP) macro.
The macro retrieves the value from the selected field and displays the
value during runtime.
Source Agent
Select the name or IP address of the BMC ProactiveNet Agent on which

the monitors are to be deployed.
Adding adapters
Input Fields
HP OM Proxy Agent Hostname/IP Type or select the name or IP address of the computer where the Proxy
Server is running.
Port
Type the port on which the proxy server runs. Unless directed
otherwise by BMC Customer Support, use the default port, 3182.
User Name and Password
Type the user name and password necessary to log in to the Proxy Server.
Skip Import
Select this option to skip importing monitor types. When you click
Next, you can directly add application classes with previously
imported monitor types.
The option is disabled if no monitor types are imported.
If the Skip Import option is not selected, you can view and modify the agent
configuration on the Proxy Server, or import HP OM monitor types from an

existing HP OM environment. See the following sections for details:
Configuring an HP OM environment on the Proxy Server on page 288
Importing HP OM monitor types on page 290
If the Skip Import option is selected, you can directly add application classes
with previously imported monitor types. See Importing HP OM application

classes and creating an adapter instance on page 291 for details.
3 Select the Control tab and view or modify the statistics polling options, as
detailed in the following table. When you finish, click Next.
Table 19: Control tab for HP OM adapter
Input Fields
Description
Select the time interval between successive statistical data polls from
the Proxy Server.
The default time is 5 minutes.
Select the time-out period for each statistical data poll.

Configuring an HP OM environment on the Proxy Server

An environment is a grouping of HP OM agents that are configured on the Proxy
Server.
Use the following procedure to configure an environment on the Proxy Server.
Adding adapters
To configure an environment on the Proxy Server

1 After you connect to the Proxy Server (Connecting the adapter for HP OM to the
Proxy Server on page 287), click Configure HP OpenView Proxy.
2 In the HP OM Server Configuration dialog box, right-click the HP OpenView
environment folder and choose Configure HP OVO environment.
3 In the Import Agents from HP OM Server dialog box, select the HP OM platform
to monitor. Complete the required information as detailed in the following table,
and click Next:
Table 20: HP OM platform details
Input Fields
Action
HP OM running on Windows (Connect to the WMI service)

HP OM Server Host Name
Type the HP OM server host name.
User Name
Type a local user name to connect to the HP OM server. Do not use a

domain user.
Password
Type the password to connect to the HP OM server.
HP OM running on UNIX/Linux (Connect to the HP OM database)

HP OM DB Host Name
Type the HP OM database host name.
DB User Name
Type the user name to connect to the HP OM database.
DB Password
Type the password to connect to the HP OM database.
DB Port
Type the HP OM database port.

The default port number for Oracle databases is 1521. The port number
cannot be less than 1024.
DB Name
Type the HP OM database name.
4 Select HP OM agents from the List of Agents and click Add or Add All to move
them to the Available Agents list.
Available Agents lists agents that will be used to import monitor types onto the
HP OM Proxy server.
The following options are also available:
Hold the Ctrl key to select multiple agents.
Click Remove or Remove All to remove agents from the Available Agents list.
Set the frequency (in minutes) that data is collected from agents.
Adding adapters
When you finish, click Next.

5 In the Save HP OM Agents to Environment screen, select one of the following
options:
To create a new environment on the HP OM Proxy server, such as for
additional HP OM servers, select Create New Environment and enter a unique

environment name.
To overwrite an existing environment on the HP OM Proxy server, select Add
to Existing Environment and select the name of an environment from the list.
6 To save the environment settings, click Save Changes.

7 (optional) Click Add More Agents to adjust agent settings in a new or existing
environment.
Note
To add or remove agents later, add a new adapter instance and adjust the HP OM
Proxy server configuration to update the existing environment.
8 Click Finish to complete the environment configuration and return to the HP OM
Server Configuration dialog box.
The configured environments are listed.
9 Click OK to return to the Import Monitor Types and Add Adapter dialog box.
All HP OM agents from the configured environments on the Proxy Server are
displayed in the dialog box.
See Importing HP OM monitor types on page 290 to continue.
Importing HP OM monitor types

Monitor types in BMC ProactiveNet correspond to the HP OM agents. When you
import monitor types, the system creates a template file on the HP OM Proxy server.
You can use this template to import application classes and create adapter instances.
Use the following procedure to import HP OM monitor types.
To import HP OM monitor types

1 Connect to the HP OM Proxy server (Connecting the adapter for HP OM to the
Proxy Server on page 287).
Adding adapters
2 Configure an environment on the HP OM Proxy server (Configuring an HP OM

environment on the Proxy Server on page 288) and click Next.
3 Select the monitor types that you want to use and the ones you want to delete.
A green check mark indicates that the monitor type is to be imported.
A green check mark with a lock indicates that the monitor type is in use.
A red X mark indicates that the monitor type is marked for deletion.
Best practice
Import all monitor types; you can then edit a single adapter instance to clear
groups of application classes, or you can filter out monitor types that you do not
need. By importing all the monitor types, you can edit a single adapter instance
later, instead of creating a new adapter instance.
4 Click Next.
See Importing HP OM application classes and creating an adapter instance on
page 291 to continue.
Target Availability monitor for HP OM
A Target Availability monitor type, HP_AGENT_CONN_INFO, is available for

every HP OM adapter instance.
The monitor provides a built-in attribute that reflects the status of the HP OM
agents. Target Availability is 100% if the HP OM agent is available; otherwise, the
value is 0%.
Importing HP OM application classes and creating an

adapter instance
Use the following procedure to import HP OM application classes and create an
adapter instance.
To import HP OM application classes and create an adapter instance

1 Connect to the HP OM Proxy server (Connecting the adapter for HP OM to the
Proxy Server on page 287).
2 Configure an environment on the HP OM Proxy server (Configuring an HP OM
environment on the Proxy Server on page 288).
3 Import HP OM monitor types (Importing HP OM monitor types on page 290).
Adding adapters
4 Select the application classes that you want to use and clear the ones you do not
want to use. Click Next.
5 (optional) On the Include Filters and Exclude Filters tabs, define filters for devices
and instances to include in, or exclude from, discovery, and then click Next.
For details about defining filters, see Filtering devices and instances on page
267.
6 On the Schedule Auto-sync Polls screen, configure the time interval in which
BMC ProactiveNet runs an automatic synchronization poll (that is, a discovery of
HP OM agents), then click Next.
7 On the Summary Details for Adapter screen, review the details and perform one
of the following actions:
If required, click Back to change the adapter details.
Click Finish to trigger an auto-sync poll and create the adapter instance.
Every agent in the configured environment is displayed in the Administration

Console under the Device => Server folder. You can expand the agents to see the
associated monitor types by group.
If you add an agent through the Administration Console, and later remove the agent,
the agent name continues to be displayed in the Administration Console. For better
management, right-click the agent name and choose Delete to remove unused
agents from the Administration Console.
Modifying the list of monitored HP OM attributes

This topic presents instructions for modifying the list of monitored attributes for the
BMC adapter for HP OM.
Through the Administration Console, you can edit the following characteristics of
HP OM adapter instances:
Include and exclude filters
Auto-sync schedule
In addition, if you imported all the monitor types of a Smart Plug-In (SPI) when you
configured the HP OM adapter instance, you can edit the attributes and groups in
the list of application classes (see To edit the list of attributes when all monitor
types are imported on page 293).
If you did not import all the monitor types of an SPI when you configured the HP
OM adapter instance, you can edit the attributes and groups by creating a new
Adding adapters
adapter instance (see To edit the list of attributes when all monitor types are not
imported on page 293).
To edit the list of attributes when all monitor types are imported
If you imported all the HP OM monitor types during monitor instance creation, then
you can modify the list of monitored attributes.
1 In the Administration Console, expand the Adapters => HP OpenView folder
and select the adapter instance.
2 Right-click the adapter instance and select Edit.
3 In the Edit HP OpenView dialog box, click Next.
4 Select or clear groups of application classes and click Next.
5 Adjust the include and exclude filters as required and click Next.
6 Adjust the auto-sync schedule as required and click Next.
7 Review the summary details for the adapter. Click Back to adjust details, or
Finish to complete editing the adapter instance.
Note
After you edit or delete an adapter for HP OVO, the system might take several
minutes to respond if sub-processes are still running. As a workaround, you can
manually stop the process:
(Windows) Through Windows Task Manager, end the ovcodautil.exe process.
(UNIX) Run the kill ovcodautil command.
To edit the list of attributes when all monitor types are not imported
If you did not import all the HP OM monitor types during monitor instance creation,
then you can adjust the list of monitor types by adding a new HP OM adapter instance.
1 In the Administration Console, add a new instance and connect to the HP OM
Proxy server as described in Adding an adapter for HP OM on page 286.
Verify that the Skip Import check box is clear so that you can import new
monitor types.
2 On the Import HP OpenView Application Classes screen, which lists the
monitored agents, click Next and edit the list of imported monitor types.
Adding adapters
Note
You cannot remove monitor types that are in use, but you can clear the attributes
groups from the list of application classes so that the attributes are not displayed
in the Operations Console.
Enabling debug logging for the adapter for HP OM

To troubleshoot issues that might arise in the adapter for HP OM, you can enable
debug logging.
To enable debug logging for the adapter for HP OM

1 On the proxy server, open the ovconfig.xml file, located in the installDirectory
\pw\pproxy\PNS\lib directory.
2 Change the value of the logLevel attribute to DEBUG, that is,
logLevel="DEBUG".
The debugging information is written to the ovadapter.log file with the PID
number at the end of the file name. The file is located in the installDirectory\pw
\pproxy\PNS\log directory.
XML files for SPIs

This section describes XML files that you can use, edit, or create to import any HP
OM Smart Plug-In (SPI), including custom SPIs.
The BMC ProactiveNet adapter for HP OM uses an XML file to import and integrate
HP OM SPI groups and attributes. The XML file contains the specifications HP OM
SPIs, including the groups and attributes (also called parameters) to be monitored in
BMC ProactiveNet. The adapter loads the XML files on the proxy server and
synchronizes the monitor information with BMC ProactiveNet for display in the
Operations Console.
You can use the provided XML files for common SPIs, or edit the files for your
specific requirements. You can also create an XML file for custom SPIs.
Provided XML files for SPIs

The following table describes the XML files for SPIs that are provided with the BMC
ProactiveNet installation. The files are located in the proxy server in the
installDirectory\pw\pproxy\PNS\lib\ovxml directory.
Adding adapters
File name
SPI Description
ADSPI.xml
Microsoft Active Directory
CODA.xml
Basic SPI provided with the HP agent
DBSPI_MSS_GRAPH.xml
Microsoft SQL Server graph metrics
DBSPI_MSS_REPORT.xml
Microsoft SQL Server report metrics
DBSPI_ORA_GRAPH.xml
Oracle Database graph metrics
DBSPI_ORA_REPORT.xml
Oracle Database report metrics
MOSS_2007.xml
Microsoft Office SharePoint Server 2007
MSES_BIZTALKSERVER_2004_INTERVAL.xml
Microsoft BizTalk Server
MSES_BIZTALKSERVER_INTERVAL.xml
Microsoft BizTalk Server
NET_SPS2003.xml
Microsoft Office SharePoint Portal Server 2003
NET_SPS2003_COMMON.xml
Microsoft Office SharePoint Portal Server 2003

common metrics
OASSPI_METRICS.xml
Oracle Application server
OASSPI_RPT_METRICS.xml
Oracle Application server report metrics
SCOPE.xml
SPI provided with the HP performance agent
WBSSPI_METRICS.xml
WebSphere Application server
WBSSPI_RPT_METRICS.xml
WebSphere Application server report metrics
WINOSSPI-DNS.xml
Microsoft DNS Server
WINOSSPI-IIS.xml
Microsoft Internet Information Server
WINOSSPI-Win2k.xml
Microsoft Windows 2000 operating system
WINOSSPI-WinOS.xml
Microsoft Windows operating system
WINOSSPI-WTS-Win2k.xml
Microsoft Windows Terminal Server Windows 2000

operating system
WLSSPI_METRICS.xml
Oracle WebLogic Server
WLSSPI_RPT_ METRICS.xml
Oracle WebLogic Server report metrics
XML reference for SPIs

You can create or edit XML files to import HP OM Smart Plug-Ins (SPIs) into BMC
ProactiveNet for monitoring and analysis.
This topic describes the XML elements and attributes required to import an SPI into
BMC ProactiveNet.
An XML generation tool is provided, via the command line interface, to help create
XML files for agent types that are not provided within installation. For details about
Adding adapters
the pw ovxmlgenerator command, see BMC ProactiveNet Command Line Interface

Reference Manual.
After you choose a provided XML specification file, or create your own, you can edit
the file to reflect your environment and requirements.
The following example shows the elements and attributes used in the XML file for SPIs.
Example
<?xml version="1.0" encoding="UTF-8"?>
<SPI name="WINOSSPI-Win2k" calculation="no">
<GROUP name="WINOSSPI-Win2k" parent="WINOSSPI-Win2k" hasInstances="yes"
label="WINOSSPI-Win2k" nameIdentifier="_InstanceName"
groupIdentifier="SystemUpTime">
<parameter name="SystemUpTime">
<type>2</type>
<description>System Up Time</description>
<unit>#</unit>
<style>standard</style>
<factor>1</factor>
</parameter>
</GROUP>
</SPI>
The following list describes the elements and attributes in the XML file.
SPI
The <SPI> root element contains the SPI group and parameter details.
The <SPI> element contains the following attributes: name and calculation.
name
The value of the name attribute is the name of the SPI, exactly as it is
provided by HP OM.
calculation
The value of the calculation attribute indicates whether one or more

parameters in the SPI require mathematical manipulation.
A yes value indicates that one or more parameters are calculated as a
delta value or require a normalization factor.
For information about calculating delta values, see the <style> element.
For more information about using normalization factors, see the
<factor> element.
A no value indicates that none of the parameters are calculated as a
delta value or require a normalization factor.
Adding adapters
GROUP
Use one or more <GROUP> elements to define group details and to contain
the parameter details of the group. If the SPI does not contain a group, add a
group using the SPI name as the group name.
The <GROUP> element contains the following attributes: name, parent,
hasInstances, label, nameIdentifier, and groupIdentifier.
name
The value of the name attribute is the name of the group, exactly as it is
provided by HP OM.
parent
The value of the parent attribute is the name of the SPI, exactly as it is
provided by HP OM. The attribute is reserved for future subgroup
functionality of the adapter for HP OM.
hasInstances
The value of the hasInstances attribute indicates whether the group of

parameters can have more than one instance.
A yes value indicates that the group can have more than one instance,
such as for CPUs or disks.
A no value indicates that the group has only one instance, such as for
GLOBAL parameters.
label
The value of the label attribute is the name of the group that appears in the
Operations Console.
nameIdentifier
The value of the nameIdentifier attribute specifies the name of the

parameter that provides the instance name.
If no parameter provides the instance name, leave the nameIdentifier
attribute empty. The instance name, in this case, is the same as the group
name.
groupIdentifier
The value of the groupIdentifier attribute specifies the name of a

parameter that uniquely identifies the group.
Adding adapters
parameter
Use one or more <parameter> elements to define the name of each parameter
and to contain elements with the parameter properties.
Note
The adapter for HP OM can only use numeric parameters for metric analysis.
Do not add parameters with string values.
The <parameter> element contains the name attribute.
name
The value of the name attribute specifies the name of the parameter,
exactly as it is provided by HP OM.
type
The content of the <type> element is always 2, indicating a numerical value

that you can use to generate a graph.
description
Type the content of the <description> element to add a description of the

parameter and to identify it in the Operations Console.
unit
Type the contents of the <unit> element to specify the units of the parameter;
for example, sec., #, or days, which will cause the units to be displayed with
the parameter in the Operations Console.
style
Type the contents of the <style> element to specify whether the parameter
appears at its current value or as the difference since the previous collection.
Use one of the following contents for the element:
A standard value indicates that the Operations Console shows the
current value of the parameter.
A delta value indicates that the Operations Console shows the change in
the parameter since the previously collected value.
Note
If the content of the <style> element is delta for any parameter in the SPI,
ensure that the value of the calculation attribute in the <SPI> root element is
yes.
Adding adapters
factor
The <factor> element is a non-zero normalizing value.

Depending on your system configuration, the Operations Console might
display some values in the SPI as greater than or less than the defined units
by a factor of 10, 100, or 1,000. Adjust the contents of the <factor> element as
required for your system.
Note
If the content of the <factor> element does not equal 1 for any parameter in
the SPI, ensure that the value of the calculation attribute in the <SPI> root
element is yes.
Adding an adapter for IBM Tivoli Monitoring

Adding an adapter for IBM Tivoli Monitoring involves the listed tasks.
Task reference
Verifying adapter for IBM Tivoli Monitoring prerequisites on page 220
Connecting the adapter for IBM Tivoli Monitoring to the Proxy Server on page 299
Configuring an IBM Tivoli Monitoring environment on the Proxy Server on page 301
Importing IBM Tivoli Monitoring monitor types on page 302
Importing IBM Tivoli Monitoring application classes and creating an adapter instance on page 303
The tasks are linked in one graphic interface, but you can skip tasks depending on
your current environment and requirements. The first time you configure an
adapter, though, you need to perform each task, in order.
Connecting the adapter for IBM Tivoli Monitoring to the

Proxy Server
The Proxy Server enables communication between the adapter and the ProactiveNet
Server.
Use the following procedure to connect the adapter for IBM Tivoli Monitoring to the
Proxy Server.
Before you begin

Before you begin, verify that your environment satisfies the requirements listed in
Verifying adapter for IBM Tivoli Monitoring prerequisites on page 220.
Adding adapters
To connect to the Proxy Server

1 In the Administration Console, select and right-click the Adapters folder, and
choose Import Monitor Types And Add Adapter => IBM Tivoli.
2 In the Import Monitor Types And Add Adapter dialog box, on the Configuration
tab, complete the required information as detailed in the following table:
Table 21: Configuration tab for IBM Tivoli Monitoring adapter
Input Fields
Instance Name
Type a unique instance name for the IBM Tivoli Monitoring adapter.
You can also select an item from the Insert Macro list to more easily
identify the adapter instance. For example, enter an instance name and
select IBM Tivoli Proxy Agent Hostname/IP to add the $(DNSIP)
macro. The macro retrieves the value from the selected field and
displays the value during runtime.
Source Agent

the monitors are to be deployed.
IBM Tivoli Monitoring Proxy

Agent Hostname/IP
Type or select the name or IP address of the computer where the Proxy
Server is running.
IBM Tivoli Monitoring Server Port Type the port on which the proxy server runs. Unless directed
otherwise by BMC Customer Support, use the default port, 3182.
Type the user name and password necessary to log in to the Proxy Server.
Skip Import
Select this option to skip importing monitor types. When you click
Next, you can directly add application classes with previously
imported monitor types.
The option is disabled if no monitor types are imported.
Adding adapters
Note
If the Skip Import option is not selected, you can view and modify the agent
configuration on the Proxy Server, or import IBM Tivoli Monitoring monitor

types from an existing configuration. See the following sections for details:
Configuring an IBM Tivoli Monitoring environment on the Proxy Server
on page 301
Importing IBM Tivoli Monitoring monitor types on page 302

If the Skip Import option is selected, you can directly add application classes
with previously imported monitor types. See Importing IBM Tivoli

Monitoring application classes and creating an adapter instance on page 303
for details.
detailed in the following table. When you finish, click Next.
Table 22: Control tab for IBM Tivoli Monitoring adapter
Input Fields
Description
Select the time interval between successive statistical data polls from
the Proxy server.

Configuring an IBM Tivoli Monitoring environment on the

Proxy Server
An environment is a grouping of agents from the IBM Tivoli Monitoring Enterprise
Monitoring Server (TEMS) that are configured on the IBM Tivoli Monitoring Proxy
server.
Use the following procedure to configure an environment on the IBM Tivoli
Monitoring Proxy server. Note that all agents on the monitoring server are
automatically added.
To configure an environment on the IBM Tivoli Monitoring Proxy server

1 After you connect to the IBM Tivoli Monitoring Proxy server (Connecting the
adapter for IBM Tivoli Monitoring to the Proxy Server on page 299), click
Configure IBM Tivoli Proxy.
Adding adapters
2 In the IBM Tivoli Monitoring TEMS Configuration dialog box, right-click the
Tivoli TEMS folder and choose Configure Tivoli TEMS.
3 In the Import Agents from IBM Tivoli Monitoring TEMS dialog box, complete the
required information as detailed in the following table:
Table 23: TEMS details
Input Fields
Action
TEMS Host Name
Type the TEMS host name.
TEMS Port
Type the TEMS port.

Typically, the port number for TEMS is 1920. The port number cannot
be less than 1024.
TEMS Username
Type the user name to connect to the TEMS.
TEMS Password
Type the password to connect to the TEMS.
Collection Frequency (minutes)
Set the frequency that data is collected from agents.
4 Click Finish to complete the environment configuration and return to the IBM
Tivoli Monitoring TEMS Configuration dialog box.
The configured environments are listed.
5 Click OK to return to the Import Monitor Types and Add Adapter dialog box.
All IBM Tivoli Monitoring agents from the configured environment on the Proxy
Server are displayed in the dialog box.
Note
IBM Tivoli Monitoring sometimes sends data from the same agent twice by
displaying the agent as its host name and again with its full domain name. BMC
ProactiveNet reflects the status received from the agents.
See Importing IBM Tivoli Monitoring monitor types on page 302 to continue.
Importing IBM Tivoli Monitoring monitor types

Monitor types in BMC ProactiveNet correspond to IBM Tivoli Monitoring agents.
When you import monitor types, the system creates a template file on the IBM Tivoli
Monitoring Proxy server. You can use this template to import application classes and
create adapter instances.
Use the following procedure to import IBM Tivoli Monitoring monitor types.
Adding adapters
To import IBM Tivoli Monitoring monitor types

1 Connect to the IBM Tivoli Monitoring Proxy server (Connecting the adapter for
IBM Tivoli Monitoring to the Proxy Server on page 299).
2 Configure an environment on the IBM Tivoli Monitoring Proxy server
(Configuring an IBM Tivoli Monitoring environment on the Proxy Server on
page 301) and click Next.
3 Select the monitor types that you want to use and the ones you want to delete.
A green check mark indicates that the monitor type is to be imported.
A green check mark with a lock indicates that the monitor type is in use.
A red X mark indicates that the monitor type is marked for deletion.
Best practice
Import all monitor types; you can then edit a single adapter instance to clear
groups of application classes, or you can filter out monitor types that you do not
need. By importing all the monitor types, you can edit a single adapter instance
later, instead of creating a new adapter instance.
4 Click Next, review the summary screen, and click Next again.
See Importing IBM Tivoli Monitoring application classes and creating an adapter
instance on page 303 to continue.
Target Availability monitor for IBM Tivoli Monitoring
A Target Availability monitor type, ITM_AGENT_CONN_INFO, is available for

every IBM Tivoli Monitoring adapter instance.
The monitor provides a built-in attribute that reflects the status of the IBM Tivoli
Monitoring agents. Target Availability is 100% if the IBM Tivoli Monitoring agent is
available; otherwise, the value is 0%.
Importing IBM Tivoli Monitoring application classes and

creating an adapter instance
Use the following procedure to import IBM Tivoli Monitoring application classes
and create an adapter instance.
Adding adapters
To import IBM Tivoli Monitoring application classes and create an adapter

instance
1 Connect to the IBM Tivoli Monitoring Proxy server (Connecting the adapter for
IBM Tivoli Monitoring to the Proxy Server on page 299).
2 Configure an environment on the IBM Tivoli Monitoring Proxy server
(Configuring an IBM Tivoli Monitoring environment on the Proxy Server on
page 301).
3 Import IBM Tivoli Monitoring monitor types (Importing IBM Tivoli Monitoring
monitor types on page 302).
4 Select the application classes that you want to use and clear the ones you do not
want to use. Click Next.
Note
The selected application classes will appear in the Operations Console.

5 (optional) On the Include Filters and Exclude Filters tabs, define filters for devices
and instances to include in, or exclude from, discovery, and then click Next.
For details about defining filters, see Filtering devices and instances on page
267.
IBM Tivoli Monitoring agents), then click Next.
By default, the auto-sync poll interval is every 15 minutes.
7 On the Summary Details for Adapter screen, review the details and perform one
of the following actions:
Click Finish to trigger an auto-sync poll and create the adapter instance.
Every agent in the configured environment is displayed in the Administration

Console under the Device => Server folder. You can expand the agents to see the
associated monitor types by group.
If you add an agent through the Administration Console, and later remove the agent,
the agent name continues to be displayed in the Administration Console. For better
management, right-click the agent name and choose Delete to remove unused
agents from the Administration Console.
Adding adapters
Modifying the list of monitored IBM Tivoli Monitoring

attributes
This topic presents instructions for modifying the list of monitored attributes for the
BMC ProactiveNet adapter for IBM Tivoli Monitoring.
Through the Administration Console, you can edit the following characteristics of
IBM Tivoli Monitoring adapter instances:
Include and exclude filters
Auto-sync schedule
In addition, if you imported all the monitor types of IBM Tivoli Monitoring agents
when you configured the adapter instance, you can edit the attributes and groups in
the list of application classes (see To edit the list of attributes when all monitor
types are imported on page 305).
If you did not import all the monitor types of IBM Tivoli Monitoring agents when
you configured the adapter instance, you can edit the attributes and groups by
creating a new adapter instance (see To edit the list of attributes when all monitor
types are not imported on page 306).
To edit the list of attributes when all monitor types are imported
If you imported all the IBM Tivoli Monitoring monitor types during monitor
instance creation, then you can modify the list of monitored attributes.
1 In the Administration Console, expand the Adapters => IBM Tivoli folder and
select the adapter instance.
2 Right-click the adapter instance and select Edit.
3 In the Edit IBM Tivoli dialog box, click Next.
4 Select or clear groups of application classes and click Next.
5 Adjust the include and exclude filters, if required, and click Next.
6 Adjust the auto-sync schedule, if required, and click Next.
7 Review the summary details for the adapter. Click Back to adjust details, or click
Finish to complete editing the adapter instance and to trigger an auto-sync poll.
Adding adapters
To edit the list of attributes when all monitor types are not imported
If you did not import all the IBM Tivoli Monitoring monitor types during monitor
instance creation, then you can adjust the list of monitor types by adding a new IBM
Tivoli Monitoring adapter instance.
1 In the Administration Console, add a new instance and connect to the IBM Tivoli
Monitoring Proxy server as described in Adding an adapter for IBM Tivoli
Monitoring on page 299.
Verify that the Skip Import check box is clear so that you can import new
monitor types.
2 On the Import IBM Tivoli Application Classes screen, which lists the monitored
agents, click Next and edit the list of imported monitor types.
Note
You cannot remove monitor types that are in use, but you can clear the attributes
groups from the list of application classes so that the attributes are not displayed
in the Operations Console.
Enabling debug logging on the adapter

To help troubleshoot issues that might arise in the adapter for IBM Tivoli
Monitoring, you can enable debug logging.
To enable debug logging on the adapter for IBM Tivoli Monitoring

1 On the proxy server, open the itconfig.xml file, located in the installDirectory\pw
\pproxy\PNS\lib directory.
2 Change the value of the logLevel attribute to DEBUG, that is,
logLevel="DEBUG".
The debugging information is written to the itadapter.log file with the PID
number at the end of the file name. The file is located in the installDirectory\pw
\pproxy\PNS\log directory.
XML files for IBM Tivoli Monitoring agents

This section describes XML files that you can use, edit, or create to import any IBM
Tivoli Monitoring agents, including custom agents.
Adding adapters
The BMC ProactiveNet adapter for IBM Tivoli Monitoring uses an XML file to
import and integrate the groups and attributes for an IBM Tivoli Monitoring agent.
The XML file contains the specifications IBM Tivoli Monitoring agents, including the
groups and attributes (also called parameters) to be monitored in BMC ProactiveNet.
The adapter loads the XML files on the proxy server and synchronizes the monitor
information with BMC ProactiveNet for display in the Operations Console.
The current installation of BMC ProactiveNet includes XML files for common agents,
and you can edit or create XML files to correspond to your environment.
Provided XML files for IBM Tivoli Monitoring agents

The following table describes the XML files for IBM Tivoli Monitoring agents that
are provided with the BMC ProactiveNet installation. The files are located in the
proxy server in the installDirectory\pw\pproxy\PNS\lib\itxml directory.
File name
Support for IBM Tivoli Monitoring agents on...
ActiveDirectory.xml
Microsoft Active Directory
DatabasesDB2.xml
IBM DB2 database
DatabasesOracle.xml
Oracle database
DatabasesSQL.xml
SQL database
DatabasesSybase.xml
Sybase database
EnergyManagementKE8.xml
IBM Tivoli Monitoring for Energy Management

version 8
EnergyManagementKE9.xml
IBM Tivoli Monitoring for Energy Management

version 9
LinuxOS.xml
Linux operating systems
MessagingExchange.xml
Microsoft Exchange
MessagingLotusDomino.xml
IBM Lotus Domino
PerformanceAnalyzer.xml
IBM Tivoli Performance Analyzer
UnixOS.xml
UNIX operating systems
WebSphereAS.xml
WebSphere application server
WindowsOS.xml
Microsoft Windows operating systems
XML reference for IBM Tivoli Monitoring agents

You can create or edit XML files to import IBM Tivoli Monitoring agents into BMC
ProactiveNet for monitoring and analysis.
This topic describes the XML elements and attributes required to import a Tivoli
agent into BMC ProactiveNet.
Adding adapters
An XML generation tool is provided, via the command line interface, to help create
XML files for agent types that are not provided within installation. For details about
the pw itxmlgenerator command, see BMC ProactiveNet Command Line Interface
Reference Manual.
An XML validation tool is also provided. The validation tool helps prevent runtime
errors by querying the TEMS machine and verifying (such as by checking for unique
name identifiers) that the returned data is compatible with the specified XML. For
details about the validateXML command, see Validating XML specification files for
the adapter for IBM Tivoli on page 310
After you choose a provided XML specification file, or create your own, you can edit
the file to reflect your environment and requirements.
The following example shows the elements and attributes used in the XML file for
Tivoli agents.
Example
<?xml version="1.0" encoding="UTF-8"?>
<AGENT name="Linux_OS" calculation="no">
<GROUP name="KLZ_User_Login" parent="Linux_OS" hasInstances="yes"
label="KLZ_User_Login" nameIdentifier="User_Name"
groupIdentifier="Login_PID">
<parameter name="Login_PID">
<type>2</type>
<description>Login_PID</description>
<unit>#</unit>
<style>standard</style>
<factor>1</factor>
</parameter>
</GROUP>
</AGENT>
The following list describes the elements and attributes in the XML file.
AGENT
The <AGENT> root element contains all the agent groups and parameters
collected for this agent type.
The <AGENT> element contains the following attributes: name and
calculation.
name
The value of the name attribute is the name of the agent that is displayed
in BMC ProactiveNet.
Adding adapters
calculation
The value of the calculation attribute is always no for IBM Tivoli

Monitoring agents. This attribute is reserved for future use; do not change
the value.
GROUP
Use one or more <GROUP> elements to define group details and to contain
the parameter details of the group.
The <GROUP> element contains the following attributes: name, parent,
hasInstances, label, nameIdentifier, and groupIdentifier.
name
The value of the name attribute must be the name of a valid IBM Tivoli
Monitoring (ITM) SOAP object. The group name is used to retrieve the
parameters in the group.
parent
The value of the parent attribute is the name of the agent, exactly as it is
provided by IBM Tivoli Monitoring. The attribute is reserved for future
subgroup functionality of the IBM Tivoli Monitoring adapter.
hasInstances
The value of the hasInstances attribute indicates whether the group of

parameters can have more than one instance.
A yes value indicates that the group can have more than one instance,
such as for CPUs or disks.
A no value indicates that the group has only one instance, such as for
host parameters.
label
The value of the label attribute is the name of the group that appears in the
Operations Console.
nameIdentifier
The value of the nameIdentifier attribute specifies the name of a parameter

that provides the instance name. The specified parameter cannot be a
parameter in the group.
If the hasInstances attribute value is no, leave the nameIdentifier attribute
empty. The instance name, in this case, is the same as the group name.
Adding adapters
groupIdentifier
The value of the groupIdentifier attribute specifies the name of a

parameter that uniquely identifies the group.
parameter
Use one or more <parameter> elements to define the name of each parameter
and to contain elements with the parameter properties.
Note
The adapter for IBM Tivoli Monitoring can only use numeric parameters for
metric analysis. Do not add parameters with string values.
The <parameter> element contains the name attribute.
name
The value of the name attribute specifies the name of the parameter,
exactly as it is provided by IBM Tivoli Monitoring.
type
The content of the <type> element is always 2, indicating a numerical value

that you can use to generate a graph.
description
Type the content of the <description> element to add a description of the

parameter and to identify it in the Operations Console.
unit
Type the content of the <unit> element to specify the units of the parameter;
for example, sec., #, or days, which will cause the units to be displayed with
the parameter in the Operations Console.
style
The content of the <style> element is always standard. This element is

reserved for future use; do not change the value.
factor
The <factor> element is always 1. This element is reserved for future use; do
not change the value.
Validating XML specification files for the adapter for IBM Tivoli
Use the following procedure to validate the XML specification files for the adapter
for IBM Tivoli.
Adding adapters
The validation process verifies that the following are correct:

XML syntax
Instance names and group names, based on real-time collection from the TEMS
To validate XML specification files

1 On the BMC ProactiveNet server, define the PNS_HOME variable for the
(for Windows) PNS_HOME= installDirectory\pproxy\PNS\bin
(for Solaris) PNS_HOME= installDirectory/pproxy/PNS/Solaris28-sun4
2 In a command prompt, change the directory to PNS_HOME.

3 Run the validateXML command according to the following syntax:
bin/itadapter --srv hostName:port:userName:password:http --validateXML
where
hostName is the IP address or computer name of the TEMS.
port is the port that listens to the TEMS (default 1920)
userName is the name of a user with access to the TEMS
password is the password for access to the TEMS
At the end of the validation process, one of the following results is displayed:
Result
Description
VALIDATE_XML_SUCCESS
Validation is successful
ERROR=ERR_LOAD_XML_FILES_FROM_DIRECTORY PNS_HOME is not defined correctly or no XML files

exist in the itxml directory
ERROR=VALIDATE_XML
Validation fails. Check the XML for errors or

duplication.
Adding an adapter for SCOM 2007

Perform the following procedure to add an adapter for SCOM 2007.
Adding adapters
To import and add monitor types for SCOM 2007

2 Select the Adapters folder, right-click, and select Import Monitor Types And Add
Adapter => SCOM 2007. The SCOM 2007 Object Types screen is displayed.
Administration Console => Tools => Import Monitor Types And Add Adapter
=> SCOM 2007.
Table 24: Configuration and Control tabs for SCOM 2007
Input Fields
Description
Configuration Tab
Instance Name
Specify a name for the adapter instance.
Source Agent
Select the name/IP address of the BMC ProactiveNet Server/BMC

ProactiveNet Agent to import the monitor type.
RMS Hostname/IP
Specify the name/IP address of the computer hosting the SCOM 2007 Agent
to be connected.
RMS Domain Name
Specify the RMS Domain name to connect to SCOM 2007.
User Name
Specify a user name required to connect to SCOM 2007.
Password
Specify a password required to connect to SCOM 2007.
Skip Import
If you select the check box and click Next, the Add SCOM 2007 Adapter
screen is displayed to directly add the adapter with already imported monitor
types. If this option is disabled it indicates that no monitor types are imported.
Control Tab
Specify the time interval between two consecutive statistical data polls.
Specify the time-out period for each poll of statistical data. Default is 2 minutes.
Configuration Poll Interval Specify the time interval between two consecutive configuration data polls.
Default is 24 hours (One day).
Configuration Poll
Timeout
Specify the timeout period for each configuration data poll. If no data is
available at the end of this period, the system records Zero availability and
proceeds with the next scheduled poll. Default is 2 minutes.
Adding adapters
Note
If the SCOM rule is configured to collect information more frequently than the
SCOM adapter, the SCOM adapter averages the data points collected by the rule
during the collection interval of the SCOM adapter. For example, if the SCOM
adapter collection interval is 15 minutes and the SCOM rule collection interval is
one minute, 15 values are returned to the SCOM adapter when it queries the
SCOM rule. The SCOM adapter averages those 15 values and returns that value
for its collection interval. Because the result is an average, the value returned
during the SCOM adapter collection interval may not be a whole number.
3 Click Next and select the monitor types to import. Click the + icon to expand the
monitor types. Select the monitor type that you want to import or click Select All
to import all the monitor types.
4 To import SCOM rules, follow these steps:
a Click the+ icon to expand the monitor types. All the rules for that monitor type
are displayed. Select the rules you want to monitor or click Select All to import
all the enabled rules.
b Right-click the rules that you want to import and choose Enable.
c Select the enabled rules that you want to import or click Select All to import
all the enabled rules.
Note
The X indicates that the imported object type is marked to be deleted.
To delete object types:

1 Select the object type to be deleted from the Select Monitor Types To Import
screen. The Review Object Types Import/Unimport Warnings screen is displayed.
2 Click Continue to delete. The summary of server objects deleted is displayed.
3 Click Finish. The server objects are deleted.
4 Click Next. A summary of the imported application classes are displayed.
Adding adapters
Click Next to add monitor types.
6 If you choose to add monitor types, on Add BMC SCOM 2007 Adapter Object
Types screen, select the monitor types to add. Click the + icon to expand the
monitor types or click Select All to add all the monitor types of the adapter.
Click Next to create auto-synced devices and instances.
8 For instructions on including and excluding filters, see Filtering devices and
instances on page 267. Device level and instance level filtering is available for
BMC SCOM 2007.
9 Click Finish to display Summary Details for Adapter screen. The Summary
details for adapters is displayed.
10 Click Next. The scheduler screen is displayed.
11 Choose Periodic, Daily, or Weekly options that give you the flexibility to
schedule auto-sync poll periods:
Periodic Enables you to schedule auto-sync poll periods at a specific poll
interval. For example, if you select the poll period as 24 hours, then every autosync occurs after every 24 hours.
Sync Poll Interval - Specify the time interval between two consecutive auto-
sync polls. Default is 24 hours.
Auto-Sync Poll Timeout - Specify the timeout period for each poll of auto-
Daily Enables you to schedule auto-sync poll periods at specific time in a day.
For example, if you want to schedule auto-sync at 5.00 AM, then you have to
select time as 5.00 AM.
Auto-Sync Poll Time Specify the time in a day at which auto-sync poll is to
happen.
Adding adapters
Weekly Enables you to schedule auto-sync poll periods at specific day of the
week. For example, if you select auto sync at 5.00 AM on Sunday, then you
select time as 5.00 AM and select Sunday.
Auto-Sync Poll Time Specify the time in a day at which auto-sync poll is to
happen.
Days of the Week Select the day on which the auto sync poll is to happen.
Select all to trigger the auto sync poll on all days of the week.
12 Click Next to display Summary Details for Adapter screen.

13 Click Finish to display Auto-sync Progress window.
The first progress bar displays the loading of instances for the selected application
instance is loaded for each monitor types.
The second progress bar displays the auto-sync progress, this starts when the
available instances are loaded. The status of the progress bar count gets updated
as the auto-sync for each loaded instances is done.
14 Click Close in Auto-sync Progress screen to return to the Administration Console.
Auto-sync progress can be checked later. To check the progress, expand the
Adapters folder, right-click on the monitor and select Show Auto-Sync Progress.
Adding adapters
Once the device, instances, and rules are auto-synced, then auto-synced devices,
instances, and rules are displayed with a special icon as shown below.
Figure 44: Auto-synced devices and monitors screen
Note
Agent installation on Windows Server 2008 (Longhorn) does not include .NET
3.0. You must install .NET 3.0 manually using the Role Management Tool.
Customizing application class attributes

You do not need to edit application class properties unless you are importing
application classes from a custom KM or Performance Manager.
You modify the attributes for an application class from the Import BMC PATROL
Application Classes page. You can access this page when you create a monitor type,
or at a later time. Table 25 on page 316 contains the properties that you can configure.
Table 25: Application class properties
Icon
Property
Description
Application level properties

NA
Display Name
user-facing name for the application class
Adding adapters
Icon
Property
Description
NA
Monitor Category
organized grouping for similar types of application classes

You must use one of the following categories:
System
Database
Application
Web
User Transactions
Mail
Security
Network
IP Services
Directory
Other
NA
Instance Name Pattern
pattern to create a user-friendly instance name that can

uniquely identify each application class instance
In most cases you can use $(LEVEL_N), which uses the name
of the leaf node of the this instance path to name this object in
BMC ProactiveNet.
Parameter level properties
Adding adapters
Icon
Property
Description
NA
Enabled
check box that flags the parameter to import into BMC

ProactiveNet.
Do not select a parameter if the following conditions are true:
the parameter value is a text string over 100 characters
the parameter does not add value from a analytics
perspective and is not baselineable
the parameter does not return a data value on a regular basis
the parameter value is a counter that grows indefinitely
the parameter value is an enumeration type or error code
that does not follow a trend
cumulative counts of alerts or events
isAvailability
parameter value represents availability of the monitored

instance
isResponseTime
parameter value represents response time of an action or

operation on the monitored instance
isKPI
parameter value represents a key performance indicator for

the application class
Most application classes have 12 parameters that are KPIs for
the application.
isGraphedByDefault
parameter value is selected by default when you navigate to

the graph for the application instance
isDataSpiky
parameter values can spike among collections

When selected, BMC ProactiveNet applies a different
algorithm for baselining. Response time parameters tend to
fall in this category of parameters.
Adding adapters
Icon
Property
Description
detectAbnormalities
determines whether BMC ProactiveNet automatically detects

abnormalities for this parameter
Unless the parameter value represents one of the following
conditions, you should select this option:
The parameter is redundant with another parameter in the
application.
The parameter is not baselineable, which means that it
does not return a value on a regular basis.
The parameter is a counter that grows indefinitely.
The parameter value is does not follow a trend.
Attribute type
Stats
parameter that returns a numeric performance value
Configuration
parameter that returns a value that cannot be converted to a

numeric value
How SCOM maps to BMC ProactiveNet

The following figures illustrate how objects and information in SCOM 2007 map to
the BMC ProactiveNet console.
Figure 45: BMC ProactiveNet Auto-discovered rule instances
Adding adapters
Performance data configuration of rule instances configured using SCOM are

mapped to Statistical attributes in BMC ProactiveNet.
Figure 46: SCOM Performance data collection rules
Figure 47: BMC ProactiveNetStats attributes
Adding adapters
Properties of managed objects are mapped to configuration attributes in BMC

ProactiveNet.
Figure 48: SCOM Managed objects properties
Figure 49: BMC ProactiveNet - configuration attributes
Adding adapters
Note
Agent installation on Windows Server 2008 (Longhorn) does not include .NET 3.0.
You must install .NET 3.0 manually using the Role Management Tool.
Possible gaps between SCOM data and BMC ProactiveNet data

If the SCOM rule collects data less frequently than BMC ProactiveNet collects data, it
is possible that BMC ProactiveNet will display that no data has been collected.
For example, if a SCOM rule monitors size of the logical disk every two days and the
ProactiveNet collection interval is set to 15 minutes, when the SCOM adapter asks
for data from SCOM it requests all the data for this rule from the ProactiveNet
collection interval (15 minutes ago) until now. However, the SCOM rule only queries
for this data every two days, so if the two day query did not occur in the last 15
minutes then the SCOM adapter will return NO DATA .
This behavior is logical because ProactiveNet only plots the relevant data (data from
15 minutes ago) and data from a query that occurred two days ago is not relevant.
For example, in this scenario, the logical disk could be full when the SCOM adapter
query occurs; however, the SCOM rule has not yet collected this data because the
two day interval has not yet occurred.
To view the data in ProactiveNet, you can do one of the following:
view an Excel spreadsheet of all the data.
change the resolution of the graph to make it larger (for example, two days)
customize the graph
Adding an adapter for BMC TM ART

Use the following procedure to add an adapter for BMC TM ART.
Before you begin

Ensure that BMC TM ART environment satisfies the requirements listed in
Adapter for BMC TM ART prerequisites on page 221.
Ensure that you have BMC TM ART Central user credentials. The data that you
collect depends on the following user roles:

A SuperUser collects data for all projects
Adding adapters
Any other user collects data for all projects in all groups to which the user is a
member
For details about implementing BMC TM ART user roles, refer to BMC Transaction
Management Application Response Time Central Installation and Setup Guide and User
Guide.
To add an adapter to collect the agent values for the BMC TM ART
1 In the Administration Console, right-click the Adapters folder, and choose Add
Adapter => BMC TM ART.
2 In the Add BMC TM ART dialog box, on the Configuration tab, complete the
required information, as detailed in Table 26 on page 323:
Table 26: Configuration tab for BMC TM ART adapter
Input Fields
Instance Name
Type a unique instance name for the BMC TM ART adapter.

You can also select and item from the Insert Macro list to more easily
identify the adapter instance. For example, enter the instance name and
select BMC TM ART Central Server IP/Host Name to add the $
(DNSIP) macro. The macro retrieves the value from the selected field
and displays the value during runtime.
Source Agent

the monitor is to be deployed.
BMC TM ART Central Server IP/

Host Name
Type or select the name or IP address of the computer where the BMC
TM ART Central server is running.
Port
Type the BMC TM ART Central web server port, typically 19120 for an
HTTP connection, or 8443 for an HTTPS connection.
The default port number is 19120.
Note: For HTTPS ports, select the Use HTTPS check box.
Type the user name and password necessary to log in to the BMC TM
ART Central server.
Use HTTPS
Select this option to use an HTTPS connection when querying data

through a secure BMC TM ART Central server.
Note: For HTTPS connections, enter an appropriate server port in the
Port box.
Collect Synthetic Transactions
Select this option to collect synthetic transaction data.

This option is selected by default. If neither synthetic nor real collection
options are selected, synthetic transactions are collected nonetheless.
Adding adapters
Input Fields
Collect Real Transactions
Select this option to collect real transaction data.

Real transaction data is supported with BMC TM ART version 3.7 or later.
detailed in Table 27 on page 324. When you are finished, click Next.
Table 27: Control tab for BMC TM ART adapter
Input Fields
Description
Select the time interval between successive statistical data polls.


The default time is 1 minute.
4 (optional) On the Include Filters and Exclude Filters tabs, select the Instance
check box to define filters for instances to include in, or exclude from, discovery.
For details on defining filters, see Filtering BMC TM ART instances on page
325.
Note
BMC TM ART supports instance-level filtering for transaction monitors only.
Project and location monitor hierarchies are always displayed in the BMC
ProactiveNet Operation Console. If project or location monitors are selected for
filtering, only their associated transactions are affected.
Click Next.
BMC TM ART project structures). Then click Next.
Select Periodic (default), Daily, or Weekly to schedule auto-sync poll periods:
Select Periodic to schedule an auto-sync poll at a specific time interval. For
example, if you select the poll period as 24 hours, then every auto-sync
occurs after every 24 hours. Periodic is the default setting.
Input Field
Description
Specify the time interval between two consecutive auto-sync polls.

Default is 24 hours.
Specify the timeout period for each auto-sync poll. Default is 15 minutes.
Adding adapters
Select Daily to schedule an auto-sync poll at a specific time of a day. For
example, you can schedule a daily auto-sync at 5.00 A.M.
Input Field
Description
Specify the time of day to run the auto-sync poll.
Time Zone
Specify the target time zone. By default, the BMC ProactiveNet Server
time zone is selected.
Select Weekly to schedule an auto-sync poll on a specific day or specific
days of the week. For example, you can schedule polls at 5:00 A.M. on
Sundays and Thursdays.
Input Field
Description
Specify the time of day to run the auto-sync poll.
Time Zone
Specify the target time zone. By default, the BMC ProactiveNet Server
time zone is selected.
Days of the Week
Select the day or days to run the auto sync poll. Select All to trigger the
auto sync poll every day.
6 On the Summary Details for Adapter screen, review the details. The total number
of monitor types for BMC TM ART is always threeproject monitors, location
monitors, and transaction monitors. Perform one of the following actions:
Click Finish to trigger an auto-sync poll.
Although the total number of monitors for BMC TM ART is three, four monitor
types are loaded. A Target Availability monitor is automatically added for each
BMC TM ART adapter instance. Target Availability is a TMART Server type
monitor that provides a built-in statistical attribute which reflects the status of the
BMC TM ART Central target. Target Availability is 100% if BMC TM ART Central
is available; otherwise, the value is 0%. For more details on the Target Availability
monitor, see Target Availability monitor type on page 242.
Filtering BMC TM ART instances

You can filter the discovery of BMC TM ART monitor instances according to a
pattern that you define.
Adding adapters
To filter BMC TM ART instances

1 In the Administration Console, open the Add or Edit BMC TM ART dialog box.
2 On the Include Filters tab or the Exclude Filters tab, or on both tabs, select the
Instance check box to define filters for the monitor instances.
On the Include Filters tab, only the monitor instances that match the defined
filters are discovered. Monitor instances that do not match the defined filter do
not appear in the Operations Console.
On the Exclude Filters tab, monitor instances that match the defined filters are
not discovered.
If filters are defined on both tabs, monitor instances are discovered by an

intersection of the filters.
3 Complete the options as described in Table 28 on page 326.
The options on both tabs are the same. You can use up to three include filters and
three exclude filters.
Table 28: Include or exclude instance-level filters for BMC TM ART
Field or button
Monitor Type
Choose a monitor type from the list:

BMC TM ART Location
BMC TM ART Project
Adding adapters
Field or button
Attribute
Choose an attribute from the list.

For the BMC TM ART Project monitor type, choose Project Name.
For the BMC TM ART Location monitor type, choose Location Name.
Note that project monitors still appear in the Operations Console, but
only the specified locations are included or excluded.
For the BMC TM ART Transaction monitor type, choose Location
Name, Project Name, or Transaction Name. Note that project and
location monitors still appear in the Operations Console, but only the
specified transactions are included or excluded.
Note: BMC Software does not recommend use of the Instance Name
attribute for the BMC TM ART adapter. The Instance Name attribute
corresponds to the selected monitor. For example, for the BMC TM ART
Location monitor type, the Instance Name attribute behaves the same as the
Location Name attribute.
Pattern Matching
Type a pattern to match the selected attribute.

You can use regular expression to define patterns. See Examples of regular
expressions on page 328.
Add
To add the filter definition, click Add.
Update
To update (that is, overwrite) a filter definition, select a row in the Selected
Filters table and click Update.
Delete
To delete a filter definition, select the corresponding row in the Selected

OR/AND
OR and AND options are applicable when you define more than one filter.
The default option is OR.
Filter patterns for different combinations of monitor types and attribute use
the OR option for the discovery of monitor instances.
Filter patterns of different attributes for the same monitor type (that is,
different attributes for the BMC TM ART Transaction monitor type) can use
either the OR option or the AND option for the discovery of monitor instances.
See OR and AND options for BMC TM ART monitor instance filters on
page 328 for more details.
4 Click Finish to review the filter details on the Summary Details for Adapter
screen.
5 Click Finish to trigger an auto-sync poll.
Adding adapters
Note
If the pattern in a filter prevents discovery on a monitor type, such as

an Include Filter that does not match the name of the selected attribute, or
an Exclude Filter that matches all the names of the selected attribute,
then the adapter instance reverts to the state of the previous filter.
Examples of regular expressions

The following table provides examples and descriptions for some of the regular
expressions that you can use for matching the pattern of the selected attribute.
Example
Description
â
Names starting with a
[0-9]
Names with any numeric value
192.168
Names with 192.168
[a-zA-Z]
Names with any lower case or upper case letter
pattern1|pattern2|pattern3
Any of the defined attribute names
0 or more of the previous character
\s
Space
z$
Names ending with z
$real$$
Names ending with (real)
OR and AND options for BMC TM ART monitor instance filters

This topic describes the use of the OR and AND options for BMC TM ART monitor
instance filters.
You can use more than one filter of different monitor types with the default OR
option. You can use more than one filter of the same monitor type with the OR
option or the AND option. The selected option applies to all the filters in the list.
Within each filter category (include and exclude), each defined filter must have a
different combination of monitor type and attribute. You cannot enter more than one
filter with the same BMC TM ART monitor type and attribute. Instead, use regular
expressions to refine the pattern matching.
For example, Table 29 on page 329 shows an invalid filter definition where more
than one line has the same monitor type and attribute combination:
Adding adapters
Table 29: Invalid filter: filter lines use the same monitor type and attribute combination
Monitor Type
Attribute
Pattern Matching
BMC TM ART Location
Location Name
Houston
BMC TM ART Location
Location Name
Sunnyvale
BMC TM ART Location
Location Name
Austin
Table 30 on page 329 shows the valid filter definition using regular expression:
Table 30: Valid filter: one filter for three locations
Monitor Type
Attribute
Pattern Matching
BMC TM ART Location
Location Name
In the adapter for BMC TM ART, the only monitor type for which you can define
different attributes is the BMC TM ART Transaction monitor type. Filtering the
BMC TM ART Transaction monitor type results in the inclusion (or exclusion) of
the transactions only. The project and location monitors that are relevant to the filter
appear in the Operation Console, and only the transaction monitors are affected.
Additionally, the filters for different BMC TM ART monitor types, where only the
OR option is available, behave differently than might be expected because of the way
the adapter for BMC TM ART is discovered. Only monitors matching the specified
patterns are discovered.
For example, given two project names, UK and US, each with a Birmingham location
name. Table 31 on page 329 shows filters that, using the OR option, only include UK
projects with the Birmingham location:
Table 31: Filter that includes UK projects at the Birmingham location
Monitor Type
Attribute
Pattern Matching
BMC TM ART Project
Project Name
UK
BMC TM ART Location
Location Name
Birmingham
A Birmingham location for a US project name is not included with the filters,
because the project filter only includes the specified project. Because you cannot
enter two BMC TM ART Project monitor types to include both UK and US projects,
you need to refine the project name pattern. In the example, use the vertical bar
(pipe) for the project name pattern: UK|US.
Adding adapters
Note
above.

while matching it with the monitor instances to be discovered.
Adapter for BMC TM ART debug log files

The adapter for BMC TM ART includes log files that you can use for debugging issues.
The debug log files record some or all of the following information:
Processes used to connect and retrieve data from BMC TM ART Central
Data retrieved from BMC TM ART Central
Data stored in the BMC ProactiveNet database
Verification statements or errors encountered in the processes
The debug log files are disabled by default. You can use the command line interface
(CLI) commands to enable logging (see pw debug in BMC ProactiveNetCommand Line
Interface Reference Guide for details). For example, use the following command syntax
to enable logging to a debug log file:
pw debug on -a agent_name -s subsystem
where
agent_name is the host name or IP address of the remote agent
subsystem is the name of the subsystem, such as TMARTAdaptor (which
corresponds to the name of the log file)
You can find debug log files on Windows systems at installDirectory\pronto\logs

\debug and on UNIX systems at installDirectory/pw/pronto/logs/debug.
The following debug log files are available for the adapter:
Adding adapters
Log file name
Description
DetailDiagnostics.log
Records data to be displayed in Detailed Diagnostics

windows. For the BMC TM ART monitors, the log
records information about the Page Timers and the
Run Now + TrueLog Detailed Diagnostics processes.
TMARTAdaptor.log (note the
Records processes, data, and data collection

verification or errors encountered with BMC TM
ART Central.
spelling of Adaptor)
TMARTAdaptorDataCollector.log
Records data to be stored in the BMC ProactiveNet

database.
TMARTAdaptorAutoDiscovery.log
Records data about the auto-sync process. The log is

updated when the auto-sync process runs, that is,
when you add or edit an adapter instance, and when
an auto-sync is scheduled (every 24 hours by default).
TMARTAdaptorDemandPoll.log
Records data to be displayed in the FlashCheck

window.
Adding a BMC VMware Adapter

Perform the following procedure to create a BMC adapter for WMware.
To create a BMC VMware Adapter

1 On the Administration Console, right-click the Adapters folder, and choose Add
Adapter => VMware.
2 On the Add VMware page, select the Configuration tab and complete the text
boxes and selections, and click Next:
Table 32: Configuration tab for BMC VMware Adapter
Item
Instance Name
Type the instance name for the BMC VMware Adapter or select an
option from the list.
Source Agent
Select the name/IP address of the BMC ProactiveNet Agent on which

the monitor is deployed.
Protocol
Key in the protocol that is either http or https. By default https is

displayed.
VC/ESX Name
Type the fully qualified domain name or IP Address of VC or ESX Server.
Port
Specify the port number of the VC. By default the port number is 443.
Adding adapters
Item
URL Path
URL path of the VC. For example if the hostname where VC is installed
is vmvc-cal-01.bmc.com then the URL through which you can access is:
https://vmvc-cal-01.bmc.com/
User Name/Password
Type the user name and password to login into VMware Server. User
name used to create BMC VMware Adapter instance should have at
least read only privileges till the leaf node, in VC or ESX server.
Enable Failover (if target is VC)
Select this option to enable failover. For more information, see Failover
for BMC VMware Adapter on page 237
3 Select the Control tab, view or modify the polling options, and click Next:
Table 33: Control tab for BMC VMware Adapter
Item
Description
Select the time interval between two successive statistical data polls.
Select the time-out period for each poll of statistical data. Default is 2
minutes.
Configuration Poll Interval
Select the time interval between two successive configuration data

polls. Default is 24 hours.
Configuration Poll Timeout
Select the time-out period for each poll of configuration data. Default is
2 minutes.
4 On the Select Monitor types for Auto-sync screen, select the monitor types for autosync. Click the + icon to expand the auto-synced monitor type or click Select All
to add all the monitor types of the adapter.
Note
The green check mark with a lock indicates the monitor type is in use
5 Filter monitor instances to be auto-discovered at the device level.
For including and excluding filters, see Filtering devices and instances on page
267. However, only device level filtering is available for BMC VMware
Adapter. When VC is targeted the ESX Servers are listed and when ESX Server
is targeted the VMs are listed in the device level filtering. Exclude filters based
list is subtracted from the Include filters based list and devices are created
from the resultant list.
6 On the ESX Input for VMware Failover screen, enter the user credentials for ESX/
host.
Adding adapters
Note
Use the tab key to save the user name and password.
7 On the Schedule Auto-sync Polls screen, select the desired option and click Next.
Input field
Description
Periodic
Schedules auto-sync poll periods at a specific poll interval. For

example, if you select the poll period as 24 hours, then auto-sync occurs
after every 24 hours.
Daily
Schedules auto-sync poll periods at a specific time in a day. For

example, if you want to schedule auto-sync at 5.00 AM, then select 5.00
AM.
Weekly
Schedules auto-sync poll periods at specific day of the week. For

example, if you select auto-sync at 5.00 AM on Sunday, then you select
5.00 AM and Sunday.
Periodic
Select the time interval between two consecutive auto-sync polls.

minutes.
Daily
Auto-sync Poll Time
Time Zone

Server time zone.
Select the timeout period for each poll of auto-sync data.Default is 15

minutes.
Weekly
Auto-sync Poll Time
Time Zone

Server time zone.
Days of the Week
Select the day on which the auto-sync poll is to happen. Select all to
trigger the auto-sync poll on all days of the week.
minutes.
8 On the Summary details for Adapter screen, Click Finish. The information about
the number of devices included and excluded for auto-sync and the VMware
failover status is displayed.
Editing adapters
For more information on monitored attributes, see BMC ProactiveNet Monitor guide.
Editing adapters
You can edit adapters from the BMC ProactiveNet Administration Console. The
following procedure is an example to edit the BMC Performance Manager Portal
adapter. The procedure similarly applies to editing the BMC Performance Manager
Portal, BMC PATROL, HP OM, IBM Tivoli Monitoring, SCOM,BMC TM ART, and
BMC adapter for VMware.
To edit an adapter
1 Expand the Adapters folder.
2 Expand the adapter type and right-click the adapter to be edited.
3 Select Edit and the respective adapter screen is displayed.
4 Make the required changes. On the Control tab, edit the polling frequency for
statistics and configuration and click Next.
5 On the Schedule Auto-sync Polls screen edit the poll interval and poll timeout
and click Next.
6 In the message asking you to confirm the auto-discovery, do one of the following:
Click Yes to update the attributes and trigger adapter instances discovery
immediately.
Click No to update the attributes but not to trigger the auto-sync polls.
7 On the Edit Adapter Tree screen, the registered monitor types for the respective
user are displayed. Make the required changes and click Next.
Note
If existing application classes are not selected, then the corresponding instances
will be deleted (devices will not be deleted).
Note
While editing an Adapter instance, if any existing monitored instances do not

match the modified selected Application classes or Filter options, then those
instances will be marked for deletion and will be deleted after seven days. For
example, if an adapter instance is created with *.* and if *.* is replaced with a few
devices later, the instances created for all devices except the newly selected
devices will be marked for deletion and will be deleted after seven days.
Editing adapters
8 For the subsequent steps, see Adapters auto-sync feature on page 239.
Adding a new application class into an existing adapter

instance
This section uses BMC Performance Manager Portal as sample scenario to guide you
through these activities. To add new application classes to an existing adapter
instance, you must complete the following activities in the order shown.
Import the new application class into BMC ProactiveNet adapter configuration.
Edit the adapter instance and select the new application class to discover the
instances, which are part of the new application class.
To add a new application class in Portal

1 On the Add application classes screen, select the desired application class. The
selected application class is added to the element in the Portal.
2 Editing the existing Portal adapter on BMC ProactiveNet does not show the new
application class.
To import the new application class into BMC ProactiveNet adapter

configuration
2 Right-click Adapters to display the pop-up menu, and select Import Monitor
Type => BMC Portal.
3 On the Import BMC Portal Application Classes screen, complete the text boxes
and selections, and click Next.
4 On the Import BMC Portal Application Classes screen, select the new application
and click Next.
5 On the Import BMC Portal Application Classes Summary screen, click Close.
Note
Do not click Next as this will create a new Adapter instance
To edit the adapter instance and select the new application class to discover
the instances which are part of the new application class
Deleting adapters
2 Right-click Adapters to display the pop-up menu, and expand BMC Portal.
3 Select the existing adapter for Portal and click Next.
4 On the select application Classes for Auto-sync screen, select the new application
class and click Next.
5 On the Edit BMC Portal screen, complete the text boxes and selections and click
Finish.
Note
If you have added the new monitor instances for the new application class in a
new adapter instance and if you delete the new adapter instance; the new
instances gets deleted and all the historical data will be lost.
Limitations
When an adapter is edited either by changing control attributes or by auto-sync
polls. A confirmation message appears, on clicking Finish button. If you select No or
cancel the dialog box, there will be a delay in showing the changes in the
administration console. This varies between 30-40 seconds.
Deleting adapters
Perform the following procedure to delete adapters.
To delete adapters
2 Expand the adapter type, select, and then right-click on the adapter type to be
deleted.
3 Select Delete.
4 On the Confirm Deletion screen, click OK to delete the selected adapter or click
Cancel to exit without deleting the selected adapter.
5 On clicking OK, the deletion in progress message is displayed.
Note
If you delete the adapter, corresponding instances are deleted; however
corresponding groups and devices remain.
After you edit or delete an adapter for HP OVO, the system might take several
minutes to respond if sub-processes are still running. As a workaround, you

can manually stop the process:
(Windows) Through Windows Task Manager, end the ovcodautil.exe process.

(UNIX) Run the kill ovcodautil command.
If you delete an adapter instance that was created using the automated
workflow feature, mark the agent as disconnected and then delete the adapter
instance. You can reconnect the agent immediately after deleting the adapter
instance.

Perform the following procedure to view adapter details in the Administration
Console.
To view adapter details

2 Expand the adapter-type folder and right-click on the adapter-type instance for
which the details are to be viewed.
3 Choose Details.
The adapter details screen is displayed.
4 Click Details to view auto-sync details and auto-sync errors.

Adapter auto-sync summary details display the statistics of the created adapter
as computed at the last auto-sync time.
Table 34: Summary Details

Fields
Description
Last Auto-sync done at
Displays the time at which the last auto-sync (create/update/poll) was done.
Fields
Description
Total Monitor Types
Displays the total number of monitor types associated with this adapter.
Total Instance Autosynced
Displays the total number of auto-synced instances.
Total Instances Created
Displays the total number of newly created instances.
Total Instances Failed
Displays the total number of instances that could not be newly created.
Total Unavailable
Instances
Displays the total number of instances that are not auto-synced as compared to
the previous list of auto-synced instances.
Total Duplicate Instances Displays the number of auto-synced instances that have already been created as
part of other adapter instances pointing to the same host IP address.
5 Click Close to return to Administration Console.
Searching instances
To view the details of particular instance(s) based on different requirements, it
would be cumbersome to view the details if adapter has thousands of instances per
monitor types. Search utility provides the flexibility to search the required instances
with the details. The details panel include the following tabs:
Auto-sync Details
If instances are not collecting the data, then you need to check its status of such
instances in Details panel to verify the reason. If status is Discovered but
Unavailable, then such instances are not available in target application. This
can be achieved by doing search either based on column Instance Details (either
completely or partially) or column Status.
To view the details of instances created successfully for any given monitor type
can be achieved by performing a search based on column monitor type (either

completely or partially).
To view the instances which are not available in target application itself can be
achieved by performing a search based on column Status.
Auto-sync Errors
To view the details of instances failed to create for any given monitor type can be
achieved by doing search either based on column monitor type (either completely
or partially) or based on column Instance Details (either completely or partially).
Viewing and deleting instances marked for deletion
Loading Errors
To view the error during discovery for given monitor type can be achieved by
doing search based on column monitor type (either completely or partially).
To search an index:
1 Expand the Adapters folder and select the adapter. Right click the adapter to
select the Details. The details page lists the summary of the instance created.
2 Click Details in the Summary page to view the details at instance level. The Autosync Details, Auto-sync Errors, and Loading Errors tab appears.
3 Select the required tab. To search the particular instance(s), select the column
based on which search should be done. Type the pattern and click Go. The details
of instances, that contain the matching pattern under selected column is
displayed.
Note
Similar procedure needs to be followed to select the BMC PATROL, BMC Portal,
SCOM, BMC TM ART, and BMC VMware Adapter.
Viewing and deleting instances marked for

deletion
Instances that are not available in the next auto-sync are marked for deletion and are
deleted after a specified number of days. You can view those instances and delete
them before the scheduled time.
To view and delete instances marked for deletion

2 Expand the adapter type and right-click on the adapter for which the instances
are marked for deletion.
3 Select Instances Marked for Deletion.
The Instances Marked for Deletion window is displayed, and it lists the monitor
type and details for those instances that are to be deleted.
4 Select the instances that you want to delete.
To search for instances, select either Monitor Type or Instance Details from the
list, enter the search criteria, and click Go.
To sort the instances in ascending or descending order, click on either the
Monitor Type or Instance Details heading. An arrow indicates in what order

the instances are sorted.
5 When you have finished selecting the instances, click Delete.

A confirmation dialog box is displayed.
6 Click OK to confirm that you want to delete the selected instances.

Perform the following procedure to recreate adapter instances that have been deleted.
To recreate instances from the Administration Console:

2 Expand the adapter type and right-click on the adapter for which the instances
are to be recreated.
3 Select Recreate Deleted Instances.
The Recreate Deleted Instance window is displayed, and it lists monitor-type
deleted interface instances.
4 Select the instances and then click Recreate.

The status message is displayed, and the instances are recreated.
5 Click Cancel to exit without recreating the deleted instances.
Show Auto-Sync progress

This gives the information about the progress of loading and creation of auto-synced
instances. This gives the total count of the instances and the number of instances
created. If auto-sync progress takes long time, you can close that window and later
view the status using this option.
To view the auto-sync progress

1 Expand the Adapter folder.
2 Expand the adapter type and right-click on the adapter for which the auto-sync
progress is to be viewed.
The first progress bar displays loading of instance for the selected application
instance is loaded for each monitor type.
A second progress bar displays the auto-sync progress and this starts when the
3 Click close to return to Administration Console.

This enables data collection for the loaded monitor instances of the selected adapters.
To enable data collection:

2 Expand the adapter type, select and right-click on the adapter for which data
collection has to be enabled.
3 Choose Enable Data Collection.
Disabling data collection

This disables data collection for the loaded monitor instances of the selected adapters.
To disable data collection

2 Expand the adapter type, select and right-click on the adapter for which the data
collection has to be disabled.
3 Choose Disable Data Collection.

You can use the pwd_encrypt command-line utility to create a DES encrypted
password. This utility is shipped with BMC ProactiveNet. The pwd_encrypt utility
accepts a plain text password and echoes the encrypted password to standard output.
To encrypt a plain text password, type the following command:
pwd_encrypt plainTextPassword
Example:
pwd_encrypt patrol
FB0A195D60626300
Generating a report for instances marked for

deletion
As part of daily jobs, BMC ProactiveNet creates a daily report that lists the adapter
instances that are marked for deletion and sends that report to the E-mail address of
the BMC ProactiveNet administrator. By default, the report is generated at 3:30 a.m.
The E-mail lists the instances that are marked for deletion, the number of days
remaining before those instances are deleted, and a link to a web page that includes
the following details:
Source Agent: the BMC ProactiveNet Agent on which the instance is created
Adapter Type: type of data adapter associated with the instance; for example,
PATROL, Portal, System Center Operations Manager (SCOM), BMC TM ART or

BMC VMware Adapter
Adapter Instance name: name of adapter instance

Device Name/IP: name of the device and the IP address of the computer that
hosts the adapter instance
Monitor Type: the type of monitor associated with the adapter instance
Monitor Instance Name: the name of the monitor instance associated with the
adapter instance
Update/Delete Time: the time that the adapter instance was last updated or deleted
Due Time to get Deleted: the time when adapter instance is schedule to be deleted
To generate the report, perform the following steps.
To generate a report for instances marked for deletion

1 In a text editor, open the pronet.conf file.
The file is located in the installDirectory \pw\pronto\conf directory.
The variable installDirectory is the location where you installed the BMC
2 In the pronet.conf file, verify that the following property is set as follows:
api.properties.sendMailForInstancesMFD=true
3 Save and close the pronet.conf file.

To turn off generation of the report, perform the following steps:
To turn off generation of the report for instances marked for deletion
The file is located in the installDirectory \pw\pronto\conf directory.
2 In the pronet.conf file, set the following property value:
api.properties.sendMailForInstancesMFD=false
3 Save and close the pronet.conf file.

To add, modify, or delete email settings for the selected reports, perform the
following tasks.
To add a new email address

1 Click the Reports tab.
2 In the Select column of the Report screen, select the check box corresponding to
the report.
3 Click Change Email.
4 On the Change Email page, select Add.
5 Enter the email ID to be added to the selected reports.
If the email ID exists then the newly entered email ID is appended to the
existing list.
6 Select Email Type.

7 Click Apply.
8 On the Change Email Summary page, click Done.
To change an existing email address

1 On the Change Email Summary page, select Modify.
2 Enter the existing email address.
3 Enter the new email address.
You cannot modify the E-mail Type.
4 Click Apply.
To delete a new email ID

1 On the Change Email page, select Delete.
2 Click Apply.
3 On the Change Email Summary page, click Done.
6
Integrating with the BMC Atrium
CMDB
This chapter provides details about retrieving and viewing BMC Atrium CMDB
component information in BMC ProactiveNet service models.
Note
If you are integrating with the BMC Atrium CMDB, all BMC ProactiveNet Servers in
your environment must be synchronized with a single CMDB for probable cause
analysis and event propagation to work properly.
Although it is possible to configure event propagation among the nodes of one BMC
ProactiveNet Enterprise setup, status propagation will not occur. Therefore BMC
ProactiveNet does not support distribution of service models across the nodes of
BMC ProactiveNet Enterprise setup.
If you configure a new Atrium CMDB with the BMC ProactiveNet Server; and you
need to publish a service model; you must manually update and restart the
publishing server configuration.
For information about installing and configuring the BMC ProactiveNet CMDB
extensions, see the BMC ProactiveNet Getting Started Guide.
Benefits of BMC Atrium CMDB integration

The BMC Configuration Management Database (BMC Atrium CMDB) is used for
sharing configuration data among various BMC products. BMC Atrium CMDB uses
a federated data model, featuring a centralized database linked to other data stores,
to share configuration data without the high setup and maintenance costs associated
with a pure centralized approach.
Integrating BMC ProactiveNet with the BMC Atrium CMDB has the following benefits:
Provides more effective Probable Cause Analysis: BMC ProactiveNet leverages
the service relationship information from the configuration items (CIs) in BMC
Chapter 6 Integrating with the BMC Atrium CMDB
345
User scenario
Atrium CMDB for the service model components that you are monitoring in BMC
ProactiveNet to produce better results for Probable Cause Analysis.
Keeps the service model components of BMC ProactiveNet synchronized with the
service model components stored in the BMC Atrium CMDB: By default, BMC
Atrium CMDB automatically publishes service model components to the BMC
ProactiveNet cell.
Faster deployment of BMC ProactiveNet: Instead of manually configuring CIs in
BMC ProactiveNet, you can import CIs from BMC Atrium CMDB to define the
components for monitoring.
User scenario
The section provides a high-level example of how service model objects in BMC
Atrium CMDB are published to the BMC ProactiveNet cell and how they are viewed
and monitored in BMC ProactiveNet.
Suppose that your BMC Atrium CMDB maintains an online ordering service model
that has three services - online ordering, databases, and web servers.
The database service consists of two database devices (BMC_Database
configuration items) called DB1 and DB2.
The web server service consists of two web server devices (BMC_SoftwareServer
configuration items) called Web1 and Web2.
The online ordering service is dependent on, and impacted by, the database
service, the web server service, and the configuration items.
The following illustration describes this relationship.
User scenario
In BMC Atrium CMDB, you use the BMC Impact Model Designer to plot out the
service model objects. In a sandbox dataset, you specify how each component in the
service model will be published to the cell. Because the Online ordering service is a
top-level consumer component, you configure it to publish with its provider
components. Do not change the default publication setting for the provider
components; by default, their publication is determined by the setting of their
consumer components.
After setting up the service model components, you promote the service model.
Promotion reconciles objects from the sandbox dataset to the production dataset. By
default, service model objects are automatically published to the BMC ProactiveNet
cell.
In the BMC ProactiveNet Administration Console, you select the published
component and view the impact relationships in the service model. In the BMC
ProactiveNet Operations Console, you monitor the status of components and the
impact on their consumers.
Figure 50 on page 348 shows an example of how the service model looks in the BMC
ProactiveNet Administration Console. The lock icon that is displayed by each
347
Creating and editing publication filters in the BMC ProactiveNet Administration Console
component indicates that the component cannot be edited in the Administration

Console. You can only edit a service model object in its source environment.
Figure 50: Example of a service model in the BMC ProactiveNet Administration Console
After you publish components, you associate the required monitors to these
components.
You can also use templates to add monitors. For details, see the BMC ProactiveNet
Monitor Guide.
By default, the services that you publish from BMC Atrium CMDB do not contain
any metrics. For an effective Probable Cause Analysis, you have to add those metrics
that indicate the health/status of the services. For details, see the BMC ProactiveNet
User Guide.
Creating and editing publication filters in the

BMC ProactiveNet Administration Console
Use publication filters to determine which components are published to the cell from
BMC Atrium CMDB. The filters retrieve the service model objects from the cell for
viewing and monitoring in the BMC ProactiveNet Administration Console or in the
BMC ProactiveNet Operations Console.
You can create publication filters using one of the following configuration item (CI)
selection methods:
Static CI selection method: select CIs imported from BMC Atrium CMDB from a
static list.
Dynamic CI selection method: select CIs imported from BMC Atrium CMDB
whose names match a specified pattern. The specified pattern uses regular
expressions.
After you filter CIs, you can select a component from those retrieved in the Services
Editor tab, and see the service model associated with that component (see Using the
BMC ProactiveNet Administration Console for service monitoring on page 733 for
details). The service models show components that are specified for publication
that is, CIs that are set to Inherit, Yes and Propagate, and Yes, Only Me in the BMC
Impact Model Designer.
You can locate and view a CI that is not specified for publicationthat is, set to No:
Do not publish me nor my providers in the BMC Impact Model Designer. You can
display the CI and its providers separately, but not as impact providers to
components in a service model where they are specified as No. See BMC Service
Modeling and Publishing Guide for details about component settings.
Note
If a previous filter is deleted, removal from the system could take some time. The
amount of time can depend on the number of CIs or other factors, such as an
inability to communicate with the cell (as when the cell is not running). During
this time the system cannot create another filter with the same filter ID.
Service models and instances of components and relationships are not imported if
they are marked for deletion (MarkAsDeleted=Yes) in BMC Atrium CMDB
For a list of supported service model component types, see the BMC ProactiveNet
Service Modeling and Publishing Guide.
To create a static publication filter

1 In the BMC ProactiveNet Administration Console, expand the Root =>
Advanced Options => BMC Atrium CMDB => Publication Filter folder.
2 Select and right-click the Publication Filter folder and select Create Publication
Filter.
3 Enter values for Filter Name and Filter ID.
By default, the Filter ID is the same as the Filter Name, but with spaces removed.
For example, if the filter name is CS Filter, the filter ID is CSFilter
4 (optional) Enter a 255-character-or-less description in the Description field.
349
5 Select Static (the default) from the CI Selection Method list.

6 Select (the default) or clear Include all impact providers of selected CIs.
7 Select (the default) or clear Show only top level CIs.
Top-level CIs are top-level consumers, that is, consumers that are not providers to
other CIs.
8 Select the CI type and click Retrieve.
9 From the list of available CIs that matches the selected CI type, select CIs that you
want to show in the service model and click Add, or click Add All to add all the
available CIs.
You can select CIs in the following ways:
Type a character in the Name field to show only CIs that contain that character.
The field is case sensitive.
Hold the Shift key to select adjacent CIs in the list, or hold the Ctrl key to select
non-adjacent CIs in the list.
10 Click OK to close the Create Publication Filter dialog box.
To create a dynamic publication filter

2 Select and right-click the Publication Filter folder and select Create Publication
Filter.
3 Enter values for Filter Name and Filter ID.
By default, the Filter ID is the same as the Filter Name, but with spaces removed.
For example, if the filter name is CS Filter, the filter ID is CSFilter
4 (optional) Enter a 255-character-or-less description in the Description field.
5 Select Dynamic from the CI Selection Method list.
6 Select (the default) or clear Include all impact providers of selected CIs.
7 Using regular expressions, type a pattern by which to match CI names.
8 Click the + button to add another pattern.
You can use up to 11 patterns. The patterns are connected by a logical AND operator.
9 Click OK to close the Create Publication Filter dialog box.
To edit publication filters

You can edit the following
2 Select and right-click the publication filter name and select Edit .
3 Make the required changes and click OK.

After you designate service model components for publication in the BMC Impact
Model Designer (an extension for BMC Atrium CMDB), and then promote and
publish the objects to the cell, you can view these objects through filters in the BMC
The Administration tab of the BMC ProactiveNet Administration Console indicates
whether service model components that originated from BMC Atrium CMDB and
published to the cell.
Expand the folder Root => Advanced Options => BMC Atrium CMDB =>
Publication Filter. The appearance of the Atrium Filter CIs and Providers and the
Atrium Filter Individual CIs folders confirm that components from BMC Atrium
CMDB are available from the cell.
Filter
Description
Atrium Filter CIs and

Providers
CIs that are published to the cell from BMC Atrium CMDB, with their impact
providers. This includes CIs that are specified in the BMC Impact Model
Designer as Yes and Propagate, and their impact providers that are specified
either as Yes and Propagate or as Inherit.
Atrium Filter
Individual CIs
Individual CIs that are published to the cell from BMC Atrium CMDB, without
their impact providers. This includes CIs that are specified in the BMC Impact
Model Designer as Yes, Only Me.
If you create additional filters in the Administration Console, the names of the filters
are displayed under the Atrium Filter folders.
351
Note
By default, imported components create devices without any monitor instances
associated with them. You must add the required monitored instances after you
import the components. See Associate monitors to CIs through the BMC
ProactiveNet Administration Console on page 754 for details.

You can view the history of publication requests to confirm the status of the request
or to troubleshoot issues.
From the Administration tab of the BMC ProactiveNet Administration Console,
expand the folder Root => Advanced Options => BMC Atrium CMDB. Select and
right-click Publication History and select View Publication History.
The Publication History window shows the date and time of each request, the
request status, and the publication source (or publisher) of the request.
The following table describes the different publication request statuses.
Table 35: Publication request statuses
Status
Description
Success
Publication request passed to the cell successfully
Unknown
Status of the publication request is unknown. The status can indicate that the publishing
server is waiting for a response from the system, or that a publication is in progress.
Wait some time and then click Refresh to the updated status. You can also close the
window and reopen it later.
Failure
Publication request failed to be passed to the cell. Common reasons include parts of the
system that are down, or responses that time out. Refer to the Publication Details pane of
the Publication History window for details.
The following table describes different kinds of publishers that can be the source of
requests to the publishing server.
Table 36: Publication sources for requests
Publisher
Description
Automated Publisher
Publication request sent automatically from the BMC Impact Model

Designer
Publisher
Description
cli@proactiveNetServer
Publication request sent through the CLI publish command on the

where proactiveNetServer is the name BMC ProactiveNet server
of the BMC ProactiveNet server
computer
pclassinfo@proactiveNetServer
Publication request sent through the CLI pclassinfo command on

the BMC ProactiveNet server
pint@proactiveNetServer
Publication request sent through the CLI pint command on the BMC
ProactiveNet server
penv@proactiveNetServer
Publication request sent through the CLI penv command on the BMC
ProactiveNet server
psapi@proactiveNetServer
Publication request sent by creating or editing static or dynamic

filters in the Administration Console
Publishing Server
Indicates that the publishing server was restarted
For details about CLI commands, see BMC ProactiveNet Command Line Interface
Reference Manual
Detailed information about each publication request is displayed in the Publication
Details pane of the Publication History window. See BMC ProactiveNet Service
Modeling and Publishing Guide to diagnose publication issues.
Note
The publishing server retrieves publication changes for a subscription from the
Notification Engine, a component in BMC Atrium CMDB. If the publication fails, the
system removes the current subscriptions and subscribes again to the Notification
Engine. This process causes the publishing server to retrieve and publish all service
model components, not only the latest changes. The Publication History window
reflects this activity.

Computer system configuration items (CIs) that are published to the cell from BMC
Atrium CMDB are displayed as devices in the BMC ProactiveNet Administration
Console.
In the Administration Console, you can view the computer system devices under the
Root => Device => Server folder. You cannot edit devices in the Administration
Console.
A device that is synchronized with BMC Atrium CMDB shows the following icon:
353
Note
Devices that are created by the following adapters, and published through BMC
Atrium CMDB, do not display icons as CMDB-synchronized devices:
VMware
PATROL VMware
7
Configuring and using Remote
Actions/Diagnostics
What are Remote Actions/Diagnostics?
The remote actions/diagnostics executes a command on a remote device. For
example, if you want to view the Top 10 CPU processes running on a remote system,
the remote diagnostics executes the required command on the remote system and
lists the Top 10 processes using remote login protocols.
A detailed diagnostics can only be triggered from BMC ProactiveNet server and not
from any other remote agent source.
The protocols supported by remote actions/diagnostics are:
xCmd protocol
The xCmd protocol enables an application to execute a command on a remote

host and does not require a port number. The xCmd protocol requires a remote
user name and password. xCmd is only supported on Windows server.
ssh (Secure Shell) protocol
The ssh protocol provides secure, encrypted connections for logging on to remote
computers, transferring files, setting up encrypted tunnels, and running remote
commands without manual authentication. The ssh protocol requires a remote
user name, password, and a port. ssh is the recommended protocol on Windows
and Solaris servers.
telnet protocol
The telnet protocol can pass on the data it has received to many other types of
processes including the remote logon server. Communication is established using
TCP/IP and is based on a Network Virtual Terminal (NVT). The telnet protocol
requires a remote user name, user password, system prompt, and a port.
Chapter 7 Configuring and using Remote Actions/Diagnostics 355
Properties files
Note
You need to change the protocol, if you have used a different protocol after
upgrading to the recent version of BMC ProactiveNet.
Properties files
When defining remote execution tasks, you may need to configure values in the
following properties files that reside on JServer server:
..\conf\ias.properties
..\conf\resources\centraladmin-strings.properties
..\conf\resources\remoteexecution.properties
Restart the JServer, if you have modified any of the .properties file.
ias.properties
The ias.properties file specifies the event slot names, key name values, and other
configuration items of remote execution under the text properties for remote execution.
Table 37: Remote execution properties in jserver.properties
Property name
Description
com.bmc.sms.ixs.remoteexecution.hostname_slot
Specifies the event slot name that contains the host

name value. The default value is mc_host.
com.bmc.sms.ixs.remoteexecution.instance_slot
Specifies the event slot name that contains the

instance. The default value is mc_object.
com.bmc.sms.ixs.remoteexecution.application_slot

application. The default value is mc_object_class.
com.bmc.sms.ixs.remoteexecution.domain_slot

domain value. The default value is mc_location.
com.bmc.sms.ixs.remoteexecution.ias_user_key
Specifies the key name that contains the name of the

user. The default value is ias_user.
com.bmc.sms.ixs.remoteexecution.ias_user_passwor
d_key
Specifies the key name that contains the password.

The default value is ias_user_password.
com.bmc.sms.ixs.remoteexecution.action_context_ke
y
Specifies the root element in the action.xml file. You

can enter the root element in the Action Name field
of the Create Remote Actions dialog box. The default
value is 2.
Property name
Description
com.bmc.sms.ixs.remoteexecution.search_credential_ Indicates the argument number (1, 2, 3, and so on) or

repository_key
slot name.
com.bmc.sms.ixs.remoteexecution.search_in_credent If the client does not send the key, then this
ialrepository
parameter determines whether to search in the
credential repository. Valid values are true and false.
com.bmc.sms.ixs.dataparser.allowHostVerification
Boolean true/false values that tells whether host

verification is done when you add a record to the
credential_repository. xml file. The default value is
set equal to true, meaning that host verification is
required.
centraladmin-strings.properties
The centraladmin-strings.properties file defines the default communication
protocols for different operating systems.
Note
If you modify the properties in the centraladmin-strings.properties file, you must

restart the BMC ProactiveNet Server to apply the changes.
remoteexecution.properties
The remoteexecution.properties file defines the timeout values and default ports for
the SSH, FTP, SCP, and Telnet protocols.

You can create remote actions to define the commands to be executed on the remote
device.
Before you begin

To create a remote action for the cell installed with a remote BMC ProactiveNet
Agent, you must add the following line to the mcell.dir file for that cell:
admin ias_Admin userName/passWord ProactiveNet_Server_hostName:3084
Once you have updated the mcell.dir file, restart the cell.
To create remote actions

2 From the Tools menu, choose Remote Actions/Diagnostics => Remote Actions/
Diagnostics.
The Remote Actions/Diagnostics Command definition dialog box appears:
Figure 51: Remote Actions/Diagnostics Command dialog box
3 On the Remote Actions/Diagnostics screen,

Select the Detailed Diagnostics option:
to use the event criteria formulae.
to use actions on an event only scenario.
For more information, see Defining the performance managed remote actions
on page 359
Select the Event management rules option:
to use actions/diagnostics for events.
to use actions associated with devices and monitor types.
For more information, see Defining the remote action rule and task on page
362
4 Click OK.
Note: Out-of-the-box remote actions that are available with the BMC ProactiveNet
Server use the psExec protocol. Remote actions that you create use the xCmd
protocol. The psExec protocol is not supported for user-created remote actions.
Defining the performance managed remote actions

You can create remote actions to define the commands to be executed on the remote
device.
To create performance managed remote actions through detailed diagnostics

1 From the Tools menu, choose Remote Actions/Diagnostics > Remote Actions/
Diagnostics.
2 On the Remote Actions/Diagnostics dialog box, select the Detailed Diagnostics
option.
The Remote Actions/Diagnostics Command dialog box is displayed:
Figure 52: Remote Actions/Diagnostics Command dialog box
3 On the Remote Action/Diagnostics Command dialog box, click Add.

4 On the Add Command screen, enter or select the following and click Next.
Item
Description
Name
Enter a unique name for the command.
Item
Description
Command
Enter the syntax for the command that will be executed on the target
computer. For example netstat. You can include macros in this
command. For more information, see Macros for Remote Action on
page 380.
If the command is very long, you can use the Edit button to enter or
edit the command syntax.
Show Output
Select this option to view the output in the Operations Console.
Configuration Diagnostic
Select this option to qualify this command to be run with every

configuration poll of select system monitors.
Time-out
Select the time-out period for execution of the command.

An error message is displayed if the time-out period is exceeded.
5 On the Device screen, select the operating system of device and click Next.By
default, all devices are selected.
Note
If you have selected a specific operating system then the remote action/
diagnostics will not be listed in the third page of Event Rule Wizard unless you
select the monitor type for the specific operating system in second page. For
Event Only Buyer, you have to select all Operating System while defining the
remote action/diagnostics.
6 On the Monitor Type screen, select the monitor types and click Next.By default,
all monitors are selected.
7 On the User Group screen, select the desired user group and click Finish.
Note
The access permissions set while defining the User groups takes precedence. If the
user group is defined with All Diagnostics in the Diagnostics tab, then the newly
created diagnostics will be available to those user groups irrespective of whether
they are selected/non-selected in the Add to User Group screen in the Add
Command module of the Remote Actions/Diagnostics wizard.
8 On Test your command screen, select the Target IP from the list and click Test to
test the command.
The Test your command dialog box is displayed.

Figure 53: Test your command dialog box
Note
From the test button, the command does not execute properly if it requires the
cell slot values that is to be resolved at run time. This occurs since there is no
associated event with the particular command.
For example:
msend a EVENT r CRITICAL m $msg
The value for $msg is not available while executing from Test button. This
option is available from an event.
9 Click Finish to save the detail diagnostics/remote actions.
Note
Upgrading the path for Remote DD's is not supported when you upgrade from
older version of the BMC ProactiveNet Server to a recent version.
By default the remote actions logs the error messages in the
RemoteExecution.log. To debug remote actions, set the property

log4j.rootCategory to DEBUG in the du_logger. properties file located in the
installDirectory\pw\pronto\conf\resources directory.
When you edit a defined remote action/diagnostics, there is no provision for
changing the access roles.
Remote actions/diagnostics is executed for events whose status changes from

blackout to closed.
If Windows server to Windows remote computer telnet fails, increase the value
of the maxconn and maxfail parameters as follows.
C:\>tlntadmn config maxfail=10

C:\>tlntadmn config maxconn=20
Defining the remote action rule and task

You can create remote actions to define the commands that are executed on the
remote device.
To create remote actions on events

1 From the Tools menu, choose Remote Actions/Diagnostics > Remote Actions/
Diagnostics.
2 On the Remote Actions/Diagnostics dialog box, select the Event management
rules option.
The Create Remote Actions dialog box is displayed.

3 On the Create Remote Actions dialog box, enter or select the following options
and click Next.
Item
Description
Action Name
Name that describes the action to be performed. This is the label that
appears on the Action >Remote Actions menu.
Each action name must be unique.
WARNING: Duplicate action names will result in KB compilation
errors.
Action Group
Name of the group to which the customized action belongs. You can
group similar actions under the same group name. However, you
cannot nest groups.
Command
String that contains the command to be run on the jserver or remote

system
If the command string includes double quotation marks, as in the ping
command, ping "{$mc_host}", forward slash is added to the command
in the action_name.xml file under the BMC_PROACTIVENET_HOME/
server/data/admin/actions directory: ping \{$mc_host}\.
You must manually edit the action_name.xml file to remove the slash
characters from the command string. Save the action_name.xml file to
return to the Infrastructure Management tab. Select the jserver
instance object, right-click to open the pop-up menu, and choose
Action > Reload.
If the command string includes a hard-coded path, then always specify
the path name using the UNIX style forward slash /, as in c:/Program
Files/BMC Software/Test1.exe, even if the target systems is Windows.
User Access Roles
Roles including Full Access, Service Administrators, Read Only, and so

onthat have permission to execute this action. You can choose one or
more roles.
The available roles are listed in the Impact Administration server to
which your BMC Administration console is currently connected.
Note: The remote actions that are listed on the Remote Actions/
Diagnostics menu in the operations console are defined in both the cell
and the ProactiveNet database server. When you create a remote action
or detailed diagnostic from the administration console and restrict
access to a particular user group or role, you restrict the remote actions
from the ProactiveNet database server only and not from cell. Users
would still see the remote actions defined in the cell even though they
might be restricted from seeing and executing remote actions defined
in the database server.
Item
Description
Run Location
System on which the action is run. It can be any remote system that can
be pinged from the BMC ProacativeNet Performance Management
Server, or the local system on which the BMC ProacativeNet
Performance Management Server resides.
If you select Remote, you can deploy scripts to the remote system.
Operating System on Run Machine Specifies the operating system on which the remote action is to be
executed. This can be the operating system of the remote computer or
the operation system of the computer where the jserver resides.
Impact Manager(cell)
Name of the cell that receives the event associated with the action. The
action rule is defined in this cell.
Impact Administration Server
The name of the Impact Administrator Server instance on which the

action task is defined
Adding event criteria

The Event Criteria Formula field of the Create Remote Actions dialog box, allows
you to enter an event criteria.
When you define an event criteria, you build a selector that acts as a filter for the
incoming event that is associated with the action rule and action task. You can define
the selector, and the consequent event both broadly or narrowly. If the event does
not satisfy the criteria, then the action rule and action task for that event are not
available.
You should be familiar with Master Rule Language and Baroc class definitions
before developing complex event selectors. For more information on developing
complex event selectors, see the BMC Knowledge Base Development Reference Guide.
Event criteria are essentially Master Rule Language (MRL) event definition. You can
specify the event class, slot values, and operators of the event definition. For
interactive remote execution, this is the definition that the incoming event must
satisfy before the action rule invokes the remote action.
Note
Automatic remote execution requires a two-step validation. First, an event policy

automatically calls a specified action rule provided it satisfies the event criteria of the
policy. Second, the action rule that you define in the Create Remote Actions dialog
box, invokes the remote action provided it satisfies the event criteria that you have
defined in the Add Event Criteria dialog box.
Refer to the following table for event criteria descriptions fileds.
Table 38: Add Event Criteria descriptions

Field/Control button
Description
Description
Optional. Enter a description of the event. This field

can be used to classify the selectors.
Event Class
Select the list of event classes and subclasses in the

Class Chooser dialog box.
Slot
List of available slots.
Operator
List of available operators that link the slots to the

value strings.
Value
Enter a value for the slot.
Insert
Places the slot-operator-value string in the display

area, where you can review and edit. When placing
multiple slot-value combinations, the default
connector is AND. You can specify other connectors
from the list.
Edit
Displays the selected slot-value combination in the

editable fields above the display area.
Delete
Removes the selected object from the display area.
Group
Adds parentheses around the selected object to

indicate the order and the logic of the operation. You
can create nested objects using the Group button.
Move
Moves the placement of the selected object to the left

or right.
1 Complete the remaining fields using the guidelines from the following table:
Table 39: Data fields (part 2): Create Remote Actions dialog box
Field
Description
Time Out (Milliseconds)
Interval in milliseconds before the action is canceled.

The action can be canceled if the Impact
Administration server does not receive a response
before the customized or default timeout interval.
Field
Description
Use Stored Login Credentials
Boolean value (True or False) that indicates if you

can execute the action using either of the following:
the user credentials of the remote host system =
True
public key authentication = False (default)
Note: Only Event Management remote actions use
the credential_repository.xml file for credentials.
Because ProactiveNet remote actions only can be
triggered on a device-associated event, and
ProactiveNet remote actions use credentials
provided in the device data.
If you choose False (default), then your public key
account on the system is sufficient to launch the
action. The procedure does not search the
credential_repository.xml file for login credentials.
If you choose True, then the routine uses the remote
systems account information as defined in the
credential_repository.xml file (login_user and
login_password).
Reminder: For automatic remote execution, you
must specify an JServer user name and password in
the Admin record. By default, admin/admin. If you
want to modify, restart the cell.
Deploy(Use with Remote Run Location Only)
Boolean value (True or False) that indicates if you

can deploy a script from the JServer system to the
remote system and then execute the script through a
RunRemoteTask command.
The default is False, indicating that no script is
deployed.
You can only deploy a script when the selected Run
Location option is Remote. You cannot deploy a
script on a remote system when the Run Location
option is Local (jserver System). For more
information on Run Location, see Defining the
remote action rule and task on page 362
Script To Deploy (optional)
Name of the script or .bat file. If the boolean value is

set to True, the the script or .bat file is displayed.
Script Path on Destination Machine
File path of the script on the system on which it is

executed.
2 Click Add Actions.

Run iadmin -reinit actions to reload the Jserver
Assigning roles to actions

You can add or remove user roles for these actions by modifying the action
definition files (mc_actions.mrl or ao_actions.mrl depending on the type of action)
found at installDirectory \server\etc\ cellName \kb\bin.
For upgrade users

If you have created devices during the previous releases, the device does not update
to the latest port. You must manually edit the port.

Provide the required credentials to execute a remote action/diagnostics on a remote
device.
To provide credentials for detailed diagnostics option

1 Log on to the BMC ProactiveNet Administration Console.
2 In the General Administration tab, expand the Devices folder and select the
device for which you want to add credentials.
3 Right click on the device name, and select Edit.
4 On the Remote Actions/Diagnostics tab in the Edit Device dialog box, enter the
credentials and click OK.
Figure 54: Remote Actions/Diagnostics tab of the Edit Device dialog box
There can be only one credential per device. All remote actions will use the same
credentials. The supported protocols are ssh, telnet, and xCmd.
Working with credential records for event management rules

option
You can define a credential record for each application on a remote system for which
you want a specific user to execute actions. You can use the iadmin command line
interface for the following options to update credential records in the
credential_repository.xml file and to initialize any changes to the action task
definitions in the .xml files under the installDirectory\pw\server\data\admin
\actions\folder.
Following are the iadmin options for the credential record:
-acr: adds a credential record to the credential_repository.xml
-mcr: modifies an existing credential record
-dcr: deletes a credential record
-lcr: lists the credential

-reinit actions: loads the action files after any additions or changes to the action
tasks defined in the .xml files under installDirectory\pw\server\data\admin

\actions\
Guidelines for the credential records

The asterisk (*) functions as a wildcard. It is a valid entry only for the
applicationname and applicationinstancename fields. It indicates that any value of
the applicationname or applicationinstancename field is acceptable.
The search algorithm does not support pattern matching. Your entry must match
exactly the underlying value.
Any alphanumeric value is valid for the applicationname and
applicationinstancename fields.
Enclose any password values in double quotation marks to ensure proper
processing. On UNIX systems, run the iadmin command without the bash shell to
reinforce the proper processing of the password value.
The required fields in which you must enter a value are:
credentialId
hostname_or_domain
applicationname (wildcard is permitted)
applicationinstancename (wildcard is permitted)
loginuser
Working with credential records for events

You can define a credential record for each application on a remote system for which
you want a specific user to execute actions. You can use the iadmin command line
interface for the following options to update credential records in the
credential_repository.xml file and to initialize any changes to the action task
definitions in the .xml files under the installDirectory\pw\server\data\admin
\actions\folder.
Following are the iadmin options for the credential record:
-acr: adds a credential record to the credential_repository.xml
-mcr: modifies an existing credential record

-dcr: deletes a credential record
-lcr: lists the credential
-reinit actions: loads the action files after any additions or changes to the action
tasks defined in the .xml files under installDirectory\pw\server\data\admin

\actions\
Guidelines for the credential records

The asterisk (*) functions as a wildcard. It is a valid entry only for the
applicationname and applicationinstancename fields. It indicates that any value of
the applicationname or applicationinstancename field is acceptable.
The search algorithm does not support pattern matching. Your entry must match
exactly the underlying value.
Any alphanumeric value is valid for the applicationname and
applicationinstancename fields.
Enclose any password values in double quotation marks to ensure proper
processing. On UNIX systems, run the iadmin command without the bash shell to
reinforce the proper processing of the password value.
The required fields in which you must enter a value are:
credentialId
hostname_or_domain
applicationname (wildcard is permitted)
applicationinstancename (wildcard is permitted)
loginuser
To add a credential record

1 From the installDirectory\pw\server\bin directory, execute the iadmin
command using the -acr option, and follow the syntax in the example.
iadmin -acr userorgroup=<user/group>:credentialId=<string>:
applicationname=<string>:applicationinstance=<string>:
hostname_or_domain=<Hostname or Domain>:loginuser=<string>:
loginpassword=<string>:executeuser=<string>:executepassword=<string>:
login_user_domain=<string>
The following table lists the required fields for the -acr option. You must include
values for the required fields; otherwise the credentials record is not created.
Table 40: Required fields: adding a credential record
-acr field name
Description
credentialId
The user account (default) or the group Id value.
hostname_or_domain
The host name of the remote system, as in

myremotecomputer123, or the domain name in
which it resides.
applicationname
Name of the application. You can enter an asterisk

* to bypass a specific application value.
applicationinstance
Name of the application instance. You can enter an

asterisk * to bypass a specific instance value.
login_user_domain
This option is required when the login account

belongs to an MS Windows system.
The userorgroup field is optional. If you leave the userorgroup field blank, the acr argument assumes that user is the selection, and the value you enter in the
credentialId field (required) is the user account. To specify a group Id value, set
the userorgroup field equal to group, and then specify the group value in the
credentialId field.
Using the iadmin command syntax, you enter password values in clear text.
However, the passwords are encrypted when they are added to the
credential_repository.xml file.
To modify a credential record

command using the -mcr option, following the syntax shown in the example:
iadmin -mcr userorgroup=<user/group>:
credentialId=<string>:hostname_or_domain=<string>:
applicationname=<string>:applicationinstance=<string>:
login_user_domain=<string>:loginuser=<string>:
loginpassword=<string>:executeuser=<string>:
executepassword=<string>
You can modify any of the fields, but you must enter required fields listed in the
following table to create a record
Table 41: Required fields: modifying a credential record

-acr field name
Description
credentialId
The user account (default) or the group Id value. If

you specify a group Id value, you must set
userorgroup equal to group.
hostname_or_domain

myremotecomputer123, or the domain name where
it resides (domain).
applicationname

* to bypass a specific application value.
applicationinstance

asterisk * to bypass a specific instance value.
To delete a credential record

command using the -dcr option, as in the following syntax example.
iadmin -dcr userorgroup=<user/group>:credentialId=<string>:
hostname_or_domain=<string>:applicationname=<string>:
applicationinstance=<string>
To delete a record, you must specify values for the required fields listed in the
following table
Table 42: Required fields: deleting a credential record
-acr field name
Description
credentialId
The user account (default) or the group Id value.
hostname_or_domain

myremotecomputer123, or the domain name where
it resides.
applicationname

* to include all values.
applicationinstance

asterisk * to include all values.
To list credential records

command using the -lcr option, as in the following example. You do not have to
specify any credential record parameters.
iadmin -lcr
How Jserver searches for credentials

After the action task is invoked by the action rule, the Jserver searches the credential
record for the corresponding remote login credentials in the following sequence:
1 Jserver_USER + ApplicationName + ApplicationInstanceName + Host
2 Jserver_USER_GROUP + ApplicationName + ApplicationInstanceName + Host
3 Jserver_USER + ApplicationName + ApplicationInstanceName + Domain
4 Jserver_USER_GROUP + ApplicationName + ApplicationInstanceName +
Domain
5 Jserver_USER + ApplicationName + * + Host
6 Jserver_USER_GROUP + ApplicationName + * + Host
7 Jserver_USER + ApplicationName + * + Domain
8 Jserver_USER_GROUP + ApplicationName + * + Domain
9 Jserver_USER + * + * + Host
10 Jserver_USER_GROUP + * + * + Host
11 Jserver_USER + * + * + Domain
12 Jserver_USER_GROUP + * + * + Domain
13 Jserver_USER + * + ApplicationInstanceName + Host
14 Jserver_USER_GROUP + * + ApplicationInstanceName + Host
15 Jserver_USER + * + ApplicationInstanceName + Domain
16 Jserver_USER_GROUP + * + ApplicationInstanceName + Domain
The wildcard * in the ApplicationName and ApplicationInstanceName fields
indicates any value.
If you are implementing automatic remote execution, the Jserver searches the
credential records for an Jserver_USER with the same value as the Jserver user
name defined under the Encryption Key parameter of the Admin record.
Therefore, to use the default Admin record, you must modify the default
Encryption Key value of 0 by changing it to a specific Jserver user name and
password. Then you define in the credential record the jserver User with the
credential Id set equal to the value you specified in the Encryption Key value of
the Admin record.

Remote action execution gets triggered on the following scenarios:
Using Event Rule Wizard: On receiving an event, matching event rules are
identified. If the matching event rule has a remote action assigned, the remote
action is executed. An event rule can be defined through the BMC ProactiveNet
Operations Console. For more information about adding an event rule, see the
BMC ProactiveNet User Guide.
Using Remote Action policies: To set up automatic remote executions that are
triggered by events, you must first define a remote execution policy using the
remote execution policy feature of the BMC ProactiveNet Console. The policy
contains the definition of the event that triggers it. When the specified event is
received, it triggers the rule, which invokes the remote action. For more
information, see Defining the remote action policy on page 374
Using the Event list User Interface(UI): You can also trigger a remote action from
the Event list User Interface. For more information, see Executing remote actions
on page 377. From the event list UI you can select any of the pre-configured
commands which is defined. You can select the command and execute. For more
information, see BMC ProactiveNet User Guide.
Using All devices Grid View in the BMC ProactiveNet Operations Console: If a
remote action is defined for an associated device of a particular operating system

and monitor types, the remote action is listed under the tools option for the device
and instance of the monitor type in the Operations Console.
Defining the remote action policy

In this procedure you are defining a policy that will automatically call a specified
action rule provided the incoming event satisfies the remote action policys event
criteria. The associated action rule, in turn, invokes the remote action provided the
same event satisfies its event criteria.
Before you begin

If an appropriate selector definition does not already exist, use the Edit => Selectors
=> New Selector... menu option to define the event criteria for the incoming event.
Be sure that the selectors event criteria correlate with the event criteria of the
selector you defined for the action rule in the Create Remote Actions dialog.
To define selector criteria

Follow these steps to define the event selection criteria:
1 In the BMC ProactiveNet Administration Console, go to the Administration tab,
and select the Event Management Policies tab.
2 In the tree view, open the By Selector folder and highlight the selector that you
added to the remote action policy to open the Selector panel.
3 Highlight this selector in the selector list of the Selector panel.
4 Click the Update Event Selector icon in the tool bar to enable the edit function.
5 In the Event Selector Criteria list of the Selector panel, highlight the selector and
click Edit to open the Edit Criteria dialog box.
6 In the Edit Criteria dialog box, specify the slots and values for events that you
want the selector to match.
For example, you can specify the matching criteria in the event message slot,
such as $EV.msg contains unreachable.
7 Click OK.
To define a policy
1 In the tree view under My Production, open the server cell entry.
2 Choose the Remote Action Policy type under the By Policy Type folder.
The Remote Action Policy definition window is opened, as shown in Figure 55
on page 376.
Figure 55: Remote Action Policy definition window
3 Choose Edit => New Policy , or click the Add Event Policy icon in the tool bar.
4 In the Selector Chooser dialog box, choose the selector to which this policy and
designated remote action apply. Then click OK.
You can use a default or a custom selector.
5 In the Remote Action Policy tab, enter the policy name (required) and a
description (optional).
6 Designate whether the timeframes are enabled. If enabled, indicate whether
policy activation timeframes are always active (default value), or select the option
to define your timeframes schedule.
7 In the Action name list, select the remote action to apply to this policy. The action
rule that you select should have event criteria that correlate with event criteria of
the policy. You can select from predefined or customized actions, including BMC
Atrium Orchestrator workflow actions.
8 Click OK.
The event selection criteria and the remote action are applied to the remote action
policy.

Remote Actions can be executed through automated actions and on demand. You
can execute the automated actions by creating an event rule. If an action is executed
in an event rule, the request is sent to the server. The server in-turn contacts the
particular remote devices with the credentials of the specific devices. The server is
connected to the remote devices and the command is executed on the remote
devices. When the actions are executed for device automatically, you can view the
Detailed Diagnostics icon on the Intelligent Event
result of actions by clicking the
History page or on the Events List page of the BMC ProactiveNet Operation Console.
Click the relevant event using Tools menu from the event list of BMC ProactiveNet
Operations Console to view the results of the action.
When you use a remote action, it is issued from your local installation of the
Operations Console but is executed on the computer where the BMC ProactiveNet
Operations Management cell or the BMC ProactiveNet cell is installed.
To respond to an event by using a remote action

1 From the event list, select an event.
2 Click the blue wrench icon in the Tools Menu column.
3 Click Remote Actions/Diagnostics and then select a remote action.
Note
The number of remote actions that you can execute for a BMC ProactiveNet
Operations Management cell varies from that available for a BMC ProactiveNet cell.
4 To access the results of the remote action, in the event list row, click the Action
Result(s) icon in the Message column.
5 In the Event Remote Action Results dialog box, you can perform the following
operations:
Export the information about the remote action to a file by selecting the action
information and clicking Export.
View the output, errors, and details about the remote action by clicking the
corresponding tab.
Adding the AlarmPoint integration

The AlarmPoint integration for BMC ProactiveNet provides the ability to notify
AlarmPoint users on any device if an event in BMC ProactiveNet meets the
notification criteria. BMC ProactiveNet processes the events it receives, and sends
them to the AlarmPoint Java Client. The AlarmPoint Java client forwards the events
to AlarmPoint, which notifies the user on the specified notification device.
AlarmPoint client must be installed where the BMC ProactiveNet cell server is
installed. With the AlarmPoint integration, the user is notified through sms, email,
and phone messages.
On successful setup of BMC ProactiveNet server cell with AlarmPoint, the notified
event collectors are created in the Operations Console. Collectors are created when
an event rule is generated. Figure 56 on page 378 shows an example of the notified
event collectors in the Operations Console.
Figure 56: Notified events in the Operations Console
To notify an AlarmPoint user of alarms or events, create an event rule using Run
Command on ProacativeServer. Enter the pw_AlarmPoint - u<user name> in the
Path field. If you do not enter the user name, the event is notified to the default user.
E-mail will be sent to the configured user. For more information on the AlarmPoint
integration, see the Event Administration chapter of the BMC ProactiveNet User
Guide.
Configuring Alarm Point for Window and Solaris

The following configuration should be done in custom/conf/pronet.conf for
AlarmPoint to function with the JServer.
Change the property for Alarm Point in custom/conf/pronet.conf.
Windows: #pronet.jserver.alarmpoint.path=[<AP_Path>\\APAgent. By
default the property is pronet.jserver.alarmpoint.path=C:\\APAgent, or the
path where APAgent is installed.
Solaris: pronet.jserver.alarmpoint.path= <AP_Path>/APAgent. For

example, pronet.jserver.alarmpoint.path=/opt/alarmpointsystems/
APAgent.
Execute the following BMC ProactiveNet CLI command to initialize the change:
pw jproperties reload

When you use a remote action, it is issued from your local installation of the
Operations Console but is executed on the computer where the BMC ProactiveNet
Operations Management cell or the BMC ProactiveNet cell is installed.
To respond to an event by using a remote action

2 Click the blue wrench icon in the Tools Menu column.
3 Click Remote Actions/Diagnostics and then select a remote action.
Note
The number of remote actions that you can execute for a BMC ProactiveNet
Operations Management cell varies from that available for a BMC ProactiveNet cell.
4 To access the results of the remote action, in the event list row, click the Action
Result(s) icon in the Message column.
5 In the Event Remote Action Results dialog box, you can perform the following
operations:
Export the information about the remote action to a file by selecting the action
information and clicking Export.
View the output, errors, and details about the remote action by clicking the
corresponding tab.

Remote Action/Diagnostics that are auto-triggered have their output saved in the
database and this information is accessible from the Diagnostics column in the
Intelligent Action History page.
The Detailed Diagnostics icon is displayed if a diagnostics has been triggered.
Click the Detailed Diagnostics icon to show the diagnostic output. If this column
displays None, then there are no diagnostics for that event. To view the actions result
for external events, select particular event and select Logs and Notes.
To manually view the results of Remote Action on an event

1 Log on the BMC ProactiveNet Operations console.
3 From the Tools menu, select Remote Actions/Diagnostics.
To view the results of Remote Action

2 View the results of the remote action by using one of the following methods:
Click the Action Results
icon on the message column.
Click the wrench icon

In the Tools Menu column. From the pop-menu select Action Results
Note
When the DD is edited and renamed, then the display of the DD output of the
associated events from the BMC ProactiveNet Operation Console is not shown.

The command option while creating a remote action lets you define the following
parameters:
$device - Device name
$srcip - This is the IP of the source agent on which the monitor instance is
running. If there is no Source Agent attribute for a monitor or if it is a Non PNET

Event, then this will be the IP of the device
$targetip - This is the IP of the TargetIP attribute available for the monitor
instance. If there is no TargetIP attribute for the monitor or if it is a Non PNET

Event, this will be N/A
$ip - If there is an attribute Target IP for the monitor, $IP will show the ServerIP. If
there is no TargetIP attribute, this will be the Device IP.
$instancename - The name of the monitor instance while creating/updating a
monitor instance.
$monitortype - Name of a Monitor Type created by BMC ProactiveNet developers
or external developers if users write an SDK monitor.
$rulename - event rule name that triggers this command. This is applicable only if
the diagnostic command was triggered by an event rule. If not, a N/A would be
displayed as a result for this parameter.
$pronethome - Home directory where BMC ProactiveNet software is installed.

$status - The status of an event (Open or Closed). Applicable only when the
diagnostic command is triggered from Event List page and Event history page.
From other pages, N/A will be displayed as output for this parameter.
$severity - The severity of an event (Critical, Major, Minor). Applicable only when
the diagnostic command is triggered from Event List page and Event history
page. From other pages, N/A will be displayed as output for this parameter.
$mc_ueid - The universal event identifier. When an event is propagated, the
receiving cell gets a new local identifier, event_handle, but the event keeps the old
universal identifier mc_ueid. For example, t2000-alr-2356.
Events that are BMC ProactiveNet events have the format as <host><number>.
Events that are BMC ProactiveNet abnormalities have the format as
<host><number>.
Events that are BMC ProactiveNet external/imported events have the format as
<host><number>.
$mc_location - Location at which the managed object resides. For example,
labs.bmc.com
$mc_host - Fully qualified name of the host on which the problem occurred. For
example, t2000.labs.bmc.com
$mc_host_address - Network address corresponding to the mc_host slot. For
example, 172.23.30.78
Note
This slot can contain some other type of information in which a host value is
not meaningful.
$mc_object_class - Identifies the class of an object. For example, Windows Process.
If the object class cannot be derived from the original event, it should be filled in
during enrichment.
$mc_object - Subcomponent of the host to which the event is related. For example,
http://www.bmc.com or Drive = C:\Program Files\ProactiveNet, Target IP/Host

Name = 172.22.173.108
$mc_tool_class - A user-defined categorization of the tool reporting the event. For
example, the mc_tool_class value for an SNMP adapter could be SNMP. And the
mc_tool_Class value for an NT EventLog Adapter might be NT_EVLOG. The
mc_tool_class value for native events is PNET. For BMC ProactiveNet events, this
slot contains the string PNET.
$mc_tool - Any event is within any value that can further distinguish whether the
event is coming from within a mc_tool_class value. For example, for the NT Event
Log Adapter, it could be the name of the log to which the incident was logged. If
the mc_tool_class is a management tool such as PATROL or ITO, then the mc_tool
should be a string that enables an action on the event to initiate a communication
in context with the mc_tool. For BMC ProactiveNet events, this slot contains the
fully-qualified DNS name of the BMC ProactiveNet Server.
$status - Status value of the event.

$severity - Severity value of the event.
$mc_priority - Current priority of the event. Possible value include PRIORITY_5 is
considered as lowest priority, PRIORITY_4,

PRIORITY_3,PRIORITY_2,PRIORITY_1 are considered as highest priority.
Note
Macros are whole-word substitutions and do not work the way regular
expressions does.
The given example illustrates the usage of macros in general.
For example on usage of $MC_PRIORITY. If $MC_PRIORITY is used as /tmp/
$MC_PRORITY, the macro replacement will not work.
The correct usage for this macro is $MC_PRIORITY as a standalone word. It
will not work if you use suffixes or prefixes with the macro.
$msg - Text description of the event. For example, Sybase ASA Intelliscope
Forced Commits, 7.370 per sec is above All Baseline.
$mc_notes - List of free text annotations added to the event. The contents of this
slot is implementation dependant. Rules or users should not rely on a particular

value in this slot.
$mc_long_msg - BMC ProactiveNet events, more information is stored in
mc_long_msg.
$mc_owner - Current user assigned to the event.

$mc_origin_class - Identifies the event management system type. This slot may
have the same value as the mc_tool_class slot if this is only a two-layer
implementation.

This section provides information to help you troubleshoot issues that you might
encounter when implementing remote actions in your environment.
Executing reboot command via remote action results in

timeout messages
When you execute the reboot command on a remote system, you may receive a
timeout message on an action result event even though the remote system was
rebooted successfully.
For example, if you execute a reboot action without specifying the execute_user
parameter in the credential_repository.xml, the remote system is rebooted, but the
Server does not receive a response from the remote system. Because it does not
receive any response, it displays a timeout message, such as exit code 111: Timeout
occurred while reading commands output.
If you execute a reboot action by specifying the execute_user parameter in the
credential_repository.xml, the remote system is rebooted, but the Server also does
not receive a response from the remote system. The server cannot determine whether
the lack of a response is due to a timeout or some other failure such as loss of a
network connection. In this context, it displays a message, such as exit code 1007:
Encountered error while waiting for system response. May be timed
out.

The following table describes the common error codes that could be displayed while
executing the remote actions.
Table 43: Remote actions\diagnostics error codes
Error code
Description
2001
Wrong command prompt for the specified protocol or timeout

occurred while waiting for the command prompt.
1007
Encountered error while waiting for system response. Action may have
timed out.
1006
Action timeout for the run remote task
1004
Remote action has failed. Check the log file $PRONTO_HOME /logs/ias/
ias0.log for additional information.
1003
Invalid credentials for SSH
1002
Protocol not available. Unable to connect to host. Connection refused.
129
Binary command not found in path
125
121
Error when trying to connect with the PsExec service
120
PsExec protocol issue: client or server is down
111
Action timeout occurred for Run task. The timeout occurred while
reading the command output.
99
Credentials not found
Remote action executed successfully
-1
Remote action execution is pending. User Response: Press F5 to refresh.

Exit code returns to 0.
-2
ExecuteActionException. Check the log file $PRONTO_HOME /logs/ias/

-3
ExecuteActionException. Check the log file $PRONTO_HOME /logs/ias/

-4
Event deviceID is invalid
-8
Invalid device ID
-9
-10
Unable to get device credentials for device ID
-12
Could not retrieve command arguments for actionID
Error code
Description
-13
Unable to retrieve remote action details for actionID or Detailed

Diagnostics not available and may have been deleted
-14
Unable to retrieve remote action details for actionID
8
Setting up diagnostic commands
Diagnostics wizard
Launched from the Diagnostics Wizard option in the Administration Console and
triggered from the Operations Console, this powerful diagnostics feature helps
identify problems by executing specific commands registered on the BMC
ProactiveNet system. Unlike scripts that are used in the Monitor Wizard, userdefined 'diagnostic' scripts are not restricted to numeric data, but may also contain
text. Defining this type of command is appropriate when there is a large amount of
data that may not be well-defined, but is useful for diagnosing a problem. For
example, returning the output of a netstat command.
User-defined diagnostic commands are extremely valuable in helping isolate a
problem, which would not be possible to do using only statistical data returned from
monitors.
Consider the system commands normally run on a system when troubleshooting a
particular problem. These are the same commands you may want to integrate with
BMC ProactiveNet as a 'diagnostic' command to leverage the full power of BMC
ProactiveNet infrastructure.
BMC ProactiveNet offers two types of registered commands:
Preconfigured Commands
User-defined Commands
These diagnostic commands can be launched (on any agent) from the Operations
Console on demand or can be auto-triggered when tied to an Event Rule. When a
diagnostic is auto-triggered, the output of the script is auto-saved and correlated
with the event. The output appears in block text format. Refer Event Rule
Management for more details on setting up auto-triggered diagnostics.
For example, if a Web server in your network is suddenly receiving a flood of
connections, you might normally run the 'netstat -an' command to view the source of
Chapter 8 Setting up diagnostic commands
387
Script
connections. Rather than require this domain knowledge to be remembered by all

users, and simultaneously require them to manually access each computer in the
network, you can register these commands with BMC ProactiveNet. This enables
users to have centralized Web access to these troubleshooting scripts. This saves time
in isolating problems and enables greater leverage of domain knowledge.
A diagnostic command registered using Diagnostics Wizard (Administration
Console) is displayed as an available tool in the Tools menu (Operations Console).
For executing a DD, the user account associated with the corresponding monitor
requires Read access to the various tables in the database.
Note
Do not begin a detailed diagnostic command name with a number or special
character if you are going to associate it with an event rule. Such commands do
not get executed.
DD's are listed under a device based on Detailed Diagnostics (DD) against
Operating System association. Monitor type against DD association will be used

only when the DD's are shown against a monitor instance.
Script
Note
It is the responsibility of the administrator to ensure that the required scripts are
accessible to BMC ProactiveNet Agent.
Do not begin a detailed diagnostic command name with a number or special
not get executed.
Register a user-defined Script command

Follow the procedure given below to register a command.
To register a user-defined script command

1 In the Administration Console, select Tools => Diagnostics Wizard => Script
Script
The Diagnostics Command window appears. Available commands, if any, will
be listed on the window.

Button Options
Add - Click this to add a new command.

Edit - Click this to modify a previously registered command.
Delete - Click this to remove the command from the system.
Cancel - Click this to exit the Diagnostics Wizard.
2 Click Add. The Add Command window appears.

3 Fill in the required information on the configuration screen.
Name - Specify a unique name to the command you are adding.
Processing Options - Command or URL
URL option lets you add URL addresses. Parameters are also applicable to this
option.
For example: http://finance.yahoo.com/q?s=$instancename&d=t . If this URL

is launched against a monitor instance with instance name SUNW, it launches
Yahoo's stock quote page for Sun Microsystems.
The Command option lets you define the following system parameters:
$pronethome - Home directory where BMC ProactiveNet software is installed.
$ip - IP address of the device. If the diagnostic command triggered by event
rule or the diagnostic command invoked from the event matrix or All
Events then the value of this parameter is the IP address of the source agent
for the monitor associated with the event.
$device - Device name.

$targetip - IP address of the target device. If the target device is not
applicable, N/A will be displayed.
$scrip IP address of the source agent.

$instancename - Also known as Monitor Instance Name. It is the name
given by a BMC ProactiveNet Administrator when creating/updating a

monitor instance.
$monitortype - Name of a Monitor Type created by BMC ProactiveNet
developers or external developers if users write an SDK monitor.
389
Script
$rulename - Also known as the Event Rule name. This is the event rule that
triggers this user command. This is applicable only if the diagnostic

command was triggered by an event rule. If not, a 'N/A' would be displayed
as a result for this parameter.
$status - The status of an event (Open or Closed). 'Normal' will be displayed
if there is no event.
$severity - The severity of an event (Critical,Major, Minor). 'Normal' will be
displayed if there is no event.
Instance Input Configuration Parameters

Input Configuration Parameters for the monitor instance also serve as useful
parameters for user-defined scripts. To access the parameters, you must know their
names internal to BMC ProactiveNet. The procedure to obtain the names is
described as follows:
Run the command pw device help -mlist to obtain a list monitor names.
Monitor type names are in the extreme right column of the output.
Run the command pw export meta config MonitorTypeName to retrieve a list

of configuration parameters for the given monitor type.
For example:
$ pw export meta config MSSQLServerQuery
MSSQLServerQuery (25061)
CONN_TYPE (250602)
DATA_SOURCE (250606)
DB (250611)
INI_FILE (250603)
INSTANCE_NAME (250601)
PASSWORD (250605)
PORT (250610)
PW_MON_VER (250626)
SQL (250607)
SRCIP (250615)
TARGETIP (250693)
USER_NAME (250604)
With this monitor type, the possible parameters are $INSTANCE_NAME,

$USER_NAME, $PASSWORD, $PORT, etc.
Note
If you use this option, you must ensure that this command is attached to the
right monitor type. In this example, the command should only be attached to
'MS SQL Server Query'. Refer 'attaching the command under a 'Monitor Type'
section for further information.
Example command:
/usr/bin/sh -c 'cd /home/kchong; find . -name "*.java" -print'
$pronethome/scripts/querydb.sh $USER_NAME $PASSWORD $PORT
Script
Show Output - This option is displayed only if Command is selected as the
Processing Option. Determines whether to display the output or not while

executing the command. If this option is not selected, BMC ProactiveNet launches
the script without waiting for its completion, but reports back right away whether
the script has been successfully launched or not. There is a default timeout period
of 300 secs for executing a user command.
Note
If the operation times out, the script that is still being executed on the agent is
terminated.
Configuration Diagnostic - Select this option to qualify this Detailed Diagnostic
command to be run with every configuration poll of select system monitors (AIX,
HPUX, Linux, Solaris, Windows, and X86).
Timeout - Specify the duration (between 5 and 55 minutes) the system must wait
before timing out this command.
Agent from which CMD is launched - This option is displayed only if Command
is selected as the Processing Option. When you are registering a command, you
must select the Agent where this command will be executed. In using a URL the
agent selection is not required. You need not select an agent if you are registering
a URL.
Use Agent on which the monitor is running - This enables running the command
on the agent to which the commands monitor belongs.
Prompt for Agent - In this case, the Agent is known when the command is being
executed. This option is ignored if the command was triggered by an event rule. It
defaults to as if the first option was selected.
Predefined Agent - Choose the Agent from the list of predefined agents.
Use Agent on which the monitor is targeted This enables running the command
on the agent to which the commands monitor is targeted.

1 Click Next.
Select the Device OS on the new window.
The left list contains all available OS.
The right list contains all selected OS.
Click >> to move a selected OS from the left list to the right.
Click << to move a selected OS from the right list to the left.
Select All to select all items in the left list.
391
Script
Select None to not attach any specific OS type.
2 Click Next after selecting the required OS.

The left list contains all available Monitor Types.
The right list contains all selected Monitor Types under which you want to
attach this command.
Click >> to move a selected monitor from the left list to the right.
Click << to move a selected monitor from the right list to the left.
Select None to not attach any specific monitory type.
Note
If you choose to use instance configuration parameters to define the
command, the parameters selected should be in the monitor type selected.
3 Click Next. Select the User Groups on the new screen.
The left list contains all available User Groups.
The right list contains all selected User Groups.
Click >> to move a selected User Group from the left list to the right.
Click << to move a selected User Group from the right list to the left.
Select None to not attach any specific User Group.
Note
The access permissions that are set while defining the User groups takes
precedence, that is, if the user group is defined with All Diagnostics in the
Diagnostics tab, then the newly created diagnostics will be available to those
user groups irrespective of whether they are selected/non-selected in the
Add to User Group screen in the Add Command module of the Diagnostics
wizard.
4 Click Finish.
This registers the commands with BMC ProactiveNet Server and opens a 'Test'
window, if the command type is 'Command'.
Script
5 Click Transfer. No need to define script if you use this option.

To transfer the script, see Transfering files to agents on page 206.
Once transferring is finished BMC ProactiveNet returns to Test Your Command
screen.
6 Test the Command in the Test Your Command window.
a From the Source Agent list, select the Agent on which you want to test the
command.
b Use Target IP to execute the command on the given target IP. If the required
Target IP is not available in the list, use 'Edit Target IP', which will bring
editable Target IP text fields as shown in the Administration console, from
the list. This is applicable only if $ip is one of the parameters.
c Click Test to invoke a test.
The output is displayed in the Output area and the status is displayed at the
bottom of the window. Data returned from the Detail Diagnostic history output
is ordered by the timestamp when the data is gathered.
Server Time - Time when the action is triggered.
Agent Time - Time when the agent actually executes the action. Agent Time could
be different from the Server Time for the following reasons:
The Agent is a remote agent and its time is different from the server's.
The Agent is a local agent but the action didn't take place immediately after the
event has occurred. Depending on the state of the server, a busy server could
cause some delay.
1 Click Ok to close the window and bring up a list of all commands that have
been registered.
These diagnostic commands will now be available from the Operations
Console's Tools menu as well as from the Event Rule Creation/Edit page.
a Check Event Summary tables.
Verify that the command is available in the Tools menu from the Device Matrix,
Service Matrix, and All Events tables. If it is present, then the new command is
available for use.
Note
From the Service Matrix table you need to drill down to the Show Monitor level
to access the Tools menu.
You can now:
Execute this command manually from the Tools menu, and
393
Script
Attach it to an event rule so that it executes automatically when an event is
triggered (recommended).
Note
These commands will only be displayed in the Tools menu against the
monitor types where the diagnostic was registered.
1 Attach Script Command to an Event Rule.
Once you register the Script Command, it is recommended that you attach it to an
event rule so that it executes automatically when an event is triggered. Check the
thresholds to ensure that the attributes you want are enabled.
1 Options => Edit Thresholds
2 Modify the default settings, if necessary.
3 Select Enabled for the attributes required.
4 Click Apply.
a Create the Event Rule.
Once you have selected and edited the thresholds as required, you can create the
rule and attach it to an event.
1 Click Options => Event Rule Admin. A list of default scripts appears on the
Event Rule Administration screen. These are the Preconfigured Commands that
come with BMC ProactiveNet.
2 Click Add. The Create Event Rule screen is displayed.
Follow the instructions to create and attach the event rule to the new command
you just registered.
Diagnostics that are auto-triggered have their output saved in the database and
this info is easily accessible from the Diagnostics column in the Event Summary
table. The Diagnostics Double Arrow icon is displayed when an event has been
triggered. When it is displayed, click the Double Arrow icon to show the
diagnostic output. If this column displays None, then there are no diagnostics for
that event.
Editing script commands

Perform the following procedure to edit script commands.\
Script
To edit script commands

1 In the Administration Console, select Tools => Diagnostics Wizard => Script.
This launches the Diagnosis Command screen with a list of all available commands.
2 Highlight the command you want to edit and click Edit.
3 Make necessary changes.
4 Test your changes.
5 Click Ok.
Deleting script commands

Peform the following procedure to delete script commands.
To delete script commands

1 In the Administration Console, select Tools => Diagnostics Wizard => Script.
The Diagnosis Command screen displays with a list of available commands.
2 Highlight the command you want to delete and click Delete.
3 Click Ok.
Creating a detailed diagnostic script for Windows

Perform the following procedure to create a detailed diagnotic script to be run on
Windows computers.
To run a Detailed Diagnostic script on Windows host

1 Add the path of the executable/batch file in the Command field.
The batch/executable file is basically a pointer to the main script. Example, to
run a script (filename basic.java),
2 Write a batch file/executable with the following info:

set classpath=d:\nataraj\java
java -classpath d:\nataraj\java basic
The final script to execute is basic.java, which is available under d:\nataraj
\java.
395
Log file
3 Save the batch file/executable (Example, first.bat) at a particular destination

(ensure that the final script is accessible from this location).
4 To run the script (basic.java), enter the following in the Command field:
fileLocationPhysicalPath\first.bat
When you run the test, BMC ProactiveNet executes first.bat, which in turn
executes basic.java file.
Log file
This template-based diagnostic tool enables you to create user-defined log file search
commands without having to write scripts. The total number of lines displayed in
the output for all matches of all files in a given instance is limited to 100,000
characters. Irrespective of the number of files scanned or the number of matches
found, the implementation always restricts the output to this global value. Analysis
of log file monitors shows that more than 100,000 characters being pushed into the
database at same time affects database performance.
Note
While 'Log File Search DD' can match for patterns in any file, it displays correct
output only for files containing all printable characters. This is because of XML
parser limitations. If the searched file contains non-printable characters, the
output may not be displayed correctly.
Do not begin a Detailed Diagnostic command name with a number or special
not get executed.
Registering a user-defined log file command

Follow the procedure given below to register a log file command.
To register a user-defined log file command

1 In the Administration Console, select Tools => Diagnostics Wizard => Log File
This launches the Create Log File Search Diagnostics window. Available
commands, if any, will be listed on this window.

Button Options
Add: Click this to add a new command.
Log file
Edit: Click this to modify a previously registered command.

Delete: Click this to remove the command from the system.
Cancel: Click this to exit the Diagnostics Wizard.
2 Click Add. The Add Command window appears.

a In the Name field, enter a unique name for the search and click Add.
The Add Log File Search window is displayed.
b Log File - select the file to be searched.
Alternatively,
For input = '*', the system reads the most recent file.
For input = '<prefix> + *', the system retrieves all files with names containing
<prefix>
For input = '* + <suffix>', the system retrieves all files with names containing
<suffix>
c Match on Regular Expression - This pattern is used to sort and retrieve lines
from the specified file.
However,
For input = '*', the system retrieves all lines from the file. In this case, advanced
filters will not be available.
For input = '<valid pattern>', the system sequentially parses the file content
and retrieves matches. Additional filters available in the Advanced section can
be applied for more specific search.
d Negative Pattern Match - This acts as an additional sort filter for displaying
output.
e Match Case Sensitivity - Select this to enable case-sensitivity for the search.
Select this to make the search case-sensitive.
Advanced - The filters below work in tandem to further refine the search.
f Show +/- - The number of lines before and after the match to be considered for
output. This value is restricted to a maximum of 1500.
397
Log file
g Limit search to the last X lines of the file - This limits the search to the
specified number of lines in the file. This value is restricted to a maximum of
50,000.
h Limit output to X matches - This limits the search output to the specified
maximum. This value is restricted to a maximum of 50,000.
Note
For optimum system performance and output accuracy, enter values

judiciously in the Advanced section. Very large values may result in the action
getting timed out (Timeout is set to 5 mins), and the displayed result may not
be complete (the system truncates output to 100,000 characters).
i Click Apply. This displays the Add Command window again.
3 Select Configuration Diagnostic option to qualify this Detailed Diagnostic
command to be run with every configuration poll of select system monitors (AIX,
HPUX, Linux, Solaris, Windows, and X86).
4 In the Timeout field, specify the duration (between 5 and 55 minutes) the system
must wait before timing out this command.
5 Choose the agents on which the log files will be searched.
a Select Use Agent on which monitor is running option.
b Alternatively, select a predefined Agent from the list.
6 Click Next.
7 On the window that is displayed, select device types. Use this window to attach
the command under a 'Device Type'.
Move the device types from the left panel to the right.
The left list contains all available Device Types.
The right list contains all selected Device Types under which you want to
Click << to move a selected monitor from the right list to left list.
Log file
8 Click Next.
9 Select Monitor Types.
Move the monitor types from the left to the right panel.
The left list contains all available Monitor Types.
The right list contains all selected Monitor Types under which you want to
Click << to move a selected monitor from the right list to the left.
10 Click Next.
Select the User Group as specified in the previous screens.
Note
The access permissions that are set while defining the User groups takes
precedence, that is, if the user group is defined with All Diagnostics in the
Diagnostics tab, then the newly created diagnostics will be available to those
user groups irrespective of whether they are selected/non-selected in the Add
to User Group screen in the Add Command module of the Diagnostics wizard.
11 Click Finish.
This registers the commands with BMC ProactiveNet Server and opens a 'Test
window if the command type is 'Command'.
12 Test the Command on the Test Your Command window.

From the Source Agent list, select the 'Agent' on which you want to test the
command.
Use Target IP to execute the command on given target IP. If the required Target
IP is not available in the drop down list, select Edit Target IP from the list
which displays editable Target IP text fields as shown in the Administration
Console. This is applicable only if $ip is one of the parameters.
Click Test to invoke a test.
399
Log file
The output is displayed in the Output section of the window and the status is
displayed at the bottom. Click Ok to close the window and display a list of
commands that have been registered. These diagnostic commands will now be
available from the Operations Console tools menu, but ONLY to users who
have access control privileges to execute commands.
13 Check Event Summary tables.

Verify that the command is available on the Tools menu from the Device
Matrix, Service Matrix, and All Events tables. If it is present, then the new
command is available for use.
Note
From the Service Matrix table you need to drill down to the Show Monitor level
to access the Tools menu.
You can now:
Execute this command manually from the Tools menu, and
Attach it to an event rule so that it executes automatically when an event is
triggered (recommended).
Note
These commands are displayed in the Tools menu against the monitor types
where the diagnostic was registered.
14 Attach the script command to an event rule.
Once you have registered the Script Command, it is recommended that you
attach it to an event rule so that it executes automatically when an event is

triggered. Check the thresholds to ensure that the attributes you want are enabled.
a Click Options => Edit Thresholds.

b Modify the default settings, if necessary.
c Select Enabled for the attributes required.
d Click Apply.
15 Create the event rule.
After you have checked and edited the thresholds as required, you can create
the rule and attach it to an event.
a Click Options => Event Rule Admin.
Log file
A list of default scripts appears on the Event Rule Administration screen.
These are the Preconfigured Commands that come with BMC ProactiveNet.
b Click Add.
The Create Event Rule screen appears. Follow the instructions on how to
create and attach the event rule to the new command you just registered,
which is described in the Adding Event Rules section.
Editing a log file command

Perform the following procedure to edit a log file command.
To edit a log file command

1 In the Administration Console, select Tools => Diagnostics Wizard => Log File.
The Command window displays with a list of available commands.
2 Highlight the command you want to edit and click Edit.

3 Make necessary changes.
4 Test your changes.
5 Click Ok.
Deleting a log file command

Perform the following procedure to delete a log file command.
To delete a log file command

1 In the Administration Console, select Tools => Diagnostics Wizard => Log File.
The Command window displays with a list of available commands.
2 Highlight the command you want to delete and click Delete.

3 Click Ok.
401
Preconfigured commands are displayed in the Operations Console under the Tools
menu.
This section presents built-in diagnostic commands that are available for Detailed
Diagnostics (DD).
Top processes for BMC PATROL

The Detailed Diagnostics command enables you to gather Top Processes information
from the BMC PATROL agent.
This can be triggered from the Tools menu of associated monitor instance in the
Operations Console.
Select the appropriate options:
To view Top Processes Windows PATROL, select Tools => Diagnostics => Top
Processes Windows PATROL
To view Top Processes UNIX PATROL, Tools => Diagnostics => Top Processes
UNIX PATROL
Detailed Diagnostics support is available for the following monitor types:

Windows
NT_PROCESS
NT_CPU
UNIX
PROCPRES
CPU
The Top Processes for BMC PATROL DD lists the attributes for the PROCTopProcs
parameter from the configured PATROL agent.
Note
For proper execution of the BMC Patrol Top Process DD, targeting BMC Patrol agent
version 3.6, download the hotfix 3.9.20.02 that comes under controlled availability
from BMC Software site. Unzip it and copy the PatProcQuery.exe to
<BMC_Installation_Dir>\Patrol3\bin directory. Once this is done, restart the BMC
Patrol agent as well as BMC Console.
Top processes for Solaris

This command enables you to view the Top 10 Processes that are (using the
maximum percentage of CPU) making use of the maximum CPU percentage, along
with other system resources, at any given point of time. Whenever the values for
Sort Key (CPU Percentage) are same for more than one process, the processes are
sorted on 'CPU Time'.
To view top 10 processes by memory, select Tools => Diagnostics => Top ProcessesMem
To view top 10 processes by CPU, select Tools => Diagnostics => Top Processes-CPU
Summary
Agent Name - Name of the agent
Date/Time - Date and time
Group: load average

Load average (1 min) - Average number of jobs in the run queue over the last one
minute.
Load average (5 min) - Average number of jobs in the run queue over the last five
minutes.
Load average (15 min) - Average number of jobs in the run queue over the last
fifteen minutes.
Group: number of processes

Total Number of processes - Total number of processes currently running.
Number of processes in sleep state (Sleep) - Number of processes waiting for an
event to complete.
403
Number of processes in run able state (Run) - Number of processes in the run
queue.
Number of processes in zombie state (Zombie) - Number of processes
terminated and parents not waiting.
Number of processes running (CPU) - Number of processes currently running on
the processor.
Number of processes Stopped (CPU) - Number of processes currently stopped on
the processor.
Group: CPU time usage (for all the processes)

Idle - Percentage of time the CPU is idle. Duration the CPU is idle, expressed as a
percentage of the total CPU time.
User - Percentage of time usage of CPU time servicing user. Time spent by the
CPU in servicing the user, expressed as a percentage of the total CPU time.
Kernel - Percentage usage of CPU time spent executing kernel jobs. Time spent by
the CPU in executing kernel jobs, expressed as a percentage of the total CPU time.
IO wait - Percentage of CPU time spent waiting for input. Time spent by the CPU
in waiting for input, expressed as a percentage of the total CPU time.
Swap - Percentage usage of CPU time spent for swap. Time spent by the CPU on
swap, expressed as a percentage of the total CPU time.
Group: memory
Real - Amount of real memory available.
Free - Amount of free memory available.
Swap in use - Amount of swap memory being used.
Swap free - Amount of swap memory free.
Group: process
PID - The unique process identifier associated with the given process.
USERNAME - Logon name of the user running the particular process.
THR - Number of threads associated with the process.
PRI - Priority assigned to the process by the CPU.

NICE - Altered priority of the process after it has been invoked (nice / renice).
SIZE - Size of the process image in MB.
RES - Resident size of the process in MB.
STATE - State of the process in the CPU. Valid values are Sleep, Runnable, CPU,
Zombie, and Stopped.
TIME - Hr:min:sec User + sys CPU time for this process.

CPU - Percentage of CPU time used by all LWP's of this process.
COMMAND - Name of the EXECed file associated with this process.
Top processes for Linux

These commands can be triggered for any Linux Process or System monitor
instances, in response to the event raised on the monitor instance, provided the event
rule is defined to trigger these command. Whenever the values for Sort Key (CPU
percentage/Memory percentage) are same for more than one process, then those
processes are sorted on PID numbers.
There are two commands under this category.
Top Processes-CPU: This command enables you to view the Top 10 Processes that
are making maximum percentage use of the CPU, along with other system
resources, at any given point of time.
In the Operations Console, select Tools => Diagnostics => Processes-CPU.
Pronet.conf contains the following entries:
pronet.apps.detailDiagnostics.LinuxTop10.authenticationMode=0
By default this property is set to 0, which indicates local authentication. Set this
attribute to 1, which indicates centralized LDAP authentication.
pronet.apps.detailDiagnostics.LinuxTop10.displayUserName=true
By default, this attribute is set to true and the Top 10 DD display user name. If this
property is set to false, the Top 10 DD display user ID.
Top Processes-Mem: This command enables you to view the Top 10 Processes
that are making use of the maximum Memory percentage, along with other
system resources, at any given point of time.
405
In the Operations Console, select Tools => Diagnostics => Processes-Mem.
Summary
Agent Name - Name of the agent
Date/Time - Date and time
Group: Load average

Load Average (1 min) - Average number of processes ready to run during the last
1 minute.
Load Average (5 min) - Average number of processes ready to run during the last
5 minutes.
Load Average (15 min) - Average number of processes ready to run during the
last 15 minutes.
Group: number of processes

Total Number of processes (Total) - Total number of processes currently running.
Total Number of processes in Sleeping State (sleeping) - Total number of
processes in the Sleeping state.
Total number of process in Running State (running) - Total number of processes
in the run queue.
Total number of process in Zombie State (zombie) - Total number of processes
currently in the Zombie state.
Total number of process in Stopped State (stopped) - Total number of processes
in the Stopped state.
Group: CPU time usage (for all the processes)

User - Displays the percentage of CPU time in user mode.
System - Displays the percentage of CPU time in system mode.
Nice - Displays the percentage of CPU time in niced tasks.
Idle - Displays the percentage of CPU time in idle state.
Count - Number of CPUs
Irq - Percentage of CPU time spent handling interrupts. This attribute is available
only for Linux Advanced Server (ver 3 using RedHat 2.4.21).
Softirq - Percentage of CPU time spent handling soft interrupts. This attribute is
available only for Linux Advanced Server (ver 3 using RedHat 2.4.21).
IOWait - Percentage of CPU time spent waiting for Input/Output. This attribute
is available only for Linux Advanced Server (ver 3 using RedHat 2.4.21).
Group: memory
Available Memory - Total memory available.
Used Memory - Total memory used.
Free Memory - Total free memory.
Shared Memory - Total shared memory.
Memory used for buffers - Total memory used for buffer.
Memory used for Cached - Total memory used for cached.
Available Swap Space - Total swap space available.
Used Swap Space - Total swap space used.
Free Swap Space - Total free swap space.
Active Memory - Recently used memory. It is usually not reclaimed unless
absolutely necessary. This attribute is available only for Linux Advanced Server
(ver 3 using RedHat 2.4.21).
Memory In_dirty - Memory that requires writing to a disk or swapping. The
system requires more time to free such memory. This attribute is available only
for Linux Advanced Server (ver 3 using RedHat 2.4.21).
Memory In_clean - Memory freely available to the monitored system. The kernel
usually maintains a minimum amount of such memory. This attribute is available

only for Linux Advanced Server (ver 3 using RedHat 2.4.21).
Group: process
PID - The unique identifier of the given process.
User Name - Logon name of the user running the process.
Priority - Priority of the task.
407
Nice - Nice value of the task.

Size - Size of the task's code plus data plus stack space, expressed in kilobytes.
RSSize - Total amount of physical memory used by the task.
Share - Amount of shared memory used by the task.
State - State of the process in the CPU. (Valid states are S - sleeping, R - running, Z
- zombies, T - stopped or traced, W - swapped out process)
Lib - Size of use library pages.

CPU - Task's share of the CPU time, expressed as a percentage of total CPU time
per processor.
Memory - Task's share of physical memory.

Time - Total CPU time used by the task since it started.
Command - The task's command name.
Top processes for Windows

This command enables you to view the Top 10 Processes using the maximum
percentage of CPU, along with other system resources, at any given point of time.
On Windows, you must have Administrative rights to access Windows registry for
remote monitoring, otherwise the 'No data to display' message is displayed in the
diagnostic output.
Top 10 Processes for Windows (Output Attributes sorted on CPU percentage)
To view top 10 processes by memory, select Tools => Diagnostics => Top ProcessesMem
To view top 10 processes by CPU, select Tools => Diagnostics => Top Processes-CPU
Summary
Agent Name - String name of the agent
Process attributes
Process Name - Name of the process.
PID - Process ID. Each process is identified with a unique identifier. This is
required because two processes can have the same name, for example: - two Java
applications can run at the same time.
CPU - Specifies the amount of CPU consumption of the process.

Memory - Memory allocated to this process that cannot be shared with other
processes.
Handles - Windows operates mainly on registry. It is the database for the
applications stored in the system. Information about the process can be written
and retrieved from the registry using keys. A process maintains the list of opened
keys. This information is referred as Handle Count. This attribute specifies the
Handle count of the process.
Threads - Operating System can have any number of applications running on it
simultaneously. Similarly, a process can have many programs running

simultaneously. This is achieved using Threads. A process maintains the number
of threads that are running, and this number is the Thread Count. This attribute
specifies the Thread Count of the process.
Top EJBs for WebSphere

This command enables you to view the Top 10 EJBs on the Application Server. The
Top 10 EJBs are sorted based on their Average Method Response Time; hence, the
top 10 EJBs with the highest Average Method Response Time on the entire
Application Server will be displayed as the output of this feature. Under the Tools
menu in the Operations Console, it is displayed as Top EJBs.
The 'Average Method Response Time' attribute has High impact on a WebSphere 5.0
and Low impact on a WebSphere 4.0.x Application Server, hence for this DD
(Detailed Diagnostic) to function properly, the impact levels for the 'beanModule'
should be set to High on WebSphere 4.0.x Application Server and set to Low or
above on WebSphere 5.0 Application Server.
Top 10 EJBs (Output attributes sorted based on Average Method Response Time)
Summary
Target IP - IP address of the computer where the Application Server is running.
Node Name - Name of the node.
Application Server Name - Name of the application server.
409
Average Method Response Time - Average method response time of all the EJBs
deployed on the application server.
Total Method Calls - Total method calls to all EJBs deployed on the application
server.
Active Methods - Number of active methods of EJBs on the application server.

Pool Size - Pool Size of EJBs deployed on the application server.
Attributes per Enterprise Bean

EJB Name - Name of the enterprise bean.
Application Name - Name of the application to which this EJB belongs [on
WebSphere 5.0 only].
EJB type [on WebSphere 5.0 only] - Type of Enterprise bean [on WebSphere 5.0
only].
Average Method Response Time - Average method response time of the EJB.
[This attribute has High impact in WAS 5.0 and Medium impact in WAS 4.0]
Total Method Calls - Total number of method calls to the EJB. [This attribute has
High impact in WAS 5.0 and Low impact in WAS 4.0]
Number of Activates - Number of activates of the EJB.

Number of Passivates - Number of passivates of the EJB.
Active Methods - Number of active methods of the EJB.
Number of Gets found - Number of gets found for the EJB.
Pool Size - Pool Size of the EJB.
Top Servlets for WebSphere

This feature enables users to view a snapshot of the Top 10 Servlets on the
application server. The top 10 servlets are sorted based on their average response
time; hence, the top 10 servlets / JSPs with the highest average method response
time on the entire application server will be displayed as the output of this feature.
This command will be available in the Tools menu for every WebSphere 4.0.x and 5.0
Monitor instance in the Operations Console, even with WebSphere 4.0.x and 5.0
Monitor instances for which data collection for 'Web Application Statistics' is not
checked, provided the performance monitoring for the 'webAppModule' has been
enabled on the application server. This command can also be associated with Event
Rules.
The 'Average Response Time' attribute has Medium impact on WebSphere 5.0 and
WebSphere 4.0.x application server; hence, for this command to function properly,
the impact levels for the 'webAppModule' should be set to Medium or above on
WebSphere 4.0.x or 5.0 application server.
Top 10 Servlets (Output attributes sorted based on average response time)
Summary
Target IP - IP address of the computer on which the application server is running.
Node Name - Name of the node.
Application Server Name - Name of the application server.
Average Response Time - Average response time of all the servlets and JSPs
deployed on the application server.
Total Requests - Total requests to all the servlets and JSPs deployed on the
application server.
Number of Errors - Total errors while loading servlets or JSPs on the application
server.
Number of Loaded Servlets - Total loaded servlets and JSPs on the application
server.
Number of Reloads - Total reloads of servlets and JSPs on the application server.
Attributes per Servlet and JSP

Servlet Name - Name of the servlet or JSP.
Application Name - Name of the application to which the servlet/JSP belongs.
Total Requests - Total requests to the servlet/JSP.
Average Response Time - Average response time of the servlet/JSP.
Number of Errors - Number of errors while loading/reloading the servlet/JSP.
Concurrent Requests - Number of concurrent requests to the servlet/JSP.
411
WebLogic active info

This command enables users to view active queues, open socket count, and socket
reader threads information for a WebLogic application server instance. It is
displayed in the Operations Console under Tools menu as 'WebLogic Active Info' for
any WebLogic 6.1/7.0/8.1 instance. You can also specify an event rule to automate
the execution of 'Active Info'.
Top 10 Processes for WebLogic (Output Attributes for "Active Info")
Summary
Machine IP Address - IP address of the computer running Weblogic server.
Instance Name - Name of the instance.
Date/Time - Time stamp of the DD execution.
Attributes per Queue

Queue Name - Name of the queue.
Threads - Total threads in a queue
Idle Threads - Number of idle threads in a queue.
Queue Length - Number of requests pending in a queue, due to lack of threads.
Throughput - Total requests handled by all threads in the queue.
Top SQL statements for Oracle

Top SQL Statements detail diagnostic functionality displays top ten SQL statements
that are consuming resources like IO (diskreads), cache (buffer_gets), parse calls,
memory, CPU time, rows processed, and number of fetches. It also lists the
frequency of execution of the statement.
There are two preconfigured commands available under this category:
Top SQL-CPU: To sort Top 10 SQL statements based on CPU utilization. Since
CPU data is available from Oracle-9 onwards, this utility supports only monitors
created for Oracle-9 onwards.
Top SQL-DiskReads: To sort Top 10 SQL statements based on disk reads.
These commands are available under the Tools menu for any Oracle Query Monitor
and Oracle Intelliscope monitor instance in the Operations Console.
For executing Top SQL Statements for Oracle, Read permissions (for the user
account associated with the corresponding monitor) on the following tables is
required: V$SYSSTAT , dba_data_files , v$filestat, v$datafile, dba_free_space, V
$OPEN_CURSOR, v$sysstat, v$sgastat, v$sga, v$sesstat, v$statname, v$transaction,
sessions_current, v$lock, v$bgprocess, V$LIBRARYCACHE, V$RowCache, V
$ROWCACHE, and v$license.
In case access is not available to these tables, DD cannot be executed.
Summary
Target IP - IP address of the computer on which the Oracle Server is running.
Port - Oracle database port. Default is 1521.
SID - Global database name/ID of the Oracle database.
User ID - User ID to connect to the Oracle database
Password - Password corresponding to the user name specified.
Server Time - Current time on the computer where BMC ProactiveNet Server is
up and running.
Agent Time - Current time on the computer where BMC ProactiveNet Agent is
installed.
Database attributes
Protocol - Oracle database protocol.
Oracle Version - Version of Oracle Server running.
SQL query attributes

SQL Statement - The SQL statement string. (Length of the SQL Statement to be
displayed needs to be determined.)
Disk Reads - Number of disk reads.

Buffer Gets - Number of buffer gets.
Parse Calls - Number of parse calls.
413
Executions - Number of times the statement is executed.

Memory - Memory consumed by the SQL statement (sum of sharable memory
and persistent memory).
CPU Time - CPU time utilized for execution of the SQL statement. This data is
available only from Oracle-9 onwards.
Rows Processed - Number of rows that got processed during execution of the
statement.
Fetches - Number of fetches associated with execution of the statement. This data
is available from Oracle-9.2 onwards.
If the user name for the listed query has been deleted, the Top SQL Statements for
Oracle returns 'NULL' for 'User Name'.
Query display in the first column is limited to a maximum of 1000 characters.
Note
Execution of the Top SQL Statements for Oracle DD would fail if this DD would be
triggered from pre 7.1 agent in BMC ProactiveNet Server 7.1.
Top SQL statements for MS SQL

MS SQL Server Top 10 SQL Statement Detailed Diagnostic command displays the
top 10 SQL statements consuming resources such as IO (disk read), CPU, Execution
count, etc.
This command can be triggered in response to an event raised on the monitor
instance, provided the event rule is defined to trigger this command. The event rule
can be set to Response Time attribute of MS SQL Query Monitor and Cache Hit Ratio
attribute of MS SQL Intelliscope monitor.
The command also provides information about queries currently running on the
database.
There are two preconfigured commands available under this category:
Top SQL-CPU: To sort Top 10 SQL statements based on CPU utilization
Top SQL-DiskReads: To sort Top 10 SQL statements based on disk reads
These commands are available under the Tools menu for MS SQL Server Query
Monitor and MS SQL Server Intelliscope monitors in the Operations Console.
For successful execution of the Detailed Diagnostic command:

The MS SQL Server database must be running
The database system and port must be accessible from the system where BMC
ProactiveNet Agent is running
The user name required to connect to the database must be part of the sysadmin
fixed server role. Else, the logon name must at least have VIEW SERVER STATE
permission on the server.
Summary
Target IP - IP address of the system where the MS SQL Server is running.
Port - The MS SQL server database port. Default is 1433.
User ID - User name or identifier required to connect to the MS SQL Server database.
Version - Version of the MS SQL Server database.
Top 10 SQL Statements Attributes

displayed needs to be determined).
Avg. CPU Time - Average CPU time utilized for execution of the SQL Query.
CPU Time - CPU time that was used the last time the SQL Query was executed.
Execution Count - Number of times the statement is executed
Avg. Physical Reads - Average number of physical Reads performed by execution
of this Query since it was compiled.
Physical Reads - Number of physical reads performed the last time the Query
was executed.
Avg. Logical Reads - Average number of Logical Reads performed by execution
Logical Reads - Number of Logical Reads performed the last time the Query was
executed.
Avg. Logical Writes - Average number of Logical Writes performed by execution
415
Logical Writes - Number of Logical Writes performed the last time the Query was
executed.
Avg. Elapsed Time - Total elapsed time for completed execution of the Query.
Elapsed Time - Elapsed time for the most recently completed execution of the Query.
Top 10 currently executing SQL statements attributes

The Top 10 currently Executing SQL Statements lists queries (and their statistical
data) currently being executed in the database.
displayed needs to be determined).
Status - Status of the request. It could be one of the following: Background,
Running, Runnable, Sleeping, or Suspended.
User - Name of the user who submitted the Query.

Database Name - Name of the database.
CPU Time - CPU time being utilized for execution of the SQL Query.
Memory Pages - Number of pages allocated to the execution of the query.
Reads - Number of physical reads performed by the request.
Writes - Number of physical writes performed by the request
Logical Reads - Number of Logical Reads performed by the Query.
Row Count - Number of rows returned by the Query.
Top IP traffic
This command enables users to view the Top Ten IP addresses making traffic to and
from the computer on which BMC ProactiveNet Agent is running. It gathers data by
analyzing the packets through the network interface on the agent computer and
sorts the output in descending order of the total number of packets to and from a
given IP address.
This command is available under the Tools menu for Solaris TCP Monitor and
Windows TCP Monitor in the Operations Console.
Note
Top 10 Detailed Diagnostics get associated with Windows TCP in case of remote
monitoring and executes on the Agent's IP address.
This command is supported on all Windows 2000/2003/XP/Vista (32 and 64-bit)
flavors except Windows Server 2008 (32 or 64-bit).
Top 10 IP DD interface list matches with Ethereal Interface list output ("ipconfig /
all" and "perfmon"). Network interfaces don't list WAN Adapter and Dial-up
Adapter interfaces.
BMC ProactiveNet Agent installation checks for the winpcap library installation
on any Windows OS platform. If there are any winpcap libraries present, a

warning to copy the latest libraries is displayed.
While un-installing the BMC ProactiveNet Agent, extra pcap libraries which were
copied during the installation are not removed.
Summary
Number Of Interfaces Found - Total number of available interfaces on the
monitored computer.
Listened On - Name and description (if available) of the interface listened on.
Total Number Of Packets To and From - Total number of packets sent to and
received from the given IP.
Interface - Interface on the monitored computer.

IP - IP address
Packets From - Number of packets that originated from the corresponding IP and
destined for the monitored IP.
Packets To - Number of packets that originated from the monitored IP and
destined for the corresponding IP.
Bytes From - Number of octets that originated from the corresponding IP and
destined for the monitored IP.
Bytes To - Number of packets that originated from the monitored IP and destined
for the corresponding IP.
Total Packets - Sum of Packets From and Packets To.

Total Bytes - Sum of 'Bytes To' and 'Bytes From'.
417
Oracle top wait events

The Oracle Top Wait Events Detailed diagnostic command enables you to view the
following:
Top N System wait events that occurred recently on the Oracle database - System
wait events indicate where the database or session is spending most of its time.
Top N Session wait events for which the sessions are currently waiting
The output of the command is sorted by the wait duration of the events at that point
of time.
This command can be associated with Oracle Session Wait Monitors, Oracle System
Wait Monitors, Oracle Intelliscope Monitors, and Oracle Query Monitors.
For executing Oracle Top Wait Events detailed diagnostic command, users must
have Access privileges on the following views: v$system_event, v$session, v
$session_wait, and v$sqlarea.
Summary
Target IP/Source Name - The target IP or host name of the system where the
Oracle database is running.
Port Number - The port number on which the database is responding.

Protocol - The protocol used to communicate with the database server.
User Name - The user name to access the database. The user name specified must
have 'Select' privileges on data dictionary views. The user must have the specific
privilege 'SELECT_CATALOG_ROLE' to access required tables/views.
Password - The password associated with the user name to access the database.
SID - The system identifier associated with the database.
Output attributes
Date/Time - The date and time when the command was run.
Target IP - IP address of the system where the Oracle database instance is running.
Port - The port number on which the database is responding.
SID - The system identifier associated with the Oracle database.

User ID - The user name to access the Oracle database.
Oracle Version - Version of the installed database server.
Group: events waited (system wait events)

Event Name - Name of the System Wait Event.
Time Waited - The total duration (in seconds) waited for the event to occur.
Total Waits - Total number of waits associated with the event.
Total Timeouts - Total number of timeouts that occurred for the event.
Group: currently waiting events (session wait events)

Session ID - The session identifier value.
Event Name - Name of the session wait event.
Waiting Time - The duration (in seconds) for which the session has been waiting
for an event.
Type - The type of session; User or Background

Wait Class - Name of the Wait class under which the session is currently waiting.
This field is available only in Oracle version 10g.
User Name - Oracle user name of the session. This may be available only if the
event is waiting on some particular user sessions and not on all user sessions. For
a background type session, user name is not available.
SQL Text - The SQL Statement currently being executed. This may be available
only if the event is waiting on some particular user and background sessions.
To reflect true wait times, set the TIMED_STATISTICS initialization parameter to
'True'.
419
pronet.conf entries
To set the default time interval (in secs) between two consecutive executions of this
detailed diagnostic command:
pronet.apps.detailDiagnostics.OracleTopNSysWait.rateInterval=30
To set the default number of events to be considered to generate output for this
command:
pronet.apps.detailDiagnostics.OracleTopNSysWait.topEvents=500
Note
The TIME_WAITED and AVERAGE_WAIT columns will contain a value of zero
on those platforms that do not support a fast timing mechanism. If you are
running on one of these platforms and you want this column to reflect true wait
times, you must set TIMED_STATISTICS to TRUE in the parameter file. If this is
done, the system performance may be affected adversely. For setting the
parameter, execute the SQL command ALTER SYSTEM SET
TIME_STATISTICS=TRUE.
Execution of the Oracle Top Wait Events DD would fail if this DD would be
Oracle top table-spaces

The Oracle Top Table-Spaces detailed diagnostic command enables you to view top
N table-spaces using the maximum disk space. This command can be associated
with Oracle Query, Oracle Intelliscope, and Oracle Table-Spaces monitors. Oracle
Top Table-Spaces command can be triggered in response to an event raised on the
'Database Free Space' attribute of an Oracle Intelliscope monitor instance.
For executing Oracle Top Table-Spaces detailed diagnostic command, users must
have Access privileges on the following tables: DBA_TABLESPACES,
DBA_DATA_FILES, and DBA_FREE_SPACE.
Summary
Target IP/Host Name - The IP address or host name of the system where the
Oracle database instance is running.
Port Number - The port number on which the database is responding.

User Name - The user name to access the database. The user should have
CREATE SESSION and SELECT ANY DICTIONARY system privileges or

the user should have CREATE SESSION system privilege and
SELECT_CATALOG_ROLE role.
Password - The password associated with the user name to access the database.
SID - The system identifier associated with the database.
Output attributes
Target IP - IP address of the system where the Oracle database instance is running.
Port - The port number on which the database is responding.
SID - The system identifier associated with the Oracle database.
User ID - The user name to access the Oracle database.
Oracle Version - Version of the installed database server.
Group: TableSpace usage

Table Space Name - Name of the Table-Space.
Total Logical Space - Total amount of space (in MB) in the Table-Space.
Percent Logical Used Space - Percentage of space used in the database for data
growth.
Free Extent - Number of free extents available in the Table-Space.

FSFI - Percentage of Free Space Fragmentation Index (FSFI). FSFI denotes the size
of the largest extent as a percentage of the total free table space. This index is not a
monitor of the amount of free table space available.
Data File Count - Total number of data files associated with the table space.
Extent Management - Dictionary managed or Locally managed type of extent
management.
Allocation Type - System, Uniform, or User kind of extent allocation for the Table-
Space.
Segment Space Management - Space management type of the segments. Can be
manual or auto. This attribute is not available for Oracle 8i.
421
Total Physical Space - Total amount of space (in MB) in the Table-Space with
respect to auto-extensible size. This is supported from BMC ProactiveNet Server

and BMC ProactiveNet Agent 7.5 onwards.
Percent Physical Used Space - Percentage of space used in the database for data
growth with respect to auto-extensible size. This is supported from BMC

ProactiveNet Server and BMC ProactiveNet Agent 7.5 onwards.
Autoextensible - Denotes whether particular tablespace is auto-extensible ON/
OFF. This is supported from BMC ProactiveNet Server and BMC ProactiveNet
Agent 7.5 onwards.
Note
Execution of the Oracle Top Table-spaces DD would fail if this DD would be

WebLogic active info - JMX

The WebLogic Active Info - JMX Detail Diagnostic command enables you to view
Execute Queue-related information such as idle threads, throughput of queue, active
queues, and thread currently assigned to queue. The command also displays Socketrelated information such as Total number of open sockets and socket reader threads.
This command can be associated with WebLogic JMX Monitor.
WebLogic Active Info - JMX command can be run in response to JVM Memory Used
and Execute Queue Usage attributes of the monitor.

WebLogic server must be up and running.
The system on which the server is installed must be accessible from the system on
which BMC ProactiveNet Agent is running.
BMC ProactiveNet Agent can access WebLogic server on port 7001, by default. Or
the port must be the same as the one on which WebLogic server is listening on the
target system.
For data retrieval, WebLogic JMX Monitor uses weblogic.jar, which is available with
the WebLogic server installation.
For data retrieval, WebLogic Active Info - JMX DD uses weblogic.jar, which is
available with the WebLogic server installation.
Weblogic 8.1
For SSL connection:
1 Copy weblogic.jar from WL_HOMEserver/lib/ to agentInstallDirectory/pw/
apps3rdparty/jmxvamlib/weblogic/8.1 and restart agent before creating the
monitor instance.
2 Copy jsafeFIPS.jar from WL_HOMEserver/lib/ to agentInstallDirectory/pw/
apps3rdparty/jmxvamlib/weblogic/8.1.
3 Copy license.bea from WL_HOME to ' agentInstallDirectory/pw/apps3rdparty/
jmxvamlib/weblogic/8.1
where WL_HOME is the directory in which you have installed the WebLogic Server.
Note
When the target WebLogic version is 8.1 SP4, copy webserverclient+ssl.jar as
jsafeFIPS.jar is not available.
4 Restart agent before creating the monitor instance.
Weblogic 9.0/9.1
For SSL connection:
1 Copy weblogic.jar from WL_HOMEserver/lib/ to agentInstallDirectory/pw/
apps3rdparty/jmxvamlib/weblogic/9.0/.
2 Copy jsafeFIPS.jar from WL_HOMEserver/lib/ to agentInstallDirectory/pw/
apps3rdparty/jmxvamlib/weblogic/9.0/.
3 Copy license.bea from WL_HOME to agentInstallDirectory/pw/apps3rdparty/
jmxvamlib/weblogic/9.0/'.
WL_HOME is the directory in which you have installed the WebLogic Server.
Summary
Target Device - Host name or target IP of the system where WebLogic server is
running.
Application Server Name - The application server name; can be either
administrator server or managed server.
423
Port - The listening port on which the WebLogic Application Server is running.
Security Principal / User Name - The user name to access performance data
through JMX.
Security Credentials / Password - The password associated with the user name.
SSL Enabled - Select if SSL communication is required to monitor the target
WebLogic server through JMX.
Output attributes
Active queues information
Name - The Execute Queues name.
Threads - The execute threads currently assigned to the queue.
Idle Threads - The number of idle threads assigned to the queue.
Queue Length - The number of waiting requests in the queue.
Throughput - The number of requests, which have been processed by this queue.
Open Socket Count / Socket Reader Threads
Open Socket Count - Current number of sockets registered for socket mixing.
Socket Reader Threads - The percentage (1-99) of execute threads that may be
used as socket readers.
Work manager information

Name - The work managers name.
Completed Requests - The number of requests that have been processed.
Pending Requests - The number of waiting requests in the queue.
Stuck Thread Count - The number of threads that is considered stuck on the basis
of any stuck thread constraints.
Note
Work Manager attributes are only available when the target WebLogic server
version is 9.0 and above.
Solaris system configuration

Solaris System Configuration is the default configuration DD for the Solaris and X86
Solaris System monitors. This DD displays basic system configuration, status of
important sub-systems and other useful information. This DD can be executed
manually from the Operations Console (Diagnostics submenu of the Tools menu for
Solaris and X86 Solaris devices and Diagnostics sub-menu of the Tools menu for
Solaris System and X86 Solaris System monitor instances). This DD can also be
executed automatically at every configuration poll of the Solaris System and X86
Solaris System monitor instances, when configured as configuration DDs for those
monitor instances. Finally these DDs can also be executed as event actions for event
rules.
Summary
Hostname, Hostid and release of the running Operating System.
Kernel information ID, architecture and type.
System uptime information how long the system has been running and date
when system was last rebooted.
Run level current run level information.

Last five patches applied to the system this option is only available when the
Proactive Server has been installed as root. For non-root installations, this is
unavailable.
List of files in the /etc directory that have been changed in the last day.
Processor information:
Number of processors.
Number of processors online.
Number of bits in the processors address space.
Speed processor in operation.
Processors ISA and native instruction set for Solaris 10.
The number of physical processors.
Virtual processors are displayed separately.
Physical memory.
425
Swap space usage information and status of swap areas.

Information on disk files and blocks.
Network status.
Network interface parameters,
Status of physical and logical interfaces.
Routing table.
List of TCP sockets.
Note
When the agent on which the DD is running is installed with non-root user
privileges, certain error messages may get displayed at the top of the DD
output. They may be of the following type:
/bin/find: cannot read dir
/etc/inet/secret: Permission denied
/etc/sfw/private: Permission denied
/etc/sfw/openssl/private: Permission denied
/etc/apache/ssl.key: Permission denied
/etc/webmin: Permission denied
These are expected errors and they can be ignored.
Windows system configuration

Windows System Configuration is the default configuration DD for the Windows
System monitor. This DD displays basic system configuration, status of important subsystems and other useful information. This DD can be executed manually from the
Operations Console (Diagnostics submenu of the Tools menu for Windows devices
and Diagnostics submenu of the Tools menu for Windows System monitor
instances). This DD can also be executed automatically at every configuration poll of
the windows System monitor instances, when configured as configuration DDs for
those monitor instances. Finally these DDs can also be executed as event actions for
event rules.
Summary
System configurations.
Hardware Resource.
Conflicts/Sharing.
Forced Hardware.
Components.
Problem Devices.
IP Configuration.
Interface information.
Route information.
Active Routes.
Persistent Routes.
Active TCP Connections.
Limitations and workaround

Limitation: On Windows 2003 and Windows XP, the msinfo32.exe ignores
parameters supplied on the command line and dumps a lot of information which
exceeds the max data limit set for DDs (100000 characters).
Workaround: There is no workaround currently available.
JVM diagnostics
JVM DD is used to run a DD command on a JVM running on a local or remote
system. DD is executed as a result of a predefined event rule on JVM monitor and/or
from HTML UI. It gathers the health indicators from JVM using JMX technology.
427
JVM monitor is tested only against Suns JVM, thought it might work against other
vendors JVM seamlessly.
Summary
Target IP/Host Name - IP address of computer where the JVM is running
Port Number - The port on which the JMX connector is listening.
JNDI Name - Name specified in the JVM startup parameters.
Principal - Principal (User Name) required to connect to the JMX server.
Credentials - Credentials (Password) required to connect to the JMX Server.
Output attributes
GC Algorithm - Algorithm used by GC, which is controlled using JVM startup
arguments.
Current Thread CPU time (ms) - Number of milliseconds the current thread
consumed while the DD is being executed.
Threads created during DD execution (#) - Number of threads created while the
DD is being executed or the pronet.apps.detailDiagnostics.jvm.rateInterval

value, which ever is higher.
Threads destroyed during DD execution (#) Number of threads destroyed while
the DD is being executed or the pronet.apps.detailDiagnostics.jvm.rateInterval

value, which ever is higher.
Active Threads Dump - Sorted by delta of CPU Time for all the threads in JVM.
Delta is the CPU time consumed by each thread while the DD is being executed
or the pronet.apps.detailDiagnostics.jvm.rateInterval value, which ever is higher.
Platform/version support
BMC ProactiveNet Server version: 7.1 SP2 and later
BMC ProactiveNet Server platform: Solaris and Windows
BMC ProactiveNet Agent version: 7.1 SP2 and later
BMC ProactiveNet Agent platform: Solaris and Windows
JVM MoreInfo detailed diagnostics

JVM MoreInfo DD is used to run a DD command on a JVM running on a local or
remote system. It gathers the details of all the running threads from JVM using JMX
technology.
JVM monitor is tested only against Suns JVM, thought it might work against other
vendors JVM seamlessly.
Summary
Target IP/Host Name - IP address of computer where the JVM is running
Port Number - The port on which the JMX connector is listening.
JNDI Name - Name specified in the JVM startup parameters.
Principal - Principal (User Name) required to connect to the JMX server.
Credentials - Credentials (Password) required to connect to the JMX Server.
Output attributes
Number of Threads Total number of threads running on the targeted JVM, when
the DD is being executed.
Number of Deadlock Threads Total number of the deadlock threads running on
the targeted JVM, when the DD is being executed.
Total Threads Dump - Sorted by CPU Time for all the threads in JVM.
Deadlock Threads Dump Sorted by CPU Time for deadlock threads in JVM.
Examining Detailed Diagnostics for BMC TM ART monitors

Use Detailed Diagnostics for BMC TM ART monitors to observe the performance of
web transactions.
For information about adding the adapter for BMC TM ART, see Adding an adapter
for BMC TM ART on page 322.
For information about Detailed Diagnostics when the adapter for BMC TM ART is
integrated with BMC AppSight, see Application Diagnostics for BMC AppSight
integrations on page 445.
429
To view Detailed Diagnostics for BMC TM ART monitors

In the Operations Console, choose one of the following options for a selected BMC
TM ART monitor:
1 Event View
Tools => Diagnostics => Page Timers (see details in Table 44 on page 431)
Tools => Diagnostics => Run Now + TrueLog (see details in Table 45 on page
431)
2 Grid View
Tools => Remote Actions/Diagnostics => Page Timers (see details in Table 44
on page 431)
Tools => Remote Actions/Diagnostics => Run Now + TrueLog (see details in
Table 45 on page 431)
You can also add an event rule for Detailed Diagnostics in the Operations Console.
To add an event rule for Detailed Diagnostics for BMC TM ART monitors
1 Log in to the BMC ProactiveNet Operations Console with administrator
privileges.
2 Click Options at the top of the console window.
3 On the Administration tab, click Edit in the Event Rule row.
4 Click Add and follow the onscreen instructions to create the event rule.
Diagnostics that are triggered from an event rule save the output in the database.
The information is accessible from the Diagnostics column in the Event Summary
table. The Detailed Diagnostics icon
is displayed when an event has been
triggered. Click the icon to display the diagnostic output.
Page Timers diagnostics

Page timers provide response times for detailed page break-downs across the total
page download time.
Table 44 on page 431lists the monitored attributes for the Page Timers Detailed
Diagnostics option.
Table 44: Page Timers attributes for BMC TM ART transaction

Attribute
Description
Page timer name
the name of the page statistics for the transactions total page download
time
Page timers for synthetic transactions are generated dynamically. If no
statistics are displayed, then no page timers exist for the selected
transaction.
Real transactions include the following page statistics:
page server busy time
page HTML download time
Response time
the response time of the page statistic, or the percentage of the total
page download time
Refer to the information about page-breakdown analysis in BMC TM
ART Central User Guide for details.
Average response time
the average response time, calculated from the time the monitor was
activated
Run Now + TrueLog diagnostics

Run Now + TrueLog executes the Run Now command in BMC TM ART Central for
the selected monitor, and generates a TrueLog file for the transaction. Run Now +
TrueLog can only be run for synthetic transactions.
Table 45 on page 431 lists the details for the Run Now + TrueLog Detailed
Diagnostics option:
Table 45: Run Now + TrueLog attributes for BMC TM ART transaction
Attribute
Description
Time stamp
the date (YYYY-MM-DD) and time (HH:MM:SS.SSS) the Run Now

command was executed
The time stamp is displayed according to coordinated universal time
(UTC).
URL
the URL for the Execution Log in BMC TM ART Central, where you
can access the TrueLog for the selected transaction
Click the link to access BMC TM ART Central. If the BMC TM ART
Central session times out before you connect to the URL, you will need
to log in.
431
Note
The Run Now + TrueLog Detailed Diagnostics does not influence the statistics
collected in BMC TM ART Central.
Examining Detailed Diagnostics for HP OM monitors

Use Detailed Diagnostics for HP OM monitors to observe the performance of system
and network file systems for CODA and SCOPE Smart Plug-Ins (SPIs).
To view Detailed Diagnostics for HP OM monitors

1 In the Operations Console, Grid View, click the All Devices folder in the
navigation tree.
2 Select the PATROL Proxy server device name.
3 For an HP_AGENT_CONN_INFO monitor type, click Tools => Remote Actions/
Diagnostics and select the required Detailed Diagnostics:
Application diagnostics for the SCOPE SPI on page 432
Process diagnostics for the SCOPE SPI on page 433
Transaction diagnostics for the SCOPE SPI on page 433
Status diagnostics for the CODA SPI on page 434
Status diagnostics for the SCOPE SPI on page 435
Application diagnostics for the SCOPE SPI

The following table lists parameters that appear in the Applications Detailed
Diagnostics for the SCOPE SPI.
For parameter details, refer to HP OM documentation.
The results in the Application Detailed Diagnostics are sorted according to the CPU
Total Utilization value.
Parameter
HP OM parameter
Name
APP_NAME
CPU Total Utilization (%)
APP_CPU_TOTAL_UTIL
Parameter
HP OM parameter
Memory Utilization (KB)
APP_MEM_UTIL
Resident Memory (KB)
APP_MEM_RES
Virtual Memory (KB)
APP_MEM_VIRT
Alive Processes (#)
APP_ALIVE_PROC
Active Processes (#)
APP_ACTIVE_PROC
Process diagnostics for the SCOPE SPI

The following table lists parameters that appear in the Process Detailed Diagnostics
for the SCOPE SPI.
The results in the Process Detailed Diagnostics are sorted according to the CPU Total
Utilization value.
Parameter
HP OM parameter
Name
PROC_PROC_NAME
ID
PROC_PROC_ID
Parent ID
PROC_PARENT_PROC_ID
User Name
PROC_USER_NAME
CPU Total Utilization (%)
PROC_CPU_TOTAL_UTIL
Resident Memory (KB)
PROC_MEM_RES
Virtual Memory (KB)
PROC_MEM_VIRT
Thread Count (#)
PROC_THREAD_COUNT
Transaction diagnostics for the SCOPE SPI

The following table lists parameters that appear in the Transactions Detailed
Diagnostics for the SCOPE SPI.
The results in the Transactions Detailed Diagnostics are sorted according to the Time
value.
433
Parameter
HP OM parameter
Name
TT_NAME
ID
TT_TRAN_ID
Application Name
TT_APP_NAME
Application Transaction Name
TT_APP_TRAN_NAME
Time (s)
TT_WALL_TIME_PER_TRAN
User Name
TT_UNAME
User Measurement Max (#)
TT_USER_MEASUREMENT_MAX
User Measurement Avg (#)
TT_USER_MEASUREMENT_AVG
User Measurement Min (#)
TT_USER_MEASUREMENT_MIN
Status diagnostics for the CODA SPI

The following table lists parameters that appear in the Status Detailed Diagnostics
for the CODA SPI.
Parameter
Unit
GBL_COLLECTOR
not applicable
GBL_INTERVAL
seconds
GBL_OSNAME
not applicable
GBL_OSVERSION
not applicable
GBL_OSRELEASE
not applicable
GBL_MACHINE
not applicable
GBL_NUM_CPU
GBL_MEM_PHYS
MB
GBL_NUM_DISK
GBL_NUM_NETWORK
GBL_MACHINE_MODEL
not applicable
GBL_STATTIME
date and time (mm/dd/yy hh:mm:ss AM|PM)
GBL_ACTIVE_CPU
GBL_RUN_QUEUE
GBL_CPU_SYS_MODE_UTIL
Parameter
Unit
GBL_CPU_USER_MODE_UTIL
GBL_CPU_TOTAL_UTIL
GBL_DISK_PHYS_IO_RATE
GBL_INTERRUPT_RATE
GBL_SWAP_SPACE_AVAIL
MB
GBL_SWAP_SPACE_UTIL
GBL_MEM_PAGEIN_RATE
GBL_MEM_PAGEOUT_RATE
GBL_MEM_UTIL
GBL_NET_IN_PACKET_RATE
GBL_NET_OUT_PACKET_RATE
GBL_NET_ERROR_RATE
GBL_FS_SPACE_UTIL_PEAK
Status diagnostics for the SCOPE SPI

The following table lists parameters that appear in the Status Detailed Diagnostics
for the SCOPE SPI.
Parameter
Unit
GBL_STATTIME
date and time (mm/dd/yy hh:mm:ss AM|PM)
GBL_INTERVAL
seconds
GBL_INTERRUPT_RATE
GBL_ACTIVE_CPU
GBL_CPU_TOTAL_UTIL
GBL_CPU_SYS_MODE_UTIL
GBL_CPU_USER_MODE_UTIL
GBL_NUM_DISK
GBL_DISK_PHYS_IO_RATE
GBL_FS_SPACE_UTIL_PEAK
GBL_MEM_UTIL
435
Parameter
Unit
GBL_SWAP_SPACE_UTIL
GBL_MEM_PAGEOUT_RATE
GBL_MEM_PAGEIN_RATE
GBL_NUM_NETWORK
GBL_NET_ERROR_RATE
GBL_NET_IN_PACKET_RATE
GBL_NET_OUT_PACKET_RATE
GBL_RUN_QUEUE
Top 10 VMs by balloon size on an ESX server

At any time, you can view the 10 VMs with the greatest balloon size within an ESX
server.
In the Operations Console, for a selected VMware Host system monitor instance,
choose Tools => Diagnostics => Top 10 VMs by Balloon Size.
Table 46 on page 436 lists the input and output attributes for the top 10 VMs by
balloon size.
Table 46: Attributes of top 10 VMs by balloon size on an ESX server
Attribute Types
Attribute Name Description
Input attributes
DNS IP
IP address of the VC or ESX.
Username
Username to connect to the Virtual Center or ESX server.
Password
Password to connect to the Virtual Center or ESX server.
VM Name
Name of the VM under an ESX host on which the DD is triggered.
VM DNS
Name
DNS name of the VM under an ESX host on which the DD is triggered.
Balloon
Memory Size
(MB)
Balloon memory usage of VM.
Output attributes
Top 10 VMs by CPU usage on an ESX server

At any time, you can view the 10 VMs with the greatest CPU usage within an ESX
server.
choose Tools => Diagnostics => Top 10 VMs by CPU Usage.
Table 47 on page 437 lists the input and output attributes for the top 10 VMs by CPU
usage.
Table 47: Attributes of top 10 VMs by CPU usage on an ESX server
Attribute Types
Input attributes
DNS IP
Username
Password
VM Name
VM DNS
Name
CPU Usage
(%)
CPU usage of VM.
Output attributes
Top 10 VMs by memory usage on an ESX server

At any time, you can view the 10 VMs with the greatest memory usage within an
ESX server.
choose Tools => Diagnostics => Top 10 VMs by Memory Usage.
memory usage.
Table 48: Attributes of top 10 VMs by memory usage on an ESX server
Attribute Types
Input attributes
DNS IP
Username
Password
VM Name
VM DNS
Name
Memory
Usage (%)
Memory usage of VM.
Output attributes
437
Top 10 VMs by network usage on an ESX server

At any time, you can view the 10 VMs with the greatest network usage within an
ESX server.
choose Tools => Diagnostics => Top 10 VMs by Network Usage.
network usage.
Table 49: Attributes of top 10 VMs by network usage on an ESX server
Attribute Types
Input attributes
DNS IP
Username
Password
VM Name
VM DNS
Name
Network
Usage (KBps)
Network usage of VM.
Output attributes
Top 10 VMs by balloon memory size on a Virtual Center

At any time, you can view the 10 VMs with the greatest balloon size within a Virtual
Center.
In the Operations Console, for a selected VMware VC system monitor instance,
choose Tools => Diagnostics => Top 10 VMs (in the Virtual Center) by Balloon
memory.
balloon memory.
Table 50: Attributes of top 10 VMs by balloon memory size on a Virtual Center
Attribute Types
Input attributes
DNS IP
IP address of the VC.
Username
Username to connect to the Virtual Center.
Password
Password to connect to the Virtual Center.
Attribute Types
Output attributes
VM Name
Name of the VM under Virtual Center on which the DD is triggered.
VM DNS
Name
DNS name of the VM under Virtual Center on which the DD is

triggered.
Balloon
Memory Size
(MB)
Balloon Memory usage of VM.
Top 10 VMs by CPU usage on a Virtual Center

At any time, you can view the 10 VMs with the greatest CPU usage within a Virtual
Center.
choose Tools => Diagnostics => Top 10 VMs (in the Virtual Center) by CPU Usage.
usage.
Table 51: Attributes of top 10 VMs by CPU usage on a Virtual Center
Attribute Types
Input attributes
DNS IP
Username
Password
VM Name
Name of the VM under the Virtual Center on which the DD is triggered.
VM DNS
Name
DNS name of the VM under the Virtual Center on which the DD is

triggered.
CPU Usage
(%)
CPU usage of VM.
Output attributes
Top 10 VMs by Memory usage on a Virtual Center

At any time, you can view the 10 VMs with the greatest memory usage within a
Virtual Center.
choose Tools => Diagnostics => Top 10 VMs (in the Virtual Center) by Memory
Usage.
439
memory usage.
Table 52: Attributes of top 10 VMs by memory usage on a Virtual Center
Attribute Types
Input attributes
DNS IP
Username
Password
VM Name
VM DNS
Name

triggered.
Memory
Usage (%)
Memory usage of VM.
Output attributes
Top 10 VMs by Network usage on a Virtual Center

At any time, you can view the 10 VMs with the greatest network usage within a
Virtual Center.
choose Tools => Diagnostics => Top 10 VMs (in the Virtual Center) by Network
Usage.
Network usage.
Table 53: Attributes of top 10 VMs by network usage on a Virtual Center
Attribute Types
Input attributes
DNS IP
Username
Password
VM Name
VM DNS
Name

triggered.
Network
Usage (KBps)
Network usage of VM.
Output attributes
Top 10 VMs by balloon memory size on a Resource Pool

At any time, you can view the 10 VMs with the greatest balloon memory size within
a Resource Pool.
In the Operations Console, for a selected VMware Resource Pool system monitor
instance, choose Tools => Diagnostics => Top 10 VMs (in the Resource Pool) by
Balloon memory.
balloon memory.
Table 54: Attributes of top 10 VMs by balloon memory size on a Resource Pool
Attribute Types
Input attributes
DNS IP
Username
Password
Instance
Name
Name of Resource Pool to get the top VMs
VM Name
Name of the VM under the Resource Pool on which the DD is triggered.
VM DNS
Name
DNS name of the VM under the Resource Pool on which the DD is

triggered.
Balloon
Memory Size
(MB)
Output attributes
Top 10 VMs by CPU usage on a Resource Pool

At any time, you can view the 10 VMs with the greatest CPU usage within a
Resource Pool.
CPU Usage.
usage.
441
Table 55: Attributes of top 10 VMs by CPU usage on a Resource Pool

Attribute Types
Input attributes
DNS IP
Username
Password
Instance
Name
VM Name
Name of the VM under Resource Pool on which the DD is triggered.
VM DNS
Name
DNS name of the VM under Resource Pool on which the DD is

triggered.
CPU Usage
(MHz)
CPU usage of VM.
Output attributes
Top 10 VMs by memory usage on a Resource Pool

At any time, you can view the 10 VMs with the greatest memory usage within a
Resource Pool.
Memory Usage.
memory usage.
Table 56: Attributes of top 10 VMs by memory usage on a Resource Pool
Attribute Types
Input attributes
DNS IP
Username
Password
Instance
Name
VM Name
Name of the VM under Resource Pool on which the DD is triggered.
VM DNS
Name
DNS name of the VM under Resource Pool on which the DD is

triggered.
Memory
Usage (%)
Memory usage of VM.
Output attributes
Top 10 VMs by balloon memory size on a cluster

At any time, you can view the 10 VMs with the greatest balloon size within a cluster.
In the Operations Console, for a selected VMware Cluster system monitor instance,
choose Tools => Diagnostics => Top 10 VMs (in the Cluster) by Balloon memory.
balloon memory.
Table 57: Attributes of top 10 VMs by balloon memory size on a cluster
Attribute Types
Input attributes
DNS IP
Username
Password
Instance
Name
Name of the cluster to get the top VMs
VM Name
Name of the VM under cluster on which the DD is triggered.
VM DNS
Name
DNS name of the VM under cluster on which the DD is triggered.
Balloon
Memory Size
(MB)
Output attributes
Top 10 VMs by CPU usage on a cluster

At any time, you can view the 10 VMs with the greatest CPU usage within a cluster.
choose Tools => Diagnostics => Top 10 VMs (in the Cluster) by CPU Usage.
usage.
443
Table 58: Attributes of top 10 VMs by CPU usage on a cluster

Attribute Types
Input attributes
DNS IP
Username
Password
Instance
Name
VM Name
VM DNS
Name
CPU Usage
(MHz)
CPU usage of VM.
Output attributes
Top 10 VMs by Memory usage on a cluster

At any time, you can view the 10 VMs with the greatest memory usage within a cluster.
choose Tools => Diagnostics => Top 10 VMs (in the Cluster) by Memory Usage.
memory usage.
Table 59: Attributes of top 10 VMs by memory usage on a cluster
Attribute Types
Input attributes
DNS IP
Username
Password
Instance
Name
VM Name
VM DNS
Name
Memory
Usage (%)
Memory usage of VM.
Output attributes
Note
Error messages with error code 117006 (for example, Could not get data for
top 10 VMs by Memory Usage and reasonString, where reasonString is the
exception message) are displayed in the DD window for VMware adapters in the
following situations:
the VC service is stopped
connection to VC times out
ESX in which DD is invoked is switched off
all VMs under a particular ESX are powered off
The DD window displays an IP address instead of a blank if DNS is not
configured for a VM.
Application Diagnostics for BMC AppSight integrations

With BMC ProactiveNet Application Diagnostics you can capture and view detailed
availability and performance data for events that exceed defined thresholds.
BMC ProactiveNet Application Diagnostics pinpoints, captures, and communicates
the root cause of application problems for a specific transaction. The Application
Diagnostics agents are lightweight software agents that are deployed on Java EE
or .NET application servers. Their primary role is gathering diagnostic data on
application transaction performance, execution, and errors. These agents are based
on the BMC AppSight Black Box patented technology and provide deep application
diagnostics for inclusion in application root cause analysis.
To enable BMC ProactiveNet Application Diagnostics, ensure that the BMC
ProactiveNet environment includes the following components:
BMC ProactiveNet integration with BMC AppSight and supported components
(see the BMC ProactiveNet Deployment Guide)
BMC ProactiveNet basic event rule definitions based on static or dynamic
thresholds. Follow the instructions in the BMC ProactiveNet User Guide to add a
basic event rule type. Ensure that the following options are set:
On the "Add Event Rule (Page 1/3)" screen, select Basic Event Rule, if not
already selected.
445
On the "Add Event Rule (Page 2/3): Select Event/Monitor/Severity
Information" screen, on the Event tab of the "Severity/State Filter" section,

select Open . Each time an Event is opened and clear all other selections.
In the Run Agent Diagnostics list, select Application Diagnostics and click
Add.
When an event exceeds a threshold, BMC ProactiveNet retrieves details from the
BMC AppSight Server and presents the information in the BMC ProactiveNet
Application Diagnostics window (a specialized Detailed Diagnostics window).
For example, when a transaction is slow or incomplete, an event is generated. A
Detailed Diagnostics icon
is displayed next to the event in the Operations
Console. Click the icon to open the Application Diagnostics summary window.
The Application Diagnostics summary window contains the following statistical
data from the BMC AppSight Server:
Table 60: BMC ProactiveNet Application Diagnostics summary attributes
Attribute
Description
Number of captured invocations
Number of invocations, or entry points, captured for this

event
Slowest invocation
Name of the slowest captured invocation. If the invocation

name is truncated, the full name is displayed in a tool tip
over the name.
Number of application exceptions
Number of application Java exceptions in the captured

invocations
Most common exception
Name of the most common Java exception among the

captured invocations. If the exception name is truncated,
the full name is displayed in a tool tip over the name.
Technology breakdown
Pie chart that represents the percentage of time occupied

by each technology for the captured invocations.
See BMC ProactiveNet Application Diagnostics
invocation tree on page 449 for a list of the technologies
that can be displayed.
Click the link at the bottom of the window to view details about captured invocations.
Application Diagnostics for BMC TM ART on page 447
Application Diagnostics for BMC PATROL on page 448
Application Diagnostics for BMC TM ART

This topic describes the information displayed by BMC ProactiveNet Application
Diagnostics for a BMC TM ART integration.
BMC AppSight captures BMC TM ART transaction data when an event exceeds a
defined threshold. Through BMC ProactiveNet, you can examine performance
statistics and code-level data about a BMC TM ART transaction instance and about
the transaction instance invocations.
Note
An invocation can use a parameter to determine its actions, such as in a Java Struts
Framework. A specified parameter name (action, by default) and its value are
displayed at the end of the invocation name. You can customize the parameter name
by changing the value of the invocation.action.parameter.name property in the
appsightconsole.properties file. The file is located on the BMC AppSight Repository
server, in the installDirectory/server/properties directory.
Application Diagnostics transaction instance attributes

For each BMC TM ART transaction, the Application Diagnostics window displays
the transaction instance details of the captured web hits, also called entry points.
Transaction instance attributes are described in the following table.
Note
If BMC AppSight returns a single transaction instance, this window does not appear.
Table 61: Application Diagnostics transaction instance attributes
Attribute
Description
Time
Start time of the transaction instance. Time is displayed as a 24-hour clock

at the local time zone of your browser, in the following format: hh:mm:ss.
Click the Time link to see invocation attributes (see Application
Diagnostics invocation attributes on page 448 for details).
Total Duration
Total time of the transaction instance
Slowest Invocation
Name and time of the slowest invocation in the transaction instance
Avg. Invocation
Average invocation time in the transaction instance
Breakdown
Bar chart that represents the percentage of time occupied by each

technology in the transaction instance.
See BMC ProactiveNet Application Diagnostics invocation tree on page
449 for a list of the technologies that can be displayed.
447
Application Diagnostics invocation attributes

The Application Diagnostics window displays performance statistics about the
technologies involved in a selected transaction instance, as described in the
following table:
Table 62: Application Diagnostics invocation attributes
Attribute
Description
Invocation
Web entry that is part of the invocation.

Click the URL Pattern link to see the invocation tree (see BMC
ProactiveNet Application Diagnostics invocation tree on page 449 for
details).
Start
Start time of the invocation
Duration
Duration of the invocation
Server
IP address and port number where the transaction was captured, in the
following format: IP:port.
Breakdown

technology for the invocation.
Application Diagnostics for BMC PATROL

This topic describes the information displayed in BMC ProactiveNet Application
Diagnostics for BMC PATROL integration.
BMC AppSight captures BMC PATROL invocation data when an event exceeds a
defined threshold. Through BMC ProactiveNet, you can examine performance
statistics and code-level data about a BMC PATROL invocation instance.
Note
An invocation can use a parameter to determine its actions, such as in a Java Struts
Framework. A specified parameter name (action, by default) and its value are
displayed at the end of the invocation name. You can customize the parameter name
by changing the value of the invocation.action.parameter.name property in the
appsightconsole.properties file. The file is located on the BMC AppSight Repository
server, in the installDirectory/server/properties directory.
Application Diagnostics invocation attributes

The Application Diagnostics window displays performance statistics about the
technologies involved in each captured invocation, as described in the following table.
Table 63: Application Diagnostics invocation attributes

Attribute
Description
Invocation
Invocation path.
Click the link to see the invocation tree. See BMC ProactiveNet
Application Diagnostics invocation tree on page 449 for details.
Start
Start time of the invocation
Duration
Duration of the invocation
Exceptions
If an exception occurs on the invocation, the name of the first exception

(alphabetically) is displayed.
If the invocation has more than one exception, click the link to see an
alphabetical list of all exceptions.
Server
IP address and port number where the transaction was captured, in the
following format: IP:port.
Breakdown

technology in the invocation.
BMC ProactiveNet Application Diagnostics invocation tree

The BMC ProactiveNet Application Diagnostics invocation tree displays the call
stack and the exceptions involved in a selected invocation flow. Information in the
call stack can be useful to determine the source of application issues such as slowed
performance or accuracy errors.
When you click a link in the Invocation list, the BMC ProactiveNet Application
Diagnostics window displays the call stack of the invocation.
The nodes in the invocation tree represent function calls and exception details in the
stack dump. You can expand or collapse the nodes for more comfortable viewing.
To the right of each call, a bar graph represents the length of time spent in the
function call and the technologies involved in the call.
Technologies might include one or more of the following:
Web (such as JSP and ASP.NET)
Business Components (such as EJB, COM, and assemblies)
Database (such as JDBC and ADO)
Web Services
449
Directory (such as JNDI and Active Directory)

Queue
Custom user-defined commands are registered through the Administration Console
using the Diagnostics Wizard option on the Tools menu. Once defined, both
preconfigured commands and user-defined commands can be run using the Tools
menu in the Operations Console.
There are two user-defined command options from which to choose:
Script Command
Use this option to create custom script-based commands that can be executed
through the Operations Console under the Tools menu or Event Rules.
Log File Command
Use this option to create custom Log File Search commands that can be executed
through the Operations Console under the Tools menu or Event Rules.
Once defined, you can use the Diagnostics Wizard tool to add a new command, edit
a previously registered command, or delete a command from the system.
To leverage the diagnostics feature to its full potential, it is recommended that you
configure Event Rules to trigger your diagnostic command. Whenever possible this
should be set up to trigger off of the signature thresholds (as opposed to just
absolute thresholds), since signature thresholds detect abnormalities that are not
usually caught by absolute thresholds. Triggering diagnostics through signature
thresholds ties the power of diagnostics with the power of BMC ProactiveNets
probable cause correlation capabilities.
These commands, when attached to event rules, automatically launch when event
conditions are met.
Note
URL Diagnostic Commands, or other Custom commands requiring user interaction
at run time, should not be used with Event Rules, since these commands will be
ignored by the system. The best way to capture the desired
information and run a diagnostics against a Web site is to write a program/script
and run it against the site.
Remote Diagnostics Command
Use this option to create Remote Commands that can be executed through the
Operations Console under the Tools menu or Event Rules.
Configuration of poll driven detailed

diagnostics
While creating Script or log file detailed diagnostic commands, the option
Configuration Diagnostic enables you to make them available to be run with every
configuration poll. Such commands are referred to as Configuration poll driven
detailed diagnostics. For information on creating such commands, refer Script and
Log File Detailed Diagnostic topics.
BMC ProactiveNet enables you to run Detailed Diagnostic commands in the
following situations:
On Demand - The commands can be run (on any agent) from the Operations
Console (Tools menu)
Auto run - When the commands are associated with an event rule
Periodic basis - When the commands are defined to be run with every
configuration poll. This can be set from the Control tab of select monitors using
the Configuration Diagnostic field. The Detailed Diagnostic commands are run
once the configuration poll has been completed successfully.
The advantage of running Detailed Diagnostic commands on a periodic basis is that

data is collected at regular intervals and most of this data can be considered as data
collected under normal conditions. This helps us compare data collected under
normal conditions with data from abnormal situations. For example, when data is
collected from commands auto run with an event rule.
This feature is available only for the following monitors:
Linux System monitor
Solaris System monitor
Windows System monitor
X86 Solaris System monitor
Data collected from Configuration Poll Driven Detailed Diagnostics can be viewed
from the following pages of the Operations Console:
451
Graph Display page

Probable Cause Analysis for selected Event page
The Monitor Information tab of the Graph Display page displays the column
Configuration Diagnostic for monitors that support configuration poll-driven
detailed diagnostic commands.
Click the Detailed Diagnostic icon in the configuration diagnostic column to display
the Configuration Detail Diagnostics information for the monitor. The column
displays None if no Detailed Diagnostics command is associated with the monitor.
For a Configuration Poll Detailed Diagnostic command output, the Server Time and
Agent Time are the same.
However, the Date Executed column displays the time on the BMC ProactiveNet
Server computer when the Detailed Diagnostic command output was received from
the agent. This time will be equal to the Server Time and Agent Time of the
command output if it was executed on the local agent. This time of execution of the
Detailed Diagnostic command may be different from the Server Time and Agent
Time if the command was executed on a remote agent.
Clicking the Diagnostics icon on the Probable Cause Analysis for Selected Event
page displays the result of the Detailed Diagnostics command associated with the
event rule in the Detail Diagnostics window.
Clicking the Configuration Diagnostics icon in the Detail Diagnostics window
displays the results of the periodically run Configuration poll driven detailed
diagnostic commands for the monitor. The Diagnostics column displays None if no
Detailed Diagnostic command was triggered for this event rule and the Detail
Diagnostic icon if a Detail Diagnostic command was triggered for the event rule.
Limitations
You cannot stop running a periodic Detailed Diagnostic command when the
monitor with which it is associated is functioning.
Configuration poll driven Detailed Diagnostics cannot be associated with
monitors running on older BMC ProactiveNet Agents (prior to version 7.0).
After you edit or delete a Detailed Diagnostic command, edit monitor instances
(with which the command is associated to be run at every configuration poll) for
changes to be effective.
If you delete a Detailed Diagnostic command, the command is not listed in the
Control tab of the Edit <Monitor> screen. However, you must edit the monitor
instance with which the command was associated.
If you change a Detailed Diagnostic command name, the old name of the
command is no longer listed in the Control tab of the Edit <Monitor> screen.
Instead, the new name of the command is listed. Enable the command by selecting
it in the Control tab.
If you don't change the command name but alter the command properties, edit
the monitor instance with which the command is associated.
Configuration poll driven Detailed Diagnostics may not run for the first
configuration poll for any monitor instance with which the configuration poll
Detailed Diagnostic is associated. This usually happens when the agent on which the
monitor is running is busy. In such conditions, the configuration poll Detailed
Diagnostic output may not be available for the monitor from the Monitor
Information tab of the Graph Display page in the Operations Console. Please wait
for the next configuration poll for the configuration poll Detailed Diagnostic output
to be available.
453
9
Administering BMC ProactiveNet
BMC ProactiveNet Server installs a SSL-enabled Apache Server. The SSL Web server
uses a dummy certificate that needs to be replaced before HTTPS protocol is
seriously used.
Creating a Real SSL server certificate for the Apache Server

Perform the following procedure to create a real SSL server certificate for the Apache
server.
To create a real SSL server certificate for the Apache server

1 Create a RSA private key for your Apache server.
This will be Triple-DES encrypted and PEM formatted:
$ /usr/pw/apache/bin/openssl genrsa -des3 -out server.key 1024
The private key sizes for SSL must either be 512 or 1024, for compatibility with
certain Web browsers. A keysize of 1024 bits is recommended because keys
larger than 1024 bits are incompatible with some versions of Netscape
Navigator and Microsoft Internet Explorer, and with other browsers that use
RSA's BSAFE cryptography toolkit.
Back up server.key file and remember the pass-phrase you had to enter at a
secure location. You can see the details of this RSA private key via the command:
$ /usr/pw/apache/bin/openssl rsa -noout -text -in server.key
2 Create a Certificate Signing Request (CSR) with the server RSA private key.
Chapter 9 Administering BMC ProactiveNet 455
This output will be PEM formatted.

$ /usr/pw/apache/bin/openssl req -new -key server.key -out server.csr
Ensure that you enter the FQDN (Fully Qualified Domain Name) of the server
when OpenSSL prompts you for the 'CommonName', i.e. when you generate a
CSR for a Web site, which will be later accessed via https://www.foo.dom/ ,
enter 'www.foo.dom' here. You can see details of this CSR via the command
$ /usr/pw/apache/bin/openssl req -noout -text -in server.csr
3 Now send this Certificate Signing Request (CSR) to a Certifying Authority (CA)
for signing.
The result is then a real certificate that can be used for Apache.
Here you have two options:

a First, you can let the CSR be signed by a commercial CA like Verisign or
Thawte. Then you usually have to post the CSR into a Web form, pay for the
signing, and await the signed certificate that you can then store in a server.crt
file. For more information about commercial CAs see:
Verisign: http://digitalid.verisign.com/server
Thawte Consulting: http://www.thawte.com/certs/server/request.html
CertiSign Certificadora Digital Ltd: http://www.certisign.com.br
IKS GmbH: http://www.iks-jena.de/produkte/ca/
Uptime Commerce Ltd: http://www.uptimecommerce.com
BelSign NV/SA: http://www.belsign.be
b Second, you can use your own CA and get the CSR signed by this CA.
Read below on how to get CSR signed by your CA yourself. You can see
details of the received certificate via the command:
$ /usr/pw/apache/bin/openssl x509 -noout -text -in server.crt
c Now you have two files: server.key and server.crt.

They replace the two corresponding files in /usr/pw/apache/conf/ssl.key/ and /
usr/pw/apache/conf/ssl.crt/.
server.csr file is no longer needed.
The Verisign site http://www.verisign.com/support/csr/apache/v00.html also
has some info on this subject.
Removing the pass-phrase at Apache startup time

Since RSA private key inside server.key file is stored in encrypted format for security
reasons, the pass-phrase is required to read and parse this file. When you are sure
that your server is secure enough, perform the following procedure.
To remove the pass-phrase at Apache startup time

1 Remove the encryption from the RSA private key while preserving the original file:
$ cp server.key server.key.org
$ /usr/pw/apache/bin/openssl rsa -in server.key.org -out server.key
2 Ensure that server.key is now readable only by root:

$ chmod 400 server.key
Now server.key will contain an unencrypted copy of the key. When Apache
server starts, it will not prompt you for a pass-phrase. If anyone gets this key,
they will be able to impersonate you on the net. So ensure that permissions on
that file are such that only root or Web server user can read it (preferably get
your Web server to start as root but run as another server, and have the key
readable only by root).
Changing the pass-phrase on the private key file

Here are the commands to accomplish pass-phrase change:
$ /usr/pw/apache/bin/openssl rsa -des3 -in server.key -out server.key.new
$ mv server.key.new server.key
You will be asked twice for a PEM pass-phrase. At the first prompt, enter the old passphrase and at the second prompt enter the new pass-phrase.
Creating and using your own certificate authority (CA)

Perform the following procedure to create and use your own certificate authority.
To create and use your own certificate authority

1 Create a RSA private key for your CA (will be Triple-DES encrypted and PEM
formatted):
$ /usr/pw/apache/bin/openssl genrsa -des3 -out ca.key 1024
Back up ca.key file and remember the pass-phrase you currently entered at a
secure location. You can see details of this RSA private key via the following
command:
$ /usr/pw/apache/bin/openssl rsa -noout -text -in ca.key
2 Create a self-signed CA certificate (X509 structure) with the RSA key of the CA
(output will be PEM formatted):
$ /usr/pw/apache/bin/openssl req -new -x509 -days 365 -key ca.key -out
ca.crt
You can see details of this certificate via the following command:
$ /usr/pw/apache/bin/openssl x509 -noout -text -in ca.crt
3 Prepare a script for signing.

This is needed because the 'openssl ca' command has some strange
requirements and the default OpenSSL config doesn't allow one easily to use
'openssl ca' directly.
So a script named sign.sh is distributed with apache mod_ssl. Use this script for
signing. Now you can use this CA to sign server CSRs to create real SSL
certificates for use inside an Apache Web server (assuming you already have a
server.csr at hand):
$ /usr/pw/apache/openssl/misc/sign.sh server.csr
This signs the server CSR and results in a server.crt file.
Configuring the Apache web server to accept HTTPS

connection only
In case your site does not need a HTTP connection, here are the steps to reconfigure
Apache.
To configure the Apache web server to accept HTTPS connections

1 cd /usr/pw/apache/conf.
2 Save a copy of the httpd.conf file.
3 Edit the httpd.conf fileto comment out line 292 'Port 80' and line 301 'Listen 80', so
the two lines become '#Port 80' and '#Listen 80'.
4 Restart httpd by running the following command:
pw process restart httpd
Note
Switching Apache server from HTTP to HTTPS mode requires restarting the
system. BMC Software recommends due diligence before restarting the system.
Removing the pass-phrase window displayed during Apache

startup
The RSA private key inside the server.key file is stored in encrypted format for
security reasons. The pass-phrase window is displayed at startup and every restart
because the pass-phrase is required to decrypt the RSA private key (so it can be read
and parsed). Removing the pass-phrase removes a layer of security from your server
- proceed with caution!
To remove the pass-phrase window displayed during Apache startup

1 Remove the encryption from the RSA private key (while keeping a backup copy
of the original file) by following the steps given below:
$ cp server.key server.key.org
$ openssl rsa -in server.key.org -out server.key
2 Ensure that the server.key file is readable only by root:

$ chmod 400 server.key
Now server.key contains an unencrypted copy of the key. Directing your server to
the server.key file ensures that the pass-phrase is not prompted for. However, if
anyone gets this key, they will be able to impersonate you on the Internet.
PLEASE make sure that the permissions on this file are such that only root or the
Web server user can read it (It is recommended that you start the Web server as
root but run it as another user, and have the key readable only by root).
As an alternative approach you can use the 'SSLPassPhraseDialog exec:/path/to/
program' facility. But remember that this is neither more nor less secure.

This section provides details about configuring security for BMC ProactiveNet.
Securing port communication

Certain BMC ProactiveNet Server ports are used for communication between
processes. Some ports are used by processes running on the server only; these are
internal and need not be accessed by other computers in the network (Event server).
For security reasons, BMC Software recommends that all internal ports be made
accessible only via the loopback address (127.0.0.1). By default, ports that are not
required by external computers are secured, ie the properties associated with the
ports are set to the loopback address.
To make BMC ProactiveNet Server accessible to other computers in a network,
certain ports on the server must be made available. From a multi-homed computer,
BMC ProactiveNet Server processes can be accessed using any of the available IP
addresses.
Table 64: Secure port communication
Port
Process
Properties
Default
2638
Database
Server
pronet.api.database.hostname Available
( serverInstallDirectory /pw/ server IP
address
pronto/conf/pronet.conf)
12124
Local
Agent
pronet.apps.agent.port
serverInstallDirectory /pw/
pronto/conf/pronet.conf
15000
Rate
9149
JServer
Event
Server
12141
Procedure to Secure Multi-homed

port
computer Setup
Set the property
value to 127.0.0.1.
Then the database
server can not be
accessed from
other servers for
reporting.
Set the IP
address of the
required server
as the value of
the property.
Internal process
Set the IP
address of the
required server
as the value of
the property.
pronet.rate.hostIp( serverInsta 127.0.0.1

llDirectory /pw/pronto/conf/
pronet.conf)
Internal process
used by JServer;
secured by default
Port not required

by an external
computer
pronet.jserver.event.hostIp( se 127.0.0.1
rverInstallDirectory/pw/
Internal process
used by JServer;
secured by default
Port not required

by an external
computer
Log Server pronet.apps.logging.logServer 127.0.0.1

.hostnamepronet.apps.logging
.logServer.port( serverInstallD
irectory/ pw/pronto/conf/
pronet.conf)
Internal process;
secured by default
Port not required

by an external
computer
IP address
of the
available
server
Port
Process
Properties
Default
Procedure to Secure Multi-homed

port
computer Setup
8093
JBoss JMS
Server
( serverInstallDirectory /pw/
jboss/server/minimal_jms/
conf/jboss-serivice.xml) Line
# 58 change bind
address<attribute
name=BindAddress>{jboss.
bind.address}</attribute>
1100
JBoss JNDI pronet.apps.jboss.bind.addres 0.0.0.0

s ( serverInstallDirectory/pw/
Set the property

Port not required
value to 127.0.0.1. by an external
If the BMC Atrium computer
CMDB is
integrated with
BMC ProactiveNet
and you change
this property, then
the BMC Impact
Model Designer
can not
communicate with
the publishing
server.
12123
Agent
pronet.apps.agentcontrollerho 127.0.0.1
Controller stIp (serverInstallDirectory /
/ JServer pw/pronto/conf/pronet.conf
communic
ation
Internal process;
secured by default
Internal process;
secured by default
Port not required

by an external
computer
Port not required

by an external
computer
Note
To retain changes made to properties even after upgrade, copy the values to
serverInstallDirectory /pw/custom/conf/pronet.conf file.
Security related FAQs

1 How can I restrict to see only One Console (Operations/Service Mgmt/Enterprise)?
The options Enable Operations Console Access Controls, Allow EC Display
under general tab, and 'Enable SLO Access Controls under SLO tab can be used
to grant/restrict access to only one console.
2 How can I disable the HTTP interface and run BMC ProactiveNet over HTTPS
interface?
To disable HTTP interface, configure the Apache configuration file httpd.conf and
remove entries for port 80.
3 How can I set up BMC ProactiveNet to use PAM (Pluggable Authentication

Modules) to access computer level credentials?
This feature is not available in the current BMC ProactiveNet release.
4 How can I configure the HTML headers to display "Internal FR" label on top of
each page?
This is only partially supported. You can only change the logo and/or navigation
bar on the HTML page. For details on this, refer Customize logo on the
Operations Console topic.
5 How can I disable the default Pronto account?
To disable the default pronto account, simply delete the account after creating a
new account with Administrative privileges.
6 Where does BMC ProactiveNet store user names and passwords?
User names and passwords are stored in the database on BMC ProactiveNet
Server. All passwords are kept in encrypted format.
7 Are user names and passwords accessible via regular database access?
Database access to user name and password information is available to only to
database users with administrative privileges.
8 How to change the BMC ProactiveNet password policy?
The following entries in pronet.conf file can be used to set Password strength
pronet.login.minLength=6
pronet.login.maxLength=15
pronet.login.numericChars=1
9 Where is the HTTPS/SSL private key stored on BMC ProactiveNet Server?

This information is stored in a file under /usr/pw/apache/conf/, which can be read
only by the 'root' (BMC ProactiveNet install User) user. Refer Troubleshooting
section for details on working with these keys.
10 How can I print user activity lists?
To view user activity on BMC ProactiveNet, print Access.log ( located in usr/pw/
pronto/logs directory). These files record information related to user logons,
logouts, and logon failures.
11 Does BMC ProactiveNet automatically lock user accounts after certain number of
failed logon attempts?
BMC ProactiveNet does not lock the user account. However, all logon failures are
recorded in ProactiveNet.log. To lock such accounts, you can write a script to
delete the account based on the log file entries.
12 How to restrict the agent so that it will only receive connections from a specific
IPAddress?
Use the following property in pronet.conf
pronet.apps.agent.authorizedcontrolleraddress=<ipaddress>
13 How to configure agent controller to present a specific IP Address to an agent if
server has more than one NIC?
pronet.apps.agentcontroller.useIPForAgentConnection=<ipaddress>
If the servers computer has got more than one IP (more than one NIC), set this
property to IP address that agent controller will present while connecting to the
agent
14 Does BMC ProactiveNet automatically log out users after a certain period of
inactivity?
By default, inactive users are logged out of the Operations Console after 24 hours.
However, BMC ProactiveNet can be customized globally for all users. Use the
property pronet.html.globalsession.timeout in pronet.conf file located in usr/pw/
pronto/conf directory to configure this value.
If you change this property, ensure that you set the same log out period in the
Tom Cat config file /usr/pw/tomcat/conf/web.xml (line 321).
<session-config>
<session-timeout>1440</session-timeout>
</session-config>
Restart the httpd process by running the command 'pw p r httpd'.
Note
On restarting the httpd process, all users will be logged out.

15 What encryption method is used for storing password information used by BMC
ProactiveNet monitors?
Passwords used by BMC ProactiveNet monitors are protected by Passphrase
Based Encryption (PBE) as defined in PKCS#5 version 2.0. This encryption is
applied to passwords stored in the BMC ProactiveNet Server database that may
be used by a monitor to execute a transaction that requires user authentication.
16 How can I configure BMC ProactiveNet Server to run as non-root?
Run the script 'configNonRoot' to configure an installed BMC ProactiveNet Server
to run as a non-root user.
The script prompts for the new HTTP and HTTPS ports to be used by Apache
server and performs necessary changes. However, it is important that the initial
installation be performed by 'root' user. After conversion to non-root, upgrades
can be performed by a non-root user. The Apache and Tomcat components of the
server run as user 'nobody'. After running this utility, however, they will run as
the designated user.
Note
The server after being changed to run as non-root will have the following
limitations:
Web interface can no longer be accessed on ports 80 or 443; instead, you must
choose alternate ports above 1024 -- you will be prompted for these ports when
you run the conversion program "configNonRoot". You can also choose the
alternate ports by editing the file /usr/pw/apache/conf/httpd.conf
You cannot revert the ownership once you change it to non-root.

The local agent also experiences its own limitations in monitoring. More details
on this are provided later in this section.

Example
To make BMC ProactiveNet Server run as user "john":

# csh
# source /usr/pronto/bin/.tmcsh
# configNonRoot john
Follow the instructions to make BMC ProactiveNet Server run as user "john".
The same ConfigNonRoot command can also be run to switch BMC
ProactiveNet Server from one non-root user to another non-root user.
BMC ProactiveNet Server running as a non-root user can be upgraded either by
the same non-root user or by root. If upgraded by the same non-root user, the
same HTTP(S) ports will be used by the Apache Web Server during upgrade.
When BMC ProactiveNet Agent - Linux is run as non-root, the following
limitations are applicable:
Process monitor will not collect data for certain attributes (such as # file
descriptors), if process being monitored does not belong to the same user as
the agent.
Ping or Traceroute monitors cannot be run, since these require creation of
raw socket (requires root privileges). However, these utilities can be

executed from the command line by non-root users only because the sticky
bit is set, allowing them to run as root no matter who executes them.
Log File monitor will not work if the user running the agent does not have
read privileges on the log files. The workaround is to assign Read privileges
on the particular log file to "all" or to a particular group.
Disk Performance Monitor will not work since root privileges are required to
read the device files.
17 For enhanced security, Apache server can be configured to accept only SSL v3
requests. To accomplish this add the following entry in apache configuration file
httpd-ssl.conf.
SSLProtocol +SSLv3 ( Just above the directive SSLEngine on).
SSL communication between BMC ProactiveNet Server and

BMC ProactiveNet Agents
1 Does BMC ProactiveNet include its keystore files as part of the agent and server
SSL communication?
Yes, BMC ProactiveNet provides its own keystore files (pnserver.ks and
pnagent.ks) as part of the Agent and Server SSL communication. The keystore
files are stored under:
BMC ProactiveNet Server: /usr/pw/pronto/conf
BMC ProactiveNet Agent: <Agent Install Directory>/pw/pronto/conf
These files are only available to the root user for Read and Write.
2 Can you replace this keystore certificate with another one?
Yes, you can replace this keystore certificate with your own self-signed certificate.
3 How can I replace the keystore certificate with my own self-signed one?
To replace the BMC ProactiveNet certificate:
a Create a new keystore and self-signed certificate with corresponding public/
private keys.
*keytool -genkey -alias agent_<name> -keyalg RSA -validity 365 keystore agent_<name>.ks
This is the keystore that BMC ProactiveNet Agent uses.

1 Examine the keystore. Notice the entry type is |keyEntry|, which means that this
entry has a private key associated with it.
keytool -list -v -keystore agent_<name>
2 Export and examine the self-signed certificate.

*keytool -export -alias agent_<name> -keystore **agent_<name>.ks -rfc file agent_<name>.cer
3 Import the certificate into a new truststore.

*keytool -import -alias agent_<name>cert -file agent_<name>.cer -keystore
pnserver.ks
4 Examine the truststore. Note that the entry |trustedCertEntry| has been created.
*keytool -list -v -keystore pnserver.ks
keytool -export -alias pnca -keystore pnserver.ks -rfc -file pnserver.cer
keytool -import -alias pnca -file pnserver.cer -keystore agent_<name>.ks
5 Copy agent_<name>.ks to the respective pronto/conf directory of the remote

agent computer.
6 Change the following entry in the pronet.conf of the remote agent computer.
pronet.apps.ipc.ssl.context.agent.keystore.filename=pronto/conf/
agent_<name>.ks
7 Change the following entry in the .ks_pass file present in pronet/conf/ directory of
the remote computer.
pronet.apps.ipc.ssl.context.agent.keystore.passwd=<password provided during
creation of agent_<name>.ks>
8 Restart BMC ProactiveNet Agent using ./startremotepw multiple from the agent's
pronto/bin directory.
SSL communication between the agent and agent controller must be successful.
SSL communication architecture

BMC ProactiveNet Agent acts as the SSL server and the agent controller acts as the
SSL client. On both the agent and agent controller, a single keystore is used to
manage keys and certificates. The default keystores are pnagent.ks on the agent and
pnserver.ks on the server (found in <install directory>/conf directory). The keystore
file contains keyEntries (private keys) and trustedCertKey (public key) to trust the
opposite party.
Certificate authentication/trust happens on both the agent and agent controller. Key
pairs are generated through the keytool, and self-signed certificates are exported
from each keystore file.
The exported certificates are imported to the other party's keystore as
trustedCertEntries (the public key of the agent keystore is imported as a trusted
entry in the server and vice-versa).
For more information, see SSL TCP/IP Agent on page 61.
Customizing the BMC ProactiveNet

Operations Console
This section provides details about ways that you can customize the BMC
ProactiveNet Operations Console.
Customizing event text

You can customize the Event Rule Name and add it to the event description by
modifying the appropriate strings in the pronet.conf file. This adds an additional
variable called $EVENTRULE_NAME and causes the event processing system to
insert the name of the event rule into the description. The properties to modify start
with the following lines:
pronet.events.abs
pronet.events.sig
Note
Multiple event rules could affect a singe event. In this case, only the first event
rule name gets inserted into the description text.
Event messages may be customized to include additional information in the
Description field of an Event table. By editing the event text template in the
pronet.conf file, you can modify the event text and add additional event data to email notifications and event summary links.
The event definitions and default event text can be found in the main configuration
file:/usr/pw/pronto/conf/pronet.conf. However, when making configuration
changes, it is best to place them in the custom configuration file: /usr/pw/custom/conf/
pronet.conf.
You can use the definitions in the main file pronet.conf as templates. There are four
templates for absolute events and four for signature events.
Note
If you make changes to the main pronet.conf file, the changes will NOT be preserved
on upgrade, but will be over-written. However, the custom pronet.conf file is always
preserved during upgrade. When a BMC ProactiveNet process starts, it first reads
the main pronet.conf file for initialization. It then reads the custom pronet.conf, and
any properties defined in the custom file will override the definitions in the main
pronet.conf.
One application of this feature is to provide users with specific procedures to follow
when a problem occurs (i.e., "runbooks"). Such procedures can be referenced as a
URL supplied in custom event text.
For example, changing the definition in pronet.conf from
pronet.events.abs.abovethresh=$MO_TYPE $ATTR_NAME above $THRESH
$UNITS.<$EVENT_CODE,$ABNORMALITY,$AVG,$LAST,$DUR> to
pronet.events.abs.abovethresh=$MO_TYPE $ATTR_NAME above $THRESH$UNITS.
Please see http://helpserver.mycompany.com/runbooks/$MO_TYPE/
$ATTR_NAME<$EVENT_CODE,$ABNORMALITY,$AVG,$LAST,$DUR>.
This could be used to reference a Web page on a Web server called 'helpserver' that
tells an operator what to do when an event is issued for (example) Solaris System
Memory Utilization. You could make it even more specific by referring a procedure
for a particular monitor instance, for example:
http://helpserver.mycompany.com/runbooks/$MO_TYPE/$ATTR_NAME/
$INSTANCE_NAME
Of course, this would mean creating an extra Web page for each particular monitor
instance that needs its own procedure.
The above examples are simplified and are useful only in notification e-mails sent as
ASCII. They cannot be used to drill-down from the event summary.
Below is a more sophisticated example that embeds an HTML reference in the
definition so it can be referenced directly from the event summary. Note that in this
example the Web server provides dynamic Web content using active server pages:
pronet.events.abs.abovethresh=$MO_TYPE $ATTR_NAME above $THRESH
$UNITS.<A HREF http://helpserver.mycompany.com/proserver1/runbook.asp?
INST=$INSTANCE_NAME&MOTYPE=$MO_TYPE&ATTR_NAME=
$ATTR_NAME>Runbook1</A><$EVENT_CODE,$ABNORMALITY,$AVG,$LAST,
$DUR>
Note
It is very important NOT to modify the following string: <$EVENT_CODE,
$ABNORMALITY,$AVG,$LAST,$DUR>. Modifying this string will adversely

affect certain operations in the system.
Each definition must appear on a single line (ignore the line breaks in the examples).
Expanded text appearing after "=" sign should not exceed 254 characters (this
limit is imposed by the database tables). Expanded text is one that already has
variable substitutions. To prevent this, please avoid using long URL paths for
runbooks pages.
To avoid inappropriate navigation or event history generation failure, it is
recommended to have runbooks URL within quotes.
Once the changes are completed, you must restart BMC ProactiveNet Server for the
changes to take effect. Alternatively, you can just start the rate process (pw process
restart rate)., and then restart the snmpdc process (pw process restart snmpdc).
Customizing the logo on the Operations Console

BMC ProactiveNet enables the Administrator to change the ProactiveNet.gif logo on
the Operations Console.
Figure 57 on page 469 shows that the 'ProactiveNet' logo has been changed. When
such a change is made, the 'Powered by ProactiveNet' logo is placed on the top right
of the navigation bar. The 'About' link can also be changed to reflect your companys
name and point to a company Web site or other location.
Figure 57: Changing BMC ProactiveNet logo on the Operations Console
The properties files for these GIFs are located in /usr/pw/custom/conf/pronet.conf.

Properties not present by default need to be created by the user.
The default GIF size for the logo is 210 X 20 pixels and you must reload the
properties by running the following command:
pronet.conf file contains the following properties:
pronet.toplogo=/custom/ART/gui_top_logo.gif
pronet.about.href=http://my.about.com
Note
If you change the GIFs, the replacement GIFs must be copied from pronet.conf
and placed in the installDirectory /pw/custom/ART directory. The install script
will ensure that your new art files are restored during upgrades (thereby
preserving your changes)
Adding background images

BMC ProactiveNet comes with default images that you can use to customize the
background of the Tile and Canvas views in the Operations Console; however, you
can also add your own images to the BMC ProactiveNet Server and then select those
images to display in the Tile and Canvas views.
To add background images

1 On the computer that hosts the BMC ProactiveNet Server, copy the image files
that you want to add to the following directory:
installDirectory \tomcat\webapps\pronto\jsp\swf\assets\
backgrounds
The installDirectory variable is the installation directory for the BMC
BMC ProactiveNet supports common graphic file types such as .png, .gif,
.bmp, .jpg, and .swf.
2 Backup the background.xml file.
The file is located in the following directory:
installDirectory \tomcat\webapps\pronto\jsp\swf\assets
3 In a text editor that does not add new line characters to a file, open the
background.xml file.
4 In the <backgroundImages> section of the background.xml file, add an entry for
each new image by entering the name of the image that you want to display in the
Operations Console and the file name of the image, including the path where the
image is located.
For example, if you want to add a file named CompanyHQ.gif, then the entry
in the background.xml file would be as follows:
<backgroundImages>
<image name="Company Headquarters" path="/jsp/swf/assets/backgrounds/
CompanyHQ.gif"/>
Ensure that the entries that you add are formatted the same as the entries that
exist in the file. If the background.xml file is not configured correctly, the BMC
ProactiveNet Server will be unable to read it.
5 Save the background.xml file and close it.
To display the new images in the Tile and Canvas views

1 If you are logged on to the Operations Console, log out, clear the browser cache
and close the browser.
2 Open the browser, and log on to the Operations Console again.
3 Select an object in the Navigation Tree and then select Tile View or Canvas View.
4 Open the Preferences dialog box in the Tile View or Canvas View.
5 In the Background pane of the Preferences dialog box, select the Image check box
and then use the list to select the new background image that you want to display.
Changing the default number of breadcrumbs displayed in

the operations console
By default, the number of breadcrumbs displayed in the operations console is five.
Perform the following procedure to change the default value.
To change the number of breadcrumbs displayed in the operations console

The file is located in the installDirectory\pw\custom\conf directory.
2 Change the value for the following parameter:
pronet.breadcrumb.maximum=5
3 Close and save the pronet.conf file.
4 Enter the following command from a command line:

5 If the operations console is open, refresh the browser to view the change.
Improving performance when the navigation tree is loaded

in the operations console
By default, when you open the navigation tree in the operations console, all nodes
and subnodes are loaded even if a node is not expanded. If you have a lot of nodes
defined in the navigation tree, you could experience a delay in the navigation tree
loading completely. You can change the way that the navigation tree loads by
turning on an option called lazy loading. When lazy loading is turned on, a branch
in the navigation tree gets loaded only when it is expanded.
To turn on lazy loading

The file is located in the installDirectory\pw\pronto\conf directory.
2 Change the value for the following parameter to True:
pronet.navtree.lazyloading
5 If the operations console is open, refresh the browser to view the change.
Changing the maximum number of configuration items in a

folder
By default, a static or dynamic folder can hold a maximum of 500 configuration
items. You can configure this value in the pronet.conf file.
To change the maximum number of CIs in a folder

2 Enter a number for the following parameter:
pronet.max.ci.count=500
WARNING
If you enter a value that is more than 500, you might experience performance
issues when folders are loaded into the navigation tree.
4 Restart the jserver.
Configuring the operations console to automatically switch

views
You use the view icons in the operations console to change the views for the object
types that you select in the navigation tree. The view stays the same until you select
a different view. Perform the following task to enable a configuration option that
allows the view to be changed automatically. When this option is enabled, the
operations console automatically changes to the default view defined for the object
type that you select.
You can still use the toolbar to change to other views. The view does not change
when you select objects of the same type.
To automatically change views when navigating in the operations console

2 Set the following option to true:
pronet.navigation.use.default.view

4 Enter the following command from a command line to reload the property files:
Scheduling downtime
5 If the operations console is open, refresh the browser.
Scheduling downtime
Tip
For information on the relation between the Scheduled Down Time feature and the
blackout event management policy, see Relation to Scheduled Down Time feature on
page 592.
The Scheduled Down Time feature for devices, monitors, and groups enables BMC
ProactiveNet administrators to specify a time range during which the monitor,
device, or group stops collecting data.
The Scheduled Down Time feature supports multiple schedules with different time
ranges.
You can schedule down time for the following frequencies:
one-time
daily
weekly
monthly
The scheduler polls the database periodically for downtime events. By default, this
period is five minutes; therefore, down-time events cannot be scheduled with finer
granularity than five minutes. In addition, if a large number of devices is scheduled,
it may take some time for the scheduler to turn off data collection for the scheduled
devices.
To avoid the possibility of false events at the beginning of the maintenance window,
BMC ProactiveNet recommends that the downtime event be scheduled 15-20
minutes ahead of the actual maintenance period.
Scheduling downtime
Note
While scheduling downtime, allow fair time for the device, monitor, or group to stop
data collection. The time taken to stop data collection and then resume data
collection depends on the server load, number of agents, and number of monitors
scheduled for down time.
In Windows Day and Time Properties, select Automatically adjust clock for daylight
saving changes. This should always be selected to show the appropriate default time
zone.
Note for upgrade users

New and upgrade users have different options available to them in this feature.
Upgrade users can still access the Alarm/Event Generation, AlarmRule Action/
Notification, and Calculate Baseline options from the Add Device for Scheduled
Down Time dialog. For example, upgrade users can
stop alarm/event generation
stop alarm-related notifications/actions
calculate baseline parameters
If an upgrade user turns on the Data Collection option , then the Calculate Baseline
option is enabled. Upgrade users have the option to turn baseline calculation off or
on when Data Collection is on. (When Data Collection is off, the Calculate Baseline
option is disabled because there is no data to calculate.)
Usage scenario
A typical data sample can consist of the following test data:
Load on BMC ProactiveNet Server: Moderate (system load <1.5)
Number of agents scheduled down: 4
Number of monitors scheduled down: 1200
Scheduled down duration: 45 mins
Time taken to stop data collection: 10 - 15 mins
Time taken to resume data collection: 1 - 5 mins
To understand the usage of the Scheduled Down Time feature, let us look at the
following example:
Scheduling downtime
Assumptions:
BMC ProactiveNet is monitoring a web server for availability and response time.
The web server is brought down on Sunday between 4 A.M. and 8 A.M. for
maintenance.
Operations:
During regular monitoring, BMC ProactiveNet will poll for the monitored
attributes and report.
During downtime, both availability and response time will not return data and
events may be generated.
These events will automatically close after the web server is online again.
Scheduling: The web server downtime can be scheduled as follows:

1 Select web server.
2 Select the Downtime Option. Data collection is on. Alarm/Event generation is on.
AlarmRule Action/Notification is off.
3 Frequency is Weekly.
4 Specify the Time and Date as applicable.
5 Add Time Range.
Application: In the above case, BMC ProactiveNet will monitor the Web server for
availability and response time even during the device downtime and generate event/
alarm. However, any event/alarm generated during this period will not be notified.
The advantage of this setup is that, BMC ProactiveNet console will display the
events. Once the device is up again, the events will close. Thus the administrator can
check the system and ensure that the web server is working as expected before the
time to get it online.
However, in case of SLOs defined for availability of this device , data collection can
be switched off to avoid inconsistent SLO compliance calculation.
Adding a downtime schedule

Perform the following procedure to add a downtime schedule.
Scheduling downtime
To add a downtime schedule

1 In the BMC ProactiveNet Administration Console, select Tools => Schedule
Device Downtime.
Alternatively, in the BMC ProactiveNet Operations Console, launch the
Scheduled Down Time Administration window. Choose Options =>

Administration => Data Collection => Scheduled Down Time => Edit.
The Scheduled Downtime Administration window is displayed.
All devices/groups that are currently down are highlighted in Red.
The exact display of time (for each entry in "Devices Already Scheduled for
Down Time" section) may vary depending on the Administration Console
(Windows and Solaris).
2 Choose a Filter.
You can choose to filter the list by Device or by Group.
If you choose to filter by Device, and are monitoring numerous devices, the list
can be quite extensive. You can narrow your device search if Groups have been
set up for your devices.
3 Click Add to open the Scheduler.
Next, you specify the duration of the down time. You have the following options:
one-time setting
daily
weekly
monthly
To specify the duration of the down time

On the Add Device for Scheduled Down Time screen,
1 Select the Device to be scheduled. New users can skip to step 3.
2 Upgrade users only. Select the Downtime Option. These settings govern BMC
ProactiveNet behavior during the scheduled downtime.
Data Collection - Select On or Off to continue collecting data or stop data
collection respectively.
In case data collection is On,
Scheduling downtime
Alarm/Event Generation - Specify if BMC ProactiveNet should generate Events/
Alarms against the data collected.
In case Alarm/Event Generation is On,

Alarm Rule Action/Notification - Specify if BMC ProactiveNet should send
event notification for the events generated during this period.
In case Calculate Baseline is Off,

Calculate Baseline is a scheduled downtime for baseline calculations. During
this period, previously calculated baseline is used. The baseline stays

unaffected by new data. Hourly baseline is not recalculated and previous
values are used. Daily and weekly baseline values are recalculated based on the
hourly baseline. At the time of baseline calculation, BMC ProactiveNet checks
for the pause period corresponding to the current time. During the pause
period, only old values are used. Outside the pause period baseline calculation
is performed using current data.
3 Select the Frequency:

Frequency
Description
One Time Setting
The downtime is scheduled to run once. It is not a recurring setting.
Daily
The downtime is scheduled run daily at the specified time.
Weekly
The downtime is scheduled weekly at the specified day and time.
Monthly
The downtime is scheduled to occur monthly on the specified day and

time.
4 Under Time Pattern field, select the Start and End Date.
Manually specify the dates in mm/dd/yyyy format. Alternatively click on the
calendar link and select from the pop-up calendar.
5 Select the Start Time and End Time. By default, the server time is displayed here.
6 From the list, select the Time Zone. By default, the server time zone is displayed
here. When you change the time zone, the Start Time and End Time change
accordingly. If you change the Time Zone and the corresponding time falls either
in the previous day or the next day, the Start Date changes accordingly.
Note
The Time Zone field displays GMT + Time Zone difference in hours, together
with location.
Scheduling downtime
For example, from 7.1, Time Zone for Indiana-Starke displays GMT 05:00 US/
Indiana-Starke instead of GMT 5:00 as in 7.0.
7 Click Add time Range.

8 Click Yes to confirm.
To change the specified time and date combinations,
Select the entry under Time Range Entry.
Click Remove Time Range.
After specifying the required time and date combination,

9 Click Add.
The system presents various alerts/confirmatory messages. On confirmation,
BMC ProactiveNet adds the schedule to the device.
10 Click Yes to confirm the schedule.
11 Click Ok on the 'Added Successfully' message.
After defining the required Device Downtime,
12 Click Close to exit the screen.
Editing or deleting a downtime schedule

Once a schedule is set, you can view and edit it by following the procedure given below.
To edit or delete a downtime schedule

1 If the Scheduler is closed, open it from Tools menu on the Administration Console.
The Scheduler presents the Devices Scheduled selection. Selection is displayed
in red if opened during its own scheduled time.
2 Highlight the device whose schedule you want to change and click Edit. (If you
want to delete the schedule, click Delete.)
3 Modify the schedule as required, and click OK.
Note
BMC ProactiveNet does not allow editing of multiple schedules at a time.
To delete a schedule, select the schedule from the list and click Delete.
Special notes
Do not perform any operations (monitor creation, flash check, etc) on devices
during their scheduled downtime. This can result in unexpected behavior and
display of invalid data.
If the devices data collection is off, schedule downtime has no affect on the device
data collection.
From Release 6.5, editing multiple schedules is not allowed.

A schedule cannot be edited while it is active (during downtime).
In case of overlapping downtime, data collection resumes after the higher
schedule is completed.
Example: Consider the following schedules:

Weekly: down at 9:00 A.M. - up at 10:30 A.M.
Daily: down at 9:30 A.M. - up at 10:00 A.M.
In this case, data collection resumes only after 10:30 A.M. (though the daily
downtime is from 9:30 A.M. to 10:00 A.M., we have an overlapping weekly

downtime from 9 A.M. to 10:30 A.M.).
In 7.1, Day Light Savings settings have been taken care of. Time settings for the
previously scheduled downtime might get effected.
Changing the default BMC ProactiveNet

Agent TCP control port
The default BMC ProactiveNet Agent TCP control port is 12124. You might need to
change the default TCP control port if it is forbidden by a firewall, or if it is being
used by an existing application. The procedure to change the TCP control port varies
by whether the BMC ProactiveNet Agent is installed on Solaris or Windows.
To change the BMC ProactiveNet Agent control port on Solaris

1 On the BMC ProactiveNet Agent Server computer,open the /usr/pw/custom/conf/
pronet.conf file in a text editor.
2 Scroll to the # Apps properties section and find (assuming the factory defaults
are still listed) the following entry:
pronet.apps.agent.port=12124
Figure 58: Apps properties
3 Change the port to the desired value. For example, from 12124 to 12199.
4 Save the changes and exit the text editor.
5 From a command line, run the following command to restart the BMC
ProactiveNet Agent:
pw agent start
The BMC ProactiveNet Agent stops, then starts again using the revised
pronet.conf file. (Allow several minutes for this action to complete.)
To change the BMC ProactiveNet Agent control port on Windows

1 On the BMC ProactiveNet Agent Server computer, in a text editor, open Program
Files\Proactive\Agent\Custom\conf\pronet.conf.
2 Scroll to the following entry (assuming the factory defaults are still listed):
pronet.apps.agent.port=12124
3 Edit this entry by replacing the port number to the desired value.
For example: change 12124 to 12199.
4 Save the changes and close the text editor.

5 To stop and then re-start BMC ProactiveNet Agent (Windows), navigate to Start
=> Settings => Control Panel.
a Double-click the Services icon to launch the Services screen.

b Locate BMC ProactiveNet Agent on the list of services, highlight, then click
Stop. Click Yes in the warning message that is displayed.
Status for BMC ProactiveNet Agent changes from Started to (blank).
c With BMC ProactiveNet Agent still highlighted, click Start.
Status for BMC ProactiveNet Agent changes from (blank) to Started.
d Close Service and Control Panel windows.
Determining which TCP control ports are

being used
Before you change or assign a new TCP control port, you may want to determine
which TCP control ports are already in use on that server. The procedure for
retrieving this information depends on whether the server is running Solaris or
Windows.
Before you begin

Ensure that all applications on the server that are using TCP control ports are running.
To determine which TCP control ports are in use on a Windows server

1 On a Windows server, access a command line and run the following command:
netstat
On the command screen, active connections are listed, with the active TCP
control ports shown in the Local Address column in the format:

pcuser:control_port. For example, the listing hjohnson:12124 indicates that
system name hjohnson is running the BMC ProactiveNet Agent on the default
TCP control port 12124.
Figure 59: Active connections
2 Check the TCP control port listings to see if the TCP control port entry that you
want to use is not already in use.
To determine if a TCP control port is in use on a Solaris server

Note
This procedure logs you in as root (Super User), which gives you special privileges.
1 On the UNIX server, access the command line interface and run the following
command:
netstat -a|grep LISTEN|grep ". control_port "
No return indicates port 80 is not being used. Repeat for each of the following
ports: 443, 1099, 9149, 12123, 12124, 12125, 12130, and 45000.
These ports are required by the ProactiveNet product and if any are used, you
need to resolve the conflict before continuing. Refer Port Configuration Details
section for more information.
Table 65: Non-configurable (Internal Process) Ports
Control port
Description
BMC Software recommends that the following port configuration be not changed.
1099
pronet.rmi.port
8008
Connector port between Apache Web server and Tomcat servlet engine
8009
Connector port between Apache Web server and Tomcat servlet engine
used for agent and agent controller tunneling
Device application monitors and TCP control ports
Device application monitors and TCP control

ports
The table below shows the TCP Control Ports for each Device Application monitor.
These port numbers appear on the configuration screens when you create a
particular Device Application Monitor. In most cases you use the default port, but
have the ability to change a port when necessary.
Table 66: Device Application Monitor TCP Control Ports
Application
Port
Comment
Port Monitor
[Any]
Configure monitor for any TCP Control Port
SMTP Monitor
25
Well-known Port
DNS Monitor
53
Well-known Port
Web Monitor
80
Well-Known Port (http, www)
443
Well-Known Port (https)
POP3 Monitor
110
Well-known Port
NNTP Monitor
119
Well-known Port
IMAP4 Monitor (IMAP)
143
Well-known Port (reserved)
IMAP4
585
no/SSL - Well-known Port
IMAP4
993
w/SSL - Well-known Port
MS-SQL Server Monitor
1433
Microsoft SQL Server registered port
Oracle 8 Monitor
1521
Oracle (nCube License Manager) registered port
Radius Monitor
1645
Radius (Datametrics) registered port
Informix 7.3 Monitor
2055
Informix registered port
Sybase 11 Monitor
4100
Sybase registered port
NT Disk Space Monitor
12124
Agent registered port
NT Process Info Monitor
12124
NT System Info Monitor
12124
Check Point Firewall Monitor
18184

If BMC ProactiveNet Server and Administration Console are on different sides of the
firewall, the default BMC ProactiveNet setup may be affected. In such cases, special
configuration may be required - Accessing the Administration Console from a

Windows Client through a firewall.
Firewalls and BMC ProactiveNet interfaces

Firewalls block a wide range of TCP ports required by one or more BMC
ProactiveNet UI tools. Usually, this only affects the Administration Console

because it requires a wide range of TCP ports for efficient operation. HTML
interface is usually unaffected by port restrictions because most firewalls allow
incoming connections on port 80, which is needed for HTTP (Web browser) access.
If a firewall uses NAT (Network Address Translation) whose translation is one-to-
one, it causes problems for both the Administration and Operations Console. To
overcome this, certain configuration changes must be made on the server.
If BMC ProactiveNet Server is behind a firewall and the NAT translation is many-
to-one (i.e., the firewall uses IP masquerading), then it is inaccessible to both the
Administration and Operations Consoles.
Dealing with TCP/IP port restrictions

Port restrictions affect the Administration Console because it uses a Java
communications protocol called RMI (Remote Method Invocation). The
Administration Console connects to BMC ProactiveNet Server using one of the
different ways listed below:
The client first tries to contact the server on TCP port 1099. If the connection is
successful, the client and server randomly negotiate a free port between 10000 and
65000, and then reconnect on that port (the connection on port 1099 is closed).
This direct connection is the most efficient form of RMI communication. If a wide
range of ports is not available, this first form cannot be used.
If the first method fails, the client builds a URL to the server's host and port, and
uses an HTTP POST request on that URL, sending the information to the server's
method skeleton as the body of the POST. This method is slower than the direct
TCP connection because the HTTP encapsulation adds over-head to the client's
RMI requests.
Note
This method requires that Apache proxy be activated on BMC ProactiveNet
Server. Refer to instructions on Apache proxy provided at the end of this section.
If the second method also fails, the client builds URLs to the server's HTTP port,
using a CGI script that will forward the posted RMI request to the server. This is
the slowest technique because the CGI wrapper adds considerable overhead in
addition to the HTTP encapsulation.
Methods 2 and 3 are noticeably slower than the direct TCP method of remote
invocation. If the Administration Console operations seem sluggish, the first test you
must try is to attempt a direct connection on port 1099 by running the following
command:
telnet BMC ProactiveNet Server.mycompany.com 1099
If the command times out without connecting, then the communication is likely to be
happening through some form of HTTP tunneling (method 2 or 3). Under special
circumstances, it is possible to avoid the tardiness of methods 2 and 3. This
workaround, if permissible, would require you to launch pw admin from the server
and direct the xwindow output across the firewall to the user's computer. This can
be accomplished by setting the DISPLAY variable to point to the IP address of the
user's console ("setenv DISPLAY 123.45.67.89:0.0") and punching holes through the
firewall for TCP ports 6000-6004 and UDP ports 177 and 32798.
Note
The above-mentioned workaround involves some security risk and may not always
work. For more information, refer Sunsolve Infodoc 18370.
Dealing with NAT

When BMC ProactiveNet Server and a user are on opposite sides of a NATed
firewall, it can create difficulties when trying to access the server, either with the
Administration or Operations Console. These difficulties can be overcome by
making two configuration changes.
You must modify the following two files on BMC ProactiveNet Server when dealing
with a NATed firewall (Ensure that you make a backup of each file before modifying):
In /usr/pw/apache/conf/httpd.conf, modify the ServerName entry to use the host
name of the Proactive system rather than the private address (note that there are
two of these entries). By default, this entry uses the private IP address of BMC
In /usr/pw/pronto/conf/pronet.conf, modify the pronet.rmi.server.hostname
entry to use the host name of BMC ProactiveNet Server. By default, this value is
not assigned and defaults to the private IP address of BMC ProactiveNet Server
(to make this change permanent and to ensure that the change is preserved during
upgrade, copy the entire line to /usr/pw/custom/conf/pronet.conf.
Note
Ensure that you do not insert any extra spaces or tabs within the line or at the
end of line as it can cause problems.
The host name must resolve to the proper address on both sides of the firewall. If
DNS service cannot resolve the name, then an entry must be made in the hosts file
of BMC ProactiveNet Server and every computer that runs the administrator client.
On Solaris, the hosts file is /etc/hosts and on Windows it is \WINNT
\SYSTEM32\drivers\etc\hosts.
After making these changes, restart BMC ProactiveNet Server using the "pw system
start" command.
Activating the APACHE proxy server

When the proxy feature of Apache Web server is activated, it enables the
administrator client to form a virtual RMI connection with BMC ProactiveNet Server
using HTTP POSTs and GETs for RMI. For security, the proxy is deactivated in the
default configuration of BMC ProactiveNet Server.
To activate Apache proxy server

1 Go to cd /usr/pw/apache/conf.
2 Edit httpd.conf file.
3 Locate the group of lines that read.
# Proxy Server directives. Uncomment the following lines to
# enable the proxy server:
#
#
# ProxyRequests On
#
#
#
Order deny,allow
#
Deny from all
#
Allow from .your_domain.com
#
Allow from all
#
#
and uncomment the line "ProxyRequests On" and one or more of the
appropriate access
rules. For Example: "Allow from all" or "Allow from .your_domain.com"
where you
substitute the actual domain name of your network.
# Proxy Server directives. Uncomment the following lines to
# enable the proxy server:
#
ProxyRequests On
#
#
Order deny,allow
#
Deny from all
#
#
Allow from .your_domain.com

Allow from all
Note
Unless BMC ProactiveNet Server is protected by a firewall, do not comment the
'Allow from all' line as shown above. This can make BMC ProactiveNet Server
and your internal network vulnerable to attack from outside.
For minimum security risk, specify a list of specific host and/or network
addresses in this allowed hosts section. For example,
Order deny,
allow Deny from all Allow from 192.16.26.0/24 #specify network address as
(network
addr.)/(subnet mask) Allow from 192.16.27.0/24 Allow from 192.16.31.0/24
Allow from 172.17.52.150
# specify host address as 4 octets
Allow from 172.17.52.151
Allow from 172.17.52.148
Deny from all
Allow from 192.16.26.0/24 #specify network address as (network
addr.)/(subnet mask) Allow from 192.16.27.0/24 Allow from 192.16.31.0/24
Allow from 172.17.52.150
# specify host address as 4 octets
Allow from 172.17.52.151
Allow from 172.17.52.148
Admin tunnel limitations

Using HTTP Tunneling as the connection type has the following limitations:
Admin tunnel does not work if Apache HTTP is configured for a port other than 80.
Only the functionality in the Administration => General Administration tab is
available. All other functionality is disabled.
Fine tuning BMC ProactiveNet system

components
Various JRE settings for BMC ProactiveNet Server components and BMC
ProactiveNet Agent can be set and used for fine tuning various aspects of the JRE.
These settings are present in various configuration files corresponding to each
component and can be edited to suit a particular environment. Each link below
contains more details for each component and agent.
Important information for all configuration files

The configuration files are located in the installDirectory /pw/pronto/conf directory
on Solaris computers. They are located in the installDirectory \pronto\conf directory
on Windows computers.
WARNING
The settings present in the configuration files in these directories must never be
modified directly, instead the required settings from these files should be copied to
the custom configuration directory installDirectory /pw/custom/conf directory on
Solaris computers and installDirectory \custom\conf directory on Windows
computers into an identically named file and then edited.
Only settings in the Variable section present at the top of each configuration file may
be edited. Settings in the Fixed section should never be edited and if edited will be
ignored.
Note
To modify any part of the variable section, the whole variable section of the conf file
need to be copied over to pw\custom\conf directory & modified.
BMC ProactiveNet Server - Solaris edition

The following table shows which BMC ProactiveNet Server components are
supported by which configuration files:
Component
Configuration file name
Jserver
pnjserver.conf
Agent controller
pnagent_cntl.conf
Rate
pnrate.conf
Admin
pnadmin.conf
Local agent
pnagent.conf
Common settings
Following are the common settings for the BMC ProactiveNet Server Solaris
Edition, the BMC ProactiveNet Agent UNIX Edition, and the ProactiveAdmin
Solaris Edition:
Table 67: Common settings for Solaris edition

Setting
Explanation
Minheap
This is the initial size of memory allocation pool required for the component to function.
MaxHeap
This is the maximum size of memory allocation pool that a component can use. This is not
applicable for local agent on Solaris Edition, instead use LOCMaxHeap.
Specific settings
Following are the specific settings for the Local BMC ProactiveNet Agent Solaris
Edition:
Table 68: Specific settings for local agent
Setting
Default Values
Explanation
LOCMaxHeap
512m
This is the maximum size of memory allocation pool for Solaris local
agent. This setting is ignored for remote Unix agents. Default size for
remote Unix agent is 256m.
BMC ProactiveNet Server Windows edition

In order to maintain the consistency of file between Windows and Solaris, existing
Windows files have been changed. The table below lists old and new files:
Table 69: BMC ProactiveNet Configuration files
Old configuration file (Earlier version)
New configuration file (beginning in version 7.1)
pnadmin.txt
pnadmin.conf
pnagent.txt
pnagent.conf
pnagentcntl.txt
pnagentcntl.conf
pnapache.txt
pnhttpd.conf
pndbsrv.txt
pndbsrv.conf
pnjboss.txt
pnservices.conf
pnjserver.txt
pnjserver.conf
pnrate.txt
pnrate.conf
pntomcat.txt
pnjservlets.conf
Note
In earlier version these files were available in pronto/bin folder, from 7.1 onwards
these new files will be available in pronto/conf. If you upgrade to 7.1 version .txt
files will be deleted from pronto/bin folder and will be added as .conf files in pronto/
conf folders.
Common settings
Following are the common settings for the BMC ProactiveNet Server Windows
Edition and ProactiveAdmin Windows Edition:
Table 70: Common settings for Windows edition
Setting
Default Values
Explanation
Minheap
16 MB
This is the initial size of memory required.
MaxHeap
256 BM
This is the maximum amount of memory that can be used.
BMC ProactiveNet Agent Windows edition

Following are the specific settings for the BMC ProactiveNet Agent Windows Edition:
Table 71: Specific JRE settings for Local Agent
Setting
Default Values
Explanation
LOCMaxHeap
512m
This is the maximum size of memory allocation pool for windows local
agent. This setting is ignored for remote windows agents. Default size for
remote Windows agent is 256m.
10
Managing users
Overview
BMC ProactiveNet supports a hierarchical classification scheme that defines the
relationships among permissions that are assigned to user groups, which, in turn,
are assigned roles. All of these elements are contained in user definitions.
Figure 60: Relationships among users, user groups, roles and permissions
You can create new users, user groups, and roles. You cannot, however, create new
permissions. You can only select from a predefined list of existing permissions.
Chapter 10 Managing users
493

BMC ProactiveNet provides default user groups and roles that can be used to control
access to functionality in the Operations Console and the Administration Console.
Table 72 on page 494 describes the default user groups and roles provided in BMC
ProactiveNet.
Table 72: User Groups and roles
Users
User Groups
Roles
admin
Full Access
Full Access
ops
Operators
Event Operator, Data Collection Operator
user
Supervisors
Event Supervisor, Data Collection Supervisor
slm
Service Administrators
ServiceAdministrator
event_admin
Event Administrators
Event Administrator, Data Collection Administrator
Read Only
Read Only
Service Manager
Service Manager Senior
Service Operator
Service Operator Senior
WARNING
Ensure that there is another admin user in the system before deleting the admin user
or the related objects (user group/role).
For more information on the permissions that are assigned to each role and user
group, see the BMC ProactiveNet Upgrade Guide.
Users
You can add users from the BMC ProactiveNet Administration console and associate
them to a user group. You must associate at least one user group to create a user. The
list of available user groups are listed in the User Groups pane. You can also edit and
delete users.
The User folder maintains user accounts, letting you identify who has access to the
BMC ProactiveNet system.
The following operations are available:
Users
Add User
Edit User
Delete User
The user activity on BMC ProactiveNet is available in the access logs which are
available under:
usr/pronto/logs/access.log
Adding or editing users

Use the Administration Console to create new user accounts for BMC ProactiveNet
or edit properties for existing user accounts.
To add a new user

1 In the Administration Console, go to Administration => General
Administration.
2 Select the User folder, right-click, and choose Add User.
3 In the User dialog box, enter the following information:
Table 73: Properties for adding a user account
Item
Description
User Name
the name of the user.
Display Name
the name that is displayed when the user logs on to the Operations
Console.
Password
a password to be used with the user name.

The password should be at least 6 characters in length and should
contain at least one letter and one number.
Re-enter Password
password verification
Email Address
the recipients e-mail address
Force Change Password
allow users to change the password the first time they log on to the system
Disable User
disable the user account
Password will expire in x days
the number of days after which the password of the user account will
expire
The default is 60 days.
495
Users
4 Under User Groups, select the user groups that you want this account to belong
to.
5 Click Add.
A confirmation message is displayed stating that the user account has been
successfully created.
To edit information for an existing user

1 In the Administration Console, go to Administration => General
Administration.
2 Expand the User folder and select a user.
3 Right-click on the user name and choose Edit User.
4 In the User dialog box, change any of the following information:
Table 74: Properties for editing a user account
Item
Description / Task
User Name
the name of the user whose account you are changing
Display Name
the name that is displayed when the user logs in to the Operations
Console
Password
password to be used with the logon name

The password should be at least 6 characters in length and should
contain at least one letter and one number.
Re-enter Password
password
Email Address
the recipients e-mail address.
Last Login
the date and time that the user last logged on to BMC ProactiveNet
Force Change Password
allow users to change the password the first time they log on to the
system.
Disable User
disable the user account
Password will expire in x days
the number of days after which the password of the user account will
expire
The default is 60 days.
5 Under User Groups, change the user groups that this account is associated with.
6 Click Finish.
Users
A confirmation message is displayed stating that the user account has been
successfully changed.
The following default user names and passwords are used in BMC ProactiveNet:
Administrator: admin/admin
Service Manager: slm/slm

Event Administrator: event_admin/event_admin
Operator: ops/ops
Supervisor: user/user
For security reasons, the administrator should change the password for these
accounts after the initial log on to BMC ProactiveNet.
Note
By default, no user account is created for Read Only groups.
Where to go from here

You can add, edit, and delete user groups from the User dialog box by using the
New, Edit, and Delete buttons. For details, see Adding or editing user groups on
page 498 .
Associating user(s) to user groups

Perform the following procedure to associate users to user groups.
To associate user(s) to user groups

1 Select the user group from the Available User Groups list in the User Groups pane.
2 Click New to create a user group. For more information on adding user groups,
see User Groups on page 498.
Deleting users
Perform the following procedure to delete a user account.
497
User Groups
To delete an existing BMC ProactiveNet User account

1 In the Administration Console and expand the User folder.
2 Select and right-click the user and click Delete.
WARNING
Impact of deleting a user is that, any event rules or reports created by the deleted
user will display None as owner of the object.
User Groups
User groups are groups of users that have a specified set of roles and permissions
assigned to them. You must associate at least one role to create a user group.
Default user groups defined in BMC ProactiveNet are Full Access, Operators,
Supervisors, Service Administrators, Event Administrators, and Read Only. For
more information about these user groups and what access they control, see Default
users, user groups and roles on page 494.
Adding or editing user groups

Perform the following procedure to add or edit a user group.
To create or edit user group(s)

1 In the BMC ProactiveNet Administation Console, expand Advanced Options.
2 Right-click on User Group and click Add User Group or select the User Group,
right-click and select Edit User Group.
3 In the Add/Edit User Group screen, enter/edit the Name of the user group.
4 In the Roles/Users tab select the available roles for the user or click New to create
a new role. For more information on creating roles, see Roles and Permissions on
page 500.
Note
You can add, edit and delete roles from the Roles pane in the Add User Group
screen.
User Groups
5 The Views tab, permits you to either allow all views or selected views.
6 The Groups tab, provides you access to all or selected groups defined in the
system.
7 The SLOs tab provides access to all or selected SLOs.
8 The Diagnostics tab provides access to all or selected Detailed Diagnostic
commands and execute them.
9 The Reports tab provides access to all or selected reports.
10 The Folders tab provides access to all or selected event/component folders.
11 Click Finish/OK for adding/editing the user groups.
Note
The SLOs, Diagnostics and Reports tab are disabled by default. To enable the
tabs, you should select the appropriate Roles.
Managing the objects of the User Group are dependent on the role attached to
the user group.
Deleting user groups

Perform the following procedure to delete a user group.
To delete user group(s)

1 Open the Administration Console, expand Advanced Options and User Group
folder.
2 Select and right-click the User Group and click Delete.
Note
If a user is attached to only one user group, you cannot delete that user group
until you disassociate the user group from the user.
499

The availability of various BMC ProactiveNet features for a user depends on the
roles and permissions defined to that user. The roles attached to the user group gives
the permission to have access to the objects in the User Group. The predefined roles
are displayed in the available list box of the roles/permission tab in the User Group
screen.
The actions on permissions are:
view (read-only access)
edit (create, edit and delete)
edit only (only edit permissions)
The permissions are categorized based on usability such as Events, Product

Administration, SLOs, Reports, Graphs and so on.
Note
The default event list does not display events based on permissions of devices. It
displays all events based on the permissions of event collectors.
There are filters available in the Roles screen which will ease the process of selecting
permissions. The filter are on Action and Category. For example, if you want a user
to be able to only edit graphs, you can set the action to View and select the
Graphs category.
You can assign roles and permissions to a user from the User Group screen.
Defining or editing roles and permissions

Perform the following procedure to define or edit roles and permissions.
To define or edit roles and permissions

1 In the Administration Console, expand Advanced Options.
2 Right-click on Role and select Add Role or expand Role, select the role, right-click
and select Edit Role.
3 In the Roles and Permissions screen, enter or edit the name for Roles.
4 Select the filters here if required.
5 Click Finish/OK. A confirmation message is displayed on successful creation or

after successfully editing the role.
6 Add the new user role to the following .mrl files in the Knowledge Base of the
cell.
ibrsd_collectors.mrl
pom_activeevents_collectors.mrl
pom_byuser_collectors.mrl
pom_intelligentevents_collectors.mrl
For more details about .mrl files, see the BMC Knowledge Base Development
Reference Guide.
7 After you add the custom role to the .mrl files, compile and reload the cell by
opening a command prompt and entering the following commands:
mccomp -n cellName
mcontrol -n cellName reload kb

8 Log on to the BMC ProactiveNet Operations Console by using a user account
from the group to which you added the custom role.
Note
You can also define roles and permissions by clicking New from the User Group
screen.
Deleting roles and permissions

Perform the following procedure to delete roles and permissions.
To delete roles and permissions

1 In the Administration Console, expand Advanced Options.
2 Expand Role, select the role, right-click and select Delete
Note
If a user group is attached to only one role, you cannot delete that role until you
disassociate the role from the user group.
501
Configuring the system for external

authentication
Both LDAP authentication over SSL and Windows Active Directory are supported
for centralized user authentication. Both server certificate and client certificate
authentication are supported.
To enable secure LDAP authentication and LDAP queries, set the property
(com.bmc.sms.ixs.enable.ldap.login) in the ias.properties file to True. This enables
server certificate authentication and encrypted data communication with the LDAP
server and BMC ProactiveNet login modules.
To authenticate external users for LDAP server

1 Access the /pw/pronto/conf folder.
2 Edit the ias.properties file, update the following entry to TRUE and save the
file.com.bmc.sms.ixs.enable.ldap.login=true. This will enable you to log into
LDAP if you are a LDAP user.
Tip
To avoid overwriting the parameter values of a .properties file, do not copy any
backup or reserved file with the .properties extension into the same ../conf folder
as the .properties file or files you are accessing. The system reads the .properties
files randomly and can overwrite the current values of duplicate parameters with
older values. Instead, store any backup or reserved files in a separate directory.
3 Open the ldap_configuration.xml file using a text editor.
4 Configure a LDAP server host by adding the following lines for example, before
the </ldapList> tag.
<ldap alias="sun-ldap">
<host>LDAP_SERVER_HOST</host>
<port>389</port>
<version>3</version>
<baseDN>dc=bmc,dc=com</baseDN>
<connectionUserName>uid=abc,ou=Dev,ou=Groups,dc=bmc,dc=com</
connectionUserName>
<connectionPassword encrypted="true">AtrRpWDUoaMnIw5w52M4m2tQ==</
connectionPassword>
<userIdAttribute>uid</userIdAttribute>
<useSSL>false</useSSL>
<groupMemberAttribute>uniqueMember</groupMemberAttribute>
<userSearchFilter>(objectClass=inetOrgPerson)</userSearchFilter>
<groupSearchFilter>(objectClass=groupOfUniqueNames)</
groupSearchFilter>
</ldap>
5 Save the ldap_configuration.xml file.
6 Open the ldap_ppm_group_mapping .xml file using a text editor and create a
map between LDAP groups and BMC ProactiveNet Performance Management
(PPM) groups. For example, if you have a LDAP group called MyLdapGroup and
you need to map it against a PPM group called "Full Access" then the
ldap_ppm_group_mappings.xml file should have an entry for example, <entry
key="MyLdapGroup">Full Access</entry>.
7 Enter the comma separated list of LDAP groups that you need to authenticate the
user against in the ias.properties file. The property used to store this value is
com.bmc.sms.ixs.search.ldap.group in the ias.properties file. For example, if you
have LdapGroup1, LdapGroup2, LdapGroup3, LdapGroup4 groups configured
on LDAP and you want only the user "username" to be validated against
LdapGroup1 and LdapGroup2 then the ias.properties file should have the entry
for example, com.bmc.sms.ixs.search.ldap.group=LdapGroup1,LdapGroup2
8 Check whether the property com.bmc.sms.ixs.default.group.present.check is set
to false in the ias.properties file. By default this property is set to false. If this
property is set to true, you must create a separate group for the corresponding
LDAP group in the PPM environment. For example, if the value of this property
is set to true, you must use the Administration Console to create a new group
called MyLdapGroup for successful authentication of the users belonging to the
group MyLdapGroup.
9 Restart the jserver (in BMC ProactiveNet Server, either restart the jserver or the
BMC ProactiveNet Server).
10 Log in as external user from both Administration Console as well as the
Operations Console.
To authenticate external users for LDAP server with SSL

Note
The LDAP server should be configured with User Groups and Users. LDAP
authentication should be SSL that is, SSL Server certificate must be applied to the the
LDAP server.
1 Access the /pw/pronto/conf folder.
file.com.bmc.sms.ixs.enable.ldap.login=true. This will enable you to login to
LDAP if you are a LDAP user.
4 Configure the LDAP server host by adding the following lines for example, before
the </ldapList> tag.
port = LDAP SSL port
UseSSL =true
503
<ldap alias="sun-ldap">
<host>LDAP_SERVER_HOST</host>
<port>636</port>
<baseDN>dc=bmc,dc=com</baseDN>
<connectionUserName>uid=abc,ou=Dev,ou=Groups*,*dc=bmc,dc=com
</connectionUserName>
<connectionPassword encrypted="false">password</connectionPassword>
<userIdAttribute>uid</userIdAttribute>
<useSSL>true</useSSL>
<groupMemberAttribute>uniqueMember</groupMemberAttribute>
<userSearchFilter>(objectClass=inetOrgPerson)</userSearchFilter>
<groupSearchFilter>(objectClass=groupOfUniqueNames)</
groupSearchFilter>
</ldap>

6 Open the ldap_ppm_group_mapping .xml file using a text editor, and create the
map between LDAP groups and BMC ProactiveNet groups. For example, if you
have a LDAP group called MyLdapGroup and you need to map it against a PPM
group called "Full Access" then the ldap_ppm_group_mappings.xml file should
have an entry like <entry key="MyLdapGroup">Full Access</entry>.
7 Enter the comma separated list of LDAP groups that you need to authenticate the
user against in the ias.properties file. The property used to store this value is
com.bmc.sms.ixs.search.ldap.group in the ias.properties file. For example, if you
have LdapGroup1, LdapGroup2, LdapGroup3, LdapGroup4 groups configured
on LDAP and out of these you want only the user "username" to be validated
against LdapGroup1 and LdapGroup2 then the ias.properties file should have the
entry like com.bmc.sms.ixs.search.ldap.group=LdapGroup1,LdapGroup2
8 Check whether the property com.bmc.sms.ixs.default.group.present.check is set
to false in ias.properties file. By default this property is set to false. If this
LDAP group in the PPM environment. For example, if the value of this property
is set to true, you must use the Administration Console to create a new group
called MyLdapGroup for successful authentication of the users belonging to the
group MyLdapGroup.
9 Copy the SSL certificate to any local folder.
10 The SSL certificate should be imported into the jserver keystore pnserver.ks
under /install_directory/pw/pronto/conf.
11 Use the command keytool -import [-trustcacerts] [-alias <alias>] [-file <cert_file>]
[-keystore <keystore>] [-storepass <storepass>] For example, filename =
ldapcert.cer keytool -import -trustcacerts -alias pnetv2 -file ldapcert.cer -keystore
"e:\Program Files\ProactiveNet\pw\pronto\conf\pnserver.ks" -storepass
get2net
12 Restart the jserver (in the case of BMC ProactiveNet Server, either restart the
jserver or the BMC ProactiveNet Server).
13 Log in as external user from both Administration Console as well as the
Operations Console.
To authenticate external users using Windows Active Directory

1 Access the \pw\pronto\conf folder.
file.com.bmc.sms.ixs.enable.ldap.login=true.
Tip
To avoid overwriting the parameter values of a .properties file, do not copy any
backup or reserved file with the .properties extension into the same ../conf folder
as the .properties file or files you are accessing. The system reads the .properties
files randomly and can overwrite the current values of duplicate parameters with
older values. Instead, store any backup or reserved files in a separate directory.
4 Configure a server host by adding the following lines, for example, before the </
ldapList> tag.
<ldap alias="ABCDOMAIN">
<host>ABCdomain.bmc.com</host>
<port>389</port>
<baseDN>DC=ABCdomain,DC=bmc,DC=com</baseDN>
<connectionUserName>user1@ABCdomain.bmc.com</connectionUserName>
<connectionPassword encrypted="false">xyz123</connectionPassword>
<userIdAttribute>sAMAccountName</userIdAttribute>
<useSSL>false</useSSL>
<groupMemberAttribute>member</groupMemberAttribute>
<memberOfAttribute>memberOf</memberOfAttribute>
<userSearchFilter>(objectClass=organizationalPerson)</userSearchFilter>
<groupSearchFilter/>
</ldap>

6 Open the ldap_ppm_group_mapping .xml file using a text editor and create a
map between the Windows Active Directory domain group and ProactiveNet
Server.
For example, the sample code above shows a Windows domain group called
ITgroup. To map ITgroup to a ProactiveNet group called Full Access add the
following entry to the ldap_ppm_group_mappings.xml file:
<entry key="ITgroup">Full Access</entry>
505
Note
If there are multiple Windows domain groups, than add a new line entry in the
ldap_ppm_group_mapping.xml file for each domain group.
7 Save the ldap_ppm_group_mapping.xml file.
8 Open the ias.properties file in a text editor and set the value of the
com.bmc.sms.ixs.search.ldap.group property to the name of the Windows
domain group.
For example: com.bmc.sms.ixs.search.ldap.group=ITgroupCheck
Separate multiple Windows domain groups with commas.
For example: com.bmc.sms.ixs.search.ldap.group=ITgroup,DomainGroup2
9 In the ias.properties file, verify whether the
com.bmc.sms.ixs.default.group.present.check property is set to false. If this
Windows domain group.
For example, if the value of this property is set to true, you would use the
Adminstration console to create a new group called ITgroup to successfully
authenticate users belonging to the ITgroup group.
10 Restart either the jserver or the BMC ProactiveNet Server.
11 Log in as external user from both the Administration Console and the Operations
Console.
11
Deploying multiple ProactiveNet
Servers
This chapter describes how to deploy and configure multiple BMC ProacativeNet
Servers.
Multiple ProactiveNet Server deployment

overview
You can configure a central BMC ProactiveNet Server to monitor events from
multiple BMC ProactiveNet Servers for centralized event administration, and to
expand the abilities of a single event processing BMC ProactiveNet Server. You can
also use central BMC ProactiveNet Servers to structure event and data collection
around a distributed hierarchy based on geography, business operation, or other
dispersed functions for your organization.
In a central BMC ProactiveNet Server, you can aggregate the following types of events:
abnormality events and early warning events that are automatically detected
from statistically significant abnormal trends
monitoring events that are generated from BMC ProactiveNet monitors or third-
party adapters that retrieve performance data from other monitoring solutions
third-party events that are sent by other monitoring applications
Through a central ProactiveNet Server, you can perform the following activities on
events from other servers:
view event details
execute event operations, such as taking ownership of events or assigning events
export events
Chapter 11 Deploying multiple ProactiveNet Servers 507
copy events
launch the ProactiveNet Server from where an event originated
view BladeLogic device history if BMC ProactiveNet is integrated with BladeLogic
In the Event View, you can also launch Detail Diagnostics, Related Events, and View
Remote Action Results from the central BMC ProactiveNet Server, when the relevant
icon is displayed in the Message column of the event.
A central ProactiveNet Server does not require a separate installation, but it does
require configuration. On the originating ProactiveNet Servers that supply data (also
called child ProactiveNet Servers), you must configure the propagation policies to
propagate events to the central ProactiveNet Server. On the central ProactiveNet
Server, you must add details about the supplying servers.
This section provides procedures for completing the following tasks:
Configuring an originating ProactiveNet Server on page 508
Configuring a central ProactiveNet Server on page 511
To configure ProactiveNet Servers for multiple deployment, verify the following

prerequisites:
Ensure that all ProactiveNet Servers are the same version, BMC ProactiveNet 8.0
or later.
Confirm the server port and protocol of the originating ProactiveNet Servers. The
default server port is 80 and the default protocol is HTTP.
When working behind a firewall, open the server ports for the central and
originating ProactiveNet Servers.
Configuring an originating ProactiveNet Server

Use the following procedure to configure the propagation policies on an originating
ProactiveNet Server to forward events to the central ProactiveNet Server. For details
about the propagation policy, see the BMC ProactiveNet Administrator Guide .
To configure an originating ProactiveNet Server to forward events to the

central ProactiveNet Server
Repeat this procedure on every originating ProactiveNet Server in your environment.
1 On the originating ProactiveNet Server, add details for the central ProactiveNet
Server to the mcell.dir file:
a On the originating ProactiveNet Server, open the mcell.dir file, located in the
installDirectory \pw\server\etc directory.
b At the end of the file, add a line with the following cell server information for
the central ProactiveNet Server, then save and close the file:
cell centralCellName
mc cellHostName : cellPort
where
centralCellName is the name of the central ProactiveNet Server cell
cellHostName is the name of the central ProactiveNet Server host
cellPort is the cell port
For example:
cell pncell_central
mc central.bmc.com:1828
c To reload the mcell.dir file with the updated information, open a command
prompt and run the following command:
mcontrol -n childCellName reload dir
where
childCellName is the name of the originating ProactiveNet Server cell.
2 Create a rule (mrl) file to propagate MC_CELL_ACTION_RESULT events:
Note
Refer to Knowledge Base Development Reference Guide for details about rule files.
a Create a text file with the following rule:
# ACTION_RESULTS
propagate cell_action_results_event:
MC_CELL_ACTION_RESULT
to <'centralCellName'>
END
where
centralCellName is the name of the central ProactiveNet Server cell.
b Save the file with an mrl extension in the installDirectory \MCELL_HOME\

server\etc\ childCellName \kb\rules directory.
c Add the file name (without the mrl extension) to the.load file in the same
directory.
d Compile the cell by opening a command prompt and running the following
command:
mccomp -n childCellName
e Restart the cell by opening a command prompt and running the following
commands:
mkill -n childCellName
and then
mcell -n childCellName
Alternatively, instead of restarting the cell, you can reload the Knowledge Base
of the cell by running the following command:
mcontrol -n childCellName reload kb
3 Open the Administration Console and in the Administration View, click the
Event Management Policies tab.
4 Expand MyProduction => childCellName => By Policy Type => Propagation
Policy =>All_Events.
5 Click to add a policy or to edit an existing policy.
6 In the Propagation Policy Details tab, ensure the following settings:
Select the Enabled check box to enable the event management policy.
In the Policy Activation Timeframes section, select Always Active to make the
event management policy active continuously.
In the Propagate to all of list, select the cell server for the central ProactiveNet
Server.
7 Click OK to save the changes.
Configuring a central ProactiveNet Server

Use the following procedure to configure a central ProactiveNet Server to collect
data from originating ProactiveNet Servers.
To configure a central ProactiveNet Server to collect data

1 On a server designated as the central ProactiveNet Server, open the mcell.dir file,
located in the installDirectory \pw\server\etc directory.
2 At the end of the file, add a line for each originating ProactiveNet Server with the
following cell server information, then save and close the file:
cell childCellName
mc cellHostName : cellPort
where
childCellName is the name of the originating ProactiveNet Server cell
cellHostName is the name of the originating ProactiveNet Server host
cellPort is the cell port
For example:
cell pncell_01
mc 01_server.bmc.com:1828
3 To reload the mcell.dir file with the updated information, open a command
prompt and run the following command:
mcontrol -n centralCellName reload dir
where
centralCellName is the name of the central ProactiveNet Server cell.
4 On the central ProactiveNet Server, open the serverlist.xml file, located in the
installDirectory \pw\prono\conf directory.
5 For each originating ProactiveNet Server, type values under the
<OriginatingProactiveNetServer> element.
The information for <cellname> and <hostname_or_ipaddress> are the same
as those entered in step 2.

For example:
<OriginatingProactiveNetServer>
<cellname>pncell_01_server</cellname>
<hostname_or_ipaddress>01_server_bmc.com
</hostname_or_ipaddress>
<serverport></serverport>
<protocol></protocol>
</OriginatingProactiveNetServer>
where
pncell_01_server is the name of the originating ProactiveNet Server cell
01_server.bmc.com is the name of the originating ProactiveNet Server host
If you use the default server port, 80 (for HTTP), you can leave this element
blank; otherwise, type the server port.
If you use the default protocol, HTTP, you can leave this element blank;
otherwise, type the server port.
6 Save the serverlist.xml file.

7 For device aliases that were manually added to originating ProactiveNet Servers,
manually add the device aliases to the central ProactiveNet Server, too, to ensure
that events are associated with the appropriate devices.
Refer to BMC Knowledge Base Development Reference Guide for details about
device alias associations.
8 In the Event View of the central ProactiveNet Server, click the Refresh icon (not
the browser Refresh), or wait for the screen to refresh automatically.
Events from the originating ProactiveNet Servers are displayed in the central
Note
When an originating BMC ProactiveNet Server receives events in a blackout
period, the events are not propagated to the central BMC ProactiveNet Server.
12
Setting up web transactions
This chapter presents the following topics:
Web Transaction capture

BMC ProactiveNet Web Capture Tool helps you monitor Web site and application
availability in real-time from an end-user's perspective. It emulates end-user
business processes and helps report response times and availability.
A store that offers its users the convenience to shop online will definitely want to be
aware of customer satisfaction at its Web site. The store's Web site provider may
want to measure the performance of a Web transaction, such as a series of steps, that
a typical user might traverse while navigating through the store's Web site.
By measuring network response time and total user response time of these steps at
regular intervals, the Web site provider can take proactive measures to improve
degrading response times and maintain customer satisfaction.
This is where the Web Capture Tool is useful.
The Web Transaction Capture tool can be used to capture the series of steps that
form a transaction on a Web site. This transaction can be saved to a file, to be used by
the Web Transaction Monitor to provide important information such as availability
of the site, total response time for the transactions, Sum of the connect time for each
URL of the transaction and the like.
The most important feature of the Web Transaction capture tool is that it records the
series of URLs involved in a transaction as a single Transaction File. Web
Transaction Monitor then runs this recorded Web transaction file and collects data
for the series of URLs in the file instead of collecting data for a single URL (Web
Monitor).
The recorded transaction file can be configured to include subtransactions as well.
For more information on subtransactions, refer Subtransaction section.
For performance data collected, refer Web Transaction Monitor under User
Transaction Monitors in the BMC ProactiveNet Monitor Guide.
Chapter 12 Setting up web transactions 513
System requirements
System requirements
Operating System: Windows NT 4.0 (with Service Pack 6a), Windows 2000/XP/
2003
.Net version: 2.0 (Installed automatically with remote BMC ProactiveNet
Administration Console installation)
.Net version: 3.0 (Installed automatically with local BMC ProactiveNet Server and
Administration Console installation)
Browser: Internet Explorer 6.0 and 7.0.
Note
Supported for 32-bit and 64-bit processors.
Any other version of .net already installed on the system will not get
uninstalled since other applications might be using it.
Fresh installation of BMC ProactiveNet 7.6 server on Windows 2000 does not
support this feature on local BMC ProactiveNet Administration Console

installation.
Upgrading BMC ProactiveNet server to version 7.6 on Windows 2000
supports this feature on local BMC ProactiveNet Administration Console

installation.
How and where do I begin?

To ensure your Web Transaction Monitors are complete and successfully collecting
data, follow the steps given below to create the transaction file correctly:
1 Plan the Web Transaction
Use a text editor (or pen and paper) to plan your Web transaction.
2 Record the Web Transaction
Use the Web Transaction Capture Tool to record your transaction and create a
Web Transaction File.
You may include Subtransactions in the transaction file and store authentication
information. To learn to deal with pop-up windows that may appear while you
are recording, refer Pop-up Windows topic.
System requirements
3 Playback and validate the Web Transaction File

Use the Playback option in the Web Capture tool to verify that the transaction just
recorded will replay successfully. This step is recommended, but is optional.
Use the Validate option to verify whether a Web Transaction Monitor can be
created successfully using the Web Transaction file you saved.
4 Export the Transaction File
Use the export tool to transfer your transaction file to BMC ProactiveNet Server.
a Playback and validate the Web Transaction File
Use the Playback option in the Web Capture tool to verify that the transaction just
recorded will replay successfully. This step is recommended, but is optional.
5 Configure a Web Transaction Monitor
Use the Administration Console to create the Transaction Monitor.
Note
Certain limitations exist while recording and playing back Web transactions. To
learn more about them, refer Web Transaction Monitor Troubleshooting section.
Backward compatibility
The table below indicates the various features of the Web Capture Tool that are
supported for Transaction files created using earlier versions of BMC ProactiveNet:
Table 75: Backward compatibility of the web capture tool in BMC ProactiveNet 7.0 & above
Feature
Whether Supported
Alternative, if feature not supported
Open
No
None
Edit
Yes (only from the menu bar

option in the Administration
Console)
You cannot make changes to an

old transaction file using the Web
Capture tool
Playback
No
None
Validate
Yes
Creation of Monitor using the old

transaction file
Yes
Best Practices
If you are using a Web transaction file created in a version prior to BMC
ProactiveNet 7.0, it is recommended that you record and save the same transaction
in a different file using the new Web Capture tool. However, if you want to use an
old transaction file, the combination of BMC ProactiveNet Agent 6.5 and BMC
ProactiveNet Server 7.0 and above, is recommended.
Web transaction capture screen field

descriptions
This section describes options in the Web transaction capture tool.
Menu bar options

The following menu bar options are included in the web transaction capture tool.
File
Open - Click this to display the Open BMC ProactiveNet Transaction File
window. From here, select a previously recorded transaction to work with.
Save - Click this to save the transaction file in the installDirectory /pw/pronto/
usr_apps/Webtranx directory. You cannot save transaction files in any other

directory or folder.
Exit - Click this to close and quit the application.
Options
Advanced Settings
The Advanced Settings window enables you to set certain properties to govern the
recording tool.
Session Only Settings
The options that you select here are applicable to only one session of the recording.
Enable Title Match - Select this option to automatically record the title of the Web
pages as Positive Content Match.
Allow Popups - Select this option to allow other pop-up windows and screens
associated with the Web site you are viewing to be displayed while you are
recording the transaction. This does not interfere with the system authentication
pop-up windows that may be displayed.
This feature helps to record a transaction by blocking unwanted pop-up windows
that may appear on a site.
Permanent Settings
The options that you select here are applicable across all sessions.
Debug
Simple Logging - Select this to record basic logging of the navigation steps. Only
sequence of the navigation is saved.
Advanced Logging - Select this to record more detailed information about the
navigation. This info will be useful to debug problem areas in a transaction that
failed.
Record Persistent Cookies - Select this if persistent cookie information has to be
recorded in the transaction file and the same cookie must be used for the playback
of the recorded transaction.
Enable Snoop - Select this to get the snoop output. This info will be useful to
debug problem areas in a transaction that failed.
Edit - Click this to open a previously recorded file and make changes to it.
Test Monitor - Click this to check whether this transaction can be played correctly
from the monitor. This is the same as the Test Monitor button on the menu bar.
Reset - Click this to delete any unsaved transaction information.
Record
Start Recording - Click this to begin recording a new transaction. This option is
disabled when you open a previously recorded transaction.
Stop - Click this to stop recording a transaction.

View Source - Click this to view the HTML source of the Web page you are
viewing. This lets you copy the desired content for Content Match from the
HTML source so that extra line feeds or in-between newline characters are not
copied.
Play
All Steps - Click this to replay all steps of the recorded transaction without
intervention.
Step-by-Step - Click this to replay one step of the recorded transaction at a time.
You must click Next to view the next step in the transaction.
Next - Click this to play the next step in the recorded transaction. This option is
available only when you are viewing a transaction step-by-step.
Help
Help Topics - Click this to view Help topics related to the Web Transaction
Capture tool.
About - Click this to view information about the version of BMC ProactiveNet
installed on the system.
Buttons
The following buttons are included in the Web transaction capture tool.
Web capture section

Open - Click this to open a previously recorded transaction.
Record - Click this to record a new transaction file.
Save - Click this to save the transaction steps to a file.
Stop - Click this to stop recording a transaction.
Test monitor - Click this to test whether the recorded transaction can be played
successfully by the Web Transaction Monitor. Click here to know more about the
validate process.
Edit - Click this to open a previously recorded transaction and make changes to it.
Sub Transactions - Click this to display the Add/Edit Sub Transactions window.
Here you can group several steps of a transaction to form a subtransaction.
Play - Click this to view the recorded transaction.
All Steps - Click this to replay all steps of the recorded transaction without
intervention.
Step by Step - Click this to replay one step of the recorded transaction at a time.
You must click Next to view the next step in the transaction.
Reset - Click this to clear the screen without saving any changes.
Step Info - This section displays information about the steps that are recorded as
a transaction in a tree structure. Step information also displays content match and
title match, if specified. The URLs of the steps recorded are displayed in this
section. Positive content match is displayed with a '+' symbol next to the inserted
content match string and negative content match is displayed with a '-' symbol.
Title match string recorded is displayed with the letter 'T'
Log Info - When you select this tab, two additional tabs 'Debug' and 'Error' are
displayed. Debug tab contains all debug messages and the Error tab lists errors
that occurred during recording.
Update Step Name - By default, the URL of a step in a transaction is considered as
its name. This is displayed in the field next to the Update Step Name button.
Change the step name displayed in the field and click this button to assign the
name to the step.
Content Match - The Content match feature enables the Web Transaction user to
verify that the monitor navigates to the correct web pages during the transaction
playback. Content match can be specified for each step of the transaction file.
During playback, the downloaded page is parsed and the recorded content is
matched with the corresponding page to check the authenticity of the transaction
playback.
Positive - During playback, the downloaded page is checked for the specified
positive match content. If the content is present in the page, then the playback is
considered as successful. If the content is not present, then an error is reported
and availability is set to zero.
Negative - During playback, the downloaded page is checked for the negative
match content. If the content is not present in the page, then the playback is
considered as successful. If the content is present, then an error is reported and
availability is set to zero.
Insert - Click this to insert text as the content match. If the text assigned here is
found in a page on the Web site, then the transaction is considered successful. The
content match text that you assign is displayed in the field next to the Content
Match section.
Note
Go to Record => View Source to copy text for content match.
Delete - Select a content match text and click this to delete it from being a content
match.
Update - Click this to select an already assigned content match text and make
changes to it.
Title Match - Select this option to enable Title Match. Page title can be recorded as
part of the transaction file. As with Positive Content Match, the downloaded page
is checked for the Title during playback. Title match can be used to validate
rendered pages without manually insert content matches.
Ready - Indicates the status of the Web Capture tool.

Recording - Indicates the status of the Web Capture tool.

Before you start using the Web Transaction capture tool, BMC recommends that you
plan out and 'rehearse' the transaction that you want to record using a Web browser.
It is important to plan the transaction you intend to replay before you actually start
recording it since any erroneous mouse clicks or keystrokes will result in an invalid
transaction that may fail when executed by the monitor. This step will also help you
anticipate the actions you want to record, as well as avoid any surprises that might
pop up (literally!) when you are working with and recording live Web sites.
1 Delete cookies and temporary files from your browser.
Before launching your browser, it is critical to delete all cookies that have been set
in your browser and clear all pages that may be stored in cache. Failure to do this
might produce unexpected results, like an incorrect HTML page, when your
transaction is later executed by the monitor.
Note
Internet Explorer on a Windows computer is the preferred platform since this is

the environment supported by the Web Transaction capture tool.
2 Launch a text editor, such as Notepad, or use a pencil and paper to keep track of
your actions.
It is strongly advised that you write down the exact steps you take and the actions
you want to execute as you click through the intended transaction. In reality, most
Web sites are fairly complex and you may be confronted with pop up windows,
log in forms, advertisements, and other such innovative features. In the next topic
'Recording your Transaction', we will discuss these specific issues, but for now it
is important to note your steps and any 'surprises' that might appear.
3 Launch your browser and start your transaction with the first URL.
For this tutorial, we use the bmc.com Web site to record a transaction. As you
click through the site, remember to write these steps on paper or in the text editor.
Your transaction planning sheet would look like this:
Go to http://www.bmc.com
Click Contact Us option in Company menu.
Click BMC ProactiveNet's world wide office.
Stop (close the browser).
Remember - this is the trial run of the transaction. Take time to look at the Web
pages and plan out what you actually want to record.
4 Note the Content Match parameters.
You will most likely want to ensure that the transaction you are about to record
actually returns the content you were expecting. To do this you will use Content
Matching. For this sample transaction, you want to ensure that you have reached
the International Office page. To do so, make a note on your planning sheet to
attach a Positive Content Match for the string ""International Offices"" (step b
below). Alternately, add a note to attach a Negative Content Match for the string
""No listings were found"" (step e below).
Your transaction planning sheet would now look like the following:
BMC ProactiveNet International Offices transaction with content matches: http://
www.bmc.com
Go to Company => Contact Us => International Offices

Positive content match: International Offices
Negative Content match: No listings were found
Stop (close the browser)
Positive Content Match

A positive content match on a page verifies that the specified text string is found
on the page. If that string is not found, the transaction fails.
Negative Content Match
A negative content match flags the transaction as failed if the specified string
appears anywhere on the page.
More on how to specify content matching is explained in the Content Match topic.
5 Plan Sub transactions

You may want to record sub transactions. A transaction can include multiple
subtransactions.
6 Planning step completed
You have now completed the first step of planning the transaction and will now
use your planning sheet to go back and actually record the same steps you just
rehearsed and made notations about.
You will find that the more detailed your planning is, the easier it is to create a
reliable and effective monitor.

Before you actually create a new web transaction, you should plan your transaction
and practice creating a transaction using a Web browser.
For details, see Planning a Web Transaction on page 520.
For details about creating a new Web transaction, see Recording a new Web
Transaction on page 523.
Need for the transaction file

The Web Transaction File is the basis for the Web Transaction Monitor. A Web
Transaction File saves Web browser activities, which the monitor plays back to
record the Web site availability and response time. This file can created using the
Windows Administration Console and exported to BMC ProactiveNet Server as part
of the file creation process. If you set up the Web Transaction Monitor using BMC
ProactiveNet Server as the 'Source IP', then the transaction file, for example,
testfile.tran, must already reside in the following BMC ProactiveNet Server directory:
/usr/pronto/usr_apps/webtranx/testfile.tran
If you select a BMC ProactiveNet Agent (UNIX) as the 'Source IP' when setting up
this monitor, the transaction file you select (currently on BMC ProactiveNet Server)
is automatically copied to the Agent (UNIX) directory:
/usr/pronto/usr_apps/webtranx/testfile.tran
A common configuration is to install BMC ProactiveNet Server inside the Domain
and BMC ProactiveNet Agent (UNIX) outside the Domain. This requires that your
Firewall or Proxy policy enables TCP Control Port 12124 (the default port for BMC
ProactiveNet Server and BMC ProactiveNet Agent communications) to be enabled

for Proactive operations. Setting up your Firewall server and proxy server are your
responsibility, with the only requirement that your proxy server set up does not
require a user name or password.
Launching the Web Transaction Capture tool

You create Web Transaction files using a Windows PC, then export the files to the
BMC ProactiveNet Server for use with Web Transaction Monitors.
To launch the Web Transaction Capture tool

1 From the Tools menu in the Administration Console, select Web Transaction
Capture => Launch Web Capture.
2 In the BMC ProactiveNet Web Capture screen, perform one of the following
actions:
To start recording a series of steps as a transaction, click Record. For details, see
Recording a new Web Transaction on page 523.
To work with a previously recorded transaction, click Open. For details, see
Working with a previously recorded web transaction on page 531.
For a description of each option available in the BMC ProactiveNet Web Capture
screen, see Web transaction capture screen field descriptions on page 516.
Recording a new Web Transaction

Perform the following procedure to record a new web transaction.
To record a new web transaction

1 In the URL field, enter the address of the Web site and click Go.
The static BMC ProactiveNet icon next to the Go button turns dynamic. The
icon returns to its static state to indicate that the navigation to the intended
URL is complete.
Note
Do not click any button or option on the screen when the icon is changing its
status. This may lead to errors.
Figure 61: Web recorder in the record mode
Note
If the Title Match check box in the Recorder is turned on, then title of the Web
pages are automatically recorded as Positive Content Match and the Title
Match is enabled automatically in Content Match Details screen.
2 Enter the starting URL, that is the first step of the transaction, in the URL field. In
this example, we use http://www.bmc.com as the first step.
You can record additional links within the Web site by simply clicking on the
respective links. They will automatically be added to the transaction file.

Figure 62: Recording a transaction
3 Follow the steps you have planned. To continue the trial transaction recording, go
to Solutions => Infrastructure monitoring => User Transaction Recorder.
The Web Recorder window records every page you visit in the Web site. This
info is available to you in the Step Info section.

Figure 63: Step Info
While recording there will always be a slight delay from when you click on a
link and when the next page is actually rendered (more of a delay than usual).
Be sure to wait until the page is completely loaded before clicking on the next
button or link. If you do not wait there is a chance that the step will not be
recorded correctly in the transaction file, which will cause the transaction to
fail. One way to verify that you have correctly recorded each step is to verify
that the step is recorded in the Step Info section after each click.
The Log Info tab is useful when you are trying to troubleshoot a failed
transaction. This tab consists of two more tabs - Debug and Error. The Debug
tab contains all debug messages associated with the transactions and the Error
tab lists errors that occurred during recording.
4 Insert text for Content Match. For example, Infrastructure Availability. The
recommended way to insert a content match is to copy the text from the View
Source feature. For proper content match, the text should be pasted directly from
the HTML source of the URL. Do not copy the text from the page as displayed in
the browser, for there could be extra characters in the HTML source that are
hidden.
Use this feature to monitor changes in the Web content on the Web sites.
Content matches apply to specific pages.
Note
Content Matching may only contain alphanumeric characters

(Internationalization support).
In the Step Info section, select the step for which you want to add a content
match.
Go to Record => View Source.

Copy the content match text and paste it in the Content Match section of the
recorder.
Select Positive or Negative.

Click Insert.
Follow the above steps to insert multiple content match strings for a step.
Figure 64: Insert Content Match
Positive Match: This displays an error if the string is not found on the designated
page. The text strings must appear in the designated URL or frame for the
monitor to report success. The monitor reports success only if *all* strings are found.
If all the multiple strings are found, then the monitor reports success.
Negative Match: This displays an error if the string is found on the designated
page. If the text strings appear in the designated URL or frame, the monitor
reports failure (no response). The monitor reports failure if any one of the strings
is found).
Example:
HTTP 404;The page cannot be found
If any one of the negative content match strings is found, then the monitor reports
failure.
This is the exact string that must be used for defining content matches. Remember
that the monitor is case-sensitive and the string should be entered EXACTLY as it
appears on the HTML source. The reason is that there may be multiple frames in
the Web page, and this option will not display any of the frame source text (it is,
however, useful for identifying the URLs for all frames in the page). Instead, you
should right-click on the frame of interest and select View Source.
The Operations Console lists Web monitor attributes such as Source Agent and
Collect Data.
You can define multiple content matches on a page by repeating this step. Once
the form is open, you can insert content match strings for every steps without
having to open and close the form every time you want to insert a content
matching string. If you make a mistake, such as typing an incorrect string or
inserting it in the wrong place, you can change it by clicking Edit.
Note
The Web Transaction Monitor supports Unicode characters in Web content.

However, it does not support Unicode characters in a 'pop-up' login
Authentication Info.
POP-UP log in: If a logon pop-up (Basic/Digest/NTLM Authentication) window
appears during the transaction, refer Pop-up Windows help topic.
You may also run into more complicated transaction recordings, such as System
Authentication pop-up screens, advertisement windows, and other complex
transactions. For information on working with these, refer Pop-up Windows topic.
5 Click Stop to stop the transaction recording.
The Save Transaction File window is displayed. Specify a name for your
transaction file and click Save. The file is saved with the extension .tran in
installDirectory \agent\pronto\usr_apps\webtranx directory
Once you save a transaction file, you can do either of the following:
Test whether a Web Transaction Monitor can be created using the transaction
file you saved
Play back the saved transaction file
Creating a test monitor

This option helps you to verify whether a Web Transaction Monitor can be created
successfully using the transaction file created. The Test Monitor option is enabled
only when you are working with a previously saved transaction file or immediately
after you save the transaction file.
On clicking Test Monitor, the Validate Transaction window is displayed. This
window seeks proxy setting and security information.
Advanced options - proxy details

Proxy Server - Specify the IP address of the proxy server.
Proxy Port - Specify the port number on which the proxy server is listening.
Proxy User Name - Specify the user name to access the proxy server.
Proxy Password - Specify the password associated with the proxy server user name.
Security
JSSE - Select this option to use JSSE package for HTTP connections.
Cryptix - Select this option to use Cryptix (ice storm) package for HTTP
connections.
Emulate Netscape - Select this option to set Netscape as the user agent in the
HTTP request header.
Full Download - Select this option to download all images in the page.
Timeout (in secs) - Specify the timeout value for the validate process. By default,
the timeout period is 600 seconds.
Validate - Click this to begin testing the transaction file.
The View Logfile button is disabled before the file is validated.

After validation, the result (SUCCESS or FAIL) is displayed on the screen.
Success: Indicates that a monitor can be created using this transaction file to
collect data.
Fail: Indicates that a monitor cannot be created using this transaction file.
Figure 65: Transaction File Validation Result
View Logfile - Click this to view the log file of the played back transaction. This
helps in debugging a failed transaction. The log file will be stored in the logs
folder installDirectory \agent\webrecorder\logs) with the same name as the
Transaction File.
Playing a transaction file created with the Web Transaction

Capture tool
The Play feature is enabled when you are working with a previously saved
transaction file or immediately after you save the transaction file.
This feature enables you to view, playback, and add or edit content match to your
transaction file. You can also change step names using this feature.
The Step by Step and All Steps features are enabled only after you click Play.
1 Click Play.
Steps in the transaction file are displayed in the Playback Details section.
You can either playback the transaction one step at a time (Step by Step) or all
steps continuously without user intervention (All Steps).
2 Click either All Steps or Step by Step, as required.
3 If required, insert or change content match text and update the step name.
4 Click Stop.
Successfully played back transactions with Title match enabled in the Recorder and
Content Match Details screen are displayed in green and without enabling Title
match are displayed in gray color.
Figure 66: Title match playback transactions
Successfully played back transactions are displayed in green and failed transactions
in red. If a step fails, the playback process stops.
Figure 67: Playback transactions
If a step fails, you cannot continue playing back the other steps in the transaction file.
1 A message seeking confirmation to save changes made to the transaction file is
displayed. You can choose to select the same file to save current changes or save
the set of transactions with the new properties as a different file.
Note
Log entries for GUI playback of a transaction are available in the running log
file (installDirectory \agent\webrecorder\logs\WebRecorder.log). However,
the log entries are overwritten after each session.
Authentication
Working with a previously recorded web transaction

When you open a previously recorded transaction file, you can do any of the following:
Test whether a Web Transaction Monitor can be created using the transaction file
Play back the transaction file
Edit the transaction file
Recording another transaction in the same user session

If required, you can record another transaction immediately after you have saved
one. To do this, click Reset on the BMC ProactiveNet Web Recorder window. This
clears the recorder window and displays the default setting of the Web Capture tool.
Click Record and begin recording the second transaction.
If you close the Web Capture tool after saving a transaction file on the local system, a
confirmation message may be displayed, asking you whether you want to export
web transaction files that you have created from the local system to BMC
After you have created the transaction file, you may need to export it to BMC
ProactiveNet Server (if you have created the transaction file on a remote
administration console). To do this, refer Export Web Transaction File topic.
Authentication
This procedure is required to record system authentication pop-up windows that
appear while recording a transaction and is not necessary for logons, which are
presented as form data. In other words, it is not needed when user name and
password fields are part of the Web page.
If a pop-up logon (Basic/Digest/NTLM Authentication) window appears during the
transaction, you must follow the steps given below to ensure that it is recorded.
Open the Web Recorder and enter the first URL.
The Enter Network Password window pops up but notice that there is no new URL
recorded in the Web Recorder window. This pop-up window is not a browser
window. Let us refer to it as a System Authentication pop-up window.
Some additional steps are called for to record such a transaction.
Authentication
How to insert authentication information?

When you click Add Authentication in the Web Transaction Recorder, the Add/Edit
Authentication window is displayed.
Step - Select the step/URL for which you want to add authentication information.
UserName - Specify the user name that is to be used to gain access to the
particular page in the Web site.
Password - Specify the password associated with the user name.

Domain - Specify the domain where the user name and password combination is
to be used.
Authentication Type - Select the type of authentication mechanism supported by
your Web site. You can select Basic, Digest, or NTLM from the list.
Basic authentication
Upon receiving a 401-response header, the client's browser, if it supports basic
authentication, seeks user name and password information to be sent to the server. If
you are using a graphical browser, such as Netscape or Internet Explorer, a window
is displayed where you must specify your user name and password. The information
you type in is sent back to the server. If the user name is in the approved list, and the
password specified is correct, the resource will be returned to the client.
Digest authentication
Digest authentication is implemented by the module mod_auth_digest. There is an
older module, mod_digest, which implemented an older version of the digest
authentication specification, but which will probably not work with latest browsers.
Using digest authentication, your password is never sent across the network in the
clear, but is always transmitted as an MD5 digest of the user's password. In this way,
the password cannot be determined by sniffing network traffic.
NTLM authentication
NTLM is an authentication protocol used in various Microsoft network protocol
implementations and supported by the NTLM Security Support Provider
(NTLMSSP). Originally used for authentication and negotiation of secure DCE/RPC,
NTLM is also used throughout Microsoft's systems as an integrated single sign-on
mechanism.
NTLM employs a challenge-response mechanism for authentication, in which clients
are able to prove their identities without sending a password to the server. It consists
Subtransactions
of three messages, commonly referred to as Type 1 (negotiation), Type 2 (challenge),

and Type 3 (authentication).
The client sends a Type 1 message to the server. This primarily contains a list of
features supported by the client and requested of the server. The server responds
with a Type 2 message. This contains a list of features supported and agreed upon by
the server. Most importantly, however, it contains a challenge generated by the
server. The client replies to the challenge with a Type 3 message. This contains
several pieces of information about the client, including the domain and user name
of the client user. It also contains one or more responses to the Type 2 challenge.
Responses in the Type 3 message are the most critical piece, as they prove to the
server that the client user has knowledge of the account password.
Insert - Click this to save data that you have specified as user logon information.
Delete - Click this to delete saved user logon information.
Update - Click this to save changes made to the existing user logon information.
Close - Click this to close and exit from the window.
Authentication information that you save is not displayed in the Step Info section.
However, if you want to view the authentication information that you have added
for a step, open the Add/Edit Authentication window.
Subtransactions
The Web Transaction Capture tool enables you to group several transactional steps
under one transaction. These transactional steps may be referred to as
'Subtransactions'.
Subtransactions allow you to record and display more detailed data for attributes
collected by the Web Transaction Monitor. The monitor in turn reports more
granular set of stats data. This way the monitor can not only report the 'Total
Response Time' of an entire transaction but also the sub 'Response Time' of each step
in the transaction.
Apart from reporting the response time of each step in the transaction, the monitor
also maintains a baseline of each step. This is a powerful feature since it enables any
abnormal behavior associated with the subtransactions to be correlated
automatically to the degradation in Total Response Time (without having to set a
threshold on it).
Subtransactions
Working with subtransactions

Click Subtransactions to display the Add/Edit Sub Transactions window.
Alternatively, go to Record => SubTransactions. This window enables you to
configure sub transactions for a transaction by grouping different URLs/steps.
Figure 68: Add/Edit Subtransactions window
To add a subtransaction,
The Starting Step and Ending Step drop-down lists consist of URLS/steps recorded
until then. The lists display the URLs in the order they were accessed and are
numbered accordingly. You can select a single step as a subtransaction or choose
multiple steps to form a single subtransaction.
Select the first and last step to define the subtransaction.
If required, specify a name for the subtransaction in the Name field. By default,
this field displays the URL of the starting step.
Click Add.
Note
To add a single step/URL as a subtransaction, select the same step as the
first and last steps. For example, to add Step.2 as a subtransaction, select Step.
2 as both the first and last steps.
The starting URL/step of a sub transaction should always precede the
ending URL/step in the order of access. For example, you can configure a
subtransaction that navigates from Step1 to Step2 but not from Step2 to Step1.
To edit a subtransaction,
From the Select Sub Transaction list, choose the subtransaction that you want to
edit.
Change the starting and/or ending steps of the subtransaction.

If required, provide a new name for the subtransaction.
Click Update.
To delete a subtransaction
From the Select Sub Transaction list, choose the subtransaction to be removed.
Click Delete.
Notes about subtransactions:

To take advantage of this feature, BMC ProactiveNet Agent running the Web
Transaction monitor must be Version 5.1 or later.
Only 20 subtransaction attributes are supported.

No nested subtransactions are allowed.
Over lapping subtransactions are not allowed.

Now that the Web Transaction File is created and exported to BMC ProactiveNet
Server, you are ready to create the Web Transaction Monitor.
To create a Web Transaction Monitor

1 In the Administration Console, right-click on the device and navigate to Add
Monitor => User Transactions => Web Transaction Monitor.
The Add Web Transaction window is displayed.
2 Enter information required in the Basic Information tab of the Add Web
Transaction window.
Transaction File - Select the transaction file you created for this monitor from
the list. This is the transaction file created previously. If there are no files in the
list or the file you want is not present, you may have a problem with the
location or generation of your transaction file. The list contains files only in the /
usr/pronto/usr_apps/webtranx directory. If no transaction file exists, or the
file you want is not present, check the location or generation of your
transaction file.
View/Edit option is discussed in the Playback the Web Transaction File topic.
Source Agent - BMC ProactiveNet Server, unless you own an enhanced BMC
ProactiveNet license. Choose the BMC ProactiveNet Server or BMC

ProactiveNet Agent where this monitor will run.
HTTP User Agent String - Select the HTTP user agent string. Each browser
type identifies itself to the Web server by sending a HTTP user agent string
with each request. You can simulate various browser types by modifying the
user agent string, which may be useful if a site launches different content based
on the browser type making the request.
User Agent string is used by BMC ProactiveNet to identify information about
the browser making the HTTP request. Under most circumstances, this field
should not be changed, since setting it to incorrect formats could cause the
monitor to fail when making requests to the Web server.
Instance Name - Provide a unique instance name that better describes your
transaction. This is displayed on folders, graphs, lists, and so forth. Example:

Web Trans test
3 Click Advanced Options tab.

Select the options that meet your requirements for this monitor, or accept the
defaults.
Full Page Option

Download Full Page - Select this option to download the entire Web page.
By default, only the text of the base page is downloaded. When this option is
selected, response time includes the download of links referenced on that
page. Select this option only if you want all images on the page, frames, and
HTML text to be downloaded. If this option is NOT selected, only frames

and text is downloaded. This option is not recommended since it affects
performance.
HTTP Proxy
Use Proxy - Optionally, a proxy server can be used to access the URL. Select
this option if a proxy is required to access the Web site specified.
Proxy Server - Enter the name/IP address of the computer hosting the proxy
server.
Proxy Port - Enter the port of a HTTP Proxy Server.

Proxy User - Enter the user name of a HTTP Proxy Server.
Note
Your proxy server must support Proxy-Authenticate for this option to function.
Proxy Password - If the proxy server requires a password to access the URL,
enter the password here.
Statistics Polling Options

Collect Data - Select this option to enable BMC ProactiveNet Server to
collect data for the monitor device. If this option is not selected, data
collection for the device stops (or never starts for new devices); you can
conduct maintenance on the device without generating events. Used to set
data collection parameters.
Statistics Poll Interval (min) - Specify the time interval between playing two
transactions. Default is 5 minutes. For performance purposes, it is not

recommended that you replay the transaction more than every 5 minutes.
Statistics Poll Timeout (min) - Specify the duration the system must wait for
a poll response before reporting 'No Response'. Default is 2 minutes.
Number of Retries - Enter number of times to retry the Monitor before
generating an event.
Retries Wait (sec) - Enter the number of seconds to wait before retrying the
Monitor after an error condition is detected.
Page Capturing Option

Capture Page on Failure - Select this checkbox to capture the page in which
the error (if any) has occurred during playback by the monitor instance. The
captured error page can be viewed from more info option in the Operations
Console.
4 Click Finish to view the Summary screen.

The Web Transaction Monitor is now ready. Creating a Web Transaction
Monitor automatically creates a device type called WebServer and places the
newly created Web Transaction monitor under this device.
Expand the Web Transaction subfolder under the Monitors folder in the
Administration Console to see that the new monitor is listed.

The Web Transaction monitor can be tested from the command line using the
program webtranmon. This program is available in the directory /usr/pronto/bin/.
webtranmon can be run both at the server as well as the agent. webtranmon can be
used as described below:
webtranmon [-options] webtranfilename
where options include:

-proxy:host:port:user:pass
Use proxy to get pages.

-emulateNS
Set Netscape as user agent.

-fulldownload
Download objects like browser.

-jsse
Use JSSE for SSL3 support.

-cryptix
Use cryptix for SSL support.

-timeout
Should be a positive integer in seconds.

webtranmon utility implements the same functionality as Web Transaction monitors
during polling.
The final status of processing of the transaction is displayed on the screen.
The examples below list the format of the output.
Pop-up Windows
Note
On non-Windows platforms, the transaction file is looked for in the directory /usr/pw/
pronto/usr_apps/webtranx
Example 1 - Success Transaction
UNIX# webtranmon yahoo.tranStarting webtranmon test with webtran file: /usr/

pw/pronto/usr_apps/webtranx/yahoo.tranWebTran
test result: SUCCESS -- see more details in the file /data/pw/pronto/usr_apps/
webtranx/yahoo.log
Example 2 - Failure Transaction
UNIX# webtranmon failure.tranStarting webtranmon test with webtran file: /usr/

pw/pronto/usr_apps/webtranx/failure.tran
WebTran test result: FAIL -- see more details in the file /data/pw/pronto/usr_apps/
webtranx/failure.log
Pop-up Windows
This section provides details about how to record pop-up windows with the web
transaction capture tool.
System authentication pop-up Windows

This procedure is required to record system authentication pop-up windows that
appear while recording a transaction and is not necessary for logons, which are
presented as form data. In other words, it is not needed when user name and
password fields are part of the Web page.
If a pop-up logon (Basic/Digest/NTLM Authentication) window appears during the
transaction, you must follow the steps given below to ensure that it is recorded.
1 Click Add Authentication in the Web Transaction Recorder to display the Add/
Edit Authentication window.
Step - Select the step/URL for which you want to add authentication information.
UserName - Specify the user name that is to be used to gain access to the
particular page in the Web site.
Password - Specify the password associated with the user name.
Pop-up Windows
Domain - Specify the domain where the user name and password combination
is to be used.
Authentication Type - Select the type of authentication mechanism supported
by your Web site. You can select Basic, Digest, or NTLM from the list.
Basic authentication
Upon receiving a 401-response header, the client's browser, if it supports basic
authentication, seeks user name and password information to be sent to the server. If
you are using a graphical browser, such as Netscape or Internet Explorer, a window
is displayed where you must specify your user name and password. The information
you type in is sent back to the server. If the user name is in the approved list, and the
password specified is correct, the resource will be returned to the client.
Digest authentication
Digest authentication is implemented by the module mod_auth_digest. There is an
older module, mod_digest, which implemented an older version of the digest
authentication specification, but which will probably not work with latest browsers.
Using digest authentication, your password is never sent across the network in the
clear, but is always transmitted as an MD5 digest of the user's password. In this way,
the password cannot be determined by sniffing network traffic.
NTLM authentication
NTLM is an authentication protocol used in various Microsoft network protocol
implementations and supported by the NTLM Security Support Provider
(NTLMSSP). Originally used for authentication and negotiation of secure DCE/RPC,
NTLM is also used throughout Microsoft's systems as an integrated single sign-on
mechanism.
NTLM employs a challenge-response mechanism for authentication, in which clients
are able to prove their identities without sending a password to the server. It consists
of three messages, commonly referred to as Type 1 (negotiation), Type 2 (challenge),
and Type 3 (authentication).
The client sends a Type 1 message to the server. This primarily contains a list of
features supported by the client and requested of the server. The server responds
with a Type 2 message. This contains a list of features supported and agreed upon by
the server. Most importantly, however, it contains a challenge generated by the
server. The client replies to the challenge with a Type 3 message. This contains
several pieces of information about the client, including the domain and user name
of the client user. It also contains one or more responses to the Type 2 challenge.
Responses in the Type 3 message are the most critical piece, as they prove to the
server that the client user has knowledge of the account password.
Insert - Click this to save data that you have specified as user logon information.
Delete - Click this to delete saved user logon information.
Update - Click this to save changes made to the existing user logon information.
Close - Click this to close and exit from the window.
Authentication information that you save is not displayed in the Step Info section.
However, if you want to view the authentication information that you have added
for a step, open the Add/Edit Authentication window.
Browser pop-up Windows

Several sites automatically pop up small windows with advertisements. These will
be referred to as Browser pop-up windows and can be recognized by the IE logo on
the top left. While these windows may not be of interest most of the time, they affect
the way one records a content match on the main window.
If you do not want to record browser pop-up windows,
1 Go to Options => Advanced Settings.
2 Select Allow Popups option.
The Allow Popups option enables other pop-up windows and screens associated
with the Web site you are viewing to be displayed while you are recording the
transaction. This does not interfere with the system authentication pop-up windows
that may be displayed.

Transaction files need to be exported from a remote Windows Administration
console to BMC ProactiveNet Server.
After you save a Web Transaction file, a window is displayed that seeks
confirmation whether you want to export the saved transaction file from the local
system to BMC ProactiveNet Server.
If you click Yes, then the Transaction File Export window is displayed.
To export web transaction files

1 Select the file(s) that you want to export from the local system to BMC
2 Click Export.
To delete Web Transaction files from the server, select the files and click Delete.

Perform one of the following procedures depending on which version of BMC
ProactiveNet you are using.
Editing Web Transaction files created in BMC ProactiveNet

7.0 and later
To edit a previously recorded Web Transaction file,
1 Go to Tools => Web Transaction Capture => Edit.
Alternatively,
Go to Tools => Web Transaction Capture => Launch WebCapture.
The ProactiveNet Web Capture window is displayed.
2 Click Open to list all the saved transaction files.
3 Select a transaction file to be edited.
4 Click Edit, the ProactiveNet Transaction File Editor window is displayed.

All steps of the transaction are listed in the left pane. The right pane consists of
different attribute groups that can be edited for each step.
Figure 69: Transaction File Editor window
Content match details tab

Title Match Displays the name of the title match.
Enable Title Match Select this option to automatically record the title of the
Web pages as Positive Content Match.
Content Match The Content match feature enables the Web Transaction user to
verify that the monitor navigates to the correct web pages during the transaction
playback. Content match can be specified for each step of the transaction file.
During playback, the downloaded page is parsed and the recorded content is
matched with the corresponding page to check the authenticity of the transaction
playback.
Positive Match - If the content is present in the page, then the playback is

Positive content match strings are preceded by the '+' symbol in the Content
Match section. Change the content match and title match strings, if required.
Negative Match During playback, the downloaded page is checked for the
negative match content. If the content is not present in the page, then the playback
is considered as successful. If the content is present, then an error is reported and
availability is set to zero.
Negative match is used ascertain that error condition related content is not
present on the page. Negative content match strings are preceded by the '-' symbol
in the Content Match section. Change the content match and title match strings, if
required.
Note
If the title match is enabled in Recorder or can be enabled from Edit option
manually, the Content Match will be displayed in green color.
If the title match is disabled in Recorder or can be disabled from Edit option
manually, the content match will be displayed in gray color.
Add Click to add a new content match.

Update Click to save any changes made to the selected content match.
Delete Click to delete the selected content match.
Sub transaction tab

This tab displays the subtransactions that you have defined for the transaction.
Change the properties of the subtransactions, if required.
Select Sub Transaction From the Select Sub Transaction list, choose the
subtransaction that you want to edit.
Select Starting URL for the Sub Transaction From the list, select the first URL
of the sub transaction recorded.
Select Ending URL for the Sub Transaction From the list, select the last URL of
the sub transaction recorded.
Sub Transaction Name Specify a name for the sub transaction.

Add Click this to add a new sub transaction.
Update Click to save any changes made to the selected sub transaction.
Delete Click this to delete the selected sub transaction.
Advanced settings tab

From the drop-down menu of View, select either Authentication, Step Details, Form
Details, or Request Header. By default, Authentication is selected. Advanced
Settings tab is intended for advanced users. The steps involved in creating, editing,
and deleting macros are same across the Advanced Settings tab.
There are four types of View:
1 Authentication
This tab displays information to be used during system authentication. Change
any details, if required. By default, Authentication is enabled.
User Name Specify the user name that is to be used to gain access to the
particular page in the Web site and is mandatory. Left-click or right-click

macro icon to enter the new macro or edit the existing macros. See Web
Transaction macro on page 549.
Password Specify the password associated with the user name and is
mandatory. Left-click or right-click to enter the new macro or edit the existing
macros. See Web Transaction macro on page 549.
Domain Specify the domain where the user name and password combination
is to be used. Left-click or right-click to enter the new macro or edit the

existing macros. See Web Transaction macro on page 549.
Type From drop-down menu, select either BASIC, DIGEST, or NTLM.

Add Click this to add new authentication.
Delete Click this to delete the selected authentication.
2 Step Details
Protocol - Indicates the protocol used (for example, HTTP 1.1 HTTP 1.0) (non
editable).
Method - Indicates the method used.

Name - Name assigned to the transaction step.
URL - The URL of the transaction step and is mandatory. Left-click or right-
click to enter the new macro or edit the existing macros. See Web Transaction
macro on page 549.
Update - Click to update the transaction step details with any changes you made.
3 Form Details
Form Name - Name of the form associated with the URL/step.
Form Index - Index of occurrence of the form with the same name in the page
Form Source - URL of the page where the form is present.
Form Action URL - Associated URL action of the form.
Input elements involved in the form are displayed in the name value pair format.
Name - The attribute name.
Value - The attribute value. Left-click or right-click to enter the new macro or
edit the existing macros. See Web Transaction macro on page 549.
Update - Click this to save any changes made to the form details.
Delete - Click this to delete the selected form details.
4 Request Header
In HTTP protocols, the client sends a request and associated options for response
from the server. This request consists of a set of properties like
User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR
1.1.4322).
Name The attribute name.
Value The attribute value. Click

macro icon to enter the new macro or
edit the existing macros. See Web Transaction macro on page 549.
Add Click this to add a new request header.

Update Click this to save any changes made to the request header.
Delete Click this to delete the selected request header.
Editing Web Transaction files created prior to BMC

ProactiveNet 7.0
BMC ProactiveNet enables you to view a previously created transaction file and
refresh your memory on the steps performed in the chosen transaction. At this point,
some of the features can be edited.
To view or edit a transaction file

1 From the menu bar on the Administration Console, select Tools => Web
Transaction Capture => Edit.
The Select a Transaction File window is displayed. This lists all the transaction
files saved on the server. Select the file to edit and click OK.
Edit the file under the available tabs. The step being modified is highlighted in the
right window.

The Content match feature enables the Web Transaction user to verify that the
monitor navigates to the correct web pages during the transaction playback. Content
match can be specified for each step of the transaction file. During playback, the
downloaded page is parsed and the recorded content is matched with the
corresponding page to check the authenticity of the transaction playback.
Web Transaction monitor supports three types of content match:
1 Positive Match
During playback, the downloaded page is checked for the specified positive
match content. If the content is present in the page, then the playback is
2 Negative Match
During playback, the downloaded page is checked for the negative match content.
If the content is not present in the page, then the playback is considered as
successful. If the content is present, then an error is reported and availability is set
to zero.
Negative match is used ascertain that error condition related content is not
present on the page.
3 Title Match
Page title can be recorded as part of the transaction file. As with Positive Content
Match, the downloaded page is checked for the Title during playback. Title match
can be used to validate rendered pages without manually insert content matches.
To enable Title Match, select the checkbox on the recorder GUI.
Note
Content match validation is supported both by the Web Transaction Monitor as

well as the Browser Playback feature.
Best practices to record content match

To insert text for content match on a given HTML page:
Locate the content using the View Source feature (Record => View Source).
Alternatively, right-click in the browser section of the BMC ProactiveNet Web

Capture screen to access the View Source feature.
Copy the desired content from the HTML source so that extra line feeds or in-
between newline characters are not copied. Do not copy the content from the
HTML page directly.
Content match is case-specific. So it is best if the content is copied from the HTML
source (and not the HTML page), than typed manually.
International characters
You can insert international characters as content match strings.
Extra line feed characters

User must ensure that the content is not copied from the browser window, but from
the actual HTML source. This is important since the HTML source maybe different
from the way the content is rendered in the browser. The actual HTML source may
contain tags such as line feed characters, etc.

A web transaction macro is a set of tasks combined together so that you can run or
replay the entire task together with a single command. Macros are a powerful
productivity tool. A web transaction macro is defined with a name, type, and value.
Web transaction macros are available only in Advanced Settings section.
Types of Web Transaction macros

The types of Macros that can be embedded in a transaction file, so that it is executed
during monitor playback, are:
Figure 70: Web Transaction Macro flowchart
Static Macro - Simplest of all macros. The value of the macro is statistically
defined in the transaction file.
ValueList Macro - Reads the value of the macro from the specified property file. It
uses the macro name as the name of the property and gets the value of that from
the property file. Multiple values can be specified for the macro as semicolon (;)
separated values in the property file.
Dynamic Macro - The value of the macro is obtained dynamically during
playback of the transaction.
Dynamic JavaScript Macro The value is obtained by executing the JavaScript.

Dynamic Predefined Macro The value is obtained by executing a predefined script.
Dynamic HTLM Macro You should be able to indicate variables which have to
be replaced dynamically during playback. Form data or hidden-form data,

changed through JavaScript, session information, cookies, URLs, and other
information may need to be replaced dynamically.
Managing Web Transaction macros

Through the BMC ProactiveNet Transaction File Editor window, you can create new
transaction macros, edit existing macros, or delete existing macros.
To create a new Web Transaction macro

1
Click the macro icon
The Macro Input Dialog window is displayed. From the list of Type, select the
type of the macro to be created.
2 Enter appropriate input details for the type of the macro you want to create. The
fields displayed on the Macro Input Dialog window differ, depending on the type
of macro.
STATIC
Name Indicates the name of the macro and is mandatory.
Type Indicates the type of the macro and is mandatory.
Value Indicates value of the macro and is mandatory.
Default Value Indicates the default value to be replaced.
VALUELIST
ValueList File Indicates the name of the file from which the value is to be
picked along with path and is mandatory.
Default Value Indicates default value to be replaced, if there is no value in
the defined file.
DYNAMIC_EXTERNALJS
Enter JavaScript or Browse Indicates free-form editor to write java script
or click on browse to load any java script file.
DYNAMIC PREDEFINEDSCRIPT

Select PreDefined Script Name From the drop-down menu, select the
predefined script that is bundled along with BMC ProactiveNet Server.
Dynamic ID Indicates input parameters for the predefined scripts and is
mandatory.
Step number - Indicates input parameters for the predefined scripts and is
mandatory.
3 Click OK to create a new macro.
Note
Web Transaction Macro name should not contain characters $$#$ as it is a

reserved key word for the web transaction macro. The web transaction macro
name field can contain any characters except in the sequence of $$#$.
To edit an existing macro

1
2 Select the macro to be edited and click Edit. Name and type fields are disabled in
edit mode.
3 Click OK to save the changes made and exit.
To delete the already created macro

1
2 Select the macro to be deleted.

3 Click Delete.
4 Click Yes in the confirmation message to delete the selected macro and exit.
Limitation
An already applied web transaction macro cannot be deleted; however, the web
transaction macro can only be deleted if the defined web transaction macro is not
applied to any field.
Usage scenarios
Static Macro
If you want to test the same application on different web servers, then instead of
recording several similar transactions, you have to just provide the server IP
addresses as web transaction macros. You can change the IP addresses easily.
For example,
The following are the steps of a recorded transaction:
http://192.168.3.105/servlets/com.proactivenet.servlet.Login
http://192.168.3.105/jsp/LayoutPage.jsp
http://192.168.3.105/jsp/AlarmSummary.jsp
If you want to test the same application running on different web servers, then you
define a Static macro by name ServerMacro (see xml snippet below). The value of
this macro is set to http://192.168.1.122. $$#$[ServerMacro]$$#$ indicates a
variable, which has to be replaced by value of Macro ServerMacro. After replacing
the values, the transaction is changed to the following steps:
http://192.168.1.122/servlets/com.proactivenet.servlet.Login
http://192.168.1.122/jsp/LayoutPage.jsp
http://192.168.1.122/jsp/AlarmSummary.jsp
Table 76: Web transaction file StaticMacro snippet
<MACRO NAME=ServerMacro TYPE=STATIC VALUE=http://192.168.1.122
DEFAULTVALUE=192.168.3.105></MACRO><STEP URL=$$#$[ServerMacro]$$#$/servlets/
com.proactivenet.servlet.Login></STEP><STEP URL=$$#$[ServerMacro]$$#$/jsp/
LayoutPage.jsp></STEP><STEP URL=$$#$[ServerMacro]$$#$/jsp/AlarmSummary.jsp></STEP>
ValueList macro
The transaction recorded maybe for an application, which the user wants to test for
different login information. The user should be able to indicate different login
information in the transaction file. Otherwise, the user has to record several similar
transactions with just the login information changed.
You can indicate the login information as ValueList macro in the transaction file and
the Web transaction monitor can use different login information.
For example, in the xml snippet below, a ValueList macro by name Login is
defined. The value for this macro is read from the property Login in the properties
file /home1/user.list. It is then used to replace the login information in the form data.
Table 77: Web transaction file ValueList macro snippet
<MACRO NAME=Login TYPE=VALUELIST SRC=/home1/user.list DEFAULTVALUE=admin></
MACRO><STEP><FORMDATA><INPUTDATA NAME=username VALUE=$$#$[Login]$$#$></FORMDATA></
STEP>
Dynamic Macro
In a transaction, there is currentDate as one of the form input data. When this form
data is submitted, next page validates if the currentDate is same as todays date. If
the validation fails, it throws up error page.
In this case, you can use a Dynamic JavaScript macro. The macro is defined with a
JavaScript that returns todays date. That macro can be used for form input data
currentDate. This makes the transaction successful.
For example, in the transaction file snippet below, a Dynamic JavaScript macro by
name todayDate is defined. The value of this macro is a JavaScript, which returns
todays date. The macro can be used in the form input data currentDate.
Table 78: Web transaction file DynamicMacro snippet
<MACRO NAME="todayDate" TYPE="DYNAMIC_EXTERNALJS" VALUE="new Date ();"></MACRO><STEP
><FORMDATA> <INPUTDATA NAME="currentDate" VALUE="$$#$[todayDate]$$#$" TYPE="text"
ENCRYPTED="FALSE" DOMSIGNATURE=""/></FORMDATA></STEP>
Dynamic predefined macro

If the value is obtained by executing a predefined script, then it is a Dynamic
Predefined Script Macro. Below is the list of predefined scripts that can be used in
macros.
Table 79: Web transaction Dynamic Predefined Macro snippet
1
pn_getFromHTML(String dynamicId,
int stepNum)
It is used to get the value dynamically from the

downloaded HTML page.
pn_getFromHTML(String dynamicId)
2
pn_getFromHeader(String
headerName, int
stepNum)pn_getFromHeader(String
headerName)
It is used to get the value dynamically from the HTTP

header
pn_getFromCookie(String
cookieName)pn_getFromCookie(Strin
g cookieName, int stepNum)
It is used to get the value dynamically from a cookie.
pn_getFromHtmlDomPath(String
domPath, String
attributeName)pn_getFromHtmlDom
Path(String domPath, String
attributeName, int stepNum)
It is used to get the value dynamically from the

downloaded HTML page DOM path. DOM path
matches the HTML element. If attributeName is null,
then the HTML elements value is considered.

An already applied web transaction macro cannot be deleted; however, the web
transaction macro can only be deleted if the defined web transaction macro is not
applied to any field.
AJAX
AJAX-enabled sites are not supported
Web sites that include Asychronous Javascript and XML (AJAX) content are not
supported.
Example: www.flickr.com , www.maps.google.com

Web sites with DHTML layers are not supported.
Example: www.sonystyle.com
Files/Plug-ins
Web sites that download content are not supported
BMC ProactiveNet Web Capture tool does not support transactions that
download or upload files such as MS Word documents, spreadsheets,
presentation files, PDF files, and ASCII text files.
For example: http://www.copyright.gov/legislation/dmca.pdf
Web sites with Plug-ins are not supported
The Web Capture tool does not support transactions that involve plug-ins such as
Applets, Flash, SVG, and multimedia features.
For example: www.ebay.com , www.macromedia.com (Flash)
Forms
Web sites that reset passwords before a POST are not supported
Some Web sites clear the password field in a form before doing a POST to the
server. In such situations, the Web Capture tool does not record the password.
Example: www.traderji.com
Flash-based Forms are not supported
This tool does not record data from Flash Forms.

Example: Search form at www.macromedia.com
Form POST is not supported
The Web Capture tool does not support pages, which do a POST of values from
different forms in the page.
The Web Capture tool fails to record the password value when the Password field
in a form is reset to an empty string or to a predefined default value before a

POST. In such situations, playback and monitor creation fail.
This tool does not support forms that do not POST but redirect. Some pages do
not POST selected values, but use JavaScript redirection to load the required page.
This event may not be recorded by the Web Capture tool.
Example: www.hsbc.co.in
Form Action URLs with dynamic session IDs are not supported
The monitor and the Playback tool do not support transactions that have dynamic
session ID values as part of the Form action URL.

Example: www.homedepot.com
Frames
Web sites with Cross-scripting feature are not supported
Due to cross-site scripting (XSS) limitation of Internet Explorer, Web sites that
contain frames from a different domain (or a sub-domain) are not recorded.
For example: www.federaldaily.com
Images
ImageMaps are not supported
The Web Capture tool does not support Web sites with ImageMaps. (An Image
Map is a list of coordinates relating to a specific image, created in order to
hyperlink areas of the image to various destinations)
Example: http://www.ihip.com/
Image tags with OnClick eventhandlers are not supported
The Web Capture tool does not record the click event, when the action URL of a
form is manipulated and a POST happens in the OnClick eventhandler of Image
tags.
Example: www.americanairlines.com
Internationalization
URLs with internationalized Domain Names are not supported
The Web Transaction monitor does not support URLs with Internationalized
Domain Names (IDN).
Example: http://www.nestle.com/All_About/All+About+Nestl.htm
Internationalization is not supported in the Attribute pages of the Operations
Console
Attribute pages of the Operations Console do not display Non-English Unicode

characters correctly.
For more information on Internationalization support, refer Internationalization
Support topic.
Javascript
Javascript redirection is not supported
The Web Capture tool does not record JavaScript redirection in Web pages.
Suppressing JavaScript Error window
While recording and playing back a transaction, the Web Capture tool does not
suppress JavaScript Error windows that may appear.
Example: www.perbio.com
Transactions with DOM object manipulation not supported
The Web Capture tool does not support transactions wherein the DOM object of
the page is manipulated explicitly in JavaScript functions.
Example: www.mappoint.msn.com
Log files
Unicode characters not displayed correctly
Web Recorder log files and log files generated by the Validate tool do not display all
Unicode characters correctly. Non-English characters may be displayed as '?' or other
symbols.
Miscellaneous
Pop-up windows with the Close button/hyperlink are not supported
The Web Capture Tool does not close a pop-up window when the Close button or
hyperlink on it is clicked.
Workaround: Close the pop-up window manually.
Monitor plays back blocked pop-up windows
The Web Transaction monitor does not suppress pop-up windows even if
transactions are recorded without selecting the Allow Popups option.
Web sites that accept inputs from soft keyboard not supported
Transactions that require you to specify inputs using a soft keyboard (an on
screen keyboard that duplicates the hardware keyboard. One uses the mouse
pointer to choose which key/characters to enter) are not recorded.
Example: www.citibank.co.in
URLs with dynamic session IDs are not supported
The monitor and Playback tool do not support transactions that have dynamic
session ID values as part of the URL.
Example: www.lexus.com
Dynamic Page Titles are not supported
Page in a site where the title is frequently altered fails in Title Match. Such
transactions should be treated as site-specific.
Some Web servers change page titles dynamically. In such situations, the
Playback tool and Web Transaction monitors fail to match the recorded Title.
Workaround: Record the transaction without Title Match or edit the transaction
file and delete the title of the particular step.
Playback
Persistent Cookies not supported
BMC ProactiveNet Web Capture tool does not support persistent cookies while
playing back a transaction file (GUI mode).
Digest Authentication information not supported
While playing back a transaction (GUI mode), access information for Digest type
authentication must be entered manually.
NTLM Authentication
If user name or password with special characters such as '@' or domain name is
specified as NTLM authentication information for a transaction while recording,
then the same information must be entered manually during GUI playback
Support for Transactions recorded using earlier versions of BMC ProactiveNet
BMC ProactiveNet Administration Console does not support playback for

transactions recorded using earlier versions of BMC ProactiveNet that are saved on
BMC ProactiveNet Server (upgrade setups). Only those transactions that are locally
available on the BMC ProactiveNet Administration Console are played back.
13
Working with event management
policies
This chapter describes the components of event management policies and explains
how to implement them. It contains the following topics:
Displaying the Infrastructure Management

node
By default, the Infrastructure Management node is not displayed in the Event
Management Policies tab or the Dynamic Data Editor tab in the BMC ProactiveNet
Perform the following procedure to display the node in these tabs.
To display the Infrastructure Management node

1 In a text editor such as Notepad, open the ix.properties file.
By default, the file is located in the following directory:
BMC_PROACTIVENET_HOME\admin\etc\
2 Change the value of the following parameter to True:
infrastructure_management_node_visibility
3 Save and close the ix.properties file.

The Infrastructure Management node is displayed in the Event Management
Policies and the Dynamic Data Editor tabs.
Chapter 13 Working with event management policies
561

Event management policy types provide a base policy definition that enables you to
quickly create certain types of policies. Policy types allow you to quickly set up
routine event management processes.
Table 80 on page 562 describes the standard event management policy types.
Table 80: Standard event management policy types
Policy name
Definition
Blackout
sets the status of an event to BLACKOUT. A blackout policy might be used

during a maintenance window or holiday period.
Closure
closes a specified event in response to receipt of a separate event
Component Based
Enrichment
enriches the definition of an event associated with a component by assigning

selected component slot definitions to the event slots
Correlation
relates one or more cause events to an effect event, and can close the effect event
The cell maintains the association between these cause-and-effect events.
Enrichment
adds values for specific event slots if those slots are empty as received from the
event source
An enrichment event management policy can also reformat slots or normalize
slot values.
Escalation
raises or lowers the priority level of an event after a specified period of time
A specified number of event recurrences can also trigger escalation of an event.
For example, if the abnormally high temperature of a storage device goes
unchecked for 10 minutes or if a cell receives more than five high-temperature
warning events in 25 minutes, an escalation event management policy might
increase the priority level of the event to critical.
Notification
sends a request to an external service to notify a user or group of users of the event
A notification event management policy might notify a system administrator by
means of a pager about the imminent unavailability of mission-critical piece of
storage hardware.
Propagation
forwards events to other cells or to integrations to other products
Recurrence
combines duplicate events into one event that maintains a counter of the number
of duplicates
Remote action
automatically calls a specified action rule provided the incoming event satisfies
the remote execution policys event criteria
See also Configuring and using Remote Actions/Diagnostics on page 355 for
more information.
Suppression
specifies which events that the receiving cell should delete

Unlike a blackout event management policy, the suppression event management
policy maintains no record of the deleted event.
Policy name
Definition
Threshold
specifies a minimum number of duplicate events that must occur within a

specific period of time before the cell accepts the event
For events allowed to pass through to the cell, the event severity can be escalated
or de-escalated a relative number of levels or set to a specific level. If the event
occurrence rate falls below a specified level, the cell can take action against the
event, such as changing the event to closed or acknowledged status.
Timeout
changes an event status to closed after a specified period of time elapses
Component Based
Blackout
Specifies which events the receiving cell should classify as unimportant and
therefore not process . The events are logged for reporting purposes.
A Component Based Blackout event management policy might specify that the
cell ignore events generated from a component or device based on component
selection criteria for this policy.
It is also possible to define custom policy types that allow you to do specialized
event processing not supported by the out-of-the-box policy types.
For more information about creating user-defined policy types, see Creating and
using user-defined policies on page 689.

Several event management policies are included with the product that enable you to
interactively set up routine event processing quickly. Standard event management
policies that are provided out-of-the-box include:
PATROL_Portal_Closure_on_OK_Events
Apache_Login_Failed_Repeats
Blackout_Suppression
Adapter_Start_Stop_Closure
Client_Stop_Closes_Start
Sample_Component_Based_Enrichment_Policy
Sample_Intelligent_Incident_Service_Policy
Event_Reporting_Propagation
Event_Propagation_To_Remedy_Help_Desk
Dynamic enrichment policies that are provided out-of-the-box include:

563
Location_Enrichment
Service_Contact_Enrichment
PATROL_Message_Translation
BPM_STATE_CHANGE
BPM_RSM_STATE_CHANGE
PATROL_EVENT
To use these out-of-the-box dynamic enrichment policies, you must enable the
policy, import useful data into the sample .csv files and then import the data into the
cell using the policy mechanism. For instructions on creating dynamic enrichment
policies, see Creating a new dynamic enrichment event management policy on page
641.
Table 81 on page 564 lists the out-of-the-box policies and indicates whether or not
each out-of-the-box policy is enabled by default.
Table 81: Out-of-the-box policies
Policy type
Policy name
Description
Enabled?
Closure
PATROL_Portal_Closure_on_
OK_Events
closes previous Portal events for the

same managed object
Yes
Adapter_Start_Stop_Closure
closes previous events for the same

adapter instance
Yes
Client_Stop_Closes_Start
Client Stop events close Client Start

events and then close themselves
Yes
JSERVERCellConnectionStatu
sPolicy
Yes
Close_Open_Alarms
Yes
RATECellConnectionStatusPol
icy
Yes
Component Based
Enrichment
Sample_Component_Based_
Enrichment_Policy
enriches events by filling selected event

slots with the slot values of the
component type
No
Dynamic Blackout
Dynamic_Blackout
blacks out events that meet a specified

criteria during a specified time period
No
Policy type
Policy name
Description
Enabled?
appends the location of a server to an

event
No
appends contact information for a

server administrator to an event. For
example, contact information may
include the name of the administrator
for that server and his or her telephone
number.
No
PATROL_Message_Translatio
n
replaces the text of existing PATROL

No
event messages with messages that can
be more easily understood by operators
Dynamic Enrichment Location_Enrichment
Intelligent Incident
Service
Sample_Intelligent_Incident_S sample policy for creating Intelligent

ervice_Policy
Incidents for Remedy Helpdesk
Propagation
Event_Propagation_To_Remed propagates events to Remedy Helpdesk No

y_Help_Desk
Event_Reporting_Propagation
Recurrence
propagates events to the Portal for

event reporting
No
No
Apache_Login_Failed_Repeats handles repeating Apache Login Failed

events
No
Patrol_Portal_DeDup_Policy
handles repeating Portal events for the

same managed object
Yes
Suppression
Blackout_Suppression
suppresses Blackout events
No
Component Based
Blackout
Component_Based_Blackout
suppresses events that meet a specified

criteria during a specified time period
for specified components
No
For instructions on using these out-of-the-box policies, see Creating new standard
event management policies on page 591 and Creating a new dynamic enrichment
event management policy on page 641.
Note
The BMC Impact Integration for PATROL product can detect duplicate events and
can correlate events that come from the same origin. The rules for detecting
duplicated events are located in the MCELL_HOME /etc/ cellName /kb/rules/
bii4p.mrl file. See the patrol_duplicates and the correlate alarm_and_ra
definitions. You can use the new patrol_duplicates rule to delete duplicate events
and the correlate alarm_and_ra rule to close a current event after a subsequent event
arrives from the same origin.
BMC Impact Integration for PATROL does not provide a policy for these events.
565

All event management policies must include the following components:
event selector
process(es)
timeframe(s)
evaluation order
Each event management policy defines selection criteria that is applied to incoming
events to determine which events are processed. A timeframe determines when the
policy is active or inactive. The evaluation order determines which policies are
implemented first if there is a conflict.
In addition to these components, dynamic enrichment policies also require a
dynamic enrichment source file, for more information on how dynamic enrichment
policies interact with dynamic enrichment source files, see How dynamic enrichment
event management policies work on page 571.
Event management policy workflow overview

The following figure illustrates the workflow for creating and implementing an
event management policy.
Figure 71: Event management policy definition workflow
Event selectors
An event selector is the component of an event management policy that selects one
or more events to which an event management policy applies.
Rather than specifying a particular event to process, as a rule does, a selector
specifies a list of event selection criteria (also called an Event Condition Formula
(ECF)). When an incoming event meets any of the specified event selection criteria,
the cell applies the associated event management policy to the event. For more
information, see Event selection criteria on page 569.
Table 82 on page 567 lists the out-of-the-box event selectors.
Table 82: Out-of-the-box event selectors
Event selector
Group
Event selector
Events selected
Default
Adapter_Start_Stop
Adapter starting and stopping events
Default
Apache_Login_Failed
Apache web server login failed events
Default
Client Stop
client stop events
Default
PATROL_Portal_Events
events coming from PATROL Portal
Default
PATROL_Portal_OK_Events
OK severity events coming from PATROL Portal
IBRSD
All_Critical_Events
critical events propagated to the Integration with

BMC Remedy Service Desk
IBRSD
Component_Change
service model component change events from

BMC Service Impact Management
None
All_Events
all events
None
BPM_RSM_STATE_CHANGE
state change events coming from the BMC Portal

Remote Service Monitor
None
BPM_STATE_CHANGE
state change events coming from the BMC

Performance Manager
None
Blackout_Events
all blacked-out events
None
PATROL_Event
not used
None
PATROL_Events
events coming from PATROL agents
PPM
JSERVERCellConnectionStatusSelect events coming from the Jserver

or
PPM
RATECellConnectionStatusSelector
RATE events
PPM
OK_Alarms
events with a status of OK
You can create custom event selectors. For information about creating event
selectors, see How to create an event selector and specify event selection criteria on
page 581.
567
Note
The maximum number of selectors that can be displayed in the Event Management
Policies view is 2500. The view will display 1024 selectors if you set the query_size
parameter in the %BMC_PROACTIVENET_HOME%\admin\etc\ix.properties
file to less than 100 (< 100) or greater than 2500 (> 2500).
Event selector groups

An event selector group, created when an event selector is defined, enables you to
organize event selectors. For example, you could create event selector groups that
classify event selectors by the severity of events. You could create one event selector
group for major severity events and one for minor severity events.
Event selector groups appear as folders in the By Selector subtree in the Event
Management Policies navigation pane. The names of event selectors which belong
to a group are displayed as group.event_selector_name in the selectors lists in the list
pane and in the By Event Class subtree. The name also is displayed in a separate
field in the Selector Details tab.
Figure 72 on page 568 shows an event selector group called Default that has the
Adapter Start Stop event selector highlighted. Notice that details about the
highlighted event selector appear in the Selector list in the right pane of the
Administration View.
Figure 72: Event selector group name
Event selectors do not have to belong to a group. Event selectors that do not belong
to a group are displayed directly under the By Selector subtree.
Event selection criteria

Event selection criteria tells a cell to which incoming events to apply the associated
event policies. By using selection criteria to choose events rather than creating a
single event management policy for each event type, event selection criteria perform
the event management policy equivalent of dynamic data for rules. One event
management policy using event selection criteria that spans a range of event types
can be easier to maintain than a separate rule for each of many event types.
The BMC ProactiveNet Administration Console interface enables you to interactively
create syntactically accurate event selection criteria expressions without the need for
specific syntax knowledge because the editor verifies that the expression has the
correct syntax.
For more information see, How to create an event selector and specify event
selection criteria on page 581.
Timeframes
Timeframes allow you to specify when the event management policy is active. For
example, during scheduled database maintenance periods, you might want to
activate an event suppression policy for maintenance-related events to reduce
unnecessary event accumulation.
For events to be impacted by a timeframe setting, the timeframe must be active for
the entire time that is specified in the policy.
Example
An escalation policy is defined to escalate an event to priority level 1 (escalated one
level) after 10 minutes. Events are generated. No event will be escalated for at least
10 minutes. Five minutes after the policy is enabled, the policy is disabled. Even
though the policy was active at the beginning of the 10 minute period, no event is
impacted by the policy because it is not active at the end of the 10 minutes.
An escalation policy is defined to escalate an event priority after 30 minutes with an
active timeframe from 4:00 P.M. to 5:00 P.M. At 4:45 P.M. Events are generated. The
active time period expires at 5:00 P.M. Events generated at 4:45 P.M. are not
impacted by the policy because the timeframe is not active at 5:15 P.M.
Table 83 on page 570 describes the types of timeframes you can use in an event
management policy.
569
Table 83: Timeframe types and descriptions

Type
Icon
Description
Local timeframes are used for event policies only.
They are maintained in the cell and are only visible
to a single cell.
local timeframe
You create local timeframes from the Event

Management Policies tab of the BMC ProactiveNet
Administration Console, as described in How to
create a new local timeframe on page 573.
Evaluation order of event policy types

BMC ProactiveNet cells evaluate event policies of different types based on the order
of the rule phase in which the event management policy executes.
Table 84 on page 570 describes the standard rule phases and their associated event
policy types.
Table 84: Evaluation order of event policy types
Evaluation order
Rule phase
Event policy type
refine
blackoutenrichmentdynamic blackoutdynamic
enrichmenttimeout (initialization)
filter NOPASS
regulate
threshold
suppression
a
threshold
a
threshold escalation
new
closurerecurrence
abstract
no related event management policy
correlate
correlation
execute
timeout (arm)notification
propagate
propagation
10
delete
no related event management policy
11
timer
timeout (execute)escalation
a Unlike other event policies, cells evaluate threshold event policies in two distinct phasesthe first phase
for the hold threshold and the second phase for the pass through threshold.
WARNING
Although event policies of different types are evaluated according to their associated
rule phase, event policies of the same type do not have an evaluation order. For
example, if event selectors for two event policies of the same type select the same
event, the cell evaluates the event according to one event management policy and
ignores the other event management policy.
To prevent omission of event management policy evaluation, you must create
mutually exclusive event selection criteria for two event policies of the same type.
With the exception of dynamic blackout, dynamic enrichment, notification and
propagation event policies, two or more policies of the same type should not execute
against the same event. In the case of exceptional event policies, the cell evaluates all
event policies of those four types, even if their selectors reference the same event.
How dynamic enrichment event management

policies work
Dynamic enrichment event management policies require the same components as
standard event management policies. However, dynamic enrichment policies allow
you to import external enrichment data into the policy, rather than having to enter it
manually.
First, you must either export data from a data source (such as an asset database) or
manually enter information into the enrichment file (.csv).
Once the data enrichment source file contains the data required, you can use the
policy to import the data into BMC ProactiveNet for use in the enrichment process.
Figure 73 on page 571 illustrates the dynamic enrichment flow.
Figure 73: Flow of data required to implement a dynamic enrichment policy
External enrichment data sources

An external enrichment data source can provide additional information about an
event that is not available from the technology from which the event originates. An
example of an external enrichment data source is a database such as an asset data
store. Information from the database must be manually exported into a flat delimited
571
file, so that BMC ProactiveNet can access the information. The recommended format
to export the data to is a .csv file.
BMC provides some sample policies and associated enrichment data sources in the
%BMC_PROACTIVENET_HOME% \admin\etc\samples directory.
Dynamic enrichment source files

A dynamic enrichment source file must contain at least one match field and at least
one output field.
A match field is the lookup or key field which the dynamic enrichment policy uses to
identify the incoming event. You may use multiple match fields to identify an
incoming event.
An output field identifies the type of enrichment information that is to be added to
the event.
Once the policy has matched the event data of the match field(s) with the data in the
enrichment file, it will add the associated enrichment data from the enrichment file
into the output field identified in the policy.
WARNING
It is critical that the policy definition and the data enrichment source file contain the
exact same number of match fields and output fields in the same order. If the match
fields and output fields in the enrichment file and the policy do not match, the policy
will not run.
For example, if you are using the contact.csv file that is included with the product,
you must select the Host Class, Host, Object Class, and Object slots as the Match
Fields and the Service and Owner slots as the Output Fields to correspond to the
slots in the contact.csv file.
Wildcards are supported for pattern matching which enables for more generic policy
rules to be written.
Sample dynamic enrichment source files

Table 85 on page 573 lists the product-supplied dynamic enrichment source files
that are located in the %BMC_PROACTIVENET_HOME%\admin\etc\samples
directory. These sample files provide commonly needed enrichment information.
You can use these files as a guide to create your own dynamic enrichment source
files or you can modify and use these sample files.
Table 85: Dynamic enrichment source files

Data source file
Policy name
Description
location.csv
Location_Enrichment
appends the location of a server to an event
contact.csv
appends contact information for a server

administrator to an event. For example, contact
information may include the name of the
administrator for that server and his or her
telephone number
TextTranslation.cs
v
PATROL_Message_Translation
replaces the text of existing PATROL event

messages with messages that can be more easily
understood by operators in your enterprise. This
file includes predefined message translations
that will be immediately useful. For more
information, see Using the sample PATROL
messaging text translation dynamic enrichment
source file on page 578.
blackout.csv
Dynamic_Blackout
blacks out events that meet a specified criteria

during a specified time period
BPM_Category_
Table.csv
Dynamic_Enrichment_Policy
supports event categorization for BMC

Performance Manager (BPM)
BPM_RSM_STATE Dynamic_Enrichment_Policy
_CHANGE_
Category_Table.csv
supports event categorization for Remote

Service Monitor (RSM) events
PATROL_P7_
Dynamic_Enrichment_Policy
Category_Table.csv
supports event categorization for PATROL 7

events
For information on creating and using dynamic enrichment source files, see How to
create and edit a dynamic enrichment source file on page 576.

Local timeframes allow you to specify periods of time that determine when an event
management policy will or will not run. You can set up a single timeframe that can
apply to multiple policies.
For example, if you have several policies that you do not want to run on weekends,
you can set up a timeframe from 12:00AM to 12:00 AM on both Saturday and
Sunday and call that timeframe Weekend. You can then apply the timeframe
Weekend to all policies that you do not want to run on weekends.
573
Note
Timeframes are required for blackout policies.
To define an event management policy timeframe

1 From the toolbar of the Event Management Policies tab in the BMC ProactiveNet
Administration Console, click the View/Update Timeframes button
The Timeframes window is displayed, as shown in Figure 74 on page 574.

Figure 74: Timeframes
2 From the Timeframes toolbar, click the New Timeframe button.

3 In the Timeframe New dialog box, enter or modify the information described in
Table 86 on page 575.
How to add a notification service (notification policies only)
Table 86: Timeframe New dialog box options

Field
Description
Name
Name of the timeframe
Description
Description of the timeframe
Start, End
Period when the timeframe begins and ends. You can specify the End value as
either a Time or Duration. If you select Time, select the appropriate value from
the list. If you select Duration, select the number of hours that you want the
timeframe to be active.
The individual time zone of the cell will be used in timeframe calculations.
Recurrence pattern
Schedules how often the timeframe will recur. Changing the selection in the left
side list will change the options available on the right side.
Besides the Daily, Weekly, Monthly, and Yearly timeframe options, you can
select individual dates that are part of the timeframe by selecting Date List and
choosing dates from the displayed calendar.
Range of recurrence
When you have selected a Daily, Weekly, Monthly, or Yearly timeframe option,
you can choose the starting and ending date range for the recurrence.
Optionally, instead of choosing an end date, you can enter the number of
recurrences for the timeframe.
4 To create additional timeframes, click Save and repeat this procedure starting
with step 2.
5 To close the editor, click Close.
How to add a notification service (notification

policies only)
Before you can create or enable a standard notification event management policy,
you must add a notification service. A BASIC_EMAIL notification service that sends
an email notification to a specified user or group of users when selected events occur
is provided by default.
To add a notification service

1 On the Administration View, choose the Dynamic Data Editor tab.
2 In the Dynamic Data Editor tree, expand the server for which you want to add
notification.
575
3 Expand the Data section, and then expand the Cell Data section.
4 Select Notification Service.
The available notification services are listed in the Notification Service tab in the
right pane of the Administration View.
5
Click the Add data instance icon
A New notification service tab is displayed.

6 On the New tab, in the Name field, enter a unique name for the service.
7 In the Type field, choose one of the following notification service types:
Commandthe notification service is implemented using a command or script
Gatewaya gateway to an external notification service will be used
8 In the Service field, enter the appropriate information based on the notification
service type:
Commandenter the command or script used to initiate notification. For
example, the script for the default BASIC_EMAIL notification service is

mc_sendmail.
Note
If the notification service will be executed using a script, the script must be
located in the kb/bin/ platform directory of the cell Knowledge Base.
Gatewayenter the name of the destination gateway. This gateway must be
referenced in the directory file of your cell (mcell.dir).
9 [Optional.] In the available_targets field, within the square brackets enter a commaseparated list of predefined users that you want to receive the notification. The list
must be known to the notification service. If no predefined list exists, any target
string may be entered (such as an email address).
10 Click OK.
How to create and edit a dynamic enrichment

source file
Note
Dynamic enrichment source files are not required for standard event management
policies. You only need a dynamic enrichment source file if you are creating a
dynamic enrichment policy.
Before you enable a dynamic enrichment policy, you must import or enter the data
that you want to use for enrichment into a data file. You can import the enrichment
data into any delimited flat file; however, BMC Software recommends importing the
data into a .csv file and using Microsoft Excel to view and manipulate the contents of
the file. The spreadsheet format of Microsoft Excel makes it easier to view and
manipulate the information in the file.
You can use the sample data enrichment files provided with the product as a guide
to set up your own data enrichment source files. The sample files are located in the
%BMC_PROACTIVENET_HOME%\admin\etc\samples directory. For a list of
sample files provided with the product, see Sample dynamic enrichment source files
on page 572.
Before you begin

If you will be referencing a timeframe in your dynamic enrichment source file, you
must ensure that the timeframe that you will be referencing already exists. If the
timeframe you want to reference does not exist, you must define it as described in
How to create a new local timeframe on page 573.
To create a dynamic enrichment source file

1 In Microsoft Excel, create a new file and save it as type .csv.
2 In each column of the spreadsheet, enter information that corresponds to each
match value and output value that will be included in your dynamic enrichment
policy.
WARNING
It is critical that the policy definition and the data enrichment source file contain
the exact same number of match fields and output fields in the same order. If the
match fields and output fields in the enrichment file and the policy do not match,
the policy will not run.
For example, if you are using the location.csv file that is included as a sample
with the product, this file has two columnsmc_host and mc_location. If you
are creating a dynamic enrichment location policy that uses the location.csv file as
the data enrichment source file, you must select the Host slot as the Match Field
and the Location slot as the Output Field to correspond to the columns in the
location.csv file.
577
To edit a sample dynamic enrichment source file

1 Open one of the sample data source files included with the product located in the
%BMC_PROACTIVENET_HOME%\admin\etc\samples directory.
2 Import or enter information specific to your enterprise.
Figure 75 on page 578 shows an example of an edited location.csv file.
Figure 75: Example edited location.csv file

# This enrichment file is used to add an extra field "mc_location" to
an event.
# This can be useful to group together or understand the physical
location of IT components to help with event assignment and resolution.
# mc_host, mc_location
Texan1, Houston
Texan2, Houston
Cowboy*, Dallas
The location for hosts Texan1 and Texan2 is listed as Houston. The location for
all hosts beginning with Cowboy (for example, Cowboy1, CowboySmith,
CowboyAikman) is listed as Dallas.
4 The data enrichment source must be imported into the policy each time you
modify the .csv file. For instructions on importing dynamic enrichment data
source, see Importing dynamic enrichment source on page 669.
Using the sample PATROL messaging text translation

dynamic enrichment source file
The sample PATROL messaging text translation data enrichment source file,
TextTranslation.csv, provided in the %BMC_PROACTIVENET_HOME%\admin
\etc\samples directory is prepopulated with over two hundred translations for
messages from the following Knowledge Modules:
BMC SQL-BackTrack NetWorker OBSI Module
PATROL KM for CONTROL-M
PATROL KM for UNIX and Linux
PATROL KM for Microsoft Windows Servers
PATROL KM for Netware
PATROL KM for Sybase
PATROL KM for Internet Server Manager

PATROL KM for Oracle
BMC Performance Manager for Microsoft Windows Terminal Services
If you are integrated with PATROL, you can gain instant value by enabling this
policy and importing the data from TextTranslation.csv into the cell as described in
Enabling a dynamic enrichment PATROL message text translation policy on page
665. This policy enables you to reword ambiguous event messages into messages
more easily understood by the IT operators handling the events in the BMC
ProactiveNet Operations Console.
The sample policy, TextTranslation.csv, will translate PATROL event messages
coming from either BMC Impact Integration for PATROL 3 or BMC Impact
Integration for PATROL 7.
Overview of the PATROL messaging text translation

dynamic enrichment source file
The following figure shows some sample rows included in the TextTranslation.csv
file.
Figure 76: Sample rows in the TextTranslation.csv file
The first three columns are match fields for incoming events. The first column
contains the object class or application class of the KM. The second column contains
the parameter. The third column contains the origin class.
The last column is the output field or the message that should be displayed when an
event matching the criteria in the first three columns is received.
For example, in the first row, the cell will look for an event coming from the
CPUCpuUtil parameter of the CPU application class. When the cell receives that
event, it will display the message:
CPU Utilisation is at 97%
579
or whatever number the CPU utilization percentage is at that time.

Many of the messages in the sample file contain slots that will be populated with
values from the parameter. For information on the syntax for using slots in a text
message see, Editing the PATROL messaging text translation dynamic enrichment
source file on page 580
Editing the PATROL messaging text translation dynamic

enrichment source file
You can also add to and edit the TextTranslation.csv file, if required. For example,
you might want to translate the messages included in the file into your native
language. Or, you might want to include messages related to a KM that is not
already included in the file.
One of the most powerful features of the text translation file is the ability to include
CORE_EVENT base event class slots that will allow you to dynamically populate the
message with information from parameters or other components. This feature
enables you to create messages that are very meaningful.
Figure 76 on page 579 shows some actual messages in the TextTranslation.csv file
that include variables. For example,
Figure 77: Variable syntax example
FILESYSTEM
FSCapacity
Filesystem %mc_object% is %mc_parameter_value%\% full
This message includes the %mc_object% and %mc_parameter_value% variables.

This syntax in the enrichment source file enables you to substitute the value of the
slot you have referenced into the event message.
To insert a slot value into a message, use the following syntax:
Message text %<slot_name>% message text
If you need to include a % sign in the actual message text, you must precede the %
character with a back slash (\). For example, in Figure 77 on page 580 the desired
text message includes a % character. The syntax for the message is
%mc_parameter_value%\% full.
If the value of mc_object is D: and the value of mc_parameter is 97 the reworded

message would be:
Filesystem D: is 97% full.
For a list of CORE_EVENT base event class slots that you can use in text messages,
see BMC Knowledge Base Development Reference Manual.
How to create an event selector and specify

event selection criteria
An event selector is the component of an event management policy that selects one
or more events to which an event management policy applies using specified event
selection criteria. When an incoming event matches any of the specified event
selection criteria, the cell applies the associated event management policy to the event.
Before you begin

Unless you want the event management policy to run continuously, you must
define a timeframe as described in How to create a new local timeframe on page

573.
[For dynamic enrichment policies only.] Create a data enrichment source file as
described in How to create and edit a dynamic enrichment source file on page 576.
To create an event selector and specify event selection criteria

1 From the Administration View, select the Event Management Polices tab.
2 Select a valid node (non-cell group) from the navigation pane.
Valid nodes for event selector creation are all visible nodes except the top-level
cell group node. When the Add Event Selector button in the toolbar becomes
active, this is an indication that valid node is selected.
On the Administration View toolbar, click the Add Event Selector button
581
The Selector Details tab, shown in Figure 78 on page 582, is displayed.

Figure 78: Selector Details tab
4 In the Selector Name field, type the event selector name.

5 In the Group field, type an event selector group name.
The event selector that you create in the next step will belong to the event selector
group that you enter. If you enter a name of an event selector group that does not
exist, that group will be created.
button to display
To the right of the Base Event Class field, click the ellipses
an event class chooser dialog box (shown in Figure 79 on page 583) from which
to choose the event class.
Figure 79: Class Chooser dialog box
7 Select an event class from the tree and click OK to accept the class.
For more information about event classes, see the BMC Knowledge Base
Development Reference Guide.
8 In the Description field, type an optional description for the event selector.
9 Click Add to add event selection criteria to this event selector.
The Add Event Criteria editor is displayed.
583
10 From the Add Event Criteria editor, type a description for the event selection
criteria in the Description slot.
11 In the Event Class field, use one of the following methods to select an event class
on which to base the event selection criteria:
Accept the default event class in the Event Class field.
Change the class by clicking the browse button. The Class Chooser dialog box
is displayed, select a class and click OK.
Note
You cannot change the event class specified in an ECF to any class that is not at
the same level or below the event class already specified in the ECF. If the ECF
contains slots in the current class that are not in the new class, you cannot
change to the new class, even when it occurs in the hierarchy rooted in the base
event class.
12 In the Selection Definition section, shown in Figure 80 on page 584, create an
expression that is used to determine whether an event of the selected class is
processed by the policy by choosing a Slot, Operation, and Value.
Figure 80: Selection Definition section of the Add Event Criteria editor
The example expression in Figure 81 on page 584 tests events for Windows
security messages containing logon and logoff messages. You might use this
expression as part of an event selector for implementation in an event blackout
policy that hides these security events from display but maintains their history.
Figure 81: Example event selection criteria expression
For a list and definitions of EVENT slots available for selection, see the event and
data classes appendix of the BMC Knowledge Base Development Reference Guide.
For a list and definitions of the operators available for each slot, see the section
on operators in the Master Rule Language (MRL) appendix of the BMC
Knowledge Base Development Reference Guide.
Alias formulas
13 Click OK to save the expression and close the Add Event Criteria editor.
The event selection criteria is displayed in the Event Selection Criteria section of
the Selector Details tab, as shown in Figure 82 on page 585.
Figure 82: Completed event selection criteria in Selector Details tab
14 To add more event selection criteria, click Add and repeat List item. on page 584
through List item. on page 585.
15 Click OK to save the event selector and its event selector group.
Alias formulas
You can add and edit alias formulas provided you
belong to the Full Access or Service Administrators group
have at least one cell connection to the BMC ProactiveNet Server
Several default alias formulas are provided out-of-the-box. For example, default
aliases for the BMC PATROL product are offered for PATROL events of class
PATROL_EV. These aliases can be used by the BMC Impact Integration for PATROL
product.
Working with Event Alias Formulas

This section provides details about how to create event alias formulas.
To create a new event alias formula

1 From the BMC ProactiveNet Administration Console menu bar, choose
Tools =>Event Alias Formulas.
585
Alias formulas
The Alias Formulas Editor window is displayed. It lists the connected cells in
the Cell list. It displays all current alias formulas for the selected cell in the list,
as shown in Figure 83 on page 586.
Figure 83: Alias Formulas Editor
The menu bar at the top of the window contains the following icons:
Icon
Purpose
to edit a selected alias formula
to create a new alias formula
to copy an existing alias formula to use as a template for creating a new alias formula
to delete a selected alias formula
to copy an existing alias formula
to paste an alias formula
Alias formulas
2 In the Cell list, select the cell you want to work on.
3 To add a new alias formula, click the New Alias Formula icon.
The Add Alias Formula dialog box is opened.
Figure 84: Add Alias Formula dialog
4 In the Formula Name text box, enter a name for the alias formula.
5 Under the Event Match Criteria label, in the Event Class box, select an event class
from the list.
When an event arrives at the cell, its event class has to match the event class or a
subclass of the event class before the alias formula is even considered.
6 (optional) In the Match Attributes box, choose attributes and enter values to refine
which events (within the event class) will generate aliases.
For each attribute you choose, select one of the conditional operators, as
described in Table 87 on page 588, and enter a value in the text box to further
define the events that are used to generate aliases using this formula.
587
Alias formulas
Table 87: Description of conditional operators

Conditional operators Description
anything
the attribute can contain any value and is not used as a selection criteria
If every attribute listed has anything that means that every incoming event that
belongs to the event class will pass through alias formula processing
contains
the characters you enter in the text box occur someplace in the value
has prefix
the value starts with the characters you enter in the text box
has suffix
the value ends with the characters you enter in the text box
equals
the value exactly matches the characters you enter in the text box
If you use more than one attribute, each condition must test true (the Boolean
operator between the selection criteria phrases is AND) before the alias formula
process is performed. For example, in Figure 85 on page 588, the search
phrase would read: Hostname contains SALLOG and IP address equals
555.22.19.105. Both conditions must be true for the event to be selected for alias
processing.
Figure 85: Example of match attributes
7 In the Alias Formula area, use the Attribute, Text, and Function buttons in any
order and as many times as needed to build the formula:
a To insert an attribute in the formula, click the Attribute button. The attributes
shown are those that belong to the event class you selected in the Event
Definition area.
When an attribute is selected, the control shows the attribute name, and the
preview area is updated to show the syntax of the formula as it currently exists.
Alias formulas
Tip
If your formula for a configuration item contains the mc_host slot with a host
name value, then the mc_host slot of the matching event definition should also
contain the host name value, not the IP address, of the configuration item. For
example, if you assign the mc_host slot in your formula the value
mycomputer.abc.com, then the mc_host slot of the incoming event should
contain the same host name value, not the IP address.
You can check with your system administrator for the correct Domain Name
System (DNS) resolution if the object represented by the configuration item
experiences host name resolution errors.
b To insert literal text (for example, a period, semi-colon, the word Oracle), click
on the Text button. In the text box, type the literal text that you want in the
alias formula.
Literal text appears in the first part of the alias formula with data type definitions.
c To insert a function that defines the data type and an expression in the
formula, click on the Function button. Type the function and choose the data
type.
For a list of functions you can use, see BMC Knowledge Base Development
Reference Guide .
d (optional) To change the order of the elements in the alias formula, select the
part of the formula you want to move and click the Move arrow button as
appropriate.
e (optional) To delete one of the elements in the alias formula, select the part of
the formula you want to delete and click the Delete button.
8 When the alias formula is complete, click Save.
To edit an event alias formula

1 Choose Tools => Event Alias Formulas.
2 In the Alias Formulas Editor window, select an existing alias computing formula.
3 Click the Edit Alias Formula icon.
4 In the Edit Alias Formula dialog box, make changes as needed.
5 When your changes are complete, click OK.
589
Alias formulas
To delete an event alias formula

1 Choose Tools =>Event Alias Formula s .
2 In the Alias Formulas Editor window, select an existing alias computing formula.
3 Click the Delete Alias Formula icon .
Devices with multiple IP addresses

BMC ProactiveNet 8.0 supplies aliases and alias formulas for all devices. However,
the alias only applies to the first device-IP association, when the device is associated
with multiple IP addresses. You have to create a custom alias formula to supply an
alias to any subsequent device-IP associations. For example, the following alias
formula associates the alias pn_vm-w23-sms29_<IPAddress> to a device with the
attributes EA_EVENT class and with the mc_object slot equal to testobj1:
BMC_SIM_MATCH_TABLE;
data_handle=966;
mc_udid='mc.pncell_vm-w23-rds847.ad85f87.0';
mc_creation_time=1255694215;
mc_modification_time=1255694275;
mc_modification_requestor=admin;
publish_env_id='';
ReadSecurity=[];
WriteSecurity=[];
name=Custom_AF1;
tag=alias;
input_match=['<EA_EVENT>','*','*','*','*','<testobj1>','*'];
ref_instances_classes=[EA_EVENT];
output_expressions=['sprintf("pn_vm-w23-sms29_%s",
[$1.mc_host_address])'];
END
To add/edit an alias formula associated with a component instance

1 Open a service model in a View window of the Services tab.
2 Select a component instance, right-click to display the pop-up, and choose Event
Alias Formulas to open the Alias Formulas Editor window.
Note
If the host names of the component instances are not in lower case, then you must
define a custom alias formula to associate the event with the CI.
3 Refer to the procedures described in this topic, Working with Event Alias
Formulas on page 585.
Creating new standard event management

policies
This section provides instructions for creating new standard event policies based on
default event management policy types.
If you want to create an event management policy based on a custom policy type, see
Creating and using user-defined policies on page 689.
Unless you want the event management policy to run continuously, you must
define a timeframe as described in How to create a new local timeframe on page

573.
Define an event selector and specify event selection criteria as described in How
to create an event selector and specify event selection criteria on page 581.
Table 88 on page 591 lists each standard event management policy type and the
page number of the procedure for each type.
Table 88: Standard event management policy types and procedures
To create this event policy...
See...
Blackout
To create new a standard blackout policy on page 593
Component Based Enrichment
To create a new component based enrichment policy on page 597
Closure
To add an agent to a profile on page 261
Correlation
To create a new correlation policy on page 609
Enrichment
To create an enrichment policy on page 613
Escalation
To create an escalation policy on page 618
Notification
To create a new notification policy on page 623
Propagation
To create a new propagation policy on page 626
Recurrence
To create a new recurrence policy on page 629
Suppression
To create a new suppression policy on page 632
Threshold
To create a new threshold policy on page 634
Timeout
To create a new timeout policy on page 638
Component Based Blackout
To create a new component based blackout policy on page 602
591
Creating a new standard blackout policy

A blackout policy specifies a period of time during which notifications about
incoming events that match the event specification criteria are ignored. The blackout
events, however, are logged. You can view the blackout events when you open the
collector that is specific to the events.
Typically you define a blackout policy for a specific time frame or time frames,
indicating when the policy is active, inactive, or both.
Although the events originating from the device are blacked out, you can still collect
data from the device.
Relation to Scheduled Down Time feature

Note
See Scheduling downtime on page 474 for information on the Scheduled Down
Time feature.
To stop data collection from a device or monitor, you can schedule a downtime
period that effectively makes the device or monitor unavailable.
Data-only users must use the Scheduled Down Time feature to manage data
collection. You schedule a device or monitor downtime through the BMC
ProactiveNet Administration or Operations console.
Event-only users must use the blackout policy to manage event notifications. You
define an event management policy through the BMC ProactiveNet Administration
console.
Tip
When you stop data collection through the Scheduled Down Time feature on a
monitored device, the monitors stop generating events. You do not have to schedule
a blackout policy in this instance. However, if external events are generated from the
same device components, then you should schedule a blackout policy to stop the
event notifications.
Event and data users must use both the blackout policy and the Scheduled Down
Time feature to stop external event notification and data collection.
You can simultaneously
schedule a downtime period for a device to stop data collection
apply a blackout event mangement policy to events that originate from the device
You can schedule the downtime period and the event management policy at
separate or overlapping time periods.
The following matrix outlines the interrelationship among the Scheduled Down
Time, managing data collection, and the event management blackout policy features.
It focuses on the impact on internal and external events, event views, and event rules.
Table 89: Relationship among scheduled downtime, managing data collection, and blackout policy
Scheduled downtime/
Managing data
collection On or Off?
Internal
events
generated?
External
Blackout
events
policy for
generated? monitored
events?
Events displayed in Event

View
Event rule
triggered?
On
Yes
Yes
True
internal (Blackout state)

and external events
external only
On
Yes
Yes
False
internal and external events internal and

external
Off
No
Yes
True
only external events only
external only
Off
No
Yes
False
only external events only
extermal only
When to use a blackout policy

You would schedule a blackout policy for events for several reasons. Some of them
include
upgrading the BMC ProactiveNet device
changing your network environment
reducing the volume of event messages displayed in the consoles
eliminate misleading events and notifications
during a maintenance window
To create new a standard blackout policy

1 From the Event Management Policies tab of the Administration View, expand
the By Policy Type folder.
2 Under the By Policy Type folder, select Blackout Policy.
3
Click the Add Policy button
593
A Selector Chooser dialog box is displayed.
4 From the Selector Chooser dialog box, choose the event selector that you want to
use for this policy and click OK.
The Blackout Policy Details tab is displayed in the details pane of the
Administration View as shown in Figure 86 on page 594.
Figure 86: Blackout Policy Details tab
5 In the Policy Name field, type a unique alphanumeric name for the event
management policy. The name must contain no spaces.
6 In the Description field, type a description of the event management policy.
7 To enable the event management policy, select the Enabled check box. If you do
not want to enable the policy at this time, you can return to this dialog box and
enable the policy later.
8 In the Policy Activation Timeframes section, define the periods of time the event
management policy should be active (when enabled) by performing the following
actions:
a Select one of the following choices:
To make the event management policy active continuously, select Always
Active. You would choose this option rarely, only under special circumstances.
To specify when the policy is active or inactive, select Define Activation
Timeframes. This is the typical option for scheduling blackout events.
The Active Timeframes and Not Active Timeframes selections are shown,
Figure 87: Policy Activation Timeframe panel
b If you selected Define Activation Timeframes, depending on how you want to

define the timeframe for your policy do one or both of the following:
To specify the periods of time when the policy should be active, select the
Active Timeframes check box and one or more timeframes from its
scrollable list.
To specify the periods of time when the policy should be inactive, select the
Not Active Timeframes check box and one or more timeframes from its
scrollable list.
595
Note
You can select both check boxes to create active and inactive time periods.
However, the inactive time period takes precedence over the active time period.
9 When specifying the time frames, you can indicate how you want to handle
blackout events at the start, during, and at the end of the timeframe schedule. The
actions under each timeframe period are mutually exclusive and are described in
During the processing phase, the blackout event policy evaluates each event for a
match based on its selector only once, when it arrives at the cell. To maintain
adequate system performance, the blackout policy does not evaluate events at the
start and the end of every active time frame.
Table 90: Actions for blackout events
Timeframe period
At start of Blackout Window
Action
Do not change status of existing events
This default option leaves all existing events in their current status.
Change status of existing open events to blackout
You would choose this option to reclassify open events, effectively
removing unneeded statuses that would no longer make sense
during the blackout time frame.
During Blackout Window
Keep incoming events and set their status to blackout

This default option converts all incoming matching events to
blackout status.
Discard incoming events
This option filters out all incoming blacked-out events so that you
do not have to see them.
Timeframe period
Action
At End of Blackout Window
Leave blacked-out events in blackout status

This default option maintains the blackout status of the events
received during the blackout window and those events whose
status was changed to blackout at the start of the blackout window.
Change existing blacked-out events to open status
This option changes all events in blackout status to open status. It
does not impact events in closed status. Choosing this option lets
you see events which arrived during the blackout time frame that
are still valid.
Note
Blackout event actions are applied to events based on their policy selectors when
the events first arrive at the cell. If you modify an event after it has been
processed by the cell so that it no longer matches its policy selector, the blackout
event action is still applied to the event based on the initial evaluation.
10 Click OK.
BMC ProactiveNet Administration Console saves the defined event management
policy, and it is displayed in the list of event policies for the selected event selector.
Creating a new component based enrichment policy

A component based enrichment policy enables you to enhance the event definition
of an incoming event that is already associated with a component through an
mc_smc_id or mc_smc_alias match. When you define the component based policy,
you assign specified slot values from a standard list of component slots
(BMC_BaseElement class) to matching slots in the associated event definition.
Whenever an event that matches the selection criteria is received, its definition is
automatically enriched by the specified component slot values.
To create a new component based enrichment policy

2 Under the By Policy Type folder, select Component Based Enrichment Policy.
3
Click the Add Event Policy
button.
597
The event selector controls which events are processed by the policy and,
consequently, which event slots are displayed in the Event fields list.
The Component Based Enrichment Policy Details tab is displayed in the details
pane of the Administration View as shown in Figure 88 on page 599.
Figure 88: Component Based Enrichment Policy Details tab
8 Assign a numerical value to the policy in the Execution Order combo box.
The numerical value indicates the order in which policies are automatically
executed. Policies are executed in ascending chronological order. A policy with
the lowest numerical value is executed first while the policy with the highest
numerical value is executed last. During the execution phase, policies with higher
numerical values always overwrite the preceding policies with lower numerical
values.
599
Example
You have defined four component based enrichment policies and have assigned
each a unique numerical value (1, 2, 3, or 4) in the Execution Order combo box.
The policy assigned the value 1 is executed first, followed in ascending numerical
order by policies assigned the values 2, 3, and 4. During the execution sequence,
the policy with the value 2 overwrites the policy with the value 1; the policy with
value 3 overwrites the policy with value 2; and the policy with value 4 overwrites
the policy with value 3.
You should assign higher numerical values to policies that you want to execute
last and lower values to policies that you want to execute first.
actions:
Active.
Timeframes.
The Active Timeframes and Not Active Timeframes check boxes are enabled.
scrollable list.
scrollable list.
Note
10 In the Component Based Event Enrichment Details tab, assign the component
slots to the matching event slots in the Match the Component and Event Slots
section.
Consider these guidelines before you make the assignments:
The list of event slots is dynamic insofar as it depends on the base event class
you chose in the selector. The list that you see always contains a subset of the
CORE_EVENT class. It also contains any additional slot or slots derived from
the subclass you specified as the base event class.
The list of component slots is static. The component slots are derived from the
BMC_BaseElement class.
You can view and edit a list of excluded event and component slots in the
%BMC_PROACTIVENET_HOME%\pronto\data\ix
\configurationItemPolicies\
configurationItemEnrichment.slotFiltering.properties file. You can specify

event and component slots to be excluded in the appropriate field:
excluded.event.slots and excluded component.slots. Add or update the slots
using a comma-separated list.
After updating and saving the
configurationItemEnrichment.slotFiltering.properties file, restart the jserver by
entering the following commands:
pw p e jserver
pw p s jserver
The component slot value overwrites any current value in the matching event
slot.
You must match slots of similar types: STRING with STRING, INTEGER with
INTEGER, BOOLEAN with BOOLEAN, and so forth.
Note
The table does not support the assignment of LIST or LIST OF slots.
To make the assignment, select a slot name in the Event fields column and, using
the arrow button, move it to the Assignment Table, where you match it with a slot
in the Component fields column.
11 Click OK.
BMC ProactiveNet Administration Console saves the defined component based
enrichment policy, and it is displayed in the list of event policies for the selected
event selector.
601
Creating a new component based blackout policy

A component based blackout policy specifies a period of time during which
incoming events that match the component selection criteria will be ignored. All
ignored events are logged.
Typically you define a blackout policy for a specific time frame or time frames,
indicating when the policy is active, inactive, or both.
To create a new component based blackout policy

2 Under the By Policy Type folder, select Component Based Blackout Policy.
3
The Component Based Blackout policy Details tab is displayed as shown in

Figure 89: Component Based Blackout Policy Details tab
8 Edit the component selection criteria by clicking Edit Component Selector to
open the Edit Criteria dialog box.
You can devise component selector criteria by specifying the component class, a
slot within the class, and a corresponding slot value. You can include multiple
conditions by using the AND operator.
603
Some example component selectors are shown below:

BMC_BaseElement($CI) where [$CI.Name contains 'HR_Workways']
BMC_BaseElement($CI) where [$CI.Name contains 'HR_Workways' AND
$CI.Department contains 'Warehousing']
BMC_BaseElement($CI) where [$CI.Name contains 'HR_Workways' AND
$CI.Company contains 'ENEL']
9 Enter the component selection criteria, and click OK.

actions:
Active. You would choose this option rarely, only under special circumstances.
Timeframes. This is the typical option for scheduling blackout events.
The Active Timeframes and Not Active Timeframes selections are shown,
Figure 90: Policy Activation Timeframe panel

scrollable list.
scrollable list.
Note
11 When specifying the time frames, you can indicate how you want to handle
blackout events at the start, during, and at the end of the timeframe schedule. The
actions under each timeframe period are mutually exclusive and are described in
During the processing phase, the blackout event policy evaluates each event for a
match based on its selector only once, when it arrives at the cell. To maintain
adequate system performance, the blackout policy does not evaluate events at the
start and the end of every active time frame.
Table 91: Actions for blackout events
Timeframe period
At start of Blackout Window
Action
Do not change status of existing events
This default option leaves all existing events in their current status.
Change status of existing open events to blackout
You would choose this option to reclassify open events, effectively
removing unneeded statuses that would no longer make sense
during the blackout time frame.
During Blackout Window
Keep incoming events and set their status to blackout

This default option converts all incoming matching events to
blackout status.
Discard incoming events
This option filters out all incoming blacked-out events so that you
do not have to see them.
605
Timeframe period
Action
At End of Blackout Window
Leave blacked-out events in blackout status

This default option maintains the blackout status of the events
received during the blackout window and those events whose
status was changed to blackout at the start of the blackout window.
Change existing blacked-out events to open status
This option changes all events in blackout status to open status. It
does not impact events in closed status. Choosing this option lets
you see events which arrived during the blackout time frame that
are still valid.
Note
Blackout event actions are applied to events based on their policy selectors when
the events first arrive at the cell. If you modify an event after it has been
processed by the cell so that it no longer matches its policy selector, the blackout
event action is still applied to the event based on the initial evaluation.
12 Click OK.
Creating a new closure policy

An closure policy closes a specified event when a separate specified event is received.
To create a new closure policy

2 Under the By Policy Type folder, select Closure Policy.
3
The Closure Policy Details tab is displayed in the details pane of the
Figure 91: Closure Policy Details tab
607

actions:
Active.
Timeframes.
scrollable list.
scrollable list.
Note
9 Click Edit Event Criteria.
The Add Event Criteria window is displayed.
10 In the Add Event Criteria window, specify event selection criteria for the event
type that you want to close and click OK.
11 To close only matching events that occur within a certain timeframe, check the
Close Events with Age Less Than check box and specify an amount of time. If the
Close Events with Age Less Than check box is not checked, there is no limit on
the time between the closed event and the closing event.
12 To suppress (drop) the closing event, check the Suppress the Closing Event
check box.
In this context, the closing event is the event that matches the selector criteria and
that closes the previously received events, which are identified in the Events to
Close section. For example, a client-stop event can be chosen to close a clientstart event.
When you choose to suppress the closing event, you are instructing the system to
drop the event that matches the selector and that closes the previously received
events in the Events to Close section. In the example, the client-stop event, after
closing the client-start event, would then be dropped.
13 To save the completed event closure policy, click OK.
policy, and it is displayed in the list of event policies for the specified event selector.
Creating a new correlation policy

A correlation policy relates one or more cause events to an effect event. If desired,
this policy can close the effect event. The cell maintains the association between these
cause-and-effect events.
To create a new correlation policy

2 Under the By Policy Type folder, select Correlation Policy.
3
609
The Correlation Policy Details tab is displayed in the details pane of the
Administration View, as shown in Figure 92 on page 611.
Figure 92: Correlation Policy Details tab
6 To enable the event management policy immediately, select the Enabled check
box. If you do not want to enable the policy at this time, you can return to this
dialog box and enable the policy later.
611

actions:
Active.
Timeframes.
The Active Timeframes and Not Active Timeframes lists are enabled.
scrollable list.
scrollable list.
Note
9 Complete a separate Cause Event tab as appropriate for each cause event that you
want to define.
Table 92 on page 612 describes each of the controls in the Cause Event tabs.
Table 92: Cause Event tab controls
Field name
Description
Enable check box
Select this check box to relate the cause events to the effect events; this
information is stored in the cell.
Edit Event Criteria button
Click this button to specify the selection criteria for the cause event.
Correlation Timespan check box
Select this check box and enter a time limit within which the cause
event must occur to produce the effect event.
Field name
Description
Close Effect Event radio buttons
Choose one of the following radio buttons to specify the

circumstances under which the effect event will be closed:
Upon Correlationas soon as events are associated (cause and
effect), the effect event is closed
On Cause Event Closurewhen the cause event closes, the effect
event is closed also
On Its Ownclosing the cause event has no consequence to the
effect event
Escalate Cause Event check box
select this check box to escalate the cause event to the specified
priority level
De-escalate Effect Event check box
select this check box to de-escalate the effect event
10 To save the completed event correlation policy, click OK.

Creating a new enrichment policy

An enrichment policy adds values for specific event slots if those slots are empty
when the event is received from the event source. An enrichment policy can also
reformat slots or normalize slot values.
To create an enrichment policy

2 Under the By Policy Type folder, select Enrichment Policy.
3
613
The Enrichment Policy Details tab is displayed in the details pane as shown in
Figure 93: Enrichment Policy Details tab

7 In the Policy Activation Timeframes section, define the periods of time that the
event management policy should be active (when enabled) by performing the
following actions:
Active.
615
Timeframes.
scrollable list.
scrollable list.
Note
8 Enable the following check boxes as necessary to assign appropriate settings:
Event Prioritythe relative priority to assign to the event (1 is a high priority)
Event Categorythe classification to assign to the event; categories include
AVAILABILITY_MANAGEMENT
CAPACITY_MANAGEMENT
CHANGE_MANAGEMENT
CONFIGURATION_MANAGEMENT
FINANCIAL_MANAGEMENT
INCIDENT_MANAGEMENT
OPERATIONS_MANAGEMENT
PROBLEM_MANAGEMENT
RELEASE_MANAGEMENT
SECURITY_MANAGEMENT
SERVICE_CONTONUITY_MANAGEMENT
SERVICE_DESK_MANAGEMENT
SLA_MANAGEMENT
Event Severitythe severity to assign to the event
Location to Setthe physical location of the object, such as a city
Services to Setthe service that the event is associated with
9 In the Message Text Format box, define the message slot enrichment for the event
as follows:
a From the list of available event slots in the Event Slot box, select an event slot
to which to add enrichment information and click Insert.
b To insert a a slot value into the message, either type the slot name surrounded
by % characters or select the slot name from the Event Slot list and click Insert.
The box is a standard text box. You can position the cursor and type or insert
text and slot references in any order. The Event Slot list and Insert button are
provided as a convenience so you do not have to remember the valid slot
names. The resulting string of characters in the Message Text Format box,
%<slot name>%, whether typed or inserted, is used as a template to create the
message (msg slot) for the event.
Repeat steps these steps to add more enrichment information to the event slot,
if necessary.
Note
The hidden and list of slots are not available for message enrichment.
To avoid unpredictable results when adding a text message, use no more than
one set of quotation marks.
10 To save the completed event enrichment policy, click OK.
Note
The enrichment policy is ineffective when an event is updated by the RATE process.
617
Creating a new escalation policy

An escalation policy raises or lowers the priority level of an event after a specified
period of time. A specified number of event recurrences can also trigger escalation of
an event.
For example, if the abnormally high temperature of a storage device goes unchecked
for 10 minutes or if a cell receives more than five high-temperature warning events
in 25 minutes, an escalation event management policy could increase the priority
level of the event to critical.
To create an escalation policy

2 Under the By Policy Type folder, select Escalation Policy and click OK.
3
The Escalation Policy Details tab is displayed in the details pane of the
Figure 94: Escalation Policy Details tab
619
actions:
Active.
Timeframes.
scrollable list.
scrollable list.
Note
9 In the Time Escalation section, shown in Figure 95 on page 621, use the
Timespan Before Priority is Escalated selectors to enter the number of a specified
period of time that must elapse before an event is escalated. The default time
period is seconds, but this time period can be changed to minutes, hours, or days
by selecting one of these time periods from the drop list.
Note
You can set Time Escalation or Rate of Event Arrival, or both. To set only one,
leave the fields of the other set to zero.
Figure 95: Time Escalation Controls
10 Choose one of the following radio buttons to determine how the priority of the
event will be escalated after the specified time has elapsed:
Levels to Escalate/De-escalate Priority ByChoose this radio button to
escalate or de-escalate the event by a specified number of levels after the time
period specified by the Timespan Before Priority is Escalated selector has
elapsed. Enter the number of levels that the event is to be escalated.
Set Priority to This ValueChoose this radio button to set the event to a
specified priority level after the time period specified by the Timespan Before
Priority is Escalated selector has elapsed. Choose the priority level from the
drop list.
11 (optional) To prevent the event from being escalated after it has been
acknowledged, select the Do not Escalate if Acknowledged check box.
12 (optional) To prevent the event from being escalated after it has been assigned,
select the Do not Escalate if Assigned check box.
13 In the Rate of Event Arrival section, shown in Figure 96 on page 622, in the
Number of Events Needed for Escalation selector, enter the number of events
that must occur before the event is escalated.
621
Note
You can set Time Escalation or Rate of Event Arrival or both. To set only one,
leave the fields of the other set to zero.
Figure 96: Rate of Event Arrival Controls
14 In the Timespan in which Events Must Arrive selector, enter the time in which
the events must arrive before the event is escalated or the event priority is
changed.
15 Choose one of the following radio buttons to determine how the priority of the
event will be escalated after the number of events have arrived within the
specified timespan:
Levels to Escalate Causal Event PriorityChoose this radio button to escalate
the causal event by a specified number of levels after the number of events
specified Number of Events Needed for Escalation selector have occurred
within the time period specified by the Timespan in which Events Must
Arrive selector. Enter the number of levels that the event is to be escalated.
Set Priority to This ValueChoose this radio button to set the event to a
specified priority level after the number of events specified Number of Events
Needed for Escalation selector have occurred within the time period specified
by the Timespan in which Events Must Arrive selector. Choose the priority
level from the drop list.
16 To save the completed event escalation policy, click OK.

Creating a new notification policy

A notification policy sends a request to an external service to notify a user or group
of users that the event has occurred.
For example, a notification event management policy might notify a system

administrator about the imminent unavailability of a mission-critical piece of storage
hardware.
Before you begin

You must add a notification service as described in How to add a notification service
(notification policies only) on page 575.
To create a new notification policy

2 Under the By Policy Type folder, select Notification Policy and click OK.
3
623
The Notification Policy Details tab is displayed in the details pane of the
Administration View, as show in Figure 97 on page 624.
Figure 97: Notification Policy Details tab
actions:
Active.
Timeframes.
scrollable list.
scrollable list.
Note
9 From the Notification Service drop list, select the service to use as the notification
mechanism. The default service is email.
10 In the Notification Source field, enter the source of the notification.
11 In the Add field, type the name of a person or group to notify. Click Add to add
the name to the Notify slot. Add more names or groups if necessary.
12 From the Event Status that will Notify Users list, choose the event status that you
want to trigger the notification.
13 In the Notification Subject field, enter the subject of the notification message. If
desired, you can use the Event Slot drop list to choose event slots to add to the
notification subject. Click the Insert button to insert the slots into the subject.
Enter a space before and after each slot that you add.
14 In the Notification Text field, enter the notification message. If desired, you can
use the Event Slot drop list to choose event slots to add to the notification
message. Click the Insert button to insert the slots into the message. Enter a space
before and after each slot that you add.
15 (optional) Select the Auto Acknowledge check box to automatically acknowledge
the event.
625
16 (optional) Select the Auto Assign check box to automatically assign the event to
the user you select from the list.
17 To save the completed event notification policy, click OK.

A propagation policy forwards events to other cells or to integrations to other products.
To create a new propagation policy

2 Under the By Policy Type folder, select Propagation Policy and click OK.
3
The Propagation Policy Details tab is displayed in the details pane of the
Figure 98: Propagation Policy Details tab
6 In the Description box, type a description of the event management policy.
actions:
Active.
Timeframes.
627

scrollable list.
scrollable list.
Note
9 In the Propagate to all of list, choose one or more cells.
Figure 99: Propagation cell list
10 In the Propagate to one of list, select one or more cells.

11 To save the completed event propagation policy, click OK.
Creating a new recurrence policy

A recurrence policy combines duplicate events into one event that maintains a
counter of the number of duplicates.
Note
All of the dup_detect slots on the incoming event must be the same for all events
that match the selector or the recurrence policy will not function.
Because PATROL integration has dup_detect set on the mc_origin_key and these
keys are unique, recurrence policies will not operate as expected for PATROL
integration events.
To create a new recurrence policy

2 Under the By Policy Type folder, select Recurrence Policy and click OK.
3
629
The Recurrence Policy Details tab is displayed in the details pane of the
Figure 100: Recurrence Policy Details tab
5 In the Policy Name box, type a unique alphanumeric name (with no spaces) for
the event management policy.
actions:
Active.
Timeframes.

scrollable list.
scrollable list.
Note
9 If you want to define a time window for events that are considered to be
recurring, check the Recurring Events Must Arrive Within this Timespan check
box and set the maximum time after the initial event within which an event must
arrive to count toward recurrence. If the box is not checked, there is no limit on
the time between duplicate events that are counted as recurring.
10 In the Slot Updates section, select any original event values that you want
updated by the latest recurrent event values.
11 To save the completed event recurrence policy, click OK.
Creating a new remote action policy

To set up automatic remote actions that are triggered by events, you must first define
a remote action policy using the remote action policy feature of the BMC
For instructions for creating a remote action policy, see Configuring and using
Remote Actions/Diagnostics on page 355.
Creating a new suppression policy

A suppression policy specifies the events that the receiving cell should delete. Unlike
a blackout event management policy, the suppression event management policy
maintains no record of the deleted event.
631
To create a new suppression policy

2 Under the By Policy Type folder, select Suppression Policy.
3
The Suppression Policy Details tab is displayed in the details pane of the
Figure 101: Suppression Policy Details tab
actions:
Active.
Timeframes.
scrollable list.
scrollable list.
Note
9 Click OK.
633
Creating a new threshold policy

A threshold policy specifies a minimum number of duplicate events that must occur
within a specific period of time before the cell accepts the event. For events allowed
to pass through to the cell, the event severity can be escalated or de-escalated a
relative number of levels or set to a specified level. If the event occurrence rate falls
below a specified level, the cell can take action against the event, such as changing
the event to closed or acknowledged status.
To create a new threshold policy

2 Under the By Policy Type folder, select Threshold Policy.
3
The Threshold Policy Details tab is displayed in the details pane of the
Figure 102: Threshold Policy Details tab
actions:
635
Active.
Timeframes.
scrollable list.
scrollable list.
Note
9 For the Number of Duplicate Events Received slot, supply a numeric value and
an associated time measurement to specify the threshold above which an event is
accepted.
10 Select one of the following radio buttons (The threshold-specific options
displayed on the tab change depending on which button you select.):
Hold Events Until Threshold is MetSelect this option to prevent creation of
any specified event until the number of events exceeds the threshold within the
specified time period.
If you select Hold Events Until Threshold is Met, the options shown in Figure
103 on page 637 are displayed. Specify whether to include allowing the last,
first, highest, or lowest severity event to pass and whether to acknowledge or
close the passed event when incoming (new) events fall below a specified low
threshold rate.
Figure 103: Hold Events options
Pass Events throughselect this option to create all events when they meet the
required threshold rate.
If you select Pass Events through, the options shown in Figure 104 on page 637
are displayed.
Figure 104: Pass Events Through options
Choose one of the following radio buttons to determine how the severity of the
event will be escalated or de-escalated:
Levels to Escalate/De-Escalate Event Severity ByChoose this radio button to
escalate or de-escalate the severity of the event by a specified number of levels

after the number of events specified Number of Duplicated Events Received
selector have occurred within the time period specified by the Timespan in
which Events the Must Arrive selector. Enter the number of severity levels that
the event is to be escalated.
Set Severity to This ValueChoose this radio button to set the event to a
specified severity level after the number of events specified Number of

Duplicated Events Received selector have occurred within the time period
specified by the Timespan in which Events the Must Arrive selector. Choose
the severity level from the drop list.
637
Note
From the Set Severity to This Value drop list, choose Critical, Non-critical,
Minor, Warning, or OK. Do not choose Unknown, as it is considered a status
rather than a severity.
11 To save the completed event threshold policy, click OK.
Creating a new timeout policy

A timeout policy changes an event status to closed after a specified period of time
elapses.
To create a new timeout policy

2 Under the By Policy Type folder, select Timeout Policy.
3
The Timeout Policy Details tab is displayed in the details pane of the
Figure 105: Timeout Policy Details tab
actions:
Active.
Timeframes.
scrollable list.
639
Enabling and disabling out-of-the-box standard event management policies
scrollable list.
Note
9 In the Timeout Event After field, enter a number of time periods that must elapse
before an event will time out. The default time period is seconds, but this time
period can be changed to minutes, hours, or days by selecting one of these time
periods from the drop list.
10 To save the completed event timeout policy, click OK.
Enabling and disabling out-of-the-box

standard event management policies
This section provides instructions for enabling and disabling out-of-the-box standard
event management policies.
For a list of out-of-the-box event management policies, see Out-of-the-box event
management policies on page 563.
For instructions on enabling out-of-the-box dynamic enrichment policies, see
Enabling out-of-the-box dynamic enrichment event management policies on page
653.
To enable or disable a standard event management policy

2 Under the By Policy Type folder, select the policy type for the out-of-the-box
standard event policy that you want to enable.
Out-of-the-box standard event policies are included under the following policy
types:
Closure Policy
Recurrence Policy
Suppression Policy
Timeout Policy
A list of out-of-the-box standard event management policies of that policy type

are displayed in the right pane of the Administration View as shown in Figure
106 on page 641.
Figure 106: List of event management policies
3 From the list of event management policies, select the policy that you want to
enable.
The Details tab for that policy is displayed in the details pane of the
Administration View.
4
On the BMC Impact Manager toolbar, click the Update Policy button
enable the Details tab to be edited.
to
5 Enable or disable the policy by selecting or deselecting the Enabled check box.
6 Click OK.
Creating a new dynamic enrichment event

management policy
This section provides instructions for creating a new dynamic enrichment event
management policy and for creating a new dynamic enrichment blackout policy.
Before you begin
641
Ensure that the timeframe referenced in your dynamic enrichment source file
exists. If it does not exist, you must define the timeframe as described in How to
create a new local timeframe on page 573.
Determine which event selector you want to apply to your dynamic enrichment
policy. If none of the out-of-the-box event selectors are appropriate for your
policy, define an event selector and specify event selection criteria as described in
How to create an event selector and specify event selection criteria on page 581.
Create a data enrichment source file as described in How to create and edit a
dynamic enrichment source file on page 576.
To create a new dynamic enrichment policy

2 Under the By Policy Type folder, select Dynamic Enrichment Policy.
3
The Dynamic Enrichment Policy Details tab, shown in Figure 107 on page 643,
is displayed in the details pane of the Administration View.
Figure 107: Dynamic Enrichment Policy Details tab
643
7 To enable the policy immediately, select the Enabled check box. If you do not
want to enable the policy at this time, you can return to this dialog box and enable
the policy later.
8 In the Execution Order field, if more than one policy exists, specify the order of
execution.
Note
When a new policy is created, the number shown in the Execution Order field
should be one greater the largest current execution order.
If two policies have the same execution order, they will run in indeterminate order.
actions:
Active.
Timeframes.
The Active Timeframes and Not Active Timeframes lists are displayed.
scrollable list.
scrollable list.
Note
10 If you do not want to accept the default event class, you can select an event class
in the Event Class field of the Match Fields
by clicking the ellipses button
section, selecting a new event class, and clicking OK.
The Event Class determines what slots are available in the Available Event
Fields column.
11 In the Class Chooser dialog box, select an event class and click OK.
12 In Available Event Fields column, select the slots that correspond to the match
fields in your dynamic enrichment source file. Use the left arrow button to move
those slots into the Match Fields column. You may select and move multiple slots
at the same time.
13 In Available Event Fields column, select the slots that correspond to the output
fields in your dynamic enrichment source file. Use the right arrow button to move
those slots into the Output Fields column. You may select and move multiple
slots at the same time.
WARNING
For example, if you were creating a file similar to the location.csv file that is
included with the product, you must select the Host slot as the Match Field and
the Location slot as the Output Field to correspond to the slots in the location.csv
file.
14 (optional) In the Match Fields section, activate the Match Tracing check box to
add diagnostic notes to the event, if necessary.
15 In the Match Table section, in the Type field, accept the default.
Note
Typically, you do not need to the change the value of the Type field. You can
override the default; however, you must use a unique tag within the given match
table.
16 In the Match Table section, in the Tag field, accept the default.
Note
The Tag field uniquely identifies the match table that will be used by the policy
instance.
You do not need to the change the value of this field. You can override the
default; however, you must use a unique tag within the given match table.
17 In the Match Table section, in the Data File field, do one of the following actions:
Type the path to the enrichment data source.
.. In the
To browse for the enrichment data source, click the ellipses button
File Chooser dialog box, select the dynamic enrichment source file appropriate
645
for your policy and click OK. For more information, see External enrichment
data sources on page 571.
18 In the Match Table section, in the File Format field, select one of the following
radio buttons to specify the type of data enrichment file to import:
Data file with this separatorChoose this radio button to import a flat,
delimited file, such as a .csv file. Enter a separator to delimit the data column in
the file.
For example, if you are using a .csv file, enter a comma (,) as the separator.
PMEP fileChoose this radio button to import a PMEP table and select the
appropriate PMEP format for your policy from the drop list:
Blackout
Blackout CSV
Location
Location CSV
Service
Service CSV
Text
Text CSV
Note
If you select the PMEP file button, the Event Class, Match Fields, and
Output Fields are autopopulated with predefined values and become
read-only.
19 Click OK.
If this is the first time a policy is saved, the a confirmation dialog box is displayed
Figure 108: Import confirmation
20 Click Yes.
A green check mark should be displayed in the Enable column next to the policy
in the event management policies list. (You may need to scroll the window to the
right to see the Enable column.) The policy also should show up in the tree in the
left pane of the BMC ProactiveNet Administration Console window.
21 Import the data from the dynamic enrichment source enrichment file as described
in Importing dynamic enrichment source on page 669.
To create a new dynamic enrichment blackout policy

2 Under the By Policy Type folder, select Dynamic Blackout Policy.
3

647
The Dynamic Blackout Policy Details tab is displayed in the details pane of the
Figure 109: Dynamic Blackout Policy Details tab
649

7 To enable the policy immediately, select the Enabled check box. If you do not
want to enable the policy at this time, you can return to this dialog box and enable
the policy later.
execution.
Note
actions:
Active.
Timeframes.
scrollable list.
scrollable list.
Note
10 If you do not want to accept the default event class, you can select an event class
in the Event Class field of the Match Fields
by clicking the ellipses button
section, selecting a new event class, and clicking OK.
The event class determines what slots are available in the Available Event Fields
column.
11 In the Class Chooser dialog box, select an event class and click OK.
12 In Available Event Fields column, select the slots that correspond to the match
fields in your dynamic enrichment source file. Use the left arrow button to move
those slots into the Match Fields column. You may select and move multiple slots
at the same time.
13 In Available Event Fields column, select the slots that correspond to the output
fields in your dynamic enrichment source file. Use the right arrow button to move
those slots into the Output Fields column. You may select and move multiple
slots at the same time.
WARNING
For example, if you were creating a file similar to the location.csv file that is
included with the product, you must select the Host slot as the Match Field and
the Location slot as the Output Field to correspond to the slots in the location.csv
file.
15 In the Match Table section, in the Type field, accept the default.
Note
Typically, you do not need to the change the value of the Type field. You can
override the default; however, you must use a unique tag within the given match
table.
16 In the Match Table section, in the Tag field, accept the default.
Note
The Tag field uniquely identifies the match table that will be used by the policy
instance.
You do not need to the change the value of this field. You can override the
default; however, you must use a unique tag within the given match table.
17 In the Match Table section, in the Data File field, do one of the following actions:
Type the path to the enrichment data source.
651
.In the
To browse for the enrichment data source, click the ellipses button
File Chooser dialog box, select the dynamic enrichment source file appropriate
for your policy and click OK. For more information, see External enrichment
data sources on page 571.
18 In the Match Table section, in the File Format field, select one of the following
radio buttons to specify the type of data enrichment file to import:
Data file with this separatorChoose this radio button to import a flat,
delimited file, such as a .csv file. Enter a separator to delimit the data column in
the file.
For example, if you are using a .csv file, enter a comma (,) as the separator.
PMEP fileChoose this radio button to import a PMEP table and select the
appropriate PMEP format for your policy from the drop list:
Blackout
Blackout CSV
Location
Location CSV
Service
Service CSV
Text
Text CSV
Note
If you select the PMEP file button, the Event Class, Match Fields, and
Output Fields are autopopulated with predefined values and become
read-only.
19 Click OK.
If this is the first time a policy is saved, the following confirmation dialog box is
displayed:
20 Click Yes.
Enabling out-of-the-box dynamic enrichment

event management policies
This section provides instructions for enabling out-of-the-box dynamic enrichment
event management policies.
You must export data from an external enrichment data source into the dynamic
enrichment source files provided with the product before you can enable any of the
out-of-the-box dynamic enrichment policies. For more information see, How to
create and edit a dynamic enrichment source file on page 576.
The dynamic enrichment source file for the PATROL Message Text Translation
policy (TextTrans.csv) is the only out-of-the-box dynamic enrichment source file that
includes valid data. You can enable PATROL Message Text Translation policy
without exporting data into TextTrans.csv. For more information about
TextTrans.csv, see Using the sample PATROL messaging text translation dynamic
enrichment source file on page 578.
Table 93 on page 654 lists each out-of-the-box dynamic enrichment event
management policy type and the page number of the procedure for each type.
653
Table 93: Out-of-the-box dynamic enrichment event policy types and procedures
To enable this event policy...
See...
Dynamic blackout
Enabling a dynamic enrichment blackout policy on page 654
Dynamic location enrichment
Enabling a dynamic enrichment location policy on page 657
Dynamic service contact enrichment Enabling a dynamic enrichment service contact policy on page 661
Dynamic PATROL message
translation
Enabling a dynamic enrichment PATROL message text translation

policy on page 665
Enabling a dynamic enrichment blackout policy

A dynamic enrichment blackout policy specifies external schedules that initiate
event blackout.
Before you begin

For the dynamic blackout policy to work, you must define the timeframes referenced
in the enrichment source file (blackout.csv). If any of the timeframes referenced in
the enrichment source file have not been created in BEM, then the policy will not run.
For instructions on defining timeframes, see How to create a new local timeframe on
page 573.
To enable a dynamic enrichment blackout policy

2 Under the By Policy Type folder, select Dynamic Blackout Policy.
The Dynamic Blackout Policy Details tab is displayed in the details pane of the
Figure 111: Dynamic Blackout Policy Details tab
655
3 On the BMC ProactiveNet Administration Console toolbar, click the Update

Policy button
to make the Dynamic Blackout Policy Details tab editable.
4 On the Dynamic Blackout Policy Details tab, select the Enabled check box.
5 In the Execution Order field, if more than one policy of this type exists, specify
the order of execution.
Note
management policy should be active and/or inactive (when enabled) by
performing the following actions:
Active.
Timeframes.
The Active Timeframes and Not Active Timeframes timeframe lists are
displayed.
scrollable list.
scrollable list.
Note
add diagnostic notes to the event to assist with trouble-shooting an event.
8 Click OK.
A confirmation dialog box is displayed, asking if you want to import data now, as
shown in Figure 112 on page 657.
Figure 112: Import Data Confirmation dialog box
9 Click Yes.
Enabling a dynamic enrichment location policy

The dynamic enrichment location policy adds location information to an event.
Some examples of uses for a dynamic enrichment location policy include:
Provides information to IT Operations so that they know which area/datacenter
the problematic technology is located in and can direct engineers more quickly to
the problem.
Enables IT Operations to build views in the BMC ProactiveNet Administration
Console of specific areas/data centers and understand at a glance where the

problems are.
Enables IT Operations to view reports in BMC Impact Reporting based on
location. For example, they can identify which locations which are generating the
most events.
If you are integrating with a service desk the location identifier can be passed
along with the rest of event, providing more useful information to the engineer
that will be assigned to handle the incident.
657
To enable a dynamic enrichment location policy

A list of out-of-the-box dynamic enrichment policies are displayed in the right
Figure 113: List of out-of-the-box dynamic enrichment policies
3 From the list of out-of-the-box dynamic enrichment policies, select

Location_Enrichment.
659

Policy button
to make the Dynamic Enrichment Policy Details tab editable.
5 To enable the policy, select the Enabled check box.

6 In the Execution Order field, if more than one of this type of policy exists, specify
Note
actions:
Active.
Timeframes.
scrollable list.
scrollable list.
Note
9 Click OK.
displayed:
10 Click Yes.
Enabling a dynamic enrichment service contact policy

The dynamic enrichment location policy adds contact information related to the
originating technology to an event.
For example, you can add a server administrators name and telephone number to
all events originating from a particular server
To enable a dynamic enrichment service contact policy

661


Service_Contact_Enrichment.
663

Policy button
to make the Dynamic Enrichment Policy Details tab editable.
5 To enable the policy, select the Enabled check box.

6 In the Execution Order field, if more than one type of this policy exists, specify
Note
actions:
Active.
Timeframes.
scrollable list.
scrollable list.
Note
9 Click OK.
displayed:
10 Click Yes.
Enabling a dynamic enrichment PATROL message text

translation policy
If you are integrated with PATROL, the dynamic enrichment PATROL message
translation policy enables you to substitute existing PATROL messages with
messages that are meaningful to your enterprise.
For example, you can use the PATROL message translation policy to change this
message:
NT_CPU.CPU_0.CPUprcrUserTimePercent parameter CPUCputil triggered on 90 <=
97 <= 100
to the following, more comprehensible message:

CPU Utilization is at 97%
665
Note
A sample dynamic enrichment service contact policy data source file,

TextTranslation.csv, is provided in the %PROACTIVENET_HOME%\admin\etc
\samples directory. The TextTranslation.csv file includes translations for many
common messages that will be useful in your enterprise. If you are integrated with
PATROL, BMC Software recommends that you take advantage of the data that is
already included in this sample file. For information about using the
TextTranslation.csv file, see Using the sample PATROL messaging text translation
dynamic enrichment source file on page 578.
To enable a dynamic enrichment PATROL message translation policy


PATROL_Message_Translation.
4
Click the Update Policy button
not want to enable the event management policy at this time, it can be enabled later.
execution.
Note
actions:
Active.
667
Timeframes.
scrollable list.
scrollable list.
Note
9 Click OK.
displayed:
10 Click Yes.

Before a dynamic enrichment policy can take effect, the data in the dynamic
enrichment source file must be imported.
Before you begin

If you are importing a file that contains more than 500 entries, before you begin the
import procedure, change the import_method_new parameter to true in the
%BMC_PROACTIVENET_HOME%\admin\etc\ix.properties file and restart the
BMC ProactiveNet Administration Console.
To import dynamic enrichment source

1 Ensure that the policy is enabled.
2 Select Import tab.
The Import tab is displayed as shown in Figure 122 on page 669.
Figure 122: Import tab
Table 94 on page 669 describes the uneditable fields of the Import tab. These
fields are for your information only.
Table 94: Import tab uneditable fields
Field
Description
Data File
Path to the enrichment data source
File Format
Type of file used by the policy
Last Action
Last time an import (replace or merge) was completed.
3 In the field opposite the Import button, select whether you want to Replace the
existing data in the cell or Merge new data with existing data in the cell.
669
4 Click Import.
The data is imported from the file into the cell.
5 Verify that the information has been uploaded by ensuring that the Last Action
information in the Import tab shows a completed upload message.

Perform the following procedure to verify that the policy that you created is running.
To verify that a policy is running

1 Send an event that should trigger the policy.
2 In the BMC ProactiveNet Operations Console, review the Historical Attributes for
the event in the Logs & Notes pane of the Event List Details notebook and verify
that your policy has executed.
Figure 123 on page 671 shows the Logs & Notes pane in the Event List Details
notebook. Click the More Info button to expand the pane. Figure 124 on page
671 shows the expanded pane and the events that verify that the policy was
executed properly.
Figure 123: Logs & Notes pane in the Details notebook
Figure 124: Expanded Logs & Notes page showing dynamic enrichment policy has
been executed

If you need to edit event selection criteria that you have already defined, follow
these steps.
671
To edit event selection criteria

1 From the event management policy tab navigation tree, select an event selector.
2
Click the Update Event Selector button
3 From the Event Selection Criteria section of the Selector Details tab, select an
event selection criteria in the list and click Edit.
The Edit button remains inactive until you select an event selection criteria.
4 Use the Edit Event Criteria editor to make the necessary changes to the
description, event class, or expression.
5 To save the edited event selection criteria, click OK.
6 From the Selector Details tab, click OK to save the edited event selection criteria
and the event selector.

If you need to delete an event selector that you have defined, follow these steps.
To delete an event selector

1 From the event management policy navigation tree, select the appropriate event
selector.
2
Click the Delete Event Selector button
The Delete Confirmation dialog box is displayed.

3 Click Yes.
The event selector is deleted.

This section lists some common problems encountered with event management
policies and some tools to assist you trouble-shoot problems not listed here.
Problem: The policy is not running

If the policy is not running, try the following:
Access the Policy Details tab for the policy and ensure that the Enabled check box
is selected.
(Dynamic enrichment policies only) Access the Policy Details tab for the policy
and ensure that the Match Fields and Output Fields contain the exact same
number of match fields in the same order as the associated data enrichment
source file.
(Dynamic enrichment policies only) Ensure that you have imported the data from
the data enrichment source file into the cell using the Import tab.
For policies that use a schedule, check to see if CellEventEnable=No is set in

mcell.conf. If it is then change it to CellEventEnable=Yes.
Problem: I receive an invalid data error when running a

dynamic enrichment policy
Access the Policy Details tab for the policy and ensure that the Match Fields and
Output Fields contain the exact same number of match fields in the same order as
the associated data enrichment source file.
Figure 125 on page 673 shows an example error message generated by dynamic
enrichment policy that has a mismatch between the match and output fields defined
in the policy and the number of columns included in the enrichment data source file.
Figure 125: Invalid data error: dynamic enrichment policy
673
Problem: I receive an error message when running a

dynamic enrichment blackout policy
Ensure that the timeframe defined in the data source enrichment file actually exists.
For information on creating valid timeframes, see How to create a new local
timeframe on page 573.
Figure 126 on page 674 shows an example error message generated by dynamic
blackout policy that has an invalid timeframes.
Figure 126: Invalid timeframe error: dynamic blackout policy
Problem: I have several thousand data records displayed

in the Dynamic Data Editor tab
If your Match Table contains several thousand data records (testing has noted 7500),
then when you try to execute a copy, paste, export, or print action, you can
encounter poor response times from the BMC ProactiveNet Server and find message
buffer full exceptions in the trace files.
To overcome this limitation, you can uncomment out the five sizing properties in the
%BMC_PROACTIVENET_HOME%\admin\etc\ix.properties file.
#data_handle_method_new=true
#IX will handle below specified chunk size data at a time. Default data
chunk size is 100
#data_handle_chunk_size=100
#sleep interval (in milliseconds) between the specified chunk size data
handling. Default Sleep interval is 500 milliseconds
#data_handle_sleep_interval=500
#IX will handle specified chunk size data at a time while paste action.
Default data chunk size is 25
#data_paste_chunk_size=25
#sleep interval (in Milliseconds) between the specified paste chunk size
data handling. Default Sleep interval is 1000 milliseconds

#data_paste_sleep_interval=1000
After modifying the ix.properties file, you must log out and log back in to the BMC
Troubleshooting tools for dynamic enrichment policies

You can use the following methods to trouble-shoot the dynamic enrichment policies
that you have defined:
Enable the Match Tracing check box in the Dynamic Enrichment Policy Details
tab to to add diagnostic notes to the event.
Access the History tab and check the Operations Log to determine which dynamic
enrichment policy added the information into the event.
675
14
Working with the dynamic data
editor
This chapter describes the Dynamic Data Editor.
Displaying the Infrastructure Management

node
By default, the Infrastructure Management node is not displayed in the Event
Management Policies tab or the Dynamic Data Editor tab in the BMC ProactiveNet
Perform the following procedure to display the node in these tabs.
To display the Infrastructure Management node

1 In a text editor such as Notepad, open the ix.properties file.
By default, the file is located in the following directory:
BMC_PROACTIVENET_HOME\admin\etc\
2 Change the value of the following parameter to True:
infrastructure_management_node_visibility
3 Save and close the ix.properties file.

The Infrastructure Management node is displayed in the Event Management
Policies and the Dynamic Data Editor tabs.
Chapter 14 Working with the dynamic data editor
677
Dynamic data definition using the Dynamic Data Editor
Dynamic data definition using the Dynamic

Data Editor
Dynamic data is contextual reference data that is stored in the event repository and
updated whenever the context changes while the cell is running. Its function is
similar to a global variable. You use the Dynamic Data Editor to define data class
instances for use in event management rules or service models. To define the data
instances, you must first define a data class. See BMC Knowledge Base Development
Reference Guide
for additional information about dynamic data.

You can use the Dynamic Data Editor to add a dynamic data instance to use as a
contextual variable in MRL rules and policies.
This section discusses the basics of how to navigate the Dynamic Data Editor.
Navigation pane
In the Dynamic Data Editor tab on the Administration View you can view the data
classes for a cell in a hierarchical tree, as illustrated in Figure 127 on page 679.
Figure 127: Dynamic Data Editor Navigation Pane
Table 95 on page 679 lists the parts on the Administration Tab Navigation pane.
Table 95: Administration tab navigation pane
#
Name
Description
Dynamic Data Editor tab
identifies the dynamic data editor
cell group icon
identifies a cell group
cell icon
identifies a cell
679
Name
Description
DATA class
root class to which all data classes belong
DATA subclass
data class defined as a subclass of the root class DATA

Data subclasses comprise the dynamic data tables in the
current cell.
view selection tabs
access to the events, services, or administration portions of the

console
Toolbar functions
Figure 128 on page 680 describes the toolbar buttons available in the Dynamic Data
Editor.
Figure 128: Dynamic Data Editor toolbar

The Data List of the Dynamic Data Editor tab in the BMC ProactiveNet
Administration Console provides an interface to assist you in working with a cells
dynamic data. From the Data List, you can
filter slots
sort data
Filtering slots
The Slot Quick Filter enables you to filter the displayed data list according to
specified slot criteria.
To filter slots
1
or the down arrow to its right to display

Click on the Slot Quick Filter button
the Slot Quick Filter dialog box, shown in Figure 129 on page 681, in which you
set the filter criteria.
Figure 129: Slot Quick Filter dialog box
2 From the Slot list, select the slot name.

3 From the Operator list, select the specific operator with which the filter acts.
4 In the Value box, enter the value with which you want to filter the Data List.
5 Click OK.
The filter you specified appears in place of the Slot Quick Filter button and the
data instances that meet the criteria are displayed in the Data List.
To toggle the quick filter on and off, click on the Slot Quick Filter button or on
the filter specifications currently displayed in place of the icon.
Sorting data fields

You can sort fields in the Data List using two methods: a multiple column sort order
or single-click on a column to sort immediately by that column.
To sort using multiple column sorting

Designating multiple columns for a sorting order is useful in resolving sort order
conflicts in the data list. Multiple column sorting functions as the following
illustrates. Set a multiple column sort order for a maximum of three columns with
these steps.
1 Right-click on a column head to display the Slot Order Indicator.
681
2 Select the order position desired for that column.

The Slot Order Indicator permits you to select a column as having no influence
on the sort order, or as first, second or third in the order.
Note
When you select the first column to include in your sort order the only options
available in the Slot Order Indicator are None and First. After you designate a
column as first in the sort order, the option Second is available in the Slot Order
Indicator when you right-click on the second column. The Third option is
available when you have designated a column as Second in the sort order.
3 Right-click next on the column you want to include in the sort order.
4 Select the order position desired for that column.
5 Repeat if you want to establish a third column in the sort order.
An alternative method of multiple-column sorting is to press the Ctrl key and singleclick on a header to add that column as the next column in the sort order. That is,
pressing Ctrl and single-clicking on a column sets it as the first in the sort order,
pressing Ctrl and single-clicking on the next column sets it as the second in the
sort order, and the third column is set as the third in the sort order by again
pressing the Ctrl key and single-clicking on the column header.
Currently only three columns can be included in the sort order. Pressing the Ctrl
key and single-clicking on a fourth column will designate it as third in the sort
order in place of the column previously designated as third. Also, pressing the
Ctrl key and single-clicking on a column that is part of a sort order will remove it
from the sort order.
The remaining columns in the designated sort order will reposition in the sort
order to replace the one that has been removed. For example, if you press the Ctrl
key and single-click on the column previously designated as first in the sort order,
it will be removed from the order and the two remaining will move from second
to first and from third to second in the new sort order.
Remember the following facts about sorting:
Only if there is a sorting conflict in the First sort column will the sorting be
resolved by use of the Second sort column.
The sorting will extend to the Third sort column only if there is a sorting
conflict in the Second sort column.
Establishing a multiple column sort simply ensures that any sorting conflicts
that may arise can be resolved to the third column level.
If you have established a multiple sort order in the Data List, clicking on one of
the sort order columns toggles that columns display between ascending and
descending order, as indicated by the small arrow next to the sort order number
in the column head.
To sort using single-click sorting

1 Sorting also can be done by single-clicking on the column you want to use as the
basis of your Data List sort. Even if a multiple sort order has been established, as
in the preceding section, you can click on any column that is not part of the
designated multiple sort order to reset sorting. This action establishes single
column sorting and the column on which you clicked is designated as the First,
and only, column in the new sort order.

From the Administration View, you can edit and manipulate a cells dynamic data
instances. All classes that are visible in the Administration View are subclasses of the
base data class DATA and MC_SM_DATA. Subclasses of MC_SM_DATA are shown in the
navigation pane, but data instances are not shown for these classes. Each cells data
class definitions reside in its Knowledge Base.
To define data instances in the Administration View for a custom data class, you
must first define that data class in the KB of the cell. For further information, see the
BMC Knowledge Base Development Reference Guide.
The Details pane for each data instance contains the following tabs:
Extended Details tab: Displays extended details of a selected data instance.
Internals tab: Displays the internal data as defined on the base DATA class.
The Data List of the Dynamic Data Editor tab of the Administration Console
provides an interface to assist you in working with a cells dynamic data. Right-click
on a data instance in the Data List on the right side of the Administration Console to
display the pop-up context menu. For instructions on adding a data instance, see
Adding a new data instance on page 683
Adding a new data instance

The following procedures focus on creating data instances by using the New and
New Copy menu options.
683
To create a new data instance with the New option

1 In the Data List of the Dynamic Data Editor, right-click on a data instance.
2 Select New.
The New tab is displayed in the Details pane next to the Extended Data and
Internals tabs.
The fields on the New tab are the slots for which data information can be entered
for this new data instance. The fields with a white background can be edited;
fields with an asterisk are required.
The unique data identifier slot (mc_udid) has a white background and is empty.
Note
The mc_udid slot information is assigned by the cell and BMC Software
recommends that you allow the cell to assign this value rather than entering one
of your own.
The cell assigns a valid value for this slot. The slot fields that are dimmed will be
completed automatically by the cell. The only exception to this is the list
associated with the Type field that permits you to select from specified options, as
Figure 130: Type field list
3 Click OK to complete the new data instance and close the New tab.
The success or failure of your attempt to create a new data instance will be
reflected in the message bar at the bottom of BMC ProactiveNet Administration
Console window. Figure 131 on page 684 illustrates a notification of a failed
attempt to create a new data instance.
Figure 131: Message bar
To create a new data instance with the New Copy option

1 When you use the New Copy menu option, certain of the editable fields contain
slot information that is copied from the selected data instance in the Data List, as
shown in below.
The New Copy menu option provides the same selection in the type field list as
the New menu option, as shown in Figure 130 on page 684.
When you have entered or edited the appropriate slot information, click OK to
create the new data instance and close the New tab. The success or failure of your
attempt to create a new data instance is reflected in the message bar of the BMC
ProactiveNet Administration Console window.
Editing slots
A class definition consists of one or more slots. Each slot has a data type and can
have specific attributes called facets that can control the values that the slot can have
or control aspects of a class instances processing. A class that is a subclass to another
class inherits all the slots of the parent class.
The Edit pop-up menu option enables you to update the selected data instance of the
current data list in the Data List display pane.
To edit slots
1 Select and right-click on the data instance and click Edit to display the Edit tab in
the Details pane of the Dynamic Data Editor tab.
685
The Edit tab contains the slot value information of the selected data instance.
Fields that can be changed have a white background.
2 To save the edited information and close the Edit tab, click OK.
Exporting data
From the Data List in the Administration View, you can export a data instance as a
file with a specified file name, in a format selected from a list, and containing all or
only the visible slot information available for the data instance. Multiple data
instances can be exported to the same file at the same time. Do this by selecting all
the data instances your want included to begin the export process.
To export data
1 Select a data instance and select the File => Export menu option or click on the
Export toolbar button to display the Export Policies dialog box, as shown in
Figure 132: Export Data dialog box
2 In the Format list, select the format for the export file, as shown in Figure 133 on
page 686.
Figure 133: Export Data dialog boxSelecting the data format
3 With the Visible Slots and All Slots option buttons, select whether you want to
include only the visible slots or all slots in the file.
If you select All Slots, the Filter for Importing check box is available.
4 In the To File box, accept the default or specify the file name and location for the
export file.
5 Click OK to create the export file and close the Export Data dialog box.
For illustration purposes, in Figure 134 on page 687, the export file mcdata.csv
containing information on all the slots for the selected data instance is created in C:
\Documents and Settings\zane\My Documents.
Figure 134: Contents of mcdata.csv
Figure 135 on page 687 illustrates an export file containing four data instances.
Figure 135: Export file containing four data instances
687
15
Creating and using user-defined
policies
This chapter describes how to create and how to implement user-defined policy
types. This chapter presents the following topics:
Understanding user-defined event policy types

Predefined policy types cannot cover all requirements of different BMC ProactiveNet
implementations.
To support specialized event processing, you can also define and implement custom
event policy types to do specialized event processing not supported by the
predefined policy types. For instructions about creating event policy types, seeUserdefined event policy type creation on page 691.
Understanding event processing rules (MRL)

for policy types
This section describes the form of policy type rules and discusses how they work.
Format of event processing rules for policy types

A typical event processing rule for a user-defined policy type has this form:
<rule-phase> rule-name:
using_policy
{
<POLICY_TYPE> ($POL) where [ ($POL.enabled == 1) AND
Chapter 15 Creating and using user-defined policies 689
Understanding event processing rules (MRL) for policy types
(($POL.active_timeframes == [] OR
tf_active($POL.active_timeframes)) AND
NOT tf_active($POL.except_timeframes)) ]
}
$POL.selector_ecf ($EV) where [ <other conditions> ]
{
<actions>;
opadd($EV, $POL.name, "action name", "");
} END
How a rule for a policy type is processed

The processing of a rule for a policy type is a follows:
1 The using_policy clause finds the applicable policy, that is, the instance of the
user-defined policy class (derived from IM_POLICY).
These class definitions describe the slots available in a policy class:
MC_DATA_CLASS :
POLICY ISA CORE_DATA
DEFINES {
name
: STRING, key = yes, read_only = yes;
description
: STRING;
enabled
: INTEGER, default = 1;
}; END
MC_DATA_CLASS:
IM_POLICY ISA POLICY
DEFINES {
active_timeframes : LIST_OF STRING;
except_timeframes : LIST_OF STRING;
selector_name
: STRING;
selector_class
: STRING;
selector_ecf
: ECF EVENT;
ordinal
: INTEGER, default=0;
}; END
2 The tf_active calls evaluates timeframes for the policy.

3 The selector ECF selects the event to process.
4 The actions implement the policy and the opadd call adds an entry to the
operations log of the event.
Sources of information about rules

You can get more information about rules for policy types and how to create them
from these sources
For...
See...
examples of rules for policy types
the pre-defined policies in .../kb/rules/im_internal.mrl.
For...
See...
definitions of the MRL constructs and

primitives for policy rules
BMC Knowledge Base Development Reference Guide

If you want to create a new user-defined event policy to perform specialized event
processing, first, you must define a new event policy type. An event policy type is a
data class, derived from that defines the distinct type of event processing to be
performed.
Creating user-defined policy types

To define a new user-defined policy type, you must do the following things.
Table 96: Policy Type Creation process
Step
Task
Topic
Define a new policy data class that describes the policy

type and copy it to the Knowledge Base of each BMC
IM instance to use the user-defined policy.
Defining the policy data class for a new

policy type on page 691
Define the presentation names that you want to appear

in user interfaces for the policy type in a ix.properties
configuration file.
Defining presentation names for a new

policy type on page 693
Create a new rule that defines the event processing

done by the policy type and copy it to the Knowledge
Base of each BMC IM instance to use the policy.
Creating the event processing rule(s) for

a new policy type on page 694
Defining the policy data class for a new policy type

To create a new policy type, first you must define a data class derived directly from
the IM_BASE_CUSTOM_POLICY base class. This policy data class describes the
policy types data. It also provides the template of data fields (slots) used by BMC IM
to generate the BMC ProactiveNet Custom Policy Details panel in which users
specify the processing details for a policy of that type.
To define a new policy data class

1 Using a text editor, open the appropriate BAROC language file in the Knowledge
Base.
Because the IM_BASE_CUSTOM_POLICY base class is defined in .../kb/class/
im_policies.baroc file, you must define the new policy type in a separate file
that is loaded for compilation after .../kb/class/im_policies.baroc file (it is
listed after the im_policies.baroc in the .../kb/class/.load file list).
2 Define the new policy data class derived directly from the
IM_BASE_CUSTOM_POLICY base class.
a Create the new class slots. You can create slots of these types:
ENUMERATION
INTEGER
STRING
LIST OF
No other slot types are supported in custom event policies.

b Define the class slots in the order that you want them to appear in the BMC
ProactiveNet Custom Policy Type panel.
The BMC ProactiveNet Custom Policy Details panel created from the policy
type will have a field for each slot added to the IM_BASE_CUSTOM_POLICY
class. The interface fields appear in the same order as the slots are defined in
the class definition.
See the BMC Knowledge Base Development Reference Guide for detailed
information on creating new classes.
3 Save the edited file after defining the new policy type (data class).
4 Add and entry for the new file that you created to the compiler load list in the .../
kb/class/.load file after the entry for the ../kb/class/im_policies.baroc file, which
contains the base policy data class that the new policy type references.
5 Recompile the BMC Impact Manager instances Knowledge Base (KB) after
defining the new policy data class.
For more information on compiling a KB, see Compiling a Knowledge Base
in the BMC Knowledge Base Development Reference Guide.
6 Finally, you must copy the changed KB to every BMC Impact Manager instance
(cell) that will use the new policy.
Verifying that you created the class successfully

If you created the class successfully, you should be able to see it in the By Policy
list and the Custom Policy Details panel.
Next, define user-friendly presentation names to appear in the user interface for the
policy type and its slots.
Defining presentation names for a new policy type

If you want user-friendly presentation names to appear in the user interface for the
policy type and its slots instead of the internal names, you must:
define presentation names for the policy type in a resource file
list the resource file for the policy type in the BMC ix.properties file
To define presentation names for a policy type

1 Create a resource file for the policy type to list the policy type and each slot with
its assigned presentation name. The resource file name must have the .properties
file extension.
2 Edit the resource file to add an entry for each presentation name assignment.
a To define the presentation name (label) for the policy type, add a line with the
following format to the resource file:
CLASS.<
policy type name
>=<
policy type presentation name
> Policy
b To define the presentation name (label) used for a slot, add a line with the
following format to the resource file.:
SLOT.<
policy type name
>.<
slot name
>=<
slot presentation name
>
3 Place the resource file in the installDirectory \ admin\lib\lang\kbinfo directory.
a Add the base name of the resource file to the value of kb_info_resources
parameter in the installDirectory \admin\etc\ix.properties file using this format:
kb_info_resources=<resource file name>,kb_core_resource,
kb_deprecated_resource
The defined presentation names will display in the Event Management Policies
tree, the Policy Type picker window, and in the Policy List panel. Any slot or
policy type for which a presentation name is not defined displays its internal
name.
The event policy details tab for all user-defined policy types is Custom Policy
Details.
Creating the event processing rule(s) for a new policy type

Before you can define an event policy based on the user-defined policy type that you
created, you must:
create a new Knowledge Base rule or rules to define the event processing done by
the policy type
copy the rule or rules to the Knowledge Base of each BMC IM instance on which
the user-defined policy will run
Event processing rule requirements

The event processing rule or rules that you define for the new user-defined policy
type must:
do dynamic selection (use the using_policy clause)
reference the policy data class that describes the new policy type
To create the event processing rule for a new policy type

1 , Add a new file in the .../kb/rules directory, for example, my_policies.mrl, for the
new event processing rule or rules for the new policy type.
2 Edit the policy MRL file and write the event processing rule for the appropriate
rule phase.
For more information, see
Evaluation order of event policy types on page 570
Understanding event processing rules (MRL) for policy types on page 689
See the MRL for the pre-defined policy types in ...\kb\rules
\im_internal.mrl file.
3 Add the file name for the new rule or rules to the compiler load list in the ...\kb
\rule\.load file.
4 Compile the cell instances Knowledge Base (KB) after defining the rule for the
policy type.
For more information on compiling a KB, see the BMC Knowledge Base
Development Reference Guide.
5 Copy this KB change to every cell instance that will use a policy based on the new
policy type.
The definition of the policy type is complete and users can now create policies
based on it in the Custom Policy Type panel.
16
Working with BMC ProactiveNet
Infrastructure Management
Infrastructure Management makes it easier for administrators with a Full Access or
Service Administrator role to monitor and manage BMC ProactiveNet infrastructure
components in a real-time service model.
These infrastructure components include cells, servers, and integrations. In the
Infrastructure Management interface, you can perform actions on these components,
such as editing configuration and log files and packaging support files for
troubleshooting purposes. Users assigned to Full Access, Service Administrator, or
other Admin groups could remotely manage a subset of BMC ProactiveNet
Infrastructure Management components and applications. In the Infrastructure
Management tab on the Administration tab of the BMCProactiveNet Administration
Console, these users could manually launch remote actions (stop, start, pause, and so
forth) by selecting the component, right-clicking to open the pop-up menu, and
choosing the action from a list of available ones. The availability of the actions
depended on the user role and the type of component or application.
Default BMC ProactiveNet Infrastructure

Management service model
The default BMC ProactiveNet Infrastructure Management model consists of logical
groupings of BMC infrastructure applications and components. Upon installation
certain components send registration events and become automatically registered
with the BMC ProactiveNet Infrastructure Management model.
Chapter 16 Working with BMC ProactiveNet Infrastructure Management 697
Default BMC ProactiveNet Infrastructure Management service model
Gray indicates that the object is a logical grouping, components whose status is
unknown to the Impact Administration cell. Only registered components are
viewable in the Find window and services graph. The arrows indicate the direction
(provider to consumer) of the event feed. A dotted line indicates that the relationship
is inactive.
The following versions of BMC components register with this service model. They
can be added as components instances to the respective logical group.
Table 97: Supported application groups
Group Id
Name
100
EM_CELL
101
EM_SERVER_1
102
EM_SERVER_2
103
SIM_CELL
104
SIM_SERVER_1
105
SIM_SERVER_2
112
PS (BMC Impact Publishing Server)
120
Adapter
121
LOG_FILE_ADAPTER
122
SNMP_ADAPTER
123
WINDOWS_EVENT_ADAPTER
124
SYSLOG_ADAPTER
Walkthrough
Group Id
Name
125
TCP_ADAPTER
126
TELNET_ADAPTER
127
UDP_ADAPTER
142
IBRSD
152
ARS_SD
154
BiiZ
156
SLM
160
EM_Server_Standby
Roles and permissions

The following group roles have full write permission to the components and features
of the BMC ProactiveNet Infrastructure Management subtab:
Service Administrators
Event Administrators
Full Access
Only members of these groups can view the BMC ProactiveNet Infrastructure
Management subtab.
For information about assigning roles, see Defining or editing roles and
permissions on page 500.
Walkthrough
This section provides a walkthrough of BMC ProactiveNet Infrastructure
Management, highlighting its main features. You can use this walkthrough to learn
about and become familiar with BMC ProactiveNet Infrastructure Management.
Displaying the out-of-the-box real-time service model

BMC ProactiveNet Infrastructure Management automatically deploys a BMC
infrastructure service model, called BPPM Infrastructure. It consists of logical
Walkthrough
groupings of BMC services and applications, together with registered components

that send all relevant information and latest statuses. The out-of-the-box service
model reflects the real-time states of the registered components.
To display the infrastructure service model

1 In the BMC ProactiveNet Administration Console, click the Administration tab.
2 In the icon bar at the top of the navigation area on the left, click the BMC
ProactiveNet Infrastructure Management icon
(the wrench or spanner icon).

3 Under Find Infrastructure Components in the bottom pane of the navigation area,
choose Find to list the services and applications.
4 The logical groupings of components and applications are displayed, along with
registered components.
Alternatively, you can open the BMC ProactiveNet Infrastructure Management
group to display the navigation tree, as shown in the following figure.
BMC ProactiveNet Infrastructure Management navigation pane
Walkthrough
5 Locate the BMC ProactiveNet Infrastructure object in the Find list, and then, using
the mouse, click and drag it into the graph viewing area in the top right pane to
reveal the service model.
You can also choose to select BPPM Infrastructure in the navigation tree under
BPPM Infrastructure Management to display it in the graph viewing area.
You may need to click the Orientation icon
at the top of the graph viewing area to reposition it vertically.

The gray-colored icons represent logical groupings, components whose status is
unknown to the Impact Administration Cell.
Sampling context-sensitive information

The BMC ProactiveNet Infrastructure Management interface offers a range of contextsensitive information that you can access from right-click pop-up menus and multilayered notebook tabs.
For example, you can expand the model and select a component under the SIM Cells
heading.
Click the leaf component under SIM Cells to select it.
Click the Details tab. Click the subtabs such as General, Status, Priority and Cost,
Advanced, RelatedComponents, SLM, and Schedule. These tabs provide

component specific information.
Click the Administer tab. Click the subtabs such as Configuration, Logs, and
SupportPackage. You can access the Workload and Components tabs if you have
selected either a SIM or an EM cell server.
Click Edit Component in the Details=>General tab and change a property of the
component.
Status
In the Status subtab, you can view the applicable status levels of the component:
Service Level Agreement and computation statuses.
Walkthrough
Advanced
In the Advanced subtab, you can view information on identification, creation and
modification time, and read/write permissions for groups for the selected object.
Related Components
In the RelatedComponents subtab, you can retrieve status causes, possible problems,
providers, and consumers of the selected component type. You can modify the
relationship by selecting Edit Relationship..., which opens the Edit Relationships
dialog where you can add, modify, or remove relationships. Using the right-click
menu options, you can highlight a retrieved component in the list, and add a link to
the navigation tree by choosing the Add Navigation Link option.
This subtab also lets you view other components that have relationships with the
selected component.
SLM
In the SLM subtab, you can list and view the details of Service Level Management
agreements assigned to the component.
Schedule
In the Schedule subtab, you can view the times when the component is in service
together with its priority costs when it is in service and when it is out of service.
Managing files on remote systems

From the BMC ProactiveNet Infrastructure Management interface, you can edit and
save the configuration and log files of other applications and services that are
running on remote systems.
To edit and save configuration files

1 Click the leaf component under a service or an application, such as a service
impact management cell, to select it.
2 From the notebook tabs, choose Administer => Configuration.
The drop list reveals the configuration files of the selected component.
3 To modify a file, select it from the list, and click Edit.
Walkthrough
4 In the Credentials dialog box, enter the credentials of the remote system, and click
OK.
The configuration file is displayed in the editor.
The Additional command credentials check box applies mainly to UNIX systems,
where you may need to log into the system under one user account, but then
switch to another user account (for example, root) to execute the action.
5 Edit the file.
6 When you are done, you can click either of the following:
File => Save a Copy to save a copy of the file to your local system
File => Update Original to update the file on the remote system
To edit and save log files

1 Click the leaf component under a service or an application, such as a service
impact management cell, to select it.
2 From the notebook tabs, choose Administer => Logs.
The drop list reveals the log files of the selected component.
3 To modify a file, select it from the list, and click View.
4 In the dialog box, enter the credentials of the remote system, and click OK.
The log file is displayed in the editor.
5 Edit the file.
6 When you are done, click File => Save a Copy to save a copy of the file to your
local system.
You cannot update a log file on a remote system. You can save it only to the local
system.
Packaging support files

You can package selected debug files to help troubleshoot customer cases. BMC
ProactiveNet Infrastructure Management automatically packages the selected files
into a zipped file.
Walkthrough
To package support files

1 Click on a component in the service model.
2 From the notebook tabs, choose Administer=>Support Package.
3 In the Destination field, enter the file path where the package should be saved on
the local system. You can use the Browse button to navigate to the directory.
The file name of the support package is created automatically.
4 ( Optional ) Enter a tracking number in the Issue Number field.
5 ( Optional ) Enter a description of the issue in the Description field.
6 Click Create Package.
7 Enter the credentials of the remote system from which you are retrieving the files.
A pop-up progress indicator shows the status of the retrieval. If it completes

successfully, go to the specified directory and review the contents of the zipped
package. The file contents vary based on the type of component.
8 Repeat steps 1 through 7 for a server component, verifying that the file contents of
its zipped package are different from those of the service impact management
cell.
Launching remote actions

From the BMC ProactiveNet Infrastructure Management interface, you can execute
actions through the right-click pop-up menus on components and applications that
are running on remote systems.
For this exercise, you must have a registered cell component installed on a remote
system.
Walkthrough
To launch remote actions

1 Right-click the leaf component under a service impact management cell or event
management cell to select a cell residing on a remote system.
2 Choose Actions to display a list of all possible actions for that component.
3 Choose Stop Cell Server Process, click Stop, and enter the logon credentials for
the remote system.
If the selected component resides on an Microsoft Windows system, your login
credentials should have administrative rights to the system. The Additional
Command Credentials are needed check box is disabled.
When the component on the remote system has stopped, its status changes to
Unavailable.
4 Return to the BMC ProactiveNet Infrastructure Management interface, right-click
the service impact management cell component to display the pop-up menu, and
choose Actions => Start Cell Server Process.
5 Verify that the cell has started--for example, you can execute an mcstat command
to check the cell's status. Then you can verify that the status of the selected
component is changed to OK.
6 Repeat steps 1 through 5 for a BMC ProactiveNet Server component, such as
publishing server or IBRSD.
The actions permitted on the server component are limited to Stop Process and
Start Process only.
You can also launch remote actions for selected components by clicking one of the
Action toolbar icons of the BMC ProactiveNet Infrastructure Management view.
Depending on the type and state of the selected component, you can choose from
among the following actions:
Start Cell Server Process (Start)

Stop Cell Server Process (Stop)
Restart Cell Server Process (Restart)
Pause Events Admittance (Pause)
Resume Events Admittance (Resume)
Set to Active
Set to Standby
Different actions are enabled based on the status and type of component. For
example, if a component in an unknown state is already started and you choose
Actions => Start, you receive a status message notifying you that the component
is started already. For more information, see Remote actions on page 728.
Common BMC ProactiveNet Infrastructure

Management tasks
This section describes the most common BMC ProactiveNet Infrastructure
Management tasks.
Navigating the interface

In the Administration tab view of the Administration Console, select the BMC
ProactiveNet Infrastructure Management subtab, represented by the wrench icon:
In the Class drop-down list, click All if it is not already displayed.

Click Find to open the list of logical groupings and registered components in your
infrastructure.
Logical groupings and registered components are depicted by different icons:
Icon
Definition
logical services grouping
SIM cell
Icon
Definition
SIM cell server 1
SIM cell server 2 (high availability implementation)
SIM cell server standby (high availability implementation)
EM Cell
EM cell server 1
EM cell server 2 (high availability implementation)
BEM cell server standby (high availability implementation)
Publishing Server
Integration for BMC Remedy Service Desk
Select the BPPM nfrastructure grouping, which contains the default infrastructure
model, and drag-and-drop it on to the graph viewing area. You may need to select
the Orientation icon to display it along a vertical axis.
Multiple graphs
You can display multiple graph views. For example, you can select registered
components from the Results list in the navigation pane, and drag-and-drop them on
the graph viewing area, creating new graph views. You can switch from one view to
the other by selecting the tabs at the top of the graph viewing area.
Navigation tree
To help organize your model, you can display and manipulate the grouping and
component hierarchy in the navigation tree view under the BPPM Infrastructure
Management heading.
You can select objects in the navigation tree and display them in the graph viewing
area.
You can drag objects from the graph viewing area and drop into the navigation tree,
creating a navigation link between the two.
Tip
You can press the CTRL or SHIFT key and then click an object in the navigation tree
to display the object in the graph viewing area without closing any displayed objects.
You can create customized subgroups under the BMC ProactiveNet Infrastructure
Management heading. After selecting the heading, right-click to open the Add a sub
group menu item.
After you define your group, you can drag-and-drop component objects into it.
Displaying and understanding the Details and

Administer tab data
The Details subtabs display information that identifies the characteristics of the
selected component and returns its status. They let you perform common actions,
such as changing provider-consumer relationships between components. The
Administer subtabs display specific infrastructure information and let you perform
unique infrastructure actions, such as editing configuration and log files and
collecting debug files for troubleshooting.
To view data about an object in the interface, first select it. Then you can scan the
corresponding subtabs under Details and Administer. To view information on one of
the Administer tabs, the selected object must be a registered infrastructure
component, not a greyed-out logical services group icon.
Details tab data

The Details tab displays the subtabs and data
General
In the General subtab, you can view the name, class, and subtype of the selected
object. Depending on the subtype, you can also view other slot values, as described
in Table 98 on page 709.
Table 98: Slot values: Details: General subtab

Section
Slot
Description
Component
Name
Name of the component that you have selected

under BPPM Infrastructure in the navigation tree
or in the service model in the Service Model View.
Class
The type of component that you have selected
Subtype
Short Description
Description
Editable Here
contains a Boolean Yes/No indicator that says

whether the selected component object can be
edited in the BMC ProactiveNet Administration
Console.
BPPM Infrastructure Management only contains
objects that are not published. Therefore, Editable
Here is always set to Yes in BPPM Infrastructure
Management.
Master Repository
specifies the data source of the component object.

For example, component objects that originate from
a direct feed source, such as BMC IX, mposter, or
an MRL, are designated in this format: CellcellName. The default name for BPPM
Infrastructure Management is Cell-Admin.
Run State
the current state of the object, which helps to

determine its status, its icon shape, the icon's color,
as well as which actions can be performed against
the object. This slot value is updated whenever the
component changes its state, from start to stop,
from start to paused, from stop to start, and so forth.
Host
host name of the computer where the component is

installed
Port
Port number through which the BMC ProactiveNet

Server communicates with the host where the
component is installed
Data Destinations
Started Date
Owner
Role
indicates whether a component, such as a cell

server, is standalone or, in an HA pair, either
primary or secondary.
Owner name
the individual responsible for the component
Owner Contact
the contact information for the owner of the

component
Section
Slot
Release
Environment
Description
Release
Build
Cells and Cell Servers
Only
From the General subtab, you can click Edit Component to open the Edit Service
Component dialog in which you can modify the component's properties.
Status
In the Status subtab, you can view the applicable status levels of the component:
Service Level Agreement and computation statuses.
Advanced
In the Advanced subtab, you can view information on identification, creation and
modification time, and read/write permissions for groups for the selected object.
Related Components
In the RelatedComponents subtab, you can retrieve status causes, possible problems,
providers, and consumers of the selected component type. You can modify the
relationship by selecting Edit Relationship..., which opens the Edit Relationships
dialog where you can add, modify, or remove relationships. Using the right-click
menu options, you can highlight a retrieved component in the list, and add a link to
the navigation tree by choosing the Add Navigation Link option. You can view the
events associated with the component.
This subtab also lets you view other components that have relationships with the
selected component.
SLM
In the SLM subtab, you can list and view the details of Service Level Management
agreements assigned to the component.
Schedule
In the Schedule subtab, you can view the times when the component is in service
together with its priority costs when it is in service and when it is out of service.
Administer tab data

The Administer tab for BMC ProactiveNet Infrastructure Management displays the
following subtabs.
Configuration
The Configuration subtab lists the editable configuration files of the selected
component. You can retrieve these files, even those associated with components on
remote systems. Click Edit. Then enter the logon credentials for the system where
the component resides. (On UNIX, your login account must have permission to
access the target system. On Microsoft Windows, you must have administrative
privileges on the system.) The file opens in a default text editor.
You can edit any supported configuration file of an infrastructure component. The
type of file varies with the component, but the files include:
mcell.dir file
.conf files
filter files
selector files
mapping files
trace.conf files
cell_info.list file
You should know the parameters of the file before trying to edit it. Refer to the
component's respective documentation.
You can save the edited configuration file to a local or remote system. If saving to a
local system, you can specify a different file path. If saving to a remote system, you
update the configuration file in its current directory path. You cannot save it to a
different file path.
Logs
Similar to configuration files, you can open and annotate log files of components on
local systems in the Log subtab. You cannot save an edited or update a viewed log
file to a remote system, however. You must save it to the local system.
Support Package
In the SupportPackage subtab, you can prepare a zipped package of predefined
support files for troubleshooting purposes. For more information, see Creating the
support package on page 722.
Workload
The Workload subtab dynamically tracks the event activity of the cell server
component. It presents counts, averages, and percentages of different event actions,
such as sent, received, dropped, and removed. You can refresh the table by clicking
the Refresh button.
Components
The Components subtab dynamically tracks the component instances that send
events to the selected object. You refresh the table by clicking the Refresh button.
This subtab view is available for both service impact management and event
management cell servers.

To open the Edit Relationships dialog box, select an infrastructure object in the graph
area, and then perform one of the following actions:
Select the Related Components subtab from the Details notebook tab. Click the
Edit Relationship button.
Click Edit => Edit Relationship.

Click the Edit Relationship toolbar icon.
The Edit Relationships dialog box is opened. The following figure shows an open
Edit Relationships dialog box with a selected service impact management cell
opened for editing in the Edit This Relationship subdialog.
The Edit Relationships dialog box contains the fields listed in the following table:
Table 99: Edit Relationship dialog: field descriptions
Field
Description
Component Name
name of the selected infrastructure component
Related Component Type
identifies the infrastructure component subtype that

has a consumer or provider relationship to the
selected component and for which you want to search
Relationships
lists the consumer, provider, or both consumer and

provider relationships of the selected component
subtype and component
Component
identifies the infrastructure object related to the

selected component
Direction
indicates the event flow of the object relationship. A

consumer direction indicates that the component
object receives events and data from the selected
component. A provider direction indicates that the
component object sends events and data to the
selected component
State
identifies current state of the relationship: active or

inactive
Type
specifies the class that contains the relationship type
Propagation Model
identifies the status propagation model used for

determining the propagated status from the
provider's main status
Editable
indicates whether you can edit the object
You can search on component types by selecting an Impact Administration subtype

from the drop-down list. When you click Search, it retrieves the relationships
associated with the selected subtype.
Select an item in the Edit Relationships dialog, and right-click to open the pop-up
menu. You can perform actions common to all object relationships: View Service
Model, Edit Component, Add Navigation Link, and Add Relationship.
You can edit any of the component's relationships by selecting it and then choosing
the Edit Relationship button at the bottom of the dialog. The Edit This Relationship
subdialog contains the following fields:
Table 100: Edit This Relationship subdialog
Field
Description
Consumer/Provider indicator
indicates the directional flow of the relationship

between the selected component and the component
subtype. You can modify the relationship
Type of Relationship
Direct, Increasing, Decreasing, Just_Info, or

Just_Warning
Status Weight
weight (numeric value) of a relationship used while

calculating the status using weighted cluster mode
Description
Summary description of the relationship

You can add logical components to the BPPM Infrastructure Management service
model.
Logical components in this context refer to components that do not have a
predefined registration event associated with them, as do the BMC infrastructure
components listed in Table 97 on page 698. Although logical components are not
registered with the IAC and therefore do not provide real-time status information,
they can help to complement the BMC infrastructure model. For example, you can
add logical integrations and server processes to the model to represent an idealized
infrastructure environment.
Note
The names of logically created components do not display in Korean in the graph
viewing area while its component object does.
Deleting components
You can delete both logical service groupings/objects and live, registered objects
from the BMC ProactiveNet Infrastructure Management service model.
Usage reporting
To organize your service model around its real-time components, you can delete
logical groupings that do not have registered components associated with them.
Generally, you should delete the leaf objects, not objects that lie between other
objects. If you delete objects that lie between other objects, some objects that should
be deleted because of relationship associations with the other objects will
nonetheless remain.
BMC recommends that you do not delete components that have been registered
automatically with the BMC ProactiveNet Infrastructure Management service
model. However, if you delete a live, registered object, it is removed from the BMC
ProactiveNet Infrastructure Management service model, and an event of the class
Service Model Component Delete is sent to the IAC.
Tip
You can recover a deleted registered object by modifying the DATA/ADMIN_DATA/

ADMIN_REGISTRATIONS table of the IAC in the General Administration tab view.
You change the enable parameter for the specific component from NO to YES in the
Edit tab. Then you restart the component to reregister it.
Usage reporting
In the Infrastructure Management tab, you can choose the File => Usage Report
menu option to display and print a report that lists the BMC ProactiveNet
components that are registered with the BMC Impact Administration cell.
These components include:
management servers
standalone cells
high availability cells
Integration for BMC Remedy Service Desk
Note
By default, users belonging to the user group Full Access, Service Administrators
can access these reports.
You can save and print the report in a plain text file or a comma-separated values
(CSV) file for tabular data presentation.
To display and save a usage report

Be sure that you are connected to the Impact Administration Cell. Otherwise the
Usage Report... option is unavailable.
1 In the Infrastructure Management tab of the Administration Console, choose
File => Usage Report.
Save the report in .csv or .txt format
Print the report


Use the Reload menu command to access the commands for reloading a cell's
configuration.
The Reload => All menu option is the equivalent of the mcontrol command's
reload all option. This means the default data from the cell's KB\data directory is
reloaded, taking it back to a default out of the box data state. This removes any
custom data that the customer has created. However, the other options, such as
Reload => Knowledge Base, Reload => Directory (mcell.dir), etc., do not reload
data.
To reload all of the cell configuration

1 Right-click a cell.
2 Select Reload => All.
All configuration files and the KB are reloaded.
To reload only the cell's knowledge base

2 Select Reload => Knowledge Base.
The KB is reloaded.
To reload the directory

2 Select Reload => Directory .
The mcell.dir file is reloaded.
To reload cell configuration

2 Select Reload => Cell Configuration .
The configuration files mcell.conf, mcell.propagate, and mcell.modify are
reloaded.
To reload trace configuration

2 Select Reload => Trace Configuration .
The mcell.trace file is reloaded.

You can use the Propagate Events command to force the selected cell to send the
contents of the destination buffers to one or all its destination cells immediately.
To force propagation to all target cells

2 Select Propagate Events => All Destinations to force propagation of the buffer
contents to all target cells.
To force propagation to a selected target cell

2 Select Propagate Events => Select Destinations.
3 In the Propagate dialog box, specify the target cell to which you want to
propagate the buffer contents.
4 Click OK.
Collecting metrics
Use the Metrics Collection menu command to access the commands for working
with metrics.
To turn metrics collection off

2 Select Metrics Collection=> Disable.
To reset collection counters

2 Select Metrics Collection => Clear Values.
3 The collection counts are reset to 0.

Where appropriate for the component, you can perform the actions that are available
in the Services Editor tab view.
These actions include
viewing the graph of a selected component and its relationships
adding links to components from container folders
refreshing the graph view after making an edit to a component or relationship

By default, BPPM Infrastructure Management automatically maintains an audit log
of all remote actions that an administrator performs on remote hosts. The audit log
uses the following format:
IAS_USER
SUB_TYPE:OBJECT
EXPLANATION
TIME_STAMP
OS_USER
LOG_LEVEL
ACTION_ID
Table 101 on page 719describes the audit log parameters:

Table 101: Audit log parameters for Infrastructure Management
Audit log parameter
Description
TIME_STAMP
month, day, year, hour, minute, and second that the

log entry was created. Uses the format mm/dd/
yyyy hh:mm:ss
LOG_LEVEL
the severity level of the logged action. Valid values

include
INFO: informational message
SEVERE: error message
A typical SEVERE message documents the error
exceptions that occur during the execution of a
remote action, such as Unable to save file on remote
machine
Audit log parameter
Description
IAS_USER
current BMC ProactiveNet user name that has

logged on and connected with the BMC ProactivNet
Server
OS_USER
user name that logs into the remote host's operating

system. This is the user name under which the action
is executed on the remote host
SUB_TYPE
the component or application type on the BMC

ProactiveNet administrator is performing the remote
action. BPPM Infrastructure Management supports
the subtypes listed under Supported component or
application types on page 720
OBJECT
user-specified value in the Object slot of the

component or application on the which remote
action is being executed
ACTION_ID
unique Id associated with the remote action. This

unique Id is defined in the corresponding
actions.xml file stored on the computer where the
BMC ProactiveNet Server resides. It is stored under
the BMC PROACTIVENT_HOME/server/data/
admin/actions folder on the BMC ProactiveNet
Server computer.
EXPLANATION
short text description of the logged action
Supported component or application types

BMC ProactiveNet Infrastructure Management supports the following types in this
product version:
EM_CELL
SIM_SERVER_2
EM_SERVER_1
IBRSD
EM_SERVER_2
BEM_SERVER_STANDBY
SIM_CELL
SIM_SERVER_STANDBY
INTEGRATIONS
PS
SIM_SERVER_1
Sample logs
A sample audit log for a remote startup action on a service impact management cell
might look as follows:
Mon 07/23/2007 16:50:15 INFO iasuser superuser SIM_CELL:PUNE_CELL
start_im_windows Executing action
Audit log properties in the ias.properties file

These audit logs are stored by default under the BMC_PROACTIVENET_HOME/
pronto/logs/ias directory on the BMC ProactiveNet Server.
You can configure the audit log by modifying the properties in the ias.properties file
shown in the table below.
Property
Description
com.bmc.sms.ixscomm.util.auditLogEnable
Boolean true/false value that indicates whether

auditing is enabled. The default is true.
Property
Description
com.bmc.sms.ixscomm.util.auditLogFilename
specifies the file path and name of the audit log file,
using the %g indicator to show that the audit log
files are cycled through a numerical sequence. For
example, if
auditLogFilename=AuditLog%g.log
auditLogFilecount=10
auditLogLimit=5000
then the initial audit log is assigned the name
AuditLog1.file. When its file size reaches 5000 bytes,
a new audit log is generated with the same name but
incremented by one: AuditLog2.file. As each log
reaches the maximum size, a new audit log is created
and incremented by one. When the maximum log file
count (10 in this example) is reached, then the
process repeats itself because only one cycle of logs is
maintained. The first audit log of the new cycle starts
at 1 (AuditLog1), overwriting the existing file. As
new logs are generated in the new cycle, they
overwrite the existing ones in sequence.
By default the audit logs are stored in the
BMC_PROACTIVENET_HOME/server/log/ias
directory. You can specify another directory path in
this parameter value: for example,
auditLogFilename=log/AuditLog%g.log, provided
that the specified directory exists under
BMC_PROACTIVENET_HOME/server.
com.bmc.sms.ixscomm.util.auditLogLimit
size in bytes of the audit log file. The default is 5000

bytes (approximately 4.88 kilobytes). While there is
no predefined maximum size, BMC recommends
that each log file not exceed 5 MB.
com.bmc.sms.ixscomm.util.auditLogFileCount
indicates the number of audit log files that are cycled

through during a rotation. After the specified
number is reached, the cycle repeats itself,
overwriting in sequence the log files of the previous
cycle. The default is 1.
After you modify any of the properties in the ias.properties file, you must restart the
BMC ProactiveNet Server.

You can create a support package for troubleshooting purposes by collecting files
from remote systems and saving them to a specified file path on the local or a remote
system.
The support package contains the following files:

.dir files
.conf files
filter files
selector files
mapping files
trace files
trace.conf files
In addition, it contains
default support files
These are internal files of the infrastructure application. They are not included in the
other categories. They vary among the applications, but they include .baroc, .mrl,
.wic, and .cmd files. Generally, for a cell server, this package contains the files of its
KB directory and its log directory. You can choose which files to include. They also
include a sysinfo.text file that captures active port connections, OS and hardware
configurations, and network card details. The absolute file path to each file is included.
additional support files
This is a customizable list of files that the user can edit by adding or deleting files to
or from the support package. It is designed to enable the user to add other files to the
support package.
Slots for specifying support files

You can specify which support files you want to receive by editing the
corresponding slot in the Edit Service Component dialog for the selected component.
To specify which support files to include, select the component and choose Edit =>
Edit Component or choose Edit Component from the right-click pop-up menu. The
Edit Service Component dialog is displayed. Scroll down the list of slots. You can
specify values in the slots specified in the following table.
Slot
Description
Additional Support Files
full path to other support files that you want to include
Slot
Description
Configuration files
full path to configuration files (.conf)
Dir files
full path to *.dir files, such as mcell.dir or admin.dir
Filter files
full path to *.filter files
Map files
full path to *.map files
Selector files
full path to *.selector files
Trace conf files
full path to the *.trace file
Trace files
full path to the trace logs
Your support files should be on the system on which the component is running.
Enter the full path to the file you want to include. If you are adding multiple files,
separate the complete file paths with commas. There is no limit to the number of files
that you can add.
To compile your support package, choose the Administer => Support Package tab.
Browse to the destination folder where you want to save the list of configuration and
log files, and select it. You can enter the issue number (maximum of 16 characters) if
one has been assigned.
WARNING
Microsoft Windows does not support the creation of files that have any of the
following special characters in their file names: , \, /, ?, *, ", |, <, >. If the BMC
ProactiveNet Administration Console is installed on Microsoft Windows, do not
enter any of the special characters in the Issue Number slot. Otherwise, the support
package creation fails.
If you do enter the issue number, assign it as a prefix to the support package name.
You can type a short, but informative, description of the package (maximum of 256
characters). Then click Create Package.
The file name of the support package file follows this format:
OBJECT_NAME_support_package_TIMESTAMP.zip
The OBJECT_NAME value is taken from the object slot of the selected component.
The time stamp is in the format: MMDDYY_HHMMSS.
UNIX processing note

On UNIX computers, it may take several minutes to create a support package.
The following causes can contribute to the delay in processing:

whether the component for which you are creating the support package resides in
a different domain from the system on which you are running the BMC
ProactiveNet Administration Console. If it does lie in a different domain, expect a
delay.
the size of the zipped or tarred file. The greater the size, the longer the delay,
especially as the file approaches 500 kb or larger.
Reviewing the audit log of the support package

Internally, the process of building a support package consists of these actions:
1 saving the OS-based compression utility (zip or zip.exe) to the remote system
2 creating the support package
3 removing the OS-based compression utility from the remote system
4 executing the get-file action to retrieve the support package from the remote
system and putting on the system where BMC ProactiveNet Server resides
5 getting the binary file from the BMC ProactiveNet Server system to the local
system where the BMC ProactiveNet Administration Console resides
Because this is a remote action, the audit log captures the process. If the support
package creation is a success, you receive an audit log message that looks similar to
the following Windows example:
Fri Aug 17 12:49:25 IST 2007 INFO user ADPROD\slondhe SIM_SERVER_1 :slondhepun-01 saveRemoteFile : zip.exe Executing action.
Fri Aug 17 12:49:28 IST 2007 INFO user ADPROD\slondhe SIM_SERVER_1 :slondhepun-01 create_support_package_WINDOWS Executing action.
Fri Aug 17 12:49:30 IST 2007 INFO user ADPROD\slondhe SIM_SERVER_1 :slondhepun-01 remove_zip_WINDOWS Executing action.
Fri Aug 17 12:49:31 IST 2007 SEVERE user ADPROD\slondhe SIM_SERVER_1 :slondhepun-01 remove_zip_WINDOWS Stderr returned with some error.
Fri Aug 17 12:49:32 IST 2007 INFO user ADPROD\slondhe SIM_SERVER_1 :slondhepun-01 get_file : Test1_support_package.zip Executing action.
Fri Aug 17 12:49:33 IST 2007 INFO user ADPROD\slondhe SIM_SERVER_1 :slondhepun-01 getBinaryFile : Test1_support_package.zip Executing action.
In a successful support package creation, the audit log does return an error message:
Fri Aug 17 12:49:31 IST 2007 SEVERE user ADPROD\slondhe
SIM_SERVER_1 :slondhe-pun-01 remove_zip_WINDOWS Stderr returned with
some error. You can ignore this error because users can still retrieve the zipped
support package automatically from the remote system without any manual
intervention.
If you receive a SEVERE error message on any of the other support package actions,
such as saveRemoteFile, create_support_package, get_file, and getBinaryFile, it
indicates that the support package creation failed. Discard the package, and try again.
Background to BPPM Infrastructure

Management
The information in this section describes some of the internal workings of BPPM
Infrastructure Management.
How a product component registers and communicates with

the IAC
To register with the IAC, the component or application sends a configuration
information event. This configuration event contains certain required slots such as
mc_event_model_version, mc_object and mc_tool, os_class, and so forth. The
component or application sends the configuration information event upon each
startup or change in its configuration.
After it registers with the IAC, the application or component sends status
information such as startup, shutdown, and error events.
Note
All event information should be compliant with the event format strictures of
version 1.1.00 of the Common Event Model (CEM). for more information, see the
BMC ProactiveNet Knowledge Base Development Reference Guide .
Registering a remote cell with the Impact Administration Cell

When you add a remote cell using the mcrtcell CLI command, you need to register
the cell with the BMC ProactiveNet Server using the iadmin -ac command.
To manually register a remote cell with the IAC

1 Add the cell using the mcrtcell CLI command, as in the following example:
mcrtcell -as -ba -r -@ hostName/2008 -n sparkles_cell
2 Next, use the iadmin -ac command to register the cell with the BMC
ProactiveNet Server. From the BMC_PROACTIVENET_HOME/server/bin
directory, execute the iadmin -ac command as in the following example:
iadmin -ac
name=sparkles_cell:key=mc:primaryHost=moondog:primaryPort=2008:failoverHos
t=suncat:failoverPort=2008:environment=Production:usergroups=*
The cell is added automatically to the cell_info.list of the BMC ProactiveNet

Server located in the BMC_PROACTIVENET_HOME/pronto/conf directory. It is
also automatically added to the admin.dir file of the Admin cell located in the
BMC_PROACTIVENET__HOME/pronto/data/admin directory, as in the
following example:
cell
moondog_10
moondog.bmc.com:1828
mc
cell
Admin
moondog.bmc.com:1827
mc
cell
sparkles_cell
moondog.bmc.com:2008 suncat.bmc.com:2008
mc
3 Add the cell entry to the mcell.dir file.

By default, the file is located in the BMC_PROACTIVENET_HOME/server/
etcdirectory.
4 Restart the cell that you are registering.
5 Restart the BMC ProactiveNet Administration Console.
The newly registered cell is displayed in the Infrastructure tab of the
administration console. In the Event View of the BMC ProactiveNet Operations
Console, you see that the cell that you have registered sends a registration event
to the IAC.
Recreating an Impact Administration Cell

If you accidentally remove your IAC, you can recreate it through the mcrtcell CLI
command by using the -aa switch, as in the following example:
mcrtcell -aa -ba -r -@ hostName/1827 -n Admin
In this example, you create an IAC with the name "Admin" and assign it to port
number 1827.
Unregistering with the IAC

You cannot formally unregister a component. To remove a component from the
BMC ProactiveNet Infrastructure Management model, you must manually delete it.
It is removed from the BMC ProactiveNet Infrastructure Management interface, but
not from the model contained in the IAC. For example, its .log and .conf files persist
in the IAC. The application or service, however, is no longer operational.
Remote actions
While events flow only from the components to the BMC ProactiveNet
Infrastructure Management interface, administrators can initiate actions on the
components from the interface in the BMC ProactiveNet Administration Console.
Depending on the type of component and its status, you can initiate several actions
on the local or remote component.
How context-sensitive remote actions are processed

The current state of a selected component is shown in its run_state slot (Run State),
which you can view in the Details => General subtab in the BMC ProactiveNet
Infrastructure Management tab. The different run_state values are described in the
following table:
Table 102: run_state values for components
run_state value
Description
unknown
state of the component cannot be determined
active
indicates that the cell is the active server component

of an HA relationship
unavailable
the connection with the component is disrupted or

the component is down
started
the component is online; unable to determine if it's

the active component in an HA relationship
stopped
the component has sent is stopped and has sent a

status event indicating that it is stopped
paused
the component is in maintenance mode
passive
the secondary cell in an HA relationship is in

standby mode
The current run_state of the component determines which context-sensitive actions

are disabled or enabled from the Actions option on the right-click menu.
The following table indicates which menu options are enabled (Yes) or disabled
(blank) for each run_state of a normal cell or a primary cell in an HA configuration.
Table 103: Component state and menu options for a normal or primary cell in a high availability
configuration
Menu
options
run_state
Start Cell
Server
Process
state_unkn
own
Yes
state_active
Stop Cell
Server
Process
Restart Cell Pause

Resume
Set to
Server
Events
Events
Standby
Process
Admittance Admittance
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Set to
Active
state_unava Yes
ilable
state_starte
d
state_stopp
ed
Yes
state_pause
d
Yes
state_passiv None
e
Note
If a component in an unknown state is already started and you choose Actions =>
Start, you receive a status message notifying you that the component is started already.
The following table indicates which menu options are enabled (Yes) or disabled
(blank) for each run_state of a secondary cell in an HA configuration.
Menu
options
run_state
state_unkn
own
Start
Stop
Restart
Cell Server
Process
Cell Server
Process
Cell Server
Process
Pause
Resume
Set to
Events
Events
Standby
Admittance Admittance
Yes
Yes
Yes
Set to
Active
Yes
state_active
Yes
state_unava Yes
ilable
Menu
options
state_starte
d
Yes
Yes
state_pause
d
Yes
Yes
state_passiv
e
Yes
Yes
state_stopp
ed
Yes
Yes
Yes
Yes
Exceptions
Generally, most component objects receive the actions Start, Stop, Restart, Pause, and
Resume.
For cell servers, the Start, Stop, and Restart menu options in the Actions submenu
are described as:
Start Cell Server Process
Stop Cell Server Process
Restart Cell Server Process
For other objects apart from cell servers, the Start, Stop, and Restart menu options in
the Actions submenu are described as:
Start Process
Stop Process
Restart Process
Different actions are available for different types of components. The following table
lists the main exceptions:
Table 104: Components and actions
Component
Exception
HA cell
all actions. The HA cell is the only component that

allows the Set to Standby and Set to Active menu
options
receives the Restart action only
Publishing Server
receives the Start and Stop actions
Displaying remote cells in the Infrastructure Management tab after upgrading the BMC ProactiveNet Server
Component
Exception
IBRSD
receives the Stop and Start options
normal cell
receives the Stop, Start, Restart, Pause Events

Admittance, and Resume Events Admittance options
Logical components that you add to the BPPM Infrastructure Management service
model receive no actions.
Displaying remote cells in the Infrastructure

Management tab after upgrading the BMC
ProactiveNet Server
If you upgrade the BMC ProactiveNet Server, but do not upgrade any BMC
ProactiveNet remote agents, you cannot view the remote cells associated with those
agents in the Infrastructure Management tab of the BMC ProactiveNet
Administration Console. To display the remote cells and manage them from the
Infrastructure Management tab, perform the following procedure.
To display remote cells in the Infrastructure Management tab

1 On the computer where the previous version of the BMC ProactiveNet agent is
installed, open the admin_rec_options.baroc file.
This file is located in the agentInstallDirectory/pw/server/etc/cellName/kb/
records directory.
2 In the section titled Record Admin_Options Defines, change the default value
of the attribute IAC_enabled to Yes.
4 Stop the cell by entering the following command from a command line:
mkill -n cellName
5 Compile the cell by entering the following command from a command line:
mccomp -n cellName
6 Start the cell again by entering the following command from a command line:
mcell -n cellName
Displaying remote cells in the Infrastructure Management tab after upgrading the BMC ProactiveNet Server
You can now manage the cell from the Infrastructure Management tab in the
administration console.
17
Using the BMC ProactiveNet
Administration Console for service
monitoring
Services Editor tab
The Services Editor tab of the BMC ProactiveNet Administration Console is the view
that service managers, service administrators, and IT operations staff use to monitor
business services. Service managers can view the service models that represent a
companys business services. Service models are created by organizing service
model components into hierarchical relationships that can then be navigated by
operators and service managers from the Services Editor tab in the BMC Proactive
Administration Console or in the BMC ProactiveNet Operations Console.
In the Services Editor tab, a service manager or operator can see whether a service
model component consumes the services of another service model component
(consumer) or whether it provides service to another component (provider).
From the service model component, IT operations staff can view and manage the
underlying events in the BMC ProactiveNet Operations Console.
Monitoring business services in BMC

ProactiveNet
You monitor published and manually created service models that represent your
business services in the BMC ProactiveNet Administration Console Service Model
View of the Services Editor Tab. The Service Model View provides a graphical
representation of the service configuration items and how they relate to each other.
Figure 136 on page 734shows an example of an Service Model View.

Figure 136: Services Editor tab - Service Model View
Depending on whether the default setting is set to horizontal or vertical expansion,

the consumer components are displayed on the left or at the top and the direct
provider components expand to the right or toward the bottom. A direct consumer or
provider component is a component immediately linked to another component. The
status of the provider has a direct impact relationship with the consumer component.
Opening a Service Model View

1 Click the Services Editor tab at the top of the navigation pane in the BMC
2 Open a Service Model View by using one of the following methods:
From the navigation pane, select a service component instance. See Viewing
service component instances through the navigation pane on page 735.
Click and drag the service component instance from the Results list to an empty
area of the Service Model View. See Finding service component instances to
view on page 737.
Right-click a service component instance and choose View Service Model.
3 Double-click a service component instance to open or close its related service

component instances.
If you double-click a node that does not have any providers and consumers, the
message This object does not have any consumers/providers is displayed.
Viewing service component instances through the navigation

pane
Use the navigation pane to view the components associated with a service in the
Service Model View. Service managers create the navigation pane tree in BMC
Impact Model Designer.
Note
If the navigation pane tree does not reflect published changes, log out and log back
on to the BMC ProactiveNet Administration Console.
The navigation pane tree contains service component instances associated with a
production cell. To view service component instances associated with a production
cell, use the Find tool. For instructions, see Finding service component instances to
view on page 737.
The Services Editor tab navigation pane is shown inFigure 137 on page 736.
Figure 137: Services Editor tab navigation pane
Table 105 on page 736 describes the elements in the Services Editor tab navigation
pane.
Table 105: Description of elements in the Services Editor tab navigation pane
Name
Description
Service Views tab
shows the available service groups
My Services group
the top level for locally-defined service groups
Name
Description
subgroup icons
identifies user-created subgroups of components
service component icons
identifies individual components and subcomponents
Global Services group
the top-level node for globally-defined service groups
Find Service Components searches for service component instances that match specific criteria
box
Use the Show Find button in the toolbar to view or hide the Find Service
Components box.
Class list box
specifies the component type for the object of the search
Name contains text box
specifies all or part of the target component name
Propagates Priority check

box
select this check box to show the Priority Propagator service component
instances that pass their priority to a causal component when it is impacted
These components are considered the important components for your business.
In SLM Agreement check

box
select to show the service components that are associated with a Service Level
Agreement
Note: This feature requires the BMC Service Level Management product to be
installed.
Results list
displays the results of the component search
Finding service component instances to view

Use the Find Service Components tool to locate a particular component in a cell and
view it in the Service Model View.
To search for a service component instance

1 If the Find Service Components section of the navigation pane is not open, click
the Show Find button on the toolbar of the Services Editor tab.
2 From Class, select a component type, such as Computer System, application
service, database, and so on. If you select Base element, all service component
instances for all types are returned.
3 In Name Contains, enter a comparison value.
Note
If you leave Name Contains blank, the search could take a long time, depending
on the number of service component instances. Also, the Results list could be
very long. You should refine the search by specifying values in one or both of
these fields.
4 To find only those components that propagate their priority to causal

components, select Propagates Priority.
5 Click Find.
All components matching the search criteria appear in Results.
6 Drag the service component to the Service Model View.
Tip
To uniquely identify each component listed in Results, you can hover the cursor
over each component name to display its unique mc_udid slot value.
Viewing information about a service component

To view information about a service component, click the component in the Service
Model View and then select one of the tabs as shown in the following table. .
Table 106:
Services Editor service component information subtabs
Tab
Purpose
General
shows the value of slots that contain basic information about a

service component and the status computation model used for
the component, Standard (default), Self-preferred, Cluster,
Weighted_cluster
Priority and Cost
shows the value of slots that contain priority and impact

information about a service component
Related Components
provides search capabilities to find components that are

consumers of the selected component
providers of the selected component
SLM
shows information about the service level agreement

associated with the component
Note: This tab is visible only when BMC Service Level
Management is installed.
Schedule
shows the schedule associated with a component
Advanced
shows the value of slots that contain creation and security

information about a service component
Searching for provider and consumer components
Searching for provider and consumer

components
Use the Related Components tab in the Service Model View to search for providers
and consumers of a component in a service model.
1 Click a component in the Service Model View. For instructions on how to view a
component, see Opening a Service Model View on page 734.
2 Click the Related Components tab below the Service Model View.
3 To view impacts or causes, select one of the following Relationship types:
Select
To view
Providers - All
all providers to this consumer
Providers - Direct
provider components that directly impact the status of the consumer
Consumers - All
all consumer components associated with the provider component
Consumers - Direct
components that directly consume the services of the provider

component
4 Select a Component type from the drop-down list. To view all related
components regardless of type, leave the Component type set to Base Element.
5 Click Search.
Components matching the search criteria are displayed in the Components list, as
Figure 138: Related components - providers search
6 To view a component in the Components list, select the component, right-click,

and then select View Service Model.
Viewing a service components SLM agreements
Viewing a service components SLM

agreements
You can view the status of an SLM compliance target for those components
associated with a service agreement.
You can launch the Service Level Management Console by right-clicking on a
component and selecting the task that you want to perform.
To find components with an associated SLA

1 If the Find Service Component section of the navigation pane is not open, click
the Show Find button on the toolbar of the Service Editor tab.
2 In Class, if you want to select components of a specific type, select a component
type, such as Computer System, application service, database, and so on.
If you select Base element, all service components for all types are returned.
3 In Name contains,to select a subset of components by name, enter a comparison
value.
4 Select In SLM Agreement to find the components associated with an SLA.
5 Click Find.
All components matching the search criteria appear in Results.
6 Drag the service component to the Service Model View.
To view or modify an SLA associated with a component

1 Click a component in the Service Model View with an SLM status indicator. For
instructions on how to view a component, see To find components with an
associated SLA on page 740.
2 Click the SLM tab below the Service Model View.
3 To view SLM information, click Compliance Details.
The component Compliance View Dashboard is displayed, which is view only.
The component Compliance View shows all configuration items (CIs) associated
with an Agreement. For each component, you can view the Service Target
measurement status and the Agreement compliance status related to the
component.
If you want to modify or view a SLM agreement or a service target when you are
viewing the Dashboard, click the SLM Console tab in the SLM application, then
select an agreement from the list to view in the Agreement form.
Viewing property and performance data

about a cell
Property and performance information for a cell is maintained in the Impact
Manager Info dialog box.
To access this information
1 In the Event Management Polices tab or Dynamic Data Editor tab in the
Administration tab of the navigation pane, right-click a cell and choose View
Manager Info.
The General subtab

The General subtab of the Impact Manager Info dialog box is displayed. This subtab
displays information about the cell property data such as the cell name, description,
release and build versions, service address, port number, and platform information.
In a high availability (HA) environment, use the General subtab to determine
whether the server is one of a failover server pair. You can also learn whether the
primary server or the secondary server is active. The following fields provide you
with the required information.
Currently Active ServerThis field displays the active server and indicates
whether it is a primary or secondary server.
Server ModeThis field displays the status of the server and indicates whether it
is active or is in a standby mode.
The General subtab also provides you information about the IP address and ports
for the primary and secondary servers.
Figure 139: Impact Manager Information dialog box - General subtab
The Workload subtab

The Workload subtab displays performance statistics for the cell, including how
much data the cell has received, the number of errors, and how much data has been
stored, removed, and propagated.
Figure 140: Impact Manager Information dialog box - Workload subtab
Editing Service Model data in the BMC ProactiveNet Administration Console
The Components subtab

The Components subtab displays service performance data specifically pertaining to
the number of service model components associated to the cell, such as the type of
components and the relationships.
Figure 141: Impact Manager Information dialog box - Components subtab
Note
To refresh the contents of the Impact Manager Info dialog box, click the
(Refresh) icon.
Editing Service Model data in the BMC

ProactiveNet Administration Console
This section provides procedural information about how to work with your service
model and its components.
Managing Service Model components

If your user role has the correct permissions, you can create the individual
components and compose a service model by using the BMC ProactiveNet
Administration Console. Service model components can represent anything, such as
a hardware device, an application, a service, or a business entity.
For the various user roles and permissions and the operations possible for various
users, see the Default users, user groups and roles on page 494.
Creating Service Model components

You can create components for a service model in the Services Editor tab in the BMC
To create a Service Model component

1 Click the Create Component icon on the Administration Console toolbar.
2 In the Create Service Component dialog box, specify the appropriate settings as
described in the following table.
Table 107: Create component fields
Field
Description
Name (required)
specifies the name for the component. Enter a name meaningful to your
organization.
ID
specifies the unique logical ID for the component, which is how the component
is identified in the service model or in event data
Class
specifies the type of component (its data class). Select the appropriate value
from the list.
Home Cell
specifies the cell that will receive events for the component
Site
specifies the site where the cell is, if applicable
Description
briefly describes the component
Owner Name
specifies the individual responsible for the component
Owner Contact
specifies the contact information for the owner of the component
Impact Cost Per Second

During Service Schedule
specifies the cost associated with the component during service schedule timing
Impact Cost Unit
the unit of cost specified in Impact cost per second during service schedule
Field
Description
Status Model
specifies the status computation model to use for the component. Values are:
Standard (default)
Self_preferred
Cluster
Weighted_cluster
Account ID
account ID
Category
category
Company
company
Aliases
Each component instance must have a unique Alias. If more than one
component instance has the same alias, publishing will fail.
Department
department
DeviceID
unique identification for a device
Floor
floor
Home Page URI
URL of the home page of the business
Host name
if you are creating a computer system CI, specifies the name of the computer
system on which the CI resides; you must enter a value for this field
Impact Cost Per Second

Off Service Schedule
specifies the cost per second associated with the component during off-schedule
time
Item
item
Manufacturer Name
name of the manufacturer
Model
model number and details, if available
Notes
additional information about the model
Priority - During Service

Schedule
specifies a priority value that you assign to the component. This value can be
between one and five, with five being the lowest priority and one being the highest.
Priority - Off Service

Schedule
specifies a priority value that you assign to the component when for the offschedule time. This value can be between one and five, with five being the
lowest priority and one being the highest.
Propagates Priority
specify if you want the priority to be propagated to the causal components. The
value can be Yes or No.
Field
Description
Read Permission for

Groups
specify user groups that have read permissions. Type user groups in square
brackets, each separated by a comma.
While creating a component from BMC IX, if you do not enter any value in the
Read Users and Write Users fields of the component properties, by default
these fields are populated with a value Full Access when you save the properties
Region
region where the component is located
Room
physical location of the component
Schedule ID
By default, the value is 24X7X365 (always in schedule)
Self Priority Function
the method used to compute the self-priority of a CI. Choose one of the
following options:
BASE_PRIORITY
COST
WORST_SLA_STATE
Self Priority Function

Param
parameter that you can set to determine the priority of a CI
Serial Number
serial number of the component if one exists
Short Description
Default value is n/a
SiteGroup
details of the business associated with the CI
Type
type of CI
Users Affected
the number of users impacted if the CI becomes unavailable
Version Number
version number
Write Permissions for

Groups
specify user groups that have write permissions. Type user groups in square
brackets, each separated by a comma.
While creating a component from BMC IX, if you do not enter any value in the
Read Users and Write Users fields of the component properties, by default
these fields are populated with a value Full Access when you save the properties.
Business Data
Comment
Enter comments, if any.
Field
Description
Schedule Status
Specify if
High Demand
Low Demand
Default value of this slot is High Demand.
After you have specified the mandatory fields, the Apply and OK buttons are
enabled.
3 Click Apply and click OK.
Editing Service Model components

Use the Services Editor tab to edit the service model components for service models
that you create in the BMC ProactiveNet Administration Console.
Note
You cannot edit service model components that are imported from the BMC Atrium
CMDB. You must edit those components in BMC Impact Model Designer, which you
can launch from the Services Editor tab in the BMC ProactiveNet Administration
Console. For details, see Launching BMC Atrium Explorer from the BMC
ProactiveNet Administration Console on page 753.
To edit a Service Model component

1 Select a component and click the Edit Component icon on the toolbar.
Select a component and choose Edit => Edit Component from the menu bar.
Right-click a component and choose Edit Component from the menu.
2 In the Edit Service Component dialog box, modify any of the component settings
listed in Table 72 on page 494, except for the following fields, which you cannot
edit:
ID
Class
Home Cell
Schedule ID
3 Click Apply to save the changes, or click OK to save and exit the dialog box.
Deleting Service Model components

Use the Services Editor tab to delete the service model components that you create in
the BMC ProactiveNet Administration Console.
To delete a Service Model component

1 Perform one of the following steps:
Right-click a component that you want to delete and select Delete Component.
Select a component and click Delete Component on the toolbar.
The Delete Confirmation message dialog box is displayed with the following
message:
Do you really want to delete this component?
2 Click Yes.
Managing Service Model component relationships

After you have created the component instances that participate in a service model
relationship, you can define their relationships.
For each component instance for which you are creating relationships, you must know
whether it is a consumer or a provider for the related component
its relationship state value (active or inactive)
its status propagation model value (relationship policy)
Adding Service Model component relationships

Use the Services Editor tab to add relationships between the service model
components that you create in the BMC ProactiveNet Administration Console.
To add a Service Model component relationship

1 Open a component relationships pane in the Services Editor tab by using one of
the following methods:
On the navigation pane, select the component.

On the navigation pane or from Results, right-click a component and choose
View Service Model.
Drag and drop the component from either the navigation pane or Results onto
the relationships pane.
2 On the Services Editor tab navigation pane or from Results, right-click a

component and select Add Relationship.
3 In the Find Service Components pane, select a data class from the Class list.
4 In the Name Contains field, enter a comparison value.
5 If you want the priority to be propagated to the causal components, select
Propagates priority.
6 Select the In SLM Agreement check box if required.
7 Click Find.
All components matching the search criteria appear in the Results pane.
8 From the Results pane, select the appropriate component and click OK.
9 Optionally, instead of steps List item. on page 686 to List item. on page 84, drag
and drop the component from either the navigation pane or Results into the
relationships pane on the component to which you want to add the relationship
to.
10 In the Edit Relationships dialog box, specify which component should be the
consumer and which component should be the provider by selecting the required
arrow direction.
11 Specify the type of relationship:
Direct, Increasing, or Decreasing
Directthe status of the consumer component may be identical to that of its
provider component, depending on the events directly affecting the

consumers status, which is also taken into account.
Decreasingthe status of the consumer component is less critical than that
of the provider component by one level. For example, if the provider status
is WARNING, the consumer status is INFO.
Increasingthe status of the consumer component becomes more critical
than that of its provider component by one level. For example, if the
provider status is WARNING, the consumer status is MINOR.
Active or Inactive
ActiveAn active relationship is an impact relationship and indicates that
the status of the consumer instance depends in some measure on the status
of the connected provider instance.
InactiveAn inactive relationship means that no dependency exists or that
the dependency is irrelevant to the model. The components are only logically
and visually linked.
12 In the Status Weight box, accept the default value or enter a number for the
consumer object. (Status weight is used in the WEIGHTED_CLUSTER status
computation model. For more information about component status computation,
see BMC Impact Solutions Service Modeling and Publishing Guide.)
13 Optionally, in Description, type a description for the relationship. The default
description changes based on the relationship type that you select as follows:
DIRECT relationship (linear impact)
DECREASING relationship (reducing impact)
INCREASING relationship (increasing impact)
Note
To be able to add a relationship between two components from two different
cells, you must create an entry of both the cells in the mcell.dir file for both the
cells and then restart these two cells.
Editing Service Model component relationships

Use the Services Editor tab to edit the service model component relationships for
service models that you create in the BMC ProactiveNet Administration Console and
those published from the BMC Atrium CMDB.
To edit a Service Model component relationship

On the navigation pane or from Results, right-click a component and select
View Service Model.
Drag and drop the component from either the navigation pane or Results into
2 From the component details pane, click the Related Components tab.
3 Select the required component and click Edit Relationship. Alternatively, from
the menu bar, choose Edit => Edit Relationship.
The Edit Relationships dialog box opens. A list of components appears under
Relationships.
4 If required, select the required relationship and click Add Relationship. For
details about adding a relationship, see To display remote cells in the
Infrastructure Management tab on page 731.
5 If required, select the required relationship for deleting and click Remove
Relationship. For details about removing a relationship, see To remove a Service
Model component relationship on page 752.
6 If required, select the required relationship for editing and click Edit
Relationship.
7 In the Edit This Relationship dialog box, specify which component should be the
consumer and which component should be the provider by selecting the required
arrow direction.
8 Specify the type of relationship:
Direct, Decreasing, Increasing
Directthe status of the consumer component may be identical to that of its
provider component, depending on the events directly affecting the

consumers status, which is also taken into account.
Decreasingthe status of the consumer component is less critical than that
of the provider component by one level. For example, if the provider status
is WARNING, the consumer status is INFO.
Increasingthe status of the consumer component becomes more critical
than that of its provider component by one level. For example, if the
provider status is WARNING, the consumer status is MINOR.
Active or Inactive
ActiveAn active relationship is an impact relationship and indicates that
the status of the consumer instance depends in some measure on the status
of the connected provider instance.
InactiveAn inactive relationship means that no dependency exists or that
the dependency is irrelevant to the model. The components are only logically
and visually linked.
9 Optionally, in Description, type a description for the relationship. The default

description is DIRECT relationship (linear impact).
Removing Service Model Component relationships

Use the Services Editor tab to remove the service model relationships for service
models that you create in the BMC ProactiveNet Administration Console and in
BMC Atrium Explorer.
To remove a Service Model component relationship

On the navigation pane or from Results, right-click a component and choose
View Service Model.
Drag and drop the component from either the navigation pane or Results into
2 From the component details pane, click the Related Components tab.
3 Click Edit Relationship.
The Edit Relationships dialog box opens and displays a list of components under
the Relationships heading.
4 Select the required component and click Remove Relationship.
The Remove Relationship dialog box opens and displays the following message:
Do you really want to remove this relationship?
5 Click Yes.
Launching BMC Atrium Explorer from the BMC ProactiveNet Administration Console
The relationship is removed and the Services Editor view is refreshed.
Launching BMC Atrium Explorer from the

You can launch BMC Atrium Explorer from the BMC ProactiveNet Administration
Console to access the BMC Impact Model Designer so that you can edit the service
model components that are imported and synchronized with the BMC Atrium CMDB.
To launch BMC Atrium Explorer

1 In the Service Model View of the Services Editor tab, select a component in the
service model.
2 Select the Tools => Launch Atrium Explorer menu command.
BMC Atrium Explorer is launched in a separate window, and you can edit the
service model components in BMC Impact Model Designer.

For details about using BMC Impact Model Designer, see the BMC ProactiveNet
Service Modeling and Publishing Guide. For details about using BMC Atrium Explorer,
see the BMC Atrium Core User Guide.
Using a customized SSL certificate to create a

secure connection to the BMC Atrium CMDB
By default, BMC ProactiveNet uses a default keystore BMC Atrium CMDB SSL
certificate to establish a secure connection when BMC Atrium Explorer is launched.
If you want to use a customized keystore SSL certificate instead of the default, you
must import the certificate before you execute the synchronization task. Perform the
following procedure.
To import a customized CMDB SSL certificate

1 Open a command prompt.
2 Change to the following directory:
Associate monitors to CIs through the BMC ProactiveNet Administration Console
installDirectory \pw\jre\bin
3 Run the following command:
keytool -import -alias uniqueAliasName -file pathToCustomCertificate keystore installDirectory\pw\pronto\conf\pnserver.ks
The uniqueAliasName variable is the name of the file where the certificate will be
stored, and the pathToCustomCertificate variable is the location where the
certificate that you imported is stored.
4 When prompted for the keystore password, enter the value get2net.
5 When prompted to confirm that you want to trust the certificate, enter Yes.
6 To verify that the certificate is imported, enter the following command:
keytool -list -keystore installDirectory\pw\pronto\conf\pnserver.ks
The name of the certificate is displayed in the resulting list.

7 Open a command prompt and enter the following command to restart the jserver
process of the BMC ProactiveNet Server.
pw process restart jserver
Associate monitors to CIs through the BMC

ProactiveNet Administration Console
The Associate Monitors feature in the BMC ProactiveNet Administration Console
provides the ability to associate any monitor and its events to any CI by using an alias.
Monitor to CI alias overview

An alias uniquely identifies the CI. A CI can have multiple aliases. Every CI in BMC
ProactiveNet has an alias attribute and a value associated with it. The value of the
alias attribute is set when you create the CI. If an alias is not supplied, the ID is used
as the alias. The CI ID is auto-generated. cases. The alias attribute has the following
characteristics:
A token ID integrates the attributes of the CI. The Alias can be the token ID.
It can be auto-generated or entered manually.
You can only associate a monitor with one CI.
A monitor can only use one alias to refer to the CI, even when the CI has multiple
aliases.
This is important in a scalable deployment scenario where the same alias is used
on multiple servers.
The alias is used in event to CI associations.
When an event is generated on a metric that the BMC ProactiveNet Server is

monitoring, the alias for the event is the alias used for the monitor to CI mapping.
This alias is traced to a CI, and the ID slot of the event is filled. If no matching CI
is found, based on the alias, the event is associated with a device.
Use cases
By default, BMC ProactiveNet devices are associated to the Computer System
configurable instance (CI). Also by default, a native abnormality event is associated
with the monitor of the BMC ProactiveNet devices ComputerSystem CI, unless the
mc_smc_alias is set for the event. In some cases, the user might want to associate the
monitor's event with a different CI. For example, a higher level CI, such as Business
Service, or a more granular CI under the Computer System CI.
The following examples illustrate how you can use this feature:
Associate a monitor's events to a higher-level CI
A monitor might collect metrics that represent the overall health of a service or
application, for example, sales volume per minute. By default, any event on the
monitor is associated with the monitor's parent device. However, you might want
to associate the monitor to a higher level CI, for example, Business Services.
Associate a monitor's events to a more granular CI
A service model might break a device into a ComputerSystem plus other lowerlevel CI components. However, you might want events on the device's monitors
associated to a more granular CI. For example, if BMC ProactiveNet is monitoring
a database server, you could associate the database monitors with the Database
CI, and not with the ComputerSystem CI.
Associate monitors to CI in Service Model View

You can create a service model by creating components in the BMC ProactiveNet
In the Service Model View, you can perform the following tasks for a CI:
Add monitors to the list by selecting monitor type, then monitor instance.
Delete monitors from the list by selecting one or more and then pressing delete or
unassociate.
Select a group, and then all monitors in that group are added to the list.
Note
If a monitor added is already mapped to another CI, a warning dialog is displayed.

A monitor can only be mapped to one CI at a time.
Associating monitors to a CI and verifying that they are

associated
After associating all of the monitors and adapter monitors, verify that the monitors
and adapter monitors are associated to the desired components.
Note
You cannot associate monitors to a ComputerSystem CI.
To associate monitors to a CI
1 In the Service Model view, right-click on the component and select Edit
Component.
2 In the Edit Service Component window, find the values for ID and Alias, and
write those values down. The value of an alias can be an array of aliases.
3 In the Service Model view, right-click on a component and choose Associate
Monitors.
The CI Monitor Associations window is displayed.
4 In the CI Monitors Associations window, in Component, the class
(BMC_Application) and name (MyApplication) of the component are displayed,
along with a list of the component's aliases. By default, the first alias in the Alias
list is associated to the monitors. To associate a different alias to the monitors,
select another alias from the Alias list.
5 The Add Selected option is highlighted when a monitor is selected. You can add
as many monitors as you want by clicking Add Monitors and Copy From Group.
6 To remove monitors, select the monitors you want to remove (press CTRL
+SHIFT for multiple-selections) and click Remove Selected.
7 After making all desired associations, click Apply and Close.
To verify that the monitors are associated to the desired components

1 Generate an event on the monitor(s), for example, generate a regular Intelligent
Event using a threshold.
2 After generating the event(s), inspect the event in the Open Events Event List.
3 To view the mc_smc_id and mc_smc_alias event slots, click the Edit Preferences
icon in the top-left of the Objects panel and select the Component ID and
Component Alias slots.
4 Click on the event(s) you generated in the event list and for each event, verify that
the Component ID and Component Alias match those of the components to
which you associated the monitors.
Associate a monitor to a CI when CI Alias is unknown to the

A CI exists but is unknown to the BMC ProactiveNet server when the CI exists in the
CMDB, but the BMC ProactiveNet Server has not yet synced with the CMDB.
In this case, you can find the alias in the BMC Atrium Explorer, and enter the alias in
the monitor edit page.
There are some instances where associating a monitor to a CI alias that is unknown
to the BMC ProactiveNet Server is desirable. For example,
If you add the data collection (devices, monitors) before you add the service
model, you can set the aliases when the monitors are created.
If you have multiple BMC ProactiveNet Servers with one or more child servers
collecting data and feeding events to a parent or master BMC ProactiveNet Server,
you can associate a monitor to a CI alias on a child server.
The CI alias need not exist on the child server, either. If the child server does not
have a service model, the monitors events are not associated to a CI on the child
server. However, when the event is propagated to the parent or master BMC
ProactiveNet Server, the CI alias for the event is resolved to a CI alias in the
service model on the parent or master BMC ProactiveNet Server.
Associating a monitor to a CI in the Monitor edit page

You can associate a monitor to a CI alias that is unknown to the BMC ProactiveNet
Server through the Administration Console in the Monitor edit page, by using the
following steps.
To associate a monitor to a CI when the CI alias is unknown to the BMC

ProactiveNet Server
1 In the Administration Console, select a BMC ProactiveNet native monitor or an
adapter monitor and click Add or Edit.
The Add or Edit window opens and provides fields for CI ID and CI Alias.
2 In the CI ID and CI Alias fields in the Add or Edit window for the selected
monitor or adapter monitor, enter the values for the component ID and Aliases.
The component is now associated with the monitor or adapter monitor selected.
How aliases are used depends on how the BMC ProactiveNet

Servers are deployed
The deployment scenario for BMC ProactiveNet Servers can determine how aliases
are used, as in the following examples:
Multiple BMC ProactiveNet Servers using the same CMDB.
In this case, the same service model is shared and the CIs on the BMC
ProactiveNet Servers have the same alias.
Multiple BMC ProactiveNet Servers using different CMDBs.
In this case, there are multiple service models. The expectation is that the aliases
are the token IDs used by event sources and that the cell or other aliases are the
same.
Multiple BMC ProactiveNet Servers using a local cell or Service Model.
In this case, you are expected to set the same alias for the same CI.
18
Managing cells
This chapter describes how to manage and configure cells.
Production cells and test cells

A production cell is a cell that service operators and service managers use to monitor
the events and services associated with your IT resources in real time.
A test cell provides senior service managers and service administrators with a test
environment. For event management, a test cell provides KB developers with a test
environment for defining event classes, event management rules, policies, actions,
and collectors and testing their behavior with test event data.
Production and test cell naming and creation

The only way to distinguish a test cell from a production cell is by the cell name.
Adopt a naming convention for test and production cells that clearly identifies its
purpose.
You name a cell when it is created. The default production cell is created when you
install the BMC ProactiveNet Server. An additional cell can be created when you
install a BMC ProactiveNet Agent on a remote computer.
You use the mcrtcell command to create additional production or test cells on a
local computer where the cell is being created. For more information about syntax
and options available with mcrtcell, see the BMC ProactiveNet Command Line
Interface Reference Manual.
Production and test cell configuration

In BMC ProactiveNet Administration Console, assign the production and test cells to
a group. The default groups are MyTest and MyProduction.
Chapter 18 Managing cells 759
Viewing test cell data

You view test data in BMC ProactiveNet Administration Console.
To view test event data, collectors, and actions, select a test cell in the Event
Management Policies view.
To view and create test event management policies, select a test cell in the Event
Management Policies view.
To view test service model components, use the Find tool in the Services view and
select a test cell.

The more you customize your cell to fit your needs, the more efficiently the cell
works. All configuration tasks are optional.
Table 108 on page 760describes the cell configuration tasks.
Table 108: Cell configuration tasks
Task
Description
Create additional cells.
the BMC ProactiveNet Command

When you install BMC Impact Manager on a system, one cell is

installed. You can create additional cells by running the
mcrtcell command.
2
If you created multiple cells for an environment, you can create

separate configuration files for each cell.
If you created multiple cells for an environment, configure the

cells so that they can communicate with other cells in the network. on page 626
Events can be processed locally or selectively propagated to

other cells. To configure the event slots that must be propagated on page 765
when they are changed configure the propagation configuration
file.
If inbound connections to the cell are disallowed in a protected

environment, the connection has to be established within the
protected zone to allow a connection between an external client
and a cell in the protected zone.

on page 770
To add a time stamp to a slot so that the date and time is

recorded when the slot is changed, configure the mcell.modify
file.
Configuring slots for time

stamping on page 771
Creating cell-specific configuration

files on page 764
Task
Description
If desired, you can encrypt communication among the various

components.
Configuring encryption on page

772
Set the default client parameters executing CLI commands.
the BMC ProactiveNet Command

Configuring mcell.conf parameters

The mcell.conf configuration file installed with the cell enables it to run without any
additional configuration.
You can change the configuration parameters in the mcell.conf file to customize the
cell for your particular IT infrastructure and environment. You can override some
parameters using command line arguments when you start the cell. For more
To configure the mcell.conf file using a text editor

1 Open the mcell.conf file in a text editor.
The default location is MCELL_HOME \etc.
2 Create line entries using the format Parameter=Value based on the syntax rules
described in Rules for cell configuration parameter syntax on page 761.
3 Save the changes.
4 Either reload the cell configuration or restart the cell for the changes to go into
effect. For more information, see Reloading cell configuration on page 777.
Rules for cell configuration parameter syntax

One parameter per line, in the form: Parameter=Value
where the Value extends to the end of the line

Typically, the value for a parameter is a Boolean value, a string, or a path. The
supported Boolean values are Yes/No and On/Off.
The Boolean values are not case sensitive, so, for example, On, ON, on, and even
oN are equally valid.
Do not enclose the value in quotation marks unless you want the quotation marks
to be part of the value.
Times are stated in seconds unless otherwise specified.

By default, all parameter settings are disabled, that is, commented out with a #
sign at the beginning of the line of code. Enable a parameter setting by removing
the # sign that precedes it.
For more information on cell configuration parameters, see mcell.conf file

parameters on page 841
Specification of path values

Parameters that have path values contain the string FileName or DirName, for
example TraceConfigFileName or SystemLogDirName.
Path values can be stated as:
absolute pathstarts with slash (/) or backslash (\), or on Windows, with a drive
designator (for example, D:)
runtime relative pathstarts with ./ or ../. The path is relative from the cells
working directory. The working directory is the root directory (/) when it runs as
a daemon or a service. When running in foreground, it is the directory where
mcell is started.
configuration relative pathall other path values are relative from the cells log
file directory, or, for program paths, from the kb\bin directory.
Path values can contain the substitution parameters $VAR or %X. Any $VAR parameter
is substituted by the value of the environment variable VAR. The following table lists
the possible %X substitution parameters.
Table 109: Substitution parameters for %X in path value parameters
Parameter
Description
%H
cell home directory (MCELL_HOME)
%C
cell configuration directory (etc/ CellName)
%V
variable data directory (var/ CellName)
%L
log file directory (log/ CellName)
%T
temporary file directory (tmp/ CellName)
%B
Knowledge Base binary directory (kb\bin)
%P
program name
%N
cell name
Parameter
Description
%U
unique number for process
Modifying SystemLogDirName, SystemTmpDirName, SystemVarDirName, and

KBDirName
With the cell configuration parameters SystemLogDirName and SystemTmpDirName,
users can specify alternative path locations for the system defined log and tmp
directories. Their default values are % H/log and %H/tmp. To enable file name
specifications that refer to these alternative locations, use the substitution parameters
%L for the log and %T for the tmp directory. They are substituted by the specified
path to the log and tmp directory, respectively.
If you change the default value for the SystemVarDirName parameter or the
KBDirName parameter in the mcell.conf file, you must also change the value in the
statbld.conf file. If you fail to do this, the cell loses persistency and the mcdb file is
not created, because the StateBuilder is configured from statbld.conf file and has no
input from the mcell.conf file. As a result, StateBuilder does not know where to find
the log files or the KB directory it requires.
ConnectionPortRange syntax
Figure 142 on page 763 shows the syntax of ConnectionPortRange.
Figure 142: ConnectionPortRange syntax
PortRange = PortSequence{, PortSequence}
PortSequence = Port[-Port
A range is a number of sequences, each of which is a consecutive range of ports. The

cell attempts to access all ports in the specified order. The default is to use any of the
ephemeral ports.
For example,
18281840 specifies a range of ports 1828 through 1840
1828, 1829, 1840 specifies the sequence of ports 1828, 1829, and 1840
Scale factors for enhancing configuration parameters

You can add scale factors to numerical configuration parameters in the mcell.conf
file. Table 110 on page 764 lists the scale factors that are available in BMC
ProactiveNet. Scale factors are case sensitive.
Table 110: Scale factors that can be used for configuration parameters in the mcell.conf file
Symbol
Meaning
Factor
seconds
minutes
60
hours
3600
days
86400
weeks
604800
k, K
kilo
1024
mega
1048576
giga
1073741824
If you add a scale factor to a numerical configuration parameter value, then that
value is mulitpled by the scale factor that you use.
For example, if you add the minutes scale factor to the following parameter
#MessageBufferReconnectInterval=2
so that it becomes
#MessageBufferReconnectInterval=2m
then the value for that parameter is equal to 120 (2 times the scale factor for minutes,
which is 60). Without the scale factor, the parameter specific unit of measure is used,
which is seconds for most time related parameters. So in this example, without the
scale factor, the value for the #MessageBufferReconnectInterval is 2 seconds.
With the scale factor, the value changes to 2 minutes (120 seconds).
Creating cell-specific configuration files

By default, one set of configuration files is installed during installation of the BMC
Impact Manager . These files are located in the MCELL_HOME\etc directory and
multiple cells on a host can use them. You can also create unique configuration files
for individual instances (cells) as needed.
To create cell-specific configuration files

1 Using a text editor, edit the configuration file and customize it for that cell and
save it.
You can copy and edit any configuration file located in the MCELL_HOME\etc
directory.
2 Either reload the cell configuration or stop and start the cell so that the changes
take affect.
When a cell starts, it searches for configuration files in the MCELL_HOME\etc
\ CellName directory. If no configuration file is found, the cell uses the

configuration file in the MCELL_HOME\etc directory. For example, if you
copy the mcell.conf file into the MCELL_HOME\etc\ CellName directory and
modify it, the cell reads that mcell.conf file and all other files in the
MCELL_HOME\etc directory.
All cells use the following cell-specific directories:

MCELL_HOME/etc/ CellName contains cell-specific configurations (including
the Knowledge Base)
MCELL_HOME/log/ CellName contains the cells default trace file

MCELL_HOME/var/ CellName contains the persistent state of the cell (mcdb,
xact)
MCELL_HOME/tmp/ CellName contains the cells temporary files

Events can be processed locally or selectively propagated to other cells. To configure
the event slots that must be propagated when they are changed, and in which
direction (forward/backward), you configure the propagation configuration file
mcell.propagate. The mcell.propagate file lists all of the slots whose modifications
will be propagated.
In addition, using the gateways, events can be propagated to a third-party program
in a specific format that is described in a gateway configuration file, gateway.
GWType.
The default location for these files is MCELL_HOME\etc.
When an event has been propagated to a destination and that event is later modified,
the modifications are then propagated to the same destination. The event can be
propagated through a Propagate rule. If the destination is a gateway, gateway
configuration rules also apply.
For the mcell.propagate file to be effective, one or more Propagate rules must be
running. For information about Propagate rules, see the BMC Knowledge Base
Development Reference Guide .
The format is Slotname = Value, where:
Slotname = slot name or CLASS for class-specific slots
Value = sequence of { b = backward f = forward }
You can specify a slot in the base CORE_EVENT class. However, if you want to
specify a slot outside those in the base CORE_EVENT class you must use the CLASS
specifier, which means that all class-specific slots are propagated in the direction given.
Table 111 on page 766 lists the parameters in the mcell.propagate file and the
defaults.
Table 111: Default mcell.propagate options
Parameter
Action Performed
Default Values
CLASS
propagates changes to the class-specific slots up (forward)

within the cell hierarchy
mc_modhist
propagates changes to the mc_modhist up (forward) within the

cell hierarchy
This is a system defined slot that requires such propagation.

mc_notes
propagates changes to notes attached to an event up (forward)

within the cell hierarchy
mc_operation
s
propagates all of the operations that have been performed on

that event
mc_owner
propagates the person to whom the event has been assigned
mc_priority
propagates the priority of an event
bf
msg
propagates any messages associated with the event
bf
repeat_count
propagates changes to repeat_count up (forward) within the

cell hierarchy
severity
propagates severity value changes up (forward) within the cell

hierarchy
status
propagates status value changes in both directions, backward

and forward, in the cell hierarchy
bf
If you have multiple remote cells installed, you might want to use event propagation
to distribute the event processing load among the cells or to back up events on
another cell for failover.
Figure 143 on page 767 illustrates a cell network that is collecting and processing
numerous events in a distributed environment.
Figure 143: Distributed event management using event propagation
In this illustration, the lower-level cells process the source events and then propagate
(or forward) the events on to higher-level cells according to a Propagate rule or an
Event Propagation policy. As events pass through a series of cells, the cells discard
unneeded events, identify and leave behind unimportant events, and resolve some
of the problems reported by other events.
To enable event propagation, perform the following tasks:
enable cell-to-cell communication in mcell.dir
configure propagation parameters in mcell.conf
specify the slots whose modification has to propagate in mcell.propagate
either write a Propagate rule or define an Event Propagation policy
How unpropagated events are buffered

When the cell is started, the buffers are set to a minimum workable size. The default
minimum size is 5000 events for each destination buffer and 5000 requests for the
propagation buffer.
If the cell cannot propagate events, the cell stores the events to be propagated in the
destination buffers and the requests for propagation of those events in the
propagation buffer. When the buffers become full, the cell automatically expands the
buffer size by a specified percentage (10 percent, by default), unless the buffer has
exceeded a maximum size. By default, the maximum buffer size is unlimited,
although the practical limit of the buffer size is the amount of available memory.
Once the maximum defined buffer size is reached, additional requests will fail.
When automatic expansion occurs, an MC_CELL_RESOURCE_EXPANSION event
is generated.
An expanded buffer will contain free space after propagation has resumed. To free
memory resources, the buffer will be reduced when it contains more than the
specified amount of free space. Reduction will leave enough free space to avoid the
need for an immediate expansion. The buffer will never be reduced below the
specified minimum size. When the buffer is reduced, an
MC_CELL_RESOURCE_REDUCTION event is generated.
Parameters controlling the buffer size are located in the mcell.conf file. For
information on configuring these parameters, see Propagation parameters on page
855.
About mcell.dir, the cell directory file

The mcell.dir file is created during product installation. It acts as the cell directory
file and contains the list of cells, servers, and gateways known on a specific
computer. Upon startup, the cell reads the mcell.dir file and associates itself with the
appropriate name, encryption key, address information, and port number. In
addition, it reads this information for the other cells to which it connects.
The mcell.dir file for a cell has an entry for each cell and the servers and integration
gateways to which the cell connects. Figure 144 on page 768 shows the format and
an example of an entry in the mcell.dir file.
Figure 144: Format of an entry in the mcell.dir file
#
## One line per component :
# <Type> <Name> <EncryptionKey> <IpAddress/Port>
# <Type> = cell | gateway.type
#
# cell
EncryptionKey
Host/1828
# admin
ImpactAdministrationServerName
UserID/Password
3084
Each parameter in the file is defined as follows:
Host/
Attribute
Description
Type
type of component. It can be

cell cell name
gateway. typeGateway of type type
gateway.jServer - predefined jServer gateway type
admin - named Impact Administration Server (IAS)
Name
Name is an abstract name for the component. Component names are not case-sensitive and
may be any alphanumeric string, including underscores (_).
EncryptionKey
String to be used as part of the key for the encryption of the communication between a cell
and the component. Default value is mc.
Note: If the string has an odd number of characters, the last character is ignored.
For an IAS component, the string must have the form UserID / Password, or be 0. If the
value is non-zero, the indicated UserId and Password are used as IAS login credentials.
IPAddress/Port Host name or IP address and port number on which the component is listening. Default
port number for a cell is 1828.
Example of the mcell.dir file

Figure 145 on page 769 shows an example of the mcell.dir file with typical
component entries.
Figure 145: Example of the mcell.dir file and its entries
#
## One line per
# <Type> <Name>
# <Type> = cell
#
cell
cell
admin
cell
component :
<EncryptionKey> <IpAddress/Port>
| gateway.type
bos-71
local
ias1
sim1
mc
mc
mc
Mac/FreeAI1
bos-71/1828
127.0.0.1/1828
bos-71/3084
pprod001:1828 bprod001:1828
Conventions for mcell.dir file entries

The following conventions apply when creating entries for the mcell.dir file:
Cells may be grouped into separate mcell.dir files readable only by certain users
or groups (domains).
A cell must be configured to communicate with, at a minimum, the cells to which
it propagates events. A cell does not need to be configured to communicate with

the cell from which it receives events, even for backward propagation.
The mcell.dir file may define any number of entries, but each entry must be on a
separate line.
You can place mcell.dir files on remote mountable partitions or distribute them
using rdist, tftp, or any other distribution mechanism.

If inbound connections to the cell are disallowed in a protected environment, the
connection has to be established within the protected zone to allow a connection
between an external client and a cell in the protected zone. To connect to the cell, the
client issues a passive connection; that is, it waits until the cell establishes the
connection to the client.
Note
A passive connection is only possible with the server type clients, such as the cell
and gateway clients.
Configuring the client for passive connections

On the client side, the mcell.dir file has to indicate that the destination cell is located
in an isolated protected zone.
To configure the client for passive connections

1 Open the mcell.dir file in a text editor.
The default location is MCELL_HOME\etc.
2 For the destination cell, replace Host:Port with 0 as shown in the following
example:
cell
cellName EncryptionKey 0
3 Save the changes.

4 Either reload the cell configuration or stop and start the cell.
When a cell or gateway client needs to connect to an isolated destination cell, it
cannot establish a connection because it does not have the IP address and port
number of the cell. Instead, the cell or gateway client registers the destination and
waits for a connection from it.
Configuring a cell for passive connections

On the cell side, an indication is needed that a client could be waiting on a connection.
To configure a cell for passive connections

1 To configure a cell for passive connection, you must create a data object and
specify how to control it, as shown in below.
MC_CELL_PASSIVE_CLIENT ISA MC_CELL_HEARTBEAT ; END
The cell slot, as defined in the MC_CELL_HEARTBEAT superclass, gives the

name of the passive client. The enable slot in the superclass specifies whether or
not monitoring and reconnection is enabled. The cell attempts to connect to
passive client targets as configured with the standard connection parameters. As
soon as a connection is established, the connection is reversed. At that moment,
the client takes up the connection and behaves as an ordinary client.
Monitoring passive targets

The cell may not be aware that a connection has been terminated when a connection
from a passive client to a cell is terminated. The passive client cannot try to
reestablish the connection, nor can it signal the cell to reestablish the connection. To
avoid such situations, the cell monitors the passive client, based on the standard
heartbeat monitor mechanism. Then, when a disconnect is detected, the cell attempts
to connect to the passive client target.
Configuring slots for time stamping

Each event has an mc_modification_date slot that contains the time stamp of the
last modification of the event. Only select slot modifications set this time stamp. To
add a time stamp to a slot so that the date and time is recorded when the slot is
changed, you must configure the mcell.modify file. The mcell.modify file contains
the names of the slots that affect the mc_modification_date slot. When one of the
slots listed in the mcell.modify file is modified, the mc_modification_date slot is
set with the time stamp of this change.
To configure slots for time stamping

1 Open the mcell.modify file in a text editor.
The default location is MCELL_HOME\etc.
2 Create a line entry containing the name of the slot whose modification is to be
time stamped. Figure 146 on page 772 shows an example of the mcell.modify file.
Figure 146: mcell.modify file
# Configuration of slots affecting mc_modification_date when modified
# Format :
# SlotName
# Special name : CLASS : specifies all class-specific slots
status
severity
mc_priority
repeat_count
CLASS
3 Save the changes.

4 Either reload the cell configuration or stop and start the cell.
Configuring encryption
You can encrypt communication among the various BMC Impact Solutions
components. To enable encryption, make the appropriate settings in the following
locations:
the cells configuration file mcell.conf
the CLI configuration file mclient.conf
the BMC Impact Administration server used by BMC ProactiveNet
the cell directory file, which is MCELL_HOME\etc\mcell.dir by default
mcell.conf file settings that control encryption

The primary settings controlling encryption are in the cell configuration file
mcell.conf. The following settings control encryption:
Encryption
ForceEncryption
EncryptionKey
If Encryption is set to Yes, encrypted communication to and from the cell is enabled,
but not required. For example, if a BMC ProactiveNet Administration Console does
not have encryption enabled, then the communication with that particular BMC
ProactiveNet Administration Console console is not encrypted.
ForceEncryption requires encryption for all communications. If the BMC

ProactiveNet Administration Console attempts an unencrypted connection to the
cell, the connection is rejected.
The encryption process uses the EncryptionKey value as part of the encoding key. If
there is no encryption, the EncryptionKey value has no effect.
mclient.conf file settings that control encryption

All CLIs can use an mclient.conf file to determine encryption functionality. The
parameters are
Encryption
EncryptionKey
For more information about the CLI configuration parameters, see the BMC
ProactiveNet Command Line Interface Reference Manual.
mcell.dir file settings that control encryption

The mcell.dir file contains a field for an EncryptionKey. At installation, the default
EncryptionKey value is set to mc. BMC Software recommends that you modify the
value for security.
The string specified as the encryption key is transformed to a binary value as follows:
Characters of the encryption key are grouped in pairs. If the string has an odd
number of characters, the last character is ignored.
Each pair is converted to an 8-bit value. The first character of the pair determines
the four most significant bits, the second character determines the four least
significant bits.
A character in the hexadecimal range (0-9, A-F, a-f) is converted to the
corresponding hexadecimal value (for example, 8 gives the value 8, B gives the
value 11).
Any other character is converted to its ASCII code modulo 16.
Encryption behavior between cells and components

This section describes the encryption behavior of cells and components during
communication. The following actions occur when a BMC Impact Solutions
component initiates communication with a cell:
1 The component scans the cell configuration file, mcell.dir, for that cells
connection information.
2 BMC ProactiveNet Administration Console retrieves the cells connection
information from the BMC ProactiveNet Server.
3 The component opens a connection to the cell.
If the cell has Encryption=yes, the component can use encrypted or non-encrypted
communication. The component must use encrypted communication if the cell has
ForceEncryption=yes and Encryption=yes.
If the communication is encrypted, both the cell and the component must use the
same EncryptionKey values to establish communication.
Information retrieval
A component must have the address and port of a cell to establish communications
with it. To establish encrypted communications, the component must also have the
encryption key of the cell. BMC ProactiveNet Administration Console and the CLI
commands determine the information in different ways:
BMC ProactiveNet Administration Console acquires the information from the
BMC Impact Administration server (cell_info.list ).
BMC Impact CLI commands obtain the information by determining the server
location using one of the following methods:

directly from the CLI command
from CLI configuration parameters in mclient.conf

from mcell.dir if you use the -n CellName option
Default values
The default value for CellName is the name of the host (HostName). The default value
for the port is 1828.
When the mcell.dir file is present, the default value is EncryptionKey=mc at
installation. BMC Software recommends that you modify this value for security.
If the mcell.dir file is absent on the host and you do not specify an encryption key,
the CLI command uses 0 (zero) as the default value for EncryptionKey. This value
enables encrypted communications.
Note
You can disable encryption by setting the configuration parameter to

Encryption=No. You might want to use this setting to disable encryption while tracing.
Mandatory key specification conditions

You must specify the encryption key if the following conditions apply:
you execute the CLI command on a host without an mcell.dir file
the cell has an encryption key other than 0 (zero)
These conditions apply with the default installation. However, if the mcell.dir file is
present on the host, and the file specifies the encryption key, you are only required
to specify the cellName.
Limiting cell access

A client is allowed to connect to the cell if its IP address matches the general
AllowConnectionFrom as well as the client type-specific Allow*From.
Figure 147 on page 775 shows an example of masking syntax.
Figure 147: Masking syntax
AddrMaskList = AddrMask {':' AddrMask}
AddrMask = Addr ['/' Mask]
Addr = Nr '.' [Nr '.' [Nr '.' [Nr]]]
Mask = Addr | Nr Nr = 0..255
The following conventions apply:

An abbreviated Addr or Mask is expanded with zeros.
A numeric Mask (number without trailing dot) gives the number of 1 bit.
An omitted Mask defaults to all bits set to 1.
A connection is allowed if the source address ANDed with the Mask matches Addr
ANDed with the Mask .
When the Mask is all zeros, any address matches regardless of the value of Addr. For
all Mask bits whose value is one (1), the equivalent bits in Addr must match the
equivalent bits in the source address.
Table 112 on page 776 lists the IP address parameters.
Table 112: IP Address parameters

Parameter
Description
AllowConnectionFrom=0./0
all systems allowed

(same as 0.0.0.0/0)
AllowConnectionFrom=0./32
no system allowed
(00.00.00.00 is not a valid IP address)
AllowConnectionFrom=198.12./255.255.
any system from the 198.12. xx . xx

network can connect
AllowConnectionFrom=127.0.0.1/1
enables any host with an IP address lower than

128.0.0.0, because it indicates there is only 1 bit in the
mask
Only the highest-order bit is considered and must be the
same as 127, which is a 0 bit.
AllowConnectionFrom=198.12.33./
255.255.255.:198.12.92./255.255.255.
systems on the 198.12.33. xx and 198.12.92. xx

networks may connect
The default is 0./0, indicating that the server should accept connections from any
source. Usually this is useful only for testing or debugging, or for use with a system
that is isolated from the network.
To specify one single address, specify the address without a mask, or use a 32-bit
mask. The following examples are equivalent ways of specifying a single address:
127.0.0.1
127.0.0.1/32
127.0.0.1/255.255.255.255
When you specify more than one address per mask pair, a system that matches at
least one of the pairs can accept a connection.
Connection attempt using invalid encryption key

An attempt to connect to a cell using an invalid encryption key or from an
disallowed address generates an internal event MC_CELL_UNALLOWED_CONNECT. This
event contains a slot, reason, that includes the reason for the refused connection.
Configuring cell exception handling

Cell exception handling is configured using the CellExceptionHandlingEnabled
parameter in the mcell.conf file. By default, CellExceptionHandlingEnabled is set to
Yes. This setting ensures that when an exception occurs, the cell:
catches the exception
collects dump data for problem analysis, including cell trace files, cell state files
and a core dump, if possible
generates an internal event to report the abnormal termination

restarts itself
The generated internal event is of class MC_CELL_ABORT, which is a subclass of

MC_CELL_STOP. MC_CELL_ABORT has the following slots:
exception a textual description of the exception that has been caught
dump_datathe path of the file that contains the collected dump data
You may send the dump data to BMC Software Support for analysis.
If CellExceptionHandlingEnabled is set to No, when the cell encounters an
exception, the cell process will terminate and will not become available until the cell
process is started manually.

The cell does not automatically reconfigure itself, but you can customize and reload
the configuration after you have made configuration changes without restarting the
cell.
To reload cell configuration

To trigger the reconfiguration, perform one of the following actions:
1 Send a hang-up signal on UNIX.
2 Run the mcontrol command on UNIX or Windows. For information about the
mcontrol command, see the BMC ProactiveNet Command Line Interface Reference
Manual.
Table 113 on page 778 lists the specific instances in which the reconfigure feature
can be used and the effect that results from its use.
Table 113: Files for cell reconfiguration
Type
cell directory
Name/Directory
a
mcell.dir
cell tracing
mcell.trace
cell
configuration
mcell.conf
Result of reconfiguration
This internal directory is replaced with new contents from the
mcell.dir file. Associated data objects are replaced as well.
Connected clients and destinations remain connected, even if the
corresponding directory entries are modified.
Tracing is adapted and has the same effect as through the
mcfgtrace CLI.
The cell restarts automatically.
mcell.propagate
mcell.modify
KB collector
kb\collectors
KB program
kb\classes
\kb\rules
\kb\lib
\kb\bin
KB data
kb\data
\kb\records
a For mcell.dir and mcell.trace, a hang-up signal on a UNIX platform performs maximum reconfiguration
without a cell restart. For information about restarting a cell, see Interpreting cell execution failure
codes on page 830.

The installation process automatically starts a cells service. However, as changes are
made to a cells configuration files or knowledge base, you must stop and start the
cell to accept the changes.
Stopping or starting a cell on UNIX computers

By default, a cell runs as a UNIX daemon. You override this behavior with a
command line option, not a configuration file parameter.
Before you begin

A cell can be installed as owned by any user. Only users with execute permission on
the mcell binary can start the cell. All users with execute permission on the mkill or
mcontrol CLIs can stop the cell. However, if a user without root permissions
attempts to start the process, the following issues must be considered.
External actions run as the user ID that started the process. Those actions are
defined in %MCELL_HOME%\etc\ CellName \kb\bin on Windows platforms

and in $MCELL_HOME/etc/ CellName /kb/bin on UNIX platforms.
Actions are defined in .mrl files located in the kb/bin directory and listed in .load
in that directory. The action programs or scripts can be located in the kb/bin/A or
kb/bin/ Arch directory. They can also be located anywhere else on the system.
The user who starts the cell must be able to write to log and trace files in the
directories specified through configuration parameters SystemLogDirName,
SystemTmpDirName, and SystemVarDirName. Default values for these are the log
and tmp subdirectories of MCELL_HOME.
To stop a cell on UNIX computers

mkill -n cellName
If no cell name is provided, mkill attempts to stop a local cell whose name is the
same as the local host name. For more information about the mkill command, see
the BMC ProactiveNet Command Line Interface Reference Guide.
To start a cell on UNIX computers

mcell -n cellName
It is possible to start a cell without specifying a cell name. If you start a cell
without any options, the command attempts to start a cell with the same name as
the host. You must set the MCELL_HOME environment variable to point to the
directory in which the cell is installed. The home directory also can be indicated
using the option -l followed by the path to the home directory, instead of defining
it in the environment. To learn more about using the mcell command, see the
BMC ProactiveNet Command Line Interface Reference Manual.
Note
You can change all configurable cell parameters by making changes in the
configuration file, mcell.conf. When you start the cell, the cell looks for the
configuration file in the default location, MCELL_HOME\etc\cellName
\mcell.conf. Use the -c option with the mcell command to have the cell look for
the configuration file in a specified location.
Starting or stopping a cell on Windows computers

On Windows computers, you can stop a cell by using one of the following options:
Windows Services
the net stop command
the mkill command
On Windows computers, you can start a cell by using one of the following options:
Windows Services
the net start command from a command prompt window
To stop a cell on Windows platforms by using services

1 Open the Services window by choosing Start => Settings => Control
Panel => Administrative Tools => Services.
2 Select mcell_ cellName .
3 Click Stop Service.
To stop a cell on Windows platforms by using the net stop command

1 Select Start => Programs => Command Prompt.
2 Enter the following command from the command line:.
net stop mcell_cellName
To stop a cell on Windows platforms by using the mkill command

1 Choose Start => Programs => Command Prompt.
2 Enter the following command from the command line:
mkill -n cellName
Note
If you do not use the -n option when stopping a cell, the default cell, named
hostName, is stopped.
To start a cell on Windows platforms by using services

1 Open the Services window by choosing Start => Settings => Control Panel =>
Administrative Tools => Services.
2 Select mcell_ cellName.
3 Click Start Services.
To start a cell on Windows platforms by using the net start command

1 Select Start => Programs => Command Prompt.
2 Enter the following command:
net start mcell_cellName
.
Note
When used without the -d option, mcell contacts the Service Control Manager
to start itself as a service. It uses mcell_%N as a service name. %N is the cell
name as specified by the -n option. Without the -n option, the default cell name
is the hostname.

Your access to additional Impact Managers (cells) depends on the access privileges
assigned to you by your administrator. You may be able to add cells to your console
that are not currently displayed in the navigation pane. You can view the available
cells versus the cells already selected for monitoring on the Impact Managers subtab
of the Configure Administration Settings dialog box in the BMC ProactiveNet
Each cell must belong to a group, so when you add cells to your console, you add
them to a group. A group can contain just one cell, or it can contain multiple cells,
and you can create as many cell groups as you need. Cell groups enable you to
organize cells into manageable units.
By default, two cell groups labeled MyProduction and MyTest are created during the
installation process. You can edit and delete these cell groups.
You can create cell groups and name them according to your organizational needs.
For example, you can create a cell group for each of the office locations in your
enterprise. Also, as your environment changes, you might need to change the names
of the cell groups that you create.
To create a new cell group

subtab.
3 In the Group text box, enter a new group name.
4 Click Add.
The new cell group is added to Selected Impact Managers.
5 Click OK.
The new cell group is displayed in the navigation pane.
To change a cell group name

subtab.
3 From Selected Impact Managers, select a cell group.
4 In Group, enter a new name for the cell group.
5 Click Edit.
6 In the Change Group Name Configuration dialog box, click Yes to accept the
name change.
7 Click OK.
To remove a cell group name

subtab.
3 From Selected Impact Managers, select the group that you want to remove.
4 Click Remove.
5 In the Delete Group confirmation dialog box, click Yes to remove the cell group.
6 Click OK.
To add cells to a cell group

subtab.
Available Impact Managers lists all BMC Impact Managers (cells) to which you
are connected, as shown in Figure 148 on page 783.
Figure 148: Available Impact Managers list for a user account with
administrator permissions
3 From Available Impact Managers, select the cell that you want to add to the
console.
4 From Selected Impact Managers, select the group to which you want to add the
cell.
Tip
You can select multiple cells at one time, as follows:
To select adjacent cells, select the first cell, hold down the Shift key, and select
the last cell.
To select nonadjacent cells, select a cell, hold down the Ctrl key, and select each
of the other cells.
5 Click the right arrow to move the selected Impact Manager to the selected Impact
Manager group.
Tip
You can also select a cell from Available Impact Managers and drag it to the
appropriate cell group in Selected Impact Managers.
6 Click OK.
The cell that you added is displayed in its cell group in the navigation pane.

Event processing metrics are internal counts maintained on cell performance
categories in connection with event processing. These metrics count the following
items:
number of events received, including erroneous ones
number of events containing errors
number of events dropped by rules (Filter, Regulate)
number of events removed from the event repository during cleanup
number of events propagated, including sendto
number of events added to the event repository, that is, entering the permanent
context
Calculation is performed on a 60-second basis, so every minute the counters are

restarted. Counts from the last five minutes are retained. Running counters are reset
only on demand.
The resulting metrics are:
short termtotal count of the last complete one-minute interval

medium termsum of the five last, completed one-minute intervals
long termrunning total
Metrics are stored in MC_CELL_METRIC data objects, one object instance for each
metric. Each metric mentions the subject. For each of the short-, medium-, and longterm results, it contains the length of the interval, in seconds, and the total count. An
average per second is also provided, rounded to an integer. Other averages per
second, minute, or hour can be calculated by the application from this information, if
needed.
A configuration parameter, CellMetricsEnabled , determines whether metrics are
collected or not.
The mcontrol CLI is used to switch metric collection on and off, and to reset the
counters. Short- and medium-term metrics are reset whenever metrics are disabled.
Metrics can be retrieved through rules by data object access, or through a command.
The mgetinfo CLI can use that command.
The received event counter does not include incoming messages that cannot be
parsed as events. It does include events of nonexistent classes or events with
erroneous slots. These are added to the erroneous event counter. Internally
generated events are counted as received events. Dropped events include those that
are dropped when an event with the same universal ID exists.
Table 114 on page 785 lists the metrics data objects MC_CELL_METRIC slots.
Table 114: MC_CELL_METRIC slots
Slot
Description
description
metric description
long_average
long-term average, per second
long_interval
long-term interval lengths, in seconds
long_total
long-term total count
medium_average
medium-term average, per second
medium_interval
medium-term interval lengths, in seconds
medium_total
medium-term total count
short_average
short-term average, per second
short_interval
short-term interval lengths, in seconds
short_total
short-term total count
Slot
Description
subject
metric subject name
Subject names available are:

ReceivedEvents
ErrorEvents
DroppedEvents
StoredEvents
RemovedEvents
PropagatedEvents
CLI commands for collecting metrics are:

mcontrol metrics on|off|reset
mgetinfo [-v] metrics

Whenever a client connects, disconnects, or modifies an event, the cell generates an
internal event to represent this operation. Such events are only generated for certain
clients configured by means of the ReportConnectClients and
ReportModifyClients settings.
The parameter value is interpreted from left to right. Settings that conflict with
previous settings override the previous ones. Table 115 on page 786 lists the
defaults for these two parameters.
Table 115: Default values for client parameters
Parameter
Value
ReportConnectClients
browser, Console, mcontrol, mkill, mposter, msetmsg, msetrec
ReportModifyClients
mposter, msetmsg, msetrec
Every parameter corresponds to a reporting clients set. Such a set has a positive and
a negative list. Clients that belong to the positive list will have their operation
reported while operations performed by clients on the negative list will not be
reported. Clients that are not named in the parameter are considered to be on the
default list. The default list initially is the negative list. The default list can be
modified through a special setting of the parameter.
A value for a reporting configuration parameter consists of a comma separated
sequence of client names. Every client name can be prefixed with a minus sign (-) or
a plus sign (+). The client name prefixed with the minus sign (-) is added to the
negative list. When not prefixed, or prefixed with a plus sign (+), it is added to the
positive list.
The special value ALL in place of a client name refers to the default. Including ALL or
+ALL modifies the default list so it becomes the positive list. With -ALL, the default
list is the negative list. Both parameters could include - ALL, as this is the default
setting for clients that are not explicitly mentioned.
The superclass for client operation related events is MC_CELL_CLIENT. The following
table lists the slots.
Table 116: MC_CELL_CLIENT slots
Slot
Data
client_location
the location of the client as IPAddress : Port
client_name
the client's name, as announced by the client, or noname
client_type
type of client, such as adapter, CLI, console, cell
There are three subclasses of this class:

MC_CELL_ALLOWED_CONNECT to represent successful client connection
MC_CELL_UNALLOWED_CONNECT to represent a refused connection
An attempt to connect using an invalid encryption key generates an internal

event, MC_CELL_UNALLOWED_CONNECT, that contains the slot reason, which details
why the connection is refused.
MC_CELL_DISCONNECT to represent a disconnect.
Another class, MC_CELL_MODIFIED_EVENT, represents the operation of modification

of an event. Table 117 on page 787 lists the slots.
Table 117: MC_CELL_MODIFIED_EVENT slots
Slot
Data
event
universal event ID of the event being modified
requestor
identification of the user that performed the modification

To set up cell tracing, configure
the trace configuration file, mcell.trace
tracing parameters in the mcell.conf configuration file
You can also configure cell tracing using the mcfgtrace command. For further
Configuring mcell.trace
The trace configuration file, mcell.trace, configures the tracing of the cells operation.
Tracing messages are divided in several levels. Every module of the cell can be
configured differently. An output destination can be determined per message level
and per module. Messages also can be disabled at the same granularity.
The default location is MCELL_HOME \etc.
The configuration commands in mcell.trace are incremental. Every new command
adds to the configuration, possibly overriding previous commands either completely
or partly.
Figure 149 on page 788 shows the format of a configuration line in the mcell.trace
file.
Figure 149: Format of configuration line in mcell.trace file
<Module>
SWITCH
<Level>
<Switch>
<Destination>
<Destination>
Table 118 on page 788 lists the parameters that must be defined in a configuration
line.
Table 118: Trace configuration file parameters
Parameter
Description
Destination
destination file name or predefined value for the selected trace messages or switch
predefined values:
nodisables these tracing messages
consolesends to the console device
stderrsends to standard error stream
Level
message severity value level

predefined values:
FATAL
INFORM
ERROR
VERBOSE
WARNING
Parameter
a
Module
Description
name of module, each of which corresponds to a particular category of information,
such as filtering or configuration; values are as follows:
ACTION
HEARTBEAT
RESULT
COLLECT
INTEVT
ROLES
COLLMAP
MC2TEC
RULES
CONFIG
MCBAROC
SERVICE
CONTROL
MESSAGES
SRVMGT
DATAPROC
METRIC
STATBLD
DBDATAID
PROPAGATE
SVCMGT
DBEVTID
QUERY
SVRCOMM
DBEVTTM
RECOVERY
SVRDIR
EVTLOG
RECTRL
SYNCH
EVTPROC
REGEX
SYSPROC
EXPORT
REGULATE
TRACE
FILTER
SWITCH
keyword that enables access to a sublevel or category of messages for a module
Switch
switch name
a You can also specify ALL or * (wildcard) for these parameters.
Configuring a destination for cell trace output

You can use the tracing parameters to configure the cell to output information to a
specified destination. The destination for cell trace output is determined by the value
of the DESTINATION parameter in the mcell.trace file.
Possible destinations for cell trace output are:
the console
the standard error stream
an external file or files

no trace output
In addition to sending trace output to one of these destinations, you also can send
trace output to another cell. For information, see Sending trace output to another cell
on page 791.
Sending trace output to a console

To send trace output to a console, open the mcell.trace file and set the DESTINATION
parameter to the value console.
Sending trace output to the standard error stream

To send trace output to the standard error stream of the command window where
the cell is running, open the mcell.trace file and set the DESTINATION parameter to
the value stderr.
If the cell runs as a service or daemon, all trace output that is configured to go to
stderr will be redirected to the file specified in the TraceDefaultFileName
parameter in the mcell.conf file.
If you specify for the trace output to go to stderr, the trace file is truncated every
time the cell restarts, and a new trace file is written.
Sending trace output to an external file

To send trace output to an external file or files, open the mcell.trace file and set the
DESTINATION parameter to the path and file name of the destination file.
The cell keeps the trace file open on both UNIX and Windows systems. On UNIX,
any attempt to remove the file will succeed. However, all trace output goes to an
invisible file that becomes visible when the cell is restarted.
A trace destination file can be located anywhere, but the BMC Impact Solutions
process must have write access to that location.
WARNING
The MCELL_HOME \tmp\ cellName directory is for temporary files only. A trace
file placed in that directory will be deleted by the cell when it restarts. To maintain
your trace file across cell sessions, place it in a different directory.
Disabling trace output

To disable trace output, open the mcell.trace file and set the DESTINATION parameter
to the value no.
Sending trace output to another cell

Sending trace output to a cell enables you to capture the traces of one or more cells in
a centralized location. To send the trace of one cell to another cell, the trace of the
originating cell should be produced as events. Those events can be sent to the
destination cell using a propagate rule.
To enable sending cell trace information to another cell, you must
configure which module/level combinations of trace messages will be produced
as events
add a propagate rule to the Knowledge Base to specify which trace log events
have to be propagated to which destination(s)
Once configured, the cell trace module will generate an internal event for each trace
log message.
Definition of the class of trace log events

Each trace message is represented through a single MC_CELL_LOG_MSG event, as shown:
ENUMERATION MC_LOG_LEVEL
10
VERBOSE
20
INFORM
30
WARNING
40
ERROR
50
FATAL
END
MC_EV_CLASS: MC_CELL_LOG_MSG ISA MC_CELL_CONTROL
DEFINES {
log_time: INTEGER;
-- Timestamp
log_program: STRING;
-- Name of the program generating the
message
log_module: STRING;
-- Name of the module producing the message
log_level: MC_LOG_LEVEL; -- Message level
log_src_file: STRING;
-- Source file name
log_src_line: INTEGER;
-- Source file line number
log_msg_id: STRING;
-- Unique message identifier (form BMCIMCxxxxxxC)
log_args: LIST_OF STRING; -- Message argument list
log_text: STRING;
-- Message text in origin's locale
};
END
The log_time date and time slot is an integer in timestamp format.

The textual representation of the log message log_text uses the originating cell's
local message catalog.
Configuring trace messages to be produced as log events

By default, a cell will not produce log events for its trace. This has to be enabled
explicitly using the TraceEvents configuration parameter in the mcell.conf file. The
value of this parameter is a comma-separated sequence of module:level
combinations. Each one is optionally prefixed with a + or a - sign to indicate
addition or removal, respectively, from the list. The special value ALL for module and
for level indicate all modules and all levels.
For example
TraceEvents=ALL:ALL,-ALL:VERBOSE
This setting specifies that events must be generated for messages from all modules,
of all but the VERBOSE level.
WARNING
Event tracing should be configured with care, as it may produce an excessive

number of events. In particular, VERBOSE level messages should not be configured as
events.
For more information about the trace configuration parameters in mcell.conf, see
Trace parameters on page 860.
Adding a propagate rule to the Knowledge Base to specify

which trace log events have to be propagated to which
destination(s)
The propagate rule syntax is described in the BMC Knowledge Base Development
Reference Guide.
The following is an example of a propagate rule for trace log events:
propagate PropTraceEvents: MC_CELL_LOG_MSG
to CentralAdminCell
END
Event processing errors

When an error occurs during the processing of an event, the cells trace displays an
error message and generates an internal event of class MC_CELL_PROCESS_ERROR.
Table 119 on page 793 lists the slots that are associated with the
MC_CELL_PROCESS_ERROR event.
Table 119: MC_CELL_PROCESS_ERROR slots
Slot
Data
error_code
the error number
error_goal
the part of the processing command that has the error
error_message
an error description message
error_source
the position in the rule source where the error occurred
event
the mc_ueid of the event that was being processed
Automatic notification of trace configuration changes

The cell automatically generates the following MC_CELL_LOG_CHANGED event when
trace configuration is modified for a cell:
MC_EV_CLASS: MC_CELL_LOG_CHANGED ISA MC_CELL_CONTROL
DEFINES {
log_module: STRING;
-- Name of the module
log_level: MC_LOG_LEVEL; -- Message level
log_destination: STRING; -- Destination file name
};
END
If the modification applies to all modules, then log_module=ALL.

If the modification applies to all message levels, then log_level=ALL.
The log_destination slot contains the full path to the destination file, in
normalized (UNIX) form. Other possible values are:
noindicates disabling
stderrindicates redirection to the standard error stream
consoleindicates redirection to the console terminal

When the cell runs as a daemon or a service, it has no standard output or error
stream. Tracing that is configured to go to stderr will be redirected to a file in this
case. The path for that file can be configured in mcell.conf. The default is
MCELL_HOME \tmp\ cellName \trace.
If the cell service setup fails, an error file, mcell.err, is generated. Additional service
setup failures can be appended to the original file, resulting in a file content of
multiple lines. Normally, each line corresponds to one failed service setup. This error
file contains exit codes specific to BMC Impact Manager.
Table 120 on page 794 lists the exit codes for BMC Impact Manager.
Table 120: BMC Impact Manager exit codes
Code
Description
invalid command line options used
bad home directory specification through option -l
no home directory could be determined
specified home directory is invalid
internal initialization failure
16
tracing configuration failed
17
system process handling module initialization failure
19
logging facility initialization failure
27
service control module initialization failure
29
Knowledge Base load failed
37
message handling module initialization failure
39
internal object initialization failure
47
event processing module initialization failure
49
saved state reload failed
57
query handling module initialization failure
59
service activation failed
67
internal object module initialization failure
69
metrics initialization failed
77
data processing module initialization failure
79
metrics activation failed
97
service setup failed
Using the BMC ProactiveNet Administration

Console to manage cells
You can also manage cells by using a pop-up menu in the Event Management
Policies tab or the Dynamic Data Editor tab in the BMC ProactiveNet Administration
Console to perform the following tasks:
connect and disconnect a cell
view cell information
edit cell alias formulas
edit cell properties
Connecting or disconnecting a cell

Use the Disconnect and Connect menu commands to connect or disconnect a cell
from BMC ProactiveNet Administration Console .
To connect or disconnect a cell

1 On the Event Management Policies or Dynamic Data Editor tab, right-click the
cell icon or name.
2 Select Connect or Disconnect from the pop-up menu.
This menu item toggles between Connect and Disconnect, depending on the
state of the cell when you right-click it.
Viewing cell information

Use the View Manager Info menu command to view information about and the
metrics associated with the cell selected.
To view cell information

1 On the Event Management Policies or Dynamic Data Editor tab, right-click a cell.
2 Choose View Manager Info.
The Impact Manager Info dialog box appears with cell property information
presented on the Info tab.
3 To refresh the information in the Workload tab of this dialog box, click Refresh in
the top right corner of the tab.
19
Configuring StateBuilder and
gateways
This chapter describes how to configure the StateBuilder and gateways for exporting
events and contains the following topics:

The StateBuilder is an executable, statbld.exe, located in the MCELL_HOME \bin
directory. It records saved states of the cell at regular intervals. When it starts, the
cell loads its last saved state (mcdb). All transactions it performs are stored in a
transaction file (xact). As soon as the transaction file reaches a certain size, or after a
certain period, the StateBuilder is started. It produces a new saved state from the
previous file and from the transaction file. When the cell terminates and restarts, any
trailing transaction file is first processed by the StateBuilder to produce a new saved
state. A history of saved states and corresponding transaction files can be kept. The
mcdb and xact files of that history have their timestamp in the file name.
All mcdb and xact files are located in the MCELL_HOME \var\ cellName directory.
The StateBuilder runs as configured in the cells mcell.conf file, which is detailed in
StateBuilder configuration file on page 798. The configuration of how the
StateBuilder itself operates is in the statbld.conf file.
Table 121 on page 797 lists the file naming conventions for the StateBuilder.
Table 121: StateBuilder file name conventions
File
Description
mcdb
state file the cell uses at startup
mcdb.0
new state file being generated
mcdb.t
saved state history files, where t = timestamp in hexadecimal epoch

Timestamp t in the mcdb.t file corresponds to the time when the state is created.
Chapter 19 Configuring StateBuilder and gateways 797
File
Description
mcdb.lock
lock file indicating StateBuilder activity
xact
transaction file generated by the cell
xact.n
terminated transaction file, where n=1 is the oldest transaction file
xact.t.n
terminated transaction history file corresponding to mcdb.t

Timestamp t in the xact.t file refers to the mcdb.t file to which the transactions lead.
There is also a statbld.trace file for the configuration of StateBuilder tracing. For
further information, see Configuring tracing for StateBuilder on page 807.
The StateBuilder uses the gateway.export file in conjunction with its statbld.conf file
to export event data. For more information, see the StateBuilder configuration file on
page 798and Exporting events on page 805.
StateBuilder configuration file

The state configuration file, statbld.conf, is located in the MCELL_HOME \etc
directory.
Table 122 on page 798lists the statbld.conf parameters, which use the same syntax
as all BMC Impact Solutions configuration files.
Table 122: statbld.conf Parameters
Parameter
Description
Default value
Export
uses Boolean values to specify whether to export data No
ExportConfigFileName
sets path to the gateway.export file
%H/etc/%N/
gateway.export
ExportDiscarded
indicates whether discarded events are included in

the export file
No
Discarded events are those that were dropped in the

first four rule phases: Refine, Filter, Regulate, and
New (Update).
ExportTriggerArguments
sets the arguments to be passed to the executable

serving as the export trigger program
blank; no arguments
Value is interpreted as a sequence of space-separated

arguments, so spaces within each argument are not
allowed.
ExportTriggerProgram
sets the program to execute after exporting data

The value is interpreted as a path. See the mcell.conf
file for special syntax for a path.
blank
Parameter
Description
Default value
StateHistoryCount
sets the number of state files to retain in the history
Each time a new saved state is produced, the oldest

state is removed.
statbld return codes

The following table lists the return codes for statbld.
Table 123: statbld return codes
Return code
Description
failed to build new mcdb
failed to update history files
10
early initialization failure
37
process handling module initialization failure
47
StateBuilder specific file access initialization failure
57
transaction file handling initialization failure
67
failed to load KB classes
77
server directory load failure
87
internal table initialization failure
97
detected running StateBuilder (mcdb.lock)
Gateway configuration
This section discusses general message formatting that applies both to StateBuilder
export and to gateways.
Gateway specific message formats are described in a gateway configuration file. The
location of this file for gateway of a particular type is determined from the Gw Type
ConfigFileName parameter of the cell. Its default value is %H/etc/gateway. Type
where Type represents the type of gateway.
Example default parameter values for TEC and jServer gateways:
GwTECConfigFileName=%H/etc/gateway.TEC
which means: $ MCELL_HOME /etc/gateway.TEC
GwjServerConfigFileName=%H/etc/gateway.jServer
which means: $ MCELL_HOME /etc/gateway.jServer

A gateway configuration file contains parameter settings in the form of
parameter=setting.
Parameters can be specified differently for new events and for event modifications.
The parameter name must be suffixed with
.new for new events
.mod for event modifications
Without a suffix, the setting is assumed to be on both categories. Both the contents of
a message and its format are specified using parameters.
Gateway predefined variables

The following figure lists the parameters that can refer to predefined variables.
Table 124: Gateway configuration parameter predefined variables
Variable
Description
$CLASS
class name
$CONTEXT
context name:
Permanentevent permanently in DB (until out of date)
Processeddiscarded by rule processing
Regulateddiscarded by regulation
Filtereddiscarded by filter
Refineddiscarded by refine
Receiveddiscarded immediately
$DATE
date stamp
$TIME
time stamp
$MODNMS
names of modified slots (empty for new)
$GHANDLE
event ID in gateway
$CNAME
cell name of cell connecting to gateway
Variable
Description
$CHANDLE
event ID in cell
$VALUE slot
value of slot slot
$NAME
selected slot name (only for body parameter)
$VALUE
selected slot value (only for body parameter)
$MODS
all modified slots (empty for new)
$ALL
all slots (only for slots parameter)
$ALL cls
all slots, but limited to class cls(only for slots parameter)
$MAP. map
mapped value of val using map
val
val can be a literal or a variable reference
Gateway text parameters

Text parameter values consist of literal text, possibly mixed with references to
variables and with escape sequences.
Table 125 on page 801 lists these parameters.
Table 125: Gateway Configuration Parameter Text Values
Character
Name
\\
backslash
\s
space
\n
new line
\r
carriage return
\t
tab
\0ddd
character code in octal (0, 1, 2, or 3 digits d)
References to variables that are not followed by punctuation or space characters

must be enclosed in curly brackets ( { } ). For example, $NAMEabc is invalid; $
{NAME}abc is correct. Non-printable characters and hard spaces must be expressed
with an escape sequence. String values for parameters are considered from the first
non-white space character up to the first (non-escaped) white space character.
Table 126 on page 802 lists the gateway.export file parameters.
Table 126: gateway.export file parameters

Parameter
Description
Communicatio
n parameters
protocol
sets the communication protocol. Both categories, new event and

modification, use the same protocol. The last one specified is used. The
default value is MCELL.
Contents
parameters
cond
sets the condition for a slot to be included in the $ALL variable. Use
always to always include the slot. Use propagate to include the slot if
its value is different from the default value for the slot and it is able to be
parsed. The default value is propagate for new, and always for mod.
drop
lists slots that must be dropped from the $ALL and $MODS variable. List
of comma separated slot names. Only real slot names can be used. The
default value is [], so no slot is dropped.
add
lists additional new slot definitions. List of comma separated settings in

the format slotname=slotvalue. slotname represents the name for the new
defined slot and slotvalue defines the value of the new slot. The default
value is [], so no slot is added.
slots
sets and orders the slot names to be included. Non-base class slots must
be prefixed with ClassName: . The list can also contain variable
references to include those values among regular slots.
The default value is [], so no slots are exported.
modify
lists slots whose modifications result in a message. Modifications of slots

that are not included in this list are ignored. The default value is [],
which means that every slot modification is included.
map.name
Defines the map table with the name name

List of comma separated settings in the format original_value =
converted_value
original_value represents a value that has to be replaced and
converted_value is the replacement value. Both values must be literal
values.
Format
parameters
Parameter
Description
init
text or value to be printed at the beginning of each export message. The

default value is blank. At least one of the init, body, or term
parameters must be specified to populate the export file.
body
text or value to be printed for every slot to be included; can use the
variable, $NAME (name of the slot) and $VALUE (value of the slot). The
default value is blank. At least one of the init, body, or term
parameters must be specified to populate the export file.
term
text or value to be printed at the end of each event. The default value is
blank. At least one of the init, body, or term parameters must be
specified to populate the export file.
separator
sets the separator character or string to use between slot values. The
default value is nothing.
quotable
sets the characters leading to quotation when appearing in a slot value. If

the parameter value is empty, slot values are never quoted. The default
value is standard MRL quotation rules.
openquote
sets the opening quotation character to use for values that must be
quoted. The default value is a single quote ().
closequote
sets the closing quotation character to use for values that must be quoted.
The default value is a single quote ().
escapequote
determines how to escape a quotation mark inside a quoted value. The

default value is a single quote ().
Gateway configuration value mapping

For some destinations, it is necessary to map values from a cell domain to a gateway
domain. You can implement value mapping by defining a map table and using the
value mapping function.
You define a value map table using the parameter map suffixed with the name of the
map table.
map. name =[ original_value = converted value,original_value = converted value, etc.]
name represents the name you give the map table; original_value is the value to be
replaced and converted_value is the replacement value.
You convert a value applying a map table, by using the variable $MAP.
$MAP. name ( value )
If the specified value cannot be found in the map table, it is not replaced.
For example: You want to modify the value of the enumeration SEVERITY when it is
sent to a certain gateway. Value WARNING will be replaced with LOW, and value
CRITICAL with URGENT.
To do this, create a map table to define the required mapping:
Example
map.GW1severity=[WARNING=LOW,CRITICAL=URGENT]
All other values of SEVERITY are passed unchanged.

To actually replace the values of slot severity, the slot has to be dropped and a new
slot, with the same name, has to be added, mapping the value:
Example
drop=[severity]
add=[severity=$MAP.GW1severity($VALUE(severity))]
Example of printed events

To print events in BAROC format, set the parameters as shown in Figure 150 on page
804.
Figure 150: Parameters used to print event in BAROC format
init=$CLASS;\n
body=\t$NAME=$VALUE;\n
term=END\n
The BAROC format produces output similar to the example shown in Figure 151 on
page 804.
Figure 151: Example of printed events
MC_CELL_TICK;
server_handle=0;
date_reception=1010183001;
event_handle=2;
source=;
sub_source=;
...
END
The slots are displayed, one per line, indented by a tab (\t). For every slot, the slot
name and value are printed, separated by an equals sign (=) and terminated with
semicolon and a new line (\n). To terminate, END is printed on a line at the end of the
data.
In the example shown in Figure 152 on page 805, the first two lines configure the
export file so that it exports new events and modified events differently. Specifically,
Exporting events
slots.new=[$ALL] exports all slots of new events to the database and

slots.mod=[event_handle,$NAME,$VALUE] exports event_handle, slot name,
and value of events that are modified to the export file.

Figure 152: Command to configure the export file
slots.new=[$ALL]
slots.mod=[event_handle, $NAME, $VALUE]
Exporting events
Events received in the cell can be exported to a flat file that resides on the same
computer as the cell. The exported events then can be used in third-party products
for archiving and data mining. Also, they can be exported to a program on another
computer by using the BMC Impact Solutions Gateway.
To export events, you configure the statbld.conf and gateway.export files.
Modifying a statbld.conf file to export events

To modify the statbld.conf file to generate an export file, set Export=Yes and
remove the # sign that precedes it. If you retain the default value
ExportDiscarded=No, events that were discarded in the first four rule phases
Refine, Filter, Regulate, and New/Updateare not included in the export file. Set
ExportDiscarded=Yes to include these events in the export file.
Use the E xportConfigFileName parameter in the statbld.conf file to set the location
of the export configuration file. By default, the location is the gateway.export file in
the cell-specific subdirectory of MCELL_HOME \etc.
When the data files are generated, the cell can trigger a program, which can be used
to import the data automatically into another product, such as a database. This can
be controlled using the ExportTriggerArguments and the E xportTriggerProgram
parameters, which are set also in the statbld.conf file. The arguments specified in
ExportTriggerArguments are passed as arguments to the program, if any. These
are always followed by the paths to the new event and modification export files, in
that order.
The export process produces two separate files that are located in the
MCELL_HOME \var\ cellName directory. These two files are
exp.TimeStamp.new, which contains all new events since the previous export, and
exp.TimeStamp.mod, which contains all modifications of events after they have first
passed through all rule phases. The TimeStamp part of the file name corresponds to
the timestamp part used in the mcdb and xact file names and enables archiving of
multiple export files.
Exporting events
Because the primary goal of exporting events is to import the data into another
format for other use, BMC Software recommends that you remove the export files as
soon as their contents have been archived. The easiest way to do this is to have them
removed by the program that is triggered at the end of the export.
Modifying a gateway.export file to export events

In a gateway.export file, you can configure what data goes into the export file and
how that data is formatted. A default gateway.export file exists in the
MCELL_HOME \etc directory. Copy the gateway.export file to the MCELL_HOME
\etc\ cellName directory and edit the copy.
By default, the gateway.export file has the format shown in the following figure.
Figure 153: gateway.export file format
# Export Gateway Configuration
#
cond=always
slots.new=[$ALL]
slots.mod=[$MODS]
body=$VALUE
term=\n
separator=,
quotable=,"
openquote="
closequote="
escapequote="
Using the default values in the gateway.export file for new events produces output
in the format shown in Figure 154 on page 806.
Figure 154: gateway.explore file output for new events
0,1010183001,1,,,,,,,,OPEN,,[admin],1,OK,,,0,0,0,0,
mc.exp.000000001,0,['exp:1'],[],[],[],[],[],0,[],exp,
10.0.9.10:1981,28698
0,1010183001,2,,,,,,,,OPEN,,[admin],1,OK,,,0,0,0,0,
mc.exp.000000002,0,['exp:2'],[],[],[],[],[],0,[],exp,
10.0.9.10:1981,600
Using the default values in the gateway.export file for modified events produces
output in the format shown in Figure 155 on page 806.
Figure 155: gateway.explore file output for modified events
mc.exp.000000001
exp
10.0.9.10:1981
28698
mc.exp.000000002
exp
10.0.9.10:1981
600
ACK
1010183062
mc.exp.000000003
exp
10.0.9.10:1981
28698

You configure StateBuilder tracing in the MCELL_HOME \etc\statbld.trace file. The
statbld.trace file uses the same parameters as the mcell.trace configuration file. For
details on the cell tracing configuration, see the BMC Impact Solutions: Event
Monitoring Operators Guide .

If the StateBuilder process (MCELL_HOME /bin/statbld) fails to start, try the
following solutions:
Check the MCELL_HOME/var/cellName directory for the number of xact. n files,
where n is 1, 2, 3. More than three xact.n files is an indication that the StateBuilder
process is failing. If more than three xact.n files are present, follow these steps:
1 Check the MCELL_HOME/var/cellName directory to see if either of the
following files are present:
mcdb.0
mcdb.lock
If either of these files are present, delete them.

1 From a command line, manually run the StateBuilder process by entering:
statbld -n cell_name
Check the MCELL_HOME/var/cellName directory to ensure that your xact. n
files are named xact.1, xact.2, and so forth. If the file does not have the numeric
extension (.n) (the file is only named xact), then rename the file to xact.1.
Determine whether or not the MCELL_HOME/bin/statbld program exists and

can be executed by the current user who is running the mcell process.
Verify your systems available memory and compare it with the actual memory
usage of the mcell process.
On some UNIX platforms, available unused virtual memory must equal or

exceed the virtual memory used by the mcell process.
20
Setting up data views for external
reports
BMC ProactiveNet provides the ability to create customized reports to suit your
specific needs by exporting data from the BMC ProactiveNet database. To prevent
the mundane task of keeping up with ongoing schema changes and prevent possible
database entry corruption, you can leverage the Database Views feature (also called
dataviews) provided by the relational database system.
External reports benefits

Significantly reduces development time to providing data to external tools.
No special domain knowledge about data storage is required.
The read-only user option helps to prevent data corruption.
Performance considerations
Before using the dataviews feature to access data directly from the BMC
ProactiveNet database, you need to consider the performance impact on the BMC
Several factors can affect the server performance, including the following:
Hardware resources (CPU, memory & disk i/o)
Number and type of monitored instances
Poll frequencies
Chapter 20 Setting up data views for external reports 809
Creating dataviews
Number of graphs in the hourly, daily, weekly views, number of daily, weekly,
monthly reports
Number of users accessing this information

Increases to the processing load on the database server/BMC ProactiveNet Server
Note
Due to performance impact on the BMC ProactiveNet Server, dataviews should
not be used as real-time data feed. This feature is meant for the external reporting.
High volume of data in the database
When updates to monitor configuration data are scheduled. By default, this data
is updated as part of daily job that runs at 3.30. This information is not available
until the update script is run either as part of a daily job or run manually using the
pw dataview update command.
Use of custom monitors such as Monitor Wizard monitors, MetaAPI monitors, or
SDK monitors; these monitors require that you regenerate the dataviews schema
so that they appear in the dataviews.
Also, though dataviews in general provide information in a usable format, you will
have to interpret some of the raw values into corresponding usable values. For
example, No data, No response values that are stored as high negative numbers
need to be mapped to their respective meanings.
Creating dataviews
Dataview schema and views described in Dataview Tables are created during
product installation.
You can create the schema manually by using the pw dataview create command line
option. For details about this command line option, see the BMC ProactiveNet
Command Line Interface Reference Manual.
Because custom monitor schemas are created at run-time, you need to use the
command line option to reflect this schema in the dataviews. This step is also
necessary if you make any updates to the custom monitor definition. Using the
command line option, you can generate the Data Dictionary that explains each of the
dataviews tables and columns. The configuration information table values described
in the Data Dictionary match the configuration information described in the Monitor
guide with each of the Monitors. Similarly stats data column description in the Data
dictionary matches with the description of the performance data collected for each of
the monitors.
The best way to find out which column represents the data of interest is to cross
reference attribute names from the Monitor guide to the description in the Data
Dictionary.
Configuration information in the INSTANCEINFO_CFG table is populated as part of
the daily job. You can use the command line utility to update this info as desired.
The rest of the information is populated during normal operation of BMC
ProactiveNet Server. Views expose this information from the corresponding data
storage tables.

The following section describes the different types of dataviews and how they are
created and organized:
Configuration Information
Rate (Rolled up, Condensed) Information
Baseline Information
Event Information
Default dataviews
The following sections describe the default data views that are available in BMC
ProactiveNet.
Thresholds (Absolute, SLO, and Signature)

This view has the thresholds information of type 'Absolute Default Thresholds ( 156 )'.
Table 127: Global absolute thresholds - ABSDFLTTHRESHOLDS_VIEW

Columns
Description
ABSDFLTABOVE
Above means current value should be greater than the thresholdfalse

belowtrue above
ABSDFLTAUTOCLOSE
Tells whether to automatically close the event or not.false Notrue - yes
ABSDFLTDURATION
How long the current values should exceed the threshold value before
generating an event. 0 means event is generated immediately as one data point
crosses the threshold value.
ABSDFLTSEVERITY
Severity of the event: Critical, Major, Minor, Event Only
THRESHOLDID
Internal threshold ID
MOTYPE
Monitor type ID
MOATTRID
Attribute ID
MONAME
Monitor type name
MOATTRNAME
Monitor Attribute Name
ABSDFLTTHRESHOLD
Threshold value
ABSDFLTBLTYPE
Can work in conjunction with threshold value. If non-zero, raw data points will
also needs to pass the hourly, daily or weekly baseline before the event can be
triggered. Same thing applies for closing of events
This view has the thresholds information of type 'Absolute Instance Thresholds (161)'.
Table 128: Instance absolute thresholds - INSTABSTHRESHOLDS_VIEW
Columns
Description
ABSINSTANCEABOVE

belowtrue above
ABSINSTANCEAUTOCLOSE Tells whether to automatically close the event or not.false Notrue - yes
ABSINSTANCEDURATION
generating an event. 0 means event is generated immediately as one data
point crosses the threshold value.
ABSINSTANCESEVERITY
THRESHOLDID
MOTYPE
Monitor type ID
MOATTRID
Attribute ID
MONAME
Monitor type name
MOATTRNAME
MOINST
Monitor instance ID
Columns
Description
DEVICENAME
Device name
INSTNAME
Monitor instance name
ABSINSTANCETHRESHOLD Threshold value

ABSINSTANCEBLTYPE
Can work in conjunction with threshold value. If non-zero, raw data points
will also needs to pass the hourly, daily or weekly baseline before the event
can be triggered. Same thing applies for closing of events
This view has the thresholds information of type 'Signature Default Thresholds (157)'.
Table 129: Global signature thresholds - SIGNDFLTTHRESHOLDS_VIEW
View Name
Description
THRESHOLDID
MOTYPE
Monitor type ID
MONAME
Monitor type name
MOATTRID
Attribute ID of threshold
MOTTRNAME
Monitor attribute name
SIGNDFLTTHRESHOLD
Threshold value
SIGNDFLTSEVERITY
Severity of the event. Critical, Major, Minor, Event Only
SIGNDFLTDURATION
SIGDFLTSUPPRESSEVNTS
Whether to deactivate the signature threshold
SIGNABSPADFACTOR
Specify a margin around the baseline values to make it more difficult for
signature events to occur.
SIGNPERPADFACTOR
Same as absolute pad factor, but instead of using a number, a percentage of

the baseline will be used.
SIGNDFLTBLTYPE
Allow threshold to be compared of daily and weekly baseline, in addition to

hourly baseline.
SIGNDFLTABOVE

belowtrue above
SIGNDFLTAUTOCLOSE
This view has the thresholds information of type 'Signature Instance Thresholds (162)'.
Table 130: Global Signature Thresholds - INSTSIGNTHRESHOLDS_VIEW

View Name
Description
THRESHOLDID
MOTYPE
Monitor type ID
MONAME
Monitor type name
MOATTRID
Attribute ID of threshold
MOTTRNAME
Monitor attribute name
SIGNDFLTTHRESHOLD
Threshold value
SIGNINSTSEVERITY
Severity of the event. Critical, Major, Minor, Event Only
SIGNINSTANCEDURATION How long the current values should exceed the threshold value before
SIGDFLTSUPPRESSEVNTS
Whether to deactivate the signature threshold
SIGNABSPADFACTOR
Specify a margin around the baseline values to make it more difficult for
signature events to occur.
SIGNPERPADFACTOR
Same as absolute pad factor, but instead of using a number, a percentage of

the baseline will be used.
SIGNINSTBLTYPE
Allow threshold to be compared of daily and weekly baseline, in addition to

hourly baseline.
SIGNINSTABOVE

belowtrue above
SIGNINSTAUTOCLOSE
MOINST
Monitor instance ID
DEVICENAME
Device name
INSTNAME
Table 131: SLO Thresholds - SLOTHRESHOLDS_VIEW

View Name
Description
ABSINSTABOVE

belowtrue above
ABSINSTAUTOCLOSE
ABSINSTDURATION
generating an event. 0 means event is generated immediately as one data point
crosses the threshold value.
ABSINSTSEVERITY
THRESHOLDID
View Name
Description
MOTYPE
Monitor type ID
MOATTRID
Attribute ID
MONAME
Monitor type name
MOATTRNAME
MOINST
Monitor instance ID
DEVICENAME
Device name
INSTNAME
ABSINSTTHRESHOLD
Threshold value
ABSINSTBLTYPE
Can work in conjunction with threshold value. If non-zero, raw data points will
also needs to pass the hourly, daily or weekly baseline before the event can be
triggered. Same thing applies for closing of events
SLO configuration Info

This view has the information about the attributes sets used in the system in reports
and SLO.
Table 132: View Name - ATTRIBUTESET_VIEW
Columns
Description
MOINSTID
Attribute set ID
ATTRIBUTELIST
List of attributes
This view has the information about the schedules.

Table 133: View Name - SCHEDULE_VIEW
Columns
Description
MOINSTID
Internal schedule ID
NAME
Name of the schedule
TIMERANGE
Time
This view has all SLO information.

Table 134: View Name - SLO_INFO_VIEW
Columns
Description
SLOID
SLO ID
Columns
Description
NAME
Name of the SLO
CONTENTID
Content type SLO/instance. Refer to CONTENTID in

SLO_CONTENT_VIEW.
SLOTYPEID
Refer moinstid in attributeset_view
SLO_SCHEDULE
Refer moinstid in schedule_view
COMPLIANCE_OBJECTIVE
OWNER
CONTACT_INFO
CREATE_DATE
COMMENTS
UPDATE_DATE

Table 135: View Name - SLO_INSTANCES_INFO_VIEW
Columns
Description
INSTID
SLO Instance ID
SLOID
SLO ID
MOTYPEID
Monitor type ID
MOINSTID
Monitor instance ID

Table 136: View Name - SLO_THRESHOLD_INFO_VIEW
Columns
Description
INSTID
Refer instid in slo_instances_info_view
SERVICE_LEVEL_THRESHOLD_ID
Refer thresholdid in slo_threshold_view
WEIGHT
COMMENTS
This view has SLO containment information.
Table 137: View Name- SLO_CHILD_INFO_VIEW

Columns
Description
SLOID
Parent SLO IDRefer sloid in slo_info_view
CHILD_SLOID
Child SLO IdRefer sloid in slo_info_view
WEIGHT
SLO summary data

This view has SLO summary information.
Table 138: View Name - SLO_SUMMARY_VIEW
Columns
Description
SLOID
SLO ID
PREVIOUS_DAY
Compliance value for previous day
PREVIOUS_WEEK
Compliance value for previous week
WEEK_TO_DATE
Compliance value for week to date
PREVIOUS_MONTH
Compliance value for previous month
MONTH_TO_DATE
Compliance value for month to date
QUARTER_TO_DATE
Compliance value for quarter to date
YEAR_TO_DATE
Compliance value for year to date
PREVIOUS_DAY_TREND
Compliance value for previous day trend
WEEK_TO_DATE_TREND
Compliance value for week to date trend
This view has SLO summary by day.

Table 139: View Name - SLO_SUMMARY_DAY_VIEW
Columns
Description
SLOID
SLO ID
DATE_TIME
COMPLIANCE_VALUE
This view has SLO summary by week.
Table 140: View Name - SLO_SUMMARY_WEEK_VIEW

Columns
Description
SLOID
SLO ID
DATE_TIME
COMPLIANCE_VALUE
This view has SLO summary by month

Table 141: View Name - SLO_SUMMARY_MONTH_VIEW
Columns
Description
SLOID
SLO ID
DATE_TIME
COMPLIANCE_VALUE
This view has SLO summary by quarter

Table 142: View Name - SLO_SUMMARY_QUARTER_VIEW
Columns
Description
SLOID
SLO ID
DATE_TIME
COMPLIANCE_VALUE
This view has SLO summary by year.

Table 143: View Name - SLO_SUMMARY_YEAR_VIEW
Columns
Description
SLOID
SLO ID
DATE_TIME
COMPLIANCE_VALUE
This view has the data for each SLO instance by day.
Table 144: View Name - SLO_INSTANCES_DAY_VIEW

Columns
Description
INSTID
MOTYPEID
Monitor type ID
MOINSTID
Monitor instance ID
ATTRIBUTEID
Attribute ID
DATE_TIME
TOTAL_VALID_DATA_POINTS
TOTAL_VIOLATED_DATA_POINTS
TOTAL_UNKNOWN_DATA_POINTS
COMPLIANCE_VALUE
MINVALUE
MAXVALUE
MEDIAN
AVERAGE
WEIGHT
This view has the data for each instance by week.

Table 145: View Name - SLO_INSTANCES_WEEK_VIEW
Columns
Description
INSTID
MOTYPEID
Monitor type ID
MOINSTID
Monitor instance ID
ATTRIBUTEID
Attribute ID
DATE_TIME
COMPLIANCE_VALUE
MINVALUE
Columns
Description
MAXVALUE
MEDIAN
AVERAGE
WEIGHT
This view has the data for each instance by month.

Table 146: View Name - SLO_INSTANCES_MONTH_VIEW
Columns
Description
INSTID
MOTYPEID
Monitor type ID
MOINSTID
Monitor instance ID
ATTRIBUTEID
Attribute ID
DATE_TIME
COMPLIANCE_VALUE
MINVALUE
MAXVALUE
MEDIAN
AVERAGE
WEIGHT
This view has the data for each instance by quarter.

Table 147: View Name - SLO_INSTANCES_QUARTER_VIEW
Columns
Description
INSTID
MOTYPEID
Monitor type ID
MOINSTID
Monitor instance ID
Columns
Description
ATTRIBUTEID
Attribute ID
DATE_TIME
COMPLIANCE_VALUE
MINVALUE
MAXVALUE
MEDIAN
AVERAGE
WEIGHT
This view has the data for each SLO instance by year.
Table 148: View Name - SLO_INSTANCES_YEAR_VIEW
Columns
Description
INSTID
MOTYPEID
Monitor type ID
MOINSTID
Monitor instance ID
ATTRIBUTEID
Attribute ID
DATE_TIME
COMPLIANCE_VALUE
MINVALUE
MAXVALUE
MEDIAN
AVERAGE
WEIGHT
SLO Violation Records

This view has all the SLO violations.
Table 149: View Name
Columns
Description
THRESHTIME
ENDTIME
KEEPALIVETIME
VIOLATIONID
MOTYPEID
MOINSTANCEID
ATTRID
HOSTID
SLTTYPE
SLTID
SEVERITY
LASTVALUE
EXCEEDPOINTCNT
DESCRIPTION
Groups
This view has all the user groups.
Table 150: View Name - GROUP_INFO_VIEW
Columns
Description
GROUPID
Group ID
GROUPNAME
Name of the group
DESCRIPTION
This view has groups containing other groups.
Table 151: View Name - GROUP_TREE_VIEW

Columns
Description
PARENTGROUPID
Parent Group ID
CHILDGROUPID
Child Group ID
This view has monitors that belong to a specific group.

Table 152: View Name - GROUP_MONITOR_VIEW
Columns
Description
GROUPID
Group ID
MOTYPEID
Monitor type ID
MOINSTID
Monitor instance ID
Using group views

Suppose there are three groups Sample_1, Sample_2, Sample_3. This information can
be retrieved from GROUP_INFO_VIEW.
Table 153: GROUP_INFO_VIEW
Group ID
Group Name
Description
Sample_1
Sample group 1
Sample_2
Sample group 2
Sample_3
Sample group 3
Sample_1 and Sample_2 groups are made of monitor instances. This information can
be retrieved from GROUP_MONITOR_VIEW.
Table 154: GROUP_MONITOR_VIEW
Group ID
MO Type ID
MO Instance ID
20031
20031
10
20035
15
This shows that Sample_1 group contains one instance with ID 1 of monitor type
web URL (20031). Sample_2 group contains one instance with ID 10 of monitor type
web URL (20031) and one instance with ID 15 of type web transaction (20035).
Lets assume that Sample_3 group is made of other two groups. This group
containment information can be retrieved from GROUP_TREE_VIEW.
Table 155: GROUP_TREE_VIEW
Parent Group ID
Child Group ID
For details of all default dataviews in BMC ProactiveNet, use the pw dataview
gendoc command.
BMC ProactiveNet collects performance data from several heterogeneous systems
such as Network, Application, Database, and user-defined or custom systems.
Defining these heterogeneous systems requires capturing system-specific
configuration information. This configuration information resides in various tables
and is used during data collection.
To simplify access to configuration information, a single table
(INSTANCEINFO_CFG) is defined that stores information of all monitor type
instances which include application, SNMP, and monitors created by users through
the Monitor Wizard, and meta API.
Table 156 on page 824 shows the base table for all configuration dataviews for each
monitor type that exists on BMC ProactiveNet Server.
Table 156: Configuration information
Column
Description
MOTYPEID
Monitor type ID (example, Weblogic, Websphere, etc.) This value is internal and fixed.
MOINSTID
Monitor instance ID. This is a unique number generated for each instance. The value is
assigned by BMC ProactiveNet system during monitor creation. This value is internal
and fixed. This number identifies all other data for each instance.
DEVICENAME
Name of the device entered by the user when this instance is created using the
Operations Console or via command line.
INSTANAME
Description of the monitor instance.
SOURCEIP
IP address of the device from where the performance data is being collected.
TARGETIP
IP address of the device on which this instance is running.
Column
Description
CONFIGVALUES
All configuration type of attributes of this monitor type that can be displayed. This is
organized in the name=value pairs format separated by ';'. Parse this value to retrieve
the associated value for each attribute.
The schema for this table is created at the time of product installation. Therefore, if
custom monitors such as MetaAPI, SDK, and Monitor Wizards are created at runtime, you need to regenerate the schema to include these monitors. Since this is a
database table and not a view generated from an existing table, values in this table
are populated as part of daily jobs. The default run-time for daily jobs is 3.30 A.M.
Configuration dataviews named as <tablename prefix>_CFG_VIEW are created for
each monitor type using the values in this table.
Each of these Config dataviews contains the following information:
Table 157: Configuration information
Column
Description
MOTYPEID
Monitor type ID (example, Weblogic, Websphere, etc.) This value is

internal and fixed.
MOINSTID
Monitor instance ID. This is a unique number generated for each

instance. The value is assigned by BMC ProactiveNet system during
monitor creation. This value is internal and fixed. This number identifies
all other data for each instance.
DEVICENAME
Name of the device entered by the user when this instance is created
using the Administration Console or via command line.
INSTANAME
Description of the monitor instance.
SOURCEIP
IP address of the device from where performance data is being collected.
TARGETIP
IP address of the device on which this instance is running.
CONFIGATTRIBUTE NAMES
All configuration attributes with their values that can be displayed for
this monitor type.

Performance data, also called raw data or stats data, is the attribute performance
values collected during every poll of a monitor instance. Creating views for stats
data of most monitor types is relatively easy, as data is organized in individual
(horizontal) tables, which allow one to one mapping of stats table to a view for each
monitor type available in the BMC ProactiveNet system.
MetaAPI application monitors stats data is the exception to this rule and is
organized in a single (vertical) table by attribute of each monitor. To address this
issue, a view for each Stats attribute is created and a view joining these views is
created to give the effect of a horizontal table. The final view is the same as views
created for other monitors. As a result, accessing MetaAPI monitor views is
performance intensive.
Accessing stats data from a view is advantageous as values stored in the tables are
multiplied by a scale factor that is different for each attribute and monitor type.
Configuration data 'Configuration dataviews (<tablename prefix>_CFG_VIEW)' and
Stats dataviews can be joined on the MOINSTID column to get all information
related to an instance.
Stats dataviews are named as <tablename prefix>_ST_VIEW. Each of these Stats
dataviews contains the following information:
Table 158: Performance information
Column
Description
MOINSTID
Monitor instance ID. This is a unique number generated for each instance. The
value is assigned by BMC ProactiveNet system during monitor creation. This
value is internal and fixed. This number identifies all other data for each instance.
TIMERECORDED
UNIX time stamp when the data point was collected
Stats Attribute Name
Displays all Stats attributes with their values of these monitor types that are
properly converted with appropriate conversion factors. The following values
should be interpreted as described below:'No Response' = -2147483647'No Data' =
-2147483646

Raw performance data is statistically computed and rolled into hourly data called
Rate data. This enables you to retain data for an extended period of time (90 days)
without increasing disk storage or having a negative impact on database performance.
Creating views for Rate data is relatively easy for most monitor types as data is
organized in individual (horizontal) tables. This enables a one to one mapping of a
Rate table to a view for each monitor type that is available in the BMC ProactiveNet
system. Rate dataviews are named as <tablename prefix>_RT_VIEW. Each of these
Rate dataviews contains the following information:
Table 159: Rate Information
Column
Description
MOINSTID
value is assigned by the BMC ProactiveNet system during monitor creation.
This value is internal and fixed. This number identifies all other data for each
instance.
Column
Description
FROMTIME
UNIX time stamp for the start of the duration
TOTIME
UNIX time stamp for the end of the duration
Stats Attribute
Name_AVGStats Attribute
Name_HIGHStats Attribute
Name_LOW
This contains Rate values for the above FROMTIME to TOTIME duration.
Each attribute of this monitor type has three Rate values. Refer Administration
guide for further details on how Rate values are computed.
Baseline data provides attribute values during each hours of the day of the week.
Creating views for Baseline data is relatively easy for most monitor types as data is
organized in individual (horizontal) tables. This enables one to one mapping of a
Baseline table to a view for each monitor type that is available in BMC ProactiveNet
system. Baseline dataviews are named as <tablename prefix>_BL_VIEW.
Each of these baseline dataviews contains the following information:
Table 160: Baseline information
Column
Description
MOINSTID
value is assigned by BMC ProactiveNet system during monitor creation. This
value is internal and fixed. This number identifies all other data for each
instance.
TIMESLOT
This indicates the hour of the day of the week. BL_TIMESLOT_DESCR_VIEW

has textual description of each time slot. This view has two columns:
TIMESLOT and DESCRIPTION.
Stats Attribute
Name_AVGStats Attribute
Name_HIGHStats Attribute
Name_LOW
This contains Baseline values for the above TIMESLOT. Each attribute of this
monitor type has three Baseline values. Refer Administration guide for details
on how Baseline values are computed.
Event information
There is one event view for each monitor type. The view provides information about
events generated for all monitor instances of a monitor type. Event dataviews are
named as <tablename prefix>_AL_VIEW.
Each of these event dataviews contains the following information:
Table 161: Event information

Column
Description
MOINSTID
Monitor instance ID. This is a unique number generated for each instance. The value is
assigned by BMC ProactiveNet system during monitor creation. This value is internal
and fixed. This number identifies all relevant data for each instance.
EVENTID
Internal ID for this event
SEVERITY
This is an integer defined as follows:

4 = CRITICAL
3 = MAJOR
2 = MINOR
1 = ABNORMAL
0 = CLOSED
DESCRIPTION
Reason for the event
ASSIGNEDTO
Assigned person's name
THRESHTYPE
This is an integer defined as follows:156 > Crossed absolute threshold. Applicable to

all instances of specified monitor type157 > Crossed Signature threshold. Applicable to
all instances of specified monitor type158 > External events that are imported using
'pw userevent' > Crossed absolute threshold. Applicable to a specific monitor
instance162 > Crossed signature threshold. Applicable to a specific monitor instance
TIMERECORDED
UNIX time stamp. Time when this attribute value crossed the threshold the first time
CLOSED_TIME
UNIX time when the event was closed
ENDTIME
Time when the state of the event record changes. Time recorded here is typically the
time of the next event record that has the same event ID, or time when the event was
closed. The ENDTIME column is used in cases where the event changes severity while
it is still open. In that case, ENDTIME for the older records contains the start time of
the next record - each severity change creates a new event record.
EVENT_ID
Internal ID of the associated event. Every alarm is associated with an event
ATTRID
Internal ID of the attribute for which this event is created
LASTTIME
UNIX time when the event was created

These views contain all of the columns that are described with alarm and event
views information. The additional column MOTYPEID indicates the type of monitor
instance. There are also two global views, ALARM_LOG_VIEW and
Command line option
EVENT_LOG_VIEW, which provide information on all alarms and events that are
generated on BMC ProactiveNet Server.
Command line option

Command line options are provided to generate dataviews Data Dictionary, create
and delete views, and populate instance configuration data.
See the CLI description of pw dataview for details on using the command line.

This is a sample Data Dictionary generated by running 'pw dataview gendoc'
command.
Figure 156: Sample Data Dictionary
Table INSTANCEINFO_CFG
Desc : Information related to all the instances in the system is stored
here.
Columns :
MOTYPEID : Monitor type id. This value is internal and fixed.
MOINSTID : Monitor instance id. This is an unique # generated for each
instance. This value is internal and fixed. All statistics data for each
instance is identified by this.
DEVICENAME : Name of the device to which this instance is added in the
administration console.
INSTANAME : Description of the monitor instance.
SOURCEIP : IP Address of the device from where the statistics data is being
collected.
TARGETIP : IP Address of the device on which this instance is running.
CONFIGVALUES : Values of the configuration attributes of the monitor
instance in the format name=value pairs separated by ';'.
Host name : narmada
Creating views
View BMC_CFG_VIEW
Desc : This view has the config information for monitors of type 'Adapter
for BMC Patrol ( 29753 ) '
Columns :
MOINSTID : same as described in instanceinfo_cfg.
DEVICENAME : same as described in instanceinfo_cfg.
INSTNAME : same as described in instanceinfo_cfg.
SOURCEIP : same as described in instanceinfo_cfg.
TARGETIP : same as described in instanceinfo_cfg.
APP_INST : Application Instance Name
APP_PARAM : Application Parameter Name
APP_TYPE : Application Type Name
COMPUTATION : Measure As
PASSWORD : Password
PORT_NO : Port Number
SCALE_FACTOR : Scaling Factor
USER_NAME : User Name
View BMC_ST_VIEW
Desc : This view has the stats information for monitors of type 'Adapter for
BMC Patrol ( 29753 ) '

TIMERECORDED : unix time stamp of when this data is collected
VAL : Application Parameter Value ( # )
View AGENTCONN_CFG_VIEW
Desc : This view has the config information for monitors of type 'Agent
Connection (27011) '
Columns :
PW_MON_VER : Monitor Version
View AGENTCONN_ST_VIEW
Desc : This view has the stats information for monitors of type 'Agent
Connection ( 27011 ) '
STATUSCHGS : Agent Status Changes ( # )
CONN : Agents Connected ( # )
DISCONN : Agents Disconnected ( # )
NOTCONN : Agents Not Connected ( # )
TOTALAGENTS : Total Agents ( # )
View AGENTSTATUS_CFG_VIEW
Desc : This view has the config information for monitors of type 'Agent
Status ( 28601 ) '
Columns :
AGENT_IP : Agent IP
View AGENTSTATUS_ST_VIEW
Desc : This view has the stats information for monitors of type 'Agent
Status ( 28601 ) '
AVAILABILITY : Availability ( % )
View AIXCPU_CFG_VIEW
Desc : This view has the config information for monitors of type 'AIX CPU
( 43001 ) '
Columns :
PROCESSOR_NAME : Processor Name
View AIXCPU_ST_VIEW
Desc : This view has the stats information for monitors of type 'AIX CPU
( 43001 ) '
SYSTIME : % System Time ( % )
USRTIME : % User Time ( % )
WAITTIME : % Wait Time ( % )
IDLETIME : %Idle Time ( % )
CNXTSWTCH : Context Switches ( per sec )
SYSCALLS : System Calls ( per sec )

This section provides details about how to create an ASA database interface.
Install Sybase ASA driver on the Windows computer

BMC ProactiveNet provides an application on Windows that installs the ASA ODBC
drivers and creates a DSN. The following sections provide instructions on how to
install the package.
Prerequisite for ASA ODBC driver installation

Microsoft Driver Manager for Windows should be available. To check if this is
available, navigate to:
Start => Settings => Control Panel => Administrative tools => Data sources
(ODBC)
Installing the ASA ODBC driver

Perform the following procedure to install the ASA ODBC driver.
To install the ASA ODBC driver

1 Locate ASA_Client.exe in the Utilities folder on the BMC ProactiveNet DVD.
2 Double-click ASA_Client.exe.
The installation package opens to install the product. The Install Wizard
Welcome window is displayed and then the License window is displayed.
3 Click Next.
4 Follow the prompts. The installation directory will be displayed. Change the
location if you want to. After selecting the installation directory click Next.
Summary of the installation is displayed in the next window.
5 Once the installation is complete, click Finish to close the install window.
This completes the ASA ODBC driver installation.
6 Check the ODBC Administrator manager for a DSN 'ASA Client' by following
these steps:
a Select Start => Settings => Control Panel => Administrative Tools => Data
Sources (ODBC) => System DSN.
b Select ASA Client and click Configure.
The ODBC Configuration for Adaptive Server Anywhere window displays.
7 ODBC tab: ASA Client is populated by default. Modify the DSN to connect to the
ASA database of your choice, if necessary.
8 Login tab: The log in panel is configured to user name 'report' and password
'report'. You can change the user name and password if it is different.
9 Database tab: In the Server Name field, specify the server name.
Confirm the database name before filling in the field. You can confirm this by
going to BMC ProactiveNet Server under the directory: usr/pw/sybase/

storm_<hostname>.db
Example: server name is storm_krishna, where krishna is the host on which

ASA database is running.
For the By default, the database name will be storm_<hostname>. If the database
name has been modified, you can find it by the .db extension on BMC
10 Network tab: Select the TCP/IP option and fill in the host details in the Network
panel.
Enter the value: host=<hostname or IP address>:2638
Example: host=krishna:2638.
Host specifies the host on which ASA database is running and 2638 is the port
on which the database is listening for client connections.
11 Access the ODBC tab and test the connection by following these steps:
a Click Test Connection. A message window displays that the connection is
successful.
b Click OK in the message window.
12 Click OK in the ODBC window.
This completes the process of configuring the DSN that is created by
ASA_Client.exe.

This section describes how to download and install Crystal Reports and the
prerequisites for BMC ProactiveNet.
Before you begin

You need a user name and password for the BMC Software Electronic Product
Download site. You can register and obtain credentials at http://www.bmc.com/

support_home .
You must obtain a support ID and password for BMC ProactiveNet from your
BMC Software sales representative.
To download Crystal Reports and the integration components

1 Take the appropriate step:
If you are already logged on to the BMC Software Support Home, click
Downloads & Patches, and then click Product Downloads (EPD).
If you are not logged on, go to at http://webapps.bmc.com/epd and log on.
2 Follow the instructions for completing the Export Validation & License Terms
page. You must select I agree in the Export Compliance Disclaimer and TRIAL
AGREEMENT panes.
3 Click CONTINUE.
4 If you have previously entered the support for BMC ProactiveNet, go to step List
item. on page 833.
To enter the support ID and password:
a In the My Entitled Products page, click MANAGE SUPPORT IDS.

b In the Manage My Support IDs page, enter the support ID and password, and
then click ADD.
c Click BACK TO MY ENTITLED PRODUCTS.
5 If BMC ProactiveNet version 2.0.00 is not displayed, perform the following
actions:
a Click ADDITIONAL PRODUCTS.
b In the Search field, enter BMC Service Assurance Reporting, and then click
SEARCH.
Tip
Case does not matter in this search.
You can enter a substring of the product name, such as assurance rep.
6 Select BMC Service Assurance Reporting 2.0.00, and then click CONTINUE.
7 In the Select Product Version page, select BMC Service Assurance
Reporting 2.0.00, and then click CONTINUE
8 In the Download files page, choose the appropriate component for your situation:
If this is a first-time installation
Crystal Reports Server SP2 (Full Install)
If you have Crystal Reports Server XI release 2

without SP2
Crystal Reports Server SP2 (Incremental Patch-SP1

Customers Only)
If you want to design custom reports, and this is a first- Crystal Reports Designer SP2 (Full Install)
time installation
If you have Crystal Reports Designer XI release 2
without SP2
Crystal Reports Designer SP2 (Incremental PatchSP1 Customers Only)
To download temporary license passwords
License Information for BMC Service Assurance

Reporting
9 For each item that you choose, follow the instructions to complete the download.

For information about installing Crystal Reports, see the Crystal Reports Server
Installation Guide, currently available from http://help.sap.com/businessobject/
product_guides/ .
General information about the product is available from http://
businessobjects.com/ .
The following prerequisites must be met for running Crystal Reports:
Crystal Reports should be installed on the Windows computer where you would
run the report.
On BMC ProactiveNet Server, one or more Web URL monitor instances should
have been created.
The Web URL monitors should have collected data for at least 24 hours.
On the server side, the following command should be running after creation of
instances: (If its already done, ignore.)

#runjava scripts.InstanceInfo update
Sybase ASA client drivers should be installed on the Windows computer from
where Crystal reports will be run.
A DSN should be created for the ASA database of BMC ProactiveNet.

On BMC ProactiveNet Server computer, the ASA database process dbsrv7 should
be running.
Connect to ASA database through Crystal Reports

1 Start Crystal reports.
2 Select File => New.
3 Select a report type from the available report types.
4 From the Step 1: Tables tab, click SQL/ODBC icon.
The Log on Server window, which lists all ODBC driver sources available on the
system, displays.
5 Select the DSN that was created in the previous section (ASA Client).
This opens the Choose SQL Table window, which lists all tables and views of the
connected database.
Accessing the ASA database through

Microsoft Excel
This section provides details about how to create sample reports by accessing the
ASA database through Microsoft Excel.
Creating sample reports using Microsoft Excel

Perform the following procedure to create sample reports with Microsoft Excel.
Prerequisites
Microsoft Query should be installed on the Windows computer.
Sybase ASA client driver packages should be installed on the Windows computer.
On the BMC ProactiveNet Server computer, the ASA database process (dbsrv7)
should be running.
BMC ProactiveNet Server processes should have been running for at least a day
and data collection should have been occurring for 24 hours.
To create sample reports in Microsoft Excel

1 Open Microsoft Excel.
2 Select Data => Pivot Table and Pivot Chart Report from the main menu. The
Pivot Table and Pivot Chart Wizard pop-up window displays.
3 In step 1, select External Data source and Pivot Chart. Click Next.
4 In step 2, click Get Data. The Choose Data source pop-up window displays.
5 Select the data source that connects to the ASA database. Refer to the earlier
section that specifies the procedure to create DSN. Select the data source name
and click OK. Example: ASA Client.
A new pop-up window Query Wizard - Choose columns displays.
6 Choose the tables/columns you want to use in the report. For the sample report,
choose moinstid, devicename, instname columns from SOLPROC_CFG_VIEW
view and TOTALCPU column from SOLPROC_ST_VIEW view.
7 Click Next.
A warning message displays, asking to start-up Microsoft query to join the two
tables that are selected.
8 Click OK.
Microsoft Query opens and shows the column names of the two views that are
considered for the report.
9 Join the moinstid column of SOLPROC_CFG_VIEW with MOINSTID column of

SOLPROC_ST_VIEW. A warning may appear indicating that the columns are of
different types. Click OK.
10 In Microsoft Query, add criteria to TOTALCPU column.
Use Criteria"Add Criteria of main menu tool bar. The constraint is to choose the
rows that have values of TOTALCPU greater than -1. Usually, the value will be
less than 0 in the very first record on creation of monitor instance. Click Add.
11 In Microsoft Query, select moinstid column.

Keeping the moinstid column highlighted, click View "Query Properties
from main menu tool bar. Query Properties window pops up. Select Group
Records field and click OK.
12 In Microsoft Query, keeping the moinstid column highlighted, click Records =>
Sort from the main menu bar. Select SOLPROC_CFG_VIEW.moinstid for column
for sorting, use ascending order sorting, and click Add.
13 In Microsoft Query, click View""SQL. The SQL window that contains the SQL
Query statement displays.
The statement looks like:
SELECT SOLPROC_CFG_VIEW.moinstid, SOLPROC_CFG_VIEW.devicename,
SOLPROC_CFG_VIEW.instname,
SOLPROC_ST_VIEW.TOTALCPU
FROM DBA.SOLPROC_CFG_VIEW SOLPROC_CFG_VIEW, DBA.SOLPROC_ST_VIEW
SOLPROC_ST_VIEW
WHERE SOLPROC_CFG_VIEW.moinstid = SOLPROC_ST_VIEW.MOINSTID
GROUP BY SOLPROC_CFG_VIEW.moinstid, SOLPROC_CFG_VIEW.devicename,
HAVING (SOLPROC_ST_VIEW.TOTALCPU>-1)
ORDER BY SOLPROC_CFG_VIEW.moinstid
The query statement will retrieve all the records from the SOLPROC_ST_VIEW if
time-range is not provided. In order to retrieve records that is in a time-range,
edit the statement.
SELECT SOLPROC_CFG_VIEW.moinstid, SOLPROC_CFG_VIEW.devicename,
FROM DBA.SOLPROC_CFG_VIEW SOLPROC_CFG_VIEW, DBA.SOLPROC_ST_VIEW
SOLPROC_ST_VIEW
WHERE SOLPROC_CFG_VIEW.moinstid = SOLPROC_ST_VIEW.MOINSTID and
DBA.SOLPROC_ST_VIEW.TIMERECORDED
between <start-timestamp> and <end-timestamp>
GROUP BY SOLPROC_CFG_VIEW.moinstid, SOLPROC_CFG_VIEW.devicename,
HAVING (SOLPROC_ST_VIEW.TOTALCPU>-1)
ORDER BY SOLPROC_CFG_VIEW.moinstid
The start-timestamp and end-timestamp are UNIX timestamps.
14 After entering the time-range in the query, click OK.

For future reference, save the query to a file.
15 In Microsoft Query, click File => Return Data to Microsoft Excel from the main
menu.
Microsoft Query exits and Microsoft Excel gets back the prompt.
16 In Microsoft Excel, click Next in Step 2 of 3. Step3 of 3 window displays.

17 Click Options. The Pivot Table Options window displays.
18 Disable the following format options and click OK.
Grand totals for columns
Grand totals for rows
Autoformat table
19 Click Finish in the Step 3 of 3 window.

The report window appears.
20 From the Pivot table fields, drag the following fields to the More Category area
(Drop More Category fields here area).
Moinstid
Instname
21 Drag the Devicename field to Total area (Drop more Series fields here area)
22 Drag the TOTALCPU field in the Data area (Drop Data items here area)
The graph provides maximum CPU utilization by BMC ProactiveNet processes.

To change the summary formula to display graph of minimum, average, sum, or
other graph, left-click Max of TOTALCPU.
Figure 157: Pivot Table
A
mcell.conf file parameters
This appendix discusses all of the parameters in the mcell.conf file, which is
installed with the cell enables it to run without any additional configuration. You can
change the configuration parameters in the mcell.conf file to customize the cell for
your particular IT infrastructure and environment. You can override some
parameters using command line arguments when you start the cell.
Action result event parameters

Table 162: Action result event parameters
Parameter
Description
Type
Default value
ActionResultInlineLimit
the size limit, in bytes, for an action result to

be included directly in the action result event
slots
number 4096 (4 KB)
This applies to both the output stream (slot

"output_val") and the error stream (slot
"error_val"). If the respective result is larger
than the indicated size, it is stored in a file.
Instead of placing the value directly in the
*_val slot, the reference to the file is placed in
the corresponding *_ref slot.
ActionResultKeepPeriod
the period, in seconds, that an action result is

kept on behalf of a (Browser) client
number 120 (2 minutes)
The client should retrieve the result within

that period. After the period has expired, the
result is dropped. This is independent of the
action result event. A generated action result
event is not influenced by this parameter. It
exists as long as other events.
Appendix A mcell.conf file parameters 841

Table 163: Cell configuration parameters
Parameter
Description
Type
Default
value
CellDescription
used as the initial value of the

cell_description slot of the internal
MC_CELL_INFO record
string
BMC
Impact
Manager
CellExceptionHandlingEnable
d
used to configure how the the cell handles

exceptions
Boolea
n
Yes
string
Enterprise
Boolea
n
No
string
empty
Yes - cell catches exceptions,

automatically restarts itself, and collects
data for problem analysis including cell
trace files, cell state files and a core dump,
if possible
No - cell service is not available until the
cell is restarted manually
CellOperationLevel
indicates the level on which the cell must

operate
The operation level determines from which
clients the cell accepts connections and
events. The default value can accept
connections from any computer.
CellOperationRelax
indicates whether the operation level should

be lowered in case there is no license
available for the desired level, as set by
CellOperationLevel
Typically, more license tokens are available
for lower operation levels.
ConnectionPortRange1
specifies the range of ports to use for

outgoing connections
For forward propagation, this port is used on
the client side (or on the propagating cell
side). This is useful to pass the event through
firewalls with high restrictions. Most firewall
configurations ignore source port
information but require destination port
information. However, firewall configuration
usually can restrict the source ports as well.
Parameter
Description
Type
Default
value
ConnectionPortReuse 1
indicates whether or not the ports specified

in ConnectionPortRange should be reused as
much as possible
Boolea
n
Yes
determines whether or not the cell is a

Boolea
ProactiveNet Operations Manager cell. This
n
parameter is automatically configured by
mcrtcell and should not be changed manually
in mcell.conf.
No
By default, the cell or command line interface

(CLI) tries to reuse ports from the specified
range, in the given order. When
ConnectionPortReuse=No, for every new
connection within the same session, the next
free port from the specified range is used.
Only when it reaches the end of the range
will it restart at the beginning of the range.
POMEnabled
Jserver can only communicate directly with

POMEnabled cell.
A ProactiveNet Operations Manager
(POMEnabled=Yes) cell does not accept
adapter clients, unless a license key is
provided.
Note:
A ProactiveNet Operations Manager
cell Knowledge Base must not be

recompiled, unless license key is
provided.
If POMEnabled=Yes, then you cannot
msend events to the cell unless you

have an Event Management license.
If POMEnabled=No, then you can
msend events to the cell but the

Jserver will not be able to
communicate with it.
ProcessingLimit Percentage
specifies limitation of event processing speed numbe

r
At 100% the cell accepts events as fast as it
100
can. At x% it does not accept events during

(100-x)% of the time. This limits the cells
CPU utilization.
Parameter
Description
Type
ServerAllInterfaces
determines whether the cell listens on one

Boolea
specific interface or on all available interfaces n
Default
value
Yes
When ServerAllInterfaces=Yes, the

cell communicates on all network interfaces
on the host. When
ServerAllInterfaces=No, the cell only
communicates with the network interface
that has the IP address specified in the
mcell.dir file of that cell.
ServerDirectoryName 1
specifies the name of the cell directory file
path
mcell.dir
ServerPort 1
specifies the TCP/IP port number at which

the cell listens for all in-bound requests from
sources, such as the BMC ProactiveNet
Administration Console, CLIs, and adapters
numbe
r
1828
ServiceModelEnabled
specifies whether the cell is an Event

Management cell or a Service Impact Model
cell.
Boolea
n
No
If ServiceModelEnabled=No, the cell

operates as an Event Management cell.
If ServiceModelEnabled=Yes, the cell
operates as a Service Impact Model cell, if the
SIM class definitions are loaded. If these class
definitions are not available, the cell operates
as an Event Management cell.
Note: Do not try to configure a SIM cell
unless you have the proper license.
SystemLogDirName
specifies the path to the default systemdefined log directory
path
%H/log
SystemTmpDirName
specifies the path to the default systemdefined tmp directory
path
%H/tmp
SystemVarDirName
specifies the path to the default systemdefined var directory
path
%H/var
a Can also be used in the mclient.conf configuration file, which affects the behavior of all of the CLI
commands. These parameters retain the same qualities and definitions in the mclient.conf file as they
have in the mcell.conf file.
Table 164: Cell failover configuration parameters

Parameter
Description
Type
CellDuplicateAutoFailOver
determines whether the primary server

Boolean
automatically fails over to the secondary server.
Default
value
Yes
For automatic failover to occur, this parameter

must be set to YES on both servers.
CellDuplicateAutoSwitchBack
determines whether the secondary server

automatically switches back to the primary
server when the primary server restarts after
failover.
Boolean
Yes
number
120
For automatic switchback to occur, this

parameter must be set to YES on both the
primary and secondary servers.
CellDuplicateFailOverStart
TimeOut
specifies the length of time (in seconds) that

the secondary server waits to become active
after it is started.
When the secondary server starts, it expects
the primary to connect to it. If the primary
server does not connect to the secondary
within the time specified by the
CellDuplicateFailOverStartTimeOut
parameter, the secondary server will become
active.
The time specified for CellDuplicate
FailOverStartTimeOut should be longer
than the time specified for
CellDuplicateFailOverTimeOut to
allow operators to start up primary and
secondary servers at almost the same time, in
any order.
CellDuplicateFailOverTimeOut
specifies the length of time (in seconds) that

the secondary server waits to become active
after the secondary server loses connection to
the primary server.
number
90
CellDuplicateHeartbeatEnabled
can be used to disable the heartbeat of a high

availability cell, to prevent the secondary cell
server from becoming active when the
primary cell server is active due to VMware
clock discrepancies
Boolean
Yes
Parameter
Description
Type
Default
value
CellDuplicateMode
specifies the operation mode of the server.
number
1 = primary server
2 = secondary server
0 = the server is operating as a non-high
availability cell.
This is the only parameter that needs a
different value between primary and
secondary.

Table 165: Client communication parameters
Parameter
Description
ClientCleanupInterval the interval, in seconds, between clean-ups of

pending clients
Type
Default value
number
300
After each such period, clients that did not

give the cell a notice of life are disconnected.
ClientPollTimeOut
the maximum time, in milliseconds, the cell

waits for a client request before it continues
processing
number
200 milliseconds
ClientSendTimeOut
the time interval, in milliseconds, that the cell

has to send a packet to a client on the lowest
communication level
number
1000 milliseconds
DateFormat
the format used to display timestamps in the

date slot
string
CIM
number
5000 milliseconds
A default value of CIM indicates use of the

Common Information Model (CIM) format
from the Desktop Management Force Group.
DateFormat parameters use the syntax of %
[ letter ]. Table 166 on page 847 lists the
DateFormat parameters for Solaris; for other
operating systems, see their documentation.
SynchronizeTimeOut
the maximum time, in milliseconds, the cell

waits for synchronization before dropping a
connection
If the cell receives an event with an empty value for the date slot, it sets the date slot
to the textually formatted value of the date_reception slot. That value is
determined by the DateFormat parameter. This assignment is performed only once,
when the event first enters the cell. If the cell is shut down and restarted, the value of
date remains the same even if the DateFormat parameter has been modified in the
interval.
The CIM format is yyyymmddhhmmss.mmmmmmsutc, where:

yyyy = year
mm = month
dd = day
hh = hour, based on 24-hour clock
mm = minutes
ss = seconds
mmmmmm = microseconds
s = + or utc = offset in minutes from UTC; UTC is the Universal Time Coordinate system
Table 166 on page 847 lists the parameters from the Solaris platform. Other
platforms, including UNIX and Microsoft Windows platforms, may have slight
differences.
Table 166: Date and time format parameters for Solaris
Parameter
Description
%%
same as %
%a
locales abbreviated weekday name
%A
locales full weekday name
%b
locales abbreviated month name
%B
locales full month name
%c
locales appropriate date and time representation
%C
locales date and time representation as produced by date (1)
%d
day of month [1,31]; single digits are preceded by zero (0)
%D
date as %m/%d/%y
%e
day of month [1,31]; single digits are preceded by a space
%h
locales abbreviated month name
Parameter
Description
%H
hour (24-hour clock) [0,23]; single digits are preceded by zero (0)
%I
hour (12-hour clock) [1,12]; single digits are preceded by zero (0)
%j
day number of year [1,366]; single digits are preceded by zero (0)
%k
hour (24-hour clock) [0,23]; single digits are preceded by a blank
%l
hour (12-hour clock) [1,12]; single digits are preceded by a blank
%m
month number [1,12]; single digits are preceded by zero (0)
%M
minute [00,59]; initial 0 is permitted but not required
%n
insert a new line
%p
locales equivalent of A.M. or P.M.
%r
appropriate time representation in 12-hour clock format with %p
%R
time as %H:%M
%S
seconds [00,61]
%t
insert a tab
%T
time as %H:%M:%S
%u
weekday as a decimal number [1,7], where 1 represents Sunday
%U
week number of year as a decimal number [00,53], where Sunday is the first day of week 1
%V
week number of the year as a decimal number [01,53], where Monday is the first day of the week
If the week containing January 1st has four or more days in the new year, then it is considered
week 1. Otherwise, it is week 53 of the previous year, and the next week is considered week 1.
%w
weekday as a decimal number [0,6], where 0 represents Sunday
%W
week number of year as a decimal number [00,53], where Monday is the first day of week 1
%x
locales appropriate date representation
%X
locales appropriate time representation
%y
year within century [00,99]
%Y
year, including the century. (for example, 2006)
%Z
time zone name or abbreviation, or no bytes if no time zone information exists
The following table describes the encryption parameters that are listed in the
mcell.conf file.
Table 167: Encryption parameters
Parameter
Description
Type
AllowAdapterFrom
specifies the adapters within the range of IP addresses string
Default value
0./0
These are adapters that use the BMC Impact Solutions

communications protocol.
AllowBrowserFrom
specifies the BMC ProactiveNet Administration

Console and the BMC Impact Portal connections
within the range of IP addresses
string
0./0
AllowCellFrom
specifies the cells within the range of IP addresses
string
0./0
AllowCLIFrom
specifies the command line interfaces (for example,

mkill or mcstat) within the range of IP addresses
string
0./0
AllowConnectionFrom
specifies the client within the range of IP addresses

that is allowed to connect to a cell
string
0./0
AllowEIFFrom
specifies the EIF event sources (for example, a

postemsg) within the range of IP addresses
string
0./0
Encryption
specifies to use encryption
Boolean Yes
EncryptionKey
specifies the encryption key
string
ForceEncryption
specifies if encryption is to be forced
Boolean No
(empty)

Table 168: Event Repository cleanup parameters
Parameter
Description
Type
Default value
EventAutoClose
automatically closes a duplicate event

in the database when an event arrives
with status=CLOSED, or it is closed
in the Refine rule phase
Boolean
Yes
If the default value is left as Yes, the

event is dropped and the duplicate is
closed. If the value is set to No, there is
no duplicate detection and the CLOSED
event is not dropped.
Parameter
Description
Type
Default value
EventDBCleanupDurationLimit
the maximum duration, in seconds, of

a single cleanup
number
10
number
3600, or 1 hour
After expiration of that period, the

cleanup is interrupted. Normal
operation proceeds for an equal
duration. Then cleanup is resumed,
with the same limit again.
EventDBCleanupInterval
EventDBCleanupPercentage
the time interval, in seconds, between

periodic cleanups of the repository
minimum =
60; no
maximum
the percentage of free space required at number

termination of an EventDB cleanup
With a default EventDBSize of
100000, this means that at least 10000
places must be available at termination
of a completed cleanup.
10
minimum=5;
no maximum
EventDBCleanupOnDateReceptio
n
indicates the preference for deleting

events from the repository based on
when they were received instead of
when they were last modified
Boolean
No
EventDBCleanupPreferClosed
indicates the preference for cleaning

up closed events rather than older
events
Boolean
No
number
259,200, or 3
days;
When there is not enough free space

after removing all expired events,
additional, unexpired events are
removed. These are selected, oldest
first, either from any events or from
the closed ones first.
The default is no, meaning that the
event status value is not taken into
account when selecting events for
removal.
EventDBKeepClosed
the minimum age, in seconds, of

CLOSED events before they are
removed from the repository
Note: Any modifications to the
EventDBKeepClosed parameter
should be carefully considered. Events
of these classes remain in the event
repository until you manually delete
them.
no minimum;
no maximum
Parameter
Description
Type
Default value
EventDBKeepNonClosed
the minimum age, in seconds, of nonclosed events before they are removed
from the repository
number
2592000, or 30
days
minimum
value=0;
maximum
value =
4294967295, or
136 years
the number of events to retain in the

repository (the mcdb and xact files
located in the MCELL_HOME/var/
CellName directory path
EventDBSize
number
330000
minimum
value=100;
no maximum
The default size is 100000.

When the specified number is reached,
the cell performs a cleanup procedure,
which is described in Executing reboot
command via remote action results in
timeout messages on page 383
The value of the EventDBSize may
have an impact on memory
consumption. When increasing the
value of the EventDBSize, consider the
size of your systems virtual memory
and the number of programs running
on the system. Contact your system
administrator if in doubt.
EventDBNoCleanupClosed
list of classes in which closed events

will not be deleted from the repository
string
empty
EventDBNoCleanupNonClosed
list of classes in which non-closed

events will not be deleted from the
repository; comma separated
Boolean
SMC_STATE_
CHANGE
Event cleanup process

The related group of event cleanup parameters gives you control over which events
are removed, limits the duration of the cleanup, and specifies a preference for
cleaning up closed events rather than older events.
A cleanup first removes expired events. Expired events are those that are older than
the times in the EventDBKeepClosed and EventDBKeepNonClosed parameters, for
closed and non-closed events, respectively. After this cleanup, if there is still less free
space than specified in the EventDBCleanupPercentage parameter, additional,
unexpired events are removed. As many events are removed as needed to reach the
desired amount of free space.
Older events are removed first, with one possible exception. If parameter
EventDBCleanupPreferClosed=Yes, closed events are removed first, even if some
older unclosed events remain. In EventDBCleanupPreferClosed=No mode, all
events are considered, starting with the oldest first.
The mc_date_modification slot is considered to determine the time of an event.
However, if parameter EventDBCleanupOnDateReception=Yes, the
date_reception slot is considered instead.
Cleanup is interrupted if it takes longer than the value of the
EventDBCleanupDurationLimit parameter. By default, this value is 10 seconds. If
the cleanup period was not long enough to remove all expired events, a new cleanup
is scheduled for a later time with the same amount of time as the duration limit. If all
expired events were removed, the next cleanup is scheduled after the normal
interval value of EventDBCleanupInterval.
Table 169: Heartbeat parameters
Parameter
Description
Type
Default value
HeartbeatEnabled
indicates whether the heartbeat monitoring

mechanism is enabled or not
Boolean
Yes
HeartbeatInterval
the default interval between two beats, if not

specified in the data object
number
60
HeartbeatMissedCritica
l
the default number of consecutive missed beats

that are needed to generate a critical event, if not
number
HeartbeatMissedMinor

that are needed to generate a minor event, if not
number
HeartbeatMissedWarning

that are needed to generate a warning event, if
not specified in the data object
number
The heartbeat feature enables a specific cell, called the monitoring cell, to monitor one
or more cells, called the monitored cell or cells, for enabled access by the monitoring
cell.
The parameter in the mcell.conf file of the monitored cell should be
HeartbeatEnabled=Yes. By default, the monitored cell sends a beat every 300 seconds.
Heartbeats are configured through MC_CELL_HEARTBEAT dynamic data objects in the
monitoring cell. An MC_CELL_HEARTBEAT dynamic data object contains information,
such as the name of the cell to be monitored, the length of the expected time intervals
between the heartbeats, and the number of heartbeats that must be missed to
generate corresponding internal events in the monitoring cell.
The cell receives the dynamic data object either by loading it from the data directory,
receiving it through an mposter call, or viewing it in the Administrative View of the
BMC ProactiveNet Administration Console . The monitoring cell sends a request to
the monitored cell. The monitored cell sends a heartbeat back to the monitoring cell
at the specified intervals. If the monitoring cell does not receive a heartbeat in the
expected timeframe, the monitoring cell generates an alert that can be viewed in the
BMC ProactiveNet Operations Console console.
The default settings for missing heartbeats are as follows:
1 missed heartbeat generate a warning event
2 missed heartbeats generate a minor event
3 missed heartbeats generate a critical event
For example, cell 1 is the monitoring cell, which sends a request to cell 2, the monitored
cell. If it does not receive a response at a specified interval, then the monitoring cell
sends an alert that can be seen in the BMC ProactiveNet Operations Console.
After a monitoring cell terminates and restarts, it is aware of prior requests for
heartbeats because it rereads the dynamic data objects that are stored in the cell
repository mcdb. After it rereads the data, the monitoring cell attempts to resend the
request to the monitored cell.
If the monitored cell terminates, the monitoring cell resends the request for
heartbeats at the specified intervals. Table 170 on page 853 lists the
MC_CELL_HEARTBEAT slots.
Table 170: Heartbeat slots
Slot
Description
cell
target monitored cell name
enable
0 = disabled, 1 = enabled
last_time
time last heartbeat was received
interval
length of interval between heartbeats

Specify zero (0) to use the default, as determined by the HeartbeatInterval
configuration parameter.
missed_warning
number of missed heartbeats before a WARNING event is generated

Specify zero (0) to use the default, as determined by the corresponding
HeartbeatMissedWarning configuration parameter. Specify -1 to disable
generation of the corresponding event.
Slot
Description
missed_minor
number of missed heartbeats before a MINOR event is generated

HeartbeatMissedMinor configuration parameter. Specify -1 to disable generation
of the corresponding event.
missed_critical
number of missed heartbeats before a CRITICAL event is generated

HeartbeatMissedCritical configuration parameter. Specify -1 to disable
generation of the corresponding event.
missed
number of consecutive missed heartbeats
Note
Deleting an instance of an MC_CELL_HEARTBEAT data object from a monitoring cell

terminates the monitoring of the corresponding cell or cells.

Table 171: Internal cell monitors parameters
Parameter
Description
Type
Default value
CellEventEnable
a flag that indicates whether the cell should generate

internal events, such as start, stop, and heartbeat; does
not include events generated by the rules
Boolean
Yes
CellErrorEvents
indicates whether an event processing error should

Boolean
produce a special internal event to flag that error, or not
Yes
CellMetricsEnabled determines whether metrics for cell performance are

collected or not
CellTickInterval
the time interval, in seconds, between generation of cell

heartbeat events (ticks)
Boolean
Yes
number
600
Boolean
No
The purpose of such heartbeats is to send a sign of life

from the cell. A zero (0) value disables cell ticks without
disabling other internal events. This parameter operates
only if the CellEventEnable is set to Yes.
RuleLoopDetect
a flag that requires the cell to check for certain

conditions that can induce infinite looping of events
Setting this parameter to Yes can cause mild cell
performance degradation.
KB parameters
KB parameters
Table 172: KB parameters
Parameter
Description
Type
Default value
KBDirName
the path to the active KB directory
path
the KB directory in the

cells cell-specific
configuration directory
KBRecoveryDirName
the path to an alternate KB directory to be

used for recovery from catastrophic damage
path
kbrecovery
For more information, see BMC ProactiveNet

Command Line Interface Reference Manual.
The propagation parameters allow you to configure propagation and destination
buffers.
You can configure these parameters for individual destinations and also configure a
default value for all other destinations. Use the asterisk (*) to specify all destinations.
The following parameter definition illustrates how to configure these parameters for
all destinations.
DestinationBufferReconnectInterval = *=600
This example specifies that the interval to try to reconnect is 600 seconds for all
destinations. If the * is not explicitly defined, the default value for the parameter will
be applied to all destinations.
To configure parameters for individual destinations, the value for these parameters
is formatted as a comma-separated sequence of destination-specific settings in the
form of DestinationName=Value. DestinationNames #1 and #2 are reserved to
indicate the primary and secondary nodes of a high availability cell.
For example,
DestinationBufferReconnectInterval = #1=10,#2=10,*=600,SlowCell=1200
This example specifies that the interval to try to reconnect is 10 seconds for the high
availability nodes, 1200 seconds for a cell called SlowCell and 600 seconds for all
other destinations. If the * is not explicitly defined, the default value for the
parameter will be applied to all unspecified destinations.
Table 173: Propagation parameters

Parameter
Description
Type
Default
value
DestinationBufferBaseSize
the initial number of messages, or

events, retained in the buffer
number 5000
DestinationBufferExpandPercentage
percentage of the actual buffer size that number 10

the buffer expands when events
continue to be propagated after the
buffer is full
DestinationBufferSizeLimit
maximum allowed buffer size
number 0
The default value of 0 means the buffer

size is unlimited. In practice, the size is
limited to 2^32-1, or to the available
amount of memory.
If the limit is set to a value lower than
DestinationBufferBaseSize, the
buffer will not expand beyond
DestinationBufferBaseSize.
DestinationBuffer
ReducePercentage
DestinationBufferKeepSent
DestinationBufferKeepWait
minimum percentage of free buffer

size required to perform a reduction
number 50
the time, in seconds, to keep sent

events buffered while waiting for an
answer
number 300
The amount of time, in seconds, that

events are retained in the buffer until
they can be sent.
number 3600, or 1
hour
Once the specified time elapses, the

retained events are removed from the
buffer.
DestinationBufferReconnectInterval
the time interval, in seconds, in which

the cell attempts reconnection to a
destination if the original connection
failed
number 600
The cell continues to reestablish a

connection as long as there are events
in the buffer.
Destination BufferResendCount
the number of times to resend

unanswered events
PropagateBufferBaseSize
the number of requests for propagation number 5000

to retain in the propagation buffer
Such a request corresponds to firing a
Propagate rule. There is one propagate
buffer per cell with as many places for
requests as set by the parameter.
number 1
Parameter
Description
Type
Default
value
Propagate BufferExpandPercentage
percentage of the actual buffer size that number 10

the buffer expands when events
continue to be propagated after the
buffer is full
PropagateBufferSizeLimit
maximum allowed buffer size
number 0
The default value of 0 means the buffer

size is unlimited. In practice, the size is
limited to 2^32-1, or to the available
amount of memory.
If the limit is set to a value lower than
Propagate BufferBaseSize, the
buffer will not expand beyond
Propagate BufferBaseSize.
PropagateBuffer ReducePercentage
minimum percentage of free buffer

size required to perform a reduction
number 50
PropagateConfigFileName
the name of the propagation

configuration file
path
mcell.
propagate
a Can also be used in the mclient.conf configuration file, which affects the behavior of all of the BMC
Impact Solutions CLI commands. These parameters retain the same qualities and definitions in the
mclient.conf file as they have in the mcell.conf file.
Deprecated MessageBuffer propagation parameters

The MessageBuffer propagation parameters described in this section have been
deprecated, but are retained for backward compatibility with earlier versions of
BMC Impact Manager. These parameters may be removed in a later version of the
product.
If one of the DestinationBuffer parameters is not specified, or if it does not contain
a default setting, the value of the corresponding MessageBuffer parameter is used
as default. If the corresponding MessageBuffer parameter is not specified, an
internal default value is used.
Table 174: Deprecated MessageBuffer propagation parameters
Parameter
Description
Type
MessageBufferBaseSize
the initial number of messages, or events,

retained in the buffer
number 5000
the time, in seconds, to keep sent messages

buffered while waiting for an answer
number 300
MessageBufferKeepSent
Default
value
Parameter
Description
Type
Default
value
MessageBufferKeepWait
The amount of time, in seconds, that messages number 3600, or 1

are retained in the buffer until they can be sent.
hour
Once the specified time elapses, the retained
messages are removed from the buffer.
MessageBufferReconnectInterval
the time interval, in seconds, in which the cell

attempts reconnection to a destination if the
original connection failed
number 2m
The cell continues to reestablish a connection

as long as there are messages in the buffer.
MessageBufferResendCount
the number of times to resend unanswered

messages
number 1
MessageBufferSize
the number of messages, or events, retained in number 20000

the buffer when the cell is unable to send, or
when waiting for an answer; a message that is
not sent because the destination is down, for
example, or a message that was sent but not
yet answered, remains in the buffer
A cell maintains one buffer for each
destination. Such buffers have the same size,
as set by the parameter.
the number of requests for propagation to
retain in the propagation buffer
PropagateBufferSize
number 20000
Such a request corresponds to firing a

Propagate rule. There is one propagate buffer
per cell with as many places for requests as set
by the parameter.

The following table lists the parameters that report on client operations on the cell.
Table 175: Reporting client connection parameters
Parameter
Description
ReportConnectClients
reports connect and disconnect of string

clients
Type
Default value
PPM, browser, Console,
ImpactExplorer, mcontrol, mkill,
Parameter
Description
Type
Default value
ReportModifyClients
reports modifications of events

by clients
string

The following table lists the parameters that control the service model.
Table 176: Service model parameters
Parameter
Description
Type
ServiceModelEnabled
specifies whether the cell is an Event Management Boolean

cell or a Service Impact Model cell.
Default value
No
If ServiceModelEnabled=No, the cell operates as

an Event Management cell.
If ServiceModelEnabled=Yes, the cell operates as a
Service Impact Model cell, if the SIM class
definitions are loaded. If these class definitions are
not available, the cell operates as an Event
Management cell.
Note: Do not try to configure a SIM cell unless you
have the proper license.
ServiceModelPublish
controls whether or not Service Model Data is

published
Boolean
YES
Boolean
YES
Note: If ServiceModelPublish is disabled, the

ServiceModelDirectFeed parameter has no
impact. In this case, Service Model Data is always
accepted through direct feed.
ServiceModelDirectFeed
when ServiceModelPublish is enabled,

ServiceModelDirectFeed controls whether
or not Service Model Data is accepted through
direct feed
State Builder parameters

The running of the State Builder is controlled by the cell, using the parameters in the
mcell.conf file.
Table 177 on page 860 lists the StateBuilder parameters.
Trace parameters
Table 177: State Builder parameters

Parameter
Description
Type
Default value
StateBuildInterval
the time interval, in seconds, between two

builds of saved states of the cell
number
3600
StateBuildSize
the maximum size, in kilobytes, of a

transaction file before it is transformed into a
new saved state when the StateBuilder runs
again.
number
10m
If BMC Impact Manager seems to be

consuming too much CPU, verify that State
Builder is not running too frequently.
Compare the time stamps of the mcdb.* files in
the var directory of the cell. If the time
between two state builds is less than 10
minutes, increase the StateBuildSize parameter.
StateBuildConfigFileName the StateBuilder configuration file name
path
StateBuildAtTerminate
indication to run the StateBuilder when the

cell terminates
Boolean
No
StateBuildRunTimeOut
the timeout, in seconds, to consider when

waiting for the StateBuilder to terminate
number
600 seconds
Trace parameters
Table 178: Cell tracing parameters
Parameter
a
Trace
Description
Type
Default value
enables the generation of trace messages
Boolean
Yes
TraceSrc
includes the file and line number in the trace messages Boolean
No
TraceConfigFileName
location of the file containing the configuration of the

trace messages
mcell.trace
TraceDefaultFileNam
e
destination file to redirect trace messages from

path
stderr to, in case the cell runs as a daemon or service
Note: If you direct trace files to the temporary
directory of the cell (for example,
TraceDefaultFileName=%T/trace - %T=cell_tmp), the
trace file will be removed each time the cell starts
because the cell always cleans up its tmp directory at
startup.
To keep trace files across cell sessions, do not use the
tmp directory as the default destination file location.
path
=%L/%P-log
Trace parameters
Parameter
Description
Type
Default value
TraceRuleLevel
sets the level of rule execution tracing:
number
0no rule tracing and no cell error catch (not

recommended)
1no rule tracing; cell errors are caught in the
standard cell trace (default)
2rule tracing enabled
TraceRulePhases
When rule tracing is enabled, lists the rule phases to

string
be traced. The value ALL can be used to specify that
all phases are to be traced. Each phase can be prefixed
with a + or a - sign to indicate addition or removal
from the list. The list is interpreted in sequential order.
ALL
For example, the following parameter

setting:TraceRulePhases=ALL,-refine,regulate
indicates that all rule phases will be traced except for
the refine and regulate phases.
NOTE: TraceRulePhases and TraceRuleName
work together to determine which rules are traced. A
rule is only traced if both the phase to which it
belongs and the rule itself are configured for tracing.
TraceRuleNames
When rule tracing is enabled, lists module:rule

string
combinations to be traced. The value ALL can be used
to specify that all modules and/or rules are to be
traced. Each module:rule combination can be prefixed
with a + or a - sign to indicate addition or removal
from the list. The list is interpreted in sequential order.
ALL:ALL
For example, the following parameter

setting:TraceRuleNames=HelpDesk:ALL, HelpDesk:rule1,SendMail:rule1
indicates that all rules in the HelpDesk module will
be traced except for rule1. Also, rule1 from the
SendMail module will be traced.
NOTE: TraceRulePhases and TraceRuleNames
work together to determine which rules are traced. A
rule is only traced if both the phase to which it
belongs and the rule itself are configured for tracing.
Trace parameters
Parameter
Description
Type
Default value
TraceRuleHeader
enables you to configure the header text of the trace

messages. You can configure the header text to
contain references to parameters, using the following
designations to represent the associated parameters:
text
%F, %L: %P
%R: %C #
%H:
%I message id
%F source file name
%L source line number
%M KB module name
%R rule name
%P rule phase
%H handle of the main event being processed
(event_handle slot)
%C class name of the main event being processed
For example, the default parameter
settingTraceRuleHeader=%F, %L: %P %R: %C #%H:
results in a message similar to:mc_intevt.mrl, 42: new
StbldStop: MC_CELL_STATBLD_STOP #118: Rule
execution starting
TraceRuleToXact
indicates whether to include rule tracing in the

Boolean
transaction file, as well as in the standard cell trace, in
module RULES
No
TraceFileSize
limit on the size of a trace destination file, expressed

in kilobytes
number
5m
number
10
Boolean
Yes
When the trace file grows beyond the indicated size,

it is renamed with a numerical suffix appended. A
new trace file is started.
Special value 0 (the default) means no limitation on
file size.
TraceFileHistory
number of trace files to be kept in history

When this number is reached, a new numbered trace
file will remove the oldest one.
TraceFileAppend
indicates whether to append to existing trace files or

empty existing trace files at startup
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index
A
action result event parameters
ActionResultInlineLimit 841
ActionResultKeepPeriod 841
actions
responding to an event 377, 379
adapter
auto-sync 239
best practices 238
BMC PATROL 224
BMC Performance Manager Portal 225
BMC TM ART 231
BMC VMware 231
limitations 246
pre-requisites 218
prerequisites 218
SCOM 2007 230
add adapter
BMC PATROL 251
BMC Portal 282
SCOM 2007 311
adding adapters
BMC adapter for VMware 331
BMC TM ART 322
HP OVO 286
Tivoli 299
administering remote cells
Administration View (BIX) 795
Administration View
creating new data instance 683
edit menu 685
exporting data 686
managing cells from 795
Slot Quick Filter 680
sort multiple columns 681
sort, single-click 683
Advanced subtab 738
alias 758
alias formulas
conditional operators 587
functions in 589
AllowAdapterFrom 849
AllowBrowserFrom 849
AllowCellFrom 849
AllowCLIFrom 849
AllowConnectionFrom 849
AllowEIFFrom 849
Application Diagnostics. See BMC ProactiveNet
Application Diagnostics
Atrium CMDB. See BMC Atrium CMDB
Auto Bind cell connection property 33
B
blackout policy (standard), creating 592
blackout policy, creating 593, 597, 602, 640
BMC adapter for VMware
adding 331
BMC AppSight integration. See BMC ProactiveNet
Application Diagnostics
BMC Atrium CMDB
integration 345
viewing publication history 352
viewing service model objects 351
BMC Impact Explorer
remote cell administration 795
using to monitor business services 733
BMC PATROL
adapter 224
add 251
BMC ProactiveNet Application Diagnostics 448
adapter 225
BMC Portal
add 282
changing your password 35
invocation tree 449
BMC ProactiveNet Publishing Server
publication filters 348
Index
863
Auto Reconnect configuration parameter 34
configuration parameters 33
Enable Port Range configuration parameter 34
Heartbeat Rate configuration parameter 34
logging out of and in to from the
administration console 34
setting connection properties 33
BMC TM ART
BMC TM ART adapter
adding 322
limitations 247
overview 231
prerequisites 221
user credentials 322
BMC VMware
salient features 234
business services
monitoring in BMC Impact Explorer 733
C
cell configuration
creating files for specific cells 764
cell connection properties
specifying ports 32
used to connect to the BMC ProactiveNet
Server 30
cell parameters
CellDescription 842
CellOperationLevel 842
CellOperationRelax 842
ConnectionPortRange 842
POMEnabled 843
ProcessingLimitPercentage 843
ServerAllInterfaces 844
ServerPort 844
SystemLogDirName 844
SystemTmpDirName 844
SystemVarDirName 844
cell tracing parameters, list of 860
CellDescription 842
CellErrorEvents 854
CellEventEnable 854
CellMetricsEnabled 854
CellOperationLevel 842
CellOperationRelax 842
864
cells
heartbeats 855
permissions required to start on UNIX 779
production, described 759
reconfiguring 778
remote administration 795
starting and stopping 778
starting and stopping on UNIX 779
starting and stopping on Windows 780
starting or stopping on Windows 780
starting with services 781
stopping with mkill 780
stopping with services 780
test, described 759
view information 795
CellTickInterval 854
central ProactiveNet Server 507
changing your BMC ProactiveNet Administration
Console password 35
child ProactiveNet Server 507
Class list box 737
client configuration for passive connections 770
client parameters 855
ClientCleanupInterval 846
ClientPollTimeOut 846
ClientSendTimeOut 846
DateFormat 846
SynchronizedTimeOut 846
ClientCleanupInterval 846
ClientPollTimeOut 846
ClientSendTimeOut 846
closure policy, creating 606
CMDB. See BMC Atrium CMDB
commands
mcell 779
mkill 779, 780
net start 781
net stop 780
communication and encryption
AllowAdapterFrom 849
AllowBrowserFrom 849
AllowCellFrom 849
AllowCLIFrom 849
AllowConnectionFrom 849
AllowEIFFrom 849
encryption behavior 773
ForceEncryption 773
mcell.conf settings 772
mcell.dir settings 773
mclient.conf settings 773
component based enrichment policy 597
component based enrichment policy, excluding
slots 601
computer system CIs 353
conditional operators in alias formulas 587
configuration
BMC ProactiveNet Server 33
configuration files
cell-specific, creating 764
mcell.conf 761, 765
mcell.propagate 765
mcell.trace 788
StateBuilder configuration 798
configuration parameters
HeartbeatEnabled 852
HeartbeatInterval 852
HeartbeatMissedCritical 852
HeartbeatMissedMinor 852
HeartbeatMissedWarning 852
configure
PATROL Agent Proxy by typing agent name
263
PATROL proxy 251
profiles on the PATROL Agent Proxy 264
configuring
clients for passive connections 770
reloading cell configuration 778
setting cell-specific configurations up 764
StateBuilder 798
configuring adapters
BMC TM ART adapter 323
HP OVO adapter 287
Tivoli adapter 299
connecting
cells in a protected zone 770
connecting to the BMC ProactiveNet Server,
methods used 21
connection protocols, used to connect to the BMC
ProactiveNet Server 21
console
dynamic data 683
exporting data 686
sort data fields 681
sort, single-click 683
consumer components
searching for 739
correlation policy, creating 609
creating
configuration files
cell-specific 764
Creating_event_correlation_policies 609
customize
application class attributes 316
D
data
creating new instance 683
dynamic 683
exporting 686
sorting 681
DateFormat 846
deleting
event alias associations 590
deployment scenarios 758
Direct, method used to connect to the BMC
dynamic blackout policy, enabling 654
dynamic data 683
model 852
dynamic data enrichment policies
blackout 654
creating new 641
dynamic enrichment policy, creating 657
E
ECF (event condition formula) 569
edit menu 685
editing
event alias associations 589
HP OVO attribute list 292
IBM Tivoli attribute list 305
editing monitored attributes 305
Editing_slots 685
EM cell
production 759
test 759
encryption
behavior 773
mcell.conf settings 772
mcell.dir settings 773
mclient.conf settings 773
encryption key 773
enhancements
BMC PATROL 274
enrichment policy, creating 613
error file
mcell.err 794
escalation policy, creating 618
establishing inbound connection in protected
environment 770
evaluation order of policies 570
event alias associations
deleting 590
editing 589
Index
865
event condition formula 569
event management policies
closure 606
component based enrichment 597
correlation 609
enabling and disabling 640
escalation 618
execution order 599
notification 622
propagation 626
recurrence 628
remote action policy 562, 631
standard blackout 592
suppression 631
threshold 634
timeout 638
event parameters
EventAutoClose 849
EventDBCleanupDurationLimit 850
EventDBCleanupInterval 850
EventDBCleanuponDateReception 850
EventDBCleanupPercentage 850
EventDBCleanupPreferClosed 850
EventDBKeepClosed 850
EventDBKeepNonClosed 851
EventDBNoCleanupClosed 851
EventDBNoCleanupNoCleanupNonClosed 851
EventDBSize 851
repository cleanup 849
event policy
evaluation order 570
types of 562
event propagation
enabling 767
illustrated 767
event repository
cleanup parameters 849
event selectors
defined 567, 581
groups 568
maximum number 568
EventAutoClose 849
EventDBCleanupDurationLimit 850
EventDBCleanupInterval 850
EventDBCleanupOnDateReception 850
EventDBCleanupPercentage 850
EventDBCleanupPreferClosed 850
EventDBKeepClosed 850
EventDBKeepNonClosed 851
EventDBNoCleanupClosed 851
EventDBNoCleanupNonClosed 851
EventDBSize 851
events
exporting to a flat file 805
propagating using a gateway 765
responding with an action 377, 379
events, sorting 681
exclude filter types 271, 281
ExportConfigFileName 798
ExportDiscarded 798
exporting
event data from mcdb by StateBuilder 798
events to a flat file 805
exporting data 686
ExportTriggerArguments 798
ExportTriggerProgram 798
external data sources 572
F
files
gateway.export 798, 805, 806
mcdb state 797
mcell.conf 765
mcell.err error 794
mcell.modify 771
mcell.propagate 765
mcell.trace 788
propagation configuration 765
statbld.conf 797, 805
statbld.exe 797
statbld.trace 798, 807
StateBuilder configuration 798
trace configuration 788
xact transaction 798
filtering publications 348
Find Service Components box 737
finding service components to view 737
ForceEncryption 773
functions
in alias formulas 589
G
gateway 765
gateway configuration 799
gateway.export file 798, 805, 806
General subtab 738
Global Services
group 737
H
HeartbeatEnabled parameter 852
866
HeartbeatInterval parameter 852
HeartbeatMissedCritical parameter 852
HeartbeatMissedMinor parameter 852
HeartbeatMissedWarning parameter 852
heartbeats, cell 855
Hierarchy
device hierarchy 267, 277
HP OM adapter
prerequisites 219
HP OVO adapter
adding 286
HTTP Tunnel, method used to connect to the BMC
I
icons
Refresh 743
Impact/Cause View
illustrated 734
opening 734
include filter types 267, 277
Index Term 225, 227, 259, 272, 310, 330, 368, 471, 472,
522, 523, 561, 677, 697, 754758
integrating with BMC Atrium CMDB 345
K
KBDirName 855
KBDirName parameter 855
KBRecoveryDirName parameter 855
Knowledge Bases
KBDirName 855
parameters
KBRecovery 855
KPIs
abnormality thresholds 246
intelligent thresholds 245
L
launching the administration console
configuring cell connection properties to the
server 30
connection protocols used 22
on Solaris 24
on Windows 22
using multiple consoles on Windows
computers 24
using the Search function 26
lazy loading 472
M
mcdb state file 797
mcell command 779
mcell.conf file
parameter rules 761
path substitution parameters 762
specifying paths 762
mcell.dir file
configuring clients for passive connections 770
description and usage 768
example file 769
format of entries 768
keywords for entries 769
rules applied to entries 769
mcell.err file 794
mcell.modify file 771
mcell.propagate file 765
default options 766
usage 765
mcell.trace file 788
menu, editing 685
message buffer parameters
MessageBufferKeepSent 856, 857
MessageBufferKeepWait 856, 858
MessageBufferReconnectIntervalparameters
MessageBufferReconnectInterval 856,
858
MessageBufferResendCount 856, 858
MessageBufferSize 855, 857, 858
MessageBufferKeepSent 856, 857
MessageBufferKeepWait 856, 858
MessageBufferReconnectInterval 856, 858
MessageBufferResendCount 856, 858
MessageBufferSize 855, 857, 858
methods used to connect to the BMC ProactiveNet
Server, Direct 21
methods used to connect to the BMC ProactiveNet
Server, HTTP Tunnel 21
mkill command 779, 780
modify
application class attributes 316
profile on PATROL Proxy 260
monitor to CI alias 758
monitoring
business services in BMC Impact Explorer 733
monitoring passive connections 771
multiple ProactiveNet Server deployment 507
My Services group 736
Index
867
N
Name contains text box 737
navigation pane
using to view service components 735
navigation tree, improving performance 472
new data instance, creating 683
notification policy, creating 622
O
opening Impact/Cause Views 734
originating ProactiveNet Server 507
P
parameters
ActionResultInlineLimit 841
ActionResultKeepPeriod 841
client 855
HeartbeatEnabled 852
HeartbeatInveral 852
HeartbeatMissedCritical 852
HeartbeatMissedMinor 852
HeartbeatMissedWarning 852
KBRecovery 855
Server 855
state 855
trace, list of 860
tracing, configuring 792
passive connections 770
client configuration 770
monitoring 771
password, changing for the BMC ProactiveNet
Administration Console 35
permissions
considerations for root user 779
868
policies
Blackout 592, 640
Closure 606
component based enrichment 597
Correlation 609
creating new dynamic data enrichment 641
dynamic data enrichment blackout 654
Dynamic Enrichment 657
enabling dynamic data enrichment dynamic
data enrichment policies
enabling out-of-the-box 653
enabling standard out-of-the-box 640
Enrichment 613
Escalation 618
evaluation order 570
new closure 606
new correlation 609
new escalation 618
new notification 622
new propagation 626
new recurrence 628
new standard blackout 592
new suppression 631
new threshold 634
new timeout 638
Notification 622
Propagation 626
Recurrence 628
Suppression 631
Threshold 634
Timeout 638
policy type, user-defined
creating presentation names for 693
creating processing rules for 694
creating, task overview 691
defining policy data class for 691
prerequisites, adapters 218
presentation names
defining for a new policy type 693
ProcessingLimitPercentage 763, 843
production cells
described 759
profile types used in the administration console
Admin profile 36
User profile 36
PropagateBufferSize 856, 858
PropagateConfigFileName 857
Propagates Priority check box 737
propagating
events using a gateway 765
propagation configuration file, mcell propagate 765
propagation parameters
PropagateBufferSize 856, 858
PropagateConfigFileName 857
propagation policy, creating 626
properties
application level 316
parameter level 317
protected environments
client configuration for passive connections 770
monitoring passive connections 771
protected zone, connecting cells in 770
provider components
searching for 739
publication filters 348
publication history
viewing 352
publishing server
computer system CIs 353
R
reconfiguring
cell files for 778
recreate
instances 340
recurrence policy, creating 628
Refresh icon 743
Related Components subtab
described 738
illustrated 739
searching for provider and consumer service
components 739
remote actions
accessing results of 377, 379
responding to event 377, 379
remote execution
policy 374
Remote Action Policy dialog box 359, 363
Remote Action Policy window 358, 376
troubleshooting 383
results
of a remote action 377, 379
Results list 737
return codes
statbld 799
root permissions
considerations 779
rule phases 570
RuleLoopDetect 854
S
Schedule subtab 738
search
index 339
searching
for provider or consumer components 739
for service components to view 737
server parameters 855
CellErrorEvents 854
CellEventEnable 854
CellMetricstEnabled 854
CellTickInterval 854
ProcessingLimitPercentage 763, 843
RuleLoopDetect 854
ServerPort 844
ServerAllInterfaces 844
ServerPort 844
service component
viewing SLM agreements for 740
service components
accessing through navigation pane 735
finding to view 737
searching for providers 739
viewing information about 738
service model objects
viewing 351
services
starting cells with 781
stopping cells with 780
Services Group tab 736
Services View
overview 733
subtabs 738
setting
cell-specific configuration up 764
SIM cell
production 759
test 759
SLM
viewing agreements for a component 740
SLM subtab (Services View details) 738
sorting 681, 683
starting cells
UNIX platforms 779
using mcell 778
Windows 780
with net start 781
with services 780, 781
statbld return codes 799
statbld.conf file 797, 805
statbld.exe file 797
statbld.trace file 798, 807
Index
869
state configuration parameters 855
ExportConfigFileName 798
ExportDiscarded 798
ExportTriggerArguments 798
ExportTriggerProgram 798
StateHistoryCount 799
state parameters 855
StateBuildAtTerminate 860
StateBuildConfigFileName 860
StateBuildInterval 860
StateBuildRunTimeOut 860
StateBuildSize 860
StateBuildAtTerminate 860
StateBuildConfigFileName 860
StateBuilder 797
configuration parameters for event data export
798
StateBuildInterval 860
StateBuildRunTimeOut 860
StateBuildSize 860
StateHistoryCount 799
stopping cells
on Windows 780
UNIX platforms 779
using the mkill command 780
with mkill 778
with net stop 780
with services 780
subtabs
Advanced 738
General 738
in Services View 738
Related Components 738
Schedule 738
suppression policy, creating 631
SynchronizedTimeOut 846
System Center Operation Manager 2007
add 311
System Centre Operation Manager 2007
adapter 230
SystemLogDirName parameter
described 844
used to specify log and trace file directories 779
SystemTmpDirName parameter
described 844
used to specify trace and log file directories 779
SystemVarDirName parameter
described 844
test cells
described 759
threshold policy, creating 634
timeframes
creating 573
timeout policy, creating 638
Tivoli, adapter for
adding 299
Tivoli, editing monitored attributes 305
toolbar
in dynamic data editor 680
trace configuration file 788
configuring 788
parameters 788
Trace parameter 860
trace parameters
list of 860
trace, disable encryption to 775
TraceConfigFileName parameter 860
TraceDefaultFileName parameter 860
TraceFileAppend parameter 862
TraceFileHistory parameter 862
TraceFileSize parameter 862
TraceRuleLevel parameter 861
TraceRuleToXact parameter 862
TraceSrc parameter 860
tracing parameters
configuring 792
Trace 860
TraceConfigFileName 860
TraceDefaultFileName 860
TraceFileAppend 862
TraceFileHistory 862
TraceFileSize 862
TraceRuleLevel 861
TraceRuleToXact 862
TraceSrc 860
view switching, enabling 473

viewing
service component information 738
service components with find 737
Target Availability monitor

Tivoli 303
870
U
UNIX
permissions required to start cells 779
root user permissions 779
starting cells 779
stopping cells 779
views, changing automatically in the operations
console 473
X
xact transaction file 798
Windows
starting a cell with services 781
starting cells 780
starting cells with net start 781
stopping a cell with mkill command 780
stopping a cell with services 780
stopping cells 780
stopping cells with net stop 780
stopping with mkill 780
Index
871
872
49532
*166631 *

BMC ProactiveNet Administrator Guide

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

BMC ProactiveNet Administrator Guide

Cargado por

Copyright:

Formatos disponibles

BMC ProactiveNet

Contacting BMC Software

United States and Canada

BMC SOFTWARE INC

1 713 918 8800

1 713 918 8000

Outside United States and Canada

+01 713 918 8800

+01 713 918 8000

Copyright 2009 - 2010 BMC Software, Inc.

Restricted rights legend

find the most current information about BMC products

search a database for problems similar to yours and possible solutions

order or download product documentation

download products and maintenance

report a problem or ask a question

subscribe to receive proactive e-mail alerts

Support by telephone or e-mail

Before contacting BMC

operating system and environment information

sequence of events leading to the problem

commands and options that you used

product error messages

License key and password information