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

 

findinsite-js installation guide for IBM WebSphere


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.


Introduction

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
WebSphere introduction
Setting up...
Install findinsite-js
findinsite-js URLs
Work directory
Run test searches
Index your own site
Word highlighting
Configuration
Init parameters
Updating findinsite-js
Uninstalling findinsite-js


IBM WebSphere

IBM WebSphere is a Java application server that includes a servlet engine. It is available for several platforms from http://www.ibm.com/websphere/. WebSphere 4.0 supports the servlet specification JSDK 2.2.

WebSphere can be connected to several types of main server, including the "IBM HTTP Server" which is based on Apache. WebSphere includes a servlet web server so it does not need to be connected to a web server when testing.

WebSphere has an "Administrative Console" browser interface which makes it fairly easy to deploy findinsite-js.


findinsite-js Deployment, Configuration and Usage Instructions

The instructions below are for WebSphere 4.0, connected to the IBM HTTP Server.

findinsite-js has also tested OK on the Windows version of WebSphere Application Server version 5; the instructions below work, with two extra options page; and you will need to start findinsite-js in the Administrative Console Applications+Enterprise Applications section.


Installing findinsite-js

Installing the findinsite-js web application findinsitejs.war is usually called deployment.
  1. Start the WebSphere Administrative Console, eg: http://localhost:9090/admin. Give any suitable login username.

  2. In the navigation panel on the left, open Nodes, then SERVER, then click on "Enterprise Applications".

  3. Click on Install
    Fill in the top 3 fields as follows:

    Path:Browse to find findinsitejs.war on your local disk
    Application name:Eg FindinSite
    Context Root:Eg /fisjs
    Click Next

    In the next screen, select an appropriate Virtual Host, eg default_host. You can set Precompile JSPs to No.
    Click Next

    Confirm installation and click Finish.

  4. Click on link: "Plug-in configuration needs to be regenerated".
    Click Generate

  5. Click on link: "Configuration needs to be saved".
    Click OK

  6. Click Exit at top to exit console.

  7. Stop WebSphere

    Do this from the "First steps" panel,
    Or by running <WS_INSTALL_DIR>/bin/stopserver.bat

  8. Stop and restart the "IBM HTTP Server" service so that the new plug-in mapping is recognised.

    In W2000, open the Control Panel, select Administrative Tools, then Services.
    In NT4, open the Control Panel, then Services.
    Find "IBM HTTP Server". Right-click, first to stop and then again to start the server service.

  9. Restart WebSphere


findinsite-js URLs

The following URLs should now be available (assuming that "IBM HTTP Server" is running on the default web server port of 80, and the context 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 WebSphere "Application Assembly Tool"
  2. Open the findinsite-js auto-generated .EAR file, eg
    ../AppServer/installedApps/FindinSite.ear
  3. In the tree, drill down into "Web Modules+FindinSite+Web Components+FindinSite+initialization Parameters"
  4. Select the desired parameter on the right, eg work
  5. Enter a new Parameter value and click on Apply
  6. Then File+Save the application assembly

  7. In the "WebSphere Administrative Console", find the "Enterprise Applications" list.
  8. Select the checkbox next to FindinSite, click "Stop" then "Start"
  9. Wait until findinsite-js is running again


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. Check that the "findinsite-js" image is shown correctly; if not check the first IMG link in the template file FindHead.htt in the WebSphere installedApps/FindinSite.ear/findinsitejs.war/ directory.

  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 IBM WebSphere 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. In the "WebSphere Administrative Console", find the "Enterprise Applications" list.
  2. Select the checkbox next to FindinSite, click "Uninstall"
  All site Copyright © 1996-2011 PHD Computer Consultants Ltd, PHDCC   Privacy  

Last modified: 14 September 2005.

Valid HTML 4.01 Transitional Valid CSS!