How To Validate A Single Line Address On An Ipod With A Singleline Address Validation (For A Non-Profit) On A Microsoft Powerbook (For An Ipo) On An Uniden Computer (For Free) On Your Computer Or

(1)

Informatica AddressDoctor Cloud (Version 2)

(2)

Informatica AddressDoctor Cloud User Guide Version 2

December 2014

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or international Patents and other Patents Pending.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013©_{(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14}

(ALT III), as applicable.

The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing.

Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and Informatica Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners.

Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights reserved. Copyright ©_{Sun Microsystems. All rights reserved. Copyright}©_{RSA Security Inc. All Rights Reserved. Copyright}©_{Ordinal Technology Corp. All rights}

rights reserved. Copyright ©_{Red Hat, Inc. All rights reserved. Copyright}©_{The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright} ©_{EMC Corporation. All rights reserved. Copyright}©_{Flexera Software. All rights reserved. Copyright}©_{Jinfonet Software. All rights reserved. Copyright}©_{Apple Inc. All}

This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and/or other software which is licensed under various versions of the Apache License (the "License"). You may obtain a copy of these Licenses at http://www.apache.org/licenses/. Unless required by applicable law or agreed to in writing, software distributed under these Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the Licenses for the specific language governing permissions and limitations under the Licenses.

This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright ©_{1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under various versions of the GNU Lesser General Public License}

Agreement, which may be found at http:// www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.

The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine, and Vanderbilt University, Copyright (©_{) 1993-2006, all rights reserved.}

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution of this software is subject to terms available at http://www.openssl.org and http://www.openssl.org/source/license.html.

This product includes Curl software which is Copyright 1996-2013, Daniel Stenberg, <[email protected]>. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

available at http://www.dom4j.org/ license.html.

terms available at http://dojotoolkit.org/license.

This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html.

http:// www.gnu.org/software/ kawa/Software-License.html.

Deutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php.

This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software are subject to terms available at http:/ /www.boost.org/LICENSE_1_0.txt.

http:// www.pcre.org/license.txt.

available at http:// www.eclipse.org/org/documents/epl-v10.php and at http://www.eclipse.org/org/documents/edl-v10.php.

This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http:// www.stlport.org/doc/ license.html, http:// asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://

(3)

license.html, http://www.libssh2.org, http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3- license-agreement; http://antlr.org/license.html; http://aopalliance.sourceforge.net/; http://www.bouncycastle.org/licence.html; http://www.jgraph.com/jgraphdownload.html; http://www.jcraft.com/jsch/LICENSE.txt; http://jotm.objectweb.org/bsd_license.html; . http://www.w3.org/Consortium/Legal/ 2002/copyright-software-20021231; http://www.slf4j.org/license.html; http://nanoxml.sourceforge.net/orig/copyright.html; http://www.json.org/license.html; http:// forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://www.sqlite.org/copyright.html, http://www.tcl.tk/software/tcltk/license.html, http:// www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html, http://www.slf4j.org/license.html; http://www.iodbc.org/dataspace/iodbc/wiki/iODBC/License; http:// www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http://www.edankert.com/bounce/index.html; http://www.net-snmp.org/about/ license.html; http://www.openmdx.org/#FAQ; http://www.php.net/license/3_01.txt; http://srp.stanford.edu/license.txt; http://www.schneier.com/blowfish.html; http:// www.jmock.org/license.html; http://xsom.java.net; http://benalman.com/about/license/; https://github.com/CreateJS/EaselJS/blob/master/src/easeljs/display/Bitmap.js; http://www.h2database.com/html/license.html#summary; http://jsoncpp.sourceforge.net/LICENSE; http://jdbc.postgresql.org/license.html; http://

protobuf.googlecode.com/svn/trunk/src/google/protobuf/descriptor.proto; https://github.com/rantav/hector/blob/master/LICENSE; http://web.mit.edu/Kerberos/krb5-current/doc/mitK5license.html; http://jibx.sourceforge.net/jibx-license.html; https://github.com/lyokato/libgeohash/blob/master/LICENSE; https://github.com/hjiang/jsonxx/ blob/master/LICENSE; and https://code.google.com/p/lz4/.

This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and Distribution License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code License Agreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php), the new BSD License (http://opensource.org/ licenses/BSD-3-Clause), the MIT License (http://www.opensource.org/licenses/mit-license.php), the Artistic License (http://www.opensource.org/licenses/artistic-license-1.0) and the Initial Developer’s Public License Version 1.0 (http://www.firebirdsql.org/en/initial-developer-s-public-license-version-1-0/).

software are subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For further information please visit http://www.extreme.indiana.edu/.

This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775; 6,640,226; 6,789,096; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110; 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422; 7,676,516; 7,720,842; 7,721,270; 7,774,791; 8,065,266; 8,150,803; 8,166,048; 8,166,071; 8,200,622; 8,224,873; 8,271,477; 8,327,419; 8,386,435; 8,392,460; 8,453,159; 8,458,230; and RE44,478, International Patents and other Patents Pending.

DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice.

NOTICES

This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software Corporation ("DataDirect") which are subject to the following terms and conditions:

1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS. Part Number: AD-CUG-56000-0001

(4)

Chapter 1: Informatica AddressDoctor Cloud. . . 1

Informatica AddressDoctor Cloud. . . 1

Key Features of Informatica AddressDoctor Cloud. . . 1

New Features in This Release. . . 2

Single-Line Address Validation. . . 2

AddressCodeLookup. . . 3

Configurable Output Format for Element Descriptors. . . 4

Point Address Geocoding. . . 4

Support for Preserving Alias or Vanity Names for Localities and Streets. . . 5

Ability to Retrieve Address Codes for Outdated Japan Addresses. . . 5

Chapter 2: Informatica AddressDoctor Cloud Interface. . . 6

Interface Overview. . . 6

SOAP 1.1 Headers and Envelope. . . 6

SOAP 1.2 Headers and Envelope. . . 7

Request XML. . . 7

Notes About Elements in the Request XML . . . 10

Response XML . . . 11

Chapter 3: Informatica AddressDoctor Cloud Request Elements. . . 12

Login and Password. . . 12

ProcessMode. . . 13 Service Parameters. . . 15 JobToken . . . 15 CampaignId. . . 16 ReservedXml. . . 16 UseTransactionPool. . . 16 Table of Contents i

(5)

Example: Service Parameters. . . 16 Validation Parameters. . . 17 FormatType. . . 17 FormatDelimiter. . . 17 DefaultCountryISO3. . . 18 ForceCountryISO3. . . 18 CountryType. . . 18 CountryOfOriginISO3. . . 19 StreetWithNumber. . . 19 FormatWithCountry. . . 20 ElementAbbreviation. . . 20 PreferredScript. . . 20 PreferredLanguage. . . 21 GlobalCasing. . . 21 GlobalMaxLength. . . 21

MatchingScope and MatchingAlternatives. . . 22

AliasStreet and AliasLocality. . . 22

MaxResultCount. . . 22 DualAddressPriority. . . 23 GlobalPreferredDescriptor. . . 23 MatchingExtendedArchive. . . 25 StandardizeInvalidAddresses. . . 25 RangesToExpand. . . 25 FlexibleRangeExpansion. . . 26 FormatMaxLines. . . 26 GeoCodingType. . . 26 DisableCertifiedModeISO3. . . 26 Standardizations. . . 27 OutputOptions. . . 28 Addresses. . . 28 Enrichment. . . 29

Chapter 4: Informatica AddressDoctor Cloud Response Elements. . . 30

Response Elements. . . 30

Status Codes and Messages. . . 31

Process Status Codes. . . 32

JobToken. . . 33

CampaignID. . . 34

ReservedXml. . . 34

Enrichments (Response). . . 34

Enrichment Error Codes and Messages. . . 34

AMAS Status Codes and Output Fields. . . 35

CASS Status Codes and Output Fields. . . 36

(6)

SendRight Status Codes and Output Fields. . . 36

SERP Status Codes and Output Fields. . . 36

SNA Status Codes and Output Fields. . . 37

Additional Country-Specific Information in Validated Output. . . 37

Consumer Segmentation (CAMEO) Information in Validated Output. . . 38

GeoCoding in Validated Output. . . 38

Results. . . 39

ResultDataSet. . . 39

Chapter 5: Examples. . . 45

Example: VisualBasic .NET Interface . . . 45

Example: A V4 Address with GeoCoding. . . 47

Example: An Austria Address with Country-Specific Enrichment. . . 49

Example: Single Line Address Validation. . . 51

Example: AddressCodeLookup. . . 56

Example: An India Address with Multiple Levels of Locality Information. . . 58

Example: Address with Residue Information. . . 60

(7)

Preface

Welcome to the Informatica AddressDoctor Cloud User Guide. This guide provides you information about Informatica AddressDoctor Cloud features and configuration settings. This guide also contains some examples that you can use to verify your settings.

Informatica Resources

Informatica My Support Portal

As an Informatica customer, you can access the Informatica My Support Portal at

http://mysupport.informatica.com.

The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base, Informatica Product Documentation, and access to the Informatica user community. The site contains product information, user group information, newsletters, access to the Informatica How-To Library, the Informatica Knowledge Base, Informatica Product Documentation, and access to the Informatica user community.

Informatica Documentation

The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through email at [email protected]. We will use your feedback to improve our

documentation. Let us know if we can contact you regarding your comments.

The Documentation team updates documentation as needed. To get the latest documentation for your product, navigate to Product Documentation from http://mysupport.informatica.com.

Informatica Product Availability Matrixes

Product Availability Matrixes (PAMs) indicate the versions of operating systems, databases, and other types of data sources and targets that a product release supports. You can access the PAMs on the Informatica My Support Portal at https://mysupport.informatica.com/community/my-support/product-availability-matrices.

Informatica Web Site

You can access the Informatica corporate web site at http://www.informatica.com. The site contains

information about Informatica, its background, upcoming events, and sales offices. You will also find product iv

(8)

and partner information. The services area of the site includes important information about technical support, training and education, and implementation services.

Informatica How-To Library

As an Informatica customer, you can access the Informatica How-To Library at

http://mysupport.informatica.com. The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includes articles and interactive demonstrations that provide solutions to common problems, compare features and behaviors, and guide you through performing specific real-world tasks.

Informatica Knowledge Base

As an Informatica customer, you can access the Informatica Knowledge Base at

http://mysupport.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through email at [email protected].

Informatica Support YouTube Channel

You can access the Informatica Support YouTube channel at http://www.youtube.com/user/INFASupport. The Informatica Support YouTube channel includes videos about solutions that guide you through performing specific tasks. If you have questions, comments, or ideas about the Informatica Support YouTube channel, contact the Support YouTube team through email at [email protected] or send a tweet to @INFASupport.

Informatica Marketplace

The Informatica Marketplace is a forum where developers and partners can share solutions that augment, extend, or enhance data integration implementations. By leveraging any of the hundreds of solutions available on the Marketplace, you can improve your productivity and speed up time to implementation on your projects. You can access Informatica Marketplace at http://www.informaticamarketplace.com.

Informatica Velocity

You can access Informatica Velocity at http://mysupport.informatica.com. Developed from the real-world experience of hundreds of data management projects, Informatica Velocity represents the collective knowledge of our consultants who have worked with organizations from around the world to plan, develop, deploy, and maintain successful data management solutions. If you have questions, comments, or ideas about Informatica Velocity, contact Informatica Professional Services at [email protected].

Informatica Global Customer Support

You can contact a Customer Support Center by telephone or through the Online Support.

Online Support requires a user name and password. You can request a user name and password at

http://mysupport.informatica.com.

The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at http://www.informatica.com/us/services-and-training/support-services/global-support-centers/.

(9)

C

H A P T E R

1

Informatica AddressDoctor Cloud

This chapter includes the following topics:

• Informatica AddressDoctor Cloud, 1

• Key Features of Informatica AddressDoctor Cloud, 1 • New Features in This Release, 2

Informatica AddressDoctor Cloud

Informatica AddressDoctor Cloud is an online address validation solution that enables you to verify and validate international postal addresses in real time. Informatica AddressDoctor Cloud is a SOAP-based web service solution that is built on top of the latest Informatica AddressDoctor software. The current version of Informatica AddressDoctor Cloud is powered by Informatica AddressDoctor, Version 5.6.0.

You can integrate Informatica AddressDoctor Cloud with your CRM systems, e-commerce sites, or other cloud or web-based solutions and verify and validate the address data over secure (SSL) connections. The extensibility and flexibility of Informatica AddressDoctor Cloud help you access the latest features without having to change the interface. When changes to the interface do become necessary, Informatica AddressDoctor adds a new version of the interface. For example, v2 in the following example: http:// validator5.AddressDoctor.com/Webservice5/v2/...

If you do not want to upgrade immediately after a new version is released, you can continue to access the previous versions that are available even after a new version has been released.

Key Features of Informatica AddressDoctor Cloud

Informatica AddressDoctor Cloud provides the following features that significantly improve the user experience.

One Interface

Informatica AddressDoctor Cloud combines all process modes of its predecessor product, Web Service 4, into a single interface. This makes implementation of Informatica AddressDoctor Cloud much easier as there is only one application instead of the three different interfaces available previously. Informatica AddressDoctor Cloud supports up to 1000 addresses as input using batch mode and returns up to 100 addresses in the suggestion lists in the interactive and fast completion modes.

(10)

Extensibility

Informatica AddressDoctor Cloud has a very flexible Interface that enables you to implement new features without changing the Interface (that is, the WSDL). For example, the Version 4 Web Service defined enumerators for all parameters. Adding more options to the previous web service meant modifications to the interface. Informatica AddressDoctor Cloud defines the Parameter names, but not the values, which are plain String values. In this way new values can be added to existing parameters without changing the interface.

If an Interface change does become necessary in the future, Informatica AddressDoctor adds version information such as V1 or V2 in the URL. Customers can stay on a previous version and upgrade to the newer version when they are ready.

Improved Performance

Informatica AddressDoctor Cloud makes full use of the multi-threading capabilities of Informatica AddressDoctor. Additionally, Informatica AddressDoctor Cloud also benefits from the improved speed of individual address processing by Informatica AddressDoctor.

Default Method

The default call from Informatica AddressDoctor Cloud goes to the web method, process. Informatica AddressDoctor Cloud provides you objects for parameters and addresses just as the Web Service 4 did. These objects, however, have a new structure to support the capabilities of the V5 engine.

Note: Informatica AddressDoctor Cloud V2 does not support the Expert mode (ProcessEX).

New Features in This Release

Informatica AddressDoctor Cloud introduces the following new features in this release.

Single-Line Address Validation

You can use single-line address validation to validate addresses entered into the AddressComplete element as a single line and receive suggestions to complete the address. To use the single-line address validation, set the process mode to FASTCOMPLETION.

You can use single-line address validation to validate addresses from the following countries:

• Australia

• Canada

• Germany

• Great Britain

• New Zealand

• United States of America

Informatica AddressDoctor Cloud identifies address elements in a single-line address input based on their position in the sequence the elements are entered. So, it is imperative that you follow the order shown in the following table when you enter single-line addresses in the AddressComplete element. When you enter an address in single line, ensure that you do not mix Delivery Address Line (DAL) elements and Country-Specific Locality Line (CSLLN) elements.

(11)

The following table shows the order of address elements for the supported countries.

Country Order of Address Elements

Australia Sub-building, House Number, Street, Main Locality, Province, Postal Code

Canada Sub-building, House Number, Street, Delivery Service, Main Locality, Province, Postal Code

Germany Street, House Number, Postal Code, Locality, Province

Great Britain Sub-building, House Number, Street, Main Locality, SubLocality, Postal Code New Zealand Sub-building, House Number, Street, Delivery Service, Locality, Postal Code United States Sub-building, House Number, Street, Locality, Province, Postal Code

As you see in the preceding table, the typical sequence of address elements is from the specific to the generic. You must enter the elements in the specified sequence even if you leave out some of the elements from the input. However, for optimum results, we recommend that you provide as many details as possible in the input. Even though delimiters are not mandatory in a single-line address input, a comma or semicolon in the input is considered as an element separator and might fetch better suggestions. Note that Informatica AddressDoctor Cloud currently does not support country, organization, building, or contact information in the single-line address input.

If the single-line address input contains only a numeric input, Informatica AddressDoctor Cloud considers it as the Postal Code and returns suggestions accordingly. For countries where the house number appears on the left side of the street name or locality, if the single-line address input begins with a number that is followed by a string, Informatica AddressDoctor Cloud considers the number as a house number and the following string as the street name or locality. If no match is found for this combination, Informatica AddressDoctor Cloud attempts to interpret the input as street name without house number or as a combination of postal code and locality.

When there is no perfect match for an input, Informatica AddressDoctor Cloud returns multiple suggestions to help you choose the most appropriate result. If the single-line address input maps to a country that is not supported for single-line address validation, Informatica AddressDoctor Cloud returns the process status code

W9 which denotes that the address was not processed.

AddressCodeLookup

You can use the ADDRESSCODELOOKUP process mode to enter a country-specific address code and retrieve the complete or partial address for the code.

Because Informatica AddressDoctor Cloud considers the ADDRESSCODELOOKUP transactions as batch transactions, you must have sufficient batch transactions in your account to use this process mode.

Currently, Informatica AddressDoctor Cloud supports the ADDRESSCODELOOKUP process mode for the following countries and codes:

• Germany: DEU_AGS, DEU_LOCALITY_ID, DEU_STREET_ID

• South Africa.: ZAF_NADID

• Serbia: SRB_PAK

• UK: GBR_UDPRN

• Japan: JPN_CHOUMEI_AZA_CODE, JPN_CHOUMEI_AZA_GAIKU_CODE

(12)

Informatica AddressDoctor Cloud also introduces two new process status codes that denote the status of an ADDRESSCODELOOKUP request. A process status of A0 indicates that no information was found for the code you entered. A process status of A1 indicates that partial or complete address was available for the code you entered.

Configurable Output Format for Element Descriptors

You can specify the output format for street, building, and sub-building element descriptors in Australia and New Zealand addresses and the Strasse element in Germany addresses.

To specify the output format for the element descriptors, configure one of the following values for the GlobalPreferredDescriptor parameter.

DATABASE. Returns the element descriptor that the reference database specifies for the address. If the

database does not specify a descriptor for the address, Informatica AddressDoctor Cloud copies the input value to the output address. DATABASE is the default value.

LONG. Returns the expanded form of the element descriptor in the input address. SHORT. Returns the abbreviated form of the element descriptor in the input address.

PRESERVE_INPUT. Copies the element descriptor from the input address to the output address. If the input

element descriptor is not an official name, Informatica AddressDoctor returns the corresponding value from the reference address database. For example, BD is not an official name for boulevard in Australia. When you validate an Australia address where the input contains BD, Informatica AddressDoctor Cloud corrects it to BVD which is the short form for boulevard in the reference database for Australia addresses.

Point Address Geocoding

Informatica AddressDoctor Cloud supports the following point address geocoding types.

• Arrival Point (ARRIVAL_POINT). The geo-coordinates are calculated for a point that is placed in the center of a street segment in front of the house. If the arrival point geo-coordinates do not exist, then Informatica AddressDoctor uses the Standard Geocode database as a fallback to interpolate the geo-coordinates. Arrival Point geocoding is the default option. For United Kingdom addresses, Informatica AddressDoctor Cloud provides the rooftop geo-coordinates when the geocoding type is set to

ARRIVAL_POINT. Rooftop geo-coordinates are the measured coordinates for the center of the roof for the primary building on a parcel of land.

• Parcel Centroid (PARCEL_CENTROID). The geo-coordinates are calculated for a point that is at the geographic center of the parcel of land.

Informatica AddressDoctor Cloud provides the point address geo-coordinates for addresses from the following countries: • Austria • Canada • Denmark • Finland • Germany • Hungary • Latvia • Luxemburg • Mexico

(13)

Note: Informatica AddressDoctor Cloud supports only ARRIVAL_POINT geocoding for Mexico addresses. • Netherlands • Norway • Slovenia • Sweden • UK

Note: Informatica AddressDoctor Cloud supports only ARRIVAL_POINT (rooftop) geocoding for UK

addresses.

• USA

Support for Preserving Alias or Vanity Names for Localities and

Streets

You can choose to retain the aliases or vanity names for localities and streets in the validated address outputs. You can set one of the following values for the AliasLocality and AliasStreet parameters to specify whether you want the vanity name or the official name in the output.

• PRESERVE. To retain the alias name or vanity name in the validated output.

• OFFICIAL. To receive the alias or the postal name as mandated by the postal regulations of the country in

the validated output.

• OFF. To receive the postal name for the locality or street in the output.

The default value is OFFICIAL. If you are validating addresses in the certified mode, set these parameters to OFFICIAL.

Ability to Retrieve Address Codes for Outdated Japan Addresses

You can now set the MatchingExtendedArchive parameter to retrieve the new address code for deprecated or outdated addresses for Japan.

If the input address is an outdated address, and the MatchingExtendedArchive and SUPPLEMENTARY_JP parameters are enabled, Informatica AddressDoctor validates the old address against the archived

addresses in the reference database. Informatica AddressDoctor returns the validated outdated address with the old Choumei Aza code and the new Choumei Aza code as enrichment values. You can provide the new Choumei Aza code as input for the ADDRESSCODELOOKUP processing mode and receive the

corresponding new address. If MatchingExtendedArchive is set to OFF, the outdated input address is likely to be rejected, or to be corrected to some other address.

For outdated addresses, Informatica AddressDoctor Cloud returns an EERS value of F.

(14)

C

H A P T E R

2

Informatica AddressDoctor Cloud

Interface

• Interface Overview, 6

• SOAP 1.1 Headers and Envelope, 6 • SOAP 1.2 Headers and Envelope, 7 • Request XML, 7

• Response XML , 11

Interface Overview

You can use SOAP 1.1 or SOAP 1.2 to communicate with AddressDoctor Cloud. You can access AddressDoctor Cloud over HTTP port 80 or HTTPS port 443. Connections over HTTPS port 443 support encrypted messages and are secure.

SOAP 1.1 and SOAP 1.2 differ in the XML namespaces these two versions use. Additionally, in SOAP 1.2, the action parameter in the Content-Type header replaces the SOAPAction HTTP header in SOAP 1.1. Note that the SOAP interface for Informatica AddressDoctor Cloud is case-sensitive and use of wrong cases for elements, parameters, or values could cause the request to fail. For elements and parameters, use exactly the same case that is given in the Request XML section of this document. For values, always use UPPER CASE.

SOAP 1.1 Headers and Envelope

The following example shows a sample SOAP 1.1 request with the headers and the SOAP envelope XML. POST: /Webservice5/v2/AddressValidation.asmx

Host: 127.0.0.1

Content-Type: text/xml; charset=utf-8 Content-Length: length SOAPAction: "AddressDoctor/Webservice5/v2/Process" <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> 6

(15)

</soap:Body> </soap:Envelope>

The following example shows the SOAP response to the preceding request. HTTP/1.1 200 OK

Content-Type: text/xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ProcessResponse xmlns="http://validator5.AddressDoctor.com/Webservice5/v2"> </ProcessResponse> </soap:Body> </soap:Envelope>

SOAP 1.2 Headers and Envelope

The following example shows a sample SOAP 1.2 request with headers and envelope. Note the different Content-Type used and xmlns: soap declaration.

POST /Webservice5/v2/AddressValidation.asmx HTTP/1.1 Host: 127.0.0.1

Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://www.w3.org/2003/05/soap-envelope"> <soap:Body> <Process xmlns=" http://validator5.AddressDoctor.com/Webservice5/v2"> </Process> </soap:Body> </soap:Envelope>

The following example shows the SOAP 1.2 response to the preceding request. HTTP/1.1 200 OK

Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://www.w3.org/2003/05/soap-envelope"> <soap:Body> <ProcessResponse xmlns=" http://validator5.AddressDoctor.com/Webservice5/v2"> </ProcessResponse> </soap:Body> </soap:Envelope>

Request XML

The following example shows the <process> tag and its elements for both the SOAP 1.1 and SOAP 1.2 requests.

<Process xmlns="http://validator5.AddressDoctor.com/Webservice5/v2"> <login>string</login>

(16)

<password>string</password> <parameters> <ProcessMode>string</ProcessMode>  <ServiceParameters> <JobToken>string</JobToken> <CampaignId>string</CampaignId> <ReservedXml>string</ReservedXml> <UseTransactionPool>string</UseTransactionPool> </ServiceParameters>

<!-- <ValidationParameters> is optional; If you leave the validation

parameters blank, Informatica AddressDoctor Cloud uses the default values.--> <ValidationParameters> <FormatType>string</FormatType> <FormatDelimiter>string</FormatDelimiter> <DefaultCountryISO3>string</DefaultCountryISO3> <ForceCountryISO3>string</ForceCountryISO3> <CountryType>string</CountryType> <CountryOfOriginISO3>string</CountryOfOriginISO3> <StreetWithNumber>boolean</StreetWithNumber> <FormatWithCountry>boolean</FormatWithCountry> <ElementAbbreviation>boolean</ElementAbbreviation> <PreferredScript>string</PreferredScript> <PreferredLanguage>string</PreferredLanguage> <AliasStreet>string</AliasStreet> <AliasLocality>string</AliasLocality> <GlobalCasing>string</GlobalCasing> <GlobalMaxLength>int</GlobalMaxLength> <GlobalPreferredDescriptor>string</GlobalPreferredDescriptor> <MatchingScope>string</MatchingScope> <MaxResultCount>int</MaxResultCount> <DualAddressPriority>string</DualAddressPriority> <StandardizeInvalidAddresses>boolean</StandardizeInvalidAddresses> <RangesToExpand>string</RangesToExpand> <FlexibleRangeExpansion>boolean</FlexibleRangeExpansion> <GeoCodingType>string</GeoCodingType> <MatchingAlternatives>string</MatchingAlternatives> <MatchingExtendedArchive>boolean</MatchingExtendedArchive> <DisableCertifiedModeISO3>string</DisableCertifiedModeISO3> <FormatMaxLines>int</FormatMaxLines>  <Standardizations> <Element>string</Element> <Casing>string</Casing> <MaxLength>int</MaxLength> <MaxItemCount>int</MaxItemCount> </Standardizations>

<AdditionalInformationSet>

<Name>string</Name> <Value>string</Value> </AdditionalInformationSet>

<OutputOptions> <RecordId>string</RecordId> <Organization>string</Organization> <Department>string</Department> <Contact>string</Contact> <Email>string</Email> <Building>string</Building> <SubBuilding>string</SubBuilding> <Street>string</Street> <HouseNumber>string</HouseNumber> <DeliveryService>string</DeliveryService> <Locality>string</Locality> <PreferredLocality>string</PreferredLocality> <PostalCode>string</PostalCode> <Province>string</Province>

(17)

<Country>string</Country> <Residue>string</Residue> <RecipientLines>string</RecipientLines> <DeliveryAddressLines>string</DeliveryAddressLines> <CountrySpecificLocalityLine>string</CountrySpecificLocalityLine> <FormattedAddress>string</FormattedAddress> <AddressComplete>string</AddressComplete> <AddressDetailed>string</AddressDetailed> </OutputOptions> </ValidationParameters> </parameters> <addresses> <Address> <RecordId>string</RecordId> <Organization> <string>string</string> <string>string</string> </Organization> <Department> <string>string</string> <string>string</string> </Department> <Contact> <string>string</string> <string>string</string> </Contact> <Email> <string>string</string> <string>string</string> </Email> <Building> <string>string</string> <string>string</string> </Building> <SubBuilding> <string>string</string> <string>string</string> </SubBuilding> <Street> <string>string</string> <string>string</string> </Street> <HouseNumber> <string>string</string> <string>string</string> </HouseNumber> <DeliveryService> <string>string</string> <string>string</string> </DeliveryService> <Locality> <string>string</string> <string>string</string> </Locality> <PreferredLocality> <string>string</string> <string>string</string> </PreferredLocality> <PostalCode> <string>string</string> <string>string</string> </PostalCode> <Province> <string>string</string> <string>string</string> </Province> <Country> <string>string</string> <string>string</string> </Country> <Residue> Request XML 9

(18)

<string>string</string> <string>string</string> </Residue> <RecipientLines> <string>string</string> <string>string</string> </RecipientLines> <DeliveryAddressLines> <string>string</string> <string>string</string> </DeliveryAddressLines> <CountrySpecificLocalityLine> <string>string</string> <string>string</string> </CountrySpecificLocalityLine> <FormattedAddress> <string>string</string> <string>string</string> </FormattedAddress> <AdditionalAddressInformation> <Name>string</Name> <Value>string</Value> </AdditionalAddressInformation> <AdditionalAddressInformation> <Name>string</Name> <Value>string</Value> </AdditionalAddressInformation> <AddressComplete>string</AddressComplete> <AddressCode> <CodeType>string</CodeType> <Value>string</Value> </AddressCode> <AddressDetailed> <Street xsi:nil="true" /> <SubBuilding xsi:nil="true" /> <Residue xsi:nil="true" /> </AddressDetailed> </Address>

</addresses>  <enrichments> <Enrichment> <Type>string</Type> <PayloadXml>string</PayloadXml> </Enrichment>

</enrichments>

</Process>

Notes About Elements in the Request XML

• There are mandatory elements and optional elements. You must include the mandatory elements in the request. However, you can choose not to include the optional elements.

• <login> and <password> are mandatory elements. If you do not include these elements, an authentication error occurs.

• <ProcessMode> is a mandatory element.

• <ServiceParameters> is optional. However, in certain process modes, some of the service parameters are mandatory (for example, JobToken is needed when you resubmit a request in the FastCompletion mode).

(19)

• <ValidationParameters> is optional. If you omit this, Informatica AddressDoctor Cloud uses the default values for the validation parameters.

• <Standardizations> is optional.

• _{<AdditionalInformationSet> is for Informatica AddressDoctor internal use and is not supported in}

customer requests.

• _{<OutputOptions> and its elements are optional.} • _{<addresses> is mandatory.}

-At least one <Address> element must be supplied.

-Depending on the process mode specified, more <Address> elements can be supplied. -If any element of <Address> is omitted, that is considered as empty.

• _{<enrichments> is optional.}

Response XML

The following example shows the <ProcessResponse> tag and its elements.

<ProcessResponse xmlns="http://validator5.AddressDoctor.com/Webservice5/v2"> <ProcessResult> <StatusCode>int</StatusCode> <StatusMessage>string</StatusMessage> <JobToken>string</JobToken> <CampaignId>string</CampaignId> <ReservedXml>string</ReservedXml> <Results>

<! There is one <Result> element for each <Address> element in the request -->

<ProcessStatus>string</ProcessStatus> <CountryISO3>string</CountryISO3>

<Enrichments xsi:nil="true" /> </Result> </Results> </ProcessResult> </ProcessResponse> Response XML 11

(20)

C

H A P T E R

3

Informatica AddressDoctor Cloud

Request Elements

• Login and Password, 12 • ProcessMode, 13 • Service Parameters, 15 • Validation Parameters, 17 • Addresses, 28

• Enrichment, 29

Login and Password

Login and password are two mandatory parameters required to authenticate an Informatica AddressDoctor Cloud request.

The login parameter contains the Informatica AddressDoctor Data Quality Center (DQC) account ID. The password parameter contains the password for the Informatica AddressDoctor DQC account ID provided as the login.

If you do not know your Informatica AddressDoctor DQC account ID, you can log in to the Informatica AddressDoctor DQC portal by using your Informatica Passport credentials and view the Informatica DQC account ID and password. For more information about accessing the Informatica AddressDoctor DQC portal, see the Informatica AddressDoctor Data Quality Center User Guide.

If the values provided for login and password do not match with the corresponding values in the authentication server, or are left empty in the request, Informatica AddressDoctor Cloud returns an Authentication Failed error.

Example

The following example shows an Informatica AddressDoctor Cloud call. The login and password values are masked for security reasons.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="http://validator5.AddressDoctor.com/Webservice5/v2"> <soapenv:Header/> <soapenv:Body> <Process> <login>*****</login> 12

(21)

<password>**********</password> <parameters> <ProcessMode>INTERACTIVE</ProcessMode> </parameters> <addresses> <Address> <FormattedAddress>

<string>U 8 995 BURKE ROAD</string> <string>CAMBERWELL VIC 3124</string> <string>AUSTRALIA</string> </FormattedAddress> </Address> </addresses> </Process> </soapenv:Body> </soapenv:Envelope>

ProcessMode

ProcessMode is a mandatory parameter that you must specify in the request. You can specify one of the following values for the ProcessMode element.

AddressCodeLookup

You can use the ADDRESSCODELOOKUP process mode to enter a country-specific address code and retrieve the complete or partial address for the code. Because Informatica AddressDoctor Cloud considers the AddressCodeLookup transactions as batch transactions, you must have sufficient batch transactions in your account to use this process mode. Currently, Informatica AddressDoctor Cloud supports the AddressCodeLookup process mode for the following countries and codes:

• Germany: DEU_AGS, DEU_LOCALITY_ID, DEU_STREET_ID

• South Africa: ZAF_NADID

• Serbia: SRB_PAK

• UK: GBR_UDPRN

• Japan: JPN_CHOUMEI_AZA_CODE, JPN_CHOUMEI_AZA_GAIKU_CODE

Batch

If you want to cleanse large data files with minimal user intervention, set ProcessMode to BATCH. In batch mode, Informatica AddressDoctor Cloud corrects addresses but does not return address suggestions for the user to choose from. You can input up to 1000 addresses in a batch-mode request. For each of the address elements present in the request, Informatica AddressDoctor Cloud returns one result element in the response. Each of the result elements contains one ResultData element.

Certified

If you want to correct and validate addresses according to the postal certifications of countries such as Australia, Canada, France, New Zealand, or USA, set ProcessMode to CERTIFIED. Similar to the batch mode, the certified mode also enables you to correct and validate large data files with minimal human intervention. The following table lists the postal certifications that Informatica AddressDoctor Cloud currently supports. If you provide addresses that are from countries other than those that are supported for the certified mode, Informatica AddressDoctor Cloud processes such requests in batch mode. If you

(22)

also want Informatica AddressDoctor Cloud to return country-specific enrichments while validating addresses in the certified mode, you must include the required enrichment parameters in the request.

Country Certification Organization

Australia AMAS Australia Post

Canada SERP Canada Post

France SNA La Poste

New Zealand SendRight New Zealand Post

USA CASS United States Postal Service

Note: The CASS-certified data is available only from the United States-based data centers. If you are

accessing an Informatica AddressDoctor Cloud data center that is outside USA, you may not be able to use the certified mode for USA.

Interactive

If you want Informatica AddressDoctor Cloud to give you options to choose the best available match for an address, set ProcessMode to INTERACTIVE. In the interactive mode, Informatica AddressDoctor Cloud returns multiple suggestions that match the address you input. You can then choose the best possible match from the suggestions that Informatica AddressDoctor Cloud returned.

FastCompletion

If you want Informatica AddressDoctor Cloud to give you suggestions as you key in an address, set ProcessMode to FASTCOMPLETION. In the fast completion mode, you receive address suggestions with minimum input. For some countries like the United Kingdom, you need to enter only the postal code and building number to receive a complete address in many cases.

Informatica AddressDoctor Cloud also supports the single-line address validation using the

AddressComplete element in the fast completion mode. The single-line address validation support is available only for select countries.

For interactive and fast completion modes, only one Address element can be specified in the request. The response contains one Result element, but the ResultDataSet might contain up to 100 ResultData elements with the suggestions. The following table lists the process modes and how many elements each array can contain.

ProcessMode Addresses Results ResultDataSet

Batch or Certified Up to 1000 Up to 1000 0 to 1

Interactive or FastCompletion

1 1 0 to 100

Syntax

<ProcessMode>ADDRESSCODELOOKUP | BATCH | CERTIFIED | FASTCOMPLETION | INTERACTIVE</ProcessMode>

(23)

Example

The following example shows an Informatica AddressDoctor request for validating an address in the interactive mode. <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="http://validator5.AddressDoctor.com/Webservice5/v2"> <soapenv:Header/> <soapenv:Body> <Process> <login>*****</login> <password>**********</password> <parameters> <ProcessMode>INTERACTIVE</ProcessMode> </parameters> <addresses> <Address> <FormattedAddress>

Service Parameters

Service parameters in Informatica AddressDoctor Cloud requests are optional. You can include one or more of the following service parameters in an Informatica AddressDoctor Cloud request.

JobToken

This is an optional parameter, and is applicable only for interactive and fast completion mode requests. JobToken is an alphanumeric string that Informatica AddressDoctor Cloud returns in its response when an interactive or fast completion mode request fails to receive a ProcessStatus of V or C category. The alphanumeric string of JobToken can contain a maximum of 50 characters.The following is an example of JobToken:

You can include the JobToken value in the request when you resubmit an interactive or fast completion mode request that failed to receive a V or C status code. If the JobToken value in the request matches with a value that Informatica AddressDoctor Cloud returned to you, Informatica AddressDoctor Cloud recognizes the request as a resubmission of a previously uncompleted request. Such requests are not considered as new transactions and are not charged.

You can resubmit up to three interactive requests (the original request and two resubmissions using

JobToken) and five fast completion requests (the original request and four resubmissions using the JobToken) without being charged. However, if you use a JobToken for more than the maximum attempts allowed for interactive or fast completion requests, such requests are billed as new transactions.

(24)

CampaignId

This is an optional parameter. You can specify an arbitrary string value of up to 20 characters. Informatica AddressDoctor Cloud returns this string in its response.

ReservedXml

This is an optional parameter that is reserved for Informatica AddressDoctor use. You must exclude this from the request or leave this parameter empty.

UseTransactionPool

This is an optional parameter. You can include the UseTransactionPool parameter to specify the transaction pool that Informatica AddressDoctor Cloud must use for a call.

You can assign one of the following values for the UseTransactionPool parameter:

• ANY. Informatica AddressDoctor Cloud uses either production or test transaction pools based on the

availability. Note that Informatica AddressDoctor Cloud attempts to use the production transaction pool first and uses the test transaction pool only if there is no transaction left in the production pool. This is the default value.

• PRODUCTION. Informatica AddressDoctor Cloud uses only the production transaction pool.

• TEST. Informatica AddressDoctor Cloud uses only the test transaction pool.

Use the UseTransactionPool parameter if you have separate production and development environments. Even though it is technically possible to use both kinds of transactions in either environment, using test transactions for production purposes violates the Terms of Use, and using production (billable) transactions for testing reduces available transactions for the production environment.

Note: If you use the UseTransactionPool parameter during development, make sure to change the value to

production when deploying the application to the production environment. We recommend making this externally configurable, for example through a configuration file or Registry setting. Alternatively, you can use compiler switches or such code to distinguish the production environment from the development environment.

Example: Service Parameters

The following example shows an Informatica AddressDoctor Cloud request that contains the service parameters setting. <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="http://validator5.AddressDoctor.com/Webservice5/v2"> <soapenv:Header/> <soapenv:Body> <Process> <login>*****</login> <password>**********</password> <parameters> <ProcessMode>INTERACTIVE</ProcessMode> <ServiceParameters> <JobToken>b89be474-318c-4da3-87c2-f15b2e43c2cb</JobToken> <CampaignId>AddressDoctorTest</CampaignId> <ReservedXml/> <UseTransactionPool>PRODUCTION</UseTransactionPool> </ServiceParameters> </parameters> <addresses> <Address> <FormattedAddress>

(25)

Validation Parameters

Validation parameters are optional. If you do not specify validation parameters in the request, Informatica AddressDoctor Cloud uses the default value for parameters that have default values assigned to them.

FormatType

FormatType is an optional parameter that you can include in the request to specify what information goes in the FormattedAddress field. You can set one of the following values for the FormatType parameter:

• ADDRESS_ONLY. Specifies that only DeliveryAddressLine (DAL) and CountrySpecificLocalityLine

(CSLL) are included in the FormattedAddress field.

• WITH_ORGANIZATION. Specifies that organization information, DAL, and CSLL are included in the

FormattedAddress field.

• _{WITH_CONTACT. Specifies that contact, DAL, and CSLL are included in the FormattedAddress field.} • WITH_ORGANIZATION_CONTACT. Specifies that organization, contact, DAL, and CSLL are included in

the FormattedAddress field.

• WITH_ORGANIZATION_DEPARTMENT. Specifies that organization, department, DAL, and CSLL are

included in the FormattedAddress field.

• ALL. Specifies that organization, department, contact, DAL, and CSLL are included in the

FormattedAddress field. This is the default value.

You can use the FormatWithCountry or CountryOfOriginISO3 parameters to specify that the Country name be included in the formatted address line.

FormatDelimiter

FormatDelimiter is an optional parameter that you can use to specify the element separator for address elements in the AddressComplete element. Informatica AddressDoctor Cloud uses this setting for parsing both input and output. Even though delimiters are not mandatory in a single-line address input, an input with delimiters might fetch better suggestions.

You can specify one of the following delimiters for this parameter:

• LF (Line Feed) • SEMICOLON (Default) • SPACE • COMMA • PIPE (|) • TAB Validation Parameters 17

(26)

DefaultCountryISO3

DefaultCountryISO3 is an optional parameter you can include to specify the ISO-3 code of the country to which an address belongs to.

Include this parameter if most or all of the addresses that are input belong to one country and those

addresses do not contain the country information. By default, this parameter is left empty. If this parameter is left empty and Informatica AddressDoctor Cloud fails to recognize the country from the input address, a ProcessStatus of N1 is returned.

Example

ForceCountryISO3

ForceCountryISO3 is an optional parameter that you can include to override the country recognition capability of Informatica AddressDoctor Cloud.

When ForceCountryISO3 is set, Informatica AddressDoctor Cloud ignores any country information present in the data and applies the country specified for this parameter. You can set this parameter to the ISO-3 code of a given country. By default, this parameter is left empty. When this parameter is left empty, Informatica AddressDoctor Cloud uses its country recognition feature or the value provided in the DefaultCountryISO3 parameter to decide the country to which an address belongs to.

Example

CountryType

This is an optional parameter that you can use to specify the code or language to use in the country field and the country value in the FormattedAddress field. The default value for this parameter is NAME_EN which denotes the English name of the country.

The following table lists the supported values for the CountryType parameter and their descriptions.

CountryType Description

ISO2 ISO-2 code

ISO3 ISO-3 code

ISO_NUMBER ISO number

NAME_CN Chinese NAME_DA Danish NAME_DE German NAME_EN English NAME_KR Croatian NAME_NL Dutch

(27)

NAME_PL Polish NAME_PT Portuguese NAME_RU Russian NAME_SA Arabic NAME_SE Swedish NAME_ES Spanish NAME_FI Finnish NAME_FR French NAME_GR Greek NAME_HU Hungarian NAME_IT Italian NAME_JP Japanese

CountryOfOriginISO3

CountryOfOriginISO3 is an optional parameter that you can include to specify the country from where a mailing originates.

You can specify the ISO-3 code of the country from where the mailing originates, and Informatica

AddressDoctor Cloud leaves out the country name in the FormattedAddress output if the country in the input address and the country of origin are the same. Note that this setting works only if the FormatWithCountry parameter is set to ON.

If the country of origin and the country in the input address do not match, Informatica AddressDoctor Cloud retains the country information in the output. By default, this parameter is left empty. When this parameter is empty, Informatica AddressDoctor Cloud returns the country information in the FormattedAddress field of the output.

Example

StreetWithNumber

StreetWithNumber is an optional parameter that you can include to specify whether HouseNumber should be included in the Street field.

If this parameter is set to TRUE, Informatica AddressDoctor Cloud formats the house number to its correct position – before or after the street name – based on the local address conventions. By default, this parameter is set to FALSE.

(28)

FormatWithCountry

FormatWithCountry is an optional parameter that you can include to specify whether the country name should be included in the FormattedAddress field.

If FormatWithCountry is set to FALSE, Informatica AddressDoctor Cloud does not include the country name in the FormattedAddress field. If this parameter is set to TRUE and the CountryOfOriginISO3 parameter is configured, Informatica AddressDoctor Cloud returns the country name based on the value set to the latter.

ElementAbbreviation

ElementAbbreviation is an optional parameter that you can include to specify how Informatica AddressDoctor Cloud should handle street and locality names in the output.

When ElementAbbreviation is set to ON, Informatica AddressDoctor Cloud abbreviates the street and locality names for the U.S. addresses that are validated in the certified mode if the corrected address is longer than the USPS-specified length. When this parameter is set to ON in BATCH and INTERACTIVE modes, Informatica AddressDoctor Cloud abbreviates only the locality name if the output is longer than the length specified by USPS.

When ElementAbbreviation is set to ON, Informatica AddressDoctor Cloud abbreviates the output street name in Germany addresses to 22 characters if the reference database includes short names for the street. When ElementAbbreviation is set to ON, Informatica AddressDoctor Cloud leaves out the word CHOME from the Japan address output, and returns the CHOME number inside the number field. Typically, Informatica AddressDoctor Cloud includes the word CHOME in the street field of the output along with the number of CHOME.

When ElementAbbreviation is set to OFF, Informatica AddressDoctor Cloud returns the street and locality names based on the input, field-length setting, and the corresponding database entries.

PreferredScript

This is an optional parameter that you can include to specify the character set for the output. You can specify one of the following values for the PreferredScript parameter.

• DATABASE. Informatica AddressDoctor Cloud provides the output in the language the postal reference

database for a given country is in. This is the default value for PreferredScript.

• POSTAL_ADMIN_PREF. Informatica AddressDoctor Cloud provides the output in the language preferred

by the postal administration of a given country. Typically, this is the same as the DATABASE value.

• POSTAL_ADMIN_ALT. Informatica AddressDoctor Cloud provides the output in the alternate language

the postal administration of a given country permits. This setting works only for countries that have multiple native scripts. For example, when PreferredScript is set to POSTAL_ADMIN_ALT, AddressDoctor Cloud returns Japanese addresses in Kana characters instead of Kanji script, which is the

POSTAL_ADMIN_PREF for Japan.

• LATIN. Informatica AddressDoctor Cloud provides the output in Latin script. If the input was in a different

script, AddressDoctor Cloud transliterates such addresses to provide the output in Latin. Note that the Latin output might contain characters from any of the 15 different Latin character sets.

• LATIN_ALT. Informatica AddressDoctor Cloud provides the output in an alternate Latin transliteration.

This settings works only for countries that support multiple Latin transliterations. For example, when PreferredScript is set to LATIN_ALT, Russian addresses are transliterated according to BGN rules instead of ISO rules.

• LATIN_1. Informatica AddressDoctor provides the output in Latin-1 (Western European) characters.

(29)