How to upgrade to Sentinet 6.4

Sentinet upgrade can be done in two ways:

  1. Traditional process of using Sentinet.msi installation package and User Interactive configuration wizards for Repository, Node(s) and Developer Portal configurations. This process is described below and supported by all versions of Sentinet.

  2. Automated (scripted) upgrade that uses PowerShell scripts and Sentinet template configuration files. This option can also be used to install and configure a new instance of the Sentinet and its components. Please refer to the Sentinet Installation Guide, Appendix A for more details on automated and scripted deployments and upgrades.

User Interactive Upgrade

To upgrade Sentinet to a newer version, the currently installed version has to be uninstalled and the new version has to be freshly installed. The new installation will then have to be attached (configured) with the existing Sentinet Repository database. If required by the new version, it will automatically update existing Repository database schema to the new database schema, which is done by the Repository Configuration Wizard. No Sentinet configuration data will be lost during the upgrade process. All physical and virtual services, their policies, access rules, behaviors and other configurations will be available immediately after the upgrade process is completed.

Follow the steps below to execute the Sentinet upgrade process:

  1. Uninstall current Sentinet version from all computer systems on which it is currently installed.

  2. Ensure the IIS Management console application is closed before proceeding to the next step.

  3. Install the new Sentinet version. Start from the machine(s) on which the Sentinet Repository Web Application (a.k.a. Sentinet Management Server) has to be installed.

  4. Upgrading Sentinet Repository Web application(s)

    Start Sentinet Repository Configuration Wizard and attach it to the existing Sentinet Repository database (select Use existing database option). The Sentinet Repository Configuration Wizard will automatically update the Repository database schema if required. Follow all other Configuration Wizard steps providing either the same settings as for the previous installation or change them as desired.

  5. Upgrading Sentinet Node(s)

    a. Start IIS Manager console and navigate to the IIS Application that used to have the older version of the Sentinet Node.

    b. Optionally: Delete the existing Sentinet Node's web.config file from the physical location that is mapped to the IIS Server Node virtual directory. If the old web.config is not deleted, Sentinet Node Configuration Wizard will later identify a version mismatch and will warn the user that the old web.config file will be automatically deleted.

    c. Launch Nevatech Sentinet Node plug-in in the IIS Manager console from the Configure Node icon.

    d. Select Create from the right pane Actions screen to start Sentinet Node Configuration Wizard that creates Sentinet Node in the current IIS Application.

    e. Select existing Node from the Repository Tree. This will re-attach the new installation of the Node to the previously created Node. The new Node will automatically receive all configuration information of the older Node and will be fully operational upon the completion of the Sentinet Node Configuration Wizard.

  6. Upgrading Sentinet Developer Portal Web application(s)

    Start Sentinet Developer Portal Configuration Wizard and attach it to the existing Sentinet Repository database and stand-alone Monitoring database (if stand-alone Monitoring database was used by the previous version of Sentinet). The Sentinet Developer Portal Configuration Wizard will automatically update database(s) schema if required. Follow all other Configuration Wizard steps providing either the same settings as for the previous installation, or change them as desired.