moviri integration for bmc capacity optimization 1.2.03 - hp bsm - user's guide

8/21/2019 Moviri Integration for BMC Capacity Optimization 1.2.03 - HP BSM - User's Guide

1/20

Moviri S.p.A.

Via Schiaffino 11 - 20158 Milano - Italy

Phone: +39 02 495170 01, fax: +39 02 70059905

E-mail: [email protected]: www.moviri.com

Moviri Integration for BMC Capacity

Optimization - HP BSM Users Guide

Version: 1.2.03


2/20

Moviri Integration for BMC Capacity Optimization - HP BSM Users Guide

Moviri SpA HeadQuarterVia Simone Schiaffino, 11

20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower

One Market Street Suite 3500

San Francisco, CA 94105

USA

Website:www.moviri.com

Email: [email protected]

2/ 20

Moviri Integration for BMC Capacity Optimization - HP BSM

Users Guide

1 Overview of the Integration ...................................................................................................................... 3

2 Requirements ............................................................................................................................................ 4

3 Installation ................................................................................................................................................. 5

4 Datasource Check and Configuration ........................................................................................................ 9

5 Connector configuration .......................................................................................................................... 11

6 Troubleshooting ....................................................................................................................................... 14

7 Appendix A. Configuration and Business Metrics Mapping .................................................................... 15

8 Appendix B. Lookup Fields ....................................................................................................................... 17

9 Appendix C. Object Relationships ............................................................................................................ 18

10 Appendix D. Legal Notices ....................................................................................................................... 19
http://www.moviri.com/http://www.moviri.com/http://www.moviri.com/mailto:[email protected]:[email protected]:[email protected]://www.moviri.com/


3/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



3/ 20

1

Overview of the Integration

Moviri Integration for BMC Capacity OptimizationHP BSMis an additional component for the BMC

Capacity Optimization product.

It allows collecting information from HP Business Service Management (BSM) tool and it is able to extract

and summarize business KPIs associated with applications and business processes measurements.

All collected data can be managed using BMC Capacity Optimization, in order to:

Analyze business KPIs over the entire environment and in individual domains

Analyze and correlate business drivers metrics with performance data

Perform extrapolation analysis and evaluate service times.

Perform business drivers metrics forecasting

The connector supports configuration parameters that allow application, transaction flows, and business

drivers filtering, historical recovery, limiting data volume processed in a single run, specifying data

resolution and many others settings.

The documentation is targeted at BCO administrators, in charge of configuring and monitoring the

integration between BCO and HP BSM.


4/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



4/ 20

2

Requirements

2.1

Official name of data source software

HP Business Service Management (BSM)

2.2

Supported versions of BMC Capacity Optimization

BMC Capacity Optimization 4.5 - SP1 (4.5.00.01)

BMC Capacity Optimization 4.5 - CP1 (4.5.01.01)

BMC Capacity Optimization 4.5SP2 (4.5.02.00)

BMC Capacity Optimization 4.5SP2 (4.5.03.00)

BMC Capacity Optimization 9.0SP1 (9.0.01.00) and later Service Packs

BMC Capacity Optimization 9.5 (9.5.00) and later Service Packs

2.3

Supported versions of data source software

HP Business Service Management Version 9

For different version of data source software please contact Moviri (www.moviri.com)

