Upgrade Platform Analytics

Upgrade Platform Analytics from version 8.0 to version 8.0.2.

What you need to do

Check the following:

  • The Platform Analytics server and node hosts are running Platform Analytics 8.0.

    The Platform Analytics upgrade packages will work with any patches or solution packages that you installed, but will only work on version 8.0.

  • The Platform Analytics server and node hosts meet the detailed system and software requirements for Platform Analytics 8.0.2.

    Refer to the Release Notes for Platform Platform Analytics for the latest requirements.

  1. Upgrade the Platform Analytics server
  2. Verify the Platform Analytics server upgrade
  3. Upgrade the Platform Analytics node
  4. Verify the Platform Analytics node upgrade
  5. Upgrade the Platform Analytics report package
  6. Verify the reports package upgrade
  7. Data migration - for those who have upgraded LSF 7.x to LSF 8

After completing the Platform Analytics upgrade, you can optionally optimize the Platform Analytics node and server hosts.

Upgrade the Platform Analytics server

Upgrade the Platform Analytics server on a UNIX or Windows host.

Check the following:

  • You migrated the Vertica database schema to Platform Analytics 8.0.2.

    Important:

    The Platform Analytics upgrade package cannot detect whether you updated the database schema. If you proceed with the upgrade without migrating the database schema, some Platform Analytics server tasks will encounter problems and send events.

Upgrade the Platform Analytics server using the Platform Analytics server upgrade package. The upgrade package will make backups of the previous version of Platform Analytics before upgrading your server to the latest version.

  1. Log into the Platform Analytics server host with the same account that you used to install the previous version of Platform Analytics.
  2. Extract the server patch.

    unzip <server_upgrade_package>

  3. If you connected to the UNIX host, grant the execution permission to the analytics8.0.2_upgrade_server_${OS}/patch_tools directory..
  4. Run the Platform Analytics server upgrade package.
    • UNIX: analytics8.0.2_upgrade_server_${OS}/patch_tools/pinstall.sh

    • Windows: analytics8.0.2_upgrade_server_${OS}\patch_tools\pinstall.bat

    Remember:

    pinstall will automatically back up the original files from ANALYTICS_TOP, copying the files from the patch directory to this directory.

    For the Analytics server, pinstall will automatically stop the Platform Task Scheduler, which may cause running Analytics tasks to report a failed status. However, this does not indicate any data loss.

  5. Copy Platform Analytics 8.0.2 license to ANALYTICS_TOP/conf.
  6. Modify the task scheduler of the Platform Analytics Server.
    1. Open the Platform Analytics Console.
    2. Navigate to Scheduled Tasks.
    3. Add the following Scheduled Tasks

      - DailyReportETL

      To add a new task, Select Action -> Add Scheduled Task from the task bar.
      • Scheduled Task—task name DailyReportETL

      • Script File—bin/dataaggdaily.js

      • Script Function— doit

      • Select Enable Scheduling

      • Set the Run Interval—1 day

  7. (LSF 8 users only) Set LSF_VERSION in the pi.conf file.
    • Edit ANALYTICS_TOP/conf/pi.conf

    • Append the following line at the end of the file:

      LSF_VERSION=8

  8. Start Platform Analytics server.

The changed files from your previous version of Platform Analytics are backed up to the following location:

  • UNIX: ANALYTICS_TOP/upgrade_backup/version_number

  • Windows: ANALYTICS_TOP\upgrade_backup\version_number

Verify the Platform Analytics server upgrade

Verify that you have successfully upgraded the Platform Analytics server on a UNIX or Windows host.

You upgraded the Platform Analytics server and are still logged into the host.

  1. Verify that there are no errors generated in the event log file after the upgrade.

    The event log file is named event.log.host_name and is located in the PERF log directory:

    • UNIX: ANALYTICS_TOP/log

    • Windows: ANALYTICS_TOP\log

  2. Start the Platform Analytics Console.
    • UNIX: ANALYTICS_TOP/bin/runconsole.sh

    • Windows: Start > Programs > Platform Platform Analytics Server > Platform Platform Analytics Console

  3. Click Scheduled Tasks in the navigation tree and verify that there are no failed tasks.
  4. After at least an hour, verify that the data is collected and you can view reports.
  5. If your Platform Analytics installation has customizations, check that the customizations are still present.

Upgrade the Platform Analytics node

Upgrade the Platform Analytics node on a UNIX or Windows host.

Check the following:

  • You migrated the Vertica database schema to Platform Analytics 8.0.2.

    Important:

    The Platform Analytics upgrade package cannot detect whether you updated the database schema. If you proceed with the upgrade without migrating the database schema, the Platform Analytics data loaders will encounter problems and send events.

Upgrade the Platform Analytics node using the Platform Analytics node upgrade package. The upgrade package will make backups of the previous version of Platform Analytics before upgrading your node to the latest version.

The upgrade package stops the Platform Analytics data loaders to upgrade these components. These data loaders will not be stopped for longer than five minutes under normal circumstances.

Note:

