Installing the ClientHandler Software Package - Data Stream Architecture - Data Stream Utility

Data Stream Utility Installation, Configuration, and Upgrade Guide for Customers

Product
Data Stream Architecture
Data Stream Utility
Release Number
16.10
Published
August 2017
Language
English (United States)
Last Update
2018-04-17
dita:mapPath
vir1487616382457.ditamap
dita:ditavalPath
3153_DSU_ICUCustomer_1610.ditaval.ditaval
dita:id
B035-3153
lifecycle
previous
Product Category
Software
Teradata Tools and Utilities
DSC, ClientHandler, BARCmdline, and BARPortlets must be on the same version.
Important:

Make sure the DSC is up and running before installing ClientHandler.

Beginning with DSA release 16.10, the BARNC process queries the broker (ActiveMQ) for the existing DSC instances pointing to the broker. If the DSC is not running, autodiscovery fails.

DSA Package Installation Directory Notes
ClientHandler base_dir/teradata/client/version/dsa You can specify the directory as base_dir.
Do not use / or /usr as the installation directory. The permissions for the specified directory are modified so that the service user can access the directory.
  1. Verify that the DSC is up and running.
  2. On the BAR server, unzip and extract the script rpm file:
    tar zxvf clienthandler_linux_arch.xx.xx.xx.xx-######.tar.gz
    linux is the OS, arch is the architecture, xx.xx.xx.xx is the version number, and ###### is a unique number.
    A directory with the format clienthandler.xx.xx.xx.xx is extracted in the current working directory.
  3. Run the installation script from the extracted directory, where arch is the architecture, xx.xx.xx.xx is the version number, and ###### is a unique number. ./clienthandler_install.sh -r clienthandler-xx.xx.xx.xx-######.
  4. Enter values for ClientHandler. If you are doing an upgrade, the previous settings are displayed and can be changed, if desired. The following table displays prompts in the order in which they are received.
    ClientHandler Prompts Description and Default Values
    ActiveMQ Broker Host Name and Port Hostname or IP address of the machine running the ActiveMQ broker and port number on the server where the ActiveMQ broker is listening. Default: localhost: 61616
    ActiveMQ Connection Type of ActiveMQ connection (tcp or ssl). Default: tcp
    Filepath of SSL truststore If you are using SSL, enter filepath of the SSL truststore file. There is no default value.
    Filepath of SSL keystore If you are using SSL, enter filepath of the SSL keystore file. There is no default value.
    SSL Keystore Password If you are using SSL, enter the value for the client's keystore password in clear text. There is no default value.
    Server ID Unique Server ID for this ClientHandler. The hostname of the server is recommended, however the name should not include hyphens. There is no default value.
    CBB File Path The Web Service master uses this path, which is a shared directory required for Change Block Backup (CBB) temporary file storage during restore operations.
    Is Master Server? Indicates whether this server is the Web Service master server used in incremental job communication.
    All media servers defined in the target group for a Changed Block Backup (CBB) restore job must have the same Web Service master server, or the restore job will fail.
    Master Server's Hostname The host name of the Web Service master server used in incremental job communication. This prompt appears only if you respond No to the "Is Master Server?" prompt.
    Account for running ClientHandler Username to set up an account for running the DSA ClientHandler. Applicable to an install only, not an upgrade. Default: dscuser.
    UserId Userid of the dscuser, and is applicable only for NFS mounted storage targets. This id must match the anonuid configured in the NFS server. The userid must also be the same across all DSA components and servers in the environment. Applicable to an install only, not an upgrade.