Release5.2 Migration Process

This article provides information about the migration process which needs to be followed by the customers who are migrating from the existing release version to the latest Release5.2 version.

In order to migrate/upgrade to the latest OvalEdge Release5.2 version, complete the following steps:

Step#1: For the customers using the below 5.1 series related versions (5.0, 4.3, 4.2, 4.1..) and if those customers want to migrate to the Release5.2 version, then those customers need to refer to the respective older migration document.

Step#2: For customers using 5.1 and 5.1 series-related versions (5.1.1, 5.1.2, 5.1.3 ….) and if those customers want to migrate to Release5.2 version, then the migration process up to Release5.1.9 version needs to be performed manually on their desired command-line tool (Ex: MYSQL) and then after the OvalEdge application will automatically migrate from Release5.1.9 to 5.2 versions.

Example: If the customer is using 5.1 on 5140.46, then the customer needs to run the scripts manually from 5100.46 to 5140.49. Then the application will run the 5200.sql scripts automatically.

Step#3: On the successful migration, run the OvalEdge application in the desired server Ex: Tomcat.

Step#4: For the customers who installed the application in 4.3.1 or before, below SQL must be included as part of the migration.

ALTER TABLE sourcecode ADD status VARCHAR(100) NULL AFTER lineagestatus;

Step#5: Log in to the OvalEdge application, navigate to Administration > Advance Job module, and run the Service Desk Data Migration job.

Step#6: Once the Service Desk Data Migration job is executed successfully, the application will be ready to use.

Step#7: When the application is ready to use, navigate to Administration > Advanced Jobs module, and run the Cleanup oesecure.* tables And add Unique Key jobs. Once the job is executed successfully, the system creates unique key constraints in the Security Tables.