Leitcode routing data update

DHL provides its customers with new routing data on a quarterly basis.
You will receive this either on a CD or by download from the DHL portal via your own access. If you do not receive information about new routing data, please contact your DHL representative.
These routing data must be prepared for use with the HVS32 in accordance with the relevant description.

You can check which of the descriptions listed here applies to your installation using the following instructions:

Start the Services - Management Console on the server on which the Leitcodierer / routing encoder is installed
(For information on starting and using the Services - Management Console from Microsoft, see: https://technet.microsoft.com/en-us/library/cc772408.aspx)
Look for entries beginning with the names Heidler-Leitcode (the full name may differ at the end due to possible multiple installations).
If one or more service(s) with such a designation exists, follow the sub-items. Otherwise, continue with the next point.
- If several entries with the designation Heidler-Leitcode... exist, search for an entry for which the start type is set to Automatisch / automatic
- If several entries found have the start type set to Automatisch / automatic, check if there are entries ending with AT.
- Perform the following steps for each entry for which the start type is set to Automatisch / automatic. Note that the entries ending with AT refer to an installation that provides international routing code data for Austria. Such entries require the international DataFactoryCargo files.
  - Open the properties of the applicable entry.
  - Open the directory listed under Path to EXE file in the Explorer.
  - Open the properties of the HeidlerLeitcode-Service.exe
  - Check the version number in the tab Details under File version.
  - If the version number is 3.X.X.X, the description HeidlerLeitcode_V3 applies to this installation.
  - If the version number is 2.X.X.X, the description HeidlerLeitcode_V2 applies to this installation.
Look for entries with the names KELVIN: Socket-Server
If a service with such a name exists, the description KELVIN: Socket-Server applies to this installation. Otherwise, proceed to the next point.
Close the Services - Management Console and open the HVS32 via a suitable packing place shortcut such as Support (the available packing places and shortcuts may differ depending on the configuration).
Open the Post carrier configurator. Read the displayed instructions carefully and accept them if you agree with them.
Check which routing code version is used by opening the section Leitcode and checking the selection under Leitcodierer / Routing Code.
If the option "Leitcodierung / Routing code" is active, continue with the sub-items. Otherwise, no Leitcodierung is active and no installation is apparent, but if Leitcodierung is desired, contact our support team.
- If the option HEIDLER Service is selected under Leitcodierer, continue with the sub-items.
  - If the selection Heidler Leitcodierer Version > 3.0 exists and is selected the description HeidlerLeitcode_V3 applies to this installation.
  - If the selection Heidler Leitcodierer Version > 3.0 does not exist or is not selected, the description HeidlerLeitcode_V2 applies to this installation.
- If the option KELVIN® Service is selected under Leitcodierer, the description KELVIN: Socket-Server applies to this installation.

HeidlerLeitcode_V3

These instructions refer to the update of the guidance data for the "Heidler guidance code service" of the third generation.

Run the "HeidlerLeitcode-Manager" Press the button "Import / Update" in the corresponding country section.
Select when the imported database should replace the existing one. CAUTION: In the case of a delayed update, no automated comparison of the version code can take place! Please make a note of the version code displayed after the import process in order to be able to check it manually on the scheduled update date. Press the button "Next" to continue.
Next, select the DataFactoryCargo of Deutsche Post. If an unsupported compression method is used, this will be displayed in the form of an error message in the application. In this case, extract all files into an empty directory with a suitable tool, then select the previously extracted (INT_)B[NNNNNN].DAT (ex. B1806152.DAT) file instead of the archive to perform the import process. Please note that all files are extracted from the ZIP into the same directory, as the programme searches for other required files in this directory in order to import them.

Version check after an update process without delay

After a successful import process, the update process of the database can be validated with the help of a check of the version codes.
Note that for the version check, any settings made previously must be saved and the routing code service must be started!
To do this, press the "Yes" button.

Change the server address, unless the manager was running on the same machine as the routing coding service.
Confirm with the "OK" button.

Confirm the message with the "OK" button.

Translated with www.DeepL.com/Translator (free version)

Version check after an update process with delay

After a successful import process, the version code of the new database will be displayed.
Please make a note of the version and the planned update date.
Confirm the message with the "OK" button.

At the scheduled update time, check the version according to the instructions provided in section 5.2.4 Check database version'

HeidlerLeitcode_V2

These instructions refer to the update of the routing data for the "Heidler Leitcode Service" of the second generation.
Before the import of routing data is started, it must be ensured that all HVS32 clients have been terminated. The import must not be carried out in parallel with the dispatch operation !

- Create a new folder on the local hard disk of the HVS32 server (e.g. C:\Heidler\Leitcode\Update) and copy the complete contents of the current FRACHTPOST CD / ZIP into it.

- Then start the programme FPImport_Neu.exe.

FPImport_Neu.exe

You can find the current import tool here:
http://heidler-strichcode.de/transfer/Leitcode/FPImport_neu.zip

- Create a new folder on the local hard disk of the HVS32 server (e.g. C:\Heidler\Leitcode\Update) and copy the complete contents of the current FRACHTPOST CD / ZIP into it.

- In the input line "Path to Datafactory" enter the directory created in point 1.

- DB-Host: The IP address of the HVS32 server must be entered here. Alternatively leave localhost or use 127.0.0.1 in case of problems.

- DB-Path: local path and file name to the file FRACHTPOST.GDB/FDB installed on the HVS32 server (or FRACHTPOST_FB25.FDB when using Firebird 2.5)

- Please ask Support for user and password.

- By pressing the button Test parameters, you can check whether the information is correct.

- Then click on the "Start import" button. The duration of the process depends on the computer performance and takes about 30 minutes on average. After you receive the message that the import has been completed successfully, you can exit the programme.

Note: When clicking on "Start import" for the first time, an error message may appear in certain environments. Please confirm this with OK and then select "Start import" again. Provided that all parameters are set correctly, the import will then start properly.
- As soon as the import is finished, the Windows service "Heidler Leitcode" must be restarted
After the import, another step must be carried out
The indexing of the Leitcode data. The indexing is only necessary if the Frachtpost.fdb has been renewed, e.g. during the above-mentioned routing data update.
1. Exit the Leitcode service
2. Run the "HeidlerLeitcode-Manager"
3. Select the "Index" tab
4. Click on the "Create Index"
button 5. Wait until the index creation is finished (index creation takes approx. 5 - 20 min depending on the system)
6. Confirm the message and close the manager
7. Start the routing code service
The routing coder is now ready for use with current data!

To minimise downtime of the system regarding the routing code, you can also proceed as follows:

1. stop the routing code service (after the copy you can start the service again)
2. copy the freight post database to another folder on the server (or create a new sub-folder for this) and create a new folder Index
3. run the "HeidlerLeitcode-Manager" and then in the Manger select the path to this copy. (do not save)
4. Click on the button "Create index" (in new index folder)
5. Wait until the index creation is finished (the index creation takes about 5 - 20 min depending on the system)
6. Confirm the message and close the Manager (do not save the "new" path to the DB copy)
7. Call the Leitcode service and replace the database (rename) and the index folder, then start the service and test the labels.

KELVIN: Socket-Server

Before starting the routing data import, make sure that all HVS32 clients have been terminated. The import must not be carried out in parallel with the dispatch operation.
Create a new folder on the local hard disk (c:\heidler\leitcode\update) and copy the complete contents of the current FRACHTPOST.zip.
Call up the programme FPImport_Neu.exe.

FPImport_Neu.exe

- In the input line "Path to Datafactory", enter the directory created in point 1.

- In the input line DB-Host, enter the IP address of the computer acting as the dispatch server. If the import is carried out directly on the dispatch server (which also makes sense for performance reasons), you can leave the entry localhost instead of the IP address.
- The local path and file name of the file FRACHTPOST.GDB installed on the dispatch server (or FRACHTPOST_FB25.FDB when using Firebird 2.5) must be entered in the DB path input line. Please note that the local path of the file on the dispatch server must be entered and not the network path of the file from the client.

- Please ask Support for user and password.
- By pressing the button Test parameters, you can check whether the entries are correct.
- By pressing the button Start import, the import process is triggered. Then start the import again. The duration of the process depends on the computer performance and takes about 30 minutes on average. After the message about the successfully completed import appears, the programme can be exited.
- The first time you press "Start import", an error message may appear, which must be confirmed with OK and then press "Start import" again, then the import should start properly if all parameters are set.
- When the import is finished, restart the KelvinSocketServer service on the server.
- The update for the Leitcode is now complete.