or BMC Support (http://www.bmc.com/support).
http://www.moviri.com/http://www.moviri.com/http://www.moviri.com/mailto:[email protected]:[email protected]://www.moviri.com/http://www.moviri.com/http://www.moviri.com/http://www.bmc.com/supporthttp://www.bmc.com/supporthttp://www.bmc.com/supporthttp://www.bmc.com/supporthttp://www.moviri.com/mailto:[email protected]://www.moviri.com/


5/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



5/ 20

3

Installation

This section provides the information needed to download and install the Moviri Integration for BCO - HP

BSM additional component. The installation procedure is quick and easy, as it relies on the patching

mechanism provided by BCO under the section ADMINISTRATION >SYSTEM >Maintenance.1

3.1

Preparing for installation

Before you can install the service pack, you must have previously installed one of the versions of BMC

Capacity Optimizations listed in Section2.2.

3.2

Downloading the additional component

The Additional Component File can be downloaded from the BMC Electronic Product Distribution site2and

consists of the following archive:

Moviri Integration Version 1.2.03 for BMC Capacity Optimization - HP BSM.zip

3.3

Installing the additional component

To install the additional component, follow these steps:

1. Access the BCO Console

2. Navigate toAdministration > System > Maintenance activities

3. Upload the Additional Component File (as shown inFigure 1).

Figure 1: Upload Additional Component File

1Official documentation about this can be found in the BMC Capacity Optimization Administration Guide in PDF Format or online at

https://docs.bmc.com/docs/display/public/bcmco90/Maintenance2

http://www.bmc.com/support/downloads-patches
http://www.moviri.com/http://www.moviri.com/http://www.moviri.com/mailto:[email protected]:[email protected]://docs.bmc.com/docs/display/public/bcmco90/Maintenancehttps://docs.bmc.com/docs/display/public/bcmco90/Maintenancehttp://www.bmc.com/support/downloads-patcheshttp://www.bmc.com/support/downloads-patcheshttp://www.bmc.com/support/downloads-patcheshttp://www.bmc.com/support/downloads-patcheshttps://docs.bmc.com/docs/display/public/bcmco90/Maintenancemailto:[email protected]://www.moviri.com/


6/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



6/ 20

4. Read the End User License Agreement. If the terms are accepted, please click on the Yes, I Accept

button as shown inFigure 2: End User License Agreement andFigure 3: End User License

Agreement Acceptance)in order to proceed with the installation. Otherwise, the installation

procedure will stop.

Figure 2: End User License Agreement

Figure 3: End User License Agreement Acceptance


7/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



7/ 20

5. Select the BCO scheduler instances on which the additional component shall be installed. Although

it is possible to install it on any combination of BCO schedulers, it is suggested to perform the

installation on all ETL-Engines (i.e. their scheduler instances), so that tasks configured to use

"Moviri Integration for BCO - HP BSM" can be executed on any of them. Please do not install theadditional component on non-ETL Engine schedulers (e.g. BCO Application Server not installed in

AS+EE configuration)

Figure 4: Scheduler Instance selection

6. A successful execution will result in a green line in the Additional components table.

Figure 5: Successful outcome of the patching operation

7. It is possible (and recommended, in case of unsuccessful outcome, e.g. a yellow WARNING line) to

inspect the deployment log, which can be done by clicking on the icon highlighted in Figure 6.This

opens a new page in which the various executions are listed; for each of these lines the detailed log

(containing, when applicable, a backup version of any replaced files) can be downloaded (as shown

inFigure 7)


8/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



8/ 20

Figure 6: Access to ETL Deployment Log

Figure 7: Deployment Logs page


9/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



9/ 20

4

Datasource Check and Configuration

4.1

Preparing to connect to the data source software

In order to make data available to third party solutions, HP BSM provides a set of Web Service APIs which

enables various degrees of interaction with the tool.

The integration between BCO and HP Business Service Management takes advantage of the Generic Data

Engine Open API. This API can be configured directly in HP BSM user interface, section Admin > Platform >

Setup and Maintenance > Infrastructure Settings. Once in the section:

Select Foundations.

Select Generic Data Engine Open API.

In the Generic Data Engine Open API - Generic Data Engine Open API Settingstable, locate:

o Maximum Rows. You can adjust this setting in accordance to enterprises HP BSM

Administrators policies, Moviri Integration for BCO HP BSM will be able to handle

queries in chunks if needed.

o Enable Open API. Enable

The connector uses a BSM configured account to perform the data extraction. Such user must be granted

either of the following roles

System Viewer

Superuser

Figure 8 HP BSM Permissions

4.2

General functioning of the Connector

Moviri Integration for BCO HP BSM extracts End User Monitoring data from HP BSM. HP BSM performs

two types of end user monitoring:

Active, also called synthetic, with the usage of Business Process Monitors (BPMs): software robots

perform actions on monitored services at scheduled time interval from various location

Passive with the usage of Real User Monitors (RUMs): actual users transactions are collected using

