HVS32 Quickstart Guide EN

Aus Wiki - Heidler Strichcode GmbH
Zur Navigation springen Zur Suche springen

This guide gives you a short Introduction to all HVS32 services, their functions and requirements.

Please pay attention that maybe not every listed service is relevant for your individual project.

HVS32-Dispatch System

The HVS32 Dispatch System is the central part of your system, which can be upgraded with following services/interfaces/plugins. Depending on your project details, you will also find the installed services in your Windows Service Administration. Default Installationpath: C:\Heidler where all additional plugins/services will have their own subfolder. General System-requirements can be found here: system requirements You need to install a so called "Shippingstation" (German: "Packplatz") for each HVS32 Client (Workstation), those will have their own configuration for printers etc. You can find a manual for the client/shippingstation installation here: install a new client

Configuration of Interface ID's in HVS32

For the initial configuration of the HVS32 there are following important tasks:

- Definition of the "AuftraggeberID" (Mandator ID for each Sender/mandantor)
For each Mandator sender / mandantor you must define a so called "AuftraggeberID". In the import dataset you need to include the AuftraggeberID to tell the HVS32 with with Mandator you want to print the Label. Each Mandator has a configuration in the HVS32 carrier modules with it's own operatioal parameters (like carrier accountnumber, numberranges,...)

- Definition of the Dispatchtypes
For each carrier/shippingservice combination (e.g. UPS Express) you need to define a DispatchtypeID (German: VersandartID), which must be listed by you so that we can configure it at the initial configuration of the system. Example: DispatchtypeID=UPSEXP for the triggering of the shippingservice UPS Express See the manual for the configuration of Dispatchtypes here: setup dispatch types

- Preparation of the HVS32 Carrier Modules
At the beginning of each project we send Forms to you for each carrier. In those forms you need to enter all needed operational parameters for each Mandantor. Those parameters we need for the initial configuration of each carrier module. The configuration of the carriermodules will be done by us. Please send the forms to the corresponding Project Tickets to our support. Without those completed forms, we cannot start the implementation of the carrier modules.

- Installation of printers (only for "centralized polling" with HVS32 Monitoring service)
When you use the centralized polling (HVS32 running as a process only on the HVS32 server in the background with a Windows Service "HVS32 Monitoring Service"), you need to install the network- labelprinters on the HVS32 Server first.

HVS32 services/addons

In the next sections you see an overview for all possible HVS32 services/addons and a short description. Thease are Windows Services installed on the HVS32 server. Please pay attention that each project has it's own combination of services regarding to their process/needs, so there's not everything in relatiopn to your individual project.

Firebird Server - Default Instance

Important notes

  • installed as a Windows Service on your HVS32 Server, Servicename "Firebird Default Instance"
  • central Database service for the HVS32
  • needs to be running all the time
  • if the service isn't running, no HVS32 can be started
  • main database path: C:\Heidler\HVS32\Database\hvs32.fdb
  • if you use backupsoftware to handle the backup of your HVS32 Server, we recommend to stop the Firebird Database service prior your Backup. Please ask our support for details.

HVS32-Monitoring service

The HVS32-Monitoring Service is an addon service which starts an HVS32 shippingstation (most common Auto01,...) in the background as process on your HVS32 Server. It's the key part in a process for the "centralized polling". The HVS32-Monitoring is connected to the DataGatewayServer service, which is responsible for the dataflow in your interface to the hostsystem (erp/wms system like SAP etc) You can find a detailled description of the HVS32 Monitoring Service here: description HVS32 Monitoring

Important notes

  • installed as a Windows Service on your HVS32 Server, Servicename "HVS32 Monitoring Service"
  • needs a "logon" user in the windows service properties, this logon user should be an administrative service user of your domain which hase full access rights to all HVS32 Folders and to the printer drivers
  • HVS32Monitoring Service starts and monitors a HVS32 shippingstation (most time Auto01, Auto02,...) which is running as backgroundprocess on the HVS32 Server
  • if you need to change printer settings (or else) in the Station which is running within this HVS32 Monitoring service, you need to stop the service first!
  • if you stop the service, no labelprocessing will be done (because the shippingstation will be shut down)
  • the shippingstation which is running withing the HVS32 Monitoring service needs a HVS32 Workstation licence (concurrent license)

DataGatewayServer (DGS) V2 (ODBC)

The "DataGatewayServer V2" will be used to provide the interface ODBC.
It will be installed as a windows service.

important notes

  • The windows services "DataGatewayServer" and "DataGatewayGuardian" will be installed.
    • "DataGatewayGuardian" is responsible for monitoring the "DataGatewayServer".
  • The configuration of DGS can be found in the "settings.xml", which is located in the main directory (e.g./Heidler/DataGatewayServer/settings.xml).

General to the logs

  • HVS32ClientGateway.log (used in Automatic-Polling
    • Informations, which are transfered between DGS and HVS32 packing station.
  • ODBCSG.log (used in Automatic-Polling mode)
    • Informations, which are transfered between the ODBC-Database and DGS.
  • HVS32SG.log (used in interactive-mode delivery note data or address Data)
    • Informations, which are transfered between HVS32 and DGS.

DataGatewayServer (DGS) V3 (SOAP, SAP, E+P, JDBC)

The service "DataGatewayServer V3" will be used for the interface SOAP, SAP, E+P and JDBC.

important notes

  • Will be installed as a windows service "DataGatewayServer".
  • The configuration from the DGS is in the folder "config", which is located in the main directory. (e.g./Heidler/DataGatewayServer/config).

General to the logs
Logs which are named "server" for example "sapserver.log"

  • Enquiries, the DGS receives over the relevant interface. Used in automatic-Polling the hostsystem will be the "server". for example "sapserver.log". Used in interactive-mode delivery note data or address data HVS32 is the "server" -> "hvs32server.log".

Logs which are named "client". for example "hvs32client.log

Heidler ComManager

The service "Heidler-ComManager" is responsible for all connections to external servers, for example the upload of the daily closing.
So you only need one internet connection for daily closings from the HVS32 server.

important notes

  • Will be installed as the windows service "Heidler-ComManager".
  • Configuration is located in ...\HVS32\ComManager\ComManager-Configurator.exe
  • Connections between HVS32 clients and the server will use the port 9009
  • all ports for the used upload ways have to be enabled on the HVS32 (FTP 21, SFTP 22, HTTPS 443...)

Backup HVS32 Server

Under HVS32 Backup: General advice you will find an important advice in relation to the backup process for the HVS32 server.

Support HVS32

Within the active software support contract you can contact us through the phone number on your contract, or through our ticketsystem with the email support@heidler-strichcode.de, from monday to friday between 8am and 5pm.

  • Please always include your current systeminformation, you can create the information in the HVS32 under the point setup -> systeminformation(HVS32)
Abgerufen von „https://wiki.heidler-strichcode.de/w/index.php?title=HVS32_Quickstart_Guide_EN&oldid=2248“