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
142 Chapter 10: Using Verity Utilities
Location of Verity utilities
The Verity command-line utilities are located in the following directories:
Server and multiserver configuration The utility files are located in cf_root/verity/k2/
platform/bin (server configuration) or jrun_root/verity/k2/platform/bin (multiserver
configuration), where platform is _nti40 for Windows, _solaris for Solaris, or _ilnx21 for Linux.
J2EE configuration The utility files are located in verity_root/k2/platform/bin, where platform
is _nti40 for Windows, _solaris for Solaris, or _ilnx21 for Linux.
Using the mkvdk utility
The mkvdk utility is an indexing application, provided with other Verity utilities, that you can
use to create and maintain collections. It is a command-line utility that you can use within other
applications or shell scripts to provide more sophisticated scheduling and other capabilities.
The mkvdk executable file, which starts the mkvdk utility, is located in the platform/bin directory.
For more information on the specific location of this directory, see “Location of Verity utilities”
on page 142.
Note: To display a list of mkvdk command-line options, enter the following command:
mkvdk -help
The mkvdk utility syntax
The following is the basic syntax of the mkvdk command:
mkvdk -collection path [option] [dockey]
Multiple options and dockeys can be included, as needed. If dockey is a list of files, it should
consist of an at sign (@) followed by the filename that contains a simple list of files (for example,
@filelist). For more information about the options for the mkvdk utility, see “Getting started with
the Verity mkvdk utility” on page 143.
The following operations occur when you use the mkvdk utility to create a new collection:
1.
New collection directories are created and the specified style files are copied to the style
subdirectory.
2.
The style file settings are read and the required information is passed to the Verity search engine.
3.
The gateway is used to open the document files, which are parsed according to the settings in
various style files.
4.
A new partition is created, which includes an index and an attribute table.
5.
Assist data is generated, which might include a spanning word list.
When problems occur during an operation, the mkvdk utility writes error messages to the system
log file (sysinfo.log). You can direct error and other messages to the console by using the mkvdk
command with the
-outlevel option. You can direct messages to a file of your choice by using
the
-loglevel and -logfile options.