16.10 - Installing the BARCmdline Software Package - Data Stream Extensions

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

Data Stream Architecture
Data Stream Extensions
August 2017

DSC, ClientHandler, BARCmdline, and BARPortlets must be on the same version.

DSA Package Installation Directory Notes

(DSA Command-Line Interface)

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. On the BAR server, unzip and extract the script rpm file:
    tar zxvf BARCmdline_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 BARCmdline.xx.xx.xx.xx is extracted in the current working directory.
  2. 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.
    ./dscinstall -r BARCmdline-xx.xx.xx.xx-######.arch.rpm
  3. Enter values for the BAR command-line interface. If you upgrading, the previous settings are displayed and can be changed. The following table displays prompts in the order they are received.
    BAR Command-Line Prompts Description and Default Values
    ActiveMQ Broker URL Hostname or IP address of the machine running the ActiveMQ broker. Default: localhost
    ActiveMQ Broker Port Port number on the server where the JMS broker is listening (61616 for tcp, 61617 for ssl). Default: 61616
    ActiveMQ Connection Type of ActiveMQ connection (tcp or ssl). Default: tcp
    Java path If this is a generic SLES installation, enter the path to Java. No default.
    DSC Name The DSC name that the BAR command-line interface connects to.