Installing the LifeKeeper Server for GUI Administration
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.
- 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.
Running the GUI
You can run the LifeKeeper GUI on the LifeKeeper server in 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.
GUI Configuration
| Item | Description |
|---|---|
| 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 LifeKeeper GUI supports OpenJDK. In the following environments, the setup script that is executed during installation installs OpenJDK that is included with the OS. If the Linux distributor does not provide OpenJDK, install the OpenJDK package included in the LifeKeeper installation image. See the Release Notes for supported OpenJDK versions.
Note: There is memory management inconsistency between the OpenJDKs that are included with LifeKeeper and the OS as for the combination of LifeKeeper and the OS version. In order to avoid that, OpenJDK that is included with the LifeKeeper installation image needs to be installed under the /opt/LifeKeeper/lib64/java. Memory management inconsistency has already been fixed but when LifeKeeper is upgraded, JRE that is installed on /opt/LifeKeeper/lib64/java will be used. If you want to use JRE that is included with the OS, install JRE and then follow the steps above to change the /etc/default/LifeKeeper PATH. /opt/LifeKeeper/lib64/java can be deleted since it is unnecessary.
|
| Uninstall Java Runtime Environment |
|
| 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 private copy of the lighttpd web server for its administration web server. This web server is installed and configured by the steeleye-lighttpd package and uses port 81 to avoid a conflict with other web servers. |
| 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 Limitations
| Item | Description |
|---|---|
| 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. |
Post your comment on this topic.