FindinSite-JS: Search engine for a Java server website   .
Powered by FindinSite-JS
. Home | Installation | Indexing | Configuration | Advanced | Purchasing .
. .
  Servlet engines | Servlet engine installation | findinsite-js Installation / Macromedia JRun


findinsite-js installation guide for Macromedia JRun

This page is for information purposes only. It is not a recommendation to use this Java servlet engine or application server. Please consult the supplier's documentation for full installation information and details of how to deploy and configure servlets such as findinsite-js.

Since this page was written, this server software is now owned by Adobe and is available here.


findinsite-js is a Java servlet.  It is a program that must be run by a Java servlet engine on a web server, with its output viewed in a browser.
  • Java application servers usually have built-in support for Java servlets.
  • Alternatively, a Java servlet engine can be installed and connected up to an existing server.
Please refer to these pages for more information: Please consult our Getting Started Guide for an overview of how to obtain findinsite-js, set up your server, install and configure findinsite-js.  Get the findinsite-js software from the Download page.
Page contents
JRun introduction
Setting up...
Install findinsite-js
findinsite-js URLs
Work directory
Run test searches
Index your own site
Word highlighting
Init parameters
Updating findinsite-js
Uninstalling findinsite-js

Macromedia JRun

Macromedia (formerly Allaire) JRun is a Java servlet engine, available for several platforms from It supports the servlet specification JSDK 2.3.

JRun can be connected to several types of main server. JRun includes a servlet web server so it does not need to be connected to a web server when testing.

JRun has a "JRun Management Console" browser interface which makes it fairly easy to deploy findinsite-js.

JRun installation

By default, Macromedia JRun installs two servlet web servers, a JRun Admin Server and a JRun Default Server.  Each of these servers needs a separate port.

The Admin server should be only used by the "JRun Management Console" and should not be connected to your main web server.

Connect the Default server to your main web server using the Connector Wizard in the "JRun Management Console".  This automates most of the connection tasks; however for at least one server type, the Microsoft IIS server, we found that we needed to consult the documentation for the final connection steps.

You should deploy the findinsite-js Web Application in the Default server.

findinsite-js Deployment, Configuration and Usage Instructions

These instructions are for JRun 3, connected to an Apache Server.

Note that JRun 3.1 must be connected to the public internet when you deploy findinsite-js so that the Sun web application definition web site can be accessed. Thereafter, this public internet web site also needs to be accessible when JRun restarts with findinsite-js deployed.

Installing findinsite-js

Installing the findinsite-js web application findinsitejs.war is usually called deployment.
  1. Start the JRun Admin and Default servers.

  2. Start the "JRun Management Console" and login.

  3. In the navigation panel, expand the relevant server, eg "JRun Default Server" and click on "Web Applications"

  4. Click on "Deploy an Application" in the main screen.

  5. Fill in the form as follows:

    Servlet War File or Directory:Browse to select findinsitejs.war
    JRun Server Name:Select one, eg JRun Default Server
    Application Name:Eg FindinSite
    Application Host:
    Application URL:Eg /fisjs
    Application Deploy Directory:
    Click Deploy

  6. In the navigation panel, click on the relevant server, eg "JRun Default Server".
    Click on "Restart Server".

findinsite-js URLs

The following URLs should now be available (assuming that the Apache server is running on the default web server port of 80, and the JRun Application Root is /fisjs):
findinsite-js welcome page http://localhost/fisjs/
findinsite-js documentation http://localhost/fisjs/doc/
findinsite-js search page http://localhost/fisjs/search
findinsite-js configuration screen http://localhost/fisjs/search?config=now

Check the work directory location

Before you start testing findinsite-js, it is important to check that the findinsite-js work directory is in a suitable location.
findinsite-js uses a work directory to store all its configuration information and search database files. It is important that this directory is secure from unwanted direct access, while still being available to findinsite-js. It is also a good idea to make sure that this directory is not wiped accidentally, eg if you update the findinsite-js runtime to a newer version. Finally, it is also a good idea to backup the contents of the findinsite-js work directory regularly.
findinsite-js makes a directory called FindData when it starts. If this is not suitable then you need to change the work init parameter.

Changing init parameters

  1. Start the "JRun Management Console" and login.
  2. In the navigation panel, expand the relevant server, eg "JRun Default Server" and click on "Web Applications"
  3. Select "FindinSite" then "Application Variables"
  4. Add a suitably named init parameter, eg work, and give the required value.
  5. Click on "Update"
  6. Restart the Default Server

Test Search

Check that you can search the findinsite-js documentation correctly, as follows:
  1. Browse to the findinsite-js localised search page, eg http://localhost/fisjs/search.

  2. Enter some search text, eg engine and click on "Search".

  3. The first 10 hits are displayed. Click on a hit and check that the result page is displayed correctly in the browser.

    If the hit page is not shown correctly, then you probably need to alter the Additional Base URL setting in the configuration screen Searching section.

Index your own site

Follow the general Getting Started instructions to index your own site to build a search database and start searching.

Test Word highlighting

See the Word highlighting instructions for details of how to set this up for HTML pages shown in Internet Explorer 4+.

Additional Macromedia JRun Instructions

Updating findinsite-js

The only way to update findinsite-js seems to be to uninstall it, as described below, and installing it again.
Make sure that you save the work directory during the upgrade process, if necessary.

Note that you will probably need to reset the findinsite-js work init parameter to your chosen directory, as described above.

Uninstalling findinsite-js

  1. Start the "JRun Management Console" and login.
  2. In the navigation panel, expand the relevant server, eg "JRun Default Server" and click on "Web Applications"
  3. Click on "Remove an Application" in the main window
  4. Select "FindinSite" and click on "remove"
  5. Restart the JRun Default Server
  All site Copyright © 1996-2011 PHD Computer Consultants Ltd, PHDCC   Privacy  

Last modified: 14 September 2005.

Valid HTML 4.01 Transitional Valid CSS!