bsm connector for ibm tivoli integration guide… · documentationupdates...

HP BSM Connector for Oracle EnterpriseManagerFor the Windows ® and Linux operating systems

Software Version: 01.00

Integration Guide

Document Release Date: May 2013

Software Release Date: May 2013

Integration Guide

HP BSMConnector for Oracle EnterpriseManager (01.00) of 30

Legal Notices

WarrantyThe only warranties for HP products and services are set forth in the express warranty statementsaccompanying such products and services. Nothing herein should be construed as constituting anadditional warranty. HP shall not be liable for technical or editorial errors or omissions containedherein.

The information contained herein is subject to change without notice.

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

Copyright Notice© Copyright 2013 Hewlett-Packard Development Company, L.P.

Trademark NoticesMicrosoft® andWindows® are U.S. registered trademarks of Microsoft Corporation.

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


Integration Guide

Documentation UpdatesThe title page of this document contains the following identifying information:

l Software Version number, which indicates the software version.

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

l 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 themost recent edition of a document, goto:

www.hp.com/go/livenetwork

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

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

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


Integration Guide

SupportThis document describes HP Live Network Community Content. Hewlett Packard Software doesnot test, certify or support Community Content. Please use the Community Content discussionforums on HP Live Network or contact the original submitter of the Community Content directly ifany support, configuration or usability questions arise. Please back up all appropriate files beforeapplying Community Content in your environment.


Integration Guide

ContentsContents 6

Introduction 7

Oracle EnterpriseManager Terms 8

Oracle EnterpriseManager Event Integration Overview 9

Oracle EnterpriseManager Topology Integration Overview 11

Deployment Overview 12

Installation and Initial Configuration 13

Connector for Oracle EnterpriseManager Installation 14

Topology Integration 14

Event Integration 15

Oracle Enterprise Manager Type Mappings 23

Event Integration - Oracle EnterpriseManager 11g Policy 23

Event Integration - Oracle EnterpriseManager 12c Policy 25

Topology Integration 26

CI TypeMapping 27

CI Attributes 27

Uninstallation 29

Uninstalling the Connector for Oracle EnterpriseManager from aWindows System 29

Uninstalling the Connector for Oracle EnterpriseManager from a Linux System 29

Remove theOracle EnterpriseManager Connector Pack 29

Remove Policies from BSMConnector 30


Chapter 1

IntroductionHP Business ServiceManagement Connector for Oracle EnterpriseManager enables you toestablish a link betweenOracle EnterpriseManager environments and HP Business ServiceManagement (BSM)Operations Management.

The Connector for Oracle EnterpriseManager is an add-on for the HP BSM Connector. Theconnector enhances the BSMConnector to provide the following Oracle EnterpriseManagerspecific functionality:

l Topology forwarding to BSM

l Event forwarding

This functionality enables you to consolidatemanagement data from Oracle EnterpriseManagerenvironments into an HP BSM Operations Management solution.

The Connector for Oracle EnterpriseManager provides integration for the following types of OracleEnterpriseManager environment:

l Oracle EnterpriseManager Grid Control 11g

l Oracle EnterpriseManager Cloud Control 12c

of 30HP BSMConnector for Oracle EnterpriseManager (01.00)

Oracle Enterprise Manager Termsl Oracle Enterprise Manager Grid Control 11g

EnterpriseManager Grid Control is Oracle's solution for managing Oracle Grid and theapplications running on it. EnterpriseManager also enables you tomanage single instances ofOracle Database, Application Server, or Collaboration Suite using standalone consoles.

l Oracle Enterprise Manager Cloud Control 12c

Oracle EnterpriseManager Cloud Control 12c is Oracle's enterprisemanagement software formanaging the Oracle technology stack—Oracle Databases, Middleware, Applications, Serversand Storage—across the enterprise. Oracle EnterpriseManager Cloud Control 12c is typicallyused in large organizations that need a central repository of Oracle installations. Such centralrepositories are used for management purposes as well as for day-to-day administration andmanagement activities by the database administrator (DBA) teams, as well as infrastructure,middleware and application teams.

l Notification Methods

