Install a single-host cluster

  1. Prepare for installation:
    1. Obtain the necessary files.
    2. Check ports.
    3. Check the installation directory.
  2. As root, set up the cluster administrator and deploy the software:
    1. Define the database host.
    2. Define the cluster administrator.
    3. Run the RPM package.
    4. Set the command-line environment.
    5. Grant root privileges to egoadmin.
  3. As egoadmin, configure and test the cluster:
    1. Set the command-line environment.
    2. Join the host and the cluster.
    3. Configure the license.
    4. Start the host.
    5. Test the web server.

You can use this host to test or demonstrate some of the functions you would perform in a production cluster.

If you want to convert the host into a functional master host of a production clutser, follow the steps described in Migrate to a Multiple-Host Cluster.

Obtain the necessary files

Contact Platform Computing to obtain these files:
  • Demo license

  • Installation package

Obtain a demo license

For a single-host cluster, obtain a temporary license to be used for evaluation purposes.
Tip:

Copy the licence file to your host. Remember the location so you can configure the license after you install.

Obtain an RPM installation package

For a single-host cluster, obtain the RPM package that matches the kernel and glibc version of your host.

For example, for x86 hosts running Linux 2.4 with glibc version 2.3, install the package named ego-linux2.4-glibc2.3-x86-1.2.3.nnnnnn.rpm.

Tip:

Run uname -a on the host to check the kernel version. Run rpm -q glibc on the host to check the glibc version.

Check ports

The installation requires the following ports. Make sure these ports are not being used by another application.

Check the installation directory

By default, the installation will create the /opt/ego directory and copy files there.

If you cannot install to /opt, or in the unlikely event that the ego subdirectory is being used for some other purpose, you have a conflict.

Log on as root

Log on as root and take the following steps.

  1. Define the database host.
  2. Define the cluster administrator.
  3. Run the RPM package.
  4. Set the command-line environment.
  5. Grant root privileges to egoadmin.

Define the database host

The database host will run the Derby database and manage data for the Reporting feature.

Tip:

If you do not define the database host, there is no data available for reports.

To configure the master host as the database host, set the DERBY_DB_HOST variable.

Set cluster properties using variables

Set custom variables before installation if you wish to customize the cluster properties.

You can set environment variables according to your login shell. If you do not wish to use environment variables, create a simple text file /tmp/install.config and enter each variable on a new line. An environment variable is ignored if the same variable is set in the cluster properties configuration file.

  • For sh, ksh, or bash: export VARIABLE_NAME=value

  • For csh or tcsh: setenv VARIABLE_NAME value

  • In install.config: VARIABLE_NAME=value

To make hostM the DB host:
  • For sh, ksh, or bash: export DERBY_DB_HOST=hostM

  • For csh or tcsh: setenv DERBY_DB_HOST hostM

  • In the cluster properties configuration file: DERBY_DB_HOST=hostM

Define the cluster administrator

The cluster administrator will be the only non-root account that can start the cluster or edit configuration files. You can make any account the cluster administrator, but you cannot change it after installation.

Tip:

If you can create a new user account named egoadmin, do so, and skip the rest of this procedure. By default, the installer automatically makes egoadmin the cluster administrator (but it cannot create the account if it does not exist).

To use your own user account as cluster administrator, set the CLUSTERADMIN variable, and substitute the actual name of your own account whenever the documentation refers to egoadmin. This is just like setting the DERBY_DB_HOST variable.

Run the RPM package

Run RPM using the default installation options:

rpm -ivh package_name.rpm

package_name.rpm is the name of the RPM package.

For example:

rpm -ivh ego-linux2.4-glibc2.3-x86-1.2.3-nnnnnn.rpm

Set the command-line environment

On Linux hosts, set the environment before you run any EGO commands. You need to do this once for each session you open. Both root and egoadmin accounts use EGO commands to configure and start the cluster.

You need to reset the environment if the environment changes during your session, for example, if you run egoconfig mghost, which changes the location of some configuration files.

These examples assume the default installation directory /opt/ego.

  • For csh or tcsh, use cshrc.ego:

    source /opt/ego/kernel/conf/cshrc.ego

  • For sh, ksh, or bash, use profile.ego:

    . /opt/ego/kernel/conf/profile.ego

Grant root privileges to egoadmin

By default, only root can start, stop, or restart the cluster.

This step gives egoadmin (the cluster administrator) permission to do these things also.

Run the egosetsudoers.sh command.

When you run egosetsudoers.sh, it does the following:

It creates the /etc/ego.sudoers file. The file owner is root and the permissions are set to 600 because you ran this command as root. Only the root user can edit this file.

