+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Administration Manual v1.50: Java Web applet</TITLE>
- <LINK HREF="adminmanual-8.html" REL=next>
- <LINK HREF="adminmanual-6.html" REL=previous>
- <LINK HREF="adminmanual.html#toc7" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-8.html">Next</A>
-<A HREF="adminmanual-6.html">Previous</A>
-<A HREF="adminmanual.html#toc7">Contents</A>
-<HR>
-<H2><A NAME="s7">7.</A> <A HREF="adminmanual.html#toc7">Java Web applet</A></H2>
-
-<P>In the spider tree will be a directory <EM>spider-web</EM>. This is a
-neat little java web applet that can be run from a website. The applet
-must run on the same machine as the cluster. The included README file is
-shown below.</P>
-
-<P>I should comment here that the applet is precompiled, that is, ready to go.
-It was compiled using JDK1.3.1. If your version is earlier than this then it
-may not work. Should that be the case you need to recompile or update your
-JDK. To recompile do the following ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-cd /spider/spider-web
-rm *.class
-/usr/bin/javac spiderclient.java
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>I have used /usr/bin/javac as an example, your path to javac may be different.</P>
-<P>
-<PRE>
-Spider-WEB v0.6b
-
-Completely based on a clx web client written in Java by dl6dbh
-(ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
-
-The webserver has to run on the same machine as your DxSpider software!
-
-It is assumed that you have Java installed. You need JDK1.3.1 at least.
-
-Installation instructions (Performed as root):
-
-Put all the files in the spider-web directory into a newly created directory
-under the DocumentRoot of your websever for instance 'client'. In my case
-this is: /home/httpd/html/client/ although ymmv. For Suse the correct
-path should be /usr/local/httpd/htdocs/client/ for example.
-
-Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
-/home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
-/usr/local/httpd/cgi-bin/ for example.
-
-Change the permissions of the files to ensure they are correct, obviously you
-will need to use the correct path the the files according to your system:
-
-chmod 755 /home/httpd/html/cgi-bin/spider.cgi
-chmod -R 755 /home/httpd/html/client/
-
-By default the spider.cgi script should pick up your hostname (As long as this
-is set correctly). If it does not or your hostname differs from the name that
-you attach to the public address that you are using, then edit spider.cgi :
-
-# Uncomment and set the hostname manually here if the above fails.
-# $HOSTNAME = "gb7mbc.spoo.org" ;
-$PORT = "8000" ;
-
-'HOSTNAME' is the hostname of your cluster.
-
-'PORT' is the portnumber that you use to connect to your DxSpider via
-telnet (see Listeners.pm)
-
-NOTE: If you can start the console but cannot connect to the cluster from it,
-then it is possible that the machine you are on cannot resolve the hostname of
-your cluster machine. If this is the case, you need to set your hostname
-manually as above.
-
-You also need to set the $NODECALL variable. This prints the name of your
-choosing (probably your cluster callsign) on the html page.
-
-You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
-</PRE>
-</P>
-
-<HR>
-<A HREF="adminmanual-8.html">Next</A>
-<A HREF="adminmanual-6.html">Previous</A>
-<A HREF="adminmanual.html#toc7">Contents</A>
-</BODY>
-</HTML>
projects / spider.git / blobdiff