OpenForms V6 Sunsetting Notification

Formal Announcement: Sunset of OpenForms Version 6.1

Effective December 31, 2026

This notice is to inform you that Version 6.1 of our OpenForms software will reach its official end-of-support on December 31, 2026.

Click to Read More...

Communiqué

As part of our ongoing commitment to product quality, security, and long-term platform stability, we are consolidating our development and support efforts around fewer modern versions of the software. This focus enables us to more efficiently deliver enhancements and provide a stronger overall customer experience.

We encourage all customers currently operating on OpenForms Version 6.1 to begin planning their transition to OpenForms Version 7, which includes a wide range of technical and functional improvements:

  • 64-bit application architecture for improved performance and reliability
  • Generic Import Tool for enhanced data management
  • Enhanced export capabilities for self-service data extraction
  • Merge-to-PDF capabilities for modern reporting workflows
  • Enhanced Form Designer with expanded customization options
  • Upgraded Workflow Engine offering greater automation and flexibility
  • Improved Web Portal functionality for streamlined online services
  • Name merge utility for accurate record keeping
  • Parcel annexation and incorporation module for streamlined processing
  • Optimized compute functions allowing for faster calculations
  • Modernized GIS interface allowing integration with cloud hosted mapping providers
  • Modern Marshall & Swift interface leveraging cloud hosted valuation models
  • Condominium management module to build efficient workflows for Condominiums
  • Support for new modules Utility Billing and Special Assessments

 

The upgrade path from Version 6.1 to Version 7 is straightforward and can be self-performed. Upgrade guides are available on our knowledge base here. Additionally, our team is available to assist with upgrade planning, scheduling, and execution to ensure a smooth transition.

Over the coming weeks, we will also be reaching out to your designated technical contacts to discuss timelines, answer questions, and help coordinate your upgrade strategy.

If you require more immediate guidance or would like to begin planning now, please contact our support or product teams.

We appreciate your continued partnership and look forward to supporting you on Version 7 and future releases.

Related Topic(s)

OpenFormsTM Go Live! 6.1 to 7.0 Checklist

 

 

 

100-OF_Sunset_V6

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...

OpenForms – GoLive! 6.1.x to 7.0 Check List

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...

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...

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 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...

eGov – Upgrade Web User Interface

Upgrade of the eGovernment – Public Self Service Portal

Overview

The Govern Public Web Portal is an e-Government services application that contains a set of modules which provide citizens and professionals public access via the Internet. Through the portal, users are able to apply, query, request and view information. This page is intended for administrators, and contains links to instructions of how to upgrade to the current version of the e-Government (eGov) – Public Self Service Portal (WebUserInterface) that is hosted on an IIS Server.

How to Obtain the Updated Package…

The new package can be downloaded through the Govern Deploy EZ deployment application. To download through Deploy EZ:

  1. Launch Deploy EZ.
  2. Select the Download binaries from the FTP site
  3. Click Next.
  4. In the Import Selection group, select the eGovern
    Package    .
  5. Click Next.

The selected packages will be downloaded.

Copy Downloaded Files to IIS Server

Once the package has been downloaded, copy the package (WEBUserINTERFACE_6.1.XXX.XXXX.zip) from the folder \\kpb\installpoint\MSGovern.SRTClient61\Binaries\eGovern to the IIS Server.

If downloaded to the Govern install folder:

\\Install_Folder\Govern\Binaries\WEBUSERINTERFACE\6.1.XXXX.XXXX

  1. Copy the downloaded file to the IIS server.
  2. Extract the Zip file package WEBUserINTERFACE_6.1.XXXX.zip

Deploying the new version on the IIS Server

WARNING: Prior to performing any update ensure that a backup has been made of the folder that is being upgraded.

1. Stop the Application Pool

To deploy the new version on the IIS server…

  1. Open the IIS Manager console.
  2. Select the Application Pools.
  3. Locate the application pool of the website that is to be updated.
  4. Click Stop to stop the application pool.

