© 2008 Hewlett-Packard Development Company, L.P.The information contained herein is subject to change without notice.

Alon KoletJuly 2010

BSM 9 – Monitoring configuration

Objective

• Deep drill down into monitoring module

Out of scope• RUM configuration

What will we talk about

• Script parameterization - General• Availability threshold – General• TX and location renaming - General• EUM Admin configuration• Application configuration• BTF configuration• TX configuration• Hands on

Script parameterization - General• No need to edit the script with Vugen any

more• Create a script with parameters• Override the parameter values from EUM

Admin• Set different parameter values per location• Define Expiration date for parameters• The solution is limited for very specific

parameter types (file and table)

Availability threshold - General

• Defined for each TX.• Dictates the availability color that will be shown

on report for the TX depending on it’s availability• For example:

−You define

−This means that at least 9 our of 10 TX need to be completed with no availability problem

TX and location renaming - General

• Override the TX and location names from BSM• All data will be shown in the reports under the

renamed value−TX CI definition

−Location name in Location manager

EUM Admin configuration• Available trough: Admin > End User

Management• Shared configuration for BPM and RUM• Left view enables selecting specific view

from model explorer

• It also give you ability to add groups at several levels to the hierarchy

Application configuration• Allows different types of configuration

−CI Properties – CI name and description

−BPM configuration

−RUM configuration

−Alerts configuration

−Definition of location offset

Application configuration - BPM• BPM configuration

−Properties - General configuration

−Default settings – Default thresholds and breakdown config

−Data collectors – assignment of application to data collectors

−Reports configuration – Tx ordering and coloring

Application configuration - BPM• Properties

−General settings• Active/Inactive

• License type

• Link to Downtime manager

−BTF order• Relevant if

−BTF inherit application schedule

−Run mode classic/sequential or stepped (not concurrent)

−All BTF’s run on the same host

Application configuration - BPM• Properties

−Webtrace definition

−Script parameterization

−Baseline definition

Application configuration - BPM• Default settings

−Default TX thresholds

−Default TX breakdown

Application configuration - BPM• Data collectors

−Assignment of BPM hosts to applicationconfiguration

−Includes • Scheduler settings

• BTF’s

• Advanced setting

Application configuration - BPM• Reports Configuration

• TX ordering

• TX coloring

Application configuration – Alerts configuration• Alert definition for the application• Template definition

Application configuration – Location offset• Define offset for a specific location for all application config• Common usage: a location with slow connection• Shared for BPM and RUM

Application configuration – Location offset

• All locations can be defined under certain hierarchy−A location can propagate it’s offset to it’s children

• Example: All hosts from location “USA” have a slow connection.

The parent Location “USA” needs a “propagate” definition.

−A location can override the offset from it’s parent• Example: you need to define slow connection from the US

accept from FL that have fast connection (FL will override the offset that it got from “USA”)

BTF configuration• Allowed different types of configuration

−CI Properties – CI name and description

−BPM configuration

• BPM configuration−Properties - General configuration

−Data collectors – assignment of BTF to data collectors

BTF configuration - BPM• Properties

−General settings• Active/Inactive

−Script management• Add/remove script

• Update script version

• Edit script settings

−Assign script to BPM host

−View/Edit thresholds

−Apply breakdown configuration

−View/Edit script parameters

−Script ordering in a BTF (subject to same restrictions as in BTF ordering)

−Webtrace assignment – Same as in application

−Single TX script assignment – already demonstrated

BTF configuration - BPM• Properties

−TX performance and availability threshold

BTF configuration - BPM • Calculate suggested threshold

−Using existing data to define better thresholds

−Default is last 2 weeks

−Add the standard deviation to the average time

−2 views• Locations – TX view show all transactions in each

location

• TX – Location view – Show all locations for each TX

BTF configuration - BPM• Data collectors

−Define additional schedulers that are not part of the application scheduler

−Override application definition• Ability to revert to application config

TX configuration

• Offers the following configurations−CI Properties – CI name and description

−BPM configuration• Performance threshold

−locations overriding performance threshold

• Availability threshold

• Script containing TX

TX configuration• Calculate suggested threshold

−Using existing data to define better thresholds−Default is last 2 weeks−Different configuration per location−Add the standard deviation to the average time