Admin Tools

Overview

Documents the available admin tools and how to run them.

Admin Scripts

These admin scripts are in the admin/loader/src/main/scripts folder and make certain tasks easier.

• load.bat, load.csh 
  
  • Used to create database, clear indexes, and load terminology data.
• loadDelta.bat, loadDelta.csh
  
  • Used to run the delta loader.
• truncate_all.sql
  • MySQL script for removing all tables.
  • The alternative is to drop and recreate the schema

Admin Tools

The following admin tools are used to administer a term server.

• Create/update DB
• Lucene Reindex
• Terminology Loader and Remover
• QA Tools
• Release Processing Tools
• Maintenance Tools

The "server" Parameter

Most admin tools take an optional "server" parameter that can be set to true/false and has a default value of false.

This is a mechanism to support running admin tools through REST calls, rather than in a standalone fashion.  The reason for this is that tomcat deployments involve running the server as a different user than the typical admin user on the machine.  As many admin tools can affect indexes, this creates weird problems with respect to managing ownership and permissions on Lucene index files.  

By supporting a mode where all admin tools can be run through a server, there is no need to have the the user account on a production machine for running admin tools match the user account of the server.  In fact, the "load" scripts supplied with the distribution could be easily modified to use "server=true" and the entire load could be managed through a running server.  This, of course, would require the server to be deployed and running first.

References/Links

• n/a