bmc impact solutions planning and implementation guide

www.bmc.com

BMC Impact SolutionsPlanning and Implementation Guide

Supporting

BMC Event Manager 7.3.00BMC Service Impact Manager 7.3.00

February 2009

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

AIX is the trademark or registered trademark of International Business Machines Corporation in the United States, other countries, or both.

Linux is the registered trademark of Linus Torvalds.

Oracle is a registered trademark of Oracle Corporation.

Solaris is a trademark or registered trademark of Sun Microsystems, Inc., in the U.S. and several other countries.

UNIX is the registered trademark of The Open Group in the US and other countries.

BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this 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_home. 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_home

mailto:[email protected]

License key and password information

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

■ (USA or Canada) Contact the Order Services Password Team at 800 841 2031, or send an e-mail message to [email protected].

■ (Europe, the Middle East, and Africa) Fax your questions to EMEA Contracts Administration at +31 20 354 8702, or send an e-mail message to [email protected].

■ (Asia-Pacific) Contact your BMC sales representative or your local BMC office.

4 BMC Impact Solutions Planning and Implementation Guide



ContentsChapter 1 Planning your implementation 11

BMC Impact Solutions products and components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12BMC Impact Solutions overall architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Flexible deployment options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Basic deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Standard deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Atrium deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Choosing your installation scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Installing event management only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Installing service impact management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Installing a high-availability cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Recommended architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Small BMC Event Manager only environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Large BMC Event Manager only environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Small EM and SIM environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Medium EM and SIM environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Large EM and SIM environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

BMC Event Management implementation workflow . . . . . . . . . . . . . . . . . . . . . . . . . . 36BMC Service Impact Manager with the BMC Atrium CMDB implementation

workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Example architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

EM customer—large public-sector organization . . . . . . . . . . . . . . . . . . . . . . . . . . . 39EM and SIM customer—large retail company . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41EM and SIM customer—large energy company. . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Chapter 2 Implementation considerations 45

Performance and scalability lab results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Number of BMC Impact Managers to use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

When to use multiple BMC Impact Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Using tiers to share the load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Using a “processing” and a “presentation” BMC Impact Manager . . . . . . . . . . . 48

Master or Standard BMC Impact Administration Server . . . . . . . . . . . . . . . . . . . . . . . 49High-availability cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Roles and permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Event groups and image views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Internationalization compatibility for Common Event Model slots . . . . . . . . . . . . . . 51Component installation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Database for the BMC Remedy AR System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51BMC Remedy AR System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Contents 5

BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53BMC SIM CMDB extensions and BMC Remedy ITSM applications . . . . . . . . . . . 54Database for the BMC Impact Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54BMC Impact Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55BMC Impact Publishing Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55BMC Impact Service Model Editor with a firewall . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Component upgrade considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Database for the BMC Remedy AR System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56BMC Remedy AR System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57BMC Impact Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Database for the BMC Impact Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57BMC Impact Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

BMC Impact Integration for PATROL hardware sizing requirements . . . . . . . . . . . . 58Maximum number of BMC II for PATROL instances connecting to a cell . . . . . . 58Determining when to use multiple BMC II for PATROL adapters or

multiple cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Index 61


Figures 7

FiguresBMC Impact Solutions architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Physical layout for a small EM environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Physical layout for a large EM environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Physical layout for a small EM and SIM environment . . . . . . . . . . . . . . . . . . . . . . . . . 31Physical layout for medium EM and SIM environment . . . . . . . . . . . . . . . . . . . . . . . . 32Physical layout for large SIM environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Implementation workflow for BMC Event Management . . . . . . . . . . . . . . . . . . . . . . . 37implementation workflow for BMC Service Impact Management with the BMC

Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Logical architecture—large public-sector customer . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Logical architecture—large retail company . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Logical architecture—large energy company . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

TablesInstalling event management only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Factors to consider when installing BMC Service Impact Manager . . . . . . . . . . . . . . 19Installing service impact management for a small service model . . . . . . . . . . . . . . . . 20Installing service impact management for a medium to large service model . . . . . . 22Installing service impact management for a very large service model . . . . . . . . . . . . 24Computer specifications and applications for medium EM and

SIM environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Computer specifications and applications for large EM and SIM environment . . . . 34Example implementation using three servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Tables 9

C h a p t e r 1
1 Planning your implementation
This chapter describes deployment options and installation scenarios, and provides reference architectures for different size environments and recommendations for two scenarios, a BMC Event Manager only environment and a BMC Service Impact Manager environment that includes BMC Event Manager. Sizing guidelines are conservative to allow for the natural growth of the solution.

This chapter presents the following topics:

BMC Impact Solutions products and components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12BMC Impact Solutions overall architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Flexible deployment options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Basic deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Standard deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Atrium deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Choosing your installation scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Installing event management only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Installing service impact management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Installing a high-availability cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Recommended architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Small BMC Event Manager only environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Large BMC Event Manager only environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Small EM and SIM environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Medium EM and SIM environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Large EM and SIM environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

BMC Event Management implementation workflow . . . . . . . . . . . . . . . . . . . . . . . . . . 36BMC Service Impact Manager with the BMC Atrium CMDB implementation

workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Example architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

EM customer—large public-sector organization . . . . . . . . . . . . . . . . . . . . . . . . . . . 39EM and SIM customer—large retail company . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41EM and SIM customer—large energy company. . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Chapter 1 Planning your implementation 11

BMC Impact Solutions products and components

BMC Impact Solutions products and components

Products and components of this solution are

■ BMC Impact Manager (also known as “cell”)■ BMC Impact Administration Server■ BMC Impact Publishing Server■ BMC Event Adapters■ BMC Impact Integrations

— BMC Impact Database Gateway— Integration for BMC Remedy Service Desk (IBRDS)

■ BMC Impact Service Model Integration for HP OVO■ BMC Impact Service Model Editor■ BMC Atrium CMDB■ BMC SIM CMDB Extensions■ BMC Datastore■ BMC Impact Portal■ BMC Impact Explorer

For additional details, see the BMC Impact Solutions Concepts Guide.

BMC Impact Solutions overall architectureBMC Event Manager and BMC Service Impact Manager

■ handle and process all of the message traffic that accompanies IT Events

■ provide a view of the operational state (up, down, degraded) of the infrastructure based on what can be learned from message traffic

■ provide an understanding of how an outage or degradation in performance within the IT infrastructure affects the organization’s ability to deliver IT services to its customers

■ assist in finding the IT root cause of business service degradation or outage

Figure 1 on page 13 shows the architecture of the components that are part of BMC Impact Solutions.


Flexible deployment options

Figure 1 BMC Impact Solutions architecture

Flexible deployment optionsBMC Impact Solutions versions 5.x and 7.0.x were dependent on BMC Portal and BMC Atrium CMDB. While these components provide value by enabling various integrations and the BSM workflows, not all users need or require these components to get started with BMC Impact Solutions.

BMC Impact Solutions 7.3.00 provides three deployment options that allow you to get started with BMC Impact Solutions with or without the BMC Portal and BMC Atrium CMDB.

Upgrade paths are available if you want to upgrade your deployment. For example, you might upgrade from basic to either the standard or Atrium deployments or from the standard deployment to the Atrium deployment. The deployment options are discussed in detail in the following sections.


Basic deployment

Basic deployment

Basic deployment is the simplest and most light-weight way of deploying BMC Impact Solutions. A minimum basic deployment relies on the three core components of BMC Impact Solutions:

■ BMC Impact Manager (IM)—the event and service impact engine

■ BMC Impact Explorer (IX)—the operation and administration console

■ BMC Impact Administration Server (IAS)—the authentication/authorization server for the users of the solution and the infrastructure services for administering the solution. If you are familiar with versions 3.5 and 4.1 of BMC Impact Solutions, the IAS provides the functions of the IXS server as well as additional administration functionality.

The BMC Portal and BMC Atrium CMDB are not part of the basic deployment.

BMC Impact Event Adapters, BMC Impact Integration for Web Services, and other impact integration components can be used with the basic deployment.

Basic deployment has the following advantages:

■ faster time-to-value■ less complicated configuration■ less hardware required■ Microsoft Windows, AIX®, HP-UX, SolarisTM, and Linux® are supported by all core

components (For details on which versions are supported, see the BMC Impact Solutions Release Notes.)

The basic deployment option does not provide:

■ publishing to the BMC Impact Manager server(s)■ BMC Event and Impact Reporting and some operational views (which require

BMC Impact Portal)■ BSM workflows■ out-of-the-box intelligent ticketing for BMC Remedy Service Desk■ out-of-the-box BMC Remedy SLM integration


