Installation modes: Which to choose when - 20.3

Automate Evolve Installation Guide
Version
20.3
ft:locale
en-US
Product name
Automate Evolve
ft:title
Automate Evolve Installation Guide
First publish date
2018
ft:lastEdition
2023-02-03
ft:lastPublication
2023-02-03T07:49:43.995000

Review the section below which addresses your type of installation.

This information is applicable if the Installer is not already installed (when executing the installer will deploy

the application).

  • Microsoft .Net 4.8.x
  • OS - Microsoft Windows Server 2016 or 2019
  • SAP GUI 750 or above

    If not already installed, Microsoft Visual C++ 2008, 2010, 2013, and 2019 redistributables will automatically be installed.

    The Installer must be executed by an administrator, and the Installer account must have one of the following:

    1. If the Studio Manager Server Installer database creator account has SQL Authentication, the

      4 Studio Manager Server connection string will contain the SQL authentication: Worker will not connect to SQL, and permissions and user access checks will not occur. In addition, DB checks will be skipped and Worker will proceed with the next step of the installation.

    2. If the Studio Manager Server Installer database creator account does not have SQL Authentication, the Installer account must have the security admin role on the SQL server used for installation and the DB owner role on the Studio Manager database.
@ Note:
  • Language cross combinations for server and database are not supported.

Example: Evolve Worker in English and Database in Japanese or vice versa is not supported.

  • The Windows language settings should be as per the respective OS.

Example: The Windows Display Language and Preferred Language should be Japanese in case of Japanese Locale.
  • A valid Studio Manager URL for Worker association
  • The number of Worker Services
  • A valid Worker Service identity that runs the Worker Service
  • Installation Location
Upgrade

If a previous version of Installer is already installed on the machine you are executing a newer version, Installer will detect the newer version and trigger an upgrade. Installing this will upgrade the deployed application. The Installer must be executed by an administrator, and the Installer account must have one of the following:

  1. If the Studio Manager Server Installer database creator account has SQL Authentication, the Studio Manager Server connection string will contain the SQL authentication: Worker will not connect to SQL, and permissions and user access checks will not occur. In addition, DB checks will be skipped and Worker will proceed with the next step of the installation.
  2. If the Studio Manager Server Installer database creator account does not have SQL Authentication, the Installer account must have the security admin role on the SQL server used for installation and the DB owner role on the Studio Manager database.

We recommend creating a backup before performing an upgrade.

The shuttle rule file is not retained. The upgrade process will replace it with a new file. Create a backup of your Shuttle rule file before proceeding with the upgrade.

During upgrade, database details are validated after Pre-Requisite check dialog. Installation is not aborted even if the validation fails.

@ Note: Only fresh installation of Evolve Worker is supported on Japanese OS. Upgrade of Evolve and Studio Manager on Japanese OS is currently not supported. 

5

  1. Modify

If the current Installer has already been executed and you want to modify the configuration, execute the same Installer again and select Modify to make the required configuration changes. Then, re-install the application.

  • If you change the website/ URL during the modification of the configuration/reinstallation, execute

Modify Evolve Worker Installer to add and support the new URL.

  • When you run the Worker Installer in modify mode, the service identity is picked from the registry. If you change the service identity manually after installation, the registry will not be updated; if you then run the Installer in modify mode, the correct service identity will not show. Do not change the logon account manually; always use the Installer for this process.

    The Installer must be executed by an administrator, and the Installer account must have one of the following:

    1. If the Studio Manager Server Installer database creator account has SQL Authentication, the Studio Manager Server connection string will contain the SQL authentication: Worker will not connect to SQL, and permissions and user access checks will not occur. In addition, DB checks will be skipped and Worker will proceed with the next step of the installation.
    2. If the Studio Manager Server Installer database creator account does not have SQL Authentication, the Installer account must have the security admin role on the SQL server used for installation and the DB owner role on the Studio Manager database.

6

The prerequisites are the same as the Fresh Installation prerequisites. Identify the configuration which needs to be modified.

We recommend taking a snapshot of your current VM state before proceeding with the modify process.

  1. Repair

If the current Installer has already been installed and you need to repair configurations, execute the same Installer a second time and select Repair.

The Installer must be executed by an administrator, and the Installer account must have one of the following:

  1. If the Studio Manager Server Installer database creator account has SQL Authentication, the Studio Manager Server connection string will contain the SQL authentication: Worker will not connect to SQL, and permissions and user access checks will not occur. In addition, DB checks will be skipped and Worker will proceed with the next step of the installation.
  2. If the Studio Manager Server Installer database creator account does not have SQL Authentication, the Installer account must have the security admin role on the SQL server used for installation and the DB owner role on the Studio Manager database.

    We recommend creating a backup before performing a repair.

  3. Remove or Uninstall

If the current Installer is installed and you want to uninstall the configuration and application, execute the same Installer a second time and select Remove.

Note: the DB will not be removed during the uninstall process.