NotificationMethods enable you to globally define different mechanisms for sendingnotifications. These include e-mail, SNMP traps, and running custom scripts. Once defined,NotificationMethods are used by Notification Rules to send notifications to administrators foralerts, policy violations or job status changes. Each administrator has Notification Rules definedas a preference.

l Notification Rules

Notification rules enable you to choose the targets and conditions for which you want to receivenotifications from EnterpriseManager. These notifications include e-mail, SNMP traps, andrunning custom scripts.


Integration GuideChapter 1: Introduction

Oracle Enterprise Manager Event IntegrationOverview

The Connector for Oracle EnterpriseManager requires an HP BSM Connector installation. HPrecommends that you install the Oracle EnterpriseManager and HP BSM Connector on seperatecomputers. However, if the Oracle EnterpriseManager Console runs on a computer with anoperating system that the BSM Connector supports, you can install the BSM Connector andOracleEnterpriseManager on the same computer.

The following figure shows an overview theOracle EnterpriseManager Enterprise Consoleintegration scenario.

Oracle EnterpriseManager provides theManagement Connector Framework to integrate theEnterpriseManager Console with enterprise frameworks such as BSM. Using theManagementConnector Framework, we can send SOAP-based alerts to BSM Connector endpoint. Thesemessages are received by the reportMonitorData endpoint of the BSM Connecter and processedand enriched with the capabilities of aWeb Service Listener policy. The Connector for OracleEnterpriseManager uses two operations – createEvent and updateEvent – to report new eventsand event updates into BSM:



The Connector for Oracle EnterpriseManager must be registered in the Oracle EnterpriseManagersystem using Oracle EnterpriseManager CLI tools. After registering, the connector can be used asa notificationmethod (type: Java Callback). This notificationmethod can be assigned to specificnotification rules to send such alerts (availability alerts, metric alerts, and so on) to BSM over theBSMConnector:



Oracle Enterprise Manager Topology IntegrationOverview

The Connector for Oracle EnterpriseManager uses a topology-only Database policy and Jythonscript capabilities to reflect the Oracle EnterpriseManager topology model into BSM.

The BSMConnector runtime executes the following SQL statement on the Oracle EnterpriseManager database in accordance with the policy settings.

Note: In the policy source settings, youmust specify a user with read-access to the tables:MGMT_TARGETS and MGMT_TARGETS_LOAD_TIMES.

The result is then processed by the policy's Jython script:

SELECTt.host_name,t.target_name,t.target_type,t.display_name,t.discovered_name,t.type_display_name,t.target_guidFROMmgmt_targets t,mgmt_targets_load_times tlt



WHERE(t.target_guid = tlt.target_guid AND tlt.first_metadata_load_time < (SELECTsysdate FROM dual)) OR 1 = 2ANDtlt.first_metadata_load_time > ${timeOfLastRun}LIMIT ${maxRowsToFetch}

The variable ${maxRowsToFetch} can be defined in the policy source settings. The value of thevariable ${timeOfLastRun} is stored internally, but the initial value can be also defined in the policy(Initial Enumerating Value). The Jython script parses data received from theOracle EnterpriseManager database and sends it to the RTSM topology database for creation or updating of CIs forthe following CI types: Computer, Oracle Database and Oracle TNS Listener.

Deployment OverviewDeployment makes use of the remotemonitoring capabilities of the BSMConnector, giving you theoption of installing your BSM Connector on a dedicated integration server. However, youmustextract, register, and configure the event integration components of the Connector for OracleEnterpriseManager package directly on the Oracle EnterpriseManager system (using OracleEnterpriseManager CLI and UI tools).



Chapter 2

Installation and Initial ConfigurationThe BSMConnector for Oracle EnterpriseManager installation package is installed on the BSMConnector host system. From here, you copy the Event Connector package corresponding to yourOracle EnterpriseManager version to the Oracle EnterpriseManager host system and register itinto Oracle EnterpriseManager using Oracle EnterpriseManager CLI tools.

After registering the Connector for Oracle EnterpriseManager within Oracle EnterpriseManager,the connector can be used as a notificationmethod (type: Java Callback). This notificationmethod can be assigned to specific notification rules to send such alerts (availability alerts, metricalerts, and so on) to BSM over the BSMConnector.

