BMC ProactiveNet

BMC ProactiveNet Getting Started Guide
Supporting
BMC ProactiveNet version 8.6.01
April 2011
www.bmc.com
Contacting BMC Software

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

Address BMC SOFTWARE INC 2101 CITYWEST BLVD HOUSTON TX 77042-2827 USA Telephone 713 918 8800 or 800 841 2031 Fax 713 918 8000
Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000
Copyright 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 is the trademark or registered trademark of International Business Machines Corporation in the United States, other countries, or both. IT Infrastructure Library is a registered trademark of the Office of Government Commerce and is used here by BMC Software, Inc., under license from and with the permission of OGC. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office, and is used here by BMC Software, Inc., under license from and with the permission of OGC. 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. Sybase is the 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. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.
Customer support
You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, see Before contacting BMC.
Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support. From this website, you can
s s s s s s s s
read overviews about support services and programs that BMC offers find the most current information about BMC products search a database for issues similar to yours and possible solutions order or download product documentation download products and maintenance report an issue or ask a question subscribe to receive proactive e-mail alerts when new product notices are released find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers
Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to customer_support@bmc.com. (In the subject line, enter SupID:<yourSupportContractID>, such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.
Before contacting BMC

Have the following information available so that Customer Support can begin working on your issue immediately:
s
product information product name product version (release number) license number and password (trial or permanent)
operating system and environment information machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level
s s s
sequence of events leading to the issue commands and options that you used messages received (and the time and date that you received them) product error messages messages from the operating system, such as file system full messages from related software
License key and password information

If you have questions about your license key or password, use one of the following methods to get assistance:
s s
Send an e-mail message to customer_support@bmc.com. Use the Customer Support website at http://www.bmc.com/support.
Contents
Chapter 1 BMC ProactiveNet overview 11 11 11 12 13 14 15 15 16 17 17 17 18 18 18 18 19 19 19 20 20 20 21 21 21 21 22 22 22 23 23 25 25 27 27 28 28
5
What is BMC ProactiveNet? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC ProactiveNet components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC ProactiveNet Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC ProactiveNet Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC ProactiveNet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Knowledge modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC ProactiveNet default monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC ProactiveNet Performance Management Package Installation Repository and installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC ProactiveNet Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC ProactiveNet Operations Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC ProactiveNet SLO Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC ProactiveNet Integration Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Impact Model Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Impact Event Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC ProactiveNet CMDB extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC ProactiveNet Performance Management Web Services . . . . . . . . . . . . . . . . BMC ProactiveNet Data Collection Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC ProactiveNet integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Atrium Configuration Management Database (CMDB) . . . . . . . . . . . . . . . . BMC ProactiveNet Performance Management Reporting . . . . . . . . . . . . . . . . . . . BMC Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Transaction Management Application Response Time (BMC TM ART) . . BMC Atrium Orchestrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC BladeLogic Server Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC IT Service Management (BMC ITSM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Atrium Discovery Dependency Mapping (BMC Atrium Discovery) . . . . . BMC ProactiveNet Application Diagnostics (BMC AppSight integration) . . . . . BMC ProactiveNet functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event and service management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2 Preparing for your installation
Installation workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for installations on all operating systems. . . . . . . . . . . . . . . . . . . . . Requirements for installations on Microsoft Windows computers . . . . . . . . . . . .
Contents
Requirements for installations on UNIX computers. . . . . . . . . . . . . . . . . . . . . . . . . 29 Pre-installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Pre-installation tasks for all operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Pre-installation tasks for Windows environments . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Pre-installation tasks for UNIX environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Preparing to install BMC ProactiveNet in high-availability mode . . . . . . . . . . . . . . . . 37 Requirements for installing BMC ProactiveNet in high-availability mode on Microsoft Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Requirements for installing BMC ProactiveNet in high-availability mode on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Ports used by BMC ProactiveNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Preparing to install BMC ProactiveNet Performance Management with Oracle database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Creating Oracle database instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Using BMC provided scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Hardware and software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Chapter 3 Preparing for BMC Atrium CMDB integration 51
Installation scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Integrating BMC Atrium CMDB with BMC ProactiveNet . . . . . . . . . . . . . . . . . . . 51 Integrating with BMC Atrium CMDB in a cluster environment . . . . . . . . . . . . . . 53 Installing BMC ProactiveNet CMDB Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Restarting Apache Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Installing required modules and hotfixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Validating BMC Atrium CMDB elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Chapter 4 Installing the BMC ProactiveNet Server on Microsoft Windows for the first time 59
Installing BMC ProactiveNet Server on Microsoft Windows . . . . . . . . . . . . . . . . . . . . 59 Installing BMC ProactiveNet Performance Management with Oracle. . . . . . . . . . . . . 65 Applying licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Chapter 5 Installing remote BMC ProactiveNet Agent(s) on Microsoft Windows 69
Best practices for installing BMC ProactiveNet Agents . . . . . . . . . . . . . . . . . . . . . . 69 Installing multiple BMC ProactiveNet Agents on a single computer . . . . . . . . . . 73 Verifying that the BMC ProactiveNet Agent is running. . . . . . . . . . . . . . . . . . . . . . . . . 74 Chapter 6 Installing the BMC ProactiveNet Server on Solaris for the first time 75
Special considerations for installing on Solaris 10 . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Installing the BMC ProactiveNet Server on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . 76 Installing BMC ProactiveNet Performance Management with Oracle. . . . . . . . . . . . . 81 Obtaining the fingerprint for the BMC ProactiveNet Server . . . . . . . . . . . . . . . . . . . . . 83 Applying licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
BMC ProactiveNet Deployment Guide
Chapter 7
Installing remote BMC ProactiveNet Agent(s) on UNIX-based computers for the first time 87 87 88 89 92 93 93 95 95 96 97 98 99
Best practices for installing BMC ProactiveNet Agents . . . . . . . . . . . . . . . . . . . . . . . . . Installing a BMC ProactiveNet Agent on a UNIX-based computer for the first time Installing the BMC ProactiveNet Agent remotely from the BMC ProactiveNet Operations Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing multiple BMC ProactiveNet Agents on single computer . . . . . . . . . . . Finishing the installation process on the AIX platform . . . . . . . . . . . . . . . . . . . . . . . . . Verifying that the BMC ProactiveNet Agent is running . . . . . . . . . . . . . . . . . . . . . . . . Chapter 8 Installing the Administration Console on remote computers
Installing the BMC ProactiveNet Administration Console on Microsoft Windows . Launching the Administration Console on Microsoft Windows computers . . . . Installing the BMC ProactiveNet Administration Console on Solaris . . . . . . . . . . . . . Launching the Administration Console on Solaris. . . . . . . . . . . . . . . . . . . . . . . . . . Installing multiple Administration Consoles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 9 Unattended installation
101 101 102 105 106 107 107 108 108 109 111 111 112 114 115 116 120 123
Installing the BMC ProactiveNet Server on Microsoft Windows . . . . . . . . . . . . . . . . Encrypting passwords in the options file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the BMC ProactiveNet Agent on Microsoft Windows . . . . . . . . . . . . . . . . Installing BMC ProactiveNet Server on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing BMC ProactiveNet Agent on UNIX based systems. . . . . . . . . . . . . . . . . . . Uninstalling the BMC ProactiveNet Server on Microsoft Windows . . . . . . . . . . . . . Uninstalling the BMC ProactiveNet Agent on Microsoft Windows . . . . . . . . . . . . . Uninstalling the BMC ProactiveNet Server on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling the BMC ProactiveNet Agent on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 10 Installing BMC ProactiveNet in high-availability mode on Windows
Installing BMC ProactiveNet Server on a primary node . . . . . . . . . . . . . . . . . . . . . . . Installing BMC ProactiveNet Performance Management with Oracle . . . . . . . . . . . Installing BMC ProactiveNet Server on a standby node . . . . . . . . . . . . . . . . . . . . . . . Creating dependencies for BMC ProactiveNet Server cluster resource . . . . . . . . . . Installing the BMC ProactiveNet Agent in high-availability mode on Microsoft Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating dependencies for a BMC ProactiveNet Agent cluster resource . . . . . . . . . Chapter 11 Installing BMC ProactiveNet in high-availability mode on Solaris
High-availability workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Installing BMC ProactiveNet in high-availability mode on Solaris . . . . . . . . . . . . . . 125 Chapter 12 Introduction to the BMC ProactiveNet interfaces 127
Deciding which interface to use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Administering BMC ProactiveNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 BMC ProactiveNet profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Contents
Admin profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 User profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 BMC ProactiveNet Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Connecting the BMC ProactiveNet Administration Console to the BMC ProactiveNet Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Launching the BMC ProactiveNet Administration Console . . . . . . . . . . . . . . . . . 129 Logging out of and into the BMC ProactiveNet Server from the BMC ProactiveNet Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Navigating the BMC ProactiveNet Administration Console . . . . . . . . . . . . . . . . 131 BMC ProactiveNet Operations Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Launching the BMC ProactiveNet Operations Console. . . . . . . . . . . . . . . . . . . . . 133 Navigating the BMC ProactiveNet Operations Console . . . . . . . . . . . . . . . . . . . . 133 Operations Console views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Accessing the Command Line Interface (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Accessing online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Chapter 13 Post-installation tasks 141
Changing the BMC ProactiveNet Console passwords . . . . . . . . . . . . . . . . . . . . . . . . . 141 Changing your BMC ProactiveNet Administration Console password . . . . . . . 141 Changing your BMC ProactiveNet Operations Console password . . . . . . . . . . . 142 Changing the Apache HTTP port number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Configuring BMC ProactiveNet Server to run as a non-root user after installation on Solaris. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Configuring the BMC ProactiveNet Server for 256-bit SSL encryption . . . . . . . . . . . 143 Configuring BMC ProactiveNet Event Adapters to start collecting events. . . . . . . . 145 Managing the Oracle Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Oracle database backup and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Configuring BMC Atrium CMDB integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Configuring remote cells for viewing in the Operations Console. . . . . . . . . . . . . . . . 149 Registering remote cells in the Administration console . . . . . . . . . . . . . . . . . . . . . . . . 150 Configuring cell connection properties to the BMC ProactiveNet Server . . . . . . . . . 151 Specifying ports in cell connection properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Setting BMC ProactiveNet Server connection properties . . . . . . . . . . . . . . . . . . . 153 Logging out of and into the BMC ProactiveNet Server from the BMC ProactiveNet Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Adding Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Getting started with devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Summary of devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Using device aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Avoiding duplicate devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Creating a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Selecting monitors for the device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Stopping the BMC ProactiveNet Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Starting the BMC ProactiveNet Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Checking the status of the BMC ProactiveNet Server. . . . . . . . . . . . . . . . . . . . . . . . . . 165 Enabling and disabling Integration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Enabling the Integration Service to gather data from products that integrate with BMC ProactiveNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
8 BMC ProactiveNet Deployment Guide
Disabling the Integration Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying a particular IP address for the BMC ProactiveNet Agent . . . . . . . . . . . . Changing the BMC ProactiveNet Server IP address. . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring e-mail settings to receive alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 14 Chapter 15 Creating and installing component packages Configuring and using BMC ProactiveNet in high-availability mode
167 168 168 168 170 170 171 177 177 178 179 180 183 187 187 187 188 188 191
Configuring the BMC ProactiveNet Server in Sun cluster. . . . . . . . . . . . . . . . . . . . . . Creating the BMC ProactiveNet resource type . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the resource type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating the resource group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customizing the scripts to achieve BMC ProactiveNet application highavailability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running BMC ProactiveNet in high-availability mode . . . . . . . . . . . . . . . . . . . . . . . . Bringing a resource group online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually switching the BMC ProactiveNet application to the standby node . . . . . Disabling failover for BMC ProactiveNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring high-availability remote cells for viewing in the Operations Console Chapter 16 Uninstalling BMC ProactiveNet
Uninstalling the BMC ProactiveNet Server on Windows . . . . . . . . . . . . . . . . . . . . . . 191 Uninstalling the BMC ProactiveNet Server with Oracle backend . . . . . . . . . . . . . . . 192 Uninstalling the BMC ProactiveNet Agent on Windows . . . . . . . . . . . . . . . . . . . . . . 192 Uninstalling the BMC ProactiveNet Server on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . 193 Uninstalling the BMC ProactiveNet Agent on UNIX-based operating systems . . . 193 Uninstalling the BMC ProactiveNet Server on a cluster in high-availability mode on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Uninstalling the BMC ProactiveNet Agent on a cluster in high-availability mode on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Uninstalling the BMC ProactiveNet Server on a cluster in high-availability mode on UNIX- based operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Uninstalling the BMC ProactiveNet Administration Console on UNIX-based operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Removing the Oracle database objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Removing the schema from the Oracle database . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Appendix A Reconnecting to the BMC ProactiveNet database 199
Contents
10
BMC ProactiveNet Deployment Guide
Chapter
BMC ProactiveNet overview

This chapter contains an overview of the components that comprise BMC ProactiveNet and other BMC products that can be used in conjunction with BMC ProactiveNet.
What is BMC ProactiveNet?

BMC ProactiveNet is an integrated platform that combines event management and data analytics (including baselines, abnormality detection, and Root Cause Analysis algorithms) in a single seamless solution. Event management provides a real-time solution for proactive detection and resolution of IT problems before they have an impact on critical IT systems. Data analytics uses metrics data collected from the infrastructure to detect abnormalities, predict outages, and provide deep diagnostics information. The goal of data analytics is to provide a research facility to better understand, tune, and modify the selected area.
BMC ProactiveNet components

The following sections describe the components that comprise BMC ProactiveNet.
Chapter 1
11
BMC ProactiveNet Server
BMC ProactiveNet Server

The BMC ProactiveNet Server is the core BMC ProactiveNet component that receives events and data from various sources, including:
s s s s
BMC ProactiveNet Integration Services BMC PATROL Agents BMC ProactiveNet Agents BMC Impact Event Adapters
Once the BMC ProactiveNet Server has collected this information, it processes events and data using a powerful analytics engine and additional event processing instructions stored in its knowledge base. The BMC ProactiveNet Server can also leverage a service model (published from BMC Atrium CMDB or other sources) to put data and events in a business context. The BMC ProactiveNet Server is responsible for the configuring and controlling data and event collection, for storing the data collected, and presenting that data in the form of graphs, reports, views, and events. The components that comprise the BMC ProactiveNet server include:
s
BMC Service Impact Manager cellreceives the events from other cells and/or adapters. The contents of this cell are displayed in the Service Impact Graph. BMC Administrator cell - an event processing engine that collects, processes, and stores events. Each cell uses the information in its associated Knowledge Base to identify the types of events to accept and how to process and distribute them. The registrations happening in Infrastructure Management will send a registration event to the Admin Cell.
BMC ProactiveNet databasea Sybase ASA Database that stores objects collected by the BMC ProactiveNet server such as devices, instances, monitor types, configuration, and data BMC ProactiveNet agenta local agent dedicated to monitoring the health of the BM ProactiveNet server to ensure that the BMC ProactiveNet server runs at peak performance BMC ProactiveNet monitorsmonitors installed with BMC ProactiveNet server that specifically monitor the health of the BMC ProactiveNet server
12
BMC ProactiveNet Database
Components installed with BMC ProactiveNet Server include the BMC ProactiveNet Operations Console, the BMC ProactiveNet Administration Console, the BMC ProactiveNet SLO Console, and the BMC ProactiveNet Database. When you install the BMC ProactiveNet Server, you also have the option to install the BMC ProactiveNet Performance Management Installation Package Repository.
BMC ProactiveNet Database

BMC ProactiveNet Performance Management supports the following databases:
s
Sybase ASA database: This database is installed automatically when you install the BMC ProactiveNet Server. You do not need a separate license to install or operate this database. Oracle database: You must have a dedicated Oracle database instance for BMC ProactiveNet Performance Management. You must have Oracle installed with a valid license, on a machine that does not have the BMC ProactiveNet Server installed. For more information on setting up Oracle as the backend database, contact http://www.bmc.com/support. For an overview of the Oracle database, refer to Oracle database overview on page 13.
The BMC ProactiveNet Database acts as a central repository for all the monitor configuration and statistical data, including the following:
s s s s
Configuration information such as users, device, agent, monitors, and groups. Service-level objects (SLOs) and report data. Performance data such as raw performance data and event information. Processed data such as rate and baseline data.
Oracle database overview

BMC ProactiveNet Performance Management version 8.6.01 now supports Oracle as the backend database and supports the following:
s s s
Oracle Database 11g R2 Standard/Enterprise Edition Release 11.2.0.2.0. Standalone or RAC Oracle Scripts for tuning Oracle system parameters, creating tablespace and users in BMC ProactiveNet Performance Management.
Chapter 1
13
BMC ProactiveNet Agent
Deployment scenarios
The following scenarios help you in deploying BMC ProactiveNet Performance Management with Oracle:
s
Standalone installation of BMC ProactiveNet Performance Management with standalone installation of Oracle on a remote host. BMC ProactiveNet Performance Management installation in high-availability mode with standalone installation of Oracle on a remote host.
Recommendations
BMC recommends the following while deploying BMC ProactiveNet Performance Management with Oracle:
s s
Install the BMC ProactiveNet Server and Oracle Server on different machines. The BMC ProactiveNet Server and Oracle Server should be on the same subnetwork.
For the Oracle system requirements, refer to the BMC ProactiveNet version 8.6.01 Compatibility and Support Matrix.
BMC ProactiveNet Agent

Two types of BMC ProactiveNet Agents are included in the BMC ProactiveNet product.:
s
A local BMC ProactiveNet Agent monitors the health of BMC ProactiveNet Server to ensure that the server runs at peak performance. The local agent is installed with BMC ProactiveNet Server. Remote BMC ProactiveNet Agents collect device-specific data such as CPU usage, memory usage, and other data specific to the host operating system. The agents enable BMC ProactiveNet Server to remotely gather statistical data from all supported operating systems. Install the remote agents on each network element in the enterprise that you want to monitor. BMC Software recommends that you install remote agents and BMC ProactiveNet Server on separate computers. Remote BMC ProactiveNet Agents are also installed as part of BMC ProactiveNet Data Collection Host.
14
BMC PATROL Agent
BMC PATROL Agent

BMC PATROL Agent is a core component of the BMC ProactiveNet architecture that is used to monitor devices locally or remotely. BMC PATROL Agents load information from knowledge modules (KMs), gather statistics, and send data and events to BMC ProactiveNet Server. Using data from a BMC PATROL Knowledge Module, BMC PATROL Agent can:
s s s s s
Detect the presence and status of an application instance (discovery) Collect data on any measurable aspect of an application instance (parameters) Interpret data by using defined rules Store collected data in local files (history) Implement predefined actions to correct abnormal conditions (recovery actions)
Knowledge modules
Knowledge modules (KMs) are customized objects that typically manage and monitor elements of your server environment. A KM is a set of instructions that BMC PATROL Agent uses to monitor objects in your environment. BMC ProactiveNet provides an extensive set of out-of the-box knowledge modules that collect performance data from applications, databases, servers, hypervisors, cloud components, middleware, hardware, and storage. A set of knowledge modules is provided in the BMC ProactiveNet Performance Management Installation Package Repository which can be installed with the BMC ProactiveNet Server. For more information about the KMs included with BMC ProactiveNet and the BMC Performance Management Installation Package Repository, see Chapter 14, Creating and installing component packages. For specific information about available knowledge modules and their capabilities, see the getting started guides and user guides for each knowledge module.
Chapter 1
15
BMC ProactiveNet default monitors
BMC ProactiveNet default monitors

BMC ProactiveNet includes built-in default monitors. These monitors can either be Windows or Solaris based monitors. The following monitors indicate BMC ProactiveNet Servers overall health and are automatically set up during BMC ProactiveNet Server installation:
s s s s s s s
Agent Status monitor SolarisTM File System monitor Solaris Process monitor Solaris System monitor Sybase ASA Intelliscope monitor Sybase Query Web URL
NOTE
If you have an Oracle backend database, Oracle based monitors will be created instead of Sybase monitors.
The following monitors are automatically set up while adding or installing a BMC ProactiveNet remote agent:
s s s s
Agent Status monitor Agent System monitor Agent TCP monitor Ping Monitor
If BMC ProactiveNet Performance Management is installed with Oracle backend, the following monitors are set up. It does not create Sybase ASA Intelliscope monitor and Sybase Query monitors.
s s
Oracle intellisocpe Oracle Query monitors
For more information about BMC ProactiveNet monitors, see the BMC ProactiveNet Data Adapter and Monitor Guide.
16
BMC ProactiveNet Performance Management Package Installation Repository and installer
BMC ProactiveNet Performance Management Package Installation Repository and installer

When you install the BMC ProactiveNet Server, you have the option to install the BMC ProactiveNet Performance Management Package Installation Repository. The Package Installation Repository includes the current versions of BMC components that are able to be used with BMC ProactiveNet, such as the BMC PATROL Knowledge Modules and BMC PATROL Agents. From the BMC ProactiveNet Operations Console, an administrator can select the components from the repository that he or she wants to install on the same computer(s) and package them together so that they can be installed simultaneously using the integrated package installer. For more information, see Chapter 14, Creating and installing component packages.
BMC ProactiveNet Administration Console

The BMC ProactiveNet Administration Console allows you to modify and manage the BMC ProactiveNet Server and the BMC ProactiveNet Agent network management areas by adding or deleting users, groups, monitored devices, applications, and services, or changing event notifications and thresholds. You can also manage supported infrastructure components and service models. The Administration Console also provides access to event management policies, the dynamic data editor, and the services editor. For more information about the BMC ProactiveNet Administration Console, see the BMC ProactiveNet Administrator Guide.
BMC ProactiveNet Operations Console

The BMC ProactiveNet Operations Console is a Web-based application that provides options to navigate through BMC ProactiveNet and view all of the information collected and computed by the BMC ProactiveNet Server related to events, views, and graphs. For more information, see the BMC ProactiveNet User Guide.
Chapter 1
17
BMC ProactiveNet SLO Console
BMC ProactiveNet SLO Console

The BMC ProactiveNet SLO Console displays an integrated view of all Service Level Objectives (SLOs). These business views help define, measure, and track SLOs. SLO views complement existing infrastructure-centric application management solutions. SLO business views help define, measure, and track SLOs. With new business views, business structures are available in a top-down hierarchical view that delivers near real-time service level views of application and service metrics. This view provides valuable information on performance status from an end users perspective for each business unit and SLO compliance. SLO views also represent application performance levels and service levels committed to within the organization. The views represent application performance metrics in a way that relates the IT and line of business teams as a close working unit on which the company depends. For more information, see the BMC ProactiveNet User Guide.
BMC ProactiveNet Integration Service

The remote BMC ProactiveNet Agent uses the BMC ProactiveNet Integration Service to collect data from BMC PATROL and external products, such as, HP Operations Manager and IBM Tivoli Monitoring. For more information, see the BMC ProactiveNet Administrator Guide.
BMC Impact Model Designer

BMC Impact Model Designer is a plug-in installed with the BMC ProactiveNet CMDB Extensions that allows BMC ProactiveNet to use the BMC Atrium Core Console to design and create service models. For more information, see the BMC ProactiveNet Service Modeling and Publishing Guide.
BMC Impact Event Adapters

Each BMC ProactiveNet Agent hosts the BMC Impact Event Adapters. BMC Impact Event Adapters convert data from event sources into events that can be processed by the BMC ProactiveNet Server.
18
BMC ProactiveNet CMDB extensions
The BMC Impact Event Adapters can collect source events from
s s s s
operating system and application log files SNMP type 1 and type 2 traps message output from command line interfaces the Windows Event Log
For more information, see the BMC Impact Event Adapters User Guide.
BMC ProactiveNet CMDB extensions

The BMC ProactiveNet CMDB extensions, modules, and hotfixes are necessary components to integrate BMC ProactiveNet with the BMC Atrium CMDB. With integration, the BMC Atrium CMDB can be used for service modeling. The BMC ProactiveNet extensions allow the publishing server to be notified when changes have been made to the service model in the BMC Atrium CMDB. The publishing server can apply those changes immediately in the BMC ProactiveNet Server. For more information, see the BMC ProactiveNet Administrator Guide.
BMC ProactiveNet Performance Management Web Services

BMC ProactiveNet Performance Management Web Services is an integration application that enables Web Services type communications between external programs and BMC ProactiveNet components. For more information, see the BMC ProactiveNet Performance Management Web Services Getting Started Guide.
BMC ProactiveNet Data Collection Host

BMC ProactiveNet Data Collection Host is a dedicated computer used to collect metric data from virtual machines, and to send the data to BMC ProactiveNet Server for analysis. Collected data includes CPU usage, memory usage, and data that is specific to the host operating system.
Chapter 1
19
BMC ProactiveNet integrations
The data collection host is comprised of the following components:

s s s s
Remote BMC ProactiveNet Agent BMC ProactiveNet Integration Service BMC PATROL Agents BMC Performance Manager for Virtual Servers Knowledge Module
For more information about BMC Performance Manager components, see BMC PATROL for Virtual Servers Getting Started Guide. For installation instructions, see BMC ProactiveNet Deployment Guide.
BMC ProactiveNet integrations

The following BMC products integrate with and enhance the functionality of BMC ProactiveNet.
BMC Atrium Configuration Management Database (CMDB)

BMC Atrium CMDB is a repository that stores configuration items (CIs) available in an enterprise. You can import the CIs from the BMC Atrium CMDB to define service model objects that you want to monitor in BMC ProactiveNet. BMC ProactiveNet leverages the service relationship information from the CIs in BMC Atrium CMDB that are monitored by BMC ProactiveNet to produce better results for Probable Cause Analysis.
BMC ProactiveNet Performance Management Reporting

BMC ProactiveNet Performance Management Reporting is an advanced reporting platform that uses SAP BusinessObjects Enterprise Professional as the host for BMC ProactiveNet Performance Management system universes and the Reporting Engine that administers and publishes the reports. ProactiveNet Performance Management Reporting contains event report and impact report templates and also allows you to create ad hoc reports.
20
BMC Portal
BMC Portal
BMC Portal provides a common Web-based interface for the BMC Performance Manager Portal software module. BMC Performance Manager for Portal extends the features of the BMC Portal by providing real time monitoring and management functions of agentless and BMC PATROL agent-based systems. BMC ProactiveNet can be configured to synchronize this data to monitor the IT devices effectively.
BMC Transaction Management Application Response Time (BMC TM ART)

BMC TM ART is a monitoring product that lets IT administrators manage the performance and reliability of applications and measure the health of these applications based on end-user experience metrics such as availability, accuracy, and performance. 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.
BMC Atrium Orchestrator

BMC Atrium Orchestrator is a suite of components that empowers operators with process-based control. With its workflow-based process templates, customers can rapidly adapt and deploy functional design to ensure consistent and appropriate, policy-based response across the enterprise. The BMC Triage and Remediation Solution is an integration of BMC Atrium Orchestrator and BMC ProactiveNet Performance Management.
BMC BladeLogic Server Automation

BMC BladeLogic Server Automation Suite helps manage, control, and enforce configuration changes in data centers. With the integration of BMC BladeLogic, BMC ProactiveNet Performance Management retrieves change information from BMC BladeLogic for Probable Cause Analysis (PCA) candidates. BMC BladeLogic can also deploy a BMC ProactiveNet Agent as part of the batch provisioning job for a newly provisioned server.
Chapter 1
21
BMC IT Service Management (BMC ITSM)
BMC BladeLogic Server Automation Suite is also used to deploy the components of BMC ProactiveNet Data Collection Host. Each component (BMC ProactiveNet Agent and the integration service, BMC PATROL Agent and the knowledge module) and its configuration is wrapped by a BMC BladeLogic monitoring infrastructure package. The packages are loaded onto the BMC BladeLogic Application Server and deployed onto the data collection host.
BMC IT Service Management (BMC ITSM)

BMC ITSM reduces complexity and facilitates the efficiency and integration of customer support, change management, and asset management. It applies a repeatable process for production changes to improve the stability of business services while managing required changes. It streamlines the processes around IT service desk, asset management, and change management operations. The Integration for BMC Remedy Service Desk (IBRSD) component adds business context to incidents by enabling bidirectional flow of information between BMC ProactiveNet and BMC Remedy Service Desk. BMC ProactiveNet Performance Management provides a Triage and Remediation Solution by integrating BMC Atrium Orchestrator and BMC ITSM.
BMC Atrium Discovery Dependency Mapping (BMC Atrium Discovery)

BMC Atrium Discovery and Dependency Mapping automates the process of populating BMC Atrium CMDB by exploring IT systems to identify hardware and software, and then creating CIs and relationships from the discovered data.
BMC ProactiveNet Application Diagnostics (BMC AppSight integration)

BMC ProactiveNet Application Diagnostics pinpoints, captures, and communicates the root cause of application problems for a specific transaction, without the need to recreate the problem or replicate its environment in a lab. IT operations and application support staff can isolate the problems and route them to the appropriate domain expert for rapid resolution.
22
BMC ProactiveNet functionality
BMC ProactiveNet Application Diagnostics agents are lightweight software agents 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.
BMC ProactiveNet functionality

Event and service management
Event and service management functionality in BMC ProactiveNet provides solutions for proactive detection and resolution of IT problems before they have an impact on critical IT systems. It provides a view of the operational state of the IT infrastructure. If SIEM is implemented, events that occur in the IT environment are processed by the event manager and reflected in the service model. For more information on the new features, refer to the BMC ProactiveNet Release Notes.
Chapter 1
23
Event and service management
24
Chapter
Preparing for your installation

This chapter contains information about requirements that must be in place before beginning the installation, pre-installation tasks that you must perform, and other considerations. If you are upgrading from a previous BMC ProactiveNet or BMC Impact Solutions installation, see the BMC ProactiveNet Upgrade Guide.
Installation workflow
Figure 1 on page 26 provides an overview of the tasks that you must perform to install the BMC ProactiveNet components on Microsoft Windows or UNIX-based computers.
Chapter 2
25
Installation workflow
Figure 1
BMC ProactiveNet installation workflow
Installation begins.
Plan your installations.
Plan your BMC ProactiveNet deployment. For details, see the BMC ProactiveNet Deployment Guide.BMC ProactiveNet Deployment Guide.
Prepare host computers for installation.
Review system requirements and prerequisites and perform preinstallation tasks. For hardware and software requirements, see the BMC ProactiveNet version 8.6.01 Compatibility and Support Matrix document. For prerequisites and preinstallation tasks, see Installation requirements on page 27 and Pre-installation tasks on page 29.
Install the BMC ProactiveNet CMDB Extensions.
Do you want to integrate with the BMC Atrium CMDB?
yes
Using the BMC ProactiveNet provided utility, install the BMC ProactiveNet CMDB Extensions, modules, and hotfixes on the computer where the BMC Atrium CMDB is installed. For details, see Chapter 3, Preparing for BMC Atrium CMDB integration.
no
Install the BMC ProactiveNet Server.
Using the BMC ProactiveNet installation program, install the BMC ProactiveNet Server, local agent, and integration service on the server target computer. For details, see Chapter 4, Installing BMC ProactiveNet Server on Microsoft Windows or Chapter 6, Installing the BMC ProactiveNet Server on Solaris for the first time.
Install the BMC ProactiveNet Agent on remote computers.
Using the BMC ProactiveNet installation program, install the BMC ProactiveNet Agent on one or more computers. For details, see Chapter 5, Installing remote BMC ProactiveNet Agent(s) on Microsoft Windows or Chapter 7, Installing remote BMC ProactiveNet Agent(s) on UNIXbased computers for the first time.
Install the BMC ProactiveNet Administration Console.
Using the BMC ProactiveNet installation program, install the BMC ProactiveNet Administration Console on one or more computers. For details, see Chapter 8, Installing the Administration Console on remote computers.
Installation ends.
26
Installation types
Installation types
You can perform the following types of installations for the BMC ProactiveNet Server and the BMC ProactiveNet Agent:
s
first-time installation; see the following chapters: Chapter 4, Installing the BMC ProactiveNet Server on Microsoft Windows for the first time. Chapter 5, Installing remote BMC ProactiveNet Agent(s) on Microsoft Windows Chapter 6, Installing the BMC ProactiveNet Server on Solaris for the first time Chapter 7, Installing remote BMC ProactiveNet Agent(s) on UNIX-based computers for the first time Chapter 8, Installing the Administration Console on remote computers
unattended installation of BMC ProactiveNet; see Chapter 9, Unattended installation. high-availability installation; see the appropriate chapter for your operating system: Chapter 10, Installing BMC ProactiveNet in high-availability mode on Windows Chapter 11, Installing BMC ProactiveNet in high-availability mode on Solaris
If you are upgrading from BMC Impact Solutions or from a previous version of BMC ProactiveNet, see the BMC ProactiveNet Upgrade Guide.
Installation requirements
Ensure that the target computers for BMC Proactive meet or exceed the system requirements listed in the BMC ProactiveNet version 8.6.01 Compatibility and Support Matrix document and in the following sections.
Chapter 2
27
Requirements for installations on all operating systems
Requirements for installations on all operating systems

In addition to meeting the system requirements in the BMC ProactiveNet version 8.6.01 Compatibility and Support Matrix document, ensure that all your target computers meet the following requirements.
s
Ensure that port 80 is available for installing the Apache web server. If any other application is using the port, change the port allocation to make the port 80 available for BMC ProactiveNet installation. On the system where you want to host the BMC ProactiveNet Server or agent, verify the TCP control port (port 80) availability by running the following command from a command line:
netstat -a | findstr "LISTENING" | findstr "80"
Once BMC ProactiveNet has been installed, you can change the port for the Apache web server to free port 80 for use by your other application. For instructions, see Changing the Apache HTTP port number on page 142.
s
BMC Software recommends that you install BMC ProactiveNet from a local copy of the installation image and not from a network drive. Installing from a network drive can cause delays in completing the installation. The installation directory name cannot contain spaces. For successful installation, ensure that the Host name does not contain an underscore (_).
Requirements for installations on Microsoft Windows computers

s
Ensure that the user running the installation program has administrator rights and permissions and is a member of the Administrators group on the target computer. Ensure that the target computer has the most recent patch level for supported Windows operating systems. If it does not, use Microsoft Update (or Windows Update) to update it. For supported versions, see the BMC ProactiveNet version 8.6.01 Compatibility and Support Matrix document. On Windows Server 2008, if you want users with administrator privileges (not the Administrator user) to access the BMC ProactiveNet Server after the installation, you must turn off the User Access Control (UAC) before you install the server. Do not install BMC ProactiveNet Server in a root directory (for example C:\ or D:\), on a shared drive, or in the Documents and Settings folder.
28
Requirements for installations on UNIX computers
Perl should not be installed on the target computer where BMC ProactiveNet Server is being installed. While installing BMC ProactiveNet on Microsoft Windows Operating System in European locales (French and German), ensure that you do not change the default localized Administrators group name. BMC ProactiveNet Performance Management installation works with only the default localized Administrators group names. For example:
s s s
English: Administrators German: Administratoren French: Administrateurs
Requirements for installations on UNIX computers

s
Ensure that the user running the installation program is root. Ensure that gzip is installed and present in the PATH environment variable. Ensure that you have created the destination directory for the installation. The installation script will not create this directory during installation.
WARNING
The directory where the BMC ProactiveNet Server is installed and all its parent directories must have 755 permissions and must be owned by root, as well as the other group. Without these permissions and ownership, you will not be able to log into the BMC ProactiveNet Server.
Do not install the BMC ProactiveNet Agent in the /usr directory.
Pre-installation tasks
To prepare your environment for the BMC ProctiveNet installation, you must perform certain tasks before you begin the installation. The following sections provide details about the tasks that you must perform.
Pre-installation tasks for all operating systems

s
Close all applications that are running.
Chapter 2
29
Pre-installation tasks for all operating systems
Disable any anti-virus software on each host computer on which you are installing a component or exclude the ProactiveNet installation directory from the virus scanning. Turn off the Windows Firewall and then the Windows Firewall service (services.msc), before launching the installation program.
NOTE
While you install or upgrade to BMC ProactiveNet Performance Management 8.6.01, connection to the remote desktop may be lost if the Windows Firewall service is brought down before bringing down the machine firewall.
If the Windows Firewall is disabled, enable the Windows Firewall from services.msc, set the service startup type to manual.
1 Start the Windows Firewall service. 2 Enter the following command to turn off the firewall:
For Windows 2008 R2:
netsh advfirewall set allprofiles state off
For Windows 2008:

netsh firewall set opmode mode = DISABLE
For Windows 2003:

Go to Start => Control Panel => Windows Firewall and select Off to turn off the
Firewall.
3 Stop the Windows Firewall service. 4 Begin your install or upgrade process. 5 Start the Windows Firewall service after the installation is complete. 6 Enter the following command to turn on the firewall after successful installation:
For Windows 2008 R2:
netsh advfirewall set allprofiles state on
For Windows 2008:

netsh firewall set opmode mode = ENABLE
30
Pre-installation tasks for Windows environments
For Windows 2003:

Go to Start => Control Panel => Windows Firewall and select On to turn on the
Firewall.
s
Disable the following programs on the target computer: virus scanning programs Virus scanners can block the SMTP port and lock files that the installation program needs to configure the mail server and perform the installation. You can enable the virus scanning programs after the installation is completed. firewall protection programs, such as McAfee Host Intrusion Prevention Service (HIPS) HIPS can block access to ports that are used by the installation program during installation and by the BMC ProactiveNet Server at runtime. You must leave HIPS disabled after the installation is completed. You must reboot the computer after you disable the service.
Where to go from here

Proceed to the pre-installation tasks specific to your operating system:
s
Microsoft Windows, see Pre-installation tasks for Windows environments on page 31 UNIX-based operating systems, see Pre-installation tasks for UNIX environments on page 34

Perform the following tasks before launching the BMC ProactiveNet installation program.
s
Clean your temporary directories. Start with the temporary folder in your home folder. Also clean the %Temp%, %Tmp% directories, and C:\WINNT\Temp or C:\Windows\Temp if present. You might not be able to delete all the files, but BMC recommends that you remove any files or directories that begin with ProactiveNet.
Chapter 2
31
If Terminal Services is enabled, configure it to save installation log files after the installation is complete; otherwise, the log files will be deleted. For more information, see Configuring Terminal Services to save the log files on page 32.
Configuring Terminal Services to save the log files

Terminal Services creates a temp directory for each user account, and the installation program creates log files in this directory. At the end of the session, Terminal Services deletes the temp directory and any files that it contains, including the installation log files. By using the Terminal Services configuration tool, you can change Terminal Services so that it saves the log files.
WARNING
If you do not configure Terminal Services to save the log files, the installation will fail.
To configure Terminal Services to save log files 1 Choose Start => Programs => Administrative Tools => Terminal Services
Configuration.
The Terminal Services Configuration/Server Settings tool is displayed.
2 Open the Server Settings folder. 3 In the Delete temporary folders on exit dialog box, choose No and click OK. 4 In the Use temporary folder per session dialog box, choose No and click OK. 5 Close the Terminal Services Configuration/Server Settings tool. 6 Open the Registry Editor and navigate to the following registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server
32
7 Verify that the following registry keys in the Terminal Server registry have the
appropriate settings:
Key DeleteTempDirsOnExit PerSessionTempDir FlatTempDir
a a
Type REG_DWORD REG_DWORD REG_SZ
Data value 0 0 1
This registry value exists only if flat temporary folders are enabled. If flat temporary folders are disabled, the FlatTempDir key is not present.
8 Reboot the computer. NOTE

BMC Software recommends that you retain the Terminal Services settings after installing BMC ProactiveNet. Retaining these Terminal Services settings will make it easier for you to upgrade to future versions of BMC ProactiveNet.
Checking the pre-installation requirements for Windows

When you start the BMC ProactiveNet Server installation, the installation program invokes a pre-installation utility that checks to ensure that the target computer is configured based on the recommended settings. The pre-installation utility checks the environment and reports a status of OK or Not OK for each configuration variable that it checks. For Windows, the following pre-install checks are run
Preinstallation check FirewallStatus UserRights OperatingSystemPatch RAM Hard Disk Space Description Determines whether or not the firewall service is running. The firewall should be turned off. Checks to determine if the user running the preinstallation utility is an administrator or part of the administrator group. Checks that the operating system patch (if any) is supported. Checks that the necessary amount of RAM is available. This check:
s s s s
obtains the list of drives obtains the list of quorum in case of cluster systems determines the disk space available for each of the drives identifies the drive (for example, during install, it will identify if it is a C or D drive)
ProcessorConfiguration PortAvailability
Checks that the processor configuration is supported. Checks that the required ports are available. For the list of ports required, see Ports used by BMC ProactiveNet on page 39.
Chapter 2
33
Pre-installation tasks for UNIX environments
Preinstallation check PageFileSize PrimaryInterface DNSConfiguration DefaultGateway FileSystem
Description Checks the page file size. Checks whether the NIC card is available. Confirms the IP address. Verifies that the default gateway is not blank. This check: identifies the file system (for example, on Windows it will say NTFS which is supported for Windows)
Disk Info
This check:
s s s s
obtains the list of drives obtains the list of quorum/common data disks if there is a cluster installation identifies the disk space available for each drive identifies the drive and file system, and checks for sufficient space
SystemRootFreeSpace RequiredFiles OSType TerminalServices
Checks that there is enough free disk space on the system boot drive. Looks for the presence of the MSVCP60.dll file, which is required for BMC ProactiveNet Server installation or upgrade. Determines if the system architecture is 32 or 64-bit. Checks to ensure that Terminal Services is configured to save log files. If the check fails, then follow the instructions in Configuring Terminal Services to save the log files on page 32. Checks to ensure that BMC Impact Explorer is not installed. Checks to see that the Task Scheduler service is running. If this is a cluster installation, the pre-installation utility checks to see if the following services are running on primary and standby nodes:
s s
BMCImpactExplorer TaskSchedulerService Cluster installation
ClusSvc W32Time
and ensures that the necessary cluster resources (Cluster Name, Cluster IP, Cluster Disk, and Quorum Disk in the same group) are available.
When the pre-installation check utility finishes, it creates a log file and saves it to your desktop. Review the log file to determine the success or failure of the pre-installation checks. Correct any errors before you launch the installation program. If the installation program encounters a failed check on a mandatory setting, it aborts the installation. To resolve any checks that display Not OK, see the Troubleshooting Guide.

Perform the following tasks before launching the BMC ProactiveNet installation program.
34
Clean your temporary directories. Start with the temporary folder in your home folder. You may not be able to delete all the files, but BMC recommends that you remove any files or directories that begin with ProactiveNet. Ensure that the nobody user account exists on the target computer. Disable X Windows access control by using the xhost command.
If the init file is not copied to the /etc/rc3.d directory, then the BMC ProactiveNet Agent corresponding to the init file is not listed as installed (in the list of existing BMC ProactiveNet Agent installations) during installation or upgrade of other agents. This is valid only for non-root users.
Checking the pre-installation requirements for Solaris

NOTE
The preinstallation check utility must be run from the directory that you created for BMC ProactiveNet installation. For information about this directory, see Requirements for installations on UNIX computers on page 29.
When you start the BMC ProactiveNet Server installation, the installation program invokes a pre-installation utility that checks to ensure that the target computer is configured based on the recommended settings. The pre-installation utility checks the environment and reports a status of OK or Not OK for each configuration variable that it checks. For Solaris, the following pre-installation checks are run
Check Operating System Zone on the System Description Checks if operating system is SunOS. Other UNIX operating systems are not supported for Server installation. The BMC ProactiveNet Server does not support installation on the global zone when there are subzones present. Installation is only supported on non-global full zones. Zones are supported from Solaris 10 and above, so the check for presence of zones is from Solaris 10 onwards. Ensures that the root partition is not 100% full. The installation may fail if there is insufficient space available in the root partition. Checks if BMC Impact Solutions components are present. If they are present, they must be uninstalled. Checks if the nobody user and nobody group exist in the system. Checks if the processor is 64-bit SPARC processor. Installation is not supported on 32bit SPARC processor. Checks if SunOS version is supported. Verifies the IP address.
Root [ / ] partition BEM Components User nobody exists in the system Operating System Processor Type Operating System Version IP address
Chapter 2
35
Check
Description
Host names resolved Checks if the resolved IP for the host name matches the IP address. IP against IP Loghost matching with host name DNS configuration Checks if loghost matches the host name Checks whether DNS is configured on system. This is required for DHCP support for ProactiveNet Server.
Permissions on /tmp Checks if /tmp directory has read, write and execute permission for owner, group and others. gzip Checks if the gzip compression utility is present in the /usr/bin/gzip or /bin/gzip or /usr/local/bin/gzip path. Gzip is no longer shipped with BMC ProactiveNet Server and is required for successful installation. Checks if the default gateway is configured. Checks if the computer has the minimum amount of swap space available. Checks if /usr/bin/umask value is 022. Checks if the computer has the minimum memory available. Checks whether Motif Runtime kit (SUNWmfrun), ICE components package (SUNWxwice) and X11 platform software (SUNWxwplt) installation components are installed. Check if all the required patches needed for the JRE on the particular OS are present.
Default router Available swap space File mode creation mask Total memory Motif Runtime kit
Patch level on the system
If the installation program encounters a failed check on a mandatory setting, it aborts the installation. To resolve any failed checks, review the prerequisites in this chapter to ensure that you have implemented all of them. If all the prerequisites have been implemented and the pre-installation check still fails for some checks, see the BMC ProactiveNet Troubleshooting Guide. If the required patches are not installed, you will get the following message.
s
Solaris Patch Needed
If your system requires a new patch, the text will be similar to the following: Checking patch level of the system...System does NOT have required level of patch. To run the ProactiveNet Server successfully on Solaris, install the required patches from the SunSolve website and reboot the system before installing the BMC ProactiveNet Server.
36
Preparing to install BMC ProactiveNet in high-availability mode
Preparing to install BMC ProactiveNet in highavailability mode

High availability is a backup operation that automatically switches to a standby database, server, or network if the primary system fails or is temporarily shut down for maintenance. High-availability is an important function because it provides faulttolerance to mission-critical systems that rely on consistent availability and performance. Unlike a single-server system, a high availability setup maintains your data and service availability, reducing or eliminating system downtime because of software or hardware failure. BMC ProactiveNet in high-availability mode consists of two servers with identical configurations. The first server is referred to as the primary node. The second server is referred to as the standby node. The two nodes share a logical IP address and cluster name. Both servers have access to a shared storage disk. The BMC ProactiveNet Server installation will be done with logical IP/host name enabled on the primary node. The BMC ProactiveNet Server should be installed on the shared storage disk. When the primary node is down the secondary node picks up the installation from the shared storage disk. Figure 2 High-availability system architecture
Chapter 2
37
Requirements for installing BMC ProactiveNet in high-availability mode on Microsoft Windows
Requirements for installing BMC ProactiveNet in highavailability mode on Microsoft Windows

Before you install BMC ProactiveNet in high-availability mode, make sure that you have two servers with the following configuration:
s
s s s s
identical operating system version (for example, Windows 2003 or Windows 2008 Enterprise Server) identical hardware configuration located in the same domain the logical IP is configured identical timestamp
NOTE
Time Services (a software available to maintain system timestamps) are required to maintain an identical timestamp between the primary and standby nodes. Windows 2003 and 2008 Enterprise Server Windows Time services maintain the identical timestamps between the computers. Ensure that this service is running before installing the BMC ProactiveNet in highavailability mode on Windows.
the Microsoft Clustering software should be installed on both nodes add the common logical IP/host name to be allocated to the two servers to the domain name service (DNS) map the disk to be shared between the two nodes with same directory name and/or directory path on both nodes the IP address, Disk, and Network Name should be present in the same group. BMC ProactiveNet Agent installation should be done on a clean computer.
s s
NOTE
In Windows 2008 Enterprise Server instead of logging into each node for installing the BMC ProactiveNet Server, login to the cluster and install the BMC ProactiveNet Server by moving to each node.
Requirements for installing BMC ProactiveNet in highavailability mode on UNIX

Before you install BMC ProactiveNet in high-availability mode, make sure that you have two servers with the following configuration:
s
Ensure that the Sun Cluster software is installed on all computers that will be hosting nodes.
38
Ports used by BMC ProactiveNet
Apply the latest patches for the Sun Cluster software. Both computers hosting the failover configuration should have the same logical name or shared IP address. Both nodes must be physically interconnected through a private network. Both nodes should have identical timestamp.
NOTE
On Solaris, the Sun cluster installer (if installed with scinstall), maintains an identical timestamp on the participant nodes. Enable this option while installing the Sun cluster. For more information, refer to http://docs.sun.com/app/docs/doc/8192969/cacbdgeg?l=en&a=view.
After installing and configuring the cluster, verify that the clusters are online. For detailed information about prerequisites, configuration, and cluster collections using the Sun Cluster software, see www.oracle.com.

The BMC ProactiveNet Server uses several configurable and non-configurable TCP control ports for its operations. Table 1 lists the ports that you can configure and provides the procedure to change port configuration in case of conflict with another application installed on the same host where you want to install BMC ProactiveNet.
Chapter 2
39
Table 1
Port 80
Required ports for BMC ProactiveNet (part 1 of 5)

Description To change the port... Apache HTTP port used Port 80 must be available during installation; however, the port number for Web browser requests can be changed after installation. 1. Open the appropriate files for your operating system:
s s
For UNIX: /usr/pw/apache/conf/httpd.conf. For Windows: pw\ApacheGroup\Apache\conf\httpd.conf and pw\pronto\conf\pronet.conf
2. Search for the string Port 80 and replace the value 80 with the desired port number. 3. Search for the string Listen 80 and replace the value 80 with the same port number provided in the previous step. 443 Apache HTTP port used for Web browser requests in HTTPS mode 1. Open the appropriate files for your operating system:
s s
For UNIX: /usr/pw/apache/conf/httpd.conf. For Microsoft Windows: pw\ApacheGroup\Apache\conf\httpd.conf and pw\pronto\conf\pronet.conf
2. Search for the string VirtualHost _default_:443 and replace the value 443 with the desired port number. 3. Search for the string Listen 443 and replace the value 443 with the same port number provided in the previous step. 1099 It is a non-configurable port. It is required to be open. Used by the Administrator Console to connect to the BMC ProactiveNet Server. Used by the JBoss server Used by the Central Administration cell to accept client connections. It is a non-configurable port. It is required to be open. 1. If the cell is running, stop the cell by entering the following command: mkill n cell_name. 2. Open the mcell.dir file and change the cell port to the new port number. You must change the cell port in the mcell.dir files of all components (cells, integrations, and so forth) that have to connect to that cell. 3. Restart the cell.
1100 1827
40
Table 1
Port 1828

Description Used by the cell to accept client connections. To change the port... 1. If the cell is running, stop the cell by entering the following command: mkill n cell_name. 2. Open the mcell.dir file and change the cell port to the new port number. You must change the cell port in the mcell.dir files of all components (cells, integrations, and so forth) that have to connect to that cell. 3. Restart the cell.
1851
Used as a gateway from an embedded BMC ProactiveNet cell to the BMC ProactiveNet Server.
1. Update the new changes on mcell.dir. 2. Ensure that the cell is running. 3. Restart the jserver. 4. Restart the Event adapter.
2638
Used by JServer and AC to connect to the Database. The Database listens on this port for JServer or Agent Controller to initiate communication.
1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.api.database.portnum property to the new port number. 2. Restart the system by running the command: pw system start
3084
Enables Impact Administration Server actions to be triggered from the cell.
3115
Used as a gateway from the cell to Integration for BMC Remedy Service Desk (IBRSD)
3182
Used by the Integration Service to listen for the ProactiveNet Server.
Installation Directory\pw\pproxy\PNS\bin\pproxsrv.exe -install -p 3182 -m 3182 is the default port name, different port can be given in command prompt and updated to custom\pronet.conf
Chapter 2
41
Table 1
Port 3183

Description To change the port... Integration Service listens Using the command line for the ProactiveNet PATROLAgent -proxyserver tcp:<IntegrationServiceHost>: Agent. Used in failover <StagingAdapterPort> -p <PATROLAgentPort> -km UNIX3.km configuration. where,
s s
s s
<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. km must either be loaded or preloaded.
Using the environment variable Run the following command to set the PROXYSERVERS environment variable: set PROXYSERVERS=tcp:<Integration Service Host>: <StagingAdapterPort> where, PROXYSERVERS 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/proxy/proxyServers" = { REPLACE ="tcp:<IntegrationServiceHost>:< StagingAdapterPort >"} Note: You can also change the Staging Adapter port using the Administration Console. 8005 Used by Jserver to shut down the Tomcat server. Change the port number in the appropriate files for your operating system:
s
Microsoft Windows: pw\pronto\conf\pronet.conf and pw\pronto\conf\jserv.properties UNIX: tomcat/conf/server.xml
42
Table 1
Port 8008

Description Tunnel Proxy port To change the port... Change the port number in the appropriate files for your operating system:
s s
Microsoft Windows: and pw\pronto\conf\pronet.conf UNIX: pw/pronto/conf/jserv.properties
8009
Used by the Tomcat server to connect to Apache
Change the port number in the appropriate files for your operating system:
s
Microsoft Windows: pw\pronto\conf\pronet.conf and pw\pronto\conf\jserv.properties UNIX: tomcat/conf/server.xml
8093
JMS Server port
Change the port number in the appropriate files for your operating system:
s
Microsoft Windows: pw\pronto\conf\pronet.conf and pw\jboss\server\minimal_jms\delpoy\jbossmq-service.xml UNIX: pw/jboss/server/minimal_jms/delpoy/jbossmq-service.xml
9149 12123
This is a It is a non-configurable port. This port is required to be open. pronet.jserver.event.port. Agent Controller listens for the Jserver on this port 1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.agentcontroller.port property to the new port number. 2. Restart the system by running the command: pw system start
12124
Used by the Remote Agent to listen for communication from the Agent Controller. Agent Controller Call back port Used by Remote Agents to send data back to the ProactiveNet Server.
This port can be changed using the BMC ProactiveNet Administration Console or CLI.
12126
Note: Any changes to the Agent Controller Call back port configuration must be made to all remote Agents. 1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.agent.cntl.port property to the new port number. 2. Restart the system by running the command: pw system start 3. Repeat for all remote Agents. 4. Restart the BMC ProactiveNet Agent.
12134
This is a TCP port that is It is a non-configurable port. used for communication between the Agent controller and the Apache server for agent. Communication is initiated when the Agent Controller starts.
Chapter 2
43
Preparing to install BMC ProactiveNet Performance Management with Oracle database
Table 1
Port 12141

Description Log Server port To change the port... 1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.logging.logServer.port property to the new port number. 2. Restart the system by running the command: pw system start
15000
Connects the Agent Controller to the Rate process. The Rate process passively listens to port 15000 until the Agent Controller initiates contact.
1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.rate.port property to the new port number. 2. Restart the system by running the command: pw system start
45000
Message Server port
1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.messageserver.port property to the new port number. 2. Restart the system by running the command: pw system start
Preparing to install BMC ProactiveNet Performance Management with Oracle database

Creating Oracle database instances
Before You Begin
Before creating instances ensure that the machine and port of the Oracle Server is accessible from the machine where the BMC ProactiveNet Server is installed.
To create Oracle instances 1 Create a dedicated Oracle Database Instance (System ID/SID) on the machine
where Oracle is installed.
2 Set the following character sets:

s s
Database Character Set - AL32UTF8 National Character Set - UTF8
44
Using BMC provided scripts
Recommendations
BMC recommends the following:
s s
Enable the archivelog mode to run on the Oracle database. For proper functioning of BMC ProactiveNet Performance Management , ensure that there is enough space in the recovery destination folder for accommodating the archives. Take backup of the archives regularly and delete unwanted archive files from the recovery destination folders. Ensure that there are at least two sets of redo log files created with minimum size of 500 MB each on the Oracle database instance.

BMC provides a single script, run_oracle_db_scripts.sql, that sets up the database (Setting system parameters), creates tablespaces (Creating tablespaces), and users (Creating users and permissions) that are required for installing BMC ProactiveNet Performance Management. The BMC provided script will be available in the DVD under
Utilities\oracle\custom_db_scripts_pnet.
NOTE
The script is available under ServerWin_pw_v8.6_bxxxxxxx\Utilities\oracle for Windows and Server_pw_v8.6_bxxxxxxx/Utilities/oracle for Solaris (where xxxxxxx is the build
number).
Setting system parameters

BMC recommends you to set the following list of parameters. Use the ALTER SYSTEM SET command to execute the following parameters:
Chapter 2
45
bitmap_merge_area_size =0 scope =spfile; commit_point_strength =0 scope =spfile; db_block_checksum =typical scope =spfile; db_flashback_retention_target =0 scope =spfile; db_writer_processes =2 scope =spfile; fast_start_mttr_target =0 scope =spfile; fast_start_parallel_rollback =LOW scope =spfile; job_queue_processes =20 scope =spfile; parallel_execution_message_size =4096 scope =spfile; remote_login_passwordfile =EXCLUSIVE scope =spfile; replication_dependency_tracking =FALSE scope =spfile; session_cached_cursors =75 scope =spfile; session_max_open_files =20 scope =spfile; streams_pool_size =0 scope =spfile; timed_statistics =TRUE scope =spfile; undo_management =AUTO scope =spfile; undo_retention =10800 scope =spfile; shared_pool_size =0 scope =spfile; java_pool_size =0 scope =spfile; large_pool_size =0 scope =spfile; processes =1000 scope=spfile; open_cursors=4000; Alter system set sga_max_size=0 scope=spfile Alter system set sga_target=0 scope=spfile Alter system set pga_aggregate_target=0 scope=spfile
Set the memory_max_target and memory_target parameters to the maximum memory you can allocate for your Oracle instance. The memory for each parameter should be set to a minimum 50% of the total memory available for one Oracle instance. For example, if the RAM size is 4GB, the following parameters should be set to 2GB:
Alter system set memory_max_target=2000M scope=spfile Alter system set memory_target=2000M scope=spfile
NOTE
Run the above parameters explicitly without fail, as the script provided does not run these parameters.
Creating tablespaces
A tablespace with data file of initial size of 1 GB and subsequent extents with 500 MB is created. If you want large initial size and large subsequent extents you can use the manual steps mentioned below. BMC recommends that you create two tablespaces, a main and a temporary tablespace.
46
Following is a list of tablespace sizes that you can use for small, medium, and large tablespaces:
s s s
Small: 15 GB Medium: 30 GB Large: 30 GB
You can use these sizes as a reference to create your tablespaces manually. An error java.sql.SQLException: ORA-01653: unable to extend table PROACT.BIGIPLTMPOOL_0_STATS_5 by 128 in tablespace PNET_TS occurs, if the tablespace is full or if there is no sufficient disk space to extend the tablespace after a period of time. The Database Administrator monitors the tablespace and takes an appropriate action as follows:
s
s s
Add a DATAFILE into the BMC ProactiveNet Performance Management tablespace Resize DATAFILE Enable AUTOEXTEND
NOTE
Only one data file is added to the tablespace created by the scripts. However, you can add required additional data files to the same tablespace.
Alternatively, you can use the following commands to create tablespaces instead of using the BMC provided script:
CREATE TABLESPACE BPPM_TS DATAFILE '<path>' REUSE SIZE 1G AUTOEXTEND ON NEXT 500M MAXSIZE 15G CREATE TEMPORARY TABLESPACE BPPM_TMP_TS TEMPFILE '<path>' SIZE 200M REUSE AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED;
BMC recommends you to use the following tablespace sizes while creating tablespaces:
s s s
Initial SIZE: 1 GB REUSE AUTOEXTEND ON NEXT: 500 MB MAXSIZE: 15 GB or you can increase the size as per your requirement.
Chapter 2
47
Creating users and permissions

You can create the following database users:
s
A schema user, by default proact. This user has the privilege to store BMC ProactiveNet Performance Management data. You can configure the name and password. The user proact is not encrypted. A report user, by default report. This user has the privilege to access the BMC ProactiveNet Performance Management data. Ensure that this user has the name and password as 'report only. The report password is not encrypted.
Alternatively, you can use the following commands to create users instead of using the BMC provided script:
CREATE USER &userName IDENTIFIED BY &passwd;
Here, &userName is the user we are creating and &passwd is the password.
CREATE USER report IDENTIFIED BY report;
Here, the mandatory user report is created.

ALTER USER &userName DEFAULT TABLESPACE &tblsp; ALTER USER &userName TEMPORARY TABLESPACE &tblsp._TMP;
Here, the user is assigned the default table-space and temporary tablespace. Commands to grant privileges:
GRANT &privilege TO &userName;
Here, &privilege is the privilege and &userName is the user whom the grant is provided.
Use the list of privileges given below along with the GRANT command for the schema user.
48
grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant grant
connect resource create select_catalog_role execute_catalog_role gather_system_statistics select any table select on dba_data_files select on dba_temp_files select on dba_jobs_running select on dba_jobs select on dba_scheduler_jobs QUERY REWRITE UNLIMITED TABLESPACE select on sys.v_$parameter select on sys.dba_free_space select on sys.dba_tablespaces select on sys.v_$session select on sys.v_$lock select on sys.dba_jobs select on sys.v_$waitstat select on sys.v_$sysstat select on sys.v_$librarycache select on sys.v_$rowcache select on sys.dba_users select on sys.dba_roles select on sys.dba_tab_privs select on sys.dba_data_files select on sys.dba_temp_files select on sys.v_$instance select on sys.v_$rollname select on sys.v_$rollstat select on sys.v_$system_event select on sys.v_$log select on sys.v_$archive_dest select on sys.v_$database
You should grant the user report with the following privilege:
grant connect
For an unchanging password or for a password to never expire, you can use the following statements available in the BMC provided script.
CREATE PROFILE BPPM_PROFILE LIMIT PASSWORD_LIFE_TIME UNLIMITED FAILED_LOGIN_ATTEMPTS UNLIMITED ; ALTER USER <&UserName> PROFILE BPPM_PROFILE; ALTER USER report PROFILE BPPM_PROFILE;
Restart the Oracle database instance after setting all the parameters.
Chapter 2
49
Hardware and software requirements
Hardware and software requirements

Hardware and software requirements are listed in the Product Availability and Compatibility Matrix available at http://www.bmc.com/support_home. For additional requirements information, see the BMC ProactiveNet version 8.6.01 Compatibility and Support Matrix document.
50
Chapter
Preparing for BMC Atrium CMDB integration

3
If you are integrating BMC ProactiveNet with BMC Atrium CMDB, you must install the BMC ProactiveNet CMDB Extensions, components, and hotfixes before you configure the BMC ProactiveNet Server to integrate with the CMDB.
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.
Installation scenarios
The following scenarios help you to determine the installation and integration process appropriate for your environment.
Integrating BMC Atrium CMDB with BMC ProactiveNet

The following steps describe the general procedure to install or upgrade BMC ProactiveNet with BMC Atrium CMDB integration. The location of each installation component is listed in Table 2 on page 52.
Chapter 3
51
Integrating BMC Atrium CMDB with BMC ProactiveNet
1. (For BMC Atrium CMDB version 7.5, patch 5 only) Install the Notification Engine and Notification Engine Web Services. 2. Install the components in the order presented, according to the BMC Atrium CMDB version:
BMC Atrium CMDB version 7.5 patch 5 or 7.6 patch 2 or 7.6.03 fresh installation 7.6.03 upgrade Procedure A. Install the BMC ProactiveNet CMDB Extensions. B. Install BMC Atrium CMDB hotfixes. A. Install BMC Atrium CMDB hotfixes. B. Install the BMC ProactiveNet CMDB Extensions. 7.6.03 Foundation installation A. Install the AR hotfix. B. Install the BMC ProactiveNet CMDB Extensions. C. Install BMC Atrium CMDB hotfixes. 7.6.04 or 7.6.04 patch 1 A. Install the BMC ProactiveNet CMDB Extensions.
3. Run the BMC Atrium CMDB validation utility. See Validating BMC Atrium CMDB elements on page 57 for details. 4. Integrate BMC ProactiveNet with BMC Atrium CMDB in one of the following ways:
s
(install or upgrade, no previous BMC Atrium CMDB integration) Install BMC ProactiveNet Server. During the BMC ProactiveNet Server installation process, specify the BMC Atrium CMDB server details. (upgrade with an existing BMC Atrium CMDB integration) Manually configure integration between the BMC ProactiveNet Server and BMC Atrium CMDB. For instructions, see Configuring BMC Atrium CMDB integration on page 147.
Table 2 lists the location of the BMC Atrium CMDB installation components. See the documentation provided with the installation files for details. Table 2
Component AR hotfix
BMC Atrium CMDB installation component directories (part 1 of 2)

Installation directory Integrations\Atrium_CMDB\Atrium_CMDB_HotFixes\ SolutionInstall Atrium_CMDB_Foundation_7603 \ AR\Windows Integrations\Atrium_CMDB\PNET_CMDB_Extensions See Installing BMC ProactiveNet CMDB Extensions on page 54 for details.
BMC ProactiveNet CMDB Extensions
52
Integrating with BMC Atrium CMDB in a cluster environment
Table 2
Component
BMC Atrium CMDB installation component directories (part 2 of 2)

Installation directory
BMC Atrium CMDB hotfixes Integrations\Atrium_CMDB\Atrium_CMDB_HotFixes\ Atrium_CMDB_cmdbVersion\platform Contact BMC Customer Support for the latest hotfixes. Notification Engine and Notification Engine Web Services Integrations\Atrium_CMDB\ NOE_Bundle_For_CMDB_75
Integrating with BMC Atrium CMDB in a cluster environment

In a cluster environment, each BMC Remedy Action Request System server in the cluster requires BMC ProactiveNet CMDB Extensions, modules, and hotfixes. Before installing the extensions, remove servers from the server group. For instructions about configuring and removing servers in a server group, see BMC Remedy Action Request System Configuration Guide, located at http://webapps.bmc.com/support/faces/prodallversions.jsp?seqid=108018. You need to be a member of the BMC Support website to access the documentation. The following steps describe the general procedure to integrate BMC ProactiveNet with BMC Atrium CMDB in a cluster environment. The location of each installation component is listed in Table 2 on page 52. 1. In the BMC Remedy Action Request System Administration Console, remove each server from the server group. 2. Restart the servers. 3. On each server, install BMC ProactiveNet CMDB Extensions. 4. Return each server to the server group and restart the servers. 5. (for BMC Atrium CMDB version 7.5, patch 5, only) On each server, install the Notification Engine and Notification Engine Web Services. 6. On each server, install BMC Atrium CMDB hotfixes. 7. Run the BMC Atrium CMDB validation utility. See Validating BMC Atrium CMDB elements on page 57 for details.
Chapter 3
53
Installing BMC ProactiveNet CMDB Extensions

Install BMC ProactiveNet CMDB Extensions on the same computer where BMC Atrium CMDB is installed. If you have installed BMC Remedy Action Request System on both the primary and secondary server, you need to install BMC ProactiveNet CMDB Extensions on both these systems.
Before you begin

In a cluster environment, follow the guidelines in Integrating with BMC Atrium CMDB in a cluster environment on page 53. Follow the installation procedure appropriate for your operating system.
To install BMC ProactiveNet CMDB Extensions on Microsoft Windows 1 Navigate to the Integrations\Atrium_CMDB\PNET_CMDB_Extensions directory in
the installation package.
s
If you have an installation DVD, copy the contents to a directory with write permission, and navigate to the directory. If you have a download directory, navigate to the directory.
2 Double-click pnExtLoader.exe.
The InstallShield Wizard window is displayed.
3 In the Welcome dialog box, click Next. 4 Accept the software license agreement. 5 In the AR Server Connection Information dialog box, complete the following fields
and click Next.
Field AR Server Name Port Number RPC Port Number Description name of the system on which BMC Remedy Action Request System is installed target port number for the BMC Remedy Action Request System server If you specified a non-standard RPC port number while installing BMC Remedy Action Request System, enter that RPC port number. Otherwise, you can leave this field blank
54
For more information about the portmapper and port numbers used with BMC Remedy Action Request System, see the BMC Remedy Action Request System Installation Guide.
6 In the Administrator Logon Information Required dialog box, in the User Name
and Password fields, enter the credentials required to access BMC Remedy Action Request System and click Next.
7 In the Remedy CMDB Setup dialog box, perform one of the following actions:
s
If you have not enabled the portmapper to automatically obtain the port number, enter the port number of the BMC Remedy Action Request System server and click Next. If you enabled the portmapper to automatically obtain the port number, you can leave this field blank and click Next.
For more information on the portmapper and port numbers used in BMC Remedy Action Request System, see BMC Remedy Action Request System Installation Guide. The installer displays the progress of the installation.
8 Click Finish to complete the installation. 9 Restart Apache Tomcat as described in To restart Apache Tomcat on Microsoft
Windows on page 56.
To install BMC ProactiveNet CMDB Extensions on UNIX NOTE

Ensure that you have execute permissions to the common directory before starting the installation. To obtain execute permissions, run chmod -R 777 common.
1 Navigate to the Integrations/Atrium_CMDB/PNET_CMDB_Extensions directory in

the installation package.
s
2 Start the installation by executing ./pnExtLoader. 3 Read and accept the license agreement.
Chapter 3
55
Restarting Apache Tomcat
4 Answer the questions in the following table to continue with the installation.
Question Enter the server name What is the AR System installation directory? What is the TCP/IP port for AR System server? What is a valid AR System Administrator ID? What is the password for the AR System Administrator? Server port Description Enter the name of the computer on which BMC Remedy Action Request System is installed. Enter the directory in which BMC Remedy Action Request System is installed. Enter the TCP/IP port number that the BMC Remedy Action Request System server listens to. Enter the user ID required to access BMC Remedy Action Request System. Enter the password required to access BMC Remedy Action Request System. Enter the port number of the BMC Remedy Action Request System server. The default is 1840.
For more information on the portmapper and port numbers used in BMC Remedy Action Request System, see BMC Remedy Action Request System Installation Guide. The installation starts after you enter the values in the table above. The installer displays BMC ProactiveNet CMDB Extensions completed. after the installation is complete.
5 Restart Apache Tomcat as described in To restart Apache Tomcat on UNIX.
Restarting Apache Tomcat

After installing BMC ProactiveNet CMDB Extensions you must restart Apache Tomcat. Follow the procedure appropriate for your operating system.
To restart Apache Tomcat on Microsoft Windows 1 Open a command prompt and type services.msc. 2 Right-click Apache Tomcat 6 and click Restart. To restart Apache Tomcat on UNIX 1 Navigate to tomcat_home/bin. 2 Stop Apache Tomcat by executing ./shutdown.sh. 3 Restart Apache Tomcat by executing ./startup.sh.
56 BMC ProactiveNet Getting Started Guide
Installing required modules and hotfixes
Installing required modules and hotfixes

BMC Atrium CMDB version 7.5 patch 5 first requires installation of the Notification Engine and Notification Engine Web Services. All supported versions of BMC Atrium CMDB require installation of the hotfixes.
To install required modules and hotfixes 1 If you are using BMC Atrium CMDB version 7.5 patch 5, install the Notification
Engine and Notification Engine Web Services from the
Integrations/Atrium_CMDB/NOE_Bundle_For_CMDB_75 installation directory.
See the documentation provided with the installation files for details.
2 Install BMC Atrium CMDB hotfixes from the Integrations/Atrium_CMDB/

Atrium_CMDB_HotFixes/Atrium_CMDB_cmdbVersion/platform installation directory
See the documentation provided with the installation files for details. Contact BMC Customer Support for latest hotfixes.
Validating BMC Atrium CMDB elements

After you install BMC ProactiveNet CMDB Extensions, run the validate_atrium_cmdb CLI command to validate the following items:
s s s
BMC Remedy Action Request System server host, port, user name and password Supported BMC Atrium CMDB version and patch level BMC ProactiveNet CMDB Extensions version and patch level, which confirms the following: SIM class information version SIM workflow version SIM management data
Run the command from the computer where you plan to install or upgrade the BMC ProactiveNet server.
NOTE
Run the validation command before any BMC Atrium CMDB integration, whether you install BMC ProactiveNet for the first time or you upgrade to the current version of BMC ProactiveNet.
Chapter 3
57
Validating BMC Atrium CMDB elements
To validate BMC Atrium CMDB elements 1 On the computer where you plan to install or upgrade the BMC ProactiveNet
server, navigate to the Integrations/Atrium_CMDB/AtriumCMDB_Validator directory in the installation package.
s
2 In a command prompt, change the directory to the location where the files are
located.
3 Run the validate_atrium_cmdb command according to the following syntax:

validate_atrium_cmdb -s ARServerName -t port -u userName [-p password]
where
s
ARServerName is the BMC Remedy Action Request System server computer
name or IP address
s
port is the port number used by the BMC Remedy AR System server on that
computer
s
userName is a valid user name with read permission on the BMC Remedy AR
System server
s
password is a password for the user name. If a password is not required, do not
use this option. The validation status is displayed upon completion. If the validation fails, verify that the command options are correct and that the BMC Atrium CMDB server is running. Then verify that patches, hotfixes, and BMC ProactiveNet CMDB Extensions have been installed successfully. After successful validation, you can select to integrate with BMC Atrium CMDB during BMC ProactiveNet server installation or upgrade.
58
Chapter
Installing the BMC ProactiveNet Server on Microsoft Windows for the first time
4
This chapter provides instructions for installing the BMC ProactiveNet Server on Microsoft Windows for the first time. If you are upgrading, see the Upgrade Guide for instructions.
Installing BMC ProactiveNet Server on Microsoft Windows

The BMC ProactiveNet Server installation installs the following components:
s
BMC ProactiveNet Server BMC ProactiveNet Agent The BMC ProactiveNet Agent installed with the BMC ProactiveNet Server is referred to as the local agent. BMC does not recommend using the local BMC ProactiveNet Agent for monitoring anything other than the BMC ProactiveNet Server.
WARNING
The Integration Service is installed with the BMC ProactiveNet Agent. Due to conflicts with the BMC ProactiveNet Server and the drain on the resources of the local Agent, BMC Software does not recommend enabling the Integration Service on the same computer where the BMC ProactiveNet Server is installed.
Chapter 4
59
(Optional) BMC ProactiveNet Performance Management Package Installation Repository When you install the BMC ProactiveNet Server, you have the option to install the BMC ProactiveNet Performance Management Package Installation Repository. The Package Installation Repository includes the current versions of BMC components that are able to be used with BMC ProactiveNet, such as the BMC PATROL Knowledge Modules that can be integrated with BMC ProactiveNet and the BMC PATROL Agent. From the BMC ProactiveNet Operations Console, an administrator can select the components from the repository that he or she wants to install on the same computer(s) and package them together so that they can be installed simultaneously. For more information about creating component packages and installing them for use with BMC ProactiveNet, see Chapter 14, Creating and installing component packages.
BMC ProactiveNet Administration Console BMC ProactiveNet database
NOTE
If you repeatedly add/delete devices, the BMC ProactiveNet Agent may get associated to multiple devices.
Before you begin

s
Ensure that there are no remote BMC ProactiveNet Agents installed on the computer where the BMC ProactiveNet Server will be installed. If any remote BMC ProactiveNet Agents are installed on this computer, the BMC ProactiveNet Server installation will fail. Ensure that the computer on which you are installing the product adheres to the hardware, operating system, platform, and software requirements listed in the BMC ProactiveNet version 8.6.01 Compatibility and Support Matrix document. Ensure that the computer on which you are installing the product adheres to the requirements described in Chapter 2, Preparing for your installation. If you are using the Remote Desktop Connection (RDC) to install the product, then the RDC should be in console mode. While installing BMC ProactiveNet Server on a 64-bit Windows machine, ensure that you do not install it into the Program Files (x86) directory path.
60
Ensure that the .NET Framework version 3.0 is installed. If you are using a Windows 2003 machine, download and install the .NET Framework and if you are using Windows 2008, use the Role Management tool. For more information on how to install the .NET Framework, go to the Microsoft website http://www.microsoft.com. Do not start multiple server installations at the same time. If you start multiple installations, keep only one installation window open and close the other installation windows for expected results.
To install the BMC ProactiveNet Server on Microsoft Windows 1 Start the installation program using one of these methods:
s
DVD: Insert the installation DVD. In the ServerWin_pw_vX_bY directory (where X is the version number and Y is the build number), open the BPPMServer directory. Double-click the setup.cmd file. BMC Software EPD website (http://webapps.bmc.com/epd): Select BMC ProactiveNet and select the current version for the platform that you are installing to. Download the BMCProactiveNetWin_VerX_bY.zip file that corresponds to the version of the BMC ProactiveNet, unzip the file, and doubleclick the setup.exe file (where X is the version number and Y is the build number).
2 On the Welcome screen, click Next.

To agree to the license agreement, select I agree to the terms of the license agreement on the Read the License Agreement and Select the Appropriate Option screen, and click Next . The pre-installation check begins.
3 On the Directory Selection screen, accept the default directory (\Program

Files\BMC Software\ProactiveNet) or click Browse to choose a different directory
and click Next.
WARNING
Do not install BMC ProactiveNet Server in a root directory (for example C:\ or D:\), on a shared drive, or in the Documents and Settings folder.
Chapter 4
61
4 On the UDDI Connection Information screen, select Yes if you want to connect to
the UDDI server, complete the following fields and click Next. These inputs will be used for both cross launch and BladeLogic integration
Field Host Description Enter the host name of UDDI Registry for Atrium CMDB and for Atrium CMDB, the name of the Atrium Web Services Server. Enter the port of UDDI Registry for CMDB or the port of Atrium Web Services server for CMDB. The default is 7777. Enter the UDDI Registry user name. The default is Admin. Enter and confirm the UDDI Registry password.
Port User Password/ Confirm Password
5 If you have provided the UDDI details in the UDDI Connection Information
screen, the following inputs are requested. Select Yes if you want to connect to the BladeLogic Server, complete the following fields and click Next.
Field BMC BladeLogic user Description Enter the username for the BladeLogic server.
BMC BladeLogic password / Enter and confirm password for the BladeLogic server. BMC BladeLogic confirm password BMC BladeLogic role Enter the role that is defined to grant permissions to the BladeLogic user. Default is BLAdmin.
If you have not provided the UDDI details, the following inputs are requested.
Field BMC BladeLogic application server Description Enter the BladeLogic application server name.
BMC BladeLogic web service Enter the web service port number required to connect to the port BladeLogic server. BMC BladeLogic user Enter the username for the BladeLogic server. BMC BladeLogic password / Enter and confirm password for the BladeLogic server. BMC BladeLogic confirm password BMC BladeLogic role Enter the role that is defined to grant permissions to the BladeLogic user. Default is BLAdmin.
62
6 On the CMDB Connection Information screen, perform one of the following

actions:
WARNING
Before you configure the CMDB Server, ensure that BMC ProactiveNet CMDB Extensions, modules, and hotfixes are installed on the computer where the BMC Atrium CMDB is installed. If necessary, you can stop this installation, install the extensions, and then restart the BMC ProactiveNet Server installation. For information about installing the CMDB extensions, see Chapter 3, Preparing for BMC Atrium CMDB integration.
A Select No if you do not want to integrate the BMC ProactiveNet Server with
BMC Atrium CMDB, and click Next.
NOTE
Configuring the BMC ProactiveNet Server for integration with BMC Atrium CMDB is recommended, but not mandatory, during installation. If you do not configure the ProactiveNet Server for CMDB integration during installation, you can manually configure CMDB integration any time after installation is complete. For instructions, see Configuring BMC Atrium CMDB integration on page 147.
B Select Yes if you want to configure the BMC ProactiveNet Server to integrate
with BMC Atrium CMDB. Complete the following fields and click Next.
Field Host Port Description Enter the host name of the CMDB or AR Server. Enter the CMDB or AR Server port number. The default is 0. If AR is configured with a portmapper, enter port 0. User Password/ Confirm Password Version Enter the user name required to log in to the AR Server. The default is Demo. Enter and confirm the password required to log in to the AR server. Select the version number of the BMC Atrium CMDB Server. s For BMC Atrium CMDB version 7.5, enter 7.5 s For BMC Atrium CMDB version 7.6, enter 7.6 s For BMC Atrium CMDB version 7.6 patch 3, enter 7.6.03 s For BMC Atrium CMDB version 7.6 patch 4, enter 7.6.04
Chapter 4
63
7 On the Cell Configuration screen, complete the following SIM and Admin cell
fields and click Next.
Field SIM cell details: Cell Instance Name Type the cell instance name. The default is pncell_hostname. Note: Hyphens and underscores are the only special characters allowed for cell instance names. Cell Port Admin cell details: Encryption Key Port Encryption Key Enter the cell encryption key. The default is mc. No special characters are allowed. Enter the port number for the Admin cell. The default is 1827. Enter an encryption key for the Admin cell. The default is mc. Enter a port number in the range of 1024 to 65535. The default port for the cell is 1828. Description
You are not prompted for the cell details if you are upgrading from a previous version of BMC ProactiveNet Server.
8 On the Administrator Information screen, complete the following fields and click
Next. Field Sender E-mail ID Description e-mail address that you specify as the sender of any notification emails. For example, you might specify hostName@company.com so that the administrator receiving the e-mail will know immediately which host is having disk space problems or other issues that send notifications.
Administrator E-Mail ID fully-qualified e-mail address for the person that will be the administrator of the ProactiveNet Server. The format for the email address should be user@company.com. Name or IP Address of SMTP Server Name or IP address of the SMTP server.
9 On the Configuring Package Installation Repository screen, click Yes to install the
Package Installation Repository. Complete the following fields and click Next.
Field Source Directory Destination Directory Description The source directory of the Package Installation Repository. The destination directory where you want to install the Package Installation Repository.
64
Installing BMC ProactiveNet Performance Management with Oracle
10 The Validating Configuring Package Installation Repository user inputs screen

displays errors, if any. Click Preview and correct the errors. If Microsoft .NET Framework is not found on the computer a warning is displayed. Install Microsoft .NET Framework version 3.0 using the Role Management tool. On the Installation Preview screen, installation details are displayed. The BMC ProactiveNet Server installation process may take a while to complete. No more user interaction is required until the installation process is finished.
11 On the Register with BMC ProactiveNet Performance Management screen, select

Yes to register with BMC, enter your e-mail address and click Next.
12 On the Installation Summary screen, click Done to complete the installation.

After the installation is comple, you can choose View Logs to open the installation logs.
NOTE
s s
For smooth upgrade/un-installation of the BMC ProactiveNet Server, ensure that you restart the computer at least once after installing the BMC ProactiveNet Server. If the DNS configurations are not correct in a computer, a warning No DNS Entry Found is displayed. Either correct the DNS configuration and restart the installation or if you want to continue with the installation, provide the IPaddress instead of the hostname when you are required to key in the hostname.

For information on setting up Oracle as the backend database, contact http://www.bmc.com/support.
To install Oracle as the database 1 Follow the procedure until step 3 in the Installing BMC ProactiveNet Server on
Microsoft Windows on page 59.
2 On the Configuring database screen, Oracle (External) is selected as your database.

Enter the following fields and click Next.
Chapter 4
65
Field Host Name/IP Address Port Database SID Username Password Confirm Password
Description Enter the host name or IP address of the machine that is running the standalone Oracle database instance. Enter the Oracle listener port on the machine. The default port is 1521. Enter the Oracle database name. Enter the username for the database instance. Do not use the term sys or system. Enter the password for the database instance. Confirm the password.
3 If you have enabled the RAC option, you can either choose Standalone or RAC for
the installation to be on a standalone or Oracle Real Application Cluster (RAC) setup. For setting up the RAC option, contact http://www.bmc.com/support.
A If you choose Standalone enter the following fields and click Next.
Field Host Name/IP Address Port Database SID Username Password Confirm Password Description Enter the host name or IP address of the machine that is running the standalone Oracle database instance. Enter the Oracle listener port on the machine. The default port is 1521. Enter the Oracle database name. Enter the username for the database instance. Do not use the term sys or system. Enter the password for the database instance. Confirm the password.
B If you choose RAC, enter the following fields and click Next.
Field Service Name Username Password Confirm Password Description Enter the service name for the RAC setup. Enter the username for the RAC setup. Do not use the term sys or system. Enter the password for the RAC setup. Confirm the password.
4 On the Configuring Oracle RAC screen, enter the number of nodes you want to
configure in the Number of Nodes to Setup field. The default is 4.
66
NOTE
The maximum number of nodes you can enter is 100. If you enter more than 100, the number of nodes is reset to 100.
5 Select Check if the below RAC Nodes are reachable? to view all the nodes that are
currently not reachable from the list of nodes you entered. If there are any unreachable nodes, a warning message is displayed. You may click Next to continue.
NOTE
The number of rows populated is based on the number of nodes you want configured.
If you do not select Check if the below RAC Nodes are reachable?, you will be able to view the unreachable nodes from the list of nodes that you have entered. Irrespective of your selection the Check if the below RAC Nodes are reachable? validates all the nodes to find at least one valid node. If none of the nodes is valid, an error message is displayed and you cannot proceed further.
6 Enter the following fields and click Next.

Field Virtual Host Name/IP Address Port Number Description Host or IP address where Oracle is installed.
Port number where Oracle is listening for requests. The

default port is 1521.
7 Click Previous to provide the correct information and continue with the
installation.
8 Continue with the installation from step 4 in the Installing BMC ProactiveNet
Server on Microsoft Windows on page 59. For more information on creating and setting up the Oracle database, see Preparing to install BMC ProactiveNet Performance Management with Oracle database on page 44.
Chapter 4
67
Applying licenses
Applying licenses
NOTE
Applying or updating the license restarts the jserver process and forces all active user sessions on BMC ProactiveNet Server to log off.
When you purchased the product, you should have received the following license files in a .zip file from your BMC Software representative:
s s
proactivenet.lic proactivenet.sign
To apply the license 1 Unzip the license files. 2 Copy the license files to the installDirectory\pw\license directory (for example,
C:\Program Files\BMC Software\ProactiveNet\pw\license).
3 From the system icon tray, right-click the BMC ProactiveNet icon
pw commands.
and choose
4 In the BMC ProactiveNet Pw Commands window, on the command line enter the
following command:
pw lic update
The BMC ProactiveNet license is updated.
WARNING
Once you have loaded the license, moving or changing the license files can cause a number of errors to occur. When ProactiveNet is installed a hidden .pbk file is created. If the licence directory is removed and then recreated so that .pbk no longer exists, the .pbk file must be readded for ProactiveNet licensing to function properly. This file can be captured from a backup of the installation (if a backup exists) or from another computer where ProactiveNet is installed. If error messages occur, see the BMC ProactiveNet Troubleshooting Guide.
68
Chapter
Installing remote BMC ProactiveNet Agent(s) on Microsoft Windows

5
This chapter provides instructions for installing a remote BMC ProactiveNet Agent on Microsoft Windows for the first time. If you are upgrading, see the BMC ProactiveNet Upgrade Guide for instructions. The following components are installed with the remote BMC ProactiveNet Agent:
s s s
BMC ProactiveNet Agent Integration Service BMC Impact Event Adapters
BMC ProactiveNet allows you to install one or more remote BMC ProactiveNet Agents on a single computer. Multiple BMC ProactiveNet Servers can connect to the remote BMC ProactiveNet Agents running on a single computer. However, each remote BMC ProactiveNet Agent on a computer can communicate with only one BMC ProactiveNet Server at a time. For instructions and more information about installing multiple remote BMC ProactiveNet Agents, see Installing multiple BMC ProactiveNet Agents on a single computer on page 73.
Best practices for installing BMC ProactiveNet Agents

s
Do not install a remote BMC ProactiveNet Agent on the same computer as a BMC ProactiveNet Server. The BMC ProactiveNet Server is the central system of all the BMC ProactiveNet functions and should work at peak performance at all times. The BMC ProactiveNet Server has its own agent (called a local agent) that monitors the health of the BMC ProactiveNet system. Installing a remote agent on the same computer
Chapter 5
69
pulls resources away from the BMC ProactiveNet Server components. Also, if multiple BMC ProactiveNet Agents are installed on the BMC ProactiveNet Server computer, the additional remote agents will interfere with some of the server commands.
s
Do not start multiple agent installations at the same time. Ensure that the .NET Framework version 3.0 is installed. If you are using a Windows 2003 machine, download and install the .NET Framework and if you are using Windows 2008, use the Role Management tool. For more information on how to install the .NET Framework, go to the Microsoft website http://www.microsoft.com. Ensure that the computer on which you are installing the product adheres to the hardware, operating system, platform, and software requirements listed in the BMC ProactiveNet version 8.6.01 Compatibility and Support Matrix document. Ensure that the computer on which you are installing the product adheres to the requirements described in Chapter 2, Preparing for your installation.
To install BMC ProactiveNet Agent(s) on Microsoft Windows 1 Start the installation program from the BMC ProactiveNet Operations Console. A From a BMC ProactiveNet Server computer, log on to the BMC ProactiveNet
Operations Console.
B Click the Options link at the top right of the console and click on the Downloads
tab.
C From the ProactiveNet Agent Software area, click BPPMAgentvrx.x_byyy.exe

(where x is the version and y is the build number) and save the file to the computer to which you are installing the BMC ProactiveNet Agent.
2 On the computer where you are installing the BMC ProactiveNet Agent, doubleclick the BPPMAgentvrx.x_byyy.exe file.
3 On the Welcome screen, click Next or if you are installing multiple agents choose
Install a new instance of this application on the Existing Installed Instances Detected screen.
4 On the License Agreement screen, select I agree to the terms of the license agreement
and click Next. The pre-installation check utility verifies whether or not the computer meets the requirements for installing a BMC ProactiveNet Agent.
70
5 If the pre-installation check fails, click Cancel, correct the issues if there are errors
or warnings listed in the Pre-install Validation Summary window, and restart the installation process. If you do not want to resolve the warnings click Next. If Microsoft .NET Framework is not found on the computer a warning is displayed. Install Microsoft .NET Framework version 3.0 using the Role Management tool.
6 On the Directory Selection screen, accept the default directory or choose a different
directory and click Next.
WARNING
Do not install the product in a root directory (for example, C:\ or D:\), shared drive, or directly under the Documents and Settings folder.
7 On the Installation Preview screen where the installation details are displayed,
click Next.
8 On the Configuring Integration Service screen, you can enable the Integration
Service to collect data from integration adapters such as BMC PATROL, Tivoli ITM, or HP Operations Manager. Perform one of the following actions:
s
If you do not want to enable the Integration Service at this time, click Next.
NOTE
You can also enable the Integration Service after installation is complete. For instructions, see Enabling the Integration Service to gather data from products that integrate with BMC ProactiveNet on page 166. If you want to enable the Integration Service, select Yes, complete the following fields, and click Next.
Description Enter the port number of the Integration Service. The default is 3182. Enter and confirm the password for the Integration Service
Field Port Password and Confirm Password
NOTE
If you have enabled the Integration Service for the first agent, you will not be prompted with the Configuring Integration Service screen for subsequent multiple agent installations.
9 On the Configuring Cell screen, enter the following details:
Chapter 5
71
Field Cell Instance Name
Description Type the cell instance name. The default is hostname. Note: Hyphens and underscores are the only special characters allowed for cell instance names.
Cell Port Cell Encryption Key
Enter a port number in the range of 1024 to 65535. The default port for the cell is 1828. Enter the cell encryption key. The default is mc. No special characters are allowed.
10 Enter the Agent Port details and click Next. By default, the agent port is 12124. 11 On the Configuring the Agent Service screen, enter the Agent Service Display Name
if you want to change the default name displayed and click Next.
12 On the Configuring the Tunnel Agent screen, perform the following tasks to use
the BMC ProactiveNet Agent in a tunnel mode.
A Select Yes and enter the following details:

Field Tunnel ID Server Description Enter the tunnel ID name. Enter the BMC ProactiveNet Server details.
NOTE
If you use a Tunnel Agent, only the General Administration functionality in the Administration tab of the Administration Console is accessible through this connection protocol. The Event Management Policies, Dynamic Data Editor, Infrastructure Management, and Services Editor tabs will be grayed out.
B Select Yes to run the tunnel agent in a secure mode and click Next.
The BMC ProactiveNet Agent installation process begins. This process may take several minutes to complete.
13 On the Installation Summary screen, click View Log to view the log file and click
Done to exit the agent installation.
72
Installing multiple BMC ProactiveNet Agents on a single computer
NOTE
s
If you modify the control port of an agent explicitly through the pronet.conf file, the port number is not updated in the Add/Remove Programs applet and in the Agent Service display name. If you modify the control port, the port number will not be displayed when you use Add/Remove Programs Each BMC ProactiveNet Agent on a system runs in a separate JVM. You can check the version of the BMC ProactiveNet Agent under installationDirectory\Agent\Pronto\Bin\AGENT_VERSION. You can install the agent in any path except the root directory (for example C:\, D:\ and so on). To replace a BMC Event and Impact Management cell, see Upgrade Guide.
s s
Installing multiple BMC ProactiveNet Agents on a single computer

NOTE
Installing multiple BMC ProactiveNet Agents on a single computer will put additional load on the computer in terms of CPU, IO, Memory, and TCP buffer.
By installing multiple BMC ProactiveNet Agents on a single system, you can partition your monitoring into different domains and maximize hardware usage. Multiple BMC ProactiveNet Servers in different locations can connect to different BMC ProactiveNet Agents running on the same computer. Each agent can collect a different set of data authorized for its respective BMC ProactiveNet Server. You can choose to install a new instance of the agent. Alternatively, you can upgrade an existing agent by selecting from the list displayed. If you want to upgrade an existing BMC ProactiveNet Agent, see the BMC ProactiveNet Upgrade Guide.
NOTE
s
When installing multiple agents on a single computer, only the first agent installed is installed with a cell. Subsequent agent installations update the cell installed with the first agent. Do not install an earlier version of the BMC ProactiveNet Agent on the same computer where a BMC ProactiveNet Agent version 8.6.01 is already installed.
Chapter 5
73
Verifying that the BMC ProactiveNet Agent is running
To install an additional BMC ProactiveNet Agent on a computer where a BMC ProactiveNet Agent is already installed
The procedure to install multiple agents is similar to installing the BMC ProactiveNet agent for the first time.
1 Follow the procedure given in To install BMC ProactiveNet Agent(s) on Microsoft

Windows on page 70 until 12.
2 On the BMC ProactiveNet Agent Installation dialog box, click Yes to overwrite the
IP Top10 detailed diagnostics, if WinPCAP application is installed.
3 On the Edit Data screen, enter a unique port number (no other agent should have
the same port number) in the range of 1024-65535 for the BMC ProactiveNet Agent that you are installing and click Next. The installation process is complete.
4 Click Finish. NOTE

The computer requires time to update installation information. BMC recommends that you wait a minimum of five seconds between installations.

After installation, to verify that the BMC ProactiveNet Agent is running, ensure that the BMC ProactiveNet Agent Ver x.x build yyyyyyy (portNumber) service status is Started. If the BMC ProactiveNet Agent Ver x.x build yyyyyyy (portNumber) service is not running, start it.
74
Chapter
Installing the BMC ProactiveNet Server on Solaris for the first time
6
This chapter provides instructions that describe how to install the BMC ProactiveNet Server on Solaris for the first time. If you are upgrading, see the BMC ProactiveNet Upgrade Guide. The BMC ProactiveNet Server installation installs the following components:
s
BMC ProactiveNet Server a BMC ProactiveNet Agent The BMC ProactiveNet Agent installed with the BMC ProactiveNet Server is referred to as the local Agent. BMC does not recommend using the local BMC ProactiveNet Agent for monitoring anything other than the BMC ProactiveNet Server.
WARNING
The Integration Service is installed with the BMC ProactiveNet Agent. Due to conflicts with the BMC ProactiveNet Server and the drain on the resources of the local Agent, BMC Software does not recommend enabling the Integration Service on the same computer where the BMC ProactiveNet Server is installed.
the BMC ProactiveNet Operations Console the BMC ProactiveNet Administration Console BMC ProactiveNet database (Optional) BMC ProactiveNet Performance Management Package Installation Repository
Chapter 6
75
Special considerations for installing on Solaris 10
When you install the BMC ProactiveNet Server, you have the option to install the BMC ProactiveNet Performance Management Package Installation Repository. The Package Installation Repository includes the current versions of BMC components that are able to be used with BMC ProactiveNet, such as the BMC PATROL Knowledge Modules that can be integrated with BMC ProactiveNet and the BMC PATROL Agent. From the BMC ProactiveNet Operations Console, an administrator can select the components from the repository that he or she wants to install on the same computer(s) and package them together so that they can be installed simultaneously. For more information about creating component packages and installing them for use with BMC ProactiveNet, see Chapter 14, Creating and installing component packages.
NOTE
If you repeatedly add/delete devices, the BMC ProactiveNet Agent may get associated to multiple devices.
Special considerations for installing on Solaris 10

The BMC ProactiveNet Server installation is permitted only on non-global zones in Solaris 10. You will not be able to upgrade previous versions of BMC ProactiveNet Server which are installed on global zones. If you need to upgrade on a global zone, contact BMC Customer Support for assistance. Installation on Solaris 10 is supported as follows:
s s s s
Solaris 10 global zone installation (non-global zones present)not supported Solaris 10 non-global zone installation (sparse non-global zone)not supported Solaris 10 global zone installation (no non-global zones present)supported Solaris 10 non-global zone installation (full non-global zone)supported
Installing the BMC ProactiveNet Server on Solaris

This section provides instructions for installing the BMC ProactiveNet Server on Solaris for the first time.
76
Before you begin

s
Ensure that there are no remote BMC ProactiveNet Agents installed on the computer where the BMC ProactiveNet Server will be installed. If any remote BMC ProactiveNet Agents are installed on this computer, the BMC ProactiveNet Server installation will fail. Ensure that the computer on which you are installing the product adheres to the hardware, operating system, platform, and software requirements listed in the BMC ProactiveNet version 8.6.01 Compatibility and Support Matrix document. Ensure that the computer on which you are installing the product adheres to the requirements described in Chapter 2, Preparing for your installation.
WARNING
The directory where the BMC ProactiveNet Server is installed and all its parent directories must have 755 permissions and must be owned by root, as well as the other group. Without these permissions and ownership, you will not be able to log into the BMC ProactiveNet Server.
To install the BMC ProactiveNet Server for Solaris 1 Ensure you have access to the BMC ProactiveNet files that you have downloaded
from the BMC Electronic Product Download site or from the BMC ProactiveNet DVD.
NOTE
If you are moving the files from one machine to another, be sure to use binary mode.

To agree to the license agreement, select I agree to the terms of the license agreement on the Read the License Agreement and Select the Appropriate Option screen, and click Next . The pre-installation check begins.
NOTE
While preparing to install, if you get a <setup>.bin: !: not found error, you can safely ignore the same.
Chapter 6
77
3 On the Directory Selection screen, accept the default directory

(/opt/bmc/ProactiveNet) or click Browse to choose a different directory and click Next.
WARNING
Do not install BMC ProactiveNet Server in a root directory (for example C:\ or D:\), on a shared drive, or in the Documents and Settings folder.
4 On the UDDI Connection Information screen, select Yes if you want to connect to
the UDDI server, complete the following fields and click Next. These inputs will be used for both cross launch and BladeLogic integration
Field Host Description Enter the host name of UDDI Registry for Atrium CMDB and for Atrium CMDB, the name of the Atrium Web Services Server. Enter the port of UDDI Registry for CMDB or the port of Atrium Web Services server for CMDB. The default is 7777. Enter the UDDI Registry user name. The default is Admin. Enter and confirm the UDDI Registry password.
Port User Password/ Confirm Password
5 If you have provided the UDDI details in the UDDI Connection Information
screen, the following inputs are requested. Select Yes if you want to connect to the BladeLogic server, complete the following fields and click Next.
Field BMC BladeLogic user Description Enter the username for the BladeLogic server.
If you have not provided the UDDI details, the following inputs are requested.
Field BMC BladeLogic application server Description Enter the BladeLogic application server name.
BMC BladeLogic web service Enter the web service port number required to connect to the port BladeLogic server. BMC BladeLogic user Enter the username for the BladeLogic server.
78
Field
Description
6 On the CMDB Connection Information screen, perform one of the following

actions:
WARNING
Before you configure the CMDB Server, ensure that BMC ProactiveNet CMDB Extensions, modules, and hotfixes are installed on the computer where the BMC Atrium CMDB is installed. If necessary, you can stop this installation, install the extensions, and then restart the BMC ProactiveNet Server installation. For information about installing the CMDB extensions, see Chapter 3, Preparing for BMC Atrium CMDB integration.
A Select No if you do not want to integrate the BMC ProactiveNet Server with
BMC Atrium CMDB, and click Next.
NOTE
Configuring the BMC ProactiveNet Server for integration with BMC Atrium CMDB is recommended, but not mandatory, during installation. If you do not configure the ProactiveNet Server for CMDB integration during installation, you can manually configure CMDB integration any time after installation is complete. For instructions, see Configuring BMC Atrium CMDB integration on page 147.
B Select Yes if you want to configure the BMC ProactiveNet Server to integrate
with BMC Atrium CMDB. Complete the following fields and click Next.
Field Host Port Description Enter the host name of the CMDB or AR Server. Enter the CMDB or AR Server port number. The default is 0. If AR is configured with a portmapper, enter port 0. User Password/ Confirm Password Version Enter the user name required to log in to the AR Server. The default is Demo. Enter and confirm the password required to log in to the AR server. Select the version number of the BMC Atrium CMDB Server. s For BMC Atrium CMDB version 7.5, enter 7.5. s For BMC Atrium CMDB version 7.6, enter 7.6. s For BMC Atrium CMDB version 7.6 patch 3, enter 7.6.03. s For BMC Atrium CMDB version 7.6 patch 4, enter 7.6.04.
Chapter 6
79
7 On the Cell Configuration screen, complete the following SIM and Admin cell
fields and click Next.
Field SIM cell details: Cell Instance Name Type the cell instance name. The default is pncell_hostname. Note: Hyphens and underscores are the only special characters allowed for cell instance names. Cell Port Admin cell details: Encryption Key Port Encryption Key Enter the cell encryption key. The default is mc. No special characters are allowed. Enter the port number for the Admin cell. The default is 1827. Enter an encryption key for the Admin cell. The default is mc. Enter a port number in the range of 1024 to 65535. The default port for the cell is 1828. Description
You are not prompted for the cell details if you are upgrading from a previous version of BMC ProactiveNet Server.
8 On the Administrator Information screen, complete the following fields and click
Next. Field Sender E-mail ID Description e-mail address that you specify as the sender of any notification emails. For example, you might specify hostName@company.com so that the administrator receiving the e-mail will know immediately which host is having disk space problems or other issues that send notifications.
Administrator E-Mail ID fully-qualified e-mail address for the person that will be the administrator of the ProactiveNet Server. The format for the email address should be user@company.com. Name or IP Address of SMTP Server Name or IP address of the SMTP server
9 On the Configuring Package Installation Repository screen, click Yes to install the
Package Installation Repository. Complete the following fields and click Next.
Field Source Directory Destination Directory Description The source directory of the Package Installation Repository. The destination directory where you want to install the Package Installation Repository.
80
10 The Validating Configuring Package Installation Repository user inputs screen

displays errors, if any. Click Preview and correct the errors. On the Installation Preview screen, installation details are displayed. The BMC ProactiveNet Server installation process may take a while to complete. No more user interaction is required until the installation process is finished.
11 On the Register with BMC ProactiveNet Performance Management screen, select

Yes to register with BMC, enter your e-mail address and click Next.

When the BMC ProactiveNet Server installation is complete, you can choose View
Logs to open the installation logs.

To install Oracle as the database 1 Follow the procedure until step 3 in the Installing the BMC ProactiveNet Server
on Solaris on page 76.

Chapter 6
81
NOTE
NOTE
82
Obtaining the fingerprint for the BMC ProactiveNet Server


installation.
8 Continue with the installation from step 4 in the Installing the BMC ProactiveNet
Server on Solaris on page 76. For more information on creating and setting up the Oracle database, see Preparing to install BMC ProactiveNet Performance Management with Oracle database on page 44.
Obtaining the fingerprint for the BMC ProactiveNet Server

The fingerprint is used to license and activate your BMC ProactiveNet products.
To obtain the BMC ProactiveNet Server fingerprint

In a C shell, execute the following commands:
source /usr/pronto/bin/.tmcsh pw license fingerprint
The output will be similar to:

FingerPrint: HSkZDN43dRUNNVtg7SssWg==
Chapter 6
83
Applying licenses
Applying licenses
NOTE
Applying or updating the license restarts the jserver process and forces all active user sessions on BMC ProactiveNet Server to log off.
Before you can configure and use the BMC ProactiveNet Server, you need a license key. You can obtain a license key by contacting BMC Software,
NOTE
s s
You must have root privileges to apply the license. You only need to apply the license to your BMC ProactiveNet Server installations. The license is not required on your remote agent installations.
The license key consists of three files:

s s s
proactivenet.lic (license provisioning file) proactivenet.sign (encrypted signature file) licensing.dtd (formatting information)
These files are typically packaged in a .zip file, which is delivered through an e-mail.
To apply the license 1 In binary mode, copy .zip file onto the computer where you have installed BMC
ProactiveNet Server into the /usr/pw/licenses directory.
2 Unzip the file. 3 To load the license data, execute the following command: pw license update 4 Enter y to restart the jserver.
If the license update is successful, an empty command prompt is displayed. If error messages are displayed, see BMC ProactiveNet Troubleshooting Guide.
WARNING
Once you have loaded the license, moving or changing the license files can cause a number of errors to occur. When ProactiveNet is installed a hidden .pbk file is created. If the licence directory is removed and then recreated so that .pbk no longer exists, the .pbk file must be readded for ProactiveNet licensing to function properly. This file can be captured from a backup of the installation (if a backup exists) or from another computer where ProactiveNet is installed.
84
Verifying the installation

Follow these steps to verify that the installation was successful:
1 Verify that all processes are running by executing the following commands:
#csh #source /usr/pw/pronto/bin/.tmcsh pw system status
A list of pw server processes is displayed that is similar to the following:

# pw system status Servers/ -----------------------Servers/Daemon Processes -----------------------services 4820 httpd 6152 jserver 10660 pronet_agent 4680 pronet_cntl 3968 tunnelproxy 7792 rate 3976 dbsrv 6560 mcell 4952 acell 4916 pserver 4217
2 Review the output for errors.

Processes that are not running properly are denoted by a numbered error message, such as 961 > max 1. Processes that are not running at all are denoted by !Not Running!.
3 If errors occur, restart the BMC ProactiveNet Server by executing the following
command:
pw system start
If error conditions persist, contact BMC Software customer support for assistance.
Chapter 6
85
86
Chapter
Installing remote BMC ProactiveNet Agent(s) on UNIX-based computers for the first time
7
This chapter provides instructions for installing a remote BMC ProactiveNet Agent on a UNIX-based operating system for the first time. If you are upgrading, see the BMC ProactiveNet Upgrade Guide for instructions. The following components are installed with the remote BMC ProactiveNet Agent:
s s s
BMC ProactiveNet Agent Integration Service BMC Impact Event Adapters (installed on all platforms except Solaris X86)
BMC ProactiveNet allows you to install one or more remote BMC ProactiveNet Agents on a single computer. Multiple BMC ProactiveNet Servers can connect to the BMC ProactiveNet Agents running on a single computer. However, each BMC ProactiveNet Agent on a computer can communicate with one BMC ProactiveNet Server at a time. For instructions and more information about installing multiple remote BMC ProactiveNet Agents, see Installing multiple BMC ProactiveNet Agents on single computer on page 92.

Do not install a remote BMC ProactiveNet Agent on the same computer as a BMC ProactiveNet Server.
Chapter 7 Installing remote BMC ProactiveNet Agent(s) on UNIX-based computers for the first time
87
Installing a BMC ProactiveNet Agent on a UNIX-based computer for the first time
The BMC ProactiveNet Server is the central system of all the BMC ProactiveNet functions and should work at peak performance at all times. The BMC ProactiveNet Server has its own agent (called a local agent) that monitors the health of the BMC ProactiveNet system. Installing a remote agent on the same computer pulls resources away from the BMC ProactiveNet Server components. Also, if multiple BMC ProactiveNet Agents are installed on the BMC ProactiveNet Server computer, the additional remote agents will interfere with some of the server commands.
Installing a BMC ProactiveNet Agent on a UNIX-based computer for the first time
To install the BMC ProactiveNet Agent from the BMC ProactiveNet Operations Console on the BMC ProactiveNet Server computer, see Installing the BMC ProactiveNet Agent remotely from the BMC ProactiveNet Operations Console on page 89.
Before you begin

s
Ensure that you have root permissions for the computer on which you want to install the BMC ProactiveNet Agent. Ensure that the computer on which you are installing the product adheres to the requirements described in Chapter 2, Preparing for your installation.
NOTE
The BMC ProactiveNet Agent installs and starts the BMC Impact Event Adapter if you choose to enable the cell while installing. However, the BMC ProactiveNet Agent install does NOT install Perl. Perl must be installed manually for the BMC Impact Event Adapters to start. You can either start the adapters through the Services option on Windows or execute the command ./etc/init.d/BMCImpactEventAdapter start on UNIX. For supported Perl versions for the BMC Impact Event Adapters, see the BMC ProactiveNet version 8.6.01 Compatibility and Support Matrix document at http://www.bmc.com/support.
Before you install a BMC ProactiveNet Agent on Red Hat Linux, you must install the following libraries: compat-libstdc++ RPMs XFree86-libs or xorg-x11-libs RPMs Even if you have a 64-bit operating system, you must install the 32-bit version of these libraries.
88
Installing the BMC ProactiveNet Agent remotely from the BMC ProactiveNet Operations Console
Follow the steps given below to download installation files from the BMC ProactiveNet Server to a remote UNIX-based BMC ProactiveNet Agent computer.
To use the BMC ProactiveNet Server as a source for agent files 1 From a BMC ProactiveNet Server computer, log on to the BMC ProactiveNet
Operations Console and navigate to the Options tab.
2 Open the Downloads tab. 3 From the BMC ProactiveNet Agent Software section, for the platform corresponding
to the computer on which you want to install the BMC ProactiveNet Agent, click Agent8.x.xx_byyy.tar (where x is the version number and y is the build number) and save the file to the computer where you want to install BMC ProactiveNet Agent.
4 From the BMC ProactiveNet Agent Software section, for the platform corresponding
to the computer on which you want to install the BMC ProactiveNet Agent, click BPPMAgentvrx.x_byyy.bin and save the file to the computer where you want to install BMC ProactiveNet Agent.
5 Execute BPPMAgentvrx.x_byyy.bin to start the installation. 6 If there are no agents installed on that computer, the BMC ProactiveNet Agent uses
port 12124 by default. If there are agents already installed, you can either upgrade an existing agent or install a new agent.
7 If you are installing a new agent you will be prompted for the port number on
which the agent will listen to. The port number should be in the range of 102465535.
8 On the Welcome screen, click Next or if you are installing multiple agents choose
Install a new instance of this application on the Existing Installed Instances Detected screen.
9 On the License Agreement screen, select I agree to the terms of the license agreement
and click Next. The pre-installation check utility verifies whether or not the computer meets the requirements for installing a BMC ProactiveNet Agent.
89
NOTE
While preparing to install, if you get a <setup>.bin: !: not found error, you can safely ignore the same.
or warnings listed in the Pre-install Validation Summary window, and restart the installation process. If you do not want to resolve the warnings click Next.
WARNING
Do not install the BMC ProactiveNet Agent in the /usr directory.
12 (This option is available on Solaris Sparc and Linux Red Hat platforms only) On the
Configuring Integration Service screen, you can enable the Integration Service to collect data from integration adapters such as BMC PATROL, Tivoli ITM, or HP Operations Manager. Perform one of the following actions:
s
NOTE
You can also enable the Integration Service after installation is complete. For instructions see, Enabling the Integration Service to gather data from products that integrate with BMC ProactiveNet on page 166. If you want to enable the Integration Service, select Yes, complete the following fields, and click Next.
Description Enter the port number of the Integration Service. The default is 3182. Enter and confirm the password for the Integration Service.
90
Field Cell Instance Name
Description Type the cell instance name. The default is hostname. Note: Hyphens and underscores are the only special characters allowed for cell instance names.
Cell Port Cell Encryption Key
Enter a port number in the range of 1024 to 65535. The default port for the cell is 1828. Enter the cell encryption key. The default is mc. No special characters are allowed.
NOTE
Cell is not supported in Solaris Intel X86 platform.

NOTE
91
Installing multiple BMC ProactiveNet Agents on single computer
18 If you are installing on the AIX platform, see Finishing the installation process on
the AIX platform on page 93.
NOTE
s
The BMC ProactiveNet Agent (UNIX) is supported on computers running Linux as a guest operating system installed using VMware. To replace a BMC Event and Impact Management cell, see Upgrade Guide.
Installing multiple BMC ProactiveNet Agents on single computer

NOTE
Installing multiple BMC ProactiveNet Agents on a single computer will put additional load on the computer in terms of CPU, IO, Memory, and TCP buffer.
By installing multiple BMC ProactiveNet Agents on a single computer, you can partition your monitoring into different domains and maximize hardware usage. Multiple BMC ProactiveNet Servers in different locations can connect to different BMC ProactiveNet Agents running on the same computer. Each agent can collect a different set of data authorized for its respective BMC ProactiveNet Server. You can choose to install a new instance of the agent. Alternatively, you can upgrade an existing agent by selecting from the list displayed. If you want to upgrade an existing BMC ProactiveNet Agent, see the Upgrade Guide.
NOTE
When installing multiple agents on a single computer, only the first agent installed is installed with a cell. Subsequent agent installations update the cell installed with the first agent.
To install multiple BMC ProactiveNet Agents 1 Run the BMC ProactiveNet Agent installation script setupagent.sh.
The script displays the list of agents already installed on the system, if any. BMC ProactiveNet Agents older than version 8.0.00 have an Agent ID of 0.
2 Choose to install a new agent on the system. 3 To continue installing another agent on the system, specify the path of the
directory where the agent must be installed.
Finishing the installation process on the AIX platform
4 Specify the control port number on which the agent must listen.
It is important that you specify an unused port number (between 0 and 65535). The port number you specify is assigned to the property pronet.apps.agent.port in the pronet.conf file. After you specify the port number, the agent installation continues.
5 If you are installing on the AIX platform, see Finishing the installation process on
the AIX platform on page 93.
NOTE
The computer requires time to update installation information. BMC recommends that you wait a minimum of five seconds between installations.
Finishing the installation process on the AIX platform

If you are installing the BMC ProactiveNet Agent on AIX, after the installation script is finished, copy the library libdb2.a from the DB2 Administration Client installation directory (InstanceHomeDirectory/sqllib/lib) into the /usr/lib directory, add the pronet.cell.enabled=true property in the /pw/custom/conf/pronet.conf file, and restart the BMC ProactiveNet Agent.
NOTE
AIX agents cannot be connected in TCP over SSL (secure TCP) mode.

After installation, to verify that the BMC ProactiveNet Agent is running, navigate to the installDirectory/pw/pronto/bin/ directory and execute pw agent status. Verify that the pronet_agent process is listed. If the pronet_agent process is not listed, execute pw agent start. This command restarts all the BMC ProactiveNet Agent processes.
93
If any exceptions occur, contact BMC Software customer support for assistance.
94
Chapter
Installing the Administration Console on remote computers

8
The BMC ProactiveNet Administration Console is automatically installed with the BMC ProactiveNet Server; however, you can install it on a remote computer by performing the appropriate procedure for your operating system.
Installing the BMC ProactiveNet Administration Console on Microsoft Windows

Before you begin
s s
Ensure that you have administrator privileges for the target computer. Ensure that .NET framework 2.0.050727 or above is installed on the target computer.
To install the BMC ProactiveNet Administration Console on a remote Microsoft Windows computer 1 From a BMC ProactiveNet Server computer, log on to the BMC ProactiveNet
Operations Console.
2 Click the Options link at the top right of the console and click on the Downloads tab. 3 From the BMC ProactiveNet Admin Software area, click Adminx.x_byyy.exe (where x
is the version and y is the build number) and save the file to the computer to which you are installing the BMC ProactiveNet Administration Console.
4 On the computer where you are installing the BMC ProactiveNet Administration
Console, double-click the Adminx.x_byyy.exe file.
Chapter 8
95
Launching the Administration Console on Microsoft Windows computers
5 On the Welcome screen of the BMC ProactiveNet Admin installer, click Next. 6 Accept the license agreement and click Next. 7 Enter the directory where you want to install the administration console or accept
the default and click Next.
8 On the Installation Preview screen, click Install.
Launching the Administration Console on Microsoft Windows computers

Use the following procedure to verify the installation.
To launch Administration Console 1 On the Windows desktop, go to Start => Programs => BMC ProactiveNet Server =>
BMC ProactiveNet Admin.
2 On the Logon screen, enter the following details:

s
Server: Specify the name/IP Address of BMC ProactiveNet Server to which you want to connect. Username: Specify the name of the user account to access BMC ProactiveNet. Default user name is admin. Password: Specify the corresponding password for the user account. Default password is admin.
NOTE
To change the password, see Adding Agents on page 155.
Connection: Select the connection type. Either Direct (uses port 1099 and 12128*) or HTTP Tunnel (uses port 80).
A firewall may exist between the desktop and the BMC ProactiveNet Server in the datacenter. Sometimes the firewall allows only port 80 and does not allow port 1099 and 12128, in such cases you may be forced to use the HTTP Tunnel mode.
96
Installing the BMC ProactiveNet Administration Console on Solaris
HTTP Tunnel connection is approximately three times slower than a Direct Connection, although this varies depending on the latency between client and server and also the speed of the client and server computers. When connection fails with HTTP Tunnel, restart the Administration Console to log in again.
3 Click Ok to view the Administration Console.

On successful validation, the Administration Console opens. If you attempt to view online Help from the Administration Console and use Internet Explorer as your browser, you are first prompted to update Trusted site registration to allow Internet Explorer to open the Help page as a Trusted site zone. After you update the registration, you must subsequently refresh the page to view the Help from the registered Trusted site zone.
Installing the BMC ProactiveNet Administration Console on Solaris

Before you begin
Ensure that the DISPLAY variable is set by entering the following command:
setenv DISPLAY ProactiveNetServerIPaddress
To install the BMC ProactiveNet Administration Console on Solaris 1 From a BMC ProactiveNet Server computer, log on to the BMC ProactiveNet
Operations Console.
2 Click the Options link at the top right of the console and click on the Downloads tab. 3 From the BMC ProactiveNet Admin Software area, click setup_admin.bin and save
the file to the computer to which you are installing the BMC ProactiveNet Administration Console.
4 On the computer where you are installing the BMC ProactiveNet Administration
Console, execute the setup_admin.bin installation script.
5 Read and accept the license agreement. 6 Enter the directory where you want to install the administration console or accept
the default.
Chapter 8 Installing the Administration Console on remote computers 97
Launching the Administration Console on Solaris
7 Enter Y to confirm that you want to begin the installation.
Launching the Administration Console on Solaris

Use the following procedure to verify the installation.
To launch Administration Console and test the installation 1 Open the command line prompt. 2 Run the following commands:
cd installDirectory/pw/pronto/bin/ ./pw admin
3 On the Logon screen, enter the following details:

s
Server: Specify the name/IP Address of BMC ProactiveNet Server to which you want to connect. Username: Specify the name of the user account to access BMC ProactiveNet. Default user name is admin. Password: Specify the corresponding password for the user account. Default password is admin.
NOTE
To change the password, see Adding Agents on page 155.
Connection: Select the connection type. Either Direct (uses port 1099 and 12128*) or HTTP Tunnel (uses port 80).
A firewall may exist between the desktop and the BMC ProactiveNet Server in the datacenter. Sometimes the firewall allows only port 80 and does not allow port 1099 and 12128, in such cases you may be forced to use the HTTP Tunnel mode. An HTTP Tunnel connection is approximately three times slower than a Direct Connection, although this varies depending on the latency between client and server and also the speed of the client and server computers. If a connection fails with HTTP Tunnel, launch the Administration Console to log in again.
98
Installing multiple Administration Consoles
4 Click Ok to view the Administration Console.

On successful validation, the Administration Console opens. If you attempt to view online Help from the Administration Console and use Internet Explorer as your browser, you are first prompted to update Trusted site registration to allow Internet Explorer to open the Help page as a Trusted site zone. After you update the registration, you must subsequently refresh the page to view the Help from the registered Trusted site zone.

Administration Consoles from different versions of BMC ProactiveNet releases can be installed and used on the same computer. During Administration Console installation, BMC ProactiveNet checks for existing installations of the Administration Console. If an older version of the Administration Console is available on the computer, BMC ProactiveNet displays the following message: ProactiveNet Admin is already installed in the system. This installation will be a fresh installation and will not upgrade previous Admin. All installations of BMC ProactiveNet Administration Console are treated as fresh installations. After installation is complete, you can use the older installation to access the corresponding BMC ProactiveNet Server and the new installation to connect and use the new BMC ProactiveNet Server.
NOTE
You cannot upgrade the Administration Console.
Chapter 8
99
100
Chapter
Unattended installation
This approach helps you install the BMC ProactiveNet Server and BMC ProactiveNet Agent unattended.
NOTE
s s
Unattended installation of the BMC ProactiveNet Server and BMC ProactiveNet Agent in high-availability mode is not supported. It is recommended to perform an unattended installation only for fresh installation.
Installing the BMC ProactiveNet Server on Microsoft Windows

To perform an unattended installation 1 From the command prompt, navigate to the setup.cmd file under the following
directory:
<install directory>ServerWin_pw_vrxx_bXX\BPPMServer\Disk1\
2 Create the filename.options file as in the sample file provided in Figure 3 on

page 103 and Figure 4 on page 104. You can copy the options from this sample file into a text pad, save it to filename.options file and customize accordingly.
3 To install the BMC ProactiveNet Server using the filename.options file, enter the
following command at the command prompt:
setup.cmd -i silent -DOPTIONS_FILE=path\filename.options
Chapter 9 Unattended installation
101
Encrypting passwords in the options file
NOTE
Installation related information is not displayed on the console when unattended installation begins. However, installation occurs in the background. The installation progress is logged in a temporary folder during installation. Go to Start => Run and key in %temp% in the Open field to refer to the bppm_server_install.log.

For manual unattended installation, execute the following command to run the Maintenance Tool and get the encrypted passwords. Run the tool on a machine that has JRE installed. Use the encrypted passwords in the Options file before starting the installation.
BPPMServer\Disk1\utility>BPPMServerMaintenanceTool.cmd -silent -encrypt -encrypt password=<Enter password> -confirm_password=<Enter password>
Following is a sample options file. Uncomment the properties that are required.
102
Figure 3
Sample of filename.options file - Part 1 of 2
-P installLocation=<INSTALL DIR> -A SERVER # #******************************************************************************* # UDDI OPTIONS - Uncommnet the properties in the following section and provide #valid inputs if you need the UDDI service #******************************************************************************* #-J USER_HAS_UDDI_SERVER=<true/false> #-J UDDI_HOSTNAME=<UDDI server Host name> #-J UDDI_PORT=<UDDI Server port> #-J UDDI_LOGIN=<UDDI User Name> #-J UDDI_PASSWORD=<UDDI Server password> #-J CONFIRM_UDDI_PASSWORD=<UDDI Server confirm password> # #******************************************************************************* # BLADELOGIC OPTIONS - Uncommnet the properties in the following section and #provide valid inputs to integrate with BladeLogic. If UDDI is enabled, #BL_HOSTNAME and BL_PORT options should be commented. # #******************************************************************************* #-J USER_HAS_BL_SERVER=true #-J BL_HOSTNAME=< Blade logic server host name> #-J BL_PORT=< Blade logic Server port> #-J BL_LOGIN=< Blade logic user name> #-J BL_PASSWORD= < Blade logic password> #-J CONFIRM_BL_PASSWORD=< Blade logic password> #-J BL_ROLE=<Blade logic role> # #******************************************************************************* # CMDB OPTIONS - Uncommnet the properties in the following section and provide #valid inputs to integrate with CMDB # #******************************************************************************* # -J USER_HAS_CMDB_SERVER=<true/false> # -J NEW_CMDB_HOSTNAME=<CMDB server Host name> # -J NEW_CMDB_PORT=<CMDB Server port> # -J NEW_CMDB_LOGIN=<CMDB User Name> # -J NEW_CMDB_PASSWORD=<CMDB Server password> # -J NEW_CONFIRM_CMDB_PASSWORD=<CMDB Server confirm password> # -J NEW_CMDB_VERSION=<CMDB Version (7.5 | 7.6 | 7.6.03 | 7.6.04)> #******************************************************************************* # ADMIN CELL & MCELL OPTIONS - This is mandatory. Provide the valid inputs to #configure the cell #******************************************************************************* -J SIM_CELL_INSTANCE_NAME=<SIM cell instance name (pncell_<hostname>> -J SIM_CELL_PORT=<SIM cell port (1828)> -J SIM_CELL_ENC_KEY=<SIM cell encryption key (mc)> -J BPPM_ADMIN_CELL_PORT=<Admin cell port (1827)> -J ADMIN_CELL_ENC_KEY=<Admin cell encryption key (mc)>
103
Figure 4
Sample of filename.options file - Part 2 of 2
# #******************************************************************************* # ADMINISTRATOR INFO OPTIONS - Uncommnet the properties in the following section #and provide valid inputs to configure the Administrator information for #receiving emails # #******************************************************************************* # -J SENDER_EMAIL_ID=<Sender email id> # -J ADMIN_EMAIL_ID=<Administrator email id> # -J SMTP_SERVER_NAME=<SMTP Server name> # #******************************************************************************* # ORACLE SUPPORT OPTIONS - Uncommnet the properties in the following section and #provide valid inputs to configure Oracle as the backend. If the options are #commented Sybase will be installed as backend by default. # #******************************************************************************* #-J USE_ORACLE_DATABASE=<true/false> #-J ORACLE_HOSTNAME=<hostname> #-J ORACLE_PORT=1521 #-J ORACLE_SID=<sid> #-J ORACLE_USER=<username> #-J ORACLE_PASSWORD=<password> #-J ORACLE_CONFIRM_PASSWORD=<password> # # #****************************************************************************** # PACKAGE_INSTALLATION_REPOSITORY OPTIONS - Uncommnet the properties in the #following section and provide valid inputs to configure the package installation #repository # #****************************************************************************** # # -J INSTALL_PACKAGE_INSTALLATION_REPOSITORY=<true|false> # -J PACKAGE_INSTALLATION_REPOSITORY_SOURCE_PATH=<Source path> # -J PACKAGE_INSTALLATION_REPOSITORY_DESTINATION_PATH=<Destination path>
For example, to configure the package installation repository section you can uncomment the properties as follows:
-J INSTALL_PACKAGE_INSTALLATION_REPOSITORY=true -J PACKAGE_INSTALLATION_REPOSITORY_SOURCE_PATH=C:/repository -J PACKAGE_INSTALLATION_REPOSITORY_DESTINATION_PATH=C:/program files/bmc software/proactivenet/pw/pproxy
104
Installing the BMC ProactiveNet Agent on Microsoft Windows
Installing the BMC ProactiveNet Agent on Microsoft Windows

To perform an unattended installation on a local computer 1 From a command prompt, navigate to the BPPMAgentx.x_bxyz.exe file available
under the following directory:
<install directory>\pw\pronto\web\html\download\
2 Go to the filename.option files available under <install

directory>ServerWin_pw_vrxx_bXX and customize the filename.options file as required. For a list of parameters that you can customize, refer to the sample in Figure 5 on page 106.
3 To install a remote agent on the local machine using the fileName.options file, enter
the following command at the command prompt:
BPPMAgentx.x_byyyy.exe -i silent -DOPTIONS_FILE=path\filename.options
NOTE
Installation related information is not displayed on the console when unattended installation begins. However, installation occurs in the background. The installation progress is logged in a temporary folder during installation. Go to Start > Run and key in %temp% in the Open field to refer to the bppm_agent_install.log.
For information on encrypting the passwords that are required in the options file for unattended installation, refer to Encrypting passwords in the options file on page 102.
105
Installing BMC ProactiveNet Server on Solaris
Figure 5
Sample of filename.options file for BMC ProactiveNet Agent
#The install directory must be specified in the below property. -P installLocation=<INSTALL DIR> -A AGENT #****************************************************************************** # Agent port #-J AGENT_PORT=<Agent Port> ##****************************************************************************** #####Patrol proxy setting - Uncommnet the properties in the following section and #provide valid inputs to configure the Integration Service. For multiple agents, #configure the Integration Service to False on Windows only,if it is already enabled. #-J PATROL_PROXY_SELECTED=<true/false> #-J PATROL_PROXY_PORT=<Patrol proxy port> #-J PATROL_PROXY_PASSWORD=<Patrol proxy password> #-J PATROL_PROXY_CONFIRM_PASSWORD=<Patrol proxy confirm password> #****************************************************************************** #####Tunnel Agent setting -Uncommnet the properties in the following section and #provide valid inputs to configure the agent in tunnel mode # #-J TUNNEL_AGENT_SELECTED=<true/false> #-J TUNNEL_AGENT_ID=<Tunnel ID> #-J TUNNEL_AGENT_SERVER_NAME=<Server Host Name> #-J TUNNEL_AGENT_HTTPS_SELECTED=<true/false> #****************************************************************************** # #####Cell Setting - Uncommnet the properties in the following section and #provide valid inputs to configure the cell #-J CELL_NAME=<Host Name> #-J CELL_PORT=<Cell Port> #-J CELL_KEY=mc #****************************************************************************** #####Following properties are used to set Migrated KB Path and is applicable in #upgrade only. #-J MIGRATED_KB=<true/false> #-J MIGRATED_KB_HOME=<KB migration path>
Installing BMC ProactiveNet Server on Solaris

To perform an unattended installation 1 From a command prompt, navigate to the setup.bin under the following directory:
<install directory>Server_pw_vrxx_bXX/BPPMServer/Disk1/Instdata/VM/
106
Installing BMC ProactiveNet Agent on UNIX based systems
2 Go to the fileName.option files available under <install

directory>Server_pw_vrxx_bXX and customize the fileName.options file as required. For a list of parameters that you can customize, refer to the sample in Figure 3 on page 103.
3 To install the BMC ProactiveNet Server using the fileName.options file, enter the
following command at the command prompt:
./setup.bin -i silent -DOPTIONS_FILE=path/filename.options
Installing BMC ProactiveNet Agent on UNIX based systems

1 Go to the folder where you have installed the BMC ProactiveNet Agent and locate
the setup.bin.
1 From a command prompt, navigate to the BPPMAgentx.x_bxyz.bin file available

under the following directory: UNIX: <install directory>/pw/pronto/web/html/download/
2 Execute the following command:

./setup.bin -i silent -DOPTIONS_FILE=path/filename.options
Uninstalling the BMC ProactiveNet Server on Microsoft Windows

1 Go to the folder where you have installed the BMC ProactiveNet Server <install
directory>\uninstallBPPMServer\ and locate the uninstall.exe file.
107
Uninstalling the BMC ProactiveNet Agent on Microsoft Windows
uninstall.exe -i silent
NOTE
Uninstallation related information is not displayed on the console when unattended uninstallation begins. However, uninstallation occurs in the background.
Uninstalling the BMC ProactiveNet Agent on Microsoft Windows

1 Go to the folder where you have installed the BMC ProactiveNet Agent <install
directory>\uninstallBPPMAgent\ and locate the uninstall.exe file.

uninstall.exe -i silent
NOTE
Uninstalling the BMC ProactiveNet Server on Solaris

1 Go to the folder where you have installed the BMC ProactiveNet Server <install
directory>\UninstallBPPMServer\ and locate the uninstall file.

./uninstall -i silent
NOTE
Uninstallation related information is not displayed on the console when unattended uninstallation begins. However, uninstallation occurs in the background. The installation progress is logged in a temporary folder during installation.
108
Uninstalling the BMC ProactiveNet Agent on Solaris

1 Go to the folder where you have installed the BMC ProactiveNet Agent <install
directory>\UninstallBPPMAgent\ and locate the uninstall file.

./uninstall -i silent
NOTE
109
110
Chapter
10
Installing BMC ProactiveNet in highavailability mode on Windows

10
You can install both the BMC ProactiveNet Server and BMC ProactiveNet Agent in high-availability mode. For information on high-availability architecture, refer to Preparing to install BMC ProactiveNet in high-availability mode on page 37.
Installing BMC ProactiveNet Server on a primary node

You can manually install the BMC ProactiveNet Server and BMC ProactiveNet Agent on the primary node. Failover is handled automatically by Microsoft Clustering services.
Before you begin

s
Ensure that the cluster configuration is of node and cluster disk majority type. Ensure that a visible quorum disk is available. Ensure that the installables are not copied to the shared disk.
To install the BMC ProactiveNet Server as a primary node on Microsoft Windows 1 At the command prompt from the <install
directory>ServerWin_pw_vrxx_byyyy\BPPMServer\Disk1\setup.cmd directory
(where x.x is the version number and yyyy is the build number), run the following command:
setup.cmd -DINSTALL_TYPE=PRIMARY Chapter 10 Installing BMC ProactiveNet in high-availability mode on Windows 111
2 Follow the procedure from step 2 in the Installing BMC ProactiveNet Server on
3 On the Installation Summary screen, click Done to complete the installation. The
installation screen will disappear after the BMC ProactiveNet Server is brought down. When the BMC ProactiveNet Server installation is complete, you can choose View

To install Oracle as the database 1 Follow the procedure until step 3 in the Installing BMC ProactiveNet Server on

112
NOTE
NOTE
Chapter 10
Installing BMC ProactiveNet in high-availability mode on Windows
113
Installing BMC ProactiveNet Server on a standby node


installation.
8 Continue with the installation from step 4 in the Installing BMC ProactiveNet
Server on Microsoft Windows on page 59. For more information on creating and setting up the Oracle database, see Preparing to install BMC ProactiveNet Performance Management with Oracle database on page 44.
Installing BMC ProactiveNet Server on a standby node

The following procedures explain how to install the BMC ProactiveNet Server and agent on a standby node. Failover is handled automatically by Microsoft Clustering services.
To install the BMC ProactiveNet Server as a standby node on Microsoft Windows 1 Ensure that the BMC ProactiveNet Server is shut down on the primary node. If the
BMC ProactiveNet Server is running, see Stopping the BMC ProactiveNet Server on page 164.
2 Move cluster control to the standby node computer.
114
Creating dependencies for BMC ProactiveNet Server cluster resource
3 On the computer hosting the standby node, from a command prompt access the
<install directory>ServerWin_pw_vrxx_byyyy\BPPMServer\Disk1\setup.cmd
directory (where x.x is the version number and yyyy is the build number) and run the following command:
setup.cmd -DINSTALL_TYPE=SECONDARY

To agree to the license agreement, select I agree to the terms of the license agreement on the Read the License Agreement and Select the Appropriate Option screen, and click Next .

When the BMC ProactiveNet Server installation is complete, you can choose View
6 Restart both the primary and the standby nodes after Creating dependencies for
BMC ProactiveNet Server cluster resource on page 115.
NOTE
The BMC ProactiveNet Server takes time to come up during failover, as it runs on a Microsoft active-passive cluster. If the BMC ProactiveNet Server (cluster resource) does not come up, select the online option to manually set the status.
Creating dependencies for BMC ProactiveNet Server cluster resource

Use the following procedure to create dependencies for a ProactiveNet server cluster resource.
To create dependencies for Windows cluster 2003 1 Stop the BMC ProactiveNet Server using the pw system stop command. 2 Go to Start =>All Programs => Administrative Tools => Cluster Administrator and
click on the cluster name.
3 Click Resources.
A list of cluster resources is displayed.
Chapter 10
115
Installing the BMC ProactiveNet Agent in high-availability mode on Microsoft Windows
4 Right-click on the PnService and select Properties. 5 Click the Dependencies tab in the PnService Properties window and click Modify. 6 From the list of Available Resources move the resources you want to Dependencies
and click OK.
7 Restart the BMC ProactiveNet Server using the pw system start command. To create dependencies for Windows cluster 2008 1 Stop the BMC ProactiveNet Server using the pw system stop command. 2 Go to Start =>All Programs => Administrative Tools => Failover Cluster Manager and
3 Scroll down to Cluster Core Resources and select Properties. 4 Click the Dependencies tab in the PnService Properties window and click Insert to
add a resource.
5 Select the cluster name as a resource and click Insert. 6 Select the cluster resource with AND option. Similarly add all the resources. 7 Click Apply and OK. 8 Restart the BMC ProactiveNet Server using the pw system start command.

For high-availability, you must install the BMC ProactiveNet Agent on a primary and secondary node.
To install the BMC ProactiveNet Agent as a primary node on Microsoft Windows 1 Login to a virtual node (assuming cluster service is started on both the cluster
nodes).
2 Ensure that you are on the primary node.
116
3 Copy the BMC ProactiveNet agent installer (BPPMAgentvrx.x_byyy.exe ) on the

local drive (for example, C:\)
4 Set the environment variable PATROL_VIRTUALNAME=<Virtual IP address of

Cluster>.
5 At the command prompt, access the BPPMAgentvrx.x_byyy.exe (where x.x is the

version number and yyyy is the build number) file under BPPMAgent\windows directory.

BPPMAgentvrx.x_byyy.exe -DINSTALL_TYPE=PRIMARY
7 Installation should be carried out on the shared drive. 8 On the Welcome screen, click Next.
On the License Agreement screen, select I agree to the terms of the license agreement and click Next. The pre-installation check utility verifies whether or not the computer meets the requirements for installing a BMC ProactiveNet Agent.
or warnings listed in the Pre-install Validation Summary window, and restart the installation process. If you do not want to resolve the warnings click Next. If Microsoft .NET Framework is not found on the computer a warning is displayed. Install Microsoft .NET Framework version 3.0 using the Role Management tool.
WARNING
Do not install the product in a root directory (for example, C:\ or D:\), shared drive, or directly under the Documents and Settings folder.
11 On the Installation Preview screen where the installation details are displayed,
click Next.
12 On the Configuring Integration Service screen, you can enable the Integration
Service to collect data from integration adapters such as BMC PATROL, Tivoli ITM, or HP Operations Manager. Perform one of the following actions:
Chapter 10
117
NOTE
You can also enable the Integration Service after installation is complete. For instructions, see Enabling the Integration Service to gather data from products that integrate with BMC ProactiveNet on page 166. If you want to enable the Integration Service, select Yes, complete the following fields, and click Next.
Description Enter the port number of the Integration Service. The default is 3182. Enter and confirm the password for the Integration Service

Field Instance Name Description Type the cell instance name. The default is hostname. Note: Hyphens and underscores are the only special characters allowed for cell instance names. Port Encryption Key Enter a port number in the range of 1024 to 65535. The default port for the cell is 1828. Enter the cell encryption key. The default is mc. No special characters are allowed.

118
NOTE
Done to exit the agent installation. A message that the installation is complete on the primary node displays. You will be prompted to install on the standy node.
NOTE
s
If you modify the control port of an agent explicitly through the pronet.conf file, the port number is not updated in the Add/Remove Programs applet and in the Agent Service display name. If you modify the control port, the port number will not be displayed when you use Add/Remove Programs Each BMC ProactiveNet Agent on a system runs in a separate JVM. You can check the version of the BMC ProactiveNet Agent under installationDirectory\Agent\Pronto\Bin\AGENT_VERSION.
s s
To install the BMC ProactiveNet Agent as a standby node on Microsoft Windows 1 Login to virtual node (assuming cluster service is started on both the cluster
nodes).
2 Ensure that you are on the standby node. 3 Copy the BMC ProactiveNet agent installer (BPPMAgentx.x_yyyy.exe) on the local
drive (for example, C:\).
4 Set the environment variable PATROL_VIRTUALNAME=<Virtual IP address of

Cluster>.
5 At the command prompt, access the BPPMAgentvrx.x_byyy.exe (where x.x is the

version number and yyyy is the build number) file under proactiveagent\windows directory.
Chapter 10
119
Creating dependencies for a BMC ProactiveNet Agent cluster resource

BPPMAgentvrx.x_byyy.exe -DINSTALL_TYPE=SECONDARY
7 Installation will be carried out on the shared drive. 8 On the Installation Summary screen, click View Log to view the log file and click
9 Restart both the primary and the standby nodes after Creating dependencies for a
BMC ProactiveNet Agent cluster resource on page 120. If the agent services do not start, manually bring it up by starting the agent service.
NOTE
s
The BMC ProactiveNet Agent takes time to come up during failover, as it runs on a Microsoft active-passive cluster. If the BMC ProactiveNet Agent (cluster resource) does not come up, select the online option to manually set the status. After the BMC ProactiveNet agent is installed on both the primary and standby nodes, a resource ProNetAgent will be created on the cluster. For Top IP traffic to work on a remote Windows 2008 R2 64 bit agent, go to www.winpcap.org, down load WinPcap, and execute the file on standby node.
To add a BMC ProactiveNet Agent on the cluster

Add the BMC ProactiveNet Agent to the BMC ProactiveNet Server as a virtual IP of the cluster.

Use the following procedure to create dependencies for a BMC ProactiveNet Agent cluster resource.
To create dependencies for Windows cluster 2003 1 Stop the BMC ProactiveNet Server using the pw system stop command. 2 Go to Start =>All Programs => Administrative Tools => Cluster Administrator and
click the name of the cluster for which you want to create dependencies.
3 Click Resources.
120
A list of cluster resources is displayed.
4 Right-click ProNetAgent and select Properties. 5 Click the Dependencies tab in the ProNetAgent Properties window and click
Modify.
6 From the list of Available Resources, move the resources you want to Dependencies
and click OK.
7 Restart the BMC ProactiveNet Server and Agent using pw system start command. To create dependencies for Windows cluster 2008 1 Stop the BMC ProactiveNet Server and Agent using the pw system stop command. 2 Go to Start =>All Programs => Administrative Tools => Failover Cluster Manager and
3 Scroll down to Cluster Core Resources and select Properties. 4 Click on to Dependencies tab in the ProNetAgent Properties window and click
Insert to add a resource.
5 Select the cluster name as a resource and click Insert. 6 Select the cluster resource with AND option. Similarly add all the resources. 7 Click Apply and OK. 8 Restart the BMC ProactiveNet Server and Agent using the pw system start
command.
Chapter 10
121
122
Chapter
11
Installing BMC ProactiveNet in highavailability mode on Solaris

11
This chapter provides instructions to install the BMC ProactiveNet Server in highavailability mode for the first time. For information about high-availability architecture, see Preparing to install BMC ProactiveNet in high-availability mode on page 37.
High-availability workflow
Figure 6 on page 124 provides an overview of the tasks that you must perform to install and enable BMC ProactiveNet in high-availability mode on UNIX computers.
Chapter 11
Installing BMC ProactiveNet in high-availability mode on Solaris
123
High-availability workflow
Figure 6
Workflow to install and enable BMC ProactiveNet in high-availability mode on Solaris

High-availability installation begins
Install the BMC ProactiveNet Server as a primary and standby node. For more information, see Installing BMC ProactiveNet in highavailability mode on Solaris on page 125.
Create BMC ProactiveNet application resource type. For more information, see Creating the BMC ProactiveNet resource type on page 178.
Configure the resource type created for a Sun cluster. For more information, see Configuring the resource type on page 179.
Create the resource group. For more information, see Creating the resource group on page 180.
Customize the scripts to achieve BMC ProactiveNet application failover. For more information, see Customizing the scripts to achieve BMC ProactiveNet application high-availability on page 183.
Stop the BMC ProactiveNet Server pw sys stop. For more information, see Stopping the BMC ProactiveNet Server on page 164.
Bring the resource group online. For more information, see Bringing a resource group online on page 187.
High-availability installation ends.
124
Installing BMC ProactiveNet in highavailability mode on Solaris

The following applications are required to control high-availability for BMC ProactiveNet on Solaris:
s s
Sun Cluster software BMC ProactiveNet
To install the BMC ProactiveNet Server as a primary and standby node on Solaris 1 Change the host name of the primary node to the logical host name configured for
the cluster by entering the following command:
hostname logicalHostName
2 Change the ip address of the primary node to the logical ip address configured for
the cluster by entering the following commands:
ifconfig <alias interface> plumb example: ifconfig hme0:1 plumb ifconfig <alias interface> <logical ip> netmask <netmask> up example: ifconfig hme0:1 10.129.5.252 netmask 255.255.252.0 up
3 Install the BMC ProactiveNet Server on the primary node.

During the installation, choose the cluster file system (/global) that is shared on both nodes as the installation location. The installation is completed successfully.
4 After successful installation of the BMC ProactiveNet Server, change the logical
host name back to the host name of the primary node by entering the following command from a command line:
hostname primaryHostName
5 After successful installation of the BMC ProactiveNet Server, change the logical ip
address back to the ip address of the primary node by entering the following command from a command line:
ifconfig <alias interface> down example: ifconfig hme0:1 down ifconfig <alias interface> unplumb example: ifconfig hme0:1 unplumb
Chapter 11
125
6 On the primary node, remove the following files so that the BMC ProactiveNet
application does not start:
s s s
/etc/rc3.d/S81pronto /etc/rc0.d/K09pronto /etc/rc1.d/K09pronto
7 On the standby node, create the required links for the BMC ProactiveNet Server by
entering the following commands:
ln s /serverInstallDirectory/pw/usr/pw ln s /usr/pw/pronto /usr/pronto ln s /usr/pw/pronto/bin/pw /bin/pw
For information on post-installation tasks, refer to 15Configuring and using BMC ProactiveNet in high-availability mode on page 177
126
Chapter
12
Introduction to the BMC ProactiveNet interfaces

12
This chapter provides an overview of the BMC ProactiveNet interfaces and how to access each interface.
Deciding which interface to use

BMC ProactiveNet provides the following interfaces:
s s s s s
BMC ProactiveNet Administration Console BMC ProactiveNet Operations Console BMC ProactiveNet Command Line Interface (CLI) BMC ProactiveNet Service Level Objectives (SLO) Console Use to determine which console you should use to perform
Administering BMC ProactiveNet

BMC ProactiveNet administrative functions allow you to modify and manage the BMC ProactiveNet Server and the BMC ProactiveNet Agent network management areas. Using one or more of the ProactiveNet administrative interfaces you can add or delete users, groups, monitored devices, applications, and services, or change event notifications and thresholds.
Chapter 12
127
BMC ProactiveNet profiles
You can access BMC ProactiveNet administrative functions in the following ways:
s s s
the BMC ProactiveNet Administration Console the Command Line Interface (CLI) the BMC ProactiveNet Operations Console
NOTE
Although most administrative functions are accessed using the Administration Console, some administrative options are also available through the BMC ProactiveNet Operations Console. For details, see the BMC ProactiveNet User Guide.
For details about using the Administration CLI commands, see the BMC ProactiveNet Command Line Interface Reference Manual.
BMC ProactiveNet profiles

BMC ProactiveNet acknowledges the following profiles when logging into the product:
s s
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 from accessing 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 user assign access rights at both micro and macro levels.
128

The following sections explain how to launch the Administration Console and provide basic information for navigating the console.
Connecting the BMC ProactiveNet Administration Console to the BMC ProactiveNet Server
The BMC ProactiveNet Administration Console can connect to the BMC ProactiveNet Server using one of the following methods:
s
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.
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 about Secure Login, see the BMC ProactiveNet Administrator Guide.
Launching the BMC ProactiveNet Administration Console

Perform the appropriate procedure to start the Administration Console on your operating system.
Chapter 12
129
Launching the BMC ProactiveNet Administration Console
To launch the BMC ProactiveNet Administration Console from a Microsoft Windows computer 1 On the computer where the BMC ProactiveNet Server is installed, go to Start =>
Programs => BMC Proactive Server => BMC ProactiveNet Admin.
2 In the BMC ProactiveNet Administration Console Logon screen, specify the

following information:
s
name or IP Address of the BMC ProactiveNet Server computer to which you want to connect user name with access rights to the BMC ProactiveNet Server. The default is admin. password corresponding to the user name. The default is admin. type of connection to use to connect to the BMC ProactiveNet Server, either Direct or HTTP Tunnel. For details about the connection types, see Connecting the BMC ProactiveNet Administration Console to the BMC ProactiveNet Server on page 129.
3 Click OK.
The BMC ProactiveNet Administration Console is displayed.
To launch the BMC ProactiveNet Administration Console from a Solaris computer 1 On the Solaris computer where the BMC ProactiveNet Server is installed, at a
command prompt, enter the following command:
pw admin
NOTE
For remote utilization of the 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.
name or IP Address of the BMC ProactiveNet Server computer to which you want to connect user name with access rights to the BMC ProactiveNet Server. The default is admin. password corresponding to the user name. The default is admin.
130
Logging out of and into the BMC ProactiveNet Server from the BMC ProactiveNet Administration Console
type of connection to use to connect to the BMC ProactiveNet Server, either Direct or HTTP Tunnel. For details about the connection types, see Connecting the BMC ProactiveNet Administration Console to the BMC ProactiveNet Server on page 129.
2 Click OK.
The BMC ProactiveNet Administration Console is displayed.
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 1 From the menu bar of the BMC ProactiveNet Administration Console, choose
Server => Logout.
2 In the Logout Confirmation dialog box, click Yes. To log on to the BMC ProactiveNet Server from the Administration Console 1 From the menu bar of the BMC ProactiveNet Administration Console, choose
Server => Login.
2 In the BMC ProactiveNet Administration Console Logon screen, 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.
Navigating the BMC ProactiveNet Administration Console

The Administration Console has two main tabs:
s
Administrationuse this tab for general administration of user accounts and other
ProactiveNet administration tasks, working with event management policies, working with dynamic data using the Dynamic Data Editor, and administering the BMC ProactiveNet infrastructure, such as agents and cells
Chapter 12
131
Services Editoruse this tab to edit services. This tab provides service editing
functionality only; it does not display service impact or CI status. That functionality is provided by the Operations Console.
Administration tab
The Administration tab includes the following sub-tabs, identified by these icons:
s
General Administration Event Management Policies Dynamic Data Editor

BPPM
Infrastructure Management
Service 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. For more information, see the For more information about using the BMC ProactiveNet Administration Console to monitor services, see the BMC ProactiveNet Administrator Guide.

The day-to-day operations of BMC ProactiveNet are preformed using the BMC ProactiveNet Operations Console. The following sections explain how to launch the Operations Console and provide a brief overview of the Operations Console interface. For details about using the Operations Console, see the BMC ProactiveNet User Guide.
132
Launching the BMC ProactiveNet Operations Console
Launching the BMC ProactiveNet Operations Console

The BMC ProactiveNet Server is a web-based application and you can access it by logging on to the BMC ProactiveNet Operations Console using the web browsers specified in the BMC ProactiveNet version 8.6.01 Compatibility and Support Matrix document.
NOTE
Avoid multiple log-ins using the same browser, user name, and password, and launching different tabs within the same browser, as this might result in NO DATA or other unpredictable results. For multiple log-ins, open separate browser windows.
To launch to the BMC ProactiveNet Operations Console 1 Open a web browser. 2 Enter the host name or IP address of the BMC ProactiveNet Server. 3 In the BMC ProactiveNet Logon screen, enter a valid user name and password.
If you are logging on for the first time after installation, use the following default values:
s s
user name: admin password: admin
NOTE
The default protocol for this connection is HTTP. To log on using a secure HTTPS connection, click the link Switch to Secure Mode on the log on page. If you use HTTPS, BMC ProactiveNet encrypts the information relay from the Web interface for additional security. Secure connection mode is indicated by the message: You are using a secure connection now.
4 Click Log On.
Navigating the BMC ProactiveNet Operations Console

Figure 7 shows the default view in the BMC ProactiveNet Operations Console and the major areas within this console.
Chapter 12
133
Figure 7
Navigation Tree
Event and component folders
Navigation Drawers
Navigation tree
The navigation tree shows an at-a-glance synopsis of the events and views. Event and component folders are displayed in a hierarchical manner in the navigation tree. The folders displayed in the navigation tree are divided into the following categories:
s
Global: When you create a folder under this node, all BMC ProactiveNet users can view and access that folder. My Folders: When you create a folder under this node, only you can view and access that folder.
To further organize your display, beneath these top-level folders you can add event and component folders, including folders for Component Instances (CIs) associated with a service model. Your ability to add event and component folders depends on your permissions.
134
Table 2 on page 21 shows the icons for the objects in the navigation tree and provides a description for each object. Table 3 Navigation tree objects and definitions
Navigation tree top-level node (Global). The Global node contains the following default collectors:
s s s s s
Object icon Name and definition
All Event Collectorsdisplays the entire event collector hierarchy All Abnormalitiesdisplays all the abnormality events All Servicesdisplays all the services All Groupsdisplays all the groups All Devicesdisplays all the devices
Based on permissions, users can create event and component folders under this node to organize the event view. Navigation tree top-level node (Mine). Based on permissions, users can create event and component folders under this node to organize the event view. Event group collector; an event group subnode of the navigation tree top-level node or another event group node Child collector node Child group node Child service node
In the navigation tree, the severity icons for a collector dynamically change depending on the severity level of the events for that collector. For example, if there is a Critical event on one of the devices, then the green icon changes to a red icon, indicating a Critical event. This allows you to see the status of devices on your system immediately. For more information about event severity and status, see the BMC ProactiveNet User Guide.
Navigation drawers
In the navigation pane in the Operations Console is a series of drawers that enable you to navigate through BMC ProactiveNet functions and views. You can select which drawers that you want displayed in the navigation pane.
Chapter 12
135
Table 7 on page 25 describes the available drawers in the navigation pane and describes their functions. For more information about these drawers, see the BMC ProactiveNet User Guide. Table 4
Drawer Main Other cells Reports
Operations Console navigation drawers and descriptions

Description provides access to event lists and displays event information and status lists available remote cells connected to the BMC ProactiveNet Server and monitored by BMC ProactiveNet enables you to generate and manage reports based on data collected by BMC ProactiveNet. Note: You must have permission to view this drawer.
Views & Graphs Bookmarks Find CI
Provides options for the management of views and graphs in the Operations Console enables you to view, rename, and delete bookmarks of objects and their related views that you create in the navigation tree provides a search mechanism so that you can search for CIs that meet the specified search criteria Note: You must have permission to view this drawer.
Event and component folders

Event and component folders enable you to organize cells and collectors to make event displays meaningful for operators. For example, you might create an event folder for collectors that gather database warning events and allow only operators that are database administrators access to that event folder. You can drag and drop components from one existing folder to another within the top-level folders in the navigation tree. You also can drag and drop CIs from the Tile or Graph view to an existing folder in the All Services folder.
Event folders
An event folder is a grouping of collectors that shows the relationship of events or abnormalities through the hierarchy of the navigation tree. Administrators define event folders and associate them with one or more collectors. Each level of the collector is shown as a node under the event folder. An event list is associated with the lowest level nodes of an event folder. The parent level of an event folder represents all of the events or abnormalities associated with the collectors.
136
Operations Console views
Event collectors
Event collectors gather events for display in an event list to provide operators with meaningful groups of events or abnormalities and to show relationship through the hierarchy of the nodes in the navigation tree. To access the event list for a collector, operators click the collector node in the navigation tree. Event collectors are dynamic or static. Nodes for dynamic collectors appear or disappear from the navigation tree based on whether or not events are present that meet the criteria for those collectors. Nodes for static collectors remain in the navigation tree whether events are present or not.
Component folders
A component folder is a grouping of groups, services, or devices from several different event lists (collectors) that shows the relationship of groups, services, or devices through the hierarchy of the navigation tree. Administrators define component folders and associate them with one or more groups, services, or devices. Each level of the component folder is shown as a node under the parent component folder. An event list is associated with the lowest level nodes of a component folder. The parent level of a component folder represents all of the events associated with the groups, services, or devices. There are two types of component folders, static and dynamic. Static component folders are populated by selecting from a list of objects. Dynamic component folders are populated by creating a query. Static folders always contain only the objects that you manually select. Dynamic folders contain the objects that match the query so the contents of these folders can change without further editing.

Table 5 on page 138 describes the views provided by the Operations Console. Different views are available, depending on what object is selected in the navigation tree. Each view is accessed by clicking the associated button on the Operations Console toolbar. If a view is not available for the object that is selected in the navigation tree, than the button for that view will not be displayed in the Operations Console toolbar.
Chapter 12
137
Table 5
View Event
Operations Console views and associated toolbar buttons

Description Event view displays all events in an event list. This is the default view for all objects. Use the Event view to check the details of events and to address events which highlight incorrect state. Probable Cause Analysis will help on identifying the event which could be the probable cause of the event specified. An event could be assigned to other users, who can acknowledge, take ownership, fix the problem and close the event. You can also address the incorrect condition by invoking Remote Actions/Detailed Diagnostics and Local Actions. The Graph View helps check the impacting service and you can cross-launch to Impact Model Designer, Service Level Manager and Product Catalog in ITSM. You can display an Event view for:
s s s s s s
Toolbar button
event collectors abnormalities services groups devices monitors
Tile
Tile view displays an encapsulated view of event metrics for the components that are being monitored in your environment. Use the Tile view to obtain a dashboard summary of event activity. You can display a Tile view for:
s s s s
event collectors services groups devices
Canvas
Canvas view allows you to you create a graphical representation of the components that are being monitored in your environment. The components are represented by objects that can be placed on a background image. The objects can be graphics, such as images or connectors, or metrics information represented in a tile. You can create and display a Canvas view for:
s s s s
event collectors services groups devices
138
Accessing the Command Line Interface (CLI)
Table 5
View
Operations Console views and associated toolbar buttons

Description Tree/Graph view displays information for a selected object as a tree representing the hierarchy of the object. The tree view is is available for groups and services. Tree view can be used to get a real-time, interactive visualization of the event status and other details of the selected group/service. In the Group hyperbolic tree the entire group hierarchy and devices are visible on a hyperbolic pane which is mapped to a circular display region. Service tree is applicable only for the selected service. If a service is selected in the navigation tree, this view displays a graphical representation of the configuration items (CIs) in the service model and shows how those CIs relate to each other. Use the Graph view to monitor events for published service models that represent your business services. You can display a Tree/Graph view for:
s s
Toolbar button
Tree/Graph
services groups
Grid
Grid view displays information for the selected object in a tabular format. Grid view can be used to view the event status and other details of the selected object as the tabular representation of the objects will have drilldown links to granular details through graphs, views and so on. You can display a Grid view for:
s s s s
abnormalities groups devices monitors
For more information about Operations Console views, see the BMC ProactiveNet User Guide.
Accessing the Command Line Interface (CLI)

Using the pw command line interface (CLI) you can execute commands on the BMC ProactiveNet Server. The pw CLIs allow you to start, stop and perform other actions on the BMC ProactiveNet Server without using the Administration Console. The pw CLIs are documented in the BMC ProactiveNet CLI Reference Guide.
Chapter 12
139
Accessing online Help
To access the pw CLI on Microsoft Windows

From the system icon tray, right-click the BMC ProactiveNet icon commands. and choose pw
To access the pw CLI on Solaris

Access the /usr/pw/bin directory and enter pw commands from that directory. For more information about pw commands, see the BMC ProactiveNet CLI Reference Guide.

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 consoles.

To begin using the BMC ProactiveNet Operations Console, see the BMC ProactiveNet User Guide. To begin using the BMC ProactiveNet Administration Console, see the BMC ProactiveNet Administrator Guide.
140
Chapter
13
13
Post-installation tasks
This chapter provides tasks for configuring BMC ProactiveNet after installation.
Changing the BMC ProactiveNet Console passwords

For security reasons, BMC recommends that you change the passwords for the BMC ProactiveNet Administration Console and the BMC ProactiveNet Operations Console after installation. To keep your passwords secure, you also should change them periodically.
Changing your BMC ProactiveNet Administration Console password

NOTE
In a setup where LDAP authentication is used, administrators must change the password from the LDAP server and not from the BMC ProactiveNet Administration
Console.
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 field, enter your current
password.
3 In the New Password and Confirm New Password fields, enter a new password.
Chapter 13 Post-installation tasks 141
Changing your BMC ProactiveNet Operations Console password
4 Click OK.
Your password for the BMC ProactiveNet Administration Console logon is changed immediately.
NOTE
If you forget your password, an 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.
Changing your BMC ProactiveNet Operations Console password

1 Click the Options link at the top the Operations Console. 2 In the General tab, under User ID and Password, click Edit. 3 Enter the old password and the new password, and then click Apply.
Changing the Apache HTTP port number

During installation, port 80 is required to install the Apache web server. If you have another product installed that uses port 80 (such as the IIWS server), you must change the Apache HTTP port to another port number before you start the application that is using port 80.
To change the Apache HTTP port number 1 Open the appropriate files for your operating system:
s s
UNIX: /usr/pw/apache/conf/httpd.conf Microsoft Windows: pw\ApacheGroup\Apache\conf\httpd.conf and

pw\pronto\conf\pronet.conf
2 Search for the string Port 80 and replace the value 80 with the desired port number. 3 Search for the string Listen 80 and replace the value 80 with the same port number
provided in the previous step.
4 Save and exit the .conf files.
142
Configuring BMC ProactiveNet Server to run as a non-root user after installation on Solaris
5 Search for the string Listen 80 and replace the value 80 with the same port number
provided in the previous step.
Configuring BMC ProactiveNet Server to run as a non-root user after installation on Solaris
You can use the configNonRoot script to configure BMC ProactiveNet Server to run as a non-root user on Solaris. You can use this same script to switch the BMC ProactiveNet Server from one non-root user to another non-root user.
To configure BMC ProactiveNet Server to run as a non-root user on Solaris 1 From a command line, execute the following commands:
csh source /usr/pronto/bin/.tmcsh configNonRoot userName
2 When prompted by the configNonRoot script, provide the HTTP and HTTPS
ports for Apache server. The script performs the necessary changes.
Configuring the BMC ProactiveNet Server for 256-bit SSL encryption

To configure the BMC ProacativeNet Server to use 256-bit SSL encryption, follow these steps:
1 Stop the BMC ProacativeNet Server. 2 Create the certificate with the .der or .cer format.
For example iascert.cer is generated using certsrv from Windows.
3 If you cannot access the LDAP or Active Directory server, use JXplorer (an open
source LDAP browser) to export the server certificate to a file by following these steps:
A Using JXplorer, connect to the LDAP server. B From the menu bar, choose Security => Trusted Servers and CAs.
Chapter 13 Post-installation tasks 143
Configuring the BMC ProactiveNet Server for 256-bit SSL encryption
C Select the appropriate certificate, and click View Certificate. D In the General tab, click Copy to File. E Select the file location and type the file name for the certificate. 4 Copy the certificate file to the \Program Files\ProactiveNet\pw\jre\lib\security
directory.
5 Ensure that your Windows path contains the \Program

Files\ProactiveNet\pw\jre\bin path.
6 Enter the following command specifying the complete certificate and keystore
path:
keytool -importcert -v -trustcacerts -alias LDAP123 -file server.der -keystore pnserver.ks
7 When prompted, enter the keystore password.

The default keystore password is get2net.
8 Back up the following files in the \Program Files\ProactiveNet\pw\jre\lib\security

directory:
s s
local_policy.jar US_export_policy.jar
9 From the Sun website

(http://www.oracle.com/technetwork/java/javase/downloads/index.html), download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files ( jce_policy-6.zip) which contain the following files:
s s
local_policy.jar US_export_policy.jar
and copy them into the \Program Files\ProactiveNet\pw\jre\lib\security directory. These files are required for unlimited encryption strength over a network.
10 Restart the BMC ProacativeNet Server.
144
Configuring BMC ProactiveNet Event Adapters to start collecting events
Configuring BMC ProactiveNet Event Adapters to start collecting events

By default, the BMC ProactiveNet Event Adapters are disabled (in fresh installations). The BMC ProactiveNet Server installation does not start BMC ProactiveNet Event Adapters. To start BMC ProactiveNet Event Adapters, follow the procedure appropriate for your operating system. For more information about BMC ProactiveNet Event Adapters, see the BMC Impact Event Adapters User Guide.
To start BMC ProactiveNet Event Adapters on Microsoft Windows 1 Add the license. For obtaining licenses, refer to Applying licenses on page 68. 2 Choose Start=>Programs=>Administrative Tools=>Services. 3 Right-click the BMC ProactiveNet Event Adapters service and choose Properties.
The BMC ProactiveNet Event Adapters Properties dialog box is displayed.
4 In the General tab, change the Startup Type to Automatic.

This configures BMC Impact Event Adapters to start automatically after reboot.
5 Click OK and start the service. To start BMC Impact Event Adapters on UNIX-based platforms 1 Add the license. For obtaining licenses, refer to Applying licenses on page 68. 2 Copy the /etc/init.d/BMCProactiveNetEventAdapter file into the following
directories:
s s s s s
/etc/rcS.d/K02BMCProactiveNetEventAdapter /etc/rc0.d/K02BMCProactiveNetEventAdapter /etc/rc1.d/K02BMCProactiveNetEventAdapter /etc/rc2.d/K02BMCProactiveNetEventAdapter /etc/rc3.d/S98BMCProactiveNetEventAdapter
3 Start the adapter by running the command /etc/init.d/BMCProactiveNetEventAdapter

start
Chapter 13
145
Managing the Oracle Server
NOTE
If an error occurs indicating Event Adapter is not starting, add pkg on both the nodes. # pkgadd -d libgcc-3.3-sol9-sparc-local # csh # setenv LD_LIBRARY_PATH /usr/local/lib # echo $LD_LIBRARY_PATH Configuring Event Adapters: /usr/pw/server/etc/mcxa.conf Remove DISABLE from [Logfile 1] DISABLE Engine = MA::ELogfile # --Modify the following value(s) according to your environment-LogFile = /tmp/mylog.txt # Replace by the actual syslog location # Replace by the actual destination cell (if different from the global) ServerName = pncell_blrsccluster \+++ #./mcxa.sh
Managing the Oracle Server

After you install the BMC ProactiveNet Server, a remote agentless device is created where Oracle is installed. The following Oracle related monitors under this device are created by default:
s s
Oracle Query Oracle Intelliscope
Install a remote BMC ProactiveNet Agent on the Oracle server for tracking the functioning of the remote Oracle server and BMC recommends you to create some monitors such as the following:
s s s s
Disk Space Monitor that monitors the Oracle disk space. Processes Monitor that monitors the Oracle processes. Tablespace monitor that will monitor the tablespaces of the Oracle server. Ping Monitor monitors if the Oracle server is accessible.
146
Oracle database backup and restore
Oracle database backup and restore

The following three choices allow you to take a backup of the BMC ProactiveNet database and restore them back. BMC Software recommends you to take a backup regularly.
s s s
BMC Database Recovery Manager for Oracle RMAN Any other Oracle recommended backup and recovery utility
Configuring BMC Atrium CMDB integration

During the installation process, you have the option to configure the BMC ProactiveNet server integration with BMC Atrium CMDB. If you did not configure the BMC Atrium CMDB integration during installation, you can configure it now.
WARNING
Before you configure the CMDB Server, ensure that BMC ProactiveNet CMDB Extensions, modules, and hotfixes are installed on the computer where the BMC Atrium CMDB is installed. For information about installing the CMDB extensions, see Chapter 3, Preparing for BMC Atrium CMDB integration.
NOTE
Execute the integrate_atrium_tool command inside the pw directory to ensure that all the folders are deleted during uninstallation if you have integrated BMC ProactiveNet Performance Management with CMDB.
Use the following script:

integrate_atrium_cmdb -uddi_server_host_name uddiServerHostName -uddi_server_port_no uddiServerPortNumber -uddi_user_name uddiUserUame [-uddi_password uddiPassword] -cmdb_server_host_name cmdbServerHostName -cmdb_server_port_no cmdbServerPortNumber -cmdb_user_name cmdbUserName [-cmdb_password cmdbPassword] -cmdb_version cmdbVersion [-ngp_webserver_protocol webServerProtocol] [-ngp_webserver_port_no proactiveNetWebServerPortNumber]
Chapter 13
147
Configuring BMC Atrium CMDB integration
where
s
s s s s
uddiServerHostName is the host name of the UDDI web service where BMC Atrium CMDB is running uddiServerPortNumber is the port number used by the UDDI web service on the specified host uddiUserUame is the user name for the UDDI web service (optional) uddiPassword is the password for the UDDI web service user cmdbServerHostName is the host name where BMC Atrium CMDB is running cmdbServerPortNumber is the BMC Remedy Action Request System TCP port number, used to log into the system server cmdbUserName is the user name to access the BMC Remedy Action Request System server (optional) cmdbPassword is the password for the BMC Remedy Action Request System server user cmdbVersion is the BMC Atrium CMDB version. Use one of the following values: 7.6.03 (for BMC Atrium CMDB version 7.6.03) 7.6 (for BMC Atrium CMDB version 7.6 patch 2) 7.5 (for BMC Atrium CMDB version 7.5 patch 5)
NOTE
All user names and passwords are case sensitive.
Use the following optional arguments if you need to enable the cross-launch into BMC ProactiveNet.
s s
webServerProtocol is the web server protocol, either http (default) or https proactiveNetWebServerPortNumber is the port number used by the web service. The default value is 80.
For example:
integrate_atrium_cmdb -uddi_server_host_name Vm-w23-rds1184 -uddi_server_port_no 8080 -uddi_user_name admin -uddi_password admin -cmdb_server_host_name Vm-w23-rds1183 -cmdb_server_port_no 5555 -cmdb_user_name Admin -cmdb_password Admin -cmdb_version 7.6.03 -ngp_webserver_protocol https -ngp_webserver_port_no 8888
At the time of installation, if you have selected not to integrate BMC Atrium CMDB, then you need to configure IBRSD. Edit the ARSServerName parameter in the IBRSD.conf and IBRSD.dir files, located in the /usr/pw/integrations/ibrsd/conf directory.
148
Configuring remote cells for viewing in the Operations Console
Configuring remote cells for viewing in the Operations Console

You can view events on a remote cell once you configure the remote cell so that it can be viewed in the Operations Console. BMC recommends that you do not add a second BMC ProactiveNet cell as a remote cell. For example, if you have multiple server deployments with one master and two child servers, do not add the BMC ProactiveNet cells as remote cells.
To configure a remote cell for viewing in the Operations Console 1 Add an entry for the remote cell in the cell_info.list file located at
installDirectory\pw\pronto\conf\ by entering the following command:
iadmin name=remoteCellName:key=mc:primaryHost=hostName:primaryPort= portNumber:environment=environmentType:usergroups=userGroupNames
The parameters are defined as follows:

s
s s
s s
remoteCellNamename of the remote cell that you want to display as defined in the mcell.dir file key is the encryption key of the cell; the default is mc. primaryHosthostNamecomputer where the cell is located. Specify the computer name and the domain name. portNumberport on which the remote cell is listening; the default is 1828 environmentTypetype of environment where the cell is used; must be either Production or Test userGroupNamesname(s) of the user groups that can access the remote cell. To allow access to all user groups, enter an asterisk (*). To specify only certain user groups, enter the group names separated by commas. If a user group contains spaces, enclose the entire entry for this group name with double quotes.
NOTE
iadmin -ac name=qa:key=mc:primaryHost=qa.company.com:primaryPort=1828: environment=Production:usergroups="Full Access, Read Only"
2 Add an entry for the remote cell in the mcell.dir file located at
InstallationDirectory\pw\server\etc\as follows:
cell cellName mc computerNameWithDomain: portOnWhichCellIsInstalled
Chapter 13
149
Registering remote cells in the Administration console
NOTE
cell qa mc qa.company.com:1828
Registering remote cells in the Administration console

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. Follow these steps to register remote cells in the Administration Console.
To display remote cells in the Infrastructure Management tab 1 Add the cell using the mcrtcell CLI command, as in the following example:
mcrtcell -as -ba -r -@ <variableText>hostName</variableText>/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 admin -ac command as in the following example:
iadmin -ac name=sparkles_cell:key=mc:primaryHost=moondog:primaryPort=2008:failoverHost=su ncat: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 mc cell Admin mc cell sparkles_cell mc
3 Add the cell entry to the mcell.dir file.

By default, the file is located in the
BMC_PROACTIVENET_HOME</variableText>/server/etc directory.
4 Restart the cell that you are registering.
150
Configuring cell connection properties to the BMC ProactiveNet Server
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.

The first 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 => Configuration.
The Edit Configuration dialog box is displayed.
2 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 single cell, changes are applied only to the individual cell.
5 Use Table 6 to set cell connection properties as required.

Table 6
Property Name Host Port Timeout
Cell connection properties (part 1 of 2)

Description displays the name of the cell whose properties you are changing displays the name of the host computer where the cell is installed displays the port number the cell uses to connect to the host computer 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.
Chapter 13
151
Table 6
Property
Cell connection properties (part 2 of 2)

Description 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.
Refresh Freq
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 Auto Switch enables and disables automatic connection to the cell at logon; default is disabled (cleared) 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 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.
s
Use Port Range
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. If you type a value of zero in Min Port No., BMC ProactiveNet clears the Use Port Range check box. If you type a value of zero in Max Port No., BMC ProactiveNet replaces it with the value of Min Port No. If the value of Max Port No. is less than the value of Min Port No., BMC ProactiveNet changes the value of Max Port No. to that of Min Port No.
Min Port No. Max Port No. Auto Bind
specifies the lower limit of the port range specifies the upper limit of the port range 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 18 for additional information. specifies the IP address assigned to the local network card to which the console connects; available only if Auto Bind is cleared
IP Address
152
Specifying ports in cell connection properties
Specifying ports in cell connection properties

The following circumstances require that you provide more specific information about communications between the console and the cell:
s s s
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
=> Configuration.
2 In the Edit Configuration dialog box, click the Login Servers tab.
Chapter 13
153
3 Modify any of the BMC ProactiveNet Server configuration parameters listed in

Table 7BMC ProactiveNet Server configuration parameters on page 154, as needed: Table 7
Field Heartbeat Rate
BMC ProactiveNet Server configuration parameters

Description 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. specifies the maximum and minimum port number for the console to use in establishing a connection to a BMC Impact Administration Server 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.
Enable Port Range
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.
You can log out of the BMC ProactiveNet Server and log in from the BMC ProactiveNet Administration Console interface without closing the console.
154
Adding Agents
To log out of the BMC ProactiveNet Server from the Administration Console 1 From the menu bar of the BMC ProactiveNet Administration Console, choose
Server => Logout.
2 In the Logout Confirmation dialog box, click Yes. To log on to the BMC ProactiveNet Server from the Administration Console 1 From the menu bar of the BMC ProactiveNet Administration Console, choose
Server => Login.
2 In the BMC ProactiveNet Administration Console Logon screen, 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.
Adding Agents
Use the Add Agent option to add an agent after a device has already been set up. To monitor a device specifically on UNIX computers, you need to add an agent. For Windows, you may add an agent if you want to monitor for example, disks and file system. To set up the device and the agent simultaneously, see the BMC ProactiveNet Administrator Guide. 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 In the Administration Console, expand the Device folder. 2 Right-click the device where you want to add the agent.
Chapter 13
155
Adding Agents
3 In the Add Agent window, enter the following information:

Field Control Port Description 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 the BMC ProactiveNet Administrator Guide. Agent Name Agent IP Address BMC ProactiveNet inserts the device name that you specified. 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. BMC ProactiveNet lists devices with the same IP address. By default, the one created on the previous screen is selected.
Associated Device
4 Choose one of the following Connection options:

s
Direct Access using TCP/IP - choose if the remote agent uses TCP/IP. Direct Access using SSL TCP/IP - choose if the remote agent uses SSL TCP/IP. HTTP Tunnel Proxy - choose if the remote agent uses an HTTP Tunnel. For
installation about Tunnel agents, see the BMC ProactiveNet Administrator Guide.
s
TCP Proxy - choose if the remote agent uses TCP Proxy. For further details, see
the BMC ProactiveNet Administrator Guide.
5 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
6 Choose the monitor. 7 Follow the procedure in Selecting monitors for the device on page 163.
To view the new agent, expand (or close and expand) the Agents folder. To view the monitor, expand (or close and expand) the p folder. If a problem occurs while you are adding an agent, BMC ProactiveNet displays an error message. For more information, see the BMC ProactiveNet Administrator Guide.
156
Getting started with devices
Getting started with devices

The following sections give an overview of available devices and provide instructions for properly creating devices.
Summary of devices
You add devices to BMC ProactiveNet through the Device folder on the Administration Console. 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:
s s s s s s s s s s
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 BMC ProactiveNet Administrator Guide.
Using device aliases

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.
Chapter 13
157
Avoiding duplicate devices
Aliases generated automatically are prefixed with BMC_ComputerSystem and use the following naming conventions, depending on how the device is generated:
s
BMC_ComputerSystem:Host Name:Domain
For example, BMC_ComputerSystem:test.bmc.com

s
BMC_ComputerSystem:IP
For example, BMC_ComputerSystem:10.134.12.10

s
BMC_ComputerSystem:TokenID
When the BMC ProactiveNet cell receives an event, the event is processed as follows, depending on whether the event is internal or external:
s
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:Host Name:Domain or BMC_ComputerSystem:IP, 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.
For more information, see the BMC ProactiveNet Administrator Guide.
Avoiding duplicate devices

In BMC ProactiveNet, a device can be created in the following ways:
s
through one of the following adapters: BMC PATROL Adapter BMC Portal Adapter Native VMware Adapter System Center Operation Manager (SCOM) Adapter BMC Transaction Management Application Response Time (BMC TM ART) Adapter
manually by using the Administration Console or a Command Line Option integrating with the BMC Atrium CMDB
158
Creating a device
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.
Avoiding creating duplicate devices

Duplicate devices are not created in the following situations:
s s s
if devices are created by only one source if devices are created from different sources independently if different sources use the same naming convention when creating the devices; for example, IP address, host name, or fully qualified domain name
Best practices for device creation

To avoid creating duplicate devices, ensure that
s
the device is created using the fully qualified domain name of the host computer where the device is located if the device is referenced from multiple adapters that each adapter must use the fully qualified domain name of the device
Creating a device
Before adding devices, have the following information available:
s
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.
Chapter 13
159
Creating a 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 Installation requirements on page 27.
To create a device 1 In the BMC ProactiveNet Administration Console, select the Devices folder, rightclick, and choose Add => Device.
2 In the Add Device window, choose the Configuration tab. 3 From the Device Type list, choose a device type. NOTE
Ensure that you select the correct device type. The device type is used by the Probable Cause Analysis algorithm to determine correlations between events and abnormalities within the system. If the device type is not accurate, the Probable Cause Analysis may not be accurate. For example, if a computer is a Web Server, set the device type as WebServer (not
just Server).
4 In the Device Name field, 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.
5 In the DNS Name / IP Address field, specify the IP address of the device.
The 127.0.0.1 IP address 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.
160
Creating a device
6 In the Tag field, choose a descriptive tag about the device that you are creating by
following these steps:
A Click the plus icon to display the Enter Tag Details dialog box. B Choose a Tag Class 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 (such as Auckland) as the Tag Value. Tag Class is not mandatory. The Tag Value used as a keyword is currently useful in the Rule base groups functionality.
C Click Add to enter the values that you specify, and then click Finish to return to
the Add Device dialog box.
7 In the Aliases field, 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 the BMC ProactiveNet Administrator Guide.
8 In the Secondary IPs area, view any secondary IP addresses that may be associated
with the device that you are creating. 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.
9 In the Device Description field, enter a description for the device that you are
creating.
10 If you have installed a BMC ProactiveNet Agent on this device, select the Agent
Installed on Device option.
11 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.
12 Select the SNMP Data Collection 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 conduct maintenance on existing devices without generating events.
Chapter 13
161
Creating a device
13 In the SNMP Read Community String you can change the 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.
14 In the SNMP Retries field, specify how many times (count) BMC ProactiveNet Server
must request data from the device before reporting an event. Default is 2 retries.
15 In the SNMP Timeout field, specify the duration (in seconds) BMC ProactiveNet
Server must wait for data from the device before reporting an event. Default is 2 seconds.
16 Select the SNMP Use V2 option if the device is using version 2 of the protocol. 17 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.
18 Click the Remote Actions/Diagnostics tab and enter the required information.
s
Protocol Typesselect a protocol type from the list. The supported protocols are psExec, ssh (Secure Shell), and Telnet. PortNothe default port number of the selected Protocol Type is displayed. Remote User Nameenter the remote user name. This is mandatory for all
Protocol Types.
s
Remote User Passwordenter the remote user password. This is mandatory for
psExec, ssh, and Telnet protocol types. Confirm the remote user password.
162
Selecting monitors for the device
NOTE
If you choose the Telnet option from the protocol type list, you will have to fill in the information for the remote system prompt as described in the example. 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 the BMC ProactiveNet Administrator Guide.
19 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.
20 Click Finish to save your actions and execute all remaining actions (using defaults). 21 After reviewing the summary panel, click Finish.
Selecting monitors for the device

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 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 select monitors for a device 1 Create a device for the system that you want to monitor. 2 Add an agent to that device. 3 Select the monitors that you want to create for this device from the Select Monitors
to Create screen.
Chapter 13
163
Stopping the BMC ProactiveNet Server
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.
4 Click Next.
The configuration windows appear 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.
5 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.
6 Click Finish.
To view the new device listing, expand (or close and expand) the corresponding device folder.
Stopping the BMC ProactiveNet Server

The installation process automatically starts the BMC ProactiveNet Server. If you want to stop the BMC ProactiveNet Server, follow the procedure appropriate for your operating system.
To stop the BMC ProactiveNet Server on Microsoft Windows 1 From the system icon tray, right-click the BMC ProactiveNet icon 2 Choose Server Stop.
.
164
Starting the BMC ProactiveNet Server
To stop the BMC ProactiveNet Server on Solaris 1 Access the pw CLI. 2 Enter pw sys stop.
Starting the BMC ProactiveNet Server

Once you have stopped the BMC ProactiveNet Server, you must restart it manually. To restart the BMC ProactiveNet Server, follow the procedure appropriate for your operating system.
To start the BMC ProactiveNet Server on Microsoft Windows 1 From the system icon tray, right-click the BMC ProactiveNet icon 2 Choose Server Start. To start the BMC ProactiveNet Server on Solaris 1 Access the pw CLI. 2 Enter pw sys start.
.
Checking the status of the BMC ProactiveNet Server

NOTE
After the status of the BMC ProactiveNet Server changes, it may take a little time for the system tray icon to reflect the change, depending on your environment.
To check the status of the BMC ProactiveNet Server on Microsoft Windows 1 From the system icon tray, right-click the BMC ProactiveNet icon 2 Choose Server Status.
.
Chapter 13
165
Enabling and disabling Integration Services
To check the status of the BMC ProactiveNet Server on Solaris 1 Access the pw CLI. 2 Enter pw sys status.
Enabling and disabling Integration Services

The Integration service is installed automatically when you install a BMC ProactiveNet Agent.
Enabling the Integration Service to gather data from products that integrate with BMC ProactiveNet
During the installation process, you have the option to enable the Integration service. If you did not enable the Integration service during installation, but want to enable it now, follow these steps.
To enable the Integration service on Microsoft Windows 1 Open the custom\pronet.conf file and change the value of the
pronet.apps.agent.patrol.proxy.enabled property to TRUE.
2 From a command line, import pns.reg as follows:

s
If you are enabling the Integration service on a remote agent enter: Regedit /s
InstallationDirectory \Agent\pproxy\PNS\security\pns.reg
If you are enabling the Integration service on a BMC ProactiveNet Server enter:
Regedit /s InstallationDirectory \pw\pproxy\PNS\security\pns.reg
3 From a command line, register pproxsrv.exe as a service on the desired port as

follows:
s
If you are enabling the Integration service on a remote agent enter:

InstallationDirectory\Agent\pproxy\PNS\bin\pproxsrv.exe -install -p 3182 -m
166
Disabling the Integration Service
If you are enabling the Integration service on a BMC ProactiveNet Server enter:
InstallationDirectory\pw\pproxy\PNS\bin\pproxsrv.exe -install -p 3182 -m
NOTE
The default port for the Integration service is 3182. If you want to register on a different port, substitute that port number in the registration command and update the custom\pronet.conf file with the new port number.
4 Restart the BMC ProactiveNet Agent service. To enable the Integration service on UNIX or Linux 1 Open the /usr/pw/custom/conf/pronet.conf file. 2 Change the value of the pronet.apps.agent.patrol.proxy.enabled property to TRUE. 3 Restart the BMC ProactiveNet Agent by executing the following command:
pw process restart pronet_agent
Disabling the Integration Service

To disable the Integration Service, follow these steps.
1 Open the appropriate file for your operating system:

s s
For Microsoft Windows: custom\pronet.conf For UNIX or Linux: /usr/pw/custom/conf/pronet.conf
2 Change the value of the pronet.apps.agent.patrol.proxy.enabled property to FALSE. 3 Restart the BMC ProactiveNet Agent as appropriate for your operating system:
s s
For Microsoft Windows: restart the BMC ProactiveNet Agent service For UNIX or Linux: execute pw process restart pronet_agent
NOTE
Restarting the BMC ProactiveNet Agent will not stop the pproxy service.
Chapter 13
167
Specifying a particular IP address for the BMC ProactiveNet Agent
Specifying a particular IP address for the BMC ProactiveNet Agent

By default, BMC ProactiveNet creates a generic bind for the BMC ProactiveNet Agent that accepts all incoming requests. For computers with multiple IP addresses, you can specify a particular IP address or interface for the remote agent to listen to requests. To do this, set the pronet.apps.agent.bindaddress property in the pronet.conf file to a specific IP address.
Changing the BMC ProactiveNet Server IP address

You might need to change your IP address for the local agent if you are using a Network Address Translation (NAT) firewall, or you have a connectivity issue.
To change the IP address of the BMC ProactiveNet Server 1 From the Administration Console, choose Advanced Options=>Agent. 2 Right-click ProactiveNet Server and choose Edit. 3 In the Edit Remote Agent dialog box, replace the DNS Name/IP address with the
new IP address.
4 Click OK to close the dialog box and save your changes. 5 Restart the local agent.
Configuring e-mail settings to receive alerts

Review the e-mail settings on the server target computer to ensure that it is configured to receive e-mail alerts from BMC ProactiveNet. If it is not, an error or warning message similar to the following is displayed: Warning: ProactiveNets e-mail alerts may not work with the current configuration If this message is displayed, perform the following procedure.
168
Configuring e-mail settings to receive alerts
To configure e-mail settings to receive alerts from BMC ProactiveNet 1 Review the e-mail settings and make any necessary changes, as described in
Table 8: Table 8
Setting Administrator's e-mail address
E-mail settings required to receive alerts from BMC ProactiveNet

Location
s
Parameter or property to change Correct format a fully qualified e-mail address in the following format: user@company.com
UNIX: admin_user /usr/installDirectory/etc/hosts/ admin_user Microsoft Windows: installDirectory\pw\etc\hosts \admin_user from_name UNIX: /usr/installDirectory/etc/hosts/ from_name Microsoft Windows: installDirectory\pw\etc\hosts \from_name UNIX: /usr/installDirectory/custom/ conf/pronet.conf Microsoft Windows: installDirectory\pw\custom\ conf\pronet.conf UNIX: /usr/installDirectory/custom/ conf/pronet.conf Microsoft Windows: installDirectory\pw\custom\ conf\pronet.conf
Sender's e-mail address
user or user@company.com, depending on the valid From address accepted by the SMTP server
SMTP server hostname or IP address
pronet.api.emailer a fully qualified server .smtp.host hostname or IP address reachable from the BMC ProactiveNet Server host
SMTP port
pronet.api.emailer a valid port number on .smtp.port which the SMTP server is listening for SMTP requests
2 After you modify the e-mail settings, verify the configuration by using one of the
following scripts, depending on your operating system:
s s
UNIX: /usr/pw/pronto/bin/TestEmail.sh Microsoft Windows: installDirectory\pw\pronto\bin\TestEmail.bat
A Success or Failure message is sent to the administrators e-mail address and is added to the TestEmail.log file that is located in the same directory as the verification script. You can run the script multiple times until the email settings are configured correctly.
Chapter 13
169

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 consoles.
NOTE
The first time you access the online Help after launching a console, it may take some time for the online Help to be displayed.

To begin using the BMC ProactiveNet Operations Console, see the BMC ProactiveNet User Guide. To begin using the BMC ProactiveNet Administration Console, see the BMC ProactiveNet Administrator Guide. For information about monitors, see the BMC ProactiveNet Data Adapter and Monitor Guide.
170
Chapter
14
Creating and installing component packages

14
When you install the BMC ProactiveNet Server, you have the option to install the BMC ProactiveNet Performance Management Package Installation Repository. The Package Installation Repository includes the current versions of BMC components that are able to be used with BMC ProactiveNet. The Package Installation Repository includes all the BMC PATROL Knowledge Modules that can be integrated with BMC ProactiveNet, as well as the BMC PATROL Agent. From the BMC ProactiveNet Operations Console, an administrator can select the components from the repository that he or she wants to install on the same computer(s) and package them together so that they can be installed simultaneously. Once an administrator has created a package, he or she can:
s s s
save the package to the Package Installation list for future use install the package on the current host without saving the package download and install the package on any host
WARNING
Before installing a package that includes the PATROL Agent on Linux x64, you must install the glibc.i686 package from the Red Hat Enterprise Linux repository. To install the glibc.i686 package, log on as root and execute the yum install glibc.i686 command. If you do not install the glibc.i686 package, installation of the PATROL Agent will fail.
To create an installation package 1 Click Options and select the Downloads tab. 2 In the Component Installation Packages section, click Add.
The Installation Package Component Selection Page is displayed.
Chapter 14 Creating and installing component packages
171
3 From the first menu, choose the operating system for which you want to create a
package.
4 From the second menu, choose the platform for the selected operating system on
which you want to install the package. The list of components in the Package Installation Repository that are supported on the operating system and platform that you selected is displayed.
5 From the Available components list, select the components that you want to include
in your package.
NOTE
The appropriate PATROL agent for the operating system and platform that you chose is included in the Selected Components list by default.
6 From the Version drop list, select the version of the components that you want to
include in the package. You can either select a specific version or you can select Latest, which automatically updates the package with the latest versions of the components when new versions of those components are added to the Package Installation repository.
7 Click the right arrow button to move the selected components into the Selected
Components list. Click Next.
The installation wizard for the products you have selected is displayed.
8 Complete the installation screens. NOTE

The screens displayed in the installation wizard vary depending on the components that you have selected to include in your installation package. To complete the installation screens, follow the instructions in the installation guide(s) for your selected products.
The final Summary and Installation Package Details page is displayed.
9 In the Summary section, verify that the operating system and platform are correct
for the type of installation package that you want to create. Also verify that the correct components that you want to include in the installation package are listed in the Included Components list.
172
10 In the Installation Package Details section, provide the following information: A In the Name field, enter a name for the installation package that you are creating. B In the Description field, if desired, enter a description of the installation package
that you are creating. The description you enter is available in the Information page for the installation package that you are creating. By default, the information page includes the operating system and platform, as well as the selected components for each installation package.
C In the Format field, choose the desired compressed file format for your
installation package.
11 Choose from the following actions:

s
To save the installation package for future installation on the current host or other hosts, click Save Installation Package. You will receive a verification message that the installation package is saved successfully. The package now is available for installation. To install the package on another computer, see To install an existing installation package on page 174.
To save the installation package for future installation on other computers and immediately install the package on the current computer: 1. Click Save Installation Package. You will receive a verification message that the installation package is saved successfully. 2. Click Download. 3. Extract the package as appropriate for your operating system. The package is extracted on the current host into the bmc_products directory. 4. From the bmc_products directory, install the installation package by launching the appropriate installation utility for your operating system: UNIX or Linux: RunSilentInstall.sh
Microsoft Windows: RunSilentInstall.exe
The package is installed on the current host.
173
To immediately install the package on the current computer without saving the package for future use, follow these steps: 1. Click Download. 2. Extract the package as appropriate for your operating system. The package is extracted on the current host into the bmc_products directory. 3. From the bmc_products directory, install the installation package by launching the appropriate installation utility for your operating system: UNIX or Linux: RunSilentInstall.sh
Microsoft Windows: RunSilentInstall.exe
To install an existing installation package 1 From the computer on which you want to install the installation package, log into
the BMC ProactiveNet Operations Console.
2 Click Options and select the Downloads tab. 3 In the Component Installation Packages section, from the Filter by Operating System
menu, select the operating system for the current computer. The installation packages that are supported on the operating system of the current computer are displayed.
4 Click the hyperlinked name of the installation package that you want to install on
the current computer.
5 Extract the installation package as appropriate for your operating system.

The package is extracted into the bmc_products directory on the current host.
174
6 From the bmc_products directory, install the package by launching the appropriate
installation utility for your operating system:
s s
UNIX or Linux: RunSilentInstall.sh Microsoft Windows: RunSilentInstall.exe
NOTE
By default the RunSilentInstall command displays a persistent results window that closes after you press any key. If you want the results window to close as soon as the installation is complete, enter the appropriate command for your operating system:
s s
UNIX or Linux: RunSilentInstall.sh -closeResults Microsoft Windows: RunSilentInstall.exe -closeResults
To enable debugging for the package installation utility

By default, debugging is turned off during the package installation. If you turn on debugging, information generated by the package installation utility is written to the packageInstaller.log file located in the ProactiveNetInstallationDirectory\pw\pronto\logs directory.
1 From a command line, enter pw debug on -p jserver -s packageInstaller

Debugging is enabled for the package installation utility.
To delete a saved installation package

This procedure deletes installation packages that you have created from the Component Installation Packages list.
1 From the BMC ProactiveNet Operations Console, click Options and select the
Downloads tab.
2 In the Component Installation Packages section, select the check box for the
installation package that you want to delete.
3 Click Delete.
175
To add a new or updated version of a product or component to the Package Installation Repository 1 Download the product or component image that you want to add to the Package
Installation Repository onto the computer where the Package Installation Repository is installed.
2 From a command line, access the

ProactiveNetInstallationDirectory\pw\apps3rdparty\PatrolInstaller\Scripts directory.
3 Run the appropriate command for your operating system:

s s
For Microsoft Windows enter: deploy_solution.bat ImageName For UNIX enter: deploy_solution.sh ImageName
The ImageName image is added to the Package Installation Repository.
176
Chapter
15
Configuring and using BMC ProactiveNet in high-availability mode

15
The following sections help you through the post-installation procedures that you need to perform to enable high-availability.
Configuring the BMC ProactiveNet Server in Sun cluster

Sun cluster identifies the health of the nodes in the cluster with device group configured for the BMC ProactiveNet application. Sun cluster checks the status of device group configured for the BMC ProactiveNet application to verify the nodes in the cluster, which are online and functioning well. Based on the status, the sun cluster enables the BMC ProactiveNet service to be available on the online node. On Sun Cluster, the application needs to be identified with a resource group. The Sun Cluster uses the resources present in the resource group for high-availability.
1 Create BMC ProactiveNet application resource type. This is necessary to register

the BMC ProactiveNet Server as the application for high-availability. For more information, refer to Creating the BMC ProactiveNet resource type on page 178.
2 Create a resource group that specifies the resources that need to be used for highavailability and the resources included are:
s s
Logical host name Application (BMC ProactiveNet Server)
For more information, refer to Creating the resource group on page 180.
Chapter 15 Configuring and using BMC ProactiveNet in high-availability mode 177
Creating the BMC ProactiveNet resource type
Creating the BMC ProactiveNet resource type

Use the agent builder utility to create the resource type for the BMC ProactiveNet product. This utility is part of the Sun Cluster installation. Perform the following procedure on each node in the cluster.
To create the resource type on Solaris computers 1 Start the agent builder utility by entering the following command:
/usr/cluster/bin/scdsbuilder
2 In the agent builder window, provide information for the following items:
Item Vendor Name Application Name RT Version Working Directory Description Name that identifies the vendor of the resource type. Typically, the name is SUNW. Name of the resource type. Version of the generated resource type. The version is by default 1.0. Directory under which the agent builder creates a directory structure to contain all the files that are created for the target resource type. You can create only one resource type in any working directory. Under the working directory, agent builder creates a subdirectory with the resource type name. Ensure that both the primary and secondary nodes in the cluster have the same working directory name. For example, if SUNW is the vendor name and pnbmc is the application name, then the agent builder names this subdirectory as SUNWpnbmc. Scalable or Failover C, ksh Target resource type. Select Failover. Language of the generated source code. Select ksh.
3 Click Create. 4 Click Next. 5 In the configure window, provide information for the following items:
178
Configuring the resource type
Item Start Command (or file)
Description The complete command line to pass to any UNIX shell to start the base application: /usr/pw/pronto/bin/pw system start
Stop Command (optional) The complete command line to pass to any UNIX shell to stop the base application: /usr/pw/pronto/bin/pw system stop Probe Command The command to run periodically to check the health of the application. The command returns an exit status between 0 (success) and 100 (complete failure). If you do not specify a probe command, the generated code simply connects to and disconnects from the port that is used by the resource. If the connect and disconnect succeeds, the generated code declares the application healthy. Timeout A timeout value, in seconds, for each command. You can specify a new value or accept the default value that the agent builder provides. The default value is 3600 seconds for start, 500 seconds for stop, and 30 seconds for probe.
6 Click Configure.
The agent builder generates a resource type (data service) that includes source and executable code (Korn shell), a customized Resource Type Registration (RTR) file, and a Solaris package for the BMC ProactiveNet product. The Solaris package contains the RTR file in the /etc directory. The file is named based on the values that you entered for Vendor Name and Application Name in the agent builder window. For example, if the Vendor Name is SUNW and the Application Name is pnbmc, then the name of the RTR file would be SUNW.pnbmc. Open the RTR file and ensure that the RT_BASEDIR parameter is set to the path of the /bin directory. For example, if the path to the /bin directory is /opt/SUNWpnbmc/bin, then the value for the RT_BASEDIR parameter should be /opt/SUNWpnbmc/bin. The Solaris package also contains start, stop, and probe scripts for the BMC ProactiveNet application resource type in the /bin directory. Provide execute permissions for all the generated scripts in the /bin directory.
Configuring the resource type

Perform the following procedure on the primary node of the cluster.
Chapter 15
179
Creating the resource group
To configure a resource type 1 Ensure that the BMC ProactiveNet application RTR file exists in the
/opt/cluster/lib/rgm/rtreg directory or /usr/cluster/lib/rgm/rtreg directory.
If it does not exist in one of these two directories, copy the RTR file that is in the /workingDirectory/resourceType/etc directory to either the /opt/cluster/lib/rgm/rtreg directory or /usr/cluster/lib/rgm/rtreg directory. For example, if you created a resource type named SUNW.pnbmc using the agent builder, then the name of the RTR file is SUNW.pnbmc. Copy that file from the /opt/SUNWpnbmc/etc/ directory to the /opt/cluster/lib/rgm/rtreg directory or the /usr/cluster/lib/rgm/rtreg directory.
2 Register a resource type by entering the following commands:

clresourcetype register resourceType clresourcetype show resourceType
The following output is displayed

=== Registered Resource Types === Resource Type: resourceType:1.0 RT_description: pnbmc server for Sun Cluster RT_version: 1.0 API_version: 2 RT_basedir: /opt/resourceType/bin Single_instance: False Proxy: False Init_nodes: All potential masters Installed_nodes: <All> Failover: False Pkglist: resourceType RT_system: False
The variable resourceType is the resource type created using the agent builder as described in the procedure Creating the BMC ProactiveNet resource type on page 178.

A high-availability resource group contains the following types of resources:
s
Logical hostname resource - Network address resource, which is an instance of
the Logical Hostname built-in resource type.

s
Application resource - High-availability resource, which is an instance of the
BMC ProactiveNet resource type created by using the agent builder.
180
1 Create an ordered list of zones for the resource group by entering the following
command:
clresourcegroup create -n nodeZoneList resource
The variable nodeZoneList specifies a comma-separated, ordered list of zones for this resource group, and the variable resource specifies the name of the highavailability resource group that you want to create. For example:
clresourcegroup create n pacific, atlantic pnbmc_rg clresourcegroup show -v pnbmc_rg
The following output is displayed.

=== Resource Groups and Resources === Resource Group: pnbmc_rg RG_description: <NULL> RG_mode: Failover RG_state: Managed RG_project_name: default RG_affinities: <NULL> RG_SLM_type: manual Auto_start_on_new_cluster:True Failback: False Nodelist: pacific atlantic Maximum_primaries: 1 Desired_primaries: 1 RG_dependencies: <NULL> Implicit_network_dependencies: True Global_resources_used: <All> Pingpong_interval: 60 Pathprefix: <NULL> RG_System: False Suspend_automatic_recovery: False
2 Add a Logical Host Name Resource to the resource group by entering the
following command: clreslogicalhostname create -g resourceGroup -h hostNameList resource The variable resourceGroup specifies the name of the resource group in which this resource resides. The variable hostNameList specifies a comma-separated list of UNIX logical host names by which clients communicate with services in the resource group. The variable resource specifies an optional resource name of your choice. For example:
clreslogicalhostname create -g pnbmc_rg -h artic pnbmc_lg clresource show pnbmc_lg
Chapter 15
181

=== Resources === Resource: pnbmc_lg Type: SUNW.LogicalHostname:2 Type_version: 2 Group: pnbmc_rgp R_description: Resource_project_name: default Enabled {pacific}: True Enabled {atlantic}: True Monitored {pacific}: True Monitored {atlantic}: True
3 Add a BMC ProactiveNet application resource to the resource group by entering

the following command:
clresource create -g resourceGroup -t resourceType \ [-p"extension-property [{nodespecifier}]" =value ...] [-p standardProperty=value ...] resource
The variable resourceGroup specifies the name of a high-availability resource group. This resource group must already exist. The variable resourceType specifies the name of the resource type for the resource. The variable standardProperty=value specifies a comma-separated list of standard properties that you set for the resource. The standard properties that you can set depend on the resource type. The variable resource is the name of the resource to add. For example:
clresource create g pnbmc_rg t SUNW.pnbmc-p Network_resources_used=pnbmc_lg pnbmc clresource show pnbmc
The following output is displayed:

=== Resources === Resource: pnbmc Type: SUNW.pnbmc:1.0 Type_version: 1.0 Group: pnbmc_rg R_description: Resource_project_name: default Enabled {pacific}: True Enabled {atlantic}: True Monitored {pacific}: True Monitored {atlantic}: True
For example,
clresource create g resourceType_rg t RTRFileName p Port_list=2638/tcp, 12128/tcp integrationServicePortNumber/tcp -p Network_resources_used=resourceType_lg resourceType
182
Customizing the scripts to achieve BMC ProactiveNet application high-availability
4 Tune the BMC ProactiveNet application resource properties to achieve highavailability by using the following formula: Retry_Interval = (Thorough_probe_interval + Probe_timeout) * 2 * Retry_count Thorough_probe_interval is the time interval that the probe command sleeps. The default is 60 seconds. To account for the time that it takes to bring the BMC ProactiveNet Server up, set this value to 3600 seconds. Retry_Count specifies the number of restart attempts. The default is 2. BMC recommends that you set this value to 1 or 0 to achieve efficient high-availability. For the BMC ProactiveNet application, it is set to 1.
5 Run the following commands for the BMC ProactiveNet application to set the
Thorough_probe_interval and the Retry_Count:
clresource set p START_TIMEOUT=3600 resourceType clresource set p STOP_TIMEOUT=500 resourceType clresource set p Thorough_probe_interval=600 resourceType clresource set p Retry_Count=1 resourceType

The scripts are generated while creating the cluster resource type. On each node in the cluster, edit the appropriate scripts to:
s s s s
Disable the PMF monitoring Get the proper license files Start the BMC ProactiveNet application Enable the cron jobs
The scripts are available under the /bin directory of the Solaris package generated by the agent builder.
To customize scripts to achieve high-availability 1 Open the start script (resourceType_svc_start.ksh) for editing. 2 Disable the PMF monitoring by entering the following command:
pmfadm -s $PMF_TAG -a "$action -R $RESOURCE_NAME -G $RESOURCEGROUP_NAME\-T $RESOURCETYPE_NAME" $start_cmd_args
Chapter 15
183
The daemon under the control of the Sun Cluster Process Monitor Facility starts. Let it crash and invoke the action script provided. The action script will restart the resource or enable high-availability and will return a non zero exit status to cease the process monitor facility.
3 At the end of the PMF monitoring command in resourceType_svc_start.ksh file, add

the following lines under the User added code placeholder section and before the line exit 0. # User added code -- BEGIN
update_license_file /usr/pw/pronto/bin/pw system start enable_cron
# User added code -- END
4 Copy the node-specific license files to the /usr/pw/licenses directory and add the
appropriate extension as follows:
s
Rename the license files targeted to the primary node with the extension
.primary
Rename the license files targeted to the secondary node with the extension
.secondary
The files should look as follows:

/usr/pw/licenses/*.primary /usr/pw/licenses/proactivenet.lic.primary /usr/pw/licenses/proactivenet.sign.primary /usr/pw/licenses/*.secondary /usr/pw/licenses/proactivenet.lic.secondary /usr/pw/licenses/proactivenet.sign.secondary
5 Above MAIN in the start script, provide the proper licenses and enable cron jobs
for BMC ProactiveNet as described in the following steps:
A On the primary node, update the license files by entering the following
commands:
update_license_file() { cp /usr/pw/licenses/proactivenet.lic.primary /usr/pw/licenses/proactivenet.lic cp /usr/pw/licenses/proactivenet.sign.primary /usr/pw/licenses/proactivenet.sign }
B On the secondary node, update the license files by entering the following
commands:
184
update_license_file() { cp /usr/pw/licenses/proactivenet.lic.secondary /usr/pw/licenses/proactivenet.lic cp /usr/pw/licenses/proactivenet.sign.secondary /usr/pw/licenses/proactivenet.sign }
C Create a cron folder in the /usr/pw/ directory and a file called cron_entries in the
/usr/pw/cron/ directory and add the following lines: # begin_pronto -- DO NOT DELETE THIS LINE! # # the following entry is added for BMC ProactiveNet ## Changed on Mar 13, 2009 10:31:53:AM PST # # 15 * * * * /usr/pw/pronto/bin/hourlyjobs > /usr/pw/pronto/tmp/hrjob.log 2>&1 30 3 * * 1-6 /usr/pw/pronto/bin/dailyjobs hosts > /usr/pw/pronto/tmp/dajob$$.log 2>&1 30 4 * * 0 /usr/pw/pronto/bin/weeklyjobs hosts > /usr/pw/pronto/tmp/wkjob$$.log 2>&1 30 5 * * 0 /usr/pw/pronto/bin/pw database archive /usr/pw/dbarchive send-email > /usr/pw/pronto/tmp/dbarchive$$.log 2>&1 0,15,30,45 * * * * /usr/pw/pronto/bin/check_pronetprocs > /usr/pw/pronto/tmp/che ck_pronetprocs.log 2>&1 ## end_pronto -- DO NOT DELETE THIS LINE!
D To enable the cron jobs, specify the following path in the start script:
enable_cron() { crontab -l > /tmp/$$current_cron while read line; do echo "$line" >> /tmp/$$current_cron done < /usr/pw/cron/cron_entries crontab < /tmp/$$current_cron rm /tmp/$$current_cron }
6 Save and close the start script. 7 Open the stop script (resourceType_svc_stop.ksh) and edit it to disable the cron
jobs and stop the BMC ProactiveNet application as described in the following steps.
Chapter 15
185
A Add the following lines to the stop script:

# The Data service is not running as of now. Log a message and # exit suceess. # SCMSGS # @explanation # Need explanation of this message! # @user_action # Need a user action for this message. scds_syslog -p error -t "${SYSLOG_TAG}" -m \ "resourceType not already running" /usr/pw/pronto/bin/pw system stop disable_cron # Even if the resourceType is not running, we exit success, # For idempotency of # the STOP method. exit 0
B Above the Main section in the stop script, add the following function:
disable_cron() { crontab -l | sed -e /pronto/d|sed -e /ProactiveNet/d > /tmp/$$pronto crontab < /tmp/$$pronto rm /tmp/$$pronto }
8 Save and close the stop script. 9 Open the probe script (resourceType_probe.ksh) and add the following lines to
support manual shutdown of the BMC ProactiveNet application:
if [[ -e "/usr/pw/pronto/tmp/system.start" ]]; then if [[ -f $probe_cmd_prog && -x $probe_cmd_prog ]]; then hatimerun -t $PROBE_TIMEOUT $probe_cmd_args # User added code -- BEGIN vvvvvvvvvvvvvvv # User added code -- END ^^^^^^^^^^^^^^^ else # We were not supplied with a probe command. We will use the # simple_probe that comes bundled as an utility. hatimerun -t $PROBE_TIMEOUT $RT_BASEDIR/simple_probe \ -R $RESOURCE_NAME -G $RESOURCEGROUP_NAME \ -T $RESOURCETYPE_NAME # User added code -- BEGIN vvvvvvvvvvvvvvv # User added code -- END ^^^^^^^^^^^^^^^ fi else continue fi
10 Save and close the probe script.
186
Running BMC ProactiveNet in high-availability mode
Running BMC ProactiveNet in high-availability mode

1 After making the necessary changes in the generated scripts, stop the BMC
ProactiveNet Server.
2 Bring the BMC ProactiveNet resource group online on the primary node of the
cluster by executing the command in Bringing a resource group online on page 187.
Bringing a resource group online

Execute the following commands to bring the resource group online:
clresourcegroup online -emM resourceGroupName clresourcegroup online -emM resourceType_rg
Manually switching the BMC ProactiveNet application to the standby node

If you want to switch the BMC ProactiveNet application to the standby node in the cluster, you can switch manually by using the following command:
# clresourcegroup switch [-n node] resource_group
s
-n node specifies the name of the node on which the resource group is to be switched resource_group specifies the name of the resource group of the node to which you are switching
For example:
clresourcegroup switch n atlantic pnbmc_rg
This command switches the BMC ProactiveNet application to the standby node, atlantic, from the primary node in the pnbmc_rg resource group.
Chapter 15
187
Disabling failover for BMC ProactiveNet
Disabling failover for BMC ProactiveNet

If you do not want the primary node to switch to the standby node (for example, when the standby node is shut down for maintenance), you can disable failover. You can disable the failover feature by taking the resource group of the primary node offline by using the following command:
clresourcegroup offline resource_group
For example:
clresourcegroup offline pnbmc_rg clresourcegroup status

=== Cluster Resource Group Name Node Name ---------- --------pnbmc_rgp pacific No atlantic No Offline Groups === Suspended Status --------- -----Offline
Configuring high-availability remote cells for viewing in the Operations Console

You can view events on a remote cell in high-availability mode once you configure the remote cell so that it can be viewed in the Operations Console.
To configure a remote cell in high-availability mode for viewing in the Operations Console 1 Add an entry for the remote cell and its counterpart in high-availability mode in
the installDirectory \pw\pronto\conf\cell_info.list file as follows:
cell cellName encryptionkey computer1NameWithDomain: portOnWhichCellIsInstalled computer2NameWithDomain: portOnWhichHACellIsInstalled Production *
For example, cell testcell mc testcomp: 1828 hacomp: 2251 Production *
2 Add an entry for the remote cell and its counterpart in high-availability mode in
the serverInstallationDirectory\server\etc\mcell.dir file as follows:
cell cellName mc computer1NameWithDomain: portOnWhichCellIsInstalledcomputer2NameWithDomain: portOnWhichHACellIsInstalled
3 Restart the jserver process. 4 Click OK.
Chapter 15
189
190
Chapter
16
16
Uninstalling BMC ProactiveNet

Should a problem occur that causes an unstable or unusable installation of the product, you can use the procedures described in this chapter to uninstall BMC ProactiveNet.
Uninstalling the BMC ProactiveNet Server on Windows

To uninstall the BMC ProactiveNet Server for Windows 1 Choose Start => Programs => BMC ProactiveNet Server => Uninstall BMC ProactiveNet
Server.
2 On the welcome screen, click Next to uninstall the BMC ProactiveNet Server. 3 On the Uninstallation Preview screen, click Uninstall. 4 On the Uninstallation Summary screen, click View Log to view the uninstallation
logs or click Done.
NOTE
After uninstalling BMC ProactiveNet Server, restart the computer and delete any installation directories or files that remain.
Chapter 16
191
Uninstalling the BMC ProactiveNet Server with Oracle backend
Uninstalling the BMC ProactiveNet Server with Oracle backend

If the Oracle database goes down before uninstallation, the following message is displayed: Oracle database is currently unavailable. Please cleanup the Oracle Schema manually... Uninstallation will go through without deleting the database objects and you will be asked to clean the database manually. The following error message is logged in the uninstallation logs when the Oracle database goes down before the uninstallation. Oracle database is currently unavailable and the schema could not be dropped. Please drop the Oracle Schema manually! When the Oracle database goes down while deleting the database objects, the following error message will be logged in the uninstallation logs. Failed to execute the command: <Installation Directory>/runjava scripts.DropSchema with return code: <Error Code>
Uninstalling the BMC ProactiveNet Agent on Windows

To uninstall the BMC ProactiveNet Agent for Windows 1 On the computer where you installed the BMC ProactiveNet Agent, open the
Control Panel.
2 In the Control Panel, under Programs click on Uninstall a program. 3 To open the uninstallation wizard, select BMC ProactiveNet Performance
Management Agent 8.6.01, and click Uninstall/Change.
4 On the welcome screen, click Next to uninstall the BMC ProactiveNet Agent. 5 On the Uninstallation Summary screen, click View Log to view the uninstallation
logs or click Done.
192

This section explains how to uninstall the BMC ProactiveNet Server from a Solaris computer.
Before you begin

If you are a non-root user and you want to uninstall BMC ProactiveNet Server, the following directory and file must be removed by a root user before a non-root user can proceed with the uninstallation:
/etc/init.d/BMCImpactIBRSD
/usr/pw/pronto/conf/resources/en_US/kbinfo/kb_core_resource.properties
To uninstall ProactiveNet Server 1 Go to <install directory>/uninstallBPPMServer directory. 2 Execute the uninstall command.
Uninstalling the BMC ProactiveNet Agent on UNIX-based operating systems

This procedure will remove all files, programs, saved data, and related directories of your Agent (UNIX) installation. Uninstalling the BMC ProactiveNet Agent will also uninstall the cell.
NOTE
To ensure that the related directories are removed, restart your server after uninstalling the BMC ProactiveNet Agent. Under some conditions, the related directories are removed only after restart.
To uninstall the BMC ProactiveNet Agent on UNIX 1 Go to <install directory>/uninstallBPPMAgent directory. 2 Execute the uninstall command.
Chapter 16
193
Uninstalling the BMC ProactiveNet Server on a cluster in high-availability mode on Windows
NOTE
When you uninstall the BPPMAgent on a HPUX computer, sometimes the uninstallation does not remove the jre directory under the installation folder. Manually delete the folder.
Uninstalling the BMC ProactiveNet Server on a cluster in high-availability mode on Windows

Before you begin
Ensure that you restart the computer before uninstalling the BMC ProactiveNet Server on Primary node.
To uninstall the BMC ProactiveNet Server for Windows on primary node 1 Choose Start => Programs => BMC ProactiveNet Server => Uninstall BMC ProactiveNet
Server.
2 On the Confirm Uninstall screen, click OK to uninstall BMC ProactiveNet Server. 3 When uninstallation is successful, you will be prompted to restart your system. NOTE
After uninstalling BMC ProactiveNet Server, reboot the computer and delete any installation directories or files that remain.
To uninstall the BMC ProactiveNet Server for Windows on standby node 1 Go to the root drive of the install directory. Navigate to /standByuninstall/UninstallBPPMServer. 2 Execute the uninstall.exe command to uninstall the BMC ProactiveNet Server. NOTE
Ignore the severe messages displayed while uninstalling the BMC ProactiveNet Server from the standby node.
3 Delete the standByuninstall folder in the root drive of the install directory after
uninstallation is complete.
194
Uninstalling the BMC ProactiveNet Agent on a cluster in high-availability mode on Windows
Uninstalling the BMC ProactiveNet Agent on a cluster in high-availability mode on Windows

To uninstall the BMC ProactiveNet Agent for Windows on primary node 1 On the computer where you installed the BMC ProactiveNet Agent, open the
Control Panel.
2 In the Control Panel, double-click Add/Remove Programs to open the Add/Remove

Programs window.
3 To open the uninstallation wizard, select BMC ProactiveNet Agent, and click
Change/Remove.
4 On the Confirm Uninstall screen, click OK to uninstall BMC ProactiveNet Server. 5 On the Maintenance Complete screen, click Finish to complete the uninstallation. To uninstall the BMC ProactiveNet Agent for Windows on standby node 1 Go to the root drive of the install directory. Navigate to /standByuninstall/UninstallBPPMAgent. 2 Execute the uninstall.exe command to uninstall the BMC ProactiveNet Agent. NOTE
Ignore the severe messages displayed while uninstalling the BMC ProactiveNet Agent from the standby node.
Uninstalling the BMC ProactiveNet Server on a cluster in high-availability mode on UNIXbased operating systems
To uninstall the BMC ProactiveNet on a cluster 1 Go to <install directory>/uninstallBPPMServer directory. 2 Execute the uninstall command.
Chapter 16
195
Uninstalling the BMC ProactiveNet Administration Console on UNIX-based operating systems
Uninstalling the BMC ProactiveNet Administration Console on UNIX-based operating systems

The following procedure removes all files, programs, saved data, and related directories of the Administration Console installation.
To uninstall the Administration Console on UNIX 1 From a command line, access the
admin_console_installDirectory/UninstallBMCProactiveNet directory.
2 Run the following command: ./uninstall 3 At the prompt, confirm the removal of the Administration Console. 4 To ensure that related directories are removed, restart the host.
Removing the Oracle database objects

If the Oracle database objects are not deleted while uninstalling BMC ProactiveNet Performance Management, you can delete them manually. Run cleanup_db.sql script in the install directory under Server_pw_vrxx_bxxxxxxx\Utilities\oracle\db_cleanup_script.
Removing the schema from the Oracle database

If the Oracle objects were not deleted during uninstall, you can delete them manually or use the scripts provided with BMC ProactiveNet Performance Management.
To remove the schema from the Oracle database 1 The cleanup_db.sql script is present in the DVD under
Utilities\oracle\db_cleanup_script.
2 Copy the cleanup_db.sql script to the Oracle server machine and run the script after
logging in with the schema user created for BMC ProactiveNet Performance Management.
196
Chapter 16
197
198
Appendix
Reconnecting to the BMC ProactiveNet database

A
This feature allows you to reconnect to the database if the database connection is lost. The database connection maybe lost due to many factors such as, network latency and unresponsive database due to high system load. This is applicable only for Oracle database. The database reconnection feature does not support the following features:
s s s s s s s s s s s s
Auto Work Flow Detailed Diagonstics Graphs SLA Groups Updating Meta information and MetaCache Partitioning Baselining Schema creation during installation Monitor wizard Device deprovisioner PW scripts
If the database connection goes down for more than one minute and if the connection is not established, the Administrator is notified that there is problem connecting to the database.
Appendix A Reconnecting to the BMC ProactiveNet database
199
To reconnect to the database 1 Check the e-mail and the ProactiveNet.log for the error Failed to establish
DB connection after retries.
2 Check the network connection and the database server status. 3 Restart the BMC ProactiveNet Server after restoring the database connection.
Following is an example of the e-mail sent to the Administrator.
EXAMPLE
Hello, The BPPM server running on "kali" server has not been able to establish connectivity with the database. Please address the database connectivity problem and restart the BPPM server. Database server details Database Host: v3-w23-rds2059:1521 SID: ngp11 Status: Unreachable - BPPM Server.
200
Book Title
Notes
*203083* *203083* *203083* *203083*

*203083*

BMC ProactiveNet

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

BMC ProactiveNet

Transféré par

Droits d'auteur :

Formats disponibles

BMC ProactiveNet Getting Started Guide

Contacting BMC Software

United States and Canada

Outside United States and Canada

Restricted rights legend

Support by telephone or e-mail

Before contacting BMC

License key and password information