Tuesday, August 27, 2013

The BSM 9 movie

Business Process Monitoring for mobile - best practices for you

New post from HP.

http://h30499.www3.hp.com/t5/Business-Service-Management-BAC/Business-Process-Monitoring-for-mobile-best-practices-for-you/ba-p/6171311#.UhzCSxsRClY


In rapidly changing and complex IT environments, monitoring of mobile application performance can be quite challenging task. HP Business Process Monitor (BPM) provides a quick and easy solution to deliver the visibility on your mobile application performance. Mobile application performance can be measured by HP BPM from multiple internal or external locations. Monitoring locations can be extended by the HP SaaS hosted global Points-of-Presence (PoP). These PoP's include mobile transaction monitoring Over-the-Air (OTA), which then will capture the impact of mobile carrier network (latency per carrier) to the end user response times. All BPM measured monitoring data can be reported in various perspectives, clearly indicating per application, user, location or SLA performance.   

HP BPM is an application performance management solution which runs monitoring scripts recorded by a Virtual User Generator (VuGen). The document in this blog provides best practices for using VuGen to record mobile native applications for BPM. The document provides general best practices, as well as explanations how to utilize a number of emulators in script creation. The document also provides a brief description of how to record scripts using the MobileTrue client protocol. Both of these recording technologies are supported by HP LoadRunner and HP Performance Center, so customers can seamlessly integrate the mobile application testing and monitoring solutions and reuse scripts from application performance test phase in production monitoring.

A typical mobile app (HTTP/HTML) uses protocols which enable you to develop scripts using mobile devices
or device emulators that communicate with servers over HTTP. It is easy to record network traffic to a
capture file (PCAP file) and create a VuGen script, or alternatively mobile emulator on your VuGen
machine can be used to develop monitoring scripts. Many mobile device emulators are available on the internet sites. Correct emulator version needs to be installed (supported by your application) and secure match to system requirements for each emulator software used. There is more information in the attached documenton on the best practices for mobile script creation.

Thursday, July 18, 2013

HP Business Service Management (BSM) 9.22 What’s New (link)

http://serdarzeybek.com/post/52856690153/hp-business-service-management-bsm-9-22-whats-new

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.