network recording techniques


10/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



10/ 20

The connector is able to extract volume, availability and performance (response times) measurements for

both types of monitoring.


11/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



11/ 20

5

Connector configuration

There are two sections (tabs) in the ETL run configuration page where the behaviour of Moviri Integration

for BCO - HP BSM can be specified:

HP BSM EUM - Settings

HP BSM EUM - Data Selection

5.1

HP BSM EUM - Settings

The ETL needs the web service API URL in order to successfully connect to HP Business Service

Management.

The URL has the following format:

http://[:]/

Port can be typically omitted by default, since it is standard http 80 port. The default end point is

/topaz/gdeopenapi/services/GdeWsOpenAPI

API access can be tested with a standard browser composing an example query like the following:

http://yourserver/topaz/gdeopenapi/GdeOpenApi?method=getData&user=admin&password=password&q

uery=select application_name as ApplicationName,transaction_name as

TransactionName,AVG(tot_server_time) from rum_trans_t where time_stamp>=1304197200 and

time_stamp


12/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



12/ 20

5.2

HP BSM EUM - Data Selection

Figure 10 Data Selection

5.2.1 Metric Classes

The data extraction is configurable in terms of degree of information to be transferred from HP BSM. Eight

metric classes can be selectively enabled or disabled according to the depth of capacity and performanceanalyses needed in the BCO tool.

RUM Pages Basic: basic statistics on page volumes and performances (response time) for single

pages captured by BSM RUM Engines

RUM Pages Breakdown: response times breakdown in sub-components (network, server, client)

RUM Transaction Basic: basic statistics on transaction volumes, availability and performances

(response time) for single transactions captured by BSM RUM Engines

RUM Transaction Breakdown: response times breakdown in sub-components (network, server,

client)

BPM Availability Basic: basic statistics on transaction volumes and availability for single transactions

performed by BSM BPM Agents BPM Availability Breakdown: availability breakdown in terms of classification of measured response

time with respect to configured thresholds in BSM (good, warning, critical)

BPM Performance Basic: basic statistics on transaction performances (response time) for single

transactions performed by BSM BPM Agents

BPM Performance Breakdown: response times breakdown in sub-components (network, server,

client)

5.2.2 Blacklists and Whitelists

In addition to metric classes configuration, single entities can be configured to be explicitly included or

excluded during the data processing.


13/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



13/ 20

Application: BSM Applications

Page Name: Page Names as recognized by BSM RUM Engines

Page URL: Page URLs (used only if BSM RUM Engines cannot assign a Page Name to the tracked

page, i.e. Page Name = Unconfigured)

Transaction: Name of BSM or BPM Transaction Transaction Flow (Profile): Name of BPM Transaction Flow (also called Business Profile)

When specifying entities to be included wildcards can be used (e.g. Application like EComm*), while

entities to be excluded need to be fully specified (e.g. Transaction MyTransaction).

Section Property Name Value Type Required? Default Notes

BSM Connection

HP BSMEUM

Settings

HP BSM Host String Yes

Username String Yes

Password String Yes

Relative path to Generic

Data Engine Open API on

BSM host

String Yes Default end-point as

described in Par. 0

Data Selection

HP BSMEUM

Data Selection

Resolution Selection Yes 5 Minutes Data granularity to use to import data

(5min and Hour supported)

Default last counter String Yes Sets default timestamp to use when ETL

executed for the first time (or all

lastcounters are explicitly deleted)

Maximum number of days

for single task execution

Integer No -1 Sets the maximum time-interval to

import in a single extraction (since

lastcounter)

Metric Classes Selection Yes Sets which metric classes to import

Data Selection - Whitelists

HP BSMEUM

Data Selection

(advanced)

BSM Applications String No ; separated list of expressions that will

be used to restrict the scope of imported

entities. * wildcard is accepted (e.g.

Ecomm*)

RUM Page Names String No

RUM Page URLs String No

Transaction Names String No

Transaction Flows (Profiles) String No

Data Selection - Blacklists

HP BSMEUM

Data Selection

(advanced)

BSM Applications String No ; separated list of entities that are not

