Home
Welcome to the HCL Sametime® 11.6 administration documentation
Configuring
This section provides information on configuring the servers for HCL Sametime 11.6.
Community Services
This section will discuss configuration steps specific to the HCL Sametime Community server.
Configuring LDAP
Sametime has support for LDAP and native Domino directory servers to provide the user repository. When installing Sametime, you are given an option to choose which type of directory to use. Sametime supports one directory type (LDAP or Domino directory) to be configured on the server. All Sametime Community servers must share the same directories and directory type.
Creating custom Java classes for searching LDAP
Create custom Java™ classes that provide greater control over how the Sametime® Community server conducts name searches of an LDAP directory and how results are formatted.

Welcome to the HCL Sametime® 11.6 administration documentation
- Accessibility features for Sametime
  Accessibility features help users who have a disability, such as restricted mobility or limited vision, to use information technology products successfully. HCL® strives to provide products with usable access for everyone.
- What's new in HCL Sametime
  This section describes what's new in HCL Sametime® 11.6 and Sametime® Meetings 11.6.
- Checklist to deploy Sametime
  This section provides information on reviewing the checklist to deploy the Sametime clients.
- Encryption usage in Sametime
  HCL® Sametime® uses several types of encryption to protect data.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime 11.6.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime 11.6.
- Configuring
  This section provides information on configuring the servers for HCL Sametime 11.6.
  - Setting up business cards
    You can configure the Sametime Community Server so that business card information about an individual displays when a user hovers over a name in a chat window or a contact list.
  - Community Services
    This section will discuss configuration steps specific to the HCL Sametime Community server.
    - Configuring LDAP
      Sametime has support for LDAP and native Domino directory servers to provide the user repository. When installing Sametime, you are given an option to choose which type of directory to use. Sametime supports one directory type (LDAP or Domino directory) to be configured on the server. All Sametime Community servers must share the same directories and directory type.
      - Configuring the LDAP server Document
        In previous releases of Sametime, there was a separate Administration client to configure LDAP settings. These settings are now done directly inside of the configuration database that holds the settings.
      - Excluding certain domains from user and group directory lookups
        When you use Inbox awareness, you can prevent redundant requests to the LDAP or Domino® directory by defining which domains are allowed to accept resolve requests. Previous releases allowed this filtering through the use of custom code and was available only for LDAP directories.
      - Creating custom Java classes for searching LDAP
        Create custom Java™ classes that provide greater control over how the Sametime® Community server conducts name searches of an LDAP directory and how results are formatted.
        Example: Writing a Java™ class to filter searches for people and groups
        If a single search filter is not adequate to resolve user or group name searches, you can write a Java™ class containing a method that specifies exactly how directory searches are conducted. The class can invoke different LDAP search filters depending on search criteria entered by users.
        Example: Writing a Java™ class to format names returned in a search
        To return a user name in a format that is not available in an LDAP directory entry attribute, you can write a Java™ class that manipulates existing information in the LDAP directory to produce the user name in the desired format.
        Configuring the class file on the Sametime server
    - Configuring Domino Directory
    - Updating time-to-live index for persistent chat
      The time-to-live (TTL) setting in the sametime.ini defines how long the chat history is stored in the database. The default value is 90 days. Administrators can modify the value based on the organization's preferred setting.
    - Configuring Sametime Community Server connectivity
      Review the host names and ports for Community Services on the HCL Sametime Community Server.
    - Setting the same community ID for all servers in the environment
      To ensure that clients recognize all servers in the environment as belonging to a single community, add a ST_COMMUNITY_ID value to the sametime.ini file.
  - Clustering
    This section will discuss clustering steps specific to the HCL Sametime Community server.
  - Meetings
    This section will discuss Meetings configuration steps specific to the HCL Sametime Meetings server.
- Securing
  This section provides information on securing HCL Sametime 11.6 environments.
- Administering
  This section provides information on administering HCL Sametime 11.6 environments.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Troubleshooting
  Troubleshooting and Support
- Migrating and Upgrading
  This section provides information on migrating and upgrading from an earlier Sametime release.
- Notices

Creating custom Java classes for searching LDAP

Create custom Java™ classes that provide greater control over how the Sametime® Community server conducts name searches of an LDAP directory and how results are formatted.

About this task

Creating a custom Java class can be especially effective with complex LDAP directory schemas. The Java code that you write must be compatible with the Java Run-Time Environment (JRE) version compatible with the Domino server. Domino 11 uses Java 1.8.

If your configuration is using the UUID attribute as the attribute of the person entry that defines the internal ID of a Sametime user, you should include UUID in your customized filter.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.