kenaflow can be installed multiple times on the same computer. Every installation of kenaflow on a computer is called an instance.
It is not relevant which program versions of kenaflow are installed on parallel machines.
We chose a very simple setup mechanism for kenaflow to easily enable the installation of different versions.
Its almost a "copy setup". The only thing that is done only in the installer is to write a key into the Windows Registry. This key contains the binary location of the kenaflow instance.
The following instructions must be carried out separately for each instance of kenaflow. If there are several instances on the same computer, make sure that different installation directories are used.
It must be ensured that all prerequisites for the installation of kenaflow are met.
After installing the prerequisite software components, you can proceed with the installation of kenaflow.
- Download the setup as a ZIP file from the following address:
- Standard Edition: https://kenaflow.blob.core.windows.net/release-4-0/kenaflow.latest.zip
- Developer Edition: https://kenaflow.blob.core.windows.net/developer-4-0/kenaflow.latest.zip
- Free Edition: https://kenaflow.blob.core.windows.net/free-4-0/kenaflow.latest.zip
Unzip the file into a folder of your choice.
Start a command line (
cmd.exe) as administrator ("Run as Administrator"). Do not use "PowerShell" because the installer will not run if a running process "powershell.exe" or "powershell_ise.exe" is found on the computer.
Change to the folder to which you have unzipped the contents of the ZIP file.
--installparameter and, optionally, the
-d <path>parameter to specify a destination directory.
The installation is being carried out.
Finally, the setup opens the global configuration file of the new kenaflow instance in an editor (typically
The global configuration file only applies to this instance of kenaflow. So if you have more instances of kenaflow on the same computer, they each have their own global configuration files.
Now proceed with Basic Configuration.
Complex Scenarios - Some Notes
In advanced setup scenarios, e.g. when the installation is completely automated, it is possible to use a ready-made global configuration file by specifying it with the program switch
--configfile <file-name> during installation.
If the specified configuration file contains a "blank" instance ID (
00000000-0000-0000-0000-000000000000), setup will generate a new one. If the instance ID in the specified configuration file is not "empty", then this ID will be used.
It is possible to prevent the opening of the editor at the end of the installation with the
--noeditconfig program switch.