to be extracted by the connector.

Wildcards not accepted.RUM Page Names String No

RUM Page URLs String No

Transaction Names String No

Transaction Flows (Profiles) String No

Table 1: Configuration Properties

The configuration properties described apply to BCO version 9. Properties presented in BCO 4.5 are similar.


14/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



14/ 20

6

Troubleshooting

The status of the ETLs can be quickly verified from the list under ADMINISTRATION >SCHEDULER >ETL tasks,

as in Figure 16.

Figure 11 ETL List example

As shown in the online Administration Guide3, three exit statuses exist for BCO tasks:

OK - The ETL task completed successfully.

WARNING - It can be generated by a large number of causes (missing or corrupted data, etc.), for

which a complete stop of the ETL is not considered necessary.

FAILED - The ETL task was aborted, due for example to a network failure or a bad configured

parameter that could prevent an ETL from connecting to a database or mounting a network folder.

In case of a FAILED run, the log file can be accessed from the BCO web interface as shown in Figure below.

Figure 12 ETL Log

3

https://docs.bmc.com/docs/display/public/bcmco90/Managing+ETL+tasks
http://www.moviri.com/http://www.moviri.com/http://www.moviri.com/mailto:[email protected]:[email protected]://docs.bmc.com/docs/display/public/bcmco90/Managing+ETL+taskshttps://docs.bmc.com/docs/display/public/bcmco90/Managing+ETL+taskshttps://docs.bmc.com/docs/display/public/bcmco90/Managing+ETL+taskshttps://docs.bmc.com/docs/display/public/bcmco90/Managing+ETL+tasksmailto:[email protected]://www.moviri.com/


15/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



15/ 20

7

Appendix A. Configuration and Business Metrics Mapping

The table in the present section lists all the mappings between the BSM data model and BCO entities and

metrics.

First level items are BSM applications mapped to BCO Web Business Driver

Second level entities (BCO sub-resources) are:

o For RUM Pages: the page name if categorized by BSM RUM Engines, the page URL

otherwise

o For RUM Transactions: the transaction name

o For BPM Transactions: the concatenation of transaction flow name (also called Business

Process Profile) and transaction name

BSM Exposed

Table

Expression on table column(s) BCO Metric

trans_t application_id DS_WKLDNM

trans_t application_name WKLDNM

trans_t szBTFName+":"+szTransactionName TRANNMtrans_t avg(u_iWNetTime) BYTRAN_NETWORK_TIME_C

trans_t avg(u_iWFirstBufTime) BYTRAN_FRSTBUF_TIME_C

trans_t avg(u_iWRetryTime) BYTRAN_RETRY_TIME_C

trans_t avg(u_iWServerTime) BYTRAN_SERVER_TIME_C

trans_t avg(u_iWConnectionTime) BYTRAN_CONNECT_TIME_C

trans_t avg(u_iSize) BYTRAN_SIZE_C

trans_t avg(dResponseTime) BYTRAN_RESPONSE_TIME

trans_t avg(u_iWDnsTime) BYTRAN_DNS_TIME_C

trans_t avg(u_iWDownloadTime) BYTRAN_DWNLD_TIME_C

trans_t sum(Tot_ok_Hits) BYTRAN_TOTAL_PASSED_GOOD_C

trans_t sum(u_iStatus)+sum(Tot_ok_Hits)+sum(Tot_minor_Hits)+sum(Tot_critical_Hits) BYTRAN_TOTAL_HITS

trans_t sum(Tot_critical_Hits) BYTRAN_TOTAL_PASSED_CRIT_C

trans_t application_id DS_WKLDNM

trans_t sum(Tot_ok_Hits)+sum(Tot_minor_Hits)+sum(Tot_critical_Hits) BYTRAN_TOTAL_PASSEDtrans_t sum(Tot_minor_Hits) BYTRAN_TOTAL_PASSED_WARN_C

trans_t sum(u_iStatus) BYTRAN_TOTAL_FAILED

trans_t 'SYNTHETIC' BYTRAN_TYPE_C

trans_t sum(Tot_ok_Hits)+sum(Tot_minor_Hits)+sum(Tot_critical_Hits) WEIGHT

