Upgrades and Migration

 

Before upgrading from an older version of EDG, consult this documentation for migration tasks that might apply to your upgrade. The migration documentation keeps your data and the EDG application functioning correctly after an upgrade, please pay close attention to those details. You can upgrade from any previous release straight to the current release, but you’ll need to use the migration documentation starting at the version you’re currently on and following along to current release. For example, if you upgrade from version 6.3 to 7.0 you’ll need to follow the migration notes for 6.3 to 6.4 and 6.4 to 7.0.

Migration Instructions

Please make sure to take backups of everything (workspace, database, tomcat installation, etc.) first. If you need to, take screenshots of your setting on the Rights Management page. Have your credentials and connections strings/URLs handy for Explorer, RDBMS and S3 connections. Also upgrade on your test/development environment successfully before the production environment gets upgraded. This is important when testing customizations to the UI or models especially. 

In EDG 7.0, TopQuadrant has made improvements to the underlying architecture to remove outdated technologies. This was a necessary change for the stability of the product. With this, we have modernized our deployment process as requested by customers. You will not be able to use your existing web.xml or secure storage. Please make sure you read and follow the migration instructions prior to starting this process. 

Steps to upgrade from EDG 6.4 using the setup.properties file:


• Ensure you are running on Java 11
• Stop Tomcat, make sure the process is fully stopped
• Backup and remove the /edg directory and edg.war file
• Place the new edg.war into the webapps directory
• Clear the /work, /temp directories
• Copy the file called edg-setup.properties from the topbraid-edg7.0.zip download into the
tomcat root directory (or location readable by tomcat). Modify the parameters in the file to
match your existing configuration. Workspace location and vault location can be changed if
desired.
• Set the system property edg.setup for Tomcat to the full path of edg-setup.properties. This can
be done in various ways, for example by editing Tomcat’s conf/catalina.properties file. For
example: edg.setup=/var/lib/tomcat9/edg-setup.properties
• Move existing workspace to the new directory/path if a new path was specified.
• Start Tomcat
• In EDG, Enter License and then navigate to Server Administration
• In Rights Management, make sure security roles are correctly set for Any_Role, administrator,
etc.
• If you are using Explorer, S3 credentials, Auto Classifier, etc. you need to re-enter the credentials
to match what you had prior in Server Configuration. Any secure storage credentials need to be
re-entered.
• Now navigate to the home page of EDG. Setup is complete. From now on this file will act as the
source of your configuration settings. Config.ttl is no longer used for the information contained
in the setup file.
• Note: If you are using RDMBS please restart your server once setup is complete.


Steps to upgrade from EDG 6.4 using the interactive deployment wizard:


• Ensure you are running on Java 11
• Stop Tomcat, make sure the process is fully stopped
• Backup and remove the /edg directory and edg.war file
• Place the new edg.war into the webapps directory
• Clear the /work, /temp directories
• Start Tomcat
• Navigate to EDG, this should detect you need to setup configuration and present a page with an
option to use the interactive setup. Launch this option
• Fill out all the configurations to match your previous installation including the workspace
location.
• Hit the Restart EDG button after submitting the form.
• Navigate to EDG home once the application restarts to log in. Initial deployment and setup is
now complete.
• If you are using Explorer, S3 credentials, Auto Classifier, etc. you need to re-enter the credentials
to match what you had prior in Server Configuration. Any secure storage credentials need to be
re-entered.
• Note: If you are using RDMBS please restart your server once setup is complete.

After this follow any of the migration steps that are required after upgrading and test this development server thoroughly before upgrading your production environment. If your license has expired, you will need to install your new license before upgrading.