Deploy Safewhere Admin When Doing Upgrade

Deploy Safewhere Admin When Doing Upgrade

Introduction

In the previous version, you need to use the re-configure feature to install the Safewhere Admin for an existing instance.
That additional step might be a problem if you have huge amount of instances to upgrade.
In this version, we provide an option to deploy Safewhere Admin when doing a normal upgrade. In addition, in order to save you some precious server memory,
we also ship a new setting that allows you to shut Safewhere Admin down when it is no longer needed.

Configuration

Identify Configuration

New setting "Idle Time-out (minutes) for the Safewhere Admin Application Pool" for creating a new instance.
create_an_instance

New settings "Also deploy Safewhere Admin" and "Idle Time-out (minutes) for the Safewhere Admin Application Pool" for upgrading an existing instance.
upgrade_an_instance

New settings "Also deploy Safewhere Admin" and "Idle Time-out (minutes) for the Safewhere Admin Application Pool" for mass upgrading existing instances.
mass_upgrade_instances

The idle timeout value is then set to the “Idle Time-out (minutes)” setting of the application pool of the Safewhere Admin instance in IIS.
iis-swadmin-idle-time-out

Identify CLI

Identify Configurator CLI always deploys the Safewhere Admin when creating or upgrading an Identify instance.

The default value of an Safewhere Admin instance's idle timeout is 20 minutes:

You can use the parameter --safewhere-admin-idle-timeout to specify a custom timeout value: