eserp system requirements (EN)

ERP software is as versatile as your company. The IT requirements are therefore very individual.

The following is an overview of the required hardware and software and of the supported operating systems and databases.

Principles

In general, the best practices of the particular manufacturers and third party suppliers apply. This starts with the selection of compatible hardware and optimum configuration of the firmware, through to proper installation of the operating system according to the documentation provided, and culminates with optimization of the software parameters to match the particular purpose for its use.

It is assumed that all maintenance and updates are performed in a timely manner.

Please contact us regarding variations or very specific requirements (Contact).

General information

Database, application and terminal servers can run on a server or each on their own machines.

Application server

Requirements Application server

	Minimum	Above 10 users	Above 25 users
Processor	At least 4 cores At least 2,4 GHz	At least 4 cores At least 2.9 GHz	At least 8 cores At least 3.5 GHz
RAM (working memory)	16 GB	16 GB	32 GB
Free hard disk space	50 GB*	50 GB*	150 GB*

*Depends on document management system usage

Software requirements

Requirements Application server

Minimum	Recommended
Windows Server 2016 Standard	Windows Server 2022 Standard

Additional software

Minimum	Recommended
Microsoft .Net Framework 4.7.2	Microsoft .NET Framework 4.8.x
DBExpress driver files for Firebird SQL Server (Version 4.10.15.0) DBExpress driver for MS SQL Server (Version 7.5.7.0) Visual C++ Redistributable Packages for Visual Studio 2010 SP1 Visual C++ Redistributable for Visual Studio 2012 Update 4 Visual C++ Redistributable Packages for Visual Studio 2013 Visual C++ Redistributable Packages for Visual Studio 2015 - 2019

Database server

Requirements Database server

es2000 recommends a Microsoft SQL database server.

Also see Selection SQL Server

Microsoft SQL Server (MSSQL)

	Minimum	Above 10 users	Above 25 users
Processor	At least 4 cores At least 2,3 GHz	At least 8 cores At least 2,4 GHz	At least 8 cores At least 3.5 GHz
RAM (working memory)	16 GB	Minimum operating system requirements plus the logical size of all active databases
Free hard disk space	25 GB	25 GB	50 GB

Software requirements

SQL server operating system (MSSQL)

Minimum	Recommended
Windows Server 2016 Standard	Windows Server 2022 Standard

Database system (MSSQL)

Minimum	Recommended
Microsoft SQL Server 2019	Microsoft SQL Server 2022

Firebird SQL server

	Minimum	Above 10 users	Above 25 users
Processor	At least 8 cores At least 3.0 GHz	At least 8 cores At least 3.5 GHz	At least 16 cores At least 4.0 GHz
RAM (working memory)	16 GB	Minimum requirement of the operating system plus the logical size of all active databases
Free hard disk space	25 GB	25 GB	50 GB

Software requirements

SQL server operating system (Firebird)

Minimum	Recommended
Windows Server 2016 Standard	Windows Server 2022 Standard

Database system (Firebird)

Is provided by es2000.

Terminal server

Requirements Terminal server

Maximum of 25 users per terminal server.

	Minimum	Above 10 users	Above 25 users
Processor	At least 4 cores At least 2.5 GHz	At least 8 cores At least 2.9 GHz	At least 8 cores At least 3.5 GHz
RAM (working memory)	25 GB	50 GB	125 GB
Hard disk drive	50 GB*	100 GB*	500 GB*

*No data is stored on the terminal server until the temp files are saved. However, we recommend that each user have approximately 20 GB of disk space.

Software requirements

Terminal server operating system

Minimum	Recommended
Windows Server 2016 Standard	Windows Server 2022 Standard

Web browser

Minimum	Recommended
Microsoft Edge	Google Chrome, Mozilla Firefox

Additional software

Minimum	Recommended
Microsoft .Net Framework 4.7.2 Microsoft Office 2019 SP2	Microsoft .NET Framework 4.8.x Microsoft Office 365 (32 bit, local)
DBExpress driver files for Firebird SQL Server (Version 4.10.15.0) DBExpress driver for MS SQL Server (Version 7.5.7.0) Visual C++ Redistributable Packages for Visual Studio 2010 SP1 Visual C++ Redistributable for Visual Studio 2012 Update 4 Visual C++ Redistributable Packages for Visual Studio 2013 Visual C++ Redistributable Packages for Visual Studio 2015 - 2019

Web server

