Prepare to Install the Data Aggregator

To ensure that your Data Aggregator installation is successful, complete the requirements before you install Data Aggregator:
capm360
HID_Prepare_to_Install_the_Data_Aggregator
To ensure that your Data Aggregator installation is successful, complete the requirements before you install Data Aggregator:
 
 
Verify the Prerequisites
Meet the following prerequisites before installing Data Aggregator:
  • Verify that Data Repository installation is complete and the service is running.
  • Verify that port numbers 8581, 61616, 61618, 61620, and 61622 are open on the Data Aggregator system. Remote access is required to these ports.
     Throughout the documentation 8182, 8382, 61617, 61619, 61621, and 61623 appear as suggested port numbers for secured communications. In the instances where these ports appear, you are free to use any value you want as long as no other processes are using it. You can change port 616xx to another port after you install the Data Aggregator. For more information, see Complete the Post-Installation Configuration.
  • Verify that ports 1099 and 11099 are blocked from external access.
    These ports must remain open locally for internal communication.
  • Verify that Security Enhanced Linux (SELinux) is disabled or permissive on the computer where you are going to install Data Aggregator. By default, some Linux distributions have this feature enabled, which does not allow Data Aggregator to function properly. Disable SELinux, set to permissive, or create a policy to exclude Data Aggregator processes from SELinux restrictions. If you would like Security Enhanced Linux (SELinux) to be enforcing, consult the Red Hat documentation.
     For information about configuring an SELinux security policy, see the Red Hat documentation.
  • To avoid potential corruption of data, exclude the installation directory, the backup directory, and all subdirectories, from antivirus scans. Prevent scanning by a local instance of an antivirus client and scanning by a remote antivirus instance. For more information about Data Aggregator backups, see Back Up Data Aggregator.
  • Verify that the directory where you are going to install has write privileges for your Data Aggregator user.
  • The installer requires the zip and unzip packages. If these packages are not installed, use one of the following commands to install them:
    yum -y install zip unzip
     
    SLES:
     
    zypper –y install zip unzip
  • For a fault tolerant environment, verify that proxy server is installed. For more information, see Fault Tolerance and Install or Uninstall the Proxy Server.
(Optional) Configure the Sudo User Account for Data Aggregator
If you do not have root access to install and run the Data Aggregator, configure the sudo user account.
 
Follow these steps:
 
  1. Locate the following file on the Data Aggregator host:
    /etc/sudoers
     
  2. Add one of the following command aliases with the following permissions to the file:
    Cmnd_Alias CA_DATAAGG = /tmp/installDA.bin,/sbin/service dadaemon *,/opt/IMDataAggregator/Uninstall/Uninstall, /opt/IMDataAggregator/RemoteEngineer/re.sh
    ## Allows the Data Aggregator user to manage the Data Aggregator
    sudouser
    ALL = CA_DATAAGG
    •  
       
      sudouser
       
      Specify the user who can run the sudo commands.
    This command alias details the commands that the sudo user must be able to run.
    SLES:
     
    Cmnd_Alias CA_DATAAGG = /tmp/installDA.bin,/usr/sbin/service dadaemon *,/usr/sbin/service activemq *,/opt/IMDataAggregator/Uninstall/Uninstall, /opt/IMDataAggregator/RemoteEngineer/re.sh
    ## Allows the Data Aggregator user to manage the Data Aggregator
    dasudouser_name ALL = CA_DATAAGG
    •  
       
      sudouser
       
      Specify the user who can run the sudo commands.
    This command alias details the commands that the sudo user must be able to run.
  3. With the sudo user configured, add the sudo prefix to all commands to install the Data Aggregator.
    Example:
     
    sudo ./installDA.bin
Configure the Limit on the Number of Open Files on Data Aggregator
Verify that the user that is installing Data Aggregator has a limit of at least 65536 on the number of open files. Set this value permanently.
 
Follow these steps:
 
  1. As the root user or a sudo user, log in to the Data Aggregator host.  
  2. Change the ulimit for the open files limit to at least 65536:
    ulimit -n
    ulimit_number
    For example:
    ulimit -n 65536
  3. Open the following file:
    /etc/security/limits.conf
     
  4. Add the following lines:
    # Added by Data Aggregator
    * soft nofile 65536
    # Added by Data Aggregator
    * hard nofile 65536
     Restart Data Aggregator for these changes to take effect. If you are upgrading, the upgrade process automatically restarts Data Aggregator.
  5. Verify that the number of open files is set properly:
    ulimit -n
    The command returns the limit that you specified earlier.
Configure UTF-8 Support
Configure the Data Aggregator host to support UTF-8 encoding. If UTF-8 encoding is not enabled, characters might not display properly during the installation.
The appropriate language packs are also required to support localized deployments.
 Some scripts that are used in the installation of selected components are not localized and run in English. For more information, see Language Support.
 
Follow these steps:
 
  1. Do one of the following steps:
    1. Type the following command from a Korn or bash shell:
      export LANG=LANG_value ; export LC_ALL=$LANG
      •  
        LANG_value
         specifies the value of the language you want the product to support. The following variables are supported:
        English:
         
        en_US.utf8
        French: 
         
        fr_FR.utf8
        Japanese
        ja_JP.utf8
        Simplified Chinese:
         
        zh_CN.utf8
        Traditional Chinese: 
         
        zh_TW.utf8
         
      For example:
      export LANG=zh_TW.utf8 ; export LC_ALL=$LANG
    2. Type the following command from a Bourne shell:
      LANG=
      LANG_value
      ; export LANG
      LC_ALL=
      LANG_value
      ; export LC_ALL
      For example:
      LANG=zh_CN ; export LANG
      LC_ALL=zh_CN ; export LC_ALL
    The language variable is set.