This page provides administrators with a comprehensive overview of the system requirements for d.velop documents. The system requirements listed here apply to the operation of d.velop documents on-premises. They apply equally to the basic, business and ultimate editions.

d.velop AG conducts quality assurance tests at operating system level. Special hardware tests and certification processes are not performed. This applies to both physical and virtual hardware (VMware, Hyper-V, etc.). For the operation of d.velop products, we require the operating system on the hardware used to be working optimally.

On this page, you can find information about the following topics.

Dependencies on the product life cycle of other manufacturers

d.velop only supports system versions that are also supported by the system manufacturers. If the support of the manufacturer ends, the support of d.velop AG for this system ends as well. Support is usually provided until the extended support end date. You can find the information here:

With the introduction of d.velop documents, some older systems that are still being maintained are no longer supported (e.g. Windows Server 2012). All the systems listed here are supported until the end of the product life cycle.

Operating systems for d.velop server applications

The following operating systems are currently supported by d.velop server applications:

Operating systems for d.velop integrating applications

The following operating systems are currently supported by d.velop integrating applications:

Database management systems

The following database management systems are supported by d.velop software:

The following d.velop documents components also support IBM Db2 on Linux, Unix and Windows:

Other applications

Web browser

Here you can find an overview of the web browser versions supported by our software products. In each case, the latest version of the browsers listed below is supported. d.velop AG usually resolves incompatibilities in new web browser versions promptly.

Certificate

A certificate is required to ensure secure communication between the web client and the servers (https). The certificate should be issued by a certification authority (CA). We do not recommend using self-signed certificates. If you also want the system to be accessible outside your organization, the certificate must be issued by an official certification authority.

The certificate must have the following properties:

• Web server certificate.
• Signature hash algorithm: at least SHA-256
• Subject alternative name (SAN):
• Fully qualified domain name (FQDN)
• DNS aliases:
• Key usage:
• Digital signature
• Key encryption
• Extended key usage:
• Server authentication

Never use the host name without the domain name in a certificate. Use only the FQDN of the system or DNS aliases (also only as FQDNs). Please note that for the top-level domain (TLD) “.local”, a certificate cannot be issued by an official certification authority. The same applies to other reserved TLDs.

Certificate revocation lists (CRL) are required to verify validity. The CRLs must be accessible by both the client and the server. Certificates from an official certification authority use CRL servers from the internet.

The certificate is required together with the certificate chain in P12 or PFX format and must be password-protected. For the password, please use only Code Page 850 characters, because some products cannot import certificates with different characters in the password.

Groupware

The following groupware systems are supported with d.velop documents:

Microsoft Office

The following Microsoft Office versions are supported with d.velop documents:

Microsoft components

The following Microsoft components are supported: