Guide To IBM Information Server Data Quality Module For SAP

IBM Information Server Data Quality Module for SAP

Version 2
Guide to IBM Information Server Data Quality Module for SAP
LC19-1181-00
IBM Information Server Data Quality Module for SAP

Version 2
Guide to IBM Information Server Data Quality Module for SAP
LC19-1181-00
Note
Before using this information and the product that it supports, read the information in “Notices” on page 49.
© Copyright International Business Machines Corporation 2006, 2007. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Chapter 1. Introduction to IBM Command variables for the update and search
Information Server Data Quality Module services . . . . . . . . . . . . . . . 22
Trace level settings for the update and search
for SAP . . . . . . . . . . . . . . . 1
services . . . . . . . . . . . . . . . 24
Editing the saprfc.ini file . . . . . . . . . . 25
Chapter 2. Installing and configuring the Parameters for the saprfc.ini file . . . . . . 25
data quality module. . . . . . . . . . 3 Installing instances of update and search services . . 26
Removing instances of update and search services 27
Chapter 3. Installing and configuring the Starting and stopping the update and search
system components . . . . . . . . . 5 services . . . . . . . . . . . . . . . . 27
Installing IBM OmniFind Enterprise Edition . . . . 5
Installing WebSphere Application Server 6.0 Refresh Chapter 6. Loading the reference
Pack 2 . . . . . . . . . . . . . . . . 7 database . . . . . . . . . . . . . . 29
Updating the HTTP server . . . . . . . . . 7 Initial load process . . . . . . . . . . . . 29
Updating WebSphere Application Server . . . . 7 Running the initial load process . . . . . . . 29
Updating the WebSphere Application Server Running the initial load process by using a file 30
plug-in . . . . . . . . . . . . . . . 8
Installing IBM Information Server Data Quality Chapter 7. Running the duplicate check
Module for SAP . . . . . . . . . . . . . 8 process . . . . . . . . . . . . . . 35
Installing the data quality module by using the
graphical interface . . . . . . . . . . . 8
Installing the data quality module in console Chapter 8. Threshold values for
mode . . . . . . . . . . . . . . . . 9 displaying matching objects . . . . . 37
Installing the data quality module in silent mode 9
Editing the es.cfg file . . . . . . . . . . 9 Chapter 9. Running the error-tolerant
Installing and registering the reference database . . 10 search process . . . . . . . . . . . 39
Creating the reference database . . . . . . . . 10
Preparing the search index . . . . . . . . . 11
Creating the collection . . . . . . . . . . 11
Chapter 10. Error messages . . . . . 41
Starting the parser service . . . . . . . . 12 Clearing the RFC queue . . . . . . . . . . 42
Creating the crawler . . . . . . . . . . 12
Configuring the index to use wildcard characters 13 Chapter 11. Troubleshooting data
Starting the data listener . . . . . . . . . 13 quality module errors . . . . . . . . 43
Configuring service properties for the data quality Ensuring that the update services are running . . . 43
module . . . . . . . . . . . . . . . . 14 Ensuring that the search services are running . . . 43
Service property variables . . . . . . . . 14 Ensuring that IBM DB2 is running . . . . . . . 44
Importing the business add-in package into SAP Ensuring that the ESAdmin application is running 44
CAM . . . . . . . . . . . . . . . . 15 Ensuring that IBM OmniFind services are running 45
Verifying the IMG address management entry . . 15 Investigating the search server communication with
Editing the node text for duplicate check and the collection . . . . . . . . . . . . . . 45
error-tolerant search . . . . . . . . . . 16 Ensuring that the data listener is running . . . . 45
Ensuring that the parse and search operations are
Chapter 4. Preparing the SAP running. . . . . . . . . . . . . . . . 46
components . . . . . . . . . . . . 17
Creating the RFC destinations . . . . . . . . 17 Accessing information about IBM . . . 47
Activating index pools . . . . . . . . . . . 18 Providing comments on the documentation . . . . 47
Updating the Customizing table . . . . . . . 18
Values for the Customizing table . . . . . . 18 Notices . . . . . . . . . . . . . . 49
Trademarks . . . . . . . . . . . . . . 51
Chapter 5. Managing data quality
module services . . . . . . . . . . 21 Index . . . . . . . . . . . . . . . 53
Data quality module services . . . . . . . . 21
Editing the command files for the update and
search services . . . . . . . . . . . . . 22
© Copyright IBM Corp. 2006, 2007 iii

iv Guide to IBM Information Server Data Quality Module for SAP
Chapter 1. Introduction to IBM Information Server Data Quality
Module for SAP
The IBM® Information Server Data Quality Module for SAP provides SAP-certified
functions for the duplicate check process and the error-tolerant search process.
After you install and configure the data quality module components, you can run
the following processes in SAP:
Error-tolerant search
Find names and addresses of customers, vendors, and business partners
even when you lack detailed knowledge of the name or the address.
Duplicate check
Maintain correct address records for vendors, customers, and business
partners by identifying duplicate records that might contain misspellings
and other erroneous data.
IBM Information Server Data Quality Module for SAP works as part of a system
that has the following major components:
v The SAP Central Address Management (CAM) system, including the SAP
business applications, their user interfaces, and the SAP CAM database. .
v IBM Information Server Data Quality Module for SAP installed on a server. This
server contains data quality module applications that are used for searches and
duplicate checking.
v A reference database, IBM DB2® V9.1, that you load with a subset of address
information from the SAP CAM database. The server component of the reference
database is installed on the same server on which you install IBM Information
Server Data Quality Module for SAP.
v The business add-in package for the data quality module, which synchronizes
the reference database with the SAP CAM database. This packages installed on
the SAP system.
v A search extender, IBM OmniFind™ Enterprise Edition V8.4, to process search
requests by using an index of the reference database. The search extender must
be installed on a server that hosts no other software programs. After you install
the search extender, you install the client component of the reference database
on the same server.
When a user of SAP who is creating or changing address data submits a request
for the error-tolerant search or duplicate check processes, the request triggers
processing on the principal data quality module server that can include using the
search extender and the reference database. The results of the request are returned
to the SAP interface.
When an SAP user creates or saves a record, the reference database is synchronized
with the SAP CAM database. To keep the databases synchronized, use the SAP
user interface for updates. Do not make updates directly to the SAP CAM database
because doing so does not ensure that the reference database is updated.
The following figure illustrates the architecture of the system.
© Copyright IBM Corp. 2006, 2007 1

SAP system Data Quality Module for SAP
SAP business IBM OmniFind server

application (GUI)
Search extender
Central Address
Management (CAM)
Principal server
Data Quality Module SAP
business add-in Gateway
package Search services
Update services
ODBC
CAM Database Reference

(customer, vendor,
business partner
database
information)
Related tasks
Chapter 7, “Running the duplicate check process,” on page 35
The duplicate check process identifies duplicate records that might contain
misspellings and other erroneous data.
Chapter 9, “Running the error-tolerant search process,” on page 39
You use the error-tolerant search process to locate customers, vendors, and
business partners when you do not have sufficient information about the name
or address. In SAP applications, this search method is also called fuzzy search
or rough search.
2 Guide to IBM Information Server Data Quality Module for SAP

Chapter 2. Installing and configuring the data quality module
You perform a sequence of tasks to install and configure the data quality module
and its related components.
To install and configure the data quality module, complete the following tasks:
1. Chapter 3, “Installing and configuring the system components,” on page 5
2. Chapter 4, “Preparing the SAP components,” on page 17
3. “Editing the command files for the update and search services” on page 22
4. Chapter 6, “Loading the reference database,” on page 29
5. “Preparing the search index” on page 11

Chapter 3. Installing and configuring the system components
The system components that you install include the search extender, the reference
database, and the IBM Information Server Data Quality Module for SAP. You
import the business add-in package.
Prerequisites:
v SAP R/3 Enterprise 4.7 Unicode or any other supported SAP application
installed in a location that the data quality module components can connect to.
See the IBM Information Server Data Quality Module for SAP release notes for a
list of supported SAP applications.
v A separate server running Microsoft® Windows® 2003 Enterprise Edition on
which to install the search extender.
v At least one server running Microsoft Windows 2003 Enterprise Edition on
which to install the reference database and the IBM Information Server Data
Quality Module for SAP. You can install each component on a separate server
but each server must run on Microsoft Windows 2003 Enterprise Edition.
v A list of available ports on each computer. You can use the netstat command to
determine available ports.
To install and configure the system components, perform these tasks and their
subtasks in the following order:
1. “Installing IBM OmniFind Enterprise Edition.”
2. “Installing WebSphere Application Server 6.0 Refresh Pack 2” on page 7.
3. “Installing IBM Information Server Data Quality Module for SAP” on page 8.
4. “Installing and registering the reference database” on page 10.
5. “Creating the reference database” on page 10.
6. “Preparing the search index” on page 11.
7. “Configuring service properties for the data quality module” on page 14.
8. “Importing the business add-in package into SAP CAM” on page 15.
When you complete the installation tasks, you must configure the customizing
program in SAP and run the initial load of data to the reference database.
Related tasks
Chapter 4, “Preparing the SAP components,” on page 17
To use the data quality module with SAP CAM, you create RFC destinations,
activate index pools, and update the Customizing table.
Chapter 6, “Loading the reference database,” on page 29
You load the reference database with a subset of information from the SAP
CAM database.
Installing IBM OmniFind Enterprise Edition

