propswith

...

...

Page info
title title

...

• If you use a space in the name of the path to install LexEVS, that is LEXEVS_HOME, you might get errors from the underlying database during runtime. It it highly recommended that you do not use a space in the path.
• Upgrading LexEVS may require reloading content. Be sure to read the release notes for each LexEVS release before installing the latest version. Preserve configuration files and indexes unless instructed to reload or do otherwise in the release notes. These files include lbconfig.props, registry.xml and the entire lbIndex directory in the resources directory. Note that the names of those last two files can be altered by variables in the lbconfig.props file.
• LexEVS loads of content are generally handled in a robust manner. Failed loads clean up after themselves relatively well when database management systems are properly configured to allow database drop functions by LexEVS. However, exiting the application in the middle of a load may cause unpredictable results. Errors will be detected for some loads and they will be listed as PENDING in any API call to the coding scheme metadata. They can be removed if this is the case, and the user can restart the load.
  • Other steps may need to be taken if this doesn't work, including dropping databases as the DBA, deleting the index file for the offending terminology, and editing the registry.xml and metadata.xml files by hand.
  • A quick, dirty solution is to drop all databases and delete all configuration files except lbconfig.props.
• Know when to scale database management systems for management of large terminologies. Administrators who load very large terminologies, such as the NCI Metathesaurus in single table mode, will experience very long delays while the deletion process completes.
• LexEVS is no longer distributed with a Java MySQL driver due to licensing concerns. If LexEVS reports an error concerning establishing a connection to the MySQL server yet the MySQL command line interface is able to connect, an adjustment in the version of Connector/J may be required.
  • The latest version of Connector/J is available from MySQL.org. The new jar should be placed in the {LEXEVS_HOME}/runtime/sqlDrivers/ directory. If you are changing drivers remove the existing driver jar file to ensure that the class loader does not incorrectly load the older driver file.
• If the user experiences slow performance with MySQL when loading or accessing terminologies then a review of the suggested configuration parameters for the database management system is recommended. Pay particular attention to the MySQL values.

...