hp operations manager i...manager. it is responsible for gathering information about infrastructure...

HP Operations Manager i

for the Windows® operating system

Software Version: 8.10

Installation and Deployment Guide

Document Release Date: 18 August 2009Software Release Date: June 2009

Legal Notices

Warranty

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notices

© Copyright 2008-2009 Hewlett-Packard Development Company, L.P.

Trademark Notices

Microsoft® and Windows® and Microsoft Vista® are U.S. registered trademarks of Microsoft Corporation.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

Acknowledgements

This product includes ANTLR.

This product includes software developed by Andy Clark.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi (http://relaxngcc.sf.net/).

This product includes cryptographic software written by Eric Young ([email protected]).

This product includes software developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/).

This product includes software developed by the JDOM Project (http://www.jdom.org/).

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http:// www.openssl.org/).

This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/).

This product includes code licensed from RSA Data Security.

This product includes software written by Tim Hudson ([email protected]).

2

http://www.jdom.org/

http://relaxngcc.sf.net/)

http://relaxngcc.sf.net/)

http://www.opensymphony.com/

http://www.apache.org/

http://www.extreme.indiana.edu/

Documentation Updates

The title page of this document contains the following identifying information:

• Software Version number, which indicates the software version.

• Document Release Date, which changes each time the document is updated.

• Software Release Date, which indicates the release date of this version of the software.

To check for recent updates or to verify that you are using the most recent edition of a document, go to:

http://h20230.www2.hp.com/selfsolve/manuals

This site requires that you register for an HP Passport and sign in. To register for an HP Passport ID, go to:

http://h20229.www2.hp.com/passport-registration.html

Or click the New users - please register link on the HP Passport login page.

You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details.

3

Support

Visit the HP Software Support Online web site at:

www.hp.com/go/hpsoftwaresupport

This web site provides contact information and details about the products, services, and support that HP Software offers.

HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support web site to:

• Search for knowledge documents of interest

• Submit and track support cases and enhancement requests

• Download software patches

• Manage support contracts

• Look up HP support contacts

• Review information about available services

• Enter into discussions with other software customers

• Research and register for software training

Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to:

http://h20229.www2.hp.com/passport-registration.html

To find more information about access levels, go to:

http://h20230.www2.hp.com/new_access_levels.jsp

4

Contents

1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9HP Operations Manager i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

HP Business Service Management Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10HP Operations Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 HP OMi Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Deployment Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13One-Machine Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Two-Machine Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Multi-Machine Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17HP Business Service Management Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Supported BSM Platform Database Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Supported BSM Platform Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Lightweight Single Sign-On Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Default Profile Database for Topology Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

