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
Using the mkvdk utility 143
The log file contains the following fields:
• Date
• Time
• Level
• Code
• Component
• Description
You can use the log file to view details about what happens during the collection creation process.
Use the mkvdk
-loglevel command and specify the numeric identifier for the message level you
want, as summarized in the following table:
To calculate the numeric parameter, add the numbers for the message types you want to include.
The default for both
-outlevel and -loglevel is 15, which selects fatal, error, warning, and
status messages (1+2+4+8).
Getting started with the Verity mkvdk utility
The following is the basic mkvdk syntax:
mkvdk -collection path [option] [...] [filespec] [...]
Where:
• Square brackets ( [ ] ) indicate optional items.
• An ellipsis (...) indicates repetition of the previous item. Thus, [filespec] [...] indicates an
optional series of filespec items.
• filespec represents a document filename or a list of document filenames. If filespec is a list of
files, it should consist of an at sign (@) followed by the filename containing the list (for
example, @filelist).
• The -collection path argument creates or opens a collection. This argument is required.
Numerous optional syntax options are listed below. All syntax options must precede the first
filespec parameter.
Type Number
Fatal 1
Error 2
Warning 4
Status 8
Info 16
Verbose 32
Debug 64