Known Problems, Features, and Limitations


The following items are known problems, features, or limitations in this release:

VdkThread_SelfService and Multithreading Models

 

Reading a Document Set with an Invalid First Key

 

VSpider Compatibility Issues

 

Profiler Compatibility Issues

 

Style Set Issues

 


VdkThread_SelfService and Multithreading Models

The use of the VdkThread_SelfService and VdkThread_MTHot multithreading models are not recommended for use.

Workaround: Use your operating system’s facilities for creating and managing threads. Refer to the “Session Suite” chapter of the Verity Developer’s Kit Programming Reference for more information. (68747, 89639)


Reading a Document Set with an Invalid First Key

The VdkCheckDocAccess function returns a “no access” result for all documents if the first document in the return vector has an invalid internal (VdkDocId ) or external (VdkDocKey ) key. This error can also occur from the VDKDocSetRead function, which calls VdkCheckDocAccess , and in utilities, such as rcvdk , which calls VDKDocSetRead .

Workaround: You must ensure that your application does not call the VdkCheckDocAccess function, directly or indirectly, with a list of keys in which the first key is invalid. (71595)


VSpider Compatibility Issues

The following items relate to the use of VSpider and VDK:

A new command option, -useget , is introduced for vspider . When -useget is specified, vspider web crawler will always use HTTP GET method to retrieve pages, instead of using HEAD and then GET. The default is off. (94816)

 

The -keyencode option allows a user to turn on the key encode in DOC_FN field, please contact Verity tech support if you want to use encoded DOC_FN field.

 


Profiler Compatibility Issues

The following items relate to the use of Profiler and VDK:

Environment variables VDK_NO_PRF_CASE , VDK_NO_PRF_STEM and VDK_NO_PRF_SNDX can be used to disable CASE/STEM/SNDX in the profiler. The environment variables must be set before the prf is opened and before the queries are loaded. With the environment variables set, profiler will turn off case, stem and soundex variations when matching queries. (93822,94150,938890)

 


Style Set Issues

The following items address settings in the style.prm style file:

To support searching for strings that contain periods, the fix is to ignore sentence tagging when counting word positions (for more details check comments in style.prm). Requires collection re-index. It is a collection level configuration parameter (NOEOS ) and it is locale-independent. Sentence tokens are still available to VDK summarization and feature extraction. (94144)

 

The following related comment and definition are from style.prm :

 

This example enables Word Count word position format but ignores sentence tagging. The word position is bumped upon sentence tokens. However, the sentence breaks may be incorrect, causing phrase operation to fail to yield a hit. This option ignores sentence tagging during indexing time for word position counting (i.e., word positions will not be bumped upon sentence breaks).

#$define IDX-CONFIG "WCT NOEOS"

To serialize VDK transactions use /serialize = 1 in style.plc . (93686, 92901, 93136)

 

The following example shows the use of the /serialize = 1 option in style.plc :

$control: 1
policy:
{
mode: default
/inherit = Generic     # inherits from Generic policy mode
/serialize = 1
}
$$

GDK API

VdkVgwKey names ending with file extensions

 

When a VdkVgwKey name ends with a valid file extension, such as .doc , .xls , .pdf , and so on, VDK attempts to load a filter for the specified file type. This can cause problems if the content of the virtual document does not match the type indicated by the key.

(83054)


Required and Optional Credentials for Gateways

The credential lists for each Verity gateway are obtained from the security interface of each gateway API when invoked by VDK. K2 Server invokes the VDK security API, obtains the credentials and then populates the K2 repository structures and classes. See the Verity K2 Gateway Developer's Kit API Reference Guide for concepts and details.

Some of the credentials, specifically the REPOSITORY_KEY, are VDK structures whose values are set internally in K2 Server. The REPOSITORY_KEY VDK structure is used for access to a particular Verity gateway, and the value is obtained by function calls to the Verity gateway itself and tracked internally. The REPOSITORY_KEY credential is not a client credential. The K2 Ticket Server sets the PREAUTHKEY credential. See the Verity Security API Guide for further information on usage of the PREAUTHKEY. The REPOSITORY_KEY is in either the required or optional column depending upon the design of the particular Verity gateway.

The following list indicates required and optional credentials for each Verity gateway:

 


Gateway

Description

Required Credentials

Optional Credentials

vgwfsys

File System gateway

USERNAME_KEY
PASSWD_KEY

REPOSITORY_KEY*
DOMAIN_KEY
PREAUTH_KEY*

vgwhttp

HTTP gateway

USERNAME_KEY
PASSWD_KEY
REPOSITORY_KEY*

DOMAIN_KEY

vgwnotes

Notes gateway

USERNAME_KEY
PASSWD_KEY
REPOSITORY_KEY*

DN_KEY
PREAUTH_KEY*

vgwmsxch

Microsoft Exchange gateway

REPOSITORY_KEY*
USERNAME_KEY
PASSWD_KEY
MBNMS_KEY

DOMAIN_KEY**

vgwodbc

ODBC gateway

USERNAME_KEY
PASSWD_KEY
REPOSITORY_KEY*

none

vgwdctm

Documentum gateway

USERNAME_KEY
PASSWD_KEY

REPOSITORY_KEY*
DOMAIN_KEY
PREAUTH_KEY*

 

FileNet gateway
NOTE: This gateway is not yet officially supported

USERNAME_KEY
PASSWD_KEY

DOMAIN_KEY
EXTENSION_KEY


* Set internally

** The DOMAIN_KEY has always been required for Exchange gateway. However in K2 V4.5.1 and earlier it was reported by the gateway as optional. In K2 V5.0 it is reported in the Required credential list.

(77341)