Versions Compared

Key

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

...

  • Create Database and ODBC DSN  :
    • Supported* version of PostgreSQL (PostgreSQL 12 or higher)
      • A database to house the RED Metadata Repository.
      • A database for the Range Table DB (Optional)
      • A database to house scheduler (Optional)
  • Software Installations
    • WhereScape RED10 with valid license key entered and EULA accepted
    • WhereScape Enablement Pack for target database version RED10
  • Windows Powershell (64-bit) version 4 or higher
    • To check the Windows Powershell Version:
      • Run the below command in Windows Powershell
        Get-Host|Select-Object Version
      • Run the below command in the Command Prompt
        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
        Note
        \[Net.ServicePointManager\]::SecurityProtocol = \[Net.ServicePointManager\]::SecurityProtocol -bor \[Net.SecurityProtocolType\]::Tls12
        Register-PSRepository -Default -Verbose
        Set-PSRepository -Name "PSGallery" -InstallationPolicy Trusted

...

  • Create Database and ODBC DSN  :
  • Software Installations
    • Databricks CLI - Refer to Setup Guide Databricks CLI Setup 
  • 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

...

Run Setup Wizard as administrator

Create a new repository or upgrade an already existing repository.
Image Modified
Select the created ODBC DSN, input login details, and then select "Validate". Press Click Next.
Image Modified
Select the directory that contains the unzipped Enablement Pack for installation. Press Click Next.
Image Modified
Using the check boxed checkboxed list, include or exclude the components that are to be installed. Press Click Next.
Image Modified
Configure a target connection (for example, Data Warehouse) and its target locations.
Image Modified
Validate and press ADDclick Add.
Image Modified
When done, press ADD and then Press Next to advanceClick Done when completed, and click Next to continue.
Image Modified
Configure a data source connection (optional) and its target locations. Validate and press ADDclick Add. Press Click Next to advancecontinue.
Image Modified
Review the installation summary and click Install
Image Modified
Clicking on the View Logs will take you to the installation log. Click on Finish once the installation is completed successfully.
Image Modified
Login to WhereScape RED.

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 the post-installation process.
Image Modified
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.
Image RemovedImage Added
You will be directed to below the PowerShell window below. Provide the directory that contains the unzipped Enablement Pack.
Image RemovedImage Added
Press Click OK
The progress bar will show the post-installation progress.
Image Modified
User will Users have to choose the schema for the target setting that were was provided. One pop-up will come for setting the default target schema for Date Dimension.
Image RemovedImage Added 
After selecting the target schema, the progress bar will show shows the progress for the installation and once it's completed, you will get the below pop-up.
Image RemovedImage Added
After pressing OK RED10 will open clicking OK RED opens automatically.
Image Modified
User The user will need to refresh the All Objects tree once.
Image RemovedImage Added

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

    Image Modified


Important Upgrade Notes
If RED upgrade 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 before installing this  Enablement Pack and rename the affected UI Configurations. While the updated Load Template will work with previous Source Enablement Pack 's we recommend moving these previous 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.

...

  1. Connection: Data Warehouse ('Databricks')- This connection was setup set as per parameters provided in Setup Wizard
    1. open properties and check if Database ID is setup set correctly
    2. open properties and check the extended properties tab, set it up for HTTP_PATH, SERVER_HOSTNAME, DB_ACCESS_TOKEN, and DBFS_TMP
  2. Connection: 'Database Source System' - this connection was setup set up as an example source connection,
    1. open its properties and set it up for a source DB in your environment
    2. or you can remove it if not required

...

  1. Add a system variable DATABRICKS_CONFIG_FILE to point to a location that permits you to configure the databricks-cli.
    Image Modified
  2. Open command prompt and configure databricks-cli using databricks configure --aad-token.
    Image RemovedImage Added
  3. On running this command, the config file should be created in the location specified in the config file system variable
    Image Modified

Windows Powershell Script Execution

On some systems, Windows Powershell script execution is disabled by default. There are several workarounds for this which can be found by searching the term "Powershell Execution Policy".
Here is the most common workaround 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:

...

  • Method 1
    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 Administrator"
    Now you have an admin prompt navigate to to the folder where you have unpacked your WhereScape Red Enablement Pack using the 'cd' command:
    C:\Windows\system32> cd <full path to the unpacked folder> 
    Run batch (.bat) scripts from the administrator prompt by simply typing the name at the prompt and clicking enter, for example:
    C:\temp\EnablementPack>install_WslPython_Modules.bat
  • Method 2
    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 Administrator"
    Now you have an admin prompt navigate to to the folder where you have unpacked your WhereScape Red Enablement Pack using the 'cd' command:
    C:\Windows\system32> cd <full path to the unpacked folder>
    Run the below command
    python -m pip install -r requirements.txt

For upgrade of an existing repository 

Image Modified
In the upgrade of the existing repository if the user gets the above error then it means the script type of wsl_post_install_enablement_pack is set to PowerShell(64-bit) change the script type to Auto Execute-PowerShell before upgrade upgrading or manually run running the wsl_post_install_enablement_pack script from the host script from RED after the upgrade.

...

If you have RED 10.x or higher installed but the script (Setup_Enablement_Pack.ps1) fails to find it on 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

...