OpenFormsTM Go Live! 6.1 to 7.0 Checklist
Go Live Checklist 6.1.x to 7.x with eGovern
Expand to view the detailed steps of the information below; review the detailed checklist if you are using eGovern.
Click to Read More...Read Less...
Overview
This document provides a high-level overview of the upgrade process from OpenForms version 6.1.x to 7.x. It is intended for technical teams responsible for planning and executing the migration. The checklist ensures that all critical steps are completed in the correct order to minimize downtime and maintain system integrity. The process involves preparation, upgrade execution, and post-upgrade validation, covering application servers, web servers, and associated components such as eGovern and Keycloak.
Required Steps
OpenForms 6.1.x to 7.x Upgrade-Go-live Checklist
- Items to be completed in specified order.
- Please contact the Application Specialist assigned to your upgrade if you encounter any errors or issues with a step, before proceeding to the next step. Provide screenshots and error logs where applicable.
Pre-Upgrade Activities
Preparation in Advance
On Clients, Application Server and Web Server
Ensure everyone has 64-bit crystal runtime.
On Web Server
- Confirm .Net 4.8 is installed
- Confirm client has SSL certificate created
- Install WebEz application, do not create website until cutover day
GNA
- Edit Email templates that eGovern uses to contain desired verbiage and appropriate URL
- ST Account Invitation
- ST Acct Inv accepted
The Day Before Upgrade
- Obtain password for download of Keycloak binaries during eGovern install process.
- Ensure all users have saved their work and logged out.
- Download the OpenForms version 7 binaries of tested version.
Upgrade Activities
On Web Server
- Stop Production website in IIS
On App Server/SQL Server
- Back up Production database
On App Server
- Upgrade the deployment using OpenForms version 7 binaries of tested version.
- Run database verification from the GNA application.
On Web Server
- Upgrade eGovern with WebEz
Run initial install of eGovern
Enter production site parameters
- Site name to be used in IIS
- Enter path to deployment directory on app server where the GovernNet.config file is
- Select or Create certificate
- Enter URL to use if different than Certificate
- Enter route path on local machine for files to be installed.
- Enter port to be used for website
- Enter the Keycloak port to be used – can increase the site port by 1.
- Enter text to be displayed on web page to id the page for users.
- Check use docker for Keycloak.
- Configure the realm.
Keycloak config
- Remove links to Google & Microsoft
From the application server in the Govern install directory copy the following:
- ResourceFiles
- governdabconfig
- Paste the Resourcefiles directory and GovernDABConfig.xml file into the eGovern install directory on the webserver.
From the Deployment you are pointing eGovern to function with directory, copy the following folders from the application server (i.e. C:\Govern\Deployments\[DeploymentName]) to the webserver C:\GovernApp\Govern_Test
- CustomControl
- SystemFiles
- eGovern
- WebApi
- WebFrontend
- And file: GovernNetConfig.xml
- Edit the paths in GovernNetConfig.xml to point to the local directories
- Run the migration of existing eGovern profiles to Keycloak.
Post Upgrade Activities
- Test logins to eGovern.
- Test eRemittance thru payment.
Summary
- Complete all tasks in the specified order and contact the assigned Application Specialist for any issues.
- Preparation steps include ensuring 64-bit Crystal runtime on all servers, .NET 4.8 installation, SSL certificate setup, and WebEz application installation.
- Update GNA email templates for eGovern prior to upgrade.
- Before upgrade day: obtain Keycloak binaries password, ensure all users log out, and download tested OpenForms 7 binaries.
- Upgrade steps: stop production IIS site, back up production database, deploy OpenForms 7 binaries, verify database, and upgrade eGovern with WebEz.
- Configure eGovern site parameters, SSL certificate, ports, Keycloak settings, and realm configuration.
- Copy necessary resource files and configuration files from application server to web server and adjust paths in GovernNetConfig.xml.
- Migrate existing eGovern profiles to Keycloak.
- Post-upgrade validation includes testing eGovern logins and eRemittance payment functionality.
Go Live Checklist 6.1.x to 7.x without eGovern
Expand to view the detailed steps of the information below; review the detailed checklist if you are not using eGovern.
Click to Read More...Read Less...
Overview
This document provides a high-level overview of the upgrade process from OpenForms version 6.1.x to 7.x. It is intended for technical teams responsible for planning and executing the migration. The checklist ensures that all critical steps are completed in the correct order to minimize downtime and maintain system integrity. The process involves preparation, upgrade execution, and post-upgrade validation, covering application servers
Required Steps
OpenForms 6.1.x to 7.x Upgrade-Go-live Checklist
- Items to be completed in specified order.
- Please contact the Application Specialist assigned to your upgrade if you encounter any errors or issues with a step, before proceeding to the next step. Provide screenshots and error logs where applicable.
Pre-Upgrade Activities
Preparation in Advance
On Clients, Application Server
Ensure everyone has 64-bit crystal runtime.
The Day Before Upgrade
- Ensure all users have saved their work and logged out.
- Download the OpenForms version 7 binaries of tested version.
Upgrade Activities
On App Server/SQL Server
- Back up Production database
On App Server
- Upgrade the deployment using OpenForms version 7 binaries of tested version.
- Run database verification from the GNA application.
Summary
- Complete all tasks in the specified order and contact the assigned Application Specialist for any issues.
- Preparation steps include ensuring 64-bit Crystal runtime on all servers, .NET 4.8 installation.
- Before upgrade day:
- Ensure all users log out, and download tested OpenForms 7 binaries.
- Upgrade steps:
- Back up production database
- Deploy OpenForms 7 binaries
- Verify database.
100-UpgdChklst_61to70
(0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...