Standard deployment

Standard deployment

Standard deployment is recommended for organizations that

■ have or plan to use BMC Performance Manager for application and systems management

■ need to report on their events and service impacts

■ use a third party repository for their service model data and want to publish this data in a controlled manner by using the BMC Impact Publishing Server

The standard deployment option includes

■ the components included in the basic deployment

■ the BMC Impact Publishing Server

■ BMC Portal, which includes the BMC Impact Portal

■ BMC Event and Impact Reporting

BMC IAS has replaced BMC Impact Portal as the authentication for BMC Impact Explorer.

BMC Impact Publishing Server can be used to control the publication of service model data (for example, data coming from a non-BMC CMDB) to the BMC Service Impact Manager.

The BMC Atrium CMDB is not part of the standard deployment.

The standard deployment has the following advantages:

■ direct publish to the BMC Impact Manager server(s)■ out-of-the-box reporting■ Portal operational views■ BMC Performance Manager integration (when applicable)■ no need to activate and work in a controlled environment like the BMC Atrium

CMDB

The standard deployment does not provide

■ BSM workflows■ out-of-the-box intelligent ticketing for BMC Remedy Service Desk■ out-of-the-box BMC Remedy SLM integration


Atrium deployment

Atrium deployment

The Atrium deployment adds the BMC Atrium CMDB to the components included in the standard deployment. The architecture is similar to the BMC Service Impact Manager architecture versions 5.x and 7.0.x.

The Atrium deployment includes all the advantages of standard deployment plus the following advantages:

■ BMC Atrium CMDB publishing to the BMC Impact Manager server(s)■ support for multiple CI providers■ BSM workflows■ out-of-the-box intelligent ticketing for BMC Remedy Service Desk■ BMC Remedy SLM integration

The Atrium deployment is appropriate for larger BSM implementations where the skills and resources are more readily available to handle a CMDB and its workflow.

Choosing your installation scenarioUse this section to help you determine whether to install event management only or install service impact management (which includes event management). This section also helps you determine whether you want to enable either scenario for high availability.

This section describes these installation scenarios:

■ event management only. See “Installing event management only” on page 17.

■ service impact management for the following service models:

— small service models (fewer than 1,000 objects).

— medium (between 1,000 and 5,000 objects) to large (between 5,000 and 10,000 objects) service models.

— very large service models (more than 10,000 objects).

See “Installing service impact management” on page 18.

■ high availability (for event or service impact management). See “Installing a high-availability cell” on page 25.


Installing event management only

Installing event management only

For event management, you can install all the products and solutions on one computer unless you want to do long-term reporting or configure a cell for high availability. If you want to do long-term reporting, you must install Reporting for BMC Service Assurance and BMC Event and Impact Reporting on a separate computer from the event management components because of space requirements.

Table 1 provides information about the order in which to install products, the computers on which to install them, and where to find the step-by-step installation instructions for each individual product or component.

For recommended hardware configurations, see “Recommended architectures” on page 26.

NOTE If you plan to install BMC Event Management only but also need to integrate BMC Performance Manager or BMC Remedy Service Desk with the BMC Atrium CMDB, you must also install the BMC SIM CMDB extensions.

Table 1 Installing event management only (part 1 of 2)

Action Computer Reference

1. (optional) Install the BMC Impact Portal database.

1 See the BMC Datastore Installation Guide.

2. Install the BMC Impact Solutions components.

1 See the BMC Impact Solutions Installation Guide.

3. (optional) Install the BMC Impact Portal. 1 See the BMC Portal Installation Guide.

For instructions for the web server, see the BMC Impact Integration Web Services Installation and Configuration Manual.

4. (optional) Install the SNMP libraries. 1 See the BMC Impact Solutions Installation Guide

5. (optional) Install BMC Impact Integration for PATROL.

1 See the BMC Impact Integration for PATROL Installation and Configuration Guide.

6. (optional) Install BMC Impact Integration for PATROL Enterprise Manager.

1 See the BMC Impact Integration for PATROL Enterprise Manager Installation and Configuration Guide.

Warning: Both BMC Impact Portal and BMC Impact Integration for PATROL Enterprise Manager use the default port number 3783. If you have both of these products installed on the same computer, you must change the port number for BMC Impact Portal. For more information, see the BMC Portal Getting Started guide.


Installing service impact management


When you install the components for service impact management (SIM), you automatically obtain the event management functionality as well as that for SIM; however, you must select the Both package option in the Impact Solutions installer to install all of the components for both BEM and SIM.

Table 2 on page 19 lists the factors that you should consider when determining which SIM installation scenario to use. The most important factor is the size of your service model (the number of objects that you are managing). Depending on the size of your service model, you might want to distribute the installation of the components among several computers. The other factors listed in this table can also influence your decisions about where to install specific components.

For recommended hardware configurations for each service impact management scenarios, see “Recommended architectures” on page 26.

7. (optional) Install Reporting for BMC Service Assurance.

2 See the BMC Event and Impact Reporting Release Notes and Crystal Reports Server XI Quick Installation Guide - Windows.

Warning: The BMC Reporting Oracle® server must be the only Oracle database management system (DBMS) on the computer. The BMC Reporting Oracle server cannot be installed on the same computer on which the BMC Atrium CMDB is installed.

8. (optional) Install BMC Event and Impact Reporting.

2 See the BMC Event and Impact Reporting Installation, Configuration, and User Guide.

Table 1 Installing event management only (part 2 of 2)




When you determine the number of computers on which you want to install the components, ensure that the computers that you select meet the requirements for installing and running these products. For system requirement information, see the BMC Impact Solutions Release Notes and the BMC Portal Release Notes.

Installing service impact management for a small service model

Table 3 on page 20 provides information about the order in which to install products, the computers on which to install them, and where to find the step-by-step installation instructions for each individual product or component.

Table 2 Factors to consider when installing BMC Service Impact Manager

Question Explanation

How many objects are you managing?

The number of objects that you are managing is the most important factor when determining your installation scenario for SIM. Depending on the size of your service model (that is, the number of objects defined in the BMC Impact Service Model Editor or BMC Impact Explorer), you can install most of the components on one computer or distribute the installation of the components among several computers.

Are you clustering your environment?

If you have an environment that contains 10,000 or more objects, consider clustering the BMC Impact Portal for fault tolerance, load balancing, and scalability. In a clustered environment, you install the datastore server on a separate computer and the web server or the application server or both on two or more computers. For detailed information about and deployment scenarios for clustering, see the BMC Portal Installation Guide and the BMC Portal Getting Started guide.

Are you performing remote and agent-based monitoring and management?

If you are going to perform remote and agent-based monitoring and management, you must install the BMC Performance Manager Portal when installing the BMC Impact Portal. You can install the BMC Performance Manager Portal on the same computer on which you install the BMC Impact Portal.

Do you want to do long-term reporting?

You can do long-term reporting by installing BMC Reporting Foundation Express and BMC Event and Impact Reporting. These products cannot be installed on the same computer on which BMC Atrium CMDB is installed. For more information about BMC Event and Impact Reporting, see the BMC Event and Impact Reporting Installation, Configuration, and User Guide.



Table 3 Installing service impact management for a small service model (part 1 of 2)


1. (optional) Install a single database to use for both BMC Impact Portal and BMC Remedy AR System.

1 See “Database for the BMC Remedy AR System” on page 51 and the BMC Remedy AR System 7.1: Installing guide or the BMC Remedy Action Request System 7.5 Installation Guide, depending on what version you will be using.

2. (optional) Install BMC Remedy AR System. 1 See “BMC Remedy AR System” on page 52 and the BMC Remedy AR System 7.1: Installing guide or the BMC Remedy Action Request System 7.5 Installation Guide, depending on what version you will be using.

3. (optional) Install BMC Remedy Administrator.

1 See “BMC Remedy AR System” on page 52 and the BMC Remedy AR System 7.1: Installing guide or the BMC Remedy Action Request System 7.5 Installation Guide, depending on what version you will be using.

4. (optional) Install BMC Remedy User. 1 See “BMC Remedy AR System” on page 52 and the BMC Remedy AR System 7.1: Installing guide or the BMC Remedy Action Request System 7.5 Installation Guide,depending on what version you will be using.

5. (optional) Install BMC Atrium CMDB. 1 See “BMC Atrium CMDB” on page 53 and the BMC Atrium CMDB 2.1: Installation and Configuration Guide or the BMC Atrium Core 7.5 Installation Guide, depending on what version you will be using.

6. (optional) Install BMC SIM CMDB extensions.

1 In the 7.3 version of BMC Impact Solutions, there are two installation programs for the BMC SIM CMDB extensions, depending on what version of the BMC Atrium CMDB you are using. For details, see the BMC Impact Solutions Installation Guide.




If you are not using a single common database server for the BMC Remedy AR System and the BMC Impact Portal, install an Oracle database for the BMC Impact Portal.

1 See “Database for the BMC Impact Portal” on page 54 and the BMC Datastore Installation Guide.

9. (optional) Install the BMC Impact Portal. 1 See “BMC Impact Portal” on page 55 and the BMC Portal Installation Guide.




Other related products, such as BMC Atrium Discovery, should be installed on a separate computer unless otherwise specified in that product’s documentation. If you are installing BMC Atrium Discovery on the same computer as BMC Impact Solutions, BMC Atrium Discovery can be installed either before or after BMC Impact Solutions.

10. (optional) Install the SNMP libraries. 1 See the BMC Impact Solutions Installation Guide.


1 See the BMC Impact Integration for PATROL User Guide.



Warning: Both BMC Impact Portal and BMC Impact Integration for PATROL Enterprise Manager use the default port number 3783. If you have both of these products installed on the same computer, you must change the port number for BMC Impact Portal. For more information, see BMC Portal Getting Started.

13. (optional) Install the AR module for the Integration for BMC Remedy Service Desk.

1 See the Integration for BMC Remedy Service Desk User Guide.



Warning: The BMC Reporting Oracle server must be the only Oracle database management system (DBMS) on the computer. The BMC Reporting Oracle server cannot be installed on the same computer on which the BMC Atrium CMDB is installed.



Table 3 Installing service impact management for a small service model (part 2 of 2)




Installing service impact management components for a medium to large service model


Table 4 Installing service impact management for a medium to large service model (part 1 of 2)


1. Install a single database to use for both the BMC Impact Portal and BMC Remedy AR System.


2. Install BMC Remedy AR System. 2 See “BMC Remedy AR System” on page 52 and the BMC Remedy AR System 7.1: Installing guide or the BMC Remedy Action Request System 7.5 Installation Guide, depending on what version you will be using.

3. Install BMC Remedy Administrator. 2 See “BMC Remedy AR System” on page 52 and the BMC Remedy AR System 7.1: Installing guide or the BMC Remedy Action Request System 7.5 Installation Guide, depending on what version you will be using.

4. Install BMC Remedy User. 2 See “BMC Remedy AR System” on page 52 and the BMC Remedy AR System 7.1: Installing guide or the BMC Remedy Action Request System 7.5 Installation Guide, depending on what version you will be using.

5. Install BMC Atrium CMDB. 2 See “BMC Atrium CMDB” on page 53 and the BMC Atrium CMDB 2.1: Installation and Configuration Guide or the BMC Atrium Core 7.5 Installation Guide, depending on what version you will be using.

6. Install BMC SIM CMDB extensions. 2 In the 7.3 version of BMC Impact Solutions, there are two installation programs for the BMC SIM CMDB extensions, depending on what version of the BMC Atrium CMDB you are using. For details, see the BMC Impact Solutions Installation Guide.








9. Install BMC Impact Portal. 1 See “BMC Impact Portal” on page 55 and the BMC Portal Installation Guide.







Warning: Both BMC Impact Portal and BMC Impact Integration for PATROL Enterprise Manager use the default port number 3783. If you have both of these installed on the same computer, you must change the port number for BMC Impact Portal. For more information, see the BMC Portal Getting Started.








Table 4 Installing service impact management for a medium to large service model (part 2 of 2)




Installing service impact management components for a very large service model


Table 5 Installing service impact management for a very large service model (part 1 of 2)


1. Install a single database to use for both the BMC Impact Portal and BMC Remedy AR System.


2. Install BMC Remedy AR System. 3 See “BMC Remedy AR System” on page 52 and the BMC Remedy AR System 7.1: Installing guide or the BMC Remedy Action Request System 7.5 Installation Guide, depending on what version you will be using.

3. Install BMC Remedy Administrator. 3 See “BMC Remedy AR System” on page 52 and the BMC Remedy AR System 7.1: Installing guide or the BMC Remedy Action Request System 7.5 Installation Guide, depending on what version you will be using.

4. Install BMC Remedy User. 3 See “BMC Remedy AR System” on page 52 and the BMC Remedy AR System 7.1: Installing guide or the BMC Remedy Action Request System 7.5 Installation Guide, depending on what version you will be using.

5. Install BMC Atrium CMDB. 3 See “BMC Atrium CMDB” on page 53 and the BMC Atrium CMDB 2.1: Installation and Configuration Guide or the BMC Atrium Core 7.5 Installation Guide, depending on what version you will be using.

6. Install BMC SIM CMDB extensions. 3 In the 7.3 version of BMC Impact Solutions, there are two installation programs for the BMC SIM CMDB extensions, depending on what version of the BMC Atrium CMDB you are using. For details, see the BMC Impact Solutions Installation Guide.







Installing a high-availability cell

Installing a high-availability cell

You can run a cell on a stand-alone computer, or you can run a high-availability cell that provides failover capability by employing two cell servers running on separate computers. If you want to install a cell for high availability, you must install the primary and secondary cell servers on two different logical operating system images of the same type. The installation script guides you through high-availability cell server installation if you choose that option.

9. Install BMC Impact Portal. 1 See “BMC Impact Portal” on page 55 and the BMC Portal Installation Guide.







Warning: Both BMC Impact Portal and BMC Impact Integration for PATROL Enterprise Manager use the default port number 3783. If you have both of these installed on the same computer, you must change the port number for BMC Impact Portal. For more information, see the BMC Portal Getting Started.



14. Install Reporting for BMC Service Assurance.



15. Install BMC Event and Impact Reporting.

4 For more information, see the BMC Event and Impact Reporting Installation, Configuration, and User Guide.

Table 5 Installing service impact management for a very large service model (part 2 of 2)



Recommended architectures

For an explanation of how a high-availability cell works and for procedures for configuring primary and secondary cell servers, see BMC Impact Solutions Infrastructure Administration Guide.

For details on registering the cell with the BMC Impact Portal, see BMC Impact Solutions Getting Started Guide.

Recommended architecturesOn equivalent hardware, BMC Impact Solutions demonstrate no substantive difference on different platforms in terms of footprint and performance. Based on testing done in BMC Software testing labs, Microsoft Windows, Linux, and UNIX platforms have very similar performance figures.

Using a dual CPU (or dual core single CPU) computer to host the BMC Impact Manager ensures that BMC Impact Manager processing does not encounter performance issues when the State Builder runs.

Both BMC Event Manager (BMC EM) and BMC Service Impact Manager (BMC SIM) use the same underlying technology, BMC Impact Manager, and therefore share many features. A SIM cell processes events in the exact same manner as a EM cell. It may therefore be tempting to use a single cell to perform both event and service impact management. However, best practice is to split event and service impact functionality into separate cells. In other words, use one cell for event management functions (event collection, normalization, de-duplication, correlation, escalation) and another cell for service impact management functions.

In each of the environments listed in the following sections, the BMC Impact Explorer runs on remote desktops, typically at operator workstations. In the associated diagrams, blue, dotted lines represent event flows. Black, dashed lines represent console connections from BMC Impact Explorer to BMC Impact Manager instances. For clarity, all application connections, failover capabilities for the IAS and cell, and event and impact reporting are not shown.

Small BMC Event Manager only environment

A small EM environment is one used to collect and manage events for a centralized IT infrastructure with the following characteristics:

■ no more than 200 computers, all located on the same local area network

■ no more than 2 monitoring tools (for example, BMC Performance Manager, SNMP) are feeding events to EM


Small BMC Event Manager only environment

■ no more than 500,000 events per day are collected and processed

■ no more than 5 users are simultaneously logged in to BMC Impact Explorer

■ no reporting needs

■ no high availability

■ standard (out-of-box) Knowledge Base and EM policies are used

In this environment, the entire BMC Impact Solution (including the BMC Portal database) can be hosted on a single, dedicated computer with the following specifications:

■ 2 CPUs (1.5 GHz or above)■ 4 GB of RAM■ 30 GB of high-speed disks

To accommodate growth (the number of events or users increases or complex rules and policies are applied), consider

■ moving the IAS to a separate computer■ placing the event integration components (BMC Impact Integration for PATROL,

adapters, and so on) on a separate computer