2. Stop the website to upgrade

In the Sites section:

  1. Select the website to upgrade and in the Manage Website
  2. Click Stop to stop the website.

3. Verify your backup…

In the folder containing the site that is being hosted, make a backup of all files in the folder. This should be done prior to copying the new version. This procedure is done in case there are errors with the installation and a roll back is required.

4. Edit the “web.config” file

Perform the following steps to edit the web.config file.

  1. Rename the config to web.config.bkp, or the filename that is located in the V1 folder; this is the folder that the website is installed in.
  2. Copy and Replace all files located in the files from the package.

<appSettings>

<!– MSGovern configuration file–>

<add key=”MSGovern.GovernNetConfig” value=”D:\inetpub\salestaxtest.kpb.us\v1\GovernNetConfig.xml” />

<add key=”MSGovern.SynchFileAndFolders” value=”FALSE” />

<add key=”MSGovern.CopyFilesAndFoldersLocally” value=”FALSE” />

<add key=”GovernSoftware.WebSite_Id” value=”1″ />

<add key=”GovernSoftware.DefaultPage” value=”WEBPROFILE” />

<add key=”GovernSoftware.UploadDirectory” value=”D:\inetpub\salestaxtest.kpb.us\vl\Dummy\”  />

<add key=”GovernSoftware.UploadMaxFileSize” value=”5048576″ />

<add key=”GovernSoftware.Version_dnet” value=”3″ />

<add key=”GovernSoftware.DisplayBuildVersion”  value=”Off” />

<add key=”GovernSoftware.TraceArTransactionResponse” value=”Off” />

<add key=”GovernSoftware.WebReportDirectoryPath” value=”D:\inetpub\salestaxtest.kpb.us\v1\Dummy\” />

<add key=”GovernSoftware.WebReportWidth” value=”875″ />

<add key=”GovernSoftware.WebReportViewerHeight” value=”1200″ />

<add key=”GovernSoftware.WebReportViewerZoomFactor” value=”100″ />

<add key=”GovernSoftware.WebReportViewerw1dthLandscape” value=”l080″ />

<add key=”GovernSoftware.WebReportViewerHeightLandscape” value=”825″ />

<add key=”GovernSoftware.WebReportV1ewerZoomFactorLandscape” value=”l00″ />

<add key=”GovernSoftware.ShowHelpPath” value=”False” />

<add key=”GovernSoftware.DebugMode value=”True” />

<add key=”GovernSoftware.ReportDebugMode” value=”False”  />

<!– Temporary Setup- Must add in GNA –>

<!– <add  key=”GovernSoftware.GisServerName” value=”mtldev01″/> –>

<!– <add  key=”GovernSoftware.GisGeoDataBaseName” value=”Layers@Juneau”/> –>

<!– <add  key=”GovernSoftware.AutoLogin.Login” value=”+5fJF+/cy3RmUG6brJBK9b5i/a+ycLok”/> –>

<!– <add  key=”GovernSoftware.Autologin.Password” value=”47rYbcSyyx6t 1Kx6ZnEn6QwFeKG4tNoq”/> –>

<add key=”GovernSoftware.cGovernWMUrl” value=”/st/account?suppressRedirect=true” />

</appSettings>
  • Open the config.bkp.
  1. Locate and copy the contents of the appSettings section to the new config file.

 

5. Restart the website…

The next step is to restart the website. In the IIS console…

  1. Open the Application Pools.
  2. In the Application Pool Tasks section, click Start to start the application pool of the site.
  3. In the IIS console open the Manage Website section and click Start to start the web site.
  1. At the bottom of the IIS Console, click the Content View tab at the bottom of the console to display the Content View in the console
  2. In the connections pane expand the sections to display the CommonPages
  3. Look in the CommonPages Content pane and locate aspx
  4. Click on aspx and select Browse under the Actions pane.

The default web browser will open to display the validator page; this will validate that the site is functional.

