Integrating with Experian QAS

3 Integrating with Experian QAS

This chapter describes how to integrate EDQ with Experian QAS API and migrate earlier versions of the QAS integration to EDQ versions 8.1.3 or later.

This chapter includes the following sections:

Software Requirements

EDQ includes a connector to the Experian QAS Batch API. You must have an installed version of the Experian QAS Batch API software appropriate for your platform. For more information, see the Experian Data Quality website found at http://www.qas.com/.

Integrating EDQ with Experian QAS

Integration of EDQ with Experian QAS Batch is carried out by editing the qas.properties file distributed with EDQ. The qas.properties file is located in the ORACLE_HOME/user_projects\domains\domains\edq_domain\edq\oedq.home\qas directory.

Once both EDQ and the QAS Batch software have been installed, edit the properties in the qas.properties as required for your integration. The properties specified in the file are as follows:

Property name	Description	Default Value
`qas.install.path`	The location of the Experian QAS Batch installation.	`C:\\Program Files (x86)\\QAS\\QuickAddress Batch API`
`qas.qaworld.ini`	The path to the `QAWorld.ini` file to use. This allows you to create and edit copies of the original `QAWorld.ini` file distributed with Experian QAS Batch API. If no value is specified for this property, it uses the `QAWorld.ini` file within the Experian QAS Batch API installation.	None
`max.number.connections`	The maximum number of connections that EDQ will create to the API. This should not be set to a value greater than 32. Note: There is a known threading and memory issue with Experian QAS Batch API versions 6.85, 6.89 and 6.95, where if maximum usage of 32 instances and 8 threads is reached, the Batch API may crash. This can be avoided by setting this property to a value between 18 and 22 inclusive.	32
`connection.pool.timeout`	This property specifies the number of milliseconds that a connection can be idle for before it is closed by the pool management functionality. If this is set to -1, idle connections will not be closed.	60,000
`connection.pool. timer.interval`	This property specifies how often, in milliseconds, the connection pool is scanned for idle connections.	60,000
`default.layout`	The default layout to use. If no layout with the specified name is available in the specified `QAWorld.ini` file, this property is ignored.	GBR

Migrating QAS integrations

Some earlier versions of EDQ (versions prior to 8.1.3) were shipped with a customized version of QAWorld.ini that was used instead of the version contained within Experian QAS. It is not possible to migrate automatically from these versions of the Experian QAS integration to the later versions. To migrate an earlier Experian QAS integration, you must:

Locate the local copy of QAWorld.ini and copy any custom layouts specified in this file into the version of QAWorld.ini contained within Experian QAS.
Update the settings in qas.properties See Integrating EDQ with Experian QAS.

In addition, any existing processes and results books that make use of QAS processors must be updated as follows:

Open each configured QAS processor and rename the output attributes to match those in the new QAWorld.ini file.
Open any results books built on results grids from QAS processors and re-map the fields to the new output attribute names.

Refer to the following table for the affected releases for each version of EDQ. All versions of EDQ (previously known as dn:Director) prior to 7.2 are affected:

Version	Releases affected
EDQ (dn:Director) 7.2	Release 7.2.9 and all earlier 7.2 releases
EDQ (dn:Director) 8.0	Release 8.0.21 and all earlier 8.0 releases
EDQ (dn:Director) 8.1	Release 8.1.2 and all earlier 8.1 releases