Figure 2 Physical layout for a small EM environment


Large BMC Event Manager only environment


A large EM environment is one used to collect and manage events for a distributed IT infrastructure with the following characteristics:

■ 2,000 to 5, 000 computers, distributed across several data centers with high-speed connections

■ multiple monitoring tools (for example, BMC Performance Manager, SNMP) are feeding events to EM

■ an total of more than 1,000,000 events per day, with an average of 300,000 events per data center

■ standard (out-of-box) Knowledge Base is used, with modifications to separate the processing and presentation of events



■ up to 15 users are simultaneously logged in to BMC Impact Explorer

In this environment, best practice is to install a BMC Impact Manager instance in each remote location. These remote Impact Managers collect events directly from the event sources, filter sympathetic events, and apply normalization and de-duplication rules to the other events. Only important events are then propagated to the Impact Manager in the operations center. Servers and Impact Managers in all remote locations should have the same configuration.

Each remote location runs the BMC Impact Manager instance as well as adapters and integration components and requires one dedicated computer with the following specifications:

■ 2 CPUs (1.5 GHz or above)■ 2 GB of RAM

The sizing of the servers in remote locations may vary based on the event volumes in each location. It may be acceptable to use servers with less power, such as a single CPU when event volumes are low (less than 200,000 events per day).

The operations center runs IAS plus two Impact Managers, one for processing events and the second for presenting events to operators. One dedicated server is required with the following specifications:

■ 2 CPUs (1.5 GHz or above)■ 4 GB of RAM■ high-speed disks



BMC IX instances run on operators’ desktops and connect to the presentation BMC Impact Manager. Since BMC IX instances need only occasional connection to the remote Impact Managers (mostly for administrative purposes), these connections are not shown in Figure 3.


■ setting up SAN technology for event and data storage in the operations center■ installing a separate Impact Manager instance to handle source events that are

received in the operations center■ if BMC Performance Manager is installed, reviewing the recommendations

provided in BMC Performance Manager Portal Performance and Scalability Guidelines.■ moving the web server and application server to separate computers

Figure 3 Physical layout for a large EM environment


Small EM and SIM environment

Small EM and SIM environment

A small EM and SIM environment is one in which EM is used to collect and manage events for a centralized IT infrastructure and SIM is the service impact management solution. It has the following characteristics:

■ no more than 200 computers, all located on the same local area network

■ no more than 2 monitoring tools (for example, BMC Performance Manager, SNMP) are feeding events to EM

■ no more than 200,000 events per day



■ standard (out-of-box) EM Knowledge Base and policies are used

■ standard (out-of-box) SIM Knowledge Base and policies are used

■ the service model has no more than a few hundred components plus the same number of relationships

■ the service model is updated monthly

■ the BMC Atrium CMDB is only used by BMC Impact Solutions (and not by Remedy ITSM applications)


In this environment, the entire BMC Impact Solution (including the BMC Atrium CMDB) can be hosted on a single, dedicated computer with the following specifications:

■ at least 2 but 4 recommended CPUs (1.5 GHz or above)■ 4 GB of RAM

In Figure 4 on page 31, the dotted, blue arrows represent event flows, the dashed, black arrows represent console connections (from BMC IX to BMC Impact Managers), and the solid orange arrows show database dependencies.


Medium EM and SIM environment

Figure 4 Physical layout for a small EM and SIM environment

To accommodate growth (the number of events or users increases or complex rules and policies are applied), apply selected suggestions for “Medium EM and SIM environment” and “Large EM and SIM environment” on page 33.


A medium EM and SIM environment is one in which EM collects and manages events and SIM is the service impact management solution. It has the following characteristics:

■ events are collected and managed from a mid-size IT infrastructure with hundreds of servers in a central location

■ various monitoring tools (for example, BMC Performance Manager, SNMP) are feeding events to EM

■ approximately 500,000 events are collected per day






■ the service model has no more than a 5,000 components plus the same number of relationships

■ the service model is updated (republished) weekly

■ the BMC Atrium CMDB is only used by BMC Impact Solutions (and not by Remedy ITSM applications)


In this environment, the BMC Impact Solution (including the BMC Atrium CMDB) is hosted on two computers with the following specifications:

Figure 5 Physical layout for medium EM and SIM environment

Table 6 Computer specifications and applications for medium EM and SIM environment

Computer Specifications Products or components

Server 1 4 CPUs4 GB of RAM

Impact Manager instances for EM and SIMBMC Impact Portal application server and web server


BMC Remedy AR SystemBMC Atrium CMDBdatabase for BMC Impact Portal and BMC Atrium CMDB


Large EM and SIM environment


■ applying BMC Portal tuning guidelines described in the BMC Performance Manager Portal Performance and Scalability Guidelines

■ increasing the number of threads (list and fast) for the BMC Remedy AR Server by using the BMC Remedy Administrator tool. The recommended number of threads is 2 for each processor. See also the white paper Performance Tuning for Business Service Management.

■ moving the database for the BMC Portal to a computer separate from the database for BMC Atrium CMDB

■ placing the event integration components (BMC Impact Integration for PATROL, adapters, and so on) on separate computers

■ setting up SAN technology for event and data storage■ using the architecture for a large EM environment (see “Large BMC Event

Manager only environment” on page 28)■ if Remedy ITSM applications are installed, reviewing the white paper Sizing and

Capacity Planning for BMC Remedy IT Service management 7.0 and BMC Atrium CMDB 2.0

■ if BMC Performance Manager is installed, reviewing the recommendations provided in BMC Performance Manager Portal Performance and Scalability Guidelines


A large EM and SIM environment is one in which EM collects and manages events and SIM is the impact management solution. It has the following characteristics:

■ 2,000 to 5,000 computers are distributed across several data centers with high-speed connections

■ various monitoring tools (for example, BMC Performance Manager, SNMP) are feeding events to EM

■ 1,000,000 or more events are collected per day




■ the service model has no more than a 10,000 components and about the same number of relationships

■ the service model may be updated (republished) daily



■ the BMC Atrium CMDB may be used by a medium configuration BMC Remedy ITSM suite

For additional information about a medium configuration environment for Remedy ITSM and BMC Atrium CMDB, see the white papers Sizing and Capacity Planning for BMC Remedy IT Service Management 7.0 and BMC Atrium CMDB 2.0 and BMC Atrium CMDB Performance.

For the EM part of this environment, dedicated Impact Manager instances are installed in each remote data center and feed events to a computer that hosts the central EM and SIM instances. The BMC Impact Solutions is hosted on 4 computers with the following specifications:

Table 7 Computer specifications and applications for large EM and SIM environment

Computer Specifications Products or components

Server 1 4 CPUs8 GB of RAMSAN storage is used for events and data

Impact Manager instances for EM and SIMBMC Impact Portal application server and web server


BMC Remedy AR SystemBMC Atrium CMDBITSM applications

Server 3 4 CPUs8 GB of RAMSAN storage is used for events and data

database for BMC Impact Portal and BMC Remedy AR System

Servers 4-n 2 CPUs2 GB RAM

Impact Manager instances in remote data centers



Figure 6 Physical layout for large SIM environment


■ applying BMC Portal tuning guidelines described in the BMC Performance Manager Portal Performance and Scalability Guidelines

■ increasing the number of threads (list and fast) for the BMC Remedy AR Server by using the BMC Remedy Administrator tool. The recommended number of threads is 2 for each processor. See also the white paper Performance Tuning for Business Service Management.

■ moving the database for the BMC Portal to a computer separate from the database for BMC Atrium CMDB

■ placing the event integration components (BMC Impact Integration for PATROL, adapters, and so on) on separate computers

■ for Remedy ITSM applications information, reviewing the white paper Sizing and Capacity Planning for BMC Remedy IT Service management 7.0 and BMC Atrium CMDB 2.0

■ if BMC Performance Manager is installed, reviewing the recommendations provided in BMC Performance Manager Portal Performance and Scalability Guidelines.


BMC Event Management implementation workflow

BMC Event Management implementation workflow

Figure 7 on page 37 shows the steps that you must complete to implement BMC Event Management.

You will need to refer to the following BMC Impact Solutions documentation to help you with your BMC Event Management implementation:

■ BMC Impact Solutions Installation Guide■ BMC Impact Solutions Getting Started Guide■ BMC Impact Solutions Event Management Guide■ BMC Impact Solution Event Adapters User Guide■ BMC Impact Solutions Infrastructure Administration Guide■ BMC Event and Impact Reporting Installation, Configuration, and User Guide■ BMC Portal Installation Guide■ BMC Datastore Installation Guide


