- Here's the first step of a complex task.
Here's (something in parens) in the info element following the first step.
`# /opt/teradata/client/version/dsa/barnc-init`
where *version* is the version of DSU you are configuring.
A prompt displays.
- a step with an image inline of a scr-schot.

- From your SSH client console, log on to the DSU instance as
ec2-userusing the applicable AWS key pair.
```
# ssh -i private-key-file ec2-user@public-DNS or public-IP
```
where:
- *private-key-file* is the private key file (`.pem`) of the AWS key pair specified when launching the DSU instance.
- *public-DNS* is the public DNS name or *public-IP* is the public IP address of the DSU instance.
- From your SSH client console, log on to the DSU instance as
ec2-userusing the applicable AWS key pair.
```
# ssh -i private-key-file ec2-user@public-DNS or public-IP
```
where:
- *private-key-file* is the private key file (`.pem`) of the AWS key pair specified when launching the DSU instance.
- *public-DNS* is the public DNS name or *public-IP* is the public IP address of the DSU instance.
-
Enter the name of the server.
For example,
prodApp-1.The script appends _media to the name. Another prompt displays.
-
Enter the IP address for the server running tdactivemq for Teradata DSU.
This IP address is the same as the DSC server that is running. For example,
9.8.7.6.The script verifies the connection to this IP address on ports 61616 and 15401. If successful, another prompt displays.
-
If the connection to the IP address fails, run the script again and provide the correct IP address to configure and initialize ClientHandler.
-
Enter the host name of the BarNC Web Services.
This host name is the DNS name for the first TPA node. For example,
ip-1-2-3-4. -
Here's step two of this complex task.
Using this info element to put in a table.
| Header row, cell 0-1 | Header row, cell 1-1 |
|---|---|
| Table row, cell 0-2 paragraph in a table row, cell 0-2
|
Table row, cell 1-2 paragraph in a table row, cell 1-2
|
| filepath in a table row, cell 0-3 | cmdname in a table row, cell 1-3 |
| userinput in a table row, cell 0-4 | cite in a table row, cell 1-4 |
| uicontrol in a table row, cell 0-5 | uicontrol in a table row, cell 1-5 |
Try a codeblock in this table row. <xsl:call-template name="process-inline-contents"/> <xsl:call-template name="process-inline-contents"/> |
Try a codeph in this table row.a little codeph |
- This step is followed by a stepresult.
The stepresult following a cmd
- Here's a
filepathin a step, followed by a cmdname in a step, followed byuserinputin a step, uicontrol in a step, ending with a cite in a step.
This info directly follows the cmd in a step.
- Using this step for a dl.
Between steps 4 and 6 with a definition list
<dl> <dt>definition term 1</dt> <dd>definition description 1</dd> </dl>
<dl> <dt>definition term 2</dt> <dd>definition description 2</dd> </dl>
- We'll try a choicetable in this step
| Choicetable header row, cell 0-1 | Choicetable header row, cell 1-1 |
|---|---|
| Table row, cell 0-2 paragraph in a table row, cell 0-2
|
Table row, cell 1-2 paragraph in a table row, cell 1-2
|
| filepath in a table row, cell 0-3 | cmdname in a table row, cell 1-3 |
| userinput in a table row, cell 0-4 | cite in a table row, cell 1-4 |
| uicontrol in a table row, cell 0-5 | uicontrol in a table row, cell 1-5 |
Try a codeblock in this table row. <xsl:call-template name="process-inline-contents"/> <xsl:call-template name="process-inline-contents"/> |
Try a codeph in this table row.a little codeph
|