System requirements

From Wiki - Heidler Strichcode GmbH
Jump to navigation Jump to search

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. Support requests for not supported/unapproved operating systems could only be processed 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.

Supported Server Operatingsystems

  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2012 (R2)

Supported Client Operatingsystems

  • Microsoft Windows 10
  • Microsoft Windows 8.1 

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


 

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

 

Recommended system requirements for central polling

The following system requirements are estimated recommendations. Please make sure your server is scalable easily (VM), so you won't run into issues if you like to add new features or functionalities in the future.

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.

For the recommended system requirements we assume an installation with our default components.

Basic version with the following components:

  • HVS32 (shipping software)
  • 1x HVS32 workstation (processing of requests)
  • 1x HVS32Monitoring (monitoring service of the workstation)
  • DataGatewayServer (interface to the host system via REST, SOAP, SAP, JDBC, HTTP)
  • Com-Manager (interface to the carrier via SFTP, FTP, etc.)
  • Carrier-API (web service communication to the carriers)


For processing up to approx. 1000 labels per hour, we recommend the following system requirements:

  • Network: min. 100Mbit/s, recommended 1.000 Mbit/s
  • HDD: min. 50 GB (SSD)
  • CPU: 8 cores
  • RAM: 12 GB


If the shipping volume exceeds ~1000 labels per hour, we recommend the following scaling:

for each 1000 labels per hour:

  • + 2 cores
  • + 3 GB RAM
  • + 5 GB HDD(SSD)

When using additional features or functionalities, the server should be scaled as follows. Which applications are used should be clarified in the project meetings.

description application CPU cores RAM (in GB) HDD (in GB) scaling
additional interfaces to the host system via REST, SOAP, SAP, JDBC oder HTTP DataGatewayServer 2 2 2 per interface
DHL Parcel Leitcode 2 2 10 once
Status Event Messages (SEM) StatusdatenManager 1 1 5 for each 1000 labels per hour
SEM web view SEMWeb 1 1 15 for each 1000 labels per hour
database archiving DBArchivierung - - min. 50

(depends on how much data has to be archived)

once

(no further cores / RAM necessary, because for this process all services will be stopped)

automated daily closing MonitoringService 1 2 5 once
automated shipping notifications via mail AMAService 1 1 5 once
calculation of shipping costs + invoice audit HFMS 2

1

4

0,5

5

5

once

for each 1000 labels per hour

calculation of shipping costs + invoice audit + best price determination HFMS / SPM 4

2

4

1

5

5

once

for each 1000 labels per hour

 


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.

 

Default ports to share

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)