Platform Analytics Version for Symphony. Installing SC

Transcription

1 Platform Analytics Version for Symphony Installing SC

2

3 Platform Analytics Version for Symphony Installing SC

4 Note Before using this information and the product it supports, read the information in Notices on page 37. This edition applies to ersion 9, release 1, modification 2 of Platform Analytics (product number 5725-G84) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures Tables ii Chapter 1. Understanding Platform Analytics Platform Analytics hosts System port usage Analytics system ports System architecture diagram Chapter 2. Preparing to install Platform Analytics Selecting the hosts Selecting the database hosts Selecting the Analytics node hosts Selecting the Analytics serer host Selecting the Analytics reporting serer host... 7 Chapter 3. Installation requirements.. 9 Obtaining the installation files Pre-installation checklist Chapter 4. Installing Platform Analytics 11 Installing Database Analytics database checklist Installing the Analytics database Installing Platform Analytics Serer Analytics serer checklist Installing the Analytics serer Installing Platform Analytics Node Analytics node checklist Installing the Analytics node Verifying that Platform Analytics is up and running 17 Enabling and configuring the remoting serer (asynchronous data loading mode only) Configuring the Analytics node Stopping redundant PERF serices Enabling and configuring the remoting client (asynchronous data loading mode only) Optimizing the Analytics serer Changing the data retention period Optimizing the Analytics node Increasing JVM memory Distributing the Analytics node workload Optimizing the Analytics database Chapter 6. Uninstalling Platform Analytics Uninstalling the Analytics serer Uninstalling the Analytics node Chapter 7. Troubleshooting Platform Analytics Some or all Analytics database nodes fail to start due to a memory error Starting the Analytics database if all nodes failed to start Starting the Analytics database if some nodes failed to start Vertica data loader timeout error Third party issues Fail to create database due to the status of Vertica Node being DOWN Notices Trademarks Priacy policy considerations Chapter 5. Configuring and optimizing Platform Analytics Verifying and configuring the Analytics serer Copyright IBM Corp iii

6 i Installing Platform Analytics for Symphony

7 Figures 1. Platform Analytics Data Collectors for Symphony system architecture with Analytics nodes in two Symphony clusters Copyright IBM Corp. 2013

8 i Installing Platform Analytics for Symphony

9 Tables 1. Default Platform Analytics serer ports Default Platform Analytics node ports Default Platform Analytics third-party tool ports Recommended hardware specifications for the Analytics database hosts Recommended hardware specifications for the Analytics node hosts Recommended hardware specifications for the Analytics serer host, not using asynchronous data loading Recommended hardware specifications for the Analytics serer host, using asynchronous data loading Hardware configuration requirements for Tableau Serer Recommended hardware specifications for the Analytics reporting serer host Data loader categories and corresponding loader controller configuration files Copyright IBM Corp ii

10 iii Installing Platform Analytics for Symphony

11 Chapter 1. Understanding Platform Analytics Platform Analytics hosts System port usage Get to know the components, ports, and architecture of IBM Platform Analytics. These are the types of Platform Analytics hosts that you can install: Analytics node Analytics nodes are hosts on which Platform Analytics Data Collectors for Symphony is installed and which collect operational data from Platform Symphony clusters. Each node belongs to a cluster from which Platform Analytics is to collect data. In each cluster, the Analytics node software is installed on a Symphony management host. (For failoer support, the Analytics node must first be installed on the Symphony master host.) Analytics database The Analytics database runs on one or more hosts and stores the cluster operational data loaded from the Analytics nodes for later reporting and analysis. Analytics serer The Analytics serer manages the data that the Analytics nodes collect. You can perform all serer functions using the Analytics Console in the serer. Platform Analytics hosts and components use the following system ports. You must ensure that the system ports for Platform Analytics are open for the hosts and components to communicate with one another. You must also ensure that your web serer port is open. Analytics system ports Platform Analytics hosts use the following TCP ports by default. The following tables describe the configuration files that you must modify to change the default settings and the firewall configurations you must set to allow communication using these ports between the arious hosts. Analytics serer ports Table 1 lists information about the default Analytics serer ports. Table 1. Default Platform Analytics serer ports Port name Default port number Description PIAM_PORT 9091 Internal port for the task scheduler. Firewall configuration (all bidirectional) not applicable Configuration file ANALYTICS_TOP\conf\pi.conf PIEM_PORT 9092 The Analytics eent manager uses this port to receie eents from the Analytics serer and nodes. Allow connections for this port from each node host to the serer host. ANALYTICS_TOP\conf\pi.conf Copyright IBM Corp