To install the search extender, you install IBM OmniFind Enterprise Edition Version
8.4. WebSphere® Application Server is installed as part of this process.
Prerequisites:
v Install the software on Microsoft Windows 2003 Enterprise Edition. No other
software should be installed on the server.

v Install a RAID disk array that is attached to the server.
v Meet all required prerequisites listed in Required and optional software and
hardware for OmniFind Enterprise Edition at www.ibm.com/support.
Check your list of available ports, and accept all default port settings in the
installation, unless they cause a conflict. If you specify ports that are not default,
keep a record of the ports that you specify.
To install IBM OmniFind Enterprise Edition:

1. Locate the installation executable file on the CD or downloaded image, and
double-click the file to start the installation wizard.
2. Follow the prompts to install the software and accept the license terms.
Specify the information that is required in the following steps of this
procedure and click Next on each page of the wizard.
3. Select Install a new version of WebSphere Information Integrator OmniFind
Edition.
4. Specify the user ID and password for the enterprise search administrator. The
default user ID esadmin is recommended. If you specify an existing user, that
user must have permission to run Windows services.
5. In the Installation directory field, specify the directory in which to install IBM
OmniFind Enterprise Edition.
6. In the Data directory field, specify the directory of the RAID disk array in
which to store the index data.
7. Select Single Server to install all search extender services on one server.
8. Clear the Install WebSphere Information Integrator Content Edition
connectors checkbox.
9. Specify the host name of the server.
10. To maximize performance, select Large for the memory configuration size.
11. Select Install WebSphere Application Server.
12. Specify the installation directory and plug-in installation directory for
WebSphere Application Server.
13. Specify the installation directory for the IBM HTTP Server.
14. Accept the default node name and specify the host name for WebSphere
Application Server.
15. Select Run WebSphere Application Server as a service and Run IBM HTTP
Server as a service.
16. Type the user ID and password for WebSphere Windows services. You can use
search administrator user ID that you created in step 4.
17. Select one or more languages to install for online help.
18. Click Install.
Do not stop the installation before it finishes. When the installation finishes,
the Installation Results window opens.
19. In the Finish window, clear the Start First Steps checkbox.
20. Select No, I will restart my computer at a later time, and click Finish.

Installing WebSphere Application Server 6.0 Refresh Pack 2
The refresh pack updates the HTTP server, the WebSphere Application Server, and
the WebSphere Application Server plug-in.
Prerequisite: “Installing IBM OmniFind Enterprise Edition” on page 5.
To install WebSphere Application Server 6.0 Refresh Pack 2:

1. Update the HTTP server.
2. Update WebSphere Application Server.
3. Update the WebSphere Application Server plug-in
4. Activate the DB2 crawler. For instructions, see Enable DB2 crawler to crawl DB2
V9.1 database at www.ibm.com/support.
5. Restart WebSphere Application Server.
Updating the HTTP server

You update the HTTP server as the first step when you install WebSphere
Application Server 6.0 Refresh Pack 2.
Prerequisite: “Installing IBM OmniFind Enterprise Edition” on page 5.
To update the HTTP server:

1. Open the 6.0-WS-WASIHS-WinX32-RP0000002 folder in the IBM OmniFind
Enterprise Edition CD or downloaded image, and copy the updateinstaller
folder to the IBM HTTP server folder. The , IBM HTTP server folder is installed
by default at C:\Program Files\IBM HTTP Server.
2. In the updateinstaller folder, run update.exe.
3. In the update installer window, do the following steps. Click Next when
necessary to move to the next page.
a. Confirm that the HTTP server root directory is specified correctly.
b. Install the maintenance package.
c. On the results page, click Finish.
Updating WebSphere Application Server

You update WebSphere Application Server as the second step when you install
WebSphere Application Server 6.0 Refresh Pack 2.
Prerequisite: “Updating the HTTP server.”
To update WebSphere Application Server:

1. Open the 6.0-WS-WAS-WinX32-RP0000002 folder in the IBM OmniFind
Enterprise Edition 8.4 CD or downloaded image, and copy the updateinstaller
folder to the root folder of WebSphere Application Server, which is installed by
default at C:\Program Files\IBM\WebSphere\AppServer.
2. In the updateinstaller, folder run update.exe.
a. Confirm that the root directory of WebSphere Application Server is specified
correctly.
Chapter 3. Installing and configuring the system components 7

If the update fails, ensure that WebSphere Application Server is not running, and
repeat steps 1-3.
Updating the WebSphere Application Server plug-in

You update the WebSphere Application Server plug-in as the third step when you
install WebSphere Application Server 6.0 Refresh Pack 2.
Prerequisite: “Updating WebSphere Application Server” on page 7.
To update the WebSphere Application Server plug-in:

1. From the 6.0-WS-WASPlugIn-WinX32-RP0000002 folder in the IBM OmniFind
Enterprise Edition 8.4 CD or downloaded image, copy the updateinstaller
folder to the root folder for WebSphere Application Server plug-ins, which is
installed by default at C:\Program Files\IBM\WebSphere\Plugins.
2. In the updateinstaller folder, run update.exe.
a. Confirm that the location of the WebSphere\Plug-ins directory is specified
correctly.
If the update fails, ensure that WebSphere Application Server and the HTTP server
are not running, and repeat steps 1-3.
Installing IBM Information Server Data Quality Module for SAP

You can install the data quality module by using the graphical interface, in silent
mode, or in console mode.
You must install IBM Information Server Data Quality Module for SAP on a
Windows 2003 Enterprise Edition computer.
For multiple installations that use the same settings, you can install the data
quality module in silent mode by using a response file.
To install the data quality module, do one of the following tasks:

v “Installing the data quality module by using the graphical interface”
v “Installing the data quality module in silent mode” on page 9
Related tasks
“Editing the command files for the update and search services” on page 22
You edit the command files to configure the services and the interaction
between system components.
Installing the data quality module by using the graphical

interface
You can use the wizard to install the data quality module.
To install the data quality module by using the graphical interface:

1. In the CD or downloaded image, double-click setup.exe.
2. Follow the prompts to install the data quality module.

3. Save your settings to a response file if you plan to run installations in silent
mode.
4. Edit the es.cfg file.
Installing the data quality module in console mode

You can install the data quality module from a command prompt rather than from
a wizard window.
To install the data quality module in console mode:

1. From the root directory of the CD or downloaded image, run the following
command to start the installer in console mode. You can optionally provide a
log file and use a different temporary directory.
install -console
2. Follow the prompts to install the data quality module.
3. Save your settings to a response file if you plan to run installations in silent
mode.
Installing the data quality module in silent mode

You can install the data quality module in silent mode by using a response file.
You can use a response file to perform multiple installations with the same
settings.
To install the data quality module in silent mode:

1. Create a response file by following steps 1-4 of “Installing the data quality
module by using the graphical interface” on page 8. You can complete the
installation by using the wizard or exit the wizard after saving your settings.
The response file is saved by default to C:\Documents and
Settings\user\is_dq_module_sap.rsp where user is the account of the person
who created the response file.
2. If required, move the response file and the installation media to the computer
where you want to install the suite.
3. Open a command prompt and change to the root directory of the IBM
Information Server Data Quality Module for SAP CD or downloaded image.
4. Enter install.exe -silent -options response_file_name_and_path to run the
installer in silent mode from the command line.
The following example shows how to run the install command in silent mode. The
installer reads the installation options from the response file is_dq_module_sap.rsp.
install.exe -silent -options c:\temp\is_dq_module_sap.rsp
Related tasks
Editing the es.cfg file

You must copy and edit the es.cfg file after installing the data quality module.
Prerequisite: “Installing IBM Information Server Data Quality Module for SAP” on
page 8

1. In a command prompt on the server where you installed IBM OmniFind
Enterprise Edition, enter echo %ES_CFG%. The path of the file es.cfg is displayed.
2. Copy the file to the installation directory on the server where you installed the
data quality module.
3. In the installation directory, open the file in a text editor and append the
following line to the end of the file:
es_server_hostname=hostname
Where hostname is the case-sensitive name or IP address of the server on which
you installed IBM OmniFind Enterprise Edition.
Installing and registering the reference database

You must install the IBM DB2 version 9.1 client and server components and
register the product license key.
Prerequisite: Ensure that you meet all prerequisites listed in Version 9 installation
prerequisites for Windows at www.ibm.com/support.
Installation is supported only on Microsoft Windows 2003 Enterprise Edition. You

install the server component of the reference database on the computer on which
you installed IBM Information Server Data Quality Module for SAP. You install the
client component on the computer on which you installed IBM OmniFind
Enterprise Edition. Accept all default settings when you install the server and
client. For more information about installing the database, see the IBM DB2
documentation included in the CD or downloaded image.
To install and register the reference database:

1. On the computer on which you installed IBM Information Server Data Quality
Module for SAP, install DB2 Enterprise Server Edition version 9.1 for Windows
from the DB2 product CD or downloaded image.
2. On the computer on which you installed IBM OmniFind Enterprise Edition,
install DB2 Client version 9.1 for Windows from the DB2 product CD or
downloaded image.
3. Log on to the computer where you installed the server edition as administrator.
4. In a command window, enter db2licm -a filename , where filename is the full
path and file name for the license file for the DB2 product. The license file is in
the db2\license directory in the IBM Information Server Data Quality Module
for SAP CD or downloaded image.
For example, if the CD drive is E: and the name of the license file is db2ese_o.lic,
enter the following command:
db2licm -a E:\db2\license\db2ese_o.lic
Creating the reference database

