Below you will find an expanded overview of the options in this file. Options in BOLD must be modified so that LexEVS can properly use your database. They are also noted as required. There are many other options that you can change for performance reasons or alternative deployment scenarios, but you probably don't need to change them in a standard LexEVS installation. Some options can not be changed after you load terminologies into LexEVS. Now would be a good time to read about what is available to you.
A single back slash "\" is not valid within the
lbconfig.props file for file or directory paths (except within JDBC connection strings). When constructing file or directory paths you must use either a forward slash "/" or two backward slashes.
The current persistence scheme used to persist to an underlying store. This should remain unchanged unless there are custom persistence layers implemented. Default is set to 2.0
Required: The address of your database server. This will include the host name or IP address followed by the name of the database that you created to store LexEVS data. For example:
The prefix to use on created tables.
The default is
Primary key strategy indicates which strategy will be used for the primary key of the database tables.
Allowable values include:
Optional variable for passing extra database parameters. These will be appended to the end of the database connection string.
Required: The Java class name that represents the driver that you wish to use with your database.
Required: The database username. This account must have permission to add and remove tables, indexes, etc inside of this database.
Required: The password for the database username.
Password encryption can be enabled by setting
This is not actually a variable that you would set within this file. It is documented here for clarity of other variables that depend on this variable.
This variable is the path that will be used to resolve any other relative (or unqualified) paths in the lbconfig.props file.
The path of the folder that contains your SQL drivers and LexEVS extensions (if you have any).
This value is only here for backwards compatibility. It is not needed in versions beyond 6.x.
The folder where all LexEVS generated indexes will be stored. This folder can potentially be large
LexEVS maintains a pool of connections to each database that it connects to. This sets the limit on the number
LexEVS maintains an internal cache of some information that it needs to query from the database to resolve
The length of time to allow an unused (and unclosed) iterator to stay valid before it is closed (and its resources freed) by the system.
This controls the maximum number of results that a user can resolve at one time for the CodedNodeSets and CodedNodeGraphs.
The number of boolean
The path where LexEVS log files will be written.
Setting API call logging to
Setting SQL logging to
Setting debug to
Indicates when a new log file should be started. This can be set to
If LOG_CHANGE is set to