RPT 8.3 Load Generation Agent

8/13/2019 RPT 8.3 Load Generation Agent

1/14

Rational Performance Tester

Load Generation Agent

Architecture and Support

RPTVersion 8.3.0

Kevin Mooney ([email protected])

Richard Ptasnik ([email protected])


2/14

Table of ontents

1. Load Generation Agent Introduction 3

2. Agent Controller 4

3. Architecture 4

4. Installation 5

4.1 Workbench Local Execution 5

4.2 Installation eatures 5

4.3 Load Generation Agent Con!iguration "

5. Workbench Con!iguration "

5.1 #er$er %ort "

5.2 #ecure Co&&unication using 'L#(##L )

5.3 *elete *e+lo,&ent *irector, )

". Con!iguration -odi!ication )

".1 Add #u++ort !or Another Workstation to an Agent )

".2 Load Generation Agent Con!iguration ile

). Agent #tatus /

).1 #hare Agent 0ith e0 Workbench /

).2 *isconnect Agent !ro& this Workbench /

. 'roubleshooting /

.1 %ort In se /

.2 Check Agents ailed 1

.3 %rocess on dri$er ter&inated 11

/. 'i+s 'ricks and -iscellaneous 13

/.1 %ri$ileges 13

/.2 -ulti+le Engines n ne Agent -achine 13

/.3 Locations 13

/.4 %orts 0ith &ulti+le 0orkbenches 13

/.5 -ax hea+ 13

/." -a6ordo&o 14

/.) -a6ordo&o debug !lag 14


3/14

!. Load Generation Agent "ntroduction

A ne0 Load Generation Agent is a $ital +art o! 7ational %er!or&ance 'ester 87%'9 :ersion .3.. As a re+lace&ent

!or the Agent Controller the Load Generation Agent o!!ers the !ollo0ing !eatures;

:er, strong execution +rocess launch reliabilit, !or agents. 'he Load Generation Agent is designed

s+eci!icall, to 0ork 0ith the 7ational %er!or&ance 'ester 0orkbench in the launch and control o! load

tests.

Agents +oll su++orted 0orkbenches looking !or schedule execution 0ork instead o! the 0orkbench ha$ing

to establish connections 0ith agents. 'his sche&e +ro$ides instant assess&ent o! agent readiness and ra+id

deli$er, o! launch co&&ands.

With the Load Generation Agent the 0orkbench is ca+able o! launching agents in +arallel thus greatl,

reducing o$erall launch ti&e !or large load testing o+erations in$ol$ing &an, agents.

'he Load Generation Agent su++orts intelligent test asset de+lo,&ent onl, +ulling assets !ro& the

0orkbench that it does not ha$e or that ha$e changed. 'his !eature results in !aster launch ti&es !or

subse


4/14

#. Agent ontroller

'he Agent Controller is still +ro$ided 0ith $ersion .3.. As an o+tional +art o! the installation the Agent Controller

can be installed in order to su++ort these !eatures;

7es+onse 'i&e ?reakdo0n 87'?9 #er$ice>oriented Architecture 8#A9 #tubs

While not a t,+ical custo&er con!iguration installing both the Load Generation Agent and the Agent Controller is a

su++orted con!iguration.

The Agent Controller cannot be used for load generation with the RPT 8.3.0 workbench.

3. Architecture

'his section describes the architecture o! the Load Generation Agent. nlike the Agent Controller architecture the

0orkbench does not &ake connections to the agents 0hen a schedule is to be executed. 'he +orts that had to be

o+ened b, !ire0alls !or those connections and the connections the agents &ade back to the 0orkbench on e+he&eral

+orts are no longer necessar,.

With the Load Generation Agent the agent &achines +oll !or 0ork sending =''% re


5/14

n a single agent there exists the -a6ordo&o ser$ice 0hich is one @a$a :irtual -achine that +olls

su++orted 0orkbenches !or schedule execution 0ork. Each *o&o box in the !igure is a single @a$a :irtual

-achine and includes the execution engine. ',+icall, there 0ill be onl, one @a$a +rocess running on the

agent during schedule execution. 'hat single @a$a +rocess is the *o&o(Engine +rocess. 'he !igure abo$e

sho0s that it is +ossible !or one agent &achine to su++ort &ulti+le execution engines. Custo&ers that ha$e

a +o0er!ul "4>bit agent 0ith a lot o! &e&or, &a, !ind it o$erall &ore e!!icient to run 0ith &ulti+le engine

+rocesses o! &odest hea+ sie than one single +rocess 0ith enor&ous hea+ sie due to garbage collectionconsiderations.

'he Load Generation Agent is designed to be si&+le and co&+act. 'he *o&o co&+onent do0nloads !ro&

the 0orkbench the assets needed !or schedule execution including the execution engine. n subse


6/14

$.3 Load Generation Agent onfiguration