Installation and initial configuration of the Connector for Oracle EnterpriseManager involves thefollowing high-level steps, which are described in detail below:

Note: Youmust import the Oracle EnterpriseManager integration-related policy files to yourBSM Connector system.

1. Install HP BSMConnector 9.2x.

The Connector for Oracle EnterpriseManager requires an HP BSMConnector 9.2x installationon a supportedWindows or Linux operating system. Install the BSM Connector before youinstall the Connector for Oracle EnterpriseManager. The BSMConnector must be able toconnect to the computer running HP Business ServiceManagement version 9.2x or higher andintegrated into BSM.

2. Install the Connector for Oracle EnterpriseManager. For details, see "Connector for OracleEnterpriseManager Installation" on next page.

3. Integrate topology by importing the database policy into BSM Connector, configure it for yourOracle EnterpriseManager installation, and activate the policy. For details, see "TopologyIntegration" on next page.

4. Integrate events by configuring the Oracle EnterpriseManager control appropriate for yourOracle EnterpriseManager product version:

n Actions for Grid Control (11g)

n Actions for Cloud Control (12c)

For details, see "Event Integration" on page 15.


Connector for Oracle Enterprise ManagerInstallation

Install the Connector for Oracle EnterpriseManager on the same computer as the BSMConnectoras follows:

Note: The Connector for Oracle EnterpriseManager does not incorporate installation logging.To generate a log file during installation, use the following command appropriate for youroperating system:

Linux: rpm -Uvvh file.rpm > error.log 2>&1

Windows: msiexec /log <LogFile> <MSI>

l OnWindows, double-click one of the following files inWindows Explorer and complete the stepsdemanded by the installer wizard:

n On a 32-bit Windows operating system:

HPBsmIntOEM-01.00.xxx-32-release.msi

n On a 64-bit Windows operating system:

HPBsmIntOEM-01.00.xxx-64-release.msi

l On Linux, enter the following command:

rpm -Uvh HPBsmIntOEM-01.00.010-Linux2.6_64-release.rpm

Topology IntegrationTo integrate Oracle EnterpriseManager topology into BSM, complete the following step on yourBSM Connector host system:

1. Using the BSMConnector interface, import the database policy appropriate for your OracleEnterpriseManager version from<OvInstallDir>/installation/HPBsmIntOEM/policies/bsmc-db-topology/<versiondirectory>where <version directory> is either 11g or 12c.

2. Open the Database policy and navigate to the "Source" tab.

3. Replace the placeholders (<...>) as follows:

<hostname>: FQDN of your Oracle EnterpriseManager database host.


Integration GuideChapter 2: Installation and Initial Configuration

<port>: Port number of your Oracle EnterpriseManager database, for example, 1521.

<sid>: Database SID of your Oracle EnterpriseManager system, for example, emrep.

<user>: User with read access to your database.

4. Save your changes.

Tip: Check your connection settings by using the "Sample Data" capability.

5. Activate the policy.

Note: After activating the topology database policy for the first time, it could take several runsof the policy to collect all available CIs from Oracle EnterpriseManager. The database policyloads the information that has changed since the last run (based on the date value). If this datehas not been updated by the Oracle EnterpriseManager runtime in themeantime, the record isnot considered for update.

To accelerate the initial topology collection process, it is recommend to increase theFrequency value of the policy to, for example, 30minutes. After you have collected anduploaded all CIs into BSM, you can decrease the Frequency value to, for example, 12 hours.

Event IntegrationThe event integration requires you to configure the following Oracle EnterpriseManager controlappropriate for your Oracle EnterpriseManager product version:

l Optional: SSL Setup for Grid Control (11g)

l Actions for Grid Control (11g)

l Optional: SSL Setup for Cloud Control (12c)

l Actions for Cloud Control (12c)

Set Up the BSM ConnectorTo set up the BSM Connector, complete the following steps:

1. Using the BSMConnector interface, import theWeb service listener policy fromOvInstallDir>/installation/HPBsmIntOEM/policies/bsmc-ws-event.

2. Activate the policy.

SSL Setup for Grid Control (11g)If required, set up SSL for Grid Control (11g) by completing the following steps:



