You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

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.

Important Messages when upgrading to 10.2.0.0

Upgrading RED

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

This version 10.2.0.0 has changes to the Azkaban components; therefore, all Azkaban Web Servers and Executor Servers need upgrading as well as the Azkaban metadata.

  • 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. Automated install script will need to take into account these new fields. Each of the Azkaban metadata, Azkaban Web Servers and Azkaban Executors will need to be upgraded to work with this release. 

Upgrading Azkaban is currently a manual process, please refer to the RED User guide for detailed upgrade instructions.

Change history for Azkaban components requiring upgrades (changes are cumulative):

  • 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 publish script has improved and can optionally be upgraded in RED. Refer to the RED user guide for detailed upgrade instructions.

Change history for integrations scripts requiring manual upgrade (changes are cumulative), upgrades are optional unless marked as required:

  • 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_scheduelr_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 
  • No labels