This example illustrates the relationship between
Performance Manager monitors and transactions; and
Silk Performer projects, scripts, user groups, and transactions
Note: Not all monitors are built on
Silk Performer scripts (for example,
Silk Test scripts, simple URL checkers).
The example monitor contains the following assets:
- Silk Performer project:
project1.ltz
- This project includes the following scripts:
script1.bdf,
script2.bdf
- script1.bdf has the following
Silk Performer user groups:
vuser1,
vuser2
- vuser1 has the following
Silk Performer transactions associated with it:
trans1,
trans2
script1.bdf:
dcluser
user
vuser1
transactions
trans1 : 1;
trans2 : 1;
user
vuser2
transactions
trans3 : 1;
A
Silk Test monitor specifies:
- Silk Performer project: project1.ltz
- Silk Performer script: script1.bdf
- Silk Performer user group: vuser1
- Silk Performer transactions: trans1 and/or trans2 (equates to
Silk Test transaction trans1 and/or trans2)
A second
Silk Test monitor might specify:
- Silk Performer project: project1.ltz
- Silk Performer script: script1.bdf
- Silk Performer user group: vuser2
- Silk Performer transactions: trans3 (equates to
Silk Test transaction trans3)
A monitor for a simple e-commerce site might consist of three simulated user transactions:
- A first transaction simulating a user purchasing a product
- A second transaction simulating a user who searches for a product, but does not make a purchase
- A third transaction might simply confirm the availability and accuracy of the home page.
Taken together three such transactions could effectively test a system's health. A monitor for a more complex system would
require more transactions.