NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. #Service_Management consists of and API and example programs to load, index, publish, and manage both vocabulary content and service metadata for the vocabulary server. Examples are found in the admin directory of the LexEVS root installation directory.
  2. LexEVS Application Programming Interface (API) is comprised of methods to support Lexical Operations, Graph Operations, Value Set Operations, Authoring Operations, and History Operations. Examples are found in the examples directory of the LexEVS root installation directory.
  3. #Documentation consists of detailed JavaDocs and both a Programmer's Guide and an Administration Guide.
  4. #Automated _ Test _ Suite is provided to validate the LexEVS installation. It includes relatively small sample vocabularies that can be loaded by the user. These can be found in the test directory and its sub-directory, testData.
  5. #Configuration and Resource Files provide custom configuration of the LexEVS runtime to users.

...

  • Runtime: contains the combined LexEVS classes and third party dependencies required for LexEVS to function in a single archive jar file.
  • Runtime components: a combined archive of LexEVS classes but with separate 3rd party jars outside of archive.
  • Unistaller: a packaged uninstaller, that just deletes the root directory. Database cleanup is left up to the user.

Deployment

...

Alternatives

Earlier versions of the LexEVS local Runtime package offered flexible database deployment alternatives depending on the underlying data base management systems(DBMS's). Single database configurations allow the user to manage databases more effectively so LexEVS no longer offers the option of loading each terminology as a separate database.

...