Installation Modes: which to choose when - 24.1

Automate Evolve Installation

Product type
Software
Portfolio
Integrate
Product family
Automate
Product
Automate > Automate Evolve
Version
24.1
Language
English
Product name
Automate Evolve
Title
Automate Evolve Installation
Copyright
2024
First publish date
2018
Last edition
2024-07-22
Last publish date
2024-07-22T13:01:12.334902

Review the section below which addresses your type of installation.

This information is applicable if the Installer is not already installed – for instances when executing the installer will deploy the application.

System Requirements - Prerequisites

  • OS - Microsoft Windows Server 2016 or 2019
  • PowerShell 5.1 or above
  • IIS Administration PowerShell module
  • Microsoft .Net 4.8.x
  • IIS 10.0 or above
Component Installer screen label Min Version check Max version check
OS Operating system(2022 or higher) Server 2016 NA
SQL Server SQL server 2019 or higher 2017 NA
Powershell Powershell (5.1 or higher) 5.1 NA
IIS IIS (10.0 or higher) 10 NA
SAP GUI SAP GUI (8.0 or higher) NA NA
DotNetFramework Microsoft .Net Framework 4.8.x 4.8.0.0 4.9.0.0

If not already installed, Microsoft Visual C++ 2013 and 2015-2019 redistributable will automatically be installed.

The Installer account must have security admin and DB creator server roles on the SQL Server used for

installation. (For an upgrade, the Installer account must have the security admin and DB owner roles.)

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.
  • If SAP GUI is not installed, you will see this message: 'A supported SAP GUI version is required for server-side script execution, such as scheduled server and web form execution. It is not mandatory for installation.' Label changes have been made as per the latest release requirements on the Prerequisite Screen.

Installation - Prerequisites

We recommend that for each of the following you use unique entries.

  • Authentication type (Windows or SAML)
  • An existing or new farm
  • Evolve website name, port, protocol, SSL Certificate (for https), hostname
  • App pool name, user identity, username\password (for custom account)
  • Database server, database name, database authentication
  • Installation location

Note: Localized characters are not supported with Evolve Site hostname and Portal Hostname.

  1. Upgrade

    If a previous version of the Installer is already installed on the machine, the Installer will detect the newer version and trigger an upgrade. Installing will upgrade the deployed application.

    The Installer account must have security admin and DB creator server roles on the SQL Server used for installation. For an upgrade, the Installer account must have the security admin, DB creator, and DB owner server roles.

    Recommendation: create a backup before performing an upgrade.

    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.
  2. 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.

The Installer account must have security admin and DB creator server roles on the SQL Server used for installation. On the database, the Installer account used must have the DB owner role.

  • 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.

  • Message queues such as wsworkflow, wsreporting, wsinfra, and wsautorunfile are created by the server Installer. If you delete any of these, they should be recreated by running the Modify server Installer.

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

Recommendation: create a backup before performing a modification.

  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 account must have security admin and DB creator server roles on the SQL Server used for installation. On the database, the Installer account used must have the DB owner role.

    We recommend creating a backup before performing a repair.

  2. 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.