HP Operations Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19HP Operations Smart Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19HP SiteScope (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

HP OMi GUI Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4 Installing HP OMi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5 Configuring HP OMi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configure HP OMi on the Data Processing Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Configure HP OMi Using an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Configure HP OMi Using a Microsoft SQL Server Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Configure HP OMi on the Gateway Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

6 Validating the HP OMi Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Verify the HP OMi Service and Process Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Verify the HP OMi Menu Entries in the BSM Platform Management Console . . . . . . . . . . . . . . . . . . . . . 39

5

7 Managing Content Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Import Content Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

8 Connecting HP OMi to HPOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

HPOM in High Availability Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Clustering and Server Pooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Server Log Shipping and Backup Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

HP OMi Systems as Nodes to HPOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Adding Nodes to HPOM for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Adding Nodes to HPOM for UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Establishing a Trust Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Requesting Certificates for HP OMi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Granting Certificates on the HPOM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Granting Certificates Using the HPOM for Windows Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Granting Certificates Using a Command Prompt or a Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Issuing Certificates for the Load Balancer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Starting the BSM Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Populating the UCMDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Configuring Message Forwarding Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Setting Up a Policy On HPOM for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Creating a New Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Adapting an Active Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Setting Up a Policy On HPOM for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Creating a New Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Adapting an Active Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

9 Validating Event Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Verify Message Forwarding from HPOM to HP OMi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Synchronize HP OMi Events with HPOM Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

10 HP OMi Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

HP OMi Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Types of Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Product License Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Installing or Updating HP OMi Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Viewing License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

11 Disabling or Uninstalling HP OMi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Disabling HP OMi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Enabling HP OMi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Uninstalling HP OMi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Uninstalling the BSM Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Post-Uninstallation Cleanup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Shared Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Cleaning Up HPOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

6

A Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Installation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Files are Missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Files are Corrupt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78The HP OMi Database is Corrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79The BSM Platform Database is Corrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Event Synchronization Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Message Forwarding from HPOM to HP OMi does not Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Verify the Black Box Communication between HP OMi and HPOM . . . . . . . . . . . . . . . . . . . . . . . . 80Empty the Black Box Communication Store and Forward Buffer on HPOM . . . . . . . . . . . . . . . . . 81Verify the HP OMi Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Verify the Sonic Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Verify the HP OMi Database Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Message Forwarding Times Out on HPOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Synchronizing HP OMi Events with HPOM Messages Does Not Work . . . . . . . . . . . . . . . . . . . . . . . . 85Verify the Event Synchronization Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Verify the BSM Platform Hostname. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Verify the Black Box Communication Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Topology Synchronization Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Web Service Fatal Error Message: Unauthorized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Web Service Fatal Error Message: Connection Refused . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Web Service Fatal Error Message: Not Found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88HTTPS Fatal Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

HPOM for Windows Server as Peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88HPOM for UNIX Server as Peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Health Perspective Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

B HP OMi Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Installation Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Topology Synchronization Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

C Starting and Stopping the BSM Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Starting the BSM Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Stopping the BSM Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

D Topology Synchronization Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

How to Use the Topology Synchronization Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Synchronizing Smart Plug-in Service Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

7

1 Getting Started

This chapter provides you with an overview of HP Operations Manager i, HP Business Service Management (BSM), and HP Operations Manager. You require BSM and HP Operations Manager before installing HP OMi.

The chapter also summarizes the HP OMi high-level installation steps that you perform while installing HP OMi.

Overview

This section provides you with an overview of HP Operations Manager i, HP Business Service Management (BSM), and HP Operations Manager that HP Operations Manager i interacts with.

HP Operations Manager i

HP Operations Manager i (referred to in this guide as HP OMi) is an event and performance manager. It is responsible for gathering information about infrastructure health, systems, and applications to help identify and resolve specific operations problems.

For a detailed description of HP OMi, see the HP Operations Manager i Concepts Guide available from the HP Software Product Manuals web site.

HP OMi helps you achieve the following:

• Create a superior view of infrastructure health across systems and networks.

• Consolidate events into one central console and correlate the IT infrastructure events and end user management events.

• Automatically determine with topology-based event correlation the root cause and event relationship.

• Effectively make use of the advanced service health for the IT infrastructure.

To achieve this, HP OMi requires the HP Business Service Management (BSM) platform and HP Operations Manager.

9

HP Business Service Management Platform

The HP Business Service Management (BSM) platform is the foundation on which you install HP OMi. You install the BSM platform by installing HP Business Availability Center (BAC), and enabling the BSM platform with a valid HP OMi license.

For the purposes of the HP OMi installation, it is important to understand the following two BSM platform components:

• Gateway Server

This component is responsible for running HP Business Service Management applications, producing reports, operating the administration console, receiving data samples from the data collectors, and distributing this data to the relevant HP Business Service Management components.

• Data Processing Server

This component is responsible for aggregating data, HP OMi event processing, running the Business Logic Engine, and controlling the CMDB service.

These two components are typically installed on separate systems, but may be installed on one for testing purposes.

For a detailed description of HP Business Availability Center (BAC), see the HP Business Availability Center Deployment Guide available from the HP Software Product Manuals web site.

HP Operations Manager

HP Operations Manager (referred to in this guide as HPOM) monitors the status and health of systems and applications. You require HPOM to receive messages about important events that occur in your managed environment. These messages are forwarded to HP OMi where they are evaluated.

Using HP Operations Manager Smart Plug-ins (SPIs), you can manage different applications (for example, Microsoft Exchange Server or the Oracle Application Server) in HPOM and monitor the availability, use, and performance of these applications running on HPOM as managed nodes. These applications are specially adapted to work with HP OMi. Other HPOM SPI integrations such as HP SiteScope and End User Management (EUM) also work with HP OMi.

For a detailed description of HP Operations Manager and the Smart Plug-ins, see the corresponding documentation available from the HP Software Product Manuals web site.

Documentation

This section lists the main documents that pertain to the HP Software or components used in conjunction with the HP OMi installation.

• HP Business Availability Center Deployment Guide

• HP Business Availability Center Platform Administration

• HP Operations Manager for Windows Installation Guide

• HP Operations Manager for UNIX Installation Guide

10 Chapter 1

Installation Summary

This section provides you with a summary of the HP OMi installation procedure. Use this summary as a checklist to identify and complete the HP OMi installation.

Determine which deployment scenario best suits your business needs and architecture. See HP OMi Deployment on page 13.

Check Prerequisites. See Hardware and Software Requirements on page 17.

Prepare the BSM platform by installing HP Business Availability Center (BAC) according to instructions in that product’s installation guide.

Install HPOM according to instructions in that product’s installation guide.

Install HP OMi on one or more BSM platform systems as required by the deployment scenario you have selected. See Installing HP OMi on page 23.

Configure HP OMi. See Configuring HP OMi on page 29.

Validate the HP OMi installation and configuration. See Validating the HP OMi Installation and Configuration on page 39.

Manage Content Packs. See Managing Content Packs on page 41.

Connect HP OMi to HPOM. See Connecting HP OMi to HPOM on page 43.

Validate the event synchronization. See Validating Event Synchronization on page 63.

Obtain, install, and update the HP OMi license. See HP OMi Licensing on page 65.

Getting Started 11

12 Chapter 1

2 HP OMi Deployment

This chapter describes three possible HP OMi deployment scenarios to assist you in determining which type of deployment best suits your business needs and architecture.

Deployment Planning

You can deploy HP OMi on the BSM platform in a number of different configurations according to the size of your system and according to your load balancing and high availability needs.

When determining which type of deployment to use in your enterprise network, consider the following examples:

• Scenario 1: One-Machine Deployment

This type of deployment is supported only for testing purposes. In this type of deployment, you deploy HP OMi on a single dedicated BSM platform system as shown in One-Machine Deployment on page 14.

• Scenario 2: Two-Machine Deployment

This is the standard deployment type that allows you to deploy HP OMi on two dedicated BSM platform systems as shown in Two-Machine Deployment on page 15.

• Scenario 3: Multi-Machine Deployment

You can deploy HP OMi on various dedicated BSM platform systems. In this way, you can benefit from the high availability and load balancing functionality to ensure service continuity and availability. See Multi-Machine Deployment on page 16.

For more information about deployment, see “Deployment Configuration” in the HP Business Availability Center Deployment Guide.

This type of deployment is not scalable and has no load balancing or high availability options.

It is recommended that server machines be dedicated to HP OMi. You should not run the HPOM server on the same machine hosting HP OMi.

Although database servers can run locally on the same machine hosting HP OMi, it is recommended to run them remotely on separate dedicated machines.

13

One-Machine Deployment

This deployment scenario is supported only for testing purposes. In this type of deployment, you install and deploy HP OMi on the same dedicated system hosting both the Gateway and the Data Processing Server.

The following Figure 1 illustrates the one-machine deployment scenario:

Figure 1 One-Machine Deployment

14 Chapter 2

Two-Machine Deployment

In this deployment scenario, you install and deploy HP OMi on two dedicated BSM platform systems, one hosting the Data Processing Server and the other the Gateway Server.

The following Figure 2 illustrates the two-machine deployment scenario:

Figure 2 Two-Machine Deployment

HP OMi Deployment 15

Multi-Machine Deployment

In this deployment scenario, you install and deploy HP OMi on multiple server machines in order to benefit from the various high availability and load balancing options.

With these options that combine multiple servers, external load balancing and failover procedures, you can configure your system to ensure service continuity, availability, and reliability despite unexpected incidents of downtime, outage, or heavy traffic.

For details and instructions about how to implement load balancing and high availability, see “High Availability for HP Business Availability Center” in the HP Business Availability Center Deployment Guide.

Figure 3 on page 16 illustrates the multi-machine deployment scenario with high availability and load balancing features:

Figure 3 Multi-Machine Deployment

16 Chapter 2

3 Hardware and Software Requirements

This chapter describes the hardware and software requirements for the HP OMi installation.

Hardware Requirements

HP OMi is installed on systems where you have installed the BSM platform. HP OMi supports Windows systems which meet the requirements in the HP Business Availability Center Deployment Guide. No additional hardware is required.

You can find the complete information about the hardware requirements in the chapter “Reviewing System Requirements” of the HP Business Availability Center Deployment Guide.

Disk Space

HP OMi requires the following free disk space for installation:

• For single-machine deployment: 350 MB

• For multiple-machine deployment:

— Gateway Server: 330 MB

— Data Processing Server: 150 MB

• Database (without any content): 750 MB

Software Requirements

Before you install HP OMi, make sure you have installed and configured the BSM platform and HP Operations Manager.

HP Business Service Management Platform

Install and configure the BSM platform by installing HP Business Availability Center (BAC) with the following properties according to the HP Business Availability Center Deployment Guide.

Version 8.00 + 8.02 Service Pack (or higher Service Packs) running on one of the following supported operating systems:

• 32-bit: Microsoft Windows 2003 Enterprise Edition R2, SP2.

• 64-bit: Microsoft Windows 2003 Enterprise Edition R2, SP2.

17

Supported BSM Platform Database Servers

HP OMi connects to the database server used by the BSM platform. HP OMi supports all the database servers that HP Business Availability Center (BAC) supports except for Oracle 9 and Microsoft SQL Server 2000.

Supported BSM Platform Web Servers

HP OMi works with all the web servers that HP Business Availability Center (BAC) supports.

Lightweight Single Sign-On Authentication

HP OMi requires Lightweight Single Sign-On (LWSSO) as an authentication type which is the default authentication strategy for HP Business Availability Center (BAC).

LWSSO is embedded in HP Business Availability Center (BAC) and does not require an external machine for authentication.

Before you install HP OMi, ensure that the authentication mode is set to “Lightweight” in the BSM platform management console under the following:

Admin → Platform → Setup and Maintenance → Infrastructure Settings Manager → Foundations → Single Sign-On

For details and instructions, see the HP Business Availability Center Platform Administration guide. See also the Task Assistant of the BSM platform management console.

Default Profile Database for Topology Views

The default profile database stores raw and aggregated measurement data obtained from the HP Business Availability Center data collectors. If necessary, you can store profile data in multiple databases but only one default profile database is required.

Viewing the status in the Health Perspective's Topology Views and the report “Key Performance Indicators (KPIs) Over Time” requires that you specify this default profile database.

Make sure you specify the default profile database for all the BSM platform server machines with an HP OMi instance. You do this in the BSM platform management console under the following:

Admin → Platform → Setup and Maintenance → Manage Profile Databases

High Availability

HP OMi supports all the high availability features that HP Business Availability Center (BAC) supports. For details, see the HP Business Availability Center Deployment Guide.

18 Chapter 3

HP Operations Manager

Install and configure one of the following HP Operations Manager products on a dedicated machine according to the product’s installation guide.

• HPOM for UNIX version 9.00

• HPOM for Windows version 8.10 with the following patches

— Server patch OMW_00029 (or higher)

— Agent patch OMW_00006 - 8.53 (or higher)

— Accessory patch OMW_00032 (or higher)

Check for updates and patches at http://support.openview.hp.com/selfsolve/patches.

HP Operations Smart Plug-ins

Smart Plug-ins (SPIs) are collections of configuration information for HPOM. SPIs make it easy to monitor specific databases, applications, or operating systems.

HP OMi is able to automatically work with the information provided by the HPOM SPIs along with the patches listed below. The patches are available only on HPOM for Windows 8.10.

Install the following SPIs and any specified or superceding patch if you want to use the associated, pre-configured content packs and enable HP OMi to process events based on those contents. This greatly reduces configuration effort and you do not have to implement your own mapping rules for Topology Synchronization. For example, If you want to manage WebSphere, you need the WebSphere Application Server SPI version 6.10 with patch OMW_00037. You must also import the WebSphere content pack (HPOprWbs) into HP OMi. For details, see Import Content Packs on page 41.

Check http://support.openview.hp.com/selfsolve/patches for the most current versions of patches.

• Oracle Application Server SPI version 11.50 with patch OMW_00035

• Microsoft SQL Server SPI version 11.50 with patch OMW_00036

• Microsoft Active Directory SPI version 06.10 with patch OMW_00045

• Microsoft Exchange Server SPI version 12.10 with patch OMW_00046

• WebSphere Application Server SPI version 6.10 with patch OMW_00037

• WebLogic SPI 6.10 with patch OMW_00038

• Virtual Infrastructure SPI version 1.00 with hotfix, VI SPI 1.00 Hotfix for OMi Readiness

• UNIX OS SPI version 4.11

• Windows OS SPI version 9.11

The order in which you apply patches is important. Make sure that you install the patches in the following order:

1 Install the server patch.

2 Install agent patch and deploy the agent on the management server node.

3 Install the accessory patch.

No patch or hotfix is required to enable HP OMi functionality for UNIX and Windows OS SPIs.

Hardware and Software Requirements 19

For information on how to install patches and to perform the post installation tasks, refer to the patch text supplied with each patch.

The patches mentioned above do not support localization.

To obtain the hotfix for the Virtual Infrastructure SPI, submit a support case to HP Software Support at http://www.hp.com/go/hpsoftwaresupport.

To check for SPI updates and patches, go to the HP support site (requires an HP Passport registration).

HP SiteScope (Optional)

HP SiteScope is an agentless monitoring solution designed to ensure the availability and performance of distributed IT infrastructures, for example, servers, operating systems, network devices, network services, applications, and application components.

If you intend to receive SiteScope events in HP OMi, you must also separately install:

• SiteScope server version 9.50 (minimum).

• For HPOM for Windows only: HPOM SiteScope Adapter version 2.00, which is available as part of the OMW_00039 patch.

Check http://support.openview.hp.com/selfsolve/patches for the most current versions of patches.

You can check for updates and patches at the HP support site (requires an HP Passport registration).

WebLogic and WebSphere content packs contain correlation rules with the database areas. These cross-domain correlation rules work with Oracle Database Server and Microsoft SQL Server databases, and require you to install the following SPIs and associated minimum patches:

• WebSphere Application Server SPI version 6.10 with patch OMW_00037

• WebLogic SPI 6.10 with patch OMW_00038

• Oracle Application Server SPI version 11.50 with patch OMW_00035

• Microsoft SQL Server SPI version 11.50 with patch OMW_00036

You must also import the content packs for the following applications into HP OMi.

• Oracle Database Server (HPOprOra)

• Microsoft SQL Server (HPOprMss)

• WebSphere Application Server (HPOprWbs)

• WebLogic Application Server (HPOprWls)

For details, see Import Content Packs on page 41.

Other SPIs can also work with HP OMi. However, they require adaptation and manual configuration effort before you can take full advantage of the HP OMi features.

The SiteScope Adapter version 2.00 is included as part of HPOM for UNIX, version 9.00. No aditional adapter or patch is required.

20 Chapter 3

HP OMi GUI Client

Make sure the machines you are using as HP OMi GUI clients have the following software installed:

• Operating system: Microsoft Windows XP, Windows Server 2003, or Windows Vista.

• Microsoft Internet Explorer version 7.0.

Before accessing the HP OMi GUI, you must configure the browser to allow active content that is hosted on the machine where HP OMi is installed.

(See Internet Explorer: Tools → Internet Options → Advanced → Security → Allow active content to run in files on My Computer or configure the GUI URL (for example, http://HPGwSrv.example.com/bsm) in your browser as a trusted site.

• Java Runtime Environment (JRE).

— Version 6 Update 10 and higher (recommended)

— Version 6 Update 4 and higher (supported)

• Adobe Flash Player version 9 or higher.

If the Flash Player is missing at runtime, the BSM platform prompts you to download and install it.

• Screen resolution.

— 1024 x 768 (minimum)

— 1280 x 1024 or higher is recommended

Hardware and Software Requirements 21

22 Chapter 3

4 Installing HP OMi

This chapter guides you through the steps required to install HP OMi on the BSM platform

systems.

It is assumed that you have already installed and configured the BSM platform and HPOM prior to installing HP OMi.

Installation Steps

This section provides you with instructions about how to install HP OMi.

In a two-machine or multi-machine deployment environment, follow the instructions in this chapter to install HP OMi first on the Data Processing Server systems, followed by the Gateway Server systems. After all installations are complete, continue with Chapter 5, Configuring HP OMi.

Follow these steps to install HP OMi:

1 If the BSM platform is running, stop it as described in Stopping the BSM Platform on page 99.

2 From the HP OMi product media, execute the install_hpomi.vbs file.

HP OMi requires the Microsoft Visual C++ 2005 Redistributable. If it is missing, the Installer prompts you to accept its installation.

Click OK in order to continue with the HP OMi installation.

23

3 After the Installer has finished initializing, click Next.

If the Installer detects any anti-virus program running on your system, it prompts you to examine the warnings before you continue with the installation.

4 Read the anti-virus-related warnings, if any, that appear in the Application requirement check warnings screen and follow the instructions as described in the screen.

24 Chapter 4

5 In the Introduction (Install) screen that appears, click Next.

6 Read the license agreement in the License Agreement screen. If you accept the terms of the agreement, continue the HP OMi installation by clicking Next.

Installing HP OMi 25

7 In the Choose the application and data folders screen, click Next.

This screen does not appear if an agent is already installed on the system.

8 In the Install Checks screen, click Next after the free disk space verification is complete and successful.

If the free disk space verification is not successful, do the following:

— Free disk space, for example by using the Windows Disk Cleanup utility.

— Repeat step 7 and step 8.

The HP Software Installer automatically checks for the BSM platform installation location and installs HP OMi in that location. You can, however, choose a different installation and data folder for the shared content (content that is installed with HP OMi and shared with other HP BSM software applications).

26 Chapter 4

9 In the Pre-Install Summary screen, click Install.

The Installer selects and installs the required HP OMi software components. Each software component and its installation progress is displayed on your screen during installation.

The Installer installs the Microsoft Visual C++ 2005 Redistributable, if required, and resumes the HP OMi installation.

Installing HP OMi 27

When the installation finishes, the Installation Complete window opens showing you a summary of the installation paths used and whether the installation was successful.

10 Click Done to close the installation program.

You have now installed an instance of HP OMi. If you are using a two-machine or multi-machine deployment, repeat the instructions in this chapter for all Data Processing Server machines and then for all Gateway Server machines.

After you have installed all the HP OMi instances, proceed to the next chapter to configure HP OMi.

If the installation was not successful, review the installation log file for any errors by clicking the View log file link in the Installation Complete window to view the log file in a web browser.

For more information about the installed packages, click the Details tab.

28 Chapter 4

5 Configuring HP OMi

This chapter shows you how to configure HP OMi on the BSM platform systems. To do so, follow the steps in each of the following sections:

• Configure HP OMi on the Data Processing Server.

Create a database and configure HP OMi to connect to the database and enter HPOM access information.

• Configure HP OMi on the Gateway Server on page 38.

Execute the configuration command to configure HP OMi on the Gateway Server machines. This command deploys the HP OMi web applications and configures the web server (Apache or Microsoft IIS) to properly handle requests from the HP OMi GUI client.

Configure HP OMi on the Data Processing Server

In this section, you create a database for HP OMi. The database configuration instructions apply to all deployment types. However, in two-machine and multi-machine deployment, you create and configure a new database for HP OMi only on one Data Processing Server machine. On the other Data Processing Server machines, you only connect to the existing database using the same data.

To create and configure the database for HP OMi, complete the following steps depending on the database server you are using:

• For the Oracle database server, follow the steps in Configure HP OMi Using an Oracle Database on page 30.

• For the Microsoft SQL Server, follow the steps in Configure HP OMi Using a Microsoft SQL Server Database on page 35.

29

Configure HP OMi Using an Oracle Database

Perform the following instructions to create an Oracle database for HP OMi:

1 Stop the BSM platform, if it is running.

2 On the BSM platform system that hosts the Data Processing Server, open a new command prompt window and launch the HP OMi configuration wizard by typing the following command:

%TOPAZ_HOME%\bin\opr-configuration.bat -setup

The default value of the system variable %TOPAZ_HOME% is C:\HPBAC.

3 In the OMi Configuration Wizard, click Next.

30 Chapter 5

4 In the database settings window that opens, select Create a new database or user schema and click Next.

5 Select Oracle Server as the database server type and click Next.

Configuring HP OMi 31

6 Enter the required data for the Oracle database configuration as follows and click Next:

— Host name: The fully qualified host name of the machine on which the Oracle database server is installed (for example, MyDB.example.com).

— Port: Database port number (default: 1521).

— SID: System identifier or name of the database that uniquely identifies the Oracle database being used (for example, OMi_ORA. The default SID is orcl.

— Admin user name: User name of the database administrator with administrative permissions on the Oracle server.

— Admin user password: Password of the database administrator.

7 Enter the required data for the new schema as follows and click Next:

— New schema name: Name of the schema you are creating (for example, HPOMi_DB_Schema).

— New schema password: Password for that schema.

— Confirm password: Re-enter the password to confirm it.

— Default tablespace: The name of the dedicated default tablespace reserved for schemas. The default tablespace name is users.

— Temporary tablespace: The name of the dedicated temporary tablespace reserved for session data. The default temporary tablespace name is temp.

32 Chapter 5

8 Enter the HPOM server information to set up the event and Topology Synchronization and click Next.

— OM Server DNS name: The fully qualified domain name of the HPOM server (for example, HPOMWSrv.example.com).

— OM Server Port number: Enter the correct web service port number.

— For Topology synchronization only:

– OM Server Username for HPOM

– OM Server Password for HPOM

– OM Server Type: Select either OM for Windows or OM for UNIX

On HPOM for Windows, the username and password are needed by the Topology Synchronization executable to authenticate the user who is trying to access the HPOM for Windows server.

The user account must be a member of the HP-OVE-Operators Windows user group and also a member of the Windows user group “Power Users” or Administrators on the HPOM for Windows system. Members of the “Power Users” group can perform any task except for those reserved for administrators of the system.

On HPOM for UNIX, the user must be an HPOM for UNIX administrator.


9 In the Summary window, click Finish.

The Oracle database configuration HP OMi on the Data Processing Server is complete.

On all additional Data Processing Server machines, do not create a new database. Instead, select the option Connect to an existing database or schema and use the same data you specified for the first Data Processing Server.

After you have completed the configuration of all HP OMi instances on the Data Processing Server machines, continue with the section Configure HP OMi on the Gateway Server on page 38.

34 Chapter 5

Configure HP OMi Using a Microsoft SQL Server Database

Before creating a Microsoft SQL Server database for HP OMi, make sure you have properly installed and configured the Microsoft SQL database server.

Perform the following instructions to create a Microsoft SQL Server database for HP OMi:


2 On the BSM platform system that hosts the Data Processing Server, open a new command prompt window and launch the HP OMi configuration wizard by typing the following command:


3 In the OMi Configuration Wizard, click Next.


4 In the database settings window that opens, select Create a new database or user schema and click Next.

5 Select Microsoft SQL Server as a database server type and click Next.

36 Chapter 5

6 Create the HP OMi database as follows and click Next:

— Host name: Database server (fully qualified hostname, for example, MyDB.example.com)

— Port: Database port number (default: 1433)

— Database name: Unique database name (for example, HPOMi_DB)

— Connect to MS SQL Server using authentication type: Select either Windows or SQL server and enter the corresponding User name and the Password.

7 Follow the instructions in step 8 on page 33 to set up the event and Topology Synchronization.

The Microsoft SQL Server database configuration for HP OMi on the Data Processing Server is complete.

On all additional Data Processing Server machines, do not create a new database. Instead, select the option Connect to an existing database or schema and use the same data you specified for the first Data Processing Server.

After you have completed the configuration of all HP OMi instances on the Data Processing Server machines, continue with the section Configure HP OMi on the Gateway Server on page 38.


Configure HP OMi on the Gateway Server

In one-machine deployment, you configure HP OMi on both the Gateway and Data Processing Server by running the configuration command given below only once.

In other deployment types, for example, two-machine deployment, you run the configuration command on every Gateway Server as follows:

1 On the BSM platform systems that host the Gateway Servers, open a new command prompt window.

2 Launch the HP OMi configuration wizard by typing the following command:



After you have completed the configuration of all HP OMi instances, continue with Chapter 6, Validating the HP OMi Installation and Configuration to make sure HP OMi has been properly installed and configured.

When you execute this command on the Gateway Server machine, it configures HP OMi without starting the configuration wizard. No user input is required.

38 Chapter 5

6 Validating the HP OMi Installation and Configuration

In this chapter, you verify whether HP OMi has properly been installed and configured. Complete the steps in this chapter on all the machines on which HP OMi is installed.

Verify the HP OMi Service and Process Names

In this section, you start the BSM platform on all the BSM platform servers (that is, on every Data Processing and Gateway Server) and you verify the HP OMi service and process names as follows:1 Start the BSM platform and log on to the status page as the BSM platform administrative

user as described in Starting the BSM Platform on page 97.

2 Check the Nanny Status and the HAC Status for the HP OMi service name OPR and the process name opr-backend. HP OMi has been successfully installed and configured if the process opr-backend is listed and running on one Data Processing Server.

In the next section, you check the BSM platform management console for HP OMi menu entries.

Verify the HP OMi Menu Entries in the BSM Platform Management Console

In this section, you verify the HP OMi-related menu entries in the BSM platform management console. The following instructions apply to all types of deployments.

To verify the menu entries, follow these steps:

1 Make sure the BSM platform is running.

2 Open Internet Explorer.

3 In the address field of your browser, start the BSM platform management console by typing in the Gateway Server address.

For example: http://HPGwSrv.example.com/bsm

In deployments involving a load balancer, use the fully qualified hostname of the load balancer’s server system (for example, VirtualSrv.example.com).

4 Log on to the BSM platform management console using an account with administrative privileges.

39

5 After you have logged on, look for Operations Management in the Applications page.

6 In the Admin menu of the BSM platform management console, click Operations Management to see the HP OMi-related menu entries.

HP OMi is now properly installed and configured. In the next chapter, you import content packs using the BSM platform management console in order to allow HP OMi to exchange customized configuration data between instances of its installation.

40 Chapter 6

7 Managing Content Packs

This chapter shows you how to import content packs using the BSM platform management console.

HP OMi uses content packs to exchange customized configuration data between instances of the HP OMi installations. A content pack can contain a complete snapshot of all (or any part of) rules, tools, mappings, and assignments that you define and configure.

For more details about content packs, see the HP Operations Manager i Concepts Guide and the online help.

Import Content Packs

This section provides you with instructions about how to import content packs. These are stored on the Data Processing Server machines.

To import content packs, complete the following steps:


2 On one of the Data Processing Server machines, open Internet Explorer.

3 In the address field of your browser, start the BSM platform management console by typing in the Gateway Server address.

For example: http://HPGwSrv.example.com/bsm

4 Log on to the BSM platform management console using an account with administrative privileges.

5 In the BSM platform management console, click the following:

Admin → Operations Management → Manage Content → Content Packs

6 In the Content Pack Definitions toolbar, click the Import a Content Pack button.

41

7 From the Import Content Pack dialog, browse to the location of the content packs (default: %TOPAZ_HOME%\HPBAC\conf\opr\content).

8 Select a content pack (for example, MM-INF.xml) and click Open.

9 Select Overwrite and click Import to import the content pack.The Information dialog window appears showing you the number of artifacts (for example, health indicator definition artifacts) that you have imported.

10 Click OK to close the Information dialog.

You can load other content packs you want to work with by following the same steps.

After you have successfully loaded the content packs, continue with Chapter 8, Connecting HP OMi to HPOM to connect the HP OMi system to HPOM.

42 Chapter 7

8 Connecting HP OMi to HPOM

This chapter describes how you connect the HP OMi and HPOM systems to achieve a bi-directional synchronization of events between the two systems.

You must establish a trust relationship between the HP OMi and HPOM systems using one of the following methods:

• Set up a connection with an HPOM HTTPS Agent

By installing HPOM HTTPS agents on all HP OMi systems, a trust relationship between HP OMi and HPOM is achieved, except for environments with a load balancer, for which the certificates must be separately granted from the HPOM management server systems.

— Make sure that an HPOM agent is installed on all Gateway Server systems and on all Data Processing Server systems in accordance with the HP Operations Manager documentation.

— If you are using a load balancer, complete the steps in the section Issuing Certificates for the Load Balancer on page 52.

— Add the CIs from HPOM to the UCMDB, as described in Populating the UCMDB on page 53.

— Set up a message forwarding policy on each HPOM management server with the node name of the load balancer, if configured, or one Gateway Server, as appropriate for your high availability arrangement, as described in Configuring Message Forwarding Policies on page 54.

• Set up a connection without an HPOM Agent

Follow the instructions in all sections of this chapter for all Gateway Servers and all Processing Servers:

— Add all Data Processing Servers, all Gateway Servers, and the load balancer, if configured, as nodes to HPOM, as described in HP OMi Systems as Nodes to HPOM on page 46.

— For connection and communication between the HP OMi and HPOM systems, establish a trust relationship between the two systems, as described in Establishing a Trust Relationship on page 50.

— If you are using a load balancer, complete the steps in the section Issuing Certificates for the Load Balancer on page 52.

— Add the CIs from HPOM to the UCMDB, as described in Populating the UCMDB on page 53.

— Set up a message forwarding policy on each HPOM management server with the node name of the load balancer, if configured, or one Gateway Server, as appropriate for your high availability arrangement, as described in Configuring Message Forwarding Policies on page 54.

43

HPOM in High Availability Environments

In addition to installing HPOM on a single system, the following configurations may also be used to achieve higher availability for HPOM:

• Clustering

For details about clustering, see the HP Operations Manager Installation Guide for your chosen operating system.

• Server Pooling

For details about server pooling, see the High Availability Through HPOM Server Pooling for HP Operations Manager on UNIX and Windows Operating Systems white paper.

• Server Log Shipping

HPOM for Windows only: For details about server log shipping for HP Operations Manager for Windows, see the HPOM 8.1 High Availability Utilizing Microsoft SQL Server Log Shipping white paper.

• Primary and Backup Servers

For details about primary and backup server arrangements for HP Operations Manager for UNIX, see the HP Operations Manager for UNIX Administrator’s Reference guide.

For details about primary and backup server arrangements for HP Operations Manager for Windows, see the HP Operations Manager for Windows Online Help.

Clustering and Server Pooling

Clustering and server pooling use dedicated applications to manage the participating HPOM systems. As a result, these are accessed using one virtual host address in place of the physical host addresses of the individual systems. To connect to an HPOM cluster or server pool, follow the instructions for connecting to a stand-alone HPOM installation and specify the virtual host address of the HPOM cluster or server pool.

• For all HP OMi systems, complete one of the following configurations:

— Install HPOM HTTPS agents from the HPOM management server associated with the virtual HPOM host address as described in the HPOM product documentation.

— Request and grant certificates from the HPOM management server associated with the virtual HPOM host address as described in the section HP OMi Systems as Nodes to HPOM on page 46.

• If you are using a load balancer, complete the steps in the section Issuing Certificates for the Load Balancer on page 52.

• Populate the UCMDB as described in Populating the UCMDB on page 53.

• Configure a message forwarding policy, as described in Configuring Message Forwarding Policies on page 54.

Server Log Shipping and Backup Servers

Backup servers that are not managed using clustering or server pooling applications must be handled as separate, physical systems. Configuring connections in such environments is more complex and some manual switching is usually required.

44 Chapter 8

To connect to an HPOM environment with two or more management servers not managed by a clustering or server pooling application, follow the instructions for connecting to a stand-alone HPOM installation and make sure that all HP OMi systems have the client certificates from all the participating HPOM management servers.

• For all HP OMi systems, complete one of the following configurations:

— Install HPOM HTTPS agents from the primary HPOM management server. After you have configured your multi-server HPOM environment, all HPOM management server certificates required by the HP OMi systems are issued automatically from the primary HPOM management server because it is synchronized with the other HPOM management servers. For details, see Exchange node configurations in the HPOM for Windows online help or information about uploading and downloading configuration information in the HPOM for UNIX Installation Guide and the Administrator’s Reference manual.

— Configure the node in the primary HPOM management server as described in HP OMi Systems as Nodes to HPOM on page 46 and exchange node configurations. For details, see Exchange node configurations in the HPOM for Windows online help or information about uploading and downloading configuration information in the HPOM for UNIX Installation Guide and the Administrator’s Reference manual.

• Issue a certificate for the load balancer from the primary HPOM management server as described in Issuing Certificates for the Load Balancer on page 52.

• Populate the UCMDB as described in Populating the UCMDB on page 53.

• Add the load balancer, if configured, or one HP OMi Gateway Server system to the existing message forwarding policy for each HPOM management server as described in Configuring Message Forwarding Policies on page 54.

• When switching to a new HPOM management server, change the HPOM Connection Settings in the Infrastructure Settings Manager for Operations Management to match the active HPOM management server and execute any required actions on the HPOM management server as described in the HPOM documentation.

To open the Infrastructure Settings page for Operations Manager:

a After logging on to the BSM platform management console, open the Infrastructure Settings page as follows:

Admin → Platform → Infrastructure Settings

b Select the Applications context.

c From the Applications drop-down menu, select Operations Management.

d In the Operations Management - HPOM Connection Settings section, set up the management server settings of HPOM.

Connecting HP OMi to HPOM 45

HP OMi Systems as Nodes to HPOM

To be able to issue certificates to HP OMi systems and establish an SSL trust relationship, you must add all Data Processing Servers, all Gateway Servers, and the load balancer, if configured, as nodes to HPOM. This trust relationship is necessary for event synchronization and topology synchronization between the HP OMi and HPOM systems.

Adding Nodes to HPOM for Windows

To add the HP OMi systems as nodes to HPOM for Windows, complete the following steps for each Gateway Server, each Data Processing Server, and if configured, the load balancer:

1 On the HPOM for Windows system, start the HPOM for Windows console as follows:

Start → Programs (or All Programs) → HP → HP Operations Manager

2 Click HP Operations Manager Console.

3 Right-click Nodes and select Configure → Nodes ...

The Configure Managed Nodes dialog box opens.

4 Right-click Managed Nodes in the right pane and select New Node.

46 Chapter 8

The Base Settings dialog box opens.

5 Enter the fully qualified domain name and the display name for the node you want to add to HPOM for Windows.

6 Select Enter manually and click Next.

The OS Setup dialog box opens.

7 In the System Type field, select x86/x64 Compatible.

8 Select the appropriate values for Operating System, Bit Length, and Version and click Next.


The Advanced Settings dialog box opens.

9 Optional: Enter a description for the node you are creating.

10 Clear the check box Automatic deployment of policies and packages.

11 Select the check box Automatically grant certificate. If the certificate cannot be granted automatically, grant it manually as described in Establishing a Trust Relationship on page 50.

12 Click Finish to close the Advanced Settings dialog box and return to the Configure Managed Nodes dialog box.

13 In the Configure Managed Nodes dialog box, click OK.

14 In the Agent Installation dialog box that opens, click Cancel.

The Agent Installation dialog box closes and the HP OMi system node is added to the list of nodes in HPOM for Windows.

48 Chapter 8

Adding Nodes to HPOM for UNIX When you add any HP OMi system as a node in HPOM for UNIX, you must decide which operators should monitor this integration and to which node groups you want to add the HP OMi systems.

All the events that relate to the integration between HP OMi and HPOM for UNIX and are generated on HPOM for UNIX belong to the message group OpC.

To add the HP OMi systems as nodes to HPOM for UNIX, complete the following steps for each Gateway Server, the Data Processing Server, and if configured, the load balancer:

1 On the HPOM for UNIX system, open a command shell.

2 Add the HP OMi system as a managed node to the node bank and to the required node groups with the following command:

opcnode -add_node node_name=<HP OMi fully qualified hostname> net_type=NETWORK_IP mach_type=<machine type> group_name=hp

The machine type values for the supported platforms are:

— 64-bit operating systems: MACH_BBC_WIN2K3_X64

— 32-bit operating systems: MACH_BBC_WINNT_X86

The fully qualified domain name in two-machine and multi-machine deployment is the domain name of a Gateway Server, for example, HPGwSrv.example.com.


Establishing a Trust Relationship

For connection and communication between the HP OMi and HPOM systems, you must establish a trust relationship between the two systems. This requires all HP OMi systems to be granted a client certificate from the primary HPOM management server. If you have a load balancer, it requires both client and server certificates from the HPOM management server, for example:

• Single system arrangements: HPOM management server certificates from the one physical system.

• Cluster or Server Pooling arrangements: HPOM management server certificates from the virtual system.

• Primary and Backup Servers, and Server Log Shipping arrangements: HPOM management server certificates from all the physical HPOM systems. After your multi-server HPOM environment is configured, all HPOM management server certificates required by the HP OMi systems are issued automatically from the primary HPOM management server because it is synchronized with the other HPOM management servers.

Issuing certificates for a load balancer is described under Issuing Certificates for the Load Balancer on page 52.

Requesting Certificates for HP OMi

To request client certificates from the primary HPOM management server for each HP OMi Gateway Server and Data Processing Server system, send a certificate request to the primary HPOM management server from each HP OMi system as follows:

1 Make sure the BSM platform is not running.

2 On the BSM host system, open a command prompt and change directory to %TOPAZ_HOME%\bin. The default value of the system variable %TOPAZ_HOME% is C:\HPBAC.

3 Start the certificate configuration script by executing the following command:

opr-certificate-configuration.bat

The command output informs you that a certificate request was sent to the HPOM server.

4 Repeat for all other HP OMi systems.

Granting Certificates on the HPOM System

The certificate requests sent to each HPOM management server must be granted to complete the establishing of the trust relationship between HP OMi and HPOM. You can view pending certificate requests and grant certificate requests using the GUI console or the command line. For details, see the appropriate section:

• Granting Certificates Using the HPOM for Windows Console on page 51

• Granting Certificates Using a Command Prompt or a Shell on page 52

50 Chapter 8

Granting Certificates Using the HPOM for Windows Console

To view pending requests and grant certificate requests using the HPOM for Windows console, complete these steps:

1 Start the HPOM for Windows console as follows:


2 Click HP Operations Manager Console.

3 In the left pane of the HPOM console, click Certificate requests.

4 In the right pane of the Certificate requests window, right-click the entry for the HP OMi system under the Mapped Node and the Requesting Client columns of the window for which you want to grant a certificate.

5 To grant a certificate request to the HP OMi system, select:

All Tasks → Grant

6 Click OK in the Grant Certificate Request dialog to confirm the granting of the certificate.

The certificate request entry disappears if the certificate is successfully granted.

If the Windows firewall is running, the certificate installation on the HP OMi node may fail because the Black Box Communication (BBC) port is not yet open. To solve the problem, manually add the BBC port 383 to the Windows firewall.


Granting Certificates Using a Command Prompt or a Shell

To view pending requests and grant certificates through a command prompt on the HPOM for Windows system or a shell on the HPOM for UNIX system, complete these steps:

1 In a command prompt or a shell on the HPOM system, list the pending incoming request as follows:

— HPOM for Windows:

ovowcsa -listpending

— HPOM for UNIX:

ovcm -listpending -l

The option “-l” (letter “l”) helps to identify the correct request if multiple requests are pending.

2 Look for the ID that relates to the pending request and copy it.

3 Grant the incoming request from the certificate server as follows:


ovowcsa -grant <copiedRequestId>

— HPOM for UNIX:

ovcm -grant <copiedRequestId>

Issuing Certificates for the Load Balancer

A client and a server certificate is required for secure communication between the load balancer and each HPOM management server. To issue these certificates, perform the following steps:

1 On the HPOM Server system, issue a certificate for the load balancer node as follows:

ovcm -issue -file <certificate_file> -name <FQDN of load balancer> [-pass <passphrase>]

2 Upload the certificate to the load balancer as both a client and a server certificate to ensure authentication for incoming and outgoing connections.

3 Enable HTTPS port forwarding on Gateway Servers even if only HTTP is used for the GUIs. Communication between HPOM and HP OMi uses HTTPS.

For more details about how to setup a load balancer, see “Load Balancing for the Gateway Server” in the HP Business Availability Center Deployment Guide.

Starting the BSM Platform

To perform the next steps in this chapter, start the BSM platform and make sure it is running by checking its status page. For details, see Starting the BSM Platform on page 97.

If the Windows firewall is running, the certificate installation on the HP OMi node may fail because the Black Box Communication (BBC) port is not yet open. To solve the problem, manually add the BBC port 383 to the Windows firewall.

52 Chapter 8

Populating the UCMDB

Mapping events to configuration items (CIs) in the UCMDB is a pre-requisite for advanced HP OMi features such as health management and Topology-based Event Correlation.

To add CIs to the UCMDB, use one the following methods:

• Discovery with UCMDB and Discovery and Dependency Mapping

Create configuration items using the discovery features of the UCMDB and Discovery and Dependency Mapping (DDM). For details, see the Discovery and Dependency Mapping documentation.

• HP OMi Topology Synchronization

Create configuration items using the Topology Synchronization feature in HP OMi.

— To add CI groups, hosts, and HPOM Agent CIs to the UCMDB, run the following command-line tool on the Data Processing Server:

%TOPAZ_HOME%\bin\opr-startTopologySync.bat

For more details, see Topology Synchronization Tool on page 101.

— To synchronize the Smart Plug-in service models and add the corresponding application-specific CIs to the UCMDB, follow the instructions in Synchronizing Smart Plug-in Service Models on page 101.

For more details about Topology Synchronization, see the HP Operations Manager i Concepts Guide and the online help.


Configuring Message Forwarding Policies

To allow event synchronization between HPOM and HP OMi, you must set up a message forwarding policy on each HPOM management server with the node name of the load balancer, if configured, or one Gateway Server, as appropriate for your high availability arrangement.

Setting Up a Policy On HPOM for Windows

Before setting up a policy and to avoid overwriting the current settings, verify whether a policy of the type server-based flexible management is already active on the HPOM for Windows server. If a policy does not exist, create a new policy as described in the section Creating a New Policy on page 54. If a policy already exists and is active, adapt the policy as described in the section Adapting an Active Policy on page 58.

Creating a New Policy

To set up a new policy on HPOM for Windows, complete the following steps:



2 In the left pane of the HPOM for Windows console, select the following:

Policy management → Server policies grouped by type → Server-based Flexible Management

3 Right-click Server-based Flexible Management (or a blank space in the right window pane).

4 Select New → Policy to create a new policy.

54 Chapter 8

The Server-based Flexible Management Editor dialog appears.

5 Insert the following text for the new policy into the blank window of the General tab:____________________________________________________________________

TIMETEMPLATES# none

RESPMGRCONFIGSRESPMGRCONFIG DESCRIPTION "Forward all messages to HP OMi"SECONDARYMANAGERSACTIONALLOWMANAGERS

MSGTARGETRULESMSGTARGETRULE DESCRIPTION "Forward all messages rule"

MSGTARGETRULECONDSMSGTARGETRULECOND DESCRIPTION "Forward all messages"

MSGTARGETMANAGERSMSGTARGETMANAGERTIMETEMPLATE "$OPC_ALWAYS"OPCMGR IP 0.0.0.0 "<HP OMi fully qualified host name>"

____________________________________________________________________

6 Replace <HP OMi fully qualified host name> in the text with the fully qualified hostname of the Gateway Server system that should receive HPOM messages (for example, HPGwSrv.example.com).

In deployments involving a load balancer, a NAT device, or a reverse proxy, use the fully qualified hostname of the system used to access the Gateway Server system (for example, VirtualSrv.example.com).

For details about load balancing and high availability, see the section “High Availability for HP Business Availability Center” in the HP Business Availability Center Deployment Guide.

7 Click Check Syntax to make sure that there are no syntax errors in the new policy text.

This forwards all messages to HP OMi. If you want to reduce the number of messages to be sent, see “Server-based Flexible Management” in the HPOM documentation and modify the text of the policy, so that only a selected subset of messages is sent to HP OMi.


8 Click Save and Close.

9 In the Save As dialog box that appears, enter a name and a description for the new policy.

10 Click OK to close the Save As dialog.

56 Chapter 8

11 From the Policy Management folder, right-click the policy and select:

All Tasks → Deploy on

The Deploy server policy on dialog box opens.

12 In the Deploy server policy on dialog box, select the name of your HPOM management server.

13 Click OK to deploy the server-based flexible management policy on the HPOM for Windows management server.

14 Test the new policy by creating a message as described in Validating Event Synchronization on page 63.

Messages that arrive at the HPOM for Windows system should be forwarded to HP OMi.

Continue with Chapter 9, Validating Event Synchronization to validate the HPOM flexible management policy and test the connection between HPOM and HP OMi.


Adapting an Active Policy

If a message forwarding policy already exists on the HPOM for Windows system, perform the following instructions to edit this policy and add another message target manager to it.



2 In the left pane of the HPOM for Windows console, select the following:

Policy management → Server policies grouped by type → Server-based Flexible Management

3 In the right pane of the HPOM for Windows console, double-click the existing policy that you want to edit. The Server-based Flexible Management Editor dialog appears.

4 Add another message target manager as shown in the following example policy text:____________________________________________________________________

TIMETEMPLATES# none




MSGTARGETMANAGERSMSGTARGETMANAGERTIMETEMPLATE "$OPC_ALWAYS"OPCMGR IP 0.0.0.0 "<First Target Manager>"

MSGTARGETMANAGERS MSGTARGETMANAGER

TIMETEMPLATE "$OPC_ALWAYS"OPCMGR IP 0.0.0.0 "<HP OMi fully qualified host name>"

____________________________________________________________________




6 Click Check Syntax to make sure that there are no syntax errors in the text of the policy.

7 Click Save and Close.


58 Chapter 8

8 Redeploy the server-based flexible management policy on the HPOM for Windows management server.


After that, messages that arrive at the HPOM for Windows system are forwarded to HP OMi.

Continue with Chapter 9, Validating Event Synchronization in order to validate the HPOM flexible management policy and test the connection between HPOM and HP OMi.


Setting Up a Policy On HPOM for UNIX

Before setting up a policy and to avoid overwriting the current settings, verify whether the msgforw message forwarding policy is already active on the HPOM for UNIX server. If the msgforw message forwarding policy does not exist, create a new policy as described in the section Creating a New Policy on page 60. If the msgforw message forwarding policy already exists and is active, adapt the policy as described in the section Adapting an Active Policy on page 61.

Creating a New Policy

To set up a new message forwarding policy on HPOM for UNIX, complete the following steps:

1 Change to the work_respmgrs directory as follows:

cd /etc/opt/OV/share/conf/OpC/mgmt_sv/work_respmgrs/

2 Create a new policy file using the following command:

vi <policy file name>

3 Insert the following text in new policy file: ____________________________________________________________________

TIMETEMPLATES# none




MSGTARGETMANAGERSMSGTARGETMANAGERTIMETEMPLATE "$OPC_ALWAYS"OPCMGR IP 0.0.0.0 "<HP OMi fully qualified host name>"

_____________________________________________________________



Policy template files can be found in:

cd /etc/opt/OV/share/conf/OpC/mgmt_sv/tmpl_respmgrs/


60 Chapter 8


5 Check syntax to make sure that there are no syntax errors in the text of the new policy as follows:

/opt/OV/bin/OpC/opcmomchk -msgforw <policy file name>

6 Copy the policy to the respmgrs directory as follows:

cp <policy file name> /etc/opt/OV/share/conf/OpC/mgmt_sv/respmgrs/

7 Restart the server processes as follows:

/opt/OV/bin/OpC/opcsv -stop

/opt/OV/bin/OpC/opcsv -start

Message forwarding from HPOM for UNIX to HP OMi is now configured and enabled.


After that, messages that arrive at the HPOM for UNIX system are forwarded to HP OMi.

Continue with Chapter 9, Validating Event Synchronization in order to validate the HPOM the flexible management policy and test the connection between HPOM and HP OMi.

Adapting an Active Policy

If the message forwarding policy already exists on the HPOM for UNIX system, perform the following instructions to edit this policy and add another message target manager to it:

1 Change to the work_respmgrs directory as follows:

cd /etc/opt/OV/share/conf/OpC/mgmt_sv/work_respmgrs/

2 Edit the existing policy to which you want to add the HP OMi system as a target as follows:

vi <policy file name>

3 Add another message target manager as shown in the following policy text:

____________________________________________________________________

TIMETEMPLATES# none




MSGTARGETMANAGERSMSGTARGETMANAGERTIMETEMPLATE "$OPC_ALWAYS"

Policy template files can be found in:

cd /etc/opt/OV/share/conf/OpC/mgmt_sv/tmpl_respmgrs/


OPCMGR IP 0.0.0.0 "<First Target Manager>"

MSGTARGETMANAGERS MSGTARGETMANAGER

TIMETEMPLATE "$OPC_ALWAYS"OPCMGR IP 0.0.0.0 "<HP OMi fully qualified host name>"

____________________________________________________________________




5 Check syntax to make sure that there are no syntax errors in the text of the new policy as follows:

/opt/OV/bin/OpC/opcmomchk -msgforw <policy file name>

6 Copy the policy to the respmgrs directory as follows:

cp msgforw /etc/opt/OV/share/conf/OpC/mgmt_sv/respmgrs/

7 Restart the server processes as follows:

/opt/OV/bin/OpC/opcsv -stop

/opt/OV/bin/OpC/opcsv -start

Message forwarding from HPOM for UNIX to HP OMi is now configured and enabled, and can be used.


After that, messages that arrive at the HPOM for UNIX system are forwarded to HP OMi.

Continue with Chapter 9, Validating Event Synchronization in order to validate the HPOM flexible management policy and test the connection between HPOM and HP OMi.


62 Chapter 8

9 Validating Event Synchronization

This chapter provides you with instructions about how to validate event synchronization and test the connection between HPOM and HP OMi.

Verify Message Forwarding from HPOM to HP OMi

In this section, you check whether the message forwarding policy for sending messages from HPOM to HP OMi is correctly configured. To do so, complete the following steps:


2 Make sure at least one open message interface policy is deployed on your HPOM system. For instructions and details, see the HP Operations Manager documentation.

3 On the HPOM system, open a command or a shell prompt.

4 Create a new message by executing the following command:

— On the HPOM for Windows system:

opcmsg a=App o=Obj msg_text="Hello"

— On the HPOM for UNIX system:

/opt/OV/bin/OpC/opcmsg a=App o=Obj msg_text="Hello"

If you have correctly configured the server-based flexible management, the message arrives at the HPOM management server and is forwarded to HP OMi. You can view the events with the HP OMi Event Browser.

Every new message is now forwarded to the HP OMi system.

If message forwarding does not work, see the troubleshooting section Message Forwarding from HPOM to HP OMi does not Work on page 80 for known problems, their solutions, and workarounds.

If the message is sent multiple times, no new message is generated by HPOM. These messages are regarded as duplicates and only the message duplicate count is increased.

To generate a new message, modify the message text for example as follows:

• On the HPOM for Windows system:opcmsg a=App o=Obj msg_text="Hello_002"

• On the HPOM for UNIX system:/opt/OV/bin/OpC/opcmsg a=App o=Obj msg_text="Hello_002"

63

Synchronize HP OMi Events with HPOM Messages

In this section, you check whether a change in an event is synchronized in HP OMi and HPOM. Choose an event that has been synchronized in HPOM and HP OMi earlier and change its severity, for example, from minor to major.

To change the severity of an event, complete the following steps:


2 Log on to the BSM platform management console.

3 Click Applications → Operations Management.

4 In the Event Browser top pane of the Event Perspective window, select the event for which you want to change the severity.

5 In the Event Details bottom pane of the Event Perspective window, click the Edit button of the General tab.

6 From the Severity drop-down list, choose another severity (for example, major) and click Save to change it to the selected severity.

7 In HPOM, verify the severity of this event and make sure it has been set to the new severity value.

64 Chapter 9

10 HP OMi Licensing

This chapter describes how to obtain, install, and update licenses for HP OMi.

HP OMi Licenses

In order to use HP OMi applications, you must obtain a valid license key from HP and then update the license key in the BSM platform.

HP OMi licenses are available for the following components:

• Event Management Foundation

• Topology-based Event Correlation

• Health Perspective Views

For details about these components, see the HP Operations Manager i Concepts Guide available from the HP Software Product Manuals web site.

You can use the corresponding HP OMi functionality only after you have obtained and added the appropriate licenses. The absence of one or more licenses for the components mentioned above restricts the availability of the corresponding HP OMi functionality.

For detailed information on the BSM platform licensing, see “Licenses” in the HP Business Availability Center Platform Administration guide.

Types of Licenses

You can obtain the following types of licenses for HP OMi:

• Temporary License

This license is automatically granted, installed, and enabled with HP Business Availability Center. This license enables you to use HP OMi for evaluation purposes and expires 60 days after the HP Business Availability Center installation.

• Permanent License

A permanent license for an HP OMi component provides you with unlimited use of this component.

See Product License Requests on page 66 for more details about requesting licenses.

65

Product License Requests

Before requesting a license, you should prepare and specify the following information:

• Order number

• Host ID of the system where you have installed the software. You can access the host ID from any system through the GUI of the BSM management.

To view the license host ID information, see Viewing License Information on page 68

• Contact information (company, name, address, phone, and email)

You may request a license in one of two ways:

• By Internet

You can get license passwords by visiting the home page of the HP License Key Delivery Service.

• By Mail, Phone or Fax

You can also request a license by mail or fax using the licence request template on the back of the entitlement certificate. Enter the requested information, and mail or fax it to the nearest HP Password Delivery License Key Delivery Service.

For details, see the HP License Key Delivery Service at the following location:

https://webware.hp.com/

66 Chapter 10

Installing or Updating HP OMi Licenses

HP OMi requires a valid license. Perform the following instructions to install or, at a later stage, update the license key (for example, after acquiring a license for one or more HP OMi components):



3 In the BSM platform management console, click the following:

Admin → Platform → Setup and Maintenance → License Management

4 At the bottom of the License Management page, click New License Key.

5 Enter the new license key you obtained and click OK.

6 Log off from the BSM platform management console and wait for a few minutes.

7 Log on to the BSM platform management console again in order to be able to view the new license key information.

To view the license information, see Viewing License Information on page 68.

For detailed information on updating the license key, see “License Management Overview” in the HP Business Availability Center Platform Administration guide.

HP OMi Licensing 67

Viewing License Information

To view the license properties, follow these steps:



3 In the BSM platform management console, select the following:

Admin → Platform → Setup and Maintenance → License Management

The General License Properties pane of the License Management section displays the following information:

• License key

• License host ID

• Maintenance number

• License type

• Expiration date

In addition to viewing the general license properties, you can check the license validity of the HP OMi components in the Operations Management pane of the License Management section. Figure 4 illustrates the HP OMi license validity:

Figure 4 HP OMi License Validity

Additionally, you can review the expiry date of the license key by selecting the following:

Help → About HP Business Service Management

68 Chapter 10

11 Disabling or Uninstalling HP OMi

This chapter provides you with instructions about how to disable or uninstall HP OMi. Uninstalling HP OMi consists of two procedures:

1 Uninstalling HP OMi on page 71

2 Post-Uninstallation Cleanup on page 75

Disabling HP OMi

Disabling HP OMi is an option you can choose when you no longer want to use the installed HP OMi software, but still want to use a licensed BAC installation.

To disable HP OMi, follow these steps:

1 First, disable the message forwarding policy in the management console of the HPOM server system.

2 Stop the BSM platform on all Data Processing and Gateway Servers as follows:

Start → Programs (or All Programs) → HP Business Availability Center → Administration → Disable Business Availability Center

3 In a command prompt window, execute the following command:

%TOPAZ_HOME%\bin\opr-configuration.bat -disable

4 Start the BSM platform again on all Data Processing and Gateway Servers as follows:

Start → Programs (or All Programs) → HP Business Availability Center → Administration → Enable Business Availability Center

After disabling HP OMi, the opr-backend process is not listed in the Nanny section in the HP Business Availability Center Server Status page

If you have a licensed version of HP Business Availability Center (HP BAC) and want to continue using it, you must disable HP OMi, rather than uninstall it.

Your HP BAC installation is no longer supported after uninstalling HP OMi, and you must uninstall and reinstall BAC to revert to a supported version.

69

Enabling HP OMi

To enable HP OMi after disabling it, complete the following steps on all Data Processing and Gateway Servers:


2 In a command prompt windows, execute the following command on all the BSM platform systems:


3 Start the BSM platform on all Data Processing and Gateway Servers.

4 On the HPOM server system, re-enable the message forwarding policy in the management console.

HP OMi is now enabled. All the BSM platform processes are up and running and the opr-backend process is listed in the Nanny and HAC status sections in the HP Business Availability Center Server Status page.

70 Chapter 11

Uninstalling HP OMi

After uninstalling HP OMi, it is required that you also uninstall the BSM platform as described in Uninstalling the BSM Platform on page 74.

To delete the installed HP OMi components from all the BSM server systems, follow these steps:

1 First, disable the message forwarding policy in the management console of the HPOM server system.

2 On all Data Processing and Gateway Servers, stop the BSM platform, if it is running.

3 In a command prompt window, disable HP OMi by executing the following command on all the BSM platform systems:

%TOPAZ_HOME%\bin\opr-configuration.bat -disable

4 Click Start → Control Panel → Add or Remove Programs.

5 Select HP Operations Manager i and click Change/Remove to start the HP Software Installer.

6 Select Uninstall and click Next.

Disabling or Uninstalling HP OMi 71

7 In the Pre-Uninstall Summary, click Uninstall.

8 Click OK when the note about deinstalling the BSM platform appears.

72 Chapter 11

The Installer selects and uninstalls the HP OMi software components. Each software component and its uninstallation progress are displayed on your screen during the uninstallation operation.

After the uninstallation process is complete, the Uninstall Complete window opens showing you a summary of the uninstallation process.

9 In the Uninstall Complete window, click Done to close the uninstallation program.

10 Restart your system to apply the changes made to it.

From the View log file link, you can access the uninstallation log file that opens in a web browser. For details on the removed packages, click the Details tab.


Uninstalling the BSM Platform

To complete the HP OMi uninstallation, delete the BSM platform from each Data Processing and Gateway Server by following the instructions in the HP

After the HP OMi and BSM platform uninstallation, perform the post-uninstallation cleanup instructions as described in Post-Uninstallation Cleanup on page 75.

74 Chapter 11

Post-Uninstallation Cleanup

In order to have a clean system after uninstallation, you can remove a number of files and directories from HP OMi, the Universal Configuration Management Database (UCMDB), and from the BSM platform systems.

Log Files

You can remove the log files manually after uninstallation (see Log Files on page 94).

Shared Components

Shared components (see Shared HP Components on page 93) are deleted during the HP OMi uninstallation (unless they are used by an HPOM Agent). However, some files such as log files and data files may still remain. You can delete these files manually after uninstallation.

Databases

After the BSM platform uninstallation, delete the databases you have created earlier for the BSM platform and HP OMi using the tools provided by your database application.

Cleaning Up HPOM

You can optionally delete the node from HPOM if you have not deployed an HPOM agent or if you want to delete the agent as well.


76 Chapter 11

A Troubleshooting

Problems may have several causes that require the troubleshooting steps in one of the troubleshooting sections, or a combination of all the steps in all sections.

After you perform the steps in a section, verify if the problem has been solved. If the problem still persists, go to the next section and perform its troubleshooting instructions and check if the problem has been solved.

This chapter provide you with solutions or workarounds to the known problems that may be encountered.

• Installation Issues on page 78

— Files are Missing on page 78

— Files are Corrupt on page 78

— The HP OMi Database is Corrupt on page 79

— The BSM Platform Database is Corrupt on page 79

• Event Synchronization Issues on page 80

— Message Forwarding from HPOM to HP OMi does not Work on page 80

— Synchronizing HP OMi Events with HPOM Messages Does Not Work on page 85

— Message Forwarding Times Out on HPOM on page 84

• Topology Synchronization Issues on page 87

— Web Service Fatal Error Message: Unauthorized on page 87

— Web Service Fatal Error Message: Connection Refused on page 87

— Web Service Fatal Error Message: Not Found on page 88

• Health Perspective Issue on page 90

77

Installation Issues

This section provides solutions to installation-related issues such as missing files and corrupted data.

Files are Missing

You can perform an HP OMi installation repair if files are accidentally deleted or if the system shows error messages that indicate that files are missing.

The installation repair results in the following:

• Missing files are reinstalled, only missing files are replaced, and modified files remain unchanged.

• HP OMi is reconfigured.

• Existing BSM platform and HP OMi databases are reused.

To reinstall missing files, perform the following steps on all the BSM platform systems:


2 Click Start → Control Panel → Add or Remove Programs.

3 Select HP Operations Manager i and click Change/Remove to start the HP Software Installer.

4 In the Application Maintenance window, select Repair and click Next.

5 Click Next to start the installation repair.

6 After the installation repair, execute the following in a new command prompt window on the HP OMi system:


7 Complete the steps as described in Configure HP OMi on the Data Processing Server on page 29. However, in the database settings window, select Connect to an existing database or user schema instead of Create a new database or user schema.

Files are Corrupt

You can perform an HP OMi installation repair if error messages are displayed indicating that some configuration files are corrupt or if the system does not work after customization.


• All files are reinstalled.

• Local configuration files are reconfigured.

• Existing BSM platform and HP OMi databases are reused.

To re-install corrupted files, perform the following steps on all the BSM platform systems:


2 Uninstall HP OMi as described in Uninstalling HP OMi on page 71.

3 In the HP OMi product media, execute the install_hpomi.vbs file.

78 Appendix A

4 On the HP OMi system, execute the following in a new command prompt window:


5 Complete the steps as described in Configure HP OMi on the Data Processing Server on page 29. However, in the database settings window, select Connect to an existing database or user schema instead of Create a new database or user schema.

The HP OMi Database is Corrupt

You can perform an HP OMi installation repair if you encounter internal event database access errors that the system reports when you access existing events.


• Event database is deleted.

• New event database is created.

• Configuration files are rewritten.

To repair a corrupted HP OMi database, perform the following steps:

1 Delete the HP OMi database using a database-specific management tool (for example, SQL Server Management Studio).

2 Create a new database as described in Configure HP OMi on the Data Processing Server on page 29.

The BSM Platform Database is Corrupt

You can restore all the databases for the BSM platform and HP OMi from previous system backups as described in the HP Business Availability Center Deployment Guide and the HP Business Availability Center Database Guide.

The installation repair results in the system being restored to a previous working state.

All existing events are lost. If you want to keep these events, try to repair the BSM platform database as described in The BSM Platform Database is Corrupt on page 79.

It is assumed that you have already created a backup of your BSM platform and HP OMi databases.

Troubleshooting 79

Event Synchronization Issues

If you find that event synchronization is not working properly, try solving this problem by performing some or all of the steps described in the following sections.

Message Forwarding from HPOM to HP OMi does not Work

Message forwarding does not work after you have configured the connection and the trust relationship between HP OMi and HPOM.

To solve the problem, complete the following steps:

Verify the Black Box Communication between HP OMi and HPOM

Make sure the Control daemon and the Black Box Communication (BBC), used for communication between HP OMi and HPOM, have started as follows:

1 In a command prompt on HP OMi and HPOM systems, execute the following command:

ovc -status

Example of the command result:___________________________________________________________________ovcd OV Control CORE (8452) Runningovbbccb OV Communication Broker CORE (2032) Running__________________________________________________________________

2 If ovc is not running, do the following:

a Start it with the following command:

ovc -start

b Verify if it is running by executing the following command:

ovc -status

3 Make sure that certificates are exchanged correctly as follows:

On the Gateway Server system, check the certificate by executing the following command:

ovcert -check

Example of the command result:

____________________________________________

OvCoreId set : OKPrivate key installed : OKCertificate installed : OKCertificate valid : OKTrusted certificates installed : OKTrusted certificates valid : OK_____________________________________________

See also Requesting Certificates for HP OMi on page 50.

ovcert –list

80 Appendix A


________________________________________________________________(Sample output)+-------------------------------------------------------+| Keystore Content |+-------------------------------------------------------+| Certificates: || 6073fd42-9326-7531-1b2d-cdab6fa099d4 (*) |+-------------------------------------------------------+| Trusted Certificates: || CA_14d14502-1671-7531-13d6-a06656d31bf3 |________________________________________________________________

4 On the HPOM system, verify if the HP OMi host system can communicate with HPOM (return value should be eServiceOk) by executing the following command:

bbcutil -ping https://<HPOMi-servername>


___________________________________________________________https://<HPOMi-servername>: status=eServiceOKcoreID=7c66bf42-d06b-752e-0e93-e82d1644cef8 bbcV=06.10.105appN=ovbbccb appV=06.10.105 conn=1 time=1094 ms___________________________________________________________

5 On the HP OMi system, verify if HPOM can communicate with the HP OMi host system (return value should be eServiceOk) by executing the following command:

bbcutil -ping https://<HPOM-servername>


___________________________________________________________https://<HPOM-servername>: status=eServiceOKcoreID=0c43c032-5c94-7535-064a-f7654a86f2d3 bbcV=06.10.070appN=ovbbccb appV=06.10.070 conn=7 time=140 ms___________________________________________________________

Empty the Black Box Communication Store and Forward Buffer on HPOM

Follow these steps to empty the BBC store and forward buffer:

1 In a command prompt or a shell window on the HPOM system, stop the HPOM server as follows:


cd %OVShareDir%/server/datafiles/bbc/snf/OvEpMessageActionServer/

vpstat -3 -r stop

— HPOM for UNIX:

/opt/OV/bin/ovc -stop SERVER

Emptying the BBC buffer deletes all messages, including those for other target systems.

Troubleshooting 81

2 Clean the BBC store and forward buffer by deleting all the files in the following location:


del *.*

— HPOM for UNIX:

cd /var/opt/OV/shared/server/datafiles/bbc/snf

rm *

3 Start the Message Action Server as follows:


vpstat -3 -r start

— HPOM for UNIX:

/opt/OV/bin/ovc -start SERVER

Verify the HP OMi Log Files

On the Gateway Server system, check the opr-gateway log files for any errors or logs as follows:

1 Change to the following sub-directory:

%TOPAZ_HOME%\log\mercury_wde

2 Open and check the following log files:

— The flowtrace log file opr-gateway-flowtrace.log. This log file is for the event flow on the Gateway Server. It contains every message or ID that arrives at HP OMi.

— The gateway log file opr-gateway.log. This is the log file for the HP OMi Gateway functionality.

On the Data Processing Server system, check the opr-backend log files for any errors or logs as follows:

1 Change to the following sub-directory:

%TOPAZ_HOME%\log\opr-backend

2 Open and check the following log files:

— The flowtrace log file opr-flowtrace-backend.log. This log file is for the event flow on the Data Processing Server. It contains every message or ID that is received from the backend.

— The backend log file opr-backend.log. This log file contains the log entries for the Data Processing Server.

Verify the Sonic Queue

Verify that the Sonic Queue opr_gateway_queue for HP OMi is created on the HP OMi system.

To make sure this queue has been created correctly, complete the following steps:

1 Make sure the BSM platform is running. If it is not running, start it first.

2 In the Create Connection dialog, accept the defaults and click OK.

3 In the tree view on the left, select AM_Cluster → Queues.

82 Appendix A

The new queue opr_gateway_queue should appear in the queue list.

4 If the queue opr_gateway_queue was not created, in the Sonic Management console, right-click:

AM_Cluster → Queues

5 Select New Queue from the context menu of the New Queue dialog box.

6 Enter the following data and click OK.

— Name = opr_gateway_queue

— Save Threshold = Use default value

— Maximum size = 2 million

7 Exit the Sonic Management console as follows:

Action → Exit

Troubleshooting 83

Verify the HP OMi Database Contents

To verify whether events are stored in the HP OMi database, follow these steps:

1 Open the Database table ALL-EVENTS.

2 Check whether events are stored in that table.

Message Forwarding Times Out on HPOM

A message forwarding connection on the HPOM server times out after 3600 seconds. If the HP OMi server is unavailable during this time, HPOM does not try to reconnect after one hour and messages are discarded.

Change Time Out on HPOM for Windows

To change the default settings on your HPOM for Windows management server, complete these steps:

1 In the HPOM for Windows management console, right-click the management server node in the node list.

2 Select Configure → Server.

3 Select Server-based Flexible Management from the Namespace drop-down list.

4 In the list, double-click the configuration item Forwarding delivery timeout (in seconds).

5 Enter a new value and click OK.

6 Redeploy the message forwarding policy you created in Configuring Message Forwarding Policies on page 54.

84 Appendix A

Change Time Out on HPOM for UNIX

To change the default settings on your HPOM for UNIX server, follow these steps:

1 In a shell window, execute the following command:

ovconfchg -ns agtrep -set ACTION_TIMEOUT <value>

2 Replace <value> with the new value (for example, 61) of the configuration item ACTION_TIMEOUT.

You can alternatively execute ovconfchg -edit, change the value of ACTION_TIMEOUT under the section [agtrep], and save changes in the editor File menu.

3 To review your changes, execute one of the following commands:

— ovconfget -ovrg server (shell view)

— ovconfchg -edit (editor view)

4 Redeploy the message forwarding policy you created in Configuring Message Forwarding Policies on page 54.

Synchronizing HP OMi Events with HPOM Messages Does Not Work

Synchronizing HP OMi events with HPOM messages does not work after you have configured the connection and the trust relationship between the two systems.

To make sure the event synchronization is enabled, complete the following steps:

Verify the Event Synchronization Settings


2 Start the BSM platform management console (for example, http://HPGwSrv.example.com/bsm).

3 After logging on to the BSM platform management console, open the Infrastructure Settings page as follows:


4 Select the Applications context.

5 From the Applications drop-down menu, select Operations Management.

6 In the Operations Management - HPOM Connection Settings section, set up the management server settings of HPOM.

7 Make sure the value of Server-Based Flexible Management is set to true.

8 Make sure the correct value of HPOM Host is set and the hostname can be resolved from the HP OMi system by executing the following command:

nslookup <fullDNSName of HPOM Server>

Verify the BSM Platform Hostname

Follow these steps to make sure the BSM platform hostname is set correctly:


2 Make sure you have activated JavaScript in your browser.

Troubleshooting 85

3 Start the BSM platform management console (for example, http://HPGwSrv.example.com/bsm).

4 After logging on to the BSM platform management console, open the Infrastructure Settings page as follows:


5 Under Foundations, select Platform Administration → Host Configuration.

6 Set the value of Default Virtual Centers Server URL to the fully qualified domain name of the BSM platform.

Verify the Black Box Communication Receiver

Make sure the Control daemon and Black Box Communication (BBC) used for communication between HPOM and HP OMi have started as follows:

1 On the HP OMi system, verify the communication by executing the following command:

ovbbccb -ping <HPOM node>

Example of a successful command result:

_______________________________________________________________tcpc125: status=eServiceOKcoreID=73d5f992-1325-7537-18be-c9b697a033b8bbcV=06.10.070 appN=ovbbccb appV=06.10.070 conn=7 time=391 ms _______________________________________________________________

If the BBC receiver is not running, perform the steps as described in Verify the Black Box Communication between HP OMi and HPOM on page 80.

86 Appendix A

Topology Synchronization Issues

This section provides you with troubleshooting steps relating to Topology Synchronization problems that may occur.

For details about the Topology Synchronization, see the section “Topology Synchronization” in the online help.

Web Service Fatal Error Message: Unauthorized

The Topology Synchronization may fail with the following error:

FATAL: Error occurred while accessing the web service: Unauthorized

In this case, verify the credentials (username and password) as follows:



3 From the menu, select Admin → Platform → Setup and Maintenance.

4 Click Infrastructure Settings.

5 Under Select Context, select Applications as a context.


7 In the Operations Management - HPOM Connection Settings section, verify and if necessary correct the username and password for the HPOM connection.

8 Click Save to save your changes.

Web Service Fatal Error Message: Connection Refused

Topology Synchronization may fail with the following error:

FATAL: Error occurred while accessing the web service: Connection refused: connect

In this case, verify the port and hostname as follows:







In the BSM platform management console, you can edit and change values by using the Edit Setting button on the right side of each entry.

HPOM Password: The password that you use for the HPOM connection.

HPOM User: The username that you use for the HPOM connection. If you are using a domain user account, make sure you prefix the username with the domain (for example, domain\username).

Troubleshooting 87

7 In the Operations Management - HPOM Connection Settings section, verify and if necessary correct the port and hostname for the HPOM connection.


Web Service Fatal Error Message: Not Found

Topology Synchronization may fail with the following error:

FATAL: Error occurred while accessing the web service: Not Found

In this case, verify the HPOM for Windows prerequisites and make sure you have installed the server patch.

HTTPS Fatal Errors

Depending on whether you have configured your server to allow https for the HPOM web service, Topology Synchronization may fail with the following errors:

HPOM for Windows Server as Peer

Fatal errors may occur according to the following cases:

• https is set to false (is off) but the server uses https:

FATAL: Error occurred while accessing the web service: Connection reset

or

FATAL: Error occurred while accessing the web service: Not Found

• https is set to true (is on) but the server uses http:

FATAL: Error occurred while accessing the web service: Unrecognized SSL message, plaintext connection?

HPOM for UNIX Server as Peer

Fatal errors may occur according to the following cases:

• https is set to false (is off) but the server uses https:

FATAL: Error occurred while accessing the web service: Unexpected end of file from server

• https is set to true (is on) but the server uses http:

FATAL: Error occurred while accessing the web service: Remote host closed connection during handshake

HPOM Type: To specify whether HPOM is an Operations Manager (OM) for Windows or for UNIX systems.

HPOM Host: Fully qualified domain name of the system hosting HPOM that HP OMi is using to gather performance metrics for the performance graphs.

HPOM Port: The port number to use when establishing a connection to HPOM (for example, 443 as a default for HPOM for Windows and 8444 as a default for HPOM for UNIX).

88 Appendix A

To change the https setting accordingly, follow these steps:







7 In the Operations Management - HPOM Connection Settings section, change the value to either false or true of the following setting:


Use HTTPS for the HPOM Web Service:

The default value is set to true, which means https is used to connect to HPOM (depending on whether you have configured your server to allow https for the HPOM web service).

Troubleshooting 89

Health Perspective Issue

Viewing the status in the Health Perspective's Topology Views and the report “KPIs Over Time” require that you specify a default profile database.

Carry out the following steps to define a default profile database on all the BSM platform server machines with an HP OMi instance.



3 From the menu, select Admin → Platform.

4 In the tab Setup and Maintenance, click Manage Profile Databases.

5 In the Database Management window, you can see if a default profile database already exists. If it does not, select either Oracle or MS SQL as the database you want to add as a default profile database.

6 Click Add and define a default profile database as follows:

a Select the checkbox Create database and/or tables.

Clear this option if a database already exists. In this case, you use an existing database as a default profile database.

b Select the option Make this my default profile database (required for custom data types).

c Enter the required database-related information and click Apply at the bottom of the window.

d Confirm this operation by clicking OK in the dialog warning you that if a default profile database already exists, it will be replaced.

90 Appendix A

— Example of the Oracle database:

— Example of the Microsoft SQL database:

Troubleshooting 91

92 Appendix A

B HP OMi Reference Information

This reference chapter describes the standard HP OMi installation locations. For details, see the following sections:

• Installation Locations on page 93

• Topology Synchronization Packages on page 94

• Log Files on page 94

Installation Locations

The HP OMi Installer installs the files in the following default locations:

• HP OMi-specific files: %TOPAZ_HOME%


You can also verify the registry key for this directory as follows:

My Computer → HKEY_LOCAL_MACHINE → SOFTWARE → Hewlett-Packard → OprBsm → InstallDir

• Shared HP Components

— %OvInstallDir%

Default: C:\Program Files\HP\HP BTO Software


My Computer → HKEY_LOCAL_MACHINE → SOFTWARE → Hewlett-Packard → HP OpenView → OvInstallDir

— %OvDataDir%

Default: C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software.


My Computer → HKEY_LOCAL_MACHINE → SOFTWARE → Hewlett-Packard → HP OpenView → OvDataDir

93

Topology Synchronization Packages

Topology Synchronization content packages or packs define what and how the topology data (for example, nodes, node groups, services) is synchronized.Topology Synchronization content packs (for example, HPOprOra for synchronizing Oracle CIs) are located on the Data Processing Server in subdirectories in the following folder:%TOPAZ_HOME%\conf\opr\topology-sync\sync-packages\

These Topology Synchronization packs are:

• default

• HPOprAds

• HPOprClu

• HPOprExc

• HPOprMss

• HPOprOra

• HPOprSys

• HPOprVir

• HPOprWbs

• HPOprWIs

• nodegroups

• operations-agent

Log Files

You can find the log files in the following folders:

• %TOPAZ_HOME%\log

• %OvDataDir%\log

• %TEMP%\

94 Appendix B

The HP OMi log files are listed in Table 1.

Table 1 HP OMi Log Files

Location and Name Description

%TOPAZ_HOME%\log\

opr-backend_boot.log

These are the startup and shutdown log files for the Data Processing Server.

%TOPAZ_HOME%\log\opr-backend_shutdown.log

%TOPAZ_HOME%\log\

opr-backend\opr-backend.log

This file contains the log entries for the Data Processing Server.

%TOPAZ_HOME%\log\opr-backend\

opr-flowtrace-backend.log

This is the log file for the event flow on the Data Processing Server. It contains every message or id that is received from the backend.

%TOPAZ_HOME%\log\EJBContainer\opr-admin.log

This is the log file for HP OMi administrator-specific tasks.

%TOPAZ_HOME%\log\EJBContainer\opr-common.log

This is the log file for the HP OMi base functionality.

%TOPAZ_HOME%\log\EJBContainer\opr-console.log

This is the log file for HP OMi web UI functionality

%TOPAZ_HOME%\log\EJBContainer\opr-flowtrace-common.log

This is the log file for the base event flow.

%TOPAZ_HOME%\log\mercury_wde\

opr-gateway.log

This is the log file for the HP OMi Gateway functionality.

%TOPAZ_HOME%\log\mercury_wde\

opr-gateway-flowtrace.log

This is the log file for the event flow on the Gateway Server. This file contains every message or id that arrives at HP OMi.

%OvDataDir%\log\System.txt This is the log file for the shared components.

%OvDataDir%\log\OMi.txt This is the log file for the HP OMi configuration scripts

%TEMP%\HPOvInstaller\

HPOpr_<version>\

This is the installation log file directory.

%TOPAZ_HOME%\log\opr-topologysync\opr-topologysync.log

These are the log files for Topology Synchronization.

%TOPAZ_HOME%\log\opr-topologysync\spring-framework.log

HP OMi Reference Information 95

96 Appendix B

C Starting and Stopping the BSM Platform

This reference chapter shows you how to start and stop the BSM platform.

Starting the BSM Platform

This section shows you how to start the BSM platform on all the BSM platform servers. That is, on each Data Processing Server and Gateway Server. For more details, see the HP

Follow these instructions to start the BSM platform and make sure it is running:

1 Start the BSM platform as follows:

Start → Programs (or All Programs) → HP Business Availability Center → Administration → Enable Business Availability Center

2 Make sure the BSM platform is running by checking its status as follows:

Start → Programs (or All Programs) → HP Business Availability Center → Administration → HP Business Availability Center Server Status

3 Log on to the status page as the BSM platform administrative user as shown in the following figure:

The BSM platform processes can take up to 30 minutes to start, depending on your hardware and network environment.

97

When all the processes are up and running, the status page responds with Server is READY as shown in the following figure:

98 Appendix C

Stopping the BSM Platform

This section shows you how to stop the BSM platform on all the BSM platform servers. That is, on each Data Processing Server and Gateway Server.

To stop the BSM platform and make sure that it is not running, follow these steps:

1 Stop the BSM platform as follows:

Start → Programs (or All Programs) → HP Business Availability Center → Administration → Disable Business Availability Center

2 Make sure the BSM platform is not running by checking its status page as follows:

Start → Programs (or All Programs) → HP Business Availability Center → Administration → HP Business Availability Center Server Status

3 Log on to the status page as the BSM platform administrative user.

The status page should respond with Server is not READY. In the Nanny section of the status page, you should be able to see a message saying Cannot check status.

Starting and Stopping the BSM Platform 99

100 Appendix C

D Topology Synchronization Tool

The HP OMi Topology Synchronization tool reads configuration item (CI) data from HPOM and writes it into the Universal Configuration Management Database (UCMDB).

The out-of-the-box Topology Synchronization is already properly configured when you configure HP OMi, and the HPOM nodegroups, nodes, and agents are synchronized in the UCMDB.

This reference chapter shows you how to use the tool and if necessary synchronize the Smart Plug-in service models by changing some of the HP OMi Topology Synchronization settings.

For more details about Topology Synchronization, see the HP Operations Manager i Concepts Guide available from the HP Software Product Manuals web site.

How to Use the Topology Synchronization Tool

You start the Topology Synchronization command-line tool as follows:


2 On the Data Processing Server, execute the following command:

%TOPAZ_HOME%\bin\opr-startTopologySync.bat

You can also start this tool as a scheduled task in Windows. The tool reads its required parameters from the BSM platform Settings Manager.

For details, see the sections “Topology Synchronization Command-Line Interface” and the “Settings Management” page of the HP OMi online help.

Synchronizing Smart Plug-in Service Models

To synchronize the Smart Plug-in service models, follow these steps:







101

7 In the Operations Management - HPOM Topology Synchronization section, verify and if necessary change the following HPOM Topology Synchronization settings:

— Packages used for Topology Sync:

Semicolon-separated list of packages used for the Topology Synchronization. These packages define what and how the topology data (for example, nodes, node groups, services) is synchronized.

The default settings are: default, nodegroups, and operations-agent.

You can find all the installed packages on the Data Processing Server machines in the following location:

%TOPAZ_HOME%\conf\opr\topology-sync\sync-packages

Specify all the packages for which you want to synchronize the Smart Plug-in service model.

For example, to synchronize the Oracle CIs and the Oracle Smart Plug-in service model, use the subdirectory name HPOprOra.

If you delete an entry from the list, the corresponding Configuration Items (CIs) are also removed from the UCMDB.

— Resolve IPs during synchronization:

Use this setting to enable IP resolution for nodes without IP address information in HPOM (default is false). Setting this to true has a negative impact on the synchronization performance.

8 Click the Edit Setting button on the right side of each entry and if necessary change its value.

The following figure shows the default content package values in addition to the HPOprOra package for the Oracle CIs and the Oracle Smart Plug-in service model:


102 Appendix D

Index

Aactive content, 21

Adobe Flash Player, 21

anti-virus software, 24

BBAC, 10

bi-directional event synchronization, 43

BSM platform, 10, 39Data Processing Server, 10Gateway Server, 10hostname, 85logging, 97post-uninstallation cleanup, 75starting, 97status page, 99stopping, 99

Ccertificates

configuring, 50granting, 50, 52load balancer, 52

changing the severity of an event, 64

configuration items, 53

configuringcertificates, 50Data Processing Server, 29Gateway Server, 38HP OMi, 29, 38message forwarding policy

UNIXactive, 61new, 60

Windowsactive, 58new, 54

Microsoft SQL Server, 35Oracle Database, 30

connecting HP OMi to HPOM, 43

content packs, importing, 41

Control daemon, 80

creatingMicrosoft SQL database, 35Oracle database, 30

Ddatabase

corrupt, 79supported products, 18

data directory, 93

Data Processing Serverconfiguring, 29content packs, 41definition, 10installing, 23log files, 82, 95Microsoft SQL Server, 35one-machine deployment, 14Oracle, 30packages, 94, 102populate UCMDB, 53requirements, 17starting BSM, 97stopping BSM, 99topology synchronization, 102topology synchronization tool, 101two-machine deployment, 15

defaultinstallation directory, 93profile database, 18

deploymentmulti-machine, 16one-machine, 14planning, 13two-machine, 15types, 13

disabling HP OMi, 69

Discovery and Dependency Mapping, 53

disk space, 17

Eenabling HP OMi, 70

103

Event Browser, 63

Event Management Foundation, 65

eventsseverity, 64synchronizing, 46, 54, 63, 64, 85troubleshooting, 80

Ffiles

corrupt, 78locations, 93, 94log, 95missing, 78

GGateway Server

adding to HPOM, 46, 49configuring HP OMi, 38connecting to HPOM, 43description, 10disabling HP OMi, 69enabling HP OMi, 70HP OMi service and process names, 39importing content packs, 41installing, 23log files, 82, 95policies, 55requirements, 17starting the BSM platform, 97stopping the BSM platform, 99troubleshooting BBC, 80two-machine deployment, 15uninstalling HP OMi, 71

GUI client, 21

Hhardware requirements, 17

health management, 53

Health Perspectivetroubleshooting, 90Views, 65

high availability, 16, 18

HPOMaccess information, 33adding a Gateway Server, 46, 49connections, 43creating new policies, 54definition, 10deploying policies, 57DNS name, 33event synchronization, 54forwarding delivery timeout, 84message forwarding

policy, 54verifying, 63

pending incoming requests, 52port number, 33request ID, 52SSL trust relationship, 46, 50supported versions, 19synchronizing events, 64user account, 33

HPOM for UNIXadding HP OMi as a node, 49granting certificates, 52setting up a policy, 60

HPOM for Windowsadding HP OMi as a node, 46granting certificates, 51, 52messages, 63pending certificate requests, 51

HP Operations Smart Plug-ins, 19

HP SiteScope, 20

Iimporting content packs, 41

installationdatabase corrupt, 79default directory, 93files corrupt, 78files missing, 78locations, 93overview, 11steps, 23troubleshooting, 78

JJava Runtime Environment (JRE), 21

104

Llicense

agreement, 25components, 65Event Management Foundation, 65expiry date, 68Health Perspective Views, 65host ID, 66installing, 67key delivery service, 66new key, 67permanent, 65properties, 68requesting, 66temporary, 65Topology-based Event Correlation, 65types, 65updating, 67viewing information, 68

Lightweight Single Sign-On Authentication, 18

load balancer, 52

load balancing, 16

log files, 94

Mmanage profile databases, 90

message forwardingtroubleshooting, 84verifying, 63

message forwarding policyon UNIX, 60

active policy, 61new policy, 60

on Windows, 54active policy, 58new policy, 54

message synchronization, troubleshooting, 85

Microsoft Active Directory SPI, 19

Microsoft Exchange Server SPI, 19

Microsoft Internet Explorer, 21

Microsoft SQL Server, configuring, 35

Microsoft SQL Server SPI, 19

Microsoft Visual C++ 2005 Redistributable, 23

Microsoft Windows Server 2003 Enterprise Edition, 17

multi-machine deployment, 16

Oone-machine deployment, 14

Oracle Application Server SPI, 19

Oracle Database, configuring, 30

Ppackages, 94

permanent license, 65

planning deployment, 13

platform, 10, 17

policy, 54, 60, 63, 69, 71, 84

process name, 39

profile database, 18

Rregistry key, 93

removingdatabase, 75log files, 75shared components, 75

requirementshardware, 17software, 17

Sscreen resolution, 21

service name, 39

severity, 64

shared components, 93

Smart Plug-insoverview, 19service model, 53synchronizing service models, 101

software requirements, 17

Sonic Queue, 82

starting the BSM platform, 97

stopping the BSM platform, 99

synchronizationevent, 46, 54, 63topology, 19, 33, 37, 53, 87, 88, 94, 95, 101, 102

synchronizingevents, 64, 85Smart Plug-in service models, 101

105

Ttemporary license, 65

time out, troubleshooting, 84, 85

topology-based event correlation, 53, 65

topology synchronizationconfiguration items (CIs), 101HPOM server, 33, 37log files, 95overview, 101packages, 94, 102populating UCMDB, 53settings, 102SPIs, 19, 88tool, 101troubleshooting, 87

topology views, 18

troubleshooting, 77Black Box Communication, 80, 86corrupt files, 78database contents, 84database corrupt, 79event synchronization, 80Health Perspective, 90HTTPS errors, 88installation, 78message forwarding, 80, 84message synchronization, 85missing files, 78Sonic Queue, 82synchronizing HPOMi events with HPOM

messages, 85time out, 84, 85topology synchronization, 87web service errors, 87

trust relationship, 50

two-machine deployment, 15

UUCMDB

populating, 53topology synchronization, 101

uninstallingBSM platform, 74HP OMi, 71

VVirtual Infrastructure SPI, 19

WWebLogic Application Server SPI, 19

web servers, 18

WebSphere Application Server SPI, 19

106