You cannot upgrade Platform Analytics node on the Windows host. Choose a Unix host to upgrade.

  1. Log into the Platform Analytics node host with the same account that you used to install the previous version of Platform Analytics.
  2. Extract the node patch.

    unzip <node_upgrade_package>

  3. If you connected to the UNIX host, grant the execution permission to the upgrade_node_${OS}/patch_tools directory..
  4. Run the Platform Analytics node upgrade package.
    • UNIX: analytics_upgrade8.0.2_node_${OS}/patch_tools/pinstall.sh

    Remember:

    pinstall will automatically back up the original files from ANALYTICS_TOP, copying the files from the patch directory to this directory.

    For the Analytics node, pinstall will automatically restart the data loader (plc), which may cause data loss in some data loaders that are currently used.

  5. Copy Platform Analytics 8.0.2 license to ANALYTICS_TOP/conf.
  6. Enable lsbpendingreasonloader/lsfjobstatusloader data loader.

    Edit the ANALYTICS_TOP/conf/plc/plc_lsf_advanced.xml file and add the line below into node <Dataloaders>.

    <DataLoader Name="lsbpendingreasonloader" Interval="600" Enable="true" LoadXML="dataloader/lsbpendingreasons.xml" />

    <DataLoader Name="lsfjobstatusloader" Interval="600" Enable="true" LoadXML="dataloader/lsbstatus.xml" />

  7. Edit the ANALYTICS_TOP/conf/dataloader/lsbevents.properties file.

    Add event type JOB_FINISH2 and JOB_STARTLIMIT to ALLOW_EVENT_TYPE field.

    This is for LSF 8.0.1 QPK users only. Add event type JOB_STATUS2 and enable this in the LSF configuration file lsb.params.

    For example, ALLOW_EVENT_TYPE=JOB_NEW JOB_FINISH JOB_FINISH2 JOB_STARTLIMIT JOB_STATUS2

  8. (Optional) Edit the ANALYTICS_TOP/conf/dataloader/lsbpendingreasons.properties[lsbstatus.properties] file.
    • If you do not want the lsbpendingreasonloader/lsfjobstatusloader data loader to delete historical lsb.pendingreaons/lsb.status files after loading the file, add the following line:

      AUTO_DELETE_STREAM_FILE=N

    • Set REMAINED_FILE_NUM to define the number of historical lsb.pendingreaons/lsb.status file. The minimum value is 1. The maximum value should be less than the value of MAX_EVENT_STREAM_SIZE, which is defined in the lsb.params file.

    • Set ARCHIVE_PATH to define the place to backup historical lsb.pendingreasons/lsb.status file.

      For example, ARCHIVE_PATH=/tmp

  9. Verify that the plc service has started. If not, restart the loader controller.

    perfadmin stop plc

    perfadmin start plc

The changed files from your previous version of Platform Analytics are backed up to the following location:

  • UNIX: ANALYTICS_TOP/.patch_backup

Verify the Platform Analytics node upgrade

Verify that you have successfully upgraded the Platform Analytics node on a UNIX or Windows host.

You upgraded the Platform Analytics node and are still logged into the host.

  1. Verify that the data loaders are running.
    • UNIX: plcclient.sh ‑s

  2. After at least one hour, verify that there are no errors in any of the data loader log files.

    You need to wait at least one hour because this is the longest data sampling interval of the data loaders.

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

    • UNIX: ANALYTICS_TOP/log/dataloader

  3. Verify that there are no errors in the loader controller log file.

    The loader controller log file is named plc.log.host_name and is located in the PERF log directory:

    • UNIX: ANALYTICS_TOP/log

Upgrade the Platform Analytics report package

Upgrade the Platform Analytics report package.

Uninstall previous reports and the parb service

  1. Run rptinstall.bat to publish the reports and install the parb service.
  2. Reinstall PAC 8.0.2 as Platform Analytics8.0.2 supports only the 8.0.2 version of Platform Applicaqtion Center.
  3. Log into the Platform Analytics reporting server with the same account that you used to install the previous version of Platform Analytics.
  4. Extract the report patch.

    unzip <report_upgrade_package>

  5. Follow the dialog prompts to complete the installation. Specify the following to complete the installation.
    • Database type

    • Database server name

    • Database name

    • Database port number

    • Database user name and password

    • Tableau server directory

    • Whether or not to use SSL

    • Tableau server administrator name and password

    • Tableau server port number

    Note:

    To publish customized workbooks, you have to install and use the Platform Analytics Designer or run the the tabcmd tool provided by the Tableau server.

Verify the reports package upgrade

Once data is collected in the database, you can view reports using the Analytics reporting server. Optionally, you can even view reports using Platform Analytics Designer or Platform Application Center.

  1. Log in to the Platform Analytics reporting server.

    http://<host_name>:<port>

    where <host_name> is the name of the system where Tableau server is installed and <port> is the number which you entered during the Tableau server installation.

  2. See if you can view workbooks, worksheets, and dashboards. Try to change measures and dimensions and see if you can view new reports.

Data migration - for those who have upgraded LSF 7.x to LSF 8

This is the mandatory step for LSF 8 users who have applied the LSF 8 add-on data solution and have enabled new data set: JOB_FINISH2, JOB_STATUS2, and JOBS_PENDINGREASONS events.

  1. Log on to Platform Analytics server host.
  2. Make sure that the value of LSF_VERSION which in pi.conf file is 7.
  3. Start the Platform Analytics server.
  4. Monitor the log files that are in the ANALYTICS_TOP/log/datatransformer directory and wait untill you see "Records written: 0" in all these log files.
    • ClusterCapacity.log.HOSTNAME

    • WorkloadStatistics.log.HOSTNAME

    • Hardware.log.HOSTNAME

    • WorkloadAccounting.log.HOSTNAME

    • FlexlmLicUsage.log.HOSTNAME

  5. Change the value of LSF_VERSION which in pi.conf file from 7 to 8.
  6. Restart the Platform Analytics server.