You create the reference database in IBM DB2 Control Center.
Prerequisite: “Installing and registering the reference database”
To create the reference database:

1. Open IBM DB2 Control Center.
2. Choose Tools → Command Editor.
3. Choose Selected → Open.

4. In the Open dialog box, select the file createDQMDB.sql, on the server where
you installed the data quality module, and click OK. This file is installed by
default at C:\IBM\ISDQSAP.
5. Choose Selected → Execute.
The reference database is created.
Preparing the search index

You prepare a search index that is based on the reference database. The search
service uses the search index to find addresses and duplicates.
Prerequisite: Use the IBM DB2 client to catalog the node, instance, and database of
the reference database into the DB2 directory of the server on which you installed
IBM OmniFind Enterprise Edition.
To prepare the search index:

1. In a Web browser, enter http://host/ESAdmin, where host is the name of the
search server, to open OmniFind Enterprise Search Administrator.
2. Log in by using the search administrator account that you created when you
installed IBM OmniFind Enterprise Edition.
3. Complete the following tasks:
a. “Creating the collection”
b. “Starting the parser service” on page 12
c. “Creating the crawler” on page 12
d. “Configuring the index to use wildcard characters” on page 13
e. “Starting the data listener” on page 13
Creating the collection

You create the collection as the first task when you prepare the search index. The
collection includes the crawl database, parser service, and index.
Prerequisite: Log in to OmniFind Enterprise Search Administrator.
To create the collection:

1. Click Create Collection.
2. In the Collection window, provide information about the collection:
a. Type a collection name. For example, type DQMCollection.
b. Do not change the default estimated number of documents, which is
1,000,000.
c. Select Collection security → Do not enable security for the collection .
d. Select Document importance → Do not apply any static ranking
e. Do not edit the default location of collection data.
f. Select Custom ID for the collection ID, and type an identifier in the text box.
Record the ID, because it is used to configure the search and update
services.
g. Select Categorization type → None.
h. Select N-gram segmentation → Enable for languages that do not use blanks
or delimiters.
i. From the Language to use menu, select a language.

j. Click OK. The collection is created and the application returns to the home
page, where the collection is listed.
In OmniFind Enterprise Search Administrator, start the parser service.
Starting the parser service

You start the parser service as the second task when you prepare the search index.
Prerequisite: “Creating the collection” on page 11

1. On the home page of OmniFind Enterprise Search Administrator, click Parse.
2. Click (Start) to start the parser service. The Parse Status button changes
color from red to green.
In OmniFind Enterprise Search Administrator, create the crawler.
Creating the crawler

You create the crawler as the third task when you prepare the search index.
Prerequisite: “Starting the parser service”
To create the crawler:

1. On the home page of OmniFind Enterprise Search Administrator, click Crawl.
2. Under the ESAdmin toolbar, click (Edit).

3. Click Create Crawler.
4. In the Create Crawler window, choose Crawler type → DB2.
5. Use the system default values for the new crawler, and click Next.
6. Type a name for the crawler, retain all default values, and click Next.
7. In the Select the DB2 Database type page, select Local or cataloged databases.
8. Click Next as necessary to advance to the Database name or pattern page.
9. Click Search for databases to populate the Available databases page.
10. Select the name of the reference database and click (Start) to populate
the Databases to crawl text box.
11. Type the user ID and password for the database, and click Apply.
12. Click Next as necessary to go to the Tables to crawl page.
13. Click Crawl specific tables.
14. Click Search for tables.
15. From the Available tables page, select ADDMNS1, and click (Start) to
add the ADDMNS1 table to the Tables to crawl field.
16. Click Apply, and click Next twice.
17. Under Edit Options, click (Edit).

18. Under the Complete match column, select All.
19. At the bottom of the page, click OK.
20. Click Finish.

In OmniFind Enterprise Search Administrator, configure the index to use wildcard
characters.
Configuring the index to use wildcard characters

You configure the index to use wildcard characters as the fourth task when you
prepare the search index.
Prerequisite: “Creating the crawler” on page 12
To configure the index to use wildcard characters:

1. On the home page of OmniFind Enterprise Search Administrator, click Index.
2. Click (Edit).
3. Select Configure options for wildcard characters.
4. Select Support wildcard characters in queries to enable more options.
5. Clear Support wildcard characters in queries that search free text.
6. Select All fields.
7. Ensure that Trailing only: Expand terms in the index (increases the size of
the index) Minimum number of matching characters: 1 is selected.
8. Click OK.
9. Click Search.
10. Verify that Status button displays a green arrow, which means that the search
is running. If the search is not running, click (Start). The collection is

ready for search.
In OmniFind Enterprise Search Administrator, activate the data listener.
Starting the data listener

You start the data listener as the fifth task when you prepare the search index.
The update service uses the IBM OmniFind Data Listener interface to queue
updates.
Prerequisite: “Configuring the index to use wildcard characters”
To start the data listener:

1. In OmniFind Enterprise Search Administrator, click System on the ESAdmin
toolbar. The data listener status is shown as running.
2. Click (Edit) to edit the listener options.

3. Click Configure Data Listener applications.
4. Use the default settings unless the default port number 6668 is being used on
the computer on which you installed IBM OmniFind Enterprise Edition. If
port 6668 is being used, enter a different port number and record the number
to use later.
5. Click Add Data Listener Application.
6. In the Data Listener client ID field, type an ID and password. Record these
credentials to use later.
7. Ensure that Specific Collections is selected.

8. In the Select column, select the collection name that you created.
9. Click OK.
10. In the Data Listener window, click OK.
11. Click (Monitor).
12. Click (Restart) to restart the data listener.
You have prepared the search index to load the reference database.
Configuring service properties for the data quality module

You configure the properties file to specify values that are used by the search
index.
To configure service properties for the data quality module:

1. In a text editor, open the file ISDQMSAP.properties in the root directory where
you installed the data quality module.
2. Edit the file to specify the required information.
Service property variables

The values of service property variables specify information that is used by the
search index.
The values are contained in the file ISDQMSAP.properties located in the root folder
of your installation of IBM Information Server Data Quality Module for SAP, by
default C:\IBM\ISDQSAP\ISDQMSAP.properties.
Table 1. Service property variables
Variable Description
hostname The host name of the server on which IBM OmniFind Enterprise
Edition is installed.
port The port that connects to the server on which IBM OmniFind
Enterprise Edition is installed. The default is 80.
collectionID The collection ID that you specified when you created the
collection. This can also be retrieved by executing the command
esadmin check in a command window on the search server.
traceLevel The Java trace level to log Java errors, warnings and information
that is written to the logs:
0 No logging.
1 Severe errors are logged.
2 Severe errors and warnings are logged.
3 All query information is logged including Java search
time and the query strings that are processed.
ODBCDriver The name of the ODBC driver. Do not change the default value,
which is com.ibm.db2.jcc.DB2Driver.
ODBCConURL The ODBC connection string. The last part of this string is the
ODBC data source name, which is the name of the reference
database. The default is jdbc:db2:DQMDB.
DBName The name of the reference database. The default is DQMDB.

Table 1. Service property variables (continued)
Variable Description
DBuser The user account which created the reference database.
DBpswd The encoded password for the reference database. Create the
encoded password by executing
java DQMchgpw DBpassword
from the installation directory of the data quality module, where

DBpassword is the password for user account.
repThreshold If the first iteration of the query plan returns a number of
records that is less than or equal to this number, the query plan
runs again using shortened query tokens. Setting this value too
high impacts search performance. The default is 10.
maxTokLen The maximum number of characters in a query token. This value
is used when the query plan runs a second time. The default is
4.
DLport The port for the data listener that you specified when you
configured the data listener. The default is 6668.
DLclientID The data listener client ID that you specified when you
configured the data listener.
DLpasswd The data listener password that you specified when you
configured the data listener.
refreshInterval The time in minutes between refreshes of the search index. The
default is 120.
Related tasks
“Starting the data listener” on page 13
You start the data listener as the fifth task when you prepare the search index.
“Creating the collection” on page 11
You create the collection as the first task when you prepare the search index.
The collection includes the crawl database, parser service, and index.
Importing the business add-in package into SAP CAM

You import the business add-in package into the SAP CAM system to keep the
reference database synchronized with the SAP CAM database.
To import the business add-in package:

1. From the business add-in CD or downloaded image, copy the file with the
extension .pat from the folder that corresponds to the SAP application that you
use, and move it to the SAP system.
2. Call the SAP transaction SAINT to import the file into the SAP CAM system.
You must verify that the correct node text appears under Address Management.
Verifying the IMG address management entry

You verify the entry after importing the business add-in package.
Prerequisite: “Importing the business add-in package into SAP CAM”
To verify the IMG address management entry:

1. In SAP, call transaction SPRO.

2. Choose Goto → Sap Reference IMG.
3. Choose Edit → Find.
4. In the Search Term field, type Address Management and press Enter.
5. In the list of search results, double-click the first instance of Address
Management. An expanded IMG structure is displayed.
6. Click to expand Address Management.
7. Do one of the following steps:
v If IBM Information Server Duplicate Check and Error-tolerant Search is the
first node displayed, leave the transaction.
v If a node is displayed with the text Node text not found, edit the node text
to display the correct text.
Editing the node text for duplicate check and error-tolerant

search
You can manually add a node name for address management.
Prerequisites:
v “Importing the business add-in package into SAP CAM” on page 15
v “Verifying the IMG address management entry” on page 15
After you import the business add-in package, if IBM Information Server
Duplicate Check and Error-tolerant Search is not displayed as a node beneath
Address Management, you must edit the node text.
To edit the node text:

1. In SAP, call transaction SIMGH.
2. In the Edit IMG structure pane, click the selection button for the IMG
structure field.
3. In the Title field of the Find Structure window, type Address management and
press F8.
4. In the Explanatory Text window, double-click Address management.
5. From the IMG structure menu, choose Change.
6. Click the check mark to close each of the two warning messages.
7. Select Node text not found and choose Edit → Nodes → Change.
8. Type IBM Information Server Duplicate Check and Error-tolerant Search
in the text box and click the check mark.
9. Choose Implementation Guide → Save.
10. Choose an existing workbench request transport or create a new workbench
request transport and click the check mark. If required, confirm the new
request.
11. Call transaction SE09 to release the request.

Chapter 4. Preparing the SAP components
Prerequisite: Chapter 3, “Installing and configuring the system components,” on

page 5
To prepare the SAP components:

1. Create the RFC destinations for search and update.
2. Activate index pools.
3. Update the Customizing table.
Creating the RFC destinations

You define remote functional call (RFC) destinations in SAP for the functions that
control searching, duplicate checking, and maintaining the reference database.
This procedure sets up destination objects from the application labeling and
enabling (ALE) layer in SAP. You create RFC destinations for the update service,
which maintains the reference database, and for the search service, which controls
searching and duplicate checking.
To create the RFC destinations:

1. In SAP, call transaction SM59.
2. In the Display and Maintain RFC Destinations window, click Create to display
the RFC Destination panel.
3. Specify the following information:
a. In the RFC destination field, type DQMUpdate to specify the destination for
the updated service.
b. In the Connection type field, type T.
c. In the Description field, type a description of the connection.
4. Click Registered Server Program.
5. In the Program ID field, type DQMUpdate to specify the ID of the update service.
The program ID must match the PROGID parameter specified in the file
saprfc.ini, which is in the root folder of the data quality module installation, by
default C:\IBM\ISDQSAP\saprfc.ini.
6. Select the Special Options tab, and in the Character Width section, select
Unicode.
7. Repeat steps 2 through 5 to configure the destination for the search service.
Type DQMSearch in the RFC destination field and in the Program ID field.
Related tasks
“Editing the saprfc.ini file” on page 25
You edit the saprfc.ini file to specify the host name and service name of the
SAP gateway.

Activating index pools
You activate all index pools for addresses that are used for the error-tolerant search
and duplicate check processes.
To activate the index pools:

1. In SAP, click Activate duplicate check index pools to start the transaction.
2. Activate the index pools that you want to include in the error-tolerant search
and duplicate check processes. If the system is CRM, do not select KNA1.
Updating the Customizing table

You run the customizing program to update the Customizing table with
information about the activated index pools and RFC destinations.
Prerequisites:
v “Creating the RFC destinations” on page 17
v “Activating index pools”
To update the Customizing table:

1. In SAP, call transaction /n/ASCQS/QS_CUS1 to run the customizing program.
The program looks for activated index pools and checks the RFC destination
used for the update process. The Destinations window opens.
2. In the RFC Destinations for Update field, type DQMUpdate.
3. In the RFC Destination for Search field, type DQMSearch.
4. Click Execute to update the Customizing table.
When the update is complete, the Customizing table opens with the active pools
displayed.
Values for the Customizing table

You can edit values in the Customizing table to change thresholds, RFC
destinations, and packet size.
The Customizing table displays the application table and the application field of an
active search index and values for the initial load of data to the reference table.
In the left view of the table, you can edit values for the following fields:
Threshold DC
The threshold value that limits the number of records displayed in the
Duplicate Check Hit List. The default is 15 percent.
Threshold FS
The threshold that limits the number of records displayed in the Rough
Search Hit List. The default is 10 percent.
RFC Destination UPDATE
The RFC destination name that is used when you add or change a record.
This name is specified as DQMUpdate when you create the RFC
destinations.
RFC Destination SEARCH
The RFC destination name that is used when you search for a record. This
name is specified as DQMSearch when you create the RFC destinations.

Packet Size
The number of addresses that are sent in one transaction. The
recommended value is 2000. The maximum value is 4000.
Related concepts
Chapter 8, “Threshold values for displaying matching objects,” on page 37
The error-tolerant search process and the duplicate check process use threshold
values to display objects that are similar to the data that you enter in SAP.
Chapter 4. Preparing the SAP components 19

Chapter 5. Managing data quality module services
You configure and start and stop the services that support the search and update
processes. You can install and remove additional service instances depending on
the performance requirements of your SAP system.
Data quality module services

The data quality module update and search services synchronize the reference
database and coordinate the search components. The index refresh service updates
the search index.
The default installation of the data quality module creates two instances of the
update service and two instances of the search service. You can install additional
update and search services.
All instances of the update service use the same command file, and all instances of
the search service use the same command file.
Each service instance has an entry in the Services window of the Windows Control
Panel for starting and stopping the service.
You can configure the command files for the update and search services in a text
editor and start and stop all service instances from the Windows Control Panel. It
is not necessary to configure the index refresh command file.
The following table lists the services, their command files and the default control
panel icons.
Service Command file Default service name

update DQMUpdate.cmd DQMUpdate1
DQMUpdate2
search DQMSearch.cmd DQMSearch1
DQMSearch2
index refresh DQMIndexRefresh.cmd DQMIndexRefresh
The command files are installed in the root folder of your installation of IBM
Information Server Data Quality Module for SAP, by default C:\IBM\ISDQSAP.
You edit both command files before running the initial load process.
You start the update services before running the initial load process, and start all
services after preparing the search index. When the search index is complete, you
can set the services to start automatically.
Using additional search and update services
The update service is used to update the reference database. The search service is
used for both the error-tolerant search and duplicate check processes. .

When a user invokes the error-tolerant search process or the duplicate check
process, each SAP request is routed to a search service instance that is not busy. If
all service instances are busy, the request waits until a service instance is available.
In some cases, when users make more concurrent requests than the default service
instances can handle, system performance can be degraded.
You can install additional service instances to support more concurrent requests.
You can also install additional update services. These additional services use the
same command files as the default services.
The search service is used more frequently than the update service. You can choose
to install more search services than update services.
How many services you can run successfully depends on how many processors
and how much memory the computer has. If you install and start more services
then the computer can handle, all services on the machine are slowed.
Related tasks
“Installing instances of update and search services” on page 26
When you install additional instances of the update and search services, you
install one instance at a time.
“Removing instances of update and search services” on page 27
You can remove one instance of a service at a time.
“Starting and stopping the update and search services” on page 27
You can start and stop instances of the services from the Windows Control
Panel.
Editing the command files for the update and search services
You edit the command files to configure the services and the interaction between
system components.
Before you run the initial load process, you must edit the command files for the
update and search services to specify the location of components and to ensure
that the default values are accurate. The command files are in the root folder of
your installation of IBM Information Server Data Quality Module for SAP, by
default C:\IBM\ISDQSAP.
To edit the command files for the update and search services:
1. In a text editor, open the DQMUpdate.cmd file and edit the values of the
command variables for the update services. Save your changes.
2. Open the DQMSearch.cmd file and edit the values of the command variables
for the search services. Save your changes.
Related tasks
“Starting and stopping the update and search services” on page 27
You can start and stop instances of the services from the Windows Control
Panel.
Command variables for the update and search services

The values of command variables specify information about the update and search
services, including the locations of components and log files.
The data quality module services are configured in two command files:
DQMUpdate.cmd and DQMSearch.cmd. The command files are in the root folder

of your installation of IBM Information Server Data Quality Module for SAP, by
Table 2. Command variables
Variable Argument Description
workdrive The drive where you
installed IBM Information
Server Data Quality Module
for SAP
INTBIN The root folder of the data
quality module installation,
by default C:\IBM\ISDQSAP
ARD –a The path to the data quality
module application
definition:
v For the DQMSearch
service
%INTBIN%\ISDQMSAP\
Scripts\ARDS\WAVECRM
v For the DQMUpdate
service
%INTBIN%\ISDQMSAP\
Scripts\ARDS\
MNVCRMS
Controls –c %INTBIN%\ISDQMSAP\
Controls
rfcname –n The name of the RFC
program registered in the
SAP server. This name
cannot be changed.
v For the DQMSearch
service:
/ASCQS/
QS_ADDRESS_SEARCH
v For the DQMUpdate
service:
/ASCQS/
QS_ADDRESS_UPDATE
rfcdest –D The name of the RFC
destination, by default either
DQMSearch or DQMUpdate.
Ensure that this is the same
name specified in the file
saprfc.ini, which is in the
root folder of the data
quality module installation,
by default
C:\IBM\ISDQSAP\saprfc.ini.
DBName –d The name of the reference
database
DBUser -u The user account that created
the reference database.
Chapter 5. Managing data quality module services 23

Table 2. Command variables (continued)
DBPass -p The encoded password for
the reference database.
Create the encoded password
by executing
from the installation

