ProactiveNet Deployment Guide v8.5

www.bmc.com

BMC ProactiveNet Deployment Guide

Supporting

BMC ProactiveNet version 8.5

October 2010

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 INC2101 CITYWEST BLVDHOUSTON TX 77042-2827 USA

Telephone 713 918 8800 or800 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.

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.

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 legendU.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.”

http://www.bmc.com

Support website

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

■ read overviews about support services and programs that BMC offers■ find the most current information about BMC products■ search a database for 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 [email protected]. (In the subject line, enter SupID:<yourSupportContractID>, such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.

Before contacting BMC

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

■ product information

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

■ operating system and environment information

— machine type— operating system type, version, and service pack or other maintenance level such as PUT or PTF— system hardware configuration— serial numbers— related software (database, application, and communication) including type, version, and service pack or

maintenance level

■ sequence of events leading to the issue

■ commands and options that you used

■ messages received (and the time and date that you received them)

— product error messages— messages from the operating system, such as file system full— messages from related software

3

http://www.bmc.com/support

mailto:[email protected]

License key and password information

If you have questions about your license key or password, use one of the following methods to get assistance:

■ Send an e-mail message to [email protected].

■ Use the Customer Support website at http://www.bmc.com/support.

4 BMC ProactiveNet Deployment Guide

mailto:[email protected]


ContentsChapter 1 About This Guide 9

Documents You May Need. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9BMC ProactiveNet Performance Management Documentation . . . . . . . . . . . . . . . 9BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10BMC BladeLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11BMC Atrium Discovery and Dependency Mapping . . . . . . . . . . . . . . . . . . . . . . . . 11BMC Atrium Orchestrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12BMC AppSight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12BMC Remedy Action Request System Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2 BMC ProactiveNet overview 15

What is BMC ProactiveNet? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15BMC ProactiveNet components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

BMC ProactiveNet server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16BMC ProactiveNet agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16BMC ProactiveNet monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17BMC ProactiveNet Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17BMC ProactiveNet Operations Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18BMC ProactiveNet SLO Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18BMC ProactiveNet Integration Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18BMC Impact Model Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19BMC Impact Event Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19BMC ProactiveNet CMDB extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19BMC ProactiveNet Performance Management Web Services . . . . . . . . . . . . . . . . 19

BMC ProactiveNet integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20BMC Atrium Configuration Management Database (CMDB) . . . . . . . . . . . . . . . . 20BMC ProactiveNet Performance Management Reporting . . . . . . . . . . . . . . . . . . . 20BMC Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20BMC Transaction Management Application Response Time (BMC TM ART) . . 21BMC Atrium Orchestrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21BMC BladeLogic Service Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21BMC IT Service Management (BMC ITSM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21BMC Atrium Discovery Dependency Mapping (BMC Atrium Discovery) . . . . . 22BMC ProactiveNet Application Diagnostics (BMC AppSight integration) . . . . . 22BMC PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 3 End-to-End Monitoring 23

BMC Products Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Contents 5

Deployment Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Hardware Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Platform Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Database Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Licensing Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Achieving End-to-End Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Deployment Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 4 Monitoring and Event Management Using BMC ProactiveNet Performance Management 29

Platform Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Products Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Installing BMC ProactiveNet Performance Management . . . . . . . . . . . . . . . . . . . . . . . 30

Installation Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Installing and Configuring BMC ProactiveNet Performance Management . . . . . 31

Deployment Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 5 Probable Cause Analysis 33

BMC Products Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Deployment Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Hardware Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Platform Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Database Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Licensing Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Configuring BMC ProactiveNet and BMC BladeLogic for Probable Cause Analysis 35Deployment Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 6 BMC Triage and Remediation Solution and IBRSD Integration 37



Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Deployment Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Chapter 7 Integrating BMC Atrium Discovery Dependency Mapping with BMC ProactiveNet Performance Management 43



Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Deployment Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47


Chapter 8 Configuring BMC ProactiveNet Application Diagnostics (BMC AppSight Integration) 49

BMC Products Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Deployment Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Hardware Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Platform Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Database Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Licensing Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Deployment Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 9 Known Issues 55

Installation on unsupported platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Installing multiple BMC ProactiveNet agents on a system. . . . . . . . . . . . . . . . . . . 55Conflicting ports between BMC Remedy Action Request System Server and BMC

Atrium Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Creating an incident in BMC Remedy Action Request System fails . . . . . . . . . . . 56Incident creation fails for BMC Remedy ITSM 7.6.00 Patch 1 . . . . . . . . . . . . . . . . 57

Appendix A Port Usage 59

Appendix B Additional Configurations 63

Configuring terminal services to save log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Licensing the BMC ProactiveNet server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Licensing BMC Remedy AR Server applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Licensing the BMC BladeLogic RSCD agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Configuring the BMC Integration service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Configuring Notification Engine for version 7.5.00 patch 5 of BMC Atrium CMDB 65Configuring BMC ProactiveNet CMDB Extensions on a BMC Remedy ITSM server

group environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Configuring BMC BladeLogic for probable cause analysis . . . . . . . . . . . . . . . . . . . . . . 69Configuring BMC ProactiveNet Performance Management for the BMC Triage and

Remediation solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Configuring the BMC Atrium Orchestrator grid for the BMC Triage and

Remediation solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Configuring BMC Atrium Orchestrator for the BMC Triage and Remediation

solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Products and artifacts installed by the BMC Atrium Orchestrator content installer for

the BCM Triage and Remediation solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Ensuring the correct AR System server user permissions for IBRSD integration . . . 73Configuring BMC Atrium CMDB and BMC Atrium Discovery synchronization . . . 74Configuring BMC ProactiveNet Application Diagnostics components (BMC

AppSight Integration). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Removing BMC AppSight connector services from a previous version of BMC

ProactiveNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Configuring and capturing in BMC AppSight for Java EE . . . . . . . . . . . . . . . . . . . 75Capturing in BMC AppSight for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Contents 7

Configuring the BMC AppSight Repository server . . . . . . . . . . . . . . . . . . . . . . . . . 77Configuring the connection between BMC ProactiveNet and the BMC AppSight

Repository server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Configuring BMC TM ART for BMC ProactiveNet Application Diagnostics . . . 80


C h a p t e r 1
1 About This Guide
This guide is written for system administrators who plan to deploy version 8.5 of the BMC ProactiveNet Performance Management product and integrate it with other BMC products. This guide also contains visual depictions of the deployment architecture to help system administrators understand how various BMC modules work with one another in multiple deployment environments.

System administrators who perform the procedures in this guide must possess at least an average understanding of the various BMC products and components mentioned. If you are a new user of BMC products, read the documents in the “Documents You May Need” section before performing the procedures mentioned in this guide.

Documents You May NeedThe procedures in this guide require you to read documentation of the respective products you are deploying. This section lists the location of the BMC product documentation you should review and understand in order to carry out the deployment. All of this documentation is available on the BMC Support website at http://www.bmc.com/support. You must have member privileges on this website in order to access the documentation.

BMC ProactiveNet Performance Management Documentation

The BMC ProactiveNet Performance Management documentation is available at http://webapps.bmc.com/support/faces/prodallversions.jsp?seqid=172810.

Table 1 on page 10 lists the BMC ProactiveNet Performance Management documents that you may find useful during the deployment.

Chapter 1 About This Guide 9

http://webapps.bmc.com/support/faces/prodallversions.jsp?seqid=172810


BMC Atrium CMDB

BMC Atrium CMDB

The BMC Atrium CMDB documentation suite is available at http://webapps.bmc.com/support/faces/prodallversions.jsp?seqid=176446.

Table 2 on page 11 lists the BMC Atrium CMDB documents that you may find useful during the deployment.

Table 1 BMC ProactiveNet Performance Management documentation

Document Description

BMC ProactiveNet Getting Started Guide

Contains detailed descriptions about installing the BMC ProactiveNet server and agent on various operating systems and also contains the prerequisites for such an installation

This guide also contains information about installing BMC Atrium CMDB Extensions. The BMC Atrium CMDB Extensions installer is shipped on the BMC ProactiveNet installation media.

BMC ProactiveNet User Guide Contains descriptive information about using BMC ProactiveNet Performance Management

BMC ProactiveNet Administrator Guide

Contains details about administering BMC ProactiveNet Performance Management and using the BMC ProactiveNet Administration Consol.

BMC ProactiveNet Performance Management Web Services Server Getting Started Guide

Contains configuration information about how to get the BMC ProactiveNet Performance Management Web Services running and use it to send events

BMC ProactiveNet Performance Management Triage and Remediation Solution Getting Started Guide

Describes the business value, installation and configuration guidelines, workflows, and customization guidelines for the triage and remediation solution that links BMC ProactiveNet and BEIM with BMC Atrium Orchestrator

BMC ProactiveNet Performance Management Release Notes

Describes the components and download files for the base license and license add-ons that are available with this solution



BMC BladeLogic

BMC BladeLogic

The BMC BladeLogic documentation is available at http://webapps.bmc.com/support/faces/prodallversions.jsp?seqid=164625.

Table 3 on page 11 lists the BMC BladeLogic documents that you may find useful during the deployment.

BMC Atrium Discovery and Dependency Mapping

The BMC Atrium Discovery and Dependency Mapping documentation is available at http://webapps.bmc.com/support/faces/prodallversions.jsp?seqid=169113.

Table 2 BMC Atrium CMDB documentation


BMC Atrium Core Quick Start card

Quick reference card for BMC Atrium Core containing an installation overview and at-a-glance information about the major constituents of the BMC Atrium Core Console

BMC Atrium Core Installation Guide

Contains information about installing, upgrading, and troubleshooting Atrium Core features such as BMC Atrium CMDB, BMC Atrium Integration Engine, Product Catalog, Atrium Web Services components, and BMC Atrium Impact Explorer

BMC Atrium CMDB User's Guide

Explains how to work with configuration items (CIs) and relationships using the BMC Atrium Core Console interface of BMC Atrium CMDB

BMC Atrium Core Concepts and Planning Guide

Describes the concepts underlying BMC Atrium Core products, including the BMC Atrium CMDB, BMC Atrium Product Catalog, and the BMC Atrium Integration Engine applications

Table 3 BMC BladeLogic documentation


BMC BladeLogic Installation Guide

Explains how to install all the components of the BMC BladeLogic system on all supported platforms

BMC BladeLogic Administration Guide

Explains how to perform all the tasks necessary to make the components of a BMC BladeLogic system function together

BMC BladeLogic Bulk Agent Installer User Guide

Explains how to use BMC BladeLogic’s BMC Bulk RSCD Agent Installer to install or upgrade RSCD agents on multiple servers simultaneously



BMC Atrium Orchestrator

Table 4 on page 12 lists the BMC Atrium Discovery and Dependency Mapping documents that you may find useful during the deployment.


Table 5 on page 12 lists the locations at which the BMC Atrium Orchestrator documentation is available.

BMC AppSight

The BMC AppSight documentation is available at http://webapps.bmc.com/support/faces/prodallversions.jsp?seqid=171493.

Table 4 BMC Atrium Discovery and Dependency Mapping documentation


BMC Atrium CMDB Data Modeling Guide

Lists the best practices for using the classes that BMC provides for BMC Atrium CMDB to model complex business entities

The paper focuses on the use of multiple related CIs to model an entity rather than on general information about a class or attribute.

BMC Atrium Discovery and Dependency Mapping: Planning and Installation

Describes how to plan and install BMC Atrium Discovery and Dependency Mapping

Mapping Your Data to BMC Atrium CMDB Classes

Contains mappings of common IT objects to the appropriate class

Also includes information about further categorizing instances using key attributes

Table 5 BMC Atrium Orchestrator documentation

Document Available at

BMC Atrium Orchestrator for Network Automation - Core


BMC Atrium Orchestrator for Server Automation - Core


BMC Atrium Orchestrator Platform


BMC Atrium Orchestrator Runbooks




BMC Remedy Action Request System Server


The BMC Remedy Action Request System Server documentation is available at http://webapps.bmc.com/support/faces/prodallversions.jsp?seqid=108018.

Table 7 on page 13 lists the BMC Action Request System Server documents that you may find useful during the deployment.

Table 6 BMC Remedy AR System Server documentation


BMC Remedy Action Request System Installation Guide

Contains instructions for installing BMC Remedy Action Request System Server

BMC Remedy Action Request System 7.5.00 BMC Remedy Mid Tier Guide

Contains information about configuring the BMC Remedy Mid Tier, setting up applications for the Mid Tier, and using applications in browsers

BMC Remedy Action Request System Database Reference

Contains database administration topics and rules related to how AR System interacts with specific databases; includes an overview of the data dictionary tables

BMC Remedy Action Request System Integration Guide

Contains instructions for integrating AR System with external systems by using Web services, plug-ins, and other products, including LDAP, OLE, and ARDBC





C h a p t e r 2
2 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 real-time solution for proactive detection and resolution of IT problems before they have an impact on critical IT systems. Data analytics provide the ability to combine information associated with an area of interest and drill down into specific details. The goal of data analytics is to provide a research facility to better understand, tune, and modify the selected area.

BMC ProactiveNet componentsThe following sections describe the components that comprise BMC ProactiveNet.


BMC ProactiveNet server

BMC ProactiveNet server

The BMC ProactiveNet server is the core BMC ProactiveNet component that receives events from various sources, such as the BMC ProactiveNet agents, BMC Impact Event Adapters, and BMC ProactiveNet Integration Services. Once the BMC ProactiveNet server has collected this data, it processes, and stores these events based on the processing instructions in its Knowledge Base. The BMC ProactiveNet server can also store Service Model data published from the Atrium CMDB or from other sources.

The BMC ProactiveNet server is responsible for configuring and controlling BMC ProactiveNet agents, gathering data collected by BMC ProactiveNet agents, collecting SNMP data, storing data, and presenting data in the form of graphs, reports, views, and events.

The components that comprise the BMC ProactiveNet server include:

■ BMC Service Impact Manager cell—receives the events from other cells and adapters. The contents of this cell are displayed in the Service Impact Graph.

■ BMC Administrator cell

■ BMC ProactiveNet database—a Sybase SQL Anywhere (Adaptive Server Anywhere) database that stores objects collected by the BMC ProactiveNet server such as devices, instances, monitor types, configuration, and data

■ BMC ProactiveNet agent—a 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 monitors—monitors installed with BMC ProactiveNet server that specifically monitor the health of the BMC ProactiveNet server

Other components installed with the BMC ProactiveNet server are the BMC ProactiveNet Operations Console, the BMC Administration Console, and the BMC ProactiveNet SLO Console.

BMC ProactiveNet agent

Two types of BMC ProactiveNet agents are included in the BMC ProactiveNet product.

A local agent is the BMC ProactiveNet agent that is installed with the BMC ProactiveNet server. The local agent monitors the health of the BM ProactiveNet server to ensure that the BMC ProactiveNet server runs at peak performance.


BMC ProactiveNet monitors

A remote agent is a BMC ProactiveNet agent that is installed on a computer other than the BMC ProactiveNet server. The remote agents should be installed on each network element in the enterprise that you want to monitor. They collect device-specific data such as CPU usage, memory usage, and other data specific to the host operating system. This enables the BMC ProactiveNet Server to remotely gather statistical data on all supported operating systems.

BMC ProactiveNet monitors

BMC ProactiveNet monitors are customized objects that typically collect critical data from Web site infrastructure. BMC ProactiveNet provides an extensive set of out-of-the-box monitors that collect performance data from applications, databases, middleware, firewalls, servers, network devices, and load balancers.

The following monitors indicate the overall health of the BMC ProactiveNet server and are automatically set up during the BMC ProactiveNet server installation:

■ Agent Status monitor ■ Oracle® Solaris File System monitor ■ Solaris Process monitor ■ Solaris System monitor ■ Sybase ASA Intelliscope monitor ■ Sybase Query ■ Web URL

The following monitors are automatically set up while adding or installing a BMC ProactiveNet remote agent:

■ Agent Status monitor ■ Agent System monitor ■ Agent TCP monitor ■ Ping Monitor

For more information about BMC ProactiveNet monitors, see the BMC ProactiveNet Monitor Guide.

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.


BMC ProactiveNet Operations Console

For more information about the BMC ProactiveNet Administration Console, see the BMC ProactiveNet Administration 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 information related to events, views, and graphs.

For more information, see the BMC ProactiveNet User Guide.

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

If you are using products such as BMC PATROL, HP Operations Manager, or Tivoli ITM as data sources for your enterprise, each remote BMC ProactiveNet agent hosts an Integration service that you can enable to collect data from these applications, integrating them with BMC ProactiveNet.

For more information, see the BMC ProactiveNet Administrator Guide.


BMC Impact Model Designer

BMC Impact Model Designer

BMC Impact Model Designer is a plug-in installed with the BMC Atrium Core Console 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.

The BMC Impact Event Adapters can collect source events from

■ 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 integrate BMC ProactiveNet with the BMC Atrium CMDB, so that 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.

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 integrations

BMC ProactiveNet integrationsThe 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. Customers can import the CIs from the BMC Atrium CMDB to define the devices, services, and applications that they want to monitor in BMC ProactiveNet. BMC ProactiveNet leverages the service relationship information from the configuration items (CIs) in BMC Atrium CMDB for the devices, services, and applications 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.

BMC Portal

BMC Portal provides a common Web-based interface for the BMC Performance Manager Portal and BMC Impact Portal software modules. BMC Performance Manager 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 Impact Portal provides views of business services and shows how the status of these services is impacted when infrastructure components have problems. 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 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 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 Service Automation

BMC BladeLogic Service Automation suites help 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.

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


BMC Atrium Discovery Dependency Mapping (BMC Atrium Discovery)

to incidents by enabling bidirectional flow of information between BMC Service Impact Manager (BMC SIM) or BMC Event Manager (BMC EM) 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.

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 PATROL

BMC PATROL provides consolidated system, network, and service-level management for high-value business applications across a heterogeneous enterprise. Through its management displays, you can integrate and customize all organization-wide event information. From a central point of control, operators can monitor and manage your enterprise’s applications, tools, networks, and IT components (such as mainframes, telecommunication devices, ATMs, and so on).


C h a p t e r 3
3 End-to-End Monitoring
BMC monitoring tools collect and leverage data and improve the availability of IT systems. Integrating BMC ProactiveNet Performance Management with BMC Atrium CMDB helps make better decisions by linking business impact and IT data.

Install and configure the BMC ProactiveNet agent to run the Integration Service and extract systems, processes, disk file systems, VMware systems, and database performances through PATROL or HP OVO agents.

Integrating BMC ProactiveNet Performance Management with BMC TM ART monitors the performance and reliability of Web-based applications.

BMC Products RequiredYou need to install the following BMC products to integrate BMC ProactiveNet Performance Management with BMC TM ART:

■ BMC ProactiveNet Performance Management

■ BMC Performance Manager Portal

■ BMC Performance Manager Portal Datastore

■ BMC PATROL (Patrol Console Server/RT Server/Central Operator)

■ BMC TM ART (Central Server, Execution Server, and BMC TM ART Workbench)

■ BMC Remedy Action Request System

■ BMC Remedy Action Request System or BMC Atrium CMDB or BMC Remedy Mid-Tier or BMC IT Service Management or BMC Service Level Management

■ BMC Remedy IT Service Management


Deployment Considerations

■ BMC Atrium CMDB Web Services

For information about these products, see the “Documents You May Need” section.

Deployment ConsiderationsThis section lists the hardware, software, and licensing considerations to integrate BMC ProactiveNet Performance Management with BMC TM ART.

Hardware Considerations

Ensure that the following deployment is in place to achieve end-to-end monitoring:

■ A minimum of 11 servers

■ Products in “BMC Products Required” must be installed on different servers. BMC TM ART central server, execution server, and the workbench must also be installed on separate servers.

Platform Considerations

The operating systems that support the BMC products listed in “BMC Products Required” are listed in the Release Notes of the respective product. See the ‘Other Documents You May Need’ section for the location of the Release Notes.

Database Considerations

Table 8 lists the databases that the products in the “BMC Products Required” section use.


Licensing Considerations


BMC ProactiveNet Performance Management, BMC Performance Manager Portal, BMC PATROL, and BMC Remedy Action Request System Server, and BMC Atrium CNDB require licenses. For information about obtaining and applying licenses, see the “Documents You May Need” section.

Achieving End-to-End Monitoring

The following procedure is high-level overview of the steps to leverage the data collected by BMC Performance Manager Portal, BMC PATROL, and BMC TM ART (BMC monitoring tools). For the detailed installation steps for these products, see the “Documents You May Need” section.

1 Ensure that the supported databases in Table 8 on page 25 are running on an identified system, for example Server-1 and are available for use.

2 Install the following components of BMC Remedy Action Request System on another system, for example Server-2, using the databases on Server-1.

Table 8 Supported databases

Product Database

BMC ProactiveNet Performance Management Sybase SQL Anywhere (Adaptive Server Anywhere) version 11.01

BMC Performance Manager Portal Oracle and the BMC Performance Manager Portal Datastore. The datastore installs Oracle binaries and creates the database for BMC Performance Manager Portal.

BMC TM ART Oracle and Microsoft SQL Server

BMC Remedy Action Request System ■ Oracle, Microsoft SQL, IBM(R) DB2(R) (on Microsoft Windows and UNIX operating systems)

■ IBM Informix(R) and Sybase SQL Anywhere (Adaptive Server Anywhere) version 11.01 (on UNIX operating systems)

See the BMC Remedy Action Request System Release Notes for more information about the supported databases on BMC Remedy Action Request System.


Achieving End-to-End Monitoring

■ BMC Remedy Action Request System Server

■ Approval Server

■ Assignment Engine

■ BMC Remedy Action Request System User

3 Install BMC Atrium CMDB and Product Catalog.

4 Obtain and apply licenses to the BMC Remedy Action Request System and BMC Atrium CMDB modules.

5 Install BMC ProactiveNet CMDB Extensions.

6 Install BMC Remedy Mid-Tier on Server-3.

7 Install the following components of BMC Atrium Web Services on Server-4:

■ BMC Atrium Core Web Services

■ BMC Web Services Infrastructure

■ BMC Web Services Registry

8 Install the following components of BMC PATROL on Server-5:

■ PATROL Console Server

■ PATROL RT server

■ PATROL Central Operator

9 Install the following components of BMC Performance Manager Portal on three different systems (Server-6, Server-7, Server-8):

■ BMC Performance Manager Portal Datastore (on Server-6). Ensure that this system contains a static IP address.

■ BMC Performance Manager Portal (on Server-7)

■ RSM (on Server-8)

10 Install the following components of BMC TM ART on two different systems (Server-9 and Server-10). Ensure that the database installed on BMC Performance Manager Portal can be used for BMC TM ART.

■ BMC TM ART Central Server (on Server-9)


Deployment Architecture

■ BMC TM ART Execution Server (on Server-10)

■ BMC TM ART Workbench (on Server - 10)

11 Install BMC ProactiveNet Performance Management on Server-11. Enable the Integration service and select to integrate with BMC Atrium CMDB. For more information, see “Installing BMC ProactiveNet Performance Management.”

12 Install the PATROL agent and the required PATROL KMs on the target servers that are to be monitored.

13 Verify the BMC ProactiveNet Performance Management-BMC Atrium CMDB integration by performing the following steps:

■ Launch the BMC ProactiveNet User Console

■ Verify that you can launch the BMC Atrium Core Console from the BMC ProactiveNet User Console. For information about doing this, see the BMC ProactiveNet Administrator Guide.

14 Launch the BMC ProactiveNet Administration Console and add the following adapters:

■ BMC PATROL adapters

■ BMC Performance Manager Portal adapters

■ BMC TM ART adapters

Deployment ArchitectureThe figure below depicts the minimum required configuration for each product to deploy end-to-end monitoring.



Figure 1 Physical layout of end-to-end monitoring


C h a p t e r 4
4 Monitoring and Event Management Using BMC ProactiveNet Performance Management
The out-of-the-box features and configurations of BMC ProactiveNet Performance Management help solve IT issues before administrators get a chance to experience the problems. These features identify the cause of the problem and help make better decisions by linking business impact and IT data. BMC ProactiveNet Performance Management provides unified management across physical and virtual environments.

Platform RequirementsFor information about hardware, software, and database requirements of BMC ProactiveNet Performance Management, see the BMC ProactiveNet Performance Management Release Notes. See the ‘Other Documents You May Need’ section for the location of these Release Notes.

Products RequiredYou need to install BMC ProactiveNet Performance Management to perform monitoring and event management tasks.


Installing BMC ProactiveNet Performance Management

Installing BMC ProactiveNet Performance Management

This section lists the high-level steps to help you install and get started with BMC ProactiveNet Performance Management. For information about detailed procedures and steps, see the BMC ProactiveNet Performance Management Getting Started Guide. See the ‘Other Documents You May Need’ section for the location of this guide.

Installation Prerequisites

■ Ensure that your system meets the minimum configuration mentioned in the BMC ProactiveNet Performance Management Release Notes.

■ Ensure that you have root (for Solaris systems)/administrative (for Microsoft Windows systems) privileges.

■ If you are using Microsoft Windows, configure terminal services to save the log files. See “Configuring terminal services to save log files”.

■ If you are using Microsoft Windows 2008, turn off user access control. For information about this procedure, see the Microsoft website (technet.microsoft.com).

■ If you are using Solaris, apply the recommended patches. The recommended patches are listed during the installation procedure. You can also see the BMC ProactiveNet Performance Management Release Notes for patch requirements.

■ Ensure that the ports listed in Appendix A, “Port Usage” are available to use.

■ Install BMC ProactiveNet CMDB Extensions if you want to integrate BMC ProactiveNet Performance Management with BMC Atrium CMDB. If you integrate without installing the extensions, the publishing server may not work as expected.

BMC ProactiveNet CMDB Extensions are bundled with the BMC ProactiveNet Performance Management DVD and include:

■ AR Notify Plug-in

■ BMC Impact Model Designer (install this if you want to publish service models to BMC ProactiveNet cells)

For information about BMC ProactiveNet CMDB Extensions, see the BMC ProactiveNet Performance Management Getting Started Guide.


Installing and Configuring BMC ProactiveNet Performance Management

■ Ensure that the host name does not contain a hyphen (-). Installation may fail if the host name contains a hyphen (-).

Installing and Configuring BMC ProactiveNet Performance Management

See the BMC ProactiveNet Performance Management Getting Started Guide for details about the steps listed below.

1 Install the BMC ProactiveNet server. Installing the server also installs the BMC ProactiveNet Administration Console and the local BMC ProactiveNet agent.

2 Obtain and apply the license for the BMC ProactiveNet server.

3 Enable the Integration Service. The Integration service is installed by default when you install the BMC ProactiveNet agent. The Integration Service collects data from all the external agents that you configure. You can choose to enable the Integration Service during installation or enable it any time after the installation. For information about configuring the Integration Service, see the BMC ProactiveNet Getting Started Guide.

4 Integrate with BMC Atrium CMDB if you want to publish service models created in BMC Impact Model Designer and the Administration Console. You can choose to integrate during installation or enable it any time after the installation. For information about service models, see the BMC ProactiveNet Service Modeling and Publishing Guide.

5 Launch the Administration Console and add monitors or devices for BMC ProactiveNet Performance Management to monitor. For more information about the Administration Console, see the BMC ProactiveNet Administrator Guide.

6 Verify self-monitoring using the FlashCheck feature. FlashCheck enables you to examine data values from a selected monitor. You can use FlashCheck to determine whether a previously detected condition still exists. For information about FlashCheck, see the BMC ProactiveNet User Guide.

7 Install the BMC ProactiveNet agent on other target systems or on remote systems that exist on a network.



Deployment ArchitectureThe following figure depicts an implementation of stand-alone BMC ProactiveNet Performance Management (without using other BMC products). This depiction uses the standard recommended hardware configuration for BMC ProactiveNet server and BMC ProactiveNet agent.

Figure 2 BMC ProactiveNet Performance Management deployment


C h a p t e r 5
5 Probable Cause Analysis
By gathering data from different sources and applying filters to rule out unrelated events, the most-likely causes for an event, such as an attribute that is outside the desired range, can be determined. This process of gathering and filtering data to determine the cause for an event is called probable cause analysis.

Probable cause analysis lowers the operational costs by detecting the cause of events and helps reduce the manual efforts required to analyze the probable cause of the changes or problem. It also improves the operational efficiency by automating the deployment of BMC ProactiveNet agents. Some events generated on BMC ProactiveNet can trigger the execution of pre-defined snapshot jobs on BMC BladeLogic.

BMC Products RequiredYou need the following BMC products to perform probable cause analysis:


■ BMC BladeLogic Service Automation


Deployment ConsiderationsThis section lists the hardware, software, and licensing considerations to perform probable cause analysis.




Ensure that the following deployment is in place to achieve probable cause analysis:

■ Minimum of two servers

■ The BMC ProactiveNet server and agent are installed on a single system.

■ BMC BladeLogic and its components are installed on another system.




Table 9, “Supported databases,” on page 34 lists the databases that the products in the “BMC Products Required” section use.


BMC ProactiveNet Performance Management and the BMC BladeLogic RSCD agent require licenses. For information about obtaining and applying licenses, see the “Documents You May Need” section.


Product Database


BMC BladeLogic Oracle and Microsoft SQL Server


Configuring BMC ProactiveNet and BMC BladeLogic for Probable Cause Analysis

Configuring BMC ProactiveNet and BMC BladeLogic for Probable Cause Analysis

The following procedure is a high-level overview of the steps you must perform in order to configure BMC ProactiveNet Performance Management and BMC BladeLogic to achieve probable cause analysis. You must be familiar with BMC BladeLogic components in order to perform the procedure below.

For detailed information about integrating BMC ProactiveNet Performance Management with BMC BladeLogic, see the BMC ProactiveNet User Guide. For detailed information about BMC BladeLogic, see the “Documents You May Need”section.

1 Install the BMC ProactiveNet server and agent on a system (Server-1). For more information about installing the BMC ProactiveNet server and agent, see See “Achieving End-to-End Monitoring” on page 25.

2 Install the BMC BladeLogic RSCD agent on Server-1.

3 Ensure the supported database for BMC BladeLogic (see Table 9, “Supported databases,” on page 34) is available and create the schema that the BMC BladeLogic Application Server can use.

4 Install and configure the following BMC BladeLogic components on another system (Server-2):

■ BMC BladeLogic Service Automation Console

■ BMC BladeLogic RSCD agent (again on Server-2)

■ BMC BladeLogic Service Application Server

5 Run the BMC ProactiveNet content installer on the system in which BMC BladeLogic Service Application Server is installed (Server-2). This installer installs the templates, component discovery jobs, snapshots jobs in its PPM folder. The content installer imports three component templates into BMC BladeLogic Application Server. These templates capture configuration changes for Solaris, Apache Web Server on Solaris, and WebLogic Application Server on Solaris.

6 Log in as administrator into the BMC BladeLogic Service Automation Console.

7 Edit all three component discovery jobs in the PPM folder to assign proper targets and to set the schedule.

8 Run all three component discovery jobs.

9 Edit all three snapshot jobs to assign proper targets and to set the schedule.



10 Run all three snapshot jobs.

11 Create an administrator account on the system in which the BMC BladeLogic Application Server is installed.

12 Enable BMC BladeLogic Web services on the BMC BladeLogic Application Server. The BMC BladeLogic Web services is used to communicate between the BMC BladeLogic Application Server and the BMC ProactiveNet server.

13 Set up the credentials on the BMC ProactiveNet server for accessing BMC BladeLogic from BMC ProactiveNet. For more information about this, see the “Configuring BMC BladeLogic for probable cause analysis” section.

14 Test the credentials you created on the BMC ProactiveNet server to ensure a successful connection between the BMC ProactiveNet server and BMC BladeLogic.

Deployment ArchitectureThe figure below depicts the physical layout for deploying probable cause analysis.

Figure 3 Deploying Probable Cause Analysis


C h a p t e r 6
6 BMC Triage and Remediation Solution and IBRSD Integration
The BMC Triage and Remediation Solution comprises BMC Atrium Orchestrator and BMC ITSM. The BMC Triage and Remediation solution helps improve service delivery by improving the operational efficiency of IT operations. This solution prevents time spent by the IT operations staff doing mundane, labor-intensive, repetitive tasks. This solution is an automated coordination of other configuration management processes such as incident management and problem management.

IBRSD integration involves integrating real-time IT and service information with the help desk to automatically create intelligent incidents that enable help desk users to prioritize incidents based on the impact to the business. It defines and manages critical relationships between IT assets and business services, and quickly determines the impact of an IT problem on various business services and user groups.

BMC Products RequiredYou need the following BMC products to carry out the BMC Triage and Remediation Solution and IBRSD integration:



■ BMC Atrium CMDB


■ BMC Remedy IT Service Management

■ BMC Atrium Orchestrator




Deployment ConsiderationsThis section lists the hardware, software, and licensing considerations to carry out the BMC Triage and Remediation Solution and IBRSD integration.


Ensure that the following deployment is in place to achieve BMC Triage and Remediation Solution and IBRSD integration.

■ A minimum of seven servers

■ BMC Remedy Action Request System, BMC Atrium CMDB, and BMC IT Service Management must all be installed on a single system

■ The BMC Performance Manager Portal Datastore module can be installed on a separate server and accessed remotely for better performance and memory usage

■ BMC Software recommends installing Atrium Web Services components on a separate server

■ BMC Atrium Orchestrator must be installed on a minimum of two servers - BMC Atrium Orchestrator must be installed on one server and the development studio on another server


The operating systems that support the BMC products listed in “BMC Products Required” are listed in the Release Notes of the respective product. For the location of the Release Notes, see the “Documents You May Need” section.


Table 10, “Supported databases,” on page 39 lists the databases that the products in the “BMC Products Required” section use.




BMC ProactiveNet Performance Management, BMC Remedy Action Request System, and BMC Atrium Orchestrator require licenses. For information about obtaining and applying licenses, see the “Documents You May Need” section.

Installation and ConfigurationThis section lists the high-level steps to install and configure BMC Triage and Remediation Solution, BMC Atrium Orchestrator, and BMC Remedy Action Request System. The installation steps are ordered in a sequence to support the input required for subsequent installs. For detailed installation and configuration steps, see the “Documents You May Need”section.

1 Ensure that the database required for BMC Remedy Action Request System is installed and running on a system (Server-1).

2 Install BMC Remedy ITSM on Server-2.

3 Install the following components of BMC Action Request System using the remote database running on Server-1.


■ Approval Server


■ BMC Remedy Action Request System User Tool


Product Database


BMC Remedy Action Request System ■ Oracle, Microsoft SQL, DB2 (on Windows and UNIX® operating systems)

■ Informix and Sybase SQL Anywhere (Adaptive Server Anywhere) version 11.01 (on UNIX operating systems)


Installation and Configuration

4 License the following components on the system in which BMC Remedy Action Request System Server is installed (Server-1):


■ BMC:Atrium CMDB Application

■ BMC:Asset Management Application

■ BMC:Asset Management User Fixed

■ BMC:Change Management Application

■ BMC:Change Management User Fixed

■ BMC:Incident Management Application

■ BMC:Incident Management User Fixed

■ BMC:Problem Management Application

■ BMC:Problem Management User Fixed

■ BMC:Financial Management Application

■ BMC:Financial Management User Fixed

5 Install BMC Atrium CMDB and the Product Catalog.

6 Install BMC ProactiveNet CMDB Extensions.

7 Install the following BMC Remedy ITSM components:

■ BMC Remedy Asset Management

■ BMC Remedy Change Management

■ BMC Remedy Service Desk

8 Create an administrator ID for BMC Remedy ITSM.

9 Log on to BMC Remedy ITSM using the ID created in step 8.

10 Configure the groups for company, people, login access details, and permissions.



11 Assign the required permissions for the user ID created in step 8. Permissions include administrator, Incident config, Incident master, Incident viewer, Incident submitter, Contact organization admin, Contact people admin, Contact support admin, Config group mapping admin, and Config categorization admin.

12 Install the IBRSD AR System module. For more information, see Integration for BMC Remedy Service Desk User Guide .

13 Install the following components of Atrium Web Services on Server-3:

■ Web Services Infrastructure

■ Atrium Core Web Services

■ Web Services Registry

14 Install the Atrium Mid Tier on Server-4.

15 Install the BMC ProactiveNet server and agent on Server-5. Select to integrate with BMC Atrium CMDB during the installation.

16 Install the components of BMC Atrium Orchestrator on Server-6 in the following order:

A Run the BMC Atrium Orchestrator installer and install the Access Manager and Repository.

B Run the BMC Atrium Orchestrator installer and install Configuration Distribution Peer (CDP) along with the following subcomponents:

■ Operator Control Panel

■ Graphic Manager

C Configure a grid. See “Configuring the BMC Atrium Orchestrator grid for the BMC Triage and Remediation solution.”

NOTE When you try to install the Access Manager and Repository first, the installer allocates ports 8080 and 8005 for the Access Manager and Repository respectively. When you then try to install CDP, port conflicts may occur and the installer displays a warning message that port 8080 is already in use. Specify a different port for CDP (for example, 8086) and proceed with the installation.



D Install the components of BMC Atrium Orchestrator (adapters, modules, Run Books, BMC Remedy Action Request Artifacts, and BMC Remedy ITSM templates) using the BMC Atrium Orchestrator content installer. Select the BMC Triage and Remediation Solution installation path that pre-selects adapters and modules required for the BMC Triage and Remediation Solution.

17 Configure the BMC ProactiveNet server cell. For more information about configuring the BMC ProactiveNet server cell, see the BMC ProactiveNet Administrator Guide.

18 Configure BMC Atrium Orchestrator. See “Configuring BMC Atrium Orchestrator for the BMC Triage and Remediation solution.”

Deployment ArchitectureThe figure below depicts the physical layout for deploying BMC Triage and Remediation Solution and IBRSD integration.

Figure 4 BMC Triage and Remediation Solution and IBRSD integration


C h a p t e r 7
7 Integrating BMC Atrium Discovery Dependency Mapping with BMC ProactiveNet Performance Management
BMC ProactiveNet Performance Management uses the configuration data discovered by BMC Atrium Discovery Dependency Mapping (BMC Atrium Discovery) and synchronizes with BMC Atrium CMDB to populate the BMC ProactiveNet server database with devices and applications that support critical business services and enable device monitoring and the probable cause analysis of business service impact.

BMC Products RequiredYou need the following BMC products to integrate BMC Atrium Discovery with BMC ProactiveNet Performance Management:



■ BMC Atrium CMDB


■ BMC Atrium Discovery

■ BMC Atrium Discovery Common Data Model (CDM) Extensions

■ BMC ProactiveNet CMDB Extensions

Chapter 7 Integrating BMC Atrium Discovery Dependency Mapping with BMC ProactiveNet PerformanceManagement 43


For information about these products, see the “Documents You May Need”section.

Deployment ConsiderationsThis section lists the hardware, software, and licensing considerations to carry out the BMC Atrium Discovery and BMC ProactiveNet Performance Management integration.


Ensure that the following deployment is in place to achieve BMC Atrium Discovery and BMC ProactiveNet Performance Management integration:

■ A minimum of seven servers.

■ BMC Remedy Action Request System and BMC Atrium CMDB must be installed on a single server.

■ BMC Performance Manager Portal Datastore must be installed on a separate server and accessed remotely for better performance and memory usage.

■ Install BMC Atrium Discovery CDM Extensions and BMC ProactiveNet CMDB Extensions on the system in which BMC Atrium CMDB is installed. You need these extensions to integrate BMC Atrium Discovery with BMC ProactiveNet Performance Management.

■ BMC Software recommends installing Atrium Web Services components on a separate server.

■ BMC Atrium Discovery is installed on a separate server. BMC Atrium Discovery is delivered as a virtual appliance and must be deployed in a VMware ESX or ESXi environment.

■ BMC ProactiveNet Performance Management is installed on a separate server.






Table 2 lists the databases that the products in the “BMC Products Required” section use.


BMC ProactiveNet Performance Management and BMC Remedy Action Request System require licenses. For information on obtaining and applying licenses, see the “Documents You May Need” section.

Installation and ConfigurationThis section lists the high-level steps to install and configure BMC Atrium Discovery with BMC ProactiveNet Performance Management. For detailed installation and configuration steps, see the “Documents You May Need”section.

1 Ensure that the database required for BMC Remedy Action Request System is installed and running on a system (Server-1).

2 On another system (Server-2), install the following components of BMC Remedy Action Request System using the remote database running on Server-1.



Product Database


BMC Atrium Discovery BMC Atrium Discovery installs its own database while deploying BMC Atrium Discovery Virtual Appliance.

BMC Remedy Action Request System ■ Oracle, Microsoft SQL, DB2 (on Windows and UNIX operating systems)

■ Informix and Sybase SQL Anywhere (Adaptive Server Anywhere) version 11.01 (on UNIX operating systems)



■ Approval Server


■ BMC Remedy Action Request System User Tool

3 Obtain and apply licenses to BMC Action Request System Server and BMC Atrium CMDB. You may need additional licenses if you are going to use BMC IT Service Management (BMC ITSM).

4 Install the following components of BMC Atrium Core on the same system in which BMC Action Request System is installed (Server-2):

■ BMC Atrium Core Console

■ Product Catalog

5 On Server-2 (the system in which BMC Atrium Core components are installed), install BMC ProactiveNet CMDB Extensions and BMC Atrium Discovery CDM Extensions.

6 Create the BMC.ADDM dataset. For information about creating datasets, see the BMC Atrium Core Concepts and Planning Guide.

7 Create a job to merge BMC.ADDM dataset with BMC.ASSET.

8 Install the following BMC Atrium Web Services components on Server-3:

■ Web Services Infrastructure

■ Atrium Core Web Services

■ Web Services Registry

9 Install BMC Remedy Mid Tier on Server-4.

10 Install the following components of BMC Atrium Discovery on Server-5:

■ VMware Converter Client

■ BMC Atrium Discovery Virtual Appliance

NOTE You do not need to install the BMC Atrium Discovery CDM Extensions if you are using BMC Atrium Core version 7.6.03. BMC Atrium Discovery CDM Extensions are installed by default in version 7.6.03 of BMC Atrium Core.



■ VM Tools

■ Set up NTP

■ Localize the BMC Atrium Discovery Virtual Appliance

11 Install the Windows Slave for BMC Atrium Discovery on Server-6.

12 Synchronize BMC Atrium Discovery with BMC Atrium CMDB. For more information, see “Configuring BMC Atrium CMDB and BMC Atrium Discovery synchronization”.

13 Install the BMC ProactiveNet server and agent on Server-7. Select to integrate with BMC Atrium CMDB during the installation.

14 Launch the BMC ProactiveNet User Console and verify the BMC Atrium CMDB integration. For information about verify the BMC Atrium CMDB integration, see the BMC ProactiveNet User Guide.

Deployment ArchitectureThe figure below depicts the integration of BMC ProactiveNet Performance Management and BMC Atrium Discovery.



Figure 5 BMC ProactiveNet Performance Management and BMC Atrium Discovery integration



C h a p t e r 88 Configuring 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.

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 Products RequiredYou need the following BMC products to integrate BMC ProactiveNet with BMC AppSight:

■ BMC ProactiveNet■ BMC AppSight

For information about these products, see “Documents You May Need” on page 9.



Deployment ConsiderationsThis section lists the hardware, software, and licensing considerations required to integrate BMC ProactiveNet with BMC AppSight.


Ensure that the following deployment is in place to integrate BMC ProactiveNet with BMC AppSight:

■ BMC AppSight Server for Java EE or Windows

■ (for Java EE) One of the following databases:— Oracle, on any computer— MaxDB (provided with the BMC AppSight Server), on the same computer as the

the BMC AppSight Server for Java EE

■ BMC AppSight Repository server, which can run on the same computer as the BMC AppSight Server

■ BMC AppSight Black Box— (for Java EE) On a server in which the application server is running— (for Windows) On a server with Internet Information Services (IIS) running ASP

or ASP.NET

■ BMC ProactiveNet Server


The operating systems that support the BMC products listed in “BMC Products Required” are listed in the Release Notes of the respective product. See “Documents You May Need” on page 9 for the location of the Release Notes.


Table 12 lists the databases used by the products.




BMC ProactiveNet requires a license. For information on obtaining and applying licenses, see “Documents You May Need” on page 9.

BMC AppSight does not require a license for use with BMC ProactiveNet. If you already own a license (or purchase a new one), you can launch and use the BMC AppSight Console from BMC ProactiveNet Application Diagnostics.

Installation and ConfigurationThis section lists the high-level steps to install and configure BMC ProactiveNet Application Diagnostics. For detailed BMC AppSight and BMC ProactiveNet installation and configuration steps, see “Documents You May Need” on page 9.

1 Install a BMC AppSight Server for Java EE or Windows on Server-1.

2 Install a BMC AppSight Repository server, which can also be on Server-1.

3 Install the BMC AppSight Black Box

■ (Java EE) on a system running the application server (Server-2)■ (Windows) on a server with IIS running ASP or ASP.NET (Server-2)

Establish the BMC AppSight Black Box connection with the applicable (Java EE or Windows) BMC AppSight Server.

4 (Java EE) Configure the capturing mode on the BMC AppSight Server. See “Configuring and capturing in BMC AppSight for Java EE” on page 75.


Product Supported database

BMC ProactiveNet Sybase SQL Anywhere (Adaptive Server Anywhere) version 11.01

BMC AppSight for Java EE BMC AppSight Server uses one of the following databases:

■ Oracle■ MaxDB, provided with the BMC AppSight Server

BMC AppSight Repository server uses HSQLDB, which is installed automatically and requires no configuration.

BMC AppSight for Windows Not applicable



5 Start a BMC AppSight recording. See “Configuring and capturing in BMC AppSight for Java EE” on page 75 or “Capturing in BMC AppSight for Windows” on page 77.

6 Install the BMC ProactiveNet Server and Agent on Server-3.

7 Configure the BMC AppSight Repository server. See “Configuring the BMC AppSight Repository server” on page 77.

8 Configure the connection between BMC ProactiveNet and the BMC AppSight Repository. See “Configuring the connection between BMC ProactiveNet and the BMC AppSight Repository server” on page 79

9 Create adapters for supported products.

For BMC TM ART, see “Configuring BMC TM ART for BMC ProactiveNet Application Diagnostics” on page 80.

10 Create event rules according to instructions in the BMC ProactiveNet User Guide (see “Documents You May Need” on page 9)

Ensure the following options are set:

■ On the “Add Event Rule (Page 1/3)” screen, select Basic Event Rule, if not already selected.

■ On the “Add Event Rule (Page 2/3): Select Event/Monitor/Severity Information” screen, on the Event tab of the Severity/State Filter section, select Open . Each time an Event is opened and clear all other selections.

■ In the Run Agent Diagnostics list, select Application Diagnostics and click Add.

11 Set thresholds.



Deployment ArchitectureThe figure below shows the integration components of BMC ProactiveNet and BMC AppSight.

Figure 6 BMC ProactiveNet and BMC AppSight integration



C h a p t e r 9
9 Known Issues
This chapter lists the known issues and workarounds that facilitate a smooth deployment of BMC ProactiveNet Performance Management and its integrated products. For some issues, this chapter also details the requirement of patches and configuration steps that enable BMC ProactiveNet Performance Management to function after a successful install.

Installation on unsupported platforms

The BMC ProactiveNet Performance Management installer allows the BMC ProactiveNet agent to be installed on an unsupported platforms. See the BMC ProactvieNet Release Notes for a list of supported platforms for the BMC ProactiveNet agent.

Installing multiple BMC ProactiveNet agents on a system

If you want to install multiple BMC ProactiveNet agents on a UNIX or Linux® system, you must install the agents as a root user. If you do not do so, BMC ProactiveNet Performance Management installs multiple cells and names all of them as the host. This can cause problems when the cells attempt to interact with the cell installed on the BMC ProactiveNet server.


Conflicting ports between BMC Remedy Action Request System Server and BMC Atrium Web Services

Conflicting ports between BMC Remedy Action Request System Server and BMC Atrium Web Services

The TCP ports of both the BMC Remedy Action Request System Java plug-in and BMC Atrium Web Services use the default port of 9999. When you are installing BMC Atrium Web Services, the installer displays an error message because of the conflicting port usage.

Workaround

Follow one of these workarounds to avoid the error message when installing BMC Atrium Web Services:

■ Install BMC Atrium Web Services on a system different from the system on which BMC Atrium Core and the BMC Remedy Action Request System are installed.

■ Provide a non-default port number (for example, 9995) for the BMC Remedy Action Request System Java Plug-in while installing the BMC Remedy Action Request System Server.

■ Change the default BMC Remedy Action Request System Java Plug-in TCP port of 9999 to a port available for use (for example, 9993) in the following BMC Remedy Action Request System files:

■ On UNIX systems, <install_directory>/usr/ar/<system_name>/conf/ar.conf _ <install_directory>/usr/ar/<system_name>/pluginsvr/pluginsvr_config.xml

■ On Windows systems, <install_directory>\arsystem\conf\ar.cfg <install_directory>\arsystem\pluginsvr\pluginsvr_config.xml

■ Restart the BMC Remedy Action Request System Server.

See Appendix A, “Port Usage” for the list of default ports and their use.

Creating an incident in BMC Remedy Action Request System fails

When you integrate a BMC Impact Manager cell with version 7.6 of BMC Remedy IT Service Management (BMC Remedy ITSM) or BMC Atrium Core, or version 7.5 patch 003 of the BMC Remedy Action Request System, and generate an event by enabling the IBRSD policy, incident creation fails.


Incident creation fails for BMC Remedy ITSM 7.6.00 Patch 1

Workaround

Perform the following steps in the BMC Remedy Action Request System, to create an incident rule:

1 Go to the Home page =>Application Administration Console => Custom Configuration => Incident Management => Advanced Options => Rules.

2 In the Configure Incident Rule page, create an incident rule with the following settings:

■ Require Service CI Related On Submit = No

■ Require CI Related On Resolved = No


When you integrate version 7.6.00 patch 1 of BMC Remedy ITSM with version 8.5 of BMC ProactiveNet Performance Management, incident creation fails.

Workaround

Perform the following steps in the BMC Remedy Action Request System:

1 Open the People form.

2 Search for Impact Server User and select the record that matches the search.

3 Click the Login/Access Details tab.

4 Enter the username and password in the respective fields and click Save.

5 Restart the BMC Remedy Action Request plug-in server.

Perform the following steps in BMC ProactiveNet Performance Management:

1 Edit the DefaultMapping.Map file at <installation_directory>\pw\integrations\ibrsd\conf

2 Remove the comments for the EventRequeser="Jim" line and from the BEMUseCaseNew and BEMUseCaseMod functions.

3 Restart IBRSD.




A p p e n d i x A
A Port Usage
This appendix lists the default port numbers that are assigned during the installation of BMC products listed in this guide. See the tables in this appendix to verify possible conflicts of ports if you install more than one BMC product on a single system.

To find out the port numbers that are already in use, use the netstat -na command (for UNIX systems) or the netstat -a command (for Microsoft Windows systems) at the command prompt. See the BMC ProactiveNet Getting Started Guide for the procedure to change port configuration in case of conflict.

)

Table 13 Default ports for BMC ProactiveNet Performance Management (part 1 of 2)

Port Port number

HTTP Web server port 80

HTTPS secure Web server port 443

pronet.rmi port 1099

Cell port 1828

Gateway BMC ProactiveNet server port 1851

Sybase ASA JDBC port (database port) 2638

IAS Admin port 3084

Gateway IBRSD port 3115

BMC ProactiveNet server 3182

Apache Tomcat shutdown port 8005

Apache Tomcat Jserver port 8007

Tunnel proxy port 8008

Apache Tomcat port 8009

JMS Server port 8093

Pronet.jserver.event port 9149

Agent controller listener port 12123

Remote agent port 12124

Agent controller call-back port 12126

Check point monitor port for receiving log messages 12130


Communication between agent controller and Apache server for agent

12134

Pronet.clserver port 12140

Log server port 12141

Rate port 15000

Message server port 45000

Table 14 Default ports for BMC Impact Management

Port Port number

BMC Impact Administration Server 3084

BMC Impact Administration cell 1827

BMC Impact Publishing Server to BMC Impact Manager 1839

BMC Impact Publishing Server to BMC Impact Portal 9378,9379,9385, 9386

Impact Service Model Editor to Impact Portal 443, 9378, 9379, 9385, 9386

BMC Impact Manager 1828

BMC Impact Portal to Web server 443

BMC Impact Portal to BMC Impact Manager 3783

BMC Impact Portal Datastore 1521

BMC Impact Integration Web Services 1828

Table 15 Default ports for BMC Portal

Port Port number

BMC Portal HTTP Web Server port 80

BMC Portal secure HTTPS Web Server port 443

RSM to BMC Portal HTTP Web Server 80

RSM to BMC Portal secure HTTPS Web Server 443

Oracle database port 1521

Table 16 Default ports for BMC PATROL

Port Port number

BMC PATROL agent 3181

BMC RTserver 2059

BMC Integration Service 3182

Table 13 Default ports for BMC ProactiveNet Performance Management (part 2 of 2)

Port Port number


The BMC Remedy Action Request System uses the portmapper by default. If you do not select the portmapper while installing the BMC Remedy Action Request System, the ports are user-defined.

Table 17 Default ports for BMC TM ART

Port Port number

HTTP port 19120

MSSQL database port 1433


Border gateway protocol 179

Table 18 Default ports for BMC BladeLogic Server Automation Suite

Port Port number

Application Server - SSL communication port 9831

Authentication Service 9840

Web Services port 9843

JMX Management port 9838

RMI Registry port 9836



Table 19 Default ports for BMC Remedy Action Request System

Port Port number

Java plug-in port 9999

Mid Tier Tomcat Shutdown port 8005

SSL port 8443

AJP13 Connector 8009

Proxy port 8082

HTTP port 8282

ServletExec 8888



Sybase database port 5000

Table 20 Default ports for BMC Atrium CMDB (part 1 of 2)

Port Port number

BMC Atrium plug-in port 9555

BMC Atrium Web Services port 9090

BMC Atrium CMDB Web Services port 9080


BMC Atrium Web Services Infrastructure database port 9999

BMC Atrium Web Services HTTP port 8120

BMC Atrium Web Services naming port 8110

BMC Atrium Web Services Registry JSP Apache Tomcat HTTP port

8090

BMC Access Manager communications port 61616

JMX RMI port (this port is not configurable. It must be available during installation)

1089

Table 21 Default ports for BMC Atrium Discovery and Dependency Mapping

Port Port number

Active Directory slave 4321

Workgroup slave 4322

Credential slave 4323

Table 22 Default ports for BMC AppSight

Port Port number

BMC AppSight port 7092

HTTP Java EE Console 8080

HTTPS Java EE Console 8443

Table 20 Default ports for BMC Atrium CMDB (part 2 of 2)

Port Port number



A p p e n d i x BB Additional Configurations

This appendix lists the configuration steps that are applicable to deployment of the BMC ProactiveNet Performance Management integrations described in this guide.

Unless stated otherwise, the steps and file names in the appendix are based on the Microsoft Windows 2003 operating system.

Configuring terminal services to save log filesTo configure terminal services and save log files:

1 From the Start menu, click Run.

2 In the Run dialog box, type tscc.msc and click OK.

3 In the Server Settings screen, set Delete temporary folders on exit to No.

4 Set Use temporary folders per session to No.

5 Restart your system.

If these settings do not take effect, perform the following steps:

1 From the Start menu, click Run.

2 Type regedit, and then click OK.

3 Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Terminal Server.

4 Update PerSessionTempDir to 0 and DeleteTempDirsOnExit to 0.

5 Restart your system.

Licensing the BMC ProactiveNet server


Licensing the BMC ProactiveNet serverPerform the following steps to license the BMC ProactiveNet server:

1 Copy the license file to <install_directory>\pw\licenses.

2 Run the - pw license update command.

Licensing BMC Remedy AR Server applicationsUsing BMC AR System or BMC Remedy Mid Tier, perform these steps to add the appropriate licenses. Adding these licenses is a prerequisite to proceeding with the installation of BMC Atrium CMDB and BMC Remedy Service Desk.

1 In the AR System, click Administration Console.

2 Select System -> General -> Add or Remove Licenses.

3 Click Add New and enter the following information:

■ License type - Select the type of license to activate.■ Number of licenses - Enter the required number of licenses.■ Key - Enter the required license key.■ Expiration Date - Enter the date for trial licenses.

Licensing the BMC BladeLogic RSCD agentPerform the following steps to license the BMC BladeLogic RSCD agent:

1 Invoke the BMC BladeLogic Network Shell (NSH).

2 Run the following command:

autolic <user_name> <password> <target_system_name>

3 Verify that the RSCD agent is licensed by using the following command:

agentinfo <target_system_name>

Configuring the BMC Integration service


Configuring the BMC Integration serviceIf you did not choose to enable the Integration service while installing BMC ProactiveNet Performance Management, you must configure it manually after the installation. For information about configuring the Integration service, see the BMC ProactiveNet Getting Started Guide.

Configuring Notification Engine for version 7.5.00 patch 5 of BMC Atrium CMDB

Perform the following steps to enable the Notification Engine for version 7.5.00 patch 5 of BMC Atrium CMDB. The steps below are specific to an environment in which BMC Atrium Core is installed on one system and BMC Atrium Web Services is installed on another system. If both the components are installed on a single system, execute all these steps in one system.

Perform the following steps on the system in which BMC Atrium Core is installed. These steps are required to enable Notification Engine.

1 Copy the noePackage.tar.gz file from BMC ProactiveNet Performance Management installation media. The NOE package must be of version 7.6 patch 002.

2 Extract the noePackage.tar.gz file.

3 Run the BMC Atrium Core Maintenance Tool:

A On Microsoft Windows systems, navigate to <installation_directory>\BMC Software\AtriumCore\atriumcore and run AtriumCoreMaintenanceTool.cmd.

On UNIX systems, navigate to <installation_directory>/AtriumCore/atriumcore and run AtriumCoreMaintenanceTool.sh.

B Click the Configuration tab and select the Extensions option.

C Browse to locate the ExtensionLoader.xml file extracted in step 2.

D Click Next.

E Enter the following AR System information:



4 Click Run.

The BMC Atrium Core Maintenance Tool enables the notification engine and restarts the AR System server.

Perform the following steps on the system in which BMC Atrium Web Services is installed. These steps are required to enable version 7.6 of Notification Engine Web Services.

1 Verify that BMC Atrium Web Services Infrastructure and TIBCO ActiveMatrix Registry are running.

2 Copy the noews7.6_img.zip file from the BMC ProactiveNet Performance Management media.

3 Extract the contents of the noews7.6_img.zip file to the BMCAtriumCoreHome/wsc/tibco/amxadministrator/2.1/samples/bmc directory.

4 Verify that the bmc directory contains the following new files:

■ bmc_manage_noews_build.xml■ bmc_manage_noews_data.xml■ bmc_manage_noews_build.properties■ webservices_list_noe.xml

5 Edit the following properties in the bmc_manage_noews_build.properties file:

User Name User name of the AR System administrator

Password The AR System administrator’s password

Port Number Port number that the AR System server listens at if no portmapper is used

AR Server Host Name

Name of the AR System server.

Table 23 Properties to be edited in the bmc_manage_noews_build.properties file (part 1 of 2)

Property Value you must enter

ATRIUMCORE_HOME <installation directory of BMC Atrium Core>

For example, C:/Program Files/BMC Software/AtriumCore

Even on Microsoft Windows systems, enter the path of the directory using a forward slash (/).

TIBCO_AMX_HTTP_SERVER_NOE_PORT

<port number used by the HTTP_Server_NOE shared resource>



6 Navigate to BMCAtriumCoreHome/wsc/tibco/amxadministrator/2.1/bin and run the following command:

admincmdline ../samples/bmc/bmc_manage_noews_build.xml e2e - DREGISTRY_ADMIN_USERNAME <user_name> -DREGISTRY_ADMIN_PASSWORD <password>

In the command above, <user_name> and <password> are the user name and password of the TIBCO ActiveMatrix Runtime UDDI administrator.

Output from the command above is logged in the bmc_manage_noews_build.log file at BMCAtriumCoreHome/wsc/tibco/ amxadministrator/2.1/bin.

HOST_NAME <host name of the system in which BMC Atrium Web Services is installed>

AMXADMIN_USERNAME <user name of the TIBCO ActiveMatrix administrator>

AMXADMIN_PASSWORD <password of the TIBCO ActiveMatrix administrator>

Copy the password (within the double quotes) from C:\Program Files\BMC Software\AtriumCore\wsc\tibco\amxadministrator\2.1\samples\bmc\bmc_manage_amxenv_build.xml

<target name="svar-ent-add" description="Add Svar at Enterprise level"><AMXAdminTaskadminURL="http://localhost:8120/amxadministrator"username="root"password="#!Ft1lMkmlZ7HtlnBjEqdDe9vnJr/YJhrc"

The password is encrypted using the TIBCO password obfuscator utility in BMCAtriumCoreHome/wsc/tibco/amxadministrator/2.1/bin

AMXADMIN_PORT <port number used by TIBCO ActiveMatrix administrator>

For example, 8120

TIBCO_AMX_REGISTRY_SERVER_PORT

<port number used by the TIBCO ActiveMatrix Runtime UDDI Server>

For example, 7777

WS_VERSION_NUMBER <version number of BMC Atrium Web Services>

For example, 7.6.00

Table 23 Properties to be edited in the bmc_manage_noews_build.properties file (part 2 of 2)

Property Value you must enter

Configuring BMC ProactiveNet CMDB Extensions on a BMC Remedy ITSM server group environment


7 In the Administration console of TIBCO ActiveMatrix, verify that the atrium_notifications_pull and atrium_notifications_subsciptions Web services are running.

8 Verify that there is only one QRD Enabled=T entry in the ar.cfg file on the system in which BMC Atrium Core is installed. If two entries exist in the file, comment one of the entries and restart the AR Server.

Configuring BMC ProactiveNet CMDB Extensions on a BMC Remedy ITSM server group environment

This section lists the configuration of BMC ProactiveNet CMDB Extensions in a BMC Remedy ITSM server group environment.

1 Ensure that the AR System or BMC Remedy Mid Tier servers are marked as unsupported on any server group. That is, the servers must not be a part of any server group. BMC ProactiveNet CMDB Extensions does not support server groups.

2 Install BMC ProactiveNet CMDB Extensions on all servers that are part of the BMC Remedy ITSM server group. For information about installing BMC ProactiveNet CMDB Extensions, see the BMC ProactiveNet Getting Started Guide.

3 On the BMC ProactiveNet server, edit the <cell home>/etc/pserver.conf file and change the values of the following parameters:

CMDBServer=<alias_name/loadbalancer_name>

ARSGroupMemebers=<server1>:<port>,<server2>:<port>

4 Restart the BMC ProactiveNet server.

5 Using the AR System or BMC Remedy Mid Tier, ensure that the servers are marked as part of server group.

Configuring BMC BladeLogic for probable cause analysis


Configuring BMC BladeLogic for probable cause analysis

This section describes the steps involved to configure BMC BladeLogic to integrate with BMC ProactiveNet Performance Management to attain probable cause analysis.

1 Create a new user for the BMC BladeLogic Application Server.

2 Assign the user you created in step 1 the role of BLAdmins. Do not assign any other roles to this user.

3 Log in to the BMC BladeLogic Application Server, using the BLAdmins account.

4 Start the BMC BladeLogic Application Server administration utility:

■ For Microsoft Windows systems, click Start => Programs => BMC Software => BladeLogic => Utilities => Application Server Administration.

■ For UNIX systems, navigate to /opt/bmc/BladeLogic/8.0/NSH/br and from the command line enter blasadmin.

5 Using the BMC BladeLogic Application Server administration utility, run the following command for the BMC BladeLogic Web services:

set AppServer EnableTomcatService true

set AppServer ValidateIpAddress false

6 (Optional) Configure the registration of BMC BladeLogic Web services in the BMC UDDI server by executing the following commands:

■ set WebServices RegistryServer registryServerHostName■ set WebServices RegistryServerPort registryServerPort■ set WebServices RegistryServerUserName registryServerUserName■ set WebServices RegistryServerPassword registryServerPassword

The port number of the default registry server is 8080.

7 Restart the BMC BladeLogic Application Server.

The BMC BladeLogic Application Server log indicates if the BMC BladeLogic Web services registration was successful for LoginService, AssumeRoleService, and CLITunnelService.

Configuring BMC ProactiveNet Performance Management for the BMC Triage and Remediation solution


8 Set up credentials using the BMC ProactiveNet server for the UDDI registry to access BMC BladeLogic from BMC ProactiveNet Performance Management by performing the following steps:

A Log in to the BMC ProactiveNet server as an administrator.

B Access the command line and enter:

pw blade setup -use_uddi -uddiuser uddiuser -uddipass uddipassword -host hostname -port portnumber -user BLAdmin -pass Bladelogic

If UDDI is not set for the BMC Bladelogic server, then enter the following command. This command uses BMC Bladelogic Web services:

pw blade setup connection -host <host_name> [-port <por_number>] -user <user_name> -pass <password>

Configuring BMC ProactiveNet Performance Management for the BMC Triage and Remediation solution

Follow the steps in this section to configure BMC ProactiveNet Performance Management to work with BMC Atrium Orchestrator.

1 Open mcell.dir and add the entry for BMC Atrium Orchestrator gateway as listed in the example below:

gateway.imcomm <BAO gateway> mc <IP_address>:1859

In the entry above, <IP_address> is the IP address of the system in which BMC Atrium Orchestrator is installed and <BAO gateway> is the BMC Atrium Orchestrator gateway name. The default gateway name is BEMGW.

You can change the BMC Atrium Orchestrator gateway name in the ao_actions.mrl file located at <system_drive>\Program Files\ProactiveNet\pw\server\etc\pncell_hostname\kb\bin

2 Recompile the BMC ProactiveNet cell using the mccomp -n <cell_name> command.

3 Reload the BMC ProactiveNet cell using the mcontrol -n <cell_name> reload all command.

Configuring the BMC Atrium Orchestrator grid for the BMC Triage and Remediation solution


Configuring the BMC Atrium Orchestrator grid for the BMC Triage and Remediation solution

To configure the BMC Atrium Orchestrator grid:

1 Launch the Configuration Distribution Peer (CDP) URL.

2 Log in to the grid using the user name and password created in BMC Atrium Orchestrator Access Manager. The default login and password are admin/admin123.

3 Click Manage => Grids.

4 Click the Add icon (+) to add a new grid.

5 Enter the name and description for the grid and click OK.

Configuring BMC Atrium Orchestrator for the BMC Triage and Remediation solution

Follow the steps in this section to configure BMC Atrium Orchestrator to work with BMC ProactiveNet Performance Management.

1 Create a directory named etc at <system_drive>\Program Files\BMC Software\AO.

2 Create a file named mcell.dir at <system_drive>\Program Files\BMC Software\AO\etc and add the following entries:

cell <cell_name> mc <cell_machine>:<cell_port> gateway.imcomm <BAO_gateway> mc <IP_address>: <monitor_adapter_port>

In the entry above, <IP_address> is address of the system in which the BMC ProactiveNet cell is installed.

For example, cell pncell_vm5-w23-pcdl215 mc Pcell_hostname:1828 gateway.imcomm AOBEMGW mc 172.21.253.86:1859

3 Restart CDP process from the Services console.

4 Launch the CDP URL and Connect to CDP.

5 Activate and configure the BEM Actor and BEM Monitor adapters.

Products and artifacts installed by the BMC Atrium Orchestrator content installer for the BCM Triage and Remediation


6 Verify that the adapters in step 6 display a Green status.

Products and artifacts installed by the BMC Atrium Orchestrator content installer for the BCM Triage and Remediation solution

The BMC Atrium Orchestrator content installer installs the following Run Book modules, Management modules, Core modules, and adapters.

Run Book module: Service Assurance and Triage Remediation

Task management modules:

■ AutoPilot OA Change Management■ AutoPilot OA Configuration Management■ AutoPilot Credential Store■ AutoPilot OA Event Management■ AutoPilot OA Incident Management■ AutoPilot OA Task Management

Platform modules:

■ AutoPilot AD Utilities■ AutoPilot OA Application Utilities■ AutoPilot OA Common Utilities■ AutoPilot OA Directory Services Utilities■ AutoPilot OA File Utilities■ AutoPilot OA Network Utilities■ AutoPilot OA Operating System Utilities■ AutoPilot OA Physical Device Utilities

Ensuring the correct AR System server user permissions for IBRSD integration


Core modules:

■ AutoPilot AD Utilities■ AutoPilot OA Application Utilities■ AutoPilot OA Common Utilities■ AutoPilot OA Directory Services Utilities■ AutoPilot OA File Utilities■ AutoPilot OA Network Utilities■ AutoPilot OA Operating System Utilities■ AutoPilot OA Physical Device Utilities

Adapters:

■ BMC Atrium Orchestrator Remedy actor adapter■ BMC Atrium Orchestrator Remedy Monitor adapter ■ BMC Atrium Orchestrator BMC Event Manager and BMC ProactiveNet monitor

adapter■ BMC Atrium Orchestrator BMC Event Manager and BMC ProactiveNet actor

adapter■ BMC Atrium Orchestrator Telnet adapter■ BMC Atrium Orchestrator Windows Command adapter■ BMC Atrium Orchestrator SSH adapter■ BMC Atrium Orchestrator SQL actor adapter■ BMC Atrium Orchestrator TSM actor adapter

For a complete and updated list of products and artifacts, see BMC ProactiveNet Performance Management Triage and Remediation Solution Getting Started Guide at http://webapps.bmc.com/support/faces/prodallversions.jsp?seqid=172810.

Ensuring the correct AR System server user permissions for IBRSD integration

Perform these steps to ensure that the BMC AR System user has the correct permissions to use IBRSD:

1 Log on to the BMC Remedy AR System.

2 Click File => Open => Object List.

3 On the Find tab, enter the User form keywords, and click Find.

Configuring BMC Atrium CMDB and BMC Atrium Discovery synchronization


4 Double-click the User form displayed in the search result to open it in the search mode.

5 Click Search.

6 Select the user ID that you used to connect to the BMC Remedy AR System.

7 A record for the selected user is displayed.

8 In the Group List field for the selected user, add the following permissions:

■ Administrator■ Incident Config■ Incident Master■ Incident Viewer■ Incident submitter■ Contact Organization Admin■ Contact Location Admin■ Contact People Admin■ Contact Support Admin■ Config Group Mapping Admin■ Config categorization Admin

Configuring BMC Atrium CMDB and BMC Atrium Discovery synchronization

To configure BMC Atrium CMDB and BMC Atrium Discovery synchronization:

1 Launch the Atrium Discovery Web console.

2 Login to Atrium Discovery.

3 Click the Administration tab.

4 Click the CMDB Sync icon.

5 Click Setup to configure BMC Atrium CMDB with Atrium Discovery.

6 Enter the BMC Atrium CMDB details.

7 Click Apply.

Configuring BMC ProactiveNet Application Diagnostics components (BMC AppSight Integration)


8 Click the Configuration tab.

9 Click the CMDB Sync icon.

BMC Atrium CMDB is synchronized with Atrium Discovery.

Configuring BMC ProactiveNet Application Diagnostics components (BMC AppSight Integration)

This section provides instructions to configure components for BMC ProactiveNet Application Diagnostics.

Removing BMC AppSight connector services from a previous version of BMC ProactiveNet

If you installed the BMC AppSight connector services in a previous version of BMC ProactiveNet, remove the services to uninstall the connector.

To remove BMC AppSight connector services

1 On the ProactiveNet Server, run the BMC PPM Application Diagnostics Connector.exe file.

The file is the same one that was used to install the connector service.

2 On the Setup Type page, select Remove one or more services and click Next.

3 On the Select Services page, select to remove all services and click Next.

4 Click Yes to confirm removal of the services and then click Finish.

Configuring and capturing in BMC AppSight for Java EE

BMC AppSight records and captures application problems for a specific transaction, and communicates the root cause to BMC ProactiveNet. Configure the capturing mode on the BMC AppSight Server and then start the recording (capturing).

Configuring and capturing in BMC AppSight for Java EE


To configure the capturing mode

1 On the BMC AppSight Server, open the cli.properties file, located in the AppSightInstallDirectory\Server\Standalone\properties folder.

2 Change the value of the DefaultSaveMode parameter to TRANSACTION-CAPTURING-MODE:

3 Save and close the file.

4 Restart the BMC AppSight Server.

To start recording in BMC AppSight for Java EE

1 On the BMC AppSight Server, run the StartRecording command from a command prompt, according to the following syntax:

In the sytax above:■ logName is a unique, user-defined alphanumeric name of the log to contain the

captured data■ BBXhost is the computer name or IP address of the Black Box■ port is the port number that is used by the BMC AppSight Server on the

computer

To stop recording in BMC AppSight for Java EE

1 On the BMC AppSight Server, run the StopRecording command from a command prompt, according to the following syntax:

In the sytax above:■ logName is the name of an existing log

DefaultSaveMode=TRANSACTION-CAPTURING-MODE

NOTE Before starting the BMC AppSight recording, ensure that the Black Boxes (BBXes) are connected to the BMC AppSight Server.

StartRecording logName "http://BBXhost:port, Business and Exceptions Flow"

StopRecording logName

Capturing in BMC AppSight for Windows


Capturing in BMC AppSight for Windows

BMC AppSight Black Boxes and server record and capture application problems for a specific transaction, and communicates the root cause to BMC ProactiveNet. Verify the Black Box connection to the BMC AppSight server and then start the recording (capturing) on the BMC AppSight Server.

Before you start the BMC AppSight recording, ensure that each Black Box is installed as a service and that the service is started.

To verify the Black Box connection to the BMC AppSight Server

1 On the BMC AppSight Server, run the AS.exe file, located in the AppSightInstallDirectory\bin folder.

2 Run the following commands:

where■ appSightServerName is the computer name or IP address of the BMC

AppSight Server.■ BBXhost is the computer name where the Black Box is installed.

The commands return the connection status of the Black Box.

To start recording in BMC AppSight for Windows


2 Run the following commands:

setserver "appSightServerName"bbxstat "BBXhost"

setserver "appSightServerName"setrpr "BBXhost" "AppSightInstallDirectory\Data\RPR\Web Server Monitor.rpr"autostartup "BBXhost"resume "BBXhost"

Configuring the BMC AppSight Repository server


where■ appSightServerName is the computer name or IP address of the BMC

AppSight Server.■ BBXhost is the computer name where the Black Box is installed.■ AppSightInstallDirectory is the absolute path of the of the BMC AppSight

installation on your system (C:\Program Files\AppSight by default).

To pause recording in BMC AppSight for Windows


2 Run the following command:

where BBXhost is the computer name where the Black Box is installed.


The BMC AppSight Repository server functions as a storage place for BMC AppSight recordings and as a proxy to send requests to, and gain control of, BMC AppSight servers. Through the BMC AppSight Repository server, BMC ProactiveNet can access detailed Application Diagnostics for slow and failed transactions.

This topic presents instructions to configure the BMC AppSight Repository.

To configure connections to the BMC AppSight components, add BMC AppSight Servers to the repository server. Black Boxes that are connected to the integrated components are listed under their respective BMC AppSight Servers, and the list is updated dynamically. If a server goes offline after you add it, only the server name is listed.

pause "BBXhost"

NOTE To add a BMC AppSight server to the repository, the server must be online and have at least one Black Box connected to it.



To configure the BMC AppSight Repository server

1 Access the BMC AppSight Repository server at the following URL:

http://AppSightReposServerHost:port/TeamLayer/ configuration/index.jsp

In the URL above:

■ AppSightReposServerHost is the computer name or IP address of the repository server

■ port is the port number that is used by the repository server on the computer. The default port is 7092.

2 For each BMC AppSight Server, type the server name in the text box, using the following syntax:

■ (for BMC AppSight Servers for Java EE)

http://AppSightServerHost:port

In the URL above:

— AppSightServerHost is the computer name or IP address of the BMC AppSight Server

— port is the port number that is used by the BMC AppSight Server on the computer

■ (for BMC AppSight Servers for Windows)

http://AppSightServerHost

In the URL above:

— AppSightServerHost is the computer name or IP address of the BMC AppSight Server

3 Click Add AppSight Server.

To remove a BMC AppSight server from the BMC AppSight Repository server

To remove a BMC AppSight server from the BMC AppSight Repository server, click the Delete icon next to the name of the server you want to delete.

Configuring the connection between BMC ProactiveNet and the BMC AppSight Repository server


To configure the number of days to keep a recording (optional)

By default, records are kept on the BMC AppSight Repository server for seven days. You can change the value of the number.of.days.to.keep.problems parameter.

1 On the BMC AppSight Repository server, open the common.properties file, located in the repositoryInstallDirectory\Server\properties folder.

2 Search for the number.of.days.to.keep.problems parameter and change the value as required.


4 Restart the BMC AppSight Repository service.

Configuring the connection between BMC ProactiveNet and the BMC AppSight Repository server

Configure the connection between the BMC ProactiveNet agent and the BMC AppSight Repository server. Establish the connection on each agent that monitors devices which BMC AppSight records.

To configure the connection between BMC ProactiveNet and the BMC AppSight Repository server

1 On the BMC ProactiveNet agent, open the pronet.conf file, located in the installDirectory\pw\pronto folder.

2 Edit the following properties as necessary:

Configuring BMC TM ART for BMC ProactiveNet Application Diagnostics




The adapter for BMC TM ART collects metrics from BMC TM ART Central and triggers events in BMC ProactiveNet when measurements cross defined thresholds. BMC ProactiveNet Application Diagnostics uses BMC AppSight technology to provide drill-down information about these events.

You configure BMC TM ART Monitor Workbench to add an HTTP header to transactions. BMC AppSight uses the unique identifier in the header to supply detailed information for every web request of a transaction.

Collecting BMC ProactiveNet Application Diagnostics for BMC TM ART transactions requires the following general procedure:

1. Install the BMC AppSight Black Box on the application server that BMC TM ART monitors (see “Documents You May Need” on page 9).

2. Configure the BMC ProactiveNet connection to the BMC AppSight Repository server (see “Configuring the BMC AppSight Repository server” on page 78 and “Configuring the connection between BMC ProactiveNet and the BMC AppSight Repository server” on page 80).

3. Configure BMC TM ART Monitor Workbench to add HTTP headers to every web request in transactions (see “Configuring BMC TM ART Workbench to add HTTP headers”).

Property Description

remoteURL Add the URL of the BMC AppSight Repository server, including the computer name or IP address of the server and the port number, using the following syntax:

pronet.apps.detailDiagnostics.application Diagnostics.remoteURL= http://AppSightReposServerHost:port

enableEscalation (optional) Set to true to save records to the AppSight database. The default setting is pronet.apps.detailDiagnostics.application Diagnostics.enableEscalation=false.

Note: If you have a full license for BMC AppSight, you can view the saved records in JSL or ASL log files in the BMC AppSight Console.



4. Configure the BMC ProactiveNet adapter for BMC TM ART (see the BMC ProactiveNet Administrator Guide).

Configuring BMC TM ART Workbench to add HTTP headers

This topic presents instructions to configure BMC TM ART Monitor Workbench (MWB files) to add HTTP headers to MWB-based transactions. Configuration is required for integration with BMC AppSight, which provides in-depth details about transactions that exceed defined thresholds. For detailed information about BMC TM ART Monitor Workbench, see http://webapps.bmc.com/support/faces/prodallversions.jsp?seqid=133068.

Edit each MWB script to add a unique HTTP header name to every web request.

To configure BMC TM ART Monitor Workbench to add HTTP headers

1 For BMC TM ART Monitor Workbench version 3.6 or earlier, copy the HttpHeaderTagging.bdh file to workbenchInstallDirectory\Working\Include directory on the BMC TM ART Monitor Workbench computer.

2 In BMC TM ART Monitor Workbench, record a web transaction to generate a script.

3 In the script, include the HttpHeaderTagging.bdh file using the keyword use declaration:

The HttpHeaderTagging.bdh file appears under the Include Files folder in the tree view.

4 In the transactions section of the script, under TMain, call the TagHeader function after the begin keyword:

NOTE For BMC TM ART Monitor Workbench version 3.9, the HttpHeaderTagging.bdh file is already in the required directory.

use "HttpHeaderTagging.bdh"

transaction TMainvarbegin

TagHeader();




When you finish configuring the MWB files to add HTTP headers, configure the BMC TM ART Monitor Workbench script in BMC TM ART Central. For details, see the BMC TM ART Central User Guide, available at http://webapps.bmc.com/support/faces/prodallversions.jsp?seqid=133068.

Description of the HTTP headers

The following table describes the components of the HTTP header name:

Header component Description

X-BMCFollowTX_1.0.00 Version number of the header name

PN BMC TM ART Monitor Workbench project name

ST Transaction start time (ST) in the Execution Server, as the number of milliseconds elapsed since midnight on January 1, 1970, UTC

ID Unique ID for every run of the script in the Execution Server of BMC TM ART Central




Notes

*166633**166633**166633**166633*

*166633*