Indexing and Search Service Post Configuration

Skip to end of metadata
Go to start of metadata

Indexing and Search Service for Oracle Communications Unified Communications Suite Post Configuration
Version 1 Update 4

This information contains procedures that you might need to run after installing and configuring Indexing and Search Service for Oracle Communications Unified Communications Suite 1 Update 4.

Topics:

Enabling Autoprovisioning

Autoprovisioning enables you to add new accounts to the ISS store automatically. By using autoprovisioning, you make account creation less prone to error than when manually bootstrapping accounts. However, unlike the issadmin.sh command, which gives you control over the group or singleton status for an account, autoprovisioning simply creates the account in the next
available index group in the ISS store by using the default allocation policy See ISS Store Instance Overview and Concepts for more information about the default allocation policy.

To Enable ISS Autoprovisioning

  1. Edit the jiss.conf file and set the iss.autoprovision.enabled configuration parameter to true.
  2. Refresh the ISS configuration for the change to take place.

For more information on autoprovisioning, see Autoprovisioning ISS Accounts.

Enabling Periodic Auto-sync

This feature checks every ISS account against Messaging Server accounts at regular intervals to detect differences, for example, from a reconstructed folder or lost event notifications, that ISS can then automatically correct.

To Enable Periodic Autosync
  1. Edit the jiss.conf file and set the iss.indexsvc.periodic.autosync.enabled configuration parameter to true.
  2. (Optional) Set the iss.indexsvc.periodic.autosync.interval configuration parameter to specify the number of seconds to wait from the start of one period until the start of the next autosync period.
    The default is 300 seconds.
  3. (Optional) Set the iss.indexsvc.periodic.autosync.count configuration parameter to specify the number of accounts to process from the list of accounts yet to be synced during each period.
    The default is 1000.
  4. Refresh the ISS configuration for the change to take place.
  5. For tuning suggestions, see Other Tuning Controls of Periodic Autosync.

For more information on periodic autosync, see Enabling Periodic Autosync.

Enabling Autobootstrapping of Accounts

Similar to the situation for active accounts described in Overview of Periodic Automatic Synchronization, accounts which have not been bootstrapped or autoprovisioned may cause event notifications of changes to such accounts to fail. To correct these accounts, you can use the autobootstrapping feature, which is useful if you want your deployment to index uninitialized accounts under such conditions.

To Enable Periodic Autobootstrap
  1. Edit the jiss.conf file and set the iss.indexsvc.periodic.autobootstrap.enabled configuration parameter to true.
  2. (Optional) Set the iss.indexsvc.periodic.autobootstrap.interval configuration parameter to specify the number of seconds to wait from the start of one period until the start of the next autobootstrap period.
    The default is 300 seconds.
  3. (Optional) Set the iss.indexsvc.periodic.autobootstrap.count configuration parameter to specify the number of accounts to process from the list of accounts yet to be bootstrapped during each period.
    The default is 500.
  4. Refresh the ISS configuration for the change to take place.

For more information, see Enabling Periodic Autobootstrap.

Enabling the Watcher Service

This feature is designed for the implementation of highly available (HA) ISS nodes, however the service itself is useful even when you do not use HA. The watcher service provides local host monitoring of ISS services and alerts you, with log file messages and email warnings, when it detects a service outage. Once alerted, you can take the appropriate corrective action, such as restarting a service.

To Enable the ISS Watcher Service

To enable the watcher service on an ISS node, configure the appropriate iss.cluster and iss.watcher parameters in the jiss.conf file as described in Administering the ISS Watcher Service.

Labels:
indexsearchservice indexsearchservice Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.