📄 build-ldapext-test-plan.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>JMeter - User's Manual: Building an Extended LDAP Test Plan</title>
</head>
<body bgcolor="#ffffff" text="#000000" link="#525D76">
<table border="0" cellspacing="0">
<tr>
<td colspan="2">
<a href="http://jakarta.apache.org"><img width="505" height="48" src="../../docs/images/jakarta-logo.gif" align="left" border="0"></a>
</td>
</tr>
</table>
<table border="0" cellspacing="4">
<tr><td>
<hr noshade size="1">
</td></tr>
<tr>
<td align="left" valign="top">
<table>
<tr>
<td bgcolor="#525D76">
<div align="right"><a href="index.html"><font size=-1 color="#ffffff" face="arial,helvetica,sanserif">Index</font></a></div>
</td>
<td bgcolor="#525D76">
<div align="right"><a href="build-ws-test-plan.html"><font size=-1 color="#ffffff" face="arial,helvetica,sanserif">Next</font></a></div>
</td>
<td bgcolor="#525D76">
<div align="right"><a href="build-ldap-test-plan.html"><font size=-1 color="#ffffff" face="arial,helvetica,sanserif">Prev</font></a></div>
</td>
</tr>
</table>
<br>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="ldapexttest"><strong>9b. Building an Extended LDAP Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p>
In this section, you will learn how to create a basic Test Plan to test an LDAP
server.
</p>
<p>
As the Extended LDAP Sampler is highly configurable, this also means that it takes
some time to build a correct testplan. You can however tune it exactly up to your
needs.
</p>
<p>
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:
<br>
</br>
<a href="test_plan.html#thread_group">
Thread Group
</a>
,
<br>
</br>
<a href="../usermanual/component_reference.html#Adding_LDAP_Extended_Request_Defaults">Adding LDAP Extended Request Defaults</a>
,
<br>
</br>
<a href="../usermanual/component_reference.html#Adding_LDAP_Requests">Adding LDAP Requests</a>
, and
<br>
</br>
<a href="../usermanual/component_reference.html#Adding_a_Listener_to_View/Store_the_Test_Results">Adding a Listener to View/Store the Test Results</a>
</p>
<p>
This example assumes that the LDAP Server is installed in your Local machine.
</p>
<p>
For the less experienced LDAP users, I build a
<a href="ldapops_tutor.html">
small
LDAP tutorial
</a>
which shortly explains
the several LDAP operations that can be used in building a complex testplan.
</p>
<p>
Take care when using LDAP special characters in the distinghuished name, in that case (eg, you want to use a + sign in a
distinghuished name) you need to escape the character by adding an "\" sign before that character.
extra exeption: if you want to add a \ character in a distinguished name (in an add or rename operation), you need to use 4 backslashes.
examples:
cn=dolf\+smits to add/search an entry with the name like cn=dolf+smits
cn=dolf \\ smits to search an entry with the name cn=dolf \ smits
cn=c:\\\\log.txt to add an entry with a name like cn=c:\log.txt
</p>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="ext_adding_users"><strong>9b.1 Adding Users</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p>
The first step you want to do with every JMeter Test Plan is to add a Thread Group element.
The Thread Group tells JMeter the number of users you want to simulate, how often the users should send
requests, and the how many requests they should send.
</p>
<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>
<p>
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../../docs/images/screenshots/ldaptest/extthreadgroup.png"><br>
<font size="-1">
Figure 9b.1. Thread Group with Default Values
</font></td></tr></table></p>
</p>
</blockquote>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="add_ldapext_defaults"><strong>9b.2 Adding LDAP Extended Request Defaults</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p>
Begin by selecting the Thread Group element. Click your right mouse button
to get the Add menu, and then select Add --> Config Element -->LDAP Extended Request Defaults. Then,
select this new element to view its Control Panel.
</p>
<p>
Like most JMeter elements, the LDAP Extended Request Defaults Control Panel has a name
field that you can modify. In this example, leave this field with the default value.
</p>
<p>
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../../docs/images/screenshots/ldaptest/extrequestdefaults.png"><br>
<font size="-1"><br>
</br>
Figure 9b.2 LDAP Defaults for our Test Plan
</font></td></tr></table></p>
</p>
<p>
For each of the different operations, some default values can be filled in.
In All cases, when a default is filled in, this is used for the LDAP extended requests.
For each requst, you can override the defaults by filling in the values in the LDAP extended request sampler.
When no valueis entered which is necesarry for a test, the test will fail in an unpredictable way!
</p>
</blockquote>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="add_extrequests"><strong>9b.3 Adding LDAP Requests</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p>
In our Test Plan, we want to use all 8 LDAP requests.
</p>
<ol>
<li>
Thread bind
</li>
<li>
Search Test
</li>
<li>
Compare Test
</li>
<li>
Single bind/unbind Test
</li>
<li>
Add Test
</li>
<li>
Modify Test
</li>
<li>
Delete Test
</li>
<li>
Rename entry (moddn)
</li>
<li>
Thread unbind
</li>
</ol>
<p>
JMeter sends requests in the order that you add them to the tree.
</p>
<p>
Adding a requests always start by:
<br>
</br>
Adding the LDAP Extended Request to the Thread Group element (Add -->
Sampler --> LDAP Ext Request). Then, select the LDAP Ext Request element in the tree
and edit the following properties.
</p>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="add_threadbind"><strong>9b.3.1 Adding a Thread bind Request</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p>
<ol>
<li>
Select the "Thread bind" button.
</li>
<li>
enter the hostname value from the LDAP server in the Servername field
</li>
<li>
Enter the portnumber from the LDAP server (389) in the port field
</li>
<li>
(optional) enter the baseDN in the DN field, this baseDN will be used as thestarting point for searches, add, deletes etc.
<br>
</br>
take care that this must be the uppermost shared level for all your request, eg When all information is stored under ou=people, dc=siemens, dc=com, you can use this value in the basedn.
<br>
</br>
You cannot search or rename anymore in the subtree ou=users,dc=siemens,dc=com!
<br>
</br>
If you need to search or rename objects in both subtrees, use the common denominator (dc=siemens,dc=com) as the baseDN.
</li>
<li>
(Optional) enter the distinghuised name from the user you want to use for authentication.
When this field is kept empty, an anonymous bind will be established.
</li>
<li>
(optional) Enter the password for the user you want to authenticate with, an empty password will also lead to an anonymous bind.
</li>
</ol>
</p>
<p>
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../../docs/images/screenshots/ldaptest/extthreadbind.png"><br>
<font size="-1">
Figure 9b.3.1. Thread Bind example
</font></td></tr></table></p>
</p>
</blockquote>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="add_searchreq"><strong>9b.3.2 Adding a search Request</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p>
<ol>
<li>
Select the "Search Test" button.
</li>
<li>
(Optional) enter the searchbase under which you want to perform the search, relative to the basedn, used in the thread bind request.
<br>
</br>
When left empty, the basedn is used as a search base, this files is important if you want to use a "base-entry" or "one-level" search (see below)
</li>
<li>
Enter the searchfilter, any decent LDAP serach filter will do, but for now, use something simple, like cn=john doe
</li>
<li>
(optional) enter the scope in the scope field, it has three options:
<ol>
<li>
Base level, Enter the value 0
<br>
</br>
only the given searchbase is used, only for checking attributes or existence.
</li>
<li>
One level, Enter the value 1
<br>
</br>
Only search in one level below given searchbase is used
</li>
<li>
Subtree, Enter the value 2
<br>
</br>
Searches for object at any point below the given basedn
</li>
</ol>
</li>
<li>
(Optional) Sizelimit, specifies the maximun number of returned entries,
</li>
<li>
(optional) Timelimit, psecifies the maximum number of miliseconds, the SERVER can use for performing the search. it is NOT the maximun time the application will wait!
<br>
</br>
When a very large returnset is returned, from a very fast server, over a very slow line, you may have to wait for ages for the completion of the search request, but this parameter will not influence this.
</li>
<li>
(Optional) Attributes you want in the search answer. This can be used to limit the size of the answer, especially when an onject has very large attributes (like jpegPhoto). There are three possibilities:
<ol>
<li>
Leave empty (the default setting must also be empty) This will return all attributes.
</li>
<li>
Put in one empty value (""), it will request a non-existent attributes, so in reality it returns no attributes
</li>
<li>
Put in the attributes, seperated by a semi-colon. It will return only the requested attributes
</li>
</ol>
</li>
<li>
(Optional) Return object, possible values are "true" and "false". True will return all java-object attributes, it will add these to the requested attributes, as specified above.
<br>
</br>
false will mean no java-object attributes will be returned.
</li>
<li>
(Optional) Dereference aliases. possible values "true" and "false". True will mean it will follow references, false says it will not.
</li>
</ol>
</p>
<p>
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../../docs/images/screenshots/ldaptest/extsearch.png"><br>
<font size="-1">
Figure 9b.3.2. search request example
</font></td></tr></table></p>
</p>
</blockquote>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="add_comparereq"><strong>9b.3.3 Adding a Compare Request</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p>
<ol>
<li>
Select the "Compare" button.
</li>
<li>
enter the entryname form the object on which you want the compare operation to work, relative to the basedn, eg "cn=john doe,ou=people"
</li>
<li>
Enter the compare filter, this must be in the form "attribute=value", eg "mail=John.doe@siemens.com"
</li>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -