User Guide

86 Chapter 7: Introducing Verity Tools
ColdFusion MX OEM restrictions
ColdFusion MX includes an OEM-restricted version of the Verity Server. The version of Verity
Server that is part of ColdFusion MX is restricted in the following areas:
• ColdFusion MX can only interact with one Verity Server at a time.
• Verity Server has the following document search limits (limits are for all collections registered
to Verity Server):
■ 10,000 documents for ColdFusion MX Developer
■ 125,000 documents for ColdFusion MX Professional
■ 250,000 documents for ColdFusion MX Enterprise
■ 750,000 documents for Macromedia Spectra sites
Note: Each row in a database table is considered a document.
If you install a fully licensed version of Verity Server and you configure ColdFusion MX to use
it, ColdFusion MX will not restrict document searches.
• The Verity Spider that is included with ColdFusion MX is licensed for local host indexing
only. Contact Verity Sales for licensing options regarding the use of the Verity Spider for
remote host indexing.
Collection structure and ColdFusion MX
Collections created in ColdFusion MX, either through the ColdFusion MX Administrator or by
using the
cfcollection tag, have different directory structures than external collections. An
external collection is one created by a tool other than ColdFusion MX, such as the native Verity
indexing tool mkvdk. For more information on mkvdk, see Chapter 8, “Managing Collections
with the mkvdk Utility,” on page 89.
The directory structure of a collection that was created with ColdFusion MX consists of two
subdirectories—custom and file—that are not present in external collections.
The type of index used dictates which folder is populated with index data. Based on the
type
attribute of the
cfindex tag, the file folder is used for type="File" and for type="Path"; the
custom folder is used for
type="Custom". For more information on indexing, see Developing
ColdFusion MX Applications.
The
type information is important when you configure the collPath attribute of a collection in
your k2server.ini file. The name of the external collection (for example, col_01) is
C:\myColls\col_01. In contrast, the collection created by ColdFusion MX (cfdocumentation)
actually contains two collections—C:\CFusionMX\Verity\Collections\cfdocumentation\file and
C:\CFusionMX\Verity\Collections\cfdocumentation\custom. Using CFML tags, you only need
to refer to cfdocumentation to access both the file and custom collections. However, since Verity
tools, such as K2 Server, do not understand the ColdFusion MX collection structure, you must
explicitly specify both the file collection and the custom collection in order for K2 Server to
search collections created with ColdFusion MX.
For more information about configuring the
collPath attribute, see “Editing the k2server.ini
file” on page 133.