'he Load Generation Agent has t0o con!iguration +ara&eters that need to be entered during installation.

Workbench hostna&e. Enter one and onl, one hostna&e that this agent 0ill +oll !or 0ork.

Workbench +ort. Enter the +ort nu&ber su++orted b, the 0orkbench. 'he de!ault +ort nu&ber is ).

*. %or&bench onfiguration

'he Load Generation Agent has se$eral o+tions that can be con!igured !ro& the 0orkbench. 'hese o+tions do not

re


7/14

*.# Secure ommunication using TLS,SSL

Check Workbench and agent communication is encryted using T!"#""!to ha$e all &essages and execution

data exchanged bet0een the 0orkbench and agents encr,+ted. All schedules executed !ro& this 0orkbench 0ill use

##L. 'he 0orkbench 0ill tell the agent 0hat +ort to use !or secure co&&unication $ia the unsecure +ort +rior to

starting schedule execution.

*.3 -elete -eploment -irector

Check $elete deloyment directory on the agent after e%ecution to ha$e the contents o! the de+lo,&ent director,

re&o$ed !ro& the agent a!ter schedule execution co&+letes. 'he de+lo,&ent director, contains all the test assets

the agent re


8/14

ou 0ill then be +ro&+ted to enter the hostna&e and +ort nu&ber !or the 0orkbench to add to the agentFs

con!iguration. A!ter +ressing the button the re


9/14

1. Agent Status

As &entioned abo$e the 0orkbench contains an Agent #tatus button. When selected it is +ossible to see 0hat

agents are +olling the 0orkbench !or 0ork and i! the, are read, to +artici+ate in schedule execution.

'he states an agent &a, dis+la, are;

7ead,. 'he agent is read, to execute a schedule.

?us,. 'he agent is read, to execute a schedule. 'he agent is currentl, executing a schedule. It is +ossible

!or an agent to be executing &ore than one schedule at a ti&e.

Lost Contact. 'he agent is no longer +olling this 0orkbench.

1.! Share Agent 2ith e2 %or&bench

I! ,ou select one or &ore agents and +ress "hare Agent with &ew Workbench ,ou can s+eci!, the hostna&e and

+ort o! a ne0 0orkbench that ,ou 0ant the agent to +oll !or 0ork in addition to the this 0orkbench.

1.# -isconnect Agent from this %or&benchI! ,ou select one or &ore agents and +ress $isconnect Agent from this Workbenchthe hostna&e !or this

0orkbench 0ill be re&o$ed !ro& the agentsD con!iguration !iles and the, 0ill no longer +oll this 0orkbench !or

0ork.

8. Troubleshooting

'his section describes so&e co&&on +roble& scenarios and +ro$ides suggestions !or !inding a solution.

8.! Port "n 4se

"ymtom

When ,ou tr, to run a schedule the !ollo0ing error &essage dialog a++ears;


10/14

'eaning

#o&e +roduct running on the 0orkbench is alread, using +ort ) the de!ault unsecure +ort 7%' uses !or

co&&unication 0ith agents.

"olution ()

sing Windo0 B %re!erences B 'est B #er$er choose a di!!erent +ort such as )1. All agentDs con!iguration !iles&ust also s+eci!, +ort )1. 'here is no need to restart the 0orkbench !or this change to take e!!ect.

"olution (*

It is +ossible the +roduct using +ort ) is no longer needed on this &achine. I! so sto+ or uninstall the +roduct

using +ort ).

8.# hec& Agents )ailed

"ymtom

When ,ou tr, to run a schedule the !ollo0ing error &essage dialog a++ears;

'eaning

ne or &ore o! the agents listed to +artici+ate in executing this schedule are not in acti$e contact 0ith this

0orkbench. 'he Agent #tatus button can be used to $ie0 agent status +rior to schedule execution to deter&ine the

likelihood o! encountering the Check Agents ailed &essage.

"olution ()

'he 7%' Agent is not installed. n an agent ,ou can use the I?- Installation -anager :ie0 Installed %ackages

!eature to ensure that the 7ational %er!or&ance 'ester Agent is installed.

"olution (*

'he Load Generation Agent is installed but the agent ser$ice -a6ordo&o is not running.

Windows Look !or the -a6ordo&o#er$ice +rocess.

I! not running; cd +Program ,iles#"$P#-'#'a/ordomo

&1A"tart

Unix Look !or the -a6ordo&o +rocess.

I! not running; cd #ot#-'#"$P#'a/ordomo

.#'$"tart.sh

Enter the co&&ands abo$e using co&&and +ro&+t or a shell. #ubstitute a++ro+riate +aths based on installation.

se 'ask -anager 8Windo0s9 or the +s co&&and 8nix9 to $eri!, the agent is running. Look !or -a6ordo&o on

nix s,ste&s. n Windo0s s,ste&s look !or -a6ordo&o#er$ice.exe.

"olution (3

