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 / BEA/Oracle WebLogic Server

 

findinsite-js installation guide for BEA/Oracle WebLogic Server


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.

This page was written when the product was named BEA WebLogic Server. It has not been updated since the software was rebranded as Oracle WebLogic Server.


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


BEA WebLogic Server

BEA WebLogic Server is a Java application server that includes a servlet engine. It is available for several platforms from (now http://www.oracle.com/appserver/). It supports the servlet specification JSDK 2.4.

WebLogic Server includes a servlet web server so it does not need to be connected to a web server when testing.

WebLogic Server has an "Admin Console" browser interface which makes it fairly easy to deploy findinsite-js.


findinsite-js Deployment, Configuration and Usage Instructions

These instructions are for WebLogic Server 7.0.


Installing findinsite-js

Installing the findinsite-js web application findinsitejs.war is usually called deployment.
  1. If necessary, use the WebLogic Server Domain Configuration Wizard to make a new domain connected to a server port.

  2. Start the WebLogic Server Admin Console, eg: http://localhost:7001/console.

  3. In the navigation panel on the left, open the domain and Deployments folders and click on "Web Applications".

  4. Click on "Configure a new Web Application..."

  5. Assuming that the findinsite-js Web Application (findinsitejs.war) is not listed at the bottom, click on "upload it through your browser". Browse to find the file findinsitejs.war on your local hard disk and then click on Upload.

  6. Click on "[select]" to the left of findinsitejs.war.

  7. Select one of the "Available Servers" and click on the right arrow icon to move the server into the "Target Servers" box.
    Enter any name for the application, eg Searcher.
    Click on the "Configure and Deploy" button.

  8. Wait until the screen updates to show the Deployed status as "true" and the "Deployment Activity" status as completed.


findinsite-js URLs

The following URLs should now be available (assuming that WebLogic Server is running locally at port 7001):
findinsite-js welcome page http://localhost:7001/findinsitejs/
findinsite-js documentation http://localhost:7001/findinsitejs/doc/
findinsite-js search page http://localhost:7001/findinsitejs/search
findinsite-js configuration screen http://localhost:7001/findinsitejs/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
Click on "Edit Web Application Deployment Descriptors..." to alter the work init parameter.


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:7001/findinsitejs/search. Check that the "findinsite-js" image is shown correctly; if not check the first IMG link in the template file FindHead.htt

  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 WebLogic Instructions

Log files

The findinsite-js log output is in the project/server directory.

For example, for user project "phdcc" on server "shiela", this is the log file...
   ../user_projects/phdcc/shiela/shiela.log


Uninstalling findinsite-js

In the WebLogic Server Admin Console, open the domain and Deployments folders and click on "Web Applications". Right-click on "findinsitejs" and select "Delete findinsitejs..."
  All site Copyright © 1996-2011 PHD Computer Consultants Ltd, PHDCC   Privacy  

Last modified: 13 September 2005.

Valid HTML 4.01 Transitional Valid CSS!