Requirements web server

	Minimum	Above 10 users	Above 25 users
Processor	At least 4 cores At least 2.5 GHz	At least 8 cores At least 2,4 GHz	At least 8 cores At least 3.5 GHz
RAM (working memory)	8 GB	8 GB	16 GB
Free hard disk space	10 GB*	10 GB*	10 GB*

*After log file size more hard disk space may be needed.

Software requirements

Web server operating system

Minimum	Recommended
Windows Server 2016 Standard	Windows Server 2022 Standard

Web server additional software

Minimum	Recommended
Microsoft .Net Framework 4.7.2	Microsoft .NET Framework 4.8.x

Workstation PC / client

Requirements Workstation PC

	Minimum	Recommended
Processor	Intel Core i5 8th generation or comparable At least 2,8 GHz	Intel Core i7 11th generation or comparable At least 2,8 GHz
RAM (working memory)	8 GB	16 GB
Free hard disk space	25 GB	25 GB
Display	Resolution 1440 x 900 (Skale 100%)	Resolution 1920 x 1080

Software requirements

Workstation PC / client operating system

Minimum	Recommended
Windows 10	Windows 11 Pro

Web browser

Minimum	Recommended
Microsoft Edge	Google Chrome, Mozilla Firefox

Additional software

Minimum	Recommended
Microsoft .Net Framework 4.7.2 Microsoft Office 2019 SP2	Microsoft .NET Framework 4.8.x Microsoft Office 365 (32 bit, local)
DBExpress driver files for Firebird SQL Server (Version 4.10.15.0) DBExpress driver for MS SQL Server (Version 7.5.7.0) Visual C++ Redistributable Packages for Visual Studio 2010 SP1 Visual C++ Redistributable for Visual Studio 2012 Update 4 Visual C++ Redistributable Packages for Visual Studio 2013 Visual C++ Redistributable Packages for Visual Studio 2015 - 2019

Mobile devices

Requirements - mobile devices

iOS

iPad-(8th generation & newer),-iPad-Air-/-iPad-Pro,-iPad-mini-(5th generation & newer)

Windows

Windows 10 / UWP-enabled touch screen devices

Android

At least-Android 10, Samsung Galaxy Tab S7 recommended

Software life cycle

The smooth operation of es2000 software solutions is dependent on the security updates and bug fixes from the platform producers and third party software providers. es2000 is therefore aligned with their product life cycles. There is no guarantee that es2000 professional software will run on discontinued systems that are not subject to regular fault maintenance.

New products are normally enabled on the release date.

Decentralized connectivity

External users and branches are connected through a terminal server such as Microsoft Remote Desktop Services (RDP). The bandwidth demand can vary greatly depending on the quality settings that have been made. For comfortable operation on popular screen sizes we recommend about 512 kbit/s per user with a minimum upload rate of 10 Mbit/s. Particular attention must be paid here to the expected printout volume.

Operation in a computer center

All the program components and services of the es2000 software require direct local access to the SQL database. This means that it is not possible to outsource a part of the program (for example: only the IIS server for the es2000 web solution) to a shared server hosted by a computer center.

Technically there is no reason why the complete infrastructure cannot be operated in a computer center if this is permitted by data protection and IT security regulations. Access is then exclusively via remote desktop (RDP). However, the current pricing structures for managed Windows servers makes it advisable to switch to server housing of your own hardware and software,

Virtualization

Functionally there are no restrictions to operating the es2000 software in machine-oriented virtualization environments such as VMware ESX or Microsoft Hyper-V. Please bear in mind the slightly increased system requirements (usually an additional 10%) due to overhead, and only use hardware that has been certified for this purpose by the manufacturer.

Please also observe any further instructions and configuration recommendations from the particular provider. As well as Microsoft's Server Virtualization Validation Program (SVVP) and the recommendations of the Microsoft SQL Server Customer Advisory Team (SQLCAT), VMware in particular has published numerous white papers on best practice1 http://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-perfbest-practices-vsphere6-0-white-paper.pdf in SQL server virtualization, throughput optimization, and latency reduction.

es2000 Support will initially try to analyze and rectify problems that occur in the virtual environment. To eliminate the effect of virtualization (particularly with terminal servers) es2000 may request that you reproduce the problem on a physical reference system.

This also applies if performance problems or faults are apparent in third party components.

Overview of eserp services

This overview indicates the connections that exist between the individual eserp services.