6. Validation of the installation

In the header of the validator page, the installed version of eGovern will be displayed. In addition, details of the website will also be displayed.

NOTE: The information in the Check Speed section can be ignored.

Documentation

Click here to view the content of this page as a document.

Related Topics

What’s New in the eGovern

Configuring the eGov

eGov Product Map

FAQ

 

 

201-all-egov-upgrade

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...

eGov – Configuration

Configuration of the eGovernment – Public Self Service Portal

Overview

When users arrive at the home page and access the ePortal, or perform a login to access the eProfile, a default starting point is used from the setup. This default refers to a department. The default and other settings are part of a series of steps needed to define the eComponent site. General configuration is carried out through the OpenForms General Settings Editor in GNA. Additional parameters are required to be completed when using the eGovern – Public Self Service Portal module.

General tab

eComponent configuration parameters are located in the Websites Manager form in the Govern New Administration (GNA) Release 6.0 and greater.

eGovern Configuration – SMTP

Configuration of the SMTP parameters of the eGovern – Public Self Service Portal is carried out within the Govern New Administration (GNA).
In the GNA ribbon …

  1. Select Application Configurations (tab) > Web Configuration (group) > Manage Web Site.
  2. In the Manage Web Site form, click the General tab.
  3. Locate the Mail group.
  4. Complete the required fields.

The required parameters are as follows:

  • Administrator Mail – This field should contain the email address of the system administrator that has been designated to receive error messages.
  • System Mail – The System Mail parameter is the address that will be used for the from field in the email message. These are system messages that will not require replies, e.g. confirmation of user payments.
  • SMTP Host – Enter the host name of your SMTP server in the SMTP Host parameter. Example: mailhost.domainName.com, or smtp.sparta.com.
  • SMTP Password – In the SMTP Password field enter the password used to access the account. Text entered into this field will appear “cloaked”, i.e. typed letters will appear as asterisks
    “ ” to hide the typed letters.
  • SMTP Port – Specify the SMTP Port; the typical port is 25.
  • SMTP User – In the SMTP User field enter the username that is used to access the account.
  • Activate email in HTML format – Select this option to send email messages in HTML format. As HTML text additional formatting can be added to the messages. The default format for sending messages is as plain text.

Include Administrator in Email Communication** – Select this option to send a copy of the email message to the administrator.

About Ports

Port information is best obtained from the System Administrator that manages the communications requirements for the organization. By default, the following ports may be used for the SMTP protocol:

For Unencrypted SMTP

Port 25 / 587 / 2525 – This is the default SMTP non-encrypted port but ISPs will deny its use because of spam and malware traffic. Alternate ports are 587, and 2525

SMTP with SSL

Port 465 – This is a deprecated port but may still be used.

Related Topics

What’s New in the eGovern

Upgrading the Web User Interface

eGov Product Map

FAQ

 

 

201-all-egov-config

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...

Govern 10.8 to OpenForms 6.0 Upgrade

Upgrade from Govern 10.8 to OpenForms 6.0

Upgrading to OpenForms version 6.0 or greater

Overview

As Govern has undergone a major revamp it is a good time for business re-engineering. Prior to upgrading to 6.1, a review of customer processes and requirements is recommended.
More than likely needs have changed, not to mention technology, hardware and software that evolved.

  • NOT A REGULAR UPDATE *** Structure changes and new features that can bring significant benefits to users if reviewed and analysed beforehand.

See also Database Standards (100-Standards) | System Requirements (100-SysReq)

Configuration Changes

DATABASE Cleanup

To improve management, the reference database information is now recorded in a XML file and created automatically when GNA is first run. Indexes have been standardized (see standards).

  • Database column types, lengths and/or nullable properties, etc. when not in compliance with the ReferenceXML need to be cleaned-up.
  • Database Indexes should be deleted and recreated at each version upgrade. Please note that CUSTOM indexes will need to be recreated manually after a delete ALL!

