You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by ms...@apache.org on 2003/06/12 14:17:18 UTC
cvs commit: jakarta-jmeter/xdocs/usermanual build-ldap-test-plan.xml component_reference.xml
mstover1 2003/06/12 05:17:18
Modified: docs/usermanual build-ldap-test-plan.html
component_reference.html
xdocs/usermanual build-ldap-test-plan.xml
component_reference.xml
Added: docs/images/screenshots/ldaptest add.png delete.png
login-config-element.png modify.png
requestdefaults.png search.png threadgroup.png
viewtable.png
Log:
LDAP doc updates
Revision Changes Path
1.1 jakarta-jmeter/docs/images/screenshots/ldaptest/add.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/ldaptest/delete.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/ldaptest/login-config-element.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/ldaptest/modify.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/ldaptest/requestdefaults.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/ldaptest/search.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/ldaptest/threadgroup.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/ldaptest/viewtable.png
<<Binary file>>
1.5 +116 -11 jakarta-jmeter/docs/usermanual/build-ldap-test-plan.html
Index: build-ldap-test-plan.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/usermanual/build-ldap-test-plan.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- build-ldap-test-plan.html 11 Jun 2003 19:30:21 -0000 1.4
+++ build-ldap-test-plan.html 12 Jun 2003 12:17:17 -0000 1.5
@@ -11,7 +11,9 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
-
+ <meta name="author" value="Elanjchezhiyan.T">
+ <meta name="email" value="chezhiyan@siptech.co.in">
+
<title>JMeter - User's Manual: Building an LDAP Test Plan</title>
</head>
@@ -98,7 +100,21 @@
You will create four users that send requests for four tests on the LDAP server.Also, you will tell
the users to run their tests twice. So, the total number of requests is (4 users) x (4 requests) x
repeat 2 times) = 32 LDAP requests. To construct the Test Plan, you will use the following elements:
-Thread Group , LDAP Request , LDAP Request Defaults, and View Results in Table.
+
+ <a href="test_plan.html#thread_group">
+ Thread Group
+ </a>
+ ,
+
+ <a href="../usermanual/component_reference.html#LDAP_Request">LDAP Request</a>
+ ,
+
+ <a href="../usermanual/component_reference.html#LDAP_Request_Defaults">LDAP Request Defaults</a>
+ , and
+
+ <a href="../usermanual/component_reference.html#View_Results_in_Table">View Results in Table</a>
+
+.
</p>
<p >
This example assumes that the LDAP Server is installed in your Local machine.
@@ -126,6 +142,14 @@
right mouse button to get the Add menu, and then select Add-->ThreadGroup. You should now see the
Thread Group element under Test Plan. If you do not see the element, then "expand" the Test Plan tree by
clicking on the Test Plan element.
+
+ <p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/threadgroup.png"><br>
+ <font size="-1">
+Figure 9.1. Thread Group with Default Values
+ </font></td></tr></table></p>
+
+
+
</p>
</blockquote>
</p>
@@ -149,8 +173,12 @@
Like most JMeter elements, the Login Config Element Control Panel has a name
field that you can modify. In this example, leave this field with the default value.
</p>
- <blockquote >
- <p >
+ <p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/login-config-element.png"><br>
+ <font size="-1">
+ Figure 9.2 Login Config Element for our Test Plan
+ </font></td></tr></table></p>
+ <p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
+ <tr><td> <p >
Enter Username field to "your Server Username",
<br >
</br>
@@ -163,7 +191,8 @@
<p >
These values are default for the LDAP Requests.
</p>
- </blockquote>
+ </td></tr>
+ </table></p>
</blockquote>
</p>
</td></tr>
@@ -172,7 +201,7 @@
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
- <a name="add_defaults"><strong>9.4 Adding LDAP Request Defaults</strong></a>
+ <a name="add_defaults"><strong>9.3 Adding LDAP Request Defaults</strong></a>
</font>
</td></tr>
<tr><td>
@@ -186,8 +215,12 @@
Like most JMeter elements, the LDAP Request Defaults Control Panel has a name
field that you can modify. In this example, leave this field with the default value.
</p>
- <blockquote >
- Enter DN field to "your Server Root Dn".
+ <p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/requestdefaults.png"><br>
+ <font size="-1">
+ Figure 9.3 LDAP Defaults for our Test Plan
+ </font></td></tr></table></p>
+ <p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
+ <tr><td> Enter DN field to "your Server Root Dn".
<br >
</br>
@@ -200,7 +233,8 @@
</br>
These values are default for the LDAP Requests.
- </blockquote>
+ </td></tr>
+ </table></p>
</blockquote>
</p>
</td></tr>
@@ -209,7 +243,7 @@
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
- <a name=""><strong>9.5 Adding LDAP Requests</strong></a>
+ <a name=""><strong>9.4 Adding LDAP Requests</strong></a>
</font>
</td></tr>
<tr><td>
@@ -261,6 +295,10 @@
</ol>
+ <p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/add.png"><br>
+ <font size="-1">
+ Figure 9.4.1 LDAP Request for Inbuilt Add test
+ </font></td></tr></table></p>
<p >
You do not have to set the Server Name field, port field, Username, Password
and DN because you already specified this value in the Login Config Element and
@@ -284,6 +322,10 @@
</ol>
+ <p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/modify.png"><br>
+ <font size="-1">
+ Figure 9.4.2 LDAP Request for Inbuilt Modify test
+ </font></td></tr></table></p>
<ol >
@@ -298,6 +340,10 @@
</ol>
+ <p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/delete.png"><br>
+ <font size="-1">
+ Figure 9.4.3 LDAP Request for Inbuilt Delete test
+ </font></td></tr></table></p>
<ol >
@@ -312,6 +358,10 @@
</ol>
+ <p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/search.png"><br>
+ <font size="-1">
+ Figure 9.4.4 LDAP Request for Inbuilt Search test
+ </font></td></tr></table></p>
</blockquote>
</p>
</td></tr>
@@ -320,7 +370,7 @@
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
- <a name="add_listener"><strong>9.6 Adding a Listener to View/Store the Test Results</strong></a>
+ <a name="add_listener"><strong>9.5 Adding a Listener to View/Store the Test Results</strong></a>
</font>
</td></tr>
<tr><td>
@@ -331,6 +381,61 @@
requests in a file and presenting a visual model of the data.Select the Siptech
Users element and add a View Results in Table (Add --> Listener -->View Results in Table)
</p>
+ <p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/viewtable.png"><br>
+ <font size="-1">
+ Figure 9.5 View result in Table Listener
+ </font></td></tr></table></p>
+ </blockquote>
+ </p>
+ </td></tr>
+ <tr><td><br></td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="saving"><strong>9.6 Saving the Test Plan</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p >
+ Although it is not required, we recommend that you save the Test Plan to a
+ file before running it. To save the Test Plan, select Save Test Plan from the
+ File menu (with the latest release, it is no longer necessary to select the
+ Test Plan element first).
+ </p>
+ <p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
+ <tr><td> JMeter allows you to save the entire Test Plan tree or
+ only a portion of it. To save only the elements located in a particular "branch"
+ of the Test Plan tree, select the Test Plan element in the tree from which to start
+ the "branch", and then click your right mouse button to access the Save As menu item.
+ Alternatively, select the appropriate Test Plan element and then select Save As from
+ the Edit menu.
+
+ </td></tr>
+ </table></p>
+ </blockquote>
+ </p>
+ </td></tr>
+ <tr><td><br></td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="running"><strong>9.7 Running the Test Plan</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p >
+ From the Run menu, select Run.
+ </p>
+ <p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
+ <tr><td> JMeter lights up a green square in the upper-right-hand corner to indicate if a
+ test is currently running. The square is turned gray when all tests stop. Even after
+ you select "stop", the green light will stay on until all test threads have exited.
+ </td></tr>
+ </table></p>
</blockquote>
</p>
</td></tr>
1.46 +165 -40 jakarta-jmeter/docs/usermanual/component_reference.html
Index: component_reference.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/usermanual/component_reference.html,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- component_reference.html 11 Jun 2003 19:30:21 -0000 1.45
+++ component_reference.html 12 Jun 2003 12:17:17 -0000 1.46
@@ -718,7 +718,20 @@
</font>
</td></tr>
<tr><td>
- For testing LDAP servers
+ This Sampler lets you send a different Ldap request(Add, Modify, Delete and Search) to a LDAP server.
+
+ <p >
+ If you are going to send multiple requests to the same LDAP server, consider
+ using an
+ <a href="../usermanual/component_reference.html#LDAP_Request_Defaults">LDAP Request Defaults</a>
+
+ Configuration Element so you do not have to enter the same information for each
+ LDAP Request.
+ </p>
+ The same way the
+ <a href="../usermanual/component_reference.html#Login_Config_Element">Login Config Element</a>
+ also using for Login and password.
+
<p><b>Control Panel</b></p>
<div align="center"><img src="../images/screenshots/ldap_request.png"></div>
<p >
@@ -729,7 +742,7 @@
Inbuilt Test cases.
</li>
-
+
<li >
User defined Test cases.
</li>
@@ -739,128 +752,240 @@
</p>
<ol >
-
+
<li >
Add Test
</li>
-
+
<ol >
<li >
Inbuilt test :
-
+
<p >
This will add a pre-defined entry in the LDAP Server and calculate
- the execution time. After execution of the test, the created entry will be
- deleted from the LDAP
- Server.
+ the execution time. After execution of the test, the created entry will be
+ deleted from the LDAP
+ Server.
</p>
</li>
-
+
<li >
User defined test :
-
+
<p >
This will add the entry in the LDAP Server. User has to enter all the
- attributes in the table.The entries are collected from the table to add. The
- execution time is calculated. The created entry will not be deleted after the
- test.
+ attributes in the table.The entries are collected from the table to add. The
+ execution time is calculated. The created entry will not be deleted after the
+ test.
</p>
</li>
</ol>
-
+
<li >
Modify Test
</li>
-
+
<ol >
<li >
Inbuilt test :
-
+
<p >
This will create a pre-defined entry first, then will modify the
- created entry in the LDAP Server.And calculate the execution time. After
- execution
- of the test, the created entry will be deleted from the LDAP Server.
+ created entry in the LDAP Server.And calculate the execution time. After
+ execution
+ of the test, the created entry will be deleted from the LDAP Server.
</p>
</li>
-
+
<li >
User defined test
-
+
<p >
This will modify the entry in the LDAP Server. User has to enter all the
- attributes in the table. The entries are collected from the table to modify.
- The execution time is calculated. The entry will not be deleted from the LDAP
- Server.
+ attributes in the table. The entries are collected from the table to modify.
+ The execution time is calculated. The entry will not be deleted from the LDAP
+ Server.
</p>
</li>
</ol>
-
+
<li >
Search Test
</li>
-
+
<ol >
<li >
Inbuilt test :
-
+
<p >
This will create the entry first, then will search if the attributes
- are available. It calculates the execution time of the search query. At the
- end of the execution,created entry will be deleted from the LDAP Server.
+ are available. It calculates the execution time of the search query. At the
+ end of the execution,created entry will be deleted from the LDAP Server.
</p>
</li>
-
+
<li >
User defined test
-
+
<p >
This will search the user defined entry(Search filter) in the Search
- base (again, defined by the user). The entries should be available in the LDAP
- Server. The execution time is calculated.
+ base (again, defined by the user). The entries should be available in the LDAP
+ Server. The execution time is calculated.
</p>
</li>
</ol>
-
+
<li >
Delete Test
</li>
-
+
<ol >
<li >
Inbuilt test :
-
+
<p >
This will create a pre-defined entry first, then it will be deleted
- from the LDAP Server. The execution time is calculated.
+ from the LDAP Server. The execution time is calculated.
</p>
</li>
-
+
<li >
User defined test
-
+
<p >
This will delete the user-defined entry in the LDAP Server. The entries
- should be available in the LDAP Server. The execution time is calculated.
+ should be available in the LDAP Server. The execution time is calculated.
</p>
</li>
</ol>
</ol>
+ <p>
+ <b>Parameters</b>
+ <table border="1" cellspacing="0" cellpadding="2">
+ <tr><th>Attribute</th><th>Description</th><th>Required</th></tr>
+ <tr>
+ <td>Name</td>
+ <td> Descriptive name for this controller that is shown in the tree.
+ </td>
+ <td>
+ No
+ </td>
+ </tr>
+ <tr>
+ <td>Server Name or IP</td>
+ <td> Domain name or IP address of the LDAP server.
+ JMeter assumes the LDAP server is listening on the default port(389).
+ </td>
+ <td>
+ Yes
+ </td>
+ </tr>
+ <tr>
+ <td>Port</td>
+ <td> default port(389).
+ </td>
+ <td>
+ Yes
+ </td>
+ </tr>
+ <tr>
+ <td>root DN</td>
+ <td> DN for the server to communicate
+ </td>
+ <td>
+ Yes
+ </td>
+ </tr>
+ <tr>
+ <td>Username</td>
+ <td> LDAP server username.
+ </td>
+ <td>
+ Usually
+ </td>
+ </tr>
+ <tr>
+ <td>Password</td>
+ <td> LDAP server password.
+ </td>
+ <td>
+ Usually
+ </td>
+ </tr>
+ <tr>
+ <td>Entry DN</td>
+ <td> the name of the context to create or Modify; may not be empty Example: do you want to add cn=apache,ou=test
+ you have to add in table name=cn, value=apache
+
+ </td>
+ <td>
+ yes
+ </td>
+ </tr>
+ <tr>
+ <td>Delete</td>
+ <td> the name of the context to Delete; may not be empty
+ </td>
+ <td>
+ yes
+ </td>
+ </tr>
+ <tr>
+ <td>Search base</td>
+ <td> the name of the context or object to search
+ </td>
+ <td>
+ yes
+ </td>
+ </tr>
+ <tr>
+ <td>Search filter</td>
+ <td> the filter expression to use for the search; may not be null
+ </td>
+ <td>
+ yes
+ </td>
+ </tr>
+ <tr>
+ <td>add test</td>
+ <td> this name, value pair to added in the given context object
+ </td>
+ <td>
+ yes
+ </td>
+ </tr>
+ <tr>
+ <td>modify test</td>
+ <td> this name, value pair to add or modify in the given context object
+ </td>
+ <td>
+ yes
+ </td>
+ </tr>
+ </table>
+ </p>
+ <p><b>See Also:</b>
+ <ul>
+ <li><a href="build-ldap-test-plan.html">Building a Ldap Test Plan</a></li>
+ <li> <a href="../usermanual/component_reference.html#LDAP_Request_Defaults">LDAP Request Defaults</a>
+</li>
+ </ul>
+ </p>
</td></tr>
<tr><td><br></td></tr>
</table>
1.3 +75 -13 jakarta-jmeter/xdocs/usermanual/build-ldap-test-plan.xml
Index: build-ldap-test-plan.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/build-ldap-test-plan.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- build-ldap-test-plan.xml 11 Jun 2003 15:49:30 -0000 1.2
+++ build-ldap-test-plan.xml 12 Jun 2003 12:17:17 -0000 1.3
@@ -1,7 +1,9 @@
<?xml version="1.0"?>
<document prev="build-ftp-test-plan.html" next="remote-test.html" date="$Date$">
+
<properties>
+ <author email="chezhiyan@siptech.co.in">Elanjchezhiyan.T</author>
<title>User's Manual: Building an LDAP Test Plan</title>
</properties>
@@ -11,7 +13,11 @@
You will create four users that send requests for four tests on the LDAP server.Also, you will tell
the users to run their tests twice. So, the total number of requests is (4 users) x (4 requests) x
repeat 2 times) = 32 LDAP requests. To construct the Test Plan, you will use the following elements:
-Thread Group , LDAP Request , LDAP Request Defaults, and View Results in Table.</p>
+<a href="test_plan.html#thread_group">Thread Group</a>,
+<complink name="LDAP Request"/>,
+<complink name="LDAP Request Defaults"/>, and
+<complink name="View Results in Table"/>
+.</p>
<p>This example assumes that the LDAP Server is installed in your Local machine.</p>
</section>
<section name="9.1 Adding Users" anchor="adding_users">
@@ -21,7 +27,11 @@
<p>Go ahead and add the ThreadGroup element by first selecting the Test Plan, clicking your
right mouse button to get the Add menu, and then select Add-->ThreadGroup. You should now see the
Thread Group element under Test Plan. If you do not see the element, then "expand" the Test Plan tree by
-clicking on the Test Plan element.</p>
+clicking on the Test Plan element.
+<figure image="../images/screenshots/ldaptest/threadgroup.png">
+Figure 9.1. Thread Group with Default Values</figure>
+
+</p>
</section>
<section name="9.2 Adding Login Config Element" anchor="add_login">
<p>Begin by selecting the Siptech Users element. Click your right mouse
@@ -30,26 +40,34 @@
<p>Like most JMeter elements, the Login Config Element Control Panel has a name
field that you can modify. In this example, leave this field with the default value.</p>
- <blockquote><p>Enter Username field to "your Server Username",<br/>
+<figure image="../images/screenshots/ldaptest/login-config-element.png">
+ Figure 9.2 Login Config Element for our Test Plan</figure>
+
+ <note><p>Enter Username field to "your Server Username",<br/>
The password field to "your Server Passowrd"</p>
- <p>These values are default for the LDAP Requests.</p></blockquote>
+ <p>These values are default for the LDAP Requests.</p></note>
</section>
- <section name="9.4 Adding LDAP Request Defaults" anchor="add_defaults">
+ <section name="9.3 Adding LDAP Request Defaults" anchor="add_defaults">
<p>Begin by selecting the Siptech Users element. Click your right mouse button
to get the Add menu, and then select Add --> Config Element -->LDAP Request Defaults. Then,
select this new element to view its Control Panel.</p>
<p>Like most JMeter elements, the LDAP Request Defaults Control Panel has a name
field that you can modify. In this example, leave this field with the default value.</p>
- <blockquote>Enter DN field to "your Server Root Dn".<br/>
+
+<figure image="../images/screenshots/ldaptest/requestdefaults.png">
+ Figure 9.3 LDAP Defaults for our Test Plan</figure>
+
+ <note>Enter DN field to "your Server Root Dn".<br/>
Enter LDAP Server's Servername field to "localhost".<br/>
The port to 389.<br/>
- These values are default for the LDAP Requests.</blockquote>
+ These values are default for the LDAP Requests.</note>
</section>
- <section name="9.5 Adding LDAP Requests" anchot="add_requests">
+
+ <section name="9.4 Adding LDAP Requests" anchot="add_requests">
<p>In our Test Plan, we need to make four LDAP requests.</p>
<ol>
<li>Inbuilt Add Test</li>
@@ -65,6 +83,10 @@
<li>Change the Name to "Inbuilt-Add Test".</li>
<li>Select the Add test Radio button</li>
</ol>
+ <figure image="../images/screenshots/ldaptest/add.png">
+ Figure 9.4.1 LDAP Request for Inbuilt Add test</figure>
+
+
<p>You do not have to set the Server Name field, port field, Username, Password
and DN because you already specified this value in the Login Config Element and
LDAP Request Defaults.</p>
@@ -74,23 +96,63 @@
<li>Change the Name to "Inbuilt-Modify Test".</li>
<li>Select the Modify test Radio button</li>
</ol>
- Next, add the second LDAP Request and edit the following properties
+ Next, add the Third LDAP Request and edit the following properties
+ <figure image="../images/screenshots/ldaptest/modify.png">
+ Figure 9.4.2 LDAP Request for Inbuilt Modify test</figure>
+
<ol>
<li>Change the Name to "Inbuilt-Delete Test".</li>
<li>Select the Delete test Radio button</li>
</ol>
- Next, add the second LDAP Request and edit the following properties
- <ol>
+ Next, add the fourth LDAP Request and edit the following properties
+
+ <figure image="../images/screenshots/ldaptest/delete.png">
+ Figure 9.4.3 LDAP Request for Inbuilt Delete test</figure>
+
+ <ol>
<li>Change the Name to "Inbuilt-Search Test".</li>
<li>Select the Search test Radio button</li>
</ol>
+ <figure image="../images/screenshots/ldaptest/search.png">
+ Figure 9.4.4 LDAP Request for Inbuilt Search test</figure>
+
</section>
- <section name="9.6 Adding a Listener to View/Store the Test Results" anchor="add_listener">
+ <section name="9.5 Adding a Listener to View/Store the Test Results" anchor="add_listener">
<p>The final element you need to add to your Test Plan is a Listener.
This element is responsible for storing all of the results of your LDAP
requests in a file and presenting a visual model of the data.Select the Siptech
Users element and add a View Results in Table (Add --> Listener -->View Results in Table)</p>
+<figure image="../images/screenshots/ldaptest/viewtable.png">
+ Figure 9.5 View result in Table Listener</figure>
+
+</section>
+<section name="9.6 Saving the Test Plan" anchor="saving">
+ <p>Although it is not required, we recommend that you save the Test Plan to a
+ file before running it. To save the Test Plan, select Save Test Plan from the
+ File menu (with the latest release, it is no longer necessary to select the
+ Test Plan element first).</p>
+
+ <note>JMeter allows you to save the entire Test Plan tree or
+ only a portion of it. To save only the elements located in a particular "branch"
+ of the Test Plan tree, select the Test Plan element in the tree from which to start
+ the "branch", and then click your right mouse button to access the Save As menu item.
+ Alternatively, select the appropriate Test Plan element and then select Save As from
+ the Edit menu.
+ </note>
+
+</section>
+
+<section name="9.7 Running the Test Plan" anchor="running">
+
+ <p>From the Run menu, select Run.</p>
+
+ <note>JMeter lights up a green square in the upper-right-hand corner to indicate if a
+ test is currently running. The square is turned gray when all tests stop. Even after
+ you select "stop", the green light will stay on until all test threads have exited.</note>
+
</section>
+
+
</body>
</document>
1.44 +79 -51 jakarta-jmeter/xdocs/usermanual/component_reference.xml
Index: component_reference.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/component_reference.xml,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- component_reference.xml 11 Jun 2003 19:01:32 -0000 1.43
+++ component_reference.xml 12 Jun 2003 12:17:17 -0000 1.44
@@ -189,57 +189,85 @@
</component>
<component name="LDAP Request" index="13.1.6" screenshot="../images/screenshots/ldap_request.png">
- <description>For testing LDAP servers</description>
- <p>There are two ways to create test cases for testing a LDAP Server.</p>
- <ol><li>Inbuilt Test cases.</li>
- <li>User defined Test cases.</li></ol>
-
-<p>There are four test scenarios of testing LDAP. The tests are given below:</p>
- <ol>
- <li>Add Test</li>
- <ol><li>Inbuilt test :
- <p>This will add a pre-defined entry in the LDAP Server and calculate
- the execution time. After execution of the test, the created entry will be
- deleted from the LDAP
- Server.</p></li>
- <li>User defined test :
- <p>This will add the entry in the LDAP Server. User has to enter all the
- attributes in the table.The entries are collected from the table to add. The
- execution time is calculated. The created entry will not be deleted after the
- test.</p></li></ol>
-
- <li>Modify Test</li>
- <ol><li>Inbuilt test :
- <p>This will create a pre-defined entry first, then will modify the
- created entry in the LDAP Server.And calculate the execution time. After
- execution
- of the test, the created entry will be deleted from the LDAP Server.</p></li>
- <li>User defined test
- <p>This will modify the entry in the LDAP Server. User has to enter all the
- attributes in the table. The entries are collected from the table to modify.
- The execution time is calculated. The entry will not be deleted from the LDAP
- Server.</p></li></ol>
-
- <li>Search Test</li>
- <ol><li>Inbuilt test :
- <p>This will create the entry first, then will search if the attributes
- are available. It calculates the execution time of the search query. At the
- end of the execution,created entry will be deleted from the LDAP Server.</p></li>
- <li>User defined test
- <p>This will search the user defined entry(Search filter) in the Search
- base (again, defined by the user). The entries should be available in the LDAP
- Server. The execution time is calculated.</p></li></ol>
-
- <li>Delete Test</li>
- <ol><li>Inbuilt test :
- <p>This will create a pre-defined entry first, then it will be deleted
- from the LDAP Server. The execution time is calculated.</p></li>
-
- <li>User defined test
- <p>This will delete the user-defined entry in the LDAP Server. The entries
- should be available in the LDAP Server. The execution time is calculated.</p></li></ol></ol>
-</component>
+ <description>This Sampler lets you send a different Ldap request(Add, Modify, Delete and Search) to a LDAP server.
+ <p>If you are going to send multiple requests to the same LDAP server, consider
+ using an <complink name="LDAP Request Defaults"/>
+ Configuration Element so you do not have to enter the same information for each
+ LDAP Request.</p> The same way the <complink name="Login Config Element"/> also using for Login and password.
+ </description>
+
+ <p>There are two ways to create test cases for testing a LDAP Server.</p>
+ <ol><li>Inbuilt Test cases.</li>
+ <li>User defined Test cases.</li></ol>
+
+ <p>There are four test scenarios of testing LDAP. The tests are given below:</p>
+ <ol>
+ <li>Add Test</li>
+ <ol><li>Inbuilt test :
+ <p>This will add a pre-defined entry in the LDAP Server and calculate
+ the execution time. After execution of the test, the created entry will be
+ deleted from the LDAP
+ Server.</p></li>
+ <li>User defined test :
+ <p>This will add the entry in the LDAP Server. User has to enter all the
+ attributes in the table.The entries are collected from the table to add. The
+ execution time is calculated. The created entry will not be deleted after the
+ test.</p></li></ol>
+
+ <li>Modify Test</li>
+ <ol><li>Inbuilt test :
+ <p>This will create a pre-defined entry first, then will modify the
+ created entry in the LDAP Server.And calculate the execution time. After
+ execution
+ of the test, the created entry will be deleted from the LDAP Server.</p></li>
+ <li>User defined test
+ <p>This will modify the entry in the LDAP Server. User has to enter all the
+ attributes in the table. The entries are collected from the table to modify.
+ The execution time is calculated. The entry will not be deleted from the LDAP
+ Server.</p></li></ol>
+
+ <li>Search Test</li>
+ <ol><li>Inbuilt test :
+ <p>This will create the entry first, then will search if the attributes
+ are available. It calculates the execution time of the search query. At the
+ end of the execution,created entry will be deleted from the LDAP Server.</p></li>
+ <li>User defined test
+ <p>This will search the user defined entry(Search filter) in the Search
+ base (again, defined by the user). The entries should be available in the LDAP
+ Server. The execution time is calculated.</p></li></ol>
+
+ <li>Delete Test</li>
+ <ol><li>Inbuilt test :
+ <p>This will create a pre-defined entry first, then it will be deleted
+ from the LDAP Server. The execution time is calculated.</p></li>
+
+ <li>User defined test
+ <p>This will delete the user-defined entry in the LDAP Server. The entries
+ should be available in the LDAP Server. The execution time is calculated.</p></li></ol></ol>
+ <properties>
+ <property name="Name" required="No">Descriptive name for this controller that is shown in the tree.</property>
+ <property name="Server Name or IP" required="Yes">Domain name or IP address of the LDAP server.
+ JMeter assumes the LDAP server is listening on the default port(389).</property>
+ <property name="Port" required="Yes">default port(389).</property>
+ <property name="root DN" required="Yes">DN for the server to communicate</property>
+ <property name="Username" required="Usually">LDAP server username.</property>
+ <property name="Password" required="Usually">LDAP server password.</property>
+ <property name="Entry DN" required="yes">the name of the context to create or Modify; may not be empty Example: do you want to add cn=apache,ou=test
+ you have to add in table name=cn, value=apache
+ </property>
+ <property name="Delete" required="yes">the name of the context to Delete; may not be empty</property>
+ <property name="Search base" required="yes">the name of the context or object to search</property>
+ <property name="Search filter" required="yes"> the filter expression to use for the search; may not be null</property>
+ <property name="add test" required="yes"> this name, value pair to added in the given context object</property>
+ <property name="modify test" required="yes"> this name, value pair to add or modify in the given context object</property>
+ </properties>
+
+ <links>
+ <link href="build-ldap-test-plan.html">Building a Ldap Test Plan</link>
+ <complink name="LDAP Request Defaults"/>
+ </links>
+</component>
<component name="WebService(SOAP) Request (Alpha Code)" index="13.1.7" screenshot="../images/screenshots/webservice_sampler.png">
<description><p>This sampler has been tested with IIS Webservice running .NET 1.0. It hasn't been tested with SUN or IBM webservices providers, but it should work. The sampler uses Apache SOAP driver, to serialize the message and set the header with the correct SOAPAction. Right now the sampler doesn't support automatic WSDL handling, since Apache SOAP currently doesn't provide support for it. Both IBM and SUN provide WSDL drivers.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
patch for Updating index.xml
Posted by Elanjchezhiyan <ch...@siptech.co.in>.
Hi Developers,
I am herewith sending you patch file for index.xml to
updating the index.html for LDAP Sampler
Regards,
Elan
--
T.Elanjchezhiyan SIP Technologies & Exports Ltd.,
Software Engineer Elnet SoftwareCity, Chennai, India.
Core Technology Group URL:http://www.siptech.com/
Chezhiyan@siptech.co.in Ph: +91-44-22541473/4 x306
patch for Updating index.xml
Posted by Elanjchezhiyan <ch...@siptech.co.in>.
Hi Developers,
Sorry I have problem in my machine, patch file for
index.xml to updating the index.html for LDAP Sampler
Regards,
Elan
--
T.Elanjchezhiyan SIP Technologies & Exports Ltd.,
Software Engineer Elnet SoftwareCity, Chennai, India.
Core Technology Group URL:http://www.siptech.com/
Chezhiyan@siptech.co.in Ph: +91-44-22541473/4 x306