BMC Service Impact Manager with the BMC Atrium CMDB implementation workflow

Figure 7 Implementation workflow for BMC Event Management


Figure 8 on page 38 shows the steps that you must complete to implement BMC Service Impact Management with a BMC Atrium CMDB.



You will need to refer to the following BMC Impact Solutions documentation to help you with your BMC Service Impact Management implementation:

■ BMC Impact Solutions Installation Guide■ BMC Impact Solutions Getting Started Guide■ BMC Impact Solutions Event Management Guide■ BMC Impact Solution Event Adapters User Guide■ BMC Impact Solutions Infrastructure Administration Guide■ BMC Event and Impact Reporting Installation, Configuration, and User Guide■ BMC Impact Solutions Service Impact Management Guide■ BMC Impact Solutions Service Modeling and Publishing Guide■ BMC Portal Installation Guide■ BMC Datastore Installation Guide

Figure 8 implementation workflow for BMC Service Impact Management with the BMC Atrium CMDB


Example architectures

Example architecturesThis section describes real-life customer production environments where BMC Impact Solutions have been successfully deployed. The architectural choices made by each customer were influenced by multiple factors (not all described here) and other approaches may have been valid, but these examples provide valuable information.

EM customer—large public-sector organization

A European-based, public sector customer chose BMC Event Manager to centralize and consolidate event information from approximately 4500 servers monitored using the BMC PATROL product. The servers are distributed across the country, but the operations are centralized. The BMC PATROL infrastructure generates approximately 1,000,000 events per day.

For event integration, all PATROL agents connect to cells using the Mexico integration component, in other words, using direct PATROL agent connections. The customer, working with BMC Professional Services, established that optimal performance of BMC II for PATROL 3 was obtained if each instance of BMC II for PATROL 3 connected to no more than 100 PATROL agents. A total of 50 BMC II for PATROL 3 instances are used in the solution.

Event processing is performed by two tiers of cells:

■ Tier 1 cells collect events from the BMC II for PATROL 3 instances and apply enrichment and filter rules to the events before propagating them to the second tier. There are 10 tier 1 cells in the environment, each configured similarly. The tier 1 cells filter out about 90 percent of the incoming events.

■ Tier 2 event processing is performed by one centralized cell that performs event correlation and de-duplication on events collected from the Tier 1 cells. This cell contains all the event management logic, but no collectors. Correlated events are propagated to a presentation cell that manages display of events to operators. This presentation cell does not contain any rules, it contains only collectors.


EM customer—large public-sector organization

Figure 9 Logical architecture—large public-sector customer

The 12 cells and the 50 BMC II for PATROL 3 instances run on only two Windows servers and each server has 4 CPUs with 4 GB RAM. Each server hosts six cells and approximately 25 BMC II for PATROL 3 instances. Data storage uses SAN technology, which provides significant performance gains in terms of processing speed. The customer estimates that using SAN-based storage for BMC IM speeds up event processing by a factor of 2 to 3.

Summary

■ A two-tiered approach to Event Management is sound in large environments. The first tier cells receive the infrastructure events and do the basic work of event filtering and normalization; the second tier takes care of event correlation, integration with ticketing/notification systems and of the presentation.

■ In high-volume environments, it is best practice to split the processing (event management rules) from the presentation (event collectors). This gives better end user experience and increases the overall performance of the solution

■ Storage Area Network (SAN) technology can be used to solve BMC Impact Manager performance bottlenecks, usually found at disk I/O level.

■ When using BMC II for PATROL 3 (mxcp) to receive events from BMC PATROL agents, limit the number of connected agents to 100 agents per integration instance.


EM and SIM customer—large retail company

EM and SIM customer—large retail company

This international retail company has been using BMC® PATROL® Enterprise Manager (BMC PATROL® EM) for many years as its central operations console to consolidate monitoring information coming mainly from BMC PATROL.

Two years ago, as the need to manage their infrastructure from a service perspective grew, they began implementing BMC SIM for one of their most important business services, the ordering process.

BMC PATROL EM still acts as the central console for event management. Events coming from BMC PATROL and a couple of other smaller event sources are integrated into BMC PATROL EM. The BMC Impact Integration for PATROL Enterprise Manager (BMC II for PATROL EM) is used to forward the events to BMC IM. Events coming from BMC PATROL EM are first processed in one cell before being forwarded to BMC Service Impact Manager. It is common practice (although not technically required) to place a “staging” cell in front of SIM cells to ensure proper normalization and centralization of events before they affect the service model.

Because the service model is large and includes elements (components and relationships) that are repeated many times, a custom utility populates the BMC Atrium CMDB with the model objects. As of November 2006, the model contains approximately 8,500 components, which are published to a single cell.

Operators and service impact managers primarily use BMC Impact Explorer as the main console. BMC Impact Portal is primarily used for authentication and authorization.


EM and SIM customer—large energy company

Figure 10 Logical architecture—large retail company

Table 8 describes the three servers that support their solution. Each server uses local hard drives for storage.


A European customer has a large, distributed IT infrastructure made up of three data centers (separated by hundreds of miles) hosting around 1,000 servers, mainframe environment, and network devices. The servers are monitored by BMC PATROL and BMC IM is used to process a daily total of about 1,800,000 events and apply those to a model of the key revenue-generating services of the company.

Table 8 Example implementation using three servers

Computer Products or components Computer specifications

Server 1 BMC Impact Portal server Sun-Fire-V2402 GB Memory2 x SUNW, UltraSPARC-IIIi, 1002 MHz

Server 2 Oracle database for BMC Impact Portal and BMC Atrium CMDB

Sun-Fire-V44016 GB Memory4 x SUNW, UltraSPARC-IIIi, 1281 MHz

Server 3 Impact Manager instances and BMC II for PATROL EM

ProLiant DL 360 G43 GB Memory2 x Intel XEON CPU, 3400 MHz



There is a dedicated Event Management server in each datacenter that takes care of the collection and processing of the local events. Events are received from

■ BMC PATROL using BMC II for PATROL 7

The BMC II for PATROL 7 integration instances run on the Patrol Console servers and connect about 50 agents per instance.

■ HP OpenView Network Node Manager using the ad-hoc integration product BMC Impact Integration for HP OpenView Network Node Manager (BMC II for NNM)

The BMC II for NNM integration instance is hosted on the HP OpenView Network Node Manager server.

■ MainView/AutoOperator on the mainframe

■ a few network devices using the SNMP adapter

The BMC Patrol agents are not “tuned,” so many events are generated by the PATROL agents. Strict filtering rules discard events based on a “top 10” logic (only events related to the most important parameters are accepted), and “info” events are closed after two minutes. Finally, only events that have an impact on service model components are propagated to the SIM instance at the central location. This requires building service model component aliases at the EM level.

As of November 2006, the service model contains approximately 3,000 components, which are stored in a single BMC Service Impact Manager instance located at the central datacenter.

Operators and service impact managers primarily use the BMC Impact Explorer as their main console. There are about 10 users simultaneously logged in.

For high-availability purposes, a backup SIM instance located in another datacenter also receives and processes the events received by EM. This “failover” mechanism cannot be considered as true high-availability architecture and is not supported as such by BMC Software.

Figure 11 on page 44 summarizes the functional architecture. The solid, red lines present the primary event stream between BEM and SIM cells, and the dashed, purple lines present the secondary event flow.

NOTE This customer currently uses version 4.1 of BMC Impact Solutions. The BMC Atrium CMDB and the BMC Impact Portal are therefore not part of their solution. The solution is nevertheless worth describing due to its distributed nature and the high event volumes.



Figure 11 Logical architecture—large energy company

Each datacenter uses a dedicated server to host the EM and, in two data centers, the SIM instance.

These three Windows 2003 servers have all the same specifications: 4 CPUs with 8 GB RAM, using SCSI RAID 5 local disks.

The customer has noted that the CPU utilization on these servers is very low (< 10%).

Summary

■ distribute the solution to match the topology of your environment. Deploy at least one Impact Manager instance per datacenter.

■ close and discard events as quickly as possible to make room for new ones. The policy at the customer is to discard closed events after 3 hours

■ limit the use of dynamic collectors to increase performance

■ build service model component aliases at the EM level so that only events that actually impact the service model are propagated to SIM


C h a p t e r 2
2 Implementation considerations
This chapter discusses items that you should consider when planning your installation or upgrade of the BMC Impact Solutions components.

It presents the following topics:

Performance and scalability lab results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Number of BMC Impact Managers to use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

