System requirements
Operating systems
All operating systems, computer systems and hardware components, which have not been explicitly approved in this document, are to be considered as generally not approved. This contains for example all Linux or MacOS based computers and operating systems. Hotline requests of that kind will generally not be rejected, but only pocessed in a severely limited fashion. When using unapproved software or hardware there is no guarantee to solve any arising problem.
The following lists always assumes the latest service packs, service releases and updates, which are always required on both the client and server.
The recommendation on multicore processors does not mean, that HVS32 will control the processor load in its current version (multithreading). Based on experience a much more smoother operation is possible with appropriate systems.
Minimum system requirements
Server
- 2,6 GHz CPU
- 4 GB RAM
- 30 GB free hard disk space
- 100 Mbit/s network conntection
- Microsoft Windows Server 2012
- Microsoft Windows Server 2008
Further server types or operating systems on demand.
Client
- Intel Pentium III or similar AMD CPU
- 3 GB RAM
- 10 GB free hard disk space
- 800 x 600 color screen and color graphics card and 16 Bit color depth
- Microsoft Windows 7
- Microsoft Windows 8
- Microsoft Windows 8.1
- Microsoft Windows 10
Recommended system requirements
Server
- 2,8 GHz Quad-Core CPU
- 8 GB RAM
- 50 GB free hard disk space
- 100 Mbit/s network connection or better
- Microsoft Windows Server 2012 (R2)
- Microsoft Windows Server 2008 (R2)
Client
- 2 GHz Intel Pentium or similar AMD CPU
- 4 GB RAM
- 10 GB free hard disk space
- color screen with resolution 1280 x 1024 or higher
- Microsoft Windows 7 (service pack 1)
- Microsoft Windows 8
- Microsoft Windows 8.1
- Microsoft Windows 10
Recommended system requirements for central polling
Server up to 10.000 packages/day
4 CPU cores (1-2 CPU cores should be added, if many services like CarrierAPI, Leitcode(DHLDE), AMAService etc. are running on the server)
RAM: 8GB (2-4 GB RAM should be added, if many services like CarrierAPI, Leitcode(DHLDE), AMAService etc. are running on the server)
Network connection min. 100Mbit/sec
50GB free solid state drive space
Server from 10.000 packages/day
Number of CPU cores = number of HVS32Polling-Clients + number of services (e.g. Firebird, DGS, Leitcode, etc.) + 2 CPU cores for the operating system
RAM: Number of HVS32Polling-Clients in GB + depending on the number of services (Firebird, DGS, Leitcode, etc.) 2 - 4GB + 4GB for the operaring system and reserve
Network connection: depending on the volume of shipping and concurrently recieved and sent TCP requests from the DGS and to network printers min. 100Mbit/sec, 1.000Mbit/sec recommended
Depending on the number of HVS32Polling-Clients and services respectively the shipping volume, the number and size of log data varies. Therefore we recommend a solid state drive whith a free space of 50GB to 75GB.
We strongly discourage to set up a VM on a server where the drive performance can be affected by other VMs (e.g. data server), because this can lead to a massive performance hit concerning the HVS32 database service.
HVS32 networking
For the network operation of the HVS32, a shared program directory on the server is required. This share must be connected as a permanent network drive with a fixed drive letter on the client. The users need all file permissions in the HVS32 directory mentioned above. These requirements should be prepared by the administrator until the installation date. A bandwidth of 100 Mbit/sec or faster is required. If the bandwidth is not achieved or when using Wi-fi connections, we recommend using the HVS32 in terminal server mode. Since the entire system depends on the bandwidth actually available, special attention should be paid to this issue. Experience has shown that the availability of the network conntection and the actual data throughput can still lead to problems though.
We explicitly advise against a cross-site operation without a terminal server environment.
Windows Terminal Server / Citrix
The support for HVS32 in a Windows Terminal Server environment (RDP) is provided to the same extend as a default installation.
However in a Citrix environment we can not provide support for the environment itself.
For Problems at the terminal server or the administration, support can only be provided for the basic default Windows components.
Everything else such as network shares, printer drivers, file permissions and RDP/ Citrix specifix settings etc. remain the responsibility of your system administrator.
We strongly recommend that the installation and configuration process be attended by a system administrator. All HVS32 versions are tested intensely and in detail on the aforementioned operating systems.
However since it is impossible to adjust all eventualities in advance, we can not give you any guarantee for the accurate program execution on every customer system.
| FTP / SFTP | Ports 22 / 21 , respectively all ports that are required for a tansmission via FTP/SFTP. For passive FTP the ports for the UDP backchannel needed to be shared, too. |
| DNS | HVS32 must be able to resolve, FTP, HTTP, HTTPS oder SMTP adresses via DNS. |
| HTTP/HTTPS | HVS32 must be able to resolve and reach HTTP and HTTPD adresses, here the ports 80 and 443 are required (e.g. for carrier UPS) |
| SMTP | To transmit carrier files or send e-mail notifications the configured ports are needed. (default port 25) |
| Data Gateway Server | The HVS32 Clients must have access to the configured ports via DataGatewayServer within the network when using communication to the ERP system (Port 5030 for interactive processing and port 5034 for polling) |
| Leitcode | Port 9000 for Leitcode determination (only neccessary for DHL DE Road) |
| Monitoring service | Port 9034 on the HVS32 with deployed HVS32 monitoring service |
| Firebird database | Port 3050 for Firebird database connection |
| Heidler Carrier API | Port 9090 using the carrier web service connection |
| HVS32CommunicationManager | Port 9009 for communication with the ComManager (via REST) |
| ScaleService (REST) | Port 8100 for communication with the ScaleService (via REST) |