Preparing the Templates in the Local System - Teradata Database on VMware

Teradata Database on VMware Developer Tier Getting Started Guide

Product
Teradata Database on VMware
Release Number
Deployer 3.01.01
Published
December 2017
Language
English (United States)
Last Update
2018-04-25
dita:mapPath
hph1509650909198.ditamap
dita:ditavalPath
TDVMWare_phase4a-4b_DEV.ditaval.ditaval
dita:id
B035-5938
lifecycle
previous
Product Category
Cloud

Before initially deploying the VM, you must prepare the templates in the local system. Having the template reside on your local system takes the VM longer to deploy. Having the template reside on vCenter enables the VM to deploy quicker.

Following are examples of deploying a Viewpoint template to the local system using either an absolute path or relative path. For the latest template version numbers, see Templates.
  • Local deployment using absolute path:

    C:\Templates\Teradata_Viewpoint_16.20.xx.xx_SLES11_SP3_on_VMware_xxxxxxxxxxxxxx.ova

  • Local deployment using relative path:

    Teradata_Viewpoint_16.20.xx.xx_SLES11_SP3_on_VMware_xxxxxxxxxxxxxx.ova

The download file names listed above are appended with 14 numbers representing when the template was created by Teradata: the year (4 digits), month (2 digits), day (2 digits), hours (2 digits), minutes (2 digits), and seconds (2 digits).

Following is an example of deploying a Viewpoint virtual machine from your local machine using an absolute path:
{
   "ESXiHost":  "cs3097-05.labs.teradata.com",
   "Datastore":  "cs3097-05.datastore",
   "vmName":  "cobra26",
   "eth0":  "10.25.28.110",
   "vmType":  "vp",
   "Template":  "Teradata_Viewpoint_16.20.xx.xx_SLES11_SP3_on_VMware_xxxxxxxxxxxxxx.o
va"
}