Update DataGatewayServer V3 (DGS V3)

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

In this description, you will find all the necessary information to update a DataGatewayServer V3 (DGS V3). Please read this carefully. For any questions, please contact support directly at (support@heidler-strichcode.de)

Directory Name / Service Name

The DGS V3 is typically installed in the Heidler directory as DataGatewayServer / DataGatewayServerV3 / DataGatewayServer_<InterfaceName>. In older projects, it may also be found under Heidler\HVS32. The name of the Windows service corresponds to the name of the installation directory.

Compatibility

  • The DGS V3 (Version 3.x.x) is not compatible with the DGS V2 (version 2.x.x). These are two different applications. An update from DGS V2 to DGS V3 is not possible. The DGS V3 must be newly installed, and the configuration must be set up manually. Please contact support for assistance.
  • Due to the constantly expanding interface, the WSDL / XSD may change after a DGS update for SOAP-Interfaces.
  • When using a Firebird database, only Firebird version 2.5 or newer is supported from version 3.6.610 or newer.
  • When using an H2 database, versions 3.8.1.671 or higher are not compatible with older versions of the DGS.
  • From version 3.8.x.x or higher, the DGS V3 is delivered only in 64-bit. Third-party components like SAP-JCO or JDBC drivers used must also be in 64-bit from this version onwards. When updating an older version of the DGS, a notification will appear in the process. Please read it carefully. Ignoring this may lead to data loss, malfunctioning behavior / inoperability of the application.
  • The update from versions 3.5.x.x or lower should only be performed by support. Please contact us regarding this.
  • With DGS version 3.7.0.634, the default charset for the E+P interface plugins changed from CP273 to UTF-8. In older versions, this charset is not present in the configuration file, so it will be overridden by the new UTF-8 charset configuration. If this interface is in use and an update from an older version has been made as mentioned, the configuration should be checked and corrected, or the update should be performed by support.

Third-Party Components

Depending on the used interface, the DGS V3 relies on third-party components. These can typically be found in the main directory of the DGS V3.
These interfaces include:

  • SAP RFC / SAP IDoc
    • Required components: sapjco3.jar, sapjco3.dll, sapidoc3.jar
  • JDBC
    • Required components: JDBC drivers (e.g., mysql-connector-java-X.X.X.jar, ojdbcX.jar, mssql-jdbc-X.X.X.jar, jt400.jar)

If you are using a third-party component, a notification will appear during the update of older versions if needed. Please read it carefully.

Update Duration / Downtime

Since the DGS V3 is a core component of the interface between the shipping system HVS32 and your pre-system / host system, at least 30-45 minutes of downtime should be planned for the update so that appropriate actions can be taken in case of an error. No processing is possible during the update.

Dependencies on Other Heidler Applications

The DGS V3 has a dependency on the shipping system HVS32. The HVS32MonitoringService application (not the HVS32MonitoringServiceLight) may be involved. If HVS32 is not reachable, requests (printing, cancellation, loading, daily closing, etc.) cannot be forwarded.

What Needs to Be Done After the Update?

During the update, the Windows service is automatically stopped. It does not start automatically after running the setup. This must be done manually.

How Do I Check if the Application is Functioning Properly After the Update?

After the Windows service has been restarted, the DGS logs should be checked. These are located in the main directory in the Logs subfolder.

dgs.log: This log records the start / stop of the Windows service as well as the individual interface modules.

dgserror.log: This log contains all application errors that occurred (not errors that occur during processing, e.g., that the shipping method ID is unknown in HVS32).

Check both logs to see if the modules loaded successfully and if any error messages appear.


Further logs:

The DGS consists of at least one server and one client module. In the Automatic-Polling process, the client module is always an hvs32client. The hvs32client.log records the communication between the DGS and HVS32. The server module corresponds to the respective interface module you are using (e.g., SOAP / REST / JDBC, etc.). In these logs (e.g., restserver.log), you can trace the communication between the host system and the DGS, i.e., all incoming and outgoing messages.

In the Interactive Processing, the roles are reversed: the client module is the interface module (e.g., restclient.log) and the server module is always an hvs32server module (hvs32server.log).

A list of interfaces can be found in our Interface Documentation.

What Tests Should I Conduct After the Update?

After the service is started and the logs have been checked, a test record should be processed.

In Automatic-Polling, an order must be processed from the host system and sent to the DGS. You could also trigger a reprint, if possible.

In the Interactive Case, the reference number can be scanned / entered into the delivery note data mask of HVS32.

Other Particulars

There are no further particulars.

Abgerufen von „https://wiki.heidler-strichcode.de/w/index.php?title=Update_DataGatewayServer_V3_(DGS_V3)&oldid=5968“