PureLoad Runner
January 2015
support@pureload.com
PureLoad Runner
|
|
| PureLoad
5.2 January 2015 |
http://www.pureload.com support@pureload.com |
PureLoad Runner is a server process that can be used from a Java
based client to control a PureLoad load execution, without the
need for the PureLoad Console (graphical user interface). Before
starting the Runner you should have Naming, Taskspace and Manager
processes started.
Also note that PureLoad Enterprise edition is required to use the
Runner.
The Runner is started in the same way as other PureLoad Servers. For example on a Linux machine:
| % bin/runner 15:49:57 INFO - server started: /127.0.0.1:1999 15:49:57 INFO - Connected to naming server: 192.168.8.1:1099 15:49:57 INFO - Runner Server started: Type: Runner Server Version: PureLoad 5.1b2 Host: localhost IP Address: 127.0.0.1 PNC Port: 1999 |
In this case the Runner server is listening on
host: localhost and port: 1999. This can be
controlled by editing bin/pureload.properties (see
System
Properties).
When the Runner is started you can test that the
communication works by using the runnercmd test
program:
| % ./bin/runnercmd localhost 1999 running false |
This shows that communication with the Runner
works as expected (the server response "false"
meaning that there are no test currently running).
The Runner Java API is used to communicate with the Runner server
that drives the test. The Runner server will communicate with the
PureLoad Naming, Taskspace and Manager servers controlling the
load test:
The PureLoad Runner Client will handle all communication between
the client and the PureLoad Runner isolating all network details
from the API.
The protocol between the client and the Runner will be internal,
based on Java reflection, using standard TCP. The main reason for
not using Java RMI is to simplify access through firewalls.
The Runner API is documented in javadoc format and available in
the <install-home>/api/runner-api
directory.
There is also a simple example Java client program using the
Runner API available in <install-home>/examples.
To use the Runner API the following libraries found in
<install-home>/lib is required:
These jar-files must be used to compile and run a client program
using the Runner API.
The Runner Command (runnercmd) is a simple command line program
that implements the Runner API.
Simply execute "runnercmd help" to get a usage message describing
the provided commands:
| % ./bin/runnercmd help Usage: runnercmd [-xml] <host> <port> <command> Available commands: props <properties file> Load properties file load <PLC file> Load PLC file start [scenario(s)] Start execution stop Stop execution abort Abort execution progress Get execution progress running Check if load test is running total Get total summary allsummary <child-flag> Get all summary results summary <task-path> <child-flag> Get summary results for specified node alltimeslot <child-flag> Get all results for latest timeslot timeslot <task-path> <child-flag> Get results for latest timeslot for specified node allmonitor Get monitor results monitor <monitor> Get monitor results export <file-path> Export comparer data help [command] Show help. Type 'runnercmd help <command>' for help on a specific command. |
Note that the actual output might differ, since new commands
might be added.
Generated output will be i plan text format if not the -xml option
is used. The -xml option will generate a simple XML format for all
results presented.