Open topic with navigation
The LifeKeeper GUI is included in the steeleye-lkGUI software package which is bundled with the LifeKeeper Core Package Cluster. The steeleye-lkGUI package:
Installs the LifeKeeper GUI Client in Java archive format.
Installs the LifeKeeper GUI Server and modifies /etc/inittab to include the GUI server.
Installs the LifeKeeper administration web server, mhttpd, and modifies /etc/inittab to include the web server.
Note: The LifeKeeper administration web server is configured to use Port 81, which should be different from any public web server.
Installs a Java policy file in /opt/LifeKeeper/htdoc/ which contains the minimum permissions required to run the LifeKeeper GUI. The LifeKeeper GUI application uses the java.policy file in this location for access control.
Prepares LifeKeeper for GUI administration.
Before continuing, you should ensure that the LifeKeeper GUI package has been installed on the LifeKeeper server(s). You can enter the command rpm -qi steeleye-lkGUI to verify that this package is installed. You should see output including the package name steeleye-lkGUI if the GUI package is installed.
Perform the following steps for each LifeKeeper server. Each step contains references or links for more detailed instructions.
You must install the Java Runtime Environment (JRE) or Java Software Development Kit (JDK) on each server. See the LifeKeeper for Linux Release Notes for the required Java version and URL to access the required download. Note: You may install the JRE from the LifeKeeper Installation Support CD by running the setup script on the Installation Support CD, and opting only to install the JRE. (See the Using the LifeKeeper Installation Support CD topic for more information.)
Start the LifeKeeper GUI Server on each server (see Starting/Stopping the GUI Server). Note: Once the GUI Server has been started following an initial installation, starting and stopping LifeKeeper will start and stop all LifeKeeper daemon processes including the GUI Server.
If you plan to allow users other than root to use the GUI, then you need to Configure GUI Users.
You can run the LifeKeeper GUI:
on the LifeKeeper server in the cluster and/or
on a remote system outside the cluster
See Running the GUI on the LifeKeeper Server for information on configuring and running the GUI on a server in your LifeKeeper cluster.
See Running the GUI on a Remote System for information on configuring and running the GUI on a remote system outside your LifeKeeper cluster.
|GUI client and server communication||The LifeKeeper GUI client and server use Java Remote Method Invocation (RMI) to communicate. For RMI to work correctly, the client and server must use resolvable hostnames or IP addresses. If DNS is not implemented (or names are not resolvable using other name lookup mechanisms), edit the /etc/hosts file on each client and server to include the names and addresses of all other LifeKeeper servers.|
|GUI Server Java platform||The LifeKeeper GUI server requires that the Java Runtime Environment (JRE) - Java virtual machine, the Java platform core classes and supporting files - be installed. The JRE 5.0 for Linux is available on the LifeKeeper for Linux Installation Support CD (See the LifeKeeper Planning and Installation Guide) or it can be downloaded directly from http://java.sun.com/javase/downloads/index_jdk5.jsp.
Note: By default, the LifeKeeper GUI server expects the JRE on each server to be installed in the directory /usr/java/j2re1.5.0_07. If this is not found, it will look in the directory /usr/java/j2sdk1.5.0_07 for a Java Software Development Kit (JDK). If you want to use a JRE or JDK in another directory location, you must edit the PATH in the LifeKeeper default file /etc/default/LifeKeeper to include the directory containing the java interpreter, java.exe. If LifeKeeper is running when you edit this file, you should stop and restart the LifeKeeper GUI server to recognize the change. Otherwise, the LifeKeeper GUI will not be able to find the Java command.
|Java remote object registry server port||The LifeKeeper GUI server uses port 82 for the Java remote object registry on each LifeKeeper server. This should allow servers to support RMI calls from clients behind typical firewalls.|
|LifeKeeper administration web server||The LifeKeeper GUI server requires an administration web server for client browser communication. Currently, the LifeKeeper GUI server is using a public domain web server, mhttpd, for its administration web server. The installation of the LifeKeeper GUI installs and configures this web server, using port 81, which should be different from any public web server.|
|GUI client network access||LifeKeeper GUI clients require network access to all hosts in the LifeKeeper cluster. When running the LifeKeeper GUI client in a browser, you will have to lower the security level to allow network access for applets. Be careful not to visit other sites with security set to low values (e.g., change the security settings only for intranet or trusted sites).|
|GUI interoperability restriction||The LifeKeeper for Linux client may only be used to administer LifeKeeper on Linux servers. The LifeKeeper for Linux GUI will not interoperate with LifeKeeper for Windows.
© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.
Open topic with navigation