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.