Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. RED Enablement Packs
  2. Enablement Pack - Home
  3. Install Guides

RED Enablement Packs : WhereScape Source Enablement Pack - Google Cloud Storage

Created by Poonam More, last modified on Jun 10, 2022
This is a guide for installing Source Enablement Packs for WhereScape RED 8.6.1.x 

Prerequisites

Source Enablement Pack Setup Scripts

The Enablement Pack Install process is entirely driven by scripts. The below table outlines these scripts, their purpose and if "Run as Administrator" is required. 

#

Enablement Pack Setup Scripts

Script Purpose

Run as Admin

Intended Application

1

install_Source_Enablement_Pack.ps1

Install Python scripts and UI Config Files for browsing files from Amazon S3, Azure Data Lake Gen2,Google Drive,Google
Cloud Storage

Yes

New and Existing installations


Powershell script above provides some help at the command line, this can be output by passing the "-help" parameter to the script.
NOTE: Note that on some systems executing Windows Powershell scripts is disabled by default, see troubleshooting for workarounds.

Source Enablement Pack Installation

  • Run Windows Powershell as Administrator 

...

  • If prompted enter source enablement pack as  'Google' Note: Skip the installation step if the target build with source packs is installed.

Google Cloud Storage Connection Setup

  1. Login to RED
  2. Check in Host Script Browse_Google_Cloud Storage in objects list.                                                                                  
  3. Check UI Configurations in Menu, Tools → UI Configurations → Maintain UI Configurations
  4. Create new connection in RED
  5. Select properties as shown in below screenshot

...

NOTE: Authentication is not done through script.It needs to be done while installing GoogleCloudSDKInstaller.

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 Source 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 .\install_Source_Enablement_Pack.ps1
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 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>

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: to 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.

If a valid RED installation can not be found

If you have Red 8.6.1.x or higher installed but the script (install_Source_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:

image2021-5-11_15-30-39.png (image/png) image2021-5-11_15-14-13.png (image/png) image2021-5-11_15-3-8.png (image/png) image2021-5-11_15-1-47.png (image/png) image2021-5-11_14-56-4.png (image/png) image2021-5-5_15-36-25.png (image/png) image2021-5-5_10-41-52.png (image/png) image2021-5-5_10-38-47.png (image/png) image2021-5-5_10-38-35.png (image/png) image2021-5-5_10-23-52.png (image/png) image2021-5-5_10-23-42.png (image/png) image2021-5-5_10-22-26.png (image/png) image2021-5-6_16-11-7.png (image/png) image2021-5-6_16-11-44.png (image/png) image2021-5-6_16-12-8.png (image/png) image2021-5-7_14-36-59.png (image/png) image2021-5-11_14-5-0.png (image/png) image2021-5-11_14-17-56.png (image/png) image2021-5-11_14-18-20.png (image/png) image2021-5-31_15-18-52.png (image/png) image2021-5-31_15-19-43.png (image/png) image2021-5-31_15-24-53.png (image/png) image2021-6-9_15-35-28.png (image/png)
Document generated by Confluence on Jun 04, 2024 23:39
Atlassian