Installing Indagine on Windows NT

Note for advanced users: You may be able to skip some of these steps if the necessary packages are already installed. There are also other possibilities for location of the files, types of install, etc. These instructions are intended to be as clear as possible for a novice user, therefore they do not consider any alternative options.

Prerequisites

1. Windows NT4.0 with Service Pack 3 or later
2. An installed 8.1.5 database, complete with interMedia Text, tested and working. It is recommended that this be on the same machine as the rest of this system, but a remote database is possible so long as client programs (SQL*Plus and SQL*Loader) are available on the local machine.

Installation Steps

1. Get ActivePerl for Win32

   From: http://www.perl.com/pub/language/info/software.html#win32

   Run the downloaded executable to install.
   Warning: We have seen problems with the "gethostbyname" call in early versions of Perl 5. Even if you already have Perl installed on your machine we recommend you download and install the latest version.

2. Get Sun's Java Development Kit 1.1.8

   From: http://www.javasoft.com/products/jdk/1.1/download-jdk-windows.html

   You will download a file called jdk1_1_8-win.exe. Simply run this file to install. The rest of this note will assume you accepted the default location "C:\jdk1.1.8".

3. Get Sun's JavaServer Web Development Kit 1.0.1

   From: http://www.javasoft.com/products/jsp/download.html

   The download is currently the second main item on this page. The Jakarta/Tomcat project is currently poorly documented and is not recommended, although advanced users may wish to use it.

   This will download a zip file which must be opened with WinZip or similar. Extract all files to a directory of your choice - we will assume it is "C:\jswdk".

4. Get the Apache WebServer 1.3.11

   From: http://www.apache.org/dist

   Get Apache 1.3.9 For Win32 - file apache_1_3_9_win32.exe. If this file is not present download the newest apache_XX_win32.exe that you can see.

   Simply run this file to install the Apache Web Server. The rest of this note will assume you accepted the default location of "C:\Program Files\Apache Group\Apache" (the default).

   If you have another WebServer (such as Oracle Application Server) installed already, you may need to change the port through which Apache runs (defaults to port 80). Do this by editing the file "C:\Program Files\Apache Group\Apache\conf\httpd.conf" and finding the section reading

       #
       # Port: The port to which the standalone server listens.
       #
       Port 80
   

   Change this to a port of your choice (eg. 888).

5. Testing Apache

   Start Apache from the Start Menu with "Start / Programs / Apache Web Server / Start Apache"

   This will start Apache with its output going to a DOS Window. You have an option to install Apache as a service instead, although I was unable to get this to work on my own machine.

   From a web browser, we can now test Apache using the URL

        http://<servername:888
   
   

   ... replacing the 888 with the port you have chosen, or 80 for the default install. You should see a "congratulations" page.

6. Testing JavaServer and Servlets

   The JavaServer defaults to port 8080. If this is already in use (eg. by OAS), you must change it in the file "C:\Jswdk\jswdk-1.0.1\webserver.xml", in the section:

   <!ATTLIST Service
       id ID #REQUIRED
       port NMTOKEN "8080"
       ...
   
   

   Before we can run our own servlet, we must make another change to this file. At the bottom, you will see a section

   <WebServer id="webServer">
       <Service id="service0">
           <WebApplication id="examples" mapping="/technology/examples" docBase="examples"/>
       </Service>
   </WebServer>
   

   We must add another "WebApplication" line in there, so it now reads:

   <WebServer id="webServer">
       <Service id="service0">
   
           <WebApplication id="examples" mapping="/technology/examples" docBase="examples"/>
           <WebApplication id="imt" mapping="/technology/imt" docBase="imt"/>
       </Service>
   </WebServer>
   

   The JavaServer is started from a DOS window. Go to the main JavaServer directory, and run the startserver batch file:

       C:\> cd \jswdk\jswdk-1.0.1
       C:\Jswdk\jswdk-1.0.1> startserver
   

   This will start the JavaServer in another DOS window (you can stop it either by running stopserver from the original window, or by entering a CTRL-C at the output window).

   Test the JavaServer with a URL like

        http://<servername>:8080
   

   You should see the default JSWDK home page. You can navigate to "Servlet Examples" and "Hello World : Execute".

We are now ready to install Indagine

1. Locating the files

   We must first expand the zip file, then move the various directories to their correct locations.

   When expanded, the zip file will produce the following directory structure:

      cgi-bin
      docs
      htdocs
        images
      imt
        images
        web-inf
          servlets
            imtext
      spider_source
   
   

   • Move the contents of the htdocs directory into the Apache htdocs directory - by default C:\Program Files\Apache Group\Apache\htdocs".

   • Move the imtdirectory structure into the jswdk main directory, such as "C:\Jswdk\jswdk-1.0.1".

   • Move the spider_source directory. This file will assume you have moved it to the root directory, so it becomes "C:\spider_source".

2. Editing Indagine's Config Files

   There are two files that must be modified to set directory names, database connection values, and so on.

   Edit the file "C:\Program Files\Apache Group\Apache\cgi-bin\isearch.conf".
   Most of the entries in this file will need to be changed to values suitable for your file system and database. Full explanations of each value are given in the comments above each item.

   Then edit the file "C:\Jswdk\jswdk-1.0.1\imt\WEB-INF\Servlets.properties". This file contains the database connection details which are passed to the search servlet as initialization parameters. You should change only the ImtButtonServlet1.initparams line. You need to know the hostname for the machine holding the database, the port on which the SQL*Net listener runs (normally 1521), and the SID for the database.

3. Setting Environment Variables

   You must change two environment variables (from "Control Panel/System/Environment"):

   PATH must include the JDK bin directory, eg. "C:\jdk1.1.8\bin"
   CLASSPATH must include 
     The JavaServer "servlet.jar" file (for Servlet classes)
     The Oracle "classes102.zip" file (for JDBC classes)
     The current directory "."(for compiling Java files)
     The parent of the current directory ".." (for compiling Java files)
   
   

   Typical settings might be:

       PATH = "C:\oracle\ora81\bin;C:\jdk1.1.8\bin"
       CLASSPATH = "C:\Jswdk\jswdk-1.0.1\lib\servlet.jar;C:\oracle\ora81\jdbc\lib\classes102.zip;.;.."
   

4. Compiling Java

   Class files are provided for the Java code. However, if you wish to make any changes, you can recompile the code as follows.

       C:> cd \jswdk\jswdk-1.0.1\imt\WEB-INF\servlets\Imtext
       C:\jswdk\jswdk-1.0.1\imt\WEB-INF\servlets\Imtext> javac ImtButtonServlet1.java
       C:\jswdk\jswdk-1.0.1\imt\WEB-INF\servlets\Imtext> javac Imtext/*.java
   

   Running an indexing job

   You should now be able to start an indexing job by accessing the URL

        http://<servername>/isearchadmin.html
   

   See Indagine manual for further details. This may be found in the "docs" directory of the installation.