When to use multiple BMC Impact Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Using tiers to share the load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Using a “processing” and a “presentation” BMC Impact Manager . . . . . . . . . . . 48

Master or Standard BMC Impact Administration Server . . . . . . . . . . . . . . . . . . . . . . . 49High-availability cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Roles and permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Event groups and image views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Internationalization compatibility for Common Event Model slots . . . . . . . . . . . . . . 51Component installation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Database for the BMC Remedy AR System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51BMC Remedy AR System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53BMC SIM CMDB extensions and BMC Remedy ITSM applications . . . . . . . . . . . 54Database for the BMC Impact Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54BMC Impact Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55BMC Impact Publishing Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55BMC Impact Service Model Editor with a firewall. . . . . . . . . . . . . . . . . . . . . . . . . . 55

Component upgrade considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Database for the BMC Remedy AR System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56BMC Remedy AR System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57BMC Impact Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Database for the BMC Impact Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57BMC Impact Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

BMC Impact Integration for PATROL hardware sizing requirements . . . . . . . . . . . . 58Maximum number of BMC II for PATROL instances connecting to a cell . . . . . . 58Determining when to use multiple BMC II for PATROL adapters or

multiple cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61


Performance and scalability lab results

Performance and scalability lab resultsTest results in the BMC Performance, Scalability, Reliability, and Interoperability labs indicate that

■ it is best to use at least a 2-CPU (or dual-core single CPU) system to host BMC Impact Managers, so that the cell does not encounter performance issues when the StateBuilder runs

■ to prevent disk I/Os causing bottlenecks when event volumes are high, use fast disks or SAN technology

■ a cell’s processing of events is directly impacted by the event database cleanup process and the StateBuilder process

■ the resource utilization of the cell is dependent on the type of adapter supplying the events and the retry and recovery mechanisms used by the adapters; for example, buffering events, attempts to resend events, and so on

■ the cell is able to handle up to 20 BMC Impact Explorer connections; however, BMC recommends no more than 15 connections because of the increase in response time for user interactions

Number of BMC Impact Managers to useThe core real-time product of BMC Impact Solutions, BMC Impact Manager, is designed to work easily in a distribution fashion. Scalability can be achieved by creating additional BMC Impact Managers, with each instance processing only part of the events. Since each instance uses its own Knowledge Base, different processing rules can be applied. This flexibility offers several options which can be combined, especially in high volume environments.

When to use multiple BMC Impact Managers

Multiple BMC Impact Managers do not necessarily imply additional hardware because many BMC Impact Manager instances can be hosted on a single computer; however, you should install no more than five BMC Impact Manager cells on a single computer with 2 CPUs and 2 GB of RAM. More than that might affect performance.

Consider using multiple BMC Impact Managers when

■ both event management and impact management functions must be provided; use one BMC Impact Manager for event management and one for service impact management.


Using tiers to share the load

■ the managed infrastructure is distributed across several locations; install one BMC Impact Manager instance in each remote location

■ the number of events is large, more than 500,000 events per day

■ there are different event sources which require a different set of event management rules

■ the event management operations are divided by teams or geographical locations

■ the number of users of BMC Impact Explorer grows to more than 10 simultaneous users; in which case, consider also separating the processing and the presentation of events into different BMC Impact Managers

■ the size of the service model is more than 20,000 components

Using tiers to share the load

One practical method to share the work load is to split the event management into multiple tiers. Each tier applies specific processing to incoming events before propagating the surviving events to the next tier. A typical two-tier architecture works as described in the following sections.

Tier 1 BMC Impact Managers

Tier 1 BMC Impact Managers receive raw events from the event sources and normalize, filter, and de-duplicate these events. You can further organize these BMC Impact Managers by location or event source.

■ By location: When the infrastructure, and therefore event sources, is distributed across several sites and data centers, BMC recommends that you deploy local BMC Impact Managers in each location so that the local events can be normalized, filtered, and processed before being forwarded to a centralized BMC Impact Manager, which is usually located in the operations center.

■ By event source: In cases where there are multiple event sources and event volume is high, you can deploy dedicated BMC Impact Managers to process the different event streams. This is especially recommended when events arrive with different formats (SNMP traps, in particular) and need to be normalized before they can be properly processed.


Using a “processing” and a “presentation” BMC Impact Manager

Tier 2 BMC Impact Managers

Tier 2 BMC Impact Managers receive events from the Tier 1 BMC Impact Managers and process them further (correlation, abstraction, and so on) and integrate with other applications, such as service impact management, notification, and service desk. These BMC Impact Managers can also present events to operators. See “Using a “processing” and a “presentation” BMC Impact Manager”.

Another factor to consider is that the BMC Impact Manager supports the distribution of a service model across multiple BMC Impact Managers, as long as the number of relationships that cross BMC Impact Managers is minimal.

Using a “processing” and a “presentation” BMC Impact Manager

Both rules (that process events) and collectors (that sort events for easier management by operators) can negatively impact the performance of the BMC Impact Manager and the BMC Impact Explorer. In enterprises with a high volume of events, consider using two BMC Impact Managers, one for processing events and the second for presenting events to operators.

The first BMC Impact Manager handles event management and has a minimum Knowledge Base (KB), which contains rules and policies, but no collectors (the kb/collectors directory is empty). The KB contains a propagation rule that ensures that all events are propagated to the second BMC Impact Manager.

The second BMC Impact Manager has all the collector definitions, but no event management rules (the kb/rules directory is empty). Users of BMC Impact Explorer connect only to this second BMC Impact Manager.

Normally, built-in mechanisms take care of synchronizing events across two BMC Impact Managers, but if you set up separate processing and presentation BMC Impact Managers, it may be necessary to extend the number of slots which are synchronized. The configuration file mcell.propagate controls which slot changes are synchronized (and in which direction) after event propagation. For more information about mcell.propagate, see the BMC Impact Solutions Infrastructure Administration Guide.


Master or Standard BMC Impact Administration Server

Master or Standard BMC Impact Administration Server

The BMC Impact Administration Server (IAS) handles logon and administrative functions for BMC IX.

You can select a Master or Standard BMC Impact Administration Server (IAS) at installation. A Master IAS enables the Infrastructure Management feature in BMC Impact Explorer and installs an accompanying administration cell on the same host as the Master IAS. (The administration cell is designated by default as Admin in the BMC Impact Explorer GUI.)

A Standard IAS provides all the features of the Master IAS, except support for Infrastructure Management and the administration cell. You must install a Master IAS before you install a standard IAS.

You can also specify the IAS as a standalone server, meaning you install only one IAS, or, to allow for failover capability, you can install one IAS on one computer as the Primary server and then install a second IAS on another computer as the Secondary server in a high-availability pair. The primary and secondary servers should be installed on the same type of platform and must have the same name.

For more information about configuring the IAS, see the BMC Impact Solutions Infrastructure Administration Guide.

High-availability cellsInstalling cells for high availability requires two servers, one to function as the primary cell server and a second to function as secondary cell server in a failover situation. These two servers must run on separate logical operating system images of the same type. Additionally, only one of the two servers should be active at any time.

NOTE To switch from a Master IAS to a Standard IAS or vice versa after installation, you must uninstall the existing server and then install the new server.


Roles and permissions

To get the same behavior for the primary and for the secondary cells, both should be installed and configured similarly, and the Knowledge Bases for both servers must be identical. Configuration parameters also should be set to the same values for both servers, except for the CellDuplicateMode parameter that indicates whether the server is a primary or a secondary server. For details about the high-availability cell configuration parameters, see the BMC Impact Solutions Infrastructure Administration Guide.

Roles and permissionsThe IAS determines several properties of BMC Impact Explorer, including roles and permissions. The edit permissions within BMC IX depend on the user role. The following group roles have full write permission to the components and features of the Infrastructure Management subtab in BMC Impact Explorer:

■ Service Administrators■ Full Access

Only members of either group can view the Infrastructure Management subtab.

For more information about defining group roles, see the BMC Impact Solutions Infrastructure Administration Guide.

Event groups and image viewsPlanning is essential to creating event groups and image views that logically and efficiently depict the IT assets of your enterprise. Before creating event groups and image views, consider these guidelines:

■ Event groups and image views organize and represent the contents of collector. Consequently, you should carefully plan and create the collectors for your enterprise. Event groups and image views can provide no more information than that gathered by collectors. (Collectors must be created before the event groups that use them. For more information about collectors, see the BMC Impact Solutions Knowledge Base Development Reference Guide.)

