|AddressDoctor 5 Attributes|
AddressDoctor 5 validates, corrects or completes the address format.
AddressDoctor 5 validates, corrects or completes specified address fields using AddressDoctor library and address database. The component filters records, and records which the component doesn't known how to correct are sent to the second (optional) output port.
|Component||Same input metadata||Sorted inputs||Inputs||Outputs||Java||CTL||Auto-propagated metadata|
|Input||0||For input data records||Any1|
|Output||0||For transformed data records||Any2|
|Output||1||For records that could not be transformed (error port)||Any2|
|Config file||||An external file defining the configuration.|
|Parameter file||||An external file defining parameters.|
|Configuration||||Specifies the address database and its location.|
|Parameters||||Controls how the transformation is performed.|
|Input mapping||yes||Determines what will be processed.|
|Output mapping||yes||Controls what will be mapped to the output.|
|Element item delimiter|
If a whole address is stored on a single line, this attribute specifies which special character separates the address fields.
delimiter is not used (default) | one of these: ; : # | \n \r\n clover_item_delimiter
|Number of threads|
The number of threads used for address processing. For more information, see Multithreading.
|1 (default) | 1-N|
 Either Config file or Configuration must be defined.
 Define either Parameter file or Parameters.
|Database Enrichments and File Types|
|Notes and Limitations|
AddressDoctor 5 serves as a GUI for setting parameters of a third party AddressDoctor library. It passes the input data and configuration to the library. Then the library does the address validation. Afterwards, the component maps the outputs from the library back to CloverDX.
AddressDoctor 5 depends on external native libraries. These libraries are currently available only for MS windows and Linux. We are reselling the libraries.
The official AddressDoctor 5 documentation contains necessary information for a detailed configuration of the AddressDoctor 5 component.
A spin-off of working with the component is the so-called transliteration. That means you can, for example, input an address in the Cyrillic alphabet and have it converted to the Roman alphabet. No extra database is needed for this task.
Address doctor is currently being tested against AddressDoctor5 library 220.127.116.1125.
The mapping of the fields sent to the error port is set up in the Output mapping attribute: use the Error output mapping tab. There are two fields ERR_CODE (integer) and ERR_MESSAGE (string) describing the error.
Table 62.2. Database Enrichments and File Types
Most commonly used for basic address parsing and cleansing.
An auto-completion style input which provides suggestions for a partial input.
Provided for specific countries only. Implements a special logic as dictated by the certification authority for the given country.
For geo coding lookups. Three types of geo files exist:
Provides additional demographic details in the databases. For example, information about the income, number of children, cars, etc. for neighborhood. Available for small set of countries only. Information provided and its precision is very much dependent on the country.
Databases required for country-specific enrichments implemented in AD engine. Available for ~10 countries.
When running on IBM Java (e.g. in WebSphere), make sure to add the following JVM parameter to prevent AddressDoctor from crashing the JVM:
Note that the parameter must be set for Worker, as well.
See IBM WebSphere in CloverDX Server Manual.
To use AddressDoctor 5, you need to set up external libraries.
The libraries provide address validation functionality.
Two types of libraries are needed: java library (
and native library (
The native library performs address validation and the java library
enables to use the functionality of native library.
Download AddressDoctor 5 libraries from http://www.addressdoctor.com/en/support/enterprisedownloadv5.asp.
Unzip the libraries into a directory chosen for AddressDoctor, e.g.
C:/AddressDoctor on MS Windows or
/opt/AddressDoctor on unix-like systems.
On Microsoft Windows 8, you need to enable Read & Execute
access right to the file
Add libraries to
classpath of CloverDX Runtime.
→ → →
-Djava.library.path=C:\AddressDoctor\lib to virtual
machine parameters. Do not forget to restart CloverDX Runtime.
When using AddressDoctor with CloverDX Server, paths to the libraries need
to be configured differently. The
library needs to be placed on the classpath of the application server.
This is specific for each application server; for example, with Tomcat you need
to place it into the
lib directory of your Tomcat installation.
Path to the directory with the native library needs to be added to the
java library path via the
Java property. This is also application server specific; in Tomcat, you can create
file and add the following line
set "CATALINA_OPTS=%CATALINA_OPTS% -Djava.library.path=path/to/AddressDoctor/library/directory".
Continue with AddressDoctor 5 Configuration
Download the address database from http://www.addressdoctor.com/en/support/countrydownloadv5.asp.
Unzip the address database into the same directory.
You will get an address database file - the file has suffix
The Configuration dialog enables you to set up a database location and Unlock Code using a graphical user interface.
Open the Configuration attribute and set up a path to database file on DataBase tab.
Do not forget your database is supplied in one of the modes (e.g. BATCH_INTERACTIVE) and thus you have to set up a matching Type (applies to Enrichment databases set in Parameters, too).
Figure 62.1. DataBase Configuration
To use the database, you need to set up Unlock Code on the UnlockCode tab.
The AddressDoctor engine is shared by all components running in the same JVM. That means that all AddressDoctor components in the same graph should have the same Configuration (or Configuration file). If the configurations differ, the AddressDoctor engine will be initialized with the settings from one of the components, but the settings will be used by all of them.
Note that in CloverDX Server environment, the settings are shared between
all running graphs.
Therefore it is recommended to set the configuration
globally using the
By default, the AddressDoctor engine is initialized on demand when a graph with AddressDoctor component is executed and de-initialized when it is not needed. This lowers memory requirements, but introduces re-initialization overhead.
Database Configuration File enables to set up address database location and Unlock Code.
Create a configuration file and set up the Config file attribute to point to the configuration file.
The configuration file contains following lines:
<?xml version="1.0" encoding="utf-8"?> <SetConfig> <General WriteXMLEncoding="UTF-16" WriteXMLBOM="NEVER" MaxMemoryUsageMB="1024" MaxAddressObjectCount="10" MaxThreadCount="1"/> <UnlockCode>Place your code here...</UnlockCode> <DataBase CountryISO3="ALL" Type="BATCH_INTERACTIVE" Path="C:/AddressDoctor" PreloadingType="NONE"/> </SetConfig>
You should replace the text Here place your code ... by your valid Unlock Code.
The address validation process is configured by these attributes:
Parameters controls which transformation will be performed. Particular settings are highly specific and should be consulted with the official AddressDoctor 5 documentation.
For instance, in the Process tab of the dialogue, you can configure various Enrichments. Enrichments allow you to add certificates of the address format. The certificates guarantee that a particular address format matches the official format of a national post office. Note that adding Enrichments usually slows the data processing and can optionally require an additional database.
Figure 62.2. AddressDoctor Parameters
Input mapping determines what will be processed. The input mapping wizard lets you do the settings in two basic steps:
Select address properties form all AddressDoctor internal fields ("metadata") that are permitted on the input. Field names are accompanied by a number in parentheses informing you how many fields can form a property ("output metadata"). For instance "Street name (6)" tells you the street name can be written on up to 6 rows of the input file.
Figure 62.3. Input mapping wizard
Specify the internal mapping of AddressDoctor - drag input fields you have chosen in the previous step on the available fields of the Input mapping.
Examine the summary of the input mapping.
Figure 62.4. Input mapping wizard
Output mapping - here you decide what will be mapped to the output, i.e. the first output port. Optionally, you can map data to the second "error" port (if no such mapping is done, error codes and error messages are generated).
Similarly to Input mapping, you do the configuration by means of a simple wizard following these steps these steps:
Select address properties for mapping.
Specify particular output mapping. That involves assigning the internal fields you have selected before to output fields. In the Error port tab, design a structure of the error output (its fields) that is sent to the second output port if the component cannot perform the address transformation.
Figure 62.5. Output mapping
Examine the summary of the output mapping.
The Number of threads attribute can be used to increase the throughput of the component by using additional threads for address processing.
Multithreading is also influenced by the Configuration attribute. Max thread count is a total limit on the number of threads concurrently accessing the AddressDoctor library (e.g. from multiple AddressDoctor components). Typically it can be set to the same number as the Number of threads attribute if using one AddressDoctor component. Additionally, for each thread requested by Number of threads two address objects will be used (see Max address object count in Configuration).
Multithreading preserves the order of output records.
It is recommended to use full database preloading to prevent the threads from blocking on file system calls. The Max memory usage option should be configured accordingly to accommodate all used databases and address objects.
If a graph fails with the message
Error: A database file has not been found.
Check whether the path pointing to the database file is correct.
Check the country of data being processed. You might not have a database for particular country.