How to Configure Convergence To Use VLV Indexes For Address Book

(Doc ID 2379586.1)

Last updated on MARCH 30, 2018

Applies to:

Oracle Communications Convergence - Version 3.0.1 and later
Information in this document applies to any platform.

Goal

Configure Corporate Address Book to use ldap VLV indexes.

Convergence can use 2 engines for the Address Book: Contacts Server and Convergence built in. Both engines use LDAP as the backend for the Corporate Address Book. So using ldap VLV indexes can be beneficial in both cases.

Short description of what VLV index is:

When an LDAP client issues a search, it may require that the server return data in segments rather than as one long stream of data. In order for the server to successfully search and return the requested data back to client "block by block" within the acceptable time limit, a VLV index (also known as browsing index) needs to be created on the server; otherwise the search will be unindexed (notes=U).

Reference: How to Configure VLV Indexes on Oracle Directory Server Enterprise Edition (ODSEE) (Doc ID 1396420.1)

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms