In addition to increasing the timeout, disable callbacks where they aren't needed.
See the "Configuring" guide: See External-Authentication-Return-Data-Capabilities in ar.conf section. To quote the guide: "A bit mask that allows you to specify the return data capabilities for the current AREA plug-in. This setting does not control the AREA plug-in, it merely describes the behavior of the plug-in, allowing for server optimization. Acceptable values are as follows: Bit 1 (Value=1)—No email address will be provided. Bit 2 (Value=2)—No notify mechanism will be provided. Bit 3 (Value=4)—No group identifiers will be provided. Bit 4 (Value=8)—No license information will be provided. Bit 5 (Value=16)—No notification user validation should occur. The default is 0, meaning the server will attempt to retrieve this information from AREA. A value of 7 will allow the server to potentially reduce the number of AREA related calls during notification processing. A value of 16 will allow the server to avoid using AREA for notification user validation and information retrieval. Use this setting for sites using a form of AREA that applies user names as email addresses and where there is no benefit to accessing an authentication database." You can eliminate all the calls by using a value of 31. This should be configured to match the information you store and retrieve from the directory. Axton Grams On 2/19/07, Anthony K R <[EMAIL PROTECTED]> wrote:
Hi Scott, Here is the answers 1) Yes 2) Using AR Admin tool click File -> Server Information -> Timeouts (tab). The value in the field 'Need to Sync' determine this 3) In the value is '0' then there would be no repeated checks. Default is 300 sec. For more info, please read the config doc. Regards, Anthony -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Scott Kemme Sent: Friday, February 09, 2007 11:01 PM To: [email protected] Subject: Remedy performance affected by LDAP issues All, My organization's LDAP servers have apparently reached their limit. when that limit is exceeded, Remedy users (and other LDAP using apps) see performance lags on saves, etc. it looks like Remedy is checking credentials against the LDAP again even though these users have already logged in successfully. so here are my questions: 1) Does Remedy call LDAP again after users are already logged in? 2) if so, how often and when (just on writes or reads and writes)? 3) is there a way to extend the time in between calls? thanks, scott ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
