WhereScape is pleased to announce that WhereScape RED 10.3.0.1 is now available.
This release of RED is compatible with WhereScape 3D 9.0 versions and up.
Note
Go to https://www1.wherescape.com to see available product versions and release notes for older versions.
Log into the WhereScape Support Portal to access downloads.
Access the User Guide here.
WhereScape RED 10.3.0.1 Release Update
WhereScape is pleased to announce that WhereScape RED 10.3.0.1 is now available.
This release of RED is compatible with WhereScape 3D 9.0 versions and up.
Note
Go to https://www1.wherescape.com to see available product versions and release notes for older versions.
Log into the WhereScape Support Portal to access downloads.
Access the User Guide here.
New Features and Improvements
WhereScape presents RED 10.3 a new version of RED with new features that ease RED 10 migrations and continue to enhance scheduling capabilities. The features implemented in this version are mainly focused on enabling RED 10 migration pathways for traditional RED customers on SQL Server, Oracle and Teradata inbuilt targets.
Target License Improvements
RED 10 now accepts existing Oracle and Teradata licenses for use on RED 10 PostgreSQL metadata.
Additionally, RED target licenses for SQL, Oracle and Teradata now allow those traditional target types and their accompanying options in RED without the need to use a Custom target license. Unlike these targets in RED 9 and below, these target types will employ a completely template and configuration driven automation approach and will require an accompanying Target Enablement Pack just as existing targets on RED 10 do.
Note: Enablement packs to support these traditional RED target types in RED 10 will soon follow.
Other Improvements
This release also includes over 20 customer improvements and fixes, please refer to the Detailed Changes section for the full list, but here are a few of note:
Scheduler
The RED metadata connection resilience of the WhereScape Job Plugin for Azkaban has been improved, allowing automatic recovery from intermittent connectivity issues. This feature ensures jobs are resumed as required and the RED job metadata is kept up to date with the Azkaban job run status.
The Azkaban Web Server's connection to the RED metadata has also undergone connection resilience improvements allowing recovery from intermittent RED metadata connectivity issues.
Application Deployment
Simplified application deployment DML and DDL logging. The feature of logging DML and DDL to a file during deployment was conditional on another setting that disabled deployment changes on the target warehouse, now the logging will be generated regardless of other settings.
Deployment of Custom Object Sub-Types from 3D to RED requires the equivalent Object Sub-Types to exist in RED for successful deployment and code generation automation, the error messaging has been improved to list all Object Sub-Types which do not have a match in RED so that the synchronization between the configurations can more easily be resolved by the user.
Advanced Connect
Improved save workflow for RED Profiles so that passwords are not lost inadvertently when forgetting to tick the save passwords checkbox. Also f ixed an issue where the last logged in profile was not remembered at the RED Login Screen.
Detailed Changes in RED 10.3.0.0
The following changes have been implemented since 10.2.0.0
Improvements
- RED-11870 Existing RED Oracle and Teradata licenses are now accepted in RED 10 and Target Types SQL, Oracle and Teradata have been enabled.
- RED-11800 Added multi-select capability to the tree view controls in 'Project Object Maintenance' and 'Job Tasks Definitions' screen.
- RED-11927 Improved RED metadata connection resilience of the WhereScape Job Plugin for Azkaban.
- RED-11893 Improved connection resilience between Azkaban Web Server and the RED Metadata.
- RED-11072 Simplified deployment setting 'Log Metadata DML and Data Warehouse DDL to a File' to always be honored regardless of other settings.
- RED-11965 When saving an Advanced Connect Profile, 'Include Session Passwords' is now selected by default.
- RED-11966 Last Profile is now remembered at the RED login screen.
- RED-11854 Updated 3rd party libraries in Azkaban components.
- RED-11002 Added a new User Preference to allow override of Template operation timeout.
- RED-11881 Improved 3D to RED deployment failure messages when deploying new Object Subtypes which don't match to RED parent types.
Fixes
- RED-11844 Resolved errors when copying or moving projects with nested object tree view enabled.
- RED-11806 Fixed "Cannot retrieve default template" error after reverting a target connection from a version.
- RED-11852 When creating new tables, with nested object tree view enabled, the new table is now correctly positioned in the object tree.
- RED-11650 Fixed truncated dialog label in Scheduler Refresh Settings.
- RED-11771 Fixed a deployment issue from 3D affecting tables with multiple surrogate key joins, where only the first column's join metadata was populating.
- RED-11929 Resolved an issue where RED could crash when Data Vault Hash Key column name length exceeded 64 chars.
- RED-11969 Fixed issue where the metadata port was not added as an environment variable for scripts.
- RED-11562 Fixed an issue where Documentation Generation could lead to application crash in some cases when using remote desktop software.
- RED-11988 Fixed issue with 3D integration with RedDeploy not honoring the Profile selected.
- RED-11941 RedCli Connection Add/Modify now ignores credentials args to avoid them being entered into the metadata.
- RED-11984 Fixed issue where a trailing semicolon was incorrectly added to procedures compiled through RED UI for Custom targets.
Detailed Changes in RED 10.3.0.1
The following changes have been implemented since 10.3.0.0
Fixes
- RED-12010 Resolved an issue generating update routines during deployment from 3D of data vault tables with columns > 64 chars.
- RED-12009 Fixed issue with deploying data vault tables from 3D with column names greater than 64 chars, now the full 256 chars limit for column names will work.
- RED-12008 Improved the performance of starting up RED on large repositories with many Groups and Projects.
- RED-12007 Storage Settings on Named Targets are now exposed to the template engine for DDL code generation.
- RED-12000 Fixed Teradata Target creation issue in RED Setup Wizard.
- RED-12017 Loads on Named targets sourced from Windows/Linux connection now allow template driven code generation for all load types.
Important Messages When Upgrading
If there are important updates to the Azkaban metadata these will be indicated in the important upgrade messages that follow. Refer to the Upgrading Azkaban section of the RED User Guide for more details.
Important Messages when upgrading to 10.3.0.1
Note
Upgrades are cumulative; therefore you should read all upgrade messages for each version between your current RED version and this version of RED.
Upgrading RED
Version 10.3.0.1
- There are no important messages for upgrading RED to this release, but please consider the cumulative upgrade messages below when upgrading.
Version 10.2.0.0
10.2 has potentially breaking changes for upgraded repositories; therefore, upgrades should be tested thoroughly before upgrading production environments:
- All ODBC, Database, Extensible Source Connection and Scheduler Configuration credentials have moved to the RED Profile, therefore each user of RED should generate their own local profile file (see the user guide for details) to continue using RED.
- For new installs, from RED 10.2.+, you will find the wsl_scheduler_profile_maintenance host script under your Host Script's in your RED metadata repository (see the user guide for details). For upgraded repositories you will need to load this script into RED manually from <RED_Installation_Directory>\Administrator\Scripts\wsl_scheduler_profile_maintenance.ps1
- All Azkaban components require upgrading and the encrypted Scheduler profile records added to redadmin.ws_scheduler_profile (see the user guide for details) in order for jobs to run.
- Post upgrade it is encouraged to remove all credentials from the metadata since these should now reside in the in-memory session level credentials only. Run the following update on the metadata to achieve this: Remove credentials after upgrade
-- Remove credentials from Database, ODBC and Extensible Source connections UPDATE red.ws_dbc_connect SET dc_extract_userid='', dc_extract_pwd='', dc_admin_userid='', dc_admin_pwd='' WHERE dc_type IN ('D','O','Z'); -- Remove credentials from Scheduler Configuration UPDATE red.ws_wrk_external_scheduler SET wes_dashboard_userid='', wes_dashboard_pwd='', wes_restapi_userid='', wes_restapi_pwd='';
Version 10.1.0.0
10.1 has potentially breaking changes for upgraded repositories; therefore, upgrades should be tested thoroughly before upgrading production environments. The potential issues after the upgrade are the following:
- Default Routine Template settings might be lost. For object types other than Load and Export these settings have been moved from target connections to the Object Subtypes. During the metadata upgrade process, the first target-enabled connection found is used to populate the new settings under Object Subtypes. If you have multiple target-enabled connections in your repository, the optimal connection may not be used for the settings transfer. Ensure to check the Object Subtypes maintenance wizard after an upgrade to this version and set any missing/incorrect default routine templates as required. Note: this configuration can be exported from test to production once resolved in test.
- [TABLEOWNER] an $OBJECT$ token expansion no longer expands empty schemas to an additional ‘.’ in table names. This means from this release onwards you must specify the actual schema name in target location settings when schema is required on your platform. Ensure to check your target location settings for target connections before upgrading and populate the schema field, if required.
Upgrading Azkaban
Upgrading Azkaban is currently a manual process, please refer to the RED User guide for detailed upgrade instructions.
Version 10.3.0.1
- RED 10.3 improves the metadata connection resilience in both the Azkaban Web Server component and RED Job Plugin. Each of the Azkaban metadata, Azkaban Web Server and Azkaban Executors will need to be upgraded to take advantage of these features.
Version 10.2.0.0
- In RED 10.2 Advanced Connect is always enabled and therefore there are new azkaban.local.properties fields (and response.xml tags) required that support this feature. Any automated installation scripts will need to take into account these new fields. Each of the Azkaban metadata, Azkaban Web Server and Azkaban Executors will need to be upgraded to work with this release.
Azkaban Change history
Change history for Azkaban components requiring upgrades (changes are cumulative):
- 10.3.0.1: Azkaban/RED metadata connection resilience improvements. Component upgrades.
- 10.2.0.0: New required fields for azkaban.local.properties and installer resposne.xml for Advanced Connect. Stand-alone script execution enhancements.
- 10.1.0.1: Log4j components upgraded to log4j2 to resolve logging issues.
- 10.1.0.0: Improvements when canceling running jobs. Component upgrades.
- 10.0.1.0: Added procedure support and long host names fix.
- 10.0.0.0: First release.
Upgrading Scheduler Integration Scripts
The default scheduler integration scripts are often improved, occasionally these improvements are required to work with a new release. Please refer to the change history below and refer to the RED user guide for detailed upgrade instructions.
Integration Scripts Change History
Change history for integration scripts requiring manual upgrade (changes are cumulative), upgrades are optional unless marked as required:
- 10.3.0.1: No changes
- 10.2.0.0:
- wsl_scheduler_publish - Required upgrade - Advanced Connect feature added.
- wsl_scheduler_lookup - Added version header and removed unused parameters.
- wsl_scheduler_dashboard - Added version header and removed unused parameters.
- wsl_scheduler_profile_maintenance - New script for maintaining the scheduler profile.
- 10.0.0.3: wsl_scheduler_publish - Support for republishing when existing job not found. Improved logging.
- 10.0.0.2: wsl_scheduler_publish - Added support for disabled tasks.
- 10.0.0.0: First release.