1. Obtain a copy of the CA certificate that the BSMConnector web server is using.

2. Copy the certificate to the system where Oracle EnterpriseManager is installed.

3. Determine the location of the JRE in the Oracle Home directory.

4. Open a commandwindow and navigate to the JRE bin directory.

5. Add the certificate to the cacerts keystore:

./keytool -importcert -keystore ../lib/security/cacerts -storepass changeit -trustcacerts -file <certfile> -alias bsmc_ca

6. Restart OMS by opening a commandwindow and run the following commands:

emctl stop oms

emctl start oms

Set Up Actions for Grid Control (11g)To set up actions for Oracle EnterpriseManager Grid Control (11g), complete the following steps:

1. Copy the HP_BSM_Connector.jar file from<OvInstallDir>/installation/HPBsmIntOEM/event-connector/11g to your OracleEnterpriseManager host system.

2. Execute the following command-line calls to register the event connector with OracleEnterpriseManager.

Note: Replace <SYSMAN_PWD>with the appropriate SYSMAN password.

Replace <OMS_HOME>with the appropriate value used in your Oracle EnterpriseManagerinstallation, for example, /u01/app/oracle/middleware/oms11g.

The emctl tool is usually located in the<OMS_HOME>/bin directory of your OracleEnterpriseManager installation, for example:

/u01/app/oracle/middleware/oms11g/bin .

a. Extract the JAR Archive

This call extracts the content of the JAR archive to <OMS_HOME>/sysman/connector/HP_BSM_Connector.

emctl extract_jar connector -jar HP_BSM_Connector.jar -cname "HP BSMConnector"

b. Register the Connector



emctl register_connector connector -dd <OMS_HOME>/sysman/connector/HP_BSM_Connector/HPBSMConnector.xml -repos_pwd <SYSMAN_PWD>

c. Register the 'createEvent' Templates

emctl register_template connector -t <OMS_HOME>/sysman/connector/HP_BSM_Connector/createEvent_request.xsl -repos_pwd <SYSMAN_PWD> -ctname "HP BSMConnector" -cname "HP BSM Connector" -iname createEvent -tname "CreateEvent Request Transformation" -ttype 2 -d "Create Event RequestTransformation"

emctl register_template connector -t <OMS_HOME>/sysman/connector/HP_BSM_Connector/createEvent_response.xsl -repos_pwd <SYSMAN_PWD> -ctname "HPBSM Connector" -cname "HP BSM Connector" -iname createEvent -tname"Create Event Response Transformation" -ttype 1 -d "Create Event ResponseTransformation"

d. Register the 'updateEvent' Templates

emctl register_template connector -t <CONNECTOR_HOME>/updateEvent_request.xsl -repos_pwd <SYSMAN_PWD> -ctname "HP BSM Connector" -cname "HPBSM Connector" -iname updateEvent -tname "Update Event RequestTransformation" -ttype 2 -d "Update Event Request Transformation"

emctl register_template connector -t <CONNECTOR_HOME>/updateEvent_response.xsl -repos_pwd <SYSMAN_PWD> -ctname "HP BSM Connector" -cname"HP BSM Connector" -iname updateEvent -tname "Update Event ResponseTransformation" -ttype 1 -d "Update Event Response Transformation"

3. After you have successfully run the commands:

a. Log on to your EnterpriseManager console, and navigate to: Setup > ManagementConnectors.



b. Click theConfigure ( ) icon of the HP BSMConnector entry.

c. Enter the hostname and port of your HP BSMConnector 09.2x system and specify theadministrator credentials.

d. Click OK to save the changes.

4. Navigate toPreferences > Rules and assign the new notificationmethod to the desired rules:



a. Click Assign Methods to Multiple Rules and from theView dropdown list, select ByMethod.

b. Select the rules you want to integrate with the event connector.

5. Make sure that your rules also send UP and Clear notifications. To check this:

a. Navigate toPreferences > Rules.

b. Select a rule and click View.

c. In theAvailability sectionmake sure that Up andDown have the valueYes.

d. In theMetrics section, make sure that all your metrics send the severity states Critical,Warning, andClear.



