As part of troubleshooting problem with integration between STEP and Loqate Local, it is possible to test if the installed Loqate Engine and Loqate Reference Data works as intended and is ready to be used by STEP. This can be done my logging on to the STEP application server and executing the Local Loqate engine directly.
Linux
For the Linux users, use the lqtBatch.exe app and follow the steps (outlined at https://support.loqate.com/batch-processor/) to go through the process on a command line interface.
Windows
The lqtDemo.exe file provides feedback to determine if an issue is with Loqate or with STEP. This file is in the Loqate server folder.
Open the lqtDemo.exe file and provide the location where the data packs have been created.
After setting the data packs location, select the ‘Verify’ tab at the top. This tab allows users to enter an address and test that standardized information is returned. The lower left corner error information displays.
In this example, the GKR location is set to a directory that does not exist.
Below, another address is entered, and returns no errors. This means there are no issues with the Loqate API and reference data deployment, but with STEP or the STEP-Loqate connection (for example, a misconfiguration in sharedconfig.properties file).
