Defining QoS Data Points Within E2E Scripts

Document ID : KB000057283
Last Modified Date : 14/02/2018
Show Technical Document Details

 

Summary: 

This article describes the best practices for adding multiple QoS checkpoints to a single E2E script.

Background:  

By default, Nimsoft E2E scripts allow users to save Quality of Service (QoS) messages to the backend for reporting purposes by selecting a checkbox within the profile properties for the script. This checkbox is fine if the user plans to store data for a single time period or single step such as the length of time it takes to login to a site, however once the user introduces multiple steps they’ll have to manually modify the script with the functions and changes described below.

Instructions: 

To make things easy, try to place comments in each section where you plan to setup new time periods.

Example:

===================================
‘’Begin Recording

‘’Stop Recording
===================================

Additionally, try to add a little detail to each comment, this way you know exactly what data you plan to store for QoS reporting – this will also be extremely helpful when declaring variables.

Example:

===================================
‘’Begin Recording: WebPageNameLogin

‘Stop Recording: WebPageNameLogin

‘’Begin Recording: WebPageNameQuery

‘Stop Recording: WebPageNameQuery
===================================

These place markers will make it much easier to assess the script and visually locate where you’d like to place each timer.

Ensure that the script you’re working with is either located in the E2E Script directory (C:\ Program Files\Nimsoft\e2e_scripting\scripts\) or else you’ll have access either locally or via UNC to the NimBUS functions (NimBUS-functions.src) your script will need to reference. The example below assumes your script was designed within the default E2E Script path.

Example:

===================================
include "Nimbus-functions.src"
===================================

Assuming you added detailed comments into the script, you’re now ready to declare your variables based off those comments – these variables will be used for the QoS records in the database.

===================================
include "Nimbus-functions.src"
target1$ = "WebPageNameLogin"
target2$ = "WebPageNameQuery"
===================================

Before you’re ready to begin starting the timer, you first have to initialize the NimBUS SDK components using niminit () – this should appear after you declare the variables but before your first function.

Now, for each place where you’ve defined a Stop/Start period for your time markers, you must add the following:

Begin Example:

===================================
‘’Begin Recording: WebPageNameLogin
nimQoSStart()
===================================

Stop Example:

===================================
nimQoSStop()
nimQoSSendTimer(Target1$)
===================================

Once you’ve completed adding each of the aforementioned components to your script, you must finish by using nimend which unloads the Nimsoft components and releases the memory – post this at the very end of the script. the 'end()' is optional.

Example:

===================================
nimend()
end()
===================================