Contents Dochome
Sun Java(TM) System Directory Server Online Help

> # Limits & Controls Tab of Chained Suffix Configuration

> When handling a request on a chained suffix, your server must establish a connection and bind to the chained server. It then sends its own request to the chained server, all of which may impact performance. Use the settings on this tab to configure the interaction between your server and the chained server.

> ## Control Client Return

> These options help you specify how your server responds to client application requests that involve the chained suffix.

> Return referral on scoped search. Select this checkbox to return referrals in response to scoped searches on the chained suffix. It is more efficient, but less transparent, to return a referral so that the client may search directly on the chained server. The referrals that will be returned are defined on the Settings tab for this suffix.

> When this checkbox is not selected, the results of broad searches in chained suffixes must be transmitted twice, first to this server and then to the client. In this case you may want to limit the size and time of chained search operation with the following fields.

> Size limit. This field specifies the maximum number of entries that should be returned in response to a search request on a chained suffix. The valid range is from -1 (no limit) to 2147483647. The default size limit is 2000 entries.

> No size limit. Select this checkbox to have any number of entries returned from a chained search. Deselect this checkbox to enter a size limit.

> Time limit. This field specifies the time limit in seconds for searches on the chained suffix. After the time limit has passed, the connection is timed out and an error is returned to the requesting client. The valid range is -1 (for no limit) to 2147483647. The default value is 3600 seconds.

> No time limit. Select this checkbox to have an unlimited search time for a chained search. Deselect this checkbox to enter a time limit.

> ## Cascading Chaining

> Cascading chaining occurs when a chained suffix is chained again by the remote server. If you implement cascading chaining, use the following controls to configure its behavior.

> Check local ACI. Select this checkbox to enable evaluation of local ACIs on all chained suffixes involved in cascading chaining. Chained requests use proxy rights to access data, but cascading chaining may involve servers that do not recognize the same users. Select this checkbox if all cascading servers share the same information about users.

> Maximum hops. Specify the maximum number of hops, or links in the cascading chaining, that are allowed. Each time a request is forwarded to another link of the same chained suffix, the hop count is decremented. Each subsequent chained link contacted further decrements the count. If a chained server receives a count of 0, it determines that a loop has been detected and notifies the client application.

> The valid range of values is 0 to 20. The default maximum number of hops is 10.

> ## Connection Management

> These fields control the pool of connections maintained by the server to perform operations on the chained suffix.

> Maximum LDAP connection(s). Maximum number of LDAP connections the server may establish with the chained server. The valid range is 1 to 50 connections. The default value is 10 connections.

> Maximum TCP connection(s). Maximum number of TCP connections the server may establish with the chained server. The valid range is 0 to 50 connections. The default value is 3 connections.

> Maximum binds per connection. Maximum number of outstanding bind operations per TCP connection. The valid range is from 1 to 25 binds per connection. The default value is 10 outstanding bind operations.

> Maximum bind retries. Number of times the server will attempt to rebind to the chained server upon failure. A value of zero indicates that the server will try to bind only once. The valid range is from 0 to 10 retries. The default value is 3 retries.

> Maximum operations per connection. Maximum number of outstanding operations per connection. The valid range is from 0 to 50 operations per connection. The default value is 10 operations.

> Bind timeout. Length of time, in seconds, before a bind attempt on the chained server should time out. The default timeout is 15 seconds.

> No bind timeout. Select this checkbox to have the server wait indefinitely when binding on a chained server. Deselect this checkbox to enter a timeout.

> Timeout before abandon. The number of seconds that the server will wait for operations to complete on the chained server. After this timeout, the server will abandon the chained operation. The valid range is 0 to 2147483647 seconds. The default timeout is 10 seconds.

> No timeout before abandon. Select this checkbox to wait indefinitely for a chained operation. Deselect this checkbox to timeout for abandoning chained operations.

> Connection life. The number of seconds to keep connections open between the server and the chained server. Keeping a connection open for multiple operations will help them complete faster, but it uses more resources if there are no more pending operations. The valid range is from 0 (connections are not kept open) to 2147483647 seconds. By default, connections are closed immediately after an operation.

> Unlimited lifetime. Select this checkbox to keep all connections to a chained server open forever. You should keep connections open all the time only if you constantly have operations on this chained suffix or if the resources are not needed for other operations. Deselect this checkbox to enter a time limit for connections.

> Contents Dochome

> Copyright 2004 Sun Microsystems, Inc. All rights reserved.