NOTES:

  • Before starting the process, we highly recommend to review the CUSTOMIZED indexes to make sure they are still needed and that they do not create performance issues.
  • To make it possible to change field types in design mode when there is data in the column, you need to turn OFF the PREVENT DESIGN CHANGE option in MS SQL SERVER and make sure to turn it back ON afterwards!!!

CLEAN UP TIPS:

  • Delete the indexes first (ALL if you have reviewed custom indexes and can recreate them) than rerun the verify database. Invalid indexes can cause multiple errors.
  • Unused tables (ex: Boat, Aircraft, MV…) or empty tables (no records) should be deleted (quicker) as they will be created correctly at the next initialize.
  • Before making changes to the column types via the design mode, you need to turn off the option that ‘Prevents design changes in MSSQL SERVER‘. Remember to turn in back ON afterwards.

DOCUMENTATION

  • Detailed information on creating the windows environment, the upgrade process and examples of data corrections made to to an upgraded database.

700-upgrade108_to_60.pdf.
[700-upgrade108_to_60 documentation]

GOVERN STRUCTURE

The basic structure of Govern has changed. The profile is now the cornerstone of the setup and the security is setup directly in the OpenForms Designer.
The same table is used for USERS and Groups can be imported into ROLES in GNA. Note: Create the desired Structure on paper first to see if doing so will be effective.

FORMS
All forms need to be created using the new OpenForms DESIGNER.

PROFILES

Profile links need to be created for Batch Programs, Reports, Forms, Accounts Receivable, etc.

REPORTS
Report defined in the database (configured) are verified to make sure the SSRS or Crystal report exists in the standard or the custom folders defined.
Note: The user will be asked to delete invalid definitions the first time. Make sure report folders are setup correctly.

Step by Step

