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

136 Chapter 9: Indexing Collections with Verity Spider
-msgdb
Syntax:
-msgdb path
Specifies the path to the ind.msg message database file.
If Verity Spider was installed properly, this option should be unnecessary. By default, the ind.msg
message database file is read from the following directory:
cf_root/lib/platform/bin
Where platform represents the platform directory.
Logging options
The following sections describe the Verity Spider logging options.
-loglevel
Syntax:
-loglevel [nostdout] argument
Specifies the types of messages to log. By default, messages are written to standard output and to
various log files in the subdirectory named /log beneath the Verity Spider job directory. If you add
nostdout to the
-loglevel option, messages are not written to standard output. Log files,
however, are still created.
The following table describes valid message types:
Message type Description
information Licensing information written to info.log. Included with all arguments.
warning Warning messages written to warning.log. Included with all arguments.
error Error messages written to error.log. Included with all arguments.
badkey Messages regarding keys that could not be indexed due to invalid documents,
written to badkey.log. Included with all arguments.
progress Current state of a document key written to progress.log. Note that a key with a
progress of "inserting" might be a badkey and therefore skipped, rather than an
indexed key. Included with all arguments.
summary Inserted, indexed, and ignored messages written to summary.log. Included with all
arguments except skip.
skip Skipped documents, with explanation, written to skip.log. Included with all
arguments, except summary.
debug Internal Verity Spider processing messages, such as enqueued, written to
debug.log. Included with both debug and trace arguments.
trace Internal Verity Spider processing messages written to debug.log. Included only with
the trace argument.