6. Log on to your BSM Connector and activate theWeb Service Listener policy from the userinterface.

SSL Setup for Cloud Control (12c)If required, set up SSL for Grid Control (12c) by completing the following steps:

1. Enter the following command to extract the CA certificate from the BSMConnector web serverkeystore to bsmc_ca.cer certificate file:

keytool -exportcert –rfc -alias <alias> -file bsmc_ca.cer -keystore <path_to_keystore> -storepass <keystore_pass>

2. Copy the certificate to the system where Oracle EnterpriseManager is installed.

3. Append the contents of the bsmc_ca.cer file to:

$INSTANCE_HOME/sysman/config/b64LocalCertificate.txt

Note: Ensure that only the following is appended to the b64LocalCertificate.txt file.Do not include blank lines, comments, or any other special characters.

-----BEGIN CERTIFICATE-----<<<Certificate in Base64 format>>>-----END CERTIFICATE-----



4. Restart OMS by opening a commandwindow and run the following commands:

emctl stop oms

emctl start oms

Configuring the Cloud Control (12c)To configure the Oracle EnterpriseManager Cloud Control (12c), complete the following steps:

1. Make sure that Oracle EnterpriseManager Software Library is configured, and, if you do nothave a valid Oracle Support account, set Patching to Offline.

2. Copy the HP_BSM_Connector.zip file from<OvInstallDir>/installation/HPBsmIntOEM/event-connector/12c to your OracleEnterpriseManager host system.

3. Execute the following command-line calls to import the HP_BSM_Connector.zip file:

emcli login -username=SYSMAN

emcli import_update -file="path/to/HP_BSM_Connector.zip" -omslocal

4. Log on to your Oracle EnterpriseManager web-console and navigate toSetup > Extensibility> Self Update.

5. Click the type:Management Connectors.



6. Select theHP BSM Connector and click Apply.

7. Navigate toSetup > Extensibility > Management Connectors.

8. Create a new connector by selectingHP BSM Connector for Oracle Enterprise Manager1.0 from the drop-down list, then click Go.

9. In the wizard that opens, enter the required information, then select the new HP BSMConnector from the list and click Configure.

10. Enter the required information:

n Enter the hostname and port of your HP BSMConnector 09.2x system.

n Optional: Enable the "Retry" option and an expiration time.

11. Click OK.

12. Navigate toSetup > Incident > Incident Rules.

13. Edit or create a new Rule Set and use your newly created Event Connector to forward events.

Note: Refer to the Oracle EnterpriseManager 12c documentation for information oncreating rule sets and rules.

.



Chapter 3

Oracle Enterprise Manager Type MappingsThe following sections describe the typemappings used in the Connector for Oracle EnterpriseManager:

l "Event Integration - Oracle EnterpriseManager 12c Policy" on page 25

l "Event Integration - Oracle EnterpriseManager 11g Policy" below

l "Topology Integration" on page 26

l "CI TypeMapping " on page 27

l "CI Attributes" on page 27

Event Integration - Oracle Enterprise Manager 11gPolicy

Defaults

Policy Attribute OEM Event Attribute Mapping

Title Message

Severity Severity <$MAP(mapSeverity)>

TimeCreated CollectionTime

Node TargetHost

Related CI TargetHost

Event Drilldown URL EventPageURL

Event Key EventGuid

Send with close status true or false based onSeverity

<$MAP(map_CLOSE_Severity)>

Source Event ID EventGuid


Rules

Rule ETI Mapping

Host Availability: CPUUtilization (%)

CPULoad <$MAP(map_ETI_CPULoad)>

Host Availability: RunQueueLength (5minute average)

CPURunQueue <$MAP(map_ETI_CPURunQueue)>

Host Availability: MemoryUtilization (%)

MemoryLoad <$MAP(map_ETI_MemoryLoad)>

Host Availability: SwapUtilization (%)

SwapUsageLevel <$MAP(map_ETI_SwapUsageLevel)>

Host Availability: NetworkInterface Combined Utilization(%)

InterfaceUtilization <$MAP(map_ETI_InterfaceUtilization)>

Host Availability: FilesystemSpace Available (%)

