Versions Compared

Old Version 7

changes.mady.by.user Morgan Mackeson-Ellis

Saved on

compared with

New Version 8

changes.mady.by.user Morgan Mackeson-Ellis

Saved on

Key

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

When Upgrading from previous versions of RED, the RED metadata, Azkaban metadata or both may need upgrading. For RED the requirement to upgrade is enforced at login when there is an application version mismatch, but it is best practice to validate and upgrade the metadata after every RED application upgrade. Refer to the Upgrading WhereScape RED section of the RED User Guide for more details.

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.

...

Upgrading RED

Version 10.3.0.0

  • This is a major release so a metadata validate and upgrade are required as usualThere 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. 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: 
    Code Block
    languagesql
    titleRemove 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='';

...

  • 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.0

  • 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.

...

  • 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):

...

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 integration scripts requiring manual upgrade (changes are cumulative), upgrades are optional unless marked as required:

...