I need an example of a simple search using verity K2 on windows 2000 and Coldfusion MX.
This is the first cold fusion project for me, so I would be grateful if u could include the obvious parts.
So far I have been able to try configuring the k2server.ini, I was not able to understand the collections part so I did not do anything
Here is the file
## This is an example of a K2 Server ini file used with ColdFusionMX.
##
## This Server section provides keywords that control
## the behavior of the entire server.
[Server]
##
## numThreads: number of Vdk search threads
## started in this server process. If there are too
## many, the system can run out of memory, if two
## few, searches will be blocked waiting for a Vdk
## thread to become free. The number is based of
## hardware resources and system needs.
numThreads=5
## maxFiles: K2 Search Engine determines default values
## per OS. For large or fragmented collections, manually
## set this value. If 'numThread=4' and 'maxFiles=100',
## the K2Server causes the system to support a max of 4
## concurrent searches, with 100 file handles for each
## search thread.
## maxFiles =
## numListeners: maximum number of clients that can
## connect to the K2 Server at any one time. This value
## must be >= to twice the number of threads specified
## in 'numThreads' values specified for all K2Brokers
## in the K2 Search system ('numThreads' in 'k2broker.ini'
## files multiplied by 2)
numListeners=20
## portNo: TCP port number for client connections.
portNo=9901
## vdkHome: directory containing Verity resources (common directory) - need it running as an NT service
## vdkHome=c:/cfusionmx/lib/common
## Changed Deb 11 Dec 2003
vdkhome=c:/coldfusionmx/verity
sortTruncDocs=
accessProfile=
knowledgeBase=
charMap=
language=
locale=
## Each Collection section controls each collection
## and search service configured for the server
## Collection Path Examples:
## Assume there is the collection called "myCollection"
## created by ColdFusionMX.
## The following example ([coll-0] and [coll-1]) in this collections section
## represent a collection created by ColdFusionMX named "CollectionCreatedWithCF".
## Since ColdFusionMX actually creates 2 collections for the user because
## both file system and custom query gateways are required, you may want to
## register both fully qualified collection names with the K2Server
## as shown in this example.
## The "collAlias" entry should be a unique collection alias name that the K2Server
## will use to identify the collection. Use one or more of these collAlias names in your
## CFSearch collection="CollectionCreatedWithCF_file, CollectionCreatedWithCF_custom"
## attribute to search using the K2Server.
## Because the K2Server is a Verity product and only understands "external"
## collections (from a CF perspective), the collPath is the pathspec to
## the actual fully qualified collection name.
## For an 'external' collection, the collPath would
## end with the collection name (i.e. "...\CollectionCreatedWithMKVDK".
## For a ColdFusionMX created collection ("internal",
## the collPath would end with "\file" to search the collection that was
## indexed by type 'file' or 'path', and "\custom" to search the collection
## that was indexed by 'custom' query results.
#[Coll-0]
##collPath=c:\cfusionmx\verity\collections\CollectionCreatedWithCF\file
##collAlias=CollectionCreatedWithCF_file
##topicSet=
##knowledgeBase=
##onLine=2
##[Coll-1]
##collPath=c:\cfusionmx\verity\collections\CollectionCreatedWithCF\custom
##collAlias=CollectionCreatedWithCF_custom
##topicSet=
##knowledgeBase=
##onLine=2
## The next example ([coll-2]) in this collections section
## represent a collection created using MKVDK or VSPIDER (both are Verity command line tools).
## named ("CollectionCreatedWithMKVDK". Although CF did not create this collection,
## CF will still search it using the K2Server.
## If you want to be able to index or manipulate this collection in CF, simply
## register this existing collection with CF using CFCollection action=create or
## from the CF administrator using a unique collection name.
##[Coll-2]
##collPath=c:\cfusionmx\verity\collections\CollectionCreatedWithMKVDK
##collAlias=CollectionCreatedWithMKVDK
##topicSet=
##knowledgeBase=
##onLine=2
This is the first cold fusion project for me, so I would be grateful if u could include the obvious parts.
So far I have been able to try configuring the k2server.ini, I was not able to understand the collections part so I did not do anything
Here is the file
## This is an example of a K2 Server ini file used with ColdFusionMX.
##
## This Server section provides keywords that control
## the behavior of the entire server.
[Server]
##
## numThreads: number of Vdk search threads
## started in this server process. If there are too
## many, the system can run out of memory, if two
## few, searches will be blocked waiting for a Vdk
## thread to become free. The number is based of
## hardware resources and system needs.
numThreads=5
## maxFiles: K2 Search Engine determines default values
## per OS. For large or fragmented collections, manually
## set this value. If 'numThread=4' and 'maxFiles=100',
## the K2Server causes the system to support a max of 4
## concurrent searches, with 100 file handles for each
## search thread.
## maxFiles =
## numListeners: maximum number of clients that can
## connect to the K2 Server at any one time. This value
## must be >= to twice the number of threads specified
## in 'numThreads' values specified for all K2Brokers
## in the K2 Search system ('numThreads' in 'k2broker.ini'
## files multiplied by 2)
numListeners=20
## portNo: TCP port number for client connections.
portNo=9901
## vdkHome: directory containing Verity resources (common directory) - need it running as an NT service
## vdkHome=c:/cfusionmx/lib/common
## Changed Deb 11 Dec 2003
vdkhome=c:/coldfusionmx/verity
sortTruncDocs=
accessProfile=
knowledgeBase=
charMap=
language=
locale=
## Each Collection section controls each collection
## and search service configured for the server
## Collection Path Examples:
## Assume there is the collection called "myCollection"
## created by ColdFusionMX.
## The following example ([coll-0] and [coll-1]) in this collections section
## represent a collection created by ColdFusionMX named "CollectionCreatedWithCF".
## Since ColdFusionMX actually creates 2 collections for the user because
## both file system and custom query gateways are required, you may want to
## register both fully qualified collection names with the K2Server
## as shown in this example.
## The "collAlias" entry should be a unique collection alias name that the K2Server
## will use to identify the collection. Use one or more of these collAlias names in your
## CFSearch collection="CollectionCreatedWithCF_file, CollectionCreatedWithCF_custom"
## attribute to search using the K2Server.
## Because the K2Server is a Verity product and only understands "external"
## collections (from a CF perspective), the collPath is the pathspec to
## the actual fully qualified collection name.
## For an 'external' collection, the collPath would
## end with the collection name (i.e. "...\CollectionCreatedWithMKVDK".
## For a ColdFusionMX created collection ("internal",
## the collPath would end with "\file" to search the collection that was
## indexed by type 'file' or 'path', and "\custom" to search the collection
## that was indexed by 'custom' query results.
#[Coll-0]
##collPath=c:\cfusionmx\verity\collections\CollectionCreatedWithCF\file
##collAlias=CollectionCreatedWithCF_file
##topicSet=
##knowledgeBase=
##onLine=2
##[Coll-1]
##collPath=c:\cfusionmx\verity\collections\CollectionCreatedWithCF\custom
##collAlias=CollectionCreatedWithCF_custom
##topicSet=
##knowledgeBase=
##onLine=2
## The next example ([coll-2]) in this collections section
## represent a collection created using MKVDK or VSPIDER (both are Verity command line tools).
## named ("CollectionCreatedWithMKVDK". Although CF did not create this collection,
## CF will still search it using the K2Server.
## If you want to be able to index or manipulate this collection in CF, simply
## register this existing collection with CF using CFCollection action=create or
## from the CF administrator using a unique collection name.
##[Coll-2]
##collPath=c:\cfusionmx\verity\collections\CollectionCreatedWithMKVDK
##collAlias=CollectionCreatedWithMKVDK
##topicSet=
##knowledgeBase=
##onLine=2