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
About Verity Spider syntax 111
Efficient DNS lookups
Verity Spider minimizes DNS lookups, which means great improvements to spidering
throughput. If spidering is limited by domain or host, then no DNS lookups are made on hosts
that fall outside of that range. In earlier versions, DNS lookups were made on all candidate URLs.
Proxy handling efficiency
To allow for greater flexibility when dealing with indexing jobs that involve proxy servers and
firewalls, use the following options:
-noproxy To reduce proxy checking for certain hosts
-proxyauth To authenticate on proxy servers
About Verity Spider syntax
Before you create an indexing task for a new collection, make copies of the relevant default style
files to ensure that you have a set of template style files in a known, stable state.
Running multiple simultaneous Verity Spider jobs can cause performance problems for searches.
This does not mean that you should never run indexing jobs when users might be searching,
because your collections are available for searching even while indexing jobs are running. To
optimize performance, try staggering your indexing jobs to avoid overloading your server.
The Verity Spider command
The vspider executable file, which starts the Verity Spider utility, is located in the platform/bin
directory, as follows:
Server and multiserver configuration The vspider.exe (Window) or vspider (UNIX) file is
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 vspider.exe (Window) or vspider (UNIX) file is located in
verity_root/k2/platform/bin where platform is _nti40 for Windows, _solaris for Solaris, or _ilnx21
for Linux.
At its most basic level, a Verity Spider command consists of the following:
vspider -initialize -collection coll [options]
Where -initialize is -start or -refresh (when starting points have changed), and
-collection is required to provide a target for the Verity Spider, and [options] can be a near-
limitless combination of the options described later in this chapter.
For example:
c:\cfusionmx7\verity\k2\_nti40\bin\vspider -common
c:\cfusionmx7\verity\k2\common
-collection c:\new -start http://localhost -indinclude *