It will setuid the egosh command and change the owner of egosh to root.

Whenever you see instructions to log on as root to start, stop, or restart a host in the cluster, you may log on as egoadmin instead.

Log on as egoadmin

Log on as egoadmin (the cluster administrator account you made during installation) and take the following steps:

  1. Set the command-line environment.
  2. Join the host and the cluster.
  3. Configure the license.
  4. Start the host.
  5. Test the web server.

Set the command-line environment

Set the command-line environment for egoadmin, same as you did for root.

  • For csh or tcsh, use cshrc.ego:

    source /opt/ego/kernel/conf/cshrc.ego

  • For sh, ksh, or bash, use profile.ego:

    . /opt/ego/kernel/conf/profile.ego

Join the host and the cluster

This step is necessary, even for a single-host cluster.

Run egoconfig to join the cluster.

For example:

egoconfig join HostM

Configure the license

Run egoconfig to configure the license.

Specify the full path to your license file:

egoconfig setlicense license_file_path

For example:

egoconfig setlicense /tmp/platform/license.dat

This command copies your license file from the location specified by license_file_path to the $EGO_CONFDIR directory, names the file license.dat, and sets the license file path in ego.conf.

Start the host

Run egosh to start EGO on your host.

egosh ego start

Test the web server

  1. Launch any web browser and visit this URL.

    http://master_host_name:8080/Platform

    If you see the Platform Management Console web page, your web server is running.

  2. Log on to the Console and check host status (optional):
    1. User Name: Admin
    2. Password: Admin
    3. On the Cluster Health section of the Cluster Health Dashboard, check the host status of the master host is ok.
      Tip:

      This may take several minutes, depending on your cluster and host configuration.

Resolve port conflicts

Resolve connection ports

The default base connection port is 7869. EGO uses five consecutive ports starting from this base port (7869-7873).

  1. You must set the BASEPORT variable to the base port that you choose.
  2. If there is a conflict, choose any free port as base port, and check that the next three ports are also free.

    For example, if you choose 7939 as your base port, check that ports 7939-7942 are not in use.

Resolve web server ports

Ports 8080, 8005, and 8009 are used by the web server.

  1. If there is a conflict, edit opt/ego/gui/tomcat/conf/server.xml and opt/ego/gui/conf/wsm.conf.
  2. Replace all occurrences of the default port numbers with the actual ports you want to use

Resolve the SD port

Ensure that port 53 is free (the default DNS server port).

Database host port

Ensure that port 1527 is free (the default Derby database port).

Web service gateway port

Port 9090 is used by the web service gateway.

  1. Ensure that port 9090 is free to be used by the web service gateway.
  2. If there is a conflict, go to the EGO configuration directory and edit wsg_port in opt/ego/kernel/conf/wsg.conf.

Resolving installation directory conflicts

If you cannot use the default installation directory, choose any directory on your host as the installation directory. The installer will create the directory if it does not already exist. If it already exists, make sure it is empty.

Read this section, then return to the default procedure (Define the cluster administrator). However, when it is time to run the RPM package, install to a custom directory using these instructions instead of the default instructions.

  1. Find your RPM version.
  2. Install to a custom installation directory.

Find your RPM version

To find out which version of RPM you are using, use the rpm --version option. Different versions of RPM require different options to install the packages.

rpm --version

RPM version 4.2.3

If you have RPM version 4.1.x or earlier: Some versions of RPM do not support the --prefix option. If the --prefix option is not supported, you need to set the RPM_INSTALL_PREFIX variable and specify the installation directory you want. This is just like setting the DERBY_DB_HOST variable; use one of the methods described in Define the database host.

Install to a custom installation directory

Run RPM and specify the installation directory:
  • For RPM version 4.2.x or later:

    rpm -ivh --prefix install_dir package_name.rpm
    • install_dir is the installation directory

    • package_name.rpm is the name of the RPM package

    For example:

    rpm -ivh --prefix /opt/test/ ego-linux2.4-glibc2.3-x86-1.2.3-nnnnnn.rpm

  • For RPM version 4.1.x or earlier, if the --prefix option is not supported, set one more environment variable before you run the package:

    setenv RPM_INSTALL_PREFIX install_dir

    rpm -ivh package_name.rpm
    • install_dir is the installation directory

    • package_name.rpm is the name of the RPM package

    For example:

    setenv RPM_INSTALL_PREFIX /opt/test

    rpm -ivh ego-linux2.4-glibc2.3-x86-1.2.3-nnnnnn.rpm

The installer will create the installation directory if it does not already exist.