File: [Development] / failsafe / FailSafe-mgr / INSTALL (download)
Revision 1.4, Mon Aug 7 23:05:20 2000 UTC (17 years, 2 months ago) by rusty
Branch: MAIN
Changes since 1.3: +39 -1
lines
Added instructions on installing & launching the GUI as
an application & an applet.
|
INSTALL: $Date: 2000/08/07 23:05:20 $
===========================================================================
BUILDING & INSTALLING THE LINUX FAILSAFE GUI (fsmgr)
Before building fsmgr, you will need to install the following:
- A JDK 1.1 Java compiler; on Linux we've been using the IBM JDK 1.1.8,
which you should be able to get from http://www.ibm.com/java/jdk/.
- Rhino (sysadm_base) headers & libraries, available from
http://oss.sgi.com/projects/rhino/. If you are installing RPM packages
rather than building from source, you need the sysadm_base-lib,
sysadm_base-client, and sysadm_base-dev packages.
- FailSafe back-end headers & libraries, available from
http://oss.sgi.com/projects/failsafe/. If you are installing RPM
packages rather than building from source, you need the cluster_admin
and FailSafe-dev packages.
If you would prefer to build & install RPM packages, see INSTALL.rpm.
Otherwise, proceed with the configure, make, and install. You may want
to use different arguments to the configure script, but here's what we use
on Linux:
./configure --prefix=/usr --sysconfdir=/etc \
--with-JAVAPATH=/usr/jdk118/bin
make
make install
RUNNING THE GUI AS AN APPLICATION
After installing the client-side GUI software on a machine, the command
"fstask" should launch the FailSafe GUI Task Manager. (Or if you're using
GNOME or KDE, see if you've got a new FailSafe icon on your application
launcher's menu.) The GUI should give you a login screen where you choose the
server to connect to; choose a node in your cluster which has the server-side
GUI software installed. (You do not need to install the server-side GUI
software on every node in your cluster, but whenever you run the GUI, you need
to connect to a node which has the server-side GUI software. Also, you can
install the client-side GUI software on cluster nodes if you don't want to use
a separate machine for administration.)
RUNNING THE GUI AS AN APPLET
As an alternative to installing the GUI on client machines which will be
used for administering your cluster, you can install the jar files on one
or more of your cluster nodes and run the GUI as an applet in web browsers
which have a Java runtime or which support the Java plugin.
To do this, you will need to install the sysadm_failsafe-client and
sysadm_base-client packages on the server. (If sysadm_base-client claims
to require that a JRE be installed, you can ignore this, since you won't
actually be running any Java on the server: you just need the jar files.)
You will also need a web server, and server-side includes will need to be
enabled in the FailSafeManager directory. If everything is working correctly,
you should see a page when you open http://[your server]/FailSafeManager/ in
your web browser. The installed HTML pages contain support for running the
GUI using the browser's own Java runtime and using the Java plugin.
Note that the GUI as an applet has not been tested much. Except for a small
startup piece (RApplet instead of RApp), the GUI code which runs as an applet
is identical to the code which runs as an application, so it "should" work the
same. (Your results may vary depending on the behavior of your browser's Java
runtime, but as you know, Java is "Write Once, Run Anywhere.")