Enterprise 6.6.x to 7 Upgrade

<< Click to Display Table of Contents >>

Enterprise 6.6.x to 7 Upgrade

Notes:

Please read this entire article carefully, and plan appropriately before beginning.

This article is for clients that are upgrading from an existing 6.6 installation.

Prior to upgrade, please review the release notes for hardware and software requirements and additional upgrade information.

Custom formats created for EDP or EDGE for 6.x versions will need to be recompiled to work with EQuIS 7. Please contact support@earthsoft.com for further information on recompiling the formats.

Starting with EQuIS Enterprise 6.4.1, recursive triggers must be enabled for the database. This can be enabled under the Options tab of the database properties in SQL Server Management Studio.

Requirements for standalone license databases have been modified and should be updated in v6.5. For more information and the script for creating an external license database, see the License Server Features and Management article.

 

Warning: Enterprise 7 does not support "local" license keys for self-hosted clients with per-core licensing for EQuIS Enterprise. When installing Enterprise 7, these "local" license keys need to be replaced with "network" license keys (which are stored in the ST_LICENSE table in the database). If you are using "local" license keys on your web/application server, please contact sales@earthsoft.com prior to upgrading to Enterprise 7.

 

Prerequisites

Microsoft SQL Server 2012, 2014, 2016, 2017, or Microsoft Azure SQL Database

Microsoft System CLR Types for Microsoft SQL Server for GEOGRAPHY data type

Windows Server 2012, 2012 R2, 2016

IIS v7 through IIS v10. The following have to be enabled in Windows Server Manager for EQuIS Enterprise to function:

Server Roles: Web Server (IIS) (installs with default selections)

Features: ASP.NET 4.5 or ASP.NET 4.7 (dependent on Windows Server version)

Server Roles > Web Server (IIS) > Application Development:

.NET Extensibility 4.7

ASP.NET 4.7 (this will enable ISAPI Extensions and Filters)

For additional guidance: https://docs.microsoft.com/en-au/iis/install/installing-iis-85/installing-iis-85-on-windows-server-2012-r2

As of build 7.0.0.19046, Microsoft .NET Framework v4.7.2 with ASP.NET is required.

Supported browsers: Chrome, Edge, Firefox

EQuIS Professional 7 must be installed prior to upgrading EQuIS Enterprise. Installation and Upgrade.

 

Back Up Files

 

Prior to upgrading, it is highly recommended that existing files and the database have been backed up.

Make a backup of your SQL database.

Make a backup of the Enterprise Installation Directory (\Program Files\EarthSoft\Enterprise6).

 

Upgrade Instructions

 

The EQuIS Enterprise 7 download links are available for download at the EarthSoft Community Center.

 

1.Download the EQuIS Enterprise 7 installer (.zip) from the Download Dashboard (Products> EQuIS Enterprise> 7).

2.Stop the IIS application pool EnterpriseAppPool.

3.Stop the EQuIS Enterprise 6 Workflow service under Windows Services.

4.Make a backup copy of your *.config files

a...\Enterprise6\bin\connectionStrings.config

b...\Enterprise6\bin\log4net.config

5.Uninstall the existing EQuIS Enterprise installation from the Windows Control Panel.

6.Extract the files downloaded in Step 1.

7.Run the EQuIS Enterprise 7 application (.exe) as administrator and step through the installation wizard.

8.Go to the extracted folder from Step 6 and copy the file widgets.equis.all.min.js. Place the file in the installation folder, which is usually C:\Program Files\EarthSoft\Enterprise7\assets\dist\js. This is only applicable to Enterprise 7 build 18212.

9.Update your database(s) with the equivalent version of EQuIS Professional using the steps outlined in the following article: Update EQuIS Database.

10.Restore the backed up *.config files backed up in Step 4.

a...\Enterprise7\bin\connectionStrings.config

b...\Enterprise7\bin\log4net.config

11.If you are not using SSL (aka HTTPS), you need to do the following:

a.Browse to your installation folder (e.g., C:\Program Files\EarthSoft\Enterprise7).

b.Open the Web.config file with a text editor (e.g., Notepad).

c.Find <httpCookies requireSSL="true" lockItem="true"/>.

d.Change it to <httpCookies requireSSL="false" lockItem="true"/>.

e.Save and close the file.

12.If you are running in a local IIS Server environment, it may be necessary to comment out the staticContent block in the Web.config file.

a.Browse to your installation folder (e.g., C:\Program Files\EarthSoft\Enterprise7).

b.Open the Web.config file with a text editor (e.g., Notepad).

c.Find <staticContent>.

d.Comment out the staticContent as seen below:

  <!--<staticContent>

     <mimeMap fileExtension=".json" mimeType="application/json"/>

     <mimeMap fileExtension=".woff" mimeType="font/woff"/>

   </staticContent>-->

     e. Save and close the file.

13.For Enterprise to correctly handle URL Rewriting in local (non-Azure) IIS, the machine hosting Enterprise will need the URL Rewrite Module installed and a registry key will need to be created. The URL Rewrite module can be downloaded from https://www.iis.net/downloads/microsoft/url-rewrite, the "UrlSegmentMaxLength" registry key needs to be a DWORD created in [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters] with decimal value: 00001000, as seen in the screenshot below.

Ent-Install_UrlSegmentMaxLength_Registry_Key

If you are running in a local IIS Server environment and the URL Rewrite Module is not enabled, you may encounter 500 server errors when navigating to your site. If so, it will be necessary to comment out the rewrite block in the Web.config file.

a.Browse to the installation folder (e.g., C:\Program Files\EarthSoft\Enterprise7).

b.Open the Web.config file with a text editor (e.g., Notepad).

c.Find <rewrite>.

d.Comment out the rewrite as shown below:

<!--<rewrite>

     <rules>

       Extracts JWT token from URL segment and converts it to query parameter

       <rule name="TOKEN">

         <match url="^token/(.+)/api/(.+)$"/>

         <action type="Rewrite" url="api/{R:2}?token={R:1}" appendQueryString="true"/>

         <conditions>

           <add input="{QUERY_STRING}" pattern="(.*)"/>

         </conditions>

       </rule>

     </rules>

   </rewrite> -->

e. Save and close the file.

14.Start the EnterpriseAppPool application pool in IIS if it has not already been started.

15.Open your web browser to your installed web application URL (e.g., https://localhost/equis7/default.aspx).

16.Login using an EQuIS Enterprise administrator account (default account is administrator/admin).

 

Warning: For security reasons, the default administrator password of "admin" should be changed immediately after initial login is successful.

 

17.Append "action=deploy" to the URL to complete the deployment step. (e.g. https://localhost/equis7/default.aspx?action=deploy). You should see a list of files that were successfully processed as shown below:

 

Ent-Deployment_Files
 

18.Start the EQuIS Enterprise 7 Workflow service under Windows Services.

19.Navigate to the web application URL (e.g., https://localhost/equis7/default.aspx) to use EQuIS Enterprise.

20.If configuring Windows Authentication (LDAP Authentication), modifications are needed in the web.config file. See Using LDAP Authentication for more information.

 

Note: The \Enterprise7\App_Data folder contains the original installed widget, dashboard, and ST_CONFIG.DATASET deployment files. These can be copied from this folder into the \Enterprise7\deploy folder if any/all of the dashboards, widgets, or other files need to be deployed again. To deploy, append "action=deploy" to the Enterprise URL (e.g., https://localhost/equis7/default.aspx?action=deploy).