For Linux installations, click here.
For unattended command line installation, click here.
The Windows installer is provided in 2 modes:
- The Web Standalone installer - for online, quick, uncomplicated installations to single servers
- The Full Server installer - for offline installations with more setting and deployment choices and the option to install on multiple machines
The standalone, quick installation process is as follows:
- First, users must run the installer as an administrator on the target machine (virtual or physical). See details here.
- Next, users are asked to choose a location for the product installation after accepting the EULA. Choose a location with enough space for the installation files (approx 1.8Gb for the entire installation)
- Next, users are asked where the data directory will be located. Choose a location that can house temporary files, the data repository and the in-memory engine. An SSD is highly recommended.
- All other installation choices are ignored and the installer assumes that the entire product will be installed on the target machine together with the internal database repository and in-memory engine. After the files are downloaded and unpacked, several sub-routines will be completed and services started.
- At the last stage you will be prompted to provide the password credentials for the first user added to the system. The user name for this user will be your current system account name.
- After some basic system initializations, the installation is completed and you will be prompted to start the Desktop client. When logging into the client (desktop or browser) you will be asked to provide the initial credentials created in step 5 above.
The server installer is similar to the stand alone except there are options for how the product will be installed:
- After choosing installation locations, the user is prompted whether to install the entire product on a single machine or to choose different components to install (for multi-server deployments).
- The user can elect to install the database repository on the target machine using the internal PostgreSQL engine or use an alternative database instance (either PostgreSQL, Oracle or MS SQL Server).
- The user can elect to just deploy the internal web server engine or to use a 3rd party web server like Microsoft IIS.
- If a multi-server setup is chosen, the user will only be prompted to provide the first-user credentials when the system recognizes that the minimum requisite servers have been installed on the network. This is the Web Server, Run Time Engine and Router.