Leitcode routing data update - Versionsgeschichte

Jschaile am 18. Dezember 2020 um 15:09 Uhr

2020-12-18T15:09:49Z

Jschaile am 14. Dezember 2020 um 10:29 Uhr

2020-12-14T10:29:53Z

Jschaile am 14. Dezember 2020 um 10:28 Uhr

2020-12-14T10:28:54Z

Jschaile am 14. Dezember 2020 um 09:33 Uhr

2020-12-14T09:33:38Z

Jschaile am 14. Dezember 2020 um 09:14 Uhr

2020-12-14T09:14:04Z

Änderungen zeigen

Jschaile am 14. Dezember 2020 um 08:50 Uhr

2020-12-14T08:50:49Z

Jschaile: Die Seite wurde neu angelegt: „en:Leitcode_Leitdaten_Update“

2020-12-14T08:50:01Z

Die Seite wurde neu angelegt: „en:Leitcode_Leitdaten_Update“

Neue Seite

[[en:Leitcode_Leitdaten_Update]]

@@ Zeile 2: / Zeile 2: @@
 = Leitcode routing data update =
-DHL provides its customers with new routing data on a quarterly basis.<br/> 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 master data, please contact your DHL representative.<br/> These routing data must be prepared for use with the HVS32 in accordance with the relevant description.
+DHL provides its customers with new routing data on a quarterly basis.<br/> 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.<br/> 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:
@@ Zeile 123: / Zeile 123: @@
 - 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.<br/> - As soon as the import is finished, the Windows service "Heidler Leitcode" must be restarted<br/> After the import, another step must be carried out<br/> The indexing of the Leitcode data. The indexing is only necessary if the Frachtpost.fdb has been renewed, e.g. during the above-mentioned master data update.<br/> 1. Exit the Leitcode service<br/> 2. Run the "HeidlerLeitcode-Manager"<br/> 3. Select the "Index" tab<br/> 4. Click on the "Create Index"<br/> button 5. Wait until the index creation is finished (index creation takes approx. 5 - 20 min depending on the system)<br/> 6. Confirm the message and close the manager<br/> 7. Start the routing code service<br/> The routing coder is now ready for use with current data!
+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.<br/> - As soon as the import is finished, the Windows service "Heidler Leitcode" must be restarted<br/> After the import, another step must be carried out<br/> 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.<br/> 1. Exit the Leitcode service<br/> 2. Run the "HeidlerLeitcode-Manager"<br/> 3. Select the "Index" tab<br/> 4. Click on the "Create Index"<br/> button 5. Wait until the index creation is finished (index creation takes approx. 5 - 20 min depending on the system)<br/> 6. Confirm the message and close the manager<br/> 7. Start the routing code service<br/> The routing coder is now ready for use with current data!
 &nbsp;
@@ Zeile 135: / Zeile 135: @@
 == KELVIN: Socket-Server ==
-Before starting the master data import, make sure that all HVS32 clients have been terminated. The import must not be carried out in parallel with the dispatch operation.<br/> Create a new folder on the local hard disk (c:\heidler\leitcode\update) and copy the complete contents of the current FRACHTPOST.zip.<br/> Call up the programme FPImport_Neu.exe.
+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.<br/> Create a new folder on the local hard disk (c:\heidler\leitcode\update) and copy the complete contents of the current FRACHTPOST.zip.<br/> Call up the programme FPImport_Neu.exe.
 === FPImport_Neu.exe ===

@@ Zeile 123: / Zeile 123: @@
 - 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.<br/> - As soon as the import is finished, the Windows service "Heidler Leitcode" must be restarted<br/> After the import, another step must be carried out<br/> The indexing of the Leitcode data. The indexing is only necessary if the Frachtpost.fdb has been renewed, e.g. during the above-mentioned master data update.<br/> 1. Exit the Leitcode service<br/> 2. Run the "Heidler Leitcode Manager"<br/> 3. Select the "Index" tab<br/> 4. Click on the "Create Index"<br/> button 5. Wait until the index creation is finished (index creation takes approx. 5 - 20 min depending on the system)<br/> 6. Confirm the message and close the manager<br/> 7. Start the routing code service<br/> The routing coder is now ready for use with current data!
+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.<br/> - As soon as the import is finished, the Windows service "Heidler Leitcode" must be restarted<br/> After the import, another step must be carried out<br/> The indexing of the Leitcode data. The indexing is only necessary if the Frachtpost.fdb has been renewed, e.g. during the above-mentioned master data update.<br/> 1. Exit the Leitcode service<br/> 2. Run the "HeidlerLeitcode-Manager"<br/> 3. Select the "Index" tab<br/> 4. Click on the "Create Index"<br/> button 5. Wait until the index creation is finished (index creation takes approx. 5 - 20 min depending on the system)<br/> 6. Confirm the message and close the manager<br/> 7. Start the routing code service<br/> The routing coder is now ready for use with current data!
 &nbsp;

@@ Zeile 123: / Zeile 123: @@
 - 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.<br/> - As soon as the import is finished, the Windows service "Heidler Leitcode" must be restarted<br/> After the import, another step must be carried out<br/> The indexing of the Leitcode data. The indexing is only necessary if the Frachtpost.fdb has been renewed, e.g. during the above-mentioned master data update.<br/> 1. Exit the master code service<br/> 2. Run the "Heidler Master Code Manager"<br/> 3. Select the "Index" tab<br/> 4. Click on the "Create Index"<br/> button 5. Wait until the index creation is finished (index creation takes approx. 5 - 20 min depending on the system)<br/> 6. Confirm the message and close the manager<br/> 7. Start the routing code service<br/> The routing coder is now ready for use with current data!
