Install_Upgrade without GUI – general information

• Before continuing, please review the Flowster Studio System Requirements.
• Launching Flowster Studio Designer with a user that does not have write access on the installation path will cause it to be unable to update the Activity Library from the Centralized Repository Path. In order to prevent this, it is recommended to install Flowster Studio deployments that contain the Designer feature to a path where the users have sufficient permissions.

Installing/upgrading Flowster Studio products without the aid of the User Interface application requires creating a transform file to personalize the settings.
The following two chapters will enumerate the required properties (ordered alphabetically) that have to be set for installing the Flowster Studio Main Engine and Flowster Studio Additional Engine and components, together with the formats and/or accepted values of the property values where clarifications are in order.

• Feature dependent properties will be under sub-bullets.
• Mandatory properties will be bolded.
• Observations under italic text.

In both cases, our recommendation is to create the transform files using the User Interface, which now has the option to only create the MST file, and not automatically go on with the installation. This way it would be easier to simply customize afterwards to other hosts specifications, and not start from scratch.
The same transform file will be used for all subsequent upgrades after the current version, with the two value exceptions that will be for the WEBAPPSINSERTUPDATE and WEBPORTALINSERTUPDATE, which, after the first installation (that will do the actual insert in the database) will have to be set to "update". – this is considering the same set of features will be deployed.

IMPORTANT:
Before upgrading a system that contains any of the additional Flowster Studio components versioned 4.x:

• Flowster Studio – Administrator
• Flowster Studio – Execution Agent
• Flowster Studio – Portal
• Flowster Studio – WebApps

Please keep in mind that the Flowster Studio 5.2 windows installer package only supports upgrading the Flowster Studio 4.x package natively, and not its components (see bullets above) as well.
Therefore, on the systems you're upgrading to the 5.2 versions of the additional components, first uninstall the individual components, and then proceed with the Flowster Studio 5.2 components installation, keeping the old property values. A recommendation would be to create the mst before uninstalling, so you'll be able to gather the old components parameter values (such as Client names, ports, etc).
The command line to install Flowster Studio without UI is:
Msiexec.exe /i <path_to_msi> /qb transforms=<path_to_mst>
The mst file can be generated using windows installer tools such as Orca, or generated with the installer UI and afterwards edited with Orca if necessary.