12 Table 1. Default Platform Analytics serer ports (continued) Port name Default port number Description Firewall configuration (all bidirectional) Configuration file Remoting serer port 9093 The Analytics remoting serer uses this port to receie data from the remoting node. Allow connections for this port from the remoting node to the serer host. ANALYTICS_TOP\conf\ remotingserer.xml Table 2. Default Platform Analytics node ports Analytics node ports Table 2 lists information about the default Analytics node ports. Port name Default port number Description Firewall configuration (all bidirectional) Configuration file ALC port 4046 The Analytics serer uses this port to manage the Analytics loader controller (alc) on the Analytics node. Allow connections for this port from the serer host to each node host. ANALYTICS_TOP/conf/plc.xml Third-party tool ports Table 3 lists information about the default Analytics third-party tool ports. Table 3. Default Platform Analytics third-party tool ports Port name Default port number Description Firewall configuration (all bidirectional) Vertica port 5433 This port is required for client connectiity, such as JDBC. Allow connections for this port from serer and node hosts. System architecture diagram Cluster operations data collected from the Analytics nodes is stored in the Analytics database for subsequent reporting and analysis by IBM Platform Analytics to proide the information you need to make business decisions, such as: Identify and remoe resource bottlenecks that are affecting business Plan for capacity and future needs by seeing how capacity is being used and where capacity is aailable Optimize asset utilization by seeing how your infrastructure and resources are being used Improe productiity and efficiency of your applications, workload costs, and computing enironment The following diagram shows a sample architecture for a system that monitors multiple IBM Platform Symphony clusters. Figure 1 on page 3 illustrates a system architecture where an Analytics node runs on a management host in each of two Symphony clusters. 2 Installing Platform Analytics for Symphony

13 Figure 1. Platform Analytics Data Collectors for Symphony system architecture with Analytics nodes in two Symphony clusters Chapter 1. Understanding Platform Analytics 3

14 4 Installing Platform Analytics for Symphony

15 Chapter 2. Preparing to install Platform Analytics Selecting the hosts Before installing Platform Analytics, you will select the hosts that meet the detailed system requirements and download the Platform Analytics installation packages. You must select the appropriate hosts that meet the detailed system requirements for the Analytics database hosts, Analytics node hosts, Analytics serer host, and Analytics reporting serer host. Selecting the database hosts For optimal performance of your production database, the Analytics database cluster should consist of at least three dedicated multi-core hosts running on a high-bandwidth network. Since the Analytics database needs to share a large olume of data among the database nodes in the database cluster during data loading or data querying, network bandwidth is an important performance bottleneck for a production database. Therefore, the Analytics database cluster should hae a Gigabit Ethernet connection with the Platform Analytics reporting serer and the Analytics node hosts. Use a 1-10 GB full duplex switch for the priate network interface and a VLAN or separate switch for the public network. The switch used for the priate network should hae sufficient bandwidth to enable 1 GB transfer speeds between any pair of nodes. The hardware requirements are the same for all the intended database hosts. Refer to the Vertica Analytic Database documentation and IBM Platform Analytics Release Notes for the latest list of system requirements and supported operating systems for the Analytics database hosts. Input/output (I/O) performance is important for the operation of a database while fault tolerance is important to safeguard your data. Using a RAID 01 or 10 system enables the database host to take adantage of data striping and data mirroring. Data striping allows data to be transferred to multiple hard disks concurrently, which improes I/O performance. Data mirroring means that your database does not lose data een if a hard disk fails. Table 4 describes the optimal configuration of the database serer depending on the size of your cluster. The hardware requirements are the same for each database host. Table 4. Recommended hardware specifications for the Analytics database hosts Cluster size Number of hosts RAM CPU Local hard disk Network Medium ( hosts) Large (more than 1000 hosts) 3 16 GB 4 2.4GHz RPM SATA/SCSI/SAS/SSD RAID 01 or GB more than 3 32 GB 8 2.4GHz RPM SATA/SCSI/SAS/SSD RAID 01 or 10 1TB Gigabit Ethernet Gigabit Ethernet Copyright IBM Corp

16 Data striping Data striping is the technique of segmenting logically-sequential data, such as a single file, so that the database can assign segments to multiple physical deices (usually disk dries for RAID storage, or network interfaces for grid-oriented storage) in a round-robin fashion and thus be read or written concurrently. Automatic data striping is aailable in certain RAID deices under software or hardware control, and in file systems of clusters. The following parameters are important when improing I/O performance: Stripe width The number of parallel stripes that can be written to or read from simultaneously. This is the number of disks in the RAID system, and as it increases, the read/write performance of striped data also increases. Stripe size The size of the stripes written to each disk. This may also be referred to as block size, chunk size, stripe length, or granularity. You should use a large stripe size of at least 1 MB. If you are using RAID deices, you should use RAID 10 or RAID 01 because it offers the best performance of all RAID systems and good fault tolerance. Selecting the Analytics node hosts When selecting a host in the cluster to be a Platform Analytics node, you need to ensure that the host is running a supported operating system, and that it meets the minimum hardware requirements. See IBM Platform Analytics Release Notes for the latest system requirements for the Analytics node host. The Analytics node must run on a management host in each Platform Symphony cluster from which you want to collect data. For optimal performance of your Analytics node, the host should be running on a high-bandwidth network. Since network bandwidth is an important performance bottleneck for the Analytics nodes, the Analytics node host should hae a Gigabit Ethernet connection with the database host. If the node is running on a Windows host, you should use the 64-bit ersion of Windows because Jaa cannot use more than 1638MB of memory on 32-bit platforms. Table 5 describes the optimal hardware configuration of the Analytics node based on the size of the clusters in which the node resides. Table 5. Recommended hardware specifications for the Analytics node hosts Cluster size RAM CPU Local hard disk Network Medium ( hosts) Large (more than 1000 hosts) 4GB 2 2.4GHz 7200 RPM SATA/SCSI/SAS 50 GB 8GB 4 2.4GHz 7200 RPM SATA/SCSI/SAS 50 GB Gigabit Ethernet Gigabit Ethernet 6 Installing Platform Analytics for Symphony

