Moviri Integrator for BMC Helix Capacity Optimization - HP BSM
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 Helix Continuous 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.
Requirements
Official name of data source software
- HP Business Service Management (BSM), formerly known as Business Availability Center (BAC)
Supported versions of data source software
- HP Business Service Management Version 9
Datasource Check and Configuration
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 BMC Helix Continuous Optimization 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 Settings table, locate:
- Maximum Rows. You can adjust this setting in accordance to enterprise’s HP BSM Administrators’ policies, “Moviri Integrator for BMC Helix Continuous Optimization – HP BSM” will be able to handle queries in chunks if needed.
- 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
General functioning of the Connector
“Moviri Integrator for BMC Helix Continuous Optimization – 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
The connector is able to extract volume, availability and performance (response times) measurements for both types of monitoring.
Connector configuration
There are two sections (tabs) in the ETL run configuration page where the behaviour of “Moviri Integrator for BMC Helix Continuous Optimization - HP BSM” can be specified:
- HP BSM EUM - Settings
- HP BSM EUM - Data Selection
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://<BSM server name>[:<port>]/<end_point>
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&query=select application_name as ApplicationName,transaction_name as TransactionName,AVG(tot_server_time) from rum_trans_t where time_stamp>=1304197200 and time_stamp<1306702800
HP BSM EUM - Data Selection
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 performance analyses needed in the BMC Helix Continuous Optimization 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…)
Blacklists and Whitelists
In addition to metric classes configuration, single entities can be configured to be explicitly included or excluded during the data processing.
- 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 BSM – EUM 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 |
| |
| Protocol | Selection | Yes | http |
|
Data Selection | |||||
HP BSM – EUM 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 BSM – EUM 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 BSM – EUM 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 |
| ||
Metrics Mapping
The table in the present section lists all the mappings between the BSM data model and BMC Helix Continuous Optimization entities and metrics.
- First level items are BSM applications mapped to BMC Helix Continuous Optimization “Web Business Driver”
- Second level entities (BMC Helix Continuous Optimization sub-resources) are:
- For RUM Pages: the page name if categorized by BSM RUM Engines, the page URL otherwise
- For RUM Transactions: the transaction name
- For BPM Transactions: the concatenation of transaction flow name (also called Business Process Profile) and transaction name
- Metrics with * were previously custom, remapped as standard after v 1.4.00
BSM Exposed Table | Expression on table column(s) | BMC Helix Continuous Optimization Metric | |
trans_t | application_id | DS_WKLDNM | |
trans_t | application_name | WKLDNM | |
trans_t | szBTFName+":"+szTransactionName | TRANNM | |
trans_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* | |
trans_t | avg(u_iWConnectionTime) | BYTRAN_CONNECT_TIME* | |
trans_t | avg(u_iSize) | BYTRAN_SIZE* | |
trans_t | avg(dResponseTime) | BYTRAN_RESPONSE_TIME | |
trans_t | avg(u_iWDnsTime) | BYTRAN_DNS_TIME_C | |
trans_t | avg(u_iWDownloadTime) | BYTRAN_DWNLD_TIME* | |
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_PASSED | |
trans_t | sum(Tot_minor_Hits) | BYTRAN_TOTAL_PASSED_WARN_C | |
trans_t | sum(u_iStatus) | BYTRAN_TOTAL_FAILED | |
trans_t | 'SYNTHETIC' | BYTRAN_TYPE* | |
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* | |
rum_trans_t | sum(availability) | BYTRAN_TOTAL_PASSED | |
rum_trans_t | avg(tot_client_time) | BYTRAN_CLIENT_TIME* | |
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* | |
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* | |
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* | |
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* | |
rum_action_t | avg(bytes_in) | BYPAGE_IN_SIZE* | |
rum_action_t | sum(total_hits) | WEIGHT | |
Lookup Fields
End User Monitoring data is modelled in BMC Helix Continuous Optimization by BSM Applications. For each BSM Application whose monitored performance and availability measurements are transferred into CO, a BMC Helix Continuous Optimization Business Driver (of type “Web business driver”) is created. RUM Pages, RUM Transactions and BPM Transactions are modeled as “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 (BMC Helix Continuous Optimization “Web business driver” corresponding to a “BSM Application”) loaded into CO. The value of the lookup field is the “BSM Application” Application ID.
Object Relationships
The ETL arranges the collected business drivers under a domain of choice.
BMC Helix Continuous Optimization automatically creates a hierarchy rule associated to the ETL to process the Object-Relationship data.
Comments
Log in or register to comment.