143 lines
9.4 KiB
HTML
143 lines
9.4 KiB
HTML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="dc.language" scheme="rfc1766" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow"/>
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<title>Directory Server (LDAP) - Manage connection properties</title>
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
|
</head>
|
|
<body>
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
|
|
|
<img src="delta.gif" alt="Start of change" />
|
|
<a name="rzahymanconnprop"></a>
|
|
<h2 id="rzahymanconnprop">Manage connection properties</h2>
|
|
<p>The ability to manage connection properties enables you to prevent clients
|
|
from locking up the server. It also ensures that the administrator always
|
|
has access to the server in the cases that the backend is kept busy with long-running
|
|
tasks. Management of the connection properties is done through the Web administration
|
|
tool. </p>
|
|
<a name="wq149"></a>
|
|
<div class="notetitle" id="wq149">Note:</div>
|
|
<div class="notebody">These selections are displayed only if you are logged
|
|
in as the administrator or a member of the administration group on a server
|
|
that supports this function.</div>
|
|
<p>To set connection properties, perform the following steps:</p>
|
|
<ol type="1">
|
|
<li>Expand the <span class="bold">Server administration</span> category
|
|
in the navigation area and click <span class="bold">Manage connection
|
|
properties</span>.
|
|
<a name="wq151"></a>
|
|
<div class="notetitle" id="wq151">Note:</div>
|
|
<div class="notebody">To change server configuration settings using
|
|
the tasks in the Server administration category of the Web Administration
|
|
tool, you must authenticate to the server as an i5/OS user profile that has
|
|
*ALLOBJ and IOSYSCFG special authorities. This can be done by authenticating
|
|
as a projected user with the password for that profile. To bind as a projected
|
|
user from the Web administration tool, enter a username of the form <tt class="xph">os400-profile=MYUSERNAME,cn=accounts,os400-sys=MYSYSTEM.COM</tt>, where MYUSERNAME
|
|
and the MYSYSTEM.COM strings are replaced with your user profile name and
|
|
the configured system projection suffix, respectively.</div></li>
|
|
<li>Select the <span class="bold">General</span> tab.</li>
|
|
<li>Set the anonymous connection setting. The <span class="bold">Allow
|
|
anonymous connections</span> check box is already selected for you so that anonymous
|
|
binds are allowed. This is the default setting. You can click the check box
|
|
to deselect the <span class="bold">Allow anonymous connections</span> function.
|
|
This action causes the server to unbind all anonymous connections.
|
|
<a name="wq152"></a>
|
|
<div class="notetitle" id="wq152">Note:</div>
|
|
<div class="notebody">Some applications might fail if you disallow anonymous binds.</div></li>
|
|
<li>In the <span class="bold">Cleanup threshold for anonymous connections</span> field, set the threshold number to initiate the unbinding of anonymous
|
|
connections. You can specify a number between 0 and 65535 .
|
|
<a name="wq153"></a>
|
|
<div class="notetitle" id="wq153">Note:</div>
|
|
<div class="notebody">The actual maximum number is limited by the number of files permitted per
|
|
process. On UNIX systems you can use the <span class="bold">ulimit -a</span> command
|
|
to determine the limits. On Windows systems this is a fixed number.</div>The default setting is 0. When this number of anonymous connections
|
|
is exceeded, connections are cleaned up based on the idle timeout limit that
|
|
you set in the <span class="bold">Idle time out</span> field.</li>
|
|
<li>In the <span class="bold">Cleanup threshold for authenticated connections</span> field, set the threshold number to initiate the unbinding of authenticated
|
|
connections. You can specify a number between 0 and 65535 .
|
|
<a name="wq154"></a>
|
|
<div class="notetitle" id="wq154">Note:</div>
|
|
<div class="notebody">The actual maximum number is limited by the number of
|
|
files permitted per process. On UNIX systems you can use the ulimit -a command
|
|
to determine the limits. On Windows systems this is a fixed number.</div>The default setting is 1100. When this number of authenticated connections
|
|
is exceeded, connections are cleaned up based on the idle timeout limit that
|
|
you set in the <span class="bold">Idle time out</span> field.</li>
|
|
<li>In the <span class="bold">Cleanup threshold for all connections</span> field, set the threshold number to initiate the unbinding of all connections.
|
|
You can specify a number between 0 and 65535 .
|
|
<a name="wq155"></a>
|
|
<div class="notetitle" id="wq155">Note:</div>
|
|
<div class="notebody">The actual maximum
|
|
number is limited by the number of files permitted per process. On UNIX systems
|
|
you can use the ulimit -a command to determine the limits. On Windows systems
|
|
this is a fixed number.</div>The default setting is 1200. When
|
|
this total number of connections is exceeded, connections are cleaned up based
|
|
on the idle timeout limit that you set in the <span class="bold">Idle
|
|
time out</span> field.</li>
|
|
<li>In the <span class="bold">Idle timeout limit</span> field, set the
|
|
number of seconds that a connection can be idle before it is closed by a cleanup
|
|
process. You can specify a number between 0 and 65535 .
|
|
<a name="wq156"></a>
|
|
<div class="notetitle" id="wq156">Note:</div>
|
|
<div class="notebody">The actual maximum number is limited by the number of files permitted per
|
|
process. On UNIX systems you can use the ulimit -a command to determine the
|
|
limits. On Windows systems this is a fixed number.</div>The default
|
|
setting is 300. When a cleanup process is initiated, any connections, subject
|
|
to the process, that exceed the limit are closed.</li>
|
|
<li>In the <span class="bold">Result timeout limit</span> field, set
|
|
the number of seconds that are allowed between write attempts. You can specify
|
|
a number between 0 and 65535 . The default setting is 120. Any connections
|
|
that exceed this limit are ended.
|
|
<a name="wq157"></a>
|
|
<div class="notetitle" id="wq157">Note:</div>
|
|
<div class="notebody">This applies to Windows systems
|
|
only. A connection that exceeds 30 seconds is automatically dropped by the
|
|
operating system. Therefore, this <span class="bold">Result timeout
|
|
limit</span> setting is overridden by the operating system after 30 seconds.</div></li>
|
|
<li>Click the <span class="bold">Emergency thread</span> tab.</li>
|
|
<li>Set the emergency thread setting. The <span class="bold">Enable
|
|
emergency thread</span> check box is already selected for you so that the emergency
|
|
thread can be activated. This is the default setting. You can click the check
|
|
box to deselect the <span class="bold">Enable emergency thread</span> function.
|
|
This action prevents the emergency thread from being activated.</li>
|
|
<li>In the <span class="bold">Pending request threshold</span> field,
|
|
set the number limit for work requests that activate the emergency thread.
|
|
Specify a number between 0 and 65535 to set the limit of work requests that
|
|
can be in the queue before activating the emergency thread. The default is
|
|
50. When the specified limit is exceeded, the emergency thread is activated.</li>
|
|
<li>In the <span class="bold">Time threshold</span> field, set the number
|
|
of minutes that can elapse since the last work item was removed from the queue.
|
|
If there are work items in the queue and this time limit is exceeded, the
|
|
emergency thread is activated. You can specify a number between 0 and 240
|
|
. The default setting is 5.</li>
|
|
<li>Select from the drop-down menu, the criteria to be used to activate the
|
|
emergency thread. You can select:
|
|
<ul>
|
|
<li><span class="bold">Size only:</span> The emergency thread is activated only
|
|
when the queue exceeds the specified amount of pending work items.</li>
|
|
<li><span class="bold">Time only:</span> The emergency thread is activated only
|
|
when the time limit between removed work items exceeds the specified amount.</li>
|
|
<li><span class="bold">Size or time:</span> The emergency thread is activated
|
|
when either the queue size or time threshold exceeds the specified amounts.</li>
|
|
<li><span class="bold">Size and time:</span> The emergency thread is activated
|
|
when both the queue size and the time threshold exceed the specified amounts.</li></ul>Size and time is the default setting.</li>
|
|
<li>Click <span class="bold">OK</span></li></ol>
|
|
<p>For more information, see <a href="rzahymanservconn.htm#rzahymanservconn">Manage server connections</a>.</p><img src="deltaend.gif" alt="End of change" />
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
|
</body>
|
|
</html>
|