WhereScape Enablement Pack for Google BigQuery - RED 10
This is a guide to installing the WhereScape Enablement Pack for Google BigQuery for WhereScape RED10
Table of Contents
- Prerequisites For PostgreSQL Metadata
- Prerequisites For Google BigQuery
- Installation Through Setup Wizard
- Upgrade Of Existing Repository
- Post Install Steps – Optional
- Source Enablement Pack Support
- Troubleshooting and Tips
Prerequisites For PostgreSQL Metadata
Before you begin the following prerequisites must be met:
- 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)
- Supported* version of PostgreSQL (PostgreSQL 12 or higher)
- 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 Windows Powershell Version:
- Run below command in Windows Powershell
- To check Windows Powershell Version:
Get-Host|Select-Object Version
- Run below command in 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 PowerShell gallery has deprecated and TLS 1.2 has been made mandatory
[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
Install-Module -Name PoshProgressBar -SkipPublisherCheck -Force
- : RED supports the following versions for the metadata repository: PostgreSQL 12 or higher
Prerequisites For Google BigQuery
Before you begin the following prerequisites must be met: - Create Database and ODBC DSN :
- Google BigQuery (ODBC driver version 3.00.xx.xxxx or higher(64-bit))
- At least one schema available to use as a RED Data Warehouse Target
- Google BigQuery (ODBC driver version 3.00.xx.xxxx or higher(64-bit))
- Software Installations
- Google Cloud SDK for utilities GSUTIL and BQ installed and on the Windows system path
- Download and Install Google Cloud SDK Installer from {+}https://cloud.google.com/sdk/docs/quickstart+
- Note: To use the Google Cloud SDK and its associated tools (GSUTIL and BQ), authentication, initialization, and project configuration are required. Please refer to the provided instructions for completing this process from {+}https://cloud.google.com/sdk/docs/install-sdk+
- Important: Google Cloud SDK and its associated tools (GSUTIL and BQ) must be authenticated again after installation. For reauthentication please refer this process from {+}https://cloud.google.com/sdk/gcloud/reference/auth/application-default+
/login or run below command as admin in Command Prompt and follow prompted instructions. A complete system restart is recommended after this process.
- Download and Install Google Cloud SDK Installer from {+}https://cloud.google.com/sdk/docs/quickstart+
- Google Cloud SDK for utilities GSUTIL and BQ installed and on the Windows system path
gcloud auth application-default login
- ODBC DSN created to connect to your RED Data Warehouse on BigQuery
- Google BigQuery Catalog Name
- At least one storage bucket needs to created on Google Cloud Storage.
- Permission Required : Upload, Read and Delete File
- Python 3.8 or higher (Tested with 3.8-3.11)
- Select "Add Python 3.8 to PATH" from installation Window
- Pip Manager Install with command : python -m pip install --upgrade pip
Note: Some of the libraries might be deprecated in the newer versions of python (Python 3.12 and higher)
Installation Through Setup Wizard
Run Setup Wizard as administrator
Create new repository or upgrade already existing repository.
Select the created ODBC DSN, input login details and then select "Validate". Press Next
Select the directory that contains unzipped Enablement Pack for installation. Press Next
Using the check boxed list, include or exclude the components that are to be installed. Press Next
Configure a target connection (example, Data Warehouse) and its target locations.
Validate and press ADD.
When done, press ADD and then Press Next to advance.
Configure a data source connection (optional) and its target locations. Validate and press ADD. Press Next to advance.
Review the installation summary and press Install
Clicking on the View Logs will take to the installation log. Click on Finish once the installation is completed successfully.
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 below PowerShell window which will give brief explanation about post installation process.
Press OK to start the post installation. If pressed Cancel installation will stop and 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 PowerShell window. Provide the directory that contains unzipped Enablement Pack.
The progress bar will show the post installation progress.
User will have to choose the schema for the target setting that were provided. One of such pop up will come for setting default target schema for Date Dimension.
After selecting the target schema progress bar will show the progress for the installation and once it's completed, you will get the below pop up.
After pressing OK RED10 will open automatically.
User will need to restart RED once.
After Restart
Upgrade Of Existing Repository
For upgrade of existing repository
- From host script set script type of wsl_post_install_enablement_pack as Auto Execute - PowerShell Script
Important Upgrade Notes
If RED repository exists, it will prompt to upgrade the repository. This enablement pack will overwrite any existing Source Enablement Pack UI Configs:
Amazon S3 | Load From Amazon S3 |
Azure Data Lake Storage Gen2 | Load From Azure Data Lake Storage Gen2 |
Google Cloud | Load From Google Cloud |
REST API | Load From REST API |
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 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.
Post Install Steps – Optional
If you used the script Setup Wizard for installation then the following optional post install steps are available.
Configure Connections
There were Three connections added that will optionally require your attention:
- Connection: Data Warehouse ('Google BigQuery' )- This connection was setup as per parameters provided in Setup Wizard
- open it's properties and check extended properties tab, set it up for GBQ_BUCKET and LOCATION
- Connection: 'Database Source System' - this connection was setup as an example source connection,
- open its properties and set it up for a source DB in your environment
- or you can remove it if not required
Enable Script Launcher Toolbar
There are a number of stand-alone scripts which provide some features such as "Ranged Loading", these scripts have been added to the Script Launcher menu but you will need to enable the menu toolbar item to see them.
To enable the Script Launcher menu in RED: Select menu item 'View->Toolbars->Script Launcher'
Source Enablement Pack Support
Source Pack Name | Supported By Google BigQuery | Supported Features | Prerequisites/Permissions Required Google Big Query |
Google Cloud Storage | Yes | Download to local and load | None |
Google Drive | No | N/A | None |
Azure Data Lake Storage Gen2 | Yes | Download to local and load | None |
Amazon S3 | Yes | Download to local and load | None |
Windows Parser |
| 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 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 batch (.bat) scripts from the administrator prompt by simply typing the name at the prompt and hit enter, for example:
C:\temp\EnablementPack>install_WslPowershell_Modules.bat
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.ps1
Notes: 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.
Setting Up Google BigQuery Configuration
1.Add a system variable GOOGLE_APPLICATION_CREDENTIALS to point to a location where credentials get generated.
2.open command prompt and cereate Google BiqQuery file using "gcloud auth application-default login"
3.On running this command, config file should be created in the location specified in the config file system variable
Windows Powershell Script Execution
On some systems Windows Powershell script execution is disabled by default. There are a number of workarounds for this which can be found by searching the term "Powershell Execution Policy".
Here is the most common workaround which WhereScape suggests, which does not permanently change the execution rights:
Start a Windows CMD prompt as Administrator, change directory to your script directory and run the WhereScape Powershell scripts with this command:
- cmd:>Powershell -ExecutionPolicy Bypass -File .\<script_file_name.ps1>
Re-install Python Libraries
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 to 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 hit enter, for example:
C:\temp\EnablementPack>uninstall_WslPython_Modules.bat
For installation of Python libraries there are two methods
- 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 to 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 hit 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 to 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 existing repository
In upgrade of exiting repository if the user gets 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 or manually run the wsl_post_install_enablement_pack script from host script from RED after upgrade.
If a valid RED installation can not be found
If you have RED 10.x or higher installed but the script (Setup_Enablement_Pack.ps1) fails to find it on you system then you are most likely running 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:
image2023-5-17_12-57-58.png (image/png) image2023-5-16_16-42-5.png (image/png) image2023-5-16_16-41-53.png (image/png) image2023-5-16_16-28-49.png (image/png) image2023-5-16_16-28-34.png (image/png) image2023-5-5_14-31-44.png (image/png) image2023-5-5_14-26-46.png (image/png) image2023-5-5_14-26-26.png (image/png) image2023-5-5_14-26-8.png (image/png) image2023-5-5_13-44-53.png (image/png) image2023-5-5_13-44-1.png (image/png) image2023-5-5_13-43-23.png (image/png) image2023-5-5_13-42-44.png (image/png) image2023-5-5_13-41-35.png (image/png) image2023-5-5_13-40-48.png (image/png) image2023-5-5_13-39-21.png (image/png) image2023-5-5_13-37-38.png (image/png) image2023-4-14_11-24-9.png (image/png) image2023-4-14_11-23-56.png (image/png) worddav8f28802bcc606872fcd1ba80d5cb0eaf.png (image/png) worddavdac1e6d68643d40a5a4b3e012a923c54.png (image/png) worddava135585b47137e44df62528f954ded8f.png (image/png) worddavea8a986ace4799130486d892480d85f0.png (image/png) worddavd2d3c877144733ebbaaba5bbf3bda2dd.png (image/png) worddavb76394cfa31d5b6e067cbd4f1488e32c.png (image/png) worddav8ea0cf3ea483ea7a242de789610ad2ba.png (image/png) worddav618cb65c184392be69e3c74024e85b92.png (image/png) worddav20b7ce4b2ab664894acee3df74dfe844.png (image/png) worddavc59f758196e39879a0edc0510b3f5f4f.png (image/png) worddav4d85e09a0382f84205f9bb1f3aca3f93.png (image/png) worddav8f07146097a5980b0bf66a2115b913e1.png (image/png) worddav9fff499c34123ad1b5397f743d3129f3.png (image/png) worddavac27573cde744c96cd8e7abb7a2ea24f.png (image/png) worddavb3543ca787efab25cd39165c5a6effea.png (image/png) worddav86d9bd86d87de0c7c2f08fc947085bf6.png (image/png) worddave5c3ccb6549cb875eddb710801253165.png (image/png) worddav92fe2ca9c94475e1037bd2eb6a0a5880.png (image/png) worddav216e4a806326cf33392235af376c56aa.png (image/png) worddav9b1fca73066ca8de7c6d1cecdf6cfd2e.png (image/png) worddav016c84efb21622d6c22ea93108b8865e.png (image/png) worddavb9a5cb10690b8bca7ef7ab657530b2d3.png (image/png) worddav9882c74559468d5d87f85c620de8bc68.png (image/png) image-2024-1-4_11-48-17.png (image/png) image-2024-1-4_11-55-29.png (image/png) image-2024-1-4_11-56-25.png (image/png) image-2024-1-4_11-57-29.png (image/png) image-2024-1-4_11-58-21.png (image/png) image-2024-1-4_11-59-33.png (image/png) image-2024-1-4_12-0-35.png (image/png) image-2024-1-4_12-4-37.png (image/png) image-2024-1-4_12-6-47.png (image/png) image-2024-1-4_12-8-39.png (image/png) image-2024-1-4_12-11-4.png (image/png) image-2024-1-4_12-13-10.png (image/png) image-2024-1-4_12-14-49.png (image/png) image-2024-1-4_12-16-2.png (image/png) image-2024-1-4_12-17-27.png (image/png) image2023-7-17_16-26-23.png (image/png) image2023-7-17_16-29-14.png (image/png) image2023-7-17_16-53-36.png (image/png) image-2024-1-5_12-11-38.png (image/png) image-2024-1-5_12-12-5.png (image/png) image-2024-1-5_12-16-22.png (image/png) image-2024-1-5_12-25-28.png (image/png) image-2024-1-5_12-27-37.png (image/png)
Document generated by Confluence on Jun 04, 2024 23:38
Atlassian