directory of the data quality
module, where DBpassword is
the password for user
account.
logname –l The name and path of the
log file that the service
writes logging information to
lognameall The name and path of the
log file that the service
rotates logs to
tracelevel –t The value used by the
service to determine how
much detail is written to the
log (0–9). A value of 9 is
used only to indicate a
problem that requires
investigation.
iload –i For update only, this flag is
set to 1 when an initial load
is run. After the initial load,
reset the flag to param=0.
Related tasks
“Editing the saprfc.ini file” on page 25
You edit the saprfc.ini file to specify the host name and service name of the
SAP gateway.
Trace level settings for the update and search services

You can set trace levels to adjust the amount of information written to the log files.
The following tables list the trace level settings for each service. You can specify
trace levels for each service in the command files, DQMUpdate.cmd and
DQMSearch.cmd.
Table 3. Update service trace level settings
Error level Description
0 Errors and global function calls
1 Errors, global function calls, and calling adapters
2 Errors, global function calls, calling adapters, SQL statements, and
performance information
3 Errors, global function calls, calling adapters, SQL statements,
performance information, SAP input data, convert data, send data, and
SAP information summary
4 Same as level 3; reserved

Table 4. Search service trace level settings
Error level Description
0 Errors and global function calls
1 Errors, global function calls, and calling adapters
2 Errors, global function calls, calling adapters, send data, blocking key,
SQL statements and results
3 Errors, global function calls, calling adapters, send data, blocking key,
SQL statements, results, SAP input data, and sending to DQM data
4 Same as level 3; reserved
Editing the saprfc.ini file

You edit the saprfc.ini file to specify the host name and service name of the SAP
gateway.
Before you start the data quality module services, you must edit the saprfc.ini file
to specify information about the SAP gateway, and to ensure that the default
values match values that are specified in the command files for the update and
search services. The saprfc.ini file is in the root folder of your installation of IBM
To edit the saprfc.ini file:

1. In a text editor, open the saprfc.ini.
2. Specify the following values:
v For the GWHOST parameter, specify the SAP host name or IP address of the
SAP gateway.
v For the GWSERV parameter, specify the service name of the SAP gateway.
3. Ensure that the values for the DEST parameters match the values that are
specified for the rfcdest variables in the command files for the search and
update services. By default, these values are DQMSearch and DQMUpdate.
4. Save your changes.
Related reference
“Command variables for the update and search services” on page 22
The values of command variables specify information about the update and
search services, including the locations of components and log files.
Parameters for the saprfc.ini file

The parameter values for the saprfc.ini file specify information about the remote
function call (RFC) destinations and the SAP gateway.
The following table describes parameters for the saprfc.ini file, which is installed
by default in C:\IBM\ISDQSAP. There are two sets of parameters with identical
names. The first set is used by the search service and the second set is used by the
update service.
Parameter Description
DEST The value of the rfcdest variable in the DQMSearch.cmd file. The
default value is DQMSearch.

Parameter Description
TYPE Specifies the type of connection. Do not change the default value of
R, which specifies that this is a registered RFC server connection.
PROGID The program ID for the search service. The default value is
DQMSearch. This value must match the program ID that you
specify when you create the RFC destination for search.
GWHOST The SAP host name or IP address of the SAP gateway.
GWSERV The service name of the SAP gateway.
RFC_TRACE The trace level for this RFC connection. The default value is 1.
DEST The value of the rfcdest variable in the DQMUpdate.cmd file. The
default value is DQMUpdate.
TYPE Specifies the type of connection. Do not change the default value of
R, which specifies that this is a registered RFC server connection.
PROGID The program ID for the update service. The default value is
DQMUpdate. This value must match the program ID that you
specify when you create the RFC destination for update.
GWHOST The SAP host name or IP address of the SAP gateway.
GWSERV The service name of the SAP gateway.
RFC_TRACE The trace level for this RFC connection. The default value is 1.
Installing instances of update and search services

When you install additional instances of the update and search services, you install
one instance at a time.
When you install a service instance you must specify a number to append to the
service name. For example, if you install an instance of the update service and
specify the number 3, the installed service is named DQMUpdate3. If you do not
specify a number, the service instance is not installed.
Specify a number that is not used by an existing service instance of the type that
you are creating. For example, the DQMSearch2 instance is installed by default. If
you specify the number 2 when you install a new instance of the search service,
the instance is updated, but no new instance is created.
To install an instance of the update service or the search service:

1. Open a command prompt and change to the directory where you installed the
data quality module, by default C:\IBM\ISDQSAP.
2. Specify the type of service instance to install and the number to append to its
name:
v To create an instance of the search service, enter DQMSearchSvrInst.cmd
number, where number is the number to append to the service instance name.
v To create an instance of the update service, enter DQMUpdateSvrInst.cmd
number, where number is the number to append to the service instance name.
For example, to create an instance of the search service that is named
DQMSearch3, enter DQMSearchSvrInst.cmd 3.
You can start the new service instance in the Services window of the Windows
Control Panel.
Related concepts

“Data quality module services” on page 21
database and coordinate the search components. The index refresh service
updates the search index.
Removing instances of update and search services

You can remove one instance of a service at a time.
To remove an instance of the update service or the search service:

1. In the Services window of the Windows Control Panel, stop the instance of the
service that you want to remove.
2. Open a command prompt and change to the directory where you installed the
data quality module, by default C:\IBM\ISDQSAP.
3. Enter DQMWinService.exe -r instance_name, where instance_name is the name of
the service instance that you want to remove.
For example, to remove the update service instance that is named
DQMUpdate3, enter DQMWinService.exe -r DQMUpdate3.
Related concepts
Starting and stopping the update and search services

You can start and stop instances of the services from the Windows Control Panel.
Prerequisite: You must edit the command file for each service before you start it
for the first time.
Each instance of the update service is named DQMUpdateInstance_Number, where

Instance_Number is a digit that makes the instance name unique. For example, the
default update service instances are DQMUpdate1 and DQMUpdate2.
Each instance of the search service is named DQMSearchInstance_Number, where

Instance_Number is a digit that makes the instance name unique. For example, the
default search service instances are DQMSearch1 and DQMSearch2.
To start or stop an instance of the update or search service:
In the Services window of the Windows Control Panel, right-click the name of an
update or search service instance, and choose Start or Stop.
Related concepts
Related tasks
Chapter 4, “Preparing the SAP components,” on page 17

Chapter 6, “Loading the reference database,” on page 29
You load the reference database with a subset of information from the SAP
CAM database.

Chapter 6. Loading the reference database
You load the reference database with a subset of information from the SAP CAM
database.
You run the initial load process to load information from the activated index pools.
You can run the initial load process again later if you need to add more index
pools.
Initial load process

The initial load process populates the reference database with the address data that
is used for the error-tolerant search and duplicate check processes.
The initial load process uses the activated index pools to load a subset of the
address information from the SAP CAM database into the reference database. The
process also adds index information that is used for searching.
During the initial load for each active index pool, you can specify two package
sizes. The default package size for the addresses read from SAP is 10,000 records.
The RFC package size, which determines how many of the read records to send at
a time, is limited to a maximum of 4,000 records.
After the process finishes, a log message provides the following information:
v A message that indicates which addresses loaded completely.
v The total number of addresses of all selected index pools that are read and
transferred, and the required time to load them.
Running the initial load process

You use the Initial Load window to specify the details of all or part of the initial
load process.
Prerequisite: “Editing the command files for the update and search services” on
page 22
To run the initial load process:

1. In the Windows Control Panel, start the service DQMUpdate.
2. In SAP, call transaction /n/ASCQS/QS_INI. The IBM IS: Initial Load window
opens.
3. In the Address Specification panel, ensure that no individual index pools are
specified. All active index pools are selected if no individual index pools are
specified.
4. In the Package Size Address Read field, type a package size, or accept the
default of 10,000.
5. Select Transfer via RFC.
6. In the RFC Specification panel, type DQMUpdate in the RFC Destination for
Update field.
7. In the Package Size RFC (max 4,000) field, type the number of addresses for
the RFC queue to send in one step.

8. Select Queue Processing (if errors) to enqueue RFC packages that cannot be
sent when RFC connection errors occur.
9. Click Program → Execute in Background to start the transfer process in the
background.
10. When the initial load process is complete, on the computer where IBM
Information Server Data Quality Module for SAP is installed, stop the update
service and edit the iload command variable:
a. In the Windows Control Panel, stop the service DQMUpdate.
b. In the file DQMUpdate.cmd, change the value of iload to 0.
Related reference
Running the initial load process by using a file

You can generate a file that contains the updates to the reference database, and use
the file to run the initial load process. After you run the initial load process by
using a file, you must start the crawl and build the search index.
Prerequisites:
v “Editing the command files for the update and search services” on page 22
v Ask the system administrator for the directory location of the SAP data that is
used for error-tolerant searches. The SAP system must be able to read from and
write to this directory.
To run the initial load process by using a file:

1. Follow steps 1-4 of “Running the initial load process” on page 29.
2. In SAP, in the IBM IS Initial Load window, select Transfer in File.
3. In the Combination of Path and File field, type the path and file for the SAP
data that is used for error-tolerant searches.
4. In the RFC Destination for Update field of the RFC Specification panel, type
DQMUpdate.
5. Click Program → Execute in Background to start the process in the background.
6. Copy the generated file to the DQM Server directory on the computer where
you installed the data quality module.
7. To perform the initial load, set the file mode initial load options in the
DQMUpdateFileMode.cmd file and run the file.
The reference database is populated.
You must start the crawl and build the search index.
Related reference
Command variables for running the initial load process by using

