Customizing Values Used in PUT Installation - Data Stream Architecture - Data Stream Extensions

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

Product
Data Stream Architecture
Data Stream Extensions
Release Number
16.00
Published
November 2016
Language
English (United States)
Last Update
2018-04-17
dita:mapPath
rte1474305422984.ditamap
dita:ditavalPath
3151_DSE_ICUCustomer_1600.ditaval.ditaval
dita:id
B035-3151
lifecycle
previous
Product Category
Software
Teradata Tools and Utilities
An inputs file for the configuration of the DSA components being installed is required before you can install DSA components with PUT. Each DSA server needs its own inputs file, customized specifically for that server. The file contains all the input values required for all the DSA components being installed on that server. The values will be different from server to server.

The following table lists the different variables required by each DSA installation package.

  1. Create a dsainputs file under the /tmp directory on the system where the DSA packages will be installed.
    Keep the dsainputs file in a secure location. The dsainputs file that is placed in /tmp cannot be used by subsequent installation or upgrade processes.
  2. Insert the following parameters for the component you are installing and the values you want to assign to the parameters. Values should be specific for that server. For example, type: BURL=localhost
    Parameter Component Description
    BARSIZE DSC The size of the BAR database that holds the repository. Acceptable values are 1 GB to 800 GB.
    BROKERLIST ClientHandler List of broker:port pairs separated by a comma. For example:

    localhost:61616, dsasrv1:61616

    BURL DSC, ClientHandler, BAR Command Line Hostname or IP address of the machine running the JMS broker (ActiveMQ). If the broker is running on the DSC server, the parameter should be localhost.
    BPORT DSC, ClientHandler, BAR Command Line Port number of the machine where the JMS broker is listening. Default is 61616.
    CONNECTION DSC, ClientHandler, BAR Command Line, BARPortlets Type of connection the JMS message broker uses. Acceptable values are tcp or ssl.
    DSCNAME DSC, BAR Command Line Unique name for the DSC server.
    CBBFILEPATH ClientHandler The path needed for Change Block Backup temporary file storage.
    DBSHOST DSC TDPID of the Teradata Repository used to store the DSC repository.
    DSCREPBACKUPSYSIP DSC IP address of the DBSHOST. Used for backup repository configuration.
    DBSUSERNAME DSC Teradata Database user used for administration purposes and repository jobs. This user must have the ability to create tables under BAR and BARBACKUP databases.
    DBSPASSWORD DSC Password for DBSUSERNAME.
    SUPERUSERNAME DSC Teradata Database user used to create the DSC repository.
    SUPERUSERPASSWORD DSC Password for SUPERUSERNAME.
    DSCUSER DSC, ClientHandler Username to set up an account for running the DSA services.
    BACKUPAPPCLIENTNAME AXMNetbackup The name of this media server in the third party application. In NetBackup, this is the client name.
    ISMASTER ClientHandler Specify yes or no on whether this server is the Web Service master server used in incremental job communication.
    MASTERHOSTNAME ClientHandler Specify the host name of the Web Service master server used in incremental job communication.
    USERID DSC, ClientHandler The user id of dscuser. Must be the same across all DSA client components and servers in the environment.
    VIEWPOINTURL DSC Hostname or IP address of the Viewpoint server.
    VIEWPOINTPORT DSC Port number of the Viewpoint server.
    VIEWPOINTTYPE DSC Type of connection used. Acceptable values are http or https.
    CAMPRIMARYURL DSC Hostname or IP address of primary CAM system, which enables alert messaging
    CAMPRIMARYPORT DSC CAM port number of primary CAM system. Default is 61616.
    CAMCLUSTERENABLED DSC Flag for enabling CAM clustering
    CAMCLUSTERURL DSC Hostname or IP address of primary and failover CAM systems, which enable alert messaging
    CAMCLUSTERPORT DSC CAM port number for clustered environment. This has the same value as CAMPRIMARYPORT. Default is 61616.
    DSARESTPORT DSC Port number for DSARest Web Service running on DSC server. Default is 9090.
    OPPASSWORD DSC Password for the DSC repository user. Used for Create, Read, Update and Delete (CRUD) operations on BAR.
    REPPASSWORD DSC Password for the backup DSC repository user. Used for Create, Read, Update and Delete (CRUD) operations on BARBACKUP.
    SERVERID ClientHandler The server ID is the name of a DSA media server, and is a unique logical name across a single DSA domain. It is defined using SQL 92 syntax and used as the selector for JMS message headers. If the ClientHandler package is installed on a TPA node, the server ID cannot be equal to the name of that system. It is not the ID for NetBackup or other third party servers.
    When upgrading a media server for multiple DSA Network Client instances, specify the server IDs in a comma-separated list, for example, server1,server2 .
    SERVERPORT ClientHandler Port number for datapath traffic, corresponds to the server.port property in clienthandler.properties. Default: 15401.
    SSLTRUSTSTOREFILE ClientHandler Full file path for truststore file.
    SSLKEYSTOREFILE ClientHandler Full file path for keystore file.
    SSLKEYSTOREPASSWORD ClientHandler The value for the keystore password should be in clear text.
    WSPORT ClientHandler Port number for ClientHandler Web Service traffic, corresponds to the WebService.port property in clienthandler.properties. Default: 15402.

    The following code is an example of a DSC server dsainputs file:

    BURL=TDActiveMQ running server name
    BPORT=TDActivemq connection port number, either 61616 for tcp, 61617 for ssl
    CONNECTION=TDActiveMQ connection type, either tcp or ssl
    DSCNAME=unique name for the DSC server
    SERVERPROTOCOL=tcp
    SERVERID=dsams name: uname -n 
    DBSUSERNAME=dbc
    DBSPASSWORD=dbc password in clear text
    SUPERUSERNAME=dbc
    SUPERUSERPASSWORD=dbc password in clear text
    DSARESTPORT=9090
    BARSIZE=400
    OPPASSWORD=BAR password in clear text
    REPPASSWORD=BARBACKUP password in clear text
    BACKUPAPPCLIENTNAME=media server for third-party name, generally dsams name: uname -n 
    DSCUSER=dscuser
    USERID=600
    VIEWPOINTURL=viewpoint server name
    VIEWPOINTPORT=80
    VIEWPOINTTYPE=URL type, either http or https
    CAMPRIMARYURL=CAM primary server
    CAMPRIMARYPORT=61616
    CAMCLUSTERENABLED=yes
    CAMCLUSTERURL=CAM primary server, CAM failover server
    CAMCLUSTERPORT=61616
    SSLTRUSTSTOREFILE=/etc/opt/teradata/dsa/client.pem
    SSLKEYSTOREFILE=/etc/opt/teradata/dsa/client-keystore.pem
    SSLKEYSTOREPASSWORD=Client keystore password in clear text, used for ssl on TDActiveMQ
    ISMASTER=y
    MASTERHOSTNAME=dsadsc server where the master server is running
    CBBFILEPATH=/var/opt/teradata/dsa/cbb
    DBSHOST=tdpid of dsadsc server
    DSCREPBACKUPSYSIP=public ip for DBSHOST
    BROKERLIST=localhost:61616

    The following code is an example of a dsainputs file for a DSA media server:

    BROKERLIST=localhost:61616
    CONNECTION=TDActiveMQ connection type, either tcp or ssl
    SERVERPROTOCOL=tcp
    SERVERID=dsams name: uname -n 
    BACKUPAPPCLIENTNAME=media server for third-party name, generally dsams name: uname -n 
    DSCUSER=dscuser
    USERID=600
    SSLTRUSTSTOREFILE=/etc/opt/teradata/dsa/client.pem
    SSLKEYSTOREFILE=/etc/opt/teradata/dsa/client-keystore.pem
    SSLKEYSTOREPASSWORD=Client keystore passwordin clear text, used for ssl on TDActiveMQ
    ISMASTER=n
    MASTERHOSTNAME=dsadsc server where the master server is running
    CBBFILEPATH=/var/opt/teradata/dsa/cbb