Table of contents
Contents
1. initialized the Monitor view appears This view contains a set of tabbed panels e one for all injectors one for each probe class here just cpu te LdapinjectorLoadTest_1 xis ths ldap ctp amp LdapLoadTest_1 csv m Test Commands Injectors and probes All injectors and probes in the test plan injector cpu Select All Id Server Role Class Arguments Comment State 7 1000 600 System Under Test CPU load initialized Deselect All v inj2 probe cpu 1000 600 CPU load of injector 2 initialized Global state o inj probe cpu 1000 600 CPU load of injector 1 initialized initialized nitialize Start Suspend Stop Collect Parameters Edit Test tk Monitor E Console m ldap run1 injector cpu Alarms Show Listen Id Time Time 60 Value 9 js 2 oo 1 oo 12 0 00 5 4 CPU ae 50 01 21 40 02 30 03 20 04 10 Store monitoring data Drawing time frame s 300 Polling period s 1 Refresh Reset The user may set the monitoring time frame the polling period time interval between two consecutive monitoring points and start or stop the monitoring process Moreover a check box table at the left side of each panel makes it possible to selectively disable or enable the collect and display of monitoring data for each blade Now you can start the injection by clicking on the Start button Then you can suspend resume or stop the test execution by clicking on the corresponding buttons The Parameters button allow2. the CSV file The behavior is now complete and looks like this Behavior definition Random_0 setUniform Random_O sleep G9 while Chrono_0 start Ldapinjector_0 connection Ldapinjector_0 search Ldapinjector_0 closeConnection chrono _O stop 2 2 4 Load Profiles Load profiles enable predefining how the Edition page for behavior description population of each behavior will evolve by setting the number of active instances according to time Behavior name Heavy load To create a load profile select the New Duplicate Remove corresponding Behavior tab and click on the Create button Load profile Create Delete Note profile is empty First we want a ramp that increases the number of simultaneously active behavior instances virtual users from O to 60 during the first minute 60 seconds e enter 60 in the Time field e enter 60 in the Population field e choose the linear Ramp style To save these settings click on the Add point button _ Add Load profile Add points for this profile Heavy load Population Ramp style 60 60 of Force stop Points Time Population Ramp style 60 60 Pi Finish Cancel 21 How To Use CLIF v2 and ISAC plug ins Note point 0 0 is implicit and will be automatically inserted whenever no point is specified for time O Then we want a constant number of simultaneously active behavior instances during 2 minutes 120 seconds Since the Time
3. Iinjector_0 connection Insert after Clear Help Up Down Design Source import Behavior Heavy load Note these variable statements are not specific to the CsvProvider plug in Many other plug ins provide helpful variables Refer to the plug ins Help from the Import tab or see the ISAC plug ins reference manual 18 November 4th 201 1 Then we add an action to perform a search on the LDAP directory Use the same method as for the LDAP connection action to add the LdapInjector_0 search request and select it in the behavior editor to set its parameters Edition page for behavior description Parameters JaniniectorLoaqdiest 14 xis 13 Behavior Page Set parameters for the selected primitive Behavior name Heavy load sample Ldaplinjector search New Duplicate Remove id Ldapinjector o 2l Behavior definition Search base csv searchBase Random_0 setUniform Random_0O sleep 9 while insert before Search Filter S csv searchFilter Search scope S csv sea rchScope Chrono_O start 6 Ldapinjector_0 connection E Insert after Ldapinjector_0 search Remove Clear Help Up Down Design Source Import Behavior Heavy load 19 How To Use CLIF v2 and ISAC plug ins Then we close the connection to the LDAP directory Add action Ldap
4. Injector_0 closeConnection to the while loop It takes no parameter Next add the Chrono_ stop instruction to the while loop to get the total duration of each connection search disconnection transaction Select this instruction in the behavior editor and set its parameters This instruction creates a pseudo request report with the full execution time of the transaction You have to state if the transaction must be considered as successful or not See the Status check box Optionally you may add a specific comment and a result string in the corresponding fields Co DINIECCOFTLOGdad ESC Ne j a x m 3 Behavior Page m Edition page for behavior description Parameters Set parameters for the selected primitive Behavior name Heavy load sample Chrono stop New Duplicate Remove Load profile Create Delete Note profile is empty id Chrono_o Behavior definition status successful Random_0 setUniform Random_O sleep 69 while Insert before comment optional search transaction e Chrono_O start Insert after result optional Ldapinjector_0 connection Ldapinjector_0 search Remove LdapInjector_0 closeConnection clear t Chrono _0 stop Help Up Down Design Source import Behavior Heavy load 20 November 4th 2011 Finally end the while loop block with the csv next control instruction to get the next line from
5. LdapInjector LdapIinjector id Ldapinjectoro Host name IpAddressOrName gt Design Source import BehaviorBO SSCS 10 November 4th 201 1 Do the same with the ConstantTimer plug in Import Page Plug ins Parameters List of plug ins used in this scenario Set plug in import parameters LdapInjector_0 LdapInjector Add use ConstantTimer ConstantTimer CsvProvider_0 CsvProvider timer 15 ConstantTimer Remove Random_0 Random Chrono_0 Chrono Remove All id timer 15 Help duration ms 1000 Up Down Add behavior Source Import Behavior BO Note each import has a unique identifier see the id field You may keep the default generated id PlugInName_0 PlugInName_1 etc but most of the time giving a shorter and more explicit id is convenient For example here we can give the id timer 1s for the ConstantTimer import initialized with a 1000ms duration The Random and Chrono plug ins have no parameter 11 How To Use CLIF v2 and ISAC plug ins Select the CSVProvider plug in and set its parameters use CsvProvider CsvProvider id csv File name LdapLoadTest_1 csv Field separator Fields names separated by the given separator login password searchBase searchFilter searchScope MacOS 9 line separator enable shared X enable loop 7 enable The file name is the name of the CSV file that will contain the external data set for the LDAP l
6. November 4th 2011 How to use CLIF v2 and ISAC plug ins Air with the Eclipse console clif ow2 org Copyright 2006 2011 France Telecom License information http creativecommons org licenses by nc sa 3 0 pd How To Use CLIF v2 and ISAC plug ins Table of contents sintroduchon to ISAC PIMG INS siiccscsccscsecscsacesdccodessssececcossensssussecsvestectscseusecevessecceuewavecunsteeasveccseasteee 3 Vi Wat ts an ISAC PUn Soie a a a a 3 12 salliin a E E E sais 3 ISAC is a Scenario Architecture for CLIF ssssssssssssssssssssssssecccssecssceccesccccessessscsssecessesesesescessoo 4 2 1 Denne an ISAC scenario for EDAP eraan A a neeveteteanenseaasiincetie 5 22 Denne your ISAC Sena Oena a R S 6 2 2 1 Create your test project and your ISAC scenario eeeenesssnnnneesssssssssrrrsssssssserrrssssseesss 6 Deel MPOT IAC PUD IS e a E tenn dos eacemeoudanaticbarasecuiurenncnenttaaees 9 ZL AICTE VOUT DEMAVION aeran Ea E EE E E E A E E 13 Pe LOA TTO L OS E E tud ot aan ca siesqictud gs ato ican utc Sh agus cteae tad ea tidacen eho 21 DD DNNE TSE LAN sstosaaictssdtnGach guiakdaintalstinsachawansanddtinleceeuad ante Sncantquaaronteatyfectannitonktdcdatiney Gbacisen 24 PS ROON Crer E rE E E E E E a A ene 24 2a CFE ATEN PON EEEE E AE T T 24 2 3 3 Add Probes and Injectors to the test DIGI ccccccccssccccccccssssccccceccasesseeeeeaaeseseeessaaaeseeeesanees 23 2 4 Deploying and executing the test plan ssseoeeee
7. and possibly more explicit string Should you change the Id be very careful about using unique Ids Using the same Id for different injectors or probes in the same test plan will result in weird behaviors 25 How To Use CLIF v2 and ISAC plug ins Id 1 Server inj2 Role probe Class cpu Arguments 1000 600 Click on the Add button Id 2 Server sut Role probe Class cpu Arguments 1000 600 Don t forget to save your test plan clicking on File gt Save or Ctrl s Now we have this view Injectors and probes Allinjectors and probes inthe test plan Id Server Role Class Arguments Comment 1000600 System Under Test CPU load 1 inj2 probe cpu 1000600 CPU load of injector 2 0 inj1 probe cpu 1000600 CPU loadpaf injector 1 And finally add injectors on both CLIF servers inj1 and inj2 Since we are using an ISAC scenario IsacRunner must be used as injector class and the scenario file name must be given as argument Don t forget to select the injector as Role Click on the Add button Td 3 Server inj Role injector Class IsacRunner Arguments LdapInjectorLoadTest_1 xis Click on the Add button Id 4 Server inj2 Role injector Class IsacRunner Arguments LdapInjectorLoadTest_1 xis Note by deploying twice the same ISAC scenario the overall generated traffic will be double In other words the global load profile will be twice as big as the Now we h
8. ave this view Injectors and probes Allinjectors and probes inthe test plan cpu injector Id Server Role Class Arguments Comment injector IsacRunner LdapInjecrLoadTest _1 xis LDAP load injector 4 inj2 injector IsacRunner LdapIinjectorLoadTest_1 xis LDAP load injector 26 November 4th 2011 The Cliffree View gives a complementary view on this test plan organized by CLIF server You may get this view from menu Window gt Views or by calling the CLIF perspective from menu Window gt Perspectives Copy paste operations are possible in this view i n r k injector 3 injector 4 27 How To Use CLIF v2 and ISAC plug ins 2 4 Deploying and executing the test plan To ease the deployment of distributed test plans CLIF embeds a code server feature which transparently ships resource files used by your test plans and scenarios the ISAC scenarios files as well as possible files used by the scenario files such as the CSV file we use here to set LDAP connection and search parameters In order to find these files the code server must be given a resolution path With the Eclipse based console this path is set by default to the current CLIF project path You may check and modify this path from the CLIF properties tab available among the project properties Right click on the project and choose Properties option Then select the CLIF properties line Properties for MyTest type Filter text CLIF prop
9. box means the time in seconds since the start of the test the new point to add will be at 120 2 minutes 60 initial ramp up 180 seconds Next we want the number of virtual users to rise to 100 as a burst Ramp style Of Of oJ Enter 180 in the Time field and 100 in the Population field Choose the horizontal vertical crenel hv ramp style Click on the Add point button Add point Load profile Add points for this profile Heavy load Population Ramp style 180 100 fon Force stop Points Time Population Ramp style 60 60 7 180 100 eJ Finish Cancel 22 November 4th 201 1 Finally we want to decrease the number of virtual users from 100 to O during 60 seconds Enter 240 in the Time field le O in the Population field and select the linear Ramp style click on the Add point button f Load profile Add points for this profile Heavy load Population Ramp style 240 o 7 Force stop Points Time Population Ramp style 60 60 Pi 180 100 J N VOTI i 240 o r Remove Finish Note the Force stop flag states if some active instances shall be stopped to enforce a decrease of the population according to the load profile or if the extra behaviors shall complete Click on the Finish button You can see the load profile graph watching the Load profiles view Jr Load profiles amp Console m Profiles Time 0 Va
10. data Each line of the CSV file represents the parameters needed to execute the scenario Then we will loop on each line to make different calls to the LDAP directory To do this we will use the CSvProvider plug in In this ISAC scenario the scenario duration will be set to 1 second We need to import the ConstantTimer plug in In our load test we will use two or more injectors and we don t want to launch the test at the same moment on each injector So we will import the Random plug in Finally we want to know the response time of group of operations that s why we will import the Chrono plug in How To Use CLIF v2 and ISAC plug ins 2 2 Define your ISAC scenario 2 2 1 Create your test project and your ISAC scenario First of all you have to create a new CLIF project Click on File gt New gt CLIF project CLIF RCP Console File Edit CLIF Search Window Help f CLIF Project Le ISAC Plug in Project Project CLIF Test Plan Test Plan Deployment Fa Test Report with CLIF Isac scenario HTTP Capture ti Import t Export Refresh h Cliffreeview 2 Ofi Example Other Enter your project name you can use default location or choose an other location Click on Finish New CLIF Project Create a new CLIF Project Choose project location Project name MyTest 7 Use default location K November 4th 2011 The console window is split into several panels called views You may have a
11. ditions provided by the different imported plug ins daplniectorLoadTest 1 xis amp 2 ee Behavior Page m Edition page for behavior description Parameters N Set parameters for the selected primitive Behavior name Heavy load Select a test condition of the while controler node ee CsvProvider notEndOfFile A Load profile Create Delete Note profile is empty Behavior definition id v Random_0 setUniform FEEEET Random_O sleep while Insert before Insert after Remove Clear Help Up Down Design Source Import Behavior Heavy load Note the id parameter must be checked carefully when the same plug in has been imported more than once to make the difference between the imports Here there is only one possible choice csv plug in id 16 November 4th 2011 To include actions in the loop select the while statement in the Behavior definition and click on the Add child button The first action that we will add is starting chronometer Chrono_ 0 with its start control This control takes no argument 4 LdapInjector_0 E Chrono stop Random_0O E Chrono split i CSV Chrono suspend timer 1s Chrono resume Chrono_0 o Chrono start if Chrono drop w 39 while ee nchoice starts the chrono Then we perform a connection to the LDAP directory Select the Chrono_o0 start instructio
12. erties dow Resource Directory for raw measures MyTest report Browse ISAC Plugin Project References Refactoring History sa MyTest Run Debug Settings re Directory For monitoring statistics MyTest stats Browse Task Tags Code server path 2 Now right click on the MyTest project in the Navigator view alternatively use the File menu and run option New gt Test Plan Deployment 28 November 4th 2011 k LdapinjectorLoadTest_1 xis in ld Test Plan Editor Injectors and probes amp report stats x _project w LdapinjectorLoadTest_1 xis Allinjectors and probes inthe test plar injector cpu k _ Id Server Role Class lt A 2 sut probe cpu cliF props inj2 probe cpu New i CLIF Project Open Ge ISAC Plug in Project Open With Mf Project B Copy CLIF Test Plan Test Plan Deployment Delete Fa Test Report with CLIF Move Isac scenario Rename HTTP Capture T cliffreeView 2 PARUNG mop E 3 Export inj1 P The deployment wizard pops up New Test Deployment New Test Deployment Choose test plan to deploy Co naina Browse Test plan to deploy Idap ctp D cancet Check that the Container field s value is MyTest Otherwise click on the Browse button and select the MyTest project Click on Finish A information window pops up to acknowledge the dep
13. f you wish Here we change it for Heavy load w LdapinjectorLoadTest 1 xis Behavior Page Edition page for behavior description Behavior name Heavy load New Duplicate Remove Load profile Create Delete Note profile is empty Behavior definition LS Insert at begin Insert at end Remove Clear Help Up Down Design Source Import Behavior Heavy load 13 How To Use CLIF v2 and ISAC plug ins At the beginning of the behavior we add a sleep action The sleep time will be variable and its variation will depend on a uniform random distribution Click on the Insert at begin button choose the Random_O import on the left hand side of the pop up window and select its setUniform control in the right hand side Click on Finish Actions Add a new action for behavior Heavy loa LdapInjector_0 G Random action lt Random_0 Random sleep 4 CSV Random setGaussian timer 15 Random setUniform Chrono_O Random setNegativeExpo if Random setDirac amp while Random setPoisson nchoice preemptive k Sets the uniform random distribution law Parameters min required the minimal integer value max required the maximal integer value 14 We set the required parameters values November 4th 2011 w LdapinjectorLoadTest 1 xis 2 L Behavior Page Edition page for behavior description Behavior name Heavy load New Duplicate Remove Load pro
14. file Create Delete Note profile is empty Behavior definition Random_O setUniform Insert before Insert after Remove Clear Help Up Down Design Source Import Behavior Heavy a m E Parameters Set parameters For the selected primitive control Random setUniform id Random_0 min 0 max 1000 And now we add a timer that will make the behavior have a sleep think time for a random duration uniformly distributed between O and 1000ms Click on the Insert after button choose the Random_ import and select the sleep timer primitive LdapInjector_0 Random_0O d preemptive This timer primitive takes no parameter Then we add a while loop Click on the while statement in the pop up window Random action Random sleep CSV oe k timer 15 Chrono_0 D if amp while ee nchoice ndom setGaussian Random setUniform Random setNegativeExpo Random setDirac Random setPoisson Insert after button and choose the daplinjector_0 Random_0O CSV timer 15 Chrono_0 iF E nchoice preemptive 15 How To Use CLIF v2 and ISAC plug ins The loop condition is while we are not at the end of the CSV file we iterate so that each virtual user uses all the lines form the CSV file and then terminates its execution Select the while statement in the behavior editor and choose the CsvProvider notEndOfFile condition among the con
15. host 1234 4 4 Configuring a CLIF server You may configure CLIF either by editing file clif props in the etc subdirectory or by using command ant config refer to the section dedicated to the command line interface in the User Manuel This configuration operation must be done everywhere you want to run a CLIF server You may also make this configuration step only once and copy the resulting file etc clif props wherever needed 4 5 Running a CLIF server Once CLIF is configured and before running CLIF servers ensure the CLIF registry is running Trying to run a CLIF server either when the Registry is not running or with an wrong configuration will result in a CLIF server failure with this Connection refused message java Exception in thread main org objectweb fractal rmi RemoteException error during marshalling unmarshalling by stub org objectweb jonathan apis presentation MarshalException exception preparing marshaller java net ConnectException Connection refused java at org objectweb fractal rmi stub Stub handleException Stub java 292 java at org objectweb fractal rmi registry NamingService_Stub list Unknown Source java at org ow2 clif deploy ClifRegistry lt init gt ClifRegistry java 95 java at org ow2 clif server lib ClifServerImpl main ClifServerImpl java 139 In our case we will deploy three CLIF servers with names inj1 inj2 and sut by running these commands 33 Ho
16. irectory contains one sub directory per initialized test whose name is the same as the cpu corresponding raw measure sub directory It contains one sub directory for injectors and one sub directory per probe class Monitoring data for each injector and probe is stored in the relevant directory in a file whose name is Id csv Store monitoring data 32 November 4th 2011 4 CLIF servers and registry 4 1 Installation Refer to the Installation Guide 4 2 Rationale CLIF servers are necessary to deploy any test plan since they host load injectors and probes CLIF servers are designated by a name which is registered in a Registry In order to run CLIF servers must be able to find this Registry which implies that the Registry must be running before a CLIF server can be launched e parameters must be given to tell the CLIF servers where to find the Registry and register themselves 4 3 Running a registry The CLIF registry is launched when necessary by the Java Swing GUI or the eclipse based GUI If you want to launch it from command line see the User Manual Here we will be using the Eclipse based console GUI Opening a CLIF test plan ctp file will automatically run the Registry unless a registry is already running To check that the Registry is running you may have a look at the Console View and look for a message of this kind Creating a CLIF Registry Fractal registry is ready registry loca
17. loyment success Information O Test plan successfully deployed 29 How To Use CLIF v2 and ISAC plug ins Now the ldap ctp editor displays a new Test tab the tab switch is at the bottom part Edit Test It contains the same view on the test plan as the Edit tab but e it is not editable e buttons have appeared 6 at the bottom and 2 on the right hand side a global status is displayed on the right hand side deployed W LdapinjectorLoadTest_1 xis ths Idap ctp 2 E Test Commands Injectors and probes 7 Allinjectors and probes inthe test plan at Ps o MISO ls Sia Select All Id Server Role Class Arguments Comment State 1000 600 System Under Test CPUload deployed Deselect All 1 inj2 probe cpu 1000 600 CPU load of injector 2 deployed Global state o inj probe cpu 1000 600 CPU load of injector 1 deployed deployed Initialize Start Suspend Stop Collect Parameters Edit Test Before starting the test execution the deployed test plan must be initialized Click on the Initialize button A dialog window pops up to ask for a name for this test run The default name is the test plan file name without the ctp extension You may modify this name as you wish In any case the initialization date will be appended to this test name and the result will be used to create the measures directory name Test id Enter test id name Idap run 30 November 4th 2011 As soon as the test is
18. lue 0 N amp Heavy load 100 80 40 100 200 240 Note the end of load profile implicitly means an instant drop to O virtual users this is explicit here since we defined a ramp down to 0 at time 240s 23 How To Use CLIF v2 and ISAC plug ins 2 3 Define the test plan 2 3 1 Rationale We want to test an LDAP directory To test it and to get performance measures we will deploy injectors and probes To have a powerful load injection we want to send requests from two different servers To be able to check the injection servers CPU usage we will deploy on each of them a CPU probe To be able to monitor the CPU usage on the LDAP server we will deploy a CPU probe on it 2 3 2 Create a test plan This test plan will be created at the same location of the ISAC scenario file Select project nee right click on it and choose option New gt CLIF Test pan m LdapInjectorLoadTest_1 xis z Behavior Page Mm CLIF Project ie ISAC Plug in Project Open in New Window Project _ CLIF Test Plan Test Plan Deployment 3 Delete Fa Test Report with CLIF Move sac scenario Rename HTTP Capture ti Import W Example Se i Other e Refresh 3 hrono O start Close Project T danliniartar 0 rannerctinn Then enter your test plan name and click on the Finish button New CLIF Test Plan Create a new CLIF Test Plan This wizard creates a new CLIF Test Plan with ctp extension that can be
19. n and click on the Insert after button Alternatively you may select the while statement and click on the Add child button In the action selector get the connection action from the LdapInjector_6 plug in LdapInjector_O E LdapInjector deleteEntry Random_0 E Ldapinjector connection dD csv E LdapInjector closeConnection timer 15 E LdapInjector sslConnection Chrono_0 g LdapInjector addEntry if Ldapin Sctor search 6 amp 9 while E LdapInjector deleteAttribute nchoice G LdapInjector addAttribute 17 How To Use CLIF v2 and ISAC plug ins Now we have to set the LDAP connection parameters values These values are provided by the CSV file through variable statements pluginId key These statements will be replaced at runtime by the value associated to key here login or password by the plug in referenced by pluginId the plug in import id namely csv in this case dapinjectorLoadTest 1 xis 2 m Behavior Page Edition page for behavior description Parameters Set parameters for the selected primitive Behavior name Heavy load sample LdapInjector connection New Duplicate Remove Load profile Create Delete Note profile is empty id Ldapinjector_0 Behavior definition Ldap connection port 389 Random_0 setUniform Random_O sleep 69 while Insert before Login DN S csv login Password csv password Remove x Chrono_0 start Ldap
20. ng ad hoc controls for the plug in itself e g to change some settings e providing support for external data provisioning e g a database of product references or a file containing identifier password pairs for some user accounts used as parameters by the behaviors 1 2 Installation See Installation Manual for Eclipse based console GUI installation How To Use CLIF v2 and ISAC plug ins 2 ISAC is a Scenario Architecture for CLIF lL CLIF RCP Console File Edit CLIF Search Window Help AP TS Navigator 2 iS MyTest 7 Load profiles 22 This view show profiles of a 405 File Please edit one With ISAC testers are given a way to define load scenarios by combining definitions of elementary behaviors typically representing users optional definitions of load profiles setting the population i e the number of active instances of each behavior as a function of time November 4th 2011 2 1 Defining an ISAC scenario for LDAP In this tutorial we will define an ISAC scenario which will send some requests on the LDAP directory We can see below the actions that our scenario will do In this scenario we will connect to the LDAP directory make a search and disconnect it We will import the LdapInjector plug in to be able to do this action To externalize the data used in the scenario mandatory parameters of the LdapInjector plug in we will create CSV file that will contain all the needed
21. oad injection A line in the CSV File will have this format login password searchBase searchFilter searchScope uid 0 ou appli dc annuaire dc com secret_O ou appli dc annuaire dc com amp uid 0 autorisation all 2 uid 1 ou appli dc annuaire dc com secret_1 ou appli dc annuaire dc com amp uid 1 autorisation all 2 uid 2 0u appli dc annuaire dc com secret_2 ou appli dc annuaire dc com amp uid 2 autorisation all 2 In the Field separator field you have to set the separator character used in the CSV file 4 in our case In the Fields names field enter the list of the parameters names columns in the CSV file separated with the given separator here Description of the check boxes e MacOS9 line separator use CR instead of LF as line separator e shared when set progression in the lines is shared by all session objects In other words each session object will get a different line instead of all getting the same sequence of lines loop when set the line sequence wraps up to the first line when the end of file has been reached Otherwise an alarm is thrown when trying to get a field value while the end of file has been reached and the empty string is used as value 12 November 4th 201 1 2 2 3 Define your behavior To define a virtual user behavior you have to select the Behavior tab of your ISAC scenario file You get the behavior editor You can now change the default behavior name BO i
22. opened by a Test Plan editor Container MyTest Browse 24 November 4th 2011 2 3 3 Add Probes and Injectors to the test plan In our case we will add e Two injectors one on each server used to inject requests on the LDAP directory e Three CPU probes one on each load injection server and one on the server where the LDAP directory is installed Click on the add button and set the properties of the injector or probe th LdapinjectorLoadTest_1 xis hs Idap ctp 4 E Test Plan Editor Injectors and probes All injectors and probes in the test plan Id Server Role Class Arguments Comment 0 local host probe Remove N Remove All Properties Manage injector and probe properties Id 0 Server local host v Refresh Role probe Class Arguments Comment Edit As we want to deploy load injectors and probes on remote machines we must be able to define CLIF servers other than the default local host which is embedded in the console To be able to change the Server name you have to run the target CLIF servers once the registry is started in the console see section 4 and click on the Refresh button Id 0 Server inj Role probe Class cpu Arguments 1000 600 a measure will be taken each 1000 ms and during 600 s Click on the Add button Note the injector or probe Id field has a default integer value 0 1 2 etc However you might change it and use an arbitrary
23. port Behavior BO Click on the Add button Import the following plug ins one by one e LdapInjector ISAC Plug ins e CSVProvider Add a new plug in e ConstantTimer e Random Chrono CommandLinelnjector i Common lt ConstantTimer t Context t Counter t CsvProvider lt Dnsinjector FileReader lt FtpInjector lt Httplnjector IpProvider Jdbcinjector LdapInjector Random lt REpInjector SipInjector Socketinjector StringHandler lt Synchro Udpinjector How To Use CLIF v2 and ISAC plug ins Now all the necessary plug ins are listed Import Page Plug ins List of plug ins used in this scenario LdapInjector_0 Ldapinjector t CsvProvider_0 CsvProvider ConstantTimer_0 ConstantTimer Random_0 Random Chrono_0 Chrono n Import tab Remove Remove All Help Up Down Add behavior Then we must set the plug ins initialization parameters Select the Ldaplnjector_0 MyLdaplnjector import and set the plug in parameters Import Page Plug ins List of plug ins used in this scenario LdapInjector_0 Ldapinjector CsvProvider_0 CsvProvider ConstantTimer_0 ConstantTimer Random_0 Random Chrono_0 Chrono Add Remove Remove All Help Up Down Add behavior Parameters Set plug in import parameters use
24. s for changing some probe injector specific parameters With IsacRunner injectors several parameters may be modified at runtime e about the scenario execution engine itself size of the thread pool tolerance on deadlines storage options e number of virtual users aka population of each defined behavior 31 How To Use CLIF v2 and ISAC plug ins 3 Browsing test results 3 1 Getting raw measures Once the test is terminated naturally completed or manually stopped you shall collect raw measures produced by injectors and probes by clicking on the Collect button unless you are not interested in these measures Collecting measures will locally create CSV formatted files containing all the measures in a tree organized breakdown of directories and files iS MyTest report amp ldap runt_2011 11 04_17h11m17 Yeo The root directory is determined by a CLIF property The default is a directory named report in the corresponding CLIF project This directory contains one sub directory per initialized test whose name is the concatenation of the chosen test id and the initialization date Each sub directory has a companion ctp file which is a copy of the deployed test plan CPU classname E gas B lifecycle classname E server prop rie e 2 e 3 e ths ldap run1_2011 11 04_17h11m17 ctp stats amp ldap runt_2011 11 04_17h11m17 cpu Q csv For each test run each injector and probe in
25. set of views defined by the ISAC perspective CLIF RCP Console MS Bals GHT SETE Ses Ea t Navigator amp 77 xml version 1 0 fi scenario SYSTEM classpath ora ow2 clif Y MyTest leg DOCTYPE p g ow2 amp report scenario stats W project w LdapinjectorLoadTest_1 xis B clif props Design Source Import Behavior BO Wr Load profiles 2 El Console Profiles Time OValue 0 scenario scenario 105 19 230 lt scenario gt Now you can see the content of your scenario file in the ISAC view At the bottom of this view you can see four tabs e Design shows the tree structure of the xis file which is an xml file e Source is an XML editor for the xis file Import allows you to import the ISAC plug ins that you will need in your scenario Behavior BO is an editor for the default BO behavior It defines your virtual users behavior and associated load profile You may define more than one behavior and give arbitrary names to behaviors Each behavior is edited in a separate tab Below the ISAC view you see the Load profile view with currently no load profile defined November 4th 2011 2 2 2 Import ISAC plug ins dis SBF COPrLod Click on the Im m ort tab to lay the list of imported ISAC plug ins This list is currently empty Import Page Plug ins List of plug ins used in this scenario Remove Remove All Help Up Down Add behavior Source Im
26. sssssssooerrsssssssseerrssssssssseersssssssseeressserssssesss 28 Browsino test resul Scenerne eaaa e are orara Eaa A uecuunesteuss 32 PGN aN Mea UOS A tia damn denetnintienierares 32 3 2 Getin e AMONILOMIN GS CAL aeee E R aeons 32 CLIE Servers ANG TOCISY ciccesverecesasexageteccsnaesadesanedocenaceoaseeaneeactanaevacesauadeesbaneonseeaueeasesaauvasesenessneneys 33 A Ne msta llat E A 33 TERANO Oa E E E Neen etre mur recy a Rome ee Inert iy Te 33 Ao a RUNIN Aie S OO ne ene ay SO nr me Tat SE Tee 33 dA omoun aC LEIE Ser y Ch aea silesaachouaiua sedssaated eacmasieucatcausinaes taacduaiaoen sie 33 A RUNMINS a C LIF SERV nssr a e a a a E 33 November 4th 2011 1 Introduction to ISAC Plug ins 1 1 What is an ISAC Plug ins In order to actually generate traffic on a System Under Test SUT we need to define a behavior A behavior can be understood as a logical definition a kind of a skeleton This skeleton must be associated to one or more ISAC plug ins Plug ins are external Java libraries that are responsible for e performing actions i e generating requests on the SUT using and managing specific protocols whose response times will be measured e g HTTP DNS JDBC TCP IP SIP LDAP e providing conditions used by the behaviors conditional statements if then else while preemptive e providing timers to implement delays think time for example with specific random distributions or computed in some arbitrary way e providi
27. the test plan has its own sub directory whose name is the injector probe Id It contains a number of text files e lifecycle lists the dates of the execution status changes e server prop lists all the Java system properties of the Java Virtual Machine running this injector or probe e alarm contains the alarm events thrown by this injector or probe if any e for injectors only file action contains the request execution reports duration Success e for probes only a specific file whose name and content depends on the probe class contains all the performed measures I 1 csv 2 csv injector 3 csv 4 c5v 3 2 Getting monitoring data Besides the raw measures monitoring data can optionally be stored also instead of just being displayed and discarded Monitoring data provide moving statistics that are very convenient to get a quick analysis of the test results To enable this feature mark the Store th Monitor 2 G Console ldap runt 2 injector cpu Alarms monitoring data check box for each class of probe injector you are show Listen Id Time interested here injector and cpu for example a z gt 04 59 Then monitoring data is written to a set of tree organized breakdown ky 7 1 04 59 of directories and CSV formatted files The root directory of this tree is A A X 0 04 59 determined by a CLIF property The default is a directory named stats in the corresponding CLIF project This d
28. variety of specific assemblies of views called perspectives You can call a specific view or perspective from the Window menu CLIF comes with two perspectives e the CLIF perspective is dedicated to defining CLIF test plans and run test executions e the ISAC perspective is dedicated to the creation of ISAC scenarios You should be now in the CLIF perspective CLIF RCP Console File Edit CLIF Search Window i MyTest amp report gt stats x _project B clif props W CliffreeView X Iin Monitor amp El Console To create an Isac scenario click on File gt New gt Isac Scenario CLIF RCP Console File Edit CLIF Search Window Help report stats x _project Go Into Open in New Window Copy B clif props Delete Move i ClifTreeView Rename ta Import t Export Refresh Close Project H i CLIF Project ie ISAC Plug in Project Project CLIF Test Plan Test Plan Deployment Fa Test Report with CLIF Isac scenario lt HTTP Capture W Example W Other How To Use CLIF v2 and ISAC plug ins Choose the container basically the target project s directory and give a name to your ISAC scenario Isac Scenario File This wizard creates a new File with xis extension that can be opened Isac Scenario Container MyTest Browse File name LdapInjectorLoadTest_1 xis Click on Finish Your window layout should automatically switch to the
29. w To Use CLIF v2 and ISAC plug ins e ant Dserver name inji server e ant Dserver name inj2 server e ant Dserver name sut server Of course these CLIF servers should be created on different computers but it is possible to create as many CLIF servers as you like on the same computer In any case CLIF server names must be unique for a given Registry 34
Download Pdf Manuals
Related Search