Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Address Verification (On-Premises)
  3. General Settings
  4. Input Parameters
  5. Process Parameters
  6. Address Enrichments
  7. Result Parameters
  8. Output Fields
  9. Assessment Codes and Return Codes
  10. Frequently Asked Questions

Developer Guide (On-Premises)

Developer Guide (On-Premises)

The General Element

The General Element

Configure the following attributes of the
General
element:
WriteXMLBOM
Specifies when Informatica Address Verification should write a byte order mark (BOM) in the
GetConfig.xml
file. You can configure one of the following options:
  • ALWAYS
  • IF_NECESSARY
  • NEVER
The default value is IF_NECESSARY.
WriteXMLEncoding
Specifies the encoding for the XML files that Address Verification creates. To view the list of encoding types, see XML Encoding Types.
CacheSize
Specifies the size of memory cache to allocate for each of the address verification threads. You can configure one of the following options:
  • NONE. Address Verification does not allocate any memory for caching.
  • SMALL. Address Verification allocates 0.4 MB of memory for caching.
  • LARGE. Address Verification allocates 0.75 MB of memory for caching.
The default value is LARGE.
If you set either SMALL or LARGE for the
CacheSize
attribute, Address Verification allocates one memory cache for each of the address processing threads. For example, if you set
MaxThreadCount
to 4, and
CacheSize
to SMALL, Address Verification allocates 4 x 0.4 = 1.6 MB of memory for caching.
MaxThreadCount
Specifies the maximum number of address processing threads that Address Verification can process simultaneously.
The default value is 1. You can set a minimum value of one, and a maximum value based on the system capabilities. There is no upper cap on the value that you can configure for this attribute. However, consider your system capabilities and number of cores available for Address Verification before you decide on a value for this attribute. For best results, you can consider a value that is one less than the total number of cores on the device.
For example, on a device that has four cores, you can set
MaxThreadCount
to 3.
MaxAddressObject
Specifies the maximum number of address objects that Address Verification can process simultaneously.
You can set a minimum value of 1 and a maximum value based on the system capabilities. The default value is 1. Based on the system capabilities, you can configure a value that is 2 or 3 times the value you set for
MaxThreadCount
. For example, if you set
MaxThreadCount
to 2, the maximum value for
MaxAddressObjectCount
can be 4 or 6.
If you set
MaxAddressObjectCount
to a value less than that of
MaxThreadCount
, Address Verification reduces the value of
MaxThreadCount
to match the value you set for
MaxAddressObjectCount
.
MaxMemoryUsageMB
Specifies the maximum amount of memory, in MB, that Address Verification can request from the operating system.
The default value is 512 MB. Consider different memory requirements such as general memory block, thread memory block, caching memory, preloading memory block, and so on when you calculate
MaxMemoryUsageMB
. Address Verification fails to initialize if you set a value lower than the size of memory Address Verification requires.
MaxResultCount
Specifies the maximum number of suggestions Address Verification returns while verifying addresses in the Interactive mode. You can configure a value between 1 and 100. The default value is 20.
PreloadingMethod
Specifies the preloading method for reference address databases. You can configure one of the following options:
  • MAP
  • LOAD
MAP is the default value. The LOAD option is available for backward compatibility.

0 COMMENTS

We’d like to hear from you!