a file
The values of command variables specify information about the locations of
components and log files.

The command variables values for running the initial load process by using a file
are specified in the file DQMUpdateFileMode.cmd. This file is the root folder of
your installation of IBM Information Server Data Quality Module for SAP, by
Table 5. Command variables for running initial load in file mode
workdrive The drive where you installed IBM Information
Server Data Quality Module for SAP.
INTBIN The root folder of the data quality module
installation, by default C:\IBM\ISDQSAP.
ARD –a The path to the data quality module application
definition: %INTBIN%\ISDQMSAP\Scripts\ARDS\
MNVCRMS
Controls –c %INTBIN%\ISDQMSAP\Controls
DBName –d The name of the reference database.
logname –l The name and path of the log file that the service
writes logging information to.
DBUser -u The user account that created the reference database.
DBPass -p The encoded password for the reference database.
Create the encoded password by executing
from the installation directory of the data quality

module, where DBpassword is the password for user
account.
iload –i This flag is set to 1 when an initial load is run. After
the initial load, reset the flag to param=0.
ilfile -f The name of the SAP extract.
ilbatch -b The number of records to be read and processed at
one time. The maximum is 10,000.
tracelevel –t The value used by the service to determine how
much detail is written to the log (0–9). A value of 9
is used only to indicate a problem that requires
investigation.
Starting a full crawl

You start a full crawl to prepare the search index when you use a file to run the
initial load process. A full crawl indexes records in the entire reference database.
Prerequisite: “Creating the crawler” on page 12
To start a full crawl:
1. Open OmniFind Enterprise Search Administrator, and click (Monitor).
2. Click (Start). The crawler service is started when the Status button
turns green.
3. Click (Details).
Chapter 6. Loading the reference database 31

4. Click (Start full crawl) to start the full crawl.
5. Click OK. The crawler service is working if the Status button is green.
6. Click (Refresh) periodically until the screen indicates that 100

percent of the tables are completely crawled. Do not click the browser refresh
button.
7. When all tables are crawled, click (Stop).

8. Click Return.
9. Click Parse.
10. Click (Details). One of the following messages appears:

The parser is processing documents
The parser has not finished parsing the current set of documents
The parser is sleeping
If the size of the store is less than the number of records in the
database, which is the number of records crawled, the parser is not
finished. It will wake up and parse another set of documents. It may
take several iterations of parse and sleep before finishing.
11. Click (Refresh) periodically to update the parser statistics,

until the parser is sleeping and all records are parsed. Do not stop the parser
service.
12. Click Return.
In OmniFind Enterprise Search Administrator, build the index.
Building the index

You build the index after starting a full crawl when you run the initial load process
by using a file.
To build the index:

1. On the home page of OmniFind Enterprise Search Administrator, click Index.
2. Scroll the page to access the main index section, where the wildcard options are
set for the next index build.
3. Click (Start) to start the main index build. The Status button displays a
green arrow: .
4. Click (Refresh) to update the index build statistics. Do not

click the browser refresh button. When the build completes successfully, the
Status button displays a green check mark. The Status table shows response
times and the number of documents. If the build fails, the button displays a red
X. The index build status history is retained so that the latest build status
report line is in the second row. The indexing service stops when the index
build is finished.

5. Verify that the number of documents equals the number of records that were
crawled.
6. Click Search.
7. Verify that the Status button displays a green arrow, which means that the
search is running. If the search is not running, click (Start). The collection
is ready for search.
Chapter 6. Loading the reference database 33

Chapter 7. Running the duplicate check process
Prerequisite: Chapter 2, “Installing and configuring the data quality module,” on

page 3
To run the duplicate check process:

1. In SAP, call a transaction type, such as create or change for a vendor, customer,
or business partner.
2. Enter the data for the transaction and click the Save icon. The duplicate check
process starts automatically. Addresses that meet the threshold criteria are
shown in the duplicate check hit list.
3. Optional: To change the number of returned results by making the duplicate
check process more or less restrictive, click Change Threshold and type a
lower threshold value to return more results or a higher threshold value to
return fewer results.
4. Select an address, keep the original address, or cancel the results if you want
to refine your search.
Option Description
To select a duplicate address: 1. Select an address in the duplicate check
hit list.
2. Click Select Duplicate.
3. Save the entry.
To keep the original address: Click the check mark button (Continue
without duplicate).
To cancel the results Click the cancel button.
Related concepts

Chapter 8. Threshold values for displaying matching objects
The error-tolerant search process uses a default threshold of 10 percent. The

duplicate check process uses a default threshold of 15 percent. These values are
specified in the Customizing table and you can adjust them when you run
error-tolerant search or the duplicate check process.
The data quality module software assigns weights based on the likelihood that
your search criteria and the data objects found by the search and duplicate check
processes are the same. A higher weight means a higher likelihood that the found
objects match the criteria.
Threshold values determine what percentage of the objects that meet the weight
criteria are shown in the hit list. As you increase the threshold value, the number
of objects that are shown in the list decreases and only the objects with the highest
weights are shown.
Related concepts
“Values for the Customizing table” on page 18
You can edit values in the Customizing table to change thresholds, RFC
destinations, and packet size.
Related tasks
Chapter 7, “Running the duplicate check process,” on page 35
Chapter 9, “Running the error-tolerant search process,” on page 39
business partners when you do not have sufficient information about the name
or address. In SAP applications, this search method is also called fuzzy search
or rough search.

Chapter 9. Running the error-tolerant search process
business partners when you do not have sufficient information about the name or
address. In SAP applications, this search method is also called fuzzy search or
rough search.
Prerequisite: Chapter 2, “Installing and configuring the data quality module,” on

page 3
To run the error-tolerant search process:

1. In SAP, call a transaction.
2. Search for vendors, customers or business partners.
3. From the initial display screen, select the appropriate choice for your search:
v Vendors by Address Attributes (Fuzzy Search).
v Customers by Address Attributes (Fuzzy Search).
v Business Partners by Address Attributes (Fuzzy Search).
4. In the search window that opens, type the name of the vendor, customer, or
business partner.
5. Press Enter to start the search. Addresses are returned that contain your search
criteria.
6. Optional: To change the number of results returned by making the search more
or less restrictive, click Change Threshold and type a lower threshold value to
return more results or a higher threshold value to return fewer results.
7. Optional: To refine the search, on the tool bar, click the filter button.
8. Optional: To start a new search, at the bottom of the window, click the filter
(New Selection) button.
9. When you find the address that you are searching for, select it and click Select.
The address that you selected is displayed in the Transaction window where
you started the error-tolerant search process.
Related concepts

Chapter 10. Error messages
You can receive error messages when saving records, updating the database or
using the search and update applications.
The following tables explain possible error messages and how to fix the errors.
Table 6. Error messages when you save a record to the SAP CAM database or delete a
record from the database
Message Cause Solution
DQ Address Hardware Error These messages indicate that Test the RFC connections,
(RFC-Queue) the new or changed address and fix them if they are not
could not be updated in the working. The next time a
IBM DQ Communication Error reference data base but was user creates or updates an
(RFC-Queue) written instead to the RFC address, the reference
queue. These errors can occur database is updated with all
from problems with the RFC the addresses that are in the
connections. The system RFC queue. To immediately
usually recovers from the update the reference database
error and resets the with the addresses in the
connections properly. RFC queue, the administrator
can clear the RFC queue.
Table 7. Error messages when you run the error-tolerant search process
Initial Load has not been Before you can run an Check your activated index
processed completely error-tolerant search, the pools. At least one index
addresses of the active index pool should show empty
pools must be processed. values for initial load. Run
This message occurs if the initial load again to process
addresses were not all the activated index pools.
processed.
Customizing not done This message appears if you Stop the error-tolerant search,
did not update the ensure that the index pools
Customizing table before are activated, update the
starting error-tolerant search. Customizing table as
necessary, and run the initial
load process again.
No RFC destination Search queries cannot be Open the Customizing table
maintained for search transferred to data quality and specify the RFC
process module server unless the destinations.
RFC destination is specified
in the Customizing table.
Table 8. Errors when you use the DQMUpdate and DQMSearch applications
INTERNAL_ERROR This message occurs when If system does not recover,
connections are lost with the the administrator should
reference database or the check to see if the services
search server. have stopped, and restart the
services if necessary.

Table 8. Errors when you use the DQMUpdate and DQMSearch applications (continued)
PARAMETER_ERROR This message occurs if a Debug the system and
value for a required specify the required value. If
parameter is not specified in the error persists, contact
an SAP table. ibm.com/support.
NO_UPDATE This message occurs when Ensure the service is still
the DQMUpdate application running. Check the logs. If
cannot commit the database the error persists, contact
operations because the RFC ibm.com/support.
server could not write to the
database or to the search
server.
Clearing the RFC queue

You can update the reference database with addresses that are in the RFC queue.
To clear the RFC queue:

1. In SAP, call transaction SMQ1.
2. In the qRFC Monitor (Outbound Queue) page, scroll to the text
Z_ASCENTIAL_QS_FS_AND_DC and double-click the text.
3. In the next page, press F5.
Addresses in the queue are sent to the update program and the reference database
is updated.

Chapter 11. Troubleshooting data quality module errors
You can seek solutions to communication problems that prevent users from
running the error-tolerant search or duplicate check processes.
When users have recurring communication problems from which the system does
not automatically recover, the administrator should do the following sequence of
steps until the problem is solved or until you are required to contact IBM support.
To troubleshoot data quality module errors:

