Installation and Getting Started Guide

6.0.0
- 6.4.0
- 6.3.0
- 6.2.0
- 6.1.0

Back Next

Configuring the Engine

Informatica Address Verification uses the Intelligent Data Verification Engine (IDVE) to process the verification jobs that you define.

The

IDVEConfig.json

file provides configuration information for Address Verification engine operations. The file includes default values for several elements.

Before initializing the engine, verify or configure the elements below in the

IDVEConfig.json

file.

Find the following elements under

Core/System

NumFunctionServers: Specifies the number of function servers available for processing. Also, determines the number of inputs that the engine can process in parallel.
NumHotStandbyFunctionServers: Specifies the number of standby function servers.
FileSetsHotSwappingEnabled: Enables or disables dynamic switches between two filesets. Supported values are true and false. Default is false.

When enabled, hot swapping increases the maximum memory requirements.
MaxMemoryMegabytes: Specifies the maximum amount of memory available for all processes, including file preloading. The default value is 1024 MB.

1024 MB is a minimum value. Depending on your workload, you might need to set a higher value.
FunctionServerInitTimeoutSeconds: Specifies the timeout period to successful initialize all function servers. Default is 600 seconds.
FunctionServerCallTimeoutSeconds: Specifies the timeout period to successfully submit a job call to a function server. Default is 60 seconds.
LicenseFilesDirectoryPath: Specifies the directory path to the license files.

Informatica sends you the license keys that you need when you buy the data. You must add the license keys at the location that you set in the LicenseFilesDirectoryPath element.
FileSetsDirectoryPath: Specifies the directory path to the reference data filesets and to the
FileSetsInfo.json
file.; The
FileSetsInfo.json
file describes the current status of the filesets. Address Verification creates the
FileSetsInfo.json
file in the directory.

Use absolute paths for all directories in the configuration file.
ExecutablesDirectoryPath: Specifies the directory path to the FunctionServer executable application.
Do not include the function server executable file name in the path.

Find the following element under

ErrorLog

FilePath: Specifies the path to the error log target file and the log file name.
ClearAtInit: Clears the log file during initialization. If the log file already exists and includes the content, the element clears the log file. Supported values are true and false. Default is true.
LogInput: Identifies the input issues that a function server instance encounters when processing an address, which prevents the function server from correctly processing the input and returning a result. Default is Disabled.

Includes the following values:

CompleteInput. The error log contains the full input data that caused the issue.
OnlySourceID . The error log contains only the "SourceID" property of the input that caused the issue. No potentially sensitive customer data written into the log.
Disabled. The error log contains only a note that the function server encountered an issue. No further input-specific data attached.

Find the following element under

InitializationLog

FilePath: Specifies the path to the initialization log file and the log file name.
LogLevel: Specifies the minimum severity that will be logged to the file. Any events with lower severity does not appear in the log file. Default is Warning.

You can configure one of the following values:

VeryCriticalError
CriticalError
Error
Warning
Status
Info
ClearAtInit: Clears the log file during initialization. If the log file already exists and includes the content, the element clears the log file. Supported values are true and false. Default is true.

Find the following elements under

Functions/AddressVerification

MaxNumJobs: Specifies the maximum number of jobs that can exist concurrently.
MaxNumInputs: Specifies the maximum number of addresses that you can submit for verification. The range is from 1 through 1000. Default is 100.
MaxNumResults: Specifies the maximum number of address results that the function can return after execution. The range is from 1 through 100. Default is 20.
MaxNumVariants: Specifies the maximum number of output variants that the function can return after execution. The range is from 1 through 10. Default is 1.

Find the following elements under

FunctionServers/FileSets

PreloadingMethod: Specifies how Address Verification preloads the reference address databases to memory. To optimize performance, you can preload reference address databases.

Set one of the following values:

Map. Address Verification uses the file mapping mechanism of the operating system.

Map is the default and recommended option.

Load. Address Verification uses a memory allocation call and loads the data to the allotted memory block.
PreloadingPriorityList: Specifies the order in which Address Verification loads data files into memory. Address Verification loads the database files in the order in which they appear in the list. Each preloaded file consumes a quantity of the available memory. If the maximum memory threshold is reached, further file data will not be preloaded to memory but will remain available for processing.

Includes the following elements:

Selector. Identifies the types of file data to prioritize during the preload operation.

The Selector is a string that specifies a Function, Country, Process Type, Process Sub Type, and DataSet ID. For example, the following values for Selector instruct Address Verification to load all data files for batch and interactive verification for Germany in the 000 data set:
AddressVerification/DEU/Verify/BatchInteractive/000

Replace any value between a [/] separator with an asterisk to select all options at that position. For example, the following parameters specify batch and interactive data files for all countries in the 000 data set:
AddressVerification/*/Verify/BatchInteractive/000

If you use multiple trailing asterisks in the Selector parameter, you can replace them with a single asterisk. For example,
AddressVerification/*/*/*/*
and
AddressVerification/*
have the same meaning.

PreloadingExtent. Specifies the preloading type for each of the reference address databases.

Set one of the following values:

Full. Address Verification copies the entire reference address database to memory.
Partial. Address Verification loads fragments of each data file, starting with the most important data.
None. Address Verification does not preload any data.

Address Verification can stop preloading data at any time if the maximum memory threshold is reached. The unloaded reference data remain in the system storage.

IDVEConfig.json Configuration File

The following image shows an example of the

IDVEConfig.json

file in a JSON editor:

Rename Saved Search

Table of Contents

Installation and Getting Started Guide

Installation and Getting Started Guide

Configuring the Engine

Configuring the Engine

IDVEConfig.json Configuration File