The best way to see how AppLoader works is to start using it. Below is a step by step guide to running your first load test. The steps are:
1. Install AppLoader:
There is a single installer for all the components of AppLoader. During install, select the components that you wish to install.
For your first load test, we recommend that you install the following on a Microsoft Windows PC:
- AppLoader console
- AppLoader Session Initiator (SI)
- Reporter
Then install on a Microsoft Windows Server (with Terminal Server):
- AppLoader Station
Open the Reporter (it should open by default after installation).
Get your activation license: Please follow the instructions at the top for obtaining your license. (Email the Hostname/IP Address to info@nrgglobal.com)
2. Open sessions for the AppLoader Stations and set up RDP connection to Stations in Terminal Server:
- Start the Console.
- Start the Session Initiator.
- Specify the IP Address / Hostname for the Terminal Server:
- Specify the User Settings:
-
You can input parameters manually:
-
You can input parameters from CSV file:
The file must be in the following format:
User,password,domain,hostExample:
user001,zebra,mydomain.com,192.168.0.18
Using a CSV file allows sessions for different hosts to be initiated in the same Session Initiator window.
Note:
All values must be specified for each row in the CSV file.
- RDP Settings (default usually OK)
- Open sessions:
Click on initiate and select Initiate sessions.
Number of Sessions: This is the number of sessions that will be initiated on TS Server Launch Delay (seconds): This is the interval between initiating subsequent sessions
(If 5 sessions are specified then you should see 5 windows open in Session Initiator and 5 stations connected in the Console)
-
Session Initiator input parameters can be saved by going to File -> Save Session Initiator. File will be saved in your ~ Chroniker Installation Folder ~ /AppsLoader/Initiator/ with .sin extension.
-
The file can be loaded back anytime by going to File -> Open Session Initiator.
- Maximize one window in Session Initiator and you should see Scenario Station loaded
- Build a simple scenario using Notepad
- Launch notepad. (When launching a program that is not in the Windows Path, please browse and select the executable file; for example, if you need to launch Internet Explorer then select iexplore.exe from C:\Program Files\Internet Explorer\iexplore.exe)
- Type “This is a test”
- Add Wait for 5 seconds
- Close Notepad
- Save Scenario and send to Console
- Saved file can be located on the machine where AppLoader Station is running
< ~ Your Douments and Settings Path ~ >\My Documents\AppLoader Station\script\< ~ Scenario Folder ~ >\
and Sent file to Console can be located on the machine where Console is running
< ~ Your Chroniker Installation Path ~ > \Chroniker\AppsLoader\Console\scenariostore
- Hit the Play button
in the console toolbar or right click the scenario of interest and select play. Multiple stations can be selected by holding CTRL or SHIFT
In the window that opens, specify the scenario, launch delay and loops to run.
4. Send scenario to all the AppLoader Stations
- Go to Console
- Highlight the stations that you want to run the scenario.
- Click the Send button
on the toolbar. - Choose the notepad scenario from the dropdown
- During send process, all console features are disabled. However, as the scenario is transferred to each station, the Last Playback Message column for each station will be updated to indicate if the scenario transfer was successful.
5. Run the Load test
- On the console, pull down the Load Test menu and check “Generate Results”
- New Load Test: Enter the name of this test as you wish it to appear in the Reporter (if no name is specified, then default name “LoadTest_date” will be used)
- Hit the Play button in the console toolbar
- You will see the scenarios playing in the Session Initiator and the status “Playing” in the Console
- Go to the Reporter.
- Click on the test name
- See how load affects the response time of the scenario and its transactions.
- Go to reports to see the reports
- To view the effect of the load variance on the back end components (servers, database, network components), you can set up Chroniker SystemWatch, NodeWatch, and SNMPwatch for these and run the load test again.