■ Creating event groups by using static collectors allows you to create the event groups before you run the event management system in a test or production environment. However, this practice can require a significant amount of manual work depending on the number of event groups you create.


Internationalization compatibility for Common Event Model slots

■ Creating event groups by using dynamic collectors requires less manual work than using static collectors, but the event groups do not exist until cells receive events to populate the dynamic collectors.

Internationalization compatibility for Common Event Model slots

The CEM 1.1.00 classes are compatible with internationalization requirements and provide language support. You should use Unicode encoding for all text.

Component installation considerationsReview the following installation considerations when you are installing the BMC Impact Solutions components the first time.

Database for the BMC Remedy AR System

If you use an Oracle database for the BMC Remedy AR System, you can use one of the following options:

■ Install the BMC Datastore from the BMC Portal Infrastructure and Datastore installation DVD for Windows. This DVD is located in the BMC Impact Portal kit. For more information, see the BMC Datastore Installation Guide. You can use the same BMC Datastore for both BMC Remedy AR System and the BMC Impact Portal.

■ Download a licensed Oracle database (Standard Edition) from the Oracle website. For information about installing Oracle, see the Oracle website.

■ Install the Oracle client to use a remote Oracle database installation.


BMC Remedy AR System


This version of BMC Impact Solutions supports versions 7.1 patch 002 and version 7.5 of the BMC Remedy AR System product. For instructions about installing the BMC Remedy AR System, see either the BMC Remedy Action Request System 7.1: Installing guide or the BMC Remedy Action Request System 7.5 Installation Guide in the respective BMC Atrium Shared Components kit.

The BMC Remedy AR System is a multi-threaded application, so performance can be enhanced by increasing the number of threads (list and fast) using the BMC Remedy Administrator tool. The recommended number of threads is 2 for each processor. More memory will be utilized for the additional threads. Check the BMC Remedy AR System product documentation for more details.

ITSM applications and SIM

If you are installing ITSM applications and SIM, you must increase the default tablespace values for ARSYSTEM and ARTMPSP. A very large asset base might require an ARSYSTEM tablespace greater than 1 GB. BMC Software recommends that you assign the ARTMPSP tablespace approximately a third of the size of the ARSYSTEM tablespace.

License requirement information

BMC Remedy AR System uses a customer-driven license enforcement system. This licensing system differs from the one used in earlier versions of the product. To review the licensing procedures for your version of BMC Remedy AR System, see the documentation that accompanied your BMC Atrium Shared Components kit or go to http://www.bmc.com/support_home to view BMC Remedy AR System documentation online.

NOTE The BMC Remedy AR System that is included as part of the BMC Service Impact Manager package is licensed exclusively to support BMC Atrium CMDB and its included application components. If you intend to install other BMC Remedy ITSM applications, custom-developed AR applications, or both, on this BMC Remedy AR System server instance, you must purchase the appropriate BMC Remedy AR System server and user licenses, ITSM application licenses, or both. This restriction does not preclude the integration of other BMC products or integration of third-party products with the BMC Atrium CMDB under the BMC Service Impact Manager package license.


http://supportweb.remedy.com

BMC Atrium CMDB

BMC Atrium CMDB

BMC Atrium CMDB is only required for enterprises that desire service impact management. It is not needed for event management only installation scenarios. The BMC Atrium CMDB database is accessed only during definition and publishing of the service model. If you are using ITSM applications and BMC Atrium Discovery, BMC recommends that the BMC Atrium CMDB database be on a separate, dedicated computer.

If you have enough resources, you can create multiple instances of Oracle on the same computer and use one for BMC Atrium CMDB and the second for BMC Portal. On a computer with multiple processors, you can install BMC Impact Portal and the BMC Datastore database on the same computer as the BMC Atrium CMDB database.

It is possible to use the same instance of Oracle for both BMC Atrium CMDB and BMC Portal for small environments without ITSM applications and where system resources prevent running multiple Oracle instances on the same computer, but this is not a recommended configuration.

Version requirement

BMC Impact Solutions supports BMC Atrium CMDB version 2.1 patch 003 and BMC Atrium CMDB 7.5. If you already have BMC Atrium CMDB installed, you must upgrade it to the version 2.1 patch 003 or version 7.5 to use it with your new BMC Impact Solutions product installation.

For instructions about installing the BMC Atrium CMDB, see the BMC Atrium CMDB 2.1 Installation and Configuration Guide or the BMC Atrium Core 7.5 Installation Guide in the respective BMC Atrium Shared Components kit.

License requirement information

If not already present, the BMC Atrium CMDB version 2.1 and version 7.5 installers generate their own license for use with the BMC Remedy AR System server. For information about licenses for earlier versions of the BMC Atrium CMDB, see the documentation that accompanied your BMC Atrium Shared Components kit or go to http://www.bmc.com/support_home to view BMC Atrium CMDB documentation online.


http://supportweb.remedy.com

BMC SIM CMDB extensions and BMC Remedy ITSM applications

BMC SIM CMDB extensions and BMC Remedy ITSM applications

In the Atrium deployment scenario, you install the BMC SIM CMDB extensions after you install the BMC Atrium CMDB. There are two separate installation programs for the BMC SIM CMDB extensions, one that installs the extensions that support BMC Atrium CMDB 2.1 and one that installs the extensions that support BMC Atrium CMDB 7.5. For details, see the BMC Impact Solutions Installation Guide.

If the BMC Remedy IT Service Management (BMC Remedy ITSM) product or any of its component products are installed after the BMC SIM CMDB extensions have been installed, you must apply a patch to the BMC Atrium CMDB by using the cmdbdriver script provided in the SIM_CMDB_Extension\patches directory on the BMC Event and Impact Management Base DVD. For directions for applying the patch, see the readme.txt file included with the script.

Database for the BMC Impact Portal

For the BMC Impact Portal, you can use one of the following options for the Oracle database:

■ Use the same Oracle database instance (either the BMC Datastore or a licensed Oracle database) that you installed for BMC Remedy AR System.

■ Create another instance of the Oracle database by using the Oracle database that you installed for the BMC Remedy AR System.

■ Install another copy of the Oracle database or the BMC Datastore on a different computer and use it solely for the BMC Impact Portal.

For installation instructions for the BMC Datastore, see the BMC Datastore Installation Guide.

NOTE Only one Oracle database installation can exist on a computer.

Many BMC Impact Portals can connect to a single Oracle database, but in such a situation, you must create a different Oracle user for each BMC Impact Portal that you install.


BMC Impact Portal

BMC Impact Portal

When you install the BMC Impact Portal from the BMC Impact Portal kit, you automatically install the BMC Impact Service Model Editor and a web-accessible version of the BMC Impact Explorer.

For installation instructions for the BMC Impact Portal, see the BMC Portal Installation Guide.

For optimization guidelines postinstallation, see the BMC Performance Manager Portal Performance and Scalability Guidelines. Since the BMC Performance Manager Portal product leverages the same base architecture as the BMC Impact Portal, much of the document remains valid for BMC Impact Portal.

BMC Impact Publishing Server

The BMC Impact Publishing Server is used to publish a new service model or changes to an existing service model. During the publishing process, the server typically uses less than 15% of CPU, but its virtual memory requirements may reach 1 GB. Consider these memory requirements when sizing the computer on which you will install and run the BMC Impact Publishing Server.

The default configuration parameter settings are estimated best practice.

BMC Impact Publishing Server works with the BMC Impact Portal but is installed separately. Advice for high volume sites without multi-processor computers is to install BMC Impact Portal and the BMC Atrium CMDB on different computers; however, best practice is to have the BMC Impact Publishing Server run on the same computer as the BMC Atrium CMDB (or in close proximity). This is because of the complexity of the data exchange protocol between these two components.

BMC Impact Service Model Editor with a firewall

If your environment contains a firewall between the BMC Impact Service Model Editor client and BMC Impact Service Model Editor server (with http port open), the BMC Impact Service Model Editor Client will fail unless ports 9378 and 9386 are opened in the firewall.


Component upgrade considerations

Component upgrade considerationsReview the following installation considerations when you are upgrading the BMC Impact Solutions components from a previous version.

Database for the BMC Remedy AR System

If you are using the BMC Datastore for the BMC Remedy AR System datastore, upgrade the BMC Datastore before you upgrade BMC Impact Solutions. For upgrade instructions, see the BMC Datastore Installation Guide.

Ensure that the following services are stopped before you upgrade the BMC Datastore; otherwise, the upgrade might fail.

■ AR System ■ BMC Impact Publishing Server■ BMC Portal■ BMC Portal Web Server■ iiws ■ mcell_cellName


