Updating HIFIS Versions
When updating HIFIS from one version to the next, there are several steps that should be carefully followed to ensure the smoothest process.
Before You Update
Before you update your HIFIS version on your production site (live instance), it is strongly recommended that you first test the version and ensure that you are aware of the impacts of updating. These impacts could include, but are not limited to:
- New modules
- New, removed, or modified fields on existing modules
- Changes in behaviour to some features
- Database structural changes which may cause some reports to stop working
- Bugs or other software issues
The best place to start in understanding the impact is to read the release notes for every version in between your current version and the one you're updating to, including the notes for the version you're updating to.
For example, if you're updating from 4.0.60.1 to 4.0.60.4, you should read the release notes for 4.0.60.2, 4.0.60.3, and 4.0.60.4.
Then, once you have a pretty good idea of what changes to expect, test out those areas in HIFIS., You can do that by either installing HIFIS on your test/sandbox/development site, or by using the national test site at demo.hifis.ca. It's particularly important to test the areas where your business will be impacted.
Once you've tested and have more data, you can make an appropriate plan. For example, you might need to re-train some staff, or have lots of communication in place, or choose to skip this version.
Getting Ready to Update
In order to update your software, first download and extract the desired HIFIS files onto your server. The latest version of HIFIS is always found at https://support.hifis.ca/software_release-version_du_logiciel/.
Note that there are always two components to download: the HIFIS Database Update Files and the HIFIS Software Update Files. Be sure to download and extract both of them.
For example, in the screenshot below, the HIFIS Database Update Files are labelled HIFIS_DB_60_Update (v62)
, and the HIFIS Software Update Files are labelled HIFIS_4.0.60_Complete (4.0.60.4)
.
Also download the Instructions file that is relevant for you. For example, if you currently had HIFIS 4.0.59 and wanted to update, you'd look at the line labelled "Using HIFIS 4.0.59 or later" and download the file called ReadMe_60_from_59.txt
.
Read the Instructions file. Depending on the version, it may contain instructions to update your web.config
file(s), which is something that should definitely not be ignored.
Once you have downloaded all the files and have read the Instructions file, you are ready to proceed with the update.
Your next step should be to inform your users about the expected downtime. Depending on the update, it's probably a good idea to schedule a 3-hour window in which HIFIS will be unavailable. The update can usually be completed in far less time, but it's good to give yourself a buffer, especially on your first few updates.
Updating HIFIS
In order to actually update HIFIS, access your server and locate the downloaded update files and the folder in which HIFIS is installed (in wwwroot). Then, follow these steps in your HIFIS website folder:
- Delete the contents of
HIFIS.Web\bin
- Delete the contents of
HIFIS.Domain\bin
- Optional: Delete the contents of
HIFIS.Web\ELMAH
, unless you particularly want to keep them - Copy the contents of your downloaded HIFIS Web folder to
HIFIS.Web
- Copy the contents of your downloaded HIFIS Domain folder to
HIFIS.Domain
- If you have your HIFIS.Domain application inside the HIFIS.Web application in IIS, then copy the following files from HIFIS.Web\bin to HIFIS.Domain\bin:
Elmah.dll
Microsoft.web.infrastructure.dll
System.web.helpers.dll
System.web.mvc.dll
System.web.webpages.dll
System.web.webpages.razor.dll
- If you are using two-factor authentication, you will also need to copy some files to
HIFIS.Domain\bin
, but which files depends on your configuration. - Open your
HIFIS.Web\web.config
file and make any changes listed in the Instructions file - Open your
HIFIS.Domain\web.config
file and make any changes listed in the Instructions file
Your HIFIS files have successfully been updated, but HIFIS will definitely not work at this point because there is a mismatch between the database version and the file version.
Now you also need to update your database. To update your HIFIS database, follow these steps:
- Open the
readme.txt
file within the HIFIS Database Update Files. It contains roughly the same instructions as are outlined below, straight from the developers. Open the
Update(XXXX).sql
file in SQL Server Management Studio (SSMS). There should be many files labelled PartialUpdate but only one just labelled Update. For example, in the screenshot below, the file is calledUpdate(v52-60).sql
In SSMS, enable SQL Command Mode by going to Query > SQLCMD Mode
- Where it says
SETVAR DBName
, enter the name of the database you wish to update, in quotation marks. See example below. Where it says
SETVAR RelativePath
, enter the file location of the folder you extracted the HIFIS Database Update Files to, in quotation marks. See example below.- Follow any additional instructions in the
Update(XXXX).sql
file, if present. - Parse the command.
- If the command was successfully parsed, Execute the command.
- Once the command has completed successfully, check the Database Properties > Extended Properties for a property named
HIFIS_DB_Version
. Verify that the Value of this property is what you expected.
Congratulations, you've theoretically updated HIFIS successfully. Just a few more steps:
- Open Internet Information Services (IIS) and restart your website. You may need to stop, wait ten seconds, and then start, instead of just clicking the restart button.
- Browse your website. It is normal and expected for it to take longer than usual to load for the first time after an update, so be patient.
- Once HIFIS loads, verify that the version number in the right of the footer is as expected.