Update 10.8 to v6.0+ and create a deployment …

  1. Restore Database to MS SQL Server
  2. Create Deployment/Connection Key
  3. Download & Install Binaries
  4. Install GNA
  5. GNA Utilities – Verify Database
  6. Correct Errors — see MS SQL SERVER Option to allow
  7. GNA Utilities – Verify Database
  8. Review Users
  9. Review Departments
  10. GNA Import/Export – Import ….
  11. GNA Import/Export – Import Forms
  12. GNA Verify database (Always after an import)
  13. GNA System Registry for Reports
  14. GNA Create Profile (Forms, Reports, Batch Process (testbatch) ….
  15. GSM Synchronize
  16. GSM Import Departments (If desired)
  17. GSM Review Roles
  18. GSM Review Security (Applications, Forms, etc.)
  19. Open Govern and review the options
  20. Search, send to the treeview and open a form

 

Model Updater

IMPORTANT NOTE:
Model Updater has not been re-engineered for version 6.0. It is on the roadmap.

Troubleshooting

At any point, if there are problems, Govern VALIDATOR should be executed,

 

 

100-upgrade-GFWtoOF

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...

100-upgrade-OFtoOF

Upgrade from Govern 5.x to Govern 6.0

Overview

This page is intended for customers, business analysts and technical services to provide tools and tips when upgrading to Openforms 6.0 from a prior Openforms version or from Govern for Windows. Govern users that are upgrading from Release 5.1 to Release 6.0 will need to note the changes in the behavior of the Release 6.0 suite of applications. Click here for Upgrade Configuration Details.

Tips before upgrade

  • Prior to any upgrade, it is recommended that a complete backup of the database prior to copying or upgrading be performed.

Design Workflow Changes

The Model Designer (MoD) application is no longer a part of the suite. Forms are now designed with the OpenForms™ Designer (OFD). The Business Entity Designer (BED) is still used for designing Business Entities.

Database Changes

For Release 6.0, changes have been made to the structure of models used in the Model Designer (MoD) Release 5.1 and the new OpenForms™ Designer (OFD) Release 6.0. As a result of these changes, the databases that are used by Release 6.0 applications are not compatible. Govern applications that are prior to Release 6.0 will be referred to as legacy applications. Govern Databases created for use with releases prior to 6.0 will be referred to as legacy databases.
In order to assure the integrity of the 6.0 database, the Govern system will prevent the use of any legacy databases unless they have been created for, or upgraded to Release 6.0.

Legacy Applications

Release 5.1 Applications

The following Release 5.1 applications WILL NOT work with a Release 6.0 database.

  • Business Entity Designer (BED)
  • Query Tool (QT)
  • Security Manager (SM)
  • Model Designer (MoD)
  • Govern
  • Govern New Administration (GNA)

 

Release 5.1 Exceptions

Users attempting to set a Release 6.0 database as a Default Connection Key in the Connection Key Management form in the Release 5.1 Govern New Administration (GNA), will be presented with a warning indicating that they cannot select a database version that is greater than Release 5.1. No change will be made to the default connection key.
When a user tries to access any of the above applications, a warning message is displayed.

Release 6.0 Applications

Govern Release 6.0 applications will not run with a Release 5.1 or lower database. The following is a list of the Release 6.0 applications that will not work with a legacy database, i.e. a version that is less than Release 6.0.

  • Business Entity Designer (BED)
  • Security Manager (SM)
  • Query Tool (QT)
  • Open Form Designer (OFD)
  • Govern (Release 6.0)

Attempting to run any of the above Release 6.0 applications will result in a warning being displayed.

Release 6.0 Exceptions

Users attempting to set a Release 5.1 database as a Default Connection Key in the Connection Key Management form in the Release 6.0 Govern New Administration (GNA), they will be presented with a warning indicating that they cannot select a database version that is less than Release 6.0. If the user selects Yes, the system will run the Database Verification process and will update the selected database to a Release 6.0 version.

WARNING: When users select the Yes option, GNA will display the Database Verification form to perform a non-reversible upgrade to their database. After the process is complete, the NET_DB_VERSION column in (Table: USR_KEY_MASTER) is updated.

 

NOTE: If errors are encountered during the Database Verification process, the conversion to a Release 6.0 database will not be complete. Any errors will have to be addressed and the process repeated.

Upgrade Paths to Release 6.0

WARNING: Prior to any upgrade, it is recommended that a complete backup of the database prior to copying or upgrading should be performed.

Users that will be using Release 6.0 have two (2) paths to upgrade to Govern Release 6.0 applications:

OPTION 1 – Direct Upgrade

This path is one that will immediately upgrade your current installation database from Release 5.1 to Release 6.0. The database upgrade is irreversible and as such, a complete database backup should be made prior to the upgrade. Should it be necessary to roll back to your Release 5.1 database, the backup can be restored. The Deploy EZ application will be used to update the currently existing deployment. The deployment will consist of the Release 6.0 replacement applications.

NOTE: This Option 1 upgrade path will replace the Release 5.1 applications with their Release 6.0 versions.

 

Upgrade Steps for OPTION 1

  1. Open the Govern New Administration (GNA) Release 5.1.
  2. Use the Connection Key Management form to ensure that the default connection key is set to your Release 5.1 database; close the GNA application when done.
  3. Perform a complete backup of your current Release 5.1 database with your Database Management application.
  4. Update your current deployment with Deploy EZ; update the applications to the latest Release 6.0 versions.
  5. Run the Govern New Administration (GNA) Release 6.0.
  6. At the prompt, click Yes to perform the database update.
  7. When the process is complete, restart the application.

Upon completion of the process, the NET_DB_VERSION column in (Table: USR_KEY_MASTER) is updated. The database conversion is complete. Close GNA and restart the application.

OPTION 2 – Parallel Install

This Option 2 upgrade path is non destructive in that a new Release 6.0 Deployment is created; a name that reflects that it is a Release 6.0 is recommended. As with Option 1 above, a full backup of the Release 5.1 database is mandatory. In addition a new Connection Key (CK) must be created to reflect the existence of a Release 6.0 database. Installing the applications in the Release 6.0 deployment will not overwrite any existing Release 5.1 applications. The newly installed application will run independently of the legacy applications on a separate database.

NOTE: The Option 2 upgrade path will leave the existing Release 5.1 applications and database intact; as no upgrade is actually performed on existing Release 5.1 applications. The database upgrade that is performed is on a duplicate database that is created from a backup of the Release 5.1 version.
There is no synchronization of data between the old and new database; the 5.1 and 6.0 environments are independent of each other. If synchronization of data is required it will have to be performed by a qualified database administrator that is knowledgeable on the functioning of the Govern application and the database structure.

Upgrade Steps for OPTION 2

  1. Perform a complete backup of your current Release 5.1 database with your Database Management application.
  2. With you DB Management application, create a duplicate of the Release 5.1 database; rename with a 6.0 designation, e.g. mydbase_60
  3. Open the Govern New Administration (GNA) Release 5.1.
  4. Use the Connection Key Management form to create a connection key to the newly designated Release 6.0 database.
  5. Set the new connection key as the Default connection; close the GNA application when done.
  6. Launch Deploy EZ.
  7. Create a new deployment with a Release 6.0 designation.
  8. Create your deployment with the latest required Release 6.0 applications.
  9. Run the Govern New Administration (GNA) Release 6.0.
  10. At the prompt, click Yes to perform the database update.
  11. When the process is complete, restart the application.

Upon completion of the process, the NET_DB_VERSION column in (Table: USR_KEY_MASTER) is updated. The database conversion is complete. Restart your applications.

Batch Programs

Batch programs are now linked to profiles and as such will need to be recreated.
The USR_BP_MENU will no longer be used.

Configuration Re-engineering

Click here for more information.

 

 

100-upgrade-OFtoOF

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...

Govern for Windows Installation

Govern for Windows Installation

For use with OpenForms version 6.0

How to install

Download Govern for Windows full installation pack for 10.8

NOTE: Contact Govern Support for the address to download installation packs

Steps to Upgrade

Upgrade to the Latest Version of 10.8

The following are the steps to upgrade your database to the latest version of Govern for Windows Release 10.8.

  1. Copy the Govern for Windows Full pack 10.8 to File server; ensure that you also obtain the latest version of the Govern for Windows 10.8 Reference Database.
  2. Create the following folders
    • Bin
    • Bitmap
    • Documentation
    • Help
    • Install32_108
    • StandardReports
    • CustomReports
    • Scripts
  3. Unzip the packages in the download files.
  4. Create an ODBC connection to the database. (Use the the 32 bit ODBC Data Source Administrator)
  5. Configure a .INI file with your organization name and serial number obtained from Harris Govern Technical Support.
  6. Run Govern for Windows Updata Release 10.8.
  7. In Updata, create an MS Access attach table.
  8. Verify that you are using the latest version of the reference database, then run the Upgrade process.

At the end of the upgrade process, your database will have been updated to the latest version of Release 10.8; you may now proceed to the next step of upgrading to Govern V6.0.

Going from Version 10.8 to Govern V6.0

Having successfully completed the upgrade to the latest version of the Govern for Windows 10.8 database, You now need to create a deployment of the latest Govern V6.0 applications. The steps to upgrade to V6.0 are as follows:

  1. Created a V6.0 deployment with DeployEZ; during the deployment you will create the Connection Key to the Database.
  2. Install the Govern New Administration (GNA) V6.0.
  3. Allow GNA to perform its Pre-Upgrade Check.
  4. Restart GNA and run the Database Verification.
  5. Correct any database errors that GNA finds.
  6. Run the Database Verification process again.

After this process, you database will have been upgraded to V6.0. The following is a link to a more detailed description of the upgrade process.
Click 100-upgrade-GFW_to_OF.pdf for the document.

 

 

700-Install

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...