Resolving email addresses as Sametime IDs more efficiently

You can configure a custom Java™ class filter to ensure the efficient resolving of email address as IBM® Sametime® IDs (STId).

About this task

When you process an external user request to interact with an internal user, the Sametime Gateway requests that the Sametime Community Server interpret (resolve) the internal user's email address as the internal user's Sametime ID (STId). The Sametime Community Server resolves the STId, by searching LDAP with the user's email as the search filter. Multiple simultaneous queries could lead to a performance issue. Sametime Gateway is expected to report slow resolve behavior with messages like the following one:

CLFRC0268W
Performance warning: The resolve operation: Email --> STId ( {0} --> {1} ) 
took {2} seconds to complete. Review your community server and/or LDAP 
configuration, and consult the Sametime Gateway Infocenter. 
Awaiting {3} more resolve requests to complete.

Procedure

To ensure an effective LDAP search, verify that you have a configured a custom Java class that can generate an efficient email to STId LDAP search. Using the Sametime Community Server default LDAP search leads to degraded performance caused by a full scan of the LDAP tree. The example StLdapCustomized class described in Creating custom Java classes for searching the LDAP provides an efficient way to resolve email to STId. You might also consider limiting the base DN in which to search. See one of the steps in Sametime Prerequisite: Connect to LDAP Servers on configuring a base DN.

What to do next

As an additional step for optimizing the LDAP searches on the Community server, you can also include or exclude certain domains from user and group directory lookups.