+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.<br/> - As soon as the import is finished, the Windows service "Heidler Leitcode" must be restarted<br/> After the import, another step must be carried out<br/> The indexing of the Leitcode data. The indexing is only necessary if the Frachtpost.fdb has been renewed, e.g. during the above-mentioned master data update.<br/> 1. Exit the Leitcode service<br/> 2. Run the "Heidler Leitcode Manager"<br/> 3. Select the "Index" tab<br/> 4. Click on the "Create Index"<br/> button 5. Wait until the index creation is finished (index creation takes approx. 5 - 20 min depending on the system)<br/> 6. Confirm the message and close the manager<br/> 7. Start the routing code service<br/> The routing coder is now ready for use with current data!
 &nbsp;
@@ Zeile 141: / Zeile 141: @@
 ----
-- In the input line "Path to Datafactory", enter the directory created in point 1.[[File:LeitcodeUpdateHeidler.PNG|right|HeidlerLeitcodeUpdate.PNG]]<br/> - 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.<br/> - 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.<br/> <br/> - Please ask Support for user and password.<br/> - By pressing the button Test parameters, you can check whether the entries are correct.<br/> - By pressing the button Start import, the import process is triggered.&nbsp;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.<br/> - 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.<br/> - When the import is finished, restart the KelvinSocketServer service on the server.<br/> - The update for the master code is now complete.
+- In the input line "Path to Datafactory", enter the directory created in point 1.[[File:LeitcodeUpdateHeidler.PNG|right|HeidlerLeitcodeUpdate.PNG]]<br/> - 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.<br/> - 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.<br/> <br/> - Please ask Support for user and password.<br/> - By pressing the button Test parameters, you can check whether the entries are correct.<br/> - By pressing the button Start import, the import process is triggered.&nbsp;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.<br/> - 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.<br/> - When the import is finished, restart the KelvinSocketServer service on the server.<br/> - The update for the Leitcode is now complete.

@@ Zeile 2: / Zeile 2: @@
 = Leitcode routing data update =
-DHL provides its customers with new master data on a quarterly basis.<br/> 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 master data, please contact your DHL representative.<br/> These master data must be prepared for use with the HVS32 in accordance with the relevant description.
+DHL provides its customers with new routing data on a quarterly basis.<br/> 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 master data, please contact your DHL representative.<br/> 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''&nbsp;on the server on which the routing encoder is installed&nbsp;<br/> (For information on starting and using the ''Services - Management Console'' from Microsoft, see: [https://technet.microsoft.com/de-de/library/cc772408.aspx https://technet.microsoft.com/de-de/library/cc772408.aspx])
+*Start the ''Services - Management Console''&nbsp;on the server on which the Leitcodierer / routing encoder is installed&nbsp;<br/> (For information on starting and using the ''Services - Management Console'' from Microsoft, see: [https://technet.microsoft.com/de-de/library/cc772408.aspx https://technet.microsoft.com/en-us/library/cc772408.aspx])
 *Look for entries beginning with the names ''Heidler-Leitcode''&nbsp;&nbsp;(the full name may differ at the end due to possible multiple installations).
 *If one or more service(s)&nbsp;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 ''Automatic''&nbsp;
+**If several entries with the designation ''Heidler-Leitcode...'' exist, search for an entry for which the start type is set to ''Automatisch / automatic''&nbsp;
-**If several entries found have the start type set to ''Automatic'', check if there are entries ending with ''AT''.
+**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 ''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.
+**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 ''properties'' of the applicable entry.
 ***Open the directory listed under ''Path to EXE file'' in the Explorer.
-***Open the ''Properties'' of the&nbsp;''HeidlerLeitcode-Service.exe&nbsp;''
+***Open the ''properties'' of the&nbsp;''HeidlerLeitcode-Service.exe&nbsp;''
 ***Check the version number in the tab ''Details'' under ''File version''.
 ***If the version number is ''3.X.X.X'', the description [[#HeidlerLeitcode_V3|''HeidlerLeitcode_V3'']] applies to this installation.
@@ Zeile 22: / Zeile 22: @@
 *Close the&nbsp;''Services - Management Console''&nbsp;and open the ''HVS32'' via a&nbsp;suitable&nbsp;packing place shortcut&nbsp;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 ''Routing Code'' and checking the selection under ''Routing Code''.
+*Check which routing code version is used by opening the section ''Leitcode'' and checking the selection under ''Leitcodierer / Routing Code''.
-*If the option "Routing code" is active, continue with the sub-items. Otherwise, no guide coding is active and no installation is apparent, but if guide coding is desired, contact our support team.
+*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 Lead encoder, continue with the sub-items.
+**If the option ''HEIDLER Service'' is selected under Leitcodierer, continue with the sub-items.
 ***If the selection ''Heidler Leitcodierer Version > 3.0''&nbsp;exists and ''is selected''&nbsp;the description [[#HeidlerLeitcode_V3|''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|''HeidlerLeitcode_V2'']] applies to this installation.

← Nächstältere Version		Version vom 14. Dezember 2020, 08:50 Uhr
Zeile 1:		Zeile 1:
−	[[en:Leitcode_Leitdaten_Update]]	+	[[de:Leitcode_Leitdaten_Update]]