Document Actions

Upgrade Isite for UNIX/Linux


Obtaining and Install the Software

  1. Download the appropriate Isite software from this page.
    Note: For this example we will be using the Linux 2.6.8 version of Isite. We will also be using GNU tar to extract it. We will also assume that your database name will be will be in bold and the string you are searching for will be in bold italics. The $ at the beginning of each command is the shell prompt.
    Be sure to set aside your old sapi.ini and zserver.ini files when you install the Isite code.
  2. Untar the file (for this example we will be using /home/wwwdev/demo/Isite2):
    3. $ tar xzvf clearinghouse2-v2.3_Linux_2.6.8-24.10-i386-2005010602-static.tar.gz
    Note: All commands should be entered all on one line unless specified otherwise.
  3. This should output something like the following:
    4. Isite2/bin/GetScript
    Isite2/bin/Key1
    Isite2/bin/SearchScript
    Isite2/bin/Iindex2
    Isite2/bin/Isearch2
    Isite2/bin/Iutil2
    Isite2/bin/Iget2
    ...
  4. Stop the zserver process manually.
  5. Open and edit the file zserver.ini. Confirm the following parameters are set similar to below:
    ServerType=STANDALONE
    Port=6668
    SAPI=sapi.ini
    AccessLog=zserver_access.log
    DBList=test
  6. Restore your .ini files into the same directory as the new zserver executable and check the sapi.ini file for the following style to be sure that your Fieldmaps points to the full path names of the *_fgdc.map files on your computer.
    [test]
    Type=ISEARCH
    Location=/home/wwwdev/demo/Isite2/db
    Fieldmaps=/home/wwwdev/demo/Isite2/bin/bib1_fgdc.map,\
    /home/wwwdev/demo/Isite2/bin/gils_fgdc.map,\
    /home/wwwdev/demo/Isite2/bin/geo_fgdc.map

    In this example the database is called "test" (this must match the DBList parameter in zserver.ini). The database is stored in the /home/wwwdev/demo/Isite2/db directory. The type is ISEARCH.

    The pathnames to Fieldmaps must be set to the location where you just installed Isite on your system. Be sure that you have no spaces in your fieldmaps declaration line. Verify that these files are in the right spots with the following commands:

    • $ file /home/wwwdev/demo/Isite2/db
    • $ file /home/wwwdev/demo/Isite2/bin/bib1_fgdc.map
    • $ file /home/wwwdev/demo/Isite2/bin/gils_fgdc.map
    • $ file /home/wwwdev/demo/Isite2/bin/geo_fgdc.map

    Each command should return either "directory" or "ASCII text". If it returns "(No such file or directory)" check your path names.

  7. You now need to index your metadata. The Iindex command should be run with the following arguments from the Isite2/bin directory, following the path examples above:
    $ /home/wwwdev/demo/Isite2/bin/Iindex2 -d /home/wwwdev/demo/Isite2/db/test -t fgdc -o fieldtype=/home/wwwdev/demo/Isite2/bin/fgdc.fields
    /home/wwwdev/demo/Isite2/data/*.xml
    Note: For this example we will assume your metadata is located in /home/wwwdev/demo/Isite2/data.

    The database test will be written to the /home/wwwdev/demo/Isite2/db directory, using FGDC metadata format, using FGDC search fields, and using as input all files in the /home/wwwdev/demo/Isite2/data directory that end in *.xml . You will need to adapt these pathnames to match your system.

    Click here for advanced indexing options

    If all is successful, you should receive a message similar to the following: 

    Iindex v2.2
Building document list ...
Creating new cache [/home/wwwdev/demo/Isite2/db/test.db]
Building database /home/wwwdev/demo/Isite2/db/test:

	Parsing files ...
	Parsing /home/wwwdev/demo/Isite2/data/cgia-wswtemp.xml, key=10
	Parsing /home/wwwdev/demo/Isite2/data/dds10.xml, key=240591
	Parsing /home/wwwdev/demo/Isite2/data/dust.xml, key=359671
	Parsing /home/wwwdev/demo/Isite2/data/glaciers.xml, key=4113759
	Parsing /home/wwwdev/demo/Isite2/data/goes_9_conus.xml, key=5134543

	Indexing 21624 words ...
Writing compressed blocks to sequence table 1
...................................
Wrote 36 blocks of compressed strings.

Done with sequence table 1
Dumping sparse table 1...
Done with sparse table 1
Database files saved to disk.

    It is recommended that you save this command line as a script that can be run over and over again and edited if changes are warranted.

  8. Start your Z39.50 Clearinghouse Server process by changing directory to Isite2/bin and invoking the zserver command. You may wish to put this in the background:

    • $ ./zserver &

    You should also include it in startup scripts typically stored in the /etc/rc.d directory so it will get restarted after system reboots.

    9. Testing the zserver Installation

  9. Once you have the zserver running (on port 6668 and with a database named "test"), you can test it by confirming that it up by executing the following command:
    10. $ ./zping localhost 6668
  10. The following title search for the string "water" should only return a single hit:
    11. $ ./zclient localhost 6668 "test" "water[1,4]"
  11. Confirm that a full text search for the string water returns 4 hits:
    12. $ ./zclient localhost 6668 "test" "water[1,1016]"
  12. Finally a global spatial search should return 5 hits (all the records):
    13. $ ./zclient localhost 6668 "test" "90 -180 -90 180[1,2060]"
  13. See the online tutorials for creating a Clearinghouse Node for further details of testing and registration. Until you register your server with the FGDC, it will not be included in the search forms. To register, fill in the server-level metadata at http://registry.fgdc.gov/.

If you need assistance, contact us at support@clearinghouse3.fgdc.gov.