Page History

Versions Compared

Key

This line was added.
This line was removed.
Formatting was changed.

...

This is a guide to installing the WhereScape Enablement Pack for Teradata for WhereScape RED10Table of Contents

Prerequisites For PostgreSQL Metadata

Before you begin the following prerequisites must be met:

Create Database and ODBC DSN DSN:
- Supported* version of PostgreSQL (PostgreSQL 12 or higher)
  - A database to house the RED Metadata Repository.
  - A database to house scheduler (Optional)
Software Installations
- WhereScape RED10.1.x.x with valid license key entered and EULA accepted
- WhereScape Enablement Pack for target database version RED10.1.x.x
Windows Powershell (64-bit) version 4 or higher
- To check the Windows Powershell Version:
  - Run the below command in Windows Powershell
    Code Block
    Get-Host|Select-Object Version

Code Block
Get-Host\|Select-Object Version

- - Run the below command in the Command Prompt
    Code Block
    powershell $psversiontable

Code Block
powershell $psversiontable

...

Run the following command using PowerShell
- - The security protocol TLS 1.0 and 1.1 used by PowerShell to communicate with the PowerShell gallery has been deprecated and TLS 1.2 has been made mandatory

...

Code Block
\[Net.ServicePointManager\]::SecurityProtocol = \[Net.ServicePointManager\]::SecurityProtocol -bor \[Net.SecurityProtocolType\]::Tls12 Register-PSRepository -Default -Verbose Set-PSRepository -Name "PSGallery" -InstallationPolicy Trusted

Code Block

\[Net.ServicePointManager\]::SecurityProtocol = \[Net.ServicePointManager\]::SecurityProtocol -bor \[Net.SecurityProtocolType\]::Tls12
Register-PSRepository -Default -Verbose
Set-PSRepository -Name "PSGallery" -InstallationPolicy Trusted

Progress bar placeholder info line

Code Block
Install-Module -Name PoshProgressBar -SkipPublisherCheck -Force

: RED supports the following versions for the metadata repository: PostgreSQL 12 or higherhigher

Prerequisites Target Database

Before you begin the following prerequisites must be met:

Access to an a Teradata (Target Environment), with the following connectivity information :
1. Server Name
2. Database Name
3. User Name
4. Password
5. At least one database is available to use as a RED Data Warehouse Target with permissions CREATE, EXECUTE, DROP, SELECT PROCEDURE.
Create Database and ODBC DSN Teradata ODBC driver (64-bit)
1. Add ODBC DSN for Teradata Target Database
2. The 'Return Output Parameters As ResultSet' option is to be checked in the driver options setting.
Software installation
- Install the necessary Teradata Tools and Utilities (TTU) (TBuild CLI Tool) as per Teradata's documentation.
Python 3.8 or higher
- Select "Add Python 3.8 to PATH" from the installation Window
- Pip Manager Install with the command: python -m pip install --upgrade pip

Installation Through Setup Wizard

Run Setup Wizard as administrator

Create a new repository or upgrade already an existing repository.

Select the created ODBC DSN, input login details, and then select "Validate". Press Click Next

Select the directory that contains the unzipped Enablement Pack for installation. Press Click Next

Using the check boxed checkboxed list, include or exclude the components that are to be installed. Press Click Next.

Configure a target connection (for example, a Data Warehouse) and its target locations. Validate and press ADD. Validate and click Add

When done, press ADD click Add and then Press Next to advancecontinue.

Configure a data source connection (optional) and its target locations. Validate and press ADDclick Add. Press Click Next to advancecontinue.

Review the installation summary and click Install

Clicking on the Click View Logs will take to open the installation log. Click on Finish once the installation is completed successfully.

Login to WhereScape RED.
Note:

Note
There is a post-install script that will run at the first login to RED10 to complete the post-setup wizard installation process.

You will be directed to the below PowerShell window which will give a brief explanation about of the post-installation process.

Press Click OK to start the post-installation. If pressed Cancel installation will stop and the user will be directed to RED.
The user will be directed to the window below, where they have to select the target connection to be configured. Additionally, by deselecting the provided options, the user can choose not to install a particular option.

You will be directed to below the PowerShell window below. Provide the directory that contains the unzipped Enablement Pack.

Press Click OK
The progress bar will show the post-installation progress.

User Users will have to choose the database for the target setting that were was provided. One pop-up will come for setting the default target target for Date Dimension.

After selecting the target target progress bar will show the progress for the installation and once it's completed, you will get the below pop-up.

After pressing clicking OK, RED10 will open opens automatically.

User The user will need to restart RED once.

Upgrade Of Existing Repository

For upgrade of an existing repository

From host script set the script type of wsl_post_install_enablement_pack as Auto Execute - PowerShell Script

Important Upgrade Notes
If RED upgrade upgrades the repository option is chosen.
This enablement pack will overwrite any existing Source Enablement Pack UI Configs:

...

To ensure existing Source Enablement Pack connections and associated Load Tables continue to browse and load:
Go into UI Configuration Maintenance in RED prior to before installing this Enablement Pack and rename the affected UI Configurations. While the updated Load Template will work with the previous Source Enablement Pack 's we recommend moving these previous earlier versions of Load Tables to newly created Parser-based connections following this install. The earlier versions of the Source Enablement Pack will be deprecated following this release.

Post Install Steps – Optional

If you used the script Setup Wizard for installation then , the following optional post-install steps are available.

...

Connection: 'Database Source System' - this connection was setup set up as an example source connection,
- open it's properties and set it up for a source DB in your environment
- or you can remove it if not required
Execute Update Procedure for dim_date_td to Initialize Date Dimension for Target

Note

...

Please avoid regenerating the procedure update_dim_date_td as it is a custom procedure.

Source Enablement Pack Support

Source Pack Name	Supported By Teradata	Supported Features	Prerequisites
Amazon S3	Yes	Teradata Access Module for S3 (CSV)	Create a credential file by following the documentation linked below, and paste the directory location of the credential file into the 'Amazon S3 Config Directory' Extended Property: {+}https://docs.teradata.com/r/Enterprise_IntelliFlex_Lake_VMware/Teradata-Tools-and-Utilities-Access-Module-Reference-20.00/Teradata-Access-Module-for-S3/The-config-and-credentials-Files+
Azure Data Lake Storage Gen2	Yes	Teradata Access Module for Azure Blob (CSV)	Create a credential file by following the documentation linked below, and paste the directory location of the credential file into the 'Azure Config Directory' Extended Property: {+}https://docs.teradata.com/r/Enterprise_IntelliFlex_Lake_VMware/Teradata-Tools-and-Utilities-Access-Module-Reference-20.00/Teradata-Access-Module-for-Azure-Blob/The-Credentials-File+
Google Cloud Storage	Yes	Teradata TPT	None
Windows Parser	1. CSV 2. Excel 3. JSON 4. XML 5. AVRO 6. ORC 7. PARQUET	Load Template, Source Properties will have option to select parser type to load the files.	Refer to Windows Parser Guide

Troubleshooting and Tips

Run As Administrator

Press the Windows Key on your keyboard and start typing cmd.exe, when the cmd.exe icon shows up in the search list right click it to bring up the context menu, select "Run As as Administrator"
Now you have an admin prompt navigate to to the folder where you have unpacked your WhereScape Red Enablement Pack to using the 'cd' command:
C:\Windows\system32> cd <full path to the unpacked folder>
Run Powershell (.ps1) scripts from the administrator prompt by typing the Powershell run script command, for example:
C:\temp\EnablementPack>Powershell -ExecutionPolicy Bypass -File .\Setup_Enablement_Pack.ps1Notes:

Note
In the event you can not bypass the Powershell execution policy due to group policies you can instead

...

try -ExecutionPolicy RemoteSigned

...

which should allow unsigned local scripts.

Windows Powershell Script Execution

On some systems, Windows Powershell script execution is disabled by default. There are a number of several workarounds for this which can be found by searching the term "Powershell Execution Policy".
Here is the most common workaround which that WhereScape suggests, which does not permanently change the execution rights:
Start a Windows CMD prompt as Administrator, change the directory to your script directory, and run the WhereScape Powershell scripts with this command:

cmd:>Powershell -ExecutionPolicy Bypass -File .\<script_file_name.ps1>

Restarting failed scripts

Some of the setup scripts will track each step and output the step number when there is a failure. To restart from the failed step (or to skip the step) provide the parameter "-startAtStep <step number>" to the script.
Example:
Powershell -ExecutionPolicy Bypass -File .\<script_file_name.ps1> -startAtStep 123

Tip

...

T avoid having to provide all the parameters again you can copy the full command line with parameters from the first "INFO" message from the beginning of the console output.

Python requirements for offline install
Additionally to the base Python installation being required, the WhereScape Python Template set also requires certain additional Python libraries. The install scripts uses use the PIP (package manager) to download these libraries, however, for offline installs, you will need to install the required libraries yourself.
Required Python libraries/add-ons:

...

If you have RED 10.x or higher installed but the script (Setup_Enablement_Pack.ps1) fails to find it on you your system then you are most likely running the PowerShell (x86) version which does not show installed 64-bit apps by default. Please open a 64-bit version of Powershell instead and re-run the script.

Attachments:

Content

Space Tools