ADMINISTRATION TOOLS

Scheduling Administration Request processing
Each setting in the Administration Process section of the Server document controls the timing of specific types of requests. Interval settings and replication schedules for each server determine how quickly the administrative settings replicate throughout the domain. As these requests are carried out, the speed with which they are replicated to the appropriate databases in the domain depends on the replication schedule for those servers. If necessary, you can schedule separate replication events for more immediate updates.

To adjust the default timing of when administration requests are carried out, edit the Server document. You may want to force a request to occur immediately if the administration request is critical.

To schedule Administration Process requests

1. From the IBM® Lotus® Domino® Administrator, click the Configuration tab.

2. Choose Server - All Server Documents.

3. Select the server whose server document you are editing.

4. Click the Server Tasks - Administration Process tab.

5. Complete these fields, and then click Save and Close.
FieldEnter
IntervalThe number of minutes that pass between the processing of name-management requests -- rename, delete, and recertify. The default is 60 minutes.
Execute once a day requests atThe time when updates to Person documents occur and "Rename person in unread lists" requests run. The default is 12 AM.
Start executing onThe day on which Updates to Authors and Readers fields in a database and discovery of shared and private design elements for a deleted person occur. The default is Sunday.
Start executing atThe time when the updates to Authors and Readers fields in a database and discovery of shared and private design elements for a deleted person occur. The default is 12 AM.
Mail file moves expire afterThe number of days during which the IBM® Lotus® Notes® client will update mail-related changes. The default is 21 days. Valid values are 7 to 60, inclusive.
Store Admin Process log entries when status of no change is recordedLogs a "No change" status entry in the Administration Process log each time a database is scanned to determine whether an administration request requires a change to that database and no change is made. The default is No. Keeping this field set to "No" may greatly reduce the size of the Administration Request database.
Suspend Admin Process at(Optional) Time when the Administration Process stops processing requests. To conserve server resources, suspend the Administration Process during peak computer hours.
Restart Admin Process at(Optional) Time when the Administration Process starts processing requests again. To conserve server resources, set the Administration Process to restart during non-peak computer usage hours.
Related topics