Tool Upgrade Documentation
Objective: Upgrade the existing tools and technologies to the latest versions and configure them appropriately.
Activities Performed:
- Database Backup:
- Duration: 2 hours
- Description: Backup of the current database to ensure no data loss during the upgrade process.
- Uninstallation of Previous Versions:
- Java 1.8
- MySQL 5.7
- Redis
- WildFly 11
- Duration: 40 minutes
- Tools Uninstalled:
- Installation of New Versions:
- JDK 17
- MySQL 8.0
- Redis 5
- WildFly 30
- Duration: 1 hour 15 minutes
- Paths for all Tools
Wildfly30 – E:\uat_new\wildfly-30.0.0.Final\wildfly-30.0.0.Final
Redis5 – C:\Program Files\Redis
Java17 – C:\Program Files\Java\jdk-17.0.3.1
MySQL8 – F:\MYSQL8\MySQL\MySQL Server 8.0
- Paths for all Tools
- Database Schema Configuration changes:
- Duration: 2 hours
- Description:
Before tacking the backup we have made changes in db schema to make compatible with MySQL 8.0. Changes are mentioned here:
- While restoring latest backup need to replace NO_AUTO_CREATE_USER in db routines
- Keep sql_mode in my.ini config file (MySQL 8)
| sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION'; |
| 3. As part of testing done below datatype change (MySQL 8) alter table db_iemr.t_phy_anthropometry modify BMI decimal(7,3); 4. Reserved keywords would be changed to MySQL supported columns. ex: system, value etc.(identified in Pr_Practioner sp) |
| DB Objects | Upgradation Issues | |
| Tables | 5(trigger related tables) | Dump files created with an earlier version of mysqldump must be modified manually to remove instances of NO_AUTO_CREATE_USER. |
| Views | No Issues | |
| Procedures | All Procedures | Dump files created with an earlier version of mysqldump must be modified manually to remove instances of NO_AUTO_CREATE_USER. Reserved keywords whould be changed toMysql supported columns. ex: system,value etc.(identified in Pr_Practioner sp) |
| Triggers | All Triggers | Dump files created with an earlier version of mysqldump must be modified manually to remove instances of NO_AUTO_CREATE_USER. |
| Functions | No Issues | |
| Events | All Events | /*!50003 SET @saved_sql_mode = @@sql_mode */ ;; /*!50003 SET sql_mode = 'STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION' */ ; |
- Database Restoration:
- Duration: 2 hours
- Description: Restored the database from the backup created earlier.
- Creation of Database Users:
- Description: Created necessary database users with required privileges for operational needs.
- Configuration of WildFly:
- Description: Set up WildFly paths for Java and MySQL to ensure proper integration and functionality.
- Creation of Shortcuts:
- Description: Created necessary shortcuts on the desktop for quick access to the newly installed tools.
Summary of Time Spent:
- Database Backup: 2 hours
- Uninstallation: 45 minutes
- Installation: 1 hour
- Database Restoration: 2 hours
- Configuration and Setup: 2 hours
- Total Time: 7 Hours 45 Minutes
Next Steps:
- Verification:
- Ensure all tools are functioning as expected.
- Verify database integrity and user access.
- Testing:
- Conduct thorough testing of the upgraded tools and configurations.
- Confirm that all integrations and functionalities are operational.
- Documentation:
- Installation guide added
Written by Avinash - Document on Tool Upgrade on War files
Time taken – 3hrs
Step 1 – All service line collected war files of tool upgrade.
Step 2 – Configuration changes done based UAT server IP/URL for all service line.
hwc-ui-next
tm-ui-next
mmu-ui-next
Ecd-ui-next
104api-v1.0
104ui-v1.0
1097api-v1.0
1097identity-0.0.1
1097ui-v1.0
adminapi-ecd-next
adminapi-v1.0
admin-ui-next
commonapi-ecd
commonapi-v1.0
ecdapi-v1.0
fhirapi-v1.0
flw-0.0.1
hwc-facility-service
hwc-inventory-ui-next
hwc-scheduler-ui-next
identity-0.0.1
identity-ecd
Inventoryapi-v1.0
inventory-ui-next
mmuapi-v1.0
scheduler-api-v1.0
scheduler-ui-next
tmapi-v1.0
Step 3 – Checked Java version. It was 8.0 and changed to 17.
Step 4 – Checked MySQL services started or not.
Step 5 – Created shortcut icon for Redis and standalone & Started Redis and Wild fly and 4 files taken pasted in deployment folder to deploy wars.
Step 6 – Application testing has to happen next step in UAT.
Step 7 – Db patch missing should be updated by Dev team. below is 1 script and rest script need to check with Dev Team.
USE `db_iemr`;
CREATE
OR REPLACE VIEW `v_get_prkngplc_blok_dist_zone_state` AS
SELECT DISTINCT
`m_sp`.`ServicePointID` AS `Servicepointid`,
`m_pp`.`ParkingPlaceID` AS `ParkingPlaceID`,
`m_pp`.`ParkingPlaceName` AS `ParkingPlaceName`,
`m_db`.`BlockID` AS `BlockID`,
`m_db`.`BlockName` AS `BlockName`,
`m_d`.`DistrictID` AS `DistrictID`,
`m_d`.`DistrictName` AS `DistrictName`,
`m_zdm`.`ZoneID` AS `ZoneID`,
`m_z`.`ZoneName` AS `ZoneName`,
`m_s`.`StateID` AS `StateID`,
`m_s`.`StateName` AS `StateName`,
`m_sp`.`ProviderServiceMapID` AS `SPproviderservicemapid`,
`m_pp`.`ProviderServiceMapID` AS `PPproviderservicemapid`,
`m_zdm`.`ProviderServiceMapID` AS `ZDMproviderservicemapid`
FROM
((((((`m_servicepoint` `m_sp`
JOIN `m_parkingplace` `m_pp` ON (((`m_sp`.`ParkingPlaceID` = `m_pp`.`ParkingPlaceID`)
AND ((0 <> `m_pp`.`Deleted`) IS FALSE))))
JOIN `m_districtblock` `m_db` ON (((`m_pp`.`DistrictBlockID` = `m_db`.`BlockID`)
AND ((0 <> `m_db`.`Deleted`) IS FALSE))))
JOIN `m_district` `m_d` ON (((`m_db`.`DistrictID` = `m_d`.`DistrictID`)
AND ((0 <> `m_d`.`Deleted`) IS FALSE))))
JOIN `m_zonedistrictmap` `m_zdm` ON (((`m_d`.`DistrictID` = `m_zdm`.`DistrictID`)
AND ((0 <> `m_zdm`.`Deleted`) IS FALSE))))
JOIN `m_zone` `m_z` ON (((`m_z`.`ZoneID` = `m_zdm`.`ZoneID`)
AND ((0 <> `m_z`.`Deleted`) IS FALSE))))
JOIN `m_state` `m_s` ON (((`m_d`.`StateID` = `m_s`.`StateID`)
AND ((0 <> `m_s`.`Deleted`) IS FALSE))))
WHERE
((0 <> `m_sp`.`Deleted`) IS FALSE);
Step- 8 If we are changing path of my.ini file, Please keep same query in both place in C drive also and installed setup path in my.ini file.
sql_mode="STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION"