Install the Platform Analytics node

Install the Platform Analytics node package on a UNIX or Windows host. You need to have one Platform Analytics node host in each cluster that Platform Analytics will handle.

What you need to do

Check the following:

  • The Platform Analytics node host meets the detailed system and software requirements.

    For more details, refer to Prepare for the Platform Analytics installation.

  • The Platform Analytics node host operating system can handle daylight savings time correctly.

  • If you want the Platform Analytics node to collect LSF cluster data, check the following:

    • You have access to the primary LSF administrator account.

    • The Platform Analytics node host must be an LSF server in the cluster with access to the LSF event file (lsb.stream).

  • If you are installing on a UNIX host, your host must have access to the X-Windows environment:

    • If you are connected to the intended Platform Analytics node host locally, the host must be running X-Windows.

    • If you are connected to the intended Platform Analytics node host via telnet, you must be running xserver on your local host.

  • The required port for the Platform Analytics hosts is free. If a firewall exists, this TCP port must be open in the firewall.

    For more details, refer to Platform Analytics hosts.

  • The Vertica database host is properly configured and running.

  • The Platform Analytics node host has access to the Vertica JDBC driver.

  • The Oracle database host is properly configured and running:

    • You have a user name, password, and URL to access the database.

    • There is appropriate space in the database allocated for Platform Analytics.

    • Platform Analytics supports your version of the Oracle database.

  • The Platform Analytics node host has access to the Oracle JDBC driver (version 10.2.0.3 only). This driver is available from the following URL:

    http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html

  • The Platform Analytics node host has access to the Platform Analytics license file (license.dat).

  1. Log into the intended Platform Analytics node host.
    • In UNIX, if you want to update the rc.boot scripts, log in as root.

    • In Windows, log in as the intended Platform Analytics administrator account. If you want the Platform Analytics node to collect LSF cluster data, you must log in as the primary LSF administrator.

  2. If you connected to the UNIX host via telnet and are running xserver on a local host, set your display environment.

    Test your display by running xclock or another X-Windows application.

    If the application displays, your display environment is already set correctly; otherwise, you need to set your display environment.

    • For csh or tcsh:

      setenv DISPLAY hostname:0.0

    • For sh, ksh, or bash:

      DISPLAY=hostname:0.0

      export DISPLAY

    where hostname is your local host.

  3. If you are installing on a UNIX host and you want the Platform Analytics node to collect LSF cluster data, source the LSF environment.
    • For csh or tcsh: source LSF_TOP/conf/cshrc.lsf

    • For sh, ksh, or bash: . LSF_TOP/conf/profile.lsf

  4. Run the Platform Analytics node installation package.
    • UNIX: ./platform_analytics8.0.2_node_platform.bin

    • Windows: platform_analytics8.0.2_node_platform.exe

  5. (Optional) If you do not have X-Windows installed on the LSF server, use the Console mode to install the Analytics node.

    For the Console mode: - console

  6. Follow the dialog prompts to complete the installation.

    To install the Platform Analytics node, you may need to input the following:

    • Platform Analytics license file location

    • Data collection settings

    • Installation directory

      Accept the default file path or specify your own installation directory.

      In this documentation, ANALYTICS_TOP refers to the top-level Platform Analytics installation directory in your host.

    • The type of data to collect from the cluster

    • Directory containing the lsf.conf file

      By default, this is the value of the LSF_ENVDIR environment variable.

    • Data source (database host) properties

      The user name and password is generally the account that you used to create your data schema.

      Replace the sample values in the URL field with the values for your database.

    • Loader controller service port

      You need to specify a port for the loader controller (plc), which uses 4046 by default.

    • Set RC properties, if you installed on a UNIX host as root.

      Enable this setting to update the rc.boot script.

  7. If you are installing on a UNIX host, source the PERF environment.
    • For csh or tcsh: source ANALYTICS_TOP/conf/cshrc.perf

    • For sh, ksh, or bash: . ANALYTICS_TOP/conf/profile.perf

  8. If you install Platform Application Center in the same cluster as Platform Analytics, disable the auto delete function of LSF events loader (lsfeventsloader) from Platform Application Center to prevent the lsb.stream.UTC files from being deleted automatically.
    • Edit the $PERF_CONFDIR/conf/dataloader/lsbevents.properties file of Platform Application Center.

    • Add AUTO_DELETE_STREAM_FILE=N

  9. Manually stop and start the plc service.

    perfadmin stop plc

    perfadmin start plc

  10. Verify that the data loaders are running.
    • Windows: plcclient ‑s

    • UNIX: plcclient.sh ‑s

  11. Verify that there are no errors in any of the data loader log files.

    The data loader log files are located in the dataloader subdirectory of the PERF log directory:

    • UNIX: $PERF_LOGDIR/dataloader

    • Windows: %PERF_LOGDIR%\dataloader