HostDiskUtilization <$MAP(map_ETI_HostDiskUtilization)>

Database Availability: Status DatabaseServerStatus <$MAP(map_ETI_DatabaseServerStatus)>

All ETI mappings are based on the Severity event attribute of Oracle EnterpriseManager. A givenseverity value should bemapped to the correct value of an ETI.

Note: All other rules do not set an ETI. They only attempt to relate the event to thecorresponding CI in RTSM.


Integration GuideChapter 3: Oracle EnterpriseManager TypeMappings

Event Integration - Oracle Enterprise Manager 12cPolicy

Defaults

Policy Attribute OEM Event Attribute Mapping

Title Message

Severity Severity <$MAP(mapSeverity)>

TimeCreated ReportedDate

Node TargetHost

Related CI TargetHost

Event Drilldown URL EventURL

Event Key EventID

Send with close status true or false based onSeverity

<$MAP(map_CLOSE_Severity)>

Source Event ID EventID

Rules

There are no specific rules setting ETIs



Topology Integration



CI Type MappingOracle Enterprise Manager Type RTSM Type

Host (host) Computer (host_node)

Listener (oracle_listener) Oracle TNS Listener (oracle_listener)

Database Instance (oracle_database) Oracle Database (oracle)

The value in brackets is the internal name of the corresponding subsystem.

Relationships

From To Type

host_node oracle_listener composition

host_node oracle_database composition

host_node ip_address containment

CI AttributesThe following CI attributes are set in the Jython script. If you want to expand the number ofattributes, modify the Jython script in the connector Database policy.

Listener Attributes

RTSM Attribute OEM Attribute/Value

discovered_product_name target_name

listener_name target_name

name target_name

user_label target_name

application_category "Database Listener"

monitored_by "BSM Connector"

"Oracle EnterpriseManager"



Database Attributes


discovered_product_name target_name

name target_name

user_label target_name

database_dbtype "Oracle"

application_category "Database"



Computer Attributes


primary_dns_name target_host

name Short form of target_host

display_label Short form of target_host





Chapter 4

UninstallationUninstalling the Connector for Oracle EnterpriseManager requires you to complete the stepsappropriate for your host operating system.

Uninstalling the Connector for Oracle EnterpriseManager from a Windows System

To uninstall the Connector for Oracle EnterpriseManager from aWindows BSMConnector hostsystem, complete the following steps:

1. Go toStart > Control Panel > Uninstall a program.

2. Right-click the Connector for Oracle EnterpriseManager entry and select Uninstall.

The Connector for Oracle EnterpriseManager software is removed from your system.

Uninstalling the Connector for Oracle EnterpriseManager from a Linux System

To uninstall the Connector for Oracle EnterpriseManager from a Linux BSMConnector hostsystem, enter the following command:

rpm -e HPBsmIntOEM

The Connector for Oracle EnterpriseManager software is removed from your system.

Remove the Oracle Enterprise Manager ConnectorPack

Grid Control (11g)TheOracle EnterpriseManager connector pack that was imported into Oracle EnterpriseManagerin "Event Integration - Oracle EnterpriseManager 11g Policy" on page 23 should bemanuallyremoved as follows:

1. Login to your OEMweb-console and navigate to:

Setup > Management Connectors

2. Select HP BSM Connector and click Delete.


Cloud Control (12c)TheOracle EnterpriseManager connector pack that was imported into Oracle EnterpriseManagerin "Event Integration - Oracle EnterpriseManager 12c Policy" on page 25 should bemanuallyremoved as follows:

1. Login to your OEMweb-console and navigate to:

Setup > Extensibility > Self Update

2. Click on typeManagement Connector.

3. Select HP BSMConnector and click Actions > Remove.

4. Select HP BSMConnector and click Actions > Delete.

5. Navigate toSetup > Extensibility > Management Connectors.

6. Select HP BSM Connector and click Delete.

Remove Policies from BSM ConnectorPolicies that weremanually imported into BSM Connector during configuration of the OracleEnterpriseManager integration should be deactivated and removed from the BSMConnector.


Integration GuideChapter 4: Uninstallation

bsm connector for ibm tivoli integration guide… · documentationupdates...

Documents