The example shows the operation of the esweb server in a DMZ Demilitarized zone (demilitarized zone) A demilitarized zone is an independent network that acts as a security zone between an external network (e.g. the Internet) and the internal network. This security network contains a web server which has firewalls monitoring its communications, for example. and assumes the application of the complete product with the basic specifications.

es Business Server service

The es Business Server service is required for eserp program functionality and is therefore installed on a central server in the network (for example on the server with the eserp installation or the database server).

Server configuration (esServerconfig)

The es Business Server service is controlled centrally using the esServerconfig configuration interface. They are installed using a setup that is designed to allow services in the same release that are already installed to be updated by means of an assistant.

esBusiness Server - Requirements

The following requirements must be met for installation and operation of the es Business Server service:

• eserp users with administrative authorizations (see eserp Service users)

• Authorization to configure the es Business Server service

• Windows user with corresponding authorizations for certain functions required (see Windows service user)

• Sharing of ports and applications in the firewall (see Firewall sharing / Used ports)

eserp Service users

A Service User must be recorded for the Business Server in the eserp Settings under Settings | External programs | es2000 | es Business Server | Settings.

This personnel number is needed for the Contact and Service call actions so that it can be entered when these actions are automatically created. This allows you to see whether an entry was made by a user or by the es Business Server.

Authorization to configure the es Business Server service

The logged in user requires certain user authorizations in eserp in order to configure the es Business Server service using the esServerconfig program.

At least the following eserp authorizations / user licence must be present:

Windows service user

To control the es Business Server services, we recommend the creation of a separate domain user. This user can be named eserpAdmin, for example. Such a user requires various user rights to enable the es Business Server services to perform their various tasks.

The required user rights depend on the modules that are used. The following authorizations are currently necessary:

For further information please see the links / information given for each item.

Execute as service

The Windows user requires authorization to execute as a service.

https://docs.microsoft.com/de-de/windows/security/threat-protection/security-policy-settings/log-on-as-a-service

Also see eserp Service users

Network access

As the Business Server service communicates with other applications on the network, the Windows user requires network access.

Also see eserp Service users

Also see Firewall sharing / Used ports

Access to the drives / folders of the document management system (DMS).

Access to the contents of the DMS is exclusively through the Business Server service. Individual eserp users do not need authorization for the corresponding sharing of the DMS.

The service user requires authorization in order to access directory sharing:

• Read

• Write

• Edit

Also see DMS technical functionality.

Relevant for modules / functions

Document management

Sending Emails through the server (access to files from the DMS)

Receiving Emails (archiving of file attachments and original Email)

Access to Microsoft Reporting Services

Microsoft Reporting Services provide extended report evaluations through the Microsoft SQL server.

The appropriate setup must be completed in order to use Microsoft Reporting Services.

Access to the system documents through esweb

The esweb product enables the documents for a system to be accessed via the Internet.

A special feature is that, where necessary, documents that may be confidential can only be accessed through special security mechanisms. The advantage is that the documents are only present on the server temporarily and when required.

Authorization Email 'Send as'

To send Email using the Business Server service, the service user needs authorization to send Emails in the name of other users / departments (Send as).

https://technet.microsoft.com/de-de/library/Bb676368(v=EXCHG.141).aspx

Relevant for modules / functions

• Sending emails

Access to the Exchange mailboxes for appointment matching

Firewall sharing / Used ports

As well as the above-mentioned service user with the corresponding authorizations, the following shares are needed in the firewall for operation of the services:

Port 12161 (TCP)

Application

esBusiness server service (events)

Default

Port 12161

Port 12163 (TCP)

Application

es Business Server service (web service)

Default

Port 12163

Port 445 (TCP)

Application

esweb -> system documents

SMB access to the system documents from the esweb

Share application / service

Application

esnetsrv.exe (server)

The es Business server service (ESBusinessService.exe) communicates with eserp via dynamic ports (> port 1024).

Share application

Application

ESofficeNet.exe (client)

The es Business server service (esnetsrv.exe) communicates with eserp (ESOfficeNet.exe) via dynamic ports (> port 1024).

esweb

The optional esweb module provides fundamental esofficeeserp functionality in a web based interface.

Access to esofficeeserp data is online via the Internet and a browser. This enables you to work in many areas while on the move using mobile terminal devices (smartphone, tablet, notebook).

The esweb user interface view is automatically adjusted for the mobile device used. A mobile view with the main functions is available for smartphones / tablets especially for use by technicians.

