Configure the Platform Analytics node

Configure the Platform Analytics node to work with your cluster to work together efficiently.

What you need to do

  1. Stop the redundant PERF services (in Platform LSF 7 clusters only)
  2. Configure the Platform LSF cluster for the host core utilization data loader
  3. Enable FLEXnet data loaders in your cluster
  4. Enable FLEXnet Manager data loaders in your cluster
  5. Install and configure the Platform FLEXnet Manager scripts
  6. Enable and configure the remoting server client (asynchronous data loading mode only)

Stop the redundant PERF services (in Platform LSF 7 clusters only)

You can only stop the PERF services if you installed Platform Analytics node in a cluster running Platform LSF 7.

Platform Analytics runs its own PERF services independent of the cluster. Since Platform LSF 7 clusters also have PERF services running, you should stop the redundant PERF services to avoid unnecessary redundancy in your cluster.

  1. Log into any host in the LSF cluster as the cluster administrator.
  2. If you logged into a UNIX host, source the LSF environment.
    • For csh or tcsh: source LSF_TOP/conf/cshrc.lsf

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

  3. Navigate to the PERF binary directory.
    • UNIX: cd $PERF_TOP/version_number/bin

    • Windows: cd %PERF_TOP%\version_number\bin

  4. Stop the loader controller (plc) and data purger (purger) services.

    perfadmin stop plc

    perfadmin stop purger

  5. Rename the loader controller configuration file (plc.xml) to another file extension to remove it from the list of LSF services.

    For example, rename plc.xml to plc.xml.bak.

  6. Rename the data purger configuration file (purger.xml) to another file extension to remove it from the list of LSF services.

    For example, rename purger.xml to purger.xml.bak.

  7. Restart EGO on the LSF master host to activate these changes.

    egosh ego restart lsf_master_host_name

LSF 8 users who have not applied the LSF 8 add-on data solution

Follow these steps only if you have LSF 8 installed and if you have not applied the LSF 8 add-on data solution (Oct Qpk).

  1. Log into the Platform Analytics node host.
  2. Edit the $PERF_TOP/conf/perf.conf file, navigate to the line:

    LSF_VERSION = 8.0

    Change 8.0 to 7.0

    If you do not change the version, the data you see may not be accurate.

    Note:

    Defining LSF_VERSION in PA node as 7.0 changes some of the loader behaviours:

    • lsfeventsloader loads JOB_FINISH events from lsb.stream files instead of JOB_FINISH2 events.

    • Data loading of bjobs data is sampled by lsfbjobloader instead of lsfjobstatusloader.

    • Data loading of jobs pending reason is sampled by lsfpendingreasonloader, instead of lsbpendingreasonloader.

  3. Navigate to the LSF directory $LSF_LIBDIR/../../../ and create a linked directory 7.0: In -s 8.0 7.0
    Note:

    This is for Platform Analytics dataloaders to dynamically link to LSF libraries after changing LSF_VERSION defined in the Platform Analytics node.

Configure the Platform LSF cluster for the host core utilization data loader

Configure elim in the Platform LSF cluster to allow the hostcoreutilloader data loader to collect data from the cluster.

  1. Log into the Platform Analytics node host.
  2. If you logged into a UNIX host, source the LSF environment.
    • For csh or tcsh: source LSF_TOP/conf/cshrc.lsf

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

  3. Copy the elim.coreutil execution files from the Platform Analytics directory to the relevant Platform LSF directory.
    • UNIX:

      cp ANALYTICS_TOP/elim/os_type/elim.coreutil $LSF_SERVERDIR

      where os_type is aix, hpux, linux, or solaris, depending on the specific UNIX operating system.

    • Windows (Platform LSF 7.0.x and 8.0 only):

      copy ANALYTICS_TOP\elim\windows\elim.coreutil.exe LSF_TOP\version\etc

  4. Edit the LSF_TOP/conf/lsf.shared file and add CORE_UTIL as a resource.

    Add the following text to the Resource section:

    CORE_UTIL     String   300     ()          (Core Utilization)

    For example,

    Begin Resource
    RESOURCENAME  TYPE    INTERVAL INCREASING  DESCRIPTION
    CORE_UTIL     String   300     ()          (Core Utilization)
    End Resource
  5. Edit the LSF_TOP/conf/lsf.cluster.cluster_name file and add CORE_UTIL as a resource map.

    Add the following text to the Resource section:

    CORE_UTIL     [default]

    For example,

    Begin ResourceMap
    RESOURCENAME  LOCATION
    CORE_UTIL     [default]
    End ResourceMap
  6. Reconfigure the Platform LSF cluster to apply your changes.

    badmin reconfig

    lsadmin reconfig

Enable FLEXnet data loaders in your cluster

Check the following:

  • You configured Platform Analytics to collect FLEXnet license data.

  • The FLEXnet usage data loader and the FLEXnet license server are using the same time zone.

  1. Log into the Platform Analytics node host.
  2. Modify the FLEXnet usage data loader configuration file to set up a server list pointing to the FLEXnet license servers.
    1. Edit the FLEXnet usage data loader configuration file.
      • UNIX: ANALYTICS_TOP/conf/dataloader/flexlicusage.properties

      • Windows: ANALYTICS_TOP\conf\dataloader\flexlicusage.properties

    2. Change the ServerList (or FileName) parameter to point to the FLEXnet license servers.
  3. Modify the FLEXnet events data loader configuration file to point to the license log file.
    1. Edit the FLEXnet events data loader configuration file.
      • UNIX: ANALYTICS_TOP/conf/dataloader/flexlicevents.properties

      • Windows: ANALYTICS_TOP\conf\dataloader\flexlicevents.properties

    2. Change the LicenseLogFile parameter to point to the FLEXnet license log file. Even for Windows, you should use a slash rather than a backslash.

      For example,

      • UNIX: LicenseLogFile=/file_path/lmgrd.log

      • Windows: C:/file_path/lmgrd.log

  4. Start the Platform Analytics node host by restarting the loader controller (plc) service.

    perfadmin stop plc

    perfadmin start plc

