Xerox DocuShare Support & Software プリント

ページ / 10
Best Practices for Content Indexing
5
To set SplitNumbers to true, run the command idoltool.bat -s setconfig idol 
Server.SplitNumber true
.
Note: 
The SplitNumbers default value is false. Setting this value to true disables wildcard 
searching on numbers.
Index the Site 
Note: 
Important last step (optional if the site was indexed in 6.5.3.)
Run dsindex index_all
After making any changes from the IDOL Server Configuration section above, run dsindex 
index_all
 for the changes to take effect.
When dsindex index_all is running while the server is in production use, the command will 
automatically pause to favor content indexing related to user activities. Indexing resumes 
when the user load is reduced.
Pause and restart dsindex index_all
New in DocuShare 6.6.1; pause dsindex index_all with the dsindex stop command, then 
restart with dsindex -continue index_all.
Note: 
After the initial dsindex index_all has completed, future indexing can be controlled by 
using the following two options; Index by classname or Batch index jobs by file size.
Index by classname 
Consider running dsindex by class type, especially if there are many documents stored as 
custom/cloned document objects.
dsindex -classname<classname>index 
When indexing by classname, as a replacement for index_all, index each object class in the 
same order run by dsindex index_all; Users, Groups, Collections, Documents, and custom 
cloned objects.
Batch index jobs by file size
Consider using the dsindex -fsizemin<number> and -fsizemax<number> options to batch 
index larger content files during non-peak user load times. 
Note: 
The contentIndexMaxFileSize <maxfilesize in bytes> configuration setting supersedes 
the dsindex -fsizemax value.
Notes for DocuShare 6.5.3 and 6.6.0 upgrades
DocuShare 6.5.3 and 6.6.0 were configured with DREREFERENCE enabled. 
DocuShare 6.6.1 is configured with DREREFERENCE disabled. 
This change reduces memory usage and startup time of content.exe. To take advantage of 
this change a site upgraded from 6.5.3 or 6.6.0 must run the regeneratematchindex 
command. This will regenerate the indices and should be done at a convenient time when it 
will not affect users. 
Back up the IDOL index data in the DSHOME\IDOLServer\IDOL\content directory before 
running this command. 
Skip this step if dsindex index_all was completed after upgrading to 6.6.1.