17 Selecting the Analytics serer host When selecting a host to be the Platform Analytics serer, you need to ensure that the host is running a supported operating system. See IBM Platform Analytics Release Notes for the latest list of supported operating systems for the Analytics serer host. Tip: If you select a host that also meets the Tableau Serer system requirements, you can also select the Platform Analytics serer host to be the Platform Analytics reporting serer host. For optimal performance, the Analytics serer host should be a dedicated multi-core host with sufficient memory and input/output performance. The network bandwidth between the Analytics serer, the database hosts, and the Analytics nodes is a key performance factor in the Analytics serer host. If you are not using asynchronous data loading mode, the hardware configuration shown in Table 6 should be sufficient. Table 6. Recommended hardware specifications for the Analytics serer host, not using asynchronous data loading RAM CPU Local hard disk Network 4GB GHz 7200 RPM SATA/SCSI/SAS 50 GB Gigabit Ethernet If you are using asynchronous data loading mode, memory is a key performance factor for the Analytics serer host. You should only use the asynchronous data loading mode for sending data from the Analytics node to the database oer a slow or unstable network. Table 7 describes the optimal hardware configuration of the Analytics serer if you are using asynchronous data loading, depending on the size of your cluster. Table 7. Recommended hardware specifications for the Analytics serer host, using asynchronous data loading Cluster size RAM CPU Local hard disk Network Medium ( hosts) Large (more than 1000 hosts) 4GB 4 2.4GHz 7200 RPM SATA/SCSI/SAS 50 GB 8GB 4 2.4GHz 7200 RPM SATA/SCSI/SAS 50 GB Gigabit Ethernet Gigabit Ethernet Note: Aoid using an NFS disk mount instead of a local hard disk. Selecting the Analytics reporting serer host When selecting a host to be the Analytics reporting serer host, you must ensure that it meets the detailed system requirements for Tableau Serer shown in Table 8 on page 8. Chapter 2. Preparing to install Platform Analytics 7

18 Table 8. Hardware configuration requirements for Tableau Serer Operating system RAM CPU Serices User accounts Windows Serer 2003 (SP2 or later) Windows Serer 2008 Windows Serer 2008 R2 4 GB and aboe Dual-core Do not run Internet Information Serices (IIS) to aoid conflicts with the web serer port 80. Access to an administrator account to install software and serices. Access to a user account that the serice can use (optional). Tip: If the Analytics serer host also meets the Tableau Serer system requirements, you can select the Analytics serer host to also be the Platform Analytics reporting serer host. Refer to the Tableau Serer documentation or to IBM Platform Analytics Release Notes for the latest list of system requirements and supported operating systems for the Tableau Serer. The network bandwidth between the Platform Analytics reporting host and the database cluster may be an important performance bottleneck. Therefore, the Platform Analytics reporting host should hae a Gigabit Ethernet connection with database hosts. Table 9 describes the optimal hardware configuration of the Platform Analytics reporting serer, depending on the size of your cluster. Table 9. Recommended hardware specifications for the Analytics reporting serer host Cluster size RAM CPU Local hard disk Network Medium ( hosts) Large (more than 1000 hosts) 4GB 4 2.4GHz 7200 RPM SATA/SCSI/SAS 50 GB 8GB 4 2.4GHz 7200 RPM SATA/SCSI/SAS 50 GB Gigabit Ethernet Gigabit Ethernet 8 Installing Platform Analytics for Symphony

19 Chapter 3. Installation requirements Before you attempt to install Platform Analytics, you must ensure that you hae satisfied all of the installation requirements. Obtaining the installation files Pre-installation checklist Obtain the necessary installation files for Platform Analytics, the Analytics database, and the Tableau Serer. Obtain the following files to install Platform Analytics: IBM Platform Analytics serer installation package IBM Platform Analytics node installation package Choose the package that matches the operating system and system architecture on which you intend to install it. IBM Platform Analytics documentation package Obtain the following files to install the Analytics database: Analytics database installation package IBM Platform Analytics database schema package Obtain the following file to install Tableau Serer: Tableau Serer installation package Note: Obtain Vertica and Tableau keys from by proiding your name, your ID, Platform Analytics ersion (for example, 9.1.2), Platform Analytics edition (For example, Standard Ed), and date of purchase. Use the following pre-installation checklists to erify that you hae satisfied all of the installation requirements and are ready to install Platform Analytics. Important: Do not attempt to install Platform Analytics until you hae completed this checklist. Failure to satisfy all installation requirements may cause problems during or after the installation. Remember that system sizing depends on a number of factors, the most significant include: Number of sessions and tasks per day across all clusters Number of hosts to be monitored Number of running sessions and tasks to be monitored Number of concurrent running sessions and tasks to be supported Amount of session and task data to be retained Consider these factors, along with the specifications listed in Selecting the hosts on page 5, to help plan your installation. Check the following items before you install Platform Analytics: Make sure that the Analytics installation package that you downloaded matches the operating system and the system architecture on which you intend to install it. Copyright IBM Corp

