Wednesday, July 31, 2013
Thursday, July 18, 2013
HP BPM – How it works
The first thing you do is record a
representative user interaction/session against the applications you will be
monitoring - we call the output a “script”.
Scripts are usually recorded by
someone that has knowledge of the application like a business analyst, a line
of business expert or an application developer.
The key thing is to record the real
usage of some sort of business service in the same way it is expected to be
used by end-users.
There is usually more than one
interaction between the user and the applications being tested by a single script.
During the creation of the script,
the start and end points of important business service sub-steps are
noted. These subs-steps within the
script are called “transactions”. An example
for an online banking system may be… Login, Access Account, Transfer Funds,
Verify Account Transfer.
As part of a post recording effort,
the script it may be parameterized (password/accounts added, data field values
varied from a list) and data values of application output checked with known
good outcomes.
HP BPM can use scripts that were
created with either a) HP Virtual User Generator (HP VuGen),
or b) HP QuickTest Professional (HP QTP).
If your organization is already
using HP LoadRunner in pre-production area then your
application development team may already have scripts that you can leverage for
production monitoring.
The next step is to load the
scripts into the HP BSM script repository.
It is a simple task that is performed from a
browser.
NOTE : You can actually share the
Script Repository with HP LoadRunner so the scripts may already be available
to the production monitoring team.
Saturday, July 13, 2013
HP BPM how to movies
Hi,
Here is a list of some of the HP BPM "how to" movies that we have on youtube:
http://www.youtube.com/watch?v=CvpOQqRE03g
http://www.youtube.com/watch?v=m1r-ih4jVzs
Here is a list of some of the HP BPM "how to" movies that we have on youtube:
http://www.youtube.com/watch?v=BwRjpjSoFM4&list=PL71EB317F393707A1
http://www.youtube.com/watch?v=CvpOQqRE03g
http://www.youtube.com/watch?v=m1r-ih4jVzs
http://www.youtube.com/watch?v=QPtO4wtgYsA
Thursday, July 11, 2013
HP BPM Protocol Support
Early warning of actual customer experience issues with HP BPM
What if you had:
early warning of actual customer experience issues…
Early warning allows for a
pro-active response to minimize business impact.
Find application issues before
your users start using the application – by monitoring them 24x7.
… adequate information to prioritize those issues?
Is the issue isolated to one
application, a specific step? Is the
issue localized to one location?
What is the business impact
associated with an issue?
and detailed information in order to resolve them?
What was the application
error? Which step failed? Is it widespread?
Which component contributes to a
response time issue (network, server, transfer speed, DNS, etc.)?
This is what HP Business Process Monitor makes possible.
Need early warning of application performance and
availability issues
Early warning allows for a
pro-active response.
Test your services even outside
normal business hours before your customers expect the application to be
working.
Real User monitoring will only
catch issues if a user is actually using the application. Proactively validating the application availability on a regular basis gives you a
baseline and 24x7 monitoring capabilities.
Need adequate information to
prioritize issues
HP BPM can help you determine the
scope of the issue.
By associating a downtime cost to
your application can see the impact to the business over time.
SLA’s that are impacted by the
performance and availability are easily determined.
Need detailed information in order to resolve
HP BPM can capture what the user
saw (for web transactions). In general
the errors returned are captured.
Response time of transaction
sub-components is captured which greatly helps determine where the issue should
be assigned for resolution.
HP BPM integrates tightly with HP
Diagnostics and TransactionVision to isolate problems in application
sub-component level (queues, database, Java/.NET components, etc.).
Issues that we hear from customers like yourself where we
know that HP BPM can help….
IT is reactive to user complaints
of application performance. Customers are effectively being used as monitoring
tools and IT is the last to know of an outage or slowdown.
You want a reduction in the
number of help desk calls and escalation costs
Embarrassed to see systems
monitoring dashboard indicate “All Green” when users are still reporting
problems.
Application production issues
result in large teams spending too much time on conference bridges playing the
“blame game”
The business had a highly visible
outage and their user satisfaction ratings and image have suffered
Spending too much time isolating
the issue (issue ping-pongs between IT groups until the cause of
outage/slowdown is determined)
Application owner is demanding
Service Levels be managed at the business service level but all that IT is
monitoring is infrastructure health
Performance/availability
initiatives with a critical application
Reducing mean time to repair and
the associated downtime cost
Eliminating the need for costly
application specialists to do intitial triage on issues
Shortening application
implementation time with best practices and cooperation between production and
development
Wednesday, July 3, 2013
Subscribe to:
Posts (Atom)