WhereScape Insights is designed to provide information about how a WhereScape Scheduler environment is performing, as well as give insights into how existing Scheduler configurations can be optimized.
WhereScape Insights consists of two components
A high-level architecture diagram for WhereScape insights is displayed below.

All other required applications are listed below. They are included in the WhereScape_Insights_20250110-1200.zip folder and will be installed automatically during the installation process.
WhereScape RED 10.0.1.0 with valid license key entered and EULA accepted
[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12 Register-PSRepository -Default -Verbose Set-PSRepository -Name "PSGallery" -InstallationPolicy Trusted |
Create system level ODBC DSN’s to connect to each existing WhereScape RED repository that will be included in the WhereScape Insights dashboards:
Four connections will be present in the new RED 10 metadata repository, for connecting to existing WhereScape RED environments. These connections need to be configured to allow WhereScape Insights to connect to any existing WhereScape RED environments. Please refer to the WhereScape RED user guide for further details on how to configure connections.
| Connection Name | Usage |
|---|---|
| Scheduler Data RED10_1 | This connection should be used for connecting to existing RED 10 metadata repositories. |
| Scheduler Data RED10_2 | This connection should be used for connecting to existing RED 10 metadata repositories. |
| Scheduler Data | This connection should be used for connecting to existing RED 9 metadata repositories. |
| Scheduler Data_2 | This connection should be used for connecting to existing RED 9 metadata repositories. |
Included with the WhereScape Insights pack are three files:
The ws_yf_config.dump is a PostgreSQL pg_dump of the Yellowfin configuration database YFInstances.zip is a compressed copy of the Yellowfin system, including all support and configuration files.
If the system is prepared correctly, it should now be possible to install the WS Red reporting solution.
Step one is to install the YF Configuration database.
This is critical as Yellowfin won’t launch if it cannot see a configuration database.
The ws_yf_config.dump file was created with the pg_dump command. Yellowfin will access this PostgreSQL database using the YFAdmin user account.
It is therefore necessary to ensure you have the YFAdmin user account created within the PostgreSQL 16 system.
Yellowfin will also use this account to access the data within the RED reporting database.
| If the password is changed, this can be re-configured in Yellowfin, but will require administrative access to perform the change. It is therefore best to keep the password as is. |
createdb -U YFAdmin YFConfig pg_restore -U YFAdmin -d YFConfig -1 c:\WS_YF_Deployment\ws_yf_config.dump C:\YFInstances\WhereScape\appserver\bin
Do not terminate or close this terminal window. Closing this window will shut down the Yellowfin instance immediately. |
At this point you should be able to access Yellowfin via a browser on the same system by using the URL: localhost
The following screen should appear: 
C:\YFInstances\WhereScape\appserver\bin directory and execute ‘Service install’ 

Included in the Yellowfin instance is a JavaScript file that will add users to the system on your behalf. It can only be executed from the server system; users will not be able to successfully add accounts should they decide to attempt to use the tool. To execute, from the server system, launch a browser and issue the URL: localhost/ws_admin_createuser.jsp
You will be presented with a form to complete:

Complete the form as required. The email address will form the users userID. There will be a default password created for the user. The user will be asked to change their password on first login.
For example:
Salutation: Dr
First Name: Bob
Last Name: Pies
Email Address: bob.pies@bobspies.com
YF Credentials will be:
UserID: bob.pies@bobspies.com
Password: P4ssword123456789!
The user can now log in, with the default Dashboards and reports.
The system has been configured to check for a license on the local machine every 24 hours. To ensure the system is functional, it will be necessary to ensure a valid license.lic file exists in the C:\YFInstances\WhereScape\appserver\webapps\ROOT folder.
The filename must be license.lic, anything else and the system will fail to authenticate the license.
Forcing a license update can be achieved by placing the license.lic file in the correct location and stopping/starting the Yellowfin server.