20 Verify that you can ping the database hosts from the Analytics node hosts, Analytics serer host, and Analytics reporting serer host. Verify that the Analytics node hosts can ping the Analytics serer host, and ice ersa. Make sure that the Analytics serer host and Analytics reporting serer host meet the hardware configuration requirements. If you plan to install both on the same system, make sure your hardware supports and withstands both configurations. Verify that you hae enough memory and disk space for each host. 10 Installing Platform Analytics for Symphony

21 Chapter 4. Installing Platform Analytics Installing Database After preparing your hardware, you can install the Analytics database, the Analytics serer, and the Analytics node. Then, reiew the items on the post-installation checklist. The intended database host (or hosts in the cluster) must meet the Platform Analytics and Vertica system requirements. Analytics database checklist Note: Obtain Vertica and Tableau keys from by proiding your name, your ID, Platform Analytics ersion (for example, 9.1.2), Platform Analytics edition (For example, Standard Ed), and date of purchase. Manually check the following items for the Analytics database hosts in the cluster: Verify that the operating system type and ersion of the hosts meet the Vertica requirements. All hosts in the database cluster must be running the same operating system type and ersion. Verify that the hosts default shell for root and current user is BASH. Ensure that the hosts hae at least 1 GB of RAM per logical processor. Ensure that the hosts hae at least 2 GB of swap space. Ensure that the disk read-ahead is at least 2048 sectors. Verify that the configured data and catalog directories are created on all cluster hosts. Verify the Python ersion; only ersion 2.x, higher than 2.3.4, is supported. Verify the ssh access configuration. Verify that NTP is running on startup. Verify that the SELinux is disabled or set it to permissie mode. Verify that the Transparent Hugepage is set to madise or disabled. Verify that the I/O scheduler is set to deadline or noop. Verify that the CPU frequency scaling is disabled. Verify that CPU frequency scaling must be disabled. Define the loopback address. Ensure that port 5433 is not in use and that /de/pts is mounted. Manually check the following items as described in the Vertica Analytic Database documentation, Installation and Configuration Guide before you install the database: Make sure that you follow the security setting that is required for the Analytics database installation, as described in the Vertica documentation. Make a note of disk storage locations. Make note of IP addresses of the hosts in the database cluster. If you are using a host with multiple network interfaces, use the IP address that is assigned to the NIC connected to the other cluster hosts, not the NIC that is used for client connections. Copyright IBM Corp

22 Dynamically assigned IP addresses are not supported. Subnet Masks must be the same for all hosts. Set the host locale (Language). Set the default time zone. Remoe nonessential applications. Disable firewall. Optionally, run Spread on a separate control network. Back up any existing database. Proide root SSH access to all the cluster hosts. Installing the Analytics database The Analytics database, which consists of one or more database hosts, contains the cluster operations data for reporting and analysis. You must install and configure the Analytics database before you install Platform Analytics. You can install the Analytics database on a single host or on a cluster of multiple hosts. Installing the database on multiple hosts improes the performance and reliability of your database. Before you begin Important: Make sure you hae reiewed and satisfied the installation requirements in Pre-installation checklist on page 9. For details about installing the database, see the Vertica documentation, Installation and Configuration Guide. Follow the steps that are described in the Before You Install and Installing Vertica chapters. Procedure 1. Log in to the intended database host (or hosts in the cluster) as root. 2. Extract the installation package to a shared directory that all the cluster hosts can access. 3. Edit the install.config file and configure all required parameters. You must configure all the required parameters in the install.config file. To configure any required or optional parameter, uncomment the line and specify the appropriate alue. 4. Run the database installation script:./analyticsverticainstaller.sh -f install.config Note: When you configure DB_DATA_PATH, the installer sets owner and group of the folder to DBA_USER. So it is not recommended to configure DB_DATA_PATH to folder such as /opt, otherwise, the permissions, owner, group of this folder will be changed. The installer performs the following steps: a. Initializes configurations for the installation b. Installs/repairs SSH keys for the root account on the cluster hosts c. Checks prerequisites on the cluster hosts Note: If there are any errors in the preious three steps, then an install.log file is generated in the installation folder. Fix the errors and rerun the installation script. 12 Installing Platform Analytics for Symphony

23 d. Installs and configures the Analytics database e. Creates the database connection for Platform Analytics Note: As part of the preious step, the database installation script creates a new user for the Vertica database administrator. If the user already exists, the script changes the password of the database administrator to the one specified by DBA_PASSWORD in the install.config file. This change is done to ensure that the password used on a cluster of multiple hosts is uniform across the hosts. f. Deploys the Platform Analytics database schema Note: If there are any errors in the preious three steps, then an install.log file is generated in the installation folder. Fix the errors, then complete the following steps: 1) Delete the /opt/ertica directory, and the files and directories under your DB_DATA_PATH and DB_CATALOG_PATH paths. 2) Rerun the database installation script. What to do next If you must update any of the parameters in the database install.config file, see the description of the dbconfig command in Administering Platform Analytics for Symphony. Installing Platform Analytics Serer The intended serer host must meet the Platform Analytics system requirements. Analytics serer checklist Note: Obtain Vertica and Tableau keys from pckeys@ca.ibm.com by proiding your name, your ID, Platform Analytics ersion (for example, 9.1.2), Platform Analytics edition (For example, Standard Ed), and date of purchase. Manually check the following items: The Analytics serer meets the detailed system and software requirements. The Analytics serer s operating system can handle daylight saings time correctly. Remoed any preious installations of Platform Analytics from your host. The required ports for Platform Analytics and database hosts are free. If a firewall exists, all these ports must be open in the firewall. All the required ports are TCP. The Analytics database host is properly configured and running. The Analytics serer has access to the Analytics database JDBC drier. Installing the Analytics serer Perform this task to install the Platform Analytics serer on a host. Before you begin Important: Make sure you hae reiewed and satisfied the installation requirements in Pre-installation checklist on page 9. Chapter 4. Installing Platform Analytics 13

