Thank you for downloading the LexAccess Tool Java, UTF-8, 2009. This package includes one compressed file: LexAccess2009.tgz.
Download the LexAccess2009.tgz file from LexAccess Tool web site
Uncompress and unarchive this file into the location where you intend to have it installed. On a Unix machine, this would look like:
shell> gtar -xzvf LexAccess2009.tgz
If you are on a windows platform, pkzip and winzip may be used to uncompress and unarchive this file. Please make sure the file you download has the right extension (tgz) before you unzip it. Change the extension to tgz if it is not. Winzip looks into the file to check if there is tar file within it, and it asks if it should create a temparary file with the tar file in it. The proper response is to allow this to happen. Once the temparary file has been created, winzip reads it and displays the archive as it would any other zip'ed file. Unzip the resulting contents to the location you want to install to. Make sure that you preserve the directory structures when unarchiving.
Once the files are in place, change directories to the top level. This should be LexAccess2009. If you are on a windows platform, this will involve opening up a DOS command window, and changing directories to where you have put these files. We will henceforth refer to this top level directory as the LA_DIR directory.
From the LA_DIR, invoke the appropriate installation command. These are installation scripts appropriate to the platforms we know about:
The scripts shown above will alter the configuration file settings to set the install location.
Please notes that the default DB come with LexAccess is HSqlDb and works pretty well. If you wish to use your own database server (such as MySql), please make sure it provides compatible JDBC and refer to OtherDB (MySql) pages for details.
The script will create shell files in the LA_DIR bin directory for the LexAccess tool, with the proper environment set up.
Once done, the script will attempt to verify that the installation was successful.
If the installation was successful, there will be a congratulation message that finishes off this process.
If the installation is not successful, there will be a message indicating so. Please refer to the LA_DIR logs directory for a complete transcript of the process. It is likely that there were error messages indicating the source of the failure.
After a successful installation
The LexAccess tool is now ready to be used. It can be found in the LA_DIR/bin directory. On the Unix platforms, it include the following shell script:
On the Windows platform, they include the following batch file:
Each may be used from any location on the machine. If you put the LA_DIR bin path in your $PATH enviroment variable they do not have to be referenced with the whole path.
shell> lexAccess -f:id saw saw|noun|base|E0054443|saw|saw|basic saw|noun|singular|E0054443|saw|saw|basic saws|noun|plural|E0054443|saw|saw|reg saw|verb|base|E0054444|saw|saw|basic saw|verb|pres1p23p|E0054444|saw|saw|basic saw|verb|infinitive|E0054444|saw|saw|basic saws|verb|pres3s|E0054444|saw|saw|irreg sawed|verb|past|E0054444|saw|saw|irreg sawn|verb|pastPart|E0054444|saw|saw|irreg sawing|verb|presPart|E0054444|saw|saw|irreg saws|verb|pres3s|E0054444|saw|saw|reg sawed|verb|past|E0054444|saw|saw|reg sawed|verb|pastPart|E0054444|saw|saw|reg sawing|verb|presPart|E0054444|saw|saw|reg see|verb|base|E0055007|see|see|basic see|verb|pres1p23p|E0055007|see|see|basic see|verb|infinitive|E0055007|see|see|basic sees|verb|pres3s|E0055007|see|see|irreg saw|verb|past|E0055007|see|see|irreg seen|verb|pastPart|E0055007|see|see|irreg seeing|verb|presPart|E0055007|see|see|irreg
An Example Installation
Altering your environment to use the LexAccess tool, once they have been installed
You may invoke these tools from a command line. These tools are found in the __LA_DIR__/bin directory. You can add this __LA_DIR__/bin path to your $PATH environment variable. This would enable you to find and run these tools from any location.
In UNIX, this would be done by adding this path to your ~/.cshrc or ~/.profile startup script.
In Windows, this would be done by appending this path to the PATH variable from the "control panel\System\Advanced\Environment variable\Edit" menus.