Maytas Hub Upgrade Guide

This document details upgrading an existing version of Maytas Hub to 5.28.9010.1.

Both Maytas and Maytas Hub must be upgraded to 5.28 concurrently as there are updates which are not compatible with earlier versions.

It is important to uninstall any previous versions of Maytas and Maytas Hub on your system, including old training or testing versions. Leaving old versions on your system can lead to increased security risks.

Update .NET Version to 4.7.2

As of this upgrade, Maytas Hub requires .NET version 4.7.2 to be installed on the Maytas Hub application server.

Instructions for downloading and installing .NET 4.7.2 can be found here.

Upgrade Maytas Hub

Extract Files

  1. On your Maytas Hub server, browse to the root of your Maytas Hub website and make a backup copy of the Maytas Hub folder (this is often found at C:\inetpub\wwwroot). If you are unsure of the exact location of the folder, please contact Maytas Support for assistance.
  2. In the original Maytas Hub folder, delete the bin folder and the Scripts folder.
  3. Browse to the Maytas Hub folder of the upgrade and open MaytasHub.5.28.9010.1.zip.
  4. Open the MaytasHub.5.28.9010.1 folder in the zip file and extract the contents to your Maytas Hub folder (the original, not the backup). Overwrite all existing files when prompted.

    Please note that it is the contents of MaytasHub.5.28.9010.1 that should be extracted, not the folder itself.

  5. Open IIS and restart the Application Pool associated with your Maytas Hub application.
  6. Each user should refresh their browser cache after the upgrade. Instructions for each browser are as follows:

Run Server Manager Updates

Maytas Hub SQL updates are included in the Maytas Server Manager updates. Please ensure that the Server Manager updates have been applied as per the instructions in the Maytas Upgrade Guide, even if you do not use Maytas.

Upgrade Stats Service

There is an updated version of the Maytas Hub Stats Service which should be installed. First, the current version must be uninstalled:

  1. On the server where the Stats Service runs, go to Start | Control Panel | Uninstall a program.
  2. From the list of installed programs, select Maytas Hub Stats Service and click Uninstall.
  3. Click Yes to the message that appears. You may also be prompted to close the Stats Service if it is running – click OK to confirm this.

Next, install the new version:

  1. Go to the Maytas Hub\StatsService folder of the upgrade.
  2. Run Maytas.MaytasHubStats.Installer.msi.
  3. Click Next, then click Next again.
  4. Enter the Database Name and SQL Server Name for the Maytas database and click Next. Please note that the SQL Server name must include the instance if it has one.
  5. Click Install. The Stats Service will now be installed.
  6. Click Finish.

Update Web.Config

The 5.27 release updated the Newtonsoft Json version from 12.0.0.0 to 13.0.0.0.

To update the Json version:

  1. On the server where Maytas Hub runs, browse to the root of your Hub website and open web.config for editing.
  2. Locate the following section:

  3. Change the version numbers of 12 to 13, so that the versions read as follows:

  4. Save and close web.config.
  5. In IIS, restart your Hub website.

Start Maytas Hub

Maytas Hub can now be started as follows:

  1. Open a web browser.
  2. Go to the following address:

    http://MaytasHubserver/instancename

    where MaytasHubserver is the name of the server where Maytas Hub runs, and instancename is the name of the Maytas Hub folder. The instance name is determined when the MSI installer is run (by default this will be MaytasHub). An example URL for a server called myserver would be:

    http://myserver/MaytasHub

  3. You will now be prompted to log in to Maytas Hub. Enter your Maytas Hub user credentials and click Log in.

Application Forms

If you use any application forms with Maytas Hub, it is important to test adding an applicant after the upgrade has been applied. If you encounter any issues, please raise a ticket on the Self Service portal as your database may require additional configuration.