24 Procedure 1. Install and configure Tableau Serer. Make sure that the Tableau Serer (tabsc) serice has started. Note: You will find a separate installer for Tableau Serer in the installation package. Refer to the Tableau Serer documentation if you need more installation details. If you do not hae internet and if you want to actiate Tableau Serer offline, follow the Tableau Serer steps in this link: 2. Log in to the intended Platform Analytics serer as administrator. 3. Extract the Platform Analytics serer package and edit the install.config file. Important: Configure all the required parameters in the install.config file. To configure any required or optional parameter, uncomment the line and specify the appropriate alue. 4. Naigate to the top-leel installation directory and run the Platform Analytics serer installation package: Note: Make sure you hae administrator priileges before running this batch file. AnalyticsSererInstaller.bat -f install.config Note: You can receie notifications of eents ia . This means you will be made aware of potential problems in your cluster without haing to constantly monitor the Platform Analytics Console. After enabling notifications, specify the SMTP mail serer and the intended recipient of the notifications. The intended sender is the account that is used to send the notifications. 5. Verify that the pats serice has started: Windows: ANALYTICS_TOP\bin\perfadmin list Installing Platform Analytics Node The intended node host (or hosts in the cluster) must meet the Platform Analytics system requirements. Analytics node checklist Manually check the following items: The Analytics node host meets the detailed system and software requirements. The Analytics node host operating system can handle daylight saings time correctly. The Analytics node must run on a management host in each Platform Symphony cluster from which you want to collect data. The required port for the Platform Analytics hosts is free. If a firewall exists, this TCP port must be open in the firewall. The Analytics database host is properly configured and running. The Analytics node host has access to the Analytics database JDBC drier. 14 Installing Platform Analytics for Symphony

25 Installing the Analytics node Install the Platform Analytics node package on a management host. You must hae at least one Analytics node host in each cluster that Platform Analytics will handle. Before you begin Important: Make sure you hae reiewed and satisfied the installation requirements in Pre-installation checklist on page 9. You can install the Analytics node in a Symphony cluster, either with or without failoer support. For failoer support, you must install the Analytics node on the Platform Symphony master host and on one or more management hosts. You can choose to run the Analytics node on a non-master management host to aoid increasing the load on the master host. Without failoer support, you can install the Analytics node on the Platform Symphony master host or a non-master management host. To aoid increasing the load on the master host, install the Analytics node on a non-master management host. The Symphony shared directory must already exist and be set up according to the instructions in the Platform Symphony installation documentation. You can use this command to configure the shared directory: egoconfig mghost SHARED_TOP Installing the Analytics node with failoer support Follow this procedure to install the Analytics node in a Platform Symphony cluster with failoer support. This requires you to install the Analytics node on the Symphony master host and on one or more management hosts in the cluster. Procedure 1. Log in to the Platform Symphony master host. 2. Extract the Analytics node package, edit the install.config file, and configure all required parameters. You must configure all the required parameters in the install.config file. To configure any required or optional parameter, uncomment the line and specify the appropriate alue. Note: For failoer to work successfully, you must configure and install the Analytics node in the exact same path location on each management host. 3. Run the Analytics node installation script: On UNIX nodes:./analyticsnodeinstaller.sh -f install.config Or, for silent installation:./analyticsnodeinstaller.sh -f install.config -silent On Windows nodes: AnalyticsNodeInstaller.bat -f install.config Or, for silent installation: AnalyticsNodeInstaller.bat -f install.config -silent 4. Run paconfig on the master host to moe the Analytics configuration and work directories to the SHARED_TOP Symphony shared directory. UNIX: paconfig mghost pa -f Chapter 4. Installing Platform Analytics 15

26 Windows: paconfig mghost pa username password -f 5. Repeat step 3 to install the Analytics node on one or more other management hosts in the cluster. Note: If you want to configure the Analytics node (for instance, running dbconfig) on another management host other than the master, first run the following command on that host: paconfig mghost pa 6. Log in to the Platform Management Console and run the post-installation action to register Platform Analytics as an EGO serice. To run the post-installation action, after installing Platform Symphony and naigating to the Symphony GUI, follow the instructions in the Cluster Configuration pop-up window. This window appears when you enter your user name and password (for example, Admin/Admin). Note: Ensure that you enable the pop-up window function in your browser. 7. For Analytics nodes on UNIX hosts, source the Platform Symphony enironment. For csh or tcsh: source SOAM_TOP/cshrc.platform For sh, ksh, or bash:. SOAM_TOP/profile.platform 8. For Analytics nodes on Windows hosts, run the Symphony Command Prompt from the Windows Start menu. 9. Verify that the data loaders are running: egosh serice iew alc Analytics loader controller (alc) is the data loader controller. 10. Verify that there are no errors in any of the data loader log files. The data loader log files are located in ANALYTICS_TOP/log/dataloader. What to do next During normal operations, consider running the Analytics node on a non-master management host to aoid increasing the load on the master host. Installing the Analytics node without failoer support Follow this procedure to install the Analytics node on a Platform Symphony management host without failoer support. Procedure 1. Log in to the intended Analytics node host. Normally, this should be a Symphony management host other than the master host. 2. Extract the Analytics node package, edit the install.config file, and configure all required parameters. You must configure all the required parameters in the install.config file. To configure any required or optional parameter, uncomment the line and specify the appropriate alue. 3. Run the Analytics node installation script: On UNIX nodes:./analyticsnodeinstaller.sh -f install.config Or, for silent installation: 16 Installing Platform Analytics for Symphony./AnalyticsNodeInstaller.sh -f install.config -silent

27 On Windows nodes: AnalyticsNodeInstaller.bat -f install.config Or, for silent installation: AnalyticsNodeInstaller.bat -f install.config -silent 4. If you are installing the Analytics node on a non-master management host, on the local management node, copy the SOAM_TOP/gui/conf/post_install/ analytics_serice.xml and SOAM_TOP/gui/conf/post_install/ Register_serices_PA.xml files to the SHARED_TOP/gui/conf/post_install directory. (Skip this step if you are installing the Analytics node on the master host.) 5. If you are installing the Analytics node on a non-master management host, locate the following line in the analytics_serice.xml file and modify it, as shown: from: <ego:resourcerequirement>select( X86_64 )</ego:resourcerequirement> to: <ego:resourcerequirement>select(host_name)</ego:resourcerequirement> where HOST_NAME is the machine name on which the Analytics node is installed. (Skip this step if you are installing the Analytics node on the master host.) 6. Log in to the Platform Management Console and run the post-installation action to register Platform Analytics as an EGO serice. 7. For Analytics nodes on UNIX hosts, source the Platform Symphony enironment. For csh or tcsh: source SOAM_TOP/cshrc.platform For sh, ksh, or bash:. SOAM_TOP/profile.platform 8. For Analytics nodes on Windows hosts, run the Symphony Command Prompt from the Windows Start menu. 9. Verify that the data loaders are running: egosh serice iew alc Analytics loader controller (alc) is the data loader controller. 10. Verify that there are no errors in any of the data loader log files. The data loader log files are located in: ANALYTICS_TOP/log/dataloader. UNIX: ANALYTICS_TOP/log/dataloader Windows: ANALYTICS_TOP\log\dataloader Verifying that Platform Analytics is up and running After installation, erify that Platform Analytics is installed successfully and working properly. Use the following checklists to erify each part of your Platform Analytics installation. Verifying the Analytics database Ensure that the nodes are up and running. Chapter 4. Installing Platform Analytics 17

28 Verify that you can create a database user for the creation of Platform Analytics schema. Make sure that the K_SAFE parameter in the create schema file is set to the correct alue. Use the following command to check the alue of the K_SAFE parameter: SELECT current_fault_tolerance FROM system; Ensure that the network bandwidth utilization is set properly. Verifying the Analytics node Start the Analytics node after you start the Platform Analytics serer. Wait for 10 minutes after you install the Analytics node and then check the data loader log files to make sure data has been written and there are no issues for each node. Verify that the database is receiing data. If you hae configured remote data loading, then check the log file to make sure data are written correctly. If you plan to upgrade Platform Symphony after installing Platform Analytics: You must either change the alue of the SOAM_VERSION parameter in the perf.conf file to match the new Symphony ersion, or reinstall the Analytics node after upgrading Symphony. If you installed the Analytics node on a Windows host, you must also update the alue of the SOAM_VERSION enironment ariable in the PA_TOP/conf/seten.bat file. For example, if you upgraded to Platform Symphony 6.1.1, change the following line in the seten.bat file: set SOAM_VERSION=6.1.1 If you upgrade to Platform Symphony after installing Platform Analytics, add the following line to the ANALYTICS_TOP/conf/plc_pa_ego.xml file to enable the new egoconsumergrouploader data loader (or, if the line exists, make sure it is set to Enable="true"): <DataLoader Name="egoconsumergrouploader" Interal="300" Enable="true" LoadXML="dataloader/egoconsumergrouploader.xml" /> Verifying the Analytics serer Verify that you can connect to the Analytics database. When the serer runs two data transformers, check the log files. Also log on to the Analytics database to erify that aggregate_info has the proper date and proper tables updated. Note: In AGGREGATE_INFO the NEXT_BEGIN_AGG_TIME is in GMT. Verify that the report table contains data: select count(*) from rpt_<data transformer name>_raw; where <data transformer name> can be, for instance, res_alloc_workload_stats. After you install the Analytics serer and Analytics node, wait two hours and then check the Cluster tab to see if all hosts are added. Make sure you enable eent notification during the Analytics serer installation and start the serer before you start the Analytics node. Check the eent_manager_conf table to make sure that your eent manager is set to actie: eent_manager_conf.event_mgr_active = Y Verify that notification is set up correctly. To specify multiple addresses, enter multiple addresses separated by a semi-colon (;). 18 Installing Platform Analytics for Symphony

29 Verifying Tableau Serer Verify that you can actiate the serer. If offline actiation is required, then proceed with the on-screen instructions. If you are not using port 80 during the install configuration, write down the port number. Make sure you remember the Administrator user name and password. When you log in as Administrator, make sure you select Embedded Credentials on the Maintenance page. Verify that the tableau serice is up and running on the Maintenance page. Verify that the window serice for the Tableau Serer is set to Automatic and has started. Verifying the Analytics reporting serer Verify that you hae extracted the reports package on the Tableau Serer. Verify that the deployment is successful and the workbooks are under the projects folder. Make sure that the parb serice starts from Windows serices console. Chapter 4. Installing Platform Analytics 19

30 20 Installing Platform Analytics for Symphony

31 Chapter 5. Configuring and optimizing Platform Analytics After you install Platform Analytics, you can erify and configure the Analytics serer, configure the Analytics node, and optimize the Analytics serer, node, and database. Verifying and configuring the Analytics serer Use the IBM Platform Analytics Console to erify and configure the Analytics serer. Procedure 1. Log in to the Analytics serer host. 2. Launch the Platform Analytics Console. Windows: Start > All Programs > >IBM Corporation > Analytics Serer > Analytics Console 3. Click Data Collection Node in the naigation tree and erify that the node is running correctly. To iew the data loader properties, right-click each loader controller instance and select Loader Properties. 4. Click Scheduled Tasks in the naigation tree and modify the times that the scheduled tasks are running, if necessary. 5. Click Eents in the naigation tree and erify that there are no ERROR or FATAL eents. 6. Verify the notification settings. While in Eents, click Action > Notification to open the Eent Notification dialog. Enabling and configuring the remoting serer (asynchronous data loading mode only) If you intend to use asynchronous data loading mode, perform this task to enable and configure the remoting serer. About this task You should only use the asynchronous data loading mode for sending data from the Analytics node to the database oer a slow or unstable network. Normally, data loaders perform synchronous data loading, whereby they load data directly into the Analytics database. In rare cases where the network connection between the Analytics node and the database host is poor, the data loaders will perform asynchronous data loading. In such cases, the data loaders send data to the Analytics serer, and the serer then loads the data into the Analytics database. Procedure 1. Naigate to the ANALYTICS_TOP/conf/ directory. 2. Rename the remotingserer.tmpl file to remotingserer.xml. 3. Edit the remotingserer.xml file and change the IP address to the IP address of the Analytics serer host. Copyright IBM Corp

32 4. Edit the log4j.properties file and uncomment the RemotingSerer line. 5. Rename the wsm/pars.tmpl file to wsm/pars.conf. 6. Start the remoting serer: perfadmin start pars 7. If you are on a Windows host and want the remoting serer to start automatically when Windows starts, change the startup type of the pars Window serice from Manual to Automatic. Configuring the Analytics node You can perform the following tasks to configure the Analytics node to work more efficiently with your cluster. Stopping redundant PERF serices Enabling and configuring the remoting client (asynchronous data loading mode only) on page 23 Stopping redundant PERF serices Platform Analytics runs its own PERF serices (known as the ALC serice) independent of the cluster. Since Platform Symphony clusters also hae PERF serices running, you should stop the Symphony PERF serices to aoid unnecessary redundancy in your cluster. Procedure 1. Log in to any host in the Symphony cluster: egosh user logon 2. If you logged in to a UNIX host, source the Platform Symphony enironment. For csh or tcsh: source SOAM_TOP/cshrc.platform For sh, ksh, or bash:. SOAM_TOP/profile.platform 22 Installing Platform Analytics for Symphony 3. If you logged in to a Windows host, run the Platform Symphony command prompt from the Start menu. 4. Stop the loader controller (plc), data purger (purger), and the PERF Derby database (derbydb) serices: egosh serice stop plc egosh serice stop purger egosh serice stop derbydb 5. Rename the plc_serice.xml loader controller configuration file to another file extension to remoe it from the list of serices. Important: Be sure not to use a file extension of.xml. For example: Rename EGO_TOP/eserice/esc/conf/serices/plc_serice.xml to EGO_TOP/eserice/esc/conf/serices/plc_serice.xml.bak. If EGO uses a shared directory, rename SHARED_TOP/eserice/esc/conf/ serices/plc_serice.xml to SHARED_TOP/eserice/esc/conf/serices/ plc_serice.xml.bak. 6. Similarly, rename the purger_serice.xml data purger configuration file and the derby_serice.xml Derby database configuration file to another file extension to remoe them from the list of serices. 7. Restart EGO to actiate these changes:

