/
Flowster Studio Additional Engine and Components Installation

Flowster Studio Additional Engine and Components Installation


  • ADDLOCAL: Core,Designer,ExecutionAgent,WebApps,WebPortal The value is a comma separated list (no spaces) of the internal feature names that will be deployed. Eliminating one from the list will cause that feature to NOT be installed.Depending on these, several sets of particular properties will become optional.
  • DOMAINFQ: the fully qualified domain name.
  • DOMAINNETBIOS: the NetBIOS domain name.
  • INSTALLPATH: Folder path with the custom destination folder. If no customization is required, leave default (0). The custom path must end in a backslash.
  • LOCALPROTOCOL: the local protocol used for the services communication. http/https (case sensitive).
  • MAINRESTAPIHOST: host address the Main Engine RestAPI Service is configured to use
    • Use the exact value for the local address of the Main engine machine: FQDN or IP. Having the Main RestAPI service configured under FQDN and trying to connect to if via its IP address will fail.
  • MAINRESTAPIPORT: the Main RestAPI Service port.
  • MAINRESTAPIPROTOCOL: http/https. The protocol the Main RestAPI Service is configured to communicate with.
  • PREREQUISITESSUPRESSMSG: 0/1
      • if the value is 0, the installer will display a message box with the Flowster Studio 5.2 prerequisites that are not met.
      • If the value is 1, the installer will only log the information about the prerequisites that are not met.
  • RSAKEYPATH: the Flowster Studio RSA keys path. The file has to be exported from the Flowster Studio Administrator page.
      • Mandatory if the Flowster Studio RestAPI has been configured to use custom RSA Keys for communication.
  • SERVICEUSER: the identity that will run the Flowster Studio services.
      • Format: Domain\sAMAccountName or Localhost\username
  • SUPASS: the service user password.
  • SCHUSESTRONGCRYPTO: 0/1
      • Decides whether the installer will enable the TLS1.1 & TLS1.2 protocols on the machine. Default and recommended value: 1
  • TENANTNAME: the name of the default Flowster Studio tenant.
  • USEFQDNCONFIG: 0/1. Decides whether the communication addresses of the current machine's Flowster Studio services will be configured using the current machine's FQDN or IP address.


  • Core feature (the actual additional engine) related properties. Ignored if ADDLOCAL does not specify the feature.
    • CENTRALREPOPATH: The location where the Activity Library folder will be stored for Designer/Execution Agent updates. It is recommended to use a network shared path, especially if the deployment plan calls for Designer/Execution Agents to be installed to different machines.
    • EXTRAENGINE: 0/1. Decides whether or the current installation deploys a Main Engine or an Additional one. The value when installing an Additional Engine is 1.
    • LOGGINGPORT: the port used by the logging service (Flowster Studio Platform Health)
      • Default 5800.
    • OVERWRITECENTRALREPO: 0/1
      • its value will decide if the current installation will overwrite the files already in the Centralized Repository Path. See CENTRALREPOPATH.
    • RESTAPIPORT: communication port for the Flowster Studio RestAPI service.
      • Default 5500.


  • Designer feature related properties. Ignored if ADDLOCAL does not specify the feature:
    • DESIGNERWORKSPACEPATH: the Designer workspace location. Also, this is where the Snippets and Templates will be deployed. Default value: C:\ProgramData\Flowster Solutions\Flowster Studio\Designer{color}

      * ExecutionAgent
      feature related properties. Ignored if ADDLOCAL does not specify the feature:
    • EXECUTIONAGENTNAME: the User Interface sets it automatically to the local hostname.
    • EXECUTIONGROUPNAME: the name of the execution group name. Default value: local hostname + "_ExGrp"
    • INTERACTIVEAGENTPORT: The communication port for the Flowster Studio Interactive Agent. Default value: 5701
    • EXECUTIONAGENTTENANTNAME: The name of the tenant the Execution Agent will be attached to. Make sure the value is accurate, as the installer will use it to retrieve the tenantId for deployment.


  • WebApps feature related properties. Ignored if ADDLOCAL does not specify the feature:
    • USEFQDNAUTH: 0/1. Decides whether the users will login into the services using the full domain or short domain on the username field. E.g. xxxx.yyyy.zzzz\username or xxxx\username.
    • WEBAPPSAUTHENTICATION: forms/windows (case sensitive). The WebApps website authentication method.
    • WEBAPPSDESCRIPTION: the description of the Flowster Studio WebApps Service Portal.
    • WEBAPPSINSERTUPDATE: insert/update. If it's a new installation, with new databases, the value will be set to insert. Otherwise (preexisting Flowster Studio Main/Tenant databases), the value will be update.
      • The detection is done in the User Interface, so the user will have to decide and set these manually in the transform file if he/she starts from scratch or using an older mst.
    • WEBAPPSNAME: the name of the Flowster Studio WebApps Service Portal. Default value: WebApps
      • The value must be unique between the Service Portals deployed on a Flowster Studio Tenant. Please enter accordingly.
    • WEBAPPSPORT: the communication port used by the WebApps service. Default value: 5008
    • WEBAPPSTENANTANME: The name of the tenant the WebApps client will be attached to. Make sure the value is accurate, as the installer will use it to retrieve the tenantId for deployment.


  • WebPortal feature related properties. Ignored if ADDLOCAL does not specify the feature:
    • USEFQDNAUTH: 0/1. Decides whether the users will login into the services using the full domain or short domain on the username field. E.g. xxxx.yyyy.zzzz\username or xxxx\username.
    • WEBPORTALAUTHENTICATION: forms/windows (case sensitive). The WebPortal website authentication method.
    • WEBPORTALDESCRIPTION: the description of the Flowster Studio WebPortal Service Portal.
    • WEBPORTALINSERTUPDATE: insert/update. If it's a new installation, with new databases, the value will be set to insert. Otherwise (preexisting Flowster Studio Main/Tenant databases), the value will be update.
      • The detection is done in the User Interface, so the user will have to decide and set these manually in the transform file if he/she starts from scratch or using an older mst.
    • WEBPORTALNAME: the name of the Flowster Studio WebApps Service Portal. Default value: WebPortal
      • The value must be unique between the Service Portals deployed on a Flowster Studio Tenant. Please enter accordingly.
    • WEBPORTALNETWORKSHARE: the network share for the WebPortal uploads.
    • WEBPORTALPORT: the communication port used by the WebPortal service. Default value: 5600
    • WEBPORTALTENANTANME: The name of the tenant the WebPortal client will be attached to. Make sure the value is accurate, as the installer will use it to retrieve the tenantId for deployment.


Related content

Flowster Studio Additional Engine and Components Installation arguments
Flowster Studio Additional Engine and Components Installation arguments
More like this
Flowster Studio Additional Engine and Components Installation arguments
Flowster Studio Additional Engine and Components Installation arguments
More like this
Install Flowster Studio Additional Engine
Install Flowster Studio Additional Engine
More like this
Install Flowster Studio Additional Engine
Install Flowster Studio Additional Engine
More like this
Flowster Studio Main Engine Installation arguments
Flowster Studio Main Engine Installation arguments
More like this
Flowster Studio Main Engine Installation arguments
Flowster Studio Main Engine Installation arguments
More like this