Skip to main content
Skip table of contents

Runtime Requirements

Hardware

The hardware highly depends on the number of agents as well as the type and size of projects, as well as whether the Runtime instance is running on Windows or Linux.

For Windows, the following specifications can be used as a guideline:

  • CPU: x86 at least 2GHz, 4 cores

  • Memory: At least 8GB.

  • Disk space: At least 30 GB available

For the following situations, you should expect extra RAM usage:

  • Runtime instances that are using File Masking,

  • Instances that will be executing templates from DATPROF Privacy with JSON Masking,

  • Instances that will be executing templates from DATPROF Privacy using (very) large seed files.

Operating System

Windows

Windows Server 2008 or higher

Linux

Most linux distributions can be used to run Runtime. In general, we recommend Ubuntu or Debian based distributions for the best compatibility and access to utilities such as PowerShell.

When using DATPROF Runtime in production, use a dedicated server or virtual machine.

This reduces the chance of users other than the Runtime user accessing the Service database.

Service database

As of version 3.17.0 DATPROF Runtime uses an internal HSQLDB Service database. This database is installed during Runtime installation in the DATA folder of DATPROF Runtime.

For more information about the Service Database check this chapter in the Administration section.

Environment database

Every DATPROF application is installed and operates in an "Environment", which in effect just means a SQL database. Various database archetypes are supported, and an overview can be found below. These are guidelines, and generally your mileage may vary when using deviating versions of our supported database archetypes.

Below the list of supported databases.

Database

Version

Oracle

Version 11.2 and later

Microsoft SQL Server

Version 2012

Version 2014

Version 2016

Version 2017

Version 2019 and later

PostgreSQL

9.5

9.6

10.5 and later

DB2 iSeries

7.2

7.3

7.4

7.5

DB2 LUW

9.7

10.5

11.1

DB2 for z/OS

12

13

14

MongoDB

5.0 and later

Microsoft SQL Server Additional drivers and tools

  • Microsoft Command Line Utilities 14.0 for SQL Server (Sqlcmd & Bcp)
    (download link)

  • PowerShell should be installed on the server running Runtime. We also use the Sqlserver module for Powershell, but this is included in the installation files as a dependency, so does not need to be enabled manually.

PostgreSQL requirements

To use PostgreSQL for DATPROF Subset the target database requires the enabling of a foreign data wrapper (FDW).

Enable this by using this command: CREATE EXTENSION postgres_fdw.

Consult the PostgresSQL documentation for details.

Product specific database Requirements

The Database requirements for the specific DATPROF Products can be found in the Requirements section of the product manuals:

License

You should have a valid DATPROF Runtime license, available through your local DATPROF Sales representative. (sales@datprof.com)

A license is granted to an organisation or a person and contains an expiration date.

Additional System Requirements

Ports

DATPROF Runtime uses 5 network ports on your system
Default ports used are:

Port

Purpose

7070

This is the main port to access your Runtime application.

9001

This is the main port for the service database. It serves as the repository where Runtime stores its metadata.

61616

This is the port that is used for ActiveMQ client-broker communication.

61613

This port is used to implement the STOMP protocol to connect to the ActiveMQ broker and exchange messages.

All port settings are configurable. Check the section Runtime defaults for more information about these port numbers.

Supported Browsers

To access DATPROF Runtime, a browser that supports WebSockets is required. Most modern browsers offer this functionality.

  • Microsoft Edge

  • Chrome

  • Firefox

  • Safari

Microsoft Internet Explorer is no longer supported.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.