MKG Server (on-premise or private cloud) System Requirements

General requirements

The MKG Server software must be installed on a dedicated server. This means that no other applications and/or server roles may be active.

We recommend that you always install MKG Server on a virtual dedicated server, because in our experience this offers scalability benefits, less downtime and simplifies management.

As a minimum requirement, the server must have 4 (virtual) CPU cores, 8 (virtual) CPU cores are recommended. The processor load is related to the number of users as well as the way in which the software is used; this may result in different advice.

Memory

As a minimum requirement, the server must have 16 GB of RAM, 32 GB of RAM is recommended. The required working memory is also related to the number of users and the way in which the software is used; this may result in different advice.

Harddisk

Required space

The minimum free space for the MKG services is 20 GB (OS Volume) and for the setup of the application and database > 100 GB (Data Volume). The actual required disk space on the data volume is determined by the database size as well as the location of the MKG document storage.

Disk speed

The volume on which the database will be located will be loaded at both read and write levels. There is a strong correlation here in the number of users as well as the way in which the software is used; this may result in different advice.

Determine the number of Mbps required to achieve the IOPS value: Mbps = (IOPS * 4KB per IO) /1024

RAID

We strongly recommend using RAID configuration, due to an increase in performance and higher data availability in the event of a defect. MKG recommends the use of RAID-1 or RAID-1+0. We strongly discourage the use of RAID-5 in combination with a database solution, due to a decrease in performance.

There are various RAID controllers on the market. The simple controllers usually only contain a read cache. This type has a negative effect on database performance. That is why we recommend a controller with battery backup and/or its own cache memory for read and write actions.

Using SSD (solid state drive) drives in such a configuration for at least the database volume is strongly recommended.

Operating system

We currently support the following operating systems:

• Windows Server 2022 DataCenter Edition, 64 bit
• Windows Server 2022 Essentials Edition, 64 bit
• Windows Server 2022 Standard Edition, 64 bit

• Windows Server 2019 DataCenter Edition, 64 bit
• Windows Server 2019 Essentials Edition, 64 bit
• Windows Server 2019 Standard Edition, 64 bit

Network

The network must support a minimum speed of 1 Gbps. It is recommended that a speed of > 1Gbps. In addition, the following basic settings are necessary:

• TCP/IP (Version 4), a fixed IP/V4 number.
• DNS V4 record available for MKG Client workstations.
• In addition to a mandatory forward lookup record, we also recommend ensuring correct reverse lookup in the DNS server of the network.
• An internet connection is required for the software to function correctly.

The following inbound and outbound rules apply in the firewall solution:

• TCP, 8080, application: Tomcat/PASOE instance.
• TCP, 8443, application: Tomcat/PASOE instance.

If the MKG App or MKG API is to be used, which requires external access, additional configurations may be necessary.

MKG API

MKG has integrated an API (REST) interface into its software that can be used to open up the ERP environment to mobile applications or other web applications. To be prepared for the future, every environment will be provided with this interface as standard. Details about the MKG API setup can be found here. The following is necessary to use this interface:

• Internal DNS record (for example: mkgapi.companyname.nl) that points to the LAN IP address of the MKG server.
• Commercial SSL certificate that can be applied to the above DNS record.
• External DNS record (for example: mkgapi.companyname.nl) that refers to the WAN IP address of the internet connection (optional).
• NAT rule port 8443 inbound to LAN IP address of the MKG server (optional).

Server setup

There are no mandatory settings for the hard disk volume setting. This section contains suggestions.

• C: Volume for the operating system (OS).
• D: Volume for the Progress database and an application folder called ”APPS”. Network users do NOT need direct access to this folder.
• In the D:\ <root> a folder \MKG_DB will also be created, in which the physical files of the MKG database will be placed. These files can only be read and written to by the database service process. Network users do NOT need direct access to this folder (in fact, this is undesirable).
• The BACKUP subfolder of D:\MKG_DB\ contains the daily backup files of the MKG database.

Backup

The database and application are delivered with an online backup tool. This tool only creates a backup file of the Progress database at a set time. It is strongly recommended to secure the database backup, the application folder and the document folder on an external medium (outside the server), so that in the event of a disaster they can be used for a restore job or reinstallation.

Configuring and actually executing an external backup does not fall within MKG's product definition.

Document management

MKG offers in its software the option for fast and efficient handling of linking and archiving documents in various MKG processes. You must provide a file location that is available to the entire organization (read and write rights). To apply this, a share (accessible via UNC) is the most obvious option in an on-premise solution.

Additional components

The following components must be installed or enabled prior to installing the MKG software:

• Microsoft Windows Firewall: managed or displaced by a commercial product, but not "disabled".
• Microsoft .NET 4.8
• Member of Domain (AD), if applicable.
• An administrator must be able to install system services in this host as local admin. Windows UAC and the domain controller (if applicable) must allow this.

Virtualization

We strongly recommend applying virtualization of the server environment, because of the scalability or fallback options in the event of a hardware defect.

Adjusting the settings below are necessary when using Microsoft Hyper-V:

• Disable the RSC option on the V-switch for the server where MKG is running.
• Disable VMQ on the V-switch.

Adjusting the settings below are necessary when using VMware:

• In the bios of the VM itself on which MKG is active, adjust the power setting to 'High Performance'.
• In VM options, adjust the Latency-Sensitivity setting to 'High'.