Install with a new Database

UAC Enabled
If UAC is enabled on the machine, when starting the EXE, credentials for a privileged user will be required, in order to properly install Flowster Studio.



For this guide we are going to perform a full Flowster Studio installation (all features).
In order to install the application with a new database follow the steps:

• Double click on the Flowster Studio Setup.exe file.
• The Flowster Studio Setup – Features dialog opens:

• The installer will provide 5 features that can be installed: Flowster Engine, Designer, Execution Agent, Web Portal and WebApps. Unchecking features will cause parts of the installer user interface to be disabled accordingly.
• Select the location where Flowster Studio will be deployed or leave the default one (C:\Program Files\Flowster Solutions\Flowster Studio)
• Click Next. The Database Settings dialog opens:

• Enter the SQL Server instance manually or select one by clicking the Browse button (a window with all discoverable SQL server instances on the network will be listed. Depending on the size of the network, this may be time consuming).
• Flowster Studio will create the Main database. By default, the FlowsterMain name will be displayed, but this can be changed.
• For a new tenant database, type in the Database Name in the associated field. By default, the FlowsterTenant name will be used. This value can also be changed.
  • NOTE: The installer will validate against using the same database for Main and Tenant.
• Select an SQL Authentication Type (Windows Authentication and SQL Authentication options are available).
• The user that authenticates to the SQL server (current identity or SQL user, depending on the authentication type that was selected) must have a Login on the server, with the following rights:
• If the FLOWSTER Studio databases do not exist, the authentication user will require at least db-creator rights.
• If the FLOWSTER Studio databases have been previously created, the authentication user will require db-owner rights on all the relevant databases.

In case of selecting an SQL Authentication, enter the SQL server username and its password.

• Please note the Only use SQL Server Authentication[…] checkbox that is enabled if one chose the SQL Server Authentication option.Ticking this checkbox will result in FLOWSTER Studio services to use Windows Authentication (with the Service User as identity) to connect to the databases, leaving only the installer to use SQL Authentication for its connection.
• Click Next. The Flowster Studio Users dialog opens.
• Starting with version 5.2, Flowster Studio can be installed on environments not part of a domain. Also optional is to disable the LDAP Connection on domain machines. In the following, we'll exemplify both cases.
• Use LDAP Connection unchecked (it will be unchecked and disabled if the machine is not part of a domain):
  • The LDAP Connection, Domain format for portal authentication areas and the Superadmin AD User option are disabled.
  • The Service User will be prefilled with the current running identity, if the machine is not part of a domain, or will change it's prefill value with "Localhostname\". Please fill in the local user that will be used to run the Flowster Studio services.
  • The Superadmin will only have the Custom User option available. Please fill in the details.
• Use LDAP Connection checked:
  • The Active Directory URL will be automatically filled with the currently connected domain server and the default secure LDAP port, but it can be manually changed with a new value.
  • The Use SSL checkbox actions will enable/disable the secure LDAP connection, and act on the LDAP server entry by automatically adding/removing the default secure LDAP port (636).
  • Flowster Studio also supports specifying an AD Site per Active Directory entry. The field is optional.
  • The AD User will be prefilled with the identity running the installer. Adjust the value if necessary and enter its password. The user will be used by the installer and for AD operations (e.g. validate the service user and retrieve the AD User superdamin details).
• Select the Domain format for portal authentication:
  • NetBIOS domain name (the adjacent edit box will be prefilled with the system one, but can be customized)
  • Fully Qualified Domain Name (the adjacent edit box will be prefilled with the system one, but can be customized). Please note that when performing a new installation of the main engine together with the Flowster Studio portals, the Windows Authentication option for the portals will be disabled, as it will not work with FQDN\username login.
• Enter the Service User (by default, the field will be prefilled with the identity currently running Flowster Studio Setup) and its password.

UAC Enabled
The Runtime User should be in the Local Administrators Group and have Log on as a service rights, in order to run the windows processes used by Flowster Studio (e. g.: the Flowster Execution Agent windows service will not retrieve the last score and it will not be able to support workflows executions on it).

• Starting with version 5.2, Flowster Studio also supports adding a database user as superadmin (Custom User), which is also the default option.
• Opting for a Custom User (please see screenshot above) will require the username, password and password confirmation, email and display name to be entered before continuing.
• Opting for an AD User:
  • Search by: a dropdown list of the user attributes that the installer will search the Active Directory by. The supported attributes are sAMAccountName, Name, Display Name or User Principal Name.
  • After selecting how the user will be searched by, insert a User Filter that the installer will search for.
  • Click Search.
  • After the Active Directory search finishes, the list below will be populated with the Display Name and sAMAccountName (in parentheses) of all the accounts matching the chosen criteria.
  • Select a user from the list before proceeding to the next step
• Click Next. The Flowster Studio Engine Settings dialog opens:

• The installer suggests default values for services ports. The entries can be changed manually.
• Insert a custom Tenant name or continue with the default value.
• Insert the number of users that will be required to mark a task as active (default value = 1).
• Select the Default tenant language from the adjacent combobox (available options are en-US and de-DE)
  • This setting will set the default language for the default tenant and, if selected with the main engine installation – the scenario presented here -, the Flowster Studio WebPortal's login page. Installing Flowster Studio WebPortal as a separate component will have the login page set to English.
  • This setting will only be enabled for main engine installations and upgrades.
• Flowster Studio will deploy a new RestAPI client and will create a new Flowster Studio Instance that will be used correlated with the RestAPI client for workflows staging.
  • Insert data for the RestAPI client:
    • Name (additional information in the notes below)
    • Description (additional information in the notes below)
    • User (Domain\sAMAccountName format)
    • Password
  • Insert data for the Instance:
    • • Name
      • Description
      • Folder name
      • Folder description
• Provide a location for the Centralized Repository Path or leave the default one. The activity libraries will be deployed by the installer to that location, which can be a local or a network shared one.

NOTES:

• If ther is a plan to deploy additional Flowster Studio Engines, Designers or Execution Agents on other machines, use a network shared location.
• The RestAPI Client Name or Description fields must contain the "restapi" particle for install time checks in the future.
• Click Next. The Flowster Studio components settings dialog opens:
• Insert a name for the Execution Agent Group. Default value = current machine hostname + "_ExGrp".
• The Execution agent name field exists only for information purposes, as it is hardcoded to the local hostname.
• Provide a custom Interactive Agent Port if desired. Default value = 5701.
• Insert a name and a description for the WebPortal client.
• A default value for the WebPortal Port (443) is prefilled. It can be customized to a port of your choice.
• Portal network share: Network Share path for uploaded files.
• By default, the installer will provide a default location for the Designer workspace location (where the Snippets and Workflows folders will be deployed).
• Click Next. The Flowster Studio components settings (for WebApps) dialog opens:
• Insert a name and a description for the WebApps client.
• A default WebApps Port (5008) for WebApps is provided. Feel free to customize if necessary.
• Click Next. The Flowster Studio SSL certificate settings dialog opens:

• Select the PFX certificate for the SSL communication:
  • Flowster Studio default certificate, deployed with the product, or
  • manually choose a different certificate (PFX only) and enter its password, or
  • choose to keep the existing (that were not unbound) SSL certificates. If none are attached, the default certificate will be bound to the Flowster Studio services ports.
• Click Next. The Ready to Install dialog opens:
• Under the Engine selection area, tick the checkbox if the engine selection should be enabled for Designer and Portal logins. Once checked, the Use DNS records for engine server selection will be enabled.
  • If the environment is setup as such, check the Use DNS records for engine server selection option and enter the DNS Records address.
• By default, the installer will enable the TLS v1.1 and v1.2 for .NET. The option can be unchecked as per your needs.
• In order to start the installation, click Install.
• A progress dialog will be displayed (windows installer), followed by a Result.
• The installer will create shortcuts for Designer, WebPortal and WebApps on the AllUsers desktop and StartMenu.