Sun OpenSSO Enterprise 8.0 Installation and Configuration Guide

Enabling Persistent Searches

The OpenSSO Enterprise Event Service (amEventService) creates and manages the persistent search connections. Since persistent searches are disabled by default, use the following methods to enable them

The Directory Server nsslapd-maxpsearch attribute defines the maximum number of persistent searches that can be performed on Directory Server. For example:

Property Value  Entry DN: cn=config
Valid Range: 1 to maximum threadnumber
Default Value: 30
Syntax: Integer
Example: nsslapd-maxpsearch: 30

The Directory Server nsIdletimeout attribute does not apply to these connections. A connection is closed when the Directory Server or OpenSSO Enterprise server goes down or after a load balancer or firewall TCP timeout.

ProcedureTo Enable Persistent Searches Using the Console

  1. Log in to the Admin Console as amadmin.

  2. Click Configuration, Servers and Sites, server-name, SDK, and then Event Service.

  3. In the Disable Event Service Connection field, specify only the searches you want to disable, including aci, sm, or um (or a combination, with each item separated by a comma).

    That is, to enable a persistent search, make sure that aci, sm, or um is not present in this files.

  4. Click Save and log out of the Console.

  5. Restart the OpenSSO Enterprise web container.

Enabling Persistent Searches by Setting the Property

You can also enable persistent searches by setting the property, using the ssoadm command.

To enable a specific persistent searches, make sure the respective persistent search value (aci, sm, or um) is not is not included in the property.

Values are case insensitive. To specify multiple values, separate each value with a comma.

For example, to enable persistent searches for ACI changes only:,um

After you set the property, restart the OpenSSO Enterprise web container for the new values to take effect.