OvalEdge Migration Process
      Back to home
      1. Knowledge Base
      2. Architecture, Security & Releases
      3. OvalEdge Migration Process

      Release6.3.4 Migration Process for VM Model

      This document provides guidance on migrating from previous versions to the latest Release6.3.4 version.

      Prerequisites for Migration

      Before initiating the migration process, ensure that the following prerequisites are met:

      Supporting Application Configurations 

      • Upgrade Infrastructure (Optional)

        Ensure that the applications and the operating system support the upgraded amount of RAM and have sufficient space on the new SSD for optimal performance.
        Application Migration from 6.3.3 to 6.3.4

      • Upgrade Database Version

        Upgrade the database to the below-mentioned versions for software performance and security. The previous versions of MySQL are no longer supported. 
      Upgrade MySQL Version to 8.0.36 or higher. For more information, refer to 

      Pre Upgradation 

      Take Database Backup

      Ensure a comprehensive backup of the Database (MySQL or MariaDB) is taken.

      Please take a look at the following document for backup instructions.

      OvalEdgeDB Backup Process

      Table Row Count Validation

      Validate the row count of all database entities to confirm the success of the migration process.

      Detailed instructions are available in the provided document.

      DB Migration Checklist

      Externalizing oasis.properties

      Externalizing log4j.properties


      Externalizing of log4j.properties is mandatory to overcome the logs writing into Catalina. For some of the customers, the space accumulates in the Tomcat folder.

      Refer to the document for detailed steps on Externalizing log4j.properties

      Upgrade or Install ElasticSearch 


      Upgrade ElasticSearch to 7.17.x for improved search capabilities within the OvalEdge. Refer to the document for more information.

      Upgrade Java Version (optional)


      It is recommended that Java be upgraded to version 8U_422 for optimal performance and compatibility. 

      For more information, refer to Upgrading Java on Windows

      Upgrade Tomcat Service Version


      It is recommended that Tomcat be upgraded to version 9.0.x. 

      For more information, refer to

      Upgrading Tomcat from 9.0.x to 9.0.98 with Step-by-Step Instructions. 

      Application Backups

      Before commencing the migration, execute the following backup and validation procedures:

      Take Application War, and Jars Backup


      Take a backup of War files from Apache Tomcat > Webapps and Jars (csp libs). This step is critical to safeguard against any potential disruptions during the migration process.

      Take a Backup of the Shared NFS Folder


      Take a backup of the files present in the shared NFS repository.

      Tomcat Server Backup & Preparation


      Take a backup of the Tomcat server. Clearing these folders helps create a clean environment for the upcoming migration, minimizing the risk of conflicts. In the Tomcat server, empty the following folders:

      • Webapps folder
      • Temp folders (excluding Jar files). Please ensure that jar files are not removed by accident.
      • Logs folders 

      System Settings Backup


      Take the backup of the system settings table from the OvalEdge database in XLSX format to ensure the configured default settings are available to reflect in the new version.

      For detailed instructions on taking table backups to CSV/XLSX, refer to the MySQL Table Backup to CSV/XLSX Guide

      Migration Process

      For VM, the migration process involves downloading release artifacts links provided in the email. The procedure involves sequential tasks, such as downloading the war from the given link, configuring oasis.properties, and running the Tomcat service to reflect the latest changes. Furthermore, executing advanced jobs is necessary to observe the latest changes specific to certain functionalities. 

      War Replacement

      1. Download the war files from the provided email link. 
      2. Once downloaded, go to the Tomcat directory, find the "Webapps'' folder, and copy the downloaded latest war file. 
      3. This ensures the integration of the latest functionalities, improvements, and gap resolutions addressed in Release6.3.4 so that the OvalEdge application can function properly.

      Connectors & Lineage/Jars Upgrade

      1. Download the Jar files using the link provided in the email.
      2. Replace the existing csplib / jars within the External Jars Directory > third_party_jars. 
        1. Ensure that the csp library (csp-lib-6.3.4-RELEASE-with-dependencies.jar) for standard connectors is updated.
        2. Ensure that the “oe-lineage.jar” is updated.
        3. Update the csp library for big data connectors (client specific)

      Advanced Job/Jars

      1. Download the Jar files using the link provided in the email.
      2. Replace the existing csplib / jars within the External Jars Directory > third_party_jars. 
      3. Ensure that the “oe-advancejob.jar” is updated.

      Setting oasis.properties in Tomcat  

      Within the VM, users can customize the oasis.properties in the External Property Directory file to meet their specific requirements, including database connectivity, security, authentication (SSO), Elasticsearch, management of external dependencies, and configuration storage in key vaults. 

      Governance App Configurations 

      These configurations are crucial to redirect users to governance-related applications using email or direct links.  Refer to the document to configure the Governance application. Governance App Configuration

      Tomcat Service Restart

      Restart the Tomcat services to apply and update the changes and initiate the migration successfully.

      Post Migration Checks 

      Tables & Row Count Validation

      Conduct a thorough verification of data row counts in the post-migration environment.

      Ensure that the actual counts match the pre-upgradation counts to identify and rectify discrepancies. This will serve as a key indicator of a successful migration. 


      The SQL scripts can be used to validate row and table counts.

      Download the scripts from the following S3 link: Tables and Row Count Validation Scripts.

      Verify Application

      Verify that the latest enhancements and features are successfully deployed in the application post-migration.

      Run the Advance Jobs

      This involves running the Advance Jobs, which are essential processes for ensuring the proper functioning of OvalEdge in its upgraded state. 

      For more information, please refer to the Appendix A below.

      Verify System Settings

      The migration process does not mandate adjustments to any system settings. However, it's important to note that for Release6.3.4, new system settings have been introduced, some have been deprecated, and others have undergone modifications. For more information, please refer to the Appendix A below.

      Verify Data Row Counts

      Conduct a thorough verification of data row counts in the post-migration environment.

      Ensure that the actual counts match the pre-migration counts to identify and rectify any discrepancies. This is a key indicator of a successful migration. 

      Appendix A: Advanced Jobs

      After migrating to Release6.3.4, the following advanced jobs must be run

      Run the same advanced job that was run for Release6.3 migration and additionally run the below listed advanced jobs associated with Release6.3.4. 

      A1: 6.3.4 Advanced Job Checklist 

      Advanced Job Name

      Description

      Migration_JobtoInactivate_Datasets

      This advanced job is used to make the child dataset(s) inactive when their parent dataset is inactive.
      Previously, the child dataset(s) remained active and visible in the Data Catalog under code associations, even when their parent dataset was inactive. However, the child datasets will now become inactive after running this job.
      Note:
      When to run this job:
      This migration job has to run once if users migrate from any release version to R6.3.4.

      DQTAT Execution Overview

      This job analyzes the Data Quality Test Suite, highlighting the status of each Data Quality Rule (DQR) executed in the current release. The job generates a summary of passed and failed rules, listing associated objects for each failed rule. This overview enables swift identification of potential data quality issues and assists teams in pinpointing areas that may require additional focus or remediation.

      Fetching Labels for Synapse Columns

      This job helps fetch the Synapse labels at table level and column level.

      Advance Job for Inserting data into the Lineage table

      This job allows the insertion of data into the Lineage Table to build a Connection Dashboard view.

      FME TO CARTO VISTA Lineage

      This job will establish lineage from FME to Carto Vista based on the FME Components.

      Report Crawl Analysis

      This job facilitates the analysis of activated and inactivated objects during the second crawl of the Power BI server. Upon running the job, a report is generated that provides details about the updated activated and inactivated objects of the Power BI server in OvalEdge, enabling users to track and manage object status effectively.

      Appendix B: New System Settings Added in Release6.3.4

      The latest release introduces new configurations that provide users with even greater control over the application's behavior. The newly added configurations are shown below.

      Key

      Description

      Impacted Modules in OvalEdge

      dataquality.associatedobjects.tables.limit

      Set the maximum number of objects (tables and table columns) that can be associated with a Data Quality Rule.

      Parameters:

      The default value is set to 1000.

      Enter the value in the field provided.

      Minimum entered value is 1.

      Maximum entered value is 1000.

      Data Quality

      dataquality.associatedobjects.files.limit

      Set the maximum number of objects (files and file columns) that can be associated with a Data Quality Rule.

      Parameters:

      The default value is set to 20.

      Enter the value in the field provided.

      Minimum entered value is 1.

      Maximum entered value is 250.

      Data Quality

      oe.profile.importancescore.threshold

      Configure to define a threshold value for the importance score of data assets in the profiling process. Only assets with an importance score equal to or greater than this threshold will be included in the profiling. 


      Parameters:

      The default value is 0.

      Enter the value in the field provided.

      The value should be in the range of 0-100.

      In Data Catalog > Tables, Table Columns.

      max.character.count.for.text.custom.fields

      Specify the maximum character count allowed for text custom fields.

      Parameters:

      The default value is 1000 characters.

      The accepted value is < 5000.

      Custom fields are available in the Data Catalog, Business Glossary, Tags, Data Quality Recommendations, ROPA Report, and ROPA Processing Activities.

      ai.description.enable

      Configure to show/hide the 'Generate with AI' icon for the Business, Technical, and Detail descriptions.

      Parameters:

      The default value is True.

      If set to True, show the 'Generate with AI' icon for the Business, Technical, and Detail descriptions.

      If set to False, hide the 'Generate with AI' icon for the Business, Technical, and Detail descriptions.
      • Business and Technical Descriptions in Data Catalog.
      • Business and Detail Descriptions in Business Glossary.

      home.lastlogin.enable

      Configure to show/hide the user's last successful login date and the number of unsuccessful login attempts between the current and the previous successful login.

      Parameters:

      The default value is 'False'.

      If set to 'True,' show the last successful login date and the number of unsuccessful login attempts between the current and the previous successful login.

      If set to 'False,' hide the last successful login date and the number of unsuccessful login attempts between the current and the previous successful login.

      Login page

      login.warning.enable

      Configure to show/hide the banner. Upon clicking Okay, users can enter their User ID and Password to proceed with the Login.

      Parameters:

      The default value is 'False'.

      If set to True, show the banner.

      If set to False, hide the banner.

      Login page

      login.warning.description

      The specified description in the Value column shows on the banner if login.warning.enable is set to 'true.'

      The maximum number of characters supported is 2000.

      Parameters:

      The default value is 'Empty'.

      If the Value column contains the content, it shows on the banner.

      If the Value column is 'Empty,' the banner is not shown.

      Login page

      Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA USA.