-a6ordo&o is running on the agent but it is not +olling the 0orkbench !or 0ork. :eri!, that the agent can *#

resol$e the hostna&e as s+eci!ied in the con!iguration !ile. se the ing co&&and s+eci!,ing the 0orkbench

hostna&e exactl, as entered in the &a6ordo&o.con!ig !ile. I! the +ing co&&and !ails using the hostna&e but ,ou

can success!ull, +ing the 0orkbench using its I% address a 0orkaround could be to s+eci!, the 0orkbench I%


11/14

address in &a6ordo&o.con!ig instead o! the host na&e.

"olution (2

I! -a6ordo&o is running and the 0orkbench can be +inged !ro& the agent then $eri!, there is not a !ire0all blocking

access. ro& a co&&and +ro&+t or shell enter the !ollo0ing;

telnet WR45&C676"T7&A'5 080

',+e a !e0 characters and +ress Enter. ou should see the !ollo0ing;

I! unable to connect or ,ou do not recei$e a res+onse like the one abo$e +erha+s tr, te&+oraril, disabling !ire0alls

to con!ir& that is the source o! the +roble&.

"olution (9

It is also +ossible to recei$e the Check Agents ailed i! the agent con!iguration contains 0orkbenches that are not

running had 7%' uninstalled or are shutdo0n. An agent encountering co&&unication +roble&s &a, get dela,ed in

its +olling 0ork long enough that a su++orted 0orkbench &a, conclude that agent is out o! contact. I! this case is

sus+ected re&o$e an, stale 0orkbench in!or&ation !ro& each agentDs con!iguration !ile.

8.3 Process on dri+er terminated

"ymtom

When ,ou tr, to run a schedule the !ollo0ing error dialog a++ears;

'eaning

#hortl, a!ter -a6ordo&o launched the engine execution +rocess on the agent that +rocess ter&inated unex+ectedl,.

'here &a, be &essages ex+laining the reason !or the !ailure in the 0orkbench Error Log. 'his log can be o+ened

using +re!erences $ia Windo0 B #ho0 :ie0 B Error Log. At the de!ault log le$el o! WA7IG all &essages

0ritten to stderr b, the nati$e 6a$a +rogra& on the agent 0ill be sent to the 0orkbench and stored in the Error Log.


12/14

"olution ()

'he execution +rocess 0ill ter&inate at startu+ i! bad argu&ents are +assed to the @:-. =ere is an exa&+le o! the

contents o! the Error Log i! a bad argu&ent is +assed to the @:-;

ote the @:- co&+laining about an unrecognied co&&and line o+tion. In this case exa&ine an, argu&ents

s+eci!ied in the 7%'J:-A7G# general +ro+ert, !or the location and ensure there are no t,+os or bogus co&&and

line o+tions.

"olution (*

Another exa&+le o! a +roble& that +roduces the +rocess ter&inated &essage is i! so&eho0 the 0rong @:- 0as

used 0hen launching the engine execution +rocess. =ere is an exa&+le o! 0hat ha++ens i! the agent engine

execution is launched 0ith @a$a 1." instead o! the desired @a$a 1.) @:-;


13/14

'he a++earance o! :nsuortedClass;ersion5rror is a clue that the @:- on the agent is not the rede!ault &anner or i! the

installation +ath contained so&e unex+ected characters. =ere are so&e suggested 0orkarounds;

1. ninstall and re>install the +roduct. 'ake de!ault $alues !or 0here to install the agent.

2. se the en$iron&ent $ariable 7%'J@A:A to ex+licitl, s+eci!, the @a$a executable the agent should launch

!or the execution engine. or exa&+le;

RPT7?Program ,iles?-'?"$P?/dk?bin?/[email protected]%e

'he 6a$a.exe to use should be the I?- @a$a 1.) 6a$a binar, installed 0ith the 7%' Agent. A!ter ,ou set

this en$iron&ent $ariable sto+ and restart the -a6ordo&o ser$ice. ro& a co&&and +ro&+t or shell enter

the co&&ands belo0;

Windows cd +Program ,iles#-'#"$P#'a/ordomo

&1A"to

&1A"tart

Unix: cd #ot#-'#"$P#'a/ordomo

.#'$"to.sh

.#'$"tart.sh

5. Tips6 Tric&s and iscellaneous5.! Pri+ileges

'he 7ational %er!or&ance 'ester Agent +roduct &ust be installed b, a user 0ith Ad&inistrator +ri$ileges on

Windo0s and as root on nix.

5.# ultiple 'ngines 7n 7ne Agent achine

%re$ious $ersions o! 7ational %er!or&ance 'ester allo0ed &ulti+le execution engines on one agent &achine. 'he

onl, restriction is that the location hostna&es and de+lo,&ent directories &ust be uni


14/14

RPT 8.3 Load Generation Agent

Documents

Transcript of RPT 8.3 Load Generation Agent