33 egosh ego restart Enabling and configuring the remoting client (asynchronous data loading mode only) If you intend to use the asynchronous data loading mode, perform this task to enable and configure the remoting client. About this task You should only use the asynchronous data loading mode for sending data from the Analytics node to the database oer a slow or unstable network. Normally, data loaders perform synchronous data loading, whereby they load data directly into the Analytics database. In rare cases where the network connection between the Analytics node and the database host is poor, the data loaders will perform asynchronous data loading. In such cases, the data loaders send data to the Analytics serer, and the serer then loads the data into the Analytics database. Procedure 1. Log in to the Analytics node host. 2. Naigate to the ANALYTICS_TOP/conf directory. 3. Rename the remotingclient.tmp file to remotingclient.xml. 4. Edit the remotingclient.xml file and change the sererbindaddress and sererbindport parameters according to the remoting serer configuration. 5. Edit the perf.conf file and add the following parameters: ASYNC_LOADING_ENABLED=Y ASYNC_LOADING_MODE=Remoting 6. Restart the loader controller serice (alc). egosh serice stop alc egosh serice start alc Optimizing the Analytics serer Note: If you hae to restart plc, then wait seeral seconds until the STATUS show "STOPPED" before you run the command perfadmin start plc. You can perform the following tasks to modify the Analytics serer to enhance performance. About this task The following tasks are optional. Changing the data retention period You can perform this task to change the data retention period. About this task A long data retention period can hae a significant impact on performance and the data olume. You can tailor the data retention period according to your business requirements to maximize the performance of your Analytics serer. Chapter 5. Configuring and optimizing Platform Analytics 23

34 The data purger consists of multiple scheduled tasks (PartitionMaintenanceGroup*), which are enabled by default. Procedure 1. Launch the sql command line. a. Naigate to the bin subdirectory of the database installation directory. By default, this is /opt/ertica/bin. b. Run sql to connect to the database:./sql -d database_name -p port -U username -w password where: database_name is the name of the database port is the TCP port number or the local socket file extension in which the serer is listening for connections. The default is port number username is the name of the user with which to connect to the database, instead of the default user (the database administrator). password is the password for the database user. Note: As part of installation, the database script creates a new user for the Vertica database administrator. If the user already exists, the password of the database administrator is changed to the one specified by DBA_PASSWORD in the install.config file. This change is done to ensure that the password used on a cluster of multiple hosts is uniform across the hosts. Alternately, you can run sql with no options to accept the defaults and specify the administrator password at the prompt. 2. Examine the current data retention periods of the database tables for Platform Analytics. To examine the retention periods for all Analytics database tables, run the following from the sql command line: SELECT TABLE_NAME, DATA_DAYS_RANGE FROM SYS_TABLES_TO_PARTITION; To examine the retention periods for a specific database table, run the following from the sql command line: SELECT TABLE_NAME, DATA_DAYS_RANGE FROM SYS_TABLES_TO_PARTITION WHERE TABLE_NAME= table_name ; where table_name is the name of the table you want to examine. The output displays the name of the table and the corresponding data retention period in days. For example, to iew the data retention period for the RESOURCE_METRICS_BUILTIN table, run the following from the sql command line: SELECT TABLE_NAME, DATA_DAYS_RANGE FROM SYS_TABLES_TO_PARTITION WHERE TABLE_NAME= RESOURCE_METRICS_BUILTIN ; 3. Change the data retention period for the appropriate database tables. a. For each database table to change, run the following from the sql command line: UPDATE SYS_TABLES_TO_PARTITION SET DATA_DAYS_RANGE= retention_period WHERE TABLE_NAME='table_name'; where: 24 Installing Platform Analytics for Symphony

35 retention_period is the new retention period, in days table_name is the name of the table you are changing b. Commit the changes to the database. Run the following from the sql command line: COMMIT; Optimizing the Analytics node For example, to change the data retention period of the RESOURCE_METRICS_BUILTIN table to 2192 days, run the following from the sql command line: UPDATE SYS_TABLES_TO_PARTITION SET DATA_DAYS_RANGE= 2192 WHERE TABLE_NAME= RESOURCE_METRICS_BUILTIN ; COMMIT; You can perform the following optional tasks to enhance the performance of the Analytics node. Increasing JVM memory Distributing the Analytics node workload Increasing JVM memory You can perform the following task to increase the amount of memory for the Jaa Virtual Machine (JVM). About this task If you experience a problem with the JVM running out of memory, you can increase the JVM memory to at least 2 GB for the Analytics node, instead of using the default alue. Procedure 1. Log in to the Analytics node host. 2. Edit the ANALYTICS_TOP/1.2/etc/plc.sh file. 3. Naigate to the following line (toward the bottom of the file): $JAVA_HOME/bin/jaa -Xms64m -Xmx1600m -cp ${LCP} ${solarisflag} \ and change the -Xmx1600m parameter to -Xmx2048m. For example: $JAVA_HOME/bin/jaa -Xms64m -Xmx2048m -cp ${LCP} ${solarisflag} \ Distributing the Analytics node workload You can improe performance by distributing the Analytics node workload among multiple hosts or multiple loader controllers within a host so that each host or loader controller is responsible for a specific type (or types) of data loading. About this task Based on the type of data, you can categorize the data loaders into two different types, and enable each node or loader controller to be responsible for only one type of data loader. Table 10 on page 26 describes the two broad data loader categories and their corresponding loader controller configuration files. Chapter 5. Configuring and optimizing Platform Analytics 25