Configuring a TPA Node as Media Server - Data Stream Architecture

Configuring a TPA Node as Media Server - 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

15.11

Published

December 2016

Language

English (United States)

Last Update

2018-04-17

dita:mapPath

ixz1479744517237.ditamap

dita:ditavalPath

3153_DSU_ICUCustomer_1511.ditaval.ditaval

dita:id

B035-3153

lifecycle

Product Category

Software

Teradata Tools and Utilities

To configure a Media Server on TPA node, ensure that the TPA node is installed with a version of the ClientHandler package that is compatible with the DSU packages on the DSU vNode. Refer to Installing the ClientHandler Software Package.

Configure ClientHandler on the TPA node to direct itself to the DSU instance.

Edit the /etc/opt/teradata/dsa/clienthandler.properties file.

Include the IP address of the DSU instance:

# Purpose: The hostname or IP address of the machine running the 
# Java Message Service (JMS) Message Broker. 
# Default: localhost 
# Other examples include: 
# broker.url=10.0.1.199 
# broker.url=hostname 
# broker.url=[fe80::114:23ff:fe1d:32fb] 
broker.url=IP of DSU instance

For example:

broker.url=192.168.0.256

Change the Server ID to the name you would like to give the Media Server. A good choice of Media Server name is the IP of the TPA node with letters "ch" appended. For example, if the TPA node has IP 10.25.26.122, then edit as follows.
```
# Purpose: name of the BAR server. Need to be set up before the server is run 
server.id=10.25.26.122ch
```

Restart ClientHandler for changes to take effect. /etc/init.d/clienthandler restart