On this page, an overview and some tips of what is needed is given for the installation appointment. This page only contains information for the first installation. For updates please contact the responsible project consultant.
Server
Requirements
Please see this page for System Requirements .
- Requirements are fulfilled
Access
In order to install the ordered software to the destined environment, the installation team needs access to the server. This can happen by a one-time web session via e.g. Citrix or by a VPN access which also provides the ability to support questions faster than by a web session. Also, it has to be ensured that access to the target server is possible via Remote Desktop or SSH
- VPN access (preferred)
or
- WebEx on a computer
and
- Access to the target server
Rights
For the installation, it is necessary that the user which connects to the server has administration privileges. On windows server, a local administrator is required and on UNIX systems root privileges must be available.
- Windows: Local Administrator
or
- Unix: root privilege (eg sudo)
Packages
Availability
For the installation, it is necessary to download packages. It has to be ensured that packages can be downloaded with a minimum of 5000kBit/sec and placed on the server directly or by any protocol like sftp, samba, unc, ... If that is not guaranteed please ensure that an installation package is provided before the installation appointment.
- Internet access (min 5000kBit/sec)
or
- Installation package
and
- Ability to copy files on the server
Obtain license
If the installation is done by the company itself, make sure a support employee is informed and can provide a valid license after installation is completed. Otherwise, getting a valid license can take up to 48 working hours.
- Support employee is informed about the installation appointment and confirmed time and day
Database
Requirements
Please see this page for System Requirements for collation and rights on the database.
- Requirements are fulfilled
Access
In order to create the necessary database structure and values, it is required to access the database server via a database client. There are many ways to get access to the database and more clients which provide access to the database, it is just important that SQL statements can be sent to the database.
- Native SQL Statements can be sent to the database
Protocol and ports
Protocol
Since the system is a web-based application, HTTP or HTTPS is used to communicate with the application. When the application should communicate over HTTPS a valid SSL Certificate has to be available.
- If https should be used, a certificate is required
Please visit Architecture for further details.
Ports and Endpoints
By default, HTTP uses port 80 and HTTPS uses port 443. Before installation, it has to be verified that the used port is forwarded correctly and firewalls do not block this port and the necessary endpoints
- Firewalls and Proxies must not block traffic on used port to server
Please visit our Architecture page for further details and endpoints.
Modules
If it is planned that additional modules get immediately installed please refer to Module Requirements where every module can be found and what information is needed in order to get the module to work.