esweb system requirements

The following software must be installed before esweb can be installed:

• Server operating system as per the eserp system requirements (EN)

• Microsoft IIS web server (Internet information services)

  At least Version 8 with ASP.Net support and other set features

  Also see Microsoft Web Server IIS

• .Net Framework at least Version 4.7.2 as per the eserp system requirements (EN)

• esBusiness server service (installed and set up)

esweb - required IIS features

The IIS components listed below represent the minimum requirements for running esweb. If additional IIS components are activated they do not have to be removed.

Web server

General HTTP features

• Default document

• HTTP Errors

• Static content

Health and Diagnostics

• HTTP logging

Service

• Static content compression

• Dynamic content compression

Security

• Requirement filtering

• Default authentication

Application development

• .NET expandability 4.8

• .NET expandability

• ASP.NET 4.8

• ISAPI extensions

• ISAPI filters

• WebSocket protocol

Management Tools

• IIS management console

esmobile (app)

The esmobile app requires various extensions to the database and logic on the server side. The following system requirements are needed.

These include:

• esweb set up and installed

  Please note the requirements for the particular esmobile version that are given in the App Store.

• SSL certificate recommended

   

  This must be a non private certificate for operation of the Windows esmobile app.

• Mobile devices (see eserp system requirements (EN))

esofficeeserp required settings

The following settings are needed in esweb / esofficeeserp:

esweb

Select one of the two options (Personnel Vehicle store or Personnel no. in Warehouse) under Settings | General | Service - Order -> Warehouse filter.

esofficeeserp

Assign a Vehicle store to every esmobile user / employee under Office | Personnel | Details II.

Exchange interface (esExchange)

The esExchange module is part of the esBusiness Server and is used to synchronize appointments and tasks between eserp and Microsoft Exchange. Synchronization settings can be made for each user to be synchronized. It is also possible to link to several MS Exchange servers.

Requirements for operating the Exchange interface of the es Business Server service

Microsoft

• Microsoft Exchange 2016 or later

• EWS (Exchange Web Services) pre installed and executable

   

  We strongly recommend the use of Autodiscover for communication.

  To see if this is possible without problems, perform a connectivity test for Microsoft web services under https://testconnectivity.microsoft.com/.

  [Connectivity tests for Microsoft Exchange web services -> Synchronization, Notification, Availability and Automated responses]

• SSL connection A certificate that is not self signed is needed for this.

• If load balancing is used, it is essential that the entire system converges under one URL (not one URL per user / mailbox!) If this is not desirable, an additional module (esMulti-Exchange) can be purchased, which allows connection to several Exchange servers.

• Consideration of other EWS parameters

• The Exchange user account must be a Full user Exchange user account with postbox and must have authorization to impersonate the staff to be synchronized. This role is called Application impersonation.

   

  This should be carefully discussed with your provider, particularly if a cloud based Exchange solution is involved.

eserp

• eserp Version 1.50 or later (additiional database script required)

• esBusiness server Version 1.50 or later

Additional Exchange parameters

To operate the esExchange interface additional settings of the Microsoft Exchange server may be necessary. These can be viewed on the Microsoft Help pages.

To make it easier to find the commands needed, we have summarized them here. These should be configured by your IT administrator by means of the Exchange Management Shell.

The information shown here can be adapted to suit your needs. The user: exchangeadmin or name: ESExchangeEWS are possible variants.

The parameters given below apply to all supported versions of Microsoft Exchange unless otherwise stated.

Impersonation

New-ManagementRoleAssignment –Name:EsExchangeEWS –Role:ApplicationImpersonation –User:esexchangeadmin

Additional

Get-ExchangeServer | fl name,edition,admindisplayversion

Outlook add-in (esOutlook add in)

System requirements

• Microsoft desktop / server operating system, see eserp system requirements (EN)

• Microsoft Outlook, Version see eserp system requirements (EN)

• Microsoft .Net framework, Version see eserp system requirements (EN) (Download)

• VSTO Visual Studio Tools for Office Runtime version 4.0 or above (download)

Service requirements

• esweb

  Also see esweb system requirements

   

  Additional licenses: esweb Office, esweb Contact; 2 Only required when using the Service Call functionalities.

• To upload documents you must first complete installation of the es Business server services including specification of the document paths. Service users of the esBusiness server must have authorizations for acess to the document paths.