Novell GROUPWISE 8 - ADMINISTRATION Administration Manual page 574

When you have a large number of user databases that need to be indexed, you can configure the
POA to index a specific range of databases based on user FIDs. For a task of this magnitude, you
should run multiple dedicated indexing POAs with each POA configured to process a specific range
of databases. Use the
You can determine the FID numbers of the databases by listing the user databases (
the
ofuser
You could also use these switches to single out a specific user database for indexing. Specify the
same FID for both switches. To determine a user's FID, click Help > About GroupWise in the
GroupWise client. In Online mode, the FID is displayed after the username. In Caching or Remote
mode, the FID is the last three characters of the Caching or Remote directory name (for example,
).
gwstr7bh
Determining Indexing Priority
The POA carries on many processes at once. If you are not using a dedicated indexing POA, you can
configure the POA to make indexing a higher or lower priority task than responding to users'
activities in their mailboxes. You can also control how many items the POA indexes in each
database that it processes. Use the
explains the priority levels:
Table 38-1
Priority Level
0
1
2
3
999
If you have users who consistently receive more items than are processed during your current daily
indexing cycle, you could implement an appropriate /qflevel setting for permanent use.
Reclaiming Disk Space
The POA uses
indexes that have not yet been compressed. At regular intervals, the POA compresses the contents of
the files and adds the data to the
.inc
files for a period of time. Use the
574 GroupWise 8 Administration Guide
/qfuserfidbeg and
directory. The xxx part of the user database name is the FID.
/qflevel
QuickFinder Indexing Priority Levels
Description
Index a maximum of 1000 items at a time, rather than the default of 500.
Index a maximum of 500 items at time, using a low-priority thread. This keeps frequent
daytime indexing cycles from interfering with users' activities in their mailboxes.
Index a maximum of 1000 items at a time, using a medium-priority thread. This allows
additional items in each database to be processed in each indexing cycle. Using a
medium-priority thread makes indexing more important than some user activities in
mailboxes. Users might notice some slowness in response from the GroupWise client.
Index a maximum of 2000 items at a time, using a high-priority thread. Using a high-
priority thread makes indexing more important than many user activities in mailboxes.
Users will notice some slowness in response from the GroupWise client. This is
warranted only when the immediate completion of indexing is extremely important.
Index constantly until all databases have been indexed, then wait until the next indexing
cycle set on the QuickFinder property page of the POA object before starting to index
again.
files to store compressed indexes. It uses
.idx
/qfdeleteold
/qfuserfidend switches to define the range for each POA.
switch to control indexing priority. The table below
.inc
files. Afterwards, it retains the previous
.idx
switch to delete the previous versions of the
userxxx.db
files to store incremental
and
.idx
.idx
) in
.inc
and