This article applies to BoKS Manager 7.0.0.


In BoKS 7.0 the keystroke log function has been updated to support remote logging over the network to a Replica as a complement to the pre-BoKS 7.0 method of first saving the keystroke log in a local file that is then uploaded to the BoKS Master at a specified interval and/or size.
The access route modifier "ksllocal" is used to select whether local or remote keystroke logging should be used. Thus the absence of the "ksllocal" modifier will cause remote logging to be used while remote logging is the default. When upgrading from an earlier BoKS version, existing access routes with keystroke logging will use remote logging.
For BoKS domains with a high volume of keystroke log data this can be a problem since logging to a local file is more efficient and puts less strain on the system.
To change an access route to enforce local keystroke logging it must be updated to include the "ksllocal" modifier, which can be a difficult task in a large BoKS domain.

Resolution / Workaround

To resolve these issues, apply hotfix HFBM-0173, available for download from the HelpSystems Community Portal.

This hotfix adds the possibility to select whether local or remote keystroke logging should be the default and the possibility to override the default with a modifier on the access route.
The command bksdef -g { local | remote } is used to select whether local or remote logging should be the default.
The access route modifiers "ksllocal" or "kslremote" can be used to override the default setting.

Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: May 25, 2018