rum_trans_t application_id DS_WKLDNM

rum_trans_t application_name WKLDNM

rum_trans_t transaction_name TRANNM

rum_trans_t avg(tot_server_time) BYTRAN_SERVER_TIME_C

rum_trans_t sum(availability) BYTRAN_TOTAL_PASSED

rum_trans_t avg(tot_client_time) BYTRAN_CLIENT_TIME_C

rum_trans_t avg(tot_network_time) BYTRAN_NETWORK_TIME_C

rum_trans_t sum(total_hits)-sum(availability) BYTRAN_TOTAL_FAILED

rum_trans_t avg(tot_trans_size) BYTRAN_SIZE_C

rum_trans_t sum(total_hits) BYTRAN_TOTAL_HITS

rum_trans_t avg(tot_ndl_time) BYTRAN_RESPONSE_TIME

rum_trans_t 'REAL_USER' BYTRAN_TYPE_C

rum_trans_t sum(total_hits) WEIGHT

rum_action_t application_id DS_WKLDNM

rum_action_t application_name WKLDNM

rum_action_t action_name (action_descriptor if action_name = 'Unconfigured') PAGENM

rum_action_t avg(tot_server_time) BYPAGE_SERVER_TIME

rum_action_t avg(tot_client_time) BYPAGE_CLIENT_TIME

rum_action_t sum(availability) BYPAGE_TOTAL_OK

rum_action_t avg(tot_network_time) BYPAGE_NETWORK_TIME

rum_action_t avg(bytes_out) BYPAGE_OUT_SIZE_C


16/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



16/ 20

BSM Exposed

Table

Expression on table column(s) BCO Metric

rum_action_t sum(total_hits)-sum(availability) BYPAGE_TOTAL_ERROR

rum_action_t sum(total_hits) BYPAGE_TOTAL_HITS

rum_action_t avg(tot_dl_time) BYPAGE_RESPONSE_TIME

rum_action_t avg(bytes_in)+avg(bytes_out) BYPAGE_SIZE_C

rum_action_t avg(bytes_in) BYPAGE_IN_SIZE_C

rum_action_t sum(total_hits) WEIGHT

Table 2 Metrics Mapping


17/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



17/ 20

8

Appendix B. Lookup Fields

End User Monitoring data is modelled in BCO by BSM Applications. For each BSM Application whose

monitored performance and availability measurements are transferred into BCO, a BCO Business Driver (of

type Web business driver) is created. RUM Pages, RUM Transactions and BPM Transactions are modeledas Web business driver sub-resources.

The connector for HP BSM supports single lookup methodology, therefore a single DEFAULT lookup field

is set for each entity (BCO Web business driver corresponding to a BSM Application) loaded into BCO.

The value of the lookup field is the BSM Application Application ID.


18/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



18/ 20

9

Appendix C. Object Relationships

The ETL arranges the collected business drivers under a domain of choice.

BCO automatically creates a hierarchy rule associated to the ETL to process the Object-Relationship data.

Figure 13 : Hierarchy rule associated to ETL task


19/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



19/ 20

10

Appendix D. Legal Notices

10.1

Warranty

Moviri S.p.A. makes no warranty of any kind with regard to this document, including, but not limited to, the

implied warranties of merchantability and fitness for a particular purpose.

Moviri S.p.A shall not be held liable for direct, indirect, special, incidental or consequential damages in

connection with the furnishing, performance, or use of this material.

10.2

Copyright Notices.

Copyright 2010-2014 Moviri S.p.A, all rights reserved.

No part of this document may be copied, reproduced, or translated to another language without the prior

written consent of Moviri S.p.A.

The information contained in this material is subject to change without notice.

10.3

Trademark NoticesBMC Software, International Business Machines Corporation ("IBM"), Microsoft Corporation, Oracle

Corporation and the names of all their products referenced herein are registered trademarks of their

respective owners.


20/20



20158 Milan IT

T: +39 02 49517001 F: +39 02 70059905

Spear Tower



USA



*449810*

moviri integration for bmc capacity optimization 1.2.03 - hp bsm - user's guide

Documents