Server migration

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


Preparation

It is necessary to backup the whole HVS32 system with all its components and configurations before the server migration. That includes to check all additional installed services (expansion modules, etc.) to make sure that all needed data is backed up and no needed service will be forgotten during the migration. Therefore it is important to arrange an appointment with our support to review the current server as the first step.

If one of the following services is installed, please contact us to arrange an appointment for the migration with us. All of the listed services have to be installed and configured by the Heidler support.

  • HVS32 Service
  • DataGatewayServer
  • HVS32 DBService
  • Monitoring
  • HVS32 Monitoring
  • AMA Service
  • KelvinSocketServer
  • Heidler Leitcode
  • other services starting with HVS32* or Heidler*


Attention with special carriers:

  • If Fedex is used without a webservice (Heilder Carrier API), please get in touch with your Fedex contact person, so they can install the FedEx Shipment Manager Software on the new server.
  • If TNT is used, please get in touch with your TNT contact person, in terms of the future connection to the carriers servers (if web services are needed or TNT Unilab application configured!)

Backup

  • If the module DHL Road (Post) is used, the windows service "Heidler Leitcode" (old service: KelvinSocketServer) has to be stopped.
  • All HVS32 client stations need to be stopped (incl. possibly installed HVS32 Monitoring services).
  • Also stop the services for database connection: "FirebirdServerDefaultInstance" and if existent "FirebirdGuardianDefaultInstance" (there are no operations with the HVS32 possible, while these services are stopped!)
  • Copy and save the the whole HVS32 directory and all other needed directories as a safety backup.

Migration

  • Copy the same directories as for the backup to the new HVS32 server to the path C:\Heidler\HVS32 (C:\Program Files (x86)\HVS32 can cause problems)
  • If you're still using Firebird 1.5 you will have to install Firebird 1.5 manually from the HVS32 Directory \FirebirdInstall\FB15_Win32Setup.exe before the regular HVS32 installation. As installation path use C:\Heidler\Firebird

Attention: The installation and use of other Firebird versions can cause data loss! Furthermore please note, that it can cause problems if Firebird 1.5 is used with Windows Server 2012 or newer. In case you want to update to Firebird version 2.5 (32/64 bit) during the server migration, please contact us a few weeks before the migration.

  • After the successful Firebird installation, the HVS32 has to be installed: Please contact our support for the newest HVS32 version.
  • Select "New Installation" in the installer. (NOT "Update to version x.xxx.xx.x"!)
  • In the next step select the path to which you copied the "old" HVS32 version. (Should be C:\Heidler\HVS32).
  • that includes that some files have to be overwritten (only in the HVS32 folder). Please confirm this.
  • After the successful installation: Open the System.ini in the HVS32 Directory, check and change the following points, if necessary:
    • The IP-Address of the server on which you just installed the HVS32.
    • The Path to the database within the HVS32 directory (standard: C:\Heidler\HVS32\Database\hvs32.fdb)
  • The Firebird "FirebirdGuardianDefaultInstance" (For version 2.5 "FirebirdServer") should already run as a windows service. If the service is not running yet, run it manually and change the start type to "automatic".

The default migration of the HVS32 is done and it can now be started on the new server.


Further points have to be done/checked specific for every project:

  • Assignment of user permissions (Every windows user has to get full access to the HVS32 folder and all folders underneath)
  • Configuration of the network share for the folder C:\Heidler\HVS32
  • Integration of the network share on the client shipping station.
  • Installation of additional services required by this project (see point preparation) by Heidler.
  • Also adjust the connection to the host- (ERP-, LVS-) systems, that future data is transmitted correctly to the HVS32.
  • If a central polling (HVS32 Monitoring Service) is used, the Network-printer drivers must to be installed by yourself on the HVS32 server and also the printers need to be set up in the HVS32 printer output-channels within the Auto0x monitoring stations.

General Installation advices

  • It's reccomended to execute all steps listed above as an administrator.
  • In case the System.ini file can't be edited in the HVS32 folder, we suggest to copy the file to another folder, edit it there, and replace the original one in the HVS32 folder. In that case please also check your user permissions again.
Abgerufen von „https://wiki.heidler-strichcode.de/w/index.php?title=Server_migration&oldid=2123“