BMC Impact Solutions 7.3 supports version 7.1 patch 002 and version 7.5 of the BMC Remedy AR System product. These versions do not support Microsoft Windows 2000, so you must upgrade the operating system to Windows 2003 before upgrading BMC Remedy AR System to one of the supported versions.

For upgrade instructions, see the BMC Remedy Action Request System 7.1: Installing guide or the BMC Remedy Action Request System 7.5 Installation Guide in the respective BMC Atrium Shared Components kit.

NOTE If you installed the Oracle 10g client, uninstall it before you upgrade the datastore.


BMC Atrium CMDB

BMC Atrium CMDB

You can upgrade BMC Atrium CMDB versions 2.0.01 patch 006, version 2.1, or version 2.1 patch 003 to version 7.5. For BMC Atrium CMDB upgrade instructions, see the BMC Atrium Core 7.5 Installation Guide in BMC Atrium Shared Components kit.

You can also upgrade BMC Atrium CMDB version 2.0.01 patch 006 to version 2.1 patch 003, which you can also use with BMC Impact Solutions 7.3.00. For upgrade instructions, see the BMC Atrium CMDB 2.1 Installation and Configuration Guide.

Upgrading from versions earlier than 2.0.01 patch 006 is not supported. You must upgrade BMC Atrium CMDB to at least version 2.0.01 patch 006 before upgrading to version 7.5. Before upgrading to BMC Atrium CMDB version 7.5, you must apply the AR Server license and the CMDB license.

BMC Atrium CMDB 7.5 does not support Microsoft Windows 2000, so you must upgrade the operating system to Windows 2003 before upgrading the application.

BMC Impact Manager

In an Atrium deployment scenario, if you upgrade a BMC Impact Manager cell from version 7.0.02 to version 7.3.00, you must also upgrade the BMC Atrium CMDB and the BMC Impact Portal. For details about versions that are supported for the BMC Atrium CMDB upgrade, see “BMC Atrium CMDB.” For details about version that are supported for the BMC Impact Portal upgrade, see the BMC Portal Installation Guide. For upgrade instructions for the BMC Impact Manager, see the BMC Impact Solutions Installation Guide.

Database for the BMC Impact Portal

If you are not using the BMC Remedy AR System or the BMC Atrium CMDB database for the BMC Portal database, upgrade the BMC Portal database now. For upgrade instructions, see the BMC Datastore Installation Guide in the BMC Impact Portal kit.

BMC Impact Portal

For information about upgrading the BMC Impact Portal, see the BMC Portal Installation Guide.


BMC Impact Integration for PATROL hardware sizing requirements

If you plan to perform the BMC Impact Portal upgrade with BMC Datastore version 2.0 (as shipped with SIM 5.1.01), you must first upgrade the datastore to version 2.4 and then upgrade it to version 2.6.50. A direct upgrade from BMC Datastore 2.0 to 2.6.50 is not supported.

BMC Impact Integration for PATROL hardware sizing requirements

These sections describe performance tuning for BMC Impact Integration for PATROL (BMC II for PATROL).

■ In environments with 100 agents or less, you can host BMC II for PATROL on the same computer with PATROL Console Server, BMC Impact Manager, or both.

■ A single computer can host RTserver, PATROL Console Server (dedicated to BMC II for PATROL), and BMC II for PATROL for up to 500 agents.

■ If your environment exceeds these thresholds, host BMC II for PATROL, PATROL Console Server, or BMC Impact Manager on separate computers, primarily to support a higher number of PATROL agents and event rates. In this scenario, a computer with a fast CPU and large memory resources (for example, a 2-CPU computer with 4 GB of memory) is recommended to allow the BMC II for PATROL server to maintain a high throughput under peak conditions. Even so, a dedicated BMC II for PATROL computer typically has spare capacity that can be used by other PATROL infrastructure components, such as a PATROL for Event Management—Notification Server or an Aggregator for PATROL Reporting. In fact there are some scenarios where multiple BMC II for PATROL can be hosted on the same computer as PATROL or BMC Impact Manager servers to reduce the hardware costs associated with hosting the PATROL and Impact Solutions infrastructure.

Maximum number of BMC II for PATROL instances connecting to a cell

The maximum number of BMC II for PATROL instances that can be connected to a single cell is dependent on the number of events being sent from each BMC II for PATROL and the number of agents connected to each BMC II for PATROL instance.

BMC has observed that a cell can receive and process around 20-30 average PATROL events per second from one or more BMC II for PATROL instances.


Determining when to use multiple BMC II for PATROL adapters or multiple cells


The key factors in deciding when to use multiple BMC II for PATROL adapters or multiple cells are

■ the number of agents being connected

■ the event rate from agents

A single BMC II for PATROL can handle 500 PATROL agents (the actual figure may be higher). You can configure additional BMC II for PATROL adapters when a single BMC II for PATROL is not sufficient to handle the workload of the total number of PATROL agents.

In addition to creating multiple BMC II for PATROL to handle environments with more than 500 agents, an additional BMC II for PATROL is warranted any time the requirements call for more than an average event throughput of 20 events per second. In this type of scenario, it is more efficient to have the PATROL Console Server connect to multiple BMC II for PATROL adapters and to have the adapters connect to different cells. This is preferable to having a larger number of agents trying to maintain connections to a single BMC II for PATROL under peak workload situations.


A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Index

AAtrium deployment option 16

Bbasic deployment option 14BMC Atrium CMDB

installation considerations 53upgrade considerations 57

BMC Impact Integration for PATROL, hardware sizing requirements 58

BMC Impact Managerdetermining number to use 46using a processing and presentation cell 48using tiers for load sharing 47

BMC Impact Portaldatabase installation considerations 54database upgrade considerations 57installation considerations 55upgrade considerations 57

BMC Impact Publishing Server, installation considerations 55

BMC Impact Service Model Editor, using with a firewall 55

BMC Remedy AR Systemdatabase upgrade considerations 56installation considerations 51, 52upgrade considerations 56

BMC SIM CMDB extensions, installation considerations 54BMC Software, contacting 2

Ccell

determining the number to use 46installing for high availability 49using a processing and presentation 48using tiers for load sharing 47

customer support 2

Ddeployment options

Atrium 16basic 14overview 13standard 15

Eevent management

implementation workflow 36installation scenario 17recommended architecture for large environment 28recommended architecture for large event and service

impact management environment 33recommended architecture for medium event and

service impact management environment 31recommended architecture for small event and service

impact management environment 30recommended architectures for small environment 26

Hhardware sizing requirements, for BMC Impact

Integration for PATROL 58high-availability cells

implementation considerations 49when considering installation scenarios 25

IImpact Administration Server

roles and permissions 50using a Master or Standard type 49

implementation considerationsdetermining the type of IAS to use 49guidelines for creating event groups and image views

50high-availability cells 49internationalization for Common Event Model slots

51number of BMC Impact Managers to use 46

Index 61

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

performance and scalability lab results 46roles and permissions with access to the IAS 50

implementation workflowfor event management 36for service impact management with a BMC Atrium

CMDB 37installation considerations

BMC Atrium CMDB 53BMC Impact Portal 55BMC Impact Publishing Server 55BMC Remedy AR System 52BMC SIM CMDB extensions 54database for BMC Remedy AR System 51database for the BMC Impact Portal 54using BMC Impact Service Model Editor with a

firewall 55installation scenarios

event management 17high-availability cells 25overview 16recommended architectures 26service impact management for a small service model

19service impact management for medium to large

service model 22service impact management for very large service

model 24service impact management overview 18

Pperformance testing results 46product overview

architecture 12deployment options 13list of products and components 12

product support 2

Rrecommended architectures

large event and service impact management environment 33

large event management environment 28medium event and service impact management

environment 31overview 26small event and service impact management

environment 30small event management environment 26

requirements, hardware sizing for BMC Impact Integration for PATROL 58

62 BMC Impact Solutions Planning and Implementatio

Sscalability testing results 46service impact management

implementation workflow 37installation scenario for medium to large service

model 22installation scenario for small service model 19installation scenarios for very large service model 24installation scenarios overview 18recommended architecture for large environment 33recommended architecture for medium environment

31recommended architecture for small environment 30

standard deployment option 15support, customer 2

Ttechnical support 2

Uupgrade considerations

BMC Atrium CMDB 57BMC Impact Portal 57BMC Impact Portal database 57BMC Remedy AR System 56BMC Remedy AR System database 56

n Guide

*97721**97721**97721**97721*

*97721*

bmc impact solutions planning and implementation guide

Documents