Versions Compared

Key

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

WhereScape is pleased to announce that that WhereScape RED 10.2.10.x0is now available.

This release of RED is compatible with WhereScape 3D 9.0 versions and up.

Note
titleNote
Before upgrading, review

...

the Important Messages when Upgrading from Earlier Versions for more information.

 

Table of Contents
maxLevel2
To review the Release Notes for older versions visit WhereScape Documentation.

...

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.

New Features and Improvements 

Customizable Object Subtypes

Configure your Object Subtypes based on the existing object types in RED with the following configurable settings:

  • Name
  • Icon to appear in object trees and documentation
  • Default Routine Templates for automated code generation
  • Appearance in object trees

Image Removed
This feature is beneficial to customers wanting to differentiate between more object types and control the automation aspects based on those types. It's particularly useful in the case of Data Vaults where there are many object subtypes that can be configured in 3D but don't currently have a dedicated object type mapping in RED such as PIT and Bridge tables. This feature also allows setting specific icons for each object subtype which improves both productivity and look and feel.

Scheduler Improvements

Azkaban core and the RED plugin for Azkaban have been improved in this release to enhance the workflows when dealing with abnormal job runs.

Improved Azkaban/RED synchronization

Azkaban to RED metadata synchronization on aborted jobs has been improved, now when canceling jobs directly from Azkaban the RED job metadata is updated to match the external job state. This removes the need to run additional tasks via Azkaban to have the job removed from the 'Running' state in RED and allows further remedial tasks to be performed on the job run, as required, immediately following an abort.

Added support for cleaning up child processes on job cancellations

When a job is canceled directly from Azkaban an optional cleanup script is now triggered automatically by the presence of a host script object in RED matching a specific naming convention. This is beneficial to users who need to kill long running or abnormal jobs in the scheduler but ensure that the underlying child processes for the job are also killed to prevent further unwanted transactions on the source and targets involved in the task.
Job cancellations will now execute the RED metadata host scripts, if present, named:

  • wsl_scheduler_job_kill_linux on Linux
  • wsl_scheduler_job_kill_win on Windows

Improved job restart workflow

When manually marking a failed task as 'completed' in the RED Scheduler tab for an aborted job, then a restart on this job will now set the job run to 'Succeeded', provided there were no other failures in the remaining tasks to execute. This is useful when resolving a failed task externally and then later continuing the remaining tasks in the job, so that the job then appears as a successful completion in the metadata.

Migrating from Earlier Versions of RED

Note that due to both the new PostgreSQL metadata and the external Azkaban-based Scheduler, there is no upgrade path from earlier versions of RED directly to RED 10. If you are an existing customer of WhereScape RED on another metadata platform, then migration tooling will become available soon after this release along with the rollout of procedure-compatible Enablement Packs for selected Target platforms.

WhereScape 3D Compatibility

WhereScape presents RED 10.2 a new version of RED with new capabilities and features to enhance the user experience. This version includes Advanced Authentication Methods.

Advanced Authentication Methods

The Advanced Connect feature provides a new way to manage connection security and modify ODBC connection attributes in RED enabling a wide variety of authentication mechanisms for your metadata, source, and target connections. This feature combines session-based authentication, complete control over ODBC connection strings, and secure encrypted storage of passwords.

This feature is designed with security in mind and adds even more ways for enterprises to secure their metadata, sources, and targets for a wide variety of authentication methods such as OAuth, Azure Active Directory, and multifactor authentication (depending on vendor driver capabilities). Please see the product documentation for more details.

Advanced Connect is always enabled in RED 10.2 and therefore a connection string must be defined for every ODBC, Database and applicable Extensible Source Connections in RED. The connection string will always be used when establishing ODBC connections from this release onwards. RED provides suitable default connection strings when not provided by the user. 

In conjunction with Advanced Connect, RED Profiles are used to store encrypted user specific credentials outside the metadata, for the RED UI these profiles are stored on disk using Windows DPAPI encryption, for the Azkaban Scheduler the profile is stored within a new metadata table in the 'redadmin' schema and encrypted with a new encryption utility provided in this release.

RED Login Screen showing the new fields 'Profile' and 'Connection String':

Image Added

RED Connection Properties Screen showing the new Advanced Connect Parameters:

Image Added

Stand-alone Script Improvements

Stand-alone scripts can now be associated with Database/ODBC and Extensible Source Connections providing access to the associated connection settings and Credentials in your scripts.

This feature is particularly useful for “High Water Mark” scripts that require access to target connection properties. When combined with Advanced Connect this provides a secure way to run scripts directly against source and target connections in RED. Previously you could only associate Windows or Linux connections to scripts.

Online Documentation

The WhereScape product family is moving towards online product documentation which allows us to keep the documentation more up to date outside of traditional release cycles and continue to make improvements that enable our customers to use our products to their full potential. 

From this release onwards when using the in-product help you will be redirected to our documentation website hosted on https://wiki.idera.com/category/ws. Contextual product help buttons are not yet linked to the relevant pages and instead take you to the landing page, contextual based help links will follow soon. 

For offline documentation requirements you will still be able to download the full user guide PDF's. This release of RED is compatible with WhereScape 3D 8.6.9.1 versions and up for 3D exports to RED but it is recommended to use the latest version 9.0.2.1 of 3D to provide all feature capabilities.

Customer Improvements

This release also includes the customer enhancements and support fixes listed in the following Detailed Changes section.

Detailed Changes in RED 10.

...

2.0.0

The following changes have been implemented since 10.0.1.0.2

 Improvements

  • RED-
  • 11635 Added support for case-sensitive filters in the scheduler job name filter
  • RED-11634 Enhancements to the project object maintenance dialog when accessed via the ribbon

  • RED-11636 Updated reports menu on the builder screen

  • RED-11633 Upgrades to this version will use the first target connection found to transfer Routine Default Templates settings to the new Object-Subtypes feature

  • RED-11626 New Object-Subtypes feature added which enables the addition of customizable object sub-types with their own default routine templates

  • RED-11639 Improved the killing of a job via Azkaban such that the RED metadata for the job is notified of the run state

  • RED-11638 Killing a job via Azkaban now allows the optional execution of a cleanup script which enables the opportunity to kill any child processes; if required

  • RED-11772 Token replacement for [TABLEOWNER].[table_name] and $OBJECT$ now allow 2-part-naming expansion when only the database name is used in the target platform (such as Teradata), this means if the schema field is left blank then the above tokens no longer expand to include an additional period for the schema in the fully qualified object name

Issues

  • RED-11775 Fixed an issue when generating documentation for specific projects

  • RED-11708 Enhancements to the project object maintenance dialog when accessed via the ribbon

  • RED-10313 Resolved an issue where 3D deployment to RED was doubling single quotes in extended property values

  • RED-11757 Restarting a job after manually marking a failed task as complete in RED now sets the correct final job completion status

  • RED-11681 Resolved a deployment issue for source mapping objects with where clauses exceeding 4000 chars

  • RED-11701 Fixed an issue in drag'n'drop from data warehouse tables when source column datatypes contain quotes

  • RED-11555 When exporting to RED from 3D all generated routines are now correctly associated with the groups of the parent object

  • RED-11647 The Maintain Hash Keys wizard now preserves the column position order of existing Hash Key columns

  • RED-11743 Upgrade 3rd-party components in Pebble project

  • RED-11742 Upgrade 3rd-party components in Azkaban project (including log4j)

  • RED-11741 Upgrade 3rd-party components in Template Engine project

Detailed Changes in RED 10.1.0.1

The following changes have been implemented since 10.1.0.0.

Improvements and Issues

  • RED-11851 Resolved issue with log4j upgrade where logging level was not being honored.
  • RED-11849 Upgrades to reported vulnerabilities in 3rd party libraries.
  • RED-11859 Fixed issue with the deployment of Data Vault Stage tables from 3D to RED where Hash Key Sources metadata wasn't deployed.
  • RED-11857 Resolved Revert to Version functionality showing the wrong dialog.
  • RED-11866 Fixed issue in applications deployment for object deletions.
  • RED-11848 Resolved 3D to RED deployment issue in the new Object Subtypes feature.

Detailed Changes in RED 10.1.0.2

The following changes have been implemented since 10.1.0.1.

Improvements and Issues

  • 11900 Updated the WslMetadataServiceClient.dll to work with the connection string arg. Updated the scheduler integration script to use the metadata connection string. 
  • RED-11895 RED Help (User and Installation Guide) is no longer installed with the product and now links to the online documentation at http://wiki.idera.com/category/ws
  • RED-11829 Azkaban core components and RED Azkaban plugin updated for Advanced Connect feature.
  • RED-11821 Improvements to the Windows Azkaban Scheduler installer to support Advanced Connect with DPAPI encryption. 
  • RED-11816 Added an encryption utility
  • RED-11813 Moved the RED Scheduler Configuration credentials to the RED Profile.
  • RED-11752 Stand-alone scripts can now be associated with Database and Extensible Source Connections providing access to target settings and credentials
  • RED-11745 Added Advanced Connect feature to RED 10 and forced its usage, this has potentially breaking changes, please refer to the important upgrade messages.
  • RED-11907 Resolved a digital signing issue that affected the RED 10.1.0.1 installer.
  • RED-11896 Resolved issue with generating routines via templates where the default template could not be determined in some cases affecting RedCli.exe and RedDeploy.exe
  • RED-11886 Fixed issue with object subtypes import process where default routine templates would not be applied in some scenarios affecting RedClie.exe and RED UI
  • RED-11786 Resolved "Cannot retrieve default template" error occurring after upgrading to 10.1.0.0 release in some situations affecting RED UI