Enable FLEXnet Manager data loaders in your cluster

You can only enable FLEXnet Manager data loaders if you configured Platform Analytics to collect FLEXnet license data.

  1. Log into the Platform Analytics node host.
  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. Add a data source for the FLEXnet Manager Reporting database to the Platform Analytics node.

    The FLEXnet Manager Reporting data source is named FNMReportDB.

    • In UNIX, run ANALYTICS_TOP/1.2/bin/dbconfig.sh add FNMReportDB

    • In Windows, run ANALYTICS_TOP\1.2\bin\dbconfig add FNMReportDB

  4. Modify the FLEXnet Manager data loader configuration file to point to the FLEXnet Manager servers.
    1. Edit the FLEXnet Manager data loader configuration file.
      • UNIX: ANALYTICS_TOP/conf/dataloader/fnmloader.properties

      • Windows: ANALYTICS_TOP\conf\dataloader\fnmloader.properties

    2. Change the DataSource parameter to specify the name of the data source for the FLEXnet Manager Reporting database.

      Each FLEXnet Manager server has its own data source, and each data loader can only access one data source; therefore, for each FLEXnet Manager server you need to specify a separate data source for each data loader.

      For the FLEXnet Manager Reporting database,

      DataSource=FNMReportDB

  5. Enable the FLEXnet Manager data loader in your cluster.
    1. Edit the loader controller configuration file for the FLEXnet Manager data loader:
      • UNIX: ANALYTICS_TOP/conf/plc/plc_license.xml

      • Windows: ANALYTICS_TOP\conf\plc\plc_license.xml

    2. Enable data gathering for the FLEXnet Manager data loader (fnmloader) by modifying the Enable attribute of the <DataLoader Name="fnmloader" .../> element.

      The element should now resemble the following:

      <DataLoader Name="fnmloader" ... Enable="true" ... />

  6. Start the Platform Analytics node host by restarting the loader controller (plc) service.

    perfadmin stop plc

    perfadmin start plc

Install and configure the Platform FLEXnet Manager scripts

You can only configure Platform’s FLEXnet Manager scripts if you configured Platform Analytics to collect FLEXnet license data.

Check that the following are installed and functional:

  • FLEXnet Manager, version 11 or later

  • Jasper reports

Configure Platform’s FLEXnet Manager (FNM) scripts to work with the FLEXnet Manager data loaders and your LSF cluster.

  1. Enable the Platform FLEXnet Manager data loader.
    1. Edit the loader controller configuration file for license data loaders.

      Edit PERF_TOP/conf/plc/plc_license.xml.

    2. Enable the FLEXnet Manager data loader.

      <DataLoader Name="fnmloader" ... Enable="true" ... />

    3. Restart the plc service for your changes to take effect.
  2. Deploy the esub script.

    This script provides the cluster name and job submission time to the LM_PROJECT environment variable, which passes the data to FLEXnet Manager to be collected by the Platform Analytics data loader.

    1. If you have an existing script in place, add the following information to it:
      modenv(LM_PROJECT => substr($PROJECT_NAME, 0, 5).",$LSF_CLUSTER_NAME,$SUBMIT");

      Note the following:

      • $LSF_CLUSTER_NAME is the name of the LSF cluster where the job is running

      • $SUBMIT is the job submission time as the number of non-leap seconds from 00:00:00 UTC, January 1, 1970.

    2. If you do not have an existing script, you need to copy and deploy the esub.fnm script, which is located in the PERF samples directory:
      • UNIX: $PERF_TOP/samples

      • Windows: %PERF_TOP%\samples

  3. Deploy the job starter script.

    This script provides the job ID and job array index to the LM_PROJECT environment variable, which passes the data to FLEXnet Manager to be collected by the Platform Analytics data loader.

    1. Edit lsb.queues and add the JOB_STARTER parameter with the path to the jstart script to each queue that you want to control a submitted.

      JOB_STARTER = /path_to_jstart/jstart

    2. In the command console, reconfigure the master host to activate this change.

      badmin reconfig

    3. In the command console, display detailed queue information to verify the configuration.

      bqueues ‑l queue_name

      For example, if you added the script to the Normal queue,

      bqueues ‑l normal

    4. If you have an existing script in place, add the following information to it:
      LM_PROJECT=$LM_PROJECT,$LSB_JOBID,$LSF_JOBINDEX
      export LM_PROJECT
    5. If you do not have an existing script, you need to copy and deploy the jstarter.fnm script, which is located in the PERF samples directory:
      • UNIX: $PERF_TOP/samples

      • Windows: %PERF_TOP%\samples

  4. Deploy the FNM data loader to a data collection host.

Enable and configure the remoting server client (asynchronous data loading mode only)

If you intend to use the asynchronous data loading mode, enable and configure the remoting server client.

You should only use the asynchronous data loading mode for sending data from the Platform Analytics node to the database over a slow or unstable network.

  1. Log into the Platform Analytics node host.
  2. Navigate to the ANALYTICS_TOP/conf directory.
  3. Rename the remotingclient.TMP file to remotingclient.xml.
  4. Edit the remotingclient.xml file and change the serverBindAddress and serverBindPort parameters according to the remoting server configuration.
  5. Edit the perf.conf file and add the following parameters:
    ASYNC_LOADING_ENABLED=Y
    ASYNC_LOADING_MODE=JBossRemoting
  6. Restart the loader controller service (plc).

    perfadmin stop plc

    perfadmin start plc