User Guide
Table Of Contents
- Contents
- Introduction
- Administering ColdFusion MX 7
- Administering ColdFusion MX
- Using the ColdFusion MX Administrator
- Contents
- Initial administration tasks
- Accessing user assistance
- Server Settings section
- Data & Services section
- Debugging & Logging section
- Extensions section
- Event Gateways section
- Security section
- Packaging and Deployment section
- Enterprise Manager section
- Custom Extensions section
- Administrator API
- Data Source Management
- Contents
- About JDBC
- Adding data sources
- Connecting to DB2 Universal Database
- Connecting to Informix
- Connecting to Microsoft Access
- Connecting to Microsoft Access with Unicode
- Connecting to Microsoft SQL Server
- Connecting to MySQL
- Connecting to ODBC Socket
- Connecting to Oracle
- Connecting to other data sources
- Connecting to Sybase
- Connecting to JNDI data sources
- Web Server Management
- Deploying ColdFusion Applications
- Administering Security
- Using Multiple Server Instances
- Administering Verity
- Introducing Verity and Verity Tools
- Indexing Collections with Verity Spider
- Using Verity Utilities
- Contents
- Overview of Verity utilities
- Using the mkvdk utility
- Using the rck2 utility
- Using the rcvdk utility
- Using the didump utility
- Using the browse utility
- Using the merge utility
- Index
Maintenance options 137
Choose one of the following arguments to determine which message types are logged:
Maintenance options
The following sections describe the Verity Spider maintenance options.
-nooptimize
Prevents Verity Spider from optimizing the collection, thus reducing processing overhead during
indexing. Use this option sparingly, as it leaves the collection in less than optimum shape. The
following are some examples of when you might want to use this option:
• You want to manually perform custom optimization of the collection, using the mkvdk utility.
By default, the Verity Spider optimization mimics the mkvdk actions of maxmerge and
vdbopt. For more information on the mkvdk utility, see Verity Command-Line Indexing
Reference and “Using the mkvdk utility” on page 142.
• You are running multiple indexing jobs against a collection, and want to wait until they are all
finished to optimize.
Generally, you should not leave a collection unoptimized for too long, as search times can slow
significantly.
In brief, optimizing a collection means creating a small number of large partitions, which can
greatly reduce search times.
Loglevel
arguments
Description
summary Includes the following message types:
information, warning, error, badkey, progress, summary
Use this option only if you do not want skip type messages.
skip Includes the following message types:
information, warning, error, badkey, progress, skip
Use this option only if you do not want summary type messages.
verbose Includes the following message types:
information, warning, error, badkey, progress, summary, skip
debug Includes the following message types:
information, warning, error, badkey, progress, summary, skip, debug
Note: Only use this argument at the direction of Verity technical support or for
troubleshooting indexing problems.
trace Includes the following message types:
information, warning, error, badkey, progress, summary, skip, debug, trace
Note: Only use this argument at the direction of Verity technical support or for
troubleshooting indexing problems.