For users that keep their Loqate integration service implemented solely on-premise, the following topics outline Loqate's capabilities and the deployment and upgrade processes:
-
Loqate Integration Properties (here)
-
Loqate Local API Testing (here)
-
Loqate Local License Key & Data Package Update (here)
Prerequisites
The following subsections explain the prerequisites that must be met before installing the Loqate Cloud and Local and associated reference data on your STEP application server.
System Requirements for Loqate Local
A considerable amount of disk space is needed for Loqate reference data.
Additionally, a number of storage areas are required. Review the description of each storage area in Local Only section of the Loqate Integration Properties topic here.
-
LoqateLocal.DataPack.SharedFolder (Shared storage): It is recommended to allocate 150 GB of storage to this location.
-
LoqateLocal.DataPack.LocalRoot (Local storage): Stibo Systems recommends you allocate 150 GB of storage to this location.
-
LoqateLocal.DataPack.LocalFolder (Local storage): Stibo Systems recommends you allocate 100 GB of storage to this location.
Review the general shared storage requirements in the System Administration documentation. As this storage is used for random access at runtime, it is required to use RAIDed/SSD storage for optimal performance.
Install Recipes for Loqate Local and CASS
A separate install recipe is needed to integrate STEP with the Loqate Local API and CASS components required to use the address standardization and validation services of Loqate Local with STEP. Contact Stibo Systems if you need to obtain the install recipe.
Note: Though the same recipe is used for both Loqate Local and CASS, CASS is only available to users in the US who have purchased an additional CASS license. Furthermore, users should select the recipe compatible with their STEP system and always verify that it is the correct recipe before installation.
Once installed, the Loqate (and CASS, if applicable) software will be available on the STEP system. However, additional configurations must be made, and additional data must be installed for Loqate (and CASS, if applicable) to work.
Included in the Loqate (and CASS) installation are the Address Component Model and the CASS Address Component Model. These must be configured for an on-premise deployment to work.
Refer to the Address Component Model (here) and the CASS Address Component Model (here) topics in this documentation for more information.
Network Access Requirements
To gain access to the Loqate service, the following network access is required between your STEP application server and the Internet:
-
Loqate Cloud: api.addressy.com/Cleansing/International/Batch/v1.00/json4.ws
-
Loqate Local: HTTPS access to licensing.loqate.com, download.loqate.com and data.loqate.com – These are required to download the Loqate data packs (reference data)
The following commands can be useful to test if the required network access is available:
-
ping saas.loqate.com
-
ping licensing.loqate.com
-
ping download.loqate.com
-
ping data.loqate.com