1. “Ensuring that the update services are running”
2. “Ensuring that the search services are running”
3. “Ensuring that IBM DB2 is running” on page 44
4. “Ensuring that the ESAdmin application is running” on page 44
5. “Ensuring that IBM OmniFind services are running” on page 45
6. “Investigating the search server communication with the collection” on page 45
7. “Ensuring that the data listener is running” on page 45
8. “Ensuring that the parse and search operations are running” on page 46
Ensuring that the update services are running

This is the first task in troubleshooting data quality module errors.
To ensure that the update services are running:

1. In the Services window of the Windows Control Panel on the computer where
you installed IBM Information Server Data Quality Module for SAP, check to
see if all instances of the update service are started.
2. If all instances are started, skip the remaining steps in this task. Ensure that the
search services are running.
3. If any instance is not started, right-click the instance name and choose Start.
4. If the instances start and remain started, skip the remaining steps in this task.
Ensure that the search services are running.
5. If any instance does not remain started, use a text editor to open the file
DQMUpdate.cmd. This file is in the root folder of your installation of the data
quality module, by default C:\IBM\ISDQSAP.
6. Edit the DQMUpdate.cmd file to set the value for the tracelevel variable to 3,
and save the file.
7. Start the update service instance.
8. Contact ibm.com/support and provide the log file whose name corresponds to
the service instance that is not working, for example, DQMUpdate3.log.
Services log files are in the root directory of the data quality module
installation.
Ensuring that the search services are running

This is the second task in troubleshooting data quality module errors.
To ensure that the search services are running:

you installed IBM Information Server Data Quality Module for SAP, check to
see if all instances of the search service are started.
2. If all instances are started, skip the remaining steps in this task. Ensure that
IBM DB2 is running.
3. If any instance is not started, right-click the instance name and choose Start.
4. If the instances start and remain started, skip the remaining steps in this task.
Ensure that IBM DB2 is running.
5. If any instance does not remain started, use a text editor to open the
DQMSearch.cmd file. This file is in the root folder of your installation of IBM
6. Edit the DQMSearch.cmd file to set the value for thetracelevel variable to 3,
and save the file.
7. Start the search service instance that was not started.
8. Contact ibm.com/support and provide the log file whose name corresponds to
the service instance that is not working, for example, DQMSearch3.log. Services
log files are in the root directory of the data quality module installation.
Ensuring that IBM DB2 is running

This is the third task in troubleshooting data quality module errors.
To ensure that IBM DB2 is running:

you installed the server component of IBM DB2, check to see that all DB2
services are started.
2. If the services are started, Ensure that esadmin is running.
3. If the services are not started, see the documentation for IBM DB2 on how to
start the services.
Ensuring that the ESAdmin application is running

This is the fourth task in troubleshooting data quality module errors.
To ensure that the ESAdmin application is running:

1. In a command prompt on the computer where you installed IBM OmniFind
Enterprise Edition, enter the command esadmin check. A list of session IDs and
their states is displayed.
The following session IDs should display Started in the State column:
2. Ensure that the following session IDs have a state of Started:
v configmanager
v controller
v datalistener
v discovery
v monitor
v parserservice
v resource.node1
v resourcemanager
v scheduler
v searchmanager.node1

v utilities.node1
3. If the required sessions are started, skip the remaining steps in this task. Ensure
that IBM OmniFind services are running.
4. If any of the required session IDs are not started, enter the command esadmin
stop.
5. Enter the command esadmin start.
6. Enter the command esadmin check, and check to see that the required sessions
are started..
7. If the required sessions are not started, complete the remaining troubleshooting
tasks, and then repeat this task. If the required sessions are not started after
you repeat this task, contact ibm.com/support.
Ensuring that IBM OmniFind services are running

This is the fifth task in troubleshooting data quality module errors.
To ensure the IBM OmniFind services are running:

you installed IBM OmniFind Enterprise Edition, ensure that that the following
services are started:
v IBM HTTP Server 6.0.
v IBM WebSphere Application Server V6 – ESSearchServer
v IBM WebSphere Application Server V6 - node_name, where node_name is the
default node name that you accepted for WebSphere Application Server
when you installed IBM OmniFind Enterprise Edition.
v IBM WebSphere Information Integrator OmniFind Edition.
2. Start any of the services that are not started.
3. If the services do not start, contact ibm.com/support.
Investigating the search server communication with the collection

This is the sixth step in troubleshooting data quality module errors.
To investigate the search server communication with the collection:

1. In Windows Internet Explorer, browse to http://OmniFind_host_name/
ESSearchApplication, where OmniFind_host_name is the host name of the
computer on which you installed IBM OmniFind Enterprise Edition.
2. If there is no error in determining the collection, skip the rest of the steps in
this task. Ensure that the data listener is running.
3. If there is an error determining the collection, click Refresh in the search
application. Do not click the Web browser refresh button.
4. If the error persists, copy the error text and contact ibm.com/support .
Ensuring that the data listener is running

This is the seventh task in troubleshooting data quality module errors.
To ensure that the data lListener is running:

ESAdmin, where OmniFind_host_name is the host name of the computer on
which you installed IBM OmniFind Enterprise Edition.
Chapter 11. Troubleshooting data quality module errors 45

2. Enter the user ID and password for the ESAdmin account.
3. If the Collections page does display the collection name that you specified
when you created the collection, copy the error text and contact
ibm.com/support .
4. If the Collections page does display the collection name that you specified
when you created the collection, click System on the menu bar.
5. On the System page, select the Data Listener tab.
6. If the Status icon on the Data Listener tab is not green, click (Reload) to
reload the page. If the Status icon is not green after the page reloads, record the
error and contact ibm.com/support.
7. If the Status icon is green, click (Edit).

8. Click Configure support for Data Listener applications. A client ID should be
displayed in the Data Listener client ID field. If no client ID is displayed,
contact ibm.com/support.
Ensuring that the parse and search operations are running

This is the eighth task in troubleshooting data quality module errors.
To ensure that parse and search operations are running:

ESAdmin, where OmniFind_host_name is the host name of the computer on
which you installed IBM OmniFind Enterprise Edition.
2. Enter the user ID and password for the ESAdmin account.
3. If the Collections page does not display the collection name that you specified
when you created the collection, copy the error text and contact
ibm.com/support.
4. If the Collections page displays the collection name that you specified, and the
icons beneath Parse and Search are green, click (Refresh) and
skip the remaining steps in this task. The parse and search operations are
running.
5. If the Collections page displays the collection name that you specified, but the
icons beneath Parse and Search are not green, click the icon beneath Parse.
6. On the Parse tab, click to reload the page.

7. If the Status icon on the Parse tab is not green, contact ibm.com/support.
8. If the Status icon on the Parse tab is green, the parse operation is running.
Select the Search tab and click to reload the page. The Status icon on the
Search tab should turn green, to indicate that the search operation is running.
9. If the Status icon on the Search tab does not turn green, contact
ibm.com/support.

Accessing information about IBM
IBM has several methods for you to learn about products and services.
You can find the latest information on the Web at www.ibm.com/software/data/

integration/info_server/
v Product documentation in PDF and online information centers
v Product downloads and fix packs
v Release notes and other support documentation
v Web resources, such as white papers and IBM Redbooks™
v Newsgroups and user groups
v Book orders
To access product documentation, go to this site:
publib.boulder.ibm.com/infocenter/iisinfsv/v8r0/index.jsp
You can order IBM publications online or through your local IBM representative.
v To order publications online, go to the IBM Publications Center at
www.ibm.com/shop/publications/order.
v To order publications by telephone in the United States, call 1-800-879-2755.
To find your local IBM representative, go to the IBM Directory of Worldwide

Contacts at www.ibm.com/planetwide.
Providing comments on the documentation

Please send any comments that you have about this information or other
documentation.
Your feedback helps IBM to provide quality information. You can use any of the
following methods to provide comments:
v Send your comments using the online readers’ comment form at
www.ibm.com/software/awdtools/rcf/.
v Send your comments by e-mail to comments@us.ibm.com. Include the name of
the product, the version number of the product, and the name and part number
of the information (if applicable). If you are commenting on specific text, please
include the location of the text (for example, a title, a table number, or a page
number).

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation

Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law: INTERNATIONAL
BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION ″AS IS″
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003 U.S.A.
Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM’s future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:
(C) (your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. (C) Copyright IBM Corp. _enter the year or years_. All rights
reserved.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
IBM trademarks and certain non-IBM trademarks are marked at their first
occurrence in this document.
See http://www.ibm.com/legal/copytrade.shtml for information about IBM

trademarks.
The following terms are trademarks or registered trademarks of other companies:
Java™ and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows, Windows NT®, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
Intel®, Intel Inside® (logos), MMX and Pentium® are trademarks of Intel
Corporation in the United States, other countries, or both.
UNIX® is a registered trademark of The Open Group in the United States and
other countries.
Linux® is a trademark of Linus Torvalds in the United States, other countries, or

both.
Other company, product or service names might be trademarks or service marks of

others.
Notices 51
Index
Special characters data quality module (continued)
tasks to install and configure 3
IBM OmniFind Data Listener 13
IBM OmniFind Enterprise Edition
/n/ASCQS/QS_CUS1 transaction 18 troubleshooting 43 installing 5
/n/ASCQS/QS_INI transaction 29 databases prerequisites 5
reference 1 search extender 1
SAP CAM 1 services 45
A synchronizing 1 troubleshooting ESAdmin errors 44
activating documentation iload command variable, editing 29, 30
data listener 13 ordering 47 importing business add-in package 15
DB2 crawler 7 Web site 47 index pools, activating 18
index pools 18 DQMSearch 17 index pools, displayed in Customizing
address data, populating reference DQMSearch.cmd 22 table 18
database 29 DQMUpdate 17 initial load, running 29
address management, node text 16 DQMUpdate.cmd 22 initial load, running by using file 30
address management, verifying 15 DQMUpdateFileMode.cmd 31 install wizard 8
duplicate check installation, sequence of tasks 3
default threshold value 37 installing
B definition 1
running 35
console mode 9
data quality module 8
building the index 32 data quality module in silent mode 9
business add-in package 1, 15 IBM DB2 version 9.1 10
E IBM OmniFind Enterprise Edition 5
prerequisites for system
C editing command files for search and
update services 22
components 5
CAM 1 reference database 10
editing iload command variable 29, 30
cancelling the customizing program 18 search extender 5
error messages 41
Central Address Management 1 system components 5
error-tolerant search
collection for search index 11 update and search service
default threshold value 37
command files for search and update instances 26
definition 1
services, editing 22 WebSphere Application Server 5
running 39
command variables for initial load file WebSphere Application Server 6.0
errors, troubleshooting 43
mode 31 Refresh Pack 2 7
es.cfg file 9
command variables for update and search is_dq_module_sap.rsp 9
services 22 ISDQMSAP.properties 14
comments on documentation 47
configuration, sequence of tasks 3 F
configuring index to use wildcard file, using for initial load
full crawl, starting 31
30 K
characters 13 KNA1 index pools 18
configuring service properties 14 fuzzy search 39
console mode, installing in 9
Control Panel icons for services 21
crawler, creating 12 H L
creating legal notices 49
HTTP server
collection for search index 11 license file for IBM DB2 version 9.1 10
installation directory 5
crawler 12 loading reference database 29
update.exe 7
RFC destinations 17 updateinstaller folder 7
CRM systems 18 updating 7
customizing program 18 N
Customizing table, updating 18 netstat command 5
Customizing table, values 18
I node text 16
IBM DB2 version 9.1
D DB2 crawler, activating 7
installing client and server 10 O
data listener, starting 13 license file 10 OmniFind Enterprise Search
data quality module prerequisites 10 Administrator
architecture 1 reference database 1 building the index 32
installing 8 troubleshooting 44 configuring index to use wildcard
installing in silent mode 9 IBM Information Server Data Quality characters 13
platform 5 Module for SAP, see data quality creating the collection 11
prerequisites for installing 5 module 1 creating the crawler 12
response file 9

OmniFind Enterprise Search
Administrator (continued)
S T
preparing search index 11 SAINT transaction 15 thresholds
starting a full crawl 31 SAP CAM database 1 changing during duplicate check
starting the data listener 13 SAP components, preparing 17 process 35
starting the parser service 12 SAP gateway parameters 25 changing during error-tolerant
OmniFind, see IBM OmniFind Enterprise SAP transactions search 39
Edition 1 /n/ASCQS/QS_CUS1 18 in Customizing table 18
/n/ASCQS/QS_INI 29 overview 37
SAINT 15 trace level settings for update and
SE09 16 search 24
P SIMGH 16 trademarks 51
package sizes for initial load 29 SM59 17 transactions
packet size 18 SPRO 15 /n/ASCQS/QS_CUS1 18
parser service 12 saprfc.ini file, editing 25 /n/ASCQS/QS_INI 29
platform, required to install data quality saprfc.ini file, parameters 25 SAINT 15
module components 5 SE09 transaction 16 SE09 16
plug-in, WebSphere Application search extender, in system architecture 1 SIMGH 16
Server 8 search extender, installing 5 SM59 17
ports, determining available 5 search index SPRO 15
preparing SAP components 17 building the index 32
preparing search index 11 configuring for wildcard
prerequisites
data quality module components 5
characteres 13
creating the collection 11
U
IBM DB2 version 9.1 10 update service
creating the crawler 12
installing IBM OmniFind Enterprise command file 22
preparing 11
Edition 5 command line example 22
starting a full crawl 31
preparing search index 11 Control Panel icon 21
starting the data listener 13
reference database 10 installing instances 26
starting the parser service 12
WebSphere Application Server 6.0 overview 21
search service
Refresh Pack 2 7 removing instances 27
command file 22
program ID 17 RFC destination 18
Control Panel icon 21
starting and stopping 27
installing instances 26
starting automatically 21
overview 21
stopping after initial load 29, 30
R removing instances 27
trace level settings 24
RAID disk array 5 RFC destination 18
troubleshooting 43
readers’ comment form 47 starting and stopping 27
update.exe
reference database starting automatically 21
HTTP server 7
architecture 1 trace level settings 24
WebSphere Application Server 7
creating 10 troubleshooting 43
WebSphere Application Server
initial load 29 search, error-tolerant 39
plug-in 8
installing and registering 10 service properties, configuring 14
updateinstaller folder
license file 10 service property variables 14
HTTP Server 7
loading 29 services
prerequisites 10 command variables 22
sychronizing with CAM database 1 editing command files 22
plug-in 8
registering reference database license environment configuration 22
updating
key 10 starting and stopping 27
Customizing table 18
remote functional call (RFC) starting automatically 21
HTTP server 7
destinations 17 trace level settings 24
removing update and search services 27 SIMGH transaction 16
response file for installing data quality SM59 transaction 17
plug-in 7, 8
module 9 SPRO transaction 15
RFC destinations for search and starting
full crawl 31
update 18
RFC destinations, creating 17 parser service 12 V
RFC queue, clearing 42 services automatically 21 variables
rough search 39 update and search services 27 initial load file mode 31
running stopping update and search services 27 service properties 14
customizing program 18 stopping update service after initial update and search 22
duplicate check 35 load 29, 30
error-tolerant search 39 synchronizing databases 1
initial load by using file 30 system architecture 1
system components, installing 5
W
initial load of reference database 29 WebSphere Application Server
First Steps 7
installing 5
plug-in, updating 8

WebSphere Application Server (continued)
update.exe 7
updateinstaller folder 7
updating 7
version 6.0 Refresh Pack 2 7
WebSphere Application Server plug-in
update.exe 8
updateinstaller folder 8
updating 8
Windows 2003 Enterprise Edition 5
Index 55

Printed in USA
LC19-1181-00

Guide To IBM Information Server Data Quality Module For SAP

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Guide To IBM Information Server Data Quality Module For SAP

Transféré par

Droits d'auteur :

Formats disponibles

IBM Information Server Data Quality Module for SAP

Guide to IBM Information Server Data Quality Module for SAP

Guide to IBM Information Server Data Quality Module for SAP

© Copyright IBM Corp. 2006, 2007 iii

The following figure illustrates the architecture of the system.

© Copyright IBM Corp. 2006, 2007 1

SAP business IBM OmniFind server

CAM Database Reference

2 Guide to IBM Information Server Data Quality Module for SAP

© Copyright IBM Corp. 2006, 2007 3

Installing IBM OmniFind Enterprise Edition

© Copyright IBM Corp. 2006, 2007 5

To install IBM OmniFind Enterprise Edition:

6 Guide to IBM Information Server Data Quality Module for SAP

Prerequisite: “Installing IBM OmniFind Enterprise Edition” on page 5.

To install WebSphere Application Server 6.0 Refresh Pack 2:

Updating the HTTP server

Prerequisite: “Installing IBM OmniFind Enterprise Edition” on page 5.

To update the HTTP server:

Updating WebSphere Application Server

Prerequisite: “Updating the HTTP server.”

To update WebSphere Application Server:

Chapter 3. Installing and configuring the system components 7

Updating the WebSphere Application Server plug-in

Prerequisite: “Updating WebSphere Application Server” on page 7.

To update the WebSphere Application Server plug-in:

Installing IBM Information Server Data Quality Module for SAP

To install the data quality module, do one of the following tasks:

Installing the data quality module by using the graphical

To install the data quality module by using the graphical interface:

8 Guide to IBM Information Server Data Quality Module for SAP

Installing the data quality module in console mode

To install the data quality module in console mode:

Installing the data quality module in silent mode

To install the data quality module in silent mode:

Editing the es.cfg file

Chapter 3. Installing and configuring the system components 9

Installing and registering the reference database

Installation is supported only on Microsoft Windows 2003 Enterprise Edition. You

To install and register the reference database:

Creating the reference database

Prerequisite: “Installing and registering the reference database”

To create the reference database:

10 Guide to IBM Information Server Data Quality Module for SAP

The reference database is created.

Preparing the search index

To prepare the search index:

Creating the collection

Prerequisite: Log in to OmniFind Enterprise Search Administrator.

To create the collection:

Chapter 3. Installing and configuring the system components 11

In OmniFind Enterprise Search Administrator, start the parser service.

Starting the parser service

Prerequisite: “Creating the collection” on page 11

In OmniFind Enterprise Search Administrator, create the crawler.

Creating the crawler

Prerequisite: “Starting the parser service”

To create the crawler:

2. Under the ESAdmin toolbar, click (Edit).

17. Under Edit Options, click (Edit).

12 Guide